from:"adrian15"

El 16/03/14 08:04, Andrey Borzenkov escribió:

В Sun, 16 Mar 2014 06:56:46 +0100
adrian15 adrian15...@gmail.com пишет:

To be honest, I do not understand what you are trying to do here.

The same thing as in:

https://forja.cenatic.es/plugins/scmgit/cgi-bin/gitweb.cgi?p=supergrub2/supergrub2.git;a=blob_plain;f=supergrub-meta-mkrescue;hb=22683e2b5fa0d65141c1be1a7487914b1d43f4dd

(which uses Debian packages) but using source code.

Why would you want to build separate ISO for every platform? The whole
point of using grub-mkrescue is to create single ISO image that
supports and can be booted on all platforms.

Because I want to support all the GRUB2 platforms but not having a
single 60 MB (random size guess) download for that.

The other reason is because a: i386-efi + x86_64_efi + x86_pc hybrid did
not boot in a x86_64_efi only system. Right now I'm not sure if I built
it from source or if I made the iso with Debian binaries but, what it's
sure is that it did not boot at all. It just hung.

So I want a separate ISO for every platform.

8) What's the best way to build and install an hybrid system that
includes both: x86_64_efi and i386 - pc stuff?

Just built and install grub for each platform you want to use;
grub-mkrescue will automatically include every platform it finds.

Any advice for the special where I want to build x86_64_efi + x86_pc
hybrid disk?

Not really. Just build and install both platforms using the same prefix
and run grub-mkrescue that is build to use the same prefix.

Ok.

As mentioned, when building you should distinguish between host (grub
utils) and target (boot time). It is perfectly valid to build utils for
x86 and target for ARM as long as you have suitable cross tools. In
your case all builds should use the same host (which defaults to target
which may be wrong even for x86 case - consider 32 vs. 64 bit).

See INSTALL how to set various options for each environment.

Ok,I'll check that.

I prefer to build every platform in separate directory, there were
issues with incomplete cleanup. If you hit one, please report.

Well, as I don't want to have a separate directory for each build my
question would be:

What is it the official commands for doing a safe cleanup?

I always used make distclean. But IIRC there are some files that are
not removed. Not sure to which extent they affect subsequent builds. I
had problems when re-building on Windows but they should be fixed now.

From my point of view, make distclean is official and if it does not
work it is a bug that has to be fixed.

make distclean . Written down.

9) A) What's the best way to remove grub configuration files installed
on the system so that I can start from scratch so that already built
target+platform grub binaries or configurations are ignored?

There are no configuration files after make install (if we do not
count /etc/grub.d as configuration).

I meant the ones that someone makes grub-mkrescue to look for the
/usr/local/lib/grub/i386-pc/boot_hybrid.img files which I suppose are
not found in source code but in the system (Gnu/Linux filesystem I mean).

There are no special configuration files. If grub-mkrescue is called
without --directory option, it will enumerate all platforms found
under /usr/local/lib/grub (in your example). Just place additional
platform directory there and grub-mkrescue will pick it up.

So I just need to purge the /usr/local/lib/grub contents so that I can
start again without the fear of grub-mkrescue picking up an earlier
built platform (That's what I tried to achieve before with make
uninstall by the way).

That's exactly what I wanted to know.

Thank you very much!

I do not know when I will be able to try all of this but now it's much
more clear everything and I'll be able to report GRUB build errors (or
runtime) more easily for my special use case.

adrian15
--
Support free software. Donate to Super Grub Disk. Apoya el software
libre. Dona a Super Grub Disk. http://www.supergrubdisk.org/donate/

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

Re: How to deal with fatal device seeks?



