Re: missing /dev/fd/0 device nodes
Joachim Achtzehnter wrote: My guess is that the upgrade from testing to unstable somehow failed to create this link. The /dev/fd link exists on testing. And on sarge. And woody. And probably potato before that. No idea when it first came into being, but it isn't recent. [BTW: If you're using udev, perhaps your udev config is messed up somehow] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: missing /dev/fd/0 device nodes
Hi Anthony, You wrote: The /dev/fd link exists on testing. And on sarge. And woody. And probably potato before that. No idea when it first came into being, but it isn't recent. [BTW: If you're using udev, perhaps your udev config is messed up somehow] Didn't do anything knowingly with udev. All I did was to first install 'testing' on a virgin system, changed the sources list from 'testing' to 'unstable', then ran aptitude to perform the upgrade. I then connected my USB printer to this system, added it via the Web to CUPS, tried a test print and found that printing silently fails. After some looking around and enabling debug output in several places it became clear that a foomatic script was failing because there was no /dev/fd/0 file. So, if 'testing' has this symbolic link, it must have been removed somehow by the upgrade procedure... Joachim -- work: [EMAIL PROTECTED] (http://www.netacquire.com) private: [EMAIL PROTECTED] (http://www.kraut.ca) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: missing /dev/fd/0 device nodes
Hi all, Earlier today I wrote: /dev/fd/0 .. /dev/fd/3 device nodes don't exist. Do I need to configure something to get these files? Turns out that the following symbolic link was missing: ln -s /proc/self/fd /dev After adding this link CUPS started working. This system was initially installed from the testing archive because I thought that was the latest. I then changed to unstable and updated everything. I did not try printing with testing, so I can't tell whether this is a problem with unstable only, or perhaps even related to the upgrade procedure from testing to unstable. My guess is that the upgrade from testing to unstable somehow failed to create this link. Joachim -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
