openrc support thread

[phanboy_iv]

Just installed and tested, and it works perfectly here.
I'm really rather suprised that an upgrade to such a core system was so painless.
Thanks go out to Roy and the Gentoo baselayout ninjas!

[energyman76b]

ah, my fsck bug is known since october - and 'fixed'.

Well, it is not. And I don't think that patching around in the reiser4 fsck instead of changing the init-script is the right way.

Btw, is there a DOWNGRADE guide for people fed up with b2/openrc?

[coogy]

Easy upgrade,everything smooth bar some host name weridness. Prior to upgrade i'm seanx@tux following i'm seanx@unknown00065b8467a8
(the alphanumerical bit is the mac address of my eth0).

What sets it.

[uzz75]

I have only little problem with /etc/conf.d/cryptfs

swap=crypt_swap
source='/dev/sda4'


not working.

it's not important because i don't need swap...

[uzz75]

where's found ebegin eend einfo .. ?

they was nice for myself script...

[UberLord]

After reading the migration guide, I wonder what is the reason behind decision to encode names and versions into parameter names. E.g:

Code: Select all

# For 2.6.23-gentoo-r5, pass video_br=2 to cx88_dvb
module_cx88_dvb_args_2_6_23_gentoo_r5="video_br=2"
# For 2.6.x series kernels, always pass vendor and product
module_usbserial_args_2_6="vendor=0x1410 product=0x2110"
# Always pass debug to ieee1394
module_ieee1394_args="debug" 

I see module name mixed with uname (where some characters like dots and hyphen are converted to underscore).
Why not use some hierarchical structure (like INI file) instead?

All files in /etc/conf.d/ have to be shell parseable. The .INI style is not.

Also I believe the module name and its (optional) parameters should not be divided into two lexically separated information. Either I give the module (and eve2ntually its parameters) or I do not. Or is it foreseen that it will be possible to provide parameters for modules, without explicitly specifying the modules?2

It's easiest to do it like it is, otherwise we would have to use something like bash arrays, which is now a big no no for OpenRC scripts which should work on any POSIX shell.

[UberLord]

the migration guiide needs an update:
>It is critical that you run dispatch-conf and ensure your /etc is up to date before rebooting.

oh really? I never had that installed or planned to install it - and I am pretty sure that my system won't need it in the future. Or is dispatch.conf a base tool now?

It should mention etc-update, file a bug about that.

[UberLord]

I am completly underwhelmed.

No, I am pissed.

fsck crashs out on boot - and then nothing goes, because it can not check some fs. WTF? ok, /fastboot works around it, but it is completly and absolutly fucked up.

I'm pissed that people say thing are broken without saying how!
Post the exact error message, and maybe a little context and I can try to fix it so much better.

what is wrong with this fstab - except that the old baselout worked flawlessly with it?

Nothing looks wrong, but then I don't have any reiser(fs/4) partitions to play around with myself.
The chances are it's an issue with the -p parameter we pass to fsck, which both sets of reiser fsck helpers treat differently.
But without the magically error message it's purely a guess.

Second thing that REALLY pissed me of was the removal of the net stuff - ok. I was warned, but still.

You would rather you were not warned?

Boot is not faster than before - no it is slower, same like reboot/shutdown.

You're the first of many who said it's slower. Probably because of the fsck error.

And where can I tell the new baselayout/openrc stuff to NOT load modules except the ones explecitly told so?

As the guide said, check that /etc/rc.conf and /etc/conf.d/modules is to your liking.
I would pay close attention to rc_coldplug as well.

oh and this:
fancontrol [ crashed ]

File a bug and a Gentoo dev will fix the init script so it works with the stricter start-stop-daemon call.

Love it! Not!

That doesn't get bugs fixed faster.

[UberLord]

ah, my fsck bug is known since october - and 'fixed'.

Well, it is not. And I don't think that patching around in the reiser4 fsck instead of changing the init-script is the right way.

So you would rather have complicated shell code to special case reiser than patch the reiser fsck helpers to understand the -p flag which all other fsck helpers in portage do? I think not

Btw, is there a DOWNGRADE guide for people fed up with b2/openrc?

echo "sys-apps/openrc" >> /etc/portage/package.mask
echo ">=sys-apps/baeselayout-2.0.0" >> /etc/portage/package.mask
emerge -U world

[darkphader]

Problems I had with the upgrade:

• current /etc/conf.d/net file gets deleted
  • if it's suspected to not work as is it should be backed up
• txqueuelen is not getting set (I'm using iproute2)
  • "ip link set eth0 txqueuelen 10000" works fine from terminal

Other than that it seems to be working.

Chris

[slackline]

Btw, is there a DOWNGRADE guide for people fed up with b2/openrc?

No guide, but can you not just restore your /etc/init.d/ files and other things from backup (either explicit of your own, or that created by the update tool you have been using, i.e. not dispatch-conf).

Overall it would basically be reversing everything thats in the OpenRC Migration guide.

Then mask the packages in /etc/portage/package.mask.

I had a few problems with /etc/init.d/net and /etc/conf.d/net but have solved them (see thread and bug), and the migration guide has been duly updated as a consequence (see comments in the bug).

Remember that these are still marked as unstable (ARCH="~x86" etc.) you shouldn't be surprised if things don't work perfectly, so no point in getting too irate

[energyman76b]

I am completly underwhelmed.

No, I am pissed.

fsck crashs out on boot - and then nothing goes, because it can not check some fs. WTF? ok, /fastboot works around it, but it is completly and absolutly fucked up.

I'm pissed that people say thing are broken without saying how!
Post the exact error message, and maybe a little context and I can try to fix it so much better.

Something like 'can not check some filesystem' and then fsck terminates and after that every other init script is terminated.
See:
http://bugs.gentoo.org/show_bug.cgi?id=195988
http://bugs.gentoo.org/show_bug.cgi?id=199091

And I really think that patching reiser4progs is the exact wrong solution. Instead fsck should call the apropriate fsck.XYfs with the correct parameters.

what is wrong with this fstab - except that the old baselout worked flawlessly with it?

Nothing looks wrong, but then I don't have any reiser(fs/4) partitions to play around with myself.
The chances are it's an issue with the -p parameter we pass to fsck, which both sets of reiser fsck helpers treat differently.
But without the magically error message it's purely a guess.

Second thing that REALLY pissed me of was the removal of the net stuff - ok. I was warned, but still.

You would rather you were not warned?

no, I would have prefered to let the stuff in /etc/conf.d be untouched - or moved to some backup, instead of loosing it - with some 'history' and notes. Ever heard of the concept that 'user generated data' should not be touched?

Boot is not faster than before - no it is slower, same like reboot/shutdown.

You're the first of many who said it's slower. Probably because of the fsck error.

no, even with /fastboot it is slower. Partly because of aic7xxx being loaded.' Btw, rc.conf, do YES and NO have to be YES and NO or is Yes and No or yes and no correct too?

And where can I tell the new baselayout/openrc stuff to NOT load modules except the ones explecitly told so?

As the guide said, check that /etc/rc.conf and /etc/conf.d/modules is to your liking.
I would pay close attention to rc_coldplug as well.

ah yes, modules. Something went wrong with the converter-script:
modules_2_6="${modules_2_6} r8169"
module_r8169_args_2_6=""
#some commented stuff from the old file
#
#
modules_2_6="${modules_2_6} ehci-hcd"
module_ehci_hcd_args_2_6=""

shouldn't that be in one line? without the ${modules_2_6} stuff?

[paulbiz]

My /etc/init.d/net.* did not get deleted, but now it boots without waiting for network (wlan0) to come up, and services that depend on network never start even after I've got an IP from the DHCP server. In the old days it would connect to wireless, get IP, then run ntp and everything else that needs network. Am I doing something wrong? rc-status shows those other services with a "Scheduled" status, even though net.wlan0 has "Started" status. Even if I "zap" it and try to start, it tells me it is waiting for net.eth1 or net.eth2 (no mention of net.wlan0 after I've manually started it). How can I force it to know the network is now available? Is not net.wlan0 in "Started" status enough for it?

Also, these services have "Crashed" status:

Code: Select all

sensord
dictd
irqbalance
smartd

[pandaemonium]

Good job - the update worked almost without problems.

My first attempt resulted in a situation were rc-status segfaulted and no service was executed on boot at all,
but my second attempt of emerging openrc after a prior revdep-rebuild worked just fine.

[UberLord]

And I really think that patching reiser4progs is the exact wrong solution. Instead fsck should call the apropriate fsck.XYfs with the correct parameters.

Change fsck_args in /etc/conf.d/fsck then.
As to you're other errors, they are related to the Gentoo ebuild and I'm not a Gentoo dev.
But quite frankly I no longer give a flying fuck as you're just downright rude and moody.

[nuktrition]

The site says "OpenRC has many features. Here's a list of the key ones :-"

One of them are "It's fast - 29 seconds to boot my laptop running Gentoo/Linux"

Hmmm, my low end AMD 3000+ computer boots in 27 seconds... doesn't sound like
much of an improvement there.

Moving from a script based boot-up to large chunks of compiled C code?? The
beauty of scripts are that they can be modified on the fly to fix/change almost
anything.. kind'a hard to do that with compiled C code - with shell API or not.

I'm not so sure about this move to OpenRC, in my opinion it sounds like somebody
decided to fix something that didn't need it.

[Frustie]

Im not really sure im happy with this either

Ive read about openrc just yesterday and while updating my production system to update world (for clamav a.o), it kind of caught me by surprise, just noticed the update after it was done. Now im stuck with a system that requires a reboot while i have a replacement for the server sitting at home, on which ofcourse i would have wanted to test it first.

After reading about some issues with mainly the network cards/devices im really hesitant with all this rebooting, which means i will have to do this "hands-on" and more than likely prepare/bring the unfinished replacement too.

Anyway, you can call me a wuss if you want too

[slackline]

The site says "OpenRC has many features. Here's a list of the key ones :-"

One of them are "It's fast - 29 seconds to boot my laptop running Gentoo/Linux"

Hmmm, my low end AMD 3000+ computer boots in 27 seconds... doesn't sound like
much of an improvement there.

Are you attempting a comparison? Whats the spec of the laptop, is it similar to your low end AMD 3000+? What was the boot time on both of these systems prior to OpenRC?

I'm not so sure about this move to OpenRC, in my opinion it sounds like somebody
decided to fix something that didn't need it.

You could always mask it if you don't want to make the migration. But remember that at present its marked unstable, so if you do migrate don't throw your rattle out of the pram like energyman76b has done. Instead provide feedback in the forums/bugzilla to help resolve the problem.

[alistair]

and while updating my production system to update world

Ain't you brave. Your running an ~arch Production Server? You running emerge <anything> without checking what is going to happen first? Don't sound like a production system at all, more like a "non-production system".

[tejecske]

i am using ~x86 on production servers too. because i am focused on productivity instead on stability

[energyman76b]

And I really think that patching reiser4progs is the exact wrong solution. Instead fsck should call the apropriate fsck.XYfs with the correct parameters.

Change fsck_args in /etc/conf.d/fsck then.
As to you're other errors, they are related to the Gentoo ebuild and I'm not a Gentoo dev.
But quite frankly I no longer give a flying fuck as you're just downright rude and moody.

yes, I am moody. Wouldn't you moody too, if:
-boot blows up in your face
-you loose some config files that contained some important stuff
-there is a lack of documentation
and
all this trouble for no benefit?

[slackline]

yes, I am moody. Wouldn't you moody too, if:
-boot blows up in your face
-you loose some config files that contained some important stuff
-there is a lack of documentation
and
all this trouble for no benefit?

As I pointed out above, your running unstable if your using these (i.e. ARCH="~x86" or similar). Why are you therefore surprised that things aren't quite perfect? If thats what your after don't run unstable, its very simple.

All you've done (with one expcetion) is post complaints, rather than providing feedback and details of the problems/errors your encountering which would help resolve them.

Your current situation is mainly a consequence of your choice of keywords, you've no one to "blame" but yourself for that.

[Nerdanel]

The update wiped out my /etc/conf.d/net too. I tried to fix everything as well as I could, but I'm a little afraid of rebooting and seeing that I made a typo somewhere.

[tallica]

During shutdown I get 'start-stop-daemon: fopen `/var/run/gdm.pid': No such file or directory'

Code: Select all

rc shutdown logging started at Wed Apr 16 02:32:22 2008

 * Caching service dependencies ...
 [ ok ]
urandom           | * Saving random seed ...
local             | * Stopping local ...
 [ ok ]
swap              | * Deactivating swap devices ...
samba             | * samba -> stop: smbd ...
 [ ok ]
 [ ok ]
oss               | * Stopping OSS ...
xdm               | * Stopping gdm ...
 [ ok ]
netmount          | * Unmounting network filesystems ...
samba             | * samba -> stop: nmbd ...
hald              | * Stopping Hardware Abstraction Layer daemon ...
xdm               | * iptables          | * Saving iptables state ...
start-stop-daemon: fopen `/var/run/gdm.pid': No such file or directory
 [ ok ]
dcron             | * Stopping dcron ...
 [ ok ]
 [ ok ]
cupsd             | * Stopping cupsd ...
syslog-ng         | * Stopping syslog-ng ...
 [ ok ]
net.eth0          | * Bringing down interface eth0
 [ ok ]
 [ ok ]
dbus              | * Stopping D-Bnet.lo            | * Bringing down interface lo
US system messagebus ...
 [ ok ]
hwclock           | * Setting hardware clock using the system clock [Local Time] ...
 [ ok ]
iptables          | * Stopping firewall ...
 [ ok ]
 [ ok ]
net.lo            | *   Removing addresses
net.eth0          | *   Stopping dhcpcd on eth0 ...
 [ ok ]
net.eth0          | *   Removing addresses
 [ ok ]
 [ ok ]
localmount        | * Unmounting loopback devices
localmount        | *   Unmounting /usr/portage ...
 [ ok ]
localmount        | * Unmounting filesystems
localmount        | *   Unmounting /media/PART2 ...
 [ ok ]
localmount        | *   Unmounting /media/disk-3 ...
 [ ok ]
localmount        | *   Unmounting /media/disk-2 ...
 [ ok ]
localmount        | *   Unmounting /media/disk-1 ...
 [ ok ]
localmount        | *   Unmounting /media/disk ...
 [ ok ]
localmount        | *   Unmounting /media/PART1 ...
 [ ok ]
localmount        | *   Unmounting /mnt/disk4 ...
 [ ok ]
localmount        | *   Unmounting /mnt/disk3 ...
 [ ok ]
localmount        | *   Unmounting /mnt/disk2 ...
 [ ok ]
localmount        | *   Unmounting /mnt/disk1 ...
 [ ok ]
localmount        | *   Unmounting /var/tmp ...
 [ ok ]
localmount        | *   Unmounting /opt ...
 [ ok ]
localmount        | *   Unmounting /home ...
 [ ok ]
localmount        | *   Unmounting /usr ...
 [ ok ]
localmount        | *   Unmounting /boot ...
 [ ok ]
lvm               | * Shutting down the Logical Volume Manager
lvm               | *   Shutting Down logical volume: /dev/vg/test_a  ...
 [ ok ]
lvm               | *   Shutting Down logical volume: /dev/vg/test_b  ...
 [ ok ]
lvm               | *   Shutting Down volume group: vg  ...
 [ ok ]
lvm               | * Finished Shutting down the Logical Volume Manager

rc shutdown logging stopped at Wed Apr 16 02:32:27 2008

emerge --info: http://tallica.pl/linux/emerge_info

[Dirk.R.Gently]

@ mods, why do you allow troll comments to linger like nuktrition?

Nice job Uber! OpenRC is really coming around. I'll be very very glad when this finally hits stable and is an official part of gentoo. A modern rc system for thee best distro out here.