1 |
Jonathan Callen <jcallen@g.o> wrote: |
2 |
|
3 |
> On 06/09/2016 10:00 AM, Dale wrote: |
4 |
> > waltdnes@××××××××.org wrote: |
5 |
> >> On Thu, Jun 09, 2016 at 08:16:57AM -0500, Dale wrote |
6 |
> >>> karl@××××××××.se wrote: |
7 |
> >>>> Dale: |
8 |
> >>>> ... |
9 |
> >>>>> Can a system even boot without udev? |
10 |
> >>>> Yes, use sys-fs/static-dev (unless you have some special boot |
11 |
> >>>> requirements). |
12 |
> >>> Well, I was talking about if udev was removed and then a reboot |
13 |
> >>> was done. I would think it would boot to a certain point then |
14 |
> >>> when whatever started and needed devices to be created in /dev, |
15 |
> >>> it would start failing. I suspect this would vary depending on |
16 |
> >>> the install as well. |
17 |
> >> You need *A* device-manager. You can use udev, eudev, |
18 |
> >> static-dev, mdev, whatever, but you need something. Mind you, |
19 |
> >> some software assumes or requires udev/eudev. |
20 |
> >> |
21 |
> > |
22 |
> > |
23 |
> > What I was referring to was if during this switch from udev to |
24 |
> > eudev, someone rebooted without any dev manager at all. In other |
25 |
> > words, emerge -C udev and then reboot before emerging eudev or some |
26 |
> > other dev manager. I suspect that would get interesting pretty |
27 |
> > quick. |
28 |
> > |
29 |
> > Dale |
30 |
> > |
31 |
> > :-) :-) |
32 |
> > |
33 |
> > |
34 |
> |
35 |
> Actually, you no longer need a user-space device manager at all, |
36 |
> unless you want to be able to access device nodes under /dev as a |
37 |
> user that isn't UID=0 or has CAP_DAC_OVERRIDE. The kernel provides a |
38 |
> devtmpfs filesystem that will have every single device node that udev |
39 |
> used to create (udev no longer even creates the devices -- it just |
40 |
> relies on devtmpfs doing so), but most of them will be owned by 0:0 |
41 |
> (root:root) with permissions 0600; excepting certain nodes |
42 |
> like /dev/null or /dev/zero, which will be owned by 0:0 with |
43 |
> permissions 0666. One other thing that udev does that you might rely |
44 |
> on is to create symlinks like /dev/disk/by-label/*, which can be used |
45 |
> by mount(8) if you specify LABEL=foo in /etc/fstab. The only other |
46 |
> things that I'm aware of udev doing is to rename network devices and |
47 |
> (possibly) to notify other applications of changes, somehow (but I'm |
48 |
> not sure that it actually does that). |
49 |
> |
50 |
> If you don't actually need any of that (you are working on an embedded |
51 |
> system where you only need root anyway, for instance), then you can |
52 |
> just use a bare devtmpfs without a device manager changing |
53 |
> permissions, adding links, etc. |
54 |
|
55 |
THX for all the information. Now I understand better what (e)udev is |
56 |
doing. |
57 |
|
58 |
-- |
59 |
Regards |
60 |
wabe |