*BSDThis forum is for the discussion of all BSD variants.
FreeBSD, OpenBSD, NetBSD, etc.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I installed OpenBSD 3.4 on my old Alpha the other day. Now, I am used to the i386 version of OBSD usualy but i thought there would be no difference. Now, i installed from the boot disk and that all went fine but when I booted up i noticed a strange difference between the alpha port and the i386 port. My alpha's OBSD booted straight into a shell instead of the login prompt. So i checked out this shell and noticed that it was underprivaleged or something because when I tried to change things it said "... Read-only filesystem" so I tried logging in by using the
"# login" command. I logged in as root and the motd came up as usual but I continued to get the "Read-only filesystem" error, even in root!!! So I used the command "# mount -uw /" and then the filesystem is fine. Another strange thing is that I have a /etc/hostname.* file and the NIC isn't configured when I log in and all the services in /etc/rc.conf are not loaded. I have either made a stupid error or this is just plain wierd. If someone could help me that would be greatly, greatly apreciated.
I don't have a install CD, i used the floppy34.fs image disk. I do have bsd.rd installed but in the shell of my alpha i type ">>>boot dka0" (dka0=my SCSI drive with bsd installed) and it boots into the mess that I explained. I don't see any reason why it would boot to bsd.rd but if that is the case how could it be solved? After my machine boots it does ask "Enter pathname of shell or RETURN for sh:" but i just hit return, otherwise I have no choices to make on how the machine boots. Have you runned the alpha obsd port before? Does yours do this it?
Last edited by lil_drummaboy; 05-03-2004 at 07:28 PM.
Distribution: OpenBSD 4.6, OS X 10.6.2, CentOS 4 & 5
It looks like you need to specify a few variables in your SRM console. Quoting from ftp.openbsd.org/pub/OpenBSD/3.4/alpha/INSTALL.alpha
Using the SRM console:
This is not intended to be an exhaustive guide on using the
SRM firmware console. It should, however, give you enough
information to boot OpenBSD/alpha.
To see a list of devices connected to your alpha, you can
use the "show device" command. For booting the devices you
are interested in are "dva0" (the floppy drive) and
"dka*" (the disk drives).
You can set ROM variables by saying "set VARIABLE VALUE".
Some variables you will want to set:
auto_action Determines what happens when you turn power on,
halt, or crash your machine. Valid values
include "halt", "boot", and "restart".
Most users will want to set this to "boot".
bootdef_dev Default boot device (or list of devices).
boot_file Name of the kernel to boot. If this variable is
empty, "bsd" will be loaded. Note that this
variable does not exist in all versions of the SRM
console, in which case you need to always specify a
kernel filename if it differs from "bsd".
boot_osflags Flags to pass to the kernel.
IMPORTANT! For multiuser boot, this needs to be
set to "a".
To see a list of all variables on your machine use the "show"
command with no arguments.
You can bypass the boot_file and boot_osflags values from the command
prompt, with the -fi (to override boot_file) and -fl (to override
boot_osflags) options. For example,
boot -fi bsd -fl ac dka0
will boot the "bsd" kernel with the "ac" flags on dka0. However, some
versions of the SRM console (mainly on DEC 3000 series) will only let
you specify uppercase filenames.
So you need to set bootdef_dev to your disk device (dka0), boot_file to "bsd" (w/o quotes), and boot_osflags to "a" (w/o quotes).