1 |
On Fri, 21 Dec 2012 09:10:22 +0100 |
2 |
"J. Roeleveld" <joost@××××××××.org> wrote: |
3 |
|
4 |
> On Thursday, December 20, 2012 09:31:36 AM Michał Górny wrote: |
5 |
> > On Thu, 20 Dec 2012 00:27:26 +0100 |
6 |
> > |
7 |
> > "J. Roeleveld" <joost@××××××××.org> wrote: |
8 |
> > > On Wednesday, December 19, 2012 09:13:28 AM Greg KH wrote: |
9 |
> > > > On Tue, Dec 18, 2012 at 08:21:36AM +0100, J. Roeleveld wrote: |
10 |
> > > > > On Mon, December 17, 2012 22:31, Greg KH wrote: |
11 |
> > > > > > On Mon, Dec 17, 2012 at 09:03:40PM +0100, J. Roeleveld wrote: |
12 |
> > > > > >> Olav Vitters <olav@×××××××.nl> wrote: |
13 |
> > > > > >> >On Mon, Dec 17, 2012 at 09:29:26AM -0500, Richard Yao wrote: |
14 |
> > > > > >> >> As I said in an earlier email, Lennart Poettering claims that it |
15 |
> > > > > >> >> does |
16 |
> > > > > >> >> not work. We are discussing some of the things necessary to make |
17 |
> > > > > >> >> it |
18 |
> > > > > >> > |
19 |
> > > > > >> >work. |
20 |
> > > > > >> > |
21 |
> > > > > >> >Just to repeat: |
22 |
> > > > > >> >In this thread it was claimed that a separate /usr is not |
23 |
> > > > > >> >supported by |
24 |
> > > > > >> >systemd/udev. |
25 |
> > > > > >> > |
26 |
> > > > > >> >A case which works with latest systemd on various distributions. I |
27 |
> > > > > >> >checked with upstream (not Lennart), and they confirmed it works. |
28 |
> > > > > >> >I |
29 |
> > > > > >> >can |
30 |
> > > > > >> >wait for Lennart to say the same, but really not needed. |
31 |
> > > > > >> > |
32 |
> > > > > >> >I assume this will again turn into a "but I meant something else". |
33 |
> > > > > >> |
34 |
> > > > > >> Olav. |
35 |
> > > > > >> |
36 |
> > > > > >> Lennart has stated that he considers a seperate /usr without init* |
37 |
> > > > > >> broken. |
38 |
> > > > > > |
39 |
> > > > > > Yes, as do I, and so do a lot of other developers. |
40 |
> > > > > |
41 |
> > > > > It is only "broken", because upstream decided to move everything into |
42 |
> > > > > /usr |
43 |
> > > > > that was previously in /. |
44 |
> > > > |
45 |
> > > > No, not at all, please see the web page that describes, in detail, the |
46 |
> > > > problems that has been going on for quite some time now, with the /usr |
47 |
> > > > and / partitions and packages. |
48 |
> > > > |
49 |
> > > > http://freedesktop.org/wiki/Software/systemd/separate-usr-is-broken |
50 |
> > > > |
51 |
> > > > One good solution to this issue is to move everything into /usr, and |
52 |
> > > > that's something that has wonderful benifits in the long run, and is |
53 |
> > > > something that I expect all Linux distros to eventually implement. |
54 |
> > > > Those that don't, will suffer because of it. |
55 |
> > > > |
56 |
> > > > Again, see the web page for why moving stuff into /usr is a good idea |
57 |
> > > > for the reasons behind this. |
58 |
> > > > |
59 |
> > > > |
60 |
> http://www.freedesktop.org/wiki/Software/systemd/TheCaseForTheUsrMerge |
61 |
> > > |
62 |
> > > Example: /usr Network Share |
63 |
> > > When /usr is on a network share, why not add a / on network as well? |
64 |
> > > I have multiple systems and as they all have different uses, they all have |
65 |
> > > different software installed. |
66 |
> > > |
67 |
> > > Example: Multiple Guest Operating Systems on the Same Host |
68 |
> > > See answer to previous example. |
69 |
> > > |
70 |
> > > How many environments actually currently exist where a shared /usr is |
71 |
> > > being |
72 |
> > > used? |
73 |
> > |
74 |
> > Are you aware that these environments are actually one of the most |
75 |
> > important reasons for moving everything to /usr? I don't know what |
76 |
> > hackery you're using to keep the systems in sync and working but it is |
77 |
> > braindead enough. |
78 |
> |
79 |
> An init* needs to be kept in sync with the rest of the system as well. As that |
80 |
> is a compressed filesystem, it takes a lot more effort to keep that in sync in |
81 |
> comparison to a "normal" filesystem. |
82 |
> I consider having to write scripts to unpack, modify and repack an init* to be |
83 |
> more hackery then to keep a bootable root-filesystem working that can mount |
84 |
> all the filesystems needed for the whole environment. |
85 |
> Anything needed to mount /usr, /var, /run (and any other part needed for the |
86 |
> boot-process) should not be allowed to depend on anything in any of those |
87 |
> directories prior to those being mountable. |
88 |
> |
89 |
> > The difference between keeping part of the system in rootfs |
90 |
> > and initramfs is that you can discard initramfs after using it. It can |
91 |
> > be anything which is enough to get the /usr mounted and system |
92 |
> > starting. Files on rootfs *have* to be in sync with those on /usr |
93 |
> > or you're getting random failures. |
94 |
> |
95 |
> The same is true for an init*. |
96 |
> If an update of part of the OS leads to subtle changes in the filesystem where |
97 |
> older versions can no longer properly access them, the init* is broken. |
98 |
|
99 |
Just let me know when you have to maintain a lot of such systemd |
100 |
and upgrade, say, glibc. Then maybe you'll understand. |
101 |
|
102 |
-- |
103 |
Best regards, |
104 |
Michał Górny |