1 |
Walter Dnes wrote: |
2 |
|
3 |
> Steven J Long wrote |
4 |
> |
5 |
>> <dberkholz> who's going to either "port" udev as necessary, or maintain |
6 |
>> an old version forever? |
7 |
>> <Chainsaw> I will keep an old version going until the end of time. |
8 |
>> <Chainsaw> dberkholz: My plan is to patch reasonable behaviour back into |
9 |
>> udev, and going with the upstream releases as long as it is feasible. |
10 |
> |
11 |
> I use busybox's mdev, and it works fine for my simple system. |
12 |
|
13 |
Does it handle USB and other media hotplug? That's the real killer for |
14 |
desktops. (Running scripts in response to events is another issue, and what |
15 |
has led to the udev problem.) |
16 |
|
17 |
> |
18 |
>> To confirm again, that this is about without initramfs: |
19 |
>> <dberkholz> sure i can. maintain old udev-XXX forever, put an elog in new |
20 |
>> udev that says "if you want separate /usr without initramfs, install old |
21 |
>> udev, mask new, or whatever" |
22 |
> |
23 |
> systemd and udev are being merged into one tarball. For the |
24 |
> "foreseeable |
25 |
> future", it will still build 2 separate binaries. What happens down the |
26 |
> road if/when it all becomes one combined binary? |
27 |
> |
28 |
Well I've read assertions that it will be possible to build udev without |
29 |
systemd for distros and users who want it, and this is supposedly a firm |
30 |
commitment into the future. Then again, experience doesn't bode well for |
31 |
those kind of commitments. |
32 |
|
33 |
(It's much easier to introduce coupling between software in the same |
34 |
package. GregKH has also mooted a tightly-coupled "core" Linux distro, which |
35 |
afaict is the same reasoning as GnomeOS, and /that/ sounds like a |
36 |
clusterfsck waiting to happen.) |
37 |
|
38 |
>> And again, I ask: if it were *not* about running udev without an |
39 |
>> initramfs, then why would anyone even be discussing the possibility |
40 |
>> of patching or forking? |
41 |
> |
42 |
> Forking/patching udev would be a major undertaking. |
43 |
|
44 |
The point I was making was that it couldn't even be an issue, _unless_ one |
45 |
were talking about an install without an initramfs, since udev with an |
46 |
initramfs supports a split /usr. |
47 |
|
48 |
(That's required for the usr-bin merge to be useful, since the idea is to |
49 |
enable snapshotting of all distribution binaries; after years of rubbishing |
50 |
any possible reason admins might have for a split /usr, it's now critical to |
51 |
a major 'new' feature of Fedora, and all the traditional benefits are |
52 |
selling-points of the "new design".) |
53 |
|
54 |
As for the effort, so long as you don't need udev to create nodes for |
55 |
localmount, you don't need an initramfs with either our patched approach, or |
56 |
an earlymounts initscript, and now there's vapier's busybox applet to do the |
57 |
mounts for you. None of which require any modification to udev, nor |
58 |
maintenance of an initrd and the binaries therein. |
59 |
|
60 |
Regards, |
61 |
Steve. |
62 |
-- |
63 |
#friendly-coders -- We're friendly, but we're not /that/ friendly ;-) |