Ovo me je zanimalo i nema ga u zurnalu, to sam hteo ili da vidim u boot.log kako je pre bilo
ili sad u zurnalu. Nijedan distro mi ne ispisuje izlaz iz fsck a koliko se secam to je nekako
namestenao da se prikaze samo kad se desi neki zvek sistema.
Pokusao sam da mu ga dam da to ispise u zurnalu bas po arch wiki savetima ali ne radi
Sta to on brise? ta cifra varira od 390000 do ove vrednosti gore? ili ja ne razumem da clean nije ciscenje nego
eto tako mora da pise.
Code:
sudo fsck.ext4 -vpf /dev/sdc5
Po ovom sto ispise znam da je ok jer lepo kaze a ovo drugo je glupost koja zbunjuje i zato sam hteo da
imam taj ispis od boot-a da bi ga postovao
Citat:
manjaror: clean, 400941/2027648 files, 3994316/8094744 blocks
Code:fsck
To hide fsck messages during boot, let systemd check the root filesystem. For this, remove fsck from:
HOOKS=(...)
in /etc/mkinitcpio.conf and then run:
mkinitcpio -p linux
Now copy the files systemd-fsck-root.service and
[email protected] located at /usr/lib/systemd/system/ to /etc/systemd/system/ and edit them, configuring StandardOutput and StandardError like this:
(...)
[Service]
Type=oneshot
RemainAfterExit=yes
ExecStart=/usr/lib/systemd/systemd-fsck
StandardOutput=null
StandardError=journal+console
TimeoutSec=0
Mislim da sam dobro razumeo ovo na wiki, sklanjam fsck sa ekrana kod podizanja i upisujem izlaz u zurnal.
Raspored fajlova je totalno isti kod Manjara i Archa.
Code:
journalctl | grep fsck
prazno
sudo journalctl | grep fsck
prazno
Ovo dalje me totalno ne zanima da li se dize za 30 sec ili 2 minuta, meni je nebitno
Ako nema nista u distrou dizace se nabrzaka ili ako stavim / na SSD disk ima da poludi.
To je zanimljivo ako ga sistem bas zatupi i uspori, to sto pise meni nije merodavno,
za mene je merodavno vreme kad sistem starta pa dodjes do kucanja passworda,
otkucas pass nabrzaka i kad se sve pojavi na ekranu tu je kraj podizanja. :)
Code:
systemd-analyze
Startup finished in 3.101s (kernel) + 13.774s (userspace) = 16.875s
Code:systemd-analyze blame
8.723s plymouth-start.service
1.941s NetworkManager.service
1.908s ModemManager.service
1.663s systemd-vconsole-setup.service
1.551s systemd-udevd.service
1.144s media-rt2.mount
1.040s systemd-journald.service
859ms systemd-journal-flush.service
819ms lm_sensors.service
797ms keyboardctl.service
779ms media-magacin.mount
777ms media-satadisk.mount
714ms polkit.service
676ms dev-hugepages.mount
660ms systemd-logind.service
595ms systemd-modules-load.service
469ms media-satadisk1.mount
402ms rpcbind.service
395ms systemd-binfmt.service
235ms systemd-tmpfiles-setup-dev.service
218ms bluetooth.service
213ms systemd-sysctl.service
196ms systemd-user-sessions.service
190ms systemd-tmpfiles-setup.service
185ms systemd-udev-trigger.service
176ms systemd-tmpfiles-clean.service
151ms kmod-static-nodes.service
146ms wpa_supplicant.service
140ms tmp.mount
140ms systemd-remount-fs.service
138ms proc-sys-fs-binfmt_misc.mount
138ms dev-mqueue.mount
135ms udisks2.service
125ms
[email protected]
124ms plymouth-read-write.service
113ms
[email protected]
110ms upower.service
104ms ntpd.service
84ms avahi-daemon.service
81ms home.mount
55ms sys-fs-fuse-connections.mount
40ms systemd-update-utmp.service
38ms systemd-random-seed.service
36ms sys-kernel-config.mount
31ms rtkit-daemon.service
29ms plymouth-quit.service
28ms plymouth-quit-wait.service
16ms
[email protected]
11ms alsa-restore.service
2ms sys-kernel-debug.mount