2016-06-30 8:44 GMT+02:00 akhiezer <[email protected]>: > > Top-posting for summary of current/latest understanding here: > -- > * you used a debian to build lfs. > > * I had assumed that the debian that was used to build lfs, was therefore > the bare-metal OS on the computer. (That's mainly why 'the penny was > slow to drop' here, that both the debian that was used to build lfs, > and the lfs, really _are_ on virtual disks - despite your statement > stating that they were, plus the fdisk/&c outputs.) > > * Therefore the question here now is - cf too Paul's note ~today on > the thread: > - the computer that you've got debian/lfs work-area setup on: > ** what is the bare-metal OS on that computer? > ** ie, when you powered-on the computer immediately- pre- any > work on lfs, what is the OS that is booted into: is it the > debian that you used to build lfs, or another debian, or > another linux (installed on disk), or linux live-cd, or > windows, or what? > -- > > My bare metal os is osx yosemite.
> > > From: thibaut noah <[email protected]> > > Date: Thu, 30 Jun 2016 01:31:37 +0200 > > Subject: Re: [lfs-support] Grub failed me, my boot has sink > > > . > . > > > [Ken]: > > > > you mean virtualbox right? i don't use qemu for this, virtualbox only see > > the disk i give to it so yes one disk. > > > > > And, nost importantly - what happens ? "Does not boot" tells us > > > nothing. Does grub report any error ? > > > > What i mean is virtualbox doesn't find anything to boot on, so no grub no > > anything, i don't have the exact message because i'm home > > but it's something like "no boot device detected" > > > . > . > > > > > > 2016-06-29 14:22 GMT+02:00 akhiezer <[email protected]>: > > > > > > From this and what you say in other parts of the thread: > > > == > > > * you have got only one _physical_ disk; is that correct? > > > > > > > Not at all, i don't have ANY Physical disk, i have two virtual disks > (said > > it earlier) and what i do is creating another virtual machine with just > the > > virtual drive of lfs > > > OK, understood now; cf top-post summary, above. > > > > and i want to boot like this. > > > > > * you want to boot directly from power-on thru bios/uefi, directly into > > > lfs; is that correct? > > > > yes > > > > > Apols if am being dumb, but your two statements there, seem to be > contradictory: > -- > * 'and i want to boot like this': > - machine powers-on, > - goes thru bios/uefi, > - starts _an OS_ (ref top-posted summary, above: which OS is that), > - then that os starts virtualbox, > - then you use that virtualbox to run the lfs instance. > > * "you want to boot directly ...?" + 'yes': > - machine powers-on, > - goes thru bios/uefi, > - hits grub/&c screen (no 'a.n.other os'/virtualbox/&c), > - boot lfs directly to lfs login prompt (again, 'a.n.other os'/ > virtualbox/&c). > -- > > > I was under the assumption it was clear that i was talking about virtualbox only all along. Thus by saying booting directly i meant that i wanted virtualbox to boot with lfs only. > > > == > > > > > > Assuming 'yes' to both questions, then very likely: > > > -- > > > * said bios/uefi will see the single disk as sda . > > > > > > > > I verified this by booting with the arch-live iso, disk is indeed seen as > > sda. > > > > > > > * said grub will need to know what are the _real_ partitions on sda > that > > > '/' and '/boot' are on. > > > -- > > > > > > > > > > > Will run your command as soon as i arrive to work thanks. > > > The info is less-needed, if at all, if you really are wanting to > run/boot-into lfs only via virtualbox: I had gotten onto the 'booting > lfs as bare-metal os' track; whereas Bruce/Ken/&c posts deal with the > virtualbox route. > > > If still relevant: > == > * *NB* that you'd want to run the commands from the bare-metal OS on > the computer: that was the intent, while I was mistakenly thinking > that 'the debian used to build lfs' was the bare-metal os. > > * may also be useful to run: > parted /dev/sda print unit s print unit chs print > parted /dev/sdb print unit s print unit chs print > > * If the bare-metal os is non-linux, then I guess run the commands > from e.g. a linux live-cd that you have booted the _computer_ from; > don't run them from within virtualbox &c. > == > > > > > . > . > > > In any case: where on the single _physical_ disk, do those sdb{1,2,3} > > > partitions live? You need to be able to say/know, effectively: 'sdb1' > > > is 'really' 'sdaN', for some number 'N'; and similarly for 'sdb2' & > > > 'sdb3' . > > > > > There is no physical disk. > > > > > (There is, but just not (IIUIC now) in this context - ref 'penny dropped' > note in top-post, above.) > > > > rgds, > akh > > > > > > -- > -- > http://lists.linuxfromscratch.org/listinfo/lfs-support > FAQ: http://www.linuxfromscratch.org/blfs/faq.html > Unsubscribe: See the above information page > > Do not top post on this list. > > A: Because it messes up the order in which people normally read text. > Q: Why is top-posting such a bad thing? > A: Top-posting. > Q: What is the most annoying thing in e-mail? > > http://en.wikipedia.org/wiki/Posting_style >
-- http://lists.linuxfromscratch.org/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page Do not top post on this list. A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? http://en.wikipedia.org/wiki/Posting_style
