Re: [gentoo-user] Re: udev-197: what to do -- S0LVED

[Stefan G. Weichinger]

Am 15.02.2013 20:07, schrieb Alex Schuster:
> Stefan G. Weichinger writes:
>
>>  # cat /proc/version
>> Linux version 3.6.11-gentoo
>> # zgrep -i devtm /proc/config.gz
>> CONFIG_DEVTMPFS=y
>> CONFIG_DEVTMPFS_MOUNT=y
>>
>> # mount | grep tmpfs
>> udev on /dev type devtmpfs
>> (rw,nosuid,relatime,size=10240k,nr_inodes=493463,mode=755)
>> tmpfs on /run type tmpfs (rw,nosuid,nodev,relatime,mode=755)
>> shm on /dev/shm type tmpfs (rw,nosuid,nodev,noexec,relatime)
>> cgroup_root on /sys/fs/cgroup type tmpfs
>> (rw,nosuid,nodev,noexec,relatime,size=10240k,mode=755)
>>
>> I should edit /etc/fstab, I assume:
>>
>> # grep tmpfs /etc/fstab
>> # glibc 2.2 and above expects tmpfs to be mounted at /dev/shm for
>> # (tmpfs is a dynamically expandable/shrinkable ramdisk, and will
>> shm	/dev/shm	tmpfs nodev,nosuid,noexec	0 0
>
> I still have this line in my fstab on one host...
>
>> Same "mistake" as I mentioned a few days before ... the syntax seems to
>> have changed to:
>>
>> tmpfs     /dev/shm        tmpfs 	nodev,nosuid,noexec     0 0
>>
>> Right?
>
> ... but I don't have it at all on another. /dev/shm is mounted just fine
> though.
> CONFIG_DEVTMPFS_MOUNT seems to be responsible for that, although the help
> text says that it does not work when using an initramfs, which I do:
>
> CONFIG_DEVTMPFS_MOUNT:
>
> This will instruct the kernel to automatically mount the devtmpfs
> filesystem at /dev, directly after the kernel has mounted the root
> filesystem. The behavior can be overridden with the commandline parameter:
> devtmpfs.mount=0|1.
> This option does not affect initramfs based booting, here the devtmpfs
> filesystem always needs to be mounted manually after the roots is mounted.
> With this option enabled, it allows to bring up a system in rescue mode
> with init=/bin/sh, even when the /dev directory on the rootfs is
> completely empty.

I just keep that fstab-line for now ... thanks for your explanation!

Right now I already upgraded udev and I am currently rebuilding lvm2 and
libvirt (first one needed, 2nd one not important anymore on that box).

Should I restart udev before I reboot? For a test ... ?

# dmesg  | grep udevd

only shows version 171 right now ...

-

I was already able to test for the shiny new network name for the NIC:

# cat /root/bin/udev_testing.sh
#!/bin/bash
#network name testing

for i in /sys/class/net/*; do
  echo "==$i"
  udevadm test-builtin net_id "$i";
  echo
done 2>/dev/null

---->  enp2s0 instead of eth0

I don't really care about using that new naming ... doesn't matter to me
right now.

AFAI understand things won't change if I don't touch the udev-rules?

-

revdep-rebuild is through now ... no more /lib64/libudev.so.0 needed ...

Thanks, Stefan