On January 1, 2018 3:54:02 AM GMT+03:00, Hendrik Boom
wrote:
>On Sun, Dec 31, 2017 at 07:19:06PM -0500, Hendrik Boom wrote:
>> On Sun, Dec 31, 2017 at 06:00:44PM -0500, Hendrik Boom wrote:
>> > I just upgraded devuan from jessie to ascii. I now have a new
>kernel.
>> >
>> > Now I'm used to, w
On Sun, Dec 31, 2017 at 07:54:02PM -0500, Hendrik Boom wrote:
[cut]
>
> Started interactive aptitude, looking for packages with names like
> initramfs-tools. Found it in state 'u', unconfigured. And there were
> *oodles* of packages in that same state. I told aptitude 'g' and let
> iit hav
On Sun, Dec 31, 2017 at 06:00:44PM -0500, Hendrik Boom wrote:
> I just upgraded devuan from jessie to ascii. I now have a new kernel.
>
> Now I'm used to, when a new kernel is installed, that the boot process
> is also updated to boot the new kernel. But this has not happened.
>
> I still hae
On Sun, Dec 31, 2017 at 07:19:06PM -0500, Hendrik Boom wrote:
> On Sun, Dec 31, 2017 at 06:00:44PM -0500, Hendrik Boom wrote:
> > I just upgraded devuan from jessie to ascii. I now have a new kernel.
> >
> > Now I'm used to, when a new kernel is installed, that the boot process
> > is also updat
On Sun, Dec 31, 2017 at 06:00:44PM -0500, Hendrik Boom wrote:
> I just upgraded devuan from jessie to ascii. I now have a new kernel.
>
> Now I'm used to, when a new kernel is installed, that the boot process
> is also updated to boot the new kernel. But this has not happened.
>
> I still hae
I just upgraded devuan from jessie to ascii. I now have a new kernel.
Now I'm used to, when a new kernel is installed, that the boot process
is also updated to boot the new kernel. But this has not happened.
I still hae the same old /boot/grub/grub.cfg, which specified the same
old kernel and
