Arch Linux

perbh

Member

From: Republic of Texas

Registered: 2005-03-04

Posts: 765

Re: [Solved] Burning CD now - so real newbie questions concerns.

*lol*
Bruce - you have given me such a good laugh reading this - you are soooo darned close - and funny to boot!!

Your problems above is _exactly_ the reason why I prefer /dev/sdaX to uuid. The uuid will change if you change the filesystem on that particular partition. Seeing you (obviously) has a fairly large disk (many partitions) and it probably will be your main disk for a long time yet - then I would use /dev/sdaX.
uuid is useful if you are in the habit of kicking disks around, changing them or do anything that might stop your current disk from being /dev/sda. Also - if you are in the habit of booting from a usb-pen, then you might have the problem twofold:
1) grub will look upon your usb-pen as (hd0) and will load your kernel and initrd from there.
2) However, once your kernel is loaded, then this will change and your fixed disk will be /dev/sda and your usb-pen will be /dev/sdb

Confusing? Yup!

For the time being, though - and until you are vastly more comfortable - the following menu.lst should work:

default 0
timeout 10
title archlinux
  root (hd0,7)
  kernel /boot/vmlinuz26 ro root=/dev/sda8 vga=771   # some 'small' lcd's might have a problem with vga=773
  initrd /boot/kernel26.img
title Ubuntu 8.10, kernel 2.6.27-14-generic
  root (hd0,0)
  kernel /boot/vmlinuz-2.6.27-14-generic ro root=/dev/sda1 vga=771 
  initrd /boot/initrd.img-2.6.27-14-generic

The above should be all you really need - and it doesn't matter which fs you use!!
Then you can always later add in the 'recovery' and 'fallback' options and all those other 'good' things ...

Bruce_M

Member

From: Buenos Aires, Arg

Registered: 2009-09-21

Posts: 27

Website

Re: [Solved] Burning CD now - so real newbie questions concerns.

*lol*

Are you laughing at ME!

Bruce - you have given me such a good laugh reading this - you are soooo darned close - and funny to boot!!

Wonderful, colour my day successful - I made someone laugh. 

Your problems above is _exactly_ the reason why I prefer /dev/sdaX to uuid. The uuid will change if you change the filesystem on that particular partition. Seeing you (obviously) has a fairly large disk (many partitions) and it probably will be your main disk for a long time yet - then I would use /dev/sdaX.
uuid is useful if you are in the habit of kicking disks around, changing them or do anything that might stop your current disk from being /dev/sda. Also - if you are in the habit of booting from a usb-pen, then you might have the problem twofold:
1) grub will look upon your usb-pen as (hd0) and will load your kernel and initrd from there.
2) However, once your kernel is loaded, then this will change and your fixed disk will be /dev/sda and your usb-pen will be /dev/sdb

Confusing? Yup!

What is even more confusing - I don't even own a USB-pen drive.

For the time being, though - and until you are vastly more comfortable - the following menu.lst should work:

default 0
timeout 10
title archlinux
  root (hd0,7)
  kernel /boot/vmlinuz26 ro root=/dev/sda8 vga=771   # some 'small' lcd's might have a problem with vga=773
  initrd /boot/kernel26.img
title Ubuntu 8.10, kernel 2.6.27-14-generic
  root (hd0,0)
  kernel /boot/vmlinuz-2.6.27-14-generic ro root=/dev/sda1 vga=771 
  initrd /boot/initrd.img-2.6.27-14-generic

The above should be all you really need - and it doesn't matter which fs you use!!
Then you can always later add in the 'recovery' and 'fallback' options and all those other 'good' things ...

Here is what I have for my menu.lst for Ubuntu 8.10 (default stuff snipped out) and it's not working:

## should update-grub add savedefault to the default options
## can be true or false
# savedefault=false

## ## End Default Options ##

title        Ubuntu 8.10, kernel 2.6.27-14-generic
uuid        ae70c594-8586-4814-9447-7e4213c43736
kernel        /boot/vmlinuz-2.6.27-14-generic root=UUID=ae70c594-8586-4814-9447-7e4213c43736 ro quiet splash 
initrd        /boot/initrd.img-2.6.27-14-generic
quiet

