Re: [DNG] Upgrade problem [ ascii -> beowulf ] failed to boot, left at initramfs shell -- with fix and query

...on Wed, Jul 08, 2020 at 05:12:54PM +0200, Alexander Bochmann wrote: > ...on Wed, Jul 08, 2020 at 06:14:51PM +1000, Andrew McGlashan via Dng wrote: > > Using the /dev/mapper device name would likely have been just as good, > but I'm not sure as I didn't try that > I'll try if using UUIDs

Re: [DNG] Upgrade problem [ ascii -> beowulf ] failed to boot, left at initramfs shell -- with fix and query

...on Wed, Jul 08, 2020 at 06:14:51PM +1000, Andrew McGlashan via Dng wrote: > Using the /dev/mapper device name would likely have been just as good, but > I'm not sure as I didn't try that I'll try if using UUIDs in the fstab makes a difference in the boot process later tonight (and maybe

Re: [DNG] Upgrade problem [ ascii -> beowulf ] failed to boot, left at initramfs shell -- with fix and query

On 8/7/20 10:07 pm, Hendrik Boom wrote: > On Wed, Jul 08, 2020 at 06:14:51PM +1000, Andrew McGlashan via Dng wrote: >> >> >> On 8/7/20 7:31 am, Alexander Bochmann wrote: >>> Hi, >>> >>> ...on Tue, Jul 07, 2020 at 02:00:38AM +1000, Andrew McGlashan via Dng wrote: >>> >>> > After the

Re: [DNG] Upgrade problem [ ascii -> beowulf ] failed to boot, left at initramfs shell -- with fix and query

On Wed, Jul 08, 2020 at 06:14:51PM +1000, Andrew McGlashan via Dng wrote: > > > On 8/7/20 7:31 am, Alexander Bochmann wrote: > > Hi, > > > > ...on Tue, Jul 07, 2020 at 02:00:38AM +1000, Andrew McGlashan via Dng wrote: > > > > > After the dist-upgrade, it failed to boot and remained at the >

Re: [DNG] Upgrade problem [ ascii -> beowulf ] failed to boot, left at initramfs shell -- with fix and query

On 8/7/20 7:31 am, Alexander Bochmann wrote: > Hi, > > ...on Tue, Jul 07, 2020 at 02:00:38AM +1000, Andrew McGlashan via Dng wrote: > > > After the dist-upgrade, it failed to boot and remained at the ministrants > shell environment after having complained about not being able to find the >

Re: [DNG] Upgrade problem [ ascii -> beowulf ] failed to boot, left at initramfs shell -- with fix and query

Hi, ...on Tue, Jul 07, 2020 at 02:00:38AM +1000, Andrew McGlashan via Dng wrote: > After the dist-upgrade, it failed to boot and remained at the ministrants > shell environment after having complained about not being able to find the > /usr file system via it's UUID. I have a system mostly

Re: [DNG] Upgrade problem [ ascii -> beowulf ] failed to boot, left at initramfs shell -- with fix and query

Forget it - you have Thank you. On Tue, 7 Jul 2020, Jim Jackson wrote: > > > > On Tue, 7 Jul 2020, Steve Litt wrote: > > > On Mon, 6 Jul 2020 18:58:48 -0400 > > Hendrik Boom wrote: > > > > > > > Doesn't systemd require a merged /usr partition? It sounds as if a > > > systemd-ism

Re: [DNG] Upgrade problem [ ascii -> beowulf ] failed to boot, left at initramfs shell -- with fix and query

On Tue, 7 Jul 2020, Steve Litt wrote: > On Mon, 6 Jul 2020 18:58:48 -0400 > Hendrik Boom wrote: > > > > Doesn't systemd require a merged /usr partition? It sounds as if a > > systemd-ism has crept into our boot process. > > > > Fortunately I haven't upgraded my server to beowulf yet. > >

Re: [DNG] Upgrade problem [ ascii -> beowulf ] failed to boot, left at initramfs shell -- with fix and query

