linux-kernel - Re: relative objtree change broke tar builds?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <53B71FB4.2000408@suse.cz>
Date:	Fri, 04 Jul 2014 23:42:12 +0200
From:	Michal Marek <mmarek@...e.cz>
To:	Ken Moffat <zarniwhoop@...world.com>
CC:	Randy Dunlap <rdunlap@...radead.org>,
	"J. Bruce Fields" <bfields@...ldses.org>,
	linux-kbuild@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: relative objtree change broke tar builds?

Dne 19.6.2014 03:21, Ken Moffat napsal(a):
> On Wed, Jun 18, 2014 at 09:47:28PM +0200, Michal Marek wrote:
>>
>> The idea is that one should be able to compare as much as possible
>> between the build of /usr/src/linux-<version_a> built in
>> /usr/src/linux-<version_a>/build and /usr/src/linux-<version_b> built in
>> /usr/src/linux-<version_b>/build.
> [...]
>  Some of us (me included) often build things as root, but it has
> many risks and people ought not to be led to believe it is
> necessarily the correct way to do things.  Over the past 14 years I
> have built kernels in ~/ as well as in other user-writable
> directories and I am puzzled about why the idea of /usr/src/linux*
> continues to exist.

I just used /usr/src/linux as an example. If I wrote
/dev/shm/linux-2.6/build, which is where I often builf kernels, then I'm
sure somebody would complain that they tried it and ran out of memory :-).

Michal
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/