From: Aaron W. Hsu on
On Mon, 11 Jan 2010 08:59:28 -0500, GangGreene <GangGreen(a)invalid.com>
wrote:

> I just need to finish up on changing the kernel from huge to generic, smp
> setting up my wireless, and enabling kdm on boot and then I am good.
> BTW does the generic kernel have pae enabled? If not I can change it and
> recompile, I don't think it will be any trouble.

Make sure that you check out the README in /boot about initrds. That
pretty much explains how a generic kernel works. Most things are compiled
as modules, and I've never had to recompile the generic kernel proper to
get what I wanted. There is also a helper script that will show you how to
build the initrd by automatically scanning your system and generating the
command for you.

Aaron W. Hsu

--
A professor is one who talks in someone else's sleep.
From: GangGreene on
Aaron W. Hsu wrote:

> On Mon, 11 Jan 2010 08:59:28 -0500, GangGreene <GangGreen(a)invalid.com>
> wrote:
>
>> I just need to finish up on changing the kernel from huge to generic, smp
>> setting up my wireless, and enabling kdm on boot and then I am good.
>> BTW does the generic kernel have pae enabled? If not I can change it and
>> recompile, I don't think it will be any trouble.
>
> Make sure that you check out the README in /boot about initrds. That
> pretty much explains how a generic kernel works. Most things are compiled
> as modules, and I've never had to recompile the generic kernel proper to
> get what I wanted. There is also a helper script that will show you how to
> build the initrd by automatically scanning your system and generating the
> command for you.
>
> Aaron W. Hsu
>


OK Thank you
From: GangGreene on
Aaron W. Hsu wrote:

> On Mon, 11 Jan 2010 08:59:28 -0500, GangGreene <GangGreen(a)invalid.com>
> wrote:
>
>> I just need to finish up on changing the kernel from huge to generic, smp
>> setting up my wireless, and enabling kdm on boot and then I am good.
>> BTW does the generic kernel have pae enabled? If not I can change it and
>> recompile, I don't think it will be any trouble.
>
> Make sure that you check out the README in /boot about initrds. That
> pretty much explains how a generic kernel works. Most things are compiled
> as modules, and I've never had to recompile the generic kernel proper to
> get what I wanted. There is also a helper script that will show you how to
> build the initrd by automatically scanning your system and generating the
> command for you.
>
> Aaron W. Hsu
>


Did not find the helper script to build the initrd.
Do you know which package it is in?

I'll fetch it by force ;)




From: barnabyh on
* GangGreene <GangGreen(a)invalid.com> wrote:
> Douglas Mayne wrote:
>> Do you mean you are switching to Slackware 12.0? or 12.1? or 12.2?
>
> Yes switching to slack 12.2, I don't want kde4, I want kde3.5
> I will use kde 3.5 until kde4 is mature at the same state as kde 3.5.
> I was using kde4 on arch what a pain.
> Even after kde4 is mature I think I rather use xfce4. ;)
> KDE4 could be all right on slack but still I going with stable.
>

There are official KDE 3.5 packages out for Slackware 13.

ftp://ftp.slackware.no/pub/linux/slackware/unsupported/

For doing a new install like you do I would really recommend going with
13 as well.


Barnabyh
--
The general public is a bunch of morons who destroy the fun and life in
everything it collectively touches. Disney is what the public wants.
NASCAR is what the public wants. Windows is what the public wants.
(Comment on Slashdot, Monday March 28 2005, @11:02AM, Gnome
Removed From Slackware.)
From: barnabyh on
* GangGreene wrote:
>
> I Thank you for your help

You're welcome.

>
> I have a lot of the differences sorted out now between slack and arch.
> Slack is just what I have been looking for. Seems to be more stable and very
> much quicker than arch.
>

I don't know that much about Arch but Slackware is definitely more
stable. I would think even if you track -current it will be more stable
than Arch.
>
> I can then complete my exodus from arch. Arch was good when I first
> installed it 3 to 4 years ago, but now it is a PITA.... Printing is now not
> working easily, I have worked at getting my HP Laserjet 2300d working for
> weeks and it still isn't right. Something causes my desktop to freeze
> requiring a hard poweroff/boot. This machine worked well until the last
> round of updates. I no longer agree...
> I want something that works and
> continues to work. I don't have the time to be constantly fixing things
> after an upgrade.
>

Ah, the feeling that you had more time to actually use your computer and
get things done, despite the (automated anyway) virus and malware
checks, if you were using Windows.

I think Slackware will suit you fine. It may be a little more time in the
beginning but once it's done it's done, and no unpleasant surprises
unless you don't read.

There's a lot of vavavoum about Arch, but people constantly migrate back
and forth, and as you said, after a while most people want something that
works predictably.

Barnabyh
--
The general public is a bunch of morons who destroy the fun and life in
everything it collectively touches. Disney is what the public wants.
NASCAR is what the public wants. Windows is what the public wants.
(Comment on Slashdot, Monday March 28 2005, @11:02AM, Gnome
Removed From Slackware.)
First  |  Prev  |  Next  |  Last
Pages: 1 2 3 4 5
Prev: Coming gotchya
Next: Blown hard-drive and motherboard!