
For now, I'd heartily recommend masking baselayout-2 and OpenRC. I am still ironing out the bugs that came with that "upgrade". I got lucky with my 64 bit system since it only uses one network interface. However, my laptops need to be able to rename their net interfaces, and that ain't happening with this new setup. For the time being, I have things functional on two out of three systems. I am debating whether I should go for an update on the third, or whether I should leave it until the bigger kinks are removed from this system. I am leaning towards not.monsm wrote:Good stuff.
I was thinking about this after seeing that post on the Gentoo front page. I was thinking maybe its an idea to put in my own mask into my /etc/portage/package.mask file in order to avoid surprises. Then remove the mask again when I am ready to update that part.
I'll probably just try to remember it when I run world updates next time, in few weeks.




I reboot my deskside when I update the kernel. Other than that, it's here when I need it, and increasing its uptime when I'm not. I'm pretty much completely uninterested in the boot time on this machine.pappy_mcfae wrote:The speed with which my computer boots is immaterial to me.y

I'm not sure. I looked at it, and when I didn't find the ability to rename my interfaces, I decided it wasn't for me. Part of the problem for me is for some reason, my auto-networking script just stopped working. Gone...history...no more. Untying the knots was a total P.I.T.A. Perhaps I'll give it a go when they get the bigger bugs out. For now, as I said before, color me unimpressed.depontius wrote:I reboot my deskside when I update the kernel. Other than that, it's here when I need it, and increasing its uptime when I'm not. I'm pretty much completely uninterested in the boot time on this machine.pappy_mcfae wrote:The speed with which my computer boots is immaterial to me.y
My laptop, on the other hand, is a different case. I'd like to see faster boots there. But of course it also has 2 network (wired and wireless) interfaces, so I may bump into the problems others have had. I also have my own post-networking script that makes extensive changes, including runlevel, ( runlevels for home, work, nonetwork, travel, etc ) based on the issued IP address. That sounds like it may need rework.
Does the new /etc/conf.d/net.example show how to add an extra static route, like the old one did?
Given the warning, I think I'll have /etc backed up before starting this. I have a spare machine that I may try the baselayout-2 on this weekend, just to get a feel.pappy_mcfae wrote:my auto-networking script just stopped working. Gone...history...no more. Untying the knots was a total P.I.T.A. Perhaps I'll give it a go when they get the bigger bugs out. For now, as I said before, color me unimpressed.
And like you, curiously, the only machine that took the upgrade without completely falling to pieces was the machine I hardly ever reboot. Hmm.
Blessed be!
Pappy

That would be an incredibly wise thing. Unfortunately for me, I updated two machines at once, not realizing what was going to happen. That was a mistake.depontius wrote:Given the warning, I think I'll have /etc backed up before starting this. I have a spare machine that I may try the baselayout-2 on this weekend, just to get a feel.

I know. I edited said file so my wired adapter starts life as wth0. My wireless naturally starts life as wlan0. Then, I have a script that looks for carrier on the wired adapter. If it is found, wth0 is then renamed to eth0. If not, then wlan0 is renamed to eth0. It works flawlessly. And, it works the way *I* want it to.cyrillic wrote:Maybe you just didn't know where to look.pappy_mcfae wrote:I looked at it, and when I didn't find the ability to rename my interfaces, I decided it wasn't for me.
Renaming interfaces can be done easily by editing /etc/udev/rules.d/70-persistent-net.rules
In the following line:tsuehpsyde wrote:Well, I'm trying to get this working on my test box, but it's dying.Perhaps I can get some help? On reboot, I'm getting the following message:
Root-NFS: No NFS server available, giving up.
VFS: Unable to mount root fs via NFS, trying floppy.
VFS: Insert root floppy and press ENTER
VFS: Cannot open root device "sda3(then a bunch of weird symbols for almost a full line, like half an H)" or unknown-block(2,0)
Please append a correct "root=" boot option; here are the available partitions:
0800 160836480 sda driver: sd
0801 136521 sda1
0802 3911827 sda2
0803 156786367 sda3
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(2,0)
And here is my menu.lst in grub:
default 0
timeout 1
title=Gentoo 2.6.24-gentoo-r4
root (hd0,0)
kernel /boot/bzImage root=/dev/sda3
Any ideas?I haven't changed anything in grub, so I'm not sure why this migration to OpenRC started this mess, heh.
Code: Select all
kernel /boot/bzImage root=/dev/sda3