I just installed 10.04.
Had a little trouble logging in but recovery mode > startx seemed to do the trick.
However, since I went after a multi boot alongside slackware with both OSs sharing /home I seem to have a few problems.
I'll outline my install first :
Partitioned /dev/hda1 2GB swap
/dev/hda2 20 GB / for Kubuntu
/dev/hda3 20 GB / for Slackware
/dev/hda4 rest of 400 GB for home.
Installed Slackware's root and swap first with lilo on the root partition.
Next I installed Kubuntu with Grub2 to the MBR.
Then rebooted, chose Kubuntu (slackware is available in the list as well) and created a group id to which I joined my user id.
Then kdesudo kate /etc/fstab to auto mount home and add "grpid" to the end of the /dev/hda4 (the /home partition).
However, when I opened /etc/fstab I had no entry for /dev/hda4 or the Slackware partition...
I've obviously messed something simple up but I've no idea where to start. I tried
which I thought would print out a list of my partitions but nothing seemed to happen.
Here's a copy of my /etc/fstab
thanks
mike
Had a little trouble logging in but recovery mode > startx seemed to do the trick.
However, since I went after a multi boot alongside slackware with both OSs sharing /home I seem to have a few problems.
I'll outline my install first :
Partitioned /dev/hda1 2GB swap
/dev/hda2 20 GB / for Kubuntu
/dev/hda3 20 GB / for Slackware
/dev/hda4 rest of 400 GB for home.
Installed Slackware's root and swap first with lilo on the root partition.
Next I installed Kubuntu with Grub2 to the MBR.
Then rebooted, chose Kubuntu (slackware is available in the list as well) and created a group id to which I joined my user id.
Then kdesudo kate /etc/fstab to auto mount home and add "grpid" to the end of the /dev/hda4 (the /home partition).
However, when I opened /etc/fstab I had no entry for /dev/hda4 or the Slackware partition...
I've obviously messed something simple up but I've no idea where to start. I tried
Code:
fdisk -lu
Here's a copy of my /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid -o value -s UUID' to print the universally unique identifier
# for a device; this may be used with UUID= as a more robust way to name
# devices that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc nodev,noexec,nosuid 0 0
# / was on /dev/sda2 during installation
UUID=91469099-9f4e-4a49-a681-78f2693ca354 / ext3 errors=remount-ro 0 1
# swap was on /dev/sda1 during installation
UUID=46122171-e822-486c-bf30-2baad8a12335 none swap sw 0 0
/dev/fd0 /media/floppy0 auto rw,user,noauto,exec,utf8 0 0
#
# Use 'blkid -o value -s UUID' to print the universally unique identifier
# for a device; this may be used with UUID= as a more robust way to name
# devices that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc nodev,noexec,nosuid 0 0
# / was on /dev/sda2 during installation
UUID=91469099-9f4e-4a49-a681-78f2693ca354 / ext3 errors=remount-ro 0 1
# swap was on /dev/sda1 during installation
UUID=46122171-e822-486c-bf30-2baad8a12335 none swap sw 0 0
/dev/fd0 /media/floppy0 auto rw,user,noauto,exec,utf8 0 0
mike
Comment