LinuxQuestions.org
Visit Jeremy's Blog.
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 05-10-2008, 11:05 PM   #16
shadowsnipes
Senior Member
 
Registered: Sep 2005
Distribution: Slackware
Posts: 1,441

Original Poster
Rep: Reputation: 70

Quote:
Originally Posted by T3slider View Post
Please make sure to read all of the documentation (especially UPGRADE.TXT and CHANGES_AND_HINTS.TXT) and thoroughly before (and after) upgrading or installing fresh -- it'll give you less headaches and a better system in the end.
I probably should have stressed this more strongly in the HowTo. Everyone needs to read these docs for an upgrade, and the CHANGES_AND_HINTS.TXT should be read always.

In fact, I probably read both of those documents three (different) times before writing this HowTo.

The documentation is very informative, and while this HowTo includes most of it, it does not include all of it. This is intentional because:
1) I don't want this HowTo to replace the official documentation
2) This HowTo is meant to be an example of how to use the documentation

Really, it should just be a habit to read at least these two documents for every upgrade/install. I wouldn't mind at all if the setup program for Slackware gave you the option to show you them. This way, more people would likely see and read them.
 
Old 05-10-2008, 11:24 PM   #17
vvoody
Member
 
Registered: Apr 2007
Location: Shanghai,China || Sweden
Distribution: Slackware
Posts: 43

Rep: Reputation: 1
I have a problems.

When somebody 'has sent a nudge' to my MSN, the kopete don't play a sound. Before upgrading, it worked well. I open the 'Notification Setting'. And I click the play button of ''Kopete_Received.ogg", but I can not hear the sound. When I play the 'Kopete_Received.ogg' by other apps like mplayer, I hear the sound!

And I found that in the 'Notification Setting', I can play the some other *.ogg.
 
Old 05-10-2008, 11:54 PM   #18
shadowsnipes
Senior Member
 
Registered: Sep 2005
Distribution: Slackware
Posts: 1,441

Original Poster
Rep: Reputation: 70
Quote:
Originally Posted by vvoody View Post
I have a problems.

When somebody 'has sent a nudge' to my MSN, the kopete don't play a sound. Before upgrading, it worked well. I open the 'Notification Setting'. And I click the play button of ''Kopete_Received.ogg", but I can not hear the sound. When I play the 'Kopete_Received.ogg' by other apps like mplayer, I hear the sound!

And I found that in the 'Notification Setting', I can play the some other *.ogg.
Do other KDE sounds work (such as when you login to KDE). If you don't use KDE then try other KDE apps that have sound feedback.

It sounds like a problem with Artsd, or whatever your KDE sound system is set to.
 
Old 05-11-2008, 12:16 AM   #19
shadowsnipes
Senior Member
 
Registered: Sep 2005
Distribution: Slackware
Posts: 1,441

Original Poster
Rep: Reputation: 70
Part 2 of the HowTo

I needed to split the HowTo into two posts in order to be under the maximum character limit per post. I apologize for the inconvenience.
----------------------------------------------------------
Part 2 Sections:
LILO and the Fancy Bootsplash
Get Rid of Obsolete Slackware Packages from 12.0
Merge Changes for Config Files
Update Your Graphics Drivers (if needed)
Miscellaneous Fixes
Rebuild/Upgrade any Non-Slackware Packages (as Needed)
Fix Other Random Problems


** LILO and the Fancy Bootsplash **
To use the bootsplash new to Slackware 12.1 you need to modify your lilo.conf. Slackware's liloconfig has an option to add this for you, and looking at its code you can see what it is doing. It uses a function called boot_bmp() that simply cats the necessary text into lilo.conf, and then it makes sure that the boot message is turned off by commenting that line out.

The beginning of my lilo.conf looks like this (the bold sections are what I manually changed for the bootsplash)
Code:
# LILO configuration file 
# generated by 'liloconfig' 
# 
# Start LILO global section 
boot = /dev/hda 
#compact        # faster, but won't work on all systems. 

# Boot BMP Image. 
# Bitmap in BMP format: 640x480x8 
  bitmap = /boot/slack.bmp 
# Menu colors (foreground, background, shadow, highlighted 
# foreground, highlighted background, highlighted shadow): 
  bmp-colors = 255,0,255,0,255,0 
