i need to go back to slack

[pvd212]

Ok I was using Slackware 9.1 and I got board so I format /dev/hdb and renstalled Slack, but i forgot my gateway DNS and even my IP, so I again format /dev/hdb and installed Redhat. I've been wanting to try it for a while and i used this as an excuse to. I don't like it and I want to go back to Slack, but then I remembered I forgot my info. Where can I go on Redhat to get this inforormation, such as my IP, my defuilt gatway, and my DNS ? Can someone please help, I cant stand Redhat 9.0 I need my Slackware9.1!

[hard candy]

Should be in the /etc directory in /hosts, /hostname, /resolv.conf,/host.conf, /network/interfaces.

[pvd212]

thanks

[bandwidth_pig]

Also if your going through a cable or DSL router, that information will also be in there.

[pvd212]

and i am back on slack :D

[emactive]

i went from Fedora Core to Slack 9.1

didn't feel at home, right?

i don't think i would ever go back or leave...unless it was for freeBSD. i might have to give that a try.

pvd212: where in RI are you from?

[pickarooney]

Just how hard is slack? Is it a complete no-go if there are no linux drivers for your gfx card?

[emactive]

Originally posted by pickarooney
Just how hard is slack? Is it a complete no-go if there are no linux drivers for your gfx card?

i dont think slack is hard to setup. best thing to do is dedicate a computer to linux and start from there. i purposely installed slack 9.1 about 5 or 6 times just to understand the little things like partitioning and such. slack is a great learning experience. i "think" slack is flexible with their drivers now. i'm really not sure. my **** works fine in X using the default drivers it gives me. then again i barely use X. i'm always in the console.

[j79zlr]

Slack is really only marginally harder to setup than say RH. It just doesn't have a pretty GUI, it has a text menu. You have to partition yourself, (2 partitions are really not that hard).

AS for the main topic, what do you mean you forgot your IP, gateway info, and why would have to reinstall because of that?

[pickarooney]

I've only got one PC, and can't afford to have it offline for very long (a day or two max).
I'm not sure if it would give me any real advantage, apart from the learning experience. I'd gladly do it if I had a test machine of some sort... probably best I leave well enough alone for now.

[JohnT]

Originally posted by j79zlr
Slack is really only marginally harder to setup than say RH. It just doesn't have a pretty GUI, it has a text menu. You have to partition yourself, (2 partitions are really not that hard).

AS for the main topic, what do you mean you forgot your IP, gateway info, and why would have to reinstall because of that?

I agree.
Write those things down for reference or call your ISP.
BTW, I find Slackware easier to setup and configure than any other distro I've tried......the only prerequisite is the ability to read.

[pvd212]

i totally agree with you >installing slack is not hard at all .the only thing that i have truble with is my sound card. i just cant get my sound blaster live5.1 to work

i needed my ip gateway and dns to run >netconfig
but i already got it and i am runing slackware9.1 thanks to the help i got here :D

[JohnT]

i just cant get my sound blaster live5.1 to work

http://www.alsa-project.org/alsa-doc/index.php3?vendor=vendor-Creative_Labs#matrix

[FiRe_G0D]

Originally posted by pvd212
i just cant get my sound blaster live5.1 to work

Slack has SB Live drivers. You just need to uncomment the following line in ur /etc/rc.d/rc.modules file:

/sbin/modprobe emu10k1

[pvd212]

if i up my kernel from 2.4 to 2.6 then my sound card should work right >?:confused: :confused:

[voidinit]

Finally! I got a hold of another box (P233MMX/256MB RAM) to hold my www server, jboss server, mysql server, named (bind) server, and dhcpd (isc dhcp) server.

Slack is like the next best thing to LFS if you want to learn. I installed disk set a, ap, tcl, t, l, some of n and some of d. All the rest I did by hand....compiling on another box and copying the finished work over.

Next box is going to be LFS. The ulitmate learning experiece. I feel I'm ready. All thanks to slack.

[JohnT]

voidinit
Next box is going to be LFS. The ulitmate learning experiece.

More like the wait until it compiles for the next 24 hours experience. I left it on a box for about 48 hours after installing and moved on to something else. Don't install a gui and you can halve that time. IMHO its only an exercise and not much of one.

[JohnT]

Originally posted by pvd212
if i up my kernel from 2.4 to 2.6 then my sound card should work right >?:confused: :confused:


That would be the radical approach, since you already have alsa, if your using Slack 9.0-Current.

[pvd212]

i have been wanting to up my kernel for sometime now, i think ill use this as in excuse so that i have to. but i have never secssesfuly up my kernel because of one part. when you type>> make menuconfig << and i get a to pick my Linux kernel menu system. i don't know what to enable and what not is there some were i can go>to get a liste of what has to be enabled*:confused:

[JohnT]

Originally posted by pvd212
i have been wanting to up my kernel for sometime now, i think ill use this as in excuse so that i have to. but i have never secssesfuly up my kernel because of one part. when you type>> make menuconfig << and i get a to pick my Linux kernel menu system. i don't know what to enable and what not is there some were i can go>to get a liste of what has to be enabled*:confused:

Unless you have some unusual requirements you could just use the configs for a bare.i kernel to start with. Use "xconfig" and load up those configs. You can fine tune from there. They're on your Slack cd. I wouldn't use them if contemplating moving to the 2.6 though as I understand it does things a bit different. I personally will stay with my 2.4.20 as its optimized for my box and its my understanding by some copious investigation the 2.6 is only added-value if your running a server.I'm not talking about a local net server.:p . The 2.7 is the next one for the desktop...look for releases this fall.



Wim Coekaerts, director of Linux engineering for Oracle Corp., of Redwood Shores, Calif., told eWEEK: "The 2.6 kernel is a server release, so we can expect to see a greater desktop focus,(in the 2.7) which will be beneficial to us, as more users will be able to use Linux to run their clients really well."

On the server side, there are a lot of patches that will be merged into the 2.6 kernel or move into 2.7, Coekaerts said.

http://www.eweek.com/article2/0,4149,1465884,00.asp

[pvd212]

ill stay with 2.4

[JohnT]

You could always try optimizing what you have, but I have always believed .."If it ain't broke, don't fix it", but kernel optimization is a personal choice. The Slack bare.i kernel, as it comes is a decent set-up for most. I reconfigured mine for my processor (Athlon) and dropped modules I didn't need, but sometimes it is to a small advantage to do so.

[pvd212]

"JohnT:You could always try optimizing what you have, but I have always believed .."If it ain't broke, don't fix it", but kernel optimization is a personal choice. The Slack bare.i kernel, as it comes is a decent set-up for most. I reconfigured mine for my processor (Athlon) and dropped modules I didn't need, but sometimes it is to a small advantage to do so."

I also have a Athlon, is thier someware i go to learn how to optimiz my kernel>?