rc.S and rc.M on current causing trouble
in [Slackware]
|
From: Joerg on 8 Mar 2010 08:51 Hi, after upgrading to current I was hit by the miss of sd devices, resulting in a failed init process First I thought this was related to the udev-1.5.1 issue descripted in a previous thread, but since the problem was still there after rolling back to udev-1.4.1 and kernel 2.6.32.7, I took a closer look and it appears that the lines in rc.S and rc.M that use redirection to /dev/null are the culprits, since /dev/null is read-only at init time. After switching back to the previous versions of rc.S and rc.M, everything works fine, even with udev-1.5.1 and kernel 2.6.33. Now this happens only with a custom kernel, using slack's huge kernel doesn't cause any problems. I'm aware that this is not a bug, but probably somebody can tell me off hand what kernel config options need to be used to avoid this problem. TIA Joerg -- For email use g m x d o t n e t
From: Andy on 8 Mar 2010 21:02 Joerg wrote: > Hi, > > after upgrading to current I was hit by the miss of sd devices, > resulting in a failed init process First I thought this was > related to the udev-1.5.1 > issue descripted in a previous thread, but since the problem was > still there after rolling back to udev-1.4.1 and kernel 2.6.32.7, > I took a closer look and it appears that the lines in rc.S and > rc.M that use redirection to /dev/null are the culprits, since > /dev/null is read-only at init time. After switching back to the > previous versions of rc.S and rc.M, everything works fine, even > with udev-1.5.1 and kernel 2.6.33. Now this happens only with a > custom kernel, using slack's huge kernel doesn't cause any > problems. I'm aware that this is not a bug, but probably somebody > can tell me off hand what kernel config options need to be used to > avoid this problem. > > TIA > Joerg If you had followed the previous threads to their end, you would have found that you need to turn off CONFIG_SYSFS_DEPRECATED_V2. Andy
From: Joerg on 9 Mar 2010 02:10 Andy wrote: > Joerg wrote: > >> Hi, >> >> after upgrading to current I was hit by the miss of sd devices, >> resulting in a failed init process First I thought this was >> related to the udev-1.5.1 >> issue descripted in a previous thread, but since the problem >> was still there after rolling back to udev-1.4.1 and kernel >> 2.6.32.7, I took a closer look and it appears that the lines in >> rc.S and rc.M that use redirection to /dev/null are the >> culprits, since /dev/null is read-only at init time. After >> switching back to the previous versions of rc.S and rc.M, >> everything works fine, even >> with udev-1.5.1 and kernel 2.6.33. Now this happens only with >> a custom kernel, using slack's huge kernel doesn't cause any >> problems. I'm aware that this is not a bug, but probably >> somebody can tell me off hand what kernel config options need >> to be used to avoid this problem. >> >> TIA >> Joerg > > If you had followed the previous threads to their end, you would > have found that you need to turn off CONFIG_SYSFS_DEPRECATED_V2. > > Andy If you had read my post to the end you would know that's not the problem;-) My .config does meet all udev-1.5.1 requrements. Joerg -- For email use g m x d o t n e t
|
Pages: 1 Prev: seamonkey 2.0.3 upgrade on 12.2 Next: New USB devices not seen in KDE |