Re: how to tell where it booted from

2016-02-18 Thread Andrew R Paterson
On Friday 19 Feb 2016 06:41:04 Tim wrote: > Allegedly, on or about 17 February 2016, g sent: > > gone are the 'good old days' of boxes 4 and 5 5" drive bays where one > > could install install 3" drives in removable drive carriers and swap > > drives. > > Yet computer cases are still ridiculously

Re: how to tell where it booted from

2016-02-18 Thread Tim
Allegedly, on or about 17 February 2016, g sent: > gone are the 'good old days' of boxes 4 and 5 5" drive bays where one > could install install 3" drives in removable drive carriers and swap > drives. Yet computer cases are still ridiculously huge... Most PC cases that I see on sale tend to be

Re: how to tell where it booted from

2016-02-17 Thread g
time to reminisce. On 02/17/16 22:11, Tim wrote: > Tim: >>> Once you sort this out, you want to plan how you do multiboots in the >>> future. Way back when I tried it, and even two is a pain, one good >>> solution was to make your own custom boot partition, and all it did was >>> let you select

Re: how to tell where it booted from

2016-02-17 Thread Tim
Tim: >> Once you sort this out, you want to plan how you do multiboots in the >> future. Way back when I tried it, and even two is a pain, one good >> solution was to make your own custom boot partition, and all it did was >> let you select which partition to boot, it chainloaded the next one. Mi

Re: how to tell where it booted from

2016-02-17 Thread Lester M Petrie
On Wednesday, February 17, 2016 10:03:04 AM Rick Stevens wrote: > On 02/16/2016 09:19 PM, Mike Wright wrote: > > On 02/16/2016 08:15 AM, Chris Murphy wrote: > >> At the GRUB menu, type > >> > >> pager=1 > >> set > >> > >> Look for variable 'prefix=' this will be drive, partition, and path, to > >

Re: how to tell where it booted from

2016-02-17 Thread Rick Stevens
On 02/16/2016 09:19 PM, Mike Wright wrote: On 02/16/2016 08:15 AM, Chris Murphy wrote: At the GRUB menu, type pager=1 set Look for variable 'prefix=' this will be drive, partition, and path, to the GRUB directory where its cfg and modules are found. All right Chris! While at the boot prompt

Re: how to tell where it booted from

2016-02-17 Thread Tim
On Tue, 2016-02-16 at 21:19 -0800, Mike Wright wrote: > Is there a command that will take my simplified grub.cfg and install > it without modifying it in any way and leave me with a bootable > system? (please please please say yes). I seem to recall that although GRUB no-longer uses a flat menu fi

Re: how to tell where it booted from

2016-02-16 Thread Mike Wright
On 02/16/2016 08:33 AM, Tim wrote: Allegedly, on or about 15 February 2016, Mike Wright sent: I have several large disks filled with experiments and multiboots... Once you sort this out, you want to plan how you do multiboots in the future. Way back when I tried it, and even two is a pain, on

Re: how to tell where it booted from

2016-02-16 Thread Mike Wright
On 02/16/2016 08:15 AM, Chris Murphy wrote: At the GRUB menu, type pager=1 set Look for variable 'prefix=' this will be drive, partition, and path, to the GRUB directory where its cfg and modules are found. All right Chris! While at the boot prompt I have no access to anything and had forgot

Re: how to tell where it booted from

2016-02-16 Thread g
On 02/16/16 08:29, Robert Nichols wrote: <<>> > In GRUB legacy, if you get the boot menu displayed, type "c" to get a > "grub>" command prompt, then you can enter the command "root" and > see which BIOS drive and partition is being used. > . good to know. thanks for posting. was aware of using

Re: how to tell where it booted from

2016-02-16 Thread Tim
Allegedly, on or about 15 February 2016, Mike Wright sent: > I have several large disks filled with experiments and multiboots... Once you sort this out, you want to plan how you do multiboots in the future. Way back when I tried it, and even two is a pain, one good solution was to make your own

Re: how to tell where it booted from

2016-02-16 Thread Chris Murphy
At the GRUB menu, type pager=1 set Look for variable 'prefix=' this will be drive, partition, and path, to the GRUB directory where its cfg and modules are found. Chris Murphy -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedor

Re: how to tell where it booted from

2016-02-16 Thread Robert Nichols
On 02/15/2016 05:42 PM, Mike Wright wrote: Hi everybody, I have several large disks filled with experiments and multiboots. I need to make changes to the current /boot/grub/grub.cfg but I have no idea which one I'm using or which one of the systems' grub config tools were used so I don't dare j

Re: how to tell where it booted from

2016-02-16 Thread g
On 02/15/16 17:42, Mike Wright wrote: <> Hi everybody, > > I have several large disks filled with experiments and multiboots. I > need to make changes to the current /boot/grub/grub.cfg but I have no > idea which one I'm using or which one of the systems' grub config tools > were used so I

Re: how to tell where it booted from

2016-02-15 Thread Tim
Allegedly, on or about 15 February 2016, Mike Wright sent: > I have several large disks filled with experiments and multiboots. I > need to make changes to the current /boot/grub/grub.cfg but I have no > idea which one I'm using or which one of the systems' grub config > tools were used so I don

Re: how to tell where it booted from

2016-02-15 Thread Mike Wright
On 02/15/2016 04:21 PM, Rick Stevens wrote: On 02/15/2016 03:42 PM, Mike Wright wrote: Does the boot process leave any footprints behind telling where it booted from? So you can see my boot partition is a plain-old partition on /dev/sda1 and the root filesystem (block device 253:1) is a Linux

Re: how to tell where it booted from

2016-02-15 Thread Mike Wright
On 02/15/2016 04:21 PM, Rick Stevens wrote: On 02/15/2016 03:42 PM, Mike Wright wrote: Does the boot process leave any footprints behind telling where it booted from? You can always "cat /proc/cmdline" to see what the boot command line was. In my case: [root@prophead ~]# cat /proc/cmdli

Re: how to tell where it booted from

2016-02-15 Thread Mike Wright
On 02/15/2016 04:10 PM, doug wrote: On 02/15/2016 06:42 PM, Mike Wright wrote: Does the boot process leave any footprints behind telling where it booted from? Don't know if you have legacy grub or not. With legacy grub, you can change the names in menu.lst--put a 1 or 2 or whatever after the d

Re: how to tell where it booted from

2016-02-15 Thread Rick Stevens
On 02/15/2016 03:42 PM, Mike Wright wrote: Hi everybody, I have several large disks filled with experiments and multiboots. I need to make changes to the current /boot/grub/grub.cfg but I have no idea which one I'm using or which one of the systems' grub config tools were used so I don't dare j

Re: how to tell where it booted from

2016-02-15 Thread doug
On 02/15/2016 06:42 PM, Mike Wright wrote: Hi everybody, I have several large disks filled with experiments and multiboots. I need to make changes to the current /boot/grub/grub.cfg but I have no idea which one I'm using or which one of the systems' grub config tools were used so I don't da

how to tell where it booted from

2016-02-15 Thread Mike Wright
Hi everybody, I have several large disks filled with experiments and multiboots. I need to make changes to the current /boot/grub/grub.cfg but I have no idea which one I'm using or which one of the systems' grub config tools were used so I don't dare just grab any old one and use it I've se