I'm getting the same problem
( FATAL: int13_cdrom: function 42. Can't use 64bits lba )

with hd0, hd1, hd2, hd3, and worse:

* hd2,msdos5

ls (hd2,msdos5)/

Is this a bug?

adrian15

El 16/03/14 06:26, adrian15 escribió:

   I use a for loop for detecting Operating systems like this one:

for dev in (*); do

   echo $dev

done

but it hangs !!!

So some clues:

* Using 2.02~beta2-7 from Debian Unstable.
* The disk is an hybrid one (x86_64_efi + i386_pc).
* The error only happens when using Virtualbox in a non-EFI setup.

So some questions:

* Is it a bug that a non seekable device like (cd,apple4) or (cd,gpt1)
is available in non-EFI mode?
* Is it perhaps a Virtualbox bug?
* I cannot catch these fatal error as if they were exceptions inside a
try-catch. Or can I?

I will probably improve my searchindevices functions so that it also
filters these (cdsomething) devices as a workaround.

Thank you.


These are the minimal tests:

--- Using Qemu as EFI gives no problem:

echo (*)
(fd0) ... (cd) ... (cd,apple2),... (cd,gpt2)
ls (cd,apple4)/
error: unknown filesystem.
ls (cd,gpt1)/
error: unknown filesystem.

--- Using Virtualbox as BIOS (Ex. 1) (Problem):

echo (*)
(fd0) ... (cd) ... (cd,apple2),... (cd,gpt2)
ls (cd,apple4)/
FATAL: int13_cdrom: function 42. Can't use 64bits lba

--- Using Virtualbox as BIOS (Ex. 2) (No problem):

echo (*)
(fd0) ... (cd) ... (cd,apple2),... (cd,gpt2)
ls (cd,gpt4)/
error: unknown filesystem.

--- Using Virtualbox as BIOS (Ex. 3) (Problem):

echo (*)
(fd0) ... (cd) ... (cd,apple2),... (cd,gpt2)
ls (cd,gpt1)/
FATAL: int13_cdrom: function 42. Can't use 64bits lba


adrian15


--
Support free software. Donate to Super Grub Disk. Apoya el software 
libre. Dona a Super Grub Disk. http://www.supergrubdisk.org/donate/


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

Re: How to deal with fatal device seeks?


El 16/03/14 17:43, Andrey Borzenkov escribió:

В Sun, 16 Mar 2014 17:05:53 +0100
adrian15 adrian15...@gmail.com пишет:



I'm getting the same problem
( FATAL: int13_cdrom: function 42. Can't use 64bits lba )



This message does not exist in grub sources, so it likely comes from
firmware. 64 bit LBA would mean size over 2TB. So the first question -
what size of disks do you have?


SATA 0: 200 GB (Windows 7)
SATA 1: 1 GB (Rescatux USB. E.g. Grub mkrescue disk)
SATA 2: 20 GB (SteamOS E.g. Debian)




with hd0, hd1, hd2, hd3, and worse:

* hd2,msdos5

ls (hd2,msdos5)/

Is this a bug?



Hard to tell. Do you actually have working filesystem(s) on these
partitions? The message itself simply means that grub attempts to read
very high offset. I wonder if it can be somehow byte order related.


From GRUB point of view:

* (hd2,msdos1) is Gnu/Linux root filesystem
* (hd2,msdos2) No such partition
* (hd2,msdos3) No such partition
* (hd2,msdos4) No such partition
* (hd2,msdos5) FATAL: int13_cdrom: function 42. Can't use 64bits lba

From GNU/Linux point of view:

Disk /dev/sdc: 21.5 GB, 21474836480 bytes
255 heads, 63 sectors/track, 2610 cylinders, total 41943040 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00068a9f

   Device Boot  Start End  Blocks   Id  System
/dev/sdc1   *20484013670320067328   83  Linux
/dev/sdc24013875041940991  9011215  Extended
/dev/sdc54013875241940991  901120   82  Linux swap / Solaris


If I try:

ls (hd2,msdos5)/

from a 2.00-15 system mkrescue image (Super Grub2 Disk 2.00s1-beta6) I get:

error: unknown filesystem.

So, it's ok, because it is not a fatal error.
It would seem that somewhere between 2.00-15 and 2.02~beta2-7 (Debian 
version) the bug arises.


Or maybe the error was before because grub did actually to arise a FATAL 
error and it didn't.



Thank you for any indication on how to make more tests.

adrian15
--
Support free software. Donate to Super Grub Disk. Apoya el software 
libre. Dona a Super Grub Disk. http://www.supergrubdisk.org/donate/


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

Re: How to deal with fatal device seeks?


El 16/03/14 18:16, adrian15 escribió:

If I try:

ls (hd2,msdos5)/

from a 2.00-15 system mkrescue image (Super Grub2 Disk 2.00s1-beta6) I get:

error: unknown filesystem.

So, it's ok, because it is not a fatal error.
It would seem that somewhere between 2.00-15 and 2.02~beta2-7 (Debian
version) the bug arises.

Or maybe the error was before because grub did actually to arise a FATAL
error and it didn't.


2.00-22 does not have the error.

So it narrows the search between 2.00-22 and 2.02~beta2-7.

adrian15


Thank you for any indication on how to make more tests.

adrian15


--
Support free software. Donate to Super Grub Disk. Apoya el software 
libre. Dona a Super Grub Disk. http://www.supergrubdisk.org/donate/


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

Re: How to deal with fatal device seeks?

I have digged the git log for partition related commits just in case you
might think that they have something to do with my problem

(From 2.00 release to current head on master branch).

I have tried to filter them. So I have removed the ones related with
strange table partitions or emulation code.

Here there are the commits:

http://git.savannah.gnu.org/cgit/grub.git/commit/?id=e88f0420b90c2565637962754cc26fa8a4ed9256
http://git.savannah.gnu.org/cgit/grub.git/commit/?id=4bad23a15fc129218f611f51dcb268c246b207f1
http://git.savannah.gnu.org/cgit/grub.git/commit/?id=25fc51a87929262c1cc132bc29cc083ce98f0e0e
http://git.savannah.gnu.org/cgit/grub.git/commit/?id=df6da5a52dc2ec424203c0f8001903435b177fa8
http://git.savannah.gnu.org/cgit/grub.git/commit/?id=b7b78edb1ca05f30dd07ebed4bcb3d5a39aa5358
http://git.savannah.gnu.org/cgit/grub.git/commit/?id=258f43b7d7bf4b03799b6cd3004b5372e082d01b
http://git.savannah.gnu.org/cgit/grub.git/commit/?id=86d08fdb18b0142c1ce1b95db1aae989502956c5

Just hope that you, that deal with GRUB source code every day, can find
what might be the faulty commit so that I can test that the special
commit source code and reproduce it (or not to reproduce it).

Thank you for any idea!

adrian15

El 16/03/14 19:05, adrian15 escribió:

El 16/03/14 18:16, adrian15 escribió:

If I try:

ls (hd2,msdos5)/

from a 2.00-15 system mkrescue image (Super Grub2 Disk 2.00s1-beta6) I
get:

error: unknown filesystem.

So, it's ok, because it is not a fatal error.
It would seem that somewhere between 2.00-15 and 2.02~beta2-7 (Debian
version) the bug arises.

Or maybe the error was before because grub did actually to arise a FATAL
error and it didn't.

2.00-22 does not have the error.

So it narrows the search between 2.00-22 and 2.02~beta2-7.

adrian15

Thank you for any indication on how to make more tests.

adrian15

--
Support free software. Donate to Super Grub Disk. Apoya el software
libre. Dona a Super Grub Disk. http://www.supergrubdisk.org/donate/

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

How one is supposed to write kind-of-library cfg files?


( Using 2.02~beta2-7 from Debian Unstable  )

  I have tried to write some cfg files to kind of organise them as 
libraries but it does not work as expected.


  It seems as the sourced cfg files are being interpreted.


  Here below you will find the overall idea in an theoric example.
Attached you will find an actual code (although you are missing some 
pieces from Super Grub2 Disk).



When selecting the Boot manually... submenu (not when trying to run 
one of their options) I am getting these errors:


BEGIN

error: syntax error
error: Incorrect command.
error: syntax error
error: Incorrect command.
error: syntax error
error: syntax error
error: Incorrect command.
error: syntax error
error: can't find command `searchindevice'
FATAL: int13_cdrom: function 42. Can't use 64bits lba

END

searchindevice is a function which it's sourced in main.cfg so it should 
be detected ok.


But anyways... the run_option function is being interpreted while I do 
not want it !!!


I have also tried to replace source command by extract_entries_source. I 
get different output but the same problem, the sourced file is being 
interpreted (I mean it is being run).


Thank you.


### caller.cfg

function process_option {

  set option_cfg=${1}
  source ${option_cfg}
  menuentry ${option_title} {
source ${option_cfg}
run_option
  }

}

process_option ${prefix}/called.cfg
process_option ${prefix}/option2.cfg

### called.cfg

set option_title=My title



function run_option {

  function aux_lib {

  }

  function aux_lib2 {

  }

  aux_lib
  aux_lib2

  do_interesting_stuff

}


adrian15
--
Support free software. Donate to Super Grub Disk. Apoya el software 
libre. Dona a Super Grub Disk. http://www.supergrubdisk.org/donate/
# Super Grub Disk Main Configuration file
# Copyright (C) 2009  Adrian Gibanel Lopez.
#
# Super Grub Disk is free software: you can redistribute it and/or modify
# it under the terms of the GNU General Public License as published by
# the Free Software Foundation, either version 3 of the License, or
# (at your option) any later version.
#
# Super Grub Disk is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
# GNU General Public License for more details.
#
# You should have received a copy of the GNU General Public License
# along with GRUB.  If not, see http://www.gnu.org/licenses/.

# Configure gfxterm, but allow it to be disabled by holding shift during boot.
# gfxterm is required to display non-ASCII translations.
loadfont $prefix/unifont.pf2
if keystatus --shift; then
  disable_gfxterm=true
  # export disable_gfxterm is needed so that the setting will persist even after
  # a configfile /boot/grub/main.cfg (which is what language_select.cfg does 
after
  # you select a new language)
  export disable_gfxterm

  # The following strings are intentionally not made translateable.
  echo It has been detected that the shift key was held down. Because of this 
SG2D
  echo will use VGA text mode rather than gfxterm. This will cause display 
problems
  echo when using some non-English translations.
  echo
  echo Press escape to continue to the main menu
  sleep --interruptible 
fi

if [ $disable_gfxterm != true ]; then
  insmod all_video
  gfxmode=640x480
  if terminal_output --append gfxterm; \
  then \
  terminal_output --remove console; \
  fi
fi

# Export the variables so that they persist when loading a new menu.
export menu_color_normal
export menu_color_highlight
export menu_color_background
export bwcolor

function set_sgd_colors {
  if [ $bwcolor = yes ]; then
menu_color_normal=white/black
menu_color_highlight=black/white
menu_color_background=black/white
  else
menu_color_normal=white/brown
menu_color_highlight=white/blue
menu_color_background=yellow/cyan
  fi
}

set_sgd_colors

# Set secondary_locale_dir to the directory containing SG2D specific mo files.
# This makes grub aware of translations for SG2D specific strings.
secondary_locale_dir=${prefix}/sgd_locale/

insmod part_acorn
insmod part_amiga
insmod part_apple
insmod part_bsd
insmod part_gpt
insmod part_msdos
insmod part_sun
insmod part_sunpc

# Prepare environment variables, needed mostly for update_paths()
export prefix_device prefix_path prefix_uuid
regexp -s prefix_device '^\((.*)\)/' $prefix
regexp -s prefix_path '^\(.*\)/(.*)$' $prefix
probe --fs-uuid --set=prefix_uuid $prefix_device

# Define a function for updating paths when device names change.
# search.mod is required for update-paths, and must be loaded before device
# names change because $prefix will be invalid.
insmod search

function update_paths {
  search --fs-uuid --set=prefix_device $prefix_uuid
  prefix=($prefix_device)/$prefix_path
}

function process_option {

  set option_cfg=$1
  source ${option_cfg}
  menuentry ${option_title} {
source ${option_cfg

Re: How one is supposed to write kind-of-library cfg files?


El 16/03/14 04:49, adrian15 escribió:

( Using 2.02~beta2-7 from Debian Unstable  )

   I have tried to write some cfg files to kind of organise them as
libraries but it does not work as expected.

   It seems as the sourced cfg files are being interpreted.


I have managed to write a minimal working example. It would seem that 
the problem is having a function inside another function.



Is it perhaps not officially supported?

The problem happens when one selects: This is a submenu... .

error: syntax error
error: Incorrect command.
error: syntax error
...
can't find command thisisanunknowncommand
...
error: syntax error



Thank you.

### caller.cfg

function process_option {

  set option_cfg=$1
  source ${option_cfg}
  menuentry ${option_title} {
source ${option_cfg}
run_option
  }

}

menuentry $Languages... {
  configfile ${prefix}/language_select.cfg
}

submenu $This is a submenu... {

  process_option ${prefix}/called.cfg

}

menuentry $Everything {
  configfile ${prefix}/everything.cfg
}

 called.cfg

set option_title=$The called option

function run_option {

function freebsd_ufs_variants {
set device=$1
set fstype=$2
set uuid=$3

	menuentry ${finaloption_tab_str}FreeBSD ($fstype $device) (Default 
boot loader) $device $uuid {

set root=$2

kfreebsd /boot/loader
}
}

  thisisanunknowncommand
  menuentry menuinsideoption {
source ${prefix}/topbootmenu.cfg
set root=(hd0,0)
chainloader +1
  }

}



adrian15
--
Support free software. Donate to Super Grub Disk. Apoya el software 
libre. Dona a Super Grub Disk. http://www.supergrubdisk.org/donate/


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

How to deal with fatal device seeks?


  I use a for loop for detecting Operating systems like this one:

for dev in (*); do

  echo $dev

done

but it hangs !!!

So some clues:

* Using 2.02~beta2-7 from Debian Unstable.
* The disk is an hybrid one (x86_64_efi + i386_pc).
* The error only happens when using Virtualbox in a non-EFI setup.

So some questions:

* Is it a bug that a non seekable device like (cd,apple4) or (cd,gpt1) 
is available in non-EFI mode?

* Is it perhaps a Virtualbox bug?
* I cannot catch these fatal error as if they were exceptions inside a 
try-catch. Or can I?


I will probably improve my searchindevices functions so that it also 
filters these (cdsomething) devices as a workaround.


Thank you.


These are the minimal tests:

--- Using Qemu as EFI gives no problem:

echo (*)
(fd0) ... (cd) ... (cd,apple2),... (cd,gpt2)
ls (cd,apple4)/
error: unknown filesystem.
ls (cd,gpt1)/
error: unknown filesystem.

--- Using Virtualbox as BIOS (Ex. 1) (Problem):

echo (*)
(fd0) ... (cd) ... (cd,apple2),... (cd,gpt2)
ls (cd,apple4)/
FATAL: int13_cdrom: function 42. Can't use 64bits lba

--- Using Virtualbox as BIOS (Ex. 2) (No problem):

echo (*)
(fd0) ... (cd) ... (cd,apple2),... (cd,gpt2)
ls (cd,gpt4)/
error: unknown filesystem.

--- Using Virtualbox as BIOS (Ex. 3) (Problem):

echo (*)
(fd0) ... (cd) ... (cd,apple2),... (cd,gpt2)
ls (cd,gpt1)/
FATAL: int13_cdrom: function 42. Can't use 64bits lba


adrian15
--
Support free software. Donate to Super Grub Disk. Apoya el software 
libre. Dona a Super Grub Disk. http://www.supergrubdisk.org/donate/


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

Re: Trying to build Rescue image for three different target and platform

El 13/03/14 06:51, Andrey Borzenkov escribió:

В Sun, 09 Mar 2014 17:14:04 +0100
adrian15 adrian15...@gmail.com пишет:

Basically what I want to do is to use grub-mkrescue to generate a grub2
rescue disk with some custom files (The Super Grub2 Disk stuff).

However I want to build different files depending on target+platform
combination.

My four combinations are:

* (Hybrid) x86_64+efi and i386+pc
* i386 - pc
* x86_64 - efi
* i386 - efi

3) x86_64_efi build is working. Basically what I run in the src dir is:

sudo rm -rf /usr/local/share/grub
sudo rm -rf /usr/local/lib/grub
make clean
make distclean
bash linguas.sh
bash autogen.sh
./configure --target=i386 --with-platform=efi make sudo make
uninstall
make clean
make distclean
./configure --target=i386 --with-platform=pc make sudo make
uninstall
make clean
make distclean
./configure --target=x86_64 --with-platform=efi make sudo make
uninstall
make clean
make distclean
make clean
make distclean
bash linguas.sh
bash autogen.sh
./configure --target=x86_64 --with-platform=efi make sudo make
install

To be honest, I do not understand what you are trying to do here.

The same thing as in:

https://forja.cenatic.es/plugins/scmgit/cgi-bin/gitweb.cgi?p=supergrub2/supergrub2.git;a=blob_plain;f=supergrub-meta-mkrescue;hb=22683e2b5fa0d65141c1be1a7487914b1d43f4dd

(which uses Debian packages) but using source code.

6) When I build i386 - pc I get this error:

xorriso : FAILURE : Given path does not exist on disk: -boot_image
system_area='/usr/local/lib/grub/i386-pc/boot_hybrid.img'

Why is it failing to create /usr/local/lib/grub/i386-pc/boot_hybrid.img
file?

This file should be built and installed on 386-pc platform. If not
either there is a bug, or you are doing something wrong. It is hard to
tell, you are doing so many steps ...

I see.

8) What's the best way to build and install an hybrid system that
includes both: x86_64_efi and i386 - pc stuff?

Just built and install grub for each platform you want to use;
grub-mkrescue will automatically include every platform it finds.

Any advice for the special where I want to build x86_64_efi + x86_pc
hybrid disk?

Current code is:

./configure --target=i386 --with-platform=pc make sudo make install
make clean
make distclean
./configure --target=x86_64 --with-platform=efi make sudo make
install

It is better to explicitly force host platform with --host= to make
sure user space is always the same. Otherwise it should be fine.

Ok, I'll check that.

I prefer to build every platform in separate directory, there were
issues with incomplete cleanup. If you hit one, please report.

Well, as I don't want to have a separate directory for each build my
question would be:

What is it the official commands for doing a safe cleanup?

There are no configuration files after make install (if we do not
count /etc/grub.d as configuration).

Hope it's a bit more clear what I mean.

Thank you.

adrian15
--
Support free software. Donate to Super Grub Disk. Apoya el software
libre. Dona a Super Grub Disk. http://www.supergrubdisk.org/donate/

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

Trying to build Rescue image for three different target and platform

2014-03-09 Thread adrian15

Basically what I want to do is to use grub-mkrescue to generate a grub2 
rescue disk with some custom files (The Super Grub2 Disk stuff).


However I want to build different files depending on target+platform 
combination.


My four combinations are:

* (Hybrid) x86_64+efi and i386+pc
* i386 - pc
* x86_64 - efi
* i386 - efi

More about this setup.

1) As an initial setup I work with a Debian Unstable Sid Chroot amd64 as 
described in:

http://www.supergrubdisk.org/wiki/Super_Grub2_Disk_Sid_Chroot#Introduction
2) I use Debian's Grub2 source code so that I do not have to deal 
manually with dependencies. That's explained here: 
http://www.supergrubdisk.org/wiki/Super_Grub2_Disk_Sid_Chroot_Grub2_Build_And_Installation 
(just before Hybrid build section).


