The nice thing about slackware is that it's so primitive that if it
fails, it's not that much more trouble to just do for yourself what it
was trying to do for you. :-). As of slackware 3.4, the addkernel on
the text install image was still called addkernel.tty. Hmm. Looks line
it was missing a symbolic link in 3.4, too. But setup called it by its
right name, so it didn't need one. IIRC, when you boot up the install,
there is a point where it tells you to take care of any fdisk and mkfs
you need to do to make a place to install, then type setup. At this
point, you can type ls /bin and see if addkernel.tty exists. If it
does, you can do
cd /bin
ln -s addkernel.tty addkernel
and next time through setup may work a bit better. I think you can
break out of setup at any time to get into command mode and fix things
in setup. As well as the minimal linux system on the install image, you
now have access to all the commands you have already installed: if
Patrick hasn't changed things - and he's pretty conservative - they are
on /mnt, so - actually, mount will tell you where they are, or at least
what is mounted where - have a look in /mnt/bin, /mnt/sbin,
/mnt/usr/bin...
Is this any help?
Lawson
>< Microsoft free environment
This mail client runs on Wine. Your mileage may vary.
On Sun, 2 May 1999, Buddy Brannan, KB5ELV wrote:
> Just tried it again (yeah, nothin like banging yer head into a brick
wall,
> is there?), and here's the real error:
>
> .: Can't open /bin/addkernel
>
> Hrmm. I am of course no wiser than I was before. Anyway, I bet having
the
> correct error should help :)
>
> Thanks.
>
___________________________________________________________________
You don't need to buy Internet access to use free Internet e-mail.
Get completely free e-mail from Juno at http://www.juno.com/getjuno.html
or call Juno at (800) 654-JUNO [654-5866]
