On Sat, Aug 11, 2012 at 6:27 AM, David Benfell
benf...@parts-unknown.org wrote:
2) But I did notice an error that worried me--just because it looks
worrying--as it came up:
Aug 09 13:34:36 graton systemd-fsck[270]: /dev/sda3 is mounted.
Aug 09 13:34:36 graton systemd-fsck[270]: e2fsck: Cannot
On Sat, Aug 11, 2012 at 8:57 AM, David Benfell benf...@parts-unknown.orgwrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi all,
I just moved my desktop to systemd, and saw a couple things as I
booted it for the first time:
1) It is *fast*. Let me say that again. It is *fast*. I have
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 08/11/2012 04:09 AM, Mantas Mikulėnas wrote:
On Sat, Aug 11, 2012 at 6:27 AM, David Benfell
benf...@parts-unknown.org wrote:
2) But I did notice an error that worried me--just because it
looks worrying--as it came up:
Aug 09 13:34:36 graton
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 08/11/2012 05:26 AM, Aurko Roy wrote:
An error code of 8 for fsck means an operational error/general
failure. Do you get this error every time you boot or is it a one
off thing? Have you tried running it manually?
To the first question, I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi all,
I just moved my desktop to systemd, and saw a couple things as I
booted it for the first time:
1) It is *fast*. Let me say that again. It is *fast*. I have never
seen a system come up this fast. Critics of systemd might want to
consider
5 matches
Mail list logo
