Hello, Thomas.
On Fri, Dec 18, 2015 at 10:57:53AM +, Thomas Sigurdsen wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
> The problems/strange state persists with mtab being a symlink and then
> rebooting. Mtab stays a symlink through reboots too.
This is a stab in the dark, but rec
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
The problems/strange state persists with mtab being a symlink and then
rebooting. Mtab stays a symlink through reboots too.
> I wouldn't expect the symlink to fix anything without a reboot (since
> the main problem is at startup time). I'm not sure
I wouldn't expect the symlink to fix anything without a reboot (since the main
problem is at startup time). I'm not sure if the dbus issue is separate or not
- if it is the same it seems odd that it won't start even after getting
everything mounted by hand, anyway.
-John
Sent from my phone
Tho
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
> It seems to me the root of your problems is fsck failing because (it
> thinks) the partitions are already mounted.
>
> Is your mtab a symlink to /proc/mounts as it "should" be?
Just checked, and mtab is not a symlink. It is a plain text file.
Ju
It seems to me the root of your problems is fsck failing because (it thinks)
the partitions are already mounted.
Is your mtab a symlink to /proc/mounts as it "should" be?
Thomas Sigurdsen wrote:
>-BEGIN PGP SIGNED MESSAGE-
>Hash: SHA256
>
>There is an html version of this mail, that al
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
There is an html version of this mail, that also has emerge --info and
my kernel config, at:
http://browniehive.net/tmp/hp-problems.html
I've come to a dead end in troubleshooting this issue and turn to you
for help in how to continue. The following
6 matches
Mail list logo
