First Master Slackware, then appreciate Debian

DaWallace · 03-02-2005, 02:34 PM

today's boot floppies were damn good.. I used them on a desperate install earlier today and I didn't have any cds

http://www.debian.org/devel/debian-i...r/ports-status

this well hidden page on the debian site is by far the greatest debian related item I've ever come across.

EliotK · 03-02-2005, 02:49 PM

Can anyone copy and paste their grub config for debian please

bobbens · 03-02-2005, 03:12 PM

Quote:

Originally posted by EliotK
Can anyone copy and paste their grub config for debian please

you mean menu.lst?

EliotK · 03-02-2005, 03:14 PM

yah whatever it is in debian but i think im gonna reinstall all the shit again, but with fc3 first then debian, so i use debians grub.

bobbens · 03-02-2005, 03:17 PM

Code:

# menu.lst - See: grub(8), info grub, update-grub(8)
#            grub-install(8), grub-floppy(8),
#            grub-md5-crypt, /usr/share/doc/grub
#            and /usr/share/doc/grub-doc/.

## default num
# Set the default entry to the entry number NUM. Numbering starts from 0, and
# the entry number 0 is the default if the command is not used.
#
# You can specify 'saved' instead of a number. In this case, the default entry
# is the entry saved with the command 'savedefault'.           
default		0

## timeout sec
# Set a timeout, in SEC seconds, before automatically booting the default entry
# (normally the first entry defined).
timeout		5

# Pretty colours
color cyan/blue white/blue

## password ['--md5'] passwd
# If used in the first section of a menu file, disable all interactive editing
# control (menu entry editor and command-line)  and entries protected by the
# command 'lock'
# e.g. password topsecret
#      password --md5 $1$gLhU0/$aW78kHK1QfV3P2b2znUoe/
# password topsecret

#
# examples
#
# title		Windows 95/98/NT/2000
# root		(hd0,0)
# makeactive
# chainloader	+1
#
# title		Linux
# root		(hd0,1)
# kernel	/vmlinuz root=/dev/hda2 ro
#

#
# Put static boot stanzas before and/or after AUTOMAGIC KERNEL LIST

### BEGIN AUTOMAGIC KERNELS LIST
## lines between the AUTOMAGIC KERNELS LIST markers will be modified
## by the debian update-grub script except for the default optons below

## DO NOT UNCOMMENT THEM, Just edit them to your needs

## ## Start Default Options ##
## default kernel options
## default kernel options for automagic boot options
## If you want special options for specifiv kernels use kopt_x_y_z
## where x.y.z is kernel version. Minor versions can be omitted.
## e.g. kopt=root=/dev/hda1 ro
# kopt=root=/dev/hda3 ro noapic nolapic

## default grub root device
## e.g. groot=(hd0,0)
# groot=(hd0,2)

## should update-grub create alternative automagic boot options
## e.g. alternative=true
##      alternative=false
# alternative=true

## should update-grub lock alternative automagic boot options
## e.g. lockalternative=true
##      lockalternative=false
# lockalternative=false

## altoption boot targets option
## multiple altoptions lines are allowed
## e.g. altoptions=(extra menu suffix) extra boot options
##      altoptions=(recovery mode) single
# altoptions=(recovery mode) single

## controls how many kernels should be put into the menu.lst
## only counts the first occurence of a kernel, not the
## alternative kernel options
## e.g. howmany=all
##      howmany=7
# howmany=all

## should update-grub create memtest86 boot option
## e.g. memtest86=true
##      memtest86=false
# memtest86=true

## ## End Default Options ##

title Debian GNU/Linux, kernel 2.6.8-2-k7
	root (hd0,2)
	kernel /boot/vmlinuz-2.6.8-2-k7 root=/dev/hda3 ro noapic nolapic
	initrd /boot/initrd.img-2.6.8-2-k7

title Debian GNU/Linux, kernel 2.6.8-2-k7 (recovery mode)
	root (hd0,2)
	kernel /boot/vmlinuz-2.6.8-2-k7 root=/dev/hda3 ro noapic nolapic single
	initrd /boot/initrd.img-2.6.8-2-k7

title windoze, teh sux (abandoned)
	rootnoverify (hd0,0)
	makeactive
	chainloader +1

utanja · 03-02-2005, 04:36 PM

Code:

# menu.lst - See: grub(8), info grub, update-grub(8)
#            grub-install(8), grub-floppy(8),
#            grub-md5-crypt, /usr/share/doc/grub
#            and /usr/share/doc/grub-doc/.