On Mon, 6 Jul 2020 18:58:48 -0400 Hendrik Boom wrote: > Doesn't systemd require a merged /usr partition? It sounds as if a > systemd-ism has crept into our boot process. > > Fortunately I haven't upgraded my server to beowulf yet. > > -- hendrik Void Linux also symlinks all the various

Re: [DNG] Upgrade problem [ ascii -> beowulf ] failed to boot, left at initramfs shell -- with fix and query

On 7/7/20 8:58 am, Hendrik Boom wrote: > Doesn't systemd require a merged /usr partition? It sounds as if a > systemd-ism has crept into our boot process. > > Fortunately I haven't upgraded my server to beowulf yet. Probably I know that Debian wants merged /usr, wasn't sure it was

Re: [DNG] Upgrade problem [ ascii -> beowulf ] failed to boot, left at initramfs shell -- with fix and query

On Tue, Jul 07, 2020 at 02:00:38AM +1000, Andrew McGlashan via Dng wrote: > Hi, > > I had another "simple" server upgrade from Devuan Ascii to Devuan Beowulf, > these are the details and my work around for the problem. > > > There was nothing particularly special about this server, it doesn't

[DNG] Upgrade problem [ ascii -> beowulf ] failed to boot, left at initramfs shell -- with fix and query

Hi, I had another "simple" server upgrade from Devuan Ascii to Devuan Beowulf, these are the details and my work around for the problem. There was nothing particularly special about this server, it doesn't use encrypted file systems; it started out life as a Debian Wheezy installation,

Re: [DNG] Upgrade problem [ ascii -> beowulf ] chrooted bind9 server -- /usr/share/dns/root.hints issue -- with fix

It should be. I had the same problem a little over a month ago and that fixed it for me. Been running fine since. On Mon, 2020-07-06 at 00:39 +1000, Andrew McGlashan via Dng wrote: > Hi, > > Okay, not fully fixed after reboot... apparmor gave problems as > previously discussed on the list. > >

Re: [DNG] Upgrade problem [ ascii -> beowulf ] chrooted bind9 server -- /usr/share/dns/root.hints issue -- with fix

