LinuxQuestions.org
Review your favorite Linux distribution.
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 07-15-2004, 05:10 AM   #1
slacka
LQ Newbie
 
Registered: Jul 2004
Location: Chico, CA
Distribution: Slackware 10
Posts: 21

Rep: Reputation: 15
dircolors: No such file or directory


I'm using Slack 10 and kernel 2.4.26. When I start Konsole in KDE, the first thing that appears is "dircolors: No such file or directory." Also, ls does not display any colors. I know that dircolors is in the /bin directory, but when I try to execute it I always get this error. What's the deal?
 
Old 07-15-2004, 06:50 AM   #2
SciYro
Senior Member
 
Registered: Oct 2003
Location: hopefully not here
Distribution: Gentoo
Posts: 2,038

Rep: Reputation: 51
maybe its corrupted?
 
Old 07-15-2004, 09:10 AM   #3
jong357
Senior Member
 
Registered: May 2003
Location: Columbus, OH
Distribution: DIYSlackware
Posts: 1,914

Rep: Reputation: 52
You need a file in /etc thats called 'DIR_COLORS' as well. Check for that. Try THIS as well... Theres a read me in it. That should fix it.
 
Old 07-15-2004, 09:18 AM   #4
keefaz
LQ Guru
 
Registered: Mar 2004
Distribution: Slackware
Posts: 5,449

Rep: Reputation: 420Reputation: 420Reputation: 420Reputation: 420Reputation: 420
Hey, following your link and after a little browsing, I see a slackware package for GRUB, good job
 
Old 07-15-2004, 10:02 AM   #5
Bruce Hill
HCL Maintainer
 
Registered: Jun 2003
Location: McCalla, AL, USA
Distribution: Fedora, Gentoo, Ubuntu (all servers at work are openSUSE)
Posts: 6,931

Rep: Reputation: 128Reputation: 128
Quote:
Originally posted by jong357
You need a file in /etc thats called 'DIR_COLORS' as well. Check for that. Try THIS as well... Theres a read me in it. That should fix it.
I went to your "online treasure chest" and did the
upgradepkg coreutils-5.2.1-i486-2.tgz

Results before:
bash-2.05b$ uname -a
Linux paul 2.4.26 #6 Mon Jun 14 19:07:27 PDT 2004 i686 unknown unknown GNU/Linux
Results after:
bash-2.05b$ uname -a
bash: /usr/bin/uname: No such file or directory

So now what do you suggest?
 
Old 07-15-2004, 03:20 PM   #6
jong357
Senior Member
 
Registered: May 2003
Location: Columbus, OH
Distribution: DIYSlackware
Posts: 1,914

Rep: Reputation: 52
Yea... Got your e-mail... I really have a sneaking suspicion that you did a removepkg and then installpkg instead of upgradepkg. You say you didn't but.... I don't know. It works every time for me when ever I use it... I'm going to louse my computer up in the same way and then come up with a fix. Actually, I've done that before. It IS easy to fix.

In the future tho, thats like downloading Joe-Shmoe's "C:\Program Files\Windows\System 32" replacement package and then crossing your fingers I suppose... Because that's pretty much what it does... Delete all of your "Windows\System 32" directory and then replace it with newer files....

Aww man... The guilt trip.... I specifically gave a disclaimer and offered the source code patch. I honestly thought no one would ever use that thing in a million years besides myself.... Hold on....
 
Old 07-15-2004, 04:06 PM   #7
jong357
Senior Member
 
Registered: May 2003
Location: Columbus, OH
Distribution: DIYSlackware
Posts: 1,914

Rep: Reputation: 52
Hee, Hee.... What fun... I love purposefully screwing up your system.... It's the only way I get any excitement anymore for the most part.... OK.... I tried to do an "upgradepkg" first but it said it was already installed. And, once again, I tell you, I use that package all the time with no ill effects so I have no idea what happened to you...

[root@darkstar /] removepkg coreutils-5.2.1-i486-2.tgz