3) x86_64_efi build is working. Basically what I run in the src dir is:

  sudo rm -rf /usr/local/share/grub
  sudo rm -rf /usr/local/lib/grub
  make clean
  make distclean
  bash linguas.sh
  bash autogen.sh
  ./configure --target=i386 --with-platform=efi  make  sudo make 
uninstall

  make clean
  make distclean
  ./configure --target=i386 --with-platform=pc  make  sudo make 
uninstall

  make clean
  make distclean
  ./configure --target=x86_64 --with-platform=efi  make  sudo make 
uninstall

  make clean
  make distclean
  make clean
  make distclean
  bash linguas.sh
  bash autogen.sh
  ./configure --target=x86_64 --with-platform=efi  make  sudo make 
install


And what I do for generating the file image is:

grub-mkrescue --output=super_grub2_disk_x86_64_efi_2.00s1-beta6.iso 
$(mktemp -d)


4) i386_pc build is not working. Basically what I run in the src dir is:

  sudo rm -rf /usr/local/share/grub
  sudo rm -rf /usr/local/lib/grub
  make clean
  make distclean
  bash linguas.sh
  bash autogen.sh
  ./configure --target=i386 --with-platform=efi  make  sudo make 
uninstall

  make clean
  make distclean
  ./configure --target=i386 --with-platform=pc  make  sudo make 
uninstall

  make clean
  make distclean
  ./configure --target=x86_64 --with-platform=efi  make  sudo make 
uninstall

  make clean
  make distclean
  make clean
  make distclean
  bash linguas.sh
  bash autogen.sh
  ./configure --target=i386 --with-platform=pc  make  sudo make install


And what I do for generating the file image is:

grub-mkrescue --output=super_grub2_disk_i386_pc_2.00s1-beta6.iso 
$(mktemp -d)


5) I attach the current helper scripts that I use.

supergrub-mkrescue : This is a very simple wrapper around: 
grub-mkrescue. You do not need to take care about it.


supergrub-meta-mkrescue : This is what I have explained above. This 
script assumes that you have setup your grub2 source code in:

/home/adrian/gnu/sgd/debian_grub2/grub2-2.00
and that supergrub-mkrescue script is found in the same folder as 
supergrub-meta-mkrescue.


Currently supergrub-meta-mkrescue has been modified so that it ends 
(Check the return 0 ; line) after building:


* x86_64_efi
and
* i386 - pc
.

6) When I build i386 - pc I get this error:

xorriso : FAILURE : Given path does not exist on disk: -boot_image 
system_area='/usr/local/lib/grub/i386-pc/boot_hybrid.img'


Why is it failing to create /usr/local/lib/grub/i386-pc/boot_hybrid.img 
file?


7) Is it useful that I insist on building an i386+efi release? Any 
machine system that uses it? Some old Mac-something hardware perhaps?


8) What's the best way to build and install an hybrid system that 
includes both: x86_64_efi and i386 - pc stuff?


Current code is:

  ./configure --target=i386 --with-platform=pc  make  sudo make install
  make clean
  make distclean
  ./configure --target=x86_64 --with-platform=efi  make  sudo make 
install


9) A) What's the best way to remove grub configuration files installed 
on the system so that I can start from scratch so that already built 
target+platform grub binaries or configurations are ignored?


B) That's what I try to do in clean_every_build function in 
supergrub-meta-mkrescue script but I do not think its an efficient way 
of doing it.


C) You know I would like to remove the rm -rf /usr/local/share/grub and 
rm -rf /usr/local/lib/grub lines (too weird) and just use the:


./configure ; make ; make uninstall part.

D) Which I do not know if could be re-written as:

./configure ; make uninstall

(Notice that there is not a make step).

Does removing the make default target call (make) breaks make 
uninstall functionality?


10) As a summary I basically want to build and install from upstream 
source code and then make one rescue disk for each one of these four 
combinations. (And make theses rescue diks in a row)


* (Hybrid) x86_64+efi and i386+pc
* i386 - pc
* x86_64 - efi
* i386 - efi

So... any help on this build automation process?

Thank you very much!


adrian15
--
Support free software. Donate to Super Grub Disk. Apoya el software 
libre. Dona a Super Grub Disk. http://www.supergrubdisk.org/donate/
#!/bin/bash -e
usage() {
cat EOF

  $0 -o=output.iso

Re: Some ideas about new features of grub

2009-08-23 Thread adrian15


Robert Millan escribió:

On Thu, Jul 02, 2009 at 04:48:56PM +0800, Bean wrote:

LUA integration.
LUA is quite powerful, it's more suitable to do complicated task than
sh script. For example, we can use it to detect os at runtime,
implement simple commands, or draw the graphic menu.


I feel similarly about LUA as I do about writable filesystems.  In fact I'm
considering a configure flag so that it's only enabled only when user
requests it.

But I know both Marco and Pavel feel strongly about this.  Please can you
comment?



I am against a configure flag (if configure is the one from configure, 
make, make install) but a configure flag (as something specified in 
grub.cfg) is ok.


adrian15
--
Support free software. Donate to Super Grub Disk. Apoya el software 
libre. Dona a Super Grub Disk. http://www.supergrubdisk.org/index.php?pid=10




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

Re: Grub2 LUA API?

2009-08-23 Thread adrian15


Bean escribió:

Hi,

You can use grub.enum_device, which pass the uuid to the callback
function, then you can store the device-uuid mapping in a table.

Thank you. I will check your advice.


If you're looking for source code, check out script/lua/grub_lib.c

I would have prefered documentation but source code is ok.

I will, of course, report back with more improvements/doubts on this 
subject.


Thank you again.

adrian15
--
Support free software. Donate to Super Grub Disk. Apoya el software 
libre. Dona a Super Grub Disk. http://www.supergrubdisk.org/index.php?pid=10




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

os-detect lua space fix

2009-08-22 Thread adrian15

Here you a have a patch that fixes the error that osdetect.lua script 
had with spaces around the equals sign.


Now it does not complain when assigning the variable.

adrian15
--
Support free software. Donate to Super Grub Disk. Apoya el software 
libre. Dona a Super Grub Disk. http://www.supergrubdisk.org/index.php?pid=10
diff -urN original/osdetect.lua equals_space_fixed/osdetect.lua
--- original/osdetect.lua   2009-08-15 18:59:48.0 +0200
+++ equals_space_fixed/osdetect.lua 2009-08-22 17:33:52.0 +0200
@@ -156,7 +156,7 @@
local initrd
 
title = Linux  .. kernels[i]
-   source = set root =  .. device ..
+   source = set root= .. device ..
  \nlinux /boot/ .. kernelnames[i] ..
   root=UUID= ..   ro
 
___
Grub-devel mailing list
Grub-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/grub-devel

os-detect lua uuid fix

2009-08-22 Thread adrian15


Here you a have a patch that fixes the error that osdetect.lua script
had uuid not being set.

Now the linux kernel does not complain about not finding root device.

The only problem that this patch has is that is made with grub shell in 
mind instead of lua.


I suppose that we can do the same thing but getting the uuid values from 
lua script itself. If I am able to do so I will also send a patch for it.


adrian15
--
Support free software. Donate to Super Grub Disk. Apoya el software
libre. Dona a Super Grub Disk. http://www.supergrubdisk.org/index.php?pid=10

diff -urN original/osdetect.lua uuid_fix/osdetect.lua
--- original/osdetect.lua   2009-08-22 17:42:43.0 +0200
+++ uuid_fix/osdetect.lua   2009-08-22 18:23:12.0 +0200
@@ -156,9 +156,11 @@
local initrd
 
title = Linux  .. kernels[i]
+   uuid_setup = search --set=sgd_linux_kernel -f /boot/ .. 
kernelnames[i] .. \n
+   uuid_set = probe -u ($sgd_linux_kernel) --set=sgd_root_uuid .. \n
source = set root= .. device ..
  \nlinux /boot/ .. kernelnames[i] ..
-  root=UUID= ..   ro
+  root=UUID= .. $sgd_root_uuid ..   ro
 
if grub.file_exist (root .. boot/initrd- ..
kernels[i] .. .img) then
@@ -171,7 +173,7 @@
  initrd = 
end
 
-   grub.add_menu (source .. initrd, title)
+   grub.add_menu (uuid_setup .. uuid_set .. source .. initrd, title)
grub.add_menu (source ..  single .. initrd,
   title ..  (single-user mode))
   end
___
Grub-devel mailing list
Grub-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/grub-devel

Osprober lua script problems when setting root

2009-08-20 Thread adrian15 adrian15

Hi Grub-devel,

 I have built a custom grub2-based cdrom (I am using grub2 from
debian unstable) that uses osdetect.lua which I have fetched from
phcoder git two or  three days ago.
I have an Ubuntu 9.04 installation in my Virtualbox test machine.
After running the AUTO MAGIC BOOT which actually sources
$prefix/osdetect.lua I get an entry called:
Linux 2.6.28-11-generic.

Its content is:
set root = hd0,1
linux /boot/vmlinuz-2.6.28-11-generic root=UUID= ro
initrd /boot/initrd.img-2.6.28-11-generic

When booting the entry I get:  error: not an assignment.

The first bug is that error message seems not meaningful to me.
The second bug is that it seems that the set root line should not have
spaces around the equals sign.
So it should have produced: set root=hd0,1.

Or is it maybe that Debian's grub2 is not updated enough to allow
spaces around the equals sign and svn version it is?

Thank you for you attention.

phcoder, whenever the bug is fixed can you please send me a download
url for the updated file? Thank you.

adrian15
-- 
Support free software. Donate to Super Grub Disk. Apoya el software
libre. Dona a Super Grub Disk.
http://www.supergrubdisk.org/index.php?pid=10


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

Are you going to Debconf9?

2009-07-12 Thread adrian15 adrian15

Hi,

I am adrian15 from Super Grub Disk. I have been quite for a while.
I was asking myself if some of you are going to Debconf.

I won't mind meeting some of you and learning about grub2 (I am a bit
outdated) and maybe try to code some lines.

