LinuxQuestions.org
Did you know LQ has a Linux Hardware Compatibility List?
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 03-08-2010, 08:26 AM   #106
onebuck
Moderator
 
Registered: Jan 2005
Location: Midwest USA, Central Illinois
Distribution: Slackware®
Posts: 11,057
Blog Entries: 1

Original Poster
Rep: Reputation: 1373Reputation: 1373Reputation: 1373Reputation: 1373Reputation: 1373Reputation: 1373Reputation: 1373Reputation: 1373Reputation: 1373Reputation: 1373

Hi,

Just a reminder that the '/usr/share/pci.ids' file is probably dated for your system. You can get '/usr/share/pci.ids' that should be current. No harm but to update this will aid you in understanding newer devices that are not identified but output as 'unknown device'. Not everyone memorizes their 'pci:id' so update that '/usr/share/pci.ids'.

I posted 'Slackware '-current' '/usr/share/pci.ids' file is dated' to prepare anyone for the new release and thinking the system was at fault. You will need to update '/usr/share/pci.ids' to rid the 'unknown device' errors. No harm, just a aid.


Last edited by onebuck; 03-09-2010 at 08:11 AM. Reason: correct link
 
Old 03-24-2010, 08:27 PM   #107
onebuck
Moderator
 
Registered: Jan 2005
Location: Midwest USA, Central Illinois
Distribution: Slackware®
Posts: 11,057
Blog Entries: 1

Original Poster
Rep: Reputation: 1373Reputation: 1373Reputation: 1373Reputation: 1373Reputation: 1373Reputation: 1373Reputation: 1373Reputation: 1373Reputation: 1373Reputation: 1373
Hi,

There is a security bug for FireFox 3.6.

Look at Gazl's post for a remedy.

 
Old 03-24-2010, 08:40 PM   #108
GazL
Senior Member
 
Registered: May 2008
Posts: 3,328

Rep: Reputation: 884Reputation: 884Reputation: 884Reputation: 884Reputation: 884Reputation: 884Reputation: 884
Quote:
Originally Posted by onebuck View Post
Hi,

There is a security bug for FireFox 3.6.

Look at Gazl's post for a remedy.

I'd expect a fixed package to be included in Slackware very shortly, so this warning will not have a very long shelf life. By the time most people read this it will most likely be patched.

However, I would strongly encourage any Slackers who are interested in system security to subscribe to the following two threads over in the LQSEC forum:

Mozilla Firefox Vulnerabilities

and

Kernel Vulnerabilities


We've discussed this latest firefox vulnerability quite a lot over the last few weeks.
 
Old 03-25-2010, 12:04 PM   #109
onebuck
Moderator
 
Registered: Jan 2005
Location: Midwest USA, Central Illinois
Distribution: Slackware®
Posts: 11,057
Blog Entries: 1

Original Poster
Rep: Reputation: 1373Reputation: 1373Reputation: 1373Reputation: 1373Reputation: 1373Reputation: 1373Reputation: 1373Reputation: 1373Reputation: 1373Reputation: 1373
Hi,

Very interesting and appreciate the links.

Some people are just blind or put FUD out there to confuse everyone.
 
Old 03-30-2010, 10:19 PM   #110
onebuck
Moderator
 
Registered: Jan 2005
Location: Midwest USA, Central Illinois
Distribution: Slackware®
Posts: 11,057
Blog Entries: 1

Original Poster
Rep: Reputation: 1373Reputation: 1373Reputation: 1373Reputation: 1373Reputation: 1373Reputation: 1373Reputation: 1373Reputation: 1373Reputation: 1373Reputation: 1373
Hi,

Security is on everyone's mind now a days or at least it should be.

'LQ Security' wiki is a good place to start. If you use Slackware or even plan to use Slackware then be sure to check out 'Slackware Security Advisories' and if you are not on the mailing list. Be sure to follow the instructions which usually is simply a matter of downloading the necessary packages and doing 'upgradepkg packagename'.

 
1 members found this post helpful.
Old 04-05-2010, 05:57 PM   #111
onebuck
Moderator
 
Registered: Jan 2005
Location: Midwest USA, Central Illinois
Distribution: Slackware®
Posts: 11,057
Blog Entries: 1

