LinuxQuestions.org
Share your knowledge at the LQ Wiki.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices

Reply
 
Search this Thread
Old 06-15-2010, 05:18 AM   #136
Didier Spaier
Senior Member
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slackware{,64}-{14.1,current} on a Lenovo Thinkpad T61 6457-4XG
Posts: 4,522

Rep: Reputation: 1186Reputation: 1186Reputation: 1186Reputation: 1186Reputation: 1186Reputation: 1186Reputation: 1186Reputation: 1186Reputation: 1186

@H_TeXMeX_H: Seems like a "dialogue de sourds" as we say in French. OK, let's say it's my fault as I speak and write English poorly. Case closed on my side.

Last edited by Didier Spaier; 06-15-2010 at 05:19 AM.
 
Old 06-15-2010, 08:31 AM   #137
onebuck
Moderator
 
Registered: Jan 2005
Location: Midwest USA, Central Illinois
Distribution: SlackwareŽ
Posts: 11,381
Blog Entries: 3

Rep: Reputation: 1478Reputation: 1478Reputation: 1478Reputation: 1478Reputation: 1478Reputation: 1478Reputation: 1478Reputation: 1478Reputation: 1478Reputation: 1478
What I like about Slackware!

Hi,

I'm going to flip this as a lot of users seem to miss a lot by not reading the great documentation that is provided for the Slackware install. If everyone would follow the lead from the docs then a lot of problems would be alleviated. Most of the problems that I notice here on LQ would be not sticking their heads up if the OP had just read a doc such as: 'CHANGES_AND_HINTS.TXT' or associative text files.

Another big problem is that most users default to the huge kernel when PV & Team suggestion is to use the generic kernel for daily use with a initrd. Which if the user reads the suggested file '/boot/README.initrd' to know how to implement thus having a bootable system. I could continue with examples but it would be better for everyone that is interested to peruse the Slackware Forum.

I do like the idea or philosophy behind Slackware of open information and functionality! Not hidden nor is it difficult to learn how things are implemented. OPEN!

My point is 'RTFM' or 'RTFD' that are available to assist in the Slackware venture to hopefully have a working Slackware system without too much effort. But when you have a problem then be sure to post it with relative information to the Slackware Forum.

So I guess that my 'something that you do not like about slackware' is that a lot of new users don't prepare themselves for a new install. There are responsibilities on everyone to know what's necessary to have a good functioning system. Again 'I don't wanna hold your hand'... What's the next chord or is that chorus? I gotta read the sheet when I can find it!

 
1 members found this post helpful.
Old 06-15-2010, 09:04 AM   #138
SpelledJ
Member
 
Registered: Jun 2006
Location: Birmingham, AL
Distribution: Slackware64-13.1, 12.1
Posts: 119

Rep: Reputation: 20
Quote:
Originally Posted by tallship View Post
So you would have a -generic-xfs, a -generic-ext2, a -generic-reiserfs, etc., right?

But I often use an ext2 /boot and the rest as xfs - it was bad enough when I had to load support for xfs from a floppy.

Dude, that's going backwards. Really.
Sigh. No, one -generic, one default filesystem. Not using the default filesystem? Build an initrd, exactly like you have to now. Using more than one filesystem? Build an initrd, exactly like you have to now.

Don't care to get fancy with the filesystems? One filesystem for everything fine? Then you wouldn't have to fool with mkinitrd.
 
Old 06-15-2010, 09:23 AM   #139
2handband
Member
 
Registered: Jan 2009
Location: Alexandria, Minnesota
Distribution: Slackware 13.1
Posts: 809

Rep: Reputation: 96
Quote:
Originally Posted by kevmccor View Post
I have used Slackware for quite a while. Obviously, I like it. There are some occasional annoyances. Right now, my /tmp directory is full of cr*p and I can't find anything other than $rm -rf /tmp/* to deal with it. I guess my continuing complaint is packages accumulating in /tmp. Perhaps SBo could designate some environment variable such as SB0-TMP="~/.tmp" to make it easier for users to keep package collections/history together more easily.

I did find this:

http://packetstormsecurity.nl/linux/...min-FAQ-6.html

Any thoughts on a good script to clean up the /tmp directory?

Thanks
Add the following line to /etc/rc.d/rc.6:

