Re: grub2: update-grub generates broken grub.cfg when /boot is a separate partition

2007-05-10 Thread Robert Millan
On Wed, May 09, 2007 at 10:25:53PM +0200, Szántó Dániel wrote:
> On Wed, May 09, 2007 at 09:15:48AM +0200, Robert Millan wrote:
> > > ananasz:~# cat /proc/mounts 
> > > [...]
> > > /dev/sda1 /boot ext3 rw,data=ordered 0 0
> > 
> > Here it is.  /dev/sda1 _is_ the right device, but your grub.cfg is still 
> > wrong.
> > 
> > What do you see during boot?
> 
> What details should I give? The output of dmesg with the correct grub.cfg
> or the error message I get when trying to boot with the wrong one?

The error message.

> > Can you try "ln -s . /boot/boot" and confirm this works around the problem?
> 
> Nothing changes, after symlinking /boot to /boot/boot update-grub 
> generates exactly the same grub.cfg.

Does it boot now?

-- 
Robert Millan

My spam trap is [EMAIL PROTECTED]  Note: this address is only intended
for spam harvesters.  Writing to it will get you added to my black list.


___
Grub-devel mailing list
Grub-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/grub-devel


Re: pretty colors in gfxterm

2007-05-10 Thread Otavio Salvador
"Yoshinori K. Okuji" <[EMAIL PROTECTED]> writes:

>> Sorry but I didn't get what you mean by 'ad-hoc features' here. Can
>> you elaborate it, please?
>
> Features, which are not fully examined if they are generic, flexible and 
> extensible, are all ad-hoc. As I said in this list some times, I believe that 
> the user must be able to fully control how a menu (or a different kind of 
> user interface) should be displayed and provided, and style sheet support 
> meets this requirement. Of course, Marco's idea about more scripting-based 
> approach is also good, but I feel that this is rather overkill at the moment.

Ok, I agree with you.

-- 
O T A V I OS A L V A D O R
-
 E-mail: [EMAIL PROTECTED]  UIN: 5906116
 GNU/Linux User: 239058 GPG ID: 49A5F855
 Home Page: http://otavio.ossystems.com.br
-
"Microsoft sells you Windows ... Linux gives
 you the whole house."


___
Grub-devel mailing list
Grub-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/grub-devel


Re: Feature Request: in x86, the ability to boot an arbitrary bootable CD from a grub boot menu

2007-05-10 Thread Alex Roman

Actually, this is my project for the Google Summer of Code. I will be
working on GRUB2 to add CD-ROM booting functionality.

I will post more details during the course of the summer. Watch this
list for any updates.

On 07/05/07, Dustin Harriman <[EMAIL PROTECTED]> wrote:

Hello,

In the x86 world there is another boot loader somewhat similar to grub
called "Smart Boot Manager":
http://btmgr.sourceforge.net/about.html
Summary: "Smart Boot Manager (SBM) is an OS independent and
full-featured boot manager with an easy-to-use user interface.  SBM
now supports booting from CD-ROM."

SBM seems to have a killer feature that grub does not: the ability to
give a menu option to the end user at boot time to boot some bootable
CD.  In other words, when you have SBM installed in your MBR, you can
choose to boot a bootable CD, say to install Ubuntu, for example.  Can
grub do this?

I'm guessing not, as there is a tutorial on how to make a grub boot
menu entry to boot SBM to effectively allow this ability (having SBM
stored not in the MBR,
but from the root filesystem of, say, Ubuntu, much like memtest86 is done.)
Here is info on how to do that:
"GRUB/Chainloaded CD-ROM"
http://gentoo-wiki.com/TIP_Chainloading_a_bootable_CD-ROM_from_GRUB

I think it's really important for grub to have this ability to give an
option to boot an arbitrary bootable CD, like SMB has.  Why?  Because
end users, especially newbies/novice users should not have to access
BIOS whatsoever to be able to boot from a CD.  The main "use case" of
this killer feature, IMHO, would be to help make dead-easy installing
an alternative Operating System such as Ubuntu, or some other linux or
BSD variant.

Let me elaborate on the importance of this very important "use case"
(IMHO) of this requested feature:

Virtually all PCs now come from the factory having default BIOS
settings to NOT boot from CD before hard drive (which is
super-annoying).  So if a user boots their machine with an Ubuntu CD
in the drive, the CD will not boot (until they go into their BIOS to
change the boot order).

Consider the implications of these unfortunate-for-Ubuntu (et al) circumstances:
 -The special key (eg. F1, delete, etc.) one needs to press to enter
the BIOS is usually only shown when you tap Escape right at boot time.
 And you're not invited to press Escape.  You just magically need to
know to press it.  Therefore the BIOS is effectively completely hidden
from most users.  This makes it really tough for novice users to learn
about the existence of the BIOS, much less get inside it.
 -Most users have no idea what a BIOS is or how to access it.  And
they DO NOT want to learn.  It is too nebulous, technical, risky, and
uninteresting.
 -Of those who vaguely do know what a BIOS is, most are intimidated by
the BIOS and don't want to go in there whatsoever.
 -And even if users are brave enough to go into the BIOS, it's
impossible to give specific, procedural instructions in the Ubuntu (et
al) documentation as to how to modify the boot order, since all BIOS's
have different menus and controls.  All you can do is vaguely suggest
"search for a menu called something like Boot Order", and hope for the
best (ie. that the user doesn't give up on Ubuntu (et al))

So the BIOS presents a considerable technical roadblock to installing
Ubuntu (et al) for your average novice user (who is probably
installing an Operating System of any kind for the first time).  In
fact, the BIOS is probably the single most technically complex part of
the average Ubuntu (et al) install (by far), since the BIOS is such an
ugly, text-based, poorly-documented hell hole.  Therefore it must be
"smoothed over" at all costs!  No novice user should have to go in
there.

If and when grub gains this ability to boot an arbitrary boot CD (and
I'm just talking about x86 here, naturally), then perhaps as a next
step, someone could make a dead-simple Windows installer that puts
grub into the MBR, having two menu options: one to boot to Windows,
and one to boot from CD.  This menu option to boot from CD would make
it dead-easy for an end user to boot up an install CD for Ubuntu (et
al), allowing them to bypass the need to configure their BIOS.

Cheers,
Dustin Harriman

My Blog: http://ca.blog.360.yahoo.com/dustinharriman
RSS Feed: http://ca.blog.360.yahoo.com/rss-RkGSoVA1brWtXrVH9Gr5CzgVujwwGg--?cq=1

"Freedom is not the capacity to do whatever we please; freedom is the
capacity to make intelligent choices"  -Francis Moore Lappé


___
Grub-devel mailing list
Grub-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/grub-devel




--
Alex Roman <[EMAIL PROTECTED]>


___
Grub-devel mailing list
Grub-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/grub-devel


Re: grub2: update-grub generates broken grub.cfg when /boot is a separate partition

2007-05-10 Thread Robert Millan
On Thu, May 10, 2007 at 08:28:09PM +0200, Szántó Dániel wrote:
> On Thu, May 10, 2007 at 09:19:05AM +0200, Robert Millan wrote:
> > On Wed, May 09, 2007 at 10:25:53PM +0200, Szántó Dániel wrote:
> > > On Wed, May 09, 2007 at 09:15:48AM +0200, Robert Millan wrote:
> > 
> > > > Can you try "ln -s . /boot/boot" and confirm this works around the 
> > > > problem?
> > > 
> > > Nothing changes, after symlinking /boot to /boot/boot update-grub 
> > > generates exactly the same grub.cfg.
> > 
> > Does it boot now?
> 
> No,

Ah.  Well, I spotted a problem with update-grub not generating relative paths
when /boot is a separate partition.

But it seems you hit other bugs related with RAID.  I'm afraid I can't comment
on these.

> It gives the same error message:
>   Booting "Debian GNU/Linux, linux 2.6.20-1-amd64"
> 
> error: you need to load the kernel first
> 
> Press any key to continue...
> 
> If I edit the grub command line and settings to set root to hd0,0 and 
> the linux kernel paramter to root=/dev/md0, I get the same error if
> the cursor is below the last line. If the cursor is at the end of the 
> last line I get 
> error: Out of memory
> instead.
> I 
> DTR
> 

-- 
Robert Millan

My spam trap is [EMAIL PROTECTED]  Note: this address is only intended
for spam harvesters.  Writing to it will get you added to my black list.


___
Grub-devel mailing list
Grub-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/grub-devel