Or just meet someone like _x86, marco_g or nyu face to face.

http://debconf9.debconf.org/index.xhtml.en

Debian Conference is the annual Debian developers meeting, an event
filled with coding parties, discussions and workshops - all of them
highly technical in nature. It will be held in Cáceres, Extremadura,
Spain, from July 23 to 30, 2009.

Thank you.

adrian15
-- 
Support free software. Donate to Super Grub Disk. Apoya el software
libre. Dona a Super Grub Disk.
http://www.supergrubdisk.org/index.php?pid=10


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

Re: HOWTO needed: how to add my own module to making list?

2007-11-15 Thread adrian15


Oleg Strikov wrote:


Thank you for your attention, but ive got ruby already :(
ruby --version
ruby 1.8.6 (2007-03-13 patchlevel 0) [i486-linux]


That's what I thought myself when I first programmed in grub2 and it was 
true but grub2 development tools did not use ruby.


If you type ruby does it says command not found or not ?

You might need to create a link name ruby to the ruby1.8 executable 
found probably at /bin folder.


adrian15


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

Re: echo gives internal error with \n

2007-08-03 Thread adrian15


Marco Gerards escribió:

adrian15 [EMAIL PROTECTED] writes:


  I've activated the echo command (also the pause command) which it is
equivalent to the echo command... and have done some tests:


The problem is in the parser.

I see.

Two conclusions from these tests:

1) When you use \n in string that does not begin with  then it gives an
internal error. I do not see anything special on echo.c so I suppose
it's the fault of the parser, however I have not studied the parser
yet... so marco_g what's your opinnion?


True, Bean sent in a patch to fix this.

:) I knew this already.



2) The -e option is not implemented. :) I've checked the code and it is
not. However I doubt if it's going to work... I ask myself if the grub
string always appears at the beginning of the line.


Do you want to implement this? ;-)

This should not be hard to do.


Implementation is easy but what's difficult for me is the design decision.

Here there are three possible scenarios:

1a) When grub is showed it does begin in the last character position
(not in a new line).
This might imply rewriting the end of the programs so that they end
with something similar to: grub_printf(\n);
1b) Same than 1a but the execution of the last grub_printf(\n); is
automatically run from the program than runs one command after another
one. (I do not know the name in grub2.) depending on a new special flag
of the program.

2) The echo command with a -e option sets a variable which is checked
each time the grub line is going to be written. Depending on the
variable grub_printf(\ngrub); or grub_printf(grub); is run.

At what implementation were you thinking to issue this problem?




pause is equivalent to echo command but if you want to check what I am
saying check my other email that contains a patch for having both echo
and pause commands.


Well... I think you do not need to check my patch... the idea is that
pause command is the echo command plus a pause. Something like:

pause.sh:

echo $@ ; read
exit

So the pause command can have all the echo command power.

I also might work in the read command although I have to think more
about it.


adrian15



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

Re: Acer arcade instantOn and grub

2007-08-02 Thread adrian15


[EMAIL PROTECTED] escribió:

when laptop is new (read when you haven't overridden window's bootloader), 
pressing the normal power on button causes a normal boot sequence, but pressing the 
arcade button causes a different boot sequence.

A different boot sequence.


i don't really want to restore windows boot loader,

When you said before a different boot sequence did you mean that it
restores the windows boot loader or that it loads it from nowhere
instead of reading the disk... or what?


so: is there a way to replicate this job with grub or grub2?

I do not know.



for any further info please ask.


Is this information stored somehow?  So how can the bootloader
determine what is done?  In that case you can use scripting in GRUB 2
to make use of this information.  It can't be done yet, but surely
GRUB 2 can be modified to use this.

--
Marco

thanks for you answer, marco

follows a more deep description of the system

the original system uses a modified grub 0.93 chainloaded by ntldr.
the modifications of grub are released, but i can't replicate them on grub 0.97.

When you talk about this original system... this has nothing to do with
the arcade button, isn't it ?

Or is this code supposed to activate a fallback option (not the default
option but default+1 option) ?

Can you send a patch (differences from grub 0.93 and grub 0.93-modified)
so that I can try to apply to my own fork of grub 0.97?

Thank you.

adrian15



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

multidistro grub2 idea

2007-07-22 Thread adrian15


THE PROBLEM
=

The problem about boot loaders in a multi distribution environment is
the grub configurations being overlapped.
Imagined this partition layout:
part 1: windows
part 2: ubuntu
part 3: debian

If you install first windows, then ubuntu and then debian is great
possible that debian makes its menu.lst be the default one.
It can also have the correct lines for booting ubuntu or it might have
not them.
I suppose that there is more complication when you run the update-grub
command when a kernel has been updated.

THE DISCUSSION


When there are multiple distros I've been regularly astonished of the
ones that advice of copy-and-paste lines from other menu.lst and add it
to your current one. And they are people that not even use
copy-and-paste and advice to add the lines by hand.
I think the problem is here is that no one knows that a command called
configfile exists.
In my computer I have 4 menu.lst and I have not used the configfile
approach. I have installed grub in the distros' partition and  also in
the mbr which is associated with a grub installed on a /boot partition.

Disk /dev/sda: 137.4 GB, 137437871104 bytes
255 heads, 63 sectors/track, 16709 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot Start End  Blocks   Id  System
/dev/sda1   *  1127510241406c  W95 FAT32 (LBA)
/dev/sda2   12761287   96390   83  Linux(/BOOT)
/dev/sda3   1288371919535040   83  Linux   (DEBIAN)
/dev/sda4   3720   16709   1043421755  Extended
/dev/sda5   3720   1514791795378+  83  Linux   (/HOME)
/dev/sda6  15148   16166 8185086   83  Linux   (FEDORA)
/dev/sda7  16167   16198  257008+  82  Linux swap / Solaris
/dev/sda8  16199   16709 4104576   83  Linux(TEST DISTROS)


THE SOLUTION
=

I think that if grub2 is going to have scripting and so many new
features we should take advantage of them and change the way computers
do boot.

#1) All Linux installers should set or reuse a ext2 partition next to
the windows one as a /boot one where grub2 is installed.

#2) /boot/grub/

will have a new folder called:

/boot/grub/menu/

which will be filled with .cfg files from the different distros that
are installed in a computer.

As an example ubuntu installed on /dev/sda2 should have a
ubuntu-sda2.cfg file in there.

#3) grub2 should include tools to deal with this .cfg files from the
linux environment.

#4) /boot/grub/grub2.cfg will be used for determining which of the .cfg
files inside /boot/grub/menu is the default one and which it is the
timeout for it.
(If only one .cfg file is found then timeout is 0).

#5) The problems that happened when a distro had been patched for doing
one thing or another one will not exist. Why? Because distros can take
advantage of the modules in order to add its own enhacements to grub2.

#6) /boot/grub/grub2.cfg security should be enhanced.

What are your thoughts about this idea?

adrian15



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

Re: GRUB 2 documentation

2007-07-01 Thread adrian15


Khaled Hosny escribió:

I'd like to work on this, any idea where to begin? should I start with
grub legacy documentation and update/remove/add information to match
that of grub2 or should I start from scratch?



In my opinnion there are three ways to elaborate documentation.
1) From grub2 developer point of view.
2) From grub2 architecture.
3) From a grub2 user.


As long as scripting is not well defined I think you can begin with the
grub2 architecture. I think knowing yourself the grub2 architecture can
make things easier when elaborating documentation from a grub2 user
point of view.

I mean one of the first thing a grub2 documentation from a grub2 user
point of view should have is an introduction on how does grub2 work overall.

adrian15



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

Re: Grub2 request

2007-06-25 Thread adrian15


Amin Azez escribió:

Grub allows press any key to continue on multiple consoles.
It would be nice if the text could be specified per-console.

I know some serial port based 2 line lcd screens that would want smaller text.

Different get-key drivers would be good, these lcd screens have to poll to read 
keypresses.

They have 4 keys, up, down esc and enter; enough to navigate a grub menu.

If this sounds good, I'm willing to write the lcd specific code.

Sam


Does anyone know if grub2 is designed so that it has different outputs
and different behaviour on these different outputs?

