OpenMandriva releases beta Topic is solved

[viking60]

Ok now that is taken care of let's se if we can speed up the boot of this thing.
The data before:

Code: Select all

[Berserk@localhost ~]$ systemd-analyze
Startup finished in 5.687s (kernel) + 36.896s (userspace) = 42.584s


And

Code: Select all

[Berserk@localhost ~]$ systemd-analyze blame
         13.603s sshd.service
          8.970s mysqld.service
          5.415s network.service
          4.995s winbind.service
          4.760s saslauthd.service
          4.728s polkit.service
          4.694s httpd.service
          4.602s plymouth-start.service
          4.302s vboxadd-x11.service
          4.161s mandriva-save-dmesg.service
          4.122s mandriva-everytime.service.....


This means that it tooke 42,6 seconds to boot ...
Now we do the systemd magic stuff

Code: Select all

sudo systemctl enable systemd-readahead-collect systemd-readahead-replay

Ill be back with the after... need to reboot a few times first

[viking60]

First reboot 53 seconds - slower as expected.
Second reboot:

Code: Select all

[Berserk@localhost ~]$ systemd-analyze
Startup finished in 5.696s (kernel) + 19.399s (userspace) = 25.095s


Code: Select all

[Berserk@localhost ~]$ systemd-analyze blame
          5.751s mysqld.service
          3.891s network.service
          3.509s mandriva-everytime.service
          3.507s mandriva-save-dmesg.service
          3.068s httpd.service
          2.525s resolvconf.service
          2.517s vboxadd-x11.service
          2.468s wpa_supplicant.service
          2.268s saslauthd.service
          2.266s sshd.service.....


Holy smoke! That operation almost cut my boot time in half
And after the fourth boot it was pretty much exactly cut in half (roughly )

Code: Select all

[Berserk@localhost ~]$ systemd-analyze
Startup finished in 5.669s (kernel) + 17.559s (userspace) = 23.228s


Great improvement!

If you want a fast boot too - here is the tip:
viewtopic.php?f=25&t=2929
Here is the Wiki

[viking60]

Booted again:

Code: Select all

[Berserk@localhost ~]$ systemd-analyze
Startup finished in 5.507s (kernel) + 13.429s (userspace) = 18.936s


Ha! More than cut in half - I knew I was not lying.
From 42 to 18 seconds is not bad - I tell you.
Results may vary with the different installations - but you have nothing to loose.

[viking60]

hi Dedanna,

humm, this forum should have an dokuwiki or something

best regards
Blacky

Done

[Blackcrack]

blaehh it's like the american one .. *gigle*
i did see it but i can make an wiki on my blackysgate.dsndns.org or..
on my Blackysgate.net , both want be possible .. , nice but okey how ever ..
humm...... did you take the beta, add the online sources, once via mirrorlisting, once with add an spezific Source (cooker directly)
and let run finally:

urpmi --auto --auto-update --downgrade

why downgrade, because you otherwise can not update !


from the actual mirrorlisting (don't know which webcopy it's use) and the cookersources from rosa
and you want have an big problem.. you cont become an login(no bash) and the KDE don't want start fast it's need long time..

the many buttons on the panel .. hey sorry, this installer it's the last crap..
i think i mus go back to the better installer.. and better cooker distro ..

bero, you make with this schit of peace installer an big fail !

because the Drakinstaller so the normal installer who you can selecting the packages, it's an testing tool also..

it bleeds me my Heart !

best regards
Blacky

[Blackcrack]

hi,

do you know what it is need on SystemD ?

an tool who can administrating and moving the starters in sequence
and an who can also enabling and disabling some instances !

As one Gui ! maybe in QT or GTK, but this not important , important it is, to we have a graphical gui it can administrate !

like it is now, with only an "let run all" without enabling for configuring the instances..
and this is crap !

best regards
Blacky

[viking60]

As usual; I am not sure I understand what you are "saying".
But if you want a GUI for systemd then what is wrong with the draktools?

You can start and stop services there. Our added "speed up boot" services are there too.

If you are criticizing systemd in general then you are not alone - Linux users are a conservative lot who do not like change all that much.
In any case; such general criticism would be
(But do feel free to start another thread and criticize it all you want...)

[viking60]

They even fixed bug 273
I had not expected that. Good show.
For the upcoming release we will have to remember to install systemd-tools though.....

[Blackcrack]

As usual; I am not sure I understand what you are "saying".
But if you want a GUI for systemd then what is wrong with the draktools?

You can start and stop services there. Our added "speed up boot" services are there too.

If you are criticizing systemd in general then you are not alone - Linux users are a conservative lot who do not like change all that much.
In any case; such general criticism would be
(But do feel free to start another thread and criticize it all you want...)

can you move the instances with draktools ?

up/down for starting first or more behind or at last ?

nope you can't, that's the fail ....

all mus goes with edit and change it in prompt and not easy.. you mus know what you does in systemd,
in initd was really more easy ..

how ever.. the systemd it is the future and there for should be get more user attractive and more usable tools ..

ehh you have startet here with "offtopic" "Re: OpenMandriva releases beta - speeding it up"

best regards
Blacky

[viking60]

No you cannot change the instances in the draktools. (That is on topic - don't worry - the general "systemd sucks" discussion would be off).
I have seen a need to move (or delay) services when setting up network connections (often wpa_supplicant related).

But in this beta I have not had one instance where I have felt the need to rearrange services.
But then again I have not been testing wireless.

[viking60]

I find the Mandriva alias system less than user friendly.
In Other distros you can create an .alias file in your home and put your home made aliases in there.

That is way tidier than fidling arround with /etc/bashrc or /etc/profile.d IMHO

So I put this in /etc/bashrc

Code: Select all

#Making ~/.alias the home of our private aliases
if [ -f .alias ]; then
    . .alias
fi


(Yes that is fidling - but way more ellegant than 100 aliases...)
Yeah they will probably overwrite it etc etc but until then you have your aliases in one place so you can easily activate them again.
And it does make sense to seperate home made aliases from the official ones.
I wonder if I should make this an improvement suggestion Does anyone know anything that speaks against it?

[luca]

i think that now .bashrc is used for aliases:

Code: Select all

$ more .bashrc
# .bashrc

# User specific aliases and functions

# Source global definitions
if [ -f /etc/bashrc ]; then
        . /etc/bashrc
fi