Re: total newbee questions
On Wed, Mar 24, 2004 at 12:34:36AM -0400, kennon ward wrote: To All; I just created the disk for FreeBSD and got my other laptop to boot up under FreeBSD. I need some help in accessing the hard drive and the cdrom. I tried to create a directory for the CDROM and the hdd1. Then tried to mount using those directories. It did not access my hard drive or the cdrom. The question is what do I need to do to gain access to these two drives? Also does anyone out there have the source code and makefile for vi? That is the editor I have used on other Unix systems. You may have guessed that I was not a root super user :-) Thanks to all for your help. Regards Kenn Ward [EMAIL PROTECTED] Can you give some specific examples, like the actual commands you are issuing and the actual error? Are your disks being detected at boot? You can check for them by greping the output of dmesg like so: # dmesg | egrep ^ad|acd Also, you reference your disk as hdd1, which is the Linux nomenclature for secondary slave partition 1. In FreeBSD it would be ad3s1 and your CDROM would be acd(N), depending on it actual physical location. Nathan -- gpg --keyserver pgp.mit.edu --recv-keys D8527E49 pgp0.pgp Description: PGP signature
Re: total newbee questions
On Wed, Mar 24, 2004 at 12:34:36AM -0400, kennon ward wrote: To All; I just created the disk for FreeBSD and got my other laptop to boot up under FreeBSD. I need some help in accessing the hard drive and the cdrom. I tried to create a directory for the CDROM and the hdd1. Then tried to mount using those directories. It did not access my hard drive or the cdrom. The question is what do I need to do to gain access to these two drives? Also does anyone out there have the source code and makefile for vi? That is the editor I have used on other Unix systems. You may have guessed that I was not a root super user :-) Assuming you get your hard drive situation fixed up, you shouldn't need anything else to run vi(1). It's installed by default in /usr/bin, so my guess is that if you get your /usr partition available to the system, you'll be fine. If all you've got available is /, then I feel your pain, for ed(1) and red(1) are somewhat like kicking dead whales down the beach compared to something more modern... :-) Like someone else wrote, send us the output of mount and a description of how you're attempting to mount your filesystems, the relevant parts of your dmesg, etc. Kevin Kinsey DaleCo, S.P. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: total newbee questions
Kevin Kinsey [EMAIL PROTECTED] writes: If all you've got available is /, then I feel your pain, for ed(1) and red(1) are somewhat like kicking dead whales down the beach compared to something more modern... :-) You can avoid that pain without making / much bigger by installing the editors/e3 port and moving /usr/local/bin/e3* to /bin/. You'll get fair vi, emacs, pico, wordstar, and nedit emulators, all in less than 13000 bytes. I'm sure ed(1) will be with us 'till the end, but I wish e3 was also included in the base i386 FreeBSD. Or even a bigger (but small) vi editor clone that would work on all CPUs. There are several that seem negligibly small compared to much of the other stuff I see in /*bin/. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: total newbee questions
On Wed, Mar 24, 2004 at 11:17:45AM -0800, Gary W. Swearingen wrote: Kevin Kinsey [EMAIL PROTECTED] writes: You can avoid that pain without making / much bigger by installing the editors/e3 port and moving /usr/local/bin/e3* to /bin/. You'll get fair vi, emacs, pico, wordstar, and nedit emulators, all in less than 13000 bytes. I'm sure ed(1) will be with us 'till the end, but I wish e3 was also included in the base i386 FreeBSD. Or even a bigger (but small) vi editor clone that would work on all CPUs. There are several that seem negligibly small compared to much of the other stuff I see in /*bin/. That does sound nice. However, I don't suppose it'll be done, for either licensing or historical reasons. [But who am I to say, of course ;-) --- I guess nothing stops me from doing it myself ] That's quite a bit smaller even than ee, or even ed! I may try e3 ... thanks for the pointer, or I may make it SOP to cp ee(1) to /bin when setting up boxes in the future; I do recall once upon a time being stranded with nothing but ed(1) on a disk that was pretty screwed up Kevin Kinsey ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
