Once removeable media support is added to the ENBD project, that would
be the "best" way to go. If you want to help get that done, you can
pledge support to the author of that project via
http://www.pcxperience.com/enbd
Rudhuwan Abu Bakar wrote:
> hi all
>
> i have seen lots of discussion regarding floppy access mainly nbd and
> floppyd. Which are the best solutions?
>
> I have tried both but having trouble with both..
>
> Hoping for some kind of documentations for help.
>
> Thanks and regard
> duan
>
> Rick Younie wrote:
>
>>Jim McQuillan wrote:
>>
>>>Rick Younie wrote:
>>>
>>>>Wolfgang Schweer wrote:
>>>>
>>>>>On Wed, 2 Jan 2002, Rick Younie wrote:
>>>>>
>>>>>
>>>>>>I had to do a
>>>>>>mknod -m 0666 /dev/fd0 b 2 0
>>>>>>I did this from the root console on tty1 you get with
>>>>>>1:5:respawn:/bin/startsess tty1 /bin/bash --login
>>>>>>(very handy, that) but it should go in rc.mfloppy.
>>>>>>
>>>>>Hi Rick,
>>>>>
>>>>>that's o.k., but chmod 666 /dev/fd0 should do it.
>>>>>
>>>>You mean no mknod or no 0 :-) ? /dev/fd0 doesn't exist on
>>>>the ws here -- Georg's latest termserv debs.
>>>>
>>>Rick,
>>>
>>>when using devfs, the device nodes will automatically
>>>appear when the floppy device module has been loaded.
>>>
>>>So, you need to load the floppy.o module, then you should
>>>be able to do the chmod.
>>>
>>
>> [ reformatted to lose the ping-ponging ]
>>
>>Hi,
>>
>>Fair enough. You either have to explicitly load the floppy
>>module or else mknod. Starting floppyd on the workstation
>>doesn't load floppy.o itself and an "mdir a:" on the ws will
>>try and access the server floppy drive. ( not a whine, just for
>>completeness. Mtools has been problematic for quite a few people
>>I talked with. )
>>
>>Rick
>>
>
>--
>
>
>
--
Jason A. Pattie
[EMAIL PROTECTED]
_____________________________________________________________________
Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto:
https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help, try #ltsp channel on irc.openprojects.net
