[résolu] Re: clé usb multi boot pour installer debian
je me réponds, désolé pour le bruit. Après, si ça peut servir...
Le site du gars qui a rencontré le même problème:
https://www.dwarmstrong.org/multi-boot-usb/
Comme l'iso netinst ne contient pas le module iso-scan, il faut aller le
chercher dans un autre initrd (
https://ftp.debian.org/debian/dists/stable/main/installer-amd64/current/images/hd-media/)
Et ainsi le paragraphe dans grub.cfg devient
menuentry "Debian 10.7 64b" {
set iso="/debian-10.7.0-amd64-netinst.iso"
loopback loop $iso
linux (loop)/install.amd/vmlinuz iso-scan/ask_second_pass=true
iso-scan/filename=$iso priority=low gfxpayload=text quiet
initrd /debian/install.amd/initrd.gz
}
Noter l'absence de loop devant l'initrd (au contraire de tous les distri
live)
a+
f.
Le 05/01/2021 à 12:00, fabricer a écrit :
Hello la liste,
Déjà bonne année, en espérant qu'elle soit moins moisie que la précédente.
J'utilise une clé usb multiboot
(https://www.pendrivelinux.com/boot-multiple-iso-from-usb-via-grub2-using-linux/)
pour avoir à dispo sur une grosse clé plusieurs distri live 32/64 que je
peux installer vite fait sur les postes des copains.
L'idée de base : tu colles un iso sur la clé et tu modifies le grub.cfg
et voilà. Ça fonctionne au poil avec la plupart des distris (il faut
parfois chercher un peu comment rédiger le paragraphe qui va bien dans
le grub.cfg).
J'ai voulu faire la même chose avec une debian-10.7.0-amd64-netinst.iso
Voici le crub.cfg correspondant:
menuentry "Debian 10.7 64b" {
set iso="/debian-10.7.0-amd64-netinst.iso"
loopback loop $iso
linux (loop)/install.amd/vmlinuz iso-scan/ask_second_pass=true
iso-scan/filename=$iso priority=low gfxpayload=text quiet
initrd (loop)/install.amd/initrd.gz
}
L'install démarre correctement mais au moment de chercher le CD où sont
les data, l'installateur ne voit plus rien.
L'un de vous a t-il déjà réalisé cette opération ?
En sachant que:
* je ne souhaite pas cette fois, copier l'iso
debian-10.7.0-amd64-netinst.iso seul sur une clé. C'est ce que je fais
d'habitude avec succès mais à chaque fois, ça m'oblige à formater une
clé. Je souhaiterai vraiment utiliser ce multi boot user-friendly
* j'ai vu que debian proposait des iso live
(https://cdimage.debian.org/debian-cd/current-live/amd64/iso-hybrid/).
Mais il faut choisir un bureau et l'iso standart fait 945Mo. Ç'est
beaucoup pour une install basique type netinst.
Merki ;)
f.
clé usb multi boot pour installer debian
Hello la liste,
Déjà bonne année, en espérant qu'elle soit moins moisie que la précédente.
J'utilise une clé usb multiboot
(https://www.pendrivelinux.com/boot-multiple-iso-from-usb-via-grub2-using-linux/)
pour avoir à dispo sur une grosse clé plusieurs distri live 32/64 que je
peux installer vite fait sur les postes des copains.
L'idée de base : tu colles un iso sur la clé et tu modifies le grub.cfg
et voilà. Ça fonctionne au poil avec la plupart des distris (il faut
parfois chercher un peu comment rédiger le paragraphe qui va bien dans
le grub.cfg).
J'ai voulu faire la même chose avec une debian-10.7.0-amd64-netinst.iso
Voici le crub.cfg correspondant:
menuentry "Debian 10.7 64b" {
set iso="/debian-10.7.0-amd64-netinst.iso"
loopback loop $iso
linux (loop)/install.amd/vmlinuz iso-scan/ask_second_pass=true
iso-scan/filename=$iso priority=low gfxpayload=text quiet
initrd (loop)/install.amd/initrd.gz
}
L'install démarre correctement mais au moment de chercher le CD où sont
les data, l'installateur ne voit plus rien.
L'un de vous a t-il déjà réalisé cette opération ?
En sachant que:
* je ne souhaite pas cette fois, copier l'iso
debian-10.7.0-amd64-netinst.iso seul sur une clé. C'est ce que je fais
d'habitude avec succès mais à chaque fois, ça m'oblige à formater une
clé. Je souhaiterai vraiment utiliser ce multi boot user-friendly
* j'ai vu que debian proposait des iso live
(https://cdimage.debian.org/debian-cd/current-live/amd64/iso-hybrid/).
Mais il faut choisir un bureau et l'iso standart fait 945Mo. Ç'est
beaucoup pour une install basique type netinst.
Merki ;)
f.
Re: dual boot (multi-boot) (was: Help Installing a Dual...)
Michael Fothergill composed on 2017-01-22 14:08 (UTC): I run a dual boot system with debian, gentoo and windows 10 on different partitions. Dual means "two": https://www.merriam-webster.com/dictionary/dual https://en.wiktionary.org/wiki/dual http://www.dictionary.com/browse/dual?s=t 1.of, relating to, or noting two. 2.composed or consisting of two people, items, parts, etc., together; twofold; double: dual ownership; dual controls on a plane. 3.having a twofold, or double, character or nature. 4.Grammar. being or pertaining to a member of the category of number, as in Old English, Old Russian, or Arabic, that denotes two of the things in question. ... As you have three installed operating systems, you do have a multi-boot system, as well as a triple boot system. Those with dual boot, quadruple boot, quintuple boot, etc. systems also have multi-boot systems. Multi-boot means more than one installed operating system. https://en.wikipedia.org/wiki/Multi-booting -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/
Re: Choosing default OS in multi boot system
On 2013-10-30, Jonathan Dowland j...@debian.org wrote: I've wondered about this or something similar. Has anyone tried having each OS install their grub to their partition, rather than the MBR ??? and then having a separate grub configuration that installs onto the MBR which lets you chain-load each of the partitions (or LVs or whatever?) My thinking is that the MBR-level grub will not need to be updated much, and various OS's machinery built on top of grub to update when you put a new kernel in, etc., are less likely to trample on each other (or the MBR) if you have told them (or d-i or whatever) to not install to the MBR themselves. Does that sound sane? Yes, I do exactly that, and have done that on all my computers for years. You can create a small partition to install Grub alone. Install Grub to MBR and later Grub stages to to this ext3 partition. All GNU/Linux distros installed on said system have Grub installed to their own root partitions. (chainload Grub to Grub) Or if it be a great hassle for you to create a separate Grub partition as you now have your drive(s) currently partitioned, just use the first Linux partition that has a GNU/Linux distro installed on the first drive to install Grub MBR and later stages to, and chainload the other Operating Systems installed on drive(s) from there. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20131104083525.825@0.0.0
Re: Choosing default OS in multi boot system
On Mon, 2013-11-04 at 14:04 +, Kruppt wrote: On 2013-10-30, Jonathan Dowland j...@debian.org wrote: I've wondered about this or something similar. Has anyone tried having each OS install their grub to their partition, rather than the MBR ??? and then having a separate grub configuration that installs onto the MBR which lets you chain-load each of the partitions (or LVs or whatever?) My thinking is that the MBR-level grub will not need to be updated much, and various OS's machinery built on top of grub to update when you put a new kernel in, etc., are less likely to trample on each other (or the MBR) if you have told them (or d-i or whatever) to not install to the MBR themselves. Does that sound sane? Yes, I do exactly that, and have done that on all my computers for years. You can create a small partition to install Grub alone. Install Grub to MBR and later Grub stages to to this ext3 partition. All GNU/Linux distros installed on said system have Grub installed to their own root partitions. (chainload Grub to Grub) Or if it be a great hassle for you to create a separate Grub partition as you now have your drive(s) currently partitioned, just use the first Linux partition that has a GNU/Linux distro installed on the first drive to install Grub MBR and later stages to, and chainload the other Operating Systems installed on drive(s) from there. I also do this, in particular since one of the OS is Windows 7 pro it does not play nicely with others LOL. john -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1383594648.9859.1.ca...@beast.johnwfoster.com
Re: Choosing default OS in multi boot system
On Wed, Oct 30, 2013 at 05:25:45PM +, Lisi Reisz wrote: On Wednesday 30 October 2013 16:45:18 Darac Marjal wrote: Actually, it's possible to remap keys in the shell. How?? OK, a quick web search says the technique I used to use (a series of setkey statements) is no longer supported in grub2. Instead the incantation is: $ sudo mkdir -p /boot/grub/layouts $ ckbcomp us dvorak | sudo grub-mklayout -o \ /boot/grub/layouts/us:dvorak.gkb $ echo GRUB_TERMINAL_INPUT=at_keyboard | sudo tee -a \ /etc/default/grub $ sudo update-grub2 (Cadged from Bug #623975). Adjust for whatever layout you prefer, of course. I used to use a dvorak keyboard with grub quite happily. Thanks, Lisi -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201310301725.45330.lisi.re...@gmail.com signature.asc Description: Digital signature
Re: Choosing default OS in multi boot system
On Thursday 31 October 2013 09:08:32 Darac Marjal wrote: On Wed, Oct 30, 2013 at 05:25:45PM +, Lisi Reisz wrote: On Wednesday 30 October 2013 16:45:18 Darac Marjal wrote: Actually, it's possible to remap keys in the shell. How?? OK, a quick web search says the technique I used to use (a series of setkey statements) is no longer supported in grub2. Instead the incantation is: $ sudo mkdir -p /boot/grub/layouts $ ckbcomp us dvorak | sudo grub-mklayout -o \ /boot/grub/layouts/us:dvorak.gkb $ echo GRUB_TERMINAL_INPUT=at_keyboard | sudo tee -a \ /etc/default/grub $ sudo update-grub2 Thanks, Darac! That's really helpful. There are some keys on an American keyboard that I simply cannot remember. Must be my age or something. ;-) I am also so scared of GRUB2 that I have so far not dared to do anything with it other than let it run. If I can now demand that it at least uses a keyboard that I do not have to memorise (because I can _see_ it!) I am one stage nearer using it. Great. :-) Lisi -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201310312326.53263.lisi.re...@gmail.com
Choosing default OS in multi boot system
I have a laptop physically set aside for _experimenting_ with install parameters to determine my optimum configuration. One install will duplicate as closely as possible whatever comes with some donated hardware for the church's after school program for pre-teens. The combination of running the Debian Installer with as many defaults as possible and Grub2 being automatically installed each time results in two annoying characteristics. ONE: On boot, the the last system installed will be the default. That is the least likely one to run correctly (IF AT ALL) due to bad choices during install or subsequent tweaking. Resulting Grub rescue mode ... ;/ TWO: When there are multiple Debian installs present, especially when same kernel used, the Grub menu is not informative. QUESTION_ONE: Can I force the boot to default to the oldest rather than newest install. It will always be a functioning install and usually is completely normal with ONLY defaults chosen. QUESTION_TWO: Is there an automatic way for the Grub menu to display the associated partition label instead of the kernel id? the partition designation (sda1 ... sda8 etc) would be minimally acceptable. I could manually edit the configuration file which advises DO NT EDIT ;/ I do occasionally try to follow convention :) TIA -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/52710fe5.2050...@cloud85.net
Re: Choosing default OS in multi boot system
On Wed 30 Oct 2013 at 08:55:49 -0500, Richard Owlett wrote: The combination of running the Debian Installer with as many defaults as possible and Grub2 being automatically installed each time results in two annoying characteristics. ONE: On boot, the the last system installed will be the default. That is the least likely one to run correctly (IF AT ALL) due to bad choices during install or subsequent tweaking. Resulting Grub rescue mode ... ;/ TWO: When there are multiple Debian installs present, especially when same kernel used, the Grub menu is not informative. QUESTION_ONE: Can I force the boot to default to the oldest rather than newest install. It will always be a functioning install and usually is completely normal with ONLY defaults chosen. Do not install GRUB for the new install. Run update-grub from whatever you do boot into. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/30102013140939.554b1723a...@desktop.copernicus.demon.co.uk
Re: Choosing default OS in multi boot system
Le 30.10.2013 14:55, Richard Owlett a écrit : I have a laptop physically set aside for _experimenting_ with install parameters to determine my optimum configuration. One install will duplicate as closely as possible whatever comes with some donated hardware for the church's after school program for pre-teens. The combination of running the Debian Installer with as many defaults as possible and Grub2 being automatically installed each time results in two annoying characteristics. ONE: On boot, the the last system installed will be the default. That is the least likely one to run correctly (IF AT ALL) due to bad choices during install or subsequent tweaking. Resulting Grub rescue mode ... ;/ TWO: When there are multiple Debian installs present, especially when same kernel used, the Grub menu is not informative. QUESTION_ONE: Can I force the boot to default to the oldest rather than newest install. It will always be a functioning install and usually is completely normal with ONLY defaults chosen. QUESTION_TWO: Is there an automatic way for the Grub menu to display the associated partition label instead of the kernel id? the partition designation (sda1 ... sda8 etc) would be minimally acceptable. I could manually edit the configuration file which advises DO NT EDIT ;/ I do occasionally try to follow convention :) TIA My replies to your questions are: probably. You probably can do those things, but I have no idea about how, because grub became too complex to maintain. I allow you to understand here, that I think grub is bloated for my uses. Your problems are the exact ones I had, and which made me switch to lilo. Where Grub is bloated, lilo obviously lacks small features: _ no QWERTY text editor inside ( it is anyway a pain to use such keyboard if you do not usually use qwerty keyboards, as I ) _ no automatic updates when you add or remove a kernel ( os-prober does not change the /etc/lilo.conf file, so you must be careful on kernel updates. But you should anyway always be, right? ) But, by being simple, it's damn easy to add a new OS, it takes 5 lines (and some are not mandatory) at the end of the config file: === image = /boot/vmlinuz-3.2.0-2-amd64 label= linux-old root = /dev/sda6 initrd = /boot/initrd.img-3.2.0-2-amd64 read-only === I do not think I need to explain the content of those lines, except that I have used the old way /dev/sda6 for partition names, but indeed, other ones works too. It's simply that this way is easier to maintain than 9dfd6ae9-d0ff-46ef-ac65-7bb9dbe7b614. For the default system, there is a dedicated line: === default=Linux-old === There are other various things, mostly to configure the selection menu ( do you want a CLI interface, ncurse-like interface, or graphical one? How much time do you want to have to choose default? etc) but you will learn about them easily by reading comments in debian's default lilo.conf. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/43e32ac393b2193e28b696a338c06...@neutralite.org
Re: Choosing default OS in multi boot system
Brian wrote: On Wed 30 Oct 2013 at 08:55:49 -0500, Richard Owlett wrote: The combination of running the Debian Installer with as many defaults as possible and Grub2 being automatically installed each time results in two annoying characteristics. ONE: On boot, the the last system installed will be the default. That is the least likely one to run correctly (IF AT ALL) due to bad choices during install or subsequent tweaking. Resulting Grub rescue mode ... ;/ TWO: When there are multiple Debian installs present, especially when same kernel used, the Grub menu is not informative. QUESTION_ONE: Can I force the boot to default to the oldest rather than newest install. It will always be a functioning install and usually is completely normal with ONLY defaults chosen. Do not install GRUB for the new install. Run update-grub from whatever you do boot into. Thought I had tried that. Got a couple of installs to do today. I'll try it. Thanks. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/52711887.8030...@cloud85.net
Re: Choosing default OS in multi boot system
berenger.mo...@neutralite.org wrote: Le 30.10.2013 14:55, Richard Owlett a écrit : I have a laptop physically set aside for _experimenting_ with install parameters to determine my optimum configuration. One install will duplicate as closely as possible whatever comes with some donated hardware for the church's after school program for pre-teens. The combination of running the Debian Installer with as many defaults as possible and Grub2 being automatically installed each time results in two annoying characteristics. ONE: On boot, the the last system installed will be the default. That is the least likely one to run correctly (IF AT ALL) due to bad choices during install or subsequent tweaking. Resulting Grub rescue mode ... ;/ TWO: When there are multiple Debian installs present, especially when same kernel used, the Grub menu is not informative. QUESTION_ONE: Can I force the boot to default to the oldest rather than newest install. It will always be a functioning install and usually is completely normal with ONLY defaults chosen. QUESTION_TWO: Is there an automatic way for the Grub menu to display the associated partition label instead of the kernel id? the partition designation (sda1 ... sda8 etc) would be minimally acceptable. I could manually edit the configuration file which advises DO NT EDIT ;/ I do occasionally try to follow convention :) TIA My replies to your questions are: probably. You probably can do those things, but I have no idea about how, because grub became too complex to maintain. I allow you to understand here, that I think grub is bloated for my uses. Your problems are the exact ones I had, and which made me switch to lilo. Where Grub is bloated, lilo obviously lacks small features: Don't know if I'd call Grub2 bloated, but Grub-legacy was friendlier. _ no QWERTY text editor inside ( it is anyway a pain to use such keyboard if you do not usually use qwerty keyboards, as I ) Didn't know either Grub or lilo had an internal editor. _ no automatic updates when you add or remove a kernel ( os-prober does not change the /etc/lilo.conf file, so you must be careful on kernel updates. But you should anyway always be, right? ) Automation was motivation for staying with Grub, but may not be worth the bother. But, by being simple, it's damn easy to add a new OS, it takes 5 lines (and some are not mandatory) at the end of the config file: === image = /boot/vmlinuz-3.2.0-2-amd64 label= linux-old root = /dev/sda6 initrd = /boot/initrd.img-3.2.0-2-amd64 read-only === I do not think I need to explain the content of those lines, except that I have used the old way /dev/sda6 for partition names, but indeed, other ones works too. It's simply that this way is easier to maintain than 9dfd6ae9-d0ff-46ef-ac65-7bb9dbe7b614. For the default system, there is a dedicated line: === default=Linux-old === There are other various things, mostly to configure the selection menu ( do you want a CLI interface, ncurse-like interface, or graphical one? How much time do you want to have to choose default? etc) but you will learn about them easily by reading comments in debian's default lilo.conf. I experimented with it some time ago. Don't recall it being too difficult to deal with. Also I have become more familiar/comfortable with Debian/*nix way of doing things in the meantime. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/52711c57.5090...@cloud85.net
Re: Choosing default OS in multi boot system
On Wednesday, October 30, 2013 10:48:55 AM Richard Owlett wrote: Don't know if I'd call Grub2 bloated, but Grub-legacy was friendlier. Maybe not bloated, but grub2 was certainly broken the last time I tried it. Specifically, (1) when I installed a system using grub2, it would install on the first drive it found grub on, never mind that I told it to install to a different drive. (2) I could never get it to work on an ISO, a thumb drive with the contents of the ISO (but not an ISO FS) and a hard drive. 3-4 weeks I spent building, testing, debugging. I gave up and went back to grub legacy. Four hours later I had it working as desired. If grub2 has improved in the past couple years (sounds like it hasn't), I'll eventually look at it again; if it hasn't, my system will remain with grub legacy (built with the huge RedHat patchset and a few of my own bug fixes). N -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201310301115.47020.neal.p.mur...@alum.wpi.edu
Re: Choosing default OS in multi boot system
Le 30.10.2013 15:48, Richard Owlett a écrit : berenger.mo...@neutralite.org wrote: Le 30.10.2013 14:55, Richard Owlett a écrit : I have a laptop physically set aside for _experimenting_ with install parameters to determine my optimum configuration. One install will duplicate as closely as possible whatever comes with some donated hardware for the church's after school program for pre-teens. The combination of running the Debian Installer with as many defaults as possible and Grub2 being automatically installed each time results in two annoying characteristics. ONE: On boot, the the last system installed will be the default. That is the least likely one to run correctly (IF AT ALL) due to bad choices during install or subsequent tweaking. Resulting Grub rescue mode ... ;/ TWO: When there are multiple Debian installs present, especially when same kernel used, the Grub menu is not informative. QUESTION_ONE: Can I force the boot to default to the oldest rather than newest install. It will always be a functioning install and usually is completely normal with ONLY defaults chosen. QUESTION_TWO: Is there an automatic way for the Grub menu to display the associated partition label instead of the kernel id? the partition designation (sda1 ... sda8 etc) would be minimally acceptable. I could manually edit the configuration file which advises DO NT EDIT ;/ I do occasionally try to follow convention :) TIA My replies to your questions are: probably. You probably can do those things, but I have no idea about how, because grub became too complex to maintain. I allow you to understand here, that I think grub is bloated for my uses. Your problems are the exact ones I had, and which made me switch to lilo. Where Grub is bloated, lilo obviously lacks small features: Don't know if I'd call Grub2 bloated, but Grub-legacy was friendlier. In my own and humble opinion, and for my needs, it is. I do not hate grub, since when you do not have complex needs it works out of the box, and maintains itself (in fact, not really itself, it's os-prober plus some dpkg hooks which maintains it), unlike Lilo for the last point (which does not have the required hooks). But when you need to take control on your boot loader, Lilo is better, because you have less things to bother with, and I only say that because I tried to use both grub1 and grub2 (it was the transition, which did not helped my mind). Lilo was really damn easy to configure, and worked in 5 minutes, maybe less. I also had problems at installation time with grub on some installations (it refuses to installs itself, for obscure reasons, leading to unusable system), and lilo had none. Grub is able to read a configuration file when it runs, this is why there is no need ( or at least, there were ) to run a tool to update it (lilo reinstalls itself on boot sector everytime you run #lilo). But I think it was in the old grub1, now you need to run something like #update-grub to update the configuration file (???), so the strong point of grub is no longer a strong point. It also includes a shell, to tune your booting options before booting. This might be useful for 2 situations I can see: booting on a guest HD (but for that, the easier is to install a boot loader on the guest HD itself), or fixing errors (and in such situation, I prefer to simply boot on the old kernel, with it's old options, and then fix the errors definitely, instead of playing with things without auto-completion or any warning from the system). Those features are very rarely useful, if useful at all (the shell is almost unusable for people who do not know the american qwerty layout, for example), so I name it bloated. But it is not important, because the boot loader have no impact on how the system works when booted, and normal users do not even know that it exists. There are more important softwares with more critical problems :) The only problem (but not a small one) of Lilo for normal users is the need to edit the configuration file (and so, to run #lilo after) when a kernel with a different name is installed or removed*, which does not happen in stable Debian (the one officially recommended for users). *: Note that if the alternative system was extended to the kernels, aka if kernels were installed with both their real name plus 2 variants, say, linux-old and linux-last, that problem of manually editing /etc/lilo.conf and running lilo then would not be present. We could also imagine for mixed installations adding the distribution stableness in the name, like linux-testing-old, plus an identifier for system name ( root partition would probably be the best choice, being by uuid, label or /dev name ). This could provide a way for automatic updates for lilo/syslinux without changing configuration files or source code at all. Maybe the metapackages linux-image* could handle that, I do not know. _ no QWERTY text editor inside ( it is anyway a pain to
Re: Choosing default OS in multi boot system
Le 30.10.2013 16:58, berenger.mo...@neutralite.org a écrit : which does not happen in stable Debian (the one officially recommended for users). Error from myself, sorry, it happens in stable too. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/43902e12ea8d7bd926ca50d3a0f8d...@neutralite.org
Re: Choosing default OS in multi boot system
On Wed, Oct 30, 2013 at 04:58:13PM +0100, berenger.mo...@neutralite.org wrote: [cut] Don't know if I'd call Grub2 bloated, but Grub-legacy was friendlier. In my own and humble opinion, and for my needs, it is. I do not hate grub, since when you do not have complex needs it works out of the box, and maintains itself (in fact, not really itself, it's os-prober plus some dpkg hooks which maintains it), unlike Lilo for the last point (which does not have the required hooks). But when you need to take control on your boot loader, Lilo is better, because you have less things to bother with, and I only say that because I tried to use both grub1 and grub2 (it was the transition, which did not helped my mind). Lilo was really damn easy to configure, and worked in 5 minutes, maybe less. I also had problems at installation time with grub on some installations (it refuses to installs itself, for obscure reasons, leading to unusable system), and lilo had none. Grub is able to read a configuration file when it runs, this is why there is no need ( or at least, there were ) to run a tool to update it (lilo reinstalls itself on boot sector everytime you run #lilo). But I think it was in the old grub1, now you need to run something like #update-grub to update the configuration file (???), so the strong point of grub is no longer a strong point. Actually, just to clarify something there. You don't NEED to run the update-grub script. As I understand it, LILO boots by jumping execution to a defined point on the disk (the start of the kernel). When you install a new kernel, you have to tell LILO where to find the new file. For grub2, most of what update-grub is doing is parsing the kernel version and adding it to the menu. In both situations, it's possible to use /vmlinuz and /vmlinuz.old symlinks and have Linux and Old Linux menu entries. When you install a new kernel, you point /vmlinuz at it and /vmlinuz.old at the previous kernel. Then, without changing either boot loader, the new kernel will be loaded. Where Grub shines, though, is if you want to (or have to) move partitions around. Say you need a larger swap partition, so you expand /dev/sda1 (swap) and shrink /dev/sda2 (root). In shrinking /dev/sda2, all your data moves across the disk. Now you need to re-run LILO to find the kernel again. But because GRUB actually understands the partition table and filesystem, it's able to see where the file has moved to and can boot without effort. It also includes a shell, to tune your booting options before booting. This might be useful for 2 situations I can see: booting on a guest HD (but for that, the easier is to install a boot loader on the guest HD itself), or fixing errors (and in such situation, I prefer to simply boot on the old kernel, with it's old options, and then fix the errors definitely, instead of playing with things without auto-completion or any warning from the system). Those features are very rarely useful, if useful at all (the shell is almost unusable for people who do not know the american qwerty layout, for example), so I name it bloated. Actually, it's possible to remap keys in the shell. I used to use a dvorak keyboard with grub quite happily. -- vv Email vvTwitter da...@darac.org.uk Website ^^ XMPP signature.asc Description: Digital signature
Re: Choosing default OS in multi boot system
On Wednesday 30 October 2013 16:45:18 Darac Marjal wrote: Actually, it's possible to remap keys in the shell. How?? I used to use a dvorak keyboard with grub quite happily. Thanks, Lisi -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201310301725.45330.lisi.re...@gmail.com
Re: Choosing default OS in multi boot system
On 30/10/13 10:16 AM, Brian wrote: On Wed 30 Oct 2013 at 08:55:49 -0500, Richard Owlett wrote: The combination of running the Debian Installer with as many defaults as possible and Grub2 being automatically installed each time results in two annoying characteristics. ONE: On boot, the the last system installed will be the default. That is the least likely one to run correctly (IF AT ALL) due to bad choices during install or subsequent tweaking. Resulting Grub rescue mode ... ;/ TWO: When there are multiple Debian installs present, especially when same kernel used, the Grub menu is not informative. QUESTION_ONE: Can I force the boot to default to the oldest rather than newest install. It will always be a functioning install and usually is completely normal with ONLY defaults chosen. Do not install GRUB for the new install. Run update-grub from whatever you do boot into. I've been dealing with a similar problem . I have 2 partitions with Linux on them --sda3 with Debian and sda4 with Fedora. When ever Debian installs a new kernel the dpkg hooks update grub.cfg...however Grub was installed from my Fedora system and its' grub.cfg needs to be updated. So I have to boot into Fedora, update grub.cfg, then reboot into Debian. Real PITA which I have yet to find a solution to. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/5271436d.4000...@videotron.ca
Re: Choosing default OS in multi boot system
I've wondered about this or something similar. Has anyone tried having each OS install their grub to their partition, rather than the MBR — and then having a separate grub configuration that installs onto the MBR which lets you chain-load each of the partitions (or LVs or whatever?) My thinking is that the MBR-level grub will not need to be updated much, and various OS's machinery built on top of grub to update when you put a new kernel in, etc., are less likely to trample on each other (or the MBR) if you have told them (or d-i or whatever) to not install to the MBR themselves. Does that sound sane? -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20131030182211.gc12...@bryant.redmars.org
Re: Choosing default OS in multi boot system
On Wed 30 Oct 2013 at 08:55:49 -0500, Richard Owlett wrote: QUESTION_TWO: Is there an automatic way for the Grub menu to display the associated partition label instead of the kernel id? the partition designation (sda1 ... sda8 etc) would be minimally acceptable. Automating the menu display in this way is done with 10_linux and 30_os-prober in /etc/grub.d. Edits to them will stick because they are conffiles. An indication of what can be done is at http://ubuntu-install.blogspot.co.uk/2009/11/grub2-title-tweaks.html -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/30102013182337.d50a3bba8...@desktop.copernicus.demon.co.uk
Re: Choosing default OS in multi boot system
Brian wrote: On Wed 30 Oct 2013 at 08:55:49 -0500, Richard Owlett wrote: QUESTION_TWO: Is there an automatic way for the Grub menu to display the associated partition label instead of the kernel id? the partition designation (sda1 ... sda8 etc) would be minimally acceptable. Automating the menu display in this way is done with 10_linux and 30_os-prober in /etc/grub.d. Edits to them will stick because they are conffiles. An indication of what can be done is at http://ubuntu-install.blogspot.co.uk/2009/11/grub2-title-tweaks.html Just glanced at it and the first few of its included links. I think I've got some reading ahead of me. Weatherman predicting 2-3 days rain - guess I'll have time ;) P.S. there are hints of answers to questions I hadn't thought of asking. Thank you -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/52715af4.4060...@cloud85.net
Re: Choosing default OS in multi boot system
On Wed 30 Oct 2013 at 09:32:39 -0500, Richard Owlett wrote: Brian wrote: Do not install GRUB for the new install. Run update-grub from whatever you do boot into. Thought I had tried that. Got a couple of installs to do today. I'll try it. Thanks. Perhaps it would be less work to try a solution using 'GRUB_DEFAULT' The default menu entry. This may be a number, in which case it identifies the Nth entry in the generated menu counted from zero, or the full name of a menu entry, or the special string 'saved'. Using the full name may be useful if you want to set a menu entry as the default even though there may be a variable number of entries before it. If you set this to 'saved' then the default menu entry will be that saved by 'GRUB_SAVEDEFAULT', 'grub-set-default', or 'grub-reboot'. The default is '0'. This is from 'info grub' (well, because I find it a friendlier program, 'pinfo grub'). -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/30102013195434.cebde7717...@desktop.copernicus.demon.co.uk
Re: Dúvida multi-boot Debian + Kali onde ficará o GRUB?
Caros, Por hora testei instalando o Kali e usando o grub dele na MBR, que reconheceu o Debian já instalado. Funcionou normalmente. Ainda vou testar instalar o Kali e omitir seu grub, para que o grub do Debian permaneça o principal, e postarei os resultados. Abraços Em 24 de julho de 2013 17:12, CássioElias . cassioel...@hotmail.comescreveu: Você disse: Já tenho o Debian instalado, com seu grub e tudo o mais. Quando eu instalar o Kali, devo omitir a configuração do grub dele e em seguida rodar update-grub no debian para reconhecer o Kali? Acredito que sim. Omita a instalação do Grub pelo Kali, e depois no Debian você configura o Grub para puxar o Kali quandi iniciar. -- Date: Wed, 24 Jul 2013 16:30:43 -0300 Subject: Re: Dúvida multi-boot Debian + Kali onde ficará o GRUB? From: sh11td...@gmail.com To: debian-user-portuguese@lists.debian.org Ninguém? Em 22 de julho de 2013 18:24, Shutdown -h now sh11td...@gmail.comescreveu: Caros, Tenho um Debian Jessie kernel 3.9 em meu notebook, e pretendo instalar também um Linux Kali (http://www.kali.org/) Aí me surgiu a seguinte dúvida: Já tenho o Debian instalado, com seu grub e tudo o mais. Quando eu instalar o Kali, devo omitir a configuração do grub dele e em seguida rodar update-grub no debian para reconhecer o Kali? Ou devo instalar o novo grub no lugar do grub antigo, para que este novo reconheça ambos sistemas? As soluções que encontrei em pesquisas na internet foram essas 2 acima, mas eu queria saber as implicações de cada uma e melhorer práticas neste caso, e além disso: * Num caso de multi-boot apenas com sistemas GNU/Linux, é melhor instalar o grub (ou cada grub) na MBR ou na(s) partição(ões) raiz? * Existe alguma forma de saber se o grub do sistema atual foi instalado na MBR ou na partição raiz? Toda e qualquer ajuda é bem vinda. Abraços
Re: Dúvida multi-boot Debian + Kali onde ficará o GRUB?
Ninguém? Em 22 de julho de 2013 18:24, Shutdown -h now sh11td...@gmail.comescreveu: Caros, Tenho um Debian Jessie kernel 3.9 em meu notebook, e pretendo instalar também um Linux Kali (http://www.kali.org/) Aí me surgiu a seguinte dúvida: Já tenho o Debian instalado, com seu grub e tudo o mais. Quando eu instalar o Kali, devo omitir a configuração do grub dele e em seguida rodar update-grub no debian para reconhecer o Kali? Ou devo instalar o novo grub no lugar do grub antigo, para que este novo reconheça ambos sistemas? As soluções que encontrei em pesquisas na internet foram essas 2 acima, mas eu queria saber as implicações de cada uma e melhorer práticas neste caso, e além disso: * Num caso de multi-boot apenas com sistemas GNU/Linux, é melhor instalar o grub (ou cada grub) na MBR ou na(s) partição(ões) raiz? * Existe alguma forma de saber se o grub do sistema atual foi instalado na MBR ou na partição raiz? Toda e qualquer ajuda é bem vinda. Abraços
RE: Dúvida multi-boot Debian + Kali onde ficará o GRUB?
Você disse: Já tenho o Debian instalado, com seu grub e tudo o mais. Quando eu instalar o Kali, devo omitir a configuração do grub dele e em seguida rodar update-grub no debian para reconhecer o Kali? Acredito que sim. Omita a instalação do Grub pelo Kali, e depois no Debian você configura o Grub para puxar o Kali quandi iniciar. Date: Wed, 24 Jul 2013 16:30:43 -0300 Subject: Re: Dúvida multi-boot Debian + Kali onde ficará o GRUB? From: sh11td...@gmail.com To: debian-user-portuguese@lists.debian.org Ninguém? Em 22 de julho de 2013 18:24, Shutdown -h now sh11td...@gmail.com escreveu: Caros, Tenho um Debian Jessie kernel 3.9 em meu notebook, e pretendo instalar também um Linux Kali (http://www.kali.org/) Aí me surgiu a seguinte dúvida: Já tenho o Debian instalado, com seu grub e tudo o mais. Quando eu instalar o Kali, devo omitir a configuração do grub dele e em seguida rodar update-grub no debian para reconhecer o Kali? Ou devo instalar o novo grub no lugar do grub antigo, para que este novo reconheça ambos sistemas? As soluções que encontrei em pesquisas na internet foram essas 2 acima, mas eu queria saber as implicações de cada uma e melhorer práticas neste caso, e além disso: * Num caso de multi-boot apenas com sistemas GNU/Linux, é melhor instalar o grub (ou cada grub) na MBR ou na(s) partição(ões) raiz? * Existe alguma forma de saber se o grub do sistema atual foi instalado na MBR ou na partição raiz? Toda e qualquer ajuda é bem vinda. Abraços
Dúvida multi-boot Debian + Kali onde ficará o GRUB?
Caros, Tenho um Debian Jessie kernel 3.9 em meu notebook, e pretendo instalar também um Linux Kali (http://www.kali.org/) Aí me surgiu a seguinte dúvida: Já tenho o Debian instalado, com seu grub e tudo o mais. Quando eu instalar o Kali, devo omitir a configuração do grub dele e em seguida rodar update-grub no debian para reconhecer o Kali? Ou devo instalar o novo grub no lugar do grub antigo, para que este novo reconheça ambos sistemas? As soluções que encontrei em pesquisas na internet foram essas 2 acima, mas eu queria saber as implicações de cada uma e melhorer práticas neste caso, e além disso: * Num caso de multi-boot apenas com sistemas GNU/Linux, é melhor instalar o grub (ou cada grub) na MBR ou na(s) partição(ões) raiz? * Existe alguma forma de saber se o grub do sistema atual foi instalado na MBR ou na partição raiz? Toda e qualquer ajuda é bem vinda. Abraços
Re: portable Lenovo et Debian (was Re: Debian UEFI et multi boot)
Salut à tous, j'y vais de ma contribution alors... température à peu près constante 48 degres ventilo inaudible ... je suis sous KDE alors que je ne l'aime pas car les extensions Gnome 3 (joli desktop) font monter la température de + de 10 degres donc je ne l'utilise plus mais je le regrette car je n'utilise que des applis Gnome (evince,gnome-terminal et nautilus car je déteste Dolphin ) my 2 cents jerome
Re: portable Lenovo et Debian (was Re: Debian UEFI et multi boot)
Le Wed, 3 Apr 2013 09:53:16 +0200 jerome moliere jerome.moli...@gmail.com a écrit: Salut à tous, j'y vais de ma contribution alors... température à peu près constante 48 degres ventilo inaudible ... je suis sous KDE alors que je ne l'aime pas car les extensions Gnome 3 (joli desktop) font monter la température de + de 10 degres donc je ne l'utilise plus mais je le regrette car je n'utilise que des applis Gnome (evince,gnome-terminal et nautilus car je déteste Dolphin ) my 2 cents jerome Tu utilises quelles extensions ? Au repos sous Gnome 3 avec pas mal d'extensions pour le rendre vivable je suis entre 37 et 43°C en fonction de la température ambiante. Gaëtan -- Lisez la FAQ de la liste avant de poser une question : http://wiki.debian.org/fr/FrenchLists Pour vous DESABONNER, envoyez un message avec comme objet unsubscribe vers debian-user-french-requ...@lists.debian.org En cas de soucis, contactez EN ANGLAIS listmas...@lists.debian.org Archive: http://lists.debian.org/20130403200149.6bda45e35058a2c7f50d8...@neuf.fr
Debian UEFI et multi boot
Bonjour à tous voulant anticiper un peu , je voulais savoir si actuellement une Debian s'installe correctement sur une machine récente avec UEFI (surement secure) j'envisage de remplacer mon Thinkpad X201 par 1 X230 et je pense que cette machine dispose de ces nouveaux BIOS . Est ce qu'une install d'un GRUB là dessus va bien se passer sachant que je garde Windows pour les MAJ de BIOS et qq autres usages rarissimes (en réduisant la taille de la partoche initiale bien sûr) Merci de vos retours jerome J.MOLIERE - Mentor/J
Re: Debian UEFI et multi boot
Bonsoir et merci de la réponse si ce n'est pas abusé puis je te demander de développer un peu ? merci J.MOLIERE - Mentor/J Le 2 avril 2013 19:58, Nicolas Pechon zut...@laposte.net a écrit : citation de=jerome moliere Bonjour à tous voulant anticiper un peu , je voulais savoir si actuellement une Debian s'installe correctement sur une machine récente avec UEFI (surement secure) j'envisage de remplacer mon Thinkpad X201 par 1 X230 et je pense que cette machine dispose de ces nouveaux BIOS . Est ce qu'une install d'un GRUB là dessus va bien se passer sachant que je garde Windows pour les MAJ de BIOS et qq autres usages rarissimes (en réduisant la taille de la partoche initiale bien sûr) oui, Mais il faut un peu de temps pour appréhender comment fonctionne ufi -- http://www.coquille-de-bois.fr/
Re: Debian UEFI et multi boot
Le 02/04/2013 19:13, jerome moliere a écrit : Bonjour à tous voulant anticiper un peu , je voulais savoir si actuellement une Debian s'installe correctement sur une machine récente avec UEFI (surement secure) j'envisage de remplacer mon Thinkpad X201 par 1 X230 et je pense que cette machine dispose de ces nouveaux BIOS . Est ce qu'une install d'un GRUB là dessus va bien se passer sachant que je garde Windows pour les MAJ de BIOS et qq autres usages rarissimes (en réduisant la taille de la partoche initiale bien sûr) Merci de vos retours jerome J.MOLIERE - Mentor/J Je ne sais pas pour le X230, mais pour le T530 ce n'est pas un boot verrouillé (et prétendu sécurisé). Ce n'est pas (encore ?) imposé par MS pour les architectures Intel. Par contre en novembre, avec l'installeur wheezy de l'époque je n'ai pas réussi à faire un double boot en UEFI, mais ça vient peut-être du partitionnement en MS-DOS, certains outils associant obligatoirement (là aussi à l'époque, donc avec pas mal de versions béta qui ont du pas mal évoluer) boot UEFI et partitionnement GPT. -- Lisez la FAQ de la liste avant de poser une question : http://wiki.debian.org/fr/FrenchLists Pour vous DESABONNER, envoyez un message avec comme objet unsubscribe vers debian-user-french-requ...@lists.debian.org En cas de soucis, contactez EN ANGLAIS listmas...@lists.debian.org Archive: http://lists.debian.org/515b270e.9020...@rail.eu.org
Re: Debian UEFI et multi boot
Le mardi 2 avril 2013 19:13:03, jerome moliere a écrit : Bonjour à tous voulant anticiper un peu , je voulais savoir si actuellement une Debian s'installe correctement sur une machine récente avec UEFI (surement secure) Bonjour, J'ai installé wheezy en octobre dernier sur une machine acer avec uefi et windows 7 (donc sans secure boot). Je n'avais pas eu trop de problème si ce n'est que j'avais dû aller chercher une iso non officielle. Je pense que maintenant ce n'est plus nécessaire. J'avais obtenu pas mal d'aide ici et j'avais posté un compte-rendu de mon installation. Voir http://lists.debian.org/debian-user-french/2012/10/msg00109.html (et tout ce qui précède dans le fil). Il y avait quand même un bug qui empêchait windows de démarrer ensuite mais j'avais trouvé (voir lien ci-dessus) comment le réparer. Je ne sais si ce bug est toujours d'actualité. Est-ce que le secure boot peut fonctionner avec debian ? Sais pas, je dirais que non puisqu'on n'a pas la clé. Je me trompe ? De toute façon, pour ce à quoi il sert, autant désactiver le secure boot. Est ce qu'une install d'un GRUB là dessus va bien se passer Oui en installant la bonne version de grub ; grub-uefi ou un truc du style (sûrement précisé dans le lien que je t'ai transmis plus haut). -- Eddy F. -- Lisez la FAQ de la liste avant de poser une question : http://wiki.debian.org/fr/FrenchLists Pour vous DESABONNER, envoyez un message avec comme objet unsubscribe vers debian-user-french-requ...@lists.debian.org En cas de soucis, contactez EN ANGLAIS listmas...@lists.debian.org Archive: http://lists.debian.org/201304022108.33997.edfnet-...@yahoo.fr
Re: Debian UEFI et multi boot
Merci Erwan de cette réponse Je dois donc regarder dans les specs du X230 quel type de boot est fourni par Lenovo et si l''installateur de la Wheezy RC1 gère cela mieux que les beta précédentes ... Encore merci Jerrome J.MOLIERE - Mentor/J Le 2 avril 2013 20:44, Erwan David er...@rail.eu.org a écrit : Le 02/04/2013 19:13, jerome moliere a écrit : Bonjour à tous voulant anticiper un peu , je voulais savoir si actuellement une Debian s'installe correctement sur une machine récente avec UEFI (surement secure) j'envisage de remplacer mon Thinkpad X201 par 1 X230 et je pense que cette machine dispose de ces nouveaux BIOS . Est ce qu'une install d'un GRUB là dessus va bien se passer sachant que je garde Windows pour les MAJ de BIOS et qq autres usages rarissimes (en réduisant la taille de la partoche initiale bien sûr) Merci de vos retours jerome J.MOLIERE - Mentor/J Je ne sais pas pour le X230, mais pour le T530 ce n'est pas un boot verrouillé (et prétendu sécurisé). Ce n'est pas (encore ?) imposé par MS pour les architectures Intel. Par contre en novembre, avec l'installeur wheezy de l'époque je n'ai pas réussi à faire un double boot en UEFI, mais ça vient peut-être du partitionnement en MS-DOS, certains outils associant obligatoirement (là aussi à l'époque, donc avec pas mal de versions béta qui ont du pas mal évoluer) boot UEFI et partitionnement GPT. -- Lisez la FAQ de la liste avant de poser une question : http://wiki.debian.org/fr/**FrenchListshttp://wiki.debian.org/fr/FrenchLists Pour vous DESABONNER, envoyez un message avec comme objet unsubscribe vers debian-user-french-REQUEST@**lists.debian.orgdebian-user-french-requ...@lists.debian.org En cas de soucis, contactez EN ANGLAIS listmas...@lists.debian.org Archive: http://lists.debian.org/**515b270e.9020...@rail.eu.orghttp://lists.debian.org/515b270e.9020...@rail.eu.org
Re: Debian UEFI et multi boot
On 2013-04-02 13:13, jerome moliere wrote: Bonjour à tous voulant anticiper un peu , je voulais savoir si actuellement une Debian s'installe correctement sur une machine récente avec UEFI (surement secure) j'envisage de remplacer mon Thinkpad X201 par 1 X230 et je pense que cette machine dispose de ces nouveaux BIOS . Est ce qu'une install d'un GRUB là dessus va bien se passer sachant que je garde Windows pour les MAJ de BIOS et qq autres usages rarissimes (en réduisant la taille de la partoche initiale bien sûr) J'ai un X230 avec Wheezy depuis 2 mois. J'ai pris un système avec Windows 7 pensant que le BIOS aurait l'option de désativer le secure boot, et c'est le cas. J'ignore pour les systèmes avec Windows 8. Ma compréhension est qu'avec UEFI le démarrage serait plus rapide. Cependant je n'ai pas eu le temps de chercher trop de détails, j'ai simplement désactivé le secure boot et j'ai installé normallement. Tout se passe bien après plusieurs MAJ de BIOS. J'ai aussi modifiée l'image au démarrage :) https://joindiaspora.com/p/2323263 Je serais aussi intéressé de savoir la réponse, je vais probablement réinstaller si ça fonctionne avec UEFI, question d'en apprendre plus. F. -- Fabián Rodríguez http://debian.magicfab.ca signature.asc Description: OpenPGP digital signature
Re: Debian UEFI et multi boot
Le Tue, 2 Apr 2013 19:13:03 +0200 jerome moliere jerome.moli...@gmail.com a écrit: je garde Windows pour les MAJ de BIOS et qq autres usages rarissimes (en réduisant la taille de la partoche initiale bien sûr) Pour les mises à jours de BIOS ça ne sert à rien. Lenevo fournit des iso qui permettent de faire les mises à jours du BIOS via un CD-RW ou une clé USB. C'est comme ça que je fais sur mon T420. Gaëtan -- Lisez la FAQ de la liste avant de poser une question : http://wiki.debian.org/fr/FrenchLists Pour vous DESABONNER, envoyez un message avec comme objet unsubscribe vers debian-user-french-requ...@lists.debian.org En cas de soucis, contactez EN ANGLAIS listmas...@lists.debian.org Archive: http://lists.debian.org/20130402213910.de02d9a26341cb2f4540a...@neuf.fr
Re: Debian UEFI et multi boot
Merci de vos réponses ce thread a été très très instructif pour moi... Jerome
portable Lenovo et Debian (was Re: Debian UEFI et multi boot)
Bonjour, Je rebondis sur le sujet vu que vous semblez être plusieurs à utiliser des portbales Lenovo avec une Debian. J'ai moi-même un T420 que je fais tourner sous un mix de Debian Wheezy/sid/experimental et j'ai du mal à être totalement satisfait. Notamment en ce qui concerne la ventilation. Le ventilo monte rapidement dans les tours dès que la charge cpu monte un peu sans que les températures ne soient pourtant excessives (50°C) et c'est assez désagréable. Un collègue qui a le même T420 que moi mais sous windows 7 me dit au contraire trouver la machine très silencieuse. Constatez-vous la même chose sur vos Lenovo ? Avant j'avais un Dell M1330 et je n'avais ce genre de soucis. Gaëtan -- Lisez la FAQ de la liste avant de poser une question : http://wiki.debian.org/fr/FrenchLists Pour vous DESABONNER, envoyez un message avec comme objet unsubscribe vers debian-user-french-requ...@lists.debian.org En cas de soucis, contactez EN ANGLAIS listmas...@lists.debian.org Archive: http://lists.debian.org/20130402220011.b6e79837137041f58530e...@neuf.fr
Re: portable Lenovo et Debian (was Re: Debian UEFI et multi boot)
Le 02/04/2013 22:00, Gaëtan PERRIER a écrit : Bonjour, Je rebondis sur le sujet vu que vous semblez être plusieurs à utiliser des portbales Lenovo avec une Debian. J'ai moi-même un T420 que je fais tourner sous un mix de Debian Wheezy/sid/experimental et j'ai du mal à être totalement satisfait. Notamment en ce qui concerne la ventilation. Le ventilo monte rapidement dans les tours dès que la charge cpu monte un peu sans que les températures ne soient pourtant excessives (50°C) et c'est assez désagréable. Un collègue qui a le même T420 que moi mais sous windows 7 me dit au contraire trouver la machine très silencieuse. Constatez-vous la même chose sur vos Lenovo ? Avant j'avais un Dell M1330 et je n'avais ce genre de soucis. Gaëtan Mon T530 comme le T510 du boulot (sous fedora) sont tous les 2 silencieux. -- Lisez la FAQ de la liste avant de poser une question : http://wiki.debian.org/fr/FrenchLists Pour vous DESABONNER, envoyez un message avec comme objet unsubscribe vers debian-user-french-requ...@lists.debian.org En cas de soucis, contactez EN ANGLAIS listmas...@lists.debian.org Archive: http://lists.debian.org/515b39bf.9070...@rail.eu.org
Re: portable Lenovo et Debian (was Re: Debian UEFI et multi boot)
Le Tue, 02 Apr 2013 22:04:15 +0200 Erwan David er...@rail.eu.org a écrit: Le 02/04/2013 22:00, Gaëtan PERRIER a écrit : Bonjour, Je rebondis sur le sujet vu que vous semblez être plusieurs à utiliser des portbales Lenovo avec une Debian. J'ai moi-même un T420 que je fais tourner sous un mix de Debian Wheezy/sid/experimental et j'ai du mal à être totalement satisfait. Notamment en ce qui concerne la ventilation. Le ventilo monte rapidement dans les tours dès que la charge cpu monte un peu sans que les températures ne soient pourtant excessives (50°C) et c'est assez désagréable. Un collègue qui a le même T420 que moi mais sous windows 7 me dit au contraire trouver la machine très silencieuse. Constatez-vous la même chose sur vos Lenovo ? Avant j'avais un Dell M1330 et je n'avais ce genre de soucis. Gaëtan Mon T530 comme le T510 du boulot (sous fedora) sont tous les 2 silencieux. Au niveau installation tu utilises des trucs genre thinkfan, laptop-mode-tools, tp-smapi, etc. ? Gaëtan -- Lisez la FAQ de la liste avant de poser une question : http://wiki.debian.org/fr/FrenchLists Pour vous DESABONNER, envoyez un message avec comme objet unsubscribe vers debian-user-french-requ...@lists.debian.org En cas de soucis, contactez EN ANGLAIS listmas...@lists.debian.org Archive: http://lists.debian.org/20130402221911.7d32dc9d3fa5d1113075e...@neuf.fr
Re: portable Lenovo et Debian (was Re: Debian UEFI et multi boot)
Le 02/04/2013 22:19, Gaëtan PERRIER a écrit : Le Tue, 02 Apr 2013 22:04:15 +0200 Erwan David er...@rail.eu.org a écrit: Le 02/04/2013 22:00, Gaëtan PERRIER a écrit : Bonjour, Je rebondis sur le sujet vu que vous semblez être plusieurs à utiliser des portbales Lenovo avec une Debian. J'ai moi-même un T420 que je fais tourner sous un mix de Debian Wheezy/sid/experimental et j'ai du mal à être totalement satisfait. Notamment en ce qui concerne la ventilation. Le ventilo monte rapidement dans les tours dès que la charge cpu monte un peu sans que les températures ne soient pourtant excessives (50°C) et c'est assez désagréable. Un collègue qui a le même T420 que moi mais sous windows 7 me dit au contraire trouver la machine très silencieuse. Constatez-vous la même chose sur vos Lenovo ? Avant j'avais un Dell M1330 et je n'avais ce genre de soucis. Gaëtan Mon T530 comme le T510 du boulot (sous fedora) sont tous les 2 silencieux. Au niveau installation tu utilises des trucs genre thinkfan, laptop-mode-tools, tp-smapi, etc. ? Gaëtan Non, je ne crois pas. Le seul paquet spécifique que j'aie c'est tpb -- Lisez la FAQ de la liste avant de poser une question : http://wiki.debian.org/fr/FrenchLists Pour vous DESABONNER, envoyez un message avec comme objet unsubscribe vers debian-user-french-requ...@lists.debian.org En cas de soucis, contactez EN ANGLAIS listmas...@lists.debian.org Archive: http://lists.debian.org/515b3d4a.1050...@rail.eu.org
Re: portable Lenovo et Debian (was Re: Debian UEFI et multi boot)
Le Tue, 02 Apr 2013 22:19:22 +0200 Erwan David er...@rail.eu.org a écrit: Le 02/04/2013 22:19, Gaëtan PERRIER a écrit : Le Tue, 02 Apr 2013 22:04:15 +0200 Erwan David er...@rail.eu.org a écrit: Le 02/04/2013 22:00, Gaëtan PERRIER a écrit : Bonjour, Je rebondis sur le sujet vu que vous semblez être plusieurs à utiliser des portbales Lenovo avec une Debian. J'ai moi-même un T420 que je fais tourner sous un mix de Debian Wheezy/sid/experimental et j'ai du mal à être totalement satisfait. Notamment en ce qui concerne la ventilation. Le ventilo monte rapidement dans les tours dès que la charge cpu monte un peu sans que les températures ne soient pourtant excessives (50°C) et c'est assez désagréable. Un collègue qui a le même T420 que moi mais sous windows 7 me dit au contraire trouver la machine très silencieuse. Constatez-vous la même chose sur vos Lenovo ? Avant j'avais un Dell M1330 et je n'avais ce genre de soucis. Gaëtan Mon T530 comme le T510 du boulot (sous fedora) sont tous les 2 silencieux. Au niveau installation tu utilises des trucs genre thinkfan, laptop-mode-tools, tp-smapi, etc. ? Gaëtan Non, je ne crois pas. Le seul paquet spécifique que j'aie c'est tpb Il sert vraiment à quelque chose tpb ? Gnome affiche déjà tout ça à l'écran donc à quoi ça sert ? Gaëtan -- Lisez la FAQ de la liste avant de poser une question : http://wiki.debian.org/fr/FrenchLists Pour vous DESABONNER, envoyez un message avec comme objet unsubscribe vers debian-user-french-requ...@lists.debian.org En cas de soucis, contactez EN ANGLAIS listmas...@lists.debian.org Archive: http://lists.debian.org/2013040713.e3923d99611cc89ff6ca5...@neuf.fr
Re: portable Lenovo et Debian (was Re: Debian UEFI et multi boot)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2013-04-02 16:00, Gaëtan PERRIER wrote: J'ai moi-même un T420 que je fais tourner sous un mix de Debian Wheezy/sid/experimental et j'ai du mal à être totalement satisfait. Notamment en ce qui concerne la ventilation. Le ventilo monte rapidement dans les tours dès que la charge cpu monte un peu sans que les températures ne soient pourtant excessives (50°C) et c'est assez désagréable. Un collègue qui a le même T420 que moi mais sous windows 7 me dit au contraire trouver la machine très silencieuse. Constatez-vous la même chose sur vos Lenovo ? Non, quoiqu'il est possible que ce soit le ventilateur qui est plus silencieux sur un X230. J'ai utilisé ces optimisations pour la batterie: https://trisquel.info/en/wiki/optimizing-battery-time J'aussi installé lm-sensors et éxécuté sensors-detect, puis j'utilise l'extension Sensors pour Gnome3 pour garder un œil sur le tout: https://extensions.gnome.org/extension/82/cpu-temperature-indicator/ Sur une journée, la moyenne est environ de 48°C (donc aussi 50°C). F. - -- Fabián Rodríguez http://debian.magicfab.ca -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: PGP/Mime available upon request Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlFbQaEACgkQfUcTXFrypNWuIQCgmOUyR11ceea86l2JSrGixTzp /coAnRnT65vSuv8FGXaqKX/6vXnZ2wSX =qiWH -END PGP SIGNATURE- -- Lisez la FAQ de la liste avant de poser une question : http://wiki.debian.org/fr/FrenchLists Pour vous DESABONNER, envoyez un message avec comme objet unsubscribe vers debian-user-french-requ...@lists.debian.org En cas de soucis, contactez EN ANGLAIS listmas...@lists.debian.org Archive: http://lists.debian.org/515b41a1.2030...@member.fsf.org
Re: Debian UEFI et multi boot
Bonjour, Le mardi 02 avril 2013, jerome moliere a écrit... voulant anticiper un peu , je voulais savoir si actuellement une Debian s'installe correctement sur une machine récente avec UEFI (surement secure) j'envisage de remplacer mon Thinkpad X201 par 1 X230 et je pense que cette machine dispose de ces nouveaux BIOS . Est ce qu'une install d'un GRUB là dessus va bien se passer sachant que je garde Windows pour les MAJ de BIOS et qq autres usages rarissimes (en réduisant la taille de la partoche initiale bien sûr) Merci de vos retours http://tanguy.ortolo.eu/blog/article51/debian-efi Merci à Tanguy Ortolo pour sa page bien utile ! J'ai suivi cette doc pour booter mon fameux HP 4540S. Bon, la suppression de bootx64.efi ne fonctionne pas, mais le portable boote bien avec. J'ai désactivé le Secure Boot. Avant de booter en UEFI, j'utilisais le mode Ancien (traduction du BIOS), ce qui me permettait de booter sur une clé USB avec SystemRescueCd et de lancer l'OS via SRCd. Personnellement, je trouvais ça pas mal, comme méthode sécurisée de boot, mais ma fille préférait le boot classique. L'avantage du boot en mode non-uefi, c'est qu'on peut booter également sur l'usb ou le cdrom sans avoir à modifier le bios. On peut considérer ça comme un désavantage, d'ailleurs. -- jm -- Lisez la FAQ de la liste avant de poser une question : http://wiki.debian.org/fr/FrenchLists Pour vous DESABONNER, envoyez un message avec comme objet unsubscribe vers debian-user-french-requ...@lists.debian.org En cas de soucis, contactez EN ANGLAIS listmas...@lists.debian.org Archive: http://lists.debian.org/20130402204952.GD19904@espinasse
Re: portable Lenovo et Debian (was Re: Debian UEFI et multi boot)
Le Tue, 02 Apr 2013 16:37:53 -0400 Fabian Rodriguez magic...@member.fsf.org a écrit: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2013-04-02 16:00, Gaëtan PERRIER wrote: J'ai moi-même un T420 que je fais tourner sous un mix de Debian Wheezy/sid/experimental et j'ai du mal à être totalement satisfait. Notamment en ce qui concerne la ventilation. Le ventilo monte rapidement dans les tours dès que la charge cpu monte un peu sans que les températures ne soient pourtant excessives (50°C) et c'est assez désagréable. Un collègue qui a le même T420 que moi mais sous windows 7 me dit au contraire trouver la machine très silencieuse. Constatez-vous la même chose sur vos Lenovo ? Non, quoiqu'il est possible que ce soit le ventilateur qui est plus silencieux sur un X230. J'ai utilisé ces optimisations pour la batterie: https://trisquel.info/en/wiki/optimizing-battery-time Globalement ça correspond à ce que j'ai. Par contre en regardant la partie blacklist je m'aperçois que parport est chargé alors que la machine n'a pas de port parallèle. Comment ça se fait ? J'aussi installé lm-sensors et éxécuté sensors-detect, puis j'utilise l'extension Sensors pour Gnome3 pour garder un œil sur le tout: https://extensions.gnome.org/extension/82/cpu-temperature-indicator/ Oui je l'ai aussi. ;) Sur une journée, la moyenne est environ de 48°C (donc aussi 50°C). F. Et tu n'entends pas le ventilo ? Gaëtan -- Lisez la FAQ de la liste avant de poser une question : http://wiki.debian.org/fr/FrenchLists Pour vous DESABONNER, envoyez un message avec comme objet unsubscribe vers debian-user-french-requ...@lists.debian.org En cas de soucis, contactez EN ANGLAIS listmas...@lists.debian.org Archive: http://lists.debian.org/20130402230522.32eecbd9b3028e8557a7c...@neuf.fr
Re: portable Lenovo et Debian (was Re: Debian UEFI et multi boot)
Le mardi 2 avril 2013 à 23:05:22, Gaëtan PERRIER a écrit : […] Par contre en regardant la partie blacklist je m'aperçois que parport est chargé alors que la machine n'a pas de port parallèle. Comment ça se fait ? Cups force le chargement du module… -- Sylvain Sauvage -- Lisez la FAQ de la liste avant de poser une question : http://wiki.debian.org/fr/FrenchLists Pour vous DESABONNER, envoyez un message avec comme objet unsubscribe vers debian-user-french-requ...@lists.debian.org En cas de soucis, contactez EN ANGLAIS listmas...@lists.debian.org Archive: http://lists.debian.org/201304030010.18424.sylvain.l.sauv...@free.fr
Re: Debian UEFI et multi boot
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2013-04-02 16:49, Jean-Michel OLTRA wrote: Bonjour, Le mardi 02 avril 2013, jerome moliere a écrit... voulant anticiper un peu , je voulais savoir si actuellement une Debian s'installe correctement sur une machine récente avec UEFI (surement secure) j'envisage de remplacer mon Thinkpad X201 par 1 X230 et je pense que cette machine dispose de ces nouveaux BIOS . Est ce qu'une install d'un GRUB là dessus va bien se passer sachant que je garde Windows pour les MAJ de BIOS et qq autres usages rarissimes (en réduisant la taille de la partoche initiale bien sûr) J'ai perdu le message original de ce fil mais je voulais ajouter ceci: http://cdimage.debian.org/cdimage/unofficial/efi-development/upload5/ (je n'ai pas testé) A+ F. - -- Fabián Rodríguez http://debian.magicfab.ca -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: PGP/Mime available upon request Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlFbV8wACgkQfUcTXFrypNUFigCfe9HnGDG1cDVdd9dh6oblMnle m1gAoJYZdkt5ELnRusw8+mzKw2pyY6Qd =JhXh -END PGP SIGNATURE- -- Lisez la FAQ de la liste avant de poser une question : http://wiki.debian.org/fr/FrenchLists Pour vous DESABONNER, envoyez un message avec comme objet unsubscribe vers debian-user-french-requ...@lists.debian.org En cas de soucis, contactez EN ANGLAIS listmas...@lists.debian.org Archive: http://lists.debian.org/515b57cc.6000...@member.fsf.org
Re: portable Lenovo et Debian (was Re: Debian UEFI et multi boot)
Le Tue, 02 Apr 2013 22:28:33 +0200 Erwan David er...@rail.eu.org a écrit: Le 02/04/2013 22:27, Gaëtan PERRIER a écrit : Le Tue, 02 Apr 2013 22:19:22 +0200 Erwan David er...@rail.eu.org a écrit: Le 02/04/2013 22:19, Gaëtan PERRIER a écrit : Le Tue, 02 Apr 2013 22:04:15 +0200 Erwan David er...@rail.eu.org a écrit: Le 02/04/2013 22:00, Gaëtan PERRIER a écrit : Bonjour, Je rebondis sur le sujet vu que vous semblez être plusieurs à utiliser des portbales Lenovo avec une Debian. J'ai moi-même un T420 que je fais tourner sous un mix de Debian Wheezy/sid/experimental et j'ai du mal à être totalement satisfait. Notamment en ce qui concerne la ventilation. Le ventilo monte rapidement dans les tours dès que la charge cpu monte un peu sans que les températures ne soient pourtant excessives (50°C) et c'est assez désagréable. Un collègue qui a le même T420 que moi mais sous windows 7 me dit au contraire trouver la machine très silencieuse. Constatez-vous la même chose sur vos Lenovo ? Avant j'avais un Dell M1330 et je n'avais ce genre de soucis. Gaëtan Mon T530 comme le T510 du boulot (sous fedora) sont tous les 2 silencieux. Au niveau installation tu utilises des trucs genre thinkfan, laptop-mode-tools, tp-smapi, etc. ? Gaëtan Non, je ne crois pas. Le seul paquet spécifique que j'aie c'est tpb Il sert vraiment à quelque chose tpb ? Gnome affiche déjà tout ça à l'écran donc à quoi ça sert ? Gaëtan Déjà je suis sous KDE, et après je pense que c'est ce qui me permet de régler le volume avec la touche voulme du clavier par exemple (plus les touches Fn) Ah ok. Parce que moi toutes les touches spéciales (mute, vol+/-, Fn divers) fonctionnent directement. La seule qui résiste c'est mute rec. Est-ce qu'elle fonctionne chez toi ? Gaëtan -- Lisez la FAQ de la liste avant de poser une question : http://wiki.debian.org/fr/FrenchLists Pour vous DESABONNER, envoyez un message avec comme objet unsubscribe vers debian-user-french-requ...@lists.debian.org En cas de soucis, contactez EN ANGLAIS listmas...@lists.debian.org Archive: http://lists.debian.org/20130403032009.dc7df76d7755ef317076a...@neuf.fr
Re: portable Lenovo et Debian (was Re: Debian UEFI et multi boot)
Le Tue, 2 Apr 2013 22:00:11 +0200 Gaëtan PERRIER gaetan.perr...@neuf.fr a écrit: Bonjour, Je rebondis sur le sujet vu que vous semblez être plusieurs à utiliser des portbales Lenovo avec une Debian. J'ai moi-même un T420 que je fais tourner sous un mix de Debian Wheezy/sid/experimental et j'ai du mal à être totalement satisfait. Notamment en ce qui concerne la ventilation. Le ventilo monte rapidement dans les tours dès que la charge cpu monte un peu sans que les températures ne soient pourtant excessives (50°C) et c'est assez désagréable. Un collègue qui a le même T420 que moi mais sous windows 7 me dit au contraire trouver la machine très silencieuse. Constatez-vous la même chose sur vos Lenovo ? Avant j'avais un Dell M1330 et je n'avais ce genre de soucis. Je viens de constater aussi que tant que la batterie est en charge il met le ventilo à mi-régime. Dès qu'il arrive en fin charge le ventilo se coupe ... Gaëtan -- Lisez la FAQ de la liste avant de poser une question : http://wiki.debian.org/fr/FrenchLists Pour vous DESABONNER, envoyez un message avec comme objet unsubscribe vers debian-user-french-requ...@lists.debian.org En cas de soucis, contactez EN ANGLAIS listmas...@lists.debian.org Archive: http://lists.debian.org/20130403032539.efcae428fa7d116171d29...@neuf.fr
Re: Debian UEFI et multi boot
citation de=jerome moliere Bonsoir et merci de la réponse si ce n'est pas abusé puis je te demander de développer un peu ? merci J.MOLIERE - Mentor/J Pour ma part, j'ai eu quelque soucis. sur un portable avec windows 8. J'ai installé une wheezy A l'aide du CD d'install, Il a fallu que je me chroot. Puis, j'ai démonté toutes les partitions (sauf la racine), ensuite je les ai remonté, sans oublier /boot/efi. En effet, mount indiquai que les partitions étais monté ce qui était faux. Toujours chrooté, j'ai alors pu installer grub. Jusque la, l'installateur refusai d'installer grub. -- Tu sais pourquoi le chat te regarde? Bin!!! Parceque j'suis belle!!! -+- Gwenaelle 3ans -+- -- Lisez la FAQ de la liste avant de poser une question : http://wiki.debian.org/fr/FrenchLists Pour vous DESABONNER, envoyez un message avec comme objet unsubscribe vers debian-user-french-requ...@lists.debian.org En cas de soucis, contactez EN ANGLAIS listmas...@lists.debian.org Archive: http://lists.debian.org/a05c4b4ce73d29f499418d09383f06c4.squirrel@bureau
Re: GRUB setup for multi-boot ISO from memory stick
Hi Intense Red,
On Tue 04 Dec 2012 at 15:42:52 -0500, Intense Red wrote:
Thanks for your reply. It was thorough, complete, and all of the steps you
listed out were perfectly logical and made sense.
The only problem is that it doesn't seem to work. :-) I can't even get to
the first step of mounting the memory card.
You are going to keep the error message to yourself? :)
All I can think of you specified the wrong device or the filesystem on
it is not vfat.
Are you sure you want to do this? It is easier to get the installer
installing without using GRUB's loopback facility.
Okay, I'm game. What is an easier method of booting Debian from a memory
card to install it into a machine without a CD-ROM? TIA
Bob has pointed you at the definitive one. It should suit 99.99% of
users, unless there is a specialised need for something else. Using a
multi-boot USB stick would count as specialised. I'll give you what *I*
have.
1. Download vmlinuz and initrd.gz from somewhere.
http.us.debian.org/debian/dists/wheezy/main/installer-i386/current/images/hd-media/
would do.
2. Put these two files in the isos directory together with a suitable
ISO image such as
debian-wheezy-DI-b4-i386-netinst.iso
3. In grub.cfg:
menuentry debian-beta4 {
set root=(hd0,msdos1)
linux /isos/vmlinuz priority=low
initrd /isos/initrd.gz
}
Note that the booted vmlinuz will identify the USB stick as /dev/sda.
This is (hd0,msdos1) in grubspeak.
4. Boot. Scan hard drives (Yes, I know!). Select what partition or device
to search.
Are you sure you want to do this? Writing an isohybrid to a USB stck is
quick, elegant and reliable. And less work.
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20121205125814.GN6940@desktop
Re: GRUB setup for multi-boot ISO from memory stick
Hi Brian, Thanks for your reply. It was thorough, complete, and all of the steps you listed out were perfectly logical and made sense. The only problem is that it doesn't seem to work. :-) I can't even get to the first step of mounting the memory card. Are you sure you want to do this? It is easier to get the installer installing without using GRUB's loopback facility. Okay, I'm game. What is an easier method of booting Debian from a memory card to install it into a machine without a CD-ROM? TIA. -- I remember when I was a boy and I heard repeated time and time again the phrase, 'My country, right or wrong, my country!' How absolutely absurd is such an idea. How absolutely absurd to teach this idea to the youth of the country. -- Mark Twain, 1907. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201212041542.53038.intns...@golgotha.net
Re: GRUB setup for multi-boot ISO from memory stick
Intense Red wrote: Brian wrote: Are you sure you want to do this? It is easier to get the installer installing without using GRUB's loopback facility. Okay, I'm game. What is an easier method of booting Debian from a memory card to install it into a machine without a CD-ROM? TIA. If I understand you correctly then it is easy. The installer images can be copied directly to a USB storage device image. You can boot off of that USB device and then you are ready to go. Here is some documentation on it: http://www.debian.org/releases/stable/i386/ch04s03.html.en#usb-copy-isohybrid Bob signature.asc Description: Digital signature
Re: GRUB setup for multi-boot ISO from memory stick
On Sat 01 Dec 2012 at 22:53:27 -0500, Intense Red wrote:
I've been trying to set up Testing/Wheezy's DVD ISO to boot from a memory
card/USB thumb drive, as outlined at http://www.pendrivelinux.com/boot-
multiple-iso-from-usb-via-grub2-using-linux/
You'll have a FAT16/32 filesystem on the drive, then. That's of some
importance; it will save you some work. I use FAT16 and keep the ISOs in
/boot/isos.
I have the *.iso file renamed debian.iso and put in the root directory
of
the USB drive/memory card. GRUB is installed on the card just fine and it
boots
and acts like it should.
My problem is configuring GRUB to boot the Debian ISO file. My GRUB
menu.cfg
entry is:
menuentry Debian ISO {
loopback loop /debian.iso
linux (loop)/install.386/vmlinuz boot=install.386 iso-
scan/filename=/debian.iso noeject noprompt splash --
initrd (loop)/install.386/initrd.gz
}
This works for me:
menuentry debian-wheezy-beta4 {
loopback loop0 /boot/isos/debian-wheezy-DI-b4-i386-netinst.iso
linux (loop0)/install.386/vmlinuz priority=low
initrd (loop0)/install.386/initrd.gz
}
I'm fairly sure boot= and iso-scan/filename= are not needed. In fact, I
have doubts whether iso-scan/filename is even used by any Debian images.
This boots the ISO file and starts the Debian installation. The
installation
goes along just fine until the install program asks me where the CD-ROM is.
The
computer doesn't have CD-ROM and I want the installer to read the debian.iso
file as the first (and only) CD-ROM. But I can't seem to see the *.iso
file
from the booted kernel even though the kernel is booted from the debian.iso
file.
Does anyone know how to properly configure the grub.cfg entry so that it
will both boot from the *.iso file and so I can tell the installer to use the
same *.iso file as the CD-ROM?
Your GRUB stanza is basically ok. You used loopback to get the installer
going. Now it is looking around for an ISO to mount, also in loopback
mode. One problem is that kernel provides only one loop device at this
stage - /dev/loop0, and GRUB has got its hands on it. You will have to
come to the rescue and help D-I out by detecting and mounting the ISO
for it.
You need a kernel loop module which matches the running kernel. For the
Wheezy beta-4 it can be found in
loop-modules-3.2.0-4-486-di_3.2.32-1_i386.udeb
Extract loop.ko and put it on your memory card/USB thumb drive. Boot and
do the detecting of the CD-ROM. Ok, we know this will not work but it
gets the directory /cdrom created. We may as well make the installer
work for its living.
Now get a console with ALT F2 and do
mount -tvfat /dev/sdX(n) /mnt
/dev/sdX(n) is the device you booted from. 'ls -l /dev/sd*' might help
you to identify it. Now
cp /mnt/loop.ko /lib/modules/3.2.0-4-486/kernel/drivers/block/
and do
depmod
followed by
modprobe loop
if the last command didn't get any complaints you are on your way to a
successful install.
Almost finally:
mount -o loop /mnt/debian-wheezy-DI-b4-i386-netinst.iso /cdrom
Finally: load the installer components.
Are you sure you want to do this? It is easier to get the installer
installing without using GRUB's loopback facility.
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20121203000945.GK6940@desktop
GRUB setup for multi-boot ISO from memory stick
I've been trying to set up Testing/Wheezy's DVD ISO to boot from a memory
card/USB thumb drive, as outlined at http://www.pendrivelinux.com/boot-
multiple-iso-from-usb-via-grub2-using-linux/
I have the *.iso file renamed debian.iso and put in the root directory of
the USB drive/memory card. GRUB is installed on the card just fine and it boots
and acts like it should.
My problem is configuring GRUB to boot the Debian ISO file. My GRUB menu.cfg
entry is:
menuentry Debian ISO {
loopback loop /debian.iso
linux (loop)/install.386/vmlinuz boot=install.386 iso-
scan/filename=/debian.iso noeject noprompt splash --
initrd (loop)/install.386/initrd.gz
}
This boots the ISO file and starts the Debian installation. The installation
goes along just fine until the install program asks me where the CD-ROM is. The
computer doesn't have CD-ROM and I want the installer to read the debian.iso
file as the first (and only) CD-ROM. But I can't seem to see the *.iso file
from the booted kernel even though the kernel is booted from the debian.iso
file.
Does anyone know how to properly configure the grub.cfg entry so that it
will both boot from the *.iso file and so I can tell the installer to use the
same *.iso file as the CD-ROM?
--
Light travels faster than sound. This is why some people appear bright until
you hear them speak.
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201212012253.28413.intns...@golgotha.net
Re: multi-boot+grub2+separate boot partition
On Sat 10 Nov 2012 at 06:34:27 +, Russell L. Harris wrote: I wish to use grub2 to multi-boot the following systems: = Debian stable (Squeeze) on /dev/sda6 = Debian testing (Wheezy) on /dev/sda7 = Ubuntu (10.x) on /dev/sda8 This is a work machine and my primary interest is stable. But I need to become familiar with Wheezy, which is about to become stable. I am installing Ubuntu as a safety net, because Ubuntu developers seem to find a way to get all of the peripheral devices working, even if it the resulting configuration is non-standard. I have read the Debian installation manual and I have searched with Google, but thus far I have not found a HOWTO for such an arrangement using a separate boot partition. I cannot think of a reason for having such a separate partition. I plan to update testing from time to time. Once Wheezy becomes stable, I plan to drop Squeeze and install the new testing. I may even update Ubuntu. It seemed to me that the proper approach would be to use a separate boot partition on /dev/sda1, and to make it policy always to run update-grub from stable. I instructed the Squeeze installer to install grub2 to /dev/sda1. I instructed the Wheezy installer to install grub2 to /dev/sda7. I instructed the Ubuntu installer to install grub2 to /dev/sda8. I'd have installed GRUB to /dev/sda each time. Then, if Squeeze was not the last installation done and I wanted it to head the GRUB menu, I'd have booted into it and run grub-install /dev/sda -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20121110131437.GC6794@desktop
Re: multi-boot+grub2+separate boot partition
* Brian a...@cityscape.co.uk [121110 13:18]: On Sat 10 Nov 2012 at 06:34:27 +, Russell L. Harris wrote: ... I instructed the Squeeze installer to install grub2 to /dev/sda1. I instructed the Wheezy installer to install grub2 to /dev/sda7. I instructed the Ubuntu installer to install grub2 to /dev/sda8. ... I'd have installed GRUB to /dev/sda each time. Then, if Squeeze was not the last installation done and I wanted it to head the GRUB menu, I'd have booted into it and run grub-install /dev/sda Thanks, Brian. If my understanding of grub is correct, the execution of grub-install /dev/sda: (1) writes the various grub files to the /boot/grub directory of the partition corresponding to the operating system which executes grub-install, then (2) writes a short instruction phrase to the master boot record (MBR) of /dev/sda, which phrase terminates in a link to the grub code in the /boot/grub directory of the partition corresponding to the operating system which last invoked install-grub. RLH -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20121110152033.gb2...@gospelbroadcasting.org
Re: multi-boot+grub2+separate boot partition
On Sat 10 Nov 2012 at 15:20:33 +, Russell L. Harris wrote: If my understanding of grub is correct, the execution of grub-install /dev/sda: (1) writes the various grub files to the /boot/grub directory of the partition corresponding to the operating system which executes grub-install, then (2) writes a short instruction phrase to the master boot record (MBR) of /dev/sda, which phrase terminates in a link to the grub code in the /boot/grub directory of the partition corresponding to the operating system which last invoked install-grub. Yes to both. Tom H wrote a nice short account of this a couple of days ago. Here's the thread: http://lists.debian.org/debian-user/2012/11/msg00280.html -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20121110153854.GM6794@desktop
multi-boot+grub2+separate boot partition
I wish to use grub2 to multi-boot the following systems: = Debian stable (Squeeze) on /dev/sda6 = Debian testing (Wheezy) on /dev/sda7 = Ubuntu (10.x) on /dev/sda8 This is a work machine and my primary interest is stable. But I need to become familiar with Wheezy, which is about to become stable. I am installing Ubuntu as a safety net, because Ubuntu developers seem to find a way to get all of the peripheral devices working, even if it the resulting configuration is non-standard. I have read the Debian installation manual and I have searched with Google, but thus far I have not found a HOWTO for such an arrangement using a separate boot partition. I plan to update testing from time to time. Once Wheezy becomes stable, I plan to drop Squeeze and install the new testing. I may even update Ubuntu. It seemed to me that the proper approach would be to use a separate boot partition on /dev/sda1, and to make it policy always to run update-grub from stable. I instructed the Squeeze installer to install grub2 to /dev/sda1. I instructed the Wheezy installer to install grub2 to /dev/sda7. I instructed the Ubuntu installer to install grub2 to /dev/sda8. I booted into Squeeze and executed update-grub. The messages were: = found linux-image /boot/vmlnuz-2.6.32-5-686 (this is Squeeze) = found linux-image /boot/initrd-2.6.32-5-686 (this is Squeeze) = found Debian GNU/Linux (Wheezy/Sid) on /dev/sda7 = Ubuntu 10.10 on /dev/sda8 But upon rebooting, the grub menu contains only entries for Squeeze and Ubuntu. Is it reasonable to use a separate boot partition? Can this scheme be made to work? RLH -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20121110063427.ga2...@gospelbroadcasting.org
Re: multi-boot cfdisk warning: is it broke? How do I fix?
Charles Blair c-bl...@illinois.edu writes: FATAL ERROR: Bad primary partition 2: Partition ends in the final partial cylinder fdisk -l /dev/sda gives: Disk /dev/sda: 320.1 GB, 320072933376 bytes 255 heads, 63 sectors/track, 38913 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0xbb0c5abb Device Boot Start End Blocks Id System /dev/sda1 1 192 1536000 27 Unknown /dev/sda2 192 12349976562507 HPFS/NTFS /dev/sda3 37264 3891413248512 17 Hidden HPFS/NTFS /dev/sda4 12350 37264 2001285135 Extended /dev/sda5 * 12350 12392 340992 83 Linux /dev/sda6 12392 13486 8787968 83 Linux /dev/sda7 13486 13851 2928640 83 Linux /dev/sda8 13851 14826 7827456 82 Linux swap / Solaris /dev/sda9 14826 14874 389120 83 Linux /dev/sda10 14874 37264 179849216 83 Linux Partition table entries are not in disk order When the partitions are not listed in disk order, how does one know which of them is the bad one? BTW, try fdisk -luc instead of fdisk -l. There's also other fdisk programs like parted and cfdisk, perhaps they can give more detailed information. If you plan to re-partition sda1--3 and to leave the rest untouched and if the bad partition is one of sda1--3, you should be able to get away without damaging the other partitions. In any case, make backups before you do anything. -- html messages are obsolete -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87r55k41g0@yun.yagibdah.de
multi-boot warning from cfdisk: if it ain't broke...
-- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110720111854.132ea...@charlie.hsd1.il.comcast.net.
multi-boot cfdisk warning: is it broke? How do I fix?
I tried to set up a dual boot of windows and linux from
the installer. The linux part works, but windows 7 starts to boot
and then takes me back to grub.
I am sufficiently happy with linux that I was planning to get
rid of windows. I would like to use the space to give openBSD a
try.
As a first step, I tried using cfdisk -Ps /dev/sda, and got the
ominous warning:
FATAL ERROR: Bad primary partition 2: Partition ends in the final partial
cylinder
Since linux is working, I'm worried that trying to fix whatever this
problem is might wreck my system.
fdisk -l /dev/sda gives:
Disk /dev/sda: 320.1 GB, 320072933376 bytes
255 heads, 63 sectors/track, 38913 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0xbb0c5abb
Device Boot Start End Blocks Id System
/dev/sda1 1 192 1536000 27 Unknown
/dev/sda2 192 12349976562507 HPFS/NTFS
/dev/sda3 37264 3891413248512 17 Hidden HPFS/NTFS
/dev/sda4 12350 37264 2001285135 Extended
/dev/sda5 * 12350 12392 340992 83 Linux
/dev/sda6 12392 13486 8787968 83 Linux
/dev/sda7 13486 13851 2928640 83 Linux
/dev/sda8 13851 14826 7827456 82 Linux swap / Solaris
/dev/sda9 14826 14874 389120 83 Linux
/dev/sda10 14874 37264 179849216 83 Linux
Partition table entries are not in disk order
** copy of my grub.cfg file ***
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#
### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
load_env
fi
set default=0
if [ ${prev_saved_entry} ]; then
set saved_entry=${prev_saved_entry}
save_env saved_entry
set prev_saved_entry=
save_env prev_saved_entry
set boot_once=true
fi
function savedefault {
if [ -z ${boot_once} ]; then
saved_entry=${chosen}
save_env saved_entry
fi
}
function load_video {
insmod vbe
insmod vga
insmod video_bochs
insmod video_cirrus
}
insmod part_msdos
insmod ext2
set root='(hd0,msdos6)'
search --no-floppy --fs-uuid --set a5ae78d6-949a-4462-bc98-6c53a846c401
if loadfont /share/grub/unicode.pf2 ; then
set gfxmode=640x480
load_video
insmod gfxterm
fi
terminal_output gfxterm
insmod part_msdos
insmod ext2
set root='(hd0,msdos5)'
search --no-floppy --fs-uuid --set d487742e-ad50-4347-8d9a-b8d0f1908c13
set locale_dir=($root)/boot/grub/locale
set lang=en
insmod gettext
set timeout=5
### END /etc/grub.d/00_header ###
### BEGIN /etc/grub.d/05_debian_theme ###
insmod part_msdos
insmod ext2
set root='(hd0,msdos6)'
search --no-floppy --fs-uuid --set a5ae78d6-949a-4462-bc98-6c53a846c401
insmod png
if background_image /share/images/desktop-base/spacefun-grub.png; then
set color_normal=light-gray/black
set color_highlight=white/black
else
set menu_color_normal=cyan/blue
set menu_color_highlight=white/blue
fi
### END /etc/grub.d/05_debian_theme ###
### BEGIN /etc/grub.d/10_linux ###
menuentry 'Debian GNU/Linux, with Linux 2.6.32-5-amd64' --class debian --class
gnu-linux --class gnu --class os {
insmod part_msdos
insmod ext2
set root='(hd0,msdos5)'
search --no-floppy --fs-uuid --set d487742e-ad50-4347-8d9a-b8d0f1908c13
echo'Loading Linux 2.6.32-5-amd64 ...'
linux /boot/vmlinuz-2.6.32-5-amd64
root=UUID=d487742e-ad50-4347-8d9a-b8d0f1908c13 ro quiet
echo'Loading initial ramdisk ...'
initrd /boot/initrd.img-2.6.32-5-amd64
}
menuentry 'Debian GNU/Linux, with Linux 2.6.32-5-amd64 (recovery mode)' --class
debian --class gnu-linux --class gnu --class os {
insmod part_msdos
insmod ext2
set root='(hd0,msdos5)'
search --no-floppy --fs-uuid --set d487742e-ad50-4347-8d9a-b8d0f1908c13
echo'Loading Linux 2.6.32-5-amd64 ...'
linux /boot/vmlinuz-2.6.32-5-amd64
root=UUID=d487742e-ad50-4347-8d9a-b8d0f1908c13 ro single
echo'Loading initial ramdisk ...'
initrd /boot/initrd.img-2.6.32-5-amd64
}
### END /etc/grub.d/10_linux ###
### BEGIN /etc/grub.d/20_linux_xen ###
### END /etc/grub.d/20_linux_xen ###
### BEGIN /etc/grub.d/30_os-prober ###
menuentry Windows 7 (loader) (on /dev/sda1) {
insmod part_msdos
insmod ntfs
set root='(hd0,msdos1)'
search --no-floppy --fs-uuid --set 6eb0817ab0814a13
chainloader +1
}
menuentry Windows 7 (loader) (on /dev/sda2) {
insmod part_msdos
insmod ntfs
set root='(hd0,msdos2)'
search --no-floppy --fs-uuid --set b8f4a8c3f4a884ea
chainloader +1
}
menuentry Windows Recovery Environment (loader) (on /dev/sda3) {
Re: multi-boot cfdisk warning: is it broke? How do I fix?
On Wed, 20 Jul 2011 12:45:59 -0500 Charles Blair c-bl...@illinois.edu wrote: I tried to set up a dual boot of windows and linux from the installer. The linux part works, but windows 7 starts to boot and then takes me back to grub. I am sufficiently happy with linux that I was planning to get rid of windows. I would like to use the space to give openBSD a try. As a first step, I tried using cfdisk -Ps /dev/sda, and got the ominous warning: FATAL ERROR: Bad primary partition 2: Partition ends in the final partial cylinder Since linux is working, I'm worried that trying to fix whatever this problem is might wreck my system. Possibly. Windows is extremely fussy, even as far back as NT4 it could not be moved on a hard drive once installed. What did you use to shrink the original Windows partition, which I assume ran all the way up to sda3? It would appear that this software was to blame for the issue. fdisk -l /dev/sda gives: Disk /dev/sda: 320.1 GB, 320072933376 bytes 255 heads, 63 sectors/track, 38913 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0xbb0c5abb Device Boot Start End Blocks Id System /dev/sda1 1 192 1536000 27 Unknown /dev/sda2 192 12349976562507 HPFS/NTFS /dev/sda3 37264 3891413248512 17 Hidden HPFS/NTFS /dev/sda4 12350 37264 2001285135 Extended /dev/sda5 * 12350 12392 340992 83 Linux This one might be the issue. Before Vista, Windows absolutely required its boot partition to be marked bootable. I don't know if that is true now, as I haven't done any multi-boot work since XP. But Linux does not use the bootable flag, so there's no harm in moving it to sda2 to try. There's a (I hope) minor point that sda3 and sda4 share a block, which may not cause trouble, but may prevent the hidden partition (presumably a recovery image for Windows) from working. I would hope you made an image backup of that partition first, as there aren't many W7 installation discs around. /dev/sda6 12392 13486 8787968 83 Linux /dev/sda7 13486 13851 2928640 83 Linux /dev/sda8 13851 14826 7827456 82 Linux swap / Solaris /dev/sda9 14826 14874 389120 83 Linux /dev/sda10 14874 37264 179849216 83 Linux Partition table entries are not in disk order This never used to be an issue, except for at least one early Windows partition utility. I've no idea what software now might have problems with it. -- Joe -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110720200910.1159d...@jresid.jretrading.com
Re: multi-boot mess: have I destroyed Windows 7 ?
On Sat, May 28, 2011 at 3:10 PM, Charles Blair c-bl...@illinois.edu wrote: ** THE MESS * I recently tried to set up a multi-boot with windows 7 and squeeze on a laptop. When started, grub displays /dev/sda1 Windows 7 /dev/sda2 also Windows 7 /dev/sda3 Windows 7 recovery /dev/sda4 Debian /dev/sda5 Debian recovery I am relieved that Debian works, but the other choices give me failed to start error messages. I give fdisk and grub configuration information below * HOW I CREATED THE MESS The installer initially reported three partitions allocated to windows. I re-sized the largest one (I think this was the second one) and then put debian into the free space. * FDISK INFORMATION* Disk /dev/sda: 320.1 GB, 320072933376 bytes 255 heads, 63 sectors/track, 38913 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0xbb0c5abb Device Boot Start End Blocks Id System /dev/sda1 1 192 1536000 27 Unknown /dev/sda2 192 12349976562507 HPFS/NTFS /dev/sda3 37264 3891413248512 17 Hidden HPFS/NTFS /dev/sda4 12350 37264 2001285135 Extended /dev/sda5 * 12350 12392 340992 83 Linux /dev/sda6 12392 13486 8787968 83 Linux /dev/sda7 13486 13851 2928640 83 Linux /dev/sda8 13851 14826 7827456 82 Linux swap / Solaris /dev/sda9 14826 14874 389120 83 Linux /dev/sda10 14874 37264 179849216 83 Linux [snip] Hi Charles. In my experience with dual-booting, the key is to have the Win7 partition that is actually the bootable partition, flagged as bootable via gparted/fdisk/etc., before installing Debian. Win7 makes a mess of partitioning if you don't manually force it into your own partitioning scheme. I learned the hard way, and wound up wiping out the Debian installation and MBR, then rebuilding the MBR for Win7 to be bootable, then installing Debian again. There are lots of people smarter than me on this list that may have a better way, but that's what I can share with you from my own struggles. I avoid dual-booting if at all possible these days, although in some cases it is unavoidable. Maybe someone else will chime in with a better idea for you. Mark
Re: multi-boot mess: have I destroyed Windows 7 ?
On Sat, May 28, 2011 at 05:10:40PM -0500, Charles Blair wrote:
** THE MESS *
I recently tried to set up a multi-boot with windows 7
and squeeze on a laptop. When started, grub displays
/dev/sda1 Windows 7
/dev/sda2 also Windows 7
/dev/sda3 Windows 7 recovery
/dev/sda4 Debian
/dev/sda5 Debian recovery
I am relieved that Debian works, but the other choices
give me failed to start error messages. I give fdisk
and grub configuration information below
* HOW I CREATED THE MESS
The installer initially reported three partitions allocated
to windows. I re-sized the largest one (I think this was the
second one) and then put debian into the free space.
* FDISK INFORMATION*
Disk /dev/sda: 320.1 GB, 320072933376 bytes
255 heads, 63 sectors/track, 38913 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0xbb0c5abb
Device Boot Start End Blocks Id System
/dev/sda1 1 192 1536000 27 Unknown
/dev/sda2 192 12349976562507 HPFS/NTFS
^
This looks like a partition big enough, albeit cramped, to house Windows.
And it has a Windows-like arrangement: the small Unknown in front and the
smallish Hidden behind. And your menuentry points to it.
I am unfamiliar with HPFS/NTFS. I am also unfamiliar with Windows 7.
It is still worth trying a fix of your MBR and reinstalling GRUB2.
Do you have a 7 install disk?
http://www.ehow.com/how_4836283_repair-mbr-windows.html
Otherwise you might download bootrec.exe from microsoft or somewhere on line.
Then a reinstall of GRUB2 is required.
SuperGrubDisk evidently can't handle GRUB2 any longer. There is a
replacement called Rescatux. At 0.25, it is not even close to version 1.
But is says it has something like it bootrec.exe, and it says it can fix
GRUB2.
You will have to download an iso and unpack-burn to a CD.
Or, use the rescue section of the Debian installer:
http://wiki.debian.org/GrubRecover
/dev/sda3 37264 3891413248512 17 Hidden HPFS/NTFS
/dev/sda4 12350 37264 2001285135 Extended
/dev/sda5 * 12350 12392 340992 83 Linux
/dev/sda6 12392 13486 8787968 83 Linux
/dev/sda7 13486 13851 2928640 83 Linux
/dev/sda8 13851 14826 7827456 82 Linux swap / Solaris
/dev/sda9 14826 14874 389120 83 Linux
/dev/sda10 14874 37264 179849216 83 Linux
Partition table entries are not in disk order
** THE WINDOWS PART OF THE GRUB.CONF FILE **
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#
### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
load_env
fi
set default=0
if [ ${prev_saved_entry} ]; then
set saved_entry=${prev_saved_entry}
save_env saved_entry
set prev_saved_entry=
save_env prev_saved_entry
set boot_once=true
fi
function savedefault {
if [ -z ${boot_once} ]; then
saved_entry=${chosen}
save_env saved_entry
fi
}
function load_video {
insmod vbe
insmod vga
insmod video_bochs
insmod video_cirrus
}
insmod part_msdos
insmod ext2
set root='(hd0,msdos6)'
search --no-floppy --fs-uuid --set a5ae78d6-949a-4462-bc98-6c53a846c401
if loadfont /share/grub/unicode.pf2 ; then
set gfxmode=640x480
load_video
insmod gfxterm
fi
terminal_output gfxterm
insmod part_msdos
insmod ext2
set root='(hd0,msdos5)'
search --no-floppy --fs-uuid --set d487742e-ad50-4347-8d9a-b8d0f1908c13
set locale_dir=($root)/boot/grub/locale
set lang=en
insmod gettext
set timeout=5
### END /etc/grub.d/00_header ###
### BEGIN /etc/grub.d/05_debian_theme ###
insmod part_msdos
insmod ext2
set root='(hd0,msdos6)'
search --no-floppy --fs-uuid --set a5ae78d6-949a-4462-bc98-6c53a846c401
insmod png
if background_image /share/images/desktop-base/spacefun-grub.png; then
set color_normal=light-gray/black
set color_highlight=white/black
else
set menu_color_normal=cyan/blue
set menu_color_highlight=white/blue
fi
### END /etc/grub.d/05_debian_theme ###
### BEGIN /etc/grub.d/10_linux ###
menuentry 'Debian GNU/Linux, with Linux 2.6.32-5-amd64' --class debian
--class gnu-linux --class gnu --class os {
insmod part_msdos
insmod ext2
set root='(hd0,msdos5)'
search --no-floppy --fs-uuid --set d487742e-ad50-4347-8d9a-b8d0f1908c13
echo'Loading Linux 2.6.32-5-amd64 ...'
linux /boot/vmlinuz-2.6.32-5-amd64
root=UUID=d487742e-ad50-4347-8d9a-b8d0f1908c13 ro quiet
echo'Loading initial ramdisk ...'
initrd /boot/initrd.img-2.6.32-5-amd64
multi-boot mess: have I destroyed Windows 7 ?
** THE MESS *
I recently tried to set up a multi-boot with windows 7
and squeeze on a laptop. When started, grub displays
/dev/sda1 Windows 7
/dev/sda2 also Windows 7
/dev/sda3 Windows 7 recovery
/dev/sda4 Debian
/dev/sda5 Debian recovery
I am relieved that Debian works, but the other choices
give me failed to start error messages. I give fdisk
and grub configuration information below
* HOW I CREATED THE MESS
The installer initially reported three partitions allocated
to windows. I re-sized the largest one (I think this was the
second one) and then put debian into the free space.
* FDISK INFORMATION*
Disk /dev/sda: 320.1 GB, 320072933376 bytes
255 heads, 63 sectors/track, 38913 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0xbb0c5abb
Device Boot Start End Blocks Id System
/dev/sda1 1 192 1536000 27 Unknown
/dev/sda2 192 12349976562507 HPFS/NTFS
/dev/sda3 37264 3891413248512 17 Hidden HPFS/NTFS
/dev/sda4 12350 37264 2001285135 Extended
/dev/sda5 * 12350 12392 340992 83 Linux
/dev/sda6 12392 13486 8787968 83 Linux
/dev/sda7 13486 13851 2928640 83 Linux
/dev/sda8 13851 14826 7827456 82 Linux swap / Solaris
/dev/sda9 14826 14874 389120 83 Linux
/dev/sda10 14874 37264 179849216 83 Linux
Partition table entries are not in disk order
** THE WINDOWS PART OF THE GRUB.CONF FILE **
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#
### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
load_env
fi
set default=0
if [ ${prev_saved_entry} ]; then
set saved_entry=${prev_saved_entry}
save_env saved_entry
set prev_saved_entry=
save_env prev_saved_entry
set boot_once=true
fi
function savedefault {
if [ -z ${boot_once} ]; then
saved_entry=${chosen}
save_env saved_entry
fi
}
function load_video {
insmod vbe
insmod vga
insmod video_bochs
insmod video_cirrus
}
insmod part_msdos
insmod ext2
set root='(hd0,msdos6)'
search --no-floppy --fs-uuid --set a5ae78d6-949a-4462-bc98-6c53a846c401
if loadfont /share/grub/unicode.pf2 ; then
set gfxmode=640x480
load_video
insmod gfxterm
fi
terminal_output gfxterm
insmod part_msdos
insmod ext2
set root='(hd0,msdos5)'
search --no-floppy --fs-uuid --set d487742e-ad50-4347-8d9a-b8d0f1908c13
set locale_dir=($root)/boot/grub/locale
set lang=en
insmod gettext
set timeout=5
### END /etc/grub.d/00_header ###
### BEGIN /etc/grub.d/05_debian_theme ###
insmod part_msdos
insmod ext2
set root='(hd0,msdos6)'
search --no-floppy --fs-uuid --set a5ae78d6-949a-4462-bc98-6c53a846c401
insmod png
if background_image /share/images/desktop-base/spacefun-grub.png; then
set color_normal=light-gray/black
set color_highlight=white/black
else
set menu_color_normal=cyan/blue
set menu_color_highlight=white/blue
fi
### END /etc/grub.d/05_debian_theme ###
### BEGIN /etc/grub.d/10_linux ###
menuentry 'Debian GNU/Linux, with Linux 2.6.32-5-amd64' --class debian --class
gnu-linux --class gnu --class os {
insmod part_msdos
insmod ext2
set root='(hd0,msdos5)'
search --no-floppy --fs-uuid --set d487742e-ad50-4347-8d9a-b8d0f1908c13
echo'Loading Linux 2.6.32-5-amd64 ...'
linux /boot/vmlinuz-2.6.32-5-amd64
root=UUID=d487742e-ad50-4347-8d9a-b8d0f1908c13 ro quiet
echo'Loading initial ramdisk ...'
initrd /boot/initrd.img-2.6.32-5-amd64
}
menuentry 'Debian GNU/Linux, with Linux 2.6.32-5-amd64 (recovery mode)' --class
debian --class gnu-linux --class gnu --class os {
insmod part_msdos
insmod ext2
set root='(hd0,msdos5)'
search --no-floppy --fs-uuid --set d487742e-ad50-4347-8d9a-b8d0f1908c13
echo'Loading Linux 2.6.32-5-amd64 ...'
linux /boot/vmlinuz-2.6.32-5-amd64
root=UUID=d487742e-ad50-4347-8d9a-b8d0f1908c13 ro single
echo'Loading initial ramdisk ...'
initrd /boot/initrd.img-2.6.32-5-amd64
}
### END /etc/grub.d/10_linux ###
### BEGIN /etc/grub.d/20_linux_xen ###
### END /etc/grub.d/20_linux_xen ###
### BEGIN /etc/grub.d/30_os-prober ###
menuentry Windows 7 (loader) (on /dev/sda1) {
insmod part_msdos
insmod ntfs
set root='(hd0,msdos1)'
search --no-floppy --fs-uuid --set 6eb0817ab0814a13
chainloader +1
}
menuentry Windows 7 (loader) (on /dev/sda2) {
insmod part_msdos
insmod ntfs
set root='(hd0,msdos2)'
search --no-floppy --fs-uuid --set b8f4a8c3f4a884ea
chainloader +1
Re: multi-boot mess: have I destroyed Windows 7 ?
On 05/28/2011 05:10 PM, Charles Blair wrote: [snip] We can only pray that you have... grin -- Neither the wisest constitution nor the wisest laws will secure the liberty and happiness of a people whose manners are universally corrupt. Samuel Adams, essay in The Public Advertiser, 1749 -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4de1bb56.6050...@cox.net
Re: Need advice from experts in complex multi-boot setups.
I purchased an Iomega mobile HDD 250GB and am planning to install on it several OSs: MacOSX 10.5.8 (Hackintosh), Solaris10, OpenSolaris, Debian, OpenSuse, Fedora, BSDs (FreeBSD and OpenBSD). The computer is a Dell netbook Mini9 which supports all these operative systems very well (with the Solaris family only the Wifi driver does not exist natively,and needs a driver designed for Windows). I need some advice about the right strategy to follow, especially about: 1) For what OSs use primary partitions or logical partitions. The Linuxes can boot from logical partitions. Never tried to boot the Solarises from anything other than primary partitions; sorry. Never used Hackintosh or the other BSDs. 2) Different swap partitions for different OSs? The Linuxes and Solarises can share a swap partition. A former colleague once claimed that Linux could use a FreeBSD swap slice as a Linux swap partition (but not the other way around). He was very knowledgeable so I assume that it is possible. OS X uses swap files in its /var/vm directory, so Hackintosh probably does too and therefore must not need a swap partition. Please tell us how you can manage to boot Leopard (OS X 10.5) on a Dell Netbook. OS X has been hacked to boot on non-Apple hardware (and installers have been posted online); probably using the fact that OS X is based on Mach/FreeBSD. Technically interesting but morally... AFAIK at least for Linux you need 1 primary partition of small size (200MB is nearly too big) which contains /boot if you want to use LVM. I would ditch the default LVM setup (in Fedora for example) in order to free up primary partitions, should the BSDs and/or Solarises need them. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Need advice from experts in complex multi-boot setups.
The case: I purchased an Iomega mobile HDD 250GB and am planning to install on it several OSs: MacOSX 10.5.8(Hackintosh),Solaris10,OpenSolaris, Debian,OpenSuse,Fedora,BSDs(FreeBSD and OpenBSD).The computer is a Dell netbook Mini9 which supports all these operative systems very well(with the Solaris family only the Wifi driver does not exist natively,and needs a driver designed for Windows). So I need some advice about the right strategy to follow,specially about: 1)For what OSs use primary partitions or logical partitions. 2)Different swap partitions for different OSs? 3)Can GRUB handle booting all these OSs?Needs special configuration? Thanks. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Need advice from experts in complex multi-boot setups.
* Luis Maceira [091002 15:55 -0700] The case: I purchased an Iomega mobile HDD 250GB and am planning to install on it several OSs: MacOSX 10.5.8(Hackintosh),Solaris10,OpenSolaris, Debian,OpenSuse,Fedora,BSDs(FreeBSD and OpenBSD).The computer is a Dell netbook Mini9 which supports all these operative systems very well(with the Solaris family only the Wifi driver does not exist natively,and needs a driver designed for Windows). Please tell us how you can manage to boot Leopard (OSX 10.5) on a Dell Netbook. Elimar -- what IMHO then? IMHO - Inhalation of a Multi-leafed Herbal Opiate ;) --posting from alex in debian-user-- signature.asc Description: Digital signature
Re: Need advice from experts in complex multi-boot setups.
I purchased an Iomega mobile HDD 250GB and am planning to install on it several OSs: MacOSX 10.5.8 (Hackintosh), Solaris10, OpenSolaris, Debian, OpenSuse, Fedora, BSDs (FreeBSD and OpenBSD). The computer is a Dell netbook Mini9 which supports all these operative systems very well (with the Solaris family only the Wifi driver does not exist natively,and needs a driver designed for Windows). I need some advice about the right strategy to follow, especially about: 1) For what OSs use primary partitions or logical partitions. The Linuxes can boot from logical partitions. Never tried to boot the Solarises from anything other than primary partitions; sorry. Never used Hackintosh or the other BSDs. 2) Different swap partitions for different OSs? The Linuxes and Solarises can share a swap partition. A former colleague once claimed that Linux could use a FreeBSD swap slice as a Linux swap partition (but not the other way around). He was very knowledgeable so I assume that it is possible. OS X uses swap files in its /var/vm directory, so Hackintosh probably does too and therefore must not need a swap partition. Please tell us how you can manage to boot Leopard (OS X 10.5) on a Dell Netbook. OS X has been hacked to boot on non-Apple hardware (and installers have been posted online); probably using the fact that OS X is based on Mach/FreeBSD. Technically interesting but morally... -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Need advice from experts in complex multi-boot setups.
Hello, AFAIK at least for Linux you need 1 primary partition of small size (200MB is nearly too big) which contains /boot if you want to use LVM. greetings, vitaminx 2009/10/3 Tom H tomh0...@gmail.com I purchased an Iomega mobile HDD 250GB and am planning to install on it several OSs: MacOSX 10.5.8 (Hackintosh), Solaris10, OpenSolaris, Debian, OpenSuse, Fedora, BSDs (FreeBSD and OpenBSD). The computer is a Dell netbook Mini9 which supports all these operative systems very well (with the Solaris family only the Wifi driver does not exist natively,and needs a driver designed for Windows). I need some advice about the right strategy to follow, especially about: 1) For what OSs use primary partitions or logical partitions. The Linuxes can boot from logical partitions. Never tried to boot the Solarises from anything other than primary partitions; sorry. Never used Hackintosh or the other BSDs. 2) Different swap partitions for different OSs? The Linuxes and Solarises can share a swap partition. A former colleague once claimed that Linux could use a FreeBSD swap slice as a Linux swap partition (but not the other way around). He was very knowledgeable so I assume that it is possible. OS X uses swap files in its /var/vm directory, so Hackintosh probably does too and therefore must not need a swap partition. Please tell us how you can manage to boot Leopard (OS X 10.5) on a Dell Netbook. OS X has been hacked to boot on non-Apple hardware (and installers have been posted online); probably using the fact that OS X is based on Mach/FreeBSD. Technically interesting but morally... -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org -- irc ... #chezpaeule @ euirc mud ... vitaminx @ aardmud
[OT] multi-boot many small ISO from the same CD
Hi, I recently found that there are these kind of collection CDs that contains multi small Live CDs on one CD, and bootable floppy disk images as well. I've found one utility to create such CDs, but that's Windoze based. I'm wonder if anyone knows if there is any way to create such collection CDs under Linux. Any comments are welcome. thanks tong -- Tong (remove underscore(s) to reply) http://xpt.sourceforge.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: help making multi-boot system
On Thu, 23 Mar 2006 22:06:46 -0600 Mike McCarty [EMAIL PROTECTED] wrote: I hadn't thought about the inability to resize FAT partitions without reformatting. AFAIK PartitionMagic can resize FAT32 without any problems. Andrei -- If you can't explain it simply, you don't understand it well enough. (Albert Einstein) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: multi boot ( GRUB )
On Tuesday 14 February 2006 01:07, Fred Ulisses Maranhao wrote: On Mon, 13 Feb 2006 10:45:00 +0100 tombs [EMAIL PROTECTED] wrote: Pessoal, ja tentei de tudo. Fiz varias mudancas no meu menu.lst mas nao estou conseguindo fazer esse boot do ruindao funcionar. Sao dois hd's separados. Gravei primeiro o ruindao no hdb com o hd master desligado, e depois fiz a operacao inversa. Quando liguei os dois hds, pensava que o grub ia detectar o hdb e inclui-lo, mas isso nao aconteceu. Ja tentei foruns mas nao ta dando nada. você, do linux do hda, consegue ver o windows do hdb? tente fdisk /dev/hdb ou montar o hdb. Se não conseguir pode ser algo errado na bios (por exemplo, não detectou o segundo hd quando ligou os dois). voce pode ver as partições do sistema mesmo sem monta-las, usando o comando fdisk -l Se conseguir, volte a quebrar a cabeça com o grub (e nos avise). Paro por aqui, Fred Tentei hoje, o que esta no foca: title: Microsoft Windows XP Professional unhide (hd1,0) rootnoverify (hd1,0) chainloader +1 map (hd1)(hd0) makeactive Mas nao deu certo. Bom meu menu.lst é esse: title Debian GNU/Linux, kernel 2.6.14-2-386 root(hd0,2) kernel /boot/vmlinuz-2.6.14-2-386 root=/dev/hda3 ro initrd /boot/initrd.img-2.6.14-2-386 savedefault boot title Debian GNU/Linux, kernel 2.6.14-2-386 (recovery mode) root(hd0,2) kernel /boot/vmlinuz-2.6.14-2-386 root=/dev/hda3 ro single initrd /boot/initrd.img-2.6.14-2-386 savedefault boot ### END DEBIAN AUTOMAGIC KERNELS LIST # This is a divider, added to separate the menu items below from the Debian # ones. title Other operating systems: root # This entry automatically added by the Debian installer for an existing # linux installation on /dev/hda4. title Ubuntu, kernel 2.6.12-10-386 (on /dev/hda4) root(hd0,3) kernel /boot/vmlinuz-2.6.12-10-386 root=/dev/hda4 ro quiet splash initrd /boot/initrd.img-2.6.12-10-386 savedefault boot # This entry automatically added by the Debian installer for an existing # linux installation on /dev/hda4. title Ubuntu, memtest86+ (on /dev/hda4) root(hd0,3) kernel /boot/memtest86+.bin savedefault boot title Other operating systems: root # This entry manually added by root for a non-linux OS # on /dev/hdb1 title Microsoft Windows XP Professional map (hd1) (hd0) map (hd0) (hd1) rootnoverify (hd1,0) savedefault makeactive chainloader +1 Alguem poderia me ajudar, por favor? THANX -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] ___ Yahoo! doce lar. Faa do Yahoo! sua homepage. http://br.yahoo.com/homepageset.html -- Andre Novelli [EMAIL PROTECTED]
multi boot ( GRUB )
Pessoal, ja tentei de tudo. Fiz varias mudancas no meu menu.lst mas nao estou conseguindo fazer esse boot do ruindao funcionar. Sao dois hd's separados. Gravei primeiro o ruindao no hdb com o hd master desligado, e depois fiz a operacao inversa. Quando liguei os dois hds, pensava que o grub ia detectar o hdb e inclui-lo, mas isso nao aconteceu. Ja tentei foruns mas nao ta dando nada. Tentei hoje, o que esta no foca: title: Microsoft Windows XP Professional unhide (hd1,0) rootnoverify (hd1,0) chainloader +1 map (hd1)(hd0) makeactive Mas nao deu certo. Bom meu menu.lst é esse: title Debian GNU/Linux, kernel 2.6.14-2-386 root(hd0,2) kernel /boot/vmlinuz-2.6.14-2-386 root=/dev/hda3 ro initrd /boot/initrd.img-2.6.14-2-386 savedefault boot title Debian GNU/Linux, kernel 2.6.14-2-386 (recovery mode) root(hd0,2) kernel /boot/vmlinuz-2.6.14-2-386 root=/dev/hda3 ro single initrd /boot/initrd.img-2.6.14-2-386 savedefault boot ### END DEBIAN AUTOMAGIC KERNELS LIST # This is a divider, added to separate the menu items below from the Debian # ones. title Other operating systems: root # This entry automatically added by the Debian installer for an existing # linux installation on /dev/hda4. title Ubuntu, kernel 2.6.12-10-386 (on /dev/hda4) root(hd0,3) kernel /boot/vmlinuz-2.6.12-10-386 root=/dev/hda4 ro quiet splash initrd /boot/initrd.img-2.6.12-10-386 savedefault boot # This entry automatically added by the Debian installer for an existing # linux installation on /dev/hda4. title Ubuntu, memtest86+ (on /dev/hda4) root(hd0,3) kernel /boot/memtest86+.bin savedefault boot title Other operating systems: root # This entry manually added by root for a non-linux OS # on /dev/hdb1 title Microsoft Windows XP Professional map (hd1) (hd0) map (hd0) (hd1) rootnoverify (hd1,0) savedefault makeactive chainloader +1 Alguem poderia me ajudar, por favor? THANX -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: multi boot ( GRUB )
tombs escreveu: Pessoal, ja tentei de tudo. Fiz varias mudancas no meu menu.lst mas nao estou conseguindo fazer esse boot do ruindao funcionar. Sao dois hd's separados. Gravei primeiro o ruindao no hdb com o hd master desligado, e depois fiz a operacao inversa. Quando liguei os dois hds, pensava que o grub ia detectar o hdb e inclui-lo, mas isso nao aconteceu. Ja tentei foruns mas nao ta dando nada. Tentei hoje, o que esta no foca: title: Microsoft Windows XP Professional unhide (hd1,0) rootnoverify (hd1,0) chainloader +1 map (hd1)(hd0) makeactive Mas nao deu certo. Bom meu menu.lst é esse: title Debian GNU/Linux, kernel 2.6.14-2-386 root(hd0,2) kernel /boot/vmlinuz-2.6.14-2-386 root=/dev/hda3 ro initrd /boot/initrd.img-2.6.14-2-386 savedefault boot title Debian GNU/Linux, kernel 2.6.14-2-386 (recovery mode) root(hd0,2) kernel /boot/vmlinuz-2.6.14-2-386 root=/dev/hda3 ro single initrd /boot/initrd.img-2.6.14-2-386 savedefault boot ### END DEBIAN AUTOMAGIC KERNELS LIST # This is a divider, added to separate the menu items below from the Debian # ones. title Other operating systems: root # This entry automatically added by the Debian installer for an existing # linux installation on /dev/hda4. title Ubuntu, kernel 2.6.12-10-386 (on /dev/hda4) root(hd0,3) kernel /boot/vmlinuz-2.6.12-10-386 root=/dev/hda4 ro quiet splash initrd /boot/initrd.img-2.6.12-10-386 savedefault boot # This entry automatically added by the Debian installer for an existing # linux installation on /dev/hda4. title Ubuntu, memtest86+ (on /dev/hda4) root(hd0,3) kernel /boot/memtest86+.bin savedefault boot title Other operating systems: root # This entry manually added by root for a non-linux OS # on /dev/hdb1 title Microsoft Windows XP Professional map (hd1) (hd0) map (hd0) (hd1) rootnoverify (hd1,0) savedefault makeactive chainloader +1 Alguem poderia me ajudar, por favor? THANX Você já tentou conectar ambos hds e em init1 rodar: update-grub grub-install /dev/hda acredito qu o grub va detectar os sistemas e por as entradas (seu win e um que esta em um bigfoot ???), pode ser algum problema no reconhecimento do hardware. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: multi boot ( GRUB )
On Mon, 13 Feb 2006 10:45:00 +0100 tombs [EMAIL PROTECTED] wrote: Pessoal, ja tentei de tudo. Fiz varias mudancas no meu menu.lst mas nao estou conseguindo fazer esse boot do ruindao funcionar. Sao dois hd's separados. Gravei primeiro o ruindao no hdb com o hd master desligado, e depois fiz a operacao inversa. Quando liguei os dois hds, pensava que o grub ia detectar o hdb e inclui-lo, mas isso nao aconteceu. Ja tentei foruns mas nao ta dando nada. você, do linux do hda, consegue ver o windows do hdb? tente fdisk /dev/hdb ou montar o hdb. Se não conseguir pode ser algo errado na bios (por exemplo, não detectou o segundo hd quando ligou os dois). Se conseguir, volte a quebrar a cabeça com o grub (e nos avise). Paro por aqui, Fred Tentei hoje, o que esta no foca: title: Microsoft Windows XP Professional unhide (hd1,0) rootnoverify (hd1,0) chainloader +1 map (hd1)(hd0) makeactive Mas nao deu certo. Bom meu menu.lst é esse: title Debian GNU/Linux, kernel 2.6.14-2-386 root(hd0,2) kernel /boot/vmlinuz-2.6.14-2-386 root=/dev/hda3 ro initrd /boot/initrd.img-2.6.14-2-386 savedefault boot title Debian GNU/Linux, kernel 2.6.14-2-386 (recovery mode) root(hd0,2) kernel /boot/vmlinuz-2.6.14-2-386 root=/dev/hda3 ro single initrd /boot/initrd.img-2.6.14-2-386 savedefault boot ### END DEBIAN AUTOMAGIC KERNELS LIST # This is a divider, added to separate the menu items below from the Debian # ones. title Other operating systems: root # This entry automatically added by the Debian installer for an existing # linux installation on /dev/hda4. title Ubuntu, kernel 2.6.12-10-386 (on /dev/hda4) root(hd0,3) kernel /boot/vmlinuz-2.6.12-10-386 root=/dev/hda4 ro quiet splash initrd /boot/initrd.img-2.6.12-10-386 savedefault boot # This entry automatically added by the Debian installer for an existing # linux installation on /dev/hda4. title Ubuntu, memtest86+ (on /dev/hda4) root(hd0,3) kernel /boot/memtest86+.bin savedefault boot title Other operating systems: root # This entry manually added by root for a non-linux OS # on /dev/hdb1 title Microsoft Windows XP Professional map (hd1) (hd0) map (hd0) (hd1) rootnoverify (hd1,0) savedefault makeactive chainloader +1 Alguem poderia me ajudar, por favor? THANX -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] ___ Yahoo! doce lar. Faça do Yahoo! sua homepage. http://br.yahoo.com/homepageset.html
Grub le multi boot
Bonjour à tous, J'ai du mal à configurer Grub et je demande assistance... J'ai la Debian installée sur mon premier disque IDE (hda). J'ai Windows installé sur un autre disque SATA (sda?). Grub arrive correctement à démarrer la Debian mais je n'arrive pas à le configurer pour qu'il démarre Windows. Des idées ? Voila à quoi ressemble mon menu.lst : title Debian GNU/Linux, kernel 2.6.8-2-386 root(hd0,0) kernel /boot/vmlinuz-2.6.8-2-386 root=/dev/hda1 ro vga=0x318 initrd /boot/initrd.img-2.6.8-2-386 savedefault boot title Windows 95/98/NT/2000 rootnoverify(hd1,0) makeactive chainloader +1 Merci d'avance, Guillaume. Accédez au courrier électronique de La Poste : www.laposte.net ; 3615 LAPOSTENET (0,34/mn) ; tél : 08 92 68 13 50 (0,34/mn)
Re: multi boot
Le jeudi 04 mars 2004, Arnaud a écrit... bonjour, Est ce que vous auriez une solution à mon problème faire passer ton lilo.conf préciser le type de W$ que tu utilises. -- jm
Re: multi boot
Bonjour a vous tous, membre de la mailing liste J'ai deux disk dur, l'un est sous windows et l'autre sous linux. J'aurais aimer faire un multi boot afin d'éviter d'éteindre à chaque fois le pc quand je veux basculer de l'un à l'autre J'ai brancher mes deux disks comme il faut et il boot correctement sous linux. J'ai modifier mon lilo afin d'avoir une entrée pour linux mais quand je redémarre et que je choisi windows, ça marche pas il reste bloqué à loading windows. Est ce que vous auriez une solution à mon problème j ai deja eu le probleme. comment as tu mis windows sur ton 2e dure ? as tu changé les branchements de tes disque dur ?
Re: multi boot
Bonjour Avec win mis en 2eme disque apres son install En ajoutant a la fin de lilo.conf : ## other=/dev/hdb1 #ou bien other=/dev/hdc1 selon le cas label=2000_Pro table=/dev/hdb #ou table=/dev/hdc map-drive = 0x80 to = 0x81 map-drive = 0x81 to = 0x80 ## et relancer lilo Ca doit marcher P. J'ai deux disk dur, l'un est sous windows et l'autre sous linux. J'aurais aimer faire un multi boot afin d'éviter d'éteindre à chaque J'ai brancher mes deux disks comme il faut et il boot correctement sous linux. J'ai modifier mon lilo afin d'avoir une entrée pour linux mais e
multi boot
Bonjour a vous tous, membre de la mailing liste J'ai deux disk dur, l'un est sous windows et l'autre sous linux. J'aurais aimer faire un multi boot afin d'éviter d'éteindre à chaque fois le pc quand je veux basculer de l'un à l'autre J'ai brancher mes deux disks comme il faut et il boot correctement sous linux. J'ai modifier mon lilo afin d'avoir une entrée pour linux mais quand je redémarre et que je choisi windows, ça marche pas il reste bloqué à loading windows. Est ce que vous auriez une solution à mon problème Merci à tous Nono
Re: multi-boot
Kevin == Kevin Mark [EMAIL PROTECTED] writes: Kevin On Mon, Jan 19, 2004 at 05:28:27PM +0100, Chris Searle Kevin wrote: Hi Chris, why not make a boot disk? man mkboot -Kev Machine has no floppy drive. Nor CD-ROM (unless I undock one of the hard drives). Nowhere to put the disk to boot :-( -- Chris Searle -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
multi-boot
OK - multi-boot. hda1 Win2k hdc1 Win2k hdc6 boot for debian hda1 is a bog standard win2k system hdc1 contains it's replacement to be run under vmware under debian in hdc6. Trying to set it up so that either lilo (installed on hdc but not in the mbr) or ntldr (on hda1) can boot both systems - am not bothered which way round (this config is needed until everything is up and running - then hda will be removed). Have been thru the multi-boot howto. Setup 1 Machine set to boot from hda NTLDR contains the extra line c:\bootlinx.bin=Linux bootlinx.bin is created from dd if=/dev/hdc6 of=bootlinx.bin bs=512 count=1 This boots to the NTLDR - choose Linux - blank screen with a flashing cursor - no further. Tried with Bootpart - that gave some text about it being Bootpart ... then died when it tried to actually trigger the boot. The win2k on hda1 boots fine. Setup 2 Machine set to boot from hdc Lilo has other=/dev/hda1 label=Win2k Boots to LILO - choose Win2k - you get the message Can't find NTLDR. Debian on hdc6 boots fine. Now - is this possible with the table= or other lilo conf lines? Do I need to move to GRUB (hope not)? Any other hints? -- Chris Searle -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: multi-boot
On Mon, Jan 19, 2004 at 05:28:27PM +0100, Chris Searle wrote: Hi Chris, why not make a boot disk? man mkboot -Kev signature.asc Description: Digital signature
Re: PC multi boot et mail
Merci à tous pour réponse. Je vais maintenant découvrir Mozilla afin de préparer la migration. PS: C'est bien dans cette ML que je trouve ( et depuis mes premiers pas sous linux-debian ) le plus conseils précieux. Kamel At 00:33 24/04/2003 +0200, yoann wrote: Le seul veritable soucis qui me bloc et depuis pas mal de temps, c'est la messagerie: Je recherche donc le moyen d'acceder à mes mail et aux archives que je sois sous W2K ou sous Debian ( Sous W2K, j'utilise Eudora ). Imaginons, une partitions FAT32 accessible en rw sous 2 les OS où je retrouverais tout mes mails. Est-ce inconcevable ou existe-t-il une formule magique ? Bien entendus, si il le faut, je suis prêt à quitter mon bon Eudora pour une application multi plateforme J'ai fait ça dans le temps ou j'avais windows sur mon pc avec mozilla, ça marche trés bien. A l'époque, j'avais 1 win 2000, 1 XP, 1 mdk et 1 debian et tous sous mozilla pour lire les mails pointant vers le meme repertoire, maintenant, j'ai plus que debian... Le truc c'est que j'ai du bidouiller un peu à la main le fichier prefs.js pour l'histoir des chemins (à cause du repertoire genre htrkwkg.slt générere aléatoirement lors de la création du login), ça prend un peu de temps à mettre en place mais ça marche bien. ce qu'il faut garder à l'esprit, c'est que mozilla doit avoir un fichier perfs.js différent pour windows et pour linux. Merci. de rien kamel latrach yoann _ Envie de discuter en live avec vos amis ? Télécharger MSN Messenger http://www.ifrance.com/_reloc/m la 1ère messagerie instantanée de France -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
PC multi boot et mail
Bonjour, j'ai une question à vous soumettre : Voila, j'ai mon PC au boulot qui tourne sous W2K ( obligation professionnel - INTRANET, truc à la con, ... ) mais moi je voudrais bien y mettre une petite debian en multi boot ( histoire de ne pas trop me faire remarquer, je garde le W2K sous la main ). Le seul veritable soucis qui me bloc et depuis pas mal de temps, c'est la messagerie: Je recherche donc le moyen d'acceder à mes mail et aux archives que je sois sous W2K ou sous Debian ( Sous W2K, j'utilise Eudora ). Imaginons, une partitions FAT32 accessible en rw sous 2 les OS où je retrouverais tout mes mails. Est-ce inconcevable ou existe-t-il une formule magique ? Bien entendus, si il le faut, je suis prêt à quitter mon bon Eudora pour une application multi plateforme Merci. kamel latrach Network Administrator Tel: 05-49-49-57-71 Email: [EMAIL PROTECTED] e-Qual - Avenue du Futuroscope - Arobase 2, Téléport 1 86360 Chasseneuil du Poitou - FRANCE __o _`\,_ ..(_)/ (_)
Re: PC multi boot et mail
kamel latrach wrote: Le seul veritable soucis qui me bloc et depuis pas mal de temps, c'est la messagerie: Je recherche donc le moyen d'acceder à mes mail et aux archives que je sois sous W2K ou sous Debian ( Sous W2K, j'utilise Eudora ). Imaginons, une partitions FAT32 accessible en rw sous 2 les OS où je retrouverais tout mes mails. Là comme ça je vois mozilla : il utilise le même répertoire sous nunux (~/.mozilla/) et dodoz (C:\[lmachine\Profiles\[ton-profil]\Application_Data\[...]\mozilla\, 'fin dans l'genre) Donc depuis la deb tu monte la partition qui contient le-dit répertoire sous w2k, t'as gagné. En fait c'est l'ensemble du profil que tu liera aux 2 mozilla surement, mais tu peux ne spécifier que le chemins pour les mails : Mozilla edit Mail news settings ton compte server settings champ local directory. Mais il doit y avoir plus sioux pour éviter de te faire changer de client mail ... et en utilisé un plus performant sous linux (non, on ne regarde pas mes en-têtes ! :-) ) ++ JR
Re: PC multi boot et mail
Le mer 23/04/2003 à 18:02, kamel latrach a écrit : Bonjour, Bonsoir, j'ai une question à vous soumettre : Voila, j'ai mon PC au boulot qui tourne sous W2K ( obligation professionnel - INTRANET, truc à la con, ... ) mais moi je voudrais bien y mettre une petite debian en multi boot ( histoire de ne pas trop me faire remarquer, je garde le W2K sous la main ). Le seul veritable soucis qui me bloc et depuis pas mal de temps, c'est la messagerie: Je recherche donc le moyen d'acceder à mes mail et aux archives que je sois sous W2K ou sous Debian ( Sous W2K, j'utilise Eudora ). Imaginons, une partitions FAT32 accessible en rw sous 2 les OS où je retrouverais tout mes mails. Est-ce inconcevable ou existe-t-il une formule magique ? Bien entendus, si il le faut, je suis prêt à quitter mon bon Eudora pour une application multi plateforme Si mes souvenirs sont bons, dans le courrier des lecteurs de linux pratique du mois de mai (en kiosque actuellement), un lecteur raconte son expérience comme quoi il a installé Mandrake sur une partition FAT32, ce qui lui permet d'accéder à cette partition depuis windows... et donc de partager des docs et mails via Mozilla il me semble. Donc je dirais que c'est faisable. Maintenant est-ce que c'est recommandé ou viable, je ne peux te dire... Merci. de rien :) kamel latrach Network Administrator Tel: 05-49-49-57-71 Email: [EMAIL PROTECTED] e-Qual - Avenue du Futuroscope - Arobase 2, Téléport 1 86360 Chasseneuil du Poitou - FRANCE Nicolas
Re: PC multi boot et mail
Jean-Roch SOTTY wrote: kamel latrach wrote: Le seul veritable soucis qui me bloc et depuis pas mal de temps, c'est la messagerie: Je recherche donc le moyen d'acceder à mes mail et aux archives que je sois sous W2K ou sous Debian ( Sous W2K, j'utilise Eudora ). Imaginons, une partitions FAT32 accessible en rw sous 2 les OS où je retrouverais tout mes mails. Là comme ça je vois mozilla : il utilise le même répertoire sous nunux (~/.mozilla/) et dodoz C'est ce que j'ai fait avec unstable/w98 et mozilla: ca marche tres bien. Je n'ai pas pointe tout le repertoire linux vers w98 mais uniquement ce qui m'interesse: carnet d'adresse, dossier mails et favoris. -- : __ __ __ __ __ __ [EMAIL PROTECTED] : /_// __ // __ //_// __ // / phone.: +48 32 285 4554 : / / / /_/ // /_/ / / / / /_/ // / fax: +48 32 285 4554 : /_/ /_//_/ /_/ /_/ /_//_/ mobile..: +48 602 284 546
Re: PC multi boot et mail
Le seul veritable soucis qui me bloc et depuis pas mal de temps, c'est la messagerie: Je recherche donc le moyen d'acceder à mes mail et aux archives que je sois sous W2K ou sous Debian ( Sous W2K, j'utilise Eudora ). Imaginons, une partitions FAT32 accessible en rw sous 2 les OS où je retrouverais tout mes mails. Est-ce inconcevable ou existe-t-il une formule magique ? Bien entendus, si il le faut, je suis prêt à quitter mon bon Eudora pour une application multi plateforme J'ai fait ça dans le temps ou j'avais windows sur mon pc avec mozilla, ça marche trés bien. A l'époque, j'avais 1 win 2000, 1 XP, 1 mdk et 1 debian et tous sous mozilla pour lire les mails pointant vers le meme repertoire, maintenant, j'ai plus que debian... Le truc c'est que j'ai du bidouiller un peu à la main le fichier prefs.js pour l'histoir des chemins (à cause du repertoire genre htrkwkg.slt générere aléatoirement lors de la création du login), ça prend un peu de temps à mettre en place mais ça marche bien. ce qu'il faut garder à l'esprit, c'est que mozilla doit avoir un fichier perfs.js différent pour windows et pour linux. Merci. de rien kamel latrach yoann _ Envie de discuter en live avec vos amis ? Télécharger MSN Messenger http://www.ifrance.com/_reloc/m la 1ère messagerie instantanée de France
please help! multi-boot problem, i think
I was running windows me, used partition magic to partition linux partitions, then installed debian 3. Unwisely, I let it boot from the mbr. Now windows won't load at all, saying system files are missing or corrupt. lilo.conf looks like this for where windows should be: other=/dev/hda2 label=Other(hda2) It also says that Windows is at hda6, which can't be right (and doesn't even give me the error messages I get when trying to boot from hda2). When I boot from a windows me startup disk, c: is my data partition, but before installing debian, c: was naturally my windows partition. Now I'm stuck, b/c not only am I unfamiliar with Linux, I have installed only the minimal web-installer distribution of debian. Please help if you have any ideas. Thank you! _ MSN 8 helps eliminate e-mail viruses. Get 2 months FREE*. http://join.msn.com/?page=features/virus -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: please help! multi-boot problem, i think
Wesley Harris said: I was running windows me, used partition magic to partition linux partitions, then installed debian 3. Unwisely, I let it boot from the mbr. Now windows won't load at all, saying system files are missing or corrupt. more info is needed: fdisk -l /dev/hda mount each of the win32 partitions and show output of ls of them e.g. if win9x is on /dev/hda2 then mkdir /mnt/c ; mount /dev/hda2 /mnt/c -t vfat same for any other win32 partitions, mount them on different mount points. sounds like you may of wiped out the wrong partition? not sure without more info. nate -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Multi-boot
Bonjour, Est il possible d'installe une debian en multi boot avec un systeme windows (dsl) ? si oui est ce que c est comme pour une autre distri et auriez des conseils ou astuces? Merci Cedric
Re: Multi-boot
- Original Message - From: Cédric BUSCHINI [EMAIL PROTECTED] To: debian-user-french@lists.debian.org Sent: Friday, November 08, 2002 7:34 PM Subject: Multi-boot Bonjour, Est il possible d'installe une debian en multi boot avec un systeme windows (dsl) ? oui c possible (meme pour moi un debutant de chez debutant) si oui est ce que c est comme pour une autre distri et auriez des conseils ou astuces? je ne connais que Debian. Fait une defragmentation du disque fat32 et une sauvegarde de tes documents avant (crois moi ca sert...). moi j ai partionner le disque (au format ext2) avant l'installation. Pis apres y faut de la patience et beaucoup de lecture. Merci Cedric Eric Becquet
Re: Multi-boot
On Fri, 8 Nov 2002 19:34:50 +0100 Cédric BUSCHINI [EMAIL PROTECTED] wrote: salut pour faire cela j'utilise XOSL qui est de plus gratuit tu peux le trouver sur telecharger.com l'installation se passe sous dos avec la commande install une foi installer il se lance au demarrage tu n'as plus qu'a lui dire quel partition il doit booter il est aussi capable de booter les CD et Disquette personelement je te le recommande ( simple, interface graphique simpas ) lilo est aussi capable de fair les multiboot mais je trouve que c est moin pratique si tu as un problem avec xosl n'hesite pas a m'envoyer un mail Bonjour, Est il possible d'installe une debian en multi boot avec un systeme windows (dsl) ? si oui est ce que c est comme pour une autre distri et auriez des conseils ou astuces? Merci Cedric
Re: Multi-boot
On Fri, 2002-11-08 at 19:34, Cédric BUSCHINI wrote: Bonjour, Est il possible d'installe une debian en multi boot avec un systeme windows (dsl) ? oui bien sur que c'est possible. si oui est ce que c est comme pour une autre distri et auriez des conseils ou astuces? tu peux utiliser lilo pour le faire. je te joins mon fichier de config de lilo comme exemple. apres l'avoir modifier il faut _toujours_ relancer lilo en root. sinon tes modifications ne sont pas prises en compte. Merci Cedric -- - Guillaume Membré - Elève ingénieur à l'école des Mines de Nantes - France - Web site : http://collection.photo.free.fr/ # /etc/lilo.conf - See: `lilo(8)' and `lilo.conf(5)', # --- `install-mbr(8)', `/usr/share/doc/lilo/', # and `/usr/share/doc/mbr/'. # +---+ # |!! Reminder !! | # | | # | Don't forget to run `lilo' after you make changes to this | # | conffile, `/boot/bootmess.txt', or install a new kernel. The | # | computer will most likely fail to boot if a kernel-image | # | post-install script or you don't remember to run `lilo'. | # | | # +---+ # Support LBA for large hard disks. # lba32 # Overrides the default mapping between harddisk names and the BIOS' # harddisk order. Use with caution. #disk=/dev/hde #bios=0x81 #disk=/dev/sda #bios=0x80 # Specifies the boot device. This is where Lilo installs its boot # block. It can be either a partition, or the raw device, in which # case it installs in the MBR, and will overwrite the current MBR. # boot=/dev/hda # Specifies the device that should be mounted as root. (`/') # root=/dev/hda5 # Enable map compaction: # Tries to merge read requests for adjacent sectors into a single # read request. This drastically reduces load time and keeps the # map smaller. Using `compact' is especially recommended when # booting from a floppy disk. It is disabled here by default # because it doesn't always work. # # compact # Installs the specified file as the new boot sector # You have the choice between: bmp, compat, menu and text # Look in /boot/ and in lilo.conf(5) manpage for details # install=/boot/boot-menu.b # Specifies the location of the map file # map=/boot/map # You can set a password here, and uncomment the `restricted' lines # in the image definitions below to make it so that a password must # be typed to boot anything but a default configuration. If a # command line is given, other than one specified by an `append' # statement in `lilo.conf', the password will be required, but a # standard default boot will not require one. # # This will, for instance, prevent anyone with access to the # console from booting with something like `Linux init=/bin/sh', # and thus becoming `root' without proper authorization. # # Note that if you really need this type of security, you will # likely also want to use `install-mbr' to reconfigure the MBR # program, as well as set up your BIOS to disallow booting from # removable disk or CD-ROM, then put a password on getting into the # BIOS configuration as well. Please RTFM `install-mbr(8)'. # # password=tatercounter2000 # Specifies the number of deciseconds (0.1 seconds) LILO should # wait before booting the first image. # delay=20 # You can put a customized boot message up if you like. If you use # `prompt', and this computer may need to reboot unattended, you # must specify a `timeout', or it will sit there forever waiting # for a keypress. `single-key' goes with the `alias' lines in the # `image' configurations below. eg: You can press `1' to boot # `Linux', `2' to boot `LinuxOLD', if you uncomment the `alias'. # # message=/boot/bootmess.txt # prompt # single-key # delay=100 # timeout=100 append=mem=nopentium # Specifies the VGA text mode at boot time. (normal, extended, ask, mode) # # vga=ask # vga=9 # vga=9 # Kernel command line options that apply to all installed images go # here. See: The `boot-prompt-HOWO' and `kernel-parameters.txt' in # the Linux kernel `Documentation' directory. # # append= # Boot up Linux by default. # default=Linux2.4.19 image=/boot/bossa2.4/vmlinuz-2.4.18-bossa label=bossa read-only image=/boot/vmlinuz-2.4.19 label=Linux2.4.19 read-only image=/boot/vmlinuz-2.2.20 label=Linux2.2.20 read-only # restricted # alias=1 image=/boot/vmlinuz.old label=LinuxOLD read-only optional # restricted # alias=2 # If you have another OS on this machine to boot, you can uncomment the # following lines, changing the device name on the `other' line to # where your other OS' partition is. # # other=/dev/hda4 # label=HURD
setting up multi boot system
Hello I've never run any kind of other operating system besides windows and I was considering setting up debian on one of my workstations at the office since its the only place I have computer and internet access. I still need to keep windows and absolutely under no circumstances can I have one of these machines out of order. It'll be my job. So my question is, is it realistic to partition my drive and set up debian and what not and still expect to be able to use windows even if something weird is going on with debian? I would think that you would get an option on which drive to boot from before either operating system is being used right? Probably a stupid question but I couldn't find an answer anywhere else. Kindest Regards -David Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com
Re: setting up multi boot system
David Dodson wrote: Hello I've never run any kind of other operating system besides windows and I was considering setting up debian on one of my workstations at the office since its the only place I have computer and internet access. I still need to keep windows and absolutely under no circumstances can I have one of these machines out of order. It'll be my job. So my question is, is it realistic to partition my drive and set up debian and what not and still expect to be able to use windows even if something weird is going on with debian? I would think that you would get an option on which drive to boot from before either operating system is being used right? Probably a stupid question but I couldn't find an answer anywhere else. Kindest Regards -David It sounds like you will have Debian on one drive and Windows on another. You can use 'lilo' to boot one or the other. There shouldn't be any trouble with one OS messing with the other in this circumstance. During the initial installation you might want to unplug your HD with Windows on it just to make sure no mistakes are made and you partition that drive accidentally. One other thing you might consider is vmware. I've never used it but from what I understand if you have enough memory it works pretty well. You can install vmware on either windows or linux and then run other operating systems from within that operating system so you don't have to reboot each time to switch. hth, kent
Re: setting up multi boot system
I have set up several dual-boot systems (linux-windows3.1, linux-NT, and linux-w98). If you have partition magic, I have had success shrinking the vfat partition and creating linux partitions. However, if the linux partition is far from the master boot-block, then you will, I think, need to use a boot-floppy that points to the linux partition. There is an option for this during the Debian install. The same is true if you choose to put linux on a separate disk. Understand that you cannot run the two OS's simultanesously without something like vm-ware. Arthur H. Edwards 712 Valencia Dr. NE Abq. NM 87108 (505) 256-0834 On Mon, 12 Jun 2000, David Dodson wrote: Hello I've never run any kind of other operating system besides windows and I was considering setting up debian on one of my workstations at the office since its the only place I have computer and internet access. I still need to keep windows and absolutely under no circumstances can I have one of these machines out of order. It'll be my job. So my question is, is it realistic to partition my drive and set up debian and what not and still expect to be able to use windows even if something weird is going on with debian? I would think that you would get an option on which drive to boot from before either operating system is being used right? Probably a stupid question but I couldn't find an answer anywhere else. Kindest Regards -David Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null