adrian15



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

Re: status update for grub 2 developments?

2007-06-25 Thread adrian15


Bean escribió:

Well, if people want to work on scripting or networking they should
talk to me.  I have lots of code on my hd that is incomplete or just
not cleaned up.  It would be a waste of time if it were rewritten.
And please poke me a lot to get me to work... ;)


I'm interested in scripting. What could I do to help you ?


As long as you may re-read Marco_g source code you can try to fix a bug
that I have found I suppose in the parser.

If you type any command with a \ character not being inside  
characters it gives an grub internal error.

echo \n -- OK
echo \n fff -- GRUB INTERNAL ERROR

adrian15



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

Re: status update for grub 2 developments?

2007-06-19 Thread adrian15


Vesa Jääskeläinen escribió:

Joomla's tracker is a bit more what I was thinking about. It handles
tasks quite nicely. Has task dependency support.


	I think that gforge has also tasks. I just do not find right now any 
gforge site with a task site.


adrian15


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

Re: status update for grub 2 developments?

2007-06-18 Thread adrian15


Vesa Jääskeläinen escribió:

Hi all!

I think it would be wise to keep some kind of status updates from time
to time so we can keep track on what people are doing (related to grub
2). If we continue with current situation we are long in 2010's before
we have next release.
You're too optimistic. :) I was thinking about 2015. Anyway,... I will 
work hard this summer in grub2 because it needs it.

I think it would also be important to coordinate more different
activities within grub 2.

Ok.

In example graphical menu has been issue for
several years now :).

I am sorry not being an expert on this area.
 Therefore I would propose that we would setup a

group of people that would concentrate on specific issues related to
implmentation (like a work group or something).

I also think groups are a good thing.
 I do not see it as a

requirement that this group of people would implement the feature
(though that would be good), but most importantly to draft out how
features should work. When there is a spec written how feature should
work then it would be much easier to implement that feature and then it
would match ideology of other relevant developers (eg. to get patch
accepted).

I also like the specs idea.

I would see that at least following working groups should be formed. Of
course we could tackle design issue at a time and then move to other issues.

- Graphical menu (needs API spec, configuration file specs, guidelines
for implementation, information how to integrate with scripting)

I might collaborate on the how to integrate with scripting part.


- Network support (needs API spec, driver architecture, protocol stacks,
file system support)

No idea about this subject.


Perhaps some others too... (please add)


I am going to work in grub-disk. A collection of grub2.cfg files or 
maybe more that will define useful collection of command such as Search 
linux kernel, linux initrd and load them. Something similar to Super 
Grub Disk.



Anyway. First of all I would like to hear if you are developing
something above or something else, reply this e-mail and tell us about
it, there is no reason that work should be duplicated.


My current todo:
# Current development
* pause command
* map, mapboot and usbshift commands
# Short term development
* grub-disk scripts
* grub2 scripts testing
* grub legacy commands porting
# Long term development
* install and setup commands for grub2

If you want more details please visit: http://grub.enbug.org/AdrianGibanel


Ideas are welcome where to store this information are also welcome :).
We would need to track requirements for features on component level.
More automated the better.


Can we use the bugs system maybe?
A friend of mine uses trac ( http://trac.edgewall.org/ ) and he likes it 
a lot. I do not know if it fits our needs.


adrian15


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

echo gives internal error with \n

2007-06-17 Thread adrian15


  I've activated the echo command (also the pause command) which it is
equivalent to the echo command... and have done some tests:

grub pause fjfjl
fjfjl
grub pause fjfjl
fjfjl
grub pause -n \n
error: Internal error

grub pause \n
error: Internal error

grub pause -n \n
\n
grub pause -e \n

grub echo fasf
fasf
grub


Two conclusions from these tests:

1) When you use \n in string that does not begin with  then it gives an
internal error. I do not see anything special on echo.c so I suppose
it's the fault of the parser, however I have not studied the parser
yet... so marco_g what's your opinnion?

2) The -e option is not implemented. :) I've checked the code and it is
not. However I doubt if it's going to work... I ask myself if the grub
string always appears at the beginning of the line.

pause is equivalent to echo command but if you want to check what I am
saying check my other email that contains a patch for having both echo
and pause commands.

adrian15




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

pause and echo patch

2007-06-17 Thread adrian15


I attach the proposal of patch and I comment some doubts that I have.


diff -urN grub2_2007_05_31_original/commands/echo.c 
grub2_2007_05_31_pause/commands/echo.c
--- grub2_2007_05_31_original/commands/echo.c   2007-06-11 11:53:26.0 
+0200
+++ grub2_2007_05_31_pause/commands/echo.c  2007-06-17 04:25:26.0 
+0200
@@ -110,16 +110,35 @@
   return 0;
 }
 
+static grub_err_t

+grub_cmd_pause (struct grub_arg_list *state __attribute__ ((unused)),
+ int argc, char **args)
+
+{
+
+  char key;
+  if (argc!=0) 
+grub_cmd_echo(state,argc,args);

Here there is the trick for not duplicating code!

+  key = grub_getkey ();
+  
+  return 0;

+}
+
 
 GRUB_MOD_INIT(echo)
 {
+
+  (void) mod;  /* To stop warning. */
+  grub_register_command (pause, grub_cmd_pause, GRUB_COMMAND_FLAG_BOTH,
+pause [-e|-n] [MESSAGE], Pause and optionally show a 
message with echo command., options);
   (void) mod;  /* To stop warning. */
   grub_register_command (echo, grub_cmd_echo, GRUB_COMMAND_FLAG_BOTH,
-echo [-e|-n] FILE, Display a line of text.,
+echo [-e|-n] \STRING\, Display a line of text.,
 options);
 }
 
 GRUB_MOD_FINI(echo)

 {
   grub_unregister_command (echo);
+  grub_unregister_command (pause);
 }

I do not understand very well what's a module.
For instance should I have loaded the echo and pause commands in a
different module?


diff -urN grub2_2007_05_31_original/conf/common.rmk 
grub2_2007_05_31_pause/conf/common.rmk
--- grub2_2007_05_31_original/conf/common.rmk   2007-06-11 11:53:27.0 
+0200
+++ grub2_2007_05_31_pause/conf/common.rmk  2007-06-17 04:18:07.0 
+0200
@@ -168,7 +168,7 @@
 pkgdata_MODULES += hello.mod boot.mod terminal.mod ls.mod  \
cmp.mod cat.mod help.mod font.mod search.mod\
loopback.mod configfile.mod \
-   terminfo.mod test.mod blocklist.mod
+   terminfo.mod test.mod blocklist.mod echo.mod
 
 # For hello.mod.

 hello_mod_SOURCES = hello/hello.c


So if I needed to edit this rmk in order to have one more module I
should replicate the lines where it is read echo.mod and put pause.mod,
but I should not change the lines with echo.c to pause.c because both
commands are in the same file...

Am I right?


adrian15


diff -urN grub2_2007_05_31_original/commands/echo.c grub2_2007_05_31_pause/commands/echo.c
--- grub2_2007_05_31_original/commands/echo.c	2007-06-11 11:53:26.0 +0200
+++ grub2_2007_05_31_pause/commands/echo.c	2007-06-17 04:25:26.0 +0200
@@ -110,16 +110,35 @@
   return 0;
 }
 
+static grub_err_t
+grub_cmd_pause (struct grub_arg_list *state __attribute__ ((unused)),
+	  int argc, char **args)
+
+{
+
+  char key;
+  if (argc!=0) 
+grub_cmd_echo(state,argc,args);
+  key = grub_getkey ();
+  
+  return 0;
+}
+
 
 GRUB_MOD_INIT(echo)
 {
+
+  (void) mod;			/* To stop warning. */
+  grub_register_command (pause, grub_cmd_pause, GRUB_COMMAND_FLAG_BOTH,
+			 pause [-e|-n] [MESSAGE], Pause and optionally show a message with echo command., options);
   (void) mod;			/* To stop warning. */
   grub_register_command (echo, grub_cmd_echo, GRUB_COMMAND_FLAG_BOTH,
-			 echo [-e|-n] FILE, Display a line of text.,
+			 echo [-e|-n] \STRING\, Display a line of text.,
 			 options);
 }
 
 GRUB_MOD_FINI(echo)
 {
   grub_unregister_command (echo);
+  grub_unregister_command (pause);
 }

diff -urN grub2_2007_05_31_original/conf/common.rmk grub2_2007_05_31_pause/conf/common.rmk
--- grub2_2007_05_31_original/conf/common.rmk	2007-06-11 11:53:27.0 +0200
+++ grub2_2007_05_31_pause/conf/common.rmk	2007-06-17 04:18:07.0 +0200
@@ -168,7 +168,7 @@
 pkgdata_MODULES += hello.mod boot.mod terminal.mod ls.mod	\
 	cmp.mod cat.mod help.mod font.mod search.mod		\
 	loopback.mod configfile.mod\
-	terminfo.mod test.mod blocklist.mod
+	terminfo.mod test.mod blocklist.mod echo.mod
 
 # For hello.mod.
 hello_mod_SOURCES = hello/hello.c

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

map command draft #2

2007-06-17 Thread adrian15

)


Is it important that I also copy-paste the rmk files modifications or not?

adrian15