title        Ubuntu 8.10, kernel 2.6.27-14-generic (recovery mode)
uuid        ae70c594-8586-4814-9447-7e4213c43736
kernel        /boot/vmlinuz-2.6.27-14-generic root=UUID=ae70c594-8586-4814-9447-7e4213c43736 ro  single
initrd        /boot/initrd.img-2.6.27-14-generic

title        Ubuntu 8.10, kernel 2.6.27-7-generic
uuid        ae70c594-8586-4814-9447-7e4213c43736
kernel        /boot/vmlinuz-2.6.27-7-generic root=UUID=ae70c594-8586-4814-9447-7e4213c43736 ro quiet splash 
initrd        /boot/initrd.img-2.6.27-7-generic
quiet

title        Ubuntu 8.10, kernel 2.6.27-7-generic (recovery mode)
uuid        ae70c594-8586-4814-9447-7e4213c43736
kernel        /boot/vmlinuz-2.6.27-7-generic root=UUID=ae70c594-8586-4814-9447-7e4213c43736 ro  single
initrd        /boot/initrd.img-2.6.27-7-generic

title        Ubuntu 8.10, memtest86+
uuid        ae70c594-8586-4814-9447-7e4213c43736
kernel        /boot/memtest86+.bin
quiet

### END DEBIAN AUTOMAGIC KERNELS LIST
title   Other Linux Systems:
root

# (0) Arch Linux
title  Arch Linux
root   (hd0,5)
kernel /boot/vmlinuz26 root=/dev/disk/by-uuid/5d39b4e2-8e98-4712-b5c9-62f2ca1cfc2d ro vga=773
initrd /boot/kernel26.img

# (1) Arch Linux
title  Arch Linux Fallback
root   (hd0,5)
kernel /boot/vmlinuz26 root=/dev/disk/by-uuid/5d39b4e2-8e98-4712-b5c9-62f2ca1cfc2d ro vga=773
initrd /boot/kernel26-fallback.img

Keep in mind:

sda6 = /  (ARCH)
sda7 = /home (ARCH) - nothing there yet except "lost and found"
sda8 = empty - to be mounted and used by me. 

Once ARCH is configured and running nicely - sda1, 2 will be deleted (Xubu),  and 5 = 8 - used by me

Here (verbatim) is what I put up in another forum:

OK, here I am - Xubuntu 9.04 Live CD.  Pulled a few tricks to get to see my ARCH partitions:

To run a command as administrator (user "root"), use "sudo <command>".
See "man sudo_root" for details.

ubuntu@ubuntu:~$ sudo mkdir /media/6
ubuntu@ubuntu:~$ sudo mkdir /media/7
ubuntu@ubuntu:~$ sudo mkdir /media/8
ubuntu@ubuntu:~$ sudo mount -t ext4 /dev/sda6 /media/6
ubuntu@ubuntu:~$ sudo mount -t ext4 /dev/sda7 /media/7
ubuntu@ubuntu:~$ sudo mount -t ext4 /dev/sda8 /media/8
ubuntu@ubuntu:~$ cd /media/6
ubuntu@ubuntu:/media/6$ ls
bin   dev  home  lib64       media  opt   root  srv  tmp  var
boot  etc  lib   lost+found  mnt    proc  sbin  sys  usr
ubuntu@ubuntu:~$ cd /media/7
ubuntu@ubuntu:/media/7$ ls
lost+found
ubuntu@ubuntu:/media/7$ cd 
ubuntu@ubuntu:~$ sudo mkdir /media/5
ubuntu@ubuntu:~$ sudo mount -t ext3 /dev/sda5 /media/58
mount: mount point /media/58 does not exist
ubuntu@ubuntu:~$ sudo mount -t ext3 /dev/sda5 /media/5
ubuntu@ubuntu:~$ cd /media/6
ubuntu@ubuntu:/media/6$ cd boot
ubuntu@ubuntu:/media/6/boot$ ls
grub  kernel26-fallback.img  kernel26.img  System.map26  vmlinuz26
ubuntu@ubuntu:/media/6/boot$ cd grub
ubuntu@ubuntu:/media/6/boot/grub$ ls
e2fs_stage1_5     jfs_stage1_5       stage1           vstafs_stage1_5
fat_stage1_5      menu.lst           stage2           xfs_stage1_5
ffs_stage1_5      minix_stage1_5     stage2_eltorito
iso9660_stage1_5  reiserfs_stage1_5  ufs2_stage1_5
ubuntu@ubuntu:/media/6/boot/grub$ mousepad menu.lst

--------------------
To save mousepad text file on /media/5:

ubuntu@ubuntu:~$ sudo chown ubuntu:ubuntu /media/5
ubuntu@ubuntu:~$ sudo chmod 777 /media/5
ubuntu@ubuntu:~$

OK, so here it is:

# Config file for GRUB - The GNU GRand Unified Bootloader
# /boot/grub/menu.lst

# DEVICE NAME CONVERSIONS 
#
#  Linux           Grub
# -------------------------
#  /dev/fd0        (fd0)
#  /dev/sda        (hd0)
#  /dev/sdb2       (hd1,1)
#  /dev/sda3       (hd0,2)
#

#  FRAMEBUFFER RESOLUTION SETTINGS
#     +-------------------------------------------------+
#          | 640x480    800x600    1024x768   1280x1024
#      ----+--------------------------------------------
#      256 | 0x301=769  0x303=771  0x305=773   0x307=775
#      32K | 0x310=784  0x313=787  0x316=790   0x319=793
#      64K | 0x311=785  0x314=788  0x317=791   0x31A=794
#      16M | 0x312=786  0x315=789  0x318=792   0x31B=795
#     +-------------------------------------------------+
#  for more details and different resolutions see
#  http://wiki.archlinux.org/index.php/GRUB#Framebuffer_Resolution 

# general configuration:
timeout   5
default   0
color light-blue/black light-cyan/blue

# boot sections follow
# each is implicitly numbered from 0 in the order of appearance below
#
# TIP: If you want a 1024x768 framebuffer, add "vga=773" to your kernel line.
#
#-*

# (0) Arch Linux
title  Arch Linux
root   (hd0,5)
kernel /boot/vmlinuz26 root=/dev/disk/by-uuid/5d39b4e2-8e98-4712-b5c9-62f2ca1cfc2d ro
initrd /boot/kernel26.img

# (1) Arch Linux
title  Arch Linux Fallback
root   (hd0,5)
kernel /boot/vmlinuz26 root=/dev/disk/by-uuid/5d39b4e2-8e98-4712-b5c9-62f2ca1cfc2d ro
initrd /boot/kernel26-fallback.img

# (2) Windows
#title Windows
#rootnoverify (hd0,0)
#makeactive
#chainloader +1

Now my menu.lst for Ubuntu 8.10 (default stuff snipped out):

## should update-grub add savedefault to the default options
## can be true or false
# savedefault=false

## ## End Default Options ##

title        Ubuntu 8.10, kernel 2.6.27-14-generic
uuid        ae70c594-8586-4814-9447-7e4213c43736
kernel        /boot/vmlinuz-2.6.27-14-generic root=UUID=ae70c594-8586-4814-9447-7e4213c43736 ro quiet splash 
initrd        /boot/initrd.img-2.6.27-14-generic
quiet

title        Ubuntu 8.10, kernel 2.6.27-14-generic (recovery mode)
uuid        ae70c594-8586-4814-9447-7e4213c43736
kernel        /boot/vmlinuz-2.6.27-14-generic root=UUID=ae70c594-8586-4814-9447-7e4213c43736 ro  single
initrd        /boot/initrd.img-2.6.27-14-generic

title        Ubuntu 8.10, kernel 2.6.27-7-generic
uuid        ae70c594-8586-4814-9447-7e4213c43736
kernel        /boot/vmlinuz-2.6.27-7-generic root=UUID=ae70c594-8586-4814-9447-7e4213c43736 ro quiet splash 
initrd        /boot/initrd.img-2.6.27-7-generic
quiet

title        Ubuntu 8.10, kernel 2.6.27-7-generic (recovery mode)
uuid        ae70c594-8586-4814-9447-7e4213c43736
kernel        /boot/vmlinuz-2.6.27-7-generic root=UUID=ae70c594-8586-4814-9447-7e4213c43736 ro  single
initrd        /boot/initrd.img-2.6.27-7-generic

title        Ubuntu 8.10, memtest86+
uuid        ae70c594-8586-4814-9447-7e4213c43736
kernel        /boot/memtest86+.bin
quiet

### END DEBIAN AUTOMAGIC KERNELS LIST
title   Other Linux Systems:
root

# (0) Arch Linux
title  Arch Linux
root   (hd0,5)
kernel /boot/vmlinuz26 root=/dev/disk/by-uuid/5d39b4e2-8e98-4712-b5c9-62f2ca1cfc2d ro vga=773
initrd /boot/kernel26.img

# (1) Arch Linux
title  Arch Linux Fallback
root   (hd0,5)
kernel /boot/vmlinuz26 root=/dev/disk/by-uuid/5d39b4e2-8e98-4712-b5c9-62f2ca1cfc2d ro vga=773
initrd /boot/kernel26-fallback.img

But ARCH will not load. 

Any help? Honest - no pink 

CHIMO!
Bruce
---------------------------

PS: Going to get out of this LIVE CD session and try that sda6 (hd0,5) stuff though. I never did like when Ubuntu switched to that UUID stuff.

Thanks

---

Architecturally speaking in every arch there is a keystone!
In ARCHlinux it's KISS - = Keeping It Supported Stone = -
Does that make ARCH the Keystone of Linux?

Bruce_M

Member

From: Buenos Aires, Arg

Registered: 2009-09-21

Posts: 27

Website

Re: [Solved] Burning CD now - so real newbie questions concerns.

*lol*

For the time being, though - and until you are vastly more comfortable - the following menu.lst should work:

default 0
timeout 10
title archlinux
  root (hd0,7)
  kernel /boot/vmlinuz26 ro root=/dev/sda8 vga=771   # some 'small' lcd's might have a problem with vga=773
  initrd /boot/kernel26.img
title Ubuntu 8.10, kernel 2.6.27-14-generic
  root (hd0,0)
  kernel /boot/vmlinuz-2.6.27-14-generic ro root=/dev/sda1 vga=771 
  initrd /boot/initrd.img-2.6.27-14-generic

The above should be all you really need - and it doesn't matter which fs you use!!
Then you can always later add in the 'recovery' and 'fallback' options and all those other 'good' things ...

Well that didn't work I get:

ERROR 15: File not found

?????

What do I have to do?

Install ARCH then install Ubuntu because Ubuntu will see and recognize RCH's GRUB: 

---

Architecturally speaking in every arch there is a keystone!
In ARCHlinux it's KISS - = Keeping It Supported Stone = -
Does that make ARCH the Keystone of Linux?

Gen2ly

Member

From: Sevierville, TN

Registered: 2009-03-06

Posts: 1,529

Website

Re: [Solved] Burning CD now - so real newbie questions concerns.

Yeah... you're getting there.  Humbly, I refer to the wiki tutorial about grub auto-completion, just to be drive/partition just right.  Notsure.

---

Setting Up a Scripting Environment | Proud donor to wikipedia - link

Bruce_M

Member

From: Buenos Aires, Arg

Registered: 2009-09-21

Posts: 27

Website

Re: [Solved] Burning CD now - so real newbie questions concerns.

Yeah... you're getting there.  Humbly, I refer to the wiki tutorial about grub auto-completion, just to be drive/partition just right.  Notsure.

Thanks for the link and your help.

I'm a patient man, I have something that works (?¿) so no rush, but I'm puzzled by this. I've installed: Ubuntu-Xubuntu -different versions - 32 & 64bit many times, Debian Lenny twice & Dreamlinux 5 or 6 times - with chainloading et al  and never had this problem.

But I read here somewhere that ARCH doesn't "see" other distros or OS's when installing GRUB, this is a bad thing in my opinion (just an opinion) considering all the great things I've heard about ARCH.  Maybe something that needs changing with ARCH.

Boy, talk about a brass pair, haven't even got it installed and I'm suggesting a change.  But, consider this; on word of mouth, posts, reading, etc., I'm preparing to dump the only Linux I really know well, for one I can't get to boot up.  That has to say something about the things I've heard about ARCH. 

Have a great day, and thanks again.
Bruce

---

Architecturally speaking in every arch there is a keystone!
In ARCHlinux it's KISS - = Keeping It Supported Stone = -
Does that make ARCH the Keystone of Linux?

stryder

Member

Registered: 2009-02-28

Posts: 500

Re: [Solved] Burning CD now - so real newbie questions concerns.

I have not used ext4 so I cannot say anything about it's use with respect to grub, and in your case, ubuntu's grub. So let me just make a few observations that might be useful. Ubuntu's menu list has  a different format - perhaps you can try using that format. Secondly your use of chainloading in the menu.lst you showed in the previous page - chainload was spelt wrongly. Maybe that was an issue. Thirdly in using perbh's suggestion I wonder if you have changed sda8 to sda6. Finally in changing the file format to ext4 and moving root to sda6 from sda8 I wondered if you had re-installed or you merely copied arch over. And before you boot from the grub menu, you should check the commands to make sure that you are using the menu.lst you intend - I have different installations too and sometimes I amend the wrong menu.lst.

*edit* Wonder whether this guy's experience will be relevant. He found that debian could not recognize ext4. Overwriting the MBR using arch solved the problem.

Last edited by stryder (2009-09-26 06:40:42)

ngoonee

Forum Fellow

From: Between Thailand and Singapore

Registered: 2009-03-17

Posts: 7,354

Re: [Solved] Burning CD now - so real newbie questions concerns.

Yeah... you're getting there.  Humbly, I refer to the wiki tutorial about grub auto-completion, just to be drive/partition just right.  Notsure.

Thanks for the link and your help.

I'm a patient man, I have something that works (?¿) so no rush, but I'm puzzled by this. I've installed: Ubuntu-Xubuntu -different versions - 32 & 64bit many times, Debian Lenny twice & Dreamlinux 5 or 6 times - with chainloading et al  and never had this problem.

But I read here somewhere that ARCH doesn't "see" other distros or OS's when installing GRUB, this is a bad thing in my opinion (just an opinion) considering all the great things I've heard about ARCH.  Maybe something that needs changing with ARCH.

Boy, talk about a brass pair, haven't even got it installed and I'm suggesting a change.  But, consider this; on word of mouth, posts, reading, etc., I'm preparing to dump the only Linux I really know well, for one I can't get to boot up.  That has to say something about the things I've heard about ARCH. 

Have a great day, and thanks again.
Bruce

Hi Bruce.

Arch's installer does not set grub up with auto-recognition of other distros, if any, on the computer. Like many other things in Arch, the idea is to KISS, which means you should only have a long menu.lst if you need it. Isn't too hard to just add chainloading in.

---

Allan-Volunteer on the (topic being discussed) mailn lists. You never get the people who matters attention on the forums.
jasonwryan-Installing Arch is a measure of your literacy. Maintaining Arch is a measure of your diligence. Contributing to Arch is a measure of your competence.
Griemak-Bleeding edge, not bleeding flat. Edge denotes falls will occur from time to time. Bring your own parachute.

Bruce_M

Member

From: Buenos Aires, Arg

Registered: 2009-09-21

Posts: 27

Website

Re: [Solved] Burning CD now - so real newbie questions concerns.

I have not used ext4 so I cannot say anything about it's use with respect to grub, and in your case, ubuntu's grub. So let me just make a few observations that might be useful. Ubuntu's menu list has  a different format - perhaps you can try using that format. Secondly your use of chainloading in the menu.lst you showed in the previous page - chainload was spelt wrongly. Maybe that was an issue. Thirdly in using perbh's suggestion I wonder if you have changed sda8 to sda6. Finally in changing the file format to ext4 and moving root to sda6 from sda8 I wondered if you had re-installed or you merely copied arch over. And before you boot from the grub menu, you should check the commands to make sure that you are using the menu.lst you intend - I have different installations too and sometimes I amend the wrong menu.lst.

*edit* Wonder whether this guy's experience will be relevant. He found that debian could not recognize ext4. Overwriting the MBR using arch solved the problem.

Hi stryder,

perbh suggested a way of changing even the Ubuntu way of doing things (which I like as I don't care for the UUID method) in GRUB:

default 0
timeout 10
title archlinux
  root (hd0,7)
  kernel /boot/vmlinuz26 ro root=/dev/sda8 vga=771   # some 'small' lcd's might have a problem with vga=773
  initrd /boot/kernel26.img
title Ubuntu 8.10, kernel 2.6.27-14-generic
  root (hd0,0)
  kernel /boot/vmlinuz-2.6.27-14-generic ro root=/dev/sda1 vga=771 
  initrd /boot/initrd.img-2.6.27-14-generic

I didn't mess with the Xubu part as I didn't want to "bork" Xubu.  But ARCH still didn't work

As to changing sda8 to sda6 - that came about like this:

Originally I had:

sda1 - Xubu 8.10 - /
sda2 - Xubu 8.10 - /home
sda3 - SWAP
sda4 - Extended
- sda5 - /media/5 - My backups and other stuff.
- sda6 - Xubu 8.04-3 - /
- sda7 - Xubu 8.04-3 - /home
- sda8 - empty - formatted ext3
- sda9 - empty - formatted ext3
- sda10 - empty - formatted ext3
- sda11 - empty - formatted ext3

so I installed ARCH / on sda8 and /home on sda9.

When that didn't work I popped in the Xubu 9.04 Live CD and "deleted" sda6, 7, 8, 9, 10 & 11 and created:

sda6 - ext4
sda7 - ext4
sda8 - ext4

And installed ARCH again on sda6 - / and sda7 - /home

Since ARCH doesn't see other distros I told the install process to place grub on "sda6" - and that's where I think things messed up.

The ext4 issue was addressed just this morning in another forum.  I need to use "rootfs=ext4" like this:

kernel /boot/vmlinuz26 rootfs=ext4 root=/dev/sda6 ro vga=771

as GRUB (on hd0,0) is on an ext3 partition and ARCH's / is on (hd0,5) sda6

However that still came up with an ERROR 15: file not found.

I think what I will do today is:

1. backup all my personal stuff to /media/5 and put a tar.gz backup of home on a DVD
2. reinstall ARCH - sda6 / & sda7 /home & mounting sda8 then place the GRUB on hd0,0
- Will GRUB see it's going on an ext3 partition and pointing to an ext4 partition? Don't know - yet.
3. reinstall Xubu on sda1, sda2 and mount sda5

"I will have ARCH!"

Have a nice day.
Bruce

EDIT: Just saw your edit.  Hmmmmmmmmmm, interesting. May have to re-plan things. Xubu 9.04 does see and use ext4, but it's an alpha release - although I'm using it just to get my stuff working. 

- reinstall ARCH GRUB sounds good, then reconstruct the Xubu entries. 

Time to think and plan a new stratagy
Thanks.

Bruce

Last edited by Bruce_M (2009-09-26 12:10:30)

---

Architecturally speaking in every arch there is a keystone!
In ARCHlinux it's KISS - = Keeping It Supported Stone = -
Does that make ARCH the Keystone of Linux?

.:B:.

Forum Fellow

Registered: 2006-11-26

Posts: 5,819

Website

Re: [Solved] Burning CD now - so real newbie questions concerns.

It doesn't load Arch though. 
And Xubu can't read the ext4 partitions.

Still working on it. 
I'll have ARCH or die tryin'!!

Well I hope you'll do better than 50 Cent .

Shylock's snippet should help you out, you still need to point GRUB to the kernel. Your root line should be correct.

---

Got Leenucks? :: Arch: Power in simplicity :: Get Counted! Registered Linux User #392717 :: Blog thingy

Bruce_M

Member

From: Buenos Aires, Arg

Registered: 2009-09-21

Posts: 27

Website

Re: [Solved] Burning CD now - so real newbie questions concerns.

It doesn't load Arch though. 
And Xubu can't read the ext4 partitions.

Still working on it. 
I'll have ARCH or die tryin'!!

Well I hope you'll do better than 50 Cent .

Shylock's snippet should help you out, you still need to point GRUB to the kernel. Your root line should be correct.

Hi B

Not sure what you mean by 50 cent?

Syylock said:

# (0) Arch Linux
title  Arch Linux (Main)
root   (hd0,7)
kernel /boot/vmlinuz26 root=/dev/sda8 ro vga=773
initrd /boot/kernel26.img

I tried (ARCH - / = sda6):

# (0) Arch Linux
title  Arch Linux
root   (hd0,5)
kernel /boot/vmlinuz26 root=/dev/sda6 ro vga=771
initrd /boot/kernel26.img

When that didn't work I tried (rootfs=ext4):

# (0) Arch Linux
title  Arch Linux
root   (hd0,5)
kernel /boot/vmlinuz26 rootfs=ext4 root=/dev/sda6 ro vga=771
initrd /boot/kernel26.img

I need a new plan of attack, this is a battle I will not loose!
Did you ever want something bad enough that you could taste it!
That's where I am. 

Another though - maybe the install didn't go as well as I thought although everything looked good, no error messages and looking at things from the LiveCD session showed everything there. {sigh}

Have a nice day.
Bruce

ADD ON: one last thought---------

Copy the ARCH GRUB menu.lst over the Xubu menu lst - ending it with:

title Other OS

  title Ubuntu 8.10, kernel 2.6.27-14-generic
  root (hd0,0)
  kernel /boot/vmlinuz-2.6.27-14-generic ro root=/dev/sda1 vga=771 
  initrd /boot/initrd.img-2.6.27-14-generic

just to be safe.

---

Architecturally speaking in every arch there is a keystone!
In ARCHlinux it's KISS - = Keeping It Supported Stone = -
Does that make ARCH the Keystone of Linux?

Bruce_M

Member

From: Buenos Aires, Arg

Registered: 2009-09-21

Posts: 27

Website

Re: [Solved] Burning CD now - so real newbie questions concerns.

HUSTON We have ARCH!

On boot I see:
-----------
ARCH Linux 2.6.30-ARCH (myhost) (tty1)
myhost login:
-----------
before I go further I'd like to thank, in order of appearance (is this a movie?):

slightlystoopid, stryder, ngoonee, *david_a*, Xyne, Gen2ly, Diaz, sHyLoCk, perbh & B

with a special mention for perbh cuz I made him laugh and it made my day.

You all helped A LOT!

I tried "everything" and ARCH, while there would NOT boot.
Soooo - taking the advice to add "rootfs=ext4" I though why not!!!!

1. BACKED UP system to /media/5 and copied to DVD!

2.. Reinstalled ARCH:
- sda3 - SWAP
- sda6 - ext4 - / (reformat)
- sda7 - ext4 ~/ (reformat)
- sda8 - ext4 /media/8 (reformat)
- installed GRUB to MBR (hd0,0)

3. Fresh install of Xubu 9.04 Alpha6 (ext4 compatible) on:
- sda1 - ext4 - / (reformat)
- sda2 - ext4 ~/ (reformat)
- sda3 - SWAP
- sda5 - ext3 - /media/5 (did NOT reformat)
- sda6 - mount = /media/AR (did NOT reformat)
- sda7 - mount = /media/AH (did NOT reformat)
- sda6 - mount = /media/8 (did NOT reformat)

Xubu 9.04 Krazy Koala - sorry - Karmic Koala is updating in the background.

And my menu.lst (snipping out 130 lines of stuff commented out):

## ## End Default Options ##

title        Ubuntu 9.04, kernel 2.6.28-11-generic
uuid        1d35146c-07a2-4c28-8d17-7a50945af09a
kernel        /boot/vmlinuz-2.6.28-11-generic root=UUID=1d35146c-07a2-4c28-8d17-7a50945af09a ro quiet splash 
initrd        /boot/initrd.img-2.6.28-11-generic
quiet

title        Ubuntu 9.04, kernel 2.6.28-11-generic (recovery mode)
uuid        1d35146c-07a2-4c28-8d17-7a50945af09a
kernel        /boot/vmlinuz-2.6.28-11-generic root=UUID=1d35146c-07a2-4c28-8d17-7a50945af09a ro  single
initrd        /boot/initrd.img-2.6.28-11-generic

title        Ubuntu 9.04, memtest86+
uuid        1d35146c-07a2-4c28-8d17-7a50945af09a
kernel        /boot/memtest86+.bin
quiet

### END DEBIAN AUTOMAGIC KERNELS LIST

# This is a divider, added to separate the menu items below from the Debian
# ones.
title        Other operating systems:
root


# This entry automatically added by the Debian installer for an existing
# linux installation on /dev/sda6.
title        Arch Linux (on /dev/sda6)
root        (hd0,5)
kernel        /boot/vmlinuz26 rootfs=ext4 root=/dev/sda6 ro 
initrd        /boot/kernel26.img
savedefault
boot


# This entry automatically added by the Debian installer for an existing
# linux installation on /dev/sda6.
title        Arch Linux Fallback (on /dev/sda6)
root        (hd0,5)
kernel        /boot/vmlinuz26 rootfs=ext4 root=/dev/sda6 ro 
initrd        /boot/kernel26-fallback.img
savedefault
boot

Oh and as a side note: I cannot believe how fast Xubu KK is on steroids (ext4)

OK, now to do start configuring ARCH! 

I'll be back, but not in this thread.
Have a GREAT day.
Bruce

EDIT:  Second time I put this here - ISP problems!!!!

---

Architecturally speaking in every arch there is a keystone!
In ARCHlinux it's KISS - = Keeping It Supported Stone = -
Does that make ARCH the Keystone of Linux?