# Location of the option table: location x, location y, number of 
# columns, lines per column (max 15), "spill" (this is how many 
# entries must be in the first column before the next begins to 
# be used.  We don't specify it here, as there's just one column. 
  bmp-table = 60,6,1,16 
# Timer location x, timer location y, foreground color, 
# background color, shadow color. 
  bmp-timer = 65,27,0,255 

# Standard menu. 
# Or, you can comment out the bitmap menu above and 
# use a boot message with the standard menu: 
#message = /boot/boot_message.txt 
prompt 
timeout = 40

** Get Rid of Obsolete Slackware Packages from 12.0 **
The CHANGES_AND_HINTS.TXT files does a good job of listing these.

Quote:
Originally Posted by CHANGES_AND_HINTS.TXT
*** PACKAGE REMOVALS SINCE 12.0 ***

a/util-linux: Removed (replaced by util-linux-ng).
ap/espgs: Removed. This is replaced by ghostscript.
ap/gimp-print: Removed. This is replaced by gutenprint.
e/emacs-info: Removed (this is now included in the monolithic emacs package).
e/emacs-leim: Removed (this is now included in the monolithic emacs package).
e/emacs-lisp: Removed (this is now included in the monolithic emacs package).
e/emacs-misc: Removed (this is now included in the monolithic emacs package).
e/emacs-nox: Removed (this is now included in the monolithic emacs package).
l/libmusicbrainz: Removed.
l/libtunepimp: Removed.
l/mcs: Removed (renamed to l/libmcs).
x/dejavu-ttf: Renamed to x/dejavu-fonts-ttf.
x/xorg-server-xdmx: Removed. This is unmaintained upstream.
extra/ham: Removed due to lack of maintenance.
extra/intel-wlan-ipw3945/*: Removed; support for these devices is included
in the kernel now.
extra/linux-wlan-ng: This does not compile on 2.6.24.x kernels.
extra/ntfsprogs: Upgraded and moved to the AP seires.
extra/xf86-video-ati-6.6.3: Removed.
pasture/gcc-3.4.6/: Removed.
slackpkg is again useful here.
Code:
slackpkg -onoff=off clean-system
will list all of the packages not found in Slackware 12.1 (none selected for removal). Compare this to the list you created earlier and select the obsolete slackware 12 packages (the ones appearing in the slackpkg dialog but not your original list). In my example, I found two obsolete packages not included in the CHANGES_AND_HINTS.TXT file.
Code:
xf86-input-acecad-1.2.0
xf86-input-void-1.1.0

** Merge Changes for Config Files **
Quote:
Originally Posted by UPGRADE.TXT
6. Fix your config files. Some of the config files in /etc are going to
need your attention. You'll find the new incoming config files on
your system with the ".new" extension. You may need to fill these in
with information from your old config files and then move them over.
Regardless of what method you choose to upgrade packages, you will have to devote some of your time deciding if there is anything in the new config files that you need.

slackpkg has a nice feature that will find these files for you and ask what you want to do with them. This can be specifically done by running 'slackpkg new-config'. My personal preference is to Prompt for each one. If I know I didn't modify the old config (perhaps because it is not something I use, such as bluetooth), I simply Overwrite it with the new one. For the ones I know I modified, I choose to Keep them, and I manually merge any changes I want later. For all the ones I am not sure about, I Diff them and make my decision from there.

One annoying thing I noticed with slackpkg, is that if you choose Overwrite, the old config file is backed up with a .orig extension. Since I had already backed up my entire system, I found these files to be clutter and used find to remove them.

Here is a command that will find and list the .orig files under /etc
Code:
find /etc -type f -name \*.orig
And the command that will remove them
Code:
find /etc -type f -name \*.orig -exec rm -v '{}' \;
In particular, you need to be careful about any possible .orig files under /etc/modprobe.d.
Quote:
Originally Posted by CHANGES_AND_HINTS.TXT
The /etc/modprobe.d/blacklist file has been changed significantly; be sure to
move/merge the /etc/modprobe.d/blacklist.new file in its place. Also, you
must NOT leave a backup of the old blacklist file (such as blacklist.orig)
in /etc/modprobe.d/ -- ALL files in that directory are checked, so if a
module is blacklisted in *any* of them, it won't be loaded.
It is important to note that slackpkg did not find all the .new files. I used the following command and came up with these additional files.
Code:
find / -type f -name \*.new
/usr/lib/man.conf.new → Overwrite
/etc/group.new → Remove
/etc/passwd.new → Remove
/etc/shadow.new → Remove
/etc/gshadow.new → Remove
The new group and passwd files would only be useful if there were some new groups or users needed for some new feature, and something like that would have been mentioned in CHANGES_AND_HINTS.TXT. It wasn't so they were removed promptly.


** Update Your Graphics Drivers (if needed) **
You probably need to upgrade to the newest driver if you intend on using hardware acceleration. There are slackBuilds for the driver and kernel module for ATI and Nvidia cards. The slackBuilds also come with a nice script that helps you to switch between your proprietary driver and the built in kernel driver.

ATI SlackBuilds
Nvidia SlackBuilds


** Miscellaneous Fixes **
These are all specified in CHANGES_AND_HINTS.TXT.

Removed /etc/rc.d/rc.scanluns
Quote:
Originally Posted by CHANGES_AND_HINTS.TXT
The provided kernels are now compiled with CONFIG_SCSI_MULTI_LUN=y so there
should be no need for the /etc/rc.d/rc.scanluns script (it should now be
deleted, as it's not included in the sysvinit-scripts package any more).

If this configuration causes a problem with any real SCSI drives, then you
should add this to your kernel's lilo stanza: append = "max_luns=1"
Removed /etc/rc.d/rc.hplip
Quote:
Originally Posted by CHANGES_AND_HINTS.TXT
HPLIP no longer requires daemons to be started at boot time, so any
/etc/rc.d/rc.hplip script should be removed.
Added alias for hp-toolbox to either /etc/profile (system-wide) or ~/.profile (user specific)
Code:
alias hp-toolbox='LC_ALL=$LANG.UTF8 hp-toolbox'
Added my user to lp group
Quote:
Originally Posted by CHANGES_AND_HINTS.TXT
There is a minor problem with the HPLIP and CUPS versions in Slackware 12.1;
hp-toolbox will not work unless LC_ALL is set to a UTF8 locale.
An easy workaround is to start it with "LC_ALL=$LANG.UTF8 hp-toolbox" if
you're not using a UTF8 locale. Also, your user account must be a member
of the "lp" group for hp-toolbox to work properly, and to use the scanner
portion of some (all?) HP print/scan/copy units, you'll need to be a member
of the "lp" group. This is due to the fact that hplip's udev rules set
the device with group "lp" ownership.
Remove obsolete udev files
The two files to remove are located under /etc/udev/rules.d/. I actually did not have a 70-persistent-net.rules file, and it was not created until I removed 75-network-devices.rules, so keep this in mind.
Quote:
Originally Posted by CHANGES_AND_HINTS.TXT
If you have more than one network card and have been using the
75-network-devices.rules file, it is now called 70-persistent-net.rules
(and is generated from 75-persistent-net-generator.rules).
Rules for optical devices are now located in 70-persistent-cd.rules (and
are generated from 75-cd-aliases-generator.rules).
You will need to remove the old rules files (75-optical-devices.rules and
75-network-devices.rules) so that they don't conflict.


As stated above, Slackware's udev implementation will automatically create
rules files for your optical devices and network interfaces
on first boot.
If you add/remove/replace any of this hardware, and/or you "clone" a system
to another hard drive for deployment, you will need to either remove these
two rules files (so that udev will regenerate them to reflect the new or
changed hardware) or edit them accordingly.
Fix slow Xfce Terminal
I noticed after the upgrade that having Terminal open caused workspace switching to be slower and Terminal also resized slower than normal.
This is easily fixed by creating /etc/profile.d/x-fix.sh
Code:
#!/bin/sh 
# This should fix slow Xfce Terminal in Slackware 12.1 
export XLIB_SKIP_ARGB_VISUALS=1
Do not forget to make it executable.
Quote:
Originally Posted by CHANGES_AND_HINTS.TXT
If you notice Xfce's Terminal and perhaps some other applications being drawn
very slowly in X, then you should try explicitly disabling the Composite
extension in /etc/X11/xorg.conf, or set XLIB_SKIP_ARGB_VISUALS=1 in your
environment prior to starting X. For more information on this, see:
http://bugzilla.xfce.org/show_bug.cgi?id=2792
Computer won't shutdown completely
I did not have this problem, but I added it here because I lot of people did. If you are one of those people (see "Slackware 12.1 - Halt Problem") just add the following append line to your /etc/lilo.conf.
Quote:
Originally Posted by CHANGES_AND_HINTS.TXT
If you have an older machine (with a BIOS released prior to 2001) and it will
not power off on shutdown, try adding this to your kernel's lilo stanza:
append = "acpi=force"
Mouse does not work
I did not have this problem either, but many people seemed to have missed the notes about this in the CHANGES_AND_HINTS.TXT, so I felt it deserved attention here.
Quote:
Originally Posted by CHANGES_AND_HINTS.TXT
The psmouse module is no longer blacklisted by default; instead, it is loaded
with the imps protocol per /etc/modprobe.d/psmouse -- if you need/want a
different protocol, edit that file. Note that options declarations have
no bearing on *if* a module is loaded - they only affect *how* it is loaded.
In other words, the module should now be loaded automatically (since it's no
longer blacklisted), and the options in /etc/modprobe.d/psmouse are the ones
applied when loading it.
So, for instance, if your mouse doesn't use imps then edit /etc/modprobe.d/psmouse so that it uses the correct protocol for your mouse. - Thread related to 12.1 mouse problems

There are more helpful hints in CHANGES_AND_HINTS.TXT. Read it if you haven't already done so!


** Rebuild/Upgrade any Non-Slackware Packages (as Needed) **
Depending on how much and what specific software you have installed, this portion of the upgrade process can take the longest or shortest chunk of time.

Looking at my list I had created previously, I had 75 Non-Slackware packages. Some of these I chose to simply remove and some had become part of slackware (and so were upgraded during the upgrade process). As for the rest of them, if there was a newer version that looked worth my time I chose to upgrade. The others I only upgraded if they were broken.

Fortunately, almost all of my packages were created via slackBuilds (most scripts from slackBuilds.org), so I didn't need to go looking through any repositories.

Since some of the libraries were broken (no surprise) I chose to rebuild them all. A good number of the packages worked fine as is. For the few that didn't, I ran ldd to see what libraries were causing problems and rebuilt/upgraded as needed.

It is important to note that even if you choose to have a fresh installation you will have to do this step of the process.


** Fix Other Random Problems **
This is a separate section because there was no mention of these problems in CHANGES_AND_HINTS.TXT. Some may be specific to my machine as well.

Default 640x480 no longer displays
It seems that the newest Nvidia driver (169.12) for my 7600GS does not correctly handle my monitor (Dell 152FP) at a 640x480 resolution, while my previous driver (100.14.19) on Slackware 12.0 worked fine. The problem is that the driver now by default uses the wrong vertical sync. To fix it, I simply had to specify that 640x480 be used at 75Hz. This is easily done be changed my Modes under the Screen Section (in /etc/X11/xorg.conf) from
Code:
Modes      "1024x768" "800x600" "640x480"
to
Code:
Modes      "1024x768" "800x600" "640x480_75"
The other VESA modes work fine in the VertRefresh range I specified in my Monitor section (60.0 - 75.0) and are auto-detected correctly.


Remote Control for Audacious broken
This is not a problem with Slackware or Audacious, but rather a consequence of the remote control utility not keeping up with Audacious development. In my case, I had been using FoxyTunes and I had created a symlink at /usr/lib/libxmms.so that pointed to /usr/lib/libaudacious.so. This enabled FoxyTunes to work with Audacious by selecting XMMS as the player.

However, this was using Audacious 1.3.2 on Slackware 12.0. On Slackware 12.1, with Audacious 1.5.0, this no longer works because /usr/lib/libaudacious seems to have been removed. If you read the Audacious FAQ, you will see that this change has been in place since version 1.4. The remote control of audacious is now done through audtool (it has a man page), so keep this in mind when using remote control utilities.

For those interested in controlling Audacious through FoxyTunes feel free to post in this FoxyTunes thread. I've contacted the FT developers a couple times about official Audacious support, and I have been told it is on their ToDo list.

Font Problems
Here is a useful thread on font issues in 12.1.

Beautiful Fonts in 12.1 is also worth a read.

If you have Microsoft TTFs installed and the new Liberation fonts are overriding them, then (as root) simply remove the symlink at
/etc/fonts/conf.d/60-liberation.conf and then run fc-cache -f.


Enjoy Slackware 12.1!

Last edited by shadowsnipes; 07-03-2008 at 12:53 PM.
 
Old 05-11-2008, 12:27 AM   #20
vvoody
Member
 
Registered: Apr 2007
Location: Shanghai,China || Sweden
Distribution: Slackware
Posts: 43

Rep: Reputation: 1
Quote:
Originally Posted by shadowsnipes View Post
Do other KDE sounds work (such as when you login to KDE). If you don't use KDE then try other KDE apps that have sound feedback.

It sounds like a problem with Artsd, or whatever your KDE sound system is set to.
I can hear the sound when I login/logout to KDE.
 
Old 05-13-2008, 12:40 PM   #21
MQMan
Member
 
Registered: Jan 2004
Location: Los Angeles
Distribution: Slack64 13.37
Posts: 536

Rep: Reputation: 36
Apart from the extra effort in understanding what packages have been added in 12.1, is there any reason why I shouldn't leave off the "--install-new" from the mass upgradepkg. I only install the packages I need, instead of everything, and so would rather just upgrade those.

My anticipated steps would be:

Upgrade glibc
Upgrade pkgtools
Remove obsolete packages
Upgrade installed packages
Add new packages, as required.

Does anyone see any issues with this.

Cheers.
 
Old 05-13-2008, 01:13 PM   #22
shadowsnipes
Senior Member
 
Registered: Sep 2005
Distribution: Slackware
Posts: 1,441

Original Poster
Rep: Reputation: 70
Quote:
Originally Posted by MQMan View Post
Apart from the extra effort in understanding what packages have been added in 12.1, is there any reason why I shouldn't leave off the "--install-new" from the mass upgradepkg. I only install the packages I need, instead of everything, and so would rather just upgrade those.

My anticipated steps would be:

Upgrade glibc
Upgrade pkgtools
Remove obsolete packages
Upgrade installed packages
Add new packages, as required.

Does anyone see any issues with this.

Cheers.
No, as long as you are sure you added all the new packages that are needed.

The list of new packages is, of course, included in the Slackware documentation, but you should be able to use slackpkg to create a list as well. Similar to generating a list of non-Slackware software, the following command should (I haven't tested this yet) give you a list of new Slackware software.

Code:
slackpkg -dialog=off -batch=on -default_answer=no install-new > NewSlackwarePackages.txt
Edit:
Just to clarify something, as far as I know, Pat always suggests a full install. Therefore, it could always be possible to have "issues" if you don't have a full install. If you know what you are doing then this shouldn't be a problem.

Last edited by shadowsnipes; 05-13-2008 at 01:16 PM.
 
Old 05-13-2008, 03:06 PM   #23
digger95
Member
 
Registered: Oct 2007
Location: Indiana, PA
Distribution: Slackware 14
Posts: 330

Rep: Reputation: 45
Excellent guide shadowsnipes! Thanks to everyone for taking the time to write this all down and provide relevant links as well. It's been very helpful. In the end I just decided to back everything up to data-dvd and do a fresh install of 12.1. It just 'feels' cleaner. I'm afraid I'm one of those people who's bothered by the fact that there may be leftover and unused 'stuff' lurking on my machine. LoL. It's a burden.
 
Old 05-13-2008, 03:39 PM   #24
onebuck
Moderator
 
Registered: Jan 2005
Location: Midwest USA, Central Illinois
Distribution: SlackwareŽ
Posts: 11,390
Blog Entries: 3

Rep: Reputation: 1479Reputation: 1479Reputation: 1479Reputation: 1479Reputation: 1479Reputation: 1479Reputation: 1479Reputation: 1479Reputation: 1479Reputation: 1479
Hi,
Quote:
Originally Posted by digger95 View Post
Excellent guide shadowsnipes! Thanks to everyone for taking the time to write this all down and provide relevant links as well. It's been very helpful. In the end I just decided to back everything up to data-dvd and do a fresh install of 12.1. It just 'feels' cleaner. I'm afraid I'm one of those people who's bothered by the fact that there may be leftover and unused 'stuff' lurking on my machine. LoL. It's a burden.
Nothing wrong with being careful with ones equipment. You can trim the full install to your needs.
 
Old 05-18-2008, 06:45 PM   #25
shadowsnipes
Senior Member
 
Registered: Sep 2005
Distribution: Slackware
Posts: 1,441

Original Poster
Rep: Reputation: 70
I just finished updating the HowTo. As some keen observers have noticed, I had to split it into two posts in order to be under the character/post limit. Most changes are in RED, and there's a mini changelog at the top of the original post. If I goofed anything please let me know.

Quote:
Originally Posted by rworkman View Post
Moderators, please sticky this, as it will surely be useful to people.
I agree with this. If this thread has helped you please leave a post, so it can be bumped back up where people can see it easier. Hopefully it will be stickied in the future.
 
Old 05-23-2008, 11:35 PM   #26
shadowsnipes
Senior Member
 
Registered: Sep 2005
Distribution: Slackware
Posts: 1,441

Original Poster
Rep: Reputation: 70
vvoody was very kind in creating a Chinese translation of this HowTo. Please see http://www.linuxsir.org/bbs/thread329142.html for vvoody's translation.
 
Old 07-03-2008, 06:43 AM   #27
tunkaflux
LQ Newbie
 
Registered: Apr 2003
Posts: 10

Rep: Reputation: 0
Remote upgrade

Hello,

A quick question regarding this HOWTO and remote upgrading.

Is it necessary to go into runlevel 1? Reason for asking is when I go to runlevel 1, most likely ssh will be killed and I will lose the connection to my machine...

Kind regards.
 
Old 07-03-2008, 12:02 PM   #28
rworkman
Slackware Contributor
 
Registered: Oct 2004
Location: Tuscaloosa, Alabama (USA)
Distribution: Slackware
Posts: 1,921

Rep: Reputation: Disabled
Quote:
Originally Posted by tunkaflux View Post
A quick question regarding this HOWTO and remote upgrading.

Is it necessary to go into runlevel 1? Reason for asking is when I go to runlevel 1, most likely ssh will be killed and I will lose the connection to my machine...
s/most likely//

If you're doing the upgrade remotely, then no, don't go to runlevel 1. Instead, stop as many services as possible and then do the upgrade.
 
Old 07-03-2008, 01:09 PM   #29
shadowsnipes
Senior Member
 
Registered: Sep 2005
Distribution: Slackware
Posts: 1,441

Original Poster
Rep: Reputation: 70
tunkaflux,

in addition to rworkman's sound advice, I'd recommend that you use a screen session if you are going to be doing the upgrade remotely. That way if you inadvertently lose your connection you can just reconnect to that screen session. You also don't need to be connected the whole time. You can ssh in, start screen, and later during a long mass upgrade command you can detach the session and disconnect from ssh.

Take careful note of what services are running during the upgrade as you will have to restart them after wards (restarting ssh should not kick off active connections).

By they way, I added a minor update to the HowTo (Part II). I just mentioned how to make MS TTFs and Liberation fonts play nice.
 
Old 07-27-2008, 09:20 AM   #30
niels.horn
Senior Member
 
Registered: Mar 2007
Location: Rio de Janeiro - Brazil
Distribution: Slackware64-current
Posts: 1,004

Rep: Reputation: 89
Just upgraded to 12.1 yesterday. I always prefer to wait a bit so that others can find the first glitches ;-)

Thanks for all the info in this thread - upgrade went without problems.

Just had to reconfigure my vmware (as expected because of the new kernel) and find a new vmware-any-any* package on the internet.
 
  


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
howto upgrade DSM? kscott121 DamnSmallLinux 0 10-11-2007 04:04 PM
Upgrade HOWTO? jcmanous Linux - General 2 05-06-2005 08:38 AM
Howto upgrade to KDE 3.2 mooreted Mandriva 18 04-04-2004 01:19 PM
Kernel Upgrade - HOWTO needed AMMullan Linux - General 37 02-27-2004 03:34 PM
howto upgrade glibc to 2.3.2 on S9.0? carboncopy Slackware 5 10-08-2003 04:28 AM


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