Hi, Okay, not fully fixed after reboot... apparmor gave problems as previously discussed on the list. Also needed to adjust: /etc/apparmor.d/local/usr.sbin.named Added a line: /var/lib/named/** rw, Then restarted apparmor service: service apparmor reload And then bind would

[DNG] Upgrade problem [ ascii -> beowulf ] chrooted bind9 server -- /usr/share/dns/root.hints issue -- with fix

Hi, I just upgraded fron Devuan ascii to beowulf with the server running bind9 in a chroot environment and bind would not start. _This was the relevant error in /var/log/daemon.log_ Jul  5 23:36:43 bind9-server-name named[6476]: *could not configure root hints from

Re: [DNG] upgrade to ascii dkim stopped working

On Thu, Feb 28, 2019 at 05:55:46PM +0100, info at smallinnovations dot nl wrote: > opendkim (2.11.0~alpha-8) unstable; urgency=medium On systems using > systemd, this version replaces /etc/default/opendkim with the files > /etc/systemd/system/opendkim.service.d/overrride.conf and >

Re: [DNG] upgrade to ascii dkim stopped working

On 28-02-19 08:08, KatolaZ wrote: >> Apparently opendkim 2.11 has been polluted/infected by systemd. Lots of >> systemd bugreports, notes about being a native systemd daemon but simply >> not working from postfix. I downgraded opendkim from 2.11 to 2.9 and >> everythings is working again. >> >> Of

Re: [DNG] upgrade to ascii dkim stopped working

On Wed, Feb 27, 2019 at 10:30:29PM +0100, info at smallinnovations dot nl wrote: > On 25-02-19 00:18, Gregory Nowak wrote: > > On Sun, Feb 24, 2019 at 03:55:08PM +0100, info at smallinnovations dot nl > > wrote: > >> After upgrading a production server to ascii from jessie, opendkim > >> stopped

Re: [DNG] upgrade to ascii dkim stopped working

Am 2019-02-27 22:30, schrieb info at smallinnovations dot nl: Apparently opendkim 2.11 has been polluted/infected by systemd. Lots of systemd bugreports, notes about being a native systemd daemon but simply not working from postfix. I downgraded opendkim from 2.11 to 2.9 and everythings is

Re: [DNG] upgrade to ascii dkim stopped working

On Wed, Feb 27, 2019 at 10:30:29PM +0100, info at smallinnovations dot nl wrote: > Apparently opendkim 2.11 has been polluted/infected by systemd. Lots of > systemd bugreports, notes about being a native systemd daemon but simply > not working from postfix. I downgraded opendkim from 2.11 to 2.9

Re: [DNG] upgrade to ascii dkim stopped working

On 25-02-19 00:18, Gregory Nowak wrote: > On Sun, Feb 24, 2019 at 03:55:08PM +0100, info at smallinnovations dot nl > wrote: >> After upgrading a production server to ascii from jessie, opendkim >> stopped working. When i start opendkim manually i get the error >> "Starting OpenDKIM: install:

Re: [DNG] upgrade to ascii dkim stopped working

On Sun, Feb 24, 2019 at 03:55:08PM +0100, info at smallinnovations dot nl wrote: > After upgrading a production server to ascii from jessie, opendkim > stopped working. When i start opendkim manually i get the error > "Starting OpenDKIM: install: cannot create directory ‘’: No such file or >

[DNG] upgrade to ascii dkim stopped working

After upgrading a production server to ascii from jessie, opendkim stopped working. When i start opendkim manually i get the error "Starting OpenDKIM: install: cannot create directory ‘’: No such file or directory". I kept the original configfiles. There is a update remark from debian about when

Re: [DNG] upgrade to ascii

Hi, KatolaZ writes: > On Mon, Jan 01, 2018 at 01:59:23PM +0900, Olaf Meeuwissen wrote: >> Hi, >> >> [...] I just upgraded >> myself using (almost) the same without any problems and blogged about >> it here >> >> https://paddy-hack.gitlab.io/posts/upgrading-devuan-from-jessie-to-ascii/ > >

Re: [DNG] upgrade to ascii

On Mon, Jan 01, 2018 at 01:59:23PM +0900, Olaf Meeuwissen wrote: > Hi, > > Hendrik Boom writes: > > > So is this what I should have in my /etc/apt/sources.list to upgrade > > from jessie to ascii? > > > > deb http://pkgmaster.devuan.org/merged ascii main > > deb

Re: [DNG] upgrade to ascii

Hi, Hendrik Boom writes: > So is this what I should have in my /etc/apt/sources.list to upgrade > from jessie to ascii? > > deb http://pkgmaster.devuan.org/merged ascii main > deb http://pkgmaster.devuan.org/merged ascii-updates main > deb http://pkgmaster.devuan.org/merged ascii-security main >

Re: [DNG] upgrade to ascii

On 31-12-17 19:34, Antony Stone wrote: On Sunday 31 December 2017 at 19:02:41, Hendrik Boom wrote: So is this what I should have in my /etc/apt/sources.list to upgrade from jessie to ascii? deb http://pkgmaster.devuan.org/merged ascii main deb http://pkgmaster.devuan.org/merged ascii-updates

Re: [DNG] upgrade to ascii

On Sunday 31 December 2017 at 19:02:41, Hendrik Boom wrote: > So is this what I should have in my /etc/apt/sources.list to upgrade > from jessie to ascii? > > deb http://pkgmaster.devuan.org/merged ascii main > deb http://pkgmaster.devuan.org/merged ascii-updates main > deb

[DNG] upgrade to ascii

So is this what I should have in my /etc/apt/sources.list to upgrade from jessie to ascii? deb http://pkgmaster.devuan.org/merged ascii main deb http://pkgmaster.devuan.org/merged ascii-updates main deb http://pkgmaster.devuan.org/merged ascii-security main deb

Re: [DNG] Upgrade to ascii not possible?

Yevgeny Kosarzhevsky [2017-10-13 03:57]: > You are right, it looks like mirrors aren't updated. > When I replaced auto.mirror.devuan.org/merged/ > with packages.devuan.org/devuan/ > , the upgrade has worked, however >

Re: [DNG] Upgrade to ascii not possible?

Antony Stone [2017-10-12 18:11]: > So, you're only seeing 1.46+devuan1.0 > On 12 October 2017 at 21:01, Svante Signell wrote: > On Thu, 2017-10-12 at 08:47 -0400, fsmithred wrote: >> 1.46+devuan1.0 0 >> 100 http://auto.mirror.devuan.org/merged/ ascii/main amd64 Packages >

Re: [DNG] Upgrade to ascii not possible?

You are right, it looks like mirrors aren't updated. When I replaced auto.mirror.devuan.org/merged/ with packages.devuan.org/devuan/, the upgrade has worked, however I've gotten 300+ orphaned packages. On 13 October 2017 at 00:28, fsmithred wrote: > On 10/12/2017 11:51 AM,

Re: [DNG] Upgrade to ascii not possible?

On 10/12/2017 11:51 AM, Yevgeny Kosarzhevsky wrote: > On 12 October 2017 at 23:37, Antony Stone < > antony.st...@devuan.open.source.it> wrote: > >> >>> I am trying to upgrade from devuan jessie and get unresolved deps for >>> rsyslog. aptitude shows: depends on init-system-helpers >= 1.47~ >>>

Re: [DNG] Upgrade to ascii not possible?

On Thursday 12 October 2017 at 17:51:44, Yevgeny Kosarzhevsky wrote: > On 12 October 2017 at 23:37, Antony Stone < > > antony.st...@devuan.open.source.it> wrote: > > > I am trying to upgrade from devuan jessie and get unresolved deps for > > > rsyslog. aptitude shows: depends on

Re: [DNG] Upgrade to ascii not possible?

On 12 October 2017 at 23:37, Antony Stone < antony.st...@devuan.open.source.it> wrote: > > > I am trying to upgrade from devuan jessie and get unresolved deps for > > rsyslog. aptitude shows: depends on init-system-helpers >= 1.47~ > > (UNAVAILABLE) > > What do you get for each of: > > aptitude

Re: [DNG] Upgrade to ascii not possible?

On Thursday 12 October 2017 at 17:24:42, Yevgeny Kosarzhevsky wrote: > Hello, > > I am trying to upgrade from devuan jessie and get unresolved deps for > rsyslog. aptitude shows: depends on init-system-helpers >= 1.47~ > (UNAVAILABLE) What do you get for each of: aptitude search

Re: [DNG] Upgrade to ascii not possible?

Hello, I am trying to upgrade from devuan jessie and get unresolved deps for rsyslog. aptitude shows: depends on init-system-helpers >= 1.47~ (UNAVAILABLE) On 12 October 2017 at 21:01, Svante Signell wrote: > On Thu, 2017-10-12 at 08:47 -0400, fsmithred wrote: > > On

Re: [DNG] Upgrade to ascii not possible?

On Thu, 2017-10-12 at 08:47 -0400, fsmithred wrote: > On 10/11/2017 08:15 PM, Yevgeny Kosarzhevsky wrote: > > Hello, > > > > I've stuck on upgrading to ascii as there is no init-system-helpers > > available. > > Is there any solution? > > > > I see it in ascii main repo. What error message are

Re: [DNG] Upgrade to ascii not possible?

On 10/11/2017 08:15 PM, Yevgeny Kosarzhevsky wrote: > Hello, > > I've stuck on upgrading to ascii as there is no init-system-helpers > available. > Is there any solution? > I see it in ascii main repo. What error message are you getting? 1.46+devuan1.0 0 100

[DNG] Upgrade to ascii not possible?

Hello, I've stuck on upgrading to ascii as there is no init-system-helpers available. Is there any solution? -- Regards, Yevgeny ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng