Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
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.
Need some assistance here, if anyone can help it would be much apperciated.
I downloaded the latest ubuntu 7 release and installed it onto a hdd of mine, all went fine. Came to boot it up and frooze on the very first little onranage sqaure of the boot progress bar on the splash/loading screen. Rebooted few times, same thing. So I assumed my harddrive was damaged.
Installed on an entirely new harddrive, exactly the same thing. So this time went into the recovery mode from grub, it falls over on
uniform cd-rom driver loaded
And some stuff about SCSI, but the scsi stuff was before that. I dont have scsi that im aware of? so i thought its odd. Anyway ...
so switched off, unplugged CD-ROM and rebooted. Still dies in same place. Went back into recovery off the grub menu, this time it dies on
attach scsi generic sg0 type0
Anyway assistance would be cool, cant wait to get my new unbuntu system going
I tried xubuntu-7.04 on an extra disk partition and did not let ubuntu install grub to my master boot sector and sent grub to install in the first sector on the extra partition where i installed it in, and then when the install finished i boot up Slackware and added xubuntu to Slackware's LILO (including the initrd.img) and it would die about half way through the boot process, i can not say for sure but i think it has to do with the way ubuntu identifies disk partitions using UUID, personally i think it is a blunder for ubuntu to implement UUID by default and ubuntu should just set that as an option so people can choose not to use after the install is finished because not everybody wants UUID to be the tool for identifying disk partitions...
all i can say is UUID is not a kernel thing for 2.6.20 & higher, it is a ubuntu thing, if you want to use ubuntu then you will have to do it ubuntu's way, i just want to clarify that it is not something part of the linux kernel...
I also have 2.6.20 kernels that still use hda, hdb, hdc and hdd. The implementation varies between distros. However if you are talking Ubuntu family then check out the fact first.
Take a look at Post #9 of this thread I just did on the subject. I did a thread to seek advice from the "village elders" there.
Just 15 minutes ago I inserted a spare 400Gb Pata disk, the only one, into my oldest PC, AMD Athlon 2800 on a Asus A7N8X-E mobo, and installed Fedora Core 6.93-i386. The root terminal shows
[root@localhost ~]# fdisk -l
Disk /dev/sda: 400.0 GB, 400088457216 bytes
255 heads, 63 sectors/track, 48641 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sda1 * 1 40000 321299968+ 83 Linux
/dev/sda2 40001 48641 69408832+ 82 Linux swap / Solaris
[root@localhost ~]# uname -a
Linux localhost.localdomain 2.6.20-1.3104.fc7 #1 SMP Sat Apr 21 22:20:43 EDT 2007 i686 athlon i386 GNU/Linux
[root@localhost ~]# cat /etc/fstab
LABEL=/1 / ext3 defaults 1 1
tmpfs /dev/shm tmpfs defaults 0 0
devpts /dev/pts devpts gid=5,mode=620 0 0
sysfs /sys sysfs defaults 0 0
proc /proc proc defaults 0 0
LABEL=SWAP-sda2 swap swap defaults 0 0
The Fedora has been installed into sda1. I am using it to reply this thread.
The changes in 2.6.20 kernel aren't bullshit. You either take it or leave it.
I think it would be helpful if users are aware of then and able to prepare for the changes.
I am probably one to suffer most because nearly all my Pata disks have 63 partitions and only 15 are supported by SCSI/Sata/USB disks. I can still use my disks as long as I boot to the distros with the older kernels.
it has the /dev/??? par commented out and a UUID number in its place, and grub's menu.1st has the same corresponding numbers for each disk partition, this probably works just fine on a PC that that has ubutnu installed by itself with ubuntu's grub boot loader on the MBR, but it will cause problems for users of other distros that want to install ubuntu in an extra disk partition and not use ubuntu's boot loader opting to keep their MBR intact, personally i think UUID is a blunder...
i said my $00.02 and will not be making anymore software contributions to ubuntu and any other distro that uses UUID in fstab & grub as i am not about to let another distro overwrite my MBR...
To boot a Linux we must supply the hard disk location in which the distro resides. There are several ways to identify the hard disk location.
(1) Conventional device name in Linux like /dev/sda1, /dev/hdc33 etc. This is used by the majority , possibly 80%, of the Linux I have seen.
(2) Put a label into the partition and boot to the label. This is widely used by the Red Hat family.
(3) A new trend of addressing the location by UUID reference which I don't know how to work out yet. This came out recently and spearheaded by Ubuntu family.
The advantage of the (2) & (3) is that they are immune to the current Pata disk name change. A village elder in JustLinux Forum believes Ubuntu switched to this route to phase in with the Pata disk name change.
The important thing about the whole issue is that we can override it by changing to any of the remaining 2 choices so there should be no necessity to complain if you do not like any one of them. I myself change the Ubuntu and Red Hat distros' ways of addressing as a matter of routine.
Also the the arrangement of one distro can hardy influence the other distros in the same disk or the same box, as I have permitted Ubuntu to boot to UUID way, Red Hat to boot labels while the majority use the method (1) above.
when and if UUID becomes mandatory on all Linux distros (especially slackware & Crux) is the day i either quit Linux and switch to BSD or toss my PCs out to the curb for the garbage collectors, i and i dont care what the UUbuntuID family does i am not buying it...