[einit] 0.21.0 -- now with gentoo-compat-0.99.0 (superseded)

jvale · Posted: Tue Apr 03, 2007 11:49 pm Post subject:

You missed the 'entrance' and 'entranced' modules when you split the configuration files. ;P

Cheers!

EDIT:
Oh, and I just emerged from SVN and the "mount"-module tries to acess my (empty) floppy drive like crazy on startup.

modified_bessel · Posted: Wed Apr 04, 2007 8:46 am Post subject:

mdeininger · Posted: Wed Apr 04, 2007 9:34 am Post subject:

modified_bessel:
so it IS probably a problem with dbus and either of the *DMs... wonder what we're doing wrong for dbus =)

jvale:
i think ryan put those back in later that night

there must be something wrong with the bootup scans in the mounter, takes ages on my box (i get a delay of pretty much exactly 30 seconds somewhere, and i can't figure out for the life of me where the hell that delay comes from... might be the mounter doing stuff it's not supposed to

)
_________________
"Confident, lazy, cocky, dead." -- Felix Jongleur, Otherland

( Twitter | Blog | GitHub )

rmh3093 · Posted: Wed Apr 04, 2007 1:55 pm Post subject:

mdeininger · Posted: Wed Apr 04, 2007 3:17 pm Post subject:

rmh3093 · Posted: Wed Apr 04, 2007 3:18 pm Post subject:

mdeininger · Posted: Wed Apr 04, 2007 4:04 pm Post subject:

rmh3093 · Posted: Thu Apr 05, 2007 12:24 am Post subject:

Alright everyone, there has been a big change in the network templates to listen up this effect you all!

NOTE: this is not 100% perfect (but still functional), things will probably change regarding how this all works but how interfaces are configured will try to remain constant

Starting with einit-9999-r18
1) depends on sys-apps/iproute2
2) all of the old net templates are obsolete, remove any reference to them from local.xml, they might break things
3) there is no more need to hack together modules to provide a particular net-, they are generated on the fly

Configuring network interfaces is as simple as the examples below.
There are 3 required componets, 1. the interface name, 2. the control= attribute and 3. the ip= attribute.
[*]control= specifies the manager for the network interfaces, possible options now are (none, wpa_supplicant). I will make an iwconfig template soon.
[*]ip= specifies how the network interface should gets its ip address, possible options now are (dhcpcd, pump, dhclient, iproute2), with iproute2 for static address
[*]kernel-module= specifies the required kernel module for the network interface, this is optional

All other options an interface might need are configured within the interfaces brackets.

EXAMPLE

modified_bessel · Posted: Thu Apr 05, 2007 3:33 pm Post subject:

Don't know if this is simple or not, but it's about the last thing holding up my system from being 100% functional under einit.

I have to call some serial ports and a touchscreen driver; under sysvinit the following works just like I need it to:

/etc/conf.d/local.start

modified_bessel · Posted: Thu Apr 05, 2007 5:44 pm Post subject:

Typo, last line? Vairables --> Variables ?? Line 338

/lib/einit/einit.xml v. 0.21

rmh3093 · Posted: Thu Apr 05, 2007 6:22 pm Post subject:

modified_bessel · Posted: Thu Apr 05, 2007 7:56 pm Post subject:

mdeininger · Posted: Thu Apr 05, 2007 8:50 pm Post subject:

heh, i think you're right -- sorry, been at the gym the last three hours or so

_________________
"Confident, lazy, cocky, dead." -- Felix Jongleur, Otherland

( Twitter | Blog | GitHub )

mdeininger · Posted: Thu Apr 05, 2007 10:40 pm Post subject:

something else, i changed the services with mount/* to mount-*

pros: you can now create modules to take their part, and prefer them over the compiled modules; cons, you need to change your configuration and also /CUSTOM MODULES/ to reflect this

so: change the following:
mount/system -> mount-system
mount/local -> mount-local
mount/critical -> mount-critical
mount/remote -> mount-remote
_________________
"Confident, lazy, cocky, dead." -- Felix Jongleur, Otherland

( Twitter | Blog | GitHub )

UberPinguin · Posted: Fri Apr 06, 2007 6:08 pm Post subject:

I updated einit last night, but now at boot I get this:

modified_bessel · Posted: Fri Apr 06, 2007 6:36 pm Post subject:

and I got, for (einit-9999-r19.ebuild)

rmh3093 · Posted: Fri Apr 06, 2007 8:10 pm Post subject:

magnus: ever since you moved module-so from internal to external things have been weird I think
_________________
Do not meddle in the affairs of wizards, for they are subtle and quick to anger.

modified_bessel · Posted: Sat Apr 07, 2007 7:04 am Post subject:

0.21.1-svn-1094 now (somewhat) duplicating the 1081 results of UberPenguin. tty12 in an endless loop reporting udevd[16259] error. tty11 shows many broken services (dbus, hal, xdm, alsa, logging .......). After several minutes, can finally get to a login terminal, but the endless udevd loop is still active, and the filesystem is all Read-Only. /dev shows many tty devices, but no hard disks, etc....

mdeininger · Posted: Sat Apr 07, 2007 5:23 pm Post subject:

might be something about the new udev module... i added a dont-close-stdin option, that could fix it (no stdin has a tendency to kill udev utils... ohwell :-/)

if udev keeps dying, then maybe that's due to that stdin problem, just commited a fix for that. alternatively, it might be it needs >= udev-093...

as for the fd0... that's kind of weird, did you try the fbsplash plugin? (fb0 can be both a floppy and the framebuffer i think... meh..)

rmh3093: didn't move module-so from internal to external, actually i specifically made sure that module-so is built into the core in the build script...
_________________
"Confident, lazy, cocky, dead." -- Felix Jongleur, Otherland

( Twitter | Blog | GitHub )

rmh3093 · Posted: Sun Apr 08, 2007 1:20 pm Post subject:

is there anyone still having udev issues?
_________________
Do not meddle in the affairs of wizards, for they are subtle and quick to anger.

modified_bessel · Posted: Sun Apr 08, 2007 10:18 pm Post subject:

I upgraded from udev-087 to 104-r11 and that seemed to work; it is somewhat slower than 087 was under einit-0.21.0, but it seens to load fine now; no more endless floppy and hard disk loops....

Any advice on getting the network back up? I have tried endless permutations with the new network module (9999-r20, latest svn as of last night). can not get eth0 up under any circumstance; net-lo reports:

jvale · Posted: Mon Apr 09, 2007 12:19 am Post subject:

About udev:
eINIT: 0.21.1-svn-1107
udev: 104-r12

When booting, it hangs for 10 seconds when enabling udev (got the same 10 seconds in several runs).

When enabling eth0, strangely enough dhcpcd is not setting the default gateway. What puzzles me is that dhcpcd is working fine under Init, but under eINIT it doesn't set the default gateway, neither by enabling net-eth0 nor calling it directly ('dhcpcd eth0'). Gonna look into it to see if it's some freak-problem in my setup as it seems strange that eINIT would cause this. This might be the same issue as modified_bessel tough.

Update:
Did some more testing and the dhcpcd issue stands.

UberPinguin · Posted: Mon Apr 09, 2007 2:55 am Post subject:

modified_bessel · Posted: Mon Apr 09, 2007 7:03 am Post subject:

I am getting precisely the same results as jvale; same hang (~10s) on udev, and same problem with setting the gateway, eth0, etc.

I have reinstalled back to einit-0.21.0, same system as before except with udev 104 instead of the previous 087, and the results are just as with 087: no 10s hang on udev, mounts fast, gateway and eth0 activated correctly; no problems!

mdeininger · Posted: Mon Apr 09, 2007 8:20 am Post subject:

heh, i'll be able to do more thorough tests again today, so i'll probably be able to figure out what's wrong later today... lots of stuff did change, so sorry if it broke stuff :-/
_________________
"Confident, lazy, cocky, dead." -- Felix Jongleur, Otherland

( Twitter | Blog | GitHub )