On Sun, 12 May 2013 07:40:15 -0500, Dale wrote:

> > I don't know about memtest86, but memtest86+ installs a menu file
> > in /etc/grub.d, which means grub-mkconfig handles it.
> >
> > % cat /etc/grub.d/39_memtest86+
> > #!/bin/sh
> > exec tail -n +3 $0
> >
> > menuentry "memtest86+ 4.20" {
> >         linux16 /boot/memtest86plus/memtest
> > }
> >
> > menuentry "memtest86+ 4.20 (netbsd)" {
> >         insmod bsd
> >         knetbsd /boot/memtest86plus/memtest.netbsd
> > }
> 
> That is what I did last.  I just emerged the thing and it put the file
> there.  You know I don't reboot often here but this is what it says
> when I update grub:
> 
> root@fireball / # /root/grub-update
> Generating grub.cfg ...
> Found linux image: /boot/kernel-3.8.7-1
> Found linux image: /boot/kernel-3.6.6-1
> Found linux image: /boot/kernel-3.5.3-3
> done
> root@fireball / #
> 
> Shouldn't there be a line for the memtest entry or does it not show
> that?  Maybe it is working and I don't know it yet.  lol

There are no echo commands in the file, so it doesn't show anything when
adding. grub-mkconfig doesn't output anything by default, only the helper
scripts generate non-error output

Check the contents of grub.cfg.

> Oh, I have a script that has the longer command in it with all the nifty
> options.  That's why the command is different.
> 
> root@fireball / # cat /root/grub-update
>  
> grub2-mkconfig -o /boot/grub2/grub.cfg

I do a similar thing, except the script is in /usr/local/bin, where it
should be :P, and it checks if /boot is mounted ro and remounts it rw if
necessary.


-- 
Neil Bothwick

WinErr 019: User error - Not our fault. Is Not! Is Not!