On Mon, Jun 27, 2011 at 9:09 AM, Mark Knecht <[email protected]> wrote:
<SNIP>
> As a follow-up to your problems, and because I'm just plain interested
> in this /dev/null,console question, I decided to create a completely
> new Gentoo VM myself from scratch this morning. I'm going FAR more
> slowly than usual as, like you, I need to get other things done. Also
> that I'd like to understand what the tarball does actually provide,
> and also when everything in /dev really comes together correctly. (If
> indeed it does come together correctly.)
>
> I'll post back how it's going. My first observation is that the stage3
> tarball only provides /dev/null as a normal file and nothing else. I
> would guess that this is incorrect as I would think that if the normal
> file is there then the special file won't get created later. I've
> never studied how the /dev directory gets created so this will be a
> learning experience for me.
>
> As for having to get some work done, I completely understand. Just
> don't give up on us here in Gentoo land, be we real OR virtual...
>
> Cheers,
> Mark
>
Harry,
I got a few minutes this morning to finish the new Virtualbox VM
test install of Gentoo. It worked fine for me.
If you need any info about this let me know. Here's the main
points, the biggest being the use of DEVTMPFS in the kernel.
If you want the actual kernel config file get in touch off list.
Cheers,
Mark
Notes:
1) I chose the PCNET-OCI II NIC and set it as bridged. 4 processors, 2GB memory
2) /etc/fstab:
tux-test ~ # cat /etc/fstab
/dev/sda1 /boot ext2 noauto,noatime 1 2
/dev/sda3 / ext3 noatime 0 1
/dev/sda2 none swap sw 0 0
/dev/cdrom /mnt/cdrom auto noauto,ro 0 0
tux-test ~ #
3) I added DEVTMPFS to the kernel config to get around the missing
/dev stuff in the current tarballs:
tux-test ~ # cat /usr/src/linux/.config | grep CONFIG_DEVTMPFS
CONFIG_DEVTMPFS=y
CONFIG_DEVTMPFS_MOUNT=y
tux-test ~ #
4) Interestingly, it boots even though I didn't add udev to sysinit:
tux-test ~ # rc-update show | sort
fsck | boot
mtab | boot
root | boot
sshd | default
swap | boot
devfs | sysinit
dmesg | sysinit
local | default
net.lo | boot
procfs | boot
sysctl | boot
hwclock | boot
keymaps | boot
modules | boot
urandom | boot
bootmisc | boot
hostname | boot
mount-ro | shutdown
net.eth0 | default
netmount | default
killprocs | shutdown
savecache | shutdown
syslog-ng | default
localmount | boot
vixie-cron | default
termencoding | boot
udev-postmount | default
tux-test ~ #
5) World file:
tux-test ~ # cat /var/lib/portage/world
app-admin/logrotate
app-admin/syslog-ng
app-portage/eix
sys-apps/mlocate
sys-apps/pciutils
sys-boot/grub-static
sys-kernel/gentoo-sources
sys-process/vixie-cron
tux-test ~ #
6) /etc/make.conf file which I stole from another machine. Some USE
flags do not make sense in this context but they didn't hurt the
build.
tux-test ~ # cat /etc/make.conf
CFLAGS="-O2 -march=native -pipe"
CXXFLAGS="${CFLAGS}"
CHOST="x86_64-pc-linux-gnu"
USE="gstreamer jpeg2k ssse3 vdpau xvmc -bluetooth -cups -ipv6"
MAKEOPTS="-j9"
GENTOO_MIRRORS="http://gentoo.osuosl.org/ "
SYNC="rsync://rsync.namerica.gentoo.org/gentoo-portage"
EMERGE_DEFAULT_OPTS="--with-bdeps y"
INPUT_DEVICES="evdev"
VIDEO_CARDS="virtualbox"
ALSA_CARDS="hda-intel"
LINGUAS="en"
ACCEPT_LICENSE="dlj-1.1 PUEL AdobeFlash-10.1 skype-eula"
tux-test ~ #