## default num
# Set the default entry to the entry number NUM. Numbering starts from 0, and
# the entry number 0 is the default if the command is not used.
#
# You can specify 'saved' instead of a number. In this case, the default entry
# is the entry saved with the command 'savedefault'.           
default		0

## timeout sec
# Set a timeout, in SEC seconds, before automatically booting the default entry
# (normally the first entry defined).
timeout		5

# Pretty colours
color cyan/blue white/blue

## password ['--md5'] passwd
# If used in the first section of a menu file, disable all interactive editing
# control (menu entry editor and command-line)  and entries protected by the
# command 'lock'
# e.g. password topsecret
#      password --md5 $1$gLhU0/$aW78kHK1QfV3P2b2znUoe/
# password topsecret

#
# examples
#
# title		Windows 95/98/NT/2000
# root		(hd0,0)
# makeactive
# chainloader	+1
#
# title		Linux
# root		(hd0,1)
# kernel	/vmlinuz root=/dev/hda2 ro
#

#
# Put static boot stanzas before and/or after AUTOMAGIC KERNEL LIST

### BEGIN AUTOMAGIC KERNELS LIST
## lines between the AUTOMAGIC KERNELS LIST markers will be modified
## by the debian update-grub script except for the default optons below

## DO NOT UNCOMMENT THEM, Just edit them to your needs

## ## Start Default Options ##
## default kernel options
## default kernel options for automagic boot options
## If you want special options for specifiv kernels use kopt_x_y_z
## where x.y.z is kernel version. Minor versions can be omitted.
## e.g. kopt=root=/dev/hda1 ro
# kopt=root=/dev/hda6 ro

## default grub root device
## e.g. groot=(hd0,0)
# groot=(hd0,4)

## should update-grub create alternative automagic boot options
## e.g. alternative=true
##      alternative=false
# alternative=true

## should update-grub lock alternative automagic boot options
## e.g. lockalternative=true
##      lockalternative=false
# lockalternative=false

## altoption boot targets option
## multiple altoptions lines are allowed
## e.g. altoptions=(extra menu suffix) extra boot options
##      altoptions=(recovery mode) single
# altoptions=(recovery mode) single

## controls how many kernels should be put into the menu.lst
## only counts the first occurence of a kernel, not the
## alternative kernel options
## e.g. howmany=all
##      howmany=7
# howmany=all

## should update-grub create memtest86 boot option
## e.g. memtest86=true
##      memtest86=false
# memtest86=true

## ## End Default Options ##

title		Debian GNU/Linux, kernel 2.6.10p3 
root		(hd0,4)
kernel		/vmlinuz-2.6.10p3 root=/dev/hda6 ro 
savedefault
boot

title		Debian GNU/Linux, kernel 2.6.10p3 (recovery mode)
root		(hd0,4)
kernel		/vmlinuz-2.6.10p3 root=/dev/hda6 ro single
savedefault
boot

title		Debian GNU/Linux, kernel 2.6.10p1 
root		(hd0,4)
kernel		/vmlinuz-2.6.10p1 root=/dev/hda6 ro 
savedefault
boot

title		Debian GNU/Linux, kernel 2.6.10p1 (recovery mode)
root		(hd0,4)
kernel		/vmlinuz-2.6.10p1 root=/dev/hda6 ro single
savedefault
boot

title		Debian GNU/Linux, kernel 2.6.8p2 
root		(hd0,4)
kernel		/vmlinuz-2.6.8p2 root=/dev/hda6 ro 
savedefault
boot

title		Debian GNU/Linux, kernel 2.6.8p2 (recovery mode)
root		(hd0,4)
kernel		/vmlinuz-2.6.8p2 root=/dev/hda6 ro single
savedefault
boot

title		Debian GNU/Linux, kernel 2.6.10-1-686 
root		(hd0,4)
kernel		/vmlinuz-2.6.10-1-686 root=/dev/hda6 ro 
initrd		/initrd.img-2.6.10-1-686
savedefault
boot

title		Debian GNU/Linux, kernel 2.6.10-1-686 (recovery mode)
root		(hd0,4)
kernel		/vmlinuz-2.6.10-1-686 root=/dev/hda6 ro single
initrd		/initrd.img-2.6.10-1-686
savedefault
boot

### END DEBIAN AUTOMAGIC KERNELS LIST

have fun.....

Baruch · 03-04-2005, 08:24 AM

I have a different experience then the topic starter.

I switched from slackware to Debian....and then back again.