Code:
rm -rf /tmp/*
Make sure you put it in before the filesystem unmounts. Works for me.

As for whoever was complaining about Nvidia drivers, the packages at Slackbuilds.org work fine. I installed Slackware for the very first time early last week and had 3D acceleration working within 30 minutes of booting up.

Complaints about Slackware? I have one. I don't like the full install. Yes, I know, disc space is cheap and I have a lot of it... but I like simple, clean menus that aren't chock-full of applications I don't use.
Other than that i think Slack is pretty much flawless... and I've only been using it for a little over a week.
 
Old 06-15-2010, 09:33 AM   #140
onebuck
Moderator
 
Registered: Jan 2005
Location: Midwest USA, Central Illinois
Distribution: SlackwareŽ
Posts: 11,381
Blog Entries: 3

Rep: Reputation: 1478Reputation: 1478Reputation: 1478Reputation: 1478Reputation: 1478Reputation: 1478Reputation: 1478Reputation: 1478Reputation: 1478Reputation: 1478
Hi,

Quote:
Originally Posted by 2handband View Post
<snip>

Complaints about Slackware? I have one. I don't like the full install. Yes, I know, disc space is cheap and I have a lot of it... but I like simple, clean menus that aren't chock-full of applications I don't use.
Other than that i think Slack is pretty much flawless... and I've only been using it for a little over a week.
You have the option to tag it. Or do a minimal and add to suit your install. I agree that a full install may cause the lose of time but a recommended install type for a new user. Plus the Slackware distribution is used world wide to multiple user types. So some people wants are totally different than others. I think PV & Team do a wonderful balanced install and a good methodology to allow user selections.

 
Old 06-15-2010, 09:33 AM   #141
hitest
Senior Member
 
Registered: Mar 2004
Location: Prince Rupert, B.C., Canada
Distribution: Slackware, OpenBSD
Posts: 4,241

Rep: Reputation: 570Reputation: 570Reputation: 570Reputation: 570Reputation: 570Reputation: 570
Quote:
Originally Posted by 2handband View Post
Complaints about Slackware? I have one. I don't like the full install. Yes, I know, disc space is cheap and I have a lot of it... but I like simple, clean menus that aren't chock-full of applications I don't use.
Other than that i think Slack is pretty much flawless... and I've only been using it for a little over a week.
Welcome to our forum!
I'm happy to hear you like Slackware. I was a Debian user before (nice distro). Now that Slackware is up and running you could use pkgtool to remove the applications that you never use.

# pkgtool
 
Old 06-15-2010, 09:40 AM   #142
linus72
Guru
 
Registered: Jan 2009
Location: Gordonsville-AKA Mayberry-Virginia
Distribution: PocketWriter/MinimalX
Posts: 5,084

Rep: Reputation: 336Reputation: 336Reputation: 336Reputation: 336
2handband;
there are so many options with Slackware, the most simplistic (perfect) distro ever.
Tagfiles

thats the key to any minimal reproducable slack install
tagfiles

http://www.bilbos-stekkie.com/tagger/tagfiles.html

http://www.flaterco.com/kb/slackware.html

http://www.slackbook.org/html/packag...-tagfiles.html

http://chelskov.org/node/4

http://connie.slackware.com/~alien/tools/tagfiles/

http://mysticalgr.awardspace.com/?p=353&page=2

EDIT: LOL why did it doublepost?

Last edited by linus72; 06-15-2010 at 09:41 AM.
 
Old 06-15-2010, 09:40 AM   #143
linus72
Guru
 
Registered: Jan 2009
Location: Gordonsville-AKA Mayberry-Virginia
Distribution: PocketWriter/MinimalX
Posts: 5,084

Rep: Reputation: 336Reputation: 336Reputation: 336Reputation: 336
2handband;
there are so many options with Slackware, the most simplistic (perfect) distro ever.
Tagfiles

thats the key to any minimal reproducable slack install
tagfiles

http://www.bilbos-stekkie.com/tagger/tagfiles.html

http://www.flaterco.com/kb/slackware.html

http://www.slackbook.org/html/packag...-tagfiles.html

http://chelskov.org/node/4

http://connie.slackware.com/~alien/tools/tagfiles/

http://mysticalgr.awardspace.com/?p=353&page=2
 
Old 06-15-2010, 09:41 AM   #144
2handband
Member
 
Registered: Jan 2009
Location: Alexandria, Minnesota
Distribution: Slackware 13.1
Posts: 809

Rep: Reputation: 96
Quote:
Originally Posted by hitest View Post
Welcome to our forum!
I'm happy to hear you like Slackware. I was a Debian user before (nice distro). Now that Slackware is up and running you could use pkgtool to remove the applications that you never use.

# pkgtool
That's what I've been doing. Next time I do a Slackware install (I'm going to slowly migrate the rest of the computers in the house from Debian to Slack) I'll cherry-pick through the packages... I had no idea it was going to install so much stuff. I've got this one cleaned out pretty good at this point; I've probably got some orphaned libraries lying around but whatever. Glad to be here!
 
Old 06-15-2010, 10:14 AM   #145
Richard Cranium
Senior Member
 
Registered: Apr 2009
Location: Carrollton, Texas
Distribution: Slackware64 14.1
Posts: 1,566

Rep: Reputation: 462Reputation: 462Reputation: 462Reputation: 462Reputation: 462
Quote:
Originally Posted by SpelledJ View Post
Sigh. No, one -generic, one default filesystem. Not using the default filesystem? Build an initrd, exactly like you have to now. Using more than one filesystem? Build an initrd, exactly like you have to now.

Don't care to get fancy with the filesystems? One filesystem for everything fine? Then you wouldn't have to fool with mkinitrd.
Actually, the installer already should know what filesystems you intend to use for your partitions. It asks you fairly early in the process.

How many disk drive controllers are you going to build into the generic image? The installer doesn't know about that.

I think you'll end up with what we already have: a kernel with everything in it so that you can do an initial install and a generic kernel with the bare minimum to boot with which you use an initrd.

Unless someone can write a script that would troll through /sys to figure out what minimum set of modules should be loaded by initrd to allow you to boot into runlevel 3.
 
Old 06-15-2010, 10:26 AM   #146
Alien Bob
Slackware Contributor
 
Registered: Sep 2005
Location: Eindhoven, The Netherlands
Distribution: Slackware
Posts: 5,332

Rep: Reputation: Disabled
Quote:
Originally Posted by Richard Cranium View Post
Unless someone can write a script that would troll through /sys to figure out what minimum set of modules should be loaded by initrd to allow you to boot into runlevel 3.
The script /usr/share/mkinitrd/mkinitrd_command_generator.sh does just that.

Eric
 
Old 06-15-2010, 12:00 PM   #147
mlangdn
Senior Member
 
Registered: Mar 2005
Location: Kentucky
Distribution: Slackware64-current
Posts: 1,380

Rep: Reputation: 180Reputation: 180
I use the huge kernel for a first boot on a clean install, then I compile a custom kernel before all else. Today, I compiled 2.6.34 and that replaced 2.6.32. Compiling kernels is getting very complex with each new release, and I am no kernel expert.

Also today, I experimented with an initrd on the stock generic kernel. It worked just fine, but it was a bit slower to boot than my kernel. That said, we are only talking about ~10 seconds. Later, when I have more time, I am going to give the above script a run and see what happens. Curiosity killed the cat!

The generic kernel is about 2.4mb and my kernel is about 1.9mb. Not a big difference anymore.
 
Old 06-15-2010, 03:55 PM   #148
Richard Cranium
Senior Member
 
Registered: Apr 2009
Location: Carrollton, Texas
Distribution: Slackware64 14.1
Posts: 1,566

Rep: Reputation: 462Reputation: 462Reputation: 462Reputation: 462Reputation: 462
Quote:
Originally Posted by Alien Bob View Post
The script /usr/share/mkinitrd/mkinitrd_command_generator.sh does just that.

Eric
Cool. Does the installer ask if you want to run this? (I haven't done a full install in quite a while.)

For that matter, why isn't this in root's standard path? It Would Be Nice (TM) if tab-completion of "mkinitrd" offered "mkinitrd_command_generator.sh" as a possible completion.
 
Old 06-15-2010, 04:06 PM   #149
2handband
Member
 
Registered: Jan 2009
Location: Alexandria, Minnesota
Distribution: Slackware 13.1
Posts: 809

Rep: Reputation: 96
Okay, another issue... it was a mistake to package Firefox 3.6. It's crash-prone. I'm going to remove it and install 3.5.
 
Old 06-15-2010, 04:10 PM   #150
Alien Bob
Slackware Contributor
 
Registered: Sep 2005
Location: Eindhoven, The Netherlands
Distribution: Slackware
Posts: 5,332

Rep: Reputation: Disabled
Quote:
Originally Posted by Richard Cranium View Post
Cool. Does the installer ask if you want to run this? (I haven't done a full install in quite a while.)
No, but internally, the team had this working end of 2008 already. It's just never gone public.

Quote:
For that matter, why isn't this in root's standard path? It Would Be Nice (TM) if tab-completion of "mkinitrd" offered "mkinitrd_command_generator.sh" as a possible completion.
Not everything needs to be that obvious. Reading documentation in the Slackware DVD's root-directory is what reveals the existence of this script.

Eric
 
  


Reply

Tags
awesome, feedback missing, fud, slackware, slackware64, slackwarecurrent


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Post Slackware distros Tylerious Linux - Distributions 15 02-16-2006 07:12 PM
slackware post install nicole_jeff Slackware 2 05-23-2004 07:06 AM


All times are GMT -5. The time now is 01:08 PM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration