Contents of PO file 'grub-1.97+20091122.zh_CN.po'
grub-1.97+20091122.zh_CN.po.gz Description: Binary data The Translation Project robot, in the name of your translation coordinator. ___ Grub-devel mailing list Grub-devel@gnu.org http://lists.gnu.org/mailman/listinfo/grub-devel
Contents of PO file 'grub-1.97+20091122.zh_CN.po'
grub-1.97+20091122.zh_CN.po.gz Description: Binary data The Translation Project robot, in the name of your translation coordinator. ___ Grub-devel mailing list Grub-devel@gnu.org http://lists.gnu.org/mailman/listinfo/grub-devel
Contents of PO file 'grub-1.97+20091122.zh_CN.po'
grub-1.97+20091122.zh_CN.po.gz Description: Binary data The Translation Project robot, in the name of your translation coordinator. ___ Grub-devel mailing list Grub-devel@gnu.org http://lists.gnu.org/mailman/listinfo/grub-devel
Contents of PO file 'grub-1.97+20091122.zh_CN.po'
grub-1.97+20091122.zh_CN.po.gz Description: Binary data The Translation Project robot, in the name of your translation coordinator. ___ Grub-devel mailing list Grub-devel@gnu.org http://lists.gnu.org/mailman/listinfo/grub-devel
Contents of PO file 'grub-1.97+20091122.zh_CN.po'
grub-1.97+20091122.zh_CN.po.gz Description: Binary data The Translation Project robot, in the name of your translation coordinator. ___ Grub-devel mailing list Grub-devel@gnu.org http://lists.gnu.org/mailman/listinfo/grub-devel
Contents of PO file 'grub-1.97+20091122.zh_CN.po'
grub-1.97+20091122.zh_CN.po.gz Description: Binary data The Translation Project robot, in the name of your translation coordinator. ___ Grub-devel mailing list Grub-devel@gnu.org http://lists.gnu.org/mailman/listinfo/grub-devel
Contents of PO file 'grub-1.97+20091122.zh_CN.po'
grub-1.97+20091122.zh_CN.po.gz Description: Binary data The Translation Project robot, in the name of your translation coordinator. ___ Grub-devel mailing list Grub-devel@gnu.org http://lists.gnu.org/mailman/listinfo/grub-devel
Contents of PO file 'grub-1.97+20091122.id.po'
grub-1.97+20091122.id.po.gz Description: Binary data The Translation Project robot, in the name of your translation coordinator. ___ Grub-devel mailing list Grub-devel@gnu.org http://lists.gnu.org/mailman/listinfo/grub-devel
Contents of PO file 'grub-1.97+20091119.id.po'
grub-1.97+20091119.id.po.gz Description: Binary data The Translation Project robot, in the name of your translation coordinator. ___ Grub-devel mailing list Grub-devel@gnu.org http://lists.gnu.org/mailman/listinfo/grub-devel
Re: grub-1.97
richardvo...@gmail.com wrote: On Wed, Oct 28, 2009 at 11:02 AM, Bruce Dubbs wrote: Michal Suchanek wrote: I guess it's meant to be used like this: tar -jxvf grub-version.tar.bz2 cd grub-version mkdir build cd build ../configure./configure --prefix=/usr \ --sysconfdir=/etc \ --disable-largefile \ --disable-grub-emu \ --disable-grub-emu-usb \ --disable-grub-fstest \ --disable-efiemu --prefix=/some_prefix --options make make install Yes, that is exactly what we are doing. Right now the configure line is Not "exactly", and the difference is important.Michal suggested running "../configure" with a double-dot meaning parent directory. Your line has only a single dot, meaning current directory. As a result your files are all mixed together instead of separated as intended. ./configure --prefix=/usr \ --sysconfdir=/etc \ --disable-largefile \ --disable-grub-emu \ --disable-grub-emu-usb \ --disable-grub-fstest \ --disable-efiemu Ah yes. Thank you Richard. Either systems works, but using a separate build directory keeps all the 2400 generated files out of the main directory. I'll change to that in LFS. -- Bruce ___ Grub-devel mailing list Grub-devel@gnu.org http://lists.gnu.org/mailman/listinfo/grub-devel
Re: grub-1.97
On Wed, Oct 28, 2009 at 11:02 AM, Bruce Dubbs wrote: > Michal Suchanek wrote: >> >> 2009/10/28 Bruce Dubbs : > >>> I'd also like to make a comment. It may be useful if you split up the >>> build >>> into subdirectories by component. When I extracted the tarball, there >>> were >>> 57 files/directories in the top of the build tree. After configure it >>> was >>> 64. So far so good. However, after make it was over 2400 files, many >>> with >>> very long file names. This makes it almost impossible to navigate form >>> the >>> command line, even on a very big screen. If you split it up, you could >>> also >>> shorten the filenames. I would think that would be an advantage to >>> encourage programmers to read the code and contribute to the project. >>> >> >> I guess it's meant to be used like this: >> >> tar -jxvf grub-version.tar.bz2 >> cd grub-version >> mkdir build >> cd build >> ../configure./configure --prefix=/usr \ > > --sysconfdir=/etc \ > --disable-largefile \ > --disable-grub-emu \ > --disable-grub-emu-usb \ > --disable-grub-fstest \ > --disable-efiemu --prefix=/some_prefix --options >> >> make >> make install > > Yes, that is exactly what we are doing. Right now the configure line is Not "exactly", and the difference is important.Michal suggested running "../configure" with a double-dot meaning parent directory. Your line has only a single dot, meaning current directory. As a result your files are all mixed together instead of separated as intended. > > ./configure --prefix=/usr \ > --sysconfdir=/etc \ > --disable-largefile \ > --disable-grub-emu \ > --disable-grub-emu-usb \ > --disable-grub-fstest \ > --disable-efiemu ___ Grub-devel mailing list Grub-devel@gnu.org http://lists.gnu.org/mailman/listinfo/grub-devel
Re: grub-1.97
Felix Zielcke wrote: Am Mittwoch, den 28.10.2009, 11:02 -0500 schrieb Bruce Dubbs: Since there is only one Makefile, I could take a shot at creating a patch to address this problem. Would you be interested in such a patch? That's wrong that there is just one Makefile. Well it's true that there is just one file named like that, but the main Makefiles are the conf/*.mk files generated from conf/*.rmk by genmk.rb. Yes I see that now. Obviously I spoke before reviewing the internals of the build system. I'll review it in a bit more detail and see if I can contribute something useful. There wasn't yet much talk about improving our build system. Yes, that and documentation are generally the last things to be considered in a project. But except of this nobody had much interest/time to improve or even directly replace our build system by something better. I have some interest, but I'm not sure of the time. I can at least look at it and possibly make some suggestions/patches. Okuji already objected against automake because according to him it doestn't satisfy the needs for our build system. I'm not a great fan of automake either. -- Bruce ___ Grub-devel mailing list Grub-devel@gnu.org http://lists.gnu.org/mailman/listinfo/grub-devel
Re: grub-1.97
Am Mittwoch, den 28.10.2009, 17:39 +0100 schrieb Felix Zielcke: > Am Mittwoch, den 28.10.2009, 11:02 -0500 schrieb Bruce Dubbs: > > Since there is only one Makefile, I could take a shot at creating a > > patch to > > address this problem. Would you be interested in such a patch? > > That's wrong that there is just one Makefile. Well it's true that there > is just one file named like that, but the main Makefiles are the > conf/*.mk files generated from conf/*.rmk by genmk.rb. > > There wasn't yet much talk about improving our build system. > Bean just made it less complex in his lib branch (IIRC he called it > something like that) > But except of this nobody had much interest/time to improve or even > directly replace our build system by something better. > Okuji already objected against automake because according to him it > doestn't satisfy the needs for our build system. Uhm correction: I totally forgot about Vladimirs one Makefile implementation. Sorry Vladimir. But IIRC even about this there wasn't much talk about. -- Felix Zielcke Proud Debian Maintainer and GNU GRUB developer ___ Grub-devel mailing list Grub-devel@gnu.org http://lists.gnu.org/mailman/listinfo/grub-devel
Re: grub-1.97
Am Mittwoch, den 28.10.2009, 11:02 -0500 schrieb Bruce Dubbs: > Since there is only one Makefile, I could take a shot at creating a > patch to > address this problem. Would you be interested in such a patch? That's wrong that there is just one Makefile. Well it's true that there is just one file named like that, but the main Makefiles are the conf/*.mk files generated from conf/*.rmk by genmk.rb. There wasn't yet much talk about improving our build system. Bean just made it less complex in his lib branch (IIRC he called it something like that) But except of this nobody had much interest/time to improve or even directly replace our build system by something better. Okuji already objected against automake because according to him it doestn't satisfy the needs for our build system. -- Felix Zielcke Proud Debian Maintainer and GNU GRUB developer ___ Grub-devel mailing list Grub-devel@gnu.org http://lists.gnu.org/mailman/listinfo/grub-devel
Re: grub-1.97
Michal Suchanek wrote: 2009/10/28 Bruce Dubbs : I'd also like to make a comment. It may be useful if you split up the build into subdirectories by component. When I extracted the tarball, there were 57 files/directories in the top of the build tree. After configure it was 64. So far so good. However, after make it was over 2400 files, many with very long file names. This makes it almost impossible to navigate form the command line, even on a very big screen. If you split it up, you could also shorten the filenames. I would think that would be an advantage to encourage programmers to read the code and contribute to the project. I guess it's meant to be used like this: tar -jxvf grub-version.tar.bz2 cd grub-version mkdir build cd build ../configure./configure --prefix=/usr \ --sysconfdir=/etc \ --disable-largefile \ --disable-grub-emu \ --disable-grub-emu-usb \ --disable-grub-fstest \ --disable-efiemu --prefix=/some_prefix --options make make install Yes, that is exactly what we are doing. Right now the configure line is ./configure --prefix=/usr \ --sysconfdir=/etc \ --disable-largefile \ --disable-grub-emu \ --disable-grub-emu-usb \ --disable-grub-fstest \ --disable-efiemu Now you have 2k files in the build directory but the ones that are useful can be found under /some_prefix Right and 1200 of them are *.lst files, many of which have 30+ character filenames. Doing an ls puts everything in one column. Even if I expand my terminal to 269 characters, I only get 4 columns of files. It's just hard to navigate. You can find the files installed under /some_prefix in the build directory so you can use them directly as well. Yes, but you have to do `ls -l|grep ^d` just to find out what the directories are. Many of the object files are replicated numerous times because of the way grub links its modules. This may be addressed at later time, there were some patches for simplifying this process. Since there is only one Makefile, I could take a shot at creating a patch to address this problem. Would you be interested in such a patch? -- Bruce ___ Grub-devel mailing list Grub-devel@gnu.org http://lists.gnu.org/mailman/listinfo/grub-devel
Re: grub-1.97
Colin Watson wrote: On Tue, Oct 27, 2009 at 08:59:15PM -0500, Bruce Dubbs wrote: I do have a question. After building a package, we like to test it for those packages that have tests built in. When I tried `make test`, I got an error about missing m2c. I then went to the Debian repository and built m2c. Now I get the error: I don't see the string "m2c" anywhere in GRUB. This is part of the default 'make' rule for building Modula-2 programs, which is irrelevant here; it's an accident of how files happen to be named that it's used at all. GRUB does not have a regression test suite. Thanks for the confirmation. I had checked to see where m2c was used and couldn't find it either. -- Bruce ___ Grub-devel mailing list Grub-devel@gnu.org http://lists.gnu.org/mailman/listinfo/grub-devel
Re: grub-1.97
2009/10/28 Bruce Dubbs : > I am putting grub2 into the Linux From Scratch book and have built/tested it > and it works quite well for us. Thank you. > > I do have a question. After building a package, we like to test it for > those packages that have tests built in. When I tried `make test`, I got an > error about missing m2c. I then went to the Debian repository and built > m2c. Now I get the error: > > bdu...@core2:/usr/src/grub/grub-1.97$ make test > m2c -o test -e test test.mod > m2c: unknown flag `-e' > make: *** [test] Error 1 > > What version of m2c are you using and where is it available? Is this a > valid way to run a regression test for grub-1.97? > > I'd also like to make a comment. It may be useful if you split up the build > into subdirectories by component. When I extracted the tarball, there were > 57 files/directories in the top of the build tree. After configure it was > 64. So far so good. However, after make it was over 2400 files, many with > very long file names. This makes it almost impossible to navigate form the > command line, even on a very big screen. If you split it up, you could also > shorten the filenames. I would think that would be an advantage to > encourage programmers to read the code and contribute to the project. > I guess it's meant to be used like this: tar -jxvf grub-version.tar.bz2 cd grub-version mkdir build cd build ../configure --prefix=/some_prefix --options make make install Now you have 2k files in the build directory but the ones that are useful can be found under /some_prefix You can find the files installed under /some_prefix in the build directory so you can use them directly as well. Many of the object files are replicated numerous times because of the way grub links its modules. This may be addressed at later time, there were some patches for simplifying this process. I have no problems navigating the directory from command line although the layout does seem a bit odd. Maybe it's related to the fact I have some 700 files (excluding .files) in ~. Thanks Michal ___ Grub-devel mailing list Grub-devel@gnu.org http://lists.gnu.org/mailman/listinfo/grub-devel
Re: grub-1.97
On Tue, Oct 27, 2009 at 08:59:15PM -0500, Bruce Dubbs wrote: > I do have a question. After building a package, we like to test it for > those packages that have tests built in. When I tried `make test`, I got > an error about missing m2c. I then went to the Debian repository and > built m2c. Now I get the error: I don't see the string "m2c" anywhere in GRUB. This is part of the default 'make' rule for building Modula-2 programs, which is irrelevant here; it's an accident of how files happen to be named that it's used at all. GRUB does not have a regression test suite. -- Colin Watson [cjwat...@ubuntu.com] ___ Grub-devel mailing list Grub-devel@gnu.org http://lists.gnu.org/mailman/listinfo/grub-devel
grub-1.97
I am putting grub2 into the Linux From Scratch book and have built/tested it and it works quite well for us. Thank you. I do have a question. After building a package, we like to test it for those packages that have tests built in. When I tried `make test`, I got an error about missing m2c. I then went to the Debian repository and built m2c. Now I get the error: bdu...@core2:/usr/src/grub/grub-1.97$ make test m2c-o test -e test test.mod m2c: unknown flag `-e' make: *** [test] Error 1 What version of m2c are you using and where is it available? Is this a valid way to run a regression test for grub-1.97? I'd also like to make a comment. It may be useful if you split up the build into subdirectories by component. When I extracted the tarball, there were 57 files/directories in the top of the build tree. After configure it was 64. So far so good. However, after make it was over 2400 files, many with very long file names. This makes it almost impossible to navigate form the command line, even on a very big screen. If you split it up, you could also shorten the filenames. I would think that would be an advantage to encourage programmers to read the code and contribute to the project. -- Bruce Dubbs linuxfromscratch.org ___ Grub-devel mailing list Grub-devel@gnu.org http://lists.gnu.org/mailman/listinfo/grub-devel
GRUB 1.97 released
Hi, I'm proud to announce the release of GNU GRUB version 1.97. GRUB, also known as the GRand Unified Bootloader, is a modular, portable bootloader that supports a number of platforms, including standard BIOS-based PCs, IEEE-1275 platforms (such as the OLPC and some PowerPC/Sparc64 hardware) and coreboot, the free (as in freedom) pre-boot initialization framework. <http://www.gnu.org/software/grub/> This release of GRUB is a significant breakthrough compared to GRUB 1.96. Among a long list of improvements (excerpt from NEWS file is attached), GRUB 1.97 includes support for booting the kernels of FreeBSD, OpenBSD and NetBSD, it detects the Ext4 filesystem which is commonly used with the kernel Linux, and it implements a robust mechanism for booting from GPT drives, by embedding itself in the BIOS Boot partition. A source tarball for the new release can be found at: http://alpha.gnu.org/gnu/grub/grub-1.97.tar.gz and its GPG detached signature [*]: http://alpha.gnu.org/gnu/grub/grub-1.97.tar.gz.sig [*] You can use either of the above signature files to verify that the corresponding file (without the .sig suffix) is intact. First, be sure to download both the .sig file and the corresponding tarball. Then, run a command like this: gpg --verify grub-1.97.tar.gz.sig If that command fails because you don't have the required public key, then run this command to import it: gpg --keyserver keys.gnupg.net --recv-keys DEA2C38E and rerun the `gpg --verify' command. This release was bootstrapped with the following tools: Autoconf 2.61 Ruby 1.8.7 GCC 4.4 is the recommended version for building it, although any version starting with 4.1.3 is supported in this release. I hope you enjoy using GRUB as much as we enjoyed developing it. -- Robert Millan The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and how) you may access your data; but nobody's threatening your freedom: we still allow you to remove your data and not access it at all." * Add support for loading XNU (MacOS X kernel). * ACPI override support. * Integrated gptsync. * Password protection support. * Partition manipulation tool. * Add `keystatus' command. * Unicode fonts are now used by default. * Add `hdparm' command. * Add support for getting the current date and time from CMOS as variables. * Add `drivemap' command. * Add support for RAID levels 4,6 and 10. * update-grub is replaced by grub-mkconfig. * When booting from PXE, PXE can be used to load files. * High resolution timer support. * Image loaders now support IO buffering. * Add `crc' command. * Add Cygwin support. * Add x86_64 EFI support. * Use LZMA compression instead of LZO. * Support for saving the environment from and loading the environment from a file. * Allow the UUID to be used as device name. * The `search' command can use UUIDs now. * Add support for IEEE 1275 on i386. * Create partmap.lst and use it to automatically load partition map modules. * grub-mkconfig supports os-prober to add operating systems to the boot menu. * The ATA driver supports devices bigger than 2 TiB. * Add support for the UDF, AFS and EXT4 filesystems. * The ISO9660 filesystem supports the Joliet extension * Add support for loading kernels of FreeBSD, NetBSD and OpenBSD. * Add new command `sleep'. * Support for direct access to AT keyboards. * New utility `grub-fstest'. signature.asc Description: Digital signature ___ Grub-devel mailing list Grub-devel@gnu.org http://lists.gnu.org/mailman/listinfo/grub-devel
GRUB 1.97~beta4
Hi, Version 1.97~beta4 of GNU GRUB has been released. -- Robert Millan The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and how) you may access your data; but nobody's threatening your freedom: we still allow you to remove your data and not access it at all." ___ Grub-devel mailing list Grub-devel@gnu.org http://lists.gnu.org/mailman/listinfo/grub-devel
Re: Announcing GNU GRUB 1.97 beta1
2009/9/1 Michal Suchanek : > Hello > > With 1.97 beta1 I cannot use config files like the one attached. > > The message is 'You need to load the kernel first.' > > I did not try with 1.97 beta1 yet but with recent trunk I could not > use the config file but I still could boot using these commands. > > linux /boot/vmlinuz-... root=/dev/sda7 ro > initrd /boot/initrd.img-... > boot > > A there is a suggestion in the Debian bug report to comment out the > search lines but that does not help. > > Any ideas why booting with the config file might fail? > This is because the config file is from a previous broken grub packaged in Debian. I think this problem is caused by not loading the ext2 module before attempting to load the kernel. I will try to test with some modified config file to confirm if this is the case. Thanks Michal ___ Grub-devel mailing list Grub-devel@gnu.org http://lists.gnu.org/mailman/listinfo/grub-devel
Re: grub 1.97 in debian ?
Am Freitag, den 11.09.2009, 19:23 +0200 schrieb Felix Zielcke: > Am Freitag, den 11.09.2009, 22:30 +0530 schrieb J. Bakshi: > > Hello list, > > > > When gurub 1.97 likely be appeared in debian testing ( squeeze) branch ? > > > > thanks > > > > Totally wrong list to ask this. > But to answer your question: > http://packages.qa.debian.org/g/grub2.html > There you can always look up what the status is of the testing > migration. > Currently it's blocked due to a serious regression, which is already in > squeeze version but did only came up now. Well to be clear, s/regression/bug/ -- Felix Zielcke Proud Debian Maintainer ___ Grub-devel mailing list Grub-devel@gnu.org http://lists.gnu.org/mailman/listinfo/grub-devel
Re: grub 1.97 in debian ?
On Fri, 11 Sep 2009 19:23:05 +0200 Felix Zielcke wrote: > Am Freitag, den 11.09.2009, 22:30 +0530 schrieb J. Bakshi: > > Hello list, > > > > When gurub 1.97 likely be appeared in debian testing ( squeeze) > > branch ? > > > > thanks > > > > Totally wrong list to ask this. > But to answer your question: > http://packages.qa.debian.org/g/grub2.html > There you can always look up what the status is of the testing > migration. > Currently it's blocked due to a serious regression, which is already > in squeeze version but did only came up now. > Thanks for your answer. ___ Grub-devel mailing list Grub-devel@gnu.org http://lists.gnu.org/mailman/listinfo/grub-devel
Re: grub 1.97 in debian ?
Am Freitag, den 11.09.2009, 22:30 +0530 schrieb J. Bakshi: > Hello list, > > When gurub 1.97 likely be appeared in debian testing ( squeeze) branch ? > > thanks > Totally wrong list to ask this. But to answer your question: http://packages.qa.debian.org/g/grub2.html There you can always look up what the status is of the testing migration. Currently it's blocked due to a serious regression, which is already in squeeze version but did only came up now. -- Felix Zielcke Proud Debian Maintainer ___ Grub-devel mailing list Grub-devel@gnu.org http://lists.gnu.org/mailman/listinfo/grub-devel
grub 1.97 in debian ?
Hello list, When gurub 1.97 likely be appeared in debian testing ( squeeze) branch ? thanks ___ Grub-devel mailing list Grub-devel@gnu.org http://lists.gnu.org/mailman/listinfo/grub-devel
GRUB 1.97~beta2
GRUB 1.97~beta2 is out. A source tarball (as well as 1.97~beta1 one) is available from the usual location: http://alpha.gnu.org/gnu/grub/ -- Robert Millan The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and how) you may access your data; but nobody's threatening your freedom: we still allow you to remove your data and not access it at all." ___ Grub-devel mailing list Grub-devel@gnu.org http://lists.gnu.org/mailman/listinfo/grub-devel
Re: Announcing GNU GRUB 1.97 beta1
Hello With 1.97 beta1 I cannot use config files like the one attached. The message is 'You need to load the kernel first.' I did not try with 1.97 beta1 yet but with recent trunk I could not use the config file but I still could boot using these commands. linux /boot/vmlinuz-... root=/dev/sda7 ro initrd /boot/initrd.img-... boot A there is a suggestion in the Debian bug report to comment out the search lines but that does not help. Any ideas why booting with the config file might fail? Thanks Michal grub.cfg Description: Binary data ___ Grub-devel mailing list Grub-devel@gnu.org http://lists.gnu.org/mailman/listinfo/grub-devel
Announcing GNU GRUB 1.97 beta1
Hi, I hereby announce the release of GNU GRUB 1.97 beta1. This is the first of the beta releases that will lead to 1.97. I would appreciate if everyone reading this can help the GRUB project by testing this release and making sure it builds, installs and runs as expected. Note: Since I am a new GNU maintainer, I don't yet have access to alpha.gnu.org hosting facilities. Therefore, it may take a while untill 1.97~beta1 tarballs appear in the usual FTP directory [1] (when my key is processed, or when another maintainer takes care of it). In the meantime, you can already obtain this release from SVN: svn export svn://svn.sv.gnu.org/grub/tags/release_1_97~beta1 grub-1.97~beta1 Enjoy! [1] http://alpha.gnu.org/gnu/grub/ -- Robert Millan The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and how) you may access your data; but nobody's threatening your freedom: we still allow you to remove your data and not access it at all." signature.asc Description: Digital signature ___ Grub-devel mailing list Grub-devel@gnu.org http://lists.gnu.org/mailman/listinfo/grub-devel