Why? Because Slackware is the only distribution that never failed me in all those years.

Just recently i posted a question here because i had trouble with DHCP on my Debian-testing based gateway. And even Debian-stable gave me trouble a while ago. Maybe it's my incompetence, but i never had that kind of trouble with Slackware.

Sure, i love apt, but the most important thing is that a distro actually works. And Slackware always works, at least in my hands.

So that's why i pick Slackware over Debian anytime...

bobbens · 03-04-2005, 11:41 AM

Quote:

Originally posted by Baruch
I have a different experience then the topic starter.

I switched from slackware to Debian....and then back again.

Why? Because Slackware is the only distribution that never failed me in all those years.

Just recently i posted a question here because i had trouble with DHCP on my Debian-testing based gateway. And even Debian-stable gave me trouble a while ago. Maybe it's my incompetence, but i never had that kind of trouble with Slackware.

Sure, i love apt, but the most important thing is that a distro actually works. And Slackware always works, at least in my hands.

So that's why i pick Slackware over Debian anytime...

I haven't been able to get debian-stable to work on my good computer, but testing (sarge) works great. I dunno, i find debian really easy to mantain and use and am getting lots of things working lately. I haven't tried slack, but have gone to gentoo and back, because of my gcc getting corrupted. As for debian as a server, i have it as a network FTP/APT/APACHE server and have no problems at all, though i haven't attempted to do a DHCP server. Sorry your experience in debian was that poor, switching distros is always hard, especially once you've gotten used to one.

Sepero · 03-05-2005, 06:27 AM

Quote:

Originally posted by Baruch
I switched from slackware to Debian....and then back again.

Why? Because Slackware is the only distribution that never failed me in all those years.

Wow, that's a pretty bold statement. So how many years did you use Debian?

Personally, I used Slack for nearly a full year before I tried/moved to Debian. (The reason=debian policy.)

Baruch · 03-05-2005, 11:25 AM

Quote:

Originally posted by Sepero
Wow, that's a pretty bold statement. So how many years did you use Debian?

Over the years i tried lots off distributions, Slackware, Gentoo, Debian, Mandrake, Suse, Red Hat, Libranet. And i NEVER had trouble with Slackware. All the others gave me problems in one form or the other. Some serious, and some less serious problems.

So i don't see why my statement is bold, it's just what happened to me.

This doesn't mean i hate Debian. I fact i like it, and would like to use it in the future. Because it's the only really free distribution, and i love the shitload of packages at my fingertips. With Pat's recent illness, i'm more eager to switch. But like i sad, i can't get Debian working on the hardware i have. Networking is pretty essential you know, and i had lots of DHCP-problems recently with Debian-testing.

Sepero · 03-06-2005, 06:20 AM

Quote:

Originally posted by Baruch
Why? Because Slackware is the only distribution that never failed me in all those years.

Sorry, I must have mis-read your post to mean, "In all the years I used Debian and Slackware together, Slackware never failed me."

So does this mean you've never actually had a Debian system up and running? It seems pretty sad that you would let a little network trouble stop you. Heck, if I let network trouble stop me, I wouldn't be using Linux At All. Slack was my first distro, and it took me weeks to get my software modem running. (And when it came to Debian, I was very stubborn about changing distros too, because I wasn't sure if I wanted to go through all that hassle again.)

Baruch · 03-06-2005, 06:29 AM

Quote:

Originally posted by Sepero
Sorry, I must have mis-read your post to mean, "In all the years I used Debian and Slackware together, Slackware never failed me."

So does this mean you've never actually had a Debian system up and running? It seems pretty sad that you would let a little network trouble stop you. Heck, if I let network trouble stop me, I wouldn't be using Linux At All. Slack was my first distro, and it took me weeks to get my software modem running. (And when it came to Debian, I was very stubborn about changing distros too, because I wasn't sure if I wanted to go through all that hassle again.)

I tried almost two full days to get Debian working last time. I asked questions here, on debian's irc-channel, on usenet and on other forums.

Do you think that's enough?

I also have other things to do you know...

Sepero · 03-06-2005, 06:47 AM

I see your point. Perhaps you should stay with Slackware.

Baruch · 03-06-2005, 06:48 AM

Quote:

Originally posted by Sepero
I see your point. Perhaps you should stay with Slackware.

Exactly my conclusion. I'll try Debian again in a few months or so.

Sepero · 03-06-2005, 06:57 AM

Ok, maybe next time this link might be able to help you out:
http://www.debian.org/doc/