Bug#386894: Pcmcia wireless lan broken - /dev/shm/network not created

2006-09-11 Thread Petter Reinholdtsen
found 386894 2.86.ds1-16
notfound 386894 2.86.ds1-18
close 386894
merge 386894 386500
thanks

[Lars Doelle]
 I ran the script you posted for the above bug.
 And yes - it did. Case closed. Thanks a lot!

Great.

 At least i can testify that this is anything but a transparent style
 of getting things done, whenever you need a witness. :)

Heh.  Yeah. :/

Friendly,
-- 
Petter Reinholdtsen


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#386894: Pcmcia wireless lan broken - /dev/shm/network not created

2006-09-10 Thread lars . doelle
Package: initscripts
Distribution: unstable

Hi,

perhaps related to the bug #386347, something different happend,
also related to /dev/shm.

- /etc/network/run is a link to /dev/shm/network
- /etc/network/ifstate is a link to run/ifstate

Now the /dev/shm/network directory is not longer
created, making the links dangling ends.

As a result, the pcmcia wireless lan cannot longer be started,
as ifup does not function anymore under this circumstances.

As a workaround, i can create /dev/shm/network manually and
reinsert the card, to trigger the setup mechanism. But this only
works until the next reboot.

I'm not able to track down the issue further. Not even sure how
the missing /dev/shm/network/ifstate file finally gets created
automagically. The whole mechanism appears to be very obscure,
as a result i cannot even locate the right package safely.

Potentially other packages like udev, ifupdown, pcmciautils, wireless-tools
might also be candidates of the bug report, but i concluded that initscripts
might be the most suiting address.

-lars


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#386894: Pcmcia wireless lan broken - /dev/shm/network not created

2006-09-10 Thread Petter Reinholdtsen
[Lars Doelle]
 perhaps related to the bug #386347, something different happend,
 also related to /dev/shm.

Actually, it is probably the same as bug #386500.

 Now the /dev/shm/network directory is not longer created, making the
 links dangling ends.

Sound to me like some init.d script isn't being executed any more.

In your case, I believe the problem is that the ifupdown init.d script
are missing in /etc/rcS.d/.  They should look like this:

  % ls -l /etc/rc*/S*ifupdown*
  lrwxrwxrwx 1 root root 24 Sep  6 19:56 /etc/rcS.d/S18ifupdown-clean - 
../init.d/ifupdown-clean
  lrwxrwxrwx 1 root root 18 Sep  6 19:56 /etc/rcS.d/S39ifupdown - 
../init.d/ifupdown
  %

To fix it, please follow the instructions in
/usr/share/doc/sysvinit/NEWS.Debian.gz for version 2.86.ds1-20 or
newer. :)

If it work, please let us know, so we can merge this bug into #386500
and close it.

But the use of /dev/shm/ to store state information is really a bug in
the scripts using it.  /dev/shm/ is only to be used by the
shm_open()-class of functions.  Every other use of that tmpfs is a
bug.  This is part of the reason why we changed the privileges for
that file system.  But that should be the topic for another bug
against ifupdown and friends. :)

Friendly,
-- 
Petter Reinholdtsen


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#386894: Pcmcia wireless lan broken - /dev/shm/network not created

2006-09-10 Thread lars . doelle
Petter,

On Monday 11 September 2006 00:56, Petter Reinholdtsen wrote:

 Actually, it is probably the same as bug #386500.

 If it work, please let us know, so we can merge this bug into #386500
 and close it.

I ran the script you posted for the above bug.
And yes - it did. Case closed. Thanks a lot!

In fact a lot of functionality was broken, among them kde (perhaps
via famd) and the keyboard. Stuff was nicely recovered. Good job!

 But the use of /dev/shm/ to store state information is really a bug in
 the scripts using it.  /dev/shm/ is only to be used by the
 shm_open()-class of functions.  Every other use of that tmpfs is a
 bug.  This is part of the reason why we changed the privileges for
 that file system.  But that should be the topic for another bug
 against ifupdown and friends. :)

At least i can testify that this is anything but a transparent style
of getting things done, whenever you need a witness. :)


Thanks again.
-lars


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]