rm /sys/* - during boot up

ziggie216 · n00b Joined: 06 Feb 2006 Posts: 19

during start up, I see a long and yet very fast display of rm /sys/something and at the end of each remove is permission deny. I tried to remove the folders manually but even I got the permission deny (as root). I tried booting from the install cd, mount the drive, but then sys folder was empty. Does anyone know when were those file generated and what can I do about it during the start up.

nephros · Posted: Mon Feb 06, 2006 5:41 pm Post subject:

/sys is a special filesystem provided by the kernel and you can't delete any files from it (same thing with /proc).
If /sys is empty when looked at from the livecd that means the directory used as mount point (the dir on the filesystem) does not contain any files.

Can you tell which init script is trying to do that rm? I looked over my /etc/init.d but coundn't find anything. Except for the /sbin/rc, which does some cleanups in $svcdir. Did you set something strange for the svc* variables in /etc/conf.d/rc ?
_________________
Please put [SOLVED] in your topic if you are a moron.

nixnut · Posted: Mon Feb 06, 2006 5:42 pm Post subject:

Moved from Installing Gentoo to Kernel & Hardware.

/sys/ contains files for communicated with the kernel. On startup the kernel creates entries there.
_________________
Please add [solved] to the initial post's subject line if you feel your problem is resolved. Help answer the unanswered

talk is cheap. supply exceeds demand

wjb · Posted: Mon Feb 06, 2006 11:59 pm Post subject:

I had a similar problem back at the start of January - it arrived with a genkernel or udev upgrade I think. I eventually switched from genkernel to doing manual builds and that cured it. [I have to say, the /sys deletes never seemed to cause any harm though]

ziggie216 · n00b Joined: 06 Feb 2006 Posts: 19

Po0ky · Posted: Tue Feb 07, 2006 7:52 am Post subject:

Check what modules are in use when you booted with a livecd or with your working kernel version.
(Ignore most of the sata devices and just pick the one you need, it's kinda anoying the livecd always detects them all, but hey, who are we to complain)

Also: use the lspci command (emerge pciutils) to determine what hardware you have inside.
"lspci -v" will give you even morge information. (Use to determine the real chip used on a pci-card)
Use the dmesg | grep -i "acpi\|apm" to get some information on your power management system

Use www.google.com/linux for other hardware issues

And then it's just a question of going over all kernel options and use the help button to get info on an option... With drivers, you'll find the hardware it supports in there pretty often.
_________________
-- I'll eat it--

ziggie216 · n00b Joined: 06 Feb 2006 Posts: 19

yea i'm a little amazed how livecd does a better job than compiling it myself... also I just notice that when I insert the usb drive (memory stick) some kind of detection message came up...

so from what I read in the manual.. i'll need to use menuconfig and find-pick the drivers & modules right?

Po0ky · Posted: Tue Feb 07, 2006 9:44 am Post subject:

Indeed. If you can't handle the ncurses driven menu, you can use make gconfig (gtk) or make xconfig (qt-libs) also.

Start with removing everything you KNOW you don't have

_________________
-- I'll eat it--

wjb · Posted: Wed Feb 08, 2006 2:02 pm Post subject:

You don't need to change the config much to switch to a manual build - you do need to make sure that things the system needs to boot are built-in to the kernel rather than left as modules. Then its probably best to start with a make clean so it doesn't get confused by anything the previous genkernel build left lying around

Take a look at the Gentoo Handbook section