I am running Suse 7.2. My problem is that as soon as the computer boots up
(it was running for a week before it got booted again) it loads the kernel
then goes into init 0 and shuts down. I can override this in lilo by
booting with "linux init 3 " but what is the problem
I have two hard drives, the better of which is the first (hda1). I dual boot
w98 and SuSE 7.2. Because of the way that w98 insists on being on the first
drive I have it installed as hda1 and SuSE on the rest of the first drive.
At the moment I use the second (hdb) older slower drive as a spare mainly for
backups and test installs. I want to put w98 on that drive and I understand
that if I use grub rather than lilo I can then set grub to fool w98 into
thinking that is on the first drive. Rather than going through another
painful w98 install I'd like to just move the present w98 install to that
drive. Is there a linux utility that I can use to do this ? That is create
an image of the win98 install, move it to hdb1 and then set up grub to boot
it so I can check that it works before I remove it from hda1 and reorganise
that drive ?
The w98 partition is about 4.0 gigs and the second drive is 6.4 gigs.
Thanks for any pointers anyone can offer.
Can anybody tell me what is the minimum install of SuSE 7.2?
I want to d/l only the necessary files and after installation
I would like to get the rest of installation by FTP.
Is that possible?
I have a ADSL line to the Internet.
Whatever happened to the knetload app that was in KDE 1?
It was quite nice being able to have it docked in the panel.
Is there an equivalent in KDE 2-2?
Can someone point me to a download site for this application? I found some
KDE pages that say it is included in KOffice, but I downloaded the 1.1
version of that, and KOrganizer is not there. It is also not listed on the
KOffice web site. I can't find it on the FTP servers, but I'm probably
looking in the wrong place.
Michael Molloy ResortQuest International
Java Developer www.ResortQuest.com
I've just built several variants of a 2.4.9 kernel for SuSE
7.2, and am having the same kernel panic no matter what I
try in the configuration options.
I started with a generic kernel tree from ftp.kernel.org,
and applied (with no error messages) all the patches for
2.4.9 from ftp://ftp.suse.com/...../martel/next/ on the
SuSE FTP site. Everything seemed fine, and the build went
In the build, I started with the default SuSE configuration
file from /boot, did a "make oldconfig" to bring it up to
2.4.9, and then ran "make xconfig" to remove some stuff like
Amateur Radio, ISDN, and MTD support, that I don't plan to
use. I ran make dep, make bzImage, make modules, and make
modules_install, in that order, after first making sure that
the directory /lib/modules/2.4.9 was empty.
Everything seemed to work fine. I copied the bzImage file to
a new filename under /boot, configured /etc/lilo.conf as
needed, then ran lilo.
When I try to boot the new kernel, I get a panic with the
following rather cryptic information:
Process init (pid: 1, stackpage=c1409000)
Stack: <<omitted for brevity>>
Call Trace: <<omitted for brevity>>
Code: 0f 0b eb 26 8d b6 00 00 00 00 83 7b 04 00 75 1d 68 b6 00 00
Kernel panic: Attempted to kill init!
I know what init does, but I have no idea how it came to be that
some process tried to kill it.
Rebooting from the original kernel still works, so my system isn't
hosed. I also tried rebooting from the rescue CD, immediately after
the crash, to recover any useful log entries, but alas there is
nothing being logged (too early in the boot process, I guess).
The console seems to indicate that the crash is happening just
after Reiserfs is loaded, but it scrolls by too fast for me to
Has anyone seen this before, and if so, what should I be checking
in my kernel config to isolate the problem?
Thanks for any help someone can offer.
"I don't mind Microsoft making money. I mind them having
a bad operating system." -- Linus Torvalds, in the NY Times
Scott Courtney http://www.4th.com/