On Sun, 24 Oct 1999, Nicholas Brenckle wrote:
> Check your dmesg out after booting. My OpenBSD box did strange thing
> with my CDrom when installing and after install did strange things with
> my nic (3c905). I ended up having to go into config mode on boot (wd0?
> /bsd -c I forget what the wd0 part was right now, its sunday :) and
> defining the card. Eventually I built a kernal (see the FAQ for this)
> and that stopped it.
Interesting. I had to swap the old CDROM in this computer with the brand
new one I bought for my newer Intel box. OpenBSD couldn't recognize the old
CD drive, but had no trouble booting off the new one. I have 3com's too.
There are two 3c509 ISA NIC's in this machine. Are these common problems
with OpenBSD? I didn't see anything about this on
comp.unix.bsd.openbsd.misc, but it only goes back about two weeks on
news.yale.edu.
> Im not doing any routing with it tho, so this may have nothing to do
> with your problem. How are you liking OpenBSD? So far I was impressed
> with the quality of the software/time that went into it. (Check out the
> /etc/passwd file when your pw's are using blowfish... crazy..) BUT
> really not happy after using the simple menus of the last few linux
> distros. I got lazy and command lines dont help. Im going to stick with
> it for the task I had in mind tho which is exactly what you are doing,
> only on a dialup connect to Yale, not a LAN.
I was scared at first based on the all the warnings about how difficult it
is and how dangerous the installation program is. Fortunately, I was giving
it the entire hard disk, so I didn't have to worry about tricky partitioning
issues. I thought the installation was pretty easy. It may not be "clicky"
like all these X-based installers coming out for Linux right now, but it's
efficient.
I like the way they customized the default XDM login. heh. Overall, the
system seemed really well assembled, if spartan. Before I began, I didn't
even know BSD had a package system, but it turned out to be pretty good
(similar to RPM or DEB). But alas, after struggling off-and-on with OpenBSD
for several days despite midterms, I could not figure out why it always
forgot how to talk to my internal network after rebooting, even though both
network connections work *perfectly* during the installation.
Hopefully I'll have some time next weekend to try your suggestion. I'm
looking forward to running OpenBSD on this machine; it seems perfectly
suited. Last night, I got fed up with it and just installed Linux on it.
I definitely understand your feeling about Linux making things easy. I was
able to install Linux on this thing, getting all the networking functional,
improve its security a bit, and get ipchains nicely configured to do
IP-Masquerading for my internal network and to reject some spoofing attacks,
all in about an hour. Then again, the difference is probably mostly that
I'm an OpenBSD newbie.
Thanks,
Chad
This archive was generated by hypermail 2b29 : Wed Apr 27 2005 - 03:30:03 EDT