1 |
On 09/19/2011 07:17, Arun Raghavan wrote: |
2 |
|
3 |
> On 19 September 2011 16:07, Joshua Kinard <kumba@g.o> wrote: |
4 |
> [...] |
5 |
>> Yes, but some of us don't even want to have that initramfs built into our |
6 |
>> kernels. And no one, other than freedesktop.org* and a few people on |
7 |
>> linux-hotplug-devel*, said everything belongs in /usr. FHS clearly defines |
8 |
>> the roles for /, /bin, /sbin, /lib*, /usr, /var, /home, /tmp and the virtual |
9 |
>> fses. Plus others. |
10 |
>> |
11 |
>> http://www.freedesktop.org/wiki/Software/systemd/separate-usr-is-broken |
12 |
>> http://marc.info/?l=linux-hotplug&m=131206447302056&w=2 |
13 |
>> |
14 |
>> Really, MacOS's filesystem layout is not something anyone in their right |
15 |
>> mind should deign to mimic/copy. |
16 |
> |
17 |
> I didn't get that from either of the links you posted. Seems to me the |
18 |
> systemd developers are looking at the split as a host-specific / vs |
19 |
> host-independent /usr. |
20 |
|
21 |
|
22 |
From: |
23 |
http://marc.info/?l=linux-hotplug&m=131206447302056&w=2 |
24 |
|
25 |
Kay Sievers writes: |
26 |
|
27 |
> What's not needed today is stuff in /. We can think of /usr a /System. |
28 |
> The entire system is installed in one single directory, and that can |
29 |
> be mounted r/o, or even shared between many hosts/guest. The stuff on |
30 |
> the rootfs is always host-only then. |
31 |
|
32 |
It is from this that I derive the concept of a few folks wanting everything |
33 |
in /usr, as-if to brand /usr the new / (where the 'old' / has just directory |
34 |
stubs and a few symlinks, maybe some minor bits in /etc). That's also where |
35 |
my Mac comment stems from, in that /System hides most of the details of the |
36 |
BSD-nature of MacOS X, and tries to dissuade the user from ever having to go |
37 |
in there. |
38 |
|
39 |
Host-specific / and host-independent /usr is not itself a bad idea. I can |
40 |
envision quite a few useful scenarios for this. But on a single box, why? |
41 |
And for those of us with differing architectures, how would this add any |
42 |
benefit? Is this more of a detail for future RHEL releases (since Fedora is |
43 |
a type of proving ground for RH) so that sysadmins have an easier time |
44 |
managing them? Nothing wrong with it, but it needs to be a configurable |
45 |
choice by the end-user. |
46 |
|
47 |
I'll admit I may not be as informed as I oughta to be, but what I have read |
48 |
indicates that some people think this is the direction to go in, for various |
49 |
reasons. |
50 |
|
51 |
-- |
52 |
Joshua Kinard |
53 |
Gentoo/MIPS |
54 |
kumba@g.o |
55 |
4096R/D25D95E3 2011-03-28 |
56 |
|
57 |
"The past tempts us, the present confuses us, the future frightens us. And |
58 |
our lives slip away, moment by moment, lost in that vast, terrible in-between." |
59 |
|
60 |
--Emperor Turhan, Centauri Republic |