Original Poster
Rep: Reputation: 1373Reputation: 1373Reputation: 1373Reputation: 1373Reputation: 1373Reputation: 1373Reputation: 1373Reputation: 1373Reputation: 1373Reputation: 1373
Hi,

Quote:
excerpt from -current changelog x86_64;

Mon Apr 5 03:06:19 UTC 2010
kde/k3b-1.91.0-x86_64-1.txz: Upgraded.
l/libjpeg-v8a-x86_64-1.txz: Upgraded.
l/seamonkey-solibs-2.0.4-x86_64-1.txz: Upgraded.
xap/mozilla-firefox-3.6.3-x86_64-1.txz: Upgraded.
This fixes some security issues.
For more information, see:
http://www.mozilla.org/security/know...firefox36.html
(* Security fix *)
xap/mozilla-thunderbird-3.0.4-x86_64-1.txz: Upgraded.
This upgrade fixes some more security bugs.
For more information, see:
http://www.mozilla.org/security/know...derbird30.html
(* Security fix *)
xap/seamonkey-2.0.4-x86_64-1.txz: Upgraded.
This release fixes some more security vulnerabilities.
For more information, see:
http://www.mozilla.org/security/know...amonkey20.html
(* Security fix *)
Some security fixes for mozilla apps. Please be sure to use a mirror, plus let things get updated as it does take some time to settle;

'Official List of Mirrors'

'AlphaGeek's Unofficial Mirror List'

'Oregon State' <<< one that I like to use.



The above links and others can be found at 'Slackware-Links'. More than just Slackware® links!
 
Old 04-08-2010, 09:41 AM   #112
onebuck
Moderator
 
Registered: Jan 2005
Location: Midwest USA, Central Illinois
Distribution: Slackware®
Posts: 11,057
Blog Entries: 1

Original Poster
Rep: Reputation: 1373Reputation: 1373Reputation: 1373Reputation: 1373Reputation: 1373Reputation: 1373Reputation: 1373Reputation: 1373Reputation: 1373Reputation: 1373
Hi,

Just a heads up!

If you need some casual reading then look at the 'Linux Books & Online Magazines' section of 'Slackware-Links'. Loads of FREE online books and magazines to enhance your relationship with other LQ members.

 
1 members found this post helpful.
Old 04-21-2010, 09:12 AM   #113
onebuck
Moderator
 
Registered: Jan 2005
Location: Midwest USA, Central Illinois
Distribution: Slackware®
Posts: 11,057
Blog Entries: 1

Original Poster
Rep: Reputation: 1373Reputation: 1373Reputation: 1373Reputation: 1373Reputation: 1373Reputation: 1373Reputation: 1373Reputation: 1373Reputation: 1373Reputation: 1373
Hi,

Changelog cycle is at about a two week period. Some major points of interest;

Quote:
excerpt 'Current (pre-release) ChangeLog for x86 (32-bit)';

