Prev: Defining keymap prior to KDE log-in?
Next: mplayer
From: no.top.post on 12 Feb 2010 18:06
We've all seen the add: "because you're worth it", and no
one wants their sweated-labour software to have to prove itself
on the dog-box, before it gets installed on a better computer.
But I can't sacrifice my proper computer to test-install
the slak-13 DVD; and it complains:
for huge.s = out of memory ...
for hugesmp.s = unable to boot - use a kernel appropriate to your CPU.

I've only got IDE drive/s.

Can I use eg. the Debian 2.6x vlinuz & initrd which does load?

But I guess the slak initrd [is there one] has to populate
some essential files first ?
AFAIK eg. 'setup' is hidden inside of some boot-file?

== TIA

From: Douglas Mayne on 12 Feb 2010 19:28
On Fri, 12 Feb 2010 23:06:33 +0000, no.top.post wrote:

> We've all seen the add: "because you're worth it", and no one wants
> their sweated-labour software to have to prove itself on the dog-box,
> before it gets installed on a better computer. But I can't sacrifice my
> proper computer to test-install the slak-13 DVD; and it complains:
> for huge.s = out of memory ...
> for hugesmp.s = unable to boot - use a kernel appropriate to your CPU.
>
> I've only got IDE drive/s.
>
> Can I use eg. the Debian 2.6x vlinuz & initrd which does load?
>
> But I guess the slak initrd [is there one] has to populate some
> essential files first ?
>
Yes, an initrd is needed for most modular kernels.
>
> AFAIK eg. 'setup' is hidden inside of some boot-file?
>
> == TIA
>
Caveat: I haven't used any Debian kernels. However, I have used
customized modular kernels (once Slackware was installed).

I also wrote this about another install method:
http://groups.google.com/group/alt.os.linux.slackware/msg/704ccefaa58b86de

With Slackware, it's pretty easy to see if something is going to work or
to test if something is going to boot, etc. However, if that is a
critical system, then the usual caveats apply (backup first, know what
you're doing, etc.)

--
Douglas Mayne
From: Grant on 12 Feb 2010 19:49
On Fri, 12 Feb 2010 23:06:33 +0000 (UTC), no.top.post(a)gmail.com wrote:

>We've all seen the add: "because you're worth it", and no
>one wants their sweated-labour software to have to prove itself
>on the dog-box, before it gets installed on a better computer.
>But I can't sacrifice my proper computer to test-install
>the slak-13 DVD; and it complains:
> for huge.s = out of memory ...
> for hugesmp.s = unable to boot - use a kernel appropriate to your CPU.
>
>I've only got IDE drive/s.
>
>Can I use eg. the Debian 2.6x vlinuz & initrd which does load?
>
>But I guess the slak initrd [is there one] has to populate
>some essential files first ?
>AFAIK eg. 'setup' is hidden inside of some boot-file?

AFAICT 'setup' is inside the initrd. See the isolinux stuff on the DVD.

Long time ago I had to replace distro install kernel for a box, to use
correct disk drivers (I think way back 2003 or so when Intel P4-HT was
the new 'must have' feature upgrade, along with SATA drives).

Grant.
--
http://bugs.id.au/
From: Mikhail Zotov on 13 Feb 2010 10:22
On Fri, 12 Feb 2010 23:06:33 +0000 (UTC)
no.top.post(a)gmail.com wrote:
....
> But I can't sacrifice my proper computer to test-install
> the slak-13 DVD; and it complains:
> for huge.s = out of memory ...
> for hugesmp.s = unable to boot - use a kernel appropriate to your
> CPU.

This is strange. Here, Slack-13's DVD boots on a PC with only 128MB
of RAM.

--
Mikhail

 | 
Pages: 1
Prev: Defining keymap prior to KDE log-in?
Next: mplayer