deb or slack?

Then you'll have to type "man grub" to find out how to pass kernel params from its config file.

Originally posted by gui10 btw, taz are u from tasmania? i went there for a holiday in May 2000... lovely place...

I'm actually not from tasmania, although I would love to see it sometime! I'm just a huge Taz/Dizzy Devil cartoon character fan.

Originally posted by SlCKB0Y Sorry just a few things you said before that i felt needed to be straightened up. Slackware was by no means the first distro. it was more like the second or third. but its the oldest distro still actively updated. Secondly, PV does not do all the work on slackware by any stretch o f the imagination. hhe has quite a dedicated team working with him. my favourite person being david cantrell. (who is busily working on that beloved slackware auto update app). Slackware is prob easier to configure, has a BSD style init as opposed to SysV, but it will be a lot of compiling from source. I feel that you will learn so much from using and configuring slackware. i seriously learned more from installing slack than i did in a few months of using redhat. try them both and see which one you like - im willing to bet it will be slackware anyways.

As I said in my post, Slackware was "ONE OF, if not the first.." distros out there. RedHat probably came out before Slack, and it's still actively updated by the way. PV does do alot of the work although he does have a small group of people who help him. Ok, I concede to that, but it by no means is close to a Corp. to rival a RH or Mandrake. Slack will use SysV init if you want and whether or not that matters, is up for grabs. I've been using Slack for a while and am plenty happy with it and agree to learning more with it faster than any other i've used. I don't really see the point hopping distros anymore since I'm quite happy with Slackware.

i just read the manual for GRUB... and this is what it says:


[COLOR=dark blue]

"Note that GRUB does _not_ distinguish IDE from SCSI - it simply counts the drive numbers from zero, regardless of their type."

[/COLOR]

uh... doesn't that make scsi emulation a lot harder?

any ideas anyone?

Yeah, my suggestion is to go with LILO. Still the best way to go I say. But hey, who am i? Really, who am I? I don't know either. My forehead has the linux console burnt into it backwards. It says:

:nigol
:rdowssap
nigol tcerrocni
ho`D

:rdowssap = : passwodr
No wonder your getting a "D'oh"

gui10, you add the hd*=ide-scsi that Aussie gave you to the kernel line. Like this:

kernel=/boot/vmlinuz vga=normal debug=2 root=/dev/hda3 hd*=ide-scsi

The kernel line is kind of like the append line in lilo.conf.

Originally posted by Aussie :rdowssap = : passwodr No wonder your getting a "D'oh"

LOL Thanks, I tried as hard as I could! hehehe..

thanks for the tip...

i tried it but it kinda resulted in a kernel panic at bootup...

could u give me a more detailed explanation?
perhaps replcaing the hd* with an actual hdd or something ? coz i may have gotten it wrong (most likely)

thanks

Replace "hd*" with the correct info for your cd-rw. So if the drive was on the secondary slave ide channel it would be "hdd"

I'm sorry gui10. I forgot to tell you to replace the ' * ' with the correct drive letter like Aussie says in his post.

just to clarify (i know i sound paranoid but bear with me, the previous company i worked for emphasized that overcommunication is better than misunderstanding... hoho):

so if i physically connected the IDE cables such that my primary master is my first hard disk(windows) and primary slave is my cd-rw, and secondary master is my second hard disk(linux), then the line would look something like this?

kernel=/boot/vmlinuz vga=normal debug=2 root=/dev/hda3 hda=ide-scsi

or do i put hda1=ide-scsi

Primary master = hda
Primary slave = hdb
Secondary master = hdc
Secondary slave = hdd
So you need to put "hdb"
The numbers refer to the partitions on your hard drives.

ah good!
the info i was looking for...

ta aussie

Your Welcome.