| 1 |
Mick wrote: |
| 2 |
> On Tuesday 24 March 2009, Alan McKinnon wrote: |
| 3 |
> |
| 4 |
>> On Tuesday 24 March 2009 05:01:36 SOrCErEr wrote: |
| 5 |
>> |
| 6 |
>>> No, that isn't. That file exists. |
| 7 |
>>> So I tested like below. |
| 8 |
>>> |
| 9 |
>>> /etc/init.d/udev stop |
| 10 |
>>> /etc/init.d/sysfs stop |
| 11 |
>>> /etc/init.d/udev start |
| 12 |
>>> /etc/init.d/sysfs status |
| 13 |
>>> |
| 14 |
>>> Result is |
| 15 |
>>> "* status: stopped" |
| 16 |
>>> |
| 17 |
>> I had this problem recently. I had updated to udev-140 and forgot to run |
| 18 |
>> conf- update to fic the changed config file. |
| 19 |
>> |
| 20 |
>> Did you recently update udev? |
| 21 |
>> |
| 22 |
> |
| 23 |
> I am confused reading this thread. I have sysfs mounted: |
| 24 |
> |
| 25 |
> $ mount | grep sysfs |
| 26 |
> sysfs on /sys type sysfs (rw,nosuid,nodev,noexec) |
| 27 |
> |
| 28 |
> However, I do not have sysfs in /etc/init.d/sysfs. |
| 29 |
> |
| 30 |
|
| 31 |
Same here. Both the confused part and the not have the init script |
| 32 |
sysfs. I was sort of worried about rebooting. Glad it is not just me. |
| 33 |
|
| 34 |
Dale |
| 35 |
|
| 36 |
:-) :-) |
Archives