On Wed, Oct 5, 2011 at 11:42 AM, Grant Edwards <grant.b.edwa...@gmail.com> wrote: > On 2011-10-05, Canek Pel??ez Vald??s <can...@gmail.com> wrote: > >>> And the set of init scripts that belong to grub2 are just to try to >>> auto-magically generate the config file? >> >> With options from /etc/default/grub, yes. But please stop calling the >> files in /etc/grub.d "init scripts". > > I'm not calling those "init scripts". I'm referring to > > /etc/init.d/grub-common
I don't have that file, and it's not because Gentoo removes it: it was probably added by the Ubuntu developers. > That's an executable /bin/sh shell script. Don't know what that is > called if not an "init script". But it's not part of GRUB2. If you had checked the project sources, or the Gentoo ebuild, you would have realized that it is not a file from the project. > And then there are these (also /bin/sh scripts): > > /etc/grub.d/00_header > /etc/grub.d/05_debian_theme > /etc/grub.d/10_linux > /etc/grub.d/20_memtest86+ > /etc/grub.d/30_os-prober > /etc/grub.d/40_custom > > I assumed these were also some sort of init scripts, but I don't > really know when they get executed. That's the problem: you didn't know how the thing worked, and jumped to conclusions. >> That's the whole reason I dragged the init systems into the >> discussion: you said that GRUB2 "got it's own initsystem and it's own >> set of init scripts." > > You forgot the part where I said "at first glance under Ubuntu, it > appears that" or somesuch. You said that, but your next sentence was "It's got it's own init system and it's own set of init scripts", unequivocally. >> And it's simply not true. Maybe with the best of intentions, but >> that's disinformation. > > To me, /etc/init.d/grub-common is an init script. Maybe in Ubunt (and maybe not: distros this days throw every kind of scripts in /etc/init.d, and Gentoo does this too, BTW), but again you only took a quick look at how it's set in another distro, and jumped to say that the project as a whole (and not the config from a particular distro) "got it's own init system and it's own set of init scripts". To me, that's the definition of spreading disinformation: not looking for all the info, and stating that such and such is or is not when it's simply not true. It's the same history as the myth that /var will not longer be able to be on its own partition: it keeps popping up in many threads, and it's also simply not true. Again, I don't think you did it on purpose with the intention of smear GRUB2 (that was my "with the best of intentions" part), but *it is* disinformation. To finish: GRUB2 does not need or have init scripts, it doesn't have it's own init system, and if your setup works with GRUB, it will work in GRUB2, but you will probably need to learn a new way to configure it. The other way around is not true: GRUB will not support all the setups that GRUB2 will, unless someone steps up and writes the code for it. Regards. -- Canek Peláez Valdés Posgrado en Ciencia e Ingeniería de la Computación Universidad Nacional Autónoma de México
