Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations bkrike on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
3dfx, glide and banshee stuff
- Thread starter zanza
- Start date
I was a big Slackware user, but now I use Debian. I swear, it seems that Slackware is Debian without package management (heh, if you call .tar.gz management). All those problems with libs are gone with apt-get.
Last, if you can survive a Slack install , you can brave the Debian install/configure ;-)
Last, if you can survive a Slack install , you can brave the Debian install/configure ;-)
- Thread starter
- #3
well cool. i may indeed go look into debian. before i found the slack howto on the slackware site, i would create a log file of the packages i installed, just so i might be able to uninstall them later.
speaking of which... are there any "official" debain book thingys? žÅNžÅ
speaking of which... are there any "official" debain book thingys? žÅNžÅ
---i would create a log file of the packages i installed, just so i might be able to uninstall them later.
Why do that? if you install a slack tar.gz , the packager can take care of it. It's when you're compiling all sorts of stuff for it when you get into problems. Then again, if you compile a bunch of stuff on it, you ought to keep the directory so you can make clean it from your system.
---speaking of which... are there any "official" debain book thingys?
I'm confused.. Book thingys? Do you mean install help? It has a nice verbose install. It's kinda scary at first, as you configure your modules (as a list) for your /etc/modules.conf file. But that's about as hard as you get.
Why do that? if you install a slack tar.gz , the packager can take care of it. It's when you're compiling all sorts of stuff for it when you get into problems. Then again, if you compile a bunch of stuff on it, you ought to keep the directory so you can make clean it from your system.
---speaking of which... are there any "official" debain book thingys?
I'm confused.. Book thingys? Do you mean install help? It has a nice verbose install. It's kinda scary at first, as you configure your modules (as a list) for your /etc/modules.conf file. But that's about as hard as you get.
- Thread starter
- #5
Sorry for using tired person dialect. ^_^
that kind of book is what im talking about. that thing helped make slackware do-able for a newbie žÅNžÅ
that kind of book is what im talking about. that thing helped make slackware do-able for a newbie žÅNžÅ
I took a look at that, and most of all applies to debian. There are a few subjects that are different.
1: APT - apt and dpkg are the package managers. if you do a apt-get , you will see the basic commands. To install, say KDE under stable, you just do apt-get install kde . It then installs using the required source (that being cd's, packages already on your computer, or getting it from the archives on the net). Removing is the similar process.
With Debian's upgrade cycles, there's 3 branches. Stable, Testing, and unstable. Depending what you put in your /etc/apt/sources.conf , is what branch you use. I'm using stable on one computer and testing on the other. Stable.. NEVER crashes, but not current at all. Testing has a bit of bugs in it, but still is very current. Unstable is exactly that. In order to stay up to date with this line, you MUST do a
apt-get update & apt-get dist-upgrade
Every day (or less). Stay out of it.
2: The starting and stopping of servers. It's a lot easier in Debian than it is Slackware. In slack, you just shoved it in rc.local (right) or the direct runlevel of the boot sequence. You could also put it in inetd. In debian, things are a lot cleaner in that regard. There still is inetd, but we only use them for the very common services.For everything else, we put the startup file in /etc/rc(runlevel).d where runlevel is what you're running at (runlevel is actually a command too, use it to see). I'm usually in rc2 so I go in /etc/rc2.d/ . Now you see files. Those are actually scripts. Try to run one:
comp1:/etc/rc2.d# ./S20inetd
Usage: /etc/init.d/inetd {start|stop|reload|restart}
comp1:/etc/rc2.d# ./S20inetd stop
Stopping internet superserver: inetd.
comp1:/etc/rc2.d#
See how that works? YOu just call trhe script and poass it start, stop,... and it does exactly that.
Still, overall, if you've been using linux in general, Debian should be OK.
1: APT - apt and dpkg are the package managers. if you do a apt-get , you will see the basic commands. To install, say KDE under stable, you just do apt-get install kde . It then installs using the required source (that being cd's, packages already on your computer, or getting it from the archives on the net). Removing is the similar process.
With Debian's upgrade cycles, there's 3 branches. Stable, Testing, and unstable. Depending what you put in your /etc/apt/sources.conf , is what branch you use. I'm using stable on one computer and testing on the other. Stable.. NEVER crashes, but not current at all. Testing has a bit of bugs in it, but still is very current. Unstable is exactly that. In order to stay up to date with this line, you MUST do a
apt-get update & apt-get dist-upgrade
Every day (or less). Stay out of it.
2: The starting and stopping of servers. It's a lot easier in Debian than it is Slackware. In slack, you just shoved it in rc.local (right) or the direct runlevel of the boot sequence. You could also put it in inetd. In debian, things are a lot cleaner in that regard. There still is inetd, but we only use them for the very common services.For everything else, we put the startup file in /etc/rc(runlevel).d where runlevel is what you're running at (runlevel is actually a command too, use it to see). I'm usually in rc2 so I go in /etc/rc2.d/ . Now you see files. Those are actually scripts. Try to run one:
comp1:/etc/rc2.d# ./S20inetd
Usage: /etc/init.d/inetd {start|stop|reload|restart}
comp1:/etc/rc2.d# ./S20inetd stop
Stopping internet superserver: inetd.
comp1:/etc/rc2.d#
See how that works? YOu just call trhe script and poass it start, stop,... and it does exactly that.
Still, overall, if you've been using linux in general, Debian should be OK.
- Thread starter
- #7
žÅNžÅ- Status
Similar threads
