Silicon Investor (SI) -- The First Internet Community

STOCKTALK

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor. We ask that you disable ad blocking while on Silicon Investor in the best interests of our community. If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.

Pastimes : Linux OS.: Technical questions -- Ignore unavailable to you. Want to Upgrade?

To: g_m10 who wrote (176)	2/20/1999 2:48:00 AM
From: Mitch Blevins	Read Replies (2) \| Respond to of 484

2. After I used "ln -s /dev/cua1 /dev/modem" the word "modem" appeared in "/dev/" directory, but it looks like it supposed to be a directory, not just an empty file. You made the right link. Although I believe that /dev/cua# will not be supported on future kernels, and you should get in the habit of using /dev/ttyS# instead. It should _not_ be a directory, although I can't explain that strange error message from minicom. Make sure the permissions on /dev/cua1 are set so that the person you are dialing out as can read and write to it. 3. I need to mount the modem. Linuxconf allows me easy to do it, but I don't know what fstype should be used. Don't redirect commands directly to the /dev/fd0 device, as this will write raw data and be unreadable to DOS. The easiest way to do it is to format the floppy under DOS. Then mount it in Linux. You need an empty directory to mount it to which is probably /mnt/floppy or just /floppy. [prompt]$ mount -t msdos /dev/fd0 /mnt/floppy You can then redirect messages to a new file on the floppy with [prompt]$ dmesg > /mnt/floppy/myfile.txt This is a text file that can be read from DOS/Windows, but will look bad because the end-of-line characters are different betwixt the two systems and it will appear to be one huge line. You may have a program on your system to convert the file called 'unix2dos' or 'to_dos' or something. But, in a pinch you can always just use a simple awk script to convert it like this: [prompt]$ cat /mnt/floppy/myfile.txt \|awk --source '{printf "%s\r\n", $0;}' > /mnt/floppy/dosfile.txt Which will create a new file named "dosfile.txt" that can be read easily from DOS. You could have skipped this extra step and created it from the original dmesg command like so: [prompt]$ dmesg \|awk --source '{printf "%s\r\n", $0;}' > /mnt/floppy/dosfile.txt Remember to unmount the directory before pulling out the floppy... [prompt]$ umount /mnt/floppy Hope this helps... -Mitch