> the best seems to be test26.i
Then you'll have to build an "initial ramdisk" because the 2.6 kernel
hasn't build in support for sata drives.
> but it's still in test, would sata.i be alright?
That would be my choice, but remember its not an definitive choice, you
can switch to the 2.6 kernel whenever you want.
--
Thomas O.
This area is designed to become quite warm during normal operation.
The following comments apply if you have some experience with slackware.
In any case, perhaps you want to let the installer setup your system
before swapping the kernel.
I would go with the kernels from Slackware-current, 2.4.32 (package
series /a, and you'll make an initial ramdisk with the appropriate SATA
chipset module) and 2.6.15.6 (/testing, also make an initial ramdisk). Try
them both and see which you like best. If you have a newer laptop with
Pentium M, then I'd advise compiling your own kernel with some
optimizations for that CPU.
For the loader, I prefer grub. Once grub is installed, it's easy to
change the kernel which loads. Slackware's default loader is lilo.
--
Douglas Mayne
I didn't find the 2.4.32 on the Slackware discs;
what do u mean by Slackware-current???? ftp.kernel.org????
how would it be with sata.i?
at least I have no errors up to the Linux login prompt n I can launch
fdisk...
Ok. Go with the default on your cds to start with.
Slackware is maintained in release branches, with -current used for
alpha/beta testing for the next release. For example, when 10.2 was
released the -current and 10.2 branches were the same. Now, some time has
passed since the 10.2 release. -current is a lot different from 10.2.
Likewise, security updates have been issued for packages in 10.2; they are
in the "patches" directory. It's self explanatory when looking at a
slackware mirror, such as this:
http://www.slackware.at/data/
I'll respond to your other thread.
--
Douglas Mayne
> For the loader, I prefer grub. Once grub is installed, it's easy to
> change the kernel which loads. Slackware's default loader is lilo.
Why would you install grub? Is there something that grub will do
that lilo won't?
cordially, as always,
rm
--
How come so many stat fans, and pseudo stat fans, are Jewish?
> Douglas Mayne <do...@localhost.localnet> trolled:
>
>> For the loader, I prefer grub. Once grub is installed, it's easy to
>> change the kernel which loads. Slackware's default loader is lilo.
>
> Why would you install grub? Is there something that grub will do
> that lilo won't?
>
> cordially, as always,
>
> rm
>
Grub is just my personal preference. If your system boots, then there is
no tremendous advantage to switching loaders- especially if you're used to
using lilo.
The loader is a separate component which is not really part of GNU/Linux.
You're probably an old hand at dual booting, but most people coming to
GNU/Linux from Windows do not realize that the loader is a separate
component. Setting up the loader for dual boot can be a bit tricky.
Also, the user has to decide which loader to use, and it is likely that
the user has never had to answer that question before.
IMO, grub is better at dual booting. But, recently I've advocated
VMWare as a better alternative than dual booting, as I wrote here:
http://groups.google.com/group/alt.os.linux.slackware/msg/694e981b14c99a4c
and recently here:
http://groups.google.com/group/alt.os.linux.slackware/msg/19f60ce7b4abb340
(discusses both grub and vmware).
--
Douglas Mayne
> I don't understand why VMWare would be better than GRUB;
> VMWare is a computer emuler and Grub is a boot loader!
>
That's right. But, they are both means by which the same goal can be
achieved. They both will give you access to both operating systems.
VMWare is superior because they will be accessible /* simultaneously */
not sequentially.
What are you trying to accomplish by making a dual boot system? You
apparently want access to Windows applications some of the time. Dual boot
gives you that, but you need to shut down Slackware first. When you reboot
you will be running Windows and will not have access to any files on your
Slackware install*. *Actually, there is an ext2 filesystem driver
available (for money) which runs on Windows.
The above dual boot scenario is one option. Grub is a loader which
helps facilitate booting between the two OSs.
In the referenced link (which you did not include), I explained the use of
VMWare to run a virtual machine which will give access to your Windows
applications. From the link:
The other thing VMWare does is show the OSs running side-by-side.
Cross platform applications like mozilla and open office can be compared
directly. The marginal "benefits" offered by the dominant platform are
readily apparent in this environment.
I have also written about some interesting work environments which
are possible using VMWare on GNU/Linux, but I'll just stop right
here.
I see you are using google groups to post. This is important (Courtesy of
CBFalconer's sig):
"If you want to post a followup via groups.google.com, don't use
the broken "Reply" link at the bottom of the article. Click on
"show options" at the top of the article, then click on the
"Reply" at the bottom of the article headers." - Keith Thompson
Also, important, quote some context in what you are replying too.
Remember, this is usenet, not google groups. Say it twice ;-)
--
Douglas Mayne
changing the kernel when using lilo is difficult??
> changing the kernel when using lilo is difficult??
Not at all. All you'll have to do is to add an extra boot option to
/etc/lilo.conf and then run /sbin/lilo.
You can check 'man lilo.conf' for details.
I'm afraid I don't understand that question.
Slackware will install its default loader, which is lilo.
grub is a boot loader.
http://www.gnu.org/software/grub/manual/html_node/index.html
lilo is a boot loader.
http://tldp.org/HOWTO/LILO.html
Any boot loader that works can be installed and used at the user's
discretion.
And this howto is a little old, but the general idea is the
same: http://www.tldp.org/HOWTO/Linux+NT-Loader.html
I may have gotten off on the wrong foot by assuming too much, but I did
say this: "The following comments apply if you have some experience with
slackware." This has happened to me before:
http://groups.google.com/group/comp.os.linux.setup/msg/bfcb7ea71181b671
http://groups.google.com/group/comp.os.linux.misc/msg/8ec50b07733f4d49
It's hard to know where to begin offering advice when someone asks for
help. If someone is installing to slackware, then I'll give them some
bonus points for having done their homework in advance.
If you only want to install and try Slackware, then go for it. The
usual caveats apply.
--
Douglas Mayne
> Douglas Mayne wrote:
> > On Wed, 05 Apr 2006 06:05:29 -0700, heavytull wrote:
> >
> >
> > For the loader, I prefer grub. Once grub is installed, it's easy to
> > change the kernel which loads. Slackware's default loader is lilo.
> changing the kernel when using lilo is difficult??
We don't want to be sarcastic, but seriously, why would you go to
the bother of installing grub when you already have lilo installed?
You say that you prefer grub. But why? Is there some feature that
lilo lacks?
We have never used grub. We have never felt the need to use
anything but lilo.
cordially, as always,
rm
yes I search on the net about partitioning science;
I didn't find a lot more than what you said.
I asked you how can I know whether I have logical or primary partition
because there is no specific label about that with fdisk -l
in fact the only info about that is the # in the assigned name of the
partition, for example: hdb1, hdb5...
here I'm pasting what's shown by fdisk on another hd with WinXP and
Linux:
Disk /dev/hdb: 10.2 GB, 10242892800 bytes
255 heads, 63 sectors/track, 1245 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/hdb1 * 1 780 6265318+ 7 HPFS/NTFS
/dev/hdb2 781 1245 3735112+ f W95 Ext'd (LBA)
/dev/hdb5 781 853 586341 83 Linux
/dev/hdb6 854 902 393561 82 Linux swap /
Solaris
/dev/hdb7 903 1107 1646631 83 Linux
/dev/hdb8 1108 1245 1108453+ 83 Linux
I don't really understand why so many partitions for Linux, I made them
with Partition Magic long time back but I don't remember having made 4
partitions
it seems there one primary partition at least
I don't know how to call the hdb2. Since it seems the 4 others
(logical) are on it, it might be an extended partition but its number
(2) tricks me.
I didn't try again with fdisk on my laptop since yesterday when I
posted; Ok, let's admit the kernel named my hd as sd as many think in
this topic. What should I do then?? going on as if everything was ok or
doing something? I would prefer everything alright so I would prefer a
kerner which names my hd hd not sd.
I didn't try with test26, but at the end I will have to instal it on my
hd so I will have to use it everytime I use Linux so I would prefer
something safe, not a beta version.
Reply
From: heavytull - view profile
Date: Thurs, Apr 6 2006 4:06 pm
Email: "heavytull" <heavyt...@hotmail.com>
Groups: alt.os.linux.slackware
Not yet ratedRating:
show options
Reply | Reply to Author | Forward | Print | Individual Message | Show
original | Remove | Report Abuse | Find messages by this author
PM is Partition Magic?
I just resized the ntfs partition to a smaller one with PM. nothing
else!
Reply
From: Douglas Mayne - view profile
Date: Thurs, Apr 6 2006 4:47 pm
Email: Douglas Mayne <d...@localhost.localnet>
Groups: alt.os.linux.slackware
Not yet ratedRating:
show options
Reply | Reply to Author | Forward | Print | Individual Message | Show
original | Report Abuse | Find messages by this author
On Thu, 06 Apr 2006 07:03:56 -0700, heavytull wrote:
> yes I search on the net about partitioning science;
It's not a science, really ;-) You just need to understand the rules.
These are not the laws of nature. The partitioning rules were created
about 20 years ago with the advent of 10MB hard drives for PCs.
> I didn't find a lot more than what you said.
> I asked you how can I know whether I have logical or primary partition
> because there is no specific label about that with fdisk -l
> in fact the only info about that is the # in the assigned name of the
Right. The number is all you need to know to decide. If it is 4 or
lower, then it's a primary type. If it's 5 or above it's a logical
partition. The logical partitions are allocated from space which has
been
allocated on the disk on an "extended" partition. In other words, the
extended partition is the container which holds the logical partitions.
> partition, for example: hdb1, hdb5... here I'm pasting what's shown by
> fdisk on another hd with WinXP and Linux:
> Disk /dev/hdb: 10.2 GB, 10242892800 bytes
> 255 heads, 63 sectors/track, 1245 cylinders
> Units = cylinders of 16065 * 512 = 8225280 bytes
> Device Boot Start End Blocks Id System
> /dev/hdb1 * 1 780 6265318+ 7 HPFS/NTFS
> /dev/hdb2 781 1245 3735112+ f W95 Ext'd (LBA)
/dev/hdb2 is a primary partition which is type "extended." The
container
is 3.7G +/-
> /dev/hdb5 781 853 586341 83 Linux
> /dev/hdb6 854 902 393561 82 Linux swap/Solaris
(gnore the word solaris)
> /dev/hdb7 903 1107 1646631 83 Linux
> /dev/hdb8 1108 1245 1108453+ 83 Linux
sum of sizes of logical partitions: (.586+.394+1.65+1.11=3.7)
The extended partition has been fully allocated with 4 logical
partitions.
> I don't really understand why so many partitions for Linux, I made them
> with Partition Magic long time back but I don't remember having made 4
> partitions
/dev/hdb5 is likely to be a boot partition. You may have forgotten what
you did, so it's always a good idea to document your steps,
especially your partition table, and especially on dual boot
computers. A table (on paper) with some hints about what each partition
is
used for can be handy when something breaks or you need to make
changes in the future. The file /etc/fstab will also have pointers but
paper is really the best (because disks fail.)
> it seems there one primary partition at least I don't know how to call
> the hdb2. Since it seems the 4 others (logical) are on it, it might be
> an extended partition but its number (2) tricks me.
I hope my explaination above clarified that.
> I didn't try again with fdisk on my laptop since yesterday when I
> posted; Ok, let's admit the kernel named my hd as sd as many think in
> this topic. What should I do then?? going on as if everything was ok or
> doing something? I would prefer everything alright so I would prefer a
> kerner which names my hd hd not sd.
> I didn't try with test26, but at the end I will have to instal it on my
> hd so I will have to use it everytime I use Linux so I would prefer
> something safe, not a beta version.
Note: comments inline.
Slackware with kernel 2.4.31 is rock solid stable. Upgrading to
kernel 2.4.32 would have some marginal benefit. Most other GNU/Linux
distributions use a 2.6.x kernel by default. You know, the 2.6.x
kernel
has been out a long time, right? It's still in flux, but it is better
than
beta. I would run 2.6.15.6 from -current testing, but that's just me
(I'm
a gambler, I'd bet it all...) Seriously, get Slackware installed and
see
how you like it first.
I setup a Dell D610 which uses the Pentium M chip, like your laptop
does.
Processor speed scaling works with 2.6.x, and not with 2.4.x. You may
need to decide if the extra features are worth the jump to the next
kernel.
--
General: Where the hell have you been, soldier?
John: Training, sir. __Plattoon: TRAINING, SIR!__
General: What kind of training, son?
John: A-a-army training, sir! __Plattoon: ARMY TRAINING, SIR!__
Reply Rate this post: Text for clearing space
I tried the test26.s kernel, it is same as sata.i, they both recognize
the hard drive as sda and the cdrom drive as hda.
so it seems that no one kernel is the right one for my laptop.
> I tried the test26.s kernel, it is same as sata.i, they both recognize
> the hard drive as sda and the cdrom drive as hda.
> so it seems that no one kernel is the right one for my laptop.
I don't understand your conclusion. If your hard drive is SATA, then it
*will* be recognized as "sdX" by a modern kernel, because the driver
that handles that drive is providing an emulated SCSI interface to the
kernel for it. Why, if I may ask, are you so concerned with having your
SATA disk recognized as "hda"?
--
----------------------------------------------------------------------
Sylvain Robitaille s...@alcor.concordia.ca
Systems and Network analyst Concordia University
Instructional & Information Technology Montreal, Quebec, Canada
----------------------------------------------------------------------