Slack install question
 

I downloaded slack install iso and i want to know if im gonna need the extras cd for anything? I have been using rh for a while and some of the things you select during install require the 2nd cd, does anything in the slack install require a different cd?

And another question: Did they mean to keep the file names on the cd in 8.3 format or is my cd dorked. Used fireburner to create cd from image.

I just wanna try a different distro and slack seems like a good one to try, less bloat.

Thanks for any replies

i've done a full install without the second extras cd..

Under 7.0 I never used the extra's CD, nor under 7.1. When Slack 8 came out I was trying to get it on day 1 like 4.8 billion other jokers so I only ever got a copy of disc 1: Install. I've copied/used that disc at least 15 times over and never needed more than that for a base system: all of KDE or Gnome, working X, kernel source, every networking tool necessary (aside from some wireless stuff), blah blah blah

Cheers,

Finegan

Thanks for the fast replies, gonna blow away my redhat install on my laptop now, hopefully the next post will be from slack.

Thanks again.

True, the #2 CD is UN-needed. It's labeled 'extras'. The whole #2 CD is extra contrib works and sorts. It IS nice to have since it has Afterstep,BlackBox,IceWm etc.. as Slack packages to install nice and easy. Nothing critical though, unless you want the full system source. ;)

Well your looking at a proud owner of a slackware laptop. Woohoo!!!
I had a prob with the built in NIC, but ya gotta go with what you know: tulip
works great.
X setup was the same as i had to do in redhat and mandrake. had to add a ChipSet "cyberbladeXPm" line in XF86Config and bame theres a nice CLEAN looking gnome desktop.

Now I just gotta get my sound working, i didnt see a meastro3 in the rc.modules file, i'll have to read up on that one.

Had a few hicups at first: way different harddrive setup then redhat/mandrake, but got through it. Then after i did finally get the harddrive setup, i got up from the couch and zap, static elec shock, comp shut down and had to start over. The package install was kinda slick, I like the fact that you dont run into rpm dep's probs when you unselect stuff. And I must say, it is alot faster then redhat was on this laptop.

Here's info on laptop:
HP5430 pavillion
Duron 850
128mb RAM
Accton miniPCI NIC card built in works with tulip
Trident CyberbladeXP (Select cbyerblade 9250 during install or it will load older drivers) and add ChipSet "cyberbladeXPm" 1024x768x16 work great, and add vga=791 to lilo.conf to get a nice looking fb when in console.

I'll let you know if i get sound working,

Congrats on the install. Slack is a little slicker than the rest I think. Obviously a bit less graphical at first, but hey huh. At sourceforge.net, Slack has a current directory with some updated packages also...I'm just so happy when I hear people use Slack, it's a little silly I spose, but Slack doesn't get the hype the others do. :)

Got the sound to work, I hope i did it correctlly: edit /etc/rc.d/rc.modules I uncommented the line /sbin/modprobe maestro, i added a 3 on the end cause there was a module in the /usr/lib/modules/kernel/driver/sound named maestro3. Then i did ./rc.modules reload, it works so i guess i did it right. So it should start sound at bootup?

Took me a minute or two to figure out that there is no sndconfig in slack LOL

Man it's gonna take a little while to get used to the differences between slack and redhat, but i guess im doing ok cause i got it installed and up and running with sound ,vid, networking.

Well sound worked for root but no-one else, So i gave my normal user permissions to read/write the /dev/mixer /dev/dsp and /dev/cdrom. This is where GUI's would be helpfull, this typing is making me think too much LOL. I like slack so far

Yeah, Slack sort of forces you to edit files alot more and use your brain more often than i'd like I know!! :) But you sound like you have all of the basics down fine. Slackware sort of starts out fresh and as a skeleton sort of in that root IS the only one who will get permissions until you, as you've done, give your users permission to a group or the files themselves and what not. Otherwise is fairly groovy once you really get the command line hang of things, it's actually sort of fun. Have a good one and keep up the fast pace...

I'm looking to install slack on my laptop as well. I've downloaded the root and boot disc files I need, along with files out of other packages in the /slakware directories. I'd like to install just the things I need (or think I do). Is it easy for me just to install the basic basic stuff then add the rest in later.
I'd like to run the boot disk, install off the root disk, so it's on my hard drive, then add what I need in later. Can you tell me if you think this is a good idea, or am I better off downloading CD1 iso and running the install off that?
Thanks.:rolleyes:

It doesn't get any easier than the CD. You might want to try a boot/root install just for the experience factor... or, if you have a lot of bandwidth, you might want to try the boot/root/pcmcia install. I did this exact thing once, from work (which is the same university as a Slackware mirror, so mileage will vary). Slack installs rather slick, so basically no matter what goes wrong, you can troubleshoot it.

-cheers,

Finegan

Congrats to you all! I had slack on my laptop(Duron 900 Sony Vaio FXA32) but took it off due to inability to play fullscreen mame and DivX/VCD with any decent framerate(mame wouldn't fullscreen @ all).

I believe you've graduated into a more robust OS because of the fact you have to maintain control of it. Little wizards aren't going to solve any real issues because once it jumps out of that domain you're stuck.

Next thing to tackle is LFS on a laptop...but I don't currently have enough free time to do so.

J