SlackwareThis Forum is for the discussion of Slackware Linux.
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.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I had to update a Slackware 10.0 full install to Slackware 12.
First thing - I have comiled and succesfully installed 18.104.22.168 - rebooted - everything was fine on Slack 10 with 2.6 kernel.
Then i copyed files from slack 12 DVD on my harddisk - telinit 1 and followed steps from changes_and_hints. In the last step I have updated only rc.M and inittab.
After reboot - I got :
/sbin/e2fsck : No such file or directory while trying to open /dev/hda1 ( this is my / partition )
after I logint to sstem maintenance ;
The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 filesystem ( and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock:
Did that with all 3 values - same result as above.
Rebooted from CD - I run e2fsck on /dev/hda1 - everything is fine ( once it told me that superblock was modified in the future- and answered yes to fix )
I can see all the files in place...but this machine doesn't boot..
On this console
fdisk /dev/hda gives "unable to open /dev/hda" but I can mount rw /dev/hda1....
If I exclude the fact that I haven't taken care of .new files everything went smoothly. I had a little problem with upgrading to mysql 5 ( a matter of permissions on /var/lib/mysql* ) but fixed quickly. So in my case upgrade from 10 to 12 worked well. Anyway I guess reistall could reduce the amount of time.