That'll probably be really tough, since it won't even boot for the first
What you could try is using a boot diskette to get the machine up and
running, then compile a custom kernel that has support for the scsi card
compiled in (not as a module) The kernel that the installer uses has
-everything- compiled in so it'll work on a maximum number of systems,
however, the kernel it installs on your machine does not.
Hope that helps!
From: Ben Dow [mailto:bdow@WPI.EDU]
Sent: Saturday, April 28, 2001 5:30 AM
Subject: Re: [Wlug] SCSI HD Boot Failure! BLA!
Try compiling scsi support into your kernel, or using a different
precompiled kernel if you're not into compiling your own. You probably
had scsi support in the installation kernel but not the one it installs to
boot from by default.
On Sat, 28 Apr 2001, Sands Fish wrote:
> Hello again all,
> I've just recently started putting together a Mandrake 8.0 box.
> 3 hours ago, yes in the middle of the night.) For a hard drive, I have an
> IBM SCSI Drive on an Adaptec 2940-U2 card. When I ran the install, it
> the card and the drive automagically. I was impressed and happy. Went
> through the installation fine, copied all the files. But as soon as I
> rebooted to run it for the first time, I get the LILO graphical screen, I
> choose one of the options (any), and get the following error...
> request_module[block-major-8]: Root fs not mounted
> VFS: Cannot open root device "801" or 08:01
> Please append a correct "root=" boot option
> Kernel panic: VFS: Unable to mount root fs on 08:01
> Just some more information. The HD is on SCSI ID #6. The controller is
> #7. The SCSI BIOS sees the drive because I can see it report it on boot.
> When I watch the boot messages fly by for Linux, I see no reference to any
> sd# devices at all.
> I'm really completely lost here. Would changing the SCSI ID # help? That
> doesn't seem to be likely. Any suggestions would be greatly appreciated.
> Thanx a lot guys/grrls!!
> - - s a n d s - -
Wlug mailing list
I'm running three dual-homed RedHat 7.0 boxes on separate DSL or
cable, each doing IP Masquerading to private networks.
I'm attempting to do some more serious firewalling, and am trying to
debug problems in a rc.firewall script generated from Bob Ziegler's
I've noticed that when I swap between Bob's 600+ line script and
Rusty's Three-Line Guide to Masquerading (IPCHAINS How-To) , each
modified to start with "ipchains -F" which should flush all existing
rules, that the flush isn't happening. I'm switching by doing "sh
<scriptname>" after having made both scripts executable.
If I reboot Linux after changing which script is referenced in
/etc/rc.d/rc.local, then everything is clean.
dick(a)goodman1.net ---> Home: (508) 753-DICK
trader(a)goodman1.net ---> Work: (508) 757-3452 voice/fax
Just in case anyone here uses Debian and is thinking of installing
Ximian1.4, the directions that say to apt-get install task-helix-gnome
are wrong. I've gone and made some task packages based on what
helix/ximian used to have for its previous release. Just add this to
your sources.list and you can use them:
deb http://zork.net/~orion potato main
(or s/potato/unstable/ of you prefer)
also, if you need a deb-src line for ximian, until they fix it (IF they
fix it) you need to use this instead of what they say:
deb-src http://red-carpet.ximian.com/debian/ dists/potato/main/sources/
(again, s/potato/woody/ if you wish)
Orion orion [at] tribble [dot] dyndns [dot] org
"so did you eat the dog or walk it? ;)" - iain
Hello again all,
I've just recently started putting together a Mandrake 8.0 box. (About
3 hours ago, yes in the middle of the night.) For a hard drive, I have an
IBM SCSI Drive on an Adaptec 2940-U2 card. When I ran the install, it found
the card and the drive automagically. I was impressed and happy. Went
through the installation fine, copied all the files. But as soon as I
rebooted to run it for the first time, I get the LILO graphical screen, I
choose one of the options (any), and get the following error...
request_module[block-major-8]: Root fs not mounted
VFS: Cannot open root device "801" or 08:01
Please append a correct "root=" boot option
Kernel panic: VFS: Unable to mount root fs on 08:01
Just some more information. The HD is on SCSI ID #6. The controller is on
#7. The SCSI BIOS sees the drive because I can see it report it on boot.
When I watch the boot messages fly by for Linux, I see no reference to any
sd# devices at all.
I'm really completely lost here. Would changing the SCSI ID # help? That
doesn't seem to be likely. Any suggestions would be greatly appreciated.
Thanx a lot guys/grrls!!
- - s a n d s - -
I got a posting in the mailing list about getting the LUG rate for
Tribes 2 and SMAC, I am VERY interested in this; but I've not heard
anything since the origional message went out. Are people still
thinking about this??
On an unrelated note, Loki's online store is down and Tribes 2 is
shipping NOW. I hope this a good sign that they're getting so many
orders that it crashed their site. Being forward thinking, they have a
fax number posted for an alternate ordering method. Way to go Loki!
I have a Toshiba Satellite notebook running SuSE 7.0 (personal edition)
with kde as the window manager. For reasons unknown (to me at least) I
no longer click on an icon, for example, the shell icon, on the Kpanel
and get a response. Also, the icons on the desktop, netscape and
for example, have disappeared. Finally, if I click on the K menu button
I can navigate out to the various programs, but again nothing responds.
I can however, hit Alt/F2, get a command window, type in netscape, xterm
or soffice, and the respective application comes up!
I have searched the web and found no hints as to what might be going on.
I happen to have the Que "Practical KDE" by Dennis Powell where, on page
46, under "Troubleshooting" there is a section "KDE starts but
Applications won't". He suggests a
chmod 1777 /tmp
which I tried (and got
which says I didn't hit a typo) but the problem remained.
I also tried
chmod -RV 1777 /tmp
to recursively chmod (I found several subdirectories in /tmp)
but again without success. :-(
The KDE version is 1.1.2 according to the SuSE box. The kernel
is 2.2.12 (but, that, I suspect, is irrelevant).
So, my specific question is "has anyone out there seen this
and/or knows the solution/fix?". If not, a broader question
is "what would you try next?" (without blowing away everything
and reinstalling linux :-) --- this same SuSE/KDE works
fine on a Dell desktop box). As you might gather, I have
reached the point where I am open to suggestions of any
At this link you can get it from the source:
Then try going to OpenVMS Documentation where you can find:
OpenVMS Guide to System Security
-Robert N. Evans
>> I was wondering if any of you knew reliable and accurate sites on
>>VAX/VMS especially things that deal with networking and security. I need
>>right a technical paper on those. And I'm at a lost of reliable sources