On Tue, May 1, 2012 at 6:02 PM, Michael Mol <[email protected]> wrote: > On Tue, May 1, 2012 at 8:51 PM, Mark Knecht <[email protected]> wrote: >> On Tue, May 1, 2012 at 5:42 PM, Michael Mol <[email protected]> wrote: >>> On Tue, May 1, 2012 at 7:54 PM, Mark Knecht <[email protected]> wrote: > > [snip] > >>>> Maybe a 32-bit Gentoo chroot that doesn't maintain any desktop or X11, >>>> etc. could work? If I could convert the files at the command line >>>> using ffmpeg in 32-bit then that would be pretty manageable in terms >>>> of Gentoo work, assuming the ffmpeg package can be built as without >>>> any GUI stuff? >>> >>> I was just thinking that. I played with a chroot briefly just before >>> inara and kaylee bit it, and it seemed pretty trivial. Were it me, >>> that'd be the next thing I'd try. (But then, compiling is cheap for >>> me) >>> >> >> I think I'll try it in a Virtualbox VM first I instead of a chroot. >> That's pretty easy to deal with. Easy to back up. Easy to move to a >> different system down the road. No disk partitions, etc.
Hi Michael, OK, the markets are _really_ boring this morning so while I'm waiting for grass to grow on my trading platform I did the 32-bit install in a Virtualbox VM. Booted up fine the first time. Only took about an hour to get it running, so not too bad. (Made easier by being able to look at config files on host. emerge -DuN @world ran in a few minutes and the machine is up-to-date so I can start looking at maybe ffmpeg or something as a 32-bit app. For anyone following this thread silently (or looking it up in some future search) the default settings in gentoo-sources-2.3.12 were fine. I changed the processor to a Core 2 setting, removed all the networking devices except for the default Intel devices which are built in (as that's what the Virtualbox network VM model seems to be built on) and built in ext3 & ext4 file systems. I used grub, not grub-static as I usually do and just followed the 32-bit install guide. Booted perfectly the first time. The only Vbox trick was to choose the bridged adapter, not the default NAT device. After I did that networking was up and I was off and running. Cheers, Mark