Tue Apr 20 14:45:24 UTC 2010
a/kernel-firmware-2.6.33.2-noarch-1.txz: Upgraded.
a/kernel-generic-2.6.33.2-i486-1.txz: Upgraded.
a/kernel-generic-smp-2.6.33.2_smp-i686-1.txz: Upgraded.
a/kernel-huge-2.6.33.2-i486-1.txz: Upgraded.
a/kernel-huge-smp-2.6.33.2_smp-i686-1.txz: Upgraded.
a/kernel-modules-2.6.33.2-i486-1.txz: Upgraded.
a/kernel-modules-smp-2.6.33.2_smp-i686-1.txz: Upgraded.
ap/mpg123-1.12.1-i486-1.txz: Upgraded.
ap/mysql-5.1.45-i486-1.txz: Upgraded.
ap/nano-2.2.4-i486-1.txz: Upgraded.
ap/sudo-1.7.2p6-i486-1.txz: Upgraded.
This update fixes security issues that may give a user with permission
to run sudoedit the ability to run arbitrary commands.
For more information, see:
http://cve.mitre.org/cgi-bin/cvename...=CVE-2010-0426
http://cve.mitre.org/cgi-bin/cvename...=CVE-2010-1163
http://www.gratisoft.us/sudo/alerts/..._escalate.html
http://www.gratisoft.us/sudo/alerts/...escalate2.html
(* Security fix *)
d/cmake-2.8.1-i486-1.txz: Upgraded.
d/git-1.7.0.5-i486-1.txz: Upgraded.
d/kernel-headers-2.6.33.2_smp-x86-1.txz: Upgraded.
e/emacs-23.1-i486-3.txz: Rebuilt.
Fixed a broken icon and updated to the upstream .desktop file.
k/kernel-source-2.6.33.2_smp-noarch-1.txz: Upgraded.
kde/amarok-2.3.0-i486-1.txz: Upgraded.
kde/kdebase-workspace-4.3.5-i486-2.txz: Rebuilt.
Patched a security issue with KDM.
For more information, see:
http://cve.mitre.org/cgi-bin/cvename...=CVE-2010-0436
(* Security fix *)
kde/koffice-2.1.2-i486-1.txz: Upgraded.
kdei/koffice-l10n-*: Upgraded.
l/lesstif-0.95.2-i486-1.txz: Upgraded.
l/libmtp-1.0.1-i486-1.txz: Upgraded.
l/loudmouth-1.4.3-i486-1.txz: Added.
This is a Jabber library used by Amarok's mp3tunes service.
Thanks to Eric Hameleers.
l/taglib-1.6.2-i486-1.txz: Upgraded.
n/gnutls-2.8.6-i486-1.txz: Upgraded.
extra/linux-2.6.33.2-nosmp-sdk/*: Upgraded.
isolinux/initrd.img: Rebuilt.
kernels/*: Upgraded.
usb-and-pxe-installers/usbboot.img: Rebuilt.
This security fix is very interesting;
Quote:
excerpt 'CVE-2010-0426';
sudo 1.6.x before 1.6.9p21 and 1.7.x before 1.7.2p4, when a pseudo-command is enabled, permits a match between the name of the pseudo-command and the name of an executable file in an arbitrary directory, which allows local users to gain privileges via a crafted executable file, as demonstrated by a file named sudoedit in a user's home directory.
Quote:
http://www.gratisoft.us/sudo/alerts/..._escalate.html

Details:
When sudo performs its command matching, there is a special case for pseudo-commands in the sudoers file (currently, the only pseudo-command is sudoedit). Unlike a regular command, pseudo-commands do not begin with a slash ('/'). The flaw is that sudo's the matching code would only check against the list of pseudo-commands if the user-specified command also contained no slashes. As a result, if the user ran "sudo ./sudoedit" the normal matching code path was followed, which uses stat(2) to verify that the user-specified command matches the one in sudoers. In this case, it would compare the "./sudoedit" specified by the user with "sudoedit" from the sudoers file, resulting in a positive match.
Impact:
Exploitation of the bug requires that the sudoers file be configured to allow the attacker to run sudoedit. If no users have been granted access to sudoedit there is no impact. Successful exploitation of the bug will allow a user to run arbitrary commands for whichever user they have permission to run sudoedit as, typically root.
Yet another security fix for 'KDM CVE-2010-0436';

Quote:
excerpt for 'KDM CVE-2010-0436';

Race condition in backend/ctrl.c in KDM in KDE Software Compilation (SC) 2.2.0 through 4.4.2 allows local users to change the permissions of arbitrary files, and consequently gain privileges, by blocking the removal of a certain directory that contains a control socket, related to improper interaction with ksm.
So guys, you should be signing up for 'Slackware Security Advisories' if you don't follow '-current'.

'LQ Security' wiki is a good place to start. If you use Slackware or even plan to use Slackware then be sure to check out 'Slackware Security Advisories' and if you are not on the mailing list. Be sure to follow the instructions which usually is simply a matter of downloading the necessary packages and doing 'upgradepkg packagename'.
 
Old 05-07-2010, 08:34 AM   #114
onebuck
Moderator
 
Registered: Jan 2005
Location: Midwest USA, Central Illinois
Distribution: Slackware®
Posts: 11,057
Blog Entries: 1

Original Poster
Rep: Reputation: 1373Reputation: 1373Reputation: 1373Reputation: 1373Reputation: 1373Reputation: 1373Reputation: 1373Reputation: 1373Reputation: 1373Reputation: 1373
Hi,

Quote:
excerpt form 'changelog';
Thu May 6 21:02:02 UTC 2010
Hi folks! We have some pretty big changes today, with an update to the latest
KDE SC 4.4.3, and the addition of support for ConsoleKit and PolicyKit which
have been enhanced to use shadow authentication. Thanks to Andrew Psaltis for
doing some great work on polkit-1, and to Robby Workman for spending months
following the sometimes random developments coming from the CK/PK camp. :-)
Thanks to Eric Hameleers for leading the KDE 4.4.x Slackware development and
handling the out-of-tree testing through http://alien.slackbook.org/blog/.
And with that, we're calling this Slackware 13.1 BETA1. A stable release
should be just around the corner...
Please remember that when the stable becomes available to use a 'mirror'. Check out the Get Slackware section of 'Slackware-Links under 'Slackware® Mirrors:' or for you point & clickers;

Official List of Mirrors
AlphaGeek's Unofficial Mirror List
LinuxQuestions.org > ISOs > Slackware®
Oregon State << My choice
The Linux Mirror Project

For the new user to get '-current' or this 'Slackware 13.1 BETA1' I suggest that you use Alien_Bob's-script-mirror-slackware-current.sh. To download -current, create cdrom/dvd Or Alien_Bob's-script -mirror-slackware-current.sh : UK backup of script script to download the '-current' of choice ( 'x86' meaning 32bit or 'x86_64' meaning 64bit). You can either pass parameters or edit the script to create the 'ISO' medium of choice. Plus be sure to select a mirror of choice to use. The script is well documented to allow you choices. Alien_Bob is a Slackware® contributor and has graciously provided the scripts/tools.

So an ata-boy and a big Thank You to PV, Alien_Bob, Robby and Team. Plus I want to extend my personal thanks to the LQ Slackware forum members.

The above links and others can be found at 'Slackware-Links'. More than just Slackware® links!

Patience!

Happy Slacking
 
Old 05-12-2010, 05:35 PM   #115
onebuck
Moderator
 
Registered: Jan 2005
Location: Midwest USA, Central Illinois
Distribution: Slackware®
Posts: 11,057
Blog Entries: 1

Original Poster
Rep: Reputation: 1373Reputation: 1373Reputation: 1373Reputation: 1373Reputation: 1373Reputation: 1373Reputation: 1373Reputation: 1373Reputation: 1373Reputation: 1373
Hi,

I've noticed a problem for some new users that are attempting to use 'Slackware 13.1 BETA1'.

'libata_switchover' has been around since 13.0 but some new users are not aware.
A new user should look at rworkman's 'libata_switchover HOWTO';

Quote:
excerpt 'libata_switchover HOWTO';
This is written to provide one of several ways to retain a working
system after upgrading from Slackware 13.0's kernel to the newer
kernel in -current (which removes support for the "old" ide subsytem,
thereby causing all /dev/hd* devices to have /dev/sd* names.
I also suggest that everyone looks at CHANGES_AND_HINTS.TXT and the other text files. Hopefully this will keep the gotcha clown away.

 
Old 05-13-2010, 04:50 PM   #116
onebuck
Moderator
 
Registered: Jan 2005
Location: Midwest USA, Central Illinois
Distribution: Slackware®
Posts: 11,057
Blog Entries: 1

Original Poster
Rep: Reputation: 1373Reputation: 1373Reputation: 1373Reputation: 1373Reputation: 1373Reputation: 1373Reputation: 1373Reputation: 1373Reputation: 1373Reputation: 1373
Hi,

One thing that I believe everyone should read is the 'CURRENT.WARNING' as it pertains to '-current' & 'Slackware 13.1 BETA1' is '-current'.

Code:
'CURRENT.WARNING';

[Standard disclaimer follows... ]

Welcome to Slackware-current!  (x86_64)

*** Please note that you must already be ***
*** running a 2.6.x kernel before        ***
*** upgrading to Slackware-current!      ***
***                                      ***
*** upgradepkg glibc-solibs before other ***
*** packages.  Take care not to miss new ***
*** packages that were split from old    ***
*** ones:  upgradepkg --install-new is   ***
*** (as always) the safest approach.     ***

Slackware-current is a snapshot of the active Slackware development tree.
It is intended to give developers (and other Linux gurus) a chance to test
out the latest packages for Slackware.  The feedback we get will allow us
to make the next stable release better than ever.

See the ChangeLog.txt for a list of changes in Slackware-current.

Please note that the code in this directory is unstable.  It might be 
inconsistent about which version of the Linux kernel is required, could be
incomplete because it's in the process of being uploaded, or might not work
for other reasons.  In most cases, we know about these things and are working
to correct them, but still -- feel free to point out the bugs.

Production use is AT YOUR OWN RISK and is not recommended.

Security is NOT GUARANTEED.  In -current, forward progress often takes
priority.  Security fixes take time and resources, and would often have to
be done more than once.  It's more efficient to build the system and secure
it as time permits and/or the development cycle nears completion.

We do not promise to issue security advisories for Slackware-current.

Slackware-current might DELETE FILES WITHOUT WARNING when packages are
upgraded.  (If, for example, a directory location is replaced by a symbolic
link to a new location.)  Upgrade packages carefully.  Examine incoming
updates first if your machine's data is not expendable.  Again, we do not
recommend using Slackware-current to store or process valuable data.
It is a system in testing, not one that is ready to go (though often it does
work just fine...  BUT DON'T COUNT ON IT) 

#include BSD license warranty disclaimer here...

Enjoy! :)

---
Patrick J. Volkerding
volkerdi@slackware.com
Plus other text files should be read as there are hidden treasures of information that may keep you from .
 
Old 05-19-2010, 07:33 AM   #117
onebuck
Moderator
 
Registered: Jan 2005
Location: Midwest USA, Central Illinois
Distribution: Slackware®
Posts: 11,057
Blog Entries: 1

Original Poster
Rep: Reputation: 1373Reputation: 1373Reputation: 1373Reputation: 1373Reputation: 1373Reputation: 1373Reputation: 1373Reputation: 1373Reputation: 1373Reputation: 1373
Slackware 13.1 RC2

Hi,


Tue May 18 22:17:13 UTC 2010 Slackware 13.1 RC2
. Expect a stable release when it's ready.

We're getting close to a release date! So when we do have a release be sure to seed the torrents and be patient for mirror updates.

 
Old 05-25-2010, 08:43 AM   #118
onebuck
Moderator
 
Registered: Jan 2005
Location: Midwest USA, Central Illinois
Distribution: Slackware®
Posts: 11,057
Blog Entries: 1

Original Poster
Rep: Reputation: 1373Reputation: 1373Reputation: 1373Reputation: 1373Reputation: 1373Reputation: 1373Reputation: 1373Reputation: 1373Reputation: 1373Reputation: 1373
Hi,

Quote:
excerpt ftp://ftp.osuosl.org/pub/slackware/s.../ChangeLog.txt
Wed May 19 08:58:23 UTC 2010
Slackware 13.1 x86 stable is released!
Lots of thanks are due -- see the RELEASE_NOTES and the rest of the
ChangeLog for credits. The ISOs are on their way to replication,
a 6 CD-ROM 32-bit set and a dual-sided 32-bit/64-bit x86/x86_64 DVD.
We are taking pre-orders now at store.slackware.com, and offering
a discount if you sign up for a subscription. Consider picking up
a copy to help support the project. Thanks again to the Slackware
community for testing, contributing, and generally holding us to a
high level of quality. :-)
Enjoy!
Please note that you only need CD1,2 & 3 for a full install of Slackware x86.

Torrents for Slackware 13.1, 32-bit x86

Slackware 13.1 x86 Install ISO disc 1 (A/AP/D/E/L/N, bootable installer, kernels, testing/, Slackbook)

Slackware 13.1 x86 Install ISO disc 2 (F/K/T/TCL/X/XAP/Y, L source)
Slackware 13.1 x86 Install ISO disc 3 (KDE/KDEI)
Slackware 13.1 x86 ISO disc 4 (A/AP/D/E/F/installer source, extra/, pasture/, old Berkeley DB packages)
Slackware 13.1 x86 ISO disc 5 (KDE/KDEI source)
Slackware 13.1 x86 ISO disc 6 (K/N/T/TCL/X/XAP/Y source, USB and PXE installers)

Slackware 13.1 x86 DVD ISO (everything)

Slackware 13.1 x86_64 DVD ISO (everything)

Seeders are necessary!

Enjoy!
 
Old 05-27-2010, 08:50 AM   #119
onebuck
Moderator
 
Registered: Jan 2005
Location: Midwest USA, Central Illinois
Distribution: Slackware®
Posts: 11,057
Blog Entries: 1

Original Poster
Rep: Reputation: 1373Reputation: 1373Reputation: 1373Reputation: 1373Reputation: 1373Reputation: 1373Reputation: 1373Reputation: 1373Reputation: 1373Reputation: 1373
Hi,

The dust is settling for this wonderful release. Forum activity is minimal for this release other than praise.

BUT: Once You get the ISO downloaded then you should do a md5sum check on the downloaded ISO(s) image(s) to keep from having a stack of coasters. This can be done using a M$ Windows application such as 'md5sum.exe' to check the md5sum. Or for Linux from the cli you would do;

Code:
~#cd /downloadisolocation      #cdromiso.iso cdromiso.md5 

~#md5sum -c cdromiso.md5       #substitute the correct name to check
Once you are sure that everything is OK then you can burn the 'ISO IMAGE' to your selected media. Please note that some users must burn the ISO image at a slower speed to insure a good burn. By slowing the burn speed you may insure that a good copy will be created if the image is indeed valid.

Once the image has been burned to the media then a 'CdromMd5sumsAfterBurning' check would be advised. Your burn application can fail so a check of the final media would prevent you from some possible headaches.

After you have the new release ready to install then you should read for understanding and revelation to help in having no stumbling blocks or gotcha(s);


Slackware® 13.1 Release Announcement

Slackware® 13.1 CHANGES_AND_HINTS.TXT
Slackware® 13.1 UPGRADE.TXT
Slackware® 13.1 README.TXT
Slackware® 13.1-HOWTO
Slackware® 13.1 usb-and-pxe-installers
Slackware® 13.1 README.initrd

I'm sure there are people who will have some stumbles. They should first do some searches here on LQ Or Google/Linux.


I also suggest that you look at 'How to Ask Questions the Smart Way' so that in the future your thread queries provide information which will aid us in diagnosis of the problem from a good formed question(s).

Patience!
 
Old 06-01-2010, 08:27 AM   #120
onebuck
Moderator
 
Registered: Jan 2005
Location: Midwest USA, Central Illinois
Distribution: Slackware®
Posts: 11,057
Blog Entries: 1

Original Poster
Rep: Reputation: 1373Reputation: 1373Reputation: 1373Reputation: 1373Reputation: 1373Reputation: 1373Reputation: 1373Reputation: 1373Reputation: 1373Reputation: 1373
Hi,

For those that wish to create ISO from a Slackware 13.1 tree then visit http://alphageek.dyndns.org/linux/sligdo/ ;

Quote:
excerpt from http://alien.slackbook.org/blog/

Alphageek’s “sligdo files” are a very fast way of creating byte-exact copies of the official ISOs in case you already have a local mirror-copy of the full Slackware 13.1 tree. The ISOs you create with sligdo
Quote:
excerpt from sligdo

Here is a rather creative hack (if I do say so myself) to generate Slackware & Slackware64 13.1 ISOs from their file trees.
... (see page content)

Directions:

  • ensure sligdo & jigdo-file are somewhere in your $PATH & are executable.
  • place the .jigdo & .template files in a handy directory that's on a partition with enough space available
  • cd to this directory
  • run "sligdo /path/to/toplevel/slackware/"
  • wait a few minutes while the ISOs are created in $PWD/slackware-13.1-iso/ or $PWD/slackware64-13.1-iso/
  • if you're operating a Slackware mirror (or just paranoid), do an rsync touchup run against another mirror to grab the missing .asc, .md5 & .txt files.
  • enjoy
The technique is straight and easy to follow. Three SlackStars for http://alphageek.dyndns.org/linux/sligdo/ methodology.
 
  


Reply

Tags
install, machine, network, nic, slackware, virtual


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
Another slacker! :) multios Slackware 37 01-30-2008 06:22 PM
Another Slacker... :) TtuEd LinuxQuestions.org Member Intro 1 09-03-2007 02:41 PM
Greetings from a slacker Bread LinuxQuestions.org Member Intro 1 01-19-2006 06:53 PM
I'm a new Slacker olias Slackware 13 11-03-2003 02:58 PM
I'm a slacker in need Tekime Slackware 2 07-30-2002 01:33 PM


All times are GMT -5. The time now is 08:18 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