Removing package /var/log/packages/coreutils-5.2.1-i486-2...
Removing files:
--> Deleting symlink //usr/bin/cat
--> Deleting symlink //usr/bin/chgrp
--> Deleting symlink //usr/bin/chmod
--> Deleting symlink //usr/bin/chown
--> Deleting symlink //usr/bin/cp
--> Deleting symlink //usr/bin/cut
--> Deleting symlink //usr/bin/date
--> Deleting symlink //usr/bin/dd
BLAH,BLAH,BLAH forever and ever....

O.k.. Once we get further along we create a paradox for ourselves. pkgtool tries to execute commands it just removed...

--> Deleting /bin/rm
--> Deleting /bin/rmdir
/sbin/removepkg: line 149: rm: command not found
--> Deleting /bin/shred

Just for kicks... I expected this..

[root@darkstar /] upgradepkg coreutils-5.2.1-i486-2.tgz
/sbin/upgradepkg: line 1: cut: command not found
/sbin/upgradepkg: line 1: cut: command not found
dirname: too few arguments
Try `dirname --help' for more information.
/sbin/upgradepkg: line 1: cut: command not found
/sbin/upgradepkg: line 1: cut: command not found

Error: there is no installed package named .tgz.
(looking for /var/log/packages/.tgz)

This 'uname' command was slightly strange.. It still worked...

[root@darkstar /] ls
bash: ls: command not found
[root@darkstar /] uname -a
Linux darkstar 2.4.26 #2 SMP Mon Jul 12 03:43:42 EDT 2004 i686 Intel(R) Pentium(R) 4 CPU 3.00GHz GenuineIntel GNU/Linux
[root@darkstar /] cat
bash: cat: command not found

This is kind of interesting what comes next.... We still have a paradox with pkgtool trying to use commands it just removed

[root@darkstar /] installpkg coreutils-5.2.1-i486-2.tgz
/sbin/installpkg: line 1: cut: command not found
/sbin/installpkg: line 1: cut: command not found
/sbin/installpkg: line 285: mkdir: command not found
/sbin/installpkg: line 1: cut: command not found
/sbin/installpkg: line 1: cut: command not found
expr: syntax error
expr: syntax error
/sbin/installpkg: line 317: cat: command not found
/sbin/installpkg: line 317: cut: command not found
/sbin/installpkg: line 1: cat: command not found
/sbin/installpkg: line 330: cat: command not found
/sbin/installpkg: line 346: rm: command not found
/sbin/installpkg: line 347: mv: command not found
Installing package coreutils-5.2.1-i486-2...
PACKAGE DESCRIPTION:
/sbin/installpkg: line 356: cat: command not found
/sbin/installpkg: line 400: cat: command not found
/sbin/installpkg: line 405: rm: command not found
/sbin/installpkg: line 414: cat: command not found
Executing install script for coreutils-5.2.1-i486-2...

It executed the script anyway at the end, so we know some stuff got done, just not all of it..
So I decided to run it again....

[root@darkstar /] uname -a
Linux darkstar 2.4.26 #2 SMP Mon Jul 12 03:43:42 EDT 2004 i686 Intel(R) Pentium(R) 4 CPU 3.00GHz GenuineIntel GNU/Linux

Well, My 'uname' is still working...

[root@darkstar /] installpkg coreutils-5.2.1-i486-2.tgz
Installing package coreutils-5.2.1-i486-2...
PACKAGE DESCRIPTION:
coreutils: coreutils (core GNU utilities)
coreutils:
coreutils: These are the GNU core utilities, the basic command line programs
coreutils: such as 'mkdir', 'ls', and 'rm' that are needed for the system to
coreutils: run. This package is the union of the GNU fileutils, sh-utils, and
coreutils: textutils packages. Most of these programs have significant
coreutils: advantages over their Unix counterparts, such as greater speed,
coreutils: additional options, and fewer arbitrary limits.
coreutils:
Executing install script for coreutils-5.2.1-i486-2...

Well, that looked like everything went over just fine. I assume the first time I tried to install it, some key things got done, which let the second pass go over without a hitch...

[root@darkstar /] ls
. bin coreutils-5.2.1-i486-2.tgz etc lib opt root tmp var
.. boot dev home mnt proc sbin usr
[root@darkstar /] cat /proc/pci
PCI devices found:
Bus 0, device 0, function 0:
Host bridge: Intel Corp. 82875P Memory Controller Hub (rev 2).

Well, Every thing works now... Theres also another approach we can take as well to fix it. I'll uninstall it again....

[root@darkstar /] removepkg coreutils-5.2.1-i486-2.tgz
[root@darkstar /] cp
bash: cp: command not found
[root@darkstar /] mv
bash: mv: command not found

Well, Ok... If we want to do this another way, we have to boot up with our trusty Gentoo or Knoppix live CD, LIKE ALL OF US WELL PREPARED EXPIERENCED LINUX USERS HAVE LYING AROUND, right?

Since our 'mv' or 'cp' command doesn't work we'll have to use either another Linux OS on the same hard drive or a live CD. Mount your slack and copy the package over to your '/' directory of slackware and then do a:

tar -xzf coreutils-5.2.1-i486-2.tgz

In the '/' directory of your slack install...


I placed the package in my '/' directory ahead of time so there would be no need for me to use a live CD... I wonder if using your window manager's copy/paste function would work here? Hmmm...

[root@darkstar /] tar -xzf coreutils-5.2.1-i486-2.tgz
[root@darkstar /] ls
bash: /usr/bin/ls: No such file or directory

Since we just 'extracted' it, the install script didn't get executed. All the files are in place, just not the symlinks that the install script makes..... We also have a directory 'install' to delete in '/'... So now, we install the package with pkgtool... If your using a live CD, obviously, we have to 'chroot' to use pkgtool

[root@darkstar /] installpkg coreutils-5.2.1-i486-2.tgz
Installing package coreutils-5.2.1-i486-2...
PACKAGE DESCRIPTION:
coreutils: coreutils (core GNU utilities)
coreutils:
coreutils: These are the GNU core utilities, the basic command line programs
coreutils: such as 'mkdir', 'ls', and 'rm' that are needed for the system to
coreutils: run. This package is the union of the GNU fileutils, sh-utils, and
coreutils: textutils packages. Most of these programs have significant
coreutils: advantages over their Unix counterparts, such as greater speed,
coreutils: additional options, and fewer arbitrary limits.
coreutils:
Executing install script for coreutils-5.2.1-i486-2...

O.k... Since extracting it put all the files in place except for the symlinks, pkgtool goes off without a hitch again and everything is fine and dandy now...

[root@darkstar /] ls
. bin coreutils-5.2.1-i486-2.tgz etc lib opt root tmp var
.. boot dev home mnt proc sbin usr
[root@darkstar /] mv
mv: missing file argument
Try `mv --help' for more information.
[root@darkstar /] cp
cp: missing file argument
Try `cp --help' for more information.
[root@darkstar /] cat /proc/pci
PCI devices found:
Bus 0, device 0, function 0:
Host bridge: Intel Corp. 82875P Memory Controller Hub (rev 2).
Prefetchable 32 bit memory at 0xe8000000 [0xefffffff].


Theres multiple ways to fix it. All are pretty painless in my opinion... Sorry man..... I don't know what happened to you. Since shit is already loused up, keep trying to use that package.. Couldn't hurt... Or if your gun shy now, just try all this stuff I listed with the original package that comes on your slackware disk...

Looks like I might have to put a "more clear warning" in that readme that's in the same directory as the package you grabbed...

Last edited by jong357; 07-15-2004 at 06:17 PM.
 
Old 07-15-2004, 04:18 PM   #8
keefaz
LQ Guru
 
Registered: Mar 2004
Distribution: Slackware
Posts: 5,449

Rep: Reputation: 420Reputation: 420Reputation: 420Reputation: 420Reputation: 420
Well, you did good job and you said yourself that you did not think that anybody will take the risk to install your coreutils package

In my idea the official coreutils packages will react the same maneer as it contains...core utils
(like rm, cp & friends)
 
Old 07-15-2004, 04:25 PM   #9
jong357
Senior Member
 
Registered: May 2003
Location: Columbus, OH
Distribution: DIYSlackware
Posts: 1,914

Rep: Reputation: 52
It WILL do the same thing.... Thats what happened to me about 7 months ago when I tried to uninstall the "official" package and upgrade to the lastest "official" package.... Thats why I know how to fix it...

Once again.... Sorry China.... I feel bad....

I think it would be cool if as many people tried to install that as possible so I could get an accurate consensus of what is going on... Awww.... Come on..... You guys know you want to.... Pretty please? I just posted a fix. It's no big deal... Takes 10 seconds to fix....

Last edited by jong357; 07-15-2004 at 04:29 PM.
 
Old 07-15-2004, 05:08 PM   #10
thegeekster
Member
 
Registered: Dec 2003
Location: USA (Pacific coast)
Distribution: Vector 5.8-SOHO, FreeBSD 6.2
Posts: 513

Rep: Reputation: 34
Hmmm.............hey, jong, would it help to make a temporary package (such as temputils.tgz) with just the essential coreutils needed by the the Slackware packge tools, placing them in /usr/local/bin................then anyone can upgrade to your coreutils package safely and then remove that temporary package afterwards............Just a thought...
 
Old 07-15-2004, 05:11 PM   #11
jong357
Senior Member
 
Registered: May 2003
Location: Columbus, OH
Distribution: DIYSlackware
Posts: 1,914

Rep: Reputation: 52
Alright.... I can't put this down........ Damn that annoys me.... I did a removepkg on my coreutils and installed the original from the disk. I did a removepkg on the original and reinstalled it again... Don't ask me why... Then I did an upgradepkg from the original to MY package... It worked flawlessly like it always does....

[root@darkstar /] upgradepkg coreutils-5.2.1-i486-2.tgz

+==============================================================================
| Upgrading coreutils-5.2.1-i486-1 package using ./coreutils-5.2.1-i486-2.tgz
+==============================================================================

Pre-installing package coreutils-5.2.1-i486-2...

Removing package /var/log/packages/coreutils-5.2.1-i486-1-upgraded-2004-07-15,17:02:47...
--> Deleting symlink /usr/bin/cat
--> Deleting symlink /usr/bin/chgrp
--> Deleting symlink /usr/bin/chmod
--> Deleting symlink /usr/bin/chown
--> Deleting symlink /usr/bin/cp
--> Deleting symlink /usr/bin/cut
--> Deleting symlink /usr/bin/date
--> Deleting symlink /usr/bin/dd
--> Deleting symlink /usr/bin/df
--> Deleting symlink /usr/bin/dircolors
--> Deleting symlink /usr/bin/du
--> Deleting symlink /usr/bin/echo
--> Deleting symlink /usr/bin/false
--> Deleting symlink /usr/bin/ginstall
--> Deleting symlink /usr/bin/head
--> Deleting symlink /usr/bin/ln
--> Deleting symlink /usr/bin/ls
--> Deleting symlink /usr/bin/mkdir
--> Deleting symlink /usr/bin/mkfifo
--> Deleting symlink /usr/bin/mknod
--> Deleting symlink /usr/bin/mv
--> Deleting symlink /usr/bin/pwd
--> Deleting symlink /usr/bin/rm
--> Deleting symlink /usr/bin/rmdir
--> Deleting symlink /usr/bin/shred
--> Deleting symlink /usr/bin/sleep
--> Deleting symlink /usr/bin/stty
--> Deleting symlink /usr/bin/sync
--> Deleting symlink /usr/bin/touch
--> Deleting symlink /usr/bin/true
--> Deleting symlink /usr/bin/uname
--> Deleting symlink /usr/man/man1/ginstall.1.gz
--> Deleting symlink /usr/sbin/chroot
--> Deleting symlink /usr/share/locale/af/LC_TIME/coreutils.mo
--> Deleting symlink /usr/share/locale/be/LC_TIME/coreutils.mo
--> Deleting symlink /usr/share/locale/ca/LC_TIME/coreutils.mo
--> Deleting symlink /usr/share/locale/cs/LC_TIME/coreutils.mo
--> Deleting symlink /usr/share/locale/da/LC_TIME/coreutils.mo
--> Deleting symlink /usr/share/locale/de/LC_TIME/coreutils.mo
--> Deleting symlink /usr/share/locale/el/LC_TIME/coreutils.mo
--> Deleting symlink /usr/share/locale/es/LC_TIME/coreutils.mo
--> Deleting symlink /usr/share/locale/et/LC_TIME/coreutils.mo
--> Deleting symlink /usr/share/locale/fi/LC_TIME/coreutils.mo
--> Deleting symlink /usr/share/locale/fr/LC_TIME/coreutils.mo
--> Deleting symlink /usr/share/locale/ga/LC_TIME/coreutils.mo
--> Deleting symlink /usr/share/locale/gl/LC_TIME/coreutils.mo
--> Deleting symlink /usr/share/locale/hu/LC_TIME/coreutils.mo
--> Deleting symlink /usr/share/locale/it/LC_TIME/coreutils.mo
--> Deleting symlink /usr/share/locale/ja/LC_TIME/coreutils.mo
--> Deleting symlink /usr/share/locale/ko/LC_TIME/coreutils.mo
--> Deleting symlink /usr/share/locale/lg/LC_TIME/coreutils.mo
--> Deleting symlink /usr/share/locale/ms/LC_TIME/coreutils.mo
--> Deleting symlink /usr/share/locale/nb/LC_TIME/coreutils.mo
--> Deleting symlink /usr/share/locale/nl/LC_TIME/coreutils.mo
--> Deleting symlink /usr/share/locale/no/LC_TIME/coreutils.mo
--> Deleting symlink /usr/share/locale/pl/LC_TIME/coreutils.mo
--> Deleting symlink /usr/share/locale/pt/LC_TIME/coreutils.mo
--> Deleting symlink /usr/share/locale/pt_BR/LC_TIME/coreutils.mo
--> Deleting symlink /usr/share/locale/ru/LC_TIME/coreutils.mo
--> Deleting symlink /usr/share/locale/sk/LC_TIME/coreutils.mo
--> Deleting symlink /usr/share/locale/sl/LC_TIME/coreutils.mo
--> Deleting symlink /usr/share/locale/sv/LC_TIME/coreutils.mo
--> Deleting symlink /usr/share/locale/tr/LC_TIME/coreutils.mo
--> Deleting symlink /usr/share/locale/zh_CN/LC_TIME/coreutils.mo
--> Deleting symlink /usr/share/locale/zh_TW/LC_TIME/coreutils.mo

Removing package /var/log/packages/coreutils-5.2.1-i486-upgraded-2004-07-15,17:02:47...

Installing package coreutils-5.2.1-i486-2...
PACKAGE DESCRIPTION:
coreutils: coreutils (core GNU utilities)
coreutils:
coreutils: These are the GNU core utilities, the basic command line programs
coreutils: such as 'mkdir', 'ls', and 'rm' that are needed for the system to
coreutils: run. This package is the union of the GNU fileutils, sh-utils, and
coreutils: textutils packages. Most of these programs have significant
coreutils: advantages over their Unix counterparts, such as greater speed,
coreutils: additional options, and fewer arbitrary limits.
coreutils:
Executing install script for coreutils-5.2.1-i486-2...

Package coreutils-5.2.1-i486-1 upgraded with new package ./coreutils-5.2.1-i486-2.tgz.

And everything works like it should... Oh well. I'm going to forget about.... Once again, sorry.....
 
Old 07-15-2004, 05:19 PM   #12
jong357
Senior Member
 
Registered: May 2003
Location: Columbus, OH
Distribution: DIYSlackware
Posts: 1,914

Rep: Reputation: 52
Thats not a bad idea geekster... Nothing gets installed into /usr/local/bin from the coreutils package so there would be no "mixing up" of binaries... I'm still convinced that it was user error until someone else tries it and tells me that the same thing happend.... Sorry, but that shouldn't have happened and I can't really explain it.... Oh well.... Moving right along......
 
Old 07-15-2004, 05:32 PM   #13
thegeekster
Member
 
Registered: Dec 2003
Location: USA (Pacific coast)
Distribution: Vector 5.8-SOHO, FreeBSD 6.2
Posts: 513

Rep: Reputation: 34
Using the 'upgradepkg' tool should work without any problems, since it basically installs and overwrites any files with the new package, then removes any specific files and directories not installed by the new package, like the /usr/doc/<pkgname-version> stuff................It's only when you do a full uninstall then try to install the new coretutils package will there be problems due to missing files from the uninstall............

You can give the warning in the readme to NOT do a 'removepkg coreutils' followed by a 'installpkg coreutils-blah.tgz' and stress using the 'upgradepkg coretuils-blah.tgz' command...........And provide that temputils.tgz file, anyway, in case someone doesn't follow your advice...............they can always untar the file manually and use the tools provided to get out of the mess they got themselves into.............


PS: Another workaround if someone doesn't quite follow directions and does a 'removepkg' command is to manually unpack the new package by following these steps:
Quote:
1) CD to the base directory: cd /

2) Unpack the package with tar: tar -xzpvf /path/to/package.tgz

3) Run the install script, doinst.sh: sh /install/doinst.sh
NOTE: You should run the script with the 'sh' command in case it won't run by itself

4) Finally remove the /install directory: rm -rf /install
NOTE: By manually installing a package, Slack won't know about the installation because it will not get recorded in the /var/log/packages or /var/log/scripts directories..........

Last edited by thegeekster; 07-15-2004 at 06:12 PM.
 
Old 07-15-2004, 06:08 PM   #14
jong357
Senior Member
 
Registered: May 2003
Location: Columbus, OH
Distribution: DIYSlackware
Posts: 1,914

Rep: Reputation: 52
Heh, Heh, Heh..... I bet 'slacka' is staying the hell away from my stuff..... Actually thats not a slackpak. I just thought it was easier to bzip a .bashrc and bashrc with the ls alias instead of copy/pasting all that crap here... So what's up Slacka? Sorry that your thread got highjacked.....

Since I'm so anal and just CAN'T let this drop, I looked over the output you sent me China via email.... ALOT of things there just don't make sense...

Code:
/sbin/removepkg: line 297: rm: command not found
/sbin/removepkg: line 298: rm: command not found
/sbin/removepkg: line 312: mv: command not found

Removing package /var/log/packages/coreutils-5.2.1-i486-2.tgz-upgraded-2004-07-15,21:58:17...

/sbin/installpkg: line 1: cut: command not found
/sbin/installpkg: line 1: cut: command not found
Cannot install ./coreutils-5.2.1-i486-2.tgz: package does not end in .tgz
Package coreutils-5.2.1-i486-1 upgraded with new package ./coreutils-5.2.1-i486-2.tgz.
You shouldn't be seeing any "/sbin/removepkg" or "/sbin/installpkg" on an "upgradepkg"..... But then, the last line there indicates that you DID issue an "upgradepkg".... Make no sense at all... also that line that says:

Code:
Removing package /var/log/packages/coreutils-5.2.1-i486-2.tgz-upgraded-2004-07-15,21:58:17...
States that you ALREADY upgraded to my package.... TODAY even.... It seems as if you pasted output from 3 different attempts... An original "upgradepkg" DID take place according to your output. Then it seems as if you did a "removepkg" and then tried to do an "installpkg"...... You started pasting right in the middle of an opperation as well. There was no beginning PS line that indicates what command you were running... Seems like 3 different things are ALL meshed into ONE output....

Then we can also see this line:

Code:
Cannot install ./coreutils-5.2.1-i486-2.tgz: package does not end in .tgz
There is a semi-colon in there after tgz... Did you acidentally place a ":" in there after the file name?

ARRGGGGGG!!!! I'll let it drop.....
 
Old 07-15-2004, 07:17 PM   #15
slacka
LQ Newbie
 
Registered: Jul 2004
Location: Chico, CA
Distribution: Slackware 10
Posts: 21

Original Poster
Rep: Reputation: 15
jong357 was right. For some reason my DIR_COLORS file was renamed DIR_COLORS.new. All I had to do was rename the file, and I was back over the rainbow. Thanks.

As for the hijack, its ok. I'm glad more good than just my n00b problem was/is in the process of being fixed.

Last edited by slacka; 07-15-2004 at 07:19 PM.
 
  


Reply


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
Issue With /etc/profile And dircolors For All Users Chryzmo Slackware 5 12-01-2005 10:10 PM
dircolors in freebsd d0wn_under *BSD 4 10-08-2004 06:58 AM
dircolors error erikm103 Linux - Software 0 12-08-2003 12:01 AM
Aterm and dircolors Wynd Linux - Software 1 06-22-2003 12:28 AM
Should I use dircolors? Xiangbuilder Linux - General 4 04-08-2003 09:53 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 09:11 AM.

Main Menu
Advertisement
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
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration