You are not logged in.
You broke clock again with 20095012
Cthulhu For President!
Offline
I'll be using the original init until you have the new init available, please wake this topic if you opened the new one.
Offline
I'll be using the original init until you have the new init available, please wake this topic if you opened the new one.
I think the new one is here.
Seems like a very interesting project. I'll be trying it on my new laptop right away when I receive it
Offline
This looks a lot like my old BSD scripts I used on LFS
Most slowdowns come from HAL and Udev and it seems a lot of arch users are not too happy with the bloat and slowdowns these provide.
Offline
You broke clock again with 20095012
If you're like me (using utc), then what you could to do to fix this is to edit finit-arc.c, in the function shutdown(), change the parameter of the hwclock call from '--localtime' to '--utc' (ie the problem is that during the shutdown, clock is saved as localtime regardless of the rc.conf setting).
Offline
buttons wrote:You broke clock again with 20095012
If you're like me (using utc), then what you could to do to fix this is to edit finit-arc.c, in the function shutdown(), change the parameter of the hwclock call from '--localtime' to '--utc' (ie the problem is that during the shutdown, clock is saved as localtime regardless of the rc.conf setting).
No, I use localtime, and it's failing to set that...
Cthulhu For President!
Offline
Duologic wrote:I'll be using the original init until you have the new init available, please wake this topic if you opened the new one.
I think the new one is here.
Seems like a very interesting project. I'll be trying it on my new laptop right away when I receive it
I tried those initscripts.
I had to boot my arch live cd, mount /dev/sda3, restore some pacsaves, boot into my "just in case" kernel using finit-arc(the original init scripts where hosed), AND THEN reinstall initscripts.
I also had to re-edit rc.conf and put hal networkmanager and alsa back in.
Finit-arc however, decreased my boot time to 10 seconds.
thanks.
Offline
Why do you always delete the prevenient git commits? Then how do you reset them if the code is broken?
Offline
I had a problem with a git..
Italian ArchLinux User
My projects on my homepage: www.obliquo.net
Offline
colin.f.drake wrote:Duologic wrote:I'll be using the original init until you have the new init available, please wake this topic if you opened the new one.
I think the new one is here.
Seems like a very interesting project. I'll be trying it on my new laptop right away when I receive it
I tried those initscripts.
I had to boot my arch live cd, mount /dev/sda3, restore some pacsaves, boot into my "just in case" kernel using finit-arc(the original init scripts where hosed), AND THEN reinstall initscripts.
I also had to re-edit rc.conf and put hal networkmanager and alsa back in.Finit-arc however, decreased my boot time to 10 seconds.
thanks.
Exact same thing over here, except for the finit-arc part, didn't had a backup plan except for the bootcd I had somewhere. I just hoped it would be as easy as finit-arc, but quick-init just does it totally different. After copying inittab and rc.sysinit from a bootcd, I was able to get into a terminal and reinstall my initscripts. I don't know the codebase of finit-arc, but I think it looks more promising than quick-init, except for a few bugs, it works!
Offline
I disagree. Finit-arc works but is seriously dangerous for system security. I say these becouse I know the major design problems in the finit-arc source code. Init is the best, the safest solution. Actually the problem is only one: start X quickly.
Italian ArchLinux User
My projects on my homepage: www.obliquo.net
Offline
I disagree. Finit-arc works but is seriously dangerous for system security. I say these becouse I know the major design problems in the finit-arc source code. Init is the best, the safest solution. Actually the problem is only one: start X quickly.
Could you be more specific about the design/security problems, please?
Offline
bender02 finit-arc have problems with hierarchy of processes (father process's fork) for example if you upgrade kernel-headers cpu stay 100%, or FAM and PORTMAP doesn't start correctly..
Italian ArchLinux User
My projects on my homepage: www.obliquo.net
Offline
I use init indeed, but what about quick-init, installed it once and it fucked my system...
If you know the issues of finit-arc; can't you fix it then?
Offline
to the qinit scripts, 10 sec are nothing special ..
we need to pimp x
btw here is a video from my bootup:
Offline
How does your kernel boot so fast? (is it in quiet mode?)
Offline
Its a selfcompiled Kernel with "quiet" option
Offline
I can't find the line: RTC_MAJOR=$(/bin/grep -w rtc /proc/devices 2>/dev/null); RTC_MAJOR="${RTC_MAJOR%% *}" in the RTC part of your rc.sysinit script.
Last edited by Wintervenom (2009-08-03 14:20:02)
Offline
to Wintervenom
it's flase RTC_MAJOR line is in qinit.sysinit.
to Echtor2oo3
10 seconds with my pc, if you have already 10 seconds with classic init, you should have 5/6 seconds boot with quick-init. Try it.
to Duologic
quick-init fuck your system becouse it replaced a previous version of quick init that included also the initscripts. Then you losted your initscripts. Just a bit of attention
I dont want speak here about quick-init. I will open another topic for it.
The finit-arc project is temporarily suspended.
Last edited by adriano (2009-05-13 19:43:22)
Italian ArchLinux User
My projects on my homepage: www.obliquo.net
Offline
probably true, didn't search further because of a lack of time
I seem not to find a english manual somewhere, sorry I don't have much knowledge of italian..
Offline
I wrote it in english in the comments of QUICK-INIT
Italian ArchLinux User
My projects on my homepage: www.obliquo.net
Offline
Ok, so my italian isn't that bad, I did it as you said in de comments on AUR and it wouldn't boot
edit: let's try again
edit 2: still no succes, I get some errors on 'printhl: not found' and 'printsep: not found'. After a boot from the live CD en putting back my rc.conf, boot untill agetty succeeded, but my daemons don't run... and so on. Am I missing something
Last edited by Duologic (2009-05-13 22:08:48)
Offline
I think the point is that with the newer versions of quick-init you should *not* remove the original initscripts, quick-init will install alongside.
Offline
Hiyaa! thanks for the tip bender02, I've put it in the AUR comments.
Is there a topic of quick-init yet?
I've got a bug on loading alsa to early, no sound card found by alsactl. Also mounting /proc/bus/usb doesn't work on mounting filesystems, necessary for Virtualbox, don't use for now, so no rush here. Also also I can't restart HAL for some reason, it's running though.
Offline
I also have a bug with dm-raid not working with quick-init. Tradicional scripts work without any problem... It would be a nice idea to start a "oficial" topic
.::. TigTex @ Portugal .::.
Offline