On Friday 03 October 2014 04:32 PM, Ritesh Raj Sarraf wrote:
On Friday 03 October 2014 02:50 PM, Ritesh Raj Sarraf wrote:
I tried OpenRC in June. Which would mean the latest version. Since
my last try, OpenRC has not seen a new upload into the archive.
Do you still want me to test again ?
I still went ahead and tested again. And the problem remains the same.
As expected, it waits on starting crypto disks. Interrupting whatever
is stuck at that moment, the boot proceeds fine.
There are other issues that should be causing problems too. The
network does not come up, which leads to many of the services hanging
or failing, including the desktop.
The cause is that to bring the loopback interface up, the initscript
expects the /run/network/ path available. That path is non-existent.
Upon creating the path, and restarting the network service, the
loopback interface is UP. I have taken pictures in case you want to
see the actual boot hang. There are also failures in resolvconf and
dnsmasq, which I suspect is linked to similar issues.
And then the problem does not end there. Looks like the Debian Linux
userspace is plagued. Attaching a device results in KDE showing a
pop-up to mount, but attempts fail with errors like "Unexpectedly" or
"No authorization".
Screenshots of the bugs...
https://lh5.googleusercontent.com/-tKCyUAqeoIo/VC6ByE26HFI/AAAAAAAALpE/r7M2qdaw3Yg/s800/IMG_20141003_154916.jpg
https://lh6.googleusercontent.com/-Rl245YK2TPI/VC6B5ln5ccI/AAAAAAAALpM/dsupmG5BH6A/s800/IMG_20141003_155355.jpg
Do you guys know what service / facility is responsible for populating
/run ??
I think the problem lies there because not all path / folders are setup
proper. This further leads to core services failing.
--
Ritesh Raj Sarraf
RESEARCHUT - http://www.researchut.com
"Necessity is the mother of invention."
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
