Had to reset, now in deep kimshee....
Hi. This morning, while poking around, I executed the comand on the console of X, seeing if Xwindows would start up without having read much of the docs... :^ In order to get my console back, since I didn't think of logging in accross the network and killing the process, mea maxima culpa, was to power off the machine. The modules now do not load. modconf sees that the modules are selected, but cannot remove them, Module Not Found. /usr/ is loaded into the second partition on my hard disk. The fsck for the second partition is occurring after all the module failures, so it seems perhapps that the book sequence has gotten messed up somehow, if the modules are loaded from /usr If I go back to the rescue floppy, how much damage can I do to the software already loaded? All I intend to do is to select and load modules Is there a fix that I am not aware of? Some way to reorder the fsck of /hda2 to occur before the module loads are tried? ObNice: The software distribution via FTP with load and config, etc, is WONDERFUL! Thanks to Deb Ian! Curt- --- Curt Howland [EMAIL PROTECTED] http://www.Priss.com The Probability Broach by L. Neil Smith ISBN:0-812-53875-7 Available from Laissez Faire Books http://www.lfb.org/ 1.800.326.0996 -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: Had to reset, now in deep kimshee....]
/usr/ is loaded into the second partition on my hard disk. The
fsck for the second partition is occurring after all the module
failures, so it seems perhapps that the book sequence has gotten
messed up somehow, if the modules are loaded from /usr
No, in /etc/init.d/boot I read that modules are supposed to be loaded
before the fsck. This is probably because some of the filesystems may
need those modules.
However, the modules aren't supposed to be loaded from /usr: they
are supposed to live in /lib/modules, and the insmod executable
is in /sbin, so there _should_ be no problem. Did you messabout
with your system?
If I go back to the rescue floppy, how much damage can I do to
the software already loaded? All I intend to do is to select and
load modules
Well, you _can_ do a lot of damage, but if you're carefull
and don't do things like rm -rf /, then you probably will not
do too much damage. (But _DO_ unmount all filesystems before
the next reboot -- or if this fails atleast type sync).
Is there a fix that I am not aware of? Some way to reorder the
fsck of /hda2 to occur before the module loads are tried?
See above -- should not be needed.
--
joost witteveen, [EMAIL PROTECTED]
#!/bin/perl -sp0777iX+d*lMLa^*lN%0]dsXx++lMlN/dsM0j]dsj
$/=unpack('H*',$_);$_=`echo 16dio\U$kSK$/SM$n\EsN0p[lN*1
lK[d2%Sa2/d0$^Ixp|dc`;s/\W//g;$_=pack('H*',/((..)*)$/)
#what's this? see http://www.dcs.ex.ac.uk/~aba/rsa/
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to
[EMAIL PROTECTED] .
Trouble? e-mail to [EMAIL PROTECTED] .
Re: Had to reset, now in deep kimshee....]
However, the modules aren't supposed to be loaded from /usr: they are supposed
to
live in /lib/modules, and the insmod executable is in /sbin, so there _should_
be
no problem. Did you messabout with your system?
Nope. I didn't touch the modules, path, boot files
or records. Just hit the reset switch. Something got
scrambled, it seems.
Warning to anyone with write-back cache on their
hard disk: DO NOT HIT THE RESET SWITCH IN A MULTI-
TASKING ENVIRONMENT!
I was suprised that running X, with no window
manager, hung the Alt-F1, Alt-F2... console login
switch as well, since that was the first thing I
tried in order to log in and kill the process.
If I go back to the rescue floppy, how much damage can I do to
the software already loaded? All I intend to do is to select and
load modules
Well, you _can_ do a lot of damage, but if you're carefull and don't do things
like rm -rf /, then you probably will not do too much damage. (But _DO_
unmount
all filesystems before the next reboot -- or if this fails atleast type
sync).
I will print this message out and take it home with
me. Unfortunately, the machine is not local, nor
can I log into it, what with the network module
non existant.
Is there a fix that I am not aware of? Some way to reorder the
fsck of /hda2 to occur before the module loads are tried?
See above -- should not be needed.
I will not try that then. Many thanks!
--
joost witteveen, [EMAIL PROTECTED]
#!/bin/perl -sp0777iX+d*lMLa^*lN%0]dsXx++lMlN/dsM0j]dsj
$/=unpack('H*',$_);$_=`echo 16dio\U$kSK$/SM$n\EsN0p[lN*1
lK[d2%Sa2/d0$^Ixp|dc`;s/\W//g;$_=pack('H*',/((..)*)$/) #what's this? see
http://www.dcs.ex.ac.uk/~aba/rsa/
---
Curt Howland [EMAIL PROTECTED] http://www.Priss.com
The Probability Broach by L. Neil Smith
ISBN:0-812-53875-7 Available from Laissez Faire Books
http://www.lfb.org/ 1.800.326.0996
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to
[EMAIL PROTECTED] .
Trouble? e-mail to [EMAIL PROTECTED] .
Re: Had to reset, now in deep kimshee....]
However, the modules aren't supposed to be loaded from /usr: they are
supposed to
live in /lib/modules, and the insmod executable is in /sbin, so there
_should_ be
no problem. Did you messabout with your system?
Nope. I didn't touch the modules, path, boot files
or records.
Then your modules got loaded properly, or they were bad before too.
No /usr stuff is needed for the loading of the modules, as you suggest
above.
I was suprised that running X, with no window
manager, hung the Alt-F1, Alt-F2... console login
switch as well, since that was the first thing I
tried in order to log in and kill the process.
Under X, you need to type Control_Alt_F1 etc.
bascially, there are several ways to proceed.
If you boot via LILO, then the best thing to do is to type at the
lilo prompt:
linux emergency
(replacing linux for your kernel image, press TAB).
Then none of the startup scripts are executed, and you can try to go
through the bootup manually, and checking what went wrong.
If the above doesn't work (your' not using lilo, for example), just
boot from a floppy, and try to mount your root filesystem on /mnt,
cd to it and examine what may have gone wrong, possibly correcting
it.
--
joost witteveen, [EMAIL PROTECTED]
#!/bin/perl -sp0777iX+d*lMLa^*lN%0]dsXx++lMlN/dsM0j]dsj
$/=unpack('H*',$_);$_=`echo 16dio\U$kSK$/SM$n\EsN0p[lN*1
lK[d2%Sa2/d0$^Ixp|dc`;s/\W//g;$_=pack('H*',/((..)*)$/)
#what's this? see http://www.dcs.ex.ac.uk/~aba/rsa/
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to
[EMAIL PROTECTED] .
Trouble? e-mail to [EMAIL PROTECTED] .
Re: Had to reset, now in deep kimshee....]
On Wed, 28 May 1997, Curt Howland wrote:
:
:However, the modules aren't supposed to be loaded from /usr: they are
supposed to
:live in /lib/modules, and the insmod executable is in /sbin, so there
_should_ be
:no problem. Did you messabout with your system?
:
:Nope. I didn't touch the modules, path, boot files
:or records. Just hit the reset switch. Something got
:scrambled, it seems.
:
:Warning to anyone with write-back cache on their
:hard disk: DO NOT HIT THE RESET SWITCH IN A MULTI-
:TASKING ENVIRONMENT!
:
:I was suprised that running X, with no window
:manager, hung the Alt-F1, Alt-F2... console login
:switch as well, since that was the first thing I
:tried in order to log in and kill the process.
Did you try ctrl-alt-{f1,f2,...} ? I believe that is how to get back to
a VC from within X. Somebody slap me if I'm wrong. Also,
ctrl-alt-bkspc is supposed to kill the X-server, though I've been told
you shouldn't do that. Seems like it'd be less harmful than the power
switch.
:
: If I go back to the rescue floppy, how much damage can I do to
[other stuff cut out]
--
Nathan Norman:Hostmaster CFNI:[EMAIL PROTECTED]
finger [EMAIL PROTECTED] for PGP public key and other stuff
Key fingerprint = CE 03 10 AF 32 81 18 58 9D 32 C2 AB 93 6D C4 72
--
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to
[EMAIL PROTECTED] .
Trouble? e-mail to [EMAIL PROTECTED] .
