Slackware This Forum is for the discussion of Slackware Linux.
|
| Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
 |
GNU/Linux Basic Guide
This 255-page guide will provide you with the keys to understand the philosophy of free software, teach you how to use and handle it, and give you the tools required to move easily in the world of GNU/Linux. Many users and administrators will be taking their first steps with this GNU/Linux Basic guide and it will show you how to approach and solve the problems you encounter.
Click Here to receive this Complete Guide absolutely free. |
|
 |
|
06-11-2008, 04:05 AM
|
#301
|
|
Member
Registered: Oct 2007
Distribution: Slackware current
Posts: 136
Rep:
|
Cannot agree more
Quote:
Originally Posted by Alien_Hominid
I'd prefer some sort of Slackware Bible (like Ubuntu Bible) or smth.
|
Yes, that would be terrific. However, I think it is a bit challenging. I guess the first thing to do is to add an easy to find text explaining what the groups created by the installer are for. I see many bugs in Slackware reviews caused by not including a regular user to some group. Possibly that should even be in the mail the installer sends to root.
|
|
|
|
06-11-2008, 04:29 AM
|
#302
|
|
Member
Registered: Oct 2007
Distribution: Slackware current
Posts: 136
Rep:
|
Quote:
Originally Posted by shadowsnipes
That's here, and it's clearly linked from the Support page.
Sure the website doesn't boast eyecandy, but then again I highly doubt anyone will first try Slackware because they are looking for something pretty.
|
I guess you spotted a web site problem. The site does not explain why anyone should try Slackware. An official list of design goals will help to get rid of some confusion. Example: "bla-bla no dependency tracking in packages bla" - "Please refer to the design goal #X".
|
|
|
|
06-11-2008, 08:09 AM
|
#303
|
|
Senior Member
Registered: Mar 2004
Location: Prince Rupert, B.C., Canada
Distribution: Slackware, OpenBSD
Posts: 3,681
|
Quote:
Originally Posted by AGer
I see many bugs in Slackware reviews caused by not including a regular user to some group. Possibly that should even be in the mail the installer sends to root.
|
That issue is dealt with in the 12.1 ncurses installer. You are prompted to add your regular user to plugdev, cdrom, audio, video, and floppy during the set-up of a user account. All you need to do is hit the up arrow button. This is not a Slackware problem, but, a failure to read during the installation procedure.
|
|
|
|
06-11-2008, 09:16 AM
|
#304
|
|
Senior Member
Registered: Sep 2005
Distribution: Slackware
Posts: 1,439
Original Poster
Rep:
|
Quote:
Originally Posted by AGer
I guess you spotted a web site problem. The site does not explain why anyone should try Slackware. An official list of design goals will help to get rid of some confusion. Example: "bla-bla no dependency tracking in packages bla" - "Please refer to the design goal #X".
|
Agreed. Too many people look at Slackware and say something is wrong with it because they don't agree with or understand the design goals. It's like complaining a bicycle has no motor. A tool used out of its specifications will almost always be found to be undesirable.
|
|
|
|
06-12-2008, 05:55 AM
|
#305
|
|
LQ Newbie
Registered: Sep 2006
Location: /home/febrian/
Distribution: SLACKWARE Current, KDE 3.5.9, JFS on Thinkpad R61
Posts: 24
Rep:
|
Can pat replace Kwifi manager with wirelessassistant ?
|
|
|
|
06-12-2008, 08:12 AM
|
#306
|
|
LQ Newbie
Registered: Mar 2005
Location: Romania
Distribution: UBUNTU Hoary, SuSE 9.3, slack 10.1
Posts: 19
Rep:
|
LUKS encrypted partitions support right in the installer, so it could be installed with an encrypted home partition and swap?
|
|
|
|
06-12-2008, 09:56 AM
|
#307
|
|
Senior Member
Registered: Sep 2005
Distribution: Slackware
Posts: 1,439
Original Poster
Rep:
|
Quote:
Originally Posted by febriansasi
Can pat replace Kwifi manager with wirelessassistant ?
|
Kwifi manager is a part of the kdenetwork package, so it is very unlikely it will get removed.
wirelessassistant could be added, but I don't know if it is considered stable enough yet. I know some of wireless tools out there are not considered stable enough for Slackware.
|
|
|
|
06-12-2008, 06:01 PM
|
#308
|
|
Slackware Contributor
Registered: Sep 2005
Location: Eindhoven, The Netherlands
Distribution: Slackware
Posts: 4,731
Rep: 
|
Quote:
Originally Posted by Beranger
LUKS encrypted partitions support right in the installer, so it could be installed with an encrypted home partition and swap?
|
You can already do that. Read the README_CRYPT.TXT.
Eric
|
|
|
|
12-18-2008, 10:30 AM
|
#309
|
|
Senior Member
Registered: Mar 2004
Location: Middx UK
Distribution: Slackware64 14.0 (multilib)
Posts: 1,165
Rep:
|
A script to generate initrd.gz as part of the installation might be nice. After all the installer should 'know' what it needs to generate the file. I know it is not that difficult to read the Readme file and run the command but I often seem to type it wrong and it is one of those niggly little things that would make the installation more user friendly.
Last edited by arubin; 12-18-2008 at 01:29 PM.
Reason: spelling error
|
|
|
|
12-18-2008, 01:04 PM
|
#310
|
|
Slackware Contributor
Registered: Sep 2005
Location: Eindhoven, The Netherlands
Distribution: Slackware
Posts: 4,731
Rep: 
|
Just wait...
|
|
|
|
12-18-2008, 01:09 PM
|
#311
|
|
Member
Registered: Mar 2002
Location: 127.0.0.1
Distribution: Slackware, OpenBSD, FreeBSD
Posts: 638
Rep: 
|
/me wonders if Eric's mkinitrd_command_generator.sh script will be reborn ...
|
|
|
|
12-18-2008, 01:12 PM
|
#312
|
|
Senior Member
Registered: Oct 2005
Location: Lithuania
Distribution: Hybrid
Posts: 2,247
Rep:
|
As I said year ago updated Slackbook with important hal, udev, disk naming stuff, etc...
|
|
|
|
12-18-2008, 02:19 PM
|
#313
|
|
LQ 5k Club
Registered: Jan 2006
Location: Oldham, Lancs, England
Distribution: Laptop: Slackware 14.0 // Desktop: Slackware64 14.0 // Netbook: Slackware 14.0
Posts: 6,196
|
Quote:
Originally Posted by chess
/me wonders if Eric's mkinitrd_command_generator.sh script will be reborn ...
|
I didn't know it had died. 
|
|
|
|
12-18-2008, 04:22 PM
|
#314
|
|
Senior Member
Registered: Jan 2008
Location: Urbana IL
Distribution: Slackware, Pclinux, Mandriva, Kubuntu 10.10 Slck13_64-current
Posts: 2,040
Rep: 
|
I need more Cow Bell More !!!!. Thats what I need in slackware 12.2. The fact that there is know dependency program is the best thing that ever could be. and only people that understand how them rpm pacakges and deb pakages are made would agree also. just down load a deviant rpm or deb package and you have the time of your life. you may get 1000 extra libraries that will only hurt stuff you do use. trust me I spend many hours going over bad packages and I wish people would learn to type ./configure.
I need more ubuntu disks to set my coffee cup on little higher please.
Ding Ding
Last edited by Drakeo; 12-18-2008 at 04:29 PM.
|
|
|
|
12-18-2008, 06:28 PM
|
#315
|
|
Slackware Contributor
Registered: Sep 2005
Location: Eindhoven, The Netherlands
Distribution: Slackware
Posts: 4,731
Rep: 
|
Quote:
|
Originally Posted by chess
/me wonders if Eric's mkinitrd_command_generator.sh script will be reborn ...
|
Quote:
Originally Posted by brianL
I didn't know it had died. 
|
No, I jut uploaded an updated version - PiterPUNK improved the storage hardware detection (for some computers including my T41 laptop the command would list an absurd collection of required modules).
My test-installer has this script embedded and liloconfig will use it. But it still has a lot of wrinkles that need to be ironed out...
Eric
|
|
|
|
| Thread Tools |
Search this Thread |
|
|
|
Posting Rules
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is Off
|
|
|
All times are GMT -5. The time now is 11:23 PM.
|
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|