On Fri, Jan 11, 2019 at 03:16:37PM +1300, Richard Hector wrote:
It turns out the later failures to boot probably weren't; it's just that
I had 'quiet' enabled in the kernel commandline. Disabling that enabled
me to see where it was hanging
Yeah, I hate that "quiet" is the default--in the best
On 4/01/19 2:48 PM, Richard Hector wrote:
> Hi all,
>
> This is one of those annoying cases where I claim "It was working, and I
> didn't do anything, and now it doesn't" - suspicious, I know ...
>
> In this case, I can see from my emails that this machine booted (via
> wake-on-lan from a
Hi all,
This is one of those annoying cases where I claim "It was working, and I
didn't do anything, and now it doesn't" - suspicious, I know ...
In this case, I can see from my emails that this machine booted (via
wake-on-lan from a cronjob) this morning, and then shut itself down (via
a local
3 matches
Mail list logo