| 1 |
On 19-09-2011 19:19:12 -0400, Joshua Kinard wrote: |
| 2 |
> >> Really, MacOS's filesystem layout is not something anyone in their right |
| 3 |
> >> mind should deign to mimic/copy. |
| 4 |
> > |
| 5 |
> > I didn't get that from either of the links you posted. Seems to me the |
| 6 |
> > systemd developers are looking at the split as a host-specific / vs |
| 7 |
> > host-independent /usr. |
| 8 |
> |
| 9 |
> From: |
| 10 |
> http://marc.info/?l=linux-hotplug&m=131206447302056&w=2 |
| 11 |
> |
| 12 |
> Kay Sievers writes: |
| 13 |
> |
| 14 |
> > What's not needed today is stuff in /. We can think of /usr a /System. |
| 15 |
> > The entire system is installed in one single directory, and that can |
| 16 |
> > be mounted r/o, or even shared between many hosts/guest. The stuff on |
| 17 |
> > the rootfs is always host-only then. |
| 18 |
> |
| 19 |
> It is from this that I derive the concept of a few folks wanting everything |
| 20 |
> in /usr, as-if to brand /usr the new / (where the 'old' / has just directory |
| 21 |
> stubs and a few symlinks, maybe some minor bits in /etc). That's also where |
| 22 |
> my Mac comment stems from, in that /System hides most of the details of the |
| 23 |
> BSD-nature of MacOS X, and tries to dissuade the user from ever having to go |
| 24 |
> in there. |
| 25 |
|
| 26 |
Not sure what you mean here. An OSX system has /bin, /sbin, and |
| 27 |
/usr/{bin,lib}. What's in /Library and /System is typically what the OS |
| 28 |
uses for its own "services" and graphical stuff. So, /System doesn't |
| 29 |
hide any BSD-nature to me. It's true that a normal user really has |
| 30 |
nothing to do in /System. |
| 31 |
|
| 32 |
|
| 33 |
-- |
| 34 |
Fabian Groffen |
| 35 |
Gentoo on a different level |
Archives