[opensuse] lost dev file
Somehow I have lost the file /dev/ttyUSBS0, the file used by my pilot to sync in jpilot. Seems this happened once before, way back in the distant confusion of what used to serve as a memory for me...but not now. I think I recall re-booting (sorry for the Winbloze reference), to re-create the /dev files but this did not work. I seem to recall also that this file might be created on-the-fly when syncing, but apparently this is not happening, even with re-start of jpilot. Error message is device file not present, and when I look under /dev, it is in fact, not present. Any suggestions? Richard -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Tue, May 19, 2009 at 11:25 AM, Richard
Somehow I have lost the file /dev/ttyUSBS0, the file used by my pilot to sync in jpilot. Seems this happened once before, way back in the distant confusion of what used to serve as a memory for me...but not now. I think I recall re-booting (sorry for the Winbloze reference), to re-create the /dev files but this did not work. I seem to recall also that this file might be created on-the-fly when syncing, but apparently this is not happening, even with re-start of jpilot. Error message is device file not present, and when I look under /dev, it is in fact, not present. Any suggestions?
Richard -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
That device file only appears when you press the sync button on the Pilot itself. At least such was my experience. At other times, the Pilot stays off the USB. Boris. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Content-ID:
Somehow I have lost the file /dev/ttyUSBS0, the file used by my pilot to sync in jpilot. Seems this happened once before, way back in the distant confusion of what used to serve as a memory for me...but not now. I think I recall re-booting (sorry for the Winbloze reference), to re-create the /dev files but this did not work. I seem to recall also that this file might be created on-the-fly when syncing, but apparently this is not happening, even with re-start of jpilot. Error message is device file not present, and when I look under /dev, it is in fact, not present. Any suggestions?
Yes, they are created automatically when the corresponding hardware is found. - -- Cheers, Carlos R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkoUW5UACgkQtTMYHG2NR9XMxQCfV8AWvbLeheGfFbKXhfA+/m9u RlsAoImk35+wvInL8s3NP+9GaCDO2oSr =lzND -----END PGP SIGNATURE-----
On Wed May 20 2009, Carlos E. R. wrote:
Content-ID:
On Tuesday, 2009-05-19 at 08:25 -0700, Richard wrote:
Somehow I have lost the file /dev/ttyUSBS0, the file used by my pilot to sync in jpilot. Seems this happened once before, way back in the distant confusion of what used to serve as a memory for me...but not now. I think I recall re-booting (sorry for the Winbloze reference), to re-create the /dev files but this did not work. I seem to recall also that this file might be created on-the-fly when syncing, but apparently this is not happening, even with re-start of jpilot. Error message is device file not present, and when I look under /dev, it is in fact, not present. Any suggestions?
Yes, they are created automatically when the corresponding hardware is found.
Thanks Carlos, and Boris also. Any suggestions for when this file is not being created? Is this possibly a YAST issue, re-installing the hardware or is there likely some other issue with the hardware not being found? Richard -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thursday, 2009-05-21 at 08:11 -0700, Richard wrote:
Yes, they are created automatically when the corresponding hardware is found.
Thanks Carlos, and Boris also. Any suggestions for when this file is not being created? Is this possibly a YAST issue, re-installing the hardware or is there likely some other issue with the hardware not being found?
I think the kernel senses it, loads some module, udev/hal creates the device node. YaST simply configures the module to load in some cases, and configures it. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkoVsAsACgkQtTMYHG2NR9X+lgCglnbUQhEIblvqvehckFafwjcp sR0AnRBZkW32UbsZRN6Pk/eFxm6jsQfE =cR6R -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (3)
-
Boris Epstein -
Carlos E. R. -
Richard