diff -urN grub2_2007_05_31_original/commands/i386/pc/map.c grub2_2007_05_31_map/commands/i386/pc/map.c
--- grub2_2007_05_31_original/commands/i386/pc/map.c	1970-01-01 01:00:00.0 +0100
+++ grub2_2007_05_31_map/commands/i386/pc/map.c	2007-06-17 05:56:15.0 +0200
@@ -0,0 +1,107 @@
+/* map.c - Define drives map array  */
+/*
+ *  GRUB  --  GRand Unified Bootloader
+ *  Copyright (C) 2005  Free Software Foundation, Inc.
+ *
+ *  GRUB is free software; you can redistribute it and/or modify
+ *  it under the terms of the GNU General Public License as published by
+ *  the Free Software Foundation; either version 2 of the License, or
+ *  (at your option) any later version.
+ *
+ *  This program is distributed in the hope that it will be useful,
+ *  but WITHOUT ANY WARRANTY; without even the implied warranty of
+ *  MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+ *  GNU General Public License for more details.
+ *
+ *  You should have received a copy of the GNU General Public License
+ *  along with GRUB; if not, write to the Free Software
+ *  Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.
+ */
+
+#include grub/normal.h
+#include grub/dl.h
+#include grub/arg.h
+#include grub/disk.h
+#include grub/term.h
+#include grub/misc.h
+#include grub/device.h
+#include grub/file.h
+
+/* The size of the drive map.  */
+#define DRIVE_MAP_SIZE		16
+/* The BIOS drive map.  */
+static unsigned short bios_drive_map[DRIVE_MAP_SIZE + 1];
+
+int real_map_func (unsigned long to, unsigned long from) {
+int i;
+  /* Search for an empty slot in BIOS_DRIVE_MAP.  */
+  for (i = 0; i  DRIVE_MAP_SIZE; i++)
+{
+  /* Perhaps the user wants to override the map.  */
+  if ((bios_drive_map[i]  0xff) == from)
+	break;
+  
+  if (! bios_drive_map[i])
+	break;
+}
+
+  if (i == DRIVE_MAP_SIZE)
+{
+  return GRUB_ERR_OUT_OF_RANGE;
+}
+
+  if (to == from)
+/* If TO is equal to FROM, delete the entry.  */
+grub_memmove ((char *) bios_drive_map[i], (char *) bios_drive_map[i + 1],
+		  sizeof (unsigned short) * (DRIVE_MAP_SIZE - i));
+  else
+bios_drive_map[i] = from | (to  8);
+  
+  return 0;
+
+
+}
+
+
+
+static grub_err_t
+grub_cmd_map (struct grub_arg_list *state __attribute__ ((unused)),
+	   int argc, char **args)
+{
+  grub_disk_t map_disk_to,map_disk_from;
+
+/* TODO: Check map arguments from grub2 engine */  
+  if (argc != 2)
+return grub_error (GRUB_ERR_BAD_ARGUMENT, Two devices required);
+  map_disk_to = grub_disk_open (grub_file_get_device_name(args[0]));
+  if (! map_disk_to)
+return grub_error (GRUB_ERR_UNKNOWN_DEVICE, Unknown TO disk);
+/* This was a marco_g suggestion but it does not make sense to me.
+  if (grub_strcmp(map_disk_to-name,biosdisk))
+return grub_error (GRUB_ERR_UNKNOWN_DEVICE, TO disk is not a bios disk.);
+*/
+  map_disk_from = grub_disk_open (grub_file_get_device_name(args[1]));
+  if (! map_disk_from)
+return grub_error (GRUB_ERR_UNKNOWN_DEVICE, Unknown FROM disk);
+/* This was a marco_g suggestion but it does not make sense to me.
+  if (grub_strcmp(map_disk_from-name,biosdisk))
+return grub_error (GRUB_ERR_UNKNOWN_DEVICE, FROM disk is not a bios disk.);
+*/
+
+
+  return (real_map_func(map_disk_to-id,map_disk_from-id));
+  
+}
+
+
+GRUB_MOD_INIT(map)
+{
+  (void)mod;			/* To stop warning. */
+  grub_register_command (map, grub_cmd_map, GRUB_COMMAND_FLAG_BOTH,
+			 map TODEVICE FROMDEVICE, Map a drive to another, 0);
+}
+
+GRUB_MOD_FINI(map)
+{
+  grub_unregister_command (map);
+}

diff -urN grub2_2007_05_31_original/conf/i386-pc.rmk grub2_2007_05_31_map/conf/i386-pc.rmk
--- grub2_2007_05_31_original/conf/i386-pc.rmk	2007-06-11 11:53:27.0 +0200
+++ grub2_2007_05_31_map/conf/i386-pc.rmk	2007-06-14 12:38:00.0 +0200
@@ -1,5 +1,7 @@
 # -*- makefile -*-
 
+
+
 COMMON_ASFLAGS = -nostdinc -fno-builtin -m32
 COMMON_CFLAGS = -fno-builtin -mrtd -mregparm=3 -m32
 COMMON_LDFLAGS = -m32 -nostdlib
@@ -121,7 +123,7 @@
 pkgdata_MODULES = _chain.mod _linux.mod linux.mod normal.mod \
 	_multiboot.mod chain.mod multiboot.mod reboot.mod halt.mod	\
 	vbe.mod vbetest.mod vbeinfo.mod video.mod gfxterm.mod \
-	videotest.mod play.mod bitmap.mod tga.mod cpuid.mod
+	videotest.mod map.mod play.mod bitmap.mod tga.mod cpuid.mod
 
 # For _chain.mod.
 _chain_mod_SOURCES = loader/i386/pc/chainloader.c
@@ -195,6 +197,11 @@
 vbetest_mod_CFLAGS = $(COMMON_CFLAGS)
 vbetest_mod_LDFLAGS = $(COMMON_LDFLAGS)
 
+# For map.mod.
+map_mod_SOURCES = commands/i386/pc/map.c
+map_mod_CFLAGS = $(COMMON_CFLAGS)
+map_mod_LDFLAGS = $(COMMON_LDFLAGS)
+
 # For play.mod.
 play_mod_SOURCES = commands/i386/pc/play.c
 play_mod_CFLAGS = $(COMMON_CFLAGS)

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

Detection of boot devices by a linux kernel



First question:
=

Once a Kernel has booted can request the bios the different boot
devices and try to open them with a bios-disk driver or whatever the
name is?


Current problems:


I do not know what's the live cd / non-live cd installer algorithm for
detecting which grub device corresponds to which linux device.
There's a man in hardwareguys.com which gets some strange results. He
installing Linux in his 4th drive and as long as it is detected as
/dev/sdg then the linux assign it: hd6 . :)

http://forums.hardwareguys.com/ikonboard.cgi?act=ST;f=21;t=5731;#top

Probable solution:
=
If the answer for the first question is that NO here there is my
solution to problem.

We should make a command that iterates all the hard disks boot devices
and looks for the uuid from the hard disks. Once it has done so it saves
the result into a variable.

Then we can boot a kernel and pass this variable as a parametrer.

Example:
==

grub set
prefix=(cd)/boot/grub/
root=(cd)
grub detectboot -s biosdevices
grub set
root=(cd)
biosdevices=hd0|ffkei|hd1|ereok|hd2|er455
grub linux /boot/knoppix-6.0-kernel root=/dev/ram 
grubdevices=$biosdevices
grub initrd /boot/knoppix-6.0-initrd
grub boot

Then thanks to the grubdevices=hd0|ffkei|hd1|ereok|hd2|er455 string
found in /proc/cmdline the knoppix boot scripts can check the uuid for
each detected hard disk and generate a valid devices.map file.

Any comments on this?


adrian15



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

Grub2 mainstream test floppies


Now I am quite busy with pause and map commands but I do not want to
forget the grub2-disk creation (Something similar to Super Grub Disk).
grub2-disk will have some menues that explain how grub2 syntax does
work and will have some useful options such as searching an already
installed grub2.cfg and loading it, search and load vmlinuz* and
initrd*, activate partitions and so on.
(You can check Super Grub Disk http://geocities.com/supergrubdisk/ if
you want to.)

The first draft for grub2-disk is one more folder in grub2 source code
which it is called disk. This folder has an script for generating the
grub2-disk and some subfolders that contain specific grub2.cfg files (or
maybe only one grub2.cfg file).

I think we could convert the grub2-disk into a mainstream test floppy.
I myself found a lot of bugs on grub legacy because no one had tested
all the possible options on a cdrom. I think grub2 developers could
write down some grub2.cfg files into the disk folder.

This options will be used for testing new features that should be
tested by many people.
The idea is:
- Prompt if the text has been tested ok already or not.
- Prompt a text explanation
- Prompt what the possible results may be
- Prompt what information may be needed if the test fails and 
where
(mail) has to be sent.
- Run the test.



So... The grub2-disk will have a development menu which will have the
tests.


The idea is each week run the grub2-disk-creation script and upload the
correspondent generated floppy image to the grub ftp server so that
anyone that it is interested can test it without the need of knowing:
how to get data from the cvs, how to compile it, how to generate a
floppy and how to put the commands on a .cfg file.

Any comments about this?

adrian15



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

Re: how to add a new command


Alex Roman escribió:

On 12/06/07, adrian15 [EMAIL PROTECTED] wrote:
Once I write a new command like map.c or pause.c how am I 
supposed to

add it to the standard grub?
Should I write the makefiles manually?! or should I use some 
of the .sh

files at the grub2 source code root folder?


I've been editing the .rmk files in conf/ which should cause the .mk
files to get updated (at least that's my understanding of it, so far).

Make sure the command is placed in the right Makefile... I had the
problem where I was including the command in both grub-emu and
grub/i386-pc and grub-emu didn't link due to undefined symbols
(because those didn't exist in grub-emu).


Cheers!



I've finally edit conf/i386-pc.rmk, copy-pasted the play.c code and
find/replace with map.c.


Then I run make:
make prompts this:


[EMAIL PROTECTED]:~/Desktop/gnu/grub2/grub2_2007_05_31_map$ make
if test x = x; then \
  touch conf/i386-pc.mk; \
else \
   ./genmk.rb  conf/i386-pc.rmk  conf/i386-pc.mk; \
fi
make: No se hace nada para `all'.

If you check: i386-pc.mk then there is no reference to:
/map.c

If I delete i386-pc.mk and run make again:

[EMAIL PROTECTED]:~/Desktop/gnu/grub2/grub2_2007_05_31_map$ make
Makefile:111: conf/i386-pc.mk: No existe el fichero o el directorio
if test x = x; then \
  touch conf/i386-pc.mk; \
else \
   ./genmk.rb  conf/i386-pc.rmk  conf/i386-pc.mk; \
fi
make: No se hace nada para `all'.

and a empty i386-pc.mk file is created.


I check genmk.rb and it is not an executable file.






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

spanish grub wiki

Can anyone with proper permissions edit PáginaInicial and put a link to 
FrontPage page ?


Thank you.

adrian15


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

Variables help inside a command help


If you check the man pages of some linux commands you will see that
there is a place where it talks about ENVIRONMENT VARIABLES or something
similar where it describes some variables than can modify the way a
command works.

As long as we can register the options help like this:

{label, 'l', 0, search devices by a filesystem label, 0, 0},
{set, 's', GRUB_ARG_OPTION_OPTIONAL, set a variable to the first
device found, VAR, ARG_TYPE_STRING},

why shouldn't we do a similar thing for variables?

I think a command should be able to register a:
variable name
- to set or not a value for this variable
- to put a description for the variable


so that when querying a command help this variable help also shows.

And when querying help variable we see all the commands help about
this variable.

Let's see an example.

cat
defines this variable pager help:
1: Stops at each screen. 0: Do not stop.

randomcolourcat
defines this variable pager help:
1: Stops at each screen. 0: Do not stop.

find
defines this variable pager help:
1: Stops at each screen. 0: Do not stop.


So if you type help cat apart from you see right now you see also:
1: Stops at each screen. 0: Do not stop.

And if you type help variable pager you should see:
cat: 1: Stops at each screen. 0: Do not stop.
randomcolourcat: 1: Stops at each screen. 0: Do not stop.
find: 1: Stops at each screen. 0: Do not stop.


It's a stupid example but that's I mean.

adrian15



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

Pager does work from a menu?


This code from: normal/command.c

  /* Enable the pager if the environment pager is set to 1.  */
  if (interactive)
pager = grub_env_get (pager);
  else
pager = 0;
  if (pager  (! grub_strcmp (pager, 1)))
grub_set_more (1);

Can anyone confirm my suspictions that even the pager variable set to 1
there is NO stop on the screen when running a grub option that has the
cat command inside it with a big file?

I am suspecting because in grub legacy there was the same stupid
behaviour which I fixed of course.

I also do not like the way that pager is run. I mean, putting a getkey
inside the

void
grub_putcode (grub_uint32_t code)

function from: kern/term.c

it seems to me a bit childish although I do not know so far a better
solution.



adrian15



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

Checking parametres that are not inside an option


If you take a look at search.c you can see that the -s parametrer is
checked outside the command thanks to the ARG_TYPE_STRING constant.

{set, 's', GRUB_ARG_OPTION_OPTIONAL, set a variable to the first
device found, VAR, ARG_TYPE_STRING}


If I want not to check if an argument command that it IS NOT inside an
option is something (a disk, i.e.) or not... how do I do it?

I mean I want something like:

map (hd0) (hd1)

to be checked outside the command without using:

map -disk1 (hd0) -disk2 (hd1)
and the correspondent option definition at map.c

how do I do it ?

adrian15



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

How to call a command from another one


Hi,

I want to implement the pause command so that it is the same thing as
the echo command with all of its options and also that it stops.

My first approach which I could not compile because I do not how to add
a new command to grub2 is the following one:


  char key;
  if (argc!=0)
grub_cmd_echo(state,argc,args);
  key = grub_getkey ();

  return 0;



So my question is if it's an orthodox way of calling another command, if
I should call it in another way or if I should not call it in any way.

adrian15



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

Re: How to call a command from another one


Robert Millan escribió:

On Tue, Jun 12, 2007 at 01:57:11PM +0200, adrian15 wrote:

Hi,

I want to implement the pause command so that it is the same thing as
the echo command with all of its options and also that it stops.

I don't know how to call other commands, but in this case, maybe grub_printf()
will be good enough?


I agree with you but...

I think it would be a good idea to have a pause message that has the 
same options as the echo command because the echo command has some nice 
options and because I like to reuse code.


adrian15


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

Re: Pager does work from a menu?


Robert Millan escribió:

On Tue, Jun 12, 2007 at 01:57:42PM +0200, adrian15 wrote:

This code from: normal/command.c

  /* Enable the pager if the environment pager is set to 1.  */
  if (interactive)
pager = grub_env_get (pager);
  else
pager = 0;
  if (pager  (! grub_strcmp (pager, 1)))
grub_set_more (1);

Can anyone confirm my suspictions that even the pager variable set to 1
there is NO stop on the screen when running a grub option that has the
cat command inside it with a big file?


Can you ellaborate?  From the code you pasted, I just see that when
interactive is set to 0, this has the same effect as pager being set to
the 0 string.


That's what I mean. I think that interactive for grub2 means being in 
the grub2 shell (not in a menu). If you are in a menu (non interactive) 
then there is no stop between pages.


But you know I am a bit lazy. I should at last try to do a grub.cfg and 
test it on my test floppy and see if I am right or not.



I am suspecting because in grub legacy there was the same stupid
behaviour which I fixed of course.

I also do not like the way that pager is run. I mean, putting a getkey
inside the

void
grub_putcode (grub_uint32_t code)

function from: kern/term.c

it seems to me a bit childish although I do not know so far a better
solution.


Please try to tear down that language!  stupid and childish are in general
not very appropiate words for a development list.

Written down. Sorry, I'll try to use more formal synonims next time.


I suppose you're referring to:

  grub_printf (--MORE--);
  grub_setcolorstate (GRUB_TERM_COLOR_STANDARD);

  key = grub_getkey ();

What do you find wrong in this code?  AFAICS, the message is printed and then
we use grub_getkey to block untill a key is pressed.  Sounds like normal
pager-ish behaviour to me..


The code is ok. What I do not find ok is that the screen pause happens 
in a function which works it is to put a character on the screen.
I do not quite understand why a function that only has to print a 
character on the screen has also to deal with the screen by screen stop 
problem.


In my opinion this screen by screen stop problem should be solved in 
another part of the source code but so far I do not know where.


adrian15


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

help, configfile, pager and

2007-06-10 Thread adrian15


Here is a patch for some of the problems that I found in my miscelanea
mails.

More to come. :)

adrian15



diff -urN grub2_2007_05_31_original/ChangeLog
grub2_2007_05_31_small_fixes/ChangeLog
--- grub2_2007_05_31_original/ChangeLog 2007-05-20 11:10:05.0 +0200
+++ grub2_2007_05_31_small_fixes/ChangeLog  2007-06-10 18:48:40.0
+0200
@@ -1,3 +1,10 @@
+2007-06-21  adrian15  [EMAIL PROTECTED]
+   * kern/main.c: Pager variable is now set to 0 by default.
+   * commands/help.c: Help command help shows that with no pattern
+   all the commands are shown.
+   * commands/configfile.c: Configfile command help tells the user that
+   that it runs the config file with another context.
+
  2007-05-20  Robert Millan  [EMAIL PROTECTED]

* util/update-grub_lib.in: New file.
diff -urN grub2_2007_05_31_original/commands/configfile.c
grub2_2007_05_31_small_fixes/commands/configfile.c
--- grub2_2007_05_31_original/commands/configfile.c 2006-06-04
17:56:54.0 +0200
+++ grub2_2007_05_31_small_fixes/commands/configfile.c  2007-06-10
18:36:19.0 +0200
@@ -60,7 +60,7 @@
(void) mod;   /* To stop warning. */
grub_register_command (configfile, grub_cmd_configfile,
  GRUB_COMMAND_FLAG_BOTH, configfile FILE,
-Load another config file., 0);
+Load another config file with a new context., 0);
grub_register_command (source, grub_cmd_source,
  GRUB_COMMAND_FLAG_BOTH, source FILE,
  Load another config file without changing
context.,
diff -urN grub2_2007_05_31_original/commands/help.c
grub2_2007_05_31_small_fixes/commands/help.c
--- grub2_2007_05_31_original/commands/help.c   2005-11-13
16:47:08.0 +0100
+++ grub2_2007_05_31_small_fixes/commands/help.c2007-06-10
18:20:03.0 +0200
@@ -98,7 +98,7 @@
  {
(void)mod;  /* To stop warning. */
grub_register_command (help, grub_cmd_help, 
GRUB_COMMAND_FLAG_CMDLINE,

-help [PATTERN ...], Show a help message., 0);
+help [PATTERN ...], Show a command help. No pattern 
shows all
available commands., 0);
  }

  GRUB_MOD_FINI(help)
diff -urN grub2_2007_05_31_original/kern/main.c
grub2_2007_05_31_small_fixes/kern/main.c
--- grub2_2007_05_31_original/kern/main.c   2006-04-25 22:08:31.0
+0200
+++ grub2_2007_05_31_small_fixes/kern/main.c2007-06-10
18:12:53.0 +0200
@@ -127,6 +127,9 @@
grub_machine_set_prefix ();
grub_set_root_dev ();

+  /* Set pager and other unimportant variables */
+  grub_env_set (pager, 0);
+
/* Load the normal mode module.  */
grub_load_normal_mode ();



diff -urN grub2_2007_05_31_original/ChangeLog grub2_2007_05_31_small_fixes/ChangeLog
--- grub2_2007_05_31_original/ChangeLog	2007-05-20 11:10:05.0 +0200
+++ grub2_2007_05_31_small_fixes/ChangeLog	2007-06-10 18:48:40.0 +0200
@@ -1,3 +1,10 @@
+2007-06-21  adrian15  [EMAIL PROTECTED]
+	* kern/main.c: Pager variable is now set to 0 by default.
+	* commands/help.c: Help command help shows that with no pattern
+	all the commands are shown.
+	* commands/configfile.c: Configfile command help tells the user that
+	that it runs the config file with another context.
+
 2007-05-20  Robert Millan  [EMAIL PROTECTED]
 
 	* util/update-grub_lib.in: New file.
diff -urN grub2_2007_05_31_original/commands/configfile.c grub2_2007_05_31_small_fixes/commands/configfile.c
--- grub2_2007_05_31_original/commands/configfile.c	2006-06-04 17:56:54.0 +0200
+++ grub2_2007_05_31_small_fixes/commands/configfile.c	2007-06-10 18:36:19.0 +0200
@@ -60,7 +60,7 @@
   (void) mod;   /* To stop warning. */
   grub_register_command (configfile, grub_cmd_configfile,
 GRUB_COMMAND_FLAG_BOTH, configfile FILE,
-Load another config file., 0);
+Load another config file with a new context., 0);
   grub_register_command (source, grub_cmd_source,
 GRUB_COMMAND_FLAG_BOTH, source FILE,
 Load another config file without changing context.,
diff -urN grub2_2007_05_31_original/commands/help.c grub2_2007_05_31_small_fixes/commands/help.c
--- grub2_2007_05_31_original/commands/help.c	2005-11-13 16:47:08.0 +0100
+++ grub2_2007_05_31_small_fixes/commands/help.c	2007-06-10 18:20:03.0 +0200
@@ -98,7 +98,7 @@
 {
   (void)mod;			/* To stop warning. */
   grub_register_command (help, grub_cmd_help, GRUB_COMMAND_FLAG_CMDLINE,
-			 help [PATTERN ...], Show a help message., 0);
+			 help [PATTERN ...], Show a command help. No pattern shows all available commands., 0);
 }
 
 GRUB_MOD_FINI(help)
diff -urN grub2_2007_05_31_original/kern/main.c grub2_2007_05_31_small_fixes/kern/main.c
--- grub2_2007_05_31_original/kern/main.c	2006-04-25 22:08:31.0 +0200

Re: grub-mkrescue: Make GRUB rescue image

2007-06-08 Thread adrian15


Robert Millan escribió:

I'm attaching a small utility to generate a floppy or cdrom (based on floppy
emulation) rescue image, that takes all the hassle of generating the image and
doesn't need root permissions.

If nobody objects, I'd like to put this in CVS.


The rescue disk can recover a grub2 installation with something similar 
to the grub legacys' root and setup commands ?


Or is it a disk that where you only see

grub rescue 

?
adrian15


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

Re: pager (Re: grub2 miscelanea questions (1/2))

2007-06-08 Thread adrian15


Marco Gerards escribió:

set pager=1

How about setting it to 0 by default, so it shows up when you list the
variables.  Currently it just doesn't exist.


That's a good idea.
Where is the place (file) for setting default variables values?

adrian15


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

map command for grub2 draft

2007-06-07 Thread adrian15


I want to implement the map command for grub2 as long as it is an
interesting thing for stupid windows oses and because it's the clue for
making an usbshift equivalent command (See Super Grub Disk usbshift
command for more details).


1st) Where to save an array?
=

If I mimic the grub legacy map command I need to save an array with the
map definitions.

static unsigned short bios_drive_map[DRIVE_MAP_SIZE + 1];

So that each time I call something like:
map (hd0) (hd1)
it modifies this vector.

Any example on where should I define this vector so that I can use it
from each command ?

2nd) boot_func and actual mapping


If you look at grub legacy boot command


case KERNEL_TYPE_CHAINLOADER:
  /* Chainloader */

  /* Check if we should set the int13 handler.  */
  if (bios_drive_map[0] != 0)
{
  int i;

  /* Search for SAVED_DRIVE.  */
  for (i = 0; i  DRIVE_MAP_SIZE; i++)
{
  if (! bios_drive_map[i])
break;
  else if ((bios_drive_map[i]  0xFF) == saved_drive)
{
  /* Exchage SAVED_DRIVE with the mapped drive.  */
  saved_drive = (bios_drive_map[i]  8)  0xFF;
  break;
}
}

  /* Set the handler. This is somewhat dangerous.  */
  set_int13_handler (bios_drive_map);
}

  gateA20 (0);
  boot_drive = saved_drive;
  chain_stage1 (0, BOOTSEC_LOCATION, boot_part_addr);
  break;




you will see that among other things it detects if you want to do a
chainloader boot. If you do a chainloader boot it checks the
bios_drive_map array,... run some BIOS calls so that there's an actual
map and then it finally boots.

When I told marco_g that I want to modificy grub2's boot command he
became scared because the boot command was arquitecture specific (or
maybe not, I actually did not understood what he meant) and as long as I
understood I was not meant to modify it.

how should I implement this then?



adrian15



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

grub2 miscelanea questions #2

2007-06-07 Thread adrian15


1) search command file not found:
=
If you search for an inexistant file like:
search -f /boot/grub/und-video
it complains:
error: no such device

Shouldn't it be:
error: no such file /boot/grub/und-video

I mean it has to talk about files not devices and it has also to prompt
the file you have searched for... or maybe not, I do not know.

I ask marco_g if I am going to be able to use this command inside an if
statement.

if `search -f /boot/grub/grub2.cfg` then

2) chainload a device


It seems that if I run:
chainloader (hd0)+1
boot
It boots my hard disk installed bootloader.

However chainloader help only prompts:
chainloader [-f] FILE
I think the help should be:
chainloader [-f] FILE|DEVICE

3) DEVICE vs DEVICENAME


If you check the loopback command help you will see that you can use a
DEVICENAME as an argument. Should we choose DEVICE or DEVICENAME when
talking about a DEVICE ?


4) About linux command


I do not like the linux command too much. What happens with bsd and
other kernels that are not multiboot?

why don't we have something as:

kernel --type linux whatever
kernel --type bsd whateverelse

?


Or maybe is better to have a bsd command or bsd will become at last a
multiboot os?


5) windows command
===
Can we add a windows command that does:
chainloader (hd0,0)+1
boot

A question for marco_g... which it is the best way so that a command can
call other commands?

Using grub_cmd_name where name is the name of the command or can I write
a grub.cfg file on the fly and then send it to some cfg interpreter
function?


6) boot command boots also boot loaders
=
If we can use chainloader for preparing to boot another boot loader...
then boot help should read:

Boot an operating system or another boot loader.

instead of:

Boot an operating system.


adrian15



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

Re: gcs doubt #1


If you can provide a patch for sourcecode to improve or add comments
in a sane way, I am willing to commit those patches.  Just please
don't make the mistake to add useless comments.

An useful comment is one that:
-Describes a function algorithm
-Describes what a function does (as a black box)
-Boot of them ?


Yes, but I oppose to adding obvious comments.  But patches will be
reviewed, so you will learn fast enough what we want :-).


You had to choose one of the three options :).
Well... it doesn't matter. I've understood that I have to send patches
and learn by trial-error.

adrian15



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

Re: test -e patch


adrian15 [EMAIL PROTECTED] writes:


Attached you will find the patch adding test -e support for grub2.

Do you mean you also have the '-e' option ?


I mean I have everything that is possible.  That includes `-e', but
also all other features.

Ok.



+static void
+test_file_exists (const char *key)

Why not filename?

test_filename_exists
or
filename


I mean instead of key.


You are right. It was a not clean copy-paste from search command.

adrian15



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

Re: grub2 miscelanea questions (1/2)


3) Why any grub2.cfg file (I suppose it's the substitute for menu.lst)
is inside the grub2 source code?


What do you mean?


Usually a program should include examples on how to use their files and
document examples and so on... why isn't there any grub2.cfg ?


4) Why any doc folder is inside the grub2 source code?


There is?  We need documentation...

:) I might work on this too... but as an unofficial documentation. I do
not like the rigid official documentations.



5) grub2 lacks
==
5.1) pager
-

When I want to do a big ls the output does not stop screen by screen...
Is there any hidden pager that I do not know?
Maybe is not implemented yet?


set pager=1

It just isn't documented :-/


We should be able to prompt with help command (help variables perhaps?)
these kind of tricks or pseudocommands.




5.2) Chainload DEVICES


How the hell do you boot windows?
Maybe from a file that has inside it the first 512 bytes from the
Windows partition?


chainload (hd0,1)+
boot


I've checked that this works:
chainloader (hd0,1)+1
boot


6) Compulsory Argument dilemma

If I run help I can seen things like this:

ls [-f|-l|-s] NAME

and

[ EXPRESSION ]


Yes?


If [ ] means optional it should also mean optional in the case of the
test alias [ .!!!


What do you mean?


The [] has not a single meaning in this program.
If it's written after a command in the help description it means: 
Optional.
If it's used as a program it means that it runs the test command.

It might be confusing for some users I suppose.

Why did not use to new bash syntax? $((variable))




7) set help incomplete

Set help should say that if no argument is set then it shows all the
environment variables.


Why would it?  Only using set shows all env. variables.

Because it is a hidden feature.
If you do not how grub does work and type help set
it shows Set an environment variable.

The user is unable to know that Only using set shows all env.
variables because it isn't written anywhere.


9) help does not complain when no command help is available
=

How it currently works is looking at the first characters.  For
example try help l.


I know... but if the first characters do not match with any command
beginning I think an error should be prompted. Don't you think so?




10) help --all
=
Do we need this functionality in grub2?


Are there hidden commands for which this is important?  In that case,
yes.


The hipotetical dd command. :)



12) ls and -h argument


This is not an error but it curious. You can ask for the help of command
with this:
command -h
however
ls -h
works in a different way.

I suppose we may have the same problem with '-u' in the future.


Ehm, I am not sure.  You mean `-h' is short for help and we should
remove it?


I mean that if an user gets used to use the -h option for getting grub
commands help then when using ls, he will be confused a little.

adrian15



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

Re: grub2 miscelanea questions (2/2)


19) rescue and exit failure on qemu
==
I think that booting from my computer does not give this error.
If I boot from QEMU and type:

grub rescue
and then :
grub rescue exit

it says: FATAL: INT18: BOOT FAILURE


Weird.  Can you debug this?


I've checked this again.
If I do this booting from my pc I get the grub2 floppy booting again.
If I do this from qemu the FATAL: INT18: BOOT FAILURE appears again.
I would bet that it is a qemu bios's lack of the 18 interruption.

20) grub rescue help


help : Types the commands and a minimal explanation: OK
help any_command : Types the commands and a minimal explanation: NOT OK
help not_a_command : Types the commands and a minimal explanation: NOT OK


huh?


You boot grub2 and you see
grub
you type rescue and you see
grub rescue
and now what it is funny that if you type the help command, an space,
and whatever you want to write it always shows all the commands help.

It may confuse some users as Grub is not working.




21) grub rescue exit help
===
When you are in grub rescue mode and you type help the exit line it's
the following one:

exitexit from GRUB

Should it not prompt ?

exitexit from GRUB rescue


The exit command terminates GRUB and continues the boot process, IIRC.

You are right. Exit from GRUB is right, then.




22) copyright message missing

Why isn't there (when Grub is running) any message about the GRUB
Copyright and the GPL license and that you should have received and this
and that?


Why should there be such message?

This comes from GPL 2:

If the program is interactive, make it output a short notice like this
when it starts in an interactive mode:

Gnomovision version 69, Copyright (C) year  name of author
Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type
`show w'.
This is free software, and you are welcome to redistribute it
under certain conditions; type `show c' for details.


Maybe we should implement an 'about' command and run it when booting :) ?

Perhaps, but I don't see the added value.

See above about the GPL.



23) set read only variables
==
unset prefix lets me delete the prefix variable.
unset root does not let me the root variable.

I remember that bash has an option to set read only variables.
Maybe the root variable is a read only variable?


You can easily modify the code.  But I do not like making such
variables read-only.


I did not want to make any variable read only. I only wanted to make you
know that the root variable was actually a read only variable because
there is no way to delete (unset) it. It always comes to live again.

Is it a normal thing?

adrian15



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

Grub Loading Linux? kernel