[DNG] New Chimaera torrent file needs seeders.

[fsmithred via Dng]

There's a new torrent file for chimaera to include the updated live isos.
All the installer isos are unchanged and still at 4.0.0. The four live
isos are 4.0.2 and include a bugfix for the live installer.

Please seed. Thanks.

Here's the torrent file:
https://files.devuan.org/devuan_chimaera.torrent

There's a magnet link at the bottom of this page:
https://www.devuan.org/get-devuan


fsmithred

___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] connman missing from system menu

[fsmithred via Dng]

On 8/17/22 06:20, Hendrik Boom wrote:
> connman is missing from the system menu of my 32-bit laptop running chimaera.
> I have installed:
> connman-gtkverion 1.1.1+git20180626.b72c6ab-2
> connmanversion 1.36-2.2
> connman-uiversion 0-20150623-1
> The menu item is absent from the system menus in lxqt, and in xfce.
> What am I missing?
> 

> What am I missing?  Why isn't there a menu item for connman in the system 
> menu tree for either xfce or lxqt?
> 
> Shouldn't connman contain the menu item?
> 
> -- hendrik
> ___

In xfce go to Settings, Session and Startup, Application Autostart and add
connman-ui-gtk

There should be something similar in lxqt. In lxde, it's under
Preferences, Default applications for LXSession, Core applications,
Network GUI.

fsmithred
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] booting devuan minimal live on MSI laptop

[fsmithred via Dng]

Here's a devuan chimaera minimal-live iso with grub-efi-amd64-signed.
Please let me know if it works with secure boot. Thanks.

fsmithred

https://get.refracta.org/files/experimental/devuan_chimaera_4.0.0-signed_amd64_minimal-live.iso

___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] booting devuan minimal live on MSI laptop

[fsmithred via Dng]

On 4/20/22 20:55, Gregory Nowak via Dng wrote:
> So, remastering the minimal live image to have a valid secure boot
> signature seems the simplest way forward. Any help on figuring out on
> how to get a valid signature, and remastering the iso image would be
> much appreciated.

Sorry, I just saw this today. I have no experience with secure boot, but I
can make a minimal-live iso that has the signed version of grub-efi-amd64
and post the link for you. You can let me know if it works.

Thanks,
fsmithred

___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Chimaera installation issue (regulatory.db)

[fsmithred via Dng]

On 4/17/22 14:40, al3xu5 via Dng wrote:
> Hi
> 
> This is to report an istallation issue with Chimaera (net install).
> 
> The setup process halted at the beginning asking the "firmware"(???)
> package for 'regulatory.db'.
> 
> After some investigation I found it is related to a wireless-regdb package:
> 

> 
> Maybe this should be handled by the setup program.
> 
> Regards
> al3xu5
> 

That initial question about firmware is a stumbling block for many. Most
people should ignore it and proceed. The installer isos contain firmware
packages and will install them if the hardware needs it.

wireless-regdb_2020.04.29-2_all.deb is in the chimaera netinstall isos.

There are some situations that require adding the firmware from removable
media at the beginning of the install. Certain broadcom wireless devices
require an internet connection to download the actual firmware. The
firmware package in the repo is just an installer.
A laptop without an ethernet port would require the user to supply the
firmware at the beginning of the install, so we can't remove that question.

fsmithred
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

[DNG] Daedalus minimal-live sneak preview

[fsmithred via Dng]

First daedalus minimal-live isos are ready for testing and are available here:
https://files.devuan.org/devuan_daedalus/minimal-live/
or from your favorite iso mirror:
https://www.devuan.org/get-devuan

As usual, some packages no longer exist. Here's the list:

minimal-live changes for Daedalus

ftp is replaced with ftp-ssl
netcat is replaced with netcat-traditional (next build will have
netcat-openbsd)
calcurse is replaced with w2do
ninvaders is replaced with open-invaders
hasciicam is gone.
firmware-ath9k-htc is gone.

The amd64 iso will boot and install in either uefi or bios mode. The live
system has grub-efi-amd64 installed, but if you boot in bios mode, the
installer will find grub-pc and install it.

fsmithred

___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] vdev in chimaera

[fsmithred via Dng]

On 2/7/22 06:35, Didier Kryn wrote:
> Le 07/02/2022 à 08:29, aitor a écrit :
>> I've uploaded new iso images fixing a bug related to the last change in
>> simple-netaid for
>> compatibility with static ip addresses, that involved the response to
>> routing table netlink
>> events triggered by other processes. The images come with vdev by
>> default. Next step will be
>> to write a runit script for ifupdown that intend to solve the problem of
>> the still remaining
>> (at least booting with vdev) long delayed boot time when using
>> "allow-hotplug "
>> stanzas in /etc/network/interfaces.
> 
>     The long delay is also present with sysvrc. It can be supressed by
> just removing the "allow-hotplug" line, without replacing it by an "auto"
> line, and relying on ifplugd or netplug to detect the presence of the
> carrier and trigger the configuration of the interface. The delay is
> suppressed because 'ifup -a' does not find any interface to bring up and
> carrier to wait for; and then ifplugd/netplug brings them up only when the
> carrier is detected. Dunno if simple-netaid can play the role of ifplugd
> or netplug.
> 
> --     Didier
> 

I keep updating your check-link-state.patch on /etc/network/interfaces. It
seems to still be working with allow-hotplug.

The original discussion on DNG is gone, but I saved part of it here:
https://dev1galaxy.org/viewtopic.php?pid=15493#p15493

I think the line numbers are right for chimaera, but I always edit this
manually.

--- networking.orig 2021-11-08 08:47:47.520020285 -0500
+++ patches/networking.patched  2019-12-14 11:13:07.842536000 -0500
@@ -112,7 +112,13 @@
done)
if [ -n "$ifaces" ]
then
-   ifup $ifaces "$@" || true
+   # link detection does not work unless we up the link
+   ip link set "$iface" up || true
+   if [ "$(cat /sys/class/net/$link/operstate)" = up ]
+   then
+   echo "$iface"
+   fi
+
fi
 fi
 }


___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

[DNG] test message

[fsmithred via Dng]

Sorry for the noise.

Don't reply. I made other arrangements, thanks.

fsr
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] EFI boot not found, partially solved in gnuinos (Was: 1st boot failed but repaired OK)

[. fsmithred via Dng]

On 12/21/21, aitor  wrote:
> Hi,
>
> On 21/12/21 19:55, aitor wrote:
>>
>> Hi Ralph,
>>
>> On 21/12/21 12:19, Ralph Ronnquist via Dng wrote:
>>> On Tue, 21 Dec 2021 01:44:39 +0100
>>> aitor  wrote:
 ...
 The outcome is that i've been compelled to turn back the distributor
 to its default ID=devuan, and i'm rebuilding the images of gnuinos
 chimaera right now so that they will work properly in UEFI mode
 without workarounds during the first boot on the part of users.

 I wonder, to this regard, what is the trick in Devuan to put in place
 the distributor ID without the need of hijacking the boot loader...
>>> ... doesn't "scripts/magic-touch" tell the story?
>> Looking at the script, it seems that i must define a new variable:
>> GNUINOSCFG=/target/boot/efi/EFI/gnuinos/grub.cfg
>> and copy the content to $DEBIANCFG in the same way you're doing with
>> $DEVUANCFG.
>> Yes, it seems the way to go...
>>
>> I'll tell you, thanks!
>
> Oops, I knew about the --efi-directory argument for grub-install, which
> defines the
> root partition of the EFI system, but there is also another one that i was
> overlooking
> up till now:
>
> --bootloader-id=ID
>
> I found it looking at the code of grub-install.c in grub2. The value of this
> argument has
> preference over the value defined in os-release.
>
> Cheers,
>
> Aitor.
>
>
>

Another way to fix it in the installed system is to remove
grub-efi-amd64-signed if you don't use Secure Boot. Then you don't
need /boot/efi/EFI/debian.

fsmithred
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] grub-efi-amd64-signed bug: hardcoded link -> unbootable system

[fsmithred via Dng]

On 8/6/21 5:57 PM, Adrian Zaugg wrote:
> In der Nachricht vom Friday, 6 August 2021 03:25:58 CEST steht:
>> Which Beowulf iso did you use? I think we fixed this in the 3.1.1
>> point-release isos, but you still may hit it on an upgrade.
> 
> It happened on upgraded systems.
> 
> Thanx for fixing the ISO.
> 
> Don't you see a way to prevent the issue happening on upgraded systems, e.g. 
> blacklisting grub-efi-amd64-signed or using another mechanism?
> 
> Regards, Adrian.
> 
> BTW: I uninstalled grub-efi-amd64-signed without concern because of Debian 
> bug 
> #906124 [https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906124]
>  
> 

If grub-efi-amd64-signed is getting installed on upgrade from ascii to
beowulf, one way I can think of preventing it is to pin that package
before doing the upgrade. For example:

in /etc/apt/preferences.d/no-signed

Package: grub-efi-amd64-signed
Pin: release n=beowulf
Pin-Priority: -1

Aha! I see that grub-efi-amd64-bin Recommends grub-efi-amd64-signed, so
another way to block it is to block Recommends.

in /etc/apt/apt.conf.d/00norecommends

APT::Install-Recommends "no";

or else add '--no-install-recommends' to a command-line install.

I can't think of any clean ways for us to do this for the end user. Maybe
someone else has a better idea.

fsmithred
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] grub-efi-amd64-signed bug: hardcoded link -> unbootable system

[fsmithred via Dng]

On 8/4/21 7:17 AM, Adrian Zaugg wrote:
> Dear list
> 
> Beowulf is hit hard by a problem with hardcoded path in grub-efi-amd64-signed 
> leading to an unbootable system as reported on this list and on dev1galaxy 
> (manual intervention in certain configurations needed to boot). This problem 
> also exists on fresh installs of beowulf, as it seems. Is there some effort 
> under way to fix the problem? 
> 
> Best regards, Adrian.
> 
> 
> Work-around (thanks to fsmithred):
> 
> # apt purge grub-efi-amd64-signed
> ...
> # apt install --reinstall grub-efi-amd64
> ...
> 

Which Beowulf iso did you use? I think we fixed this in the 3.1.1
point-release isos, but you still may hit it on an upgrade.

fsmithred



___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] RFC: minimal-live iso changes for chimaera

[fsmithred via Dng]

On 7/20/21 11:15 AM, terryc wrote:
> On Tue, 20 Jul 2021 09:46:09 -0400
> fsmithred via Dng  wrote:
> 
>> The following packages are not in chimaera. I'm removing them from the
>> minimal-live isos so that they will build successfully.
>>
>> Suggestions for replacement packages are welcome.
>>
>> bittornado
>> termsaver
> 
> I don't know about bittornado, but chimaera (main, contrib and
> non-free) has
> 
> transmission,
> deluge,
> ctorrent,
> ktorrent,
> qbittorrent and
> rtorrent
> from an "apptitude search torrent" result.
> 
> I've used transmission in the past but currently use deluge. Both have
> a gui, whereas AFAIR them as relatively klunky.  YMMV.
> 
> How soon is the deadline for choice?
> 

I don't know when the deadline is. I just started trying to make alpha
minimal-live isos today. Go ahead and play, then let me know what you think.

Lack of a choice of torrent software won't stop me from building isos. I'm
sure the ones I build now won't be the last.

Reminder: The minimal-live iso has no gui. I know for sure that
transmission-cli is on the list. I don't know what others work on console.

fsmithred
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

[DNG] RFC: minimal-live iso changes for chimaera

[fsmithred via Dng]

The following packages are not in chimaera. I'm removing them from the
minimal-live isos so that they will build successfully.

Suggestions for replacement packages are welcome.

bittornado
termsaver

Thanks,
fsmithred

___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] desktop-live chimaera isos

[fsmithred via Dng]

On 7/16/21 3:55 PM, fsmithred wrote:
> Chimaera desktop-live isos are ready for testing. They can be downloaded
> from files.devuan.org or from your favorite iso mirror.
> https://www.devuan.org/get-devuan
> 
> Let me know if the desktop does not look like this.
> https://transfer.sh/1C8R6Pg/Screeshot_desktop-live-chimaera.png
> We're getting different results with the i386 isos on different machines
> booting in qemu. One is amd64 hardware, other is i386.


Correction: One is amd64 OS and the other is i386 OS. Hardware is 64-bit
capable in both cases.

fsr


___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

[DNG] desktop-live chimaera isos

[fsmithred via Dng]

Chimaera desktop-live isos are ready for testing. They can be downloaded
from files.devuan.org or from your favorite iso mirror.
https://www.devuan.org/get-devuan

Let me know if the desktop does not look like this.
https://transfer.sh/1C8R6Pg/Screeshot_desktop-live-chimaera.png
We're getting different results with the i386 isos on different machines
booting in qemu. One is amd64 hardware, other is i386.

Thanks,
fsmithred
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Script to migrate buster desktop to beowulf v1.6

[fsmithred via Dng]

On 4/14/21 10:15 AM, tito wrote:
> On Wed, 14 Apr 2021 09:57:38 -0400
> fsmithred via Dng  wrote:
> 
>>
>> It's currently opt-out. You must select Expert install to avoid
>> non-free and to choose your sources. Something about how the
>> installer works makes it easier to do it this way rather than the
>> reverse. And it's also easier for the non-experts to get their
>> hardware working this way.
>>
>> fsmithred
> 
> So I will add them by default. 
> 
> Ciao,
> Tito
> 

I can't think of a good way to do it, either. I just substitute buster
with beowulf, but that only works because I know what's in my
sources.list. That could break all kinds of third-party repos.

Adding non-free where it's not wanted will anger some people. Removing it
where it's wanted might break some systems.

This might be a good one to ask the users.

fsmithred
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Script to migrate buster desktop to beowulf v1.6

[fsmithred via Dng]

On 4/14/21 9:50 AM, Hendrik Boom wrote:
> On Wed, Apr 14, 2021 at 09:02:54AM -0400, Steve Litt wrote:
>> tito via Dng said on Tue, 13 Apr 2021 22:03:02 +0200
>>
>>
>>> 2) should non-free and contrib repos be added to sources.list
>>>or should that be left to the user
>>
>> I'm not sure whether my answer is responsive to your question or not,
>> but here goes...
>>
>> I believe enough non-free and contrib stuff should be available at
>> install time (or boot time on a live CD/flash) that the user doesn't
>> need to put in additional media to get boot, network, video and sound
>> working. And I believe any non-free and contrib stuff should, by
>> default, be installed at install time, but before installation the user
>> should be given the option of opting out of this non-free/contrib
>> stuff, so if he/she only uses free software, he/she can maintain that
>> principle in the installation.
>>
>> Stating it the inverse way, I HATE these installs that bomb because
>> there's no FSF-satisfying drivers, firmware or software to handle my new
>> laptop's weird hardware. And those distros that do that, their mailing
>> lists always say "well just put in a thumb drive with the
>> drivers/firmware!" How the KFDWOJMFOW do I know which drivers and
>> firmware? I think free software purist snobs drive more people back to
>> Windows than cleanse people of their non-free ways.
> 
> Yes, the nonfree software which is necessary to getting hardware to work
> should be installed unless the user explicitly says not to do it.
> He may be committed to freedom, but may have been bamboozled by the 
> hardware vendor or has been given a free (but not libre) piece of hardware 
> by a doting aunt for his birthday.
> 
> That said, he should have to opt in to receiving other nonfree software.
> That should be a separate choice.  He may well want to be as independent of 
> nonfree software as practical.
> 
> And let me remind you, there is precious little completely libre 
> computer hardware around.  Until there is, even the most extreme 
> libre/freedom advocate will have nonfree stuff somewhere in the stack.
> 
> Yes, I'm hoping for the longterm success of the libre-soc project.
> 
> -- hendrik
> ___

It's currently opt-out. You must select Expert install to avoid non-free
and to choose your sources. Something about how the installer works makes
it easier to do it this way rather than the reverse. And it's also easier
for the non-experts to get their hardware working this way.

fsmithred


___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] BUG in desktop-base

[fsmithred via Dng]

On 4/13/21 6:13 PM, tito via Dng wrote:
> On Tue, 13 Apr 2021 23:19:06 +0200
> aitor  wrote:
> 
>> Hi Tito,
>>
>> On 13/4/21 8:08, tito via Dng wrote:
>>> cat /sys/class/drm/card0-Virtual-1/modes
>>> preferred
>>> 2560x1600
>>> 1920x1440
>>> 1856x1392
>> The origin of the warning lies in the first line equal to
>> "preferred", as you pointed out:
>>
>> /var/lib/dpkg/info/desktop-base.postinst: line 30: [: preferred:
>> integer expression expected
>>
>> Imho, it should be considered a bug because the script ignores the 
>> preferred value, going ahead with the *else* statement.
>>
>> Cheers,
>>
>> Aitor.
>>
>>
> 
> Hi,
> so next question is: is it devuan or debian bug?
> 
> Ciao,
> Tito
> ___

Devuan. We fork desktop-base. You could file a bug report, or you could
just tell me. I have control over line 30 and all the others. What should
I do with it? Where and how can the script get the preferred value?

Thanks,
fsmithred

___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Default logins for ARM images?

[fsmithred via Dng]

On 4/2/21 11:13 PM, Gregory Nowak via Dng wrote:
> On Fri, Apr 02, 2021 at 07:57:21PM -0500, goli...@devuan.org wrote:
>> Greg,
>>
>> Have you not seen this thread on the forum? Because it is not a community
>> project, it is presented differently that the official devuan isos.
>>
>> Location is: Index » ARM Builds » Installer images for armel, armhf and
>> ppc64 need testing
>>
>> https://dev1galaxy.org/viewtopic.php?id=3351
>>
>> There is a link to that thread on the Download page of the website.
>>
>> golinux
> 
> Yes, I saw that thread. However, the links point to
> pkgmaster.devuan.org. The first mention of arm-files.devuan.org is in
> a post by garyz.dev1, which is quite a way down in the discussion. The readme
> file with the login credentials for the embedded images doesn't seem to be
> anywhere on pkgmaster.devuan.org as far as I can tell.
> 
> Greg
> 
> 

The linked thread is about the installer images, not the embedded images.
I think we need to do two simple things.

- Link arm-files.devuan.org from the main site as Greg suggests.
- Make a sticky thread in the forum pointing to arm-files.devuan.org

fsmithred
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Strange behaviour with last version of grub

[fsmithred via Dng]

On 3/4/21 11:08 PM, wirelessduck--- via Dng wrote:
> 
> 
>> On 5 Mar 2021, at 03:23, viverna  wrote:
>>
>> Yesterday I updated one of my computers with apt-get upgrade. This packages 
>> are upgraded:
>>
>> grub-common grub-pc grub-pc-bin grub2-common
>>
>> dpkg install from version 2.02+dfsg1-20+deb10u3 to version 
>> 2.02+dfsg1-20+deb10u4
>>

>>
>> And now the question. Has anyone reported the error in Devuan? Has anyone 
>> haved this problem?
> 
> Seems to be a bit of news about the latest update.
> https://9to5linux.com/patches-for-multiple-new-grub2-security-flaws-start-rolling-out-to-linux-distros-update-now
> 
> The changelog mentions changes to secure boot. Could that be related to the 
> issue?
> 
> https://metadata.ftp-master.debian.org/changelogs//main/g/grub2/grub2_2.02+dfsg1-20+deb10u4_changelog
> 
> 

I've been able to reproduce the problem in two systems that boot uefi,
(one beowulf, one chimaera) but only after I installed
grub-efi-amd64-signed. It's not necessary to have secure boot enabled; you
just need the signed package. I've been avoiding that package for over a
year because it has caused this problem in the past. If you don't need
secure boot, just use grub-efi-amd64.

I could not reproduce the problem on a system that boots legacy bios and
uses grub-pc.

fsmithred
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Devuan Beowulf 3.1.0 point release

[fsmithred via Dng]

On 2/16/21 1:43 AM, spiralofhope wrote:
> On Sun, 14 Feb 2021 20:36:58 -0500
> fsmithred via Dng  wrote:
> 
>> Devuan Beowulf 3.1.0 point release
> 

> 
> However,
> 
> devuan_beowulf_3.1.0_amd64_minimal-live.iso does NOT work with
> ventoy-1.0.35 (installed via Windows 10).
> 
> I get:
> 
>> No bootfile found for UEFI!
>> Maybe the image does not support X64 UEFI!
> 
> I assume it's working as intended.  :)
> 
> 

Yes, the minimal-live is bios-boot only. I made an unofficial uefi
minimal-live iso for 3.0.0 but that doesn't seem to be working now. I'll
have to try again.

fsmithred

___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

[DNG] Devuan Beowulf 3.1.0 point release

[fsmithred via Dng]

Devuan Beowulf 3.1.0 point release


Dear Init Freedom Lovers

Once again the Veteran Unix Admins salute you on this day commemorating
six years since the first Devuan pre-alpha Valentine's Day release in 2015!

Devuan Beowulf 3.1.0 point release installer ISOs, desktop-live, and
minimal-live isos are now available. Note that ARM and virtual images are
not updated in this release.
What’s new in this point release:


Installation:

The installer now offers a choice of three init systems. runit has been
added, along with sysvinit and openrc.

If you would like to select an alternate bootloader (lilo) or exclude
non-free firmware, you must select one of the Expert install options.

The recommended default mirror is now deb.devuan.org. If you would like to
use a country code mirror, please check
https://pkgmaster.devuan.org/mirror_list.txt to see if there is one
suitable for your needs.


Security updates and bug fixes:

linux-image-4.19.0-14 Debian 4.19.171-2 (2021-01-30)

firefox-esr 78.7.0esr-1~deb10u1

lightdm 1.26.0-4+devuan1 (fixes bugs related to power
buttons and accessibility features)

New package, debian-pulseaudio-config-override corrects problem of
pulseaudio being off by default

And many more. (See https://www.debian.org/security/2020/ and
https://www.debian.org/security/2021/)


Documentation

Please read the Release Notes carefully:
https://files.devuan.org/devuan_beowulf/Release_notes.txt

Beowulf 3.0.0 announcement:
https://www.devuan.org/os/announce/beowulf-stable-announce-060120.html


Download

https://files.devuan.org/devuan_beowulf/

https://www.devuan.org/get-devuan (mirrors)

The latter URL also includes information about the official Devuan package
repositories, an ISO selection guide, and links to installation guides.
What about ARM and virtual images?

ARM and Virtual Machine images are provided by the greater Devuan
community rather than as part of official releases. Users are being
encouraged to build and contribute ARM images for their particular
hardware. This will increase the variety of images available and allow the
release schedule of the installer ISOs to move forward more quickly.

Images can be built using using arm-sdk and vm-sdk:
https://www.devuan.org/os/distro-kit

Arm-related discussion happens at #devuan-arm (Freenode) and
https://dev1galaxy.org/viewforum.php?id=24


Resource Channels

Mailing list: https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
IRC: #devuan #devuan-dev (Freenode)
Forum: https://dev1galaxy.org
Source code: https://git.devuan.org
Bug tracker: https://bugs.devuan.org
Popularity contest: https://popcon.devuan.org
Package information: https://pkginfo.devuan.org
Press contact: free...@devuan.org


Chimaera coming soon

The Devuan development team will now focus on polishing our fourth
release, codename “Chimaera”, minor planet no. 623.


Appreciation

We wish to thank all of you for the incredible support given to this
development effort, which continues to make Devuan a useful and reliable
base distribution.

To support the Devuan project you can donate at:

https://www.devuan.org/donate (includes financial reports)

or take up one of the tasks listed at:

https://dev1galaxy.org/viewtopic.php?pid=1380#p1380

Happy hacking ;^)
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] install in private partition scheme ?

[fsmithred via Dng]

On 2/3/21 4:43 PM, Radisson via Dng wrote:
> 
> Am 03.02.21 um 02:59 schrieb fsmithred via Dng:
>>
>> You can have a separate /home or /boot, but if you want to  re-use an old
>> /home partition, you must do that manually after the install.
> I would like to setup a server, with separate /var and raid and so on. The
> box i use for testing is clean, no need to be careful.
> What is the recomended way to create a complex setup and install ?
> 
> It seems that the way via USB stick is not the right idea.
> 

The usb stick is not the problem. The live installer won't do what you
want. Use one of the installer isos - netinstall or server iso are best
choices for what you want, but even the desktop dvd will do it.

fsmithred

___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] install in private partition scheme ?

[fsmithred via Dng]

On 2/2/21 7:48 PM, Gregory Nowak via Dng wrote:
> On Tue, Feb 02, 2021 at 04:57:35PM +0100, rad via Dng wrote:
>> The programm calls  refrectinstaller-wrapper.sh
> 
> OK, it sounds like you're using Refracta, which is another
> distribution based on devuan.
> 
>>
>> so what program should i start from the USB-stick ?

Sorry I tuned into this so late. I would guess that rad is using the
desktop-live iso, which does use refractainstaller.

rad, what partition layout did you want? What do you mean by "private
partition"?

The installer on the live isos just copies the running live system to hard
drive. Take a look at the install guide (also on the desktop). There's a
help page you can access from inside the installer.

You can have a separate /home or /boot, but if you want to re-use an old
/home partition, you must do that manually after the install.

fsmithred
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] TB and Enigmail

[fsmithred via Dng]

On 10/23/20 3:04 AM, Simon Walter wrote:

> From what I understand, I now have to maintain two copies of my key rings:
> the regular one and the one *inside* TB.
> 

Hm.. I was already a little nervous about keeping one copy of the keyring
on the hard drive.

> 
> Has any of you TB users (assuming there are any here} done this migration?
> How is the new shiny? Is it fine? Shall I forget about TB? Any suggestions
> of what could replace it?

Nope. This is the first I've heard of it. This is not the first I've heard
of problems with enigmail. Over the past 5 years or so, it seems like it
only works about half the time. And I mean it goes months without being
available for installation.

I do still use Thunderbird for my mail, but a few months ago I installed
claws mail on my laptop just so I could send an encrypted email. It works
fine there. I might eventually switch over to using claws full-time.

fsmithred

___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Complete system HDD encryption w/o LLVM.

[fsmithred via Dng]

On 9/29/20 9:58 AM, Андрей via Dng wrote:
> Question is, Is it possible to to achieve same goal without LLVM --
> i.e. to partition system HDD with fdisk, and then still have full
> encryption?
> 

Another way to do it is with the live-isos (using refractainstaller).
Select encryption for the root partition and do not select a separate
partition for /boot.

You can also select a separate partition for /home, and if you encrypt
that, you will have to enter the passphrase to unlock each partition. You
can change that to a keyfile after the install.

The default for the live installer is to use a swap file on the root
partition, so that will be part of the encrypted filesystem.

One thing I find annoying with having /boot encrypted is that grub is very
slow to respond to the passphrase. And then you have to enter it again for
the root partition.

fsmithred


0xA73823D3094C5620.asc
Description: application/pgp-keys
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Failed run live usb iso

[fsmithred via Dng]

On 9/26/20 3:09 AM, Budi via Dng wrote:
> Did download this:
> [b]devuan_beowulf_3.0.0_amd64_desktop-live.iso[/b]
> (1.2GB)
> 
> and did:
> [code]sudo dd if=devuan_beowulf_3.0.0_amd64_desktop-live.iso
> of=/dev/sdc bs=4096[/code]
> 
> did reboot it, but got sort of this output:
> 
> Error : cannot run Apparmor   ... failed
> ...
> ...
> (Other errors)
> 
> how to solve ? Thanks before.


Check sha256sum on the iso to make sure it downloaded correctly.

Make sure the boot command contains apparmor=0

Maybe try it on a different usb stick.

fsmithred




0xA73823D3094C5620.asc
Description: application/pgp-keys
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] terminology

[fsmithred via Dng]

On 8/24/20 10:32 AM, Hendrik Boom wrote:
> 
> Mu memory may be failing ne after almost half a century, but I recall
> that the original Unix, way back in the early 70's,
> even directories could be read as files.  Not that there was 
> some hidden  trickery making them into files; instead there were 
> conventions how files could be treated as directories.
> 

I had to look up Plan 9, and in doing so, I found that "Everything is a
file" has its own wikipedia page. It says, "But file descriptors are also
created for things like anonymous pipes and network sockets via different
methods. Therefore a more accurate description of this feature is
Everything is a file descriptor."

And the page for File descriptor says, "In Unix-like systems, file
descriptors can refer to any Unix file type named in a file system. As
well as regular files, this includes directories, block and character
devices (also called "special files")"

fsmithred


0xA73823D3094C5620.asc
Description: application/pgp-keys
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] terminology

[fsmithred via Dng]

On 8/23/20 6:37 PM, goli...@devuan.org wrote:
> On 2020-08-23 17:20, Hendrik Boom wrote:
>>
>> I suspect that's what I'm going to have to do.
>> Unless something better comes along I'm calling it a Thing.
>> I do hope something better comes along.
>>
>> -- hendrik
> 
> From my early Linux days I remember discussion of "filesystem hierarchy". 
> Aren't directories and files just part of that organizational tree? They
> act as data containers.
> 

I was told that everything in linux is a file, even your hardware.

fsmithred


0xA73823D3094C5620.asc
Description: application/pgp-keys
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Can't get graphic output from qemu

[fsmithred via Dng]

On 7/13/20 12:37 AM, Ralph Ronnquist via Dng wrote:
> Joel Roth via Dng wrote on 13/7/20 1:42 pm:
>> Hi list,
>>
>> Since upgrading to ascii, I don't get a graphic window by default
>> as before.  Instead, qemu tries (and fails) to make a VNC connection.
>>
>> I can run qemu-system-x86_64 -display curses for text only.
>> The sdl and gtk options to -display which I think should
>> invoke graphic output, instead generate an error message of
>> being unsupported.
>>
>> What do I need to do to get the regular graphic output?
> 
> Afaict even for ascii, qemu has progressed away from offering a built-in
> display. I don't know what the necessary improvements where that accidentally
> rendered the built-in display non-functional, but now a separate display seems
> be the only option; vnc or spice. Plus that the serial console option is still
> available.
> 
> Ralph.


I don't know what display you guys are expecting to see, but when I run
qemu, the VM opens in a plain old window that has a title bar and menu
bar, just like it always has. The menu items are Machine and View.

qemu-system-x86_64 -enable-kvm -m 2048 -vga std -cdrom example.iso

I did run into a situation in ascii where qemu required vnc, and I don't
recall what happened to change that back to the old behavior. Maybe
installing qemu-system-gui is what fixed it.

fsmithred



0xA73823D3094C5620.asc
Description: application/pgp-keys
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] eudev-related problems after Beowulf upgrade

[fsmithred via Dng]

On 6/15/20 12:15 PM, David Kuehling wrote:
> 
> This is my diff:
> 
> --- /etc/init.d/eudev 2019-02-09 13:22:24.0 +0100
> +++ /tmp/eudev2020-06-15 17:59:00.384481497 +0200
> @@ -210,6 +210,7 @@
>   sleep 15
>  fi
>  
> +sleep 1s
>  log_action_begin_msg "Synthesizing the initial hotplug events"
>  if udevadm trigger --action=add; then
>   log_action_end_msg $?
> 
> I just did another 5 boots and this patch indeed seems to fully fix the
> problem in my case.
> 
> If this does not work for you, maybe you need a longer delay?  If you
> boot from CD-ROM, then eudev (or other background processes) requiring
> some random seeks during startup may easily exceed 1s.
> 
> Does manually running 'udevadm trigger --action=add' after startup
> mitigate the problem in your case?
> 
> David
> 

Yes, running 'udevadm trigger --action=add' after startup works.

Adding 'sleep 10' where you put it also works. I had previously tried
putting it at the end of the start case, and that didn't work.

fsmithred


0xA73823D3094C5620.asc
Description: application/pgp-keys
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Jessie to Beowulf?

[fsmithred via Dng]

On 6/15/20 6:43 AM, Antony Stone wrote:
> On Monday 15 June 2020 at 12:30:36, Luciano Mannucci wrote:
> 
>> Hello everybody! Just a quick question:
>>
>> Can I upgrade my Jessie to Beowulf directly or I have to upgrade
>> to Ascii first?
> 
> I would expect it's exactly the same as Debian - you have to go from one 
> release to the next, you can't skip them.
> 
> 
> Antony.
> 

You probably can do it. I'm not sure if dev1fanboy tested that before
writing the upgrade guides, but possibly a combination of instruction in
'Upgrade from Devuan ASCII' and 'Migrate from Debian Jessie' would work.
https://devuan.org/os/install

Make sure you have backups of anything important.

fsmithred



0xA73823D3094C5620.asc
Description: application/pgp-keys
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] eudev-related problems after Beowulf upgrade

[fsmithred via Dng]

On 6/12/20 10:05 AM, David Kuehling via Dng wrote:
> 
>   - during startup, the LVM init.d-script hangs for a very long time
>   repeatedly outputting errors of the form
> 
>   WARNING: Device /dev/xxx not initialized in udev database even after
>   waiting 1000 microseconds.
> 

To get rid of the delays, edit /etc/lvm/lvm.conf and set these four
variables to zero:

devices {
# Disable scanning udev for md/multipath components.
# This is required with recent versions of lvm2, even if you use
another solution for
# your LV device nodes; without it lvm commands will stall for minutes
waiting for udev.
multipath_component_detection = 0
md_component_detection = 0
}
activation {
# Set to 0 to disable udev synchronisation (if compiled into the
binaries).
udev_sync = 0
# Set to 0 to disable the udev rules installed by LVM2
udev_rules = 0
}


>   - none of the alsa sound driver modules is loaded during boot, so I
>   end up with a Desktop that does not support audio
> 
>   - the amdgpu module is not loaded, so not 3-D acceleration
>   
> Comparing dmesg output between successful startup and failed startup,
> the following markedly differs:
> 
> In both cases, the line 'udevd[558]: starting eudev-3.2.7' appears twice
> in the dmesg output.  Differences happen after the second time it is
> printed.  In the "failed boot" case it merely outputs
> 
>    udevd[558]: starting eudev-3.2.7
>    lp: driver loaded but no devices found
>    ppdev: user-space parallel port driver
> 
> In the succesful case it outputs a whole lot of ACPI-related stuff and
> loads the sound-related modules:
> 

This problem was showing up in the live isos but only when booting from
optical media. It didn't happen when booting from usb (except for the
couple of times it did).

Workaround for now is to put the following line in /etc/rc.local:

/etc/init.d/eudev stop && /etc/init.d/eudev start


Another possible workaround is to edit /etc/init.d/eudev and replace
stop-start-daemon in the start command with just 'udevd -d' as described
in this post:
https://dev1galaxy.org/viewtopic.php?pid=22172#p22172

CAVEAT: I can't claim that either of these workarounds is better or worse
than the other, or even what all the possible effects are.

One other issue I had with the desktop-live isos was sometimes having no
keyboard or mouse on the destkop. That was solved by installing acpi-fakekey.

fsmithred


0xA73823D3094C5620.asc
Description: application/pgp-keys
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] release status, was: Re: Devuan Beowulf 3.0.0 released.

[fsmithred via Dng]

On 6/3/20 3:43 PM, Gregory Nowak wrote:
> 
> Since this topic came up, I have a couple non critical machines
> running jessie, and they still get updates. Is this a fluke, or is
> jessie still being supported. If jessie is still being supported, then
> how long is that planned to continue as of now? Thanks.
> 
> Greg
> 
> 

Jessie will be supported until June 2020, or any minute now.

fsmithred




0xA73823D3094C5620.asc
Description: application/pgp-keys
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] beowulf-stable-announce 404

[fsmithred via Dng]

On 6/1/20 8:44 PM, Gregory Nowak wrote:
> On Mon, Jun 01, 2020 at 11:45:44AM -0500, goli...@devuan.org wrote:
>> Not enough hands on deck. The new website was release while I was sleeping
>> so that page hasn't been created yet and I won't be able to get to it for
>> several hours.  You are welcome to join the Devuan development team at any
>> time.
>>
>> golinux
> 
> Hmm, I thought we were going to have a second beta to make sure the
> bugs reported during the first beta really are squashed.
> 
> Greg
> 
> 

There were a couple more betas. I guess we failed to mention that on this
list. Most of the activity was in the forum, irc and bug reports.

I think we squashed all the bugs. Guess we'll find out.

fsmithred



0xA73823D3094C5620.asc
Description: application/pgp-keys
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Waterfox issues under Devuan ASCII

[fsmithred via Dng]

On 4/12/20 2:32 AM, Edward Bartolo via Dng wrote:
> Hi,
> 
> I will upgrade to Beowulf. As usual, I will upgrade dpkg, apt,
> aptitude and the kernel first and then reboot with the new versions.
> Then, I will do an "apt-get dist-upgrade".
> 
> If there are more critical packages which need to be upgraded first,
> please post. The above worked in Debian when there were dist-upgrade
> issues.
> 

See the upgrade guide:
https://beta.devuan.org/os/documentation/dev1fanboy/en/upgrade-to-beowulf


___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] ASCII 2.1 to Beowulf: Report + questions

[fsmithred via Dng]

On 3/22/20 12:53 PM, al3xu5 / dotcommon wrote:
> Hi all
> 
> Yesterday I dist-upgrade ASCII 2.1 (MATE DM) to Beowulf, following [1].

> 
> Now I have: 
> ~~~
> $ uname -a
> Linux computer0 4.6.0-0.bpo.1-rt-amd64 #1 SMP PREEMPT RT Debian 4.6.4-1~bpo8+1
> (2016-08-11) x86_64 GNU/Linux

You can do one of two things to get the beowulf kernel - either install
linux-image-amd64, which is a metapackage that will always install the
latest available kernel, or you can install the kernel by the full package
name, currently linux-image-4.19.0-8-amd64.

If you do the latter, stay alert to when -9 comes out. You won't get it
automatically.


> 2. Having upower installed, I have downgraded upower packages as suggested in
> [1], to avoid problems like bug#394 [2] which seems mainly related to 
> cinnamon.
> But I do not have cinnamon... So what I should do? Downgrade or not? If not,
> how to disable downgrading of those packages? 
> 

Take the downgrade. It's not really a downgrade; it's an upgrade to a
lower-numbered version. (We no longer need to fork upower.)

That's all I've got. Hope it helps.

fsmithred


___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] darkpurpy-grub theme on Beowulf

[fsmithred via Dng]

On 3/22/20 1:30 PM, J. Fahrner via Dng wrote:
> Am 2020-03-22 18:16, schrieb goli...@devuan.org:
>> I'm feeling the darkpurpy love! :)
> 
> You are right :-)
> 
>> But if all else
>> fails you can just replace the cinnabar elements with darkpurpy in
>> /usr/share/desktop-base.  That's how I got cinnabar grub working on my
>> jessie.
> 
> I tried to integrate darkpurpy-grub into update-alternatives but failed.
> In the end it was easiest for me to put the theme into /etc/default/grub


Exactly what did you copy into /etc/default/grub? I tried a couple things
and couldn't get it to work.

I did get it to work using update-alternatives. Maybe your way is easier
than this:

- Install clearlooks-phenix-darkpurpy-theme
- Make sure the following line is in /etc/default/grub

GRUB_THEME=/usr/share/desktop-base/grub-themes/desktop-grub-theme/theme.txt


Then run:
update-alternatives --install \
/usr/share/desktop-base/grub-themes/desktop-grub-theme desktop-grub-theme \
/usr/share/desktop-base/grub/themes/darkpurpy-grub 20

Generate a new boot menu:
update-grub

To change the slim theme:
update-alternatives --install \
/usr/share/slim/themes/desktop-slim-theme desktop-slim-theme \
/usr/share/slim/themes/devuan-curve-darkpurpy 20

To go back to cinnabar:
update-alternatives --config desktop-grub-theme
update-alternatives --config desktop-slim-theme

I didn't mess with the window theme or desktop background. Those are easy
to change in user settings.

fsmithred

___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Installer images for armel, armhf and ppc64 need testing

[fsmithred via Dng]

On 3/6/20 6:30 PM, fsmithred wrote:
> On 3/2/20 7:54 PM, fsmithred wrote:
>> We built beowulf installer images for armel, armhf and ppc64el. If you
>> have appropriate hardware, please test and report.
>>
>> armel (no mini.iso for these. I hope you know what to do.)
>> https://pkgmaster.devuan.org/devuan/dists/beowulf/main/installer-armel/current/images/
>>  
>> kirkwood/netboot/marvell/{dreamplug,guruplug,sheevaplug,sheevaplug-esata}
>>  kirkwood/netboot/seagate/dockstar
>>  orion/netboot/buffalo
>>
>> armhf
>> https://pkgmaster.devuan.org/devuan/dists/beowulf/main/installer-armhf/current/images/netboot/mini.iso
>>
>> ppc64el
>> https://pkgmaster.devuan.org/devuan/dists/beowulf/main/installer-ppc64el/current/images/netboot/mini.iso
>>
>> Thanks,
>> fsmithred
>>
> 
> 
> I installed from the ppc64el mini.iso in qemu today. That one works.
> Anyone else?
> 
> fsr
> 


arm64 has been added:
https://pkgmaster.devuan.org/devuan/dists/beowulf/main/installer-arm64/current/images/


fsr

___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Installer images for armel, armhf and ppc64 need testing

[fsmithred via Dng]

On 3/2/20 7:54 PM, fsmithred wrote:
> We built beowulf installer images for armel, armhf and ppc64el. If you
> have appropriate hardware, please test and report.
> 
> armel (no mini.iso for these. I hope you know what to do.)
> https://pkgmaster.devuan.org/devuan/dists/beowulf/main/installer-armel/current/images/
>   
> kirkwood/netboot/marvell/{dreamplug,guruplug,sheevaplug,sheevaplug-esata}
>   kirkwood/netboot/seagate/dockstar
>   orion/netboot/buffalo
> 
> armhf
> https://pkgmaster.devuan.org/devuan/dists/beowulf/main/installer-armhf/current/images/netboot/mini.iso
> 
> ppc64el
> https://pkgmaster.devuan.org/devuan/dists/beowulf/main/installer-ppc64el/current/images/netboot/mini.iso
> 
> Thanks,
> fsmithred
> 


I installed from the ppc64el mini.iso in qemu today. That one works.
Anyone else?

fsr

___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

[DNG] Installer images for armel, armhf and ppc64 need testing

[fsmithred via Dng]

We built beowulf installer images for armel, armhf and ppc64el. If you
have appropriate hardware, please test and report.

armel (no mini.iso for these. I hope you know what to do.)
https://pkgmaster.devuan.org/devuan/dists/beowulf/main/installer-armel/current/images/

kirkwood/netboot/marvell/{dreamplug,guruplug,sheevaplug,sheevaplug-esata}
kirkwood/netboot/seagate/dockstar
orion/netboot/buffalo

armhf
https://pkgmaster.devuan.org/devuan/dists/beowulf/main/installer-armhf/current/images/netboot/mini.iso

ppc64el
https://pkgmaster.devuan.org/devuan/dists/beowulf/main/installer-ppc64el/current/images/netboot/mini.iso

Thanks,
fsmithred

___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] why is polkit needed?

[fsmithred via Dng]

On 2/24/20 7:21 AM, Daniel Abrecht via Dng wrote:

> One last, only partially related thing. Does anyone know how to get polkit
> agents working properly? If I start `lxqt-policykit-agent`, for example,
> pkexec won't work. If I start it as `su -c 'lxqt-policykit-agent'`, it
> does, but I'm pretty sure that's not the right way to do this. I'm
> currently on devuan beowulf, but I think debian users may have similar
> problems, I think systemd/logind people may have broken something in
> polkit...
> 
> 
> Regards,
> Daniel Abrecht
>
I have a beowulf lxqt in a VM, and synaptic-pkexec works correctly.

Here's all the lxqt, policykit and polkit stuff that's running:


user  2438  2429  0 10:09 ?00:00:00 lxqt-session
root  2479 1  0 10:09 ?00:00:00
/usr/lib/policykit-1/polkitd --no-debug
user  2491  2438  0 10:09 ?00:00:00 /usr/bin/pcmanfm-qt
--desktop --profile=lxqt
user  2492  2438  0 10:09 ?00:00:00 /usr/bin/lxqt-globalkeysd
user  2493  2438  0 10:09 ?00:00:00 /usr/bin/lxqt-notificationd
user  2494  2438  1 10:09 ?00:00:03 /usr/bin/lxqt-panel
user  2495  2438  0 10:09 ?00:00:00 /usr/bin/lxqt-policykit-agent
user  2498  2438  0 10:09 ?00:00:00 /usr/bin/lxqt-runner
user  2669  2438  0 10:09 ?00:00:00 /usr/bin/lxqt-powermanagement


Here's a list of all the kit-related packages that are installed.

ii  elogind   241.3-1
amd64user, seat and session management daemon
ii  gir1.2-polkit-1.0 0.105-25+devuan7~beowulf1
amd64GObject introspection data for PolicyKit
ii  libelogind0:amd64 241.3-1
amd64user, seat and session management library
ii  libpam-cap:amd64  1:2.25-2
amd64POSIX 1003.1e capabilities (PAM module)
ii  libpam-elogind:amd64  241.3-1
amd64elogind PAM module
ii  libpam-gnome-keyring:amd643.28.2-5
amd64PAM module to unlock the GNOME keyring upon login
ii  libpam-modules:amd64  1.3.1-5
amd64Pluggable Authentication Modules for PAM
ii  libpam-modules-bin1.3.1-5
amd64Pluggable Authentication Modules for PAM - helper binaries
ii  libpam-runtime1.3.1-5
all  Runtime support for the PAM library
ii  libpam0g:amd641.3.1-5
amd64Pluggable Authentication Modules library
ii  libpolkit-agent-1-0:amd64 0.105-25+devuan7~beowulf1
amd64PolicyKit Authentication Agent API
ii  libpolkit-backend-1-0 0.105-25+devuan7~beowulf1
all  PolicyKit Authorization API
ii  libpolkit-backend-elogind-1-0:amd64   0.105-25+devuan7~beowulf1
amd64PolicyKit backend API
ii  libpolkit-gobject-1-0 0.105-25+devuan7~beowulf1
all  PolicyKit Authorization API
ii  libpolkit-gobject-elogind-1-0:amd64   0.105-25+devuan7~beowulf1
amd64PolicyKit Authorization API
ii  libpolkit-qt5-1-1:amd64   0.112.0-6
amd64PolicyKit-qt5-1 library
ii  lxqt-policykit0.14.1-1
amd64LXQt authentication agent for PolicyKit
ii  lxqt-policykit-l10n   0.14.1-1
all  Language package for lxqt-policykit
ii  policykit-1   0.105-25+devuan7~beowulf1
amd64framework for managing administrative policies and privileges

HTH,
fsmithred
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

[DNG] Sort directories before files!

[fsmithred via Dng]

This has been bugging me since I started playing with beowulf at the
beginning of last year. When I want to open a file in an application, the
file chooser lists all the contents in alphabetical order, with files and
directories mixed in together.

This makes it take longer for me to find what I want, especially if I have
to drill down through several directories.

I found the fix for it here:
https://fransdejonge.com/2018/05/sort-folders-before-files-in-the-gtk3-filechooser/

It took me a minute to figure out the picture. When you open the file
chooser, right-click on any item in it to get the popup menu with the
checkboxes. Check the appropriate box.

Cheers,
fsmithred

___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Beowulf, I2Pd, libboost 1.62 vs 1.67

[fsmithred via Dng]

On 1/12/20 9:19 PM, 'smee via Dng wrote:
> Oh I see, I'm on 2.29.0 but it is locally compiled and not installed. I
> guess if I were to compile the same version again in Beowulf (since
> it's the latest) it would pickup the correct version...?
> 

If you install i2pd 2.23.0-1 from beowulf, you will automatically get the
right libraries. And yeah, if you compile 2.29 in beowulf, it should work.


___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Beowulf, I2Pd, libboost 1.62 vs 1.67

[fsmithred via Dng]

On 1/12/20 8:40 PM, 'smee via Dng wrote:
> I tried running i2pd on my recently upgraded Beowulf instance but found
> it errors out looking for libboost 1.62.0 libraries, which
> libboostx.xx-dev appears to be an automatic install. 
> 
> Should I expect any problems rolling libboost1.67.0 back to 1.62.0. A
> quick search reveals that trying to install both versions is a bad
> idea. So I won't do that, or ask about it ;)
> 

What version of i2pd is installed? The versions in beowulf and ceres
depend on libboost 1.67.0. If one of those is asking for 1.62 then
something is wrong with the package.


___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] When upgrading to Beowulf please test and report issues with eudev-3.2.9-2 from unstable!

[fsmithred via Dng]

On 1/9/20 3:40 PM, 'smee via Dng wrote:

> 
> Correct, I can add it and try reinstall but just trying to figure out
> why firmeware-misc-nonfree and firmware-linux-nonfree are there. If the
> simplest answer is just that I must have installed them myself, I can
> accept that, but I don't think they're there by default, and according
> to this excersize seem to require me to enable the non-free
> repository...
> 

Sorry I'm tuning into this late. No, you didn't install those non-free
packages on your system. I am the one who did that.

The live isos have non-free firmware installed but do not have contrib and
non-free in sources.list. They also have a script to remove all the
non-free packages that are installed. That script is in
/usr/local/bin/remove-non-free-firmware in the desktop-live and
/root/remove-firmware.sh in the minimal live.

After running that script and removing all the non-free firmware, you
might decide that you needed one of those packages. They are included in
the desktop-live iso. (They're in /firmware on the media.) That's done in
case you delete your only means of getting online to get your wireless driver.

fsmithred



___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Fonts trouble on beowulf

[fsmithred via Dng]

On 1/8/20 1:07 PM, Rowland penny via Dng wrote:
> On 08/01/2020 17:56, fsmithred via Dng wrote:
>> On 1/8/20 11:38 AM, Rowland penny via Dng wrote:
>>> On 08/01/2020 16:25, goli...@devuan.org wrote:
>>>> On 2020-01-08 10:14, Rowland penny via Dng wrote:
>>>>> On 08/01/2020 16:02, goli...@devuan.org wrote:
>>>>>> phenix is the correct spelling and has been since jessie.  ;)  The
>>>>>> French do it differently. :D
>>>>> No, the Americans cannot spell correctly, it is Pheonix in English ;-)
>>>>>
>>>>> Rowland
>>>>>
>>>> Even DDG isn't buying that one. When I search for Pheonix I am gently
>>>> asked whether I really want to search on that non-standard word:
>>>>
>>>> Including results for phoenix.
>>>> Search only for "Pheonix"?
>>>>
>>>> urbandictionary.com has a definition though.  LOL!
>>>>
>>>> golinux
>>>>
>>>>
>>>>
>>>> ___
>>>> Dng mailing list
>>>> Dng@lists.dyne.org
>>>> https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
>>> This is what you get from upgrading to Beowulf and Thunderbird gets sets
>>> to the American version of English LOL
>>>
>>> Yes it is 'Phoenix', I just missed the transposition of the 'e' and 'o'
>>> because I knew that they were both in there, even if the spellchecker
>>> (American) was saying it was spelt wrong. I have now fixed the Thunderbird
>>> spell checker, it is now using 'English (United Kingdom)'
>>>
>>> Rowland
>>>
>>
>> Copy/paste from upstream git LISEZ-MOI.md - I don't know how it will look
>> in email, but there's an accent aigu over the e in Phenix. No o in the
>> theme name.
>>
>> "## À propos
>>
>> Le projet Clearlooks-Phénix a pour but de créer une version GTK3 de
>> Clearlooks, thème par défaut de Gnome 2. Un style est également inclus
>> pour GTK2, Unity et les gestionnaires de fenêtres Metacity, Openbox et
>> Xfwm4."
>>
>> fsmithred
> 
> Pardon ? Sorry but I do not speak French (at least I think it is French),
> but if you are referring to the mythical bird that rises from the ashes,
> it is 'Phoenix' in English. Anything else is not English.
> 
> Rowland
> 
> 

I don't really speak French, either. I was referring to the name of the
desktop theme, which is right there in the first sentence of the LISEZ-MOI
(READ-ME).

In Debian, the package is clearlooks-phenix-theme. When I forked it for
Devuan, I kept the spelling the way it was.

fsmithred

___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Fonts trouble on beowulf

[fsmithred via Dng]

On 1/8/20 11:38 AM, Rowland penny via Dng wrote:
> On 08/01/2020 16:25, goli...@devuan.org wrote:
>> On 2020-01-08 10:14, Rowland penny via Dng wrote:
>>> On 08/01/2020 16:02, goli...@devuan.org wrote:
 phenix is the correct spelling and has been since jessie.  ;)  The
 French do it differently. :D
>>>
>>> No, the Americans cannot spell correctly, it is Pheonix in English ;-)
>>>
>>> Rowland
>>>
>>
>> Even DDG isn't buying that one. When I search for Pheonix I am gently
>> asked whether I really want to search on that non-standard word:
>>
>> Including results for phoenix.
>> Search only for "Pheonix"?
>>
>> urbandictionary.com has a definition though.  LOL!
>>
>> golinux
>>
>>
>>
>> ___
>> Dng mailing list
>> Dng@lists.dyne.org
>> https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
> 
> This is what you get from upgrading to Beowulf and Thunderbird gets sets
> to the American version of English LOL
> 
> Yes it is 'Phoenix', I just missed the transposition of the 'e' and 'o'
> because I knew that they were both in there, even if the spellchecker
> (American) was saying it was spelt wrong. I have now fixed the Thunderbird
> spell checker, it is now using 'English (United Kingdom)'
> 
> Rowland
> 


Copy/paste from upstream git LISEZ-MOI.md - I don't know how it will look
in email, but there's an accent aigu over the e in Phenix. No o in the
theme name.

"## À propos

Le projet Clearlooks-Phénix a pour but de créer une version GTK3 de
Clearlooks, thème par défaut de Gnome 2. Un style est également inclus
pour GTK2, Unity et les gestionnaires de fenêtres Metacity, Openbox et Xfwm4."

fsmithred
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Refracta Snapshot - Increase allowable size

[fsmithred via Dng]

On 1/3/20 7:50 AM, 'smee via Dng wrote:
> In attempting to make a copy to upgrade (and report back), I ran into
> the size limit (got an error in the log that the squashfs was 37 g and
> I think it said allowable was 4 gb). I understand why a typical iso
> would need to be small, but is there a way I can increase this size
> limitation for my custom iso's? 
> ___


I thought I fixed that, but the test case was only 4.9GB.
https://dev1galaxy.org/viewtopic.php?id=2416

Maybe there's another limit I don't know about. Yeah, there is - 400GB.

man xorriso, under the -compliance option:
  "iso_9660_level="number chooses level 1 with  ECMA-119 names of the form
8.3 and -file_size_limit<=4g - 1, or level 2 with ECMA-119 names up to
length 32 and the same file_size_limit,  or  level  3 with   ECMA-119
names  up  to  length  32  and  -file_size_limit  >=  400g  -200k.  If
necessary -file_size_limit gets adjusted.

Maybe the option in the xorriso command needs to be changed from
   -iso-limit 3
to
   -compliance iso_9660_level=3


The line looks like this, around line 1100 or 1200,
in /usr/bin/refractasnapshot or refractasnapshot-gui

xorriso -as mkisofs -r -J -joliet-long -l -iso-level 3 ${isohybrid_opt} \

Please let me know if you try that.
Other option is to exclude a bunch of your data and maybe back it up in a
tarball if you want it available for the live system.

fsmithred
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] We need upgrade reports

[fsmithred via Dng]

On 1/1/20 3:48 AM, R. G. Sidler wrote:


Hi fsmithred,

where would you like those upgrade reports sent to?

Sincerely


R. G. Sidler



I guess this list is best; then we can compare notes.

Thanks.
fsr

___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] We need upgrade reports

[fsmithred via Dng]

On 12/31/19 4:49 PM, Dr. Nikolaus Klepp wrote:

All upgraded since some months, no problems so far.

Nik



Was that with kde desktop by any chance? (One less for me to do?)

fsr
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Catching up (was Re: Result of the Debian vote 'General Resolution: Init systems and systemd')

[fsmithred via Dng]

On 12/31/19 9:16 PM, Arnt Karlsen wrote:

On Tue, 31 Dec 2019 16:01:11 -0500, fsmithred wrote in message
<56853e51-735a-8e18-1f44-f6ae3fb6c...@gmail.com>:



CenturionDan posted this in irc a few days ago:
" with the 4.19 kernel LVM requires udev to be running and /run/udev
to exist in order for root on LV and other initramfs mounted volumes
to be mounted.."


..is this a systemd-ism directed against LVM users?


I ran into this issue on some fresh installs earlier this year and
had to create and mount /run/udev in a chroot to get grub to install.

fsr





I don't know where it came from, but I did a fresh install yesterday from 
a 2.1 iso, used guided partitioning for encrypted lvm, all files in one 
partition (with separate /boot), lxqt desktop, and then dist-upgraded it 
to beowulf.


On the first 'apt dist-upgrade' there were some conflicts with java 
libraries for libreoffice. That was resolved with 'apt --fix-broken 
install' and another dist-upgrade.


elogind, libelogind0 and libpam-elogind were held back. 'apt install 
elogind=241.3-1' fixed that (and libsystemd0 got removed.)


There were no issues with the encrypted lvm except for the shutdown delay, 
which is a well-known problem.


fsmithred



___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Catching up (was Re: Result of the Debian vote 'General Resolution: Init systems and systemd')

[fsmithred via Dng]

On 12/31/19 3:16 PM, Andrew McGlashan via Dng wrote:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Hi,

On 1/1/20 6:53 am, fsmithred via Dng wrote:

On 12/31/19 2:16 PM, Andrew McGlashan via Dng wrote:

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256

Hi,

On 1/1/20 4:20 am, fsmithred via Dng wrote:

On 12/31/19 12:06 PM, Andrew McGlashan via Dng wrote:


So how long before we can expect to get stable release
of Beowulf? Is there a reasonable timeline available yet?



About the only thing left to do is make the isos, and we're
working on that. Meanwhile, upgrades from ascii seem to be
pretty smooth.


Okay, so safe to update /etc/apt/sources.list and then: apt-get
update apt-get dist-upgrade ... now?

For production systems or any systems?

Thanks A.


For production systems, I might do an upgrade on a test system
first, only because I haven't heard a lot of upgrade reports. Also,
there might still be some issues on upgrading lvm.


I use lvm, a lot, what are the problems with lvm?


I've upgraded standard system (no X), a few xfce systems and a
mate desktop. They've all been uneventful.


Thanks
A.


CenturionDan posted this in irc a few days ago:
" with the 4.19 kernel LVM requires udev to be running and /run/udev to 
exist in order for root on LV and other initramfs mounted volumes to be 
mounted.."


I ran into this issue on some fresh installs earlier this year and had to 
create and mount /run/udev in a chroot to get grub to install.


fsr

___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

[DNG] We need upgrade reports

[fsmithred via Dng]

Please upgrade your highly customized and configured ascii production 
system to beowulf and tell us if it works. Okay, DO THIS ON A COPY, not 
the real thing.


I've upgraded standard no-X systems, xfce and mate desktops, and those 
went smoothly. We need more data points.


Thanks,
fsmithred
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Catching up (was Re: Result of the Debian vote 'General Resolution: Init systems and systemd')

[fsmithred via Dng]

On 12/31/19 2:16 PM, Andrew McGlashan via Dng wrote:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Hi,

On 1/1/20 4:20 am, fsmithred via Dng wrote:

On 12/31/19 12:06 PM, Andrew McGlashan via Dng wrote:


So how long before we can expect to get stable release of
Beowulf? Is there a reasonable timeline available yet?



About the only thing left to do is make the isos, and we're working
on that. Meanwhile, upgrades from ascii seem to be pretty smooth.


Okay, so safe to update /etc/apt/sources.list and then:
apt-get update
apt-get dist-upgrade
... now?

For production systems or any systems?

Thanks
A.


For production systems, I might do an upgrade on a test system first, only 
because I haven't heard a lot of upgrade reports. Also, there might still 
be some issues on upgrading lvm.


I've upgraded standard system (no X), a few xfce systems and a mate 
desktop. They've all been uneventful.


fsr
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

[DNG] Refracta-10.0 (beowulf) XFCE isos

[fsmithred via Dng]

Betas:
https://get.refracta.org/files/testing/

I know there are a couple of issues with the high contrast theme. (wrong 
icon set, one wrong launcher.)


What else? (other than missing documentation. Don't worry, you'll figure 
it out. Release notes will come later, but they won't be much different 
from the last notes.)


fsmithred
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Catching up (was Re: Result of the Debian vote 'General Resolution: Init systems and systemd')

[fsmithred via Dng]

On 12/31/19 12:06 PM, Andrew McGlashan via Dng wrote:



So how long before we can expect to get stable release of Beowulf?
Is there a reasonable timeline available yet?



About the only thing left to do is make the isos, and we're working on 
that. Meanwhile, upgrades from ascii seem to be pretty smooth.



fsmithred
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Result of the Debian vote 'General Resolution: Init systems and systemd'

[fsmithred via Dng]

On 12/29/19 10:46 PM, tom wrote:


I know Devuan has been pretty much more or less 'to create a binary
compatible Debian but without systemd', but at what point would it be
determined that the best course of action may be to leave Debian behind
and continue our own way? Probably won't happen any time soon due to
manpower issues but it's worth thinking about.



One way to measure that might be to see if we start falling farther behind 
debian. Right now, we're still catching up.


Jessie was 2 years late.
Ascii was 1 year late.
Beowulf is 6 months late.

Any talk of switching our base is premature.

fsmithred
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Fw: looking for a replacement for debian since systemd

[fsmithred via Dng]

On 12/13/19 8:55 PM, Steve Litt wrote:


=

Begin forwarded message:





- - -=-=-=-=-=- Don't Delete Anything Between These Lines
=-=-=-=-=-=-=-=- 7b77e0f2-4ff9-4adb-85e4-af249191f27a
[ 3 ] Choice 1: F: Focus on systemd
[ 1 ] Choice 2: B: Systemd but we support exploring alternatives
[   ] Choice 3: A: Support for multiple init systems is Important
[   ] Choice 4: D: Support non-systemd systems, without blocking progress
[ 2 ] Choice 5: H: Support portability, without blocking progress
[   ] Choice 6: E: Support for multiple init systems is Required
[   ] Choice 7: G: Support portability and multiple implementations
[ 4 ] Choice 8: Further Discussion
-=-=-=-=-=- Don't Delete Anything Between These Lines=-=-=-=-=-=-=-=-
  




This looks like one person's ballot. Their first two choices are to 
support other init systems (B and H). More talk is the last thing they want.


fsmithred

___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

[DNG] Refracta beowulf no-X isos

[fsmithred via Dng]

https://get.refracta.org/files/testing/

No X. Plenty of extra command-line software, especially stuff for rescue 
and repair.


I'm calling them beta because beowulf is still undergoing some changes. 
These were built with live-sdk, and I don't think I need to change 
anything in the build process. I'll probably make new isos when beowulf 
goes stable.


Xfce isos coming soon. (Weeks, not days.)

New versions of installer and snapshot also coming soon. (Days, not weeks. 
They're already in the new isos, just have to get them into the repo.)


(Note: These are NOT no-dbus isos, in case that's what you were thinking.)

fsmithred
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Installing devuan on newer hardware

[fsmithred via Dng]

On 10/31/19 6:44 AM, Yevgeny Kosarzhevsky via Dng wrote:

I tried mini.iso from
https://pkgmaster.devuan.org/devuan/dists/beowulf/main/installer-amd64/current/images/netboot/
but it isn't booting, bailing out to grub prompt.

Can someone suggest how would I proceed with devuan installation here?
Thanks!



The first thing to try would be to boot the installer media into rescue 
mode and try reinstalling grub. Or chroot the installed system and run 
grub-install and update-grub.


If this is a uefi system, you might just need to replace 
grub-efi-amd64-signed with grub-efi-amd64 while you're in chroot. Remember 
to 'apt update' first.


fsmithred
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Devuan as a rescue CD?

[fsmithred via Dng]

On 10/26/19 5:06 PM, Steve Litt wrote:

Hi all,

Has any of you been using Devuan as a rescue CD? If so, how has it been
working out for you, and do you have any suggestions to make the Devuan
rescue experience easy and productive?

System Rescue CD recently switched from Gentoo to Arch, thus acquiring
systemd. I wouldn't have a big problem using systemd for a narrow,
contained usage like rescue, but I've also heard their project is
foundering.

Thanks,


SteveT



I use a Refracta live-cd or usb as a rescue system. It has things like 
ddrescue, smartmontools, lm-sensors, testdisk/photorec and some other 
relevant software installed.


What is it you need to rescue? Some things are easier than others.

fsmithred

___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Devuan ASCII point release

[fsmithred via Dng]

On 10/26/19 9:54 AM, s@po wrote:




Where does 'apt-cache policy' get the version number? Oh, maybe it reads
it from the repo. I see that we have:



It could be..
Another place, I searched for and makes sense to me:
http://pkgmaster.devuan.org/merged/dists/ascii/Release




So I think it comes from :
root@desktop0:~# wget -qO- 
http://pkgmaster.devuan.org/merged/dists/{ascii,ascii-backports,ascii-security,ascii-updates}/Release|grep
 Version --color
Version: 2.0
Version: 2.0.0
Version: 2.0
Version: 2.0.0

Best Regards,



Yes, thank you. I got confirmation from another source that it's in the 
Release file. I'll find someone to make the changes.


fsmithred



___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Devuan ASCII point release

[fsmithred via Dng]

On 10/26/19 1:49 AM, Pontus Goffe via Dng wrote:

Hi,

On 2019-10-26 02:27, s@po wrote:
You see here the '2.0' String, and it comes from the funtion 
guess_release_from_apt().. like you can see above..

The guess_release_from_apt() function:
 228 def guess_release_from_apt(origin='Devuan', component='main',
 229    ignoresuites=('experimental'),
 230    label='Devuan',
 231    alternate_olabels={'Devuan 
Ports':'packages.devuan.org'}):

 232 releases = parse_apt_policy()
 233
 234 if not releases:
 235 return None
 236
 237 # We only care about the specified origin, component, and 
label

 238 releases = [x for x in releases if (
 239 x[1].get('origin', '') == origin and
 240 x[1].get('component', '') == component and
 241 x[1].get('label', '') == label) or (
 242 x[1].get('origin', '') in alternate_olabels and
 243 x[1].get('label', '') == 
alternate_olabels.get(x[1].get('origin', '')))]

 244
 245 # Check again to make sure we didn't wipe out all of the 
releases

 246 if not releases:
 247 return None
 248
 249 releases.sort(key=lambda tuple: tuple[0],reverse=True)
 250
 251 # We've sorted the list by descending priority, so the 
first entry should

 252 # be the "main" release in use on the system
 253
 254 max_priority = releases[0][0]
 255 releases = [x for x in releases if x[0] == max_priority]
 256 releases.sort(key=release_index)
 257
 258 return releases[0][1]

I am afraid that this info, you already know..
I am not a python guy( I love the Lua simplicity way :) ), I can't 
help.. :(


Best Regards,
tux


Who is a python guy?

parse_apt_policy executes 'apt-cache policy' and parses 
(parse_policy_line) the output for lines beginning with release matching 
o=Devuan and c=main


longnames = {'v' : 'version', 'o': 'origin', 'a': 'suite', 'c' : 
'component', 'l': 'label'}


In my case that is

  500 http://se.deb.devuan.org/merged ascii/main amd64 Packages
  release v=2.0,o=Devuan,a=stable,n=ascii,l=Devuan,c=main,b=amd64
  origin se.deb.devuan.org
//PG




Where does 'apt-cache policy' get the version number? Oh, maybe it reads 
it from the repo. I see that we have:


pkgmaster.devuan.org/merged/dists/1.0
pkgmaster.devuan.org/merged/dists/2.0
pkgmaster.devuan.org/merged/dists/3.0

and debian has:

debian/dists/Debian8.11
debian/dists/Debian9.11
debian/dists/Debian10.1

Maybe those directory names are supposed to be changed when there's a 
point release.


fsmithred

___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Devuan ASCII point release

[fsmithred via Dng]

On 10/25/19 9:48 AM, Joril via Dng wrote:

On 22/10/19 06:00, . fsmithred via Dng wrote:

The Devuan ASCII 2.1 point release has begun. The installer isos,
desktop-live and minimal-live isos are currently available

After installation lsb_release still reports 2.0, should I file a bug report?

# uname -r
4.9.0-11-amd64

# lsb_release -a
No LSB modules are available.
Distributor ID:    Devuan
Description:    Devuan GNU/Linux 2.0 (ascii)
Release:    2.0
Codename:    ascii
___



I don't know exactly where the 2.0 is coming from. It's not in 
/etc/os-release, /etc/devuan_version or /etc/issue, and there is no 
/etc/lsb-release file.


man lsb_release says
  "Detection of systems using a mix of packages from various 
distributions or releases is something of a black art; the current 
heuristic tends to assume that the installation is of the earliest 
distribution which is still being used by apt but that heuristic is 
subject to error."


It can't hurt to file a bug report. If you know how to fix it, let us know 
and we can correct that in the future.


fsmithred

___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

[DNG] Devuan ASCII point release

[. fsmithred via Dng]

The Devuan ASCII 2.1 point release has begun. The installer isos,
desktop-live and minimal-live isos are currently available for
download here:
http://files.devuan.org/devuan_ascii/
Other images will be uploaded as they are ready.

- The option to choose openrc is more prominent and no longer requires
an Expert install. You can't miss it.

- If you would like to select an alternate bootloader (lilo) or
exclude non-free firmware, you must select one of the Expert install
options.

- The recommended default mirror is now deb.devuan.org.  If you would
like to use a country code mirror, please check
https://pkgmaster.devuan.org/mirror_list.txt to see if there is one
suitable for your needs.

There is more information in the Release Notes:
http://files.devuan.org/devuan_ascii/Release_notes.txt
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] openvpn beowulf package imssing

[. fsmithred via Dng]

On 10/17/19, Yevgeny Kosarzhevsky via Dng  wrote:
> On Mon, 7 Oct 2019 at 12:25, Dimitris via Dng  wrote:
>> seems to be there..:
>> https://pkginfo.devuan.org/stage/beowulf/beowulf/openvpn_2.3.10-1+devuan1.html
>> mirror package :
>> https://pkgmaster.devuan.org/devuan/pool/main/o/openvpn/
>
> This package isn't installable in beowulf as it's missing libssl1.0.2
> dependency


The version of openvpn in buster (2.4.7-1) wants libssl1.1. I just
installed it in beowulf (with libelogind0 to satisfy the libsystemd0
dep.)

fsmithred
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Gnuinos Beowulf

[. fsmithred via Dng]

On 10/19/19, Aitor  wrote:

> At some point, the boot process waits for something. Pressing
> Ctrl+Alt+F4 the boot process went ahead
> ending up at a prompt.

If openssh-server is installed, it's waiting for entropy. Install
haveged and make sure it's running before ssh. I made a modified
live-config script for ssh for this purpose. I'll send it to you if
you need it.

> Startx didn't work.

If you're running without a display manager you need to either install
elogind and libpam-elogind or you need to install xserver-xorg-legacy
and add a line to /etc/X11/Xwrapper.config:
needs_root_rights=yes


fsmithred
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Can't grub ignore /dev/hdb?

[fsmithred via Dng]

On 9/13/19 5:43 PM, goli...@devuan.org wrote:

On 2019-09-13 16:24, Hendrik Boom wrote:

Haven't replaced /dev/hdb yet.
Is there some way of getting it ignored in the following scenario?

I started aptitude.
It told me it hadn't been cleanly shut down last time, and recommended
I do
    dpkg --configure -a
before I do anything else.

I do that, and the system apparently does some cleanup, generating
initrd images, and then starts to update grub.

Update-grub stalls on block 51 of device /dev/hdb, trying to do
something with it over and over (as presented on the main system
console, which is *not* the one I'm trying to run aptitude on)

Now evidently /dev/hdb is not working and will need to be replaced.

But isn't there some way to tell grub to ignore /dev/hdb?
What is it that controls which drives grub tries to work with.
It must get this from somewhere.  I did not specify or mention /dev/hdb
anywhere in my dpkg --configure -a.  And there are several other drives
I could use to install grub and a boot record.  I can even use the
grub-install command to do so.  So why, oh why, does it pick on
/dev/sdb?

-- hendrik




Open the case and unplug it?

(golinux ducks and runs)



Golinux beat me to it.

update-grub (grub-mkconfig) uses black magic to find all the bootable 
systems within reach. I read that somewhere in the comments in one of the 
grub scripts. (Note: It won't find encrypted systems except for the one 
that's running update-grub.)


It... wait... what? hdb? I hope that's a typo.

If the disk is dying, make sure you have everything you want off of it 
before you unplug it.


fsmithred


___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] [devuan-dev] Migrating from Buster to Beowulf - feedback needed

[fsmithred via Dng]

On 9/10/19 7:59 AM, Mark Hindley wrote:

I have been further testing ways of migrating buster to beowulf.

With a install of xfce4 and lightdm, the cleanest way I can come up with is:

# Migrate from Debian buster to Devuan beowulf

# Install devuan-keyring
wget 
http://pkgmaster.devuan.org/devuan/pool/main/d/devuan-keyring/devuan-keyring_2017.10.03_all.deb
dpkg -i devuan-keyring_2017.10.03_all.deb

# Change APT sources
cat > /etc/apt/sources.list = 2.28), libpam0g (>= 0.99.7.1), systemd (= 241-7~deb10u1), 
libpam-runtime (>= 1.0.1-6), dbus, systemd-sysv
# 4) Remove ', systemd-sysv from the end of the line, leaving the rest of the 
line intact
# 5) Save file
cp /var/lib/dpkg/status /var/lib/dpkg/status.save
editor /var/lib/dpkg/status

# Install new init and dbus.
# Ensure we will have dbus-x11 to provide dbus-session-bus after systemd is 
gone.
# Remove libnss-systemd to avoid delays on nss lookups after reboot.
apt install --purge sysvinit-core dbus dbus-x11 libnss-systemd-

reboot

# If you have policykit-1 installed, update it.
# This will also purge systemd* and install libpam-elogind
apt install --purge policykit-1

# The rest of the migration (base-files, eudev, etc)
# This will also purge sytemd* if not already done.
apt --purge full-upgrade

# Optionally, if you didn't edit /var/lib/dpkg/status above
# Reinstall whatever desktop and display manager was removed
# apt install xfce4 lightdm

# Change ens3 to eth0 in /etc/network/interfaces
sed s/ens3/eth0/ -i /etc/network/interfaces

reboot

# Remove cruft
apt autoremove --purge

Done!

The transitional systemd-sysv package I talked about a few days ago to smooth
over #935304 isn't going to work as I had forgotten that sysvinit-core conflicts
with systemd-sysv.

The hack to work around #935304 by editing /var/lib/dpkg/status is not pretty at
all. If you don't want it you will have to accept removal of some GUI components
with libpam-systemd and then reinstall them after libpam-elogind is in place.

I hope the instructions are reasonably clear.

Do give feedback.

Thanks

Mark


Would a transitional package that makes the edit to /var/lib/dpkg/status 
be a sane solution?


fsmithred

___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] udisks2 - who uses it? (not a poll)

[fsmithred via Dng]

On 9/10/19 5:11 AM, Daniel Reurich wrote:

On 08/09/19 07:37, fsmithred via Dng wrote:

On 9/7/19 1:33 PM, Ismael L. Donis Garcia wrote:

- Original Message - From: "fsmithred via Dng"

To: "dng" 
Sent: Friday, September 06, 2019 9:23 AM
Subject: [DNG] udisks2 - who uses it? (not a poll)



In ascii, udisks2 has been devuanized to remove a dependency on
libpam-systemd (and maybe libsystemd0, too.)

The version of udisks2 in beowulf is very old compared to what's in
buster.

The version in buster depends on libpam-systemd OR libpam-elogind.
(Also libsystemd0 OR libelogind0) Since we have libpam-elogind and
libelogind0 in the repos, we don't really need to devuanize udisks2
anymore. Do we?

Does anyone use udisks2 who doesn't want libpam-elogind or
libelogind0 with it?

fsmithred (looking to reduce the work load)



I use udisks2, but I also use libpam-elogind and libelogind0

Right now I am needing this update to install other packages.

Best Regards
--
Ismael



Thanks.

Things are moving slowly now, and I have no idea when we will get the
newer version into the repo. For now, I suggest you download udisks2 and
libudisks2-0 from packages.debian.org and install them manually.
https://packages.debian.org/buster/udisks2

If you wait for us, you'll get the exact same packages, only it will be
later.

fsmithred


fsmithred - do we need to drop udisks2 forked package from unstable and
beowulf?




Yes. Nobody has objected to that, and it will fix the problem. Here's the 
current landscape:


  Version table:
 2.8.4-1 500
500 http://debian.csail.mit.edu/debian sid/main amd64 Packages
 2.8.1-4 10
 10 http://debian.csail.mit.edu/debian buster/main amd64 Packages
 2.1.8-1+devuan2 500
500 http://deb.devuan.org/merged ascii/main amd64 Packages
500 http://auto.mirror.devuan.org/merged ascii/main amd64 Packages
 2.1.8-1 10
 10 http://debian.csail.mit.edu/debian stretch/main amd64 Packages
 2.1.3-5+devuan2 50
 50 http://deb.devuan.org/merged beowulf/main amd64 Packages
 50 http://pkgmaster.devuan.org/merged ceres/main amd64 Packages
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] udisks2 - who uses it? (not a poll)

[fsmithred via Dng]

On 9/7/19 1:33 PM, Ismael L. Donis Garcia wrote:

- Original Message - From: "fsmithred via Dng" 
To: "dng" 
Sent: Friday, September 06, 2019 9:23 AM
Subject: [DNG] udisks2 - who uses it? (not a poll)


In ascii, udisks2 has been devuanized to remove a dependency on 
libpam-systemd (and maybe libsystemd0, too.)


The version of udisks2 in beowulf is very old compared to what's in buster.

The version in buster depends on libpam-systemd OR libpam-elogind. (Also 
libsystemd0 OR libelogind0) Since we have libpam-elogind and libelogind0 
in the repos, we don't really need to devuanize udisks2 anymore. Do we?


Does anyone use udisks2 who doesn't want libpam-elogind or libelogind0 
with it?


fsmithred (looking to reduce the work load)



I use udisks2, but I also use libpam-elogind and libelogind0

Right now I am needing this update to install other packages.

Best Regards
--
Ismael



Thanks.

Things are moving slowly now, and I have no idea when we will get the 
newer version into the repo. For now, I suggest you download udisks2 and 
libudisks2-0 from packages.debian.org and install them manually.

https://packages.debian.org/buster/udisks2

If you wait for us, you'll get the exact same packages, only it will be later.

fsmithred


___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] [devuan-dev] Migrating from Buster to Beowulf - feedback needed

[fsmithred via Dng]

On 9/7/19 2:26 AM, Mark Hindley wrote:

libpam-systemd depends systemd-sysv. libpam-systemd also depends
systemd. Devuan's libpam-elogind provides libpam-systemd but conflicts with
systemd which must be removed first.

However, to get systemd uninstalled we first have to replace systemd-sysv with
sysvinit-core (leaving systemd installed) and reboot. systemd and elogind
conflict so we cannot use libpam-elogind to replace libpam-systemd *yet*.

This is the point we need a transitional package to temporarily satisfy
libpam-systemd's systemd-sysv dependency whilst the system is rebooted.

After reboot, systemd is no longer PID1 so can be removed and we can then
complete the transition replacing libpam-systemd with libpam-elogind, removing
systemd and installing elogind.

I hope that is clearer.



Kinda, sorta.

I think it's consistent with my experience of migrating buster to beowulf. 
At the time, I was ready to say that it can't be done and we shouldn't 
support it, but I did succeed after two days of messing with it. Nice to 
see you have a way to make it work smoothly.


fsmithred

___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] udisks2 - who uses it? (not a poll)

[fsmithred via Dng]

On 9/6/19 5:43 PM, Alessandro Selli wrote:

On 06/09/19 at 15:23, fsmithred via Dng wrote:

In ascii, udisks2 has been devuanized to remove a dependency on
libpam-systemd (and maybe libsystemd0, too.)

The version of udisks2 in beowulf is very old compared to what's in
buster.


   Really?  I'm on beowulf now, and I have:

ii  udisks2    2.8.1-4  amd64    D-Bus service to access and
manipulate storage devices

Same as Debian 10 (buster):




Where did you get it? That version is not in devuan. I'm still running the 
ascii version in my beowulf, because the beowulf/ceres version is older.


udisks2:
  Installed: 2.1.8-1+devuan2
  Candidate: 2.1.8-1+devuan2
  Version table:
 2.8.1-4 10
 10 http://debian.csail.mit.edu/debian buster/main amd64 Packages
 *** 2.1.8-1+devuan2 100
100 /var/lib/dpkg/status
 2.1.3-5+devuan2 500
500 http://deb.devuan.org/merged beowulf/main amd64 Packages
 50 http://deb.devuan.org/merged ceres/main amd64 Packages

I do have the buster version in one beowulf install, but I got that from 
outside of devuan.


fsmithred
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Migrating from Buster to Beowulf - feedback needed

[fsmithred via Dng]

On 9/6/19 9:05 AM, Hendrik Boom wrote:

On Fri, Sep 06, 2019 at 09:00:08AM -0400, fsmithred via Dng wrote:

On 9/6/19 8:33 AM, Hendrik Boom wrote:



I could try crossgrading to beowulf before I delete it.

...

Are there instructions already?  Or is it the usual change the
apt-sources, update, and upgrade?



Instructions for migrating to ascii should be a good outline.
https://devuan.org/os/documentation/dev1fanboy/migrate-to-ascii

Nixer posted on the forum about migrating buster to beowulf:
https://dev1galaxy.org/viewtopic.php?id=2796

I'm not going to list any steps until I try it again. When I did it a few 
months ago, it was hell. I didn't do it exactly the way nixer described.


Your input (and anyone else's) will be used to update the official 
instructions.


fsmithred
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Migrating from Buster to Beowulf - feedback needed

[fsmithred via Dng]

On 9/6/19 9:34 AM, fsmithred wrote:

On 9/6/19 9:05 AM, Hendrik Boom wrote:

On Fri, Sep 06, 2019 at 09:00:08AM -0400, fsmithred via Dng wrote:

On 9/6/19 8:33 AM, Hendrik Boom wrote:

I've got buster on a partition I never use and was thinking of deleting.
I could try crossgrading to beowulf before I delete it.
Would that help?  It would not likely get any actual usage to discover
problems beyond the actual crossgrade itself.



Yes, please. And maybe tee the output to a log file in case you get
something "interesting".


OK.  But I should maybe use the script command.
Are there instructions already?  Or is it the usual change the
apt-sources, update, and upgrade?
and how should I point to the beowulf repositories?  I've noticed
devuan repositories in different locations before, and I'm not entirely
sure the ones I'm using on my pure-devuan beowulf are the
current official ones.



I've upgraded Refracta-9 (ascii, xfce, without metapackages) with the 
follwing:


deb http://deb.devuan.org/merged beowulf main
deb http://deb.devuan.org/merged beowulf-security main

apt update
apt-get dist-upgrade
reboot

Notes:
- I have linux-image-amd64 installed, so I got the new kernel 
automatically. Make sure you get 4.19-whatever.
- There's no beowulf-updates or beowulf-backports yet. Leave those lines 
commented out if you have them.
- I used "apt" to update for less typing; I used "apt-get" out of habit. 
If you get stuck with conficts, try 'aptitude -s full-upgrade' to see if 
it offers a better solution. You could also do a plain upgrade before the 
dist-upgrade, but it may not be necessary.
- I already know that I contradicted myself, thanks. (In case someone 
wanted to point out that linux-image-amd64 is a metapackage.)



fsmithred


* Need More Coffee *

Those are very nice instructions I wrote, but they're for devuan upgrade, 
not migration from beowulf.


I'll try again after another cup.

fsmithred


___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Migrating from Buster to Beowulf - feedback needed

[fsmithred via Dng]

On 9/6/19 9:05 AM, Hendrik Boom wrote:

On Fri, Sep 06, 2019 at 09:00:08AM -0400, fsmithred via Dng wrote:

On 9/6/19 8:33 AM, Hendrik Boom wrote:

I've got buster on a partition I never use and was thinking of deleting.
I could try crossgrading to beowulf before I delete it.
Would that help?  It would not likely get any actual usage to discover
problems beyond the actual crossgrade itself.



Yes, please. And maybe tee the output to a log file in case you get
something "interesting".


OK.  But I should maybe use the script command.
Are there instructions already?  Or is it the usual change the
apt-sources, update, and upgrade?
and how should I point to the beowulf repositories?  I've noticed
devuan repositories in different locations before, and I'm not entirely
sure the ones I'm using on my pure-devuan beowulf are the
current official ones.



I've upgraded Refracta-9 (ascii, xfce, without metapackages) with the 
follwing:


deb http://deb.devuan.org/merged beowulf main
deb http://deb.devuan.org/merged beowulf-security main

apt update
apt-get dist-upgrade
reboot

Notes:
- I have linux-image-amd64 installed, so I got the new kernel 
automatically. Make sure you get 4.19-whatever.
- There's no beowulf-updates or beowulf-backports yet. Leave those lines 
commented out if you have them.
- I used "apt" to update for less typing; I used "apt-get" out of habit. 
If you get stuck with conficts, try 'aptitude -s full-upgrade' to see if 
it offers a better solution. You could also do a plain upgrade before the 
dist-upgrade, but it may not be necessary.
- I already know that I contradicted myself, thanks. (In case someone 
wanted to point out that linux-image-amd64 is a metapackage.)



fsmithred
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

[DNG] udisks2 - who uses it? (not a poll)

[fsmithred via Dng]

In ascii, udisks2 has been devuanized to remove a dependency on 
libpam-systemd (and maybe libsystemd0, too.)


The version of udisks2 in beowulf is very old compared to what's in buster.

The version in buster depends on libpam-systemd OR libpam-elogind. (Also 
libsystemd0 OR libelogind0) Since we have libpam-elogind and libelogind0 
in the repos, we don't really need to devuanize udisks2 anymore. Do we?


Does anyone use udisks2 who doesn't want libpam-elogind or libelogind0 
with it?


fsmithred (looking to reduce the work load)

___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Migrating from Buster to Beowulf - feedback needed

[fsmithred via Dng]

On 9/6/19 8:33 AM, Hendrik Boom wrote:

I've got buster on a partition I never use and was thinking of deleting.
I could try crossgrading to beowulf before I delete it.
Would that help?  It would not likely get any actual usage to discover
problems beyond the actual crossgrade itself.



Yes, please. And maybe tee the output to a log file in case you get 
something "interesting".


Thanks,
fsmithred

___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] error to install gnome-disk-utility in beowulf

[fsmithred via Dng]

On 9/3/19 12:52 PM, Florian Zieboll wrote:

On September 3, 2019 4:46:28 PM GMT+02:00, "Ismael L. Donis Garcia" 
 wrote:

Los siguientes paquetes tienen dependencias incumplidas:
gnome-disk-utility : Depende: udisks2 (>= 2.7.6) pero 2.1.3-5+devuan2
va a
ser instalado
 Depende: libudisks2-0 (>= 2.7.6) pero 2.1.3-5+devuan2
va a ser instalado
E: No se pudieron corregir los problemas, usted ha retenido paquetes
rotos.


How could I solve this error?

Best Regards



$ aptitude install gnome-disk-utility

should give you at least a clue about the problem, it might even suggest a 
viable solution.

Regards,
Florian



Right now, the versions in the devuan repo are too old. You could download 
those two packages from debian and install them - they seem to work. 
You'll need to have libpam-elogind installed.


https://packages.debian.org/buster/udisks2
https://packages.debian.org/buster/libudisks2-0

The other option is to wait until we either rebuild that version for 
devuan or move it into beowulf as it is.


fsmithred
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Identifying an installed physical hard drive without damage

[fsmithred via Dng]

On 8/11/19 8:46 PM, Hendrik Boom wrote:

On Sun, Aug 11, 2019 at 05:17:08PM -0400, Miles Fidelman wrote:



You could also execute a command that causes heavy load on /dev/sdb - be it
a test, or a search - and then see which drive's lights flash a lot (if the
drive has a light).


Good idea, but no light.

-- hendrik


Can you put your fingers on the drive and feel for activity? Or get your 
ear close to it and listen? (Assuming they are spinning disks and not SSD.)


fsr


___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] But there is a problem, but my report was wrong.

[fsmithred via Dng]

On 8/10/19 7:36 PM, Hendrik Boom wrote:



   5 Reallocated_Sector_Ct   0x0033   098   098   036Pre-fail  Always   
-   104

Count not zero.  Time to replace the disk.



Ouch! And more than just a handful.




As for moving data off, the crucial partitions are part of a RAID, so
the data are already duplicated elsewhere.  


Be aware that a lot of newer large disks (1T or more) no longer do error 
correction and aren't suitable for RAID.  (WD Black, I'm looking at you.)





And its main function nowadays is to be the disk I boot from.



If your RAID is on partitions instead of whole disk, you should be able to 
boot from any disk. If possible, install grub to another or all of the 
disks (as grub recommends).


If that fails, I think you could boot from live media and fix it.



Not sure what else would cause the input/output error you got. Bad cable
maybe?


I don't know either.  But I have a vague memory of problems like this
once before when I did not have time or energy to investigate properly.

-- hendrik



That's ok. Let it retire in dignity, before it starts clicking and sputtering.

fsmithred
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] But there is a problem, but my report was wrong.

[fsmithred via Dng]

On 8/10/19 4:32 PM, Hendrik Boom wrote:

On Sat, Aug 10, 2019 at 03:11:03PM -0400, fsmithred via Dng wrote:




Perhaps that disk is defective and I have to replace it.



If you have smartmontools installed, you can check:

   smartctl -a /dev/whatever


Im not familiar with these statistice, but it Looks bad:

   7 Seek_Error_Rate 0x000f   084   060   030Pre-fail  Always   
-   324736547

and

195 Hardware_ECC_Recovered  0x001a   071   056   000Old_age   Always   
-   204030548

Is that a lot of errors/

-- hendrik



I think it's normal to see high numbers of errors. I have more Seek errors 
and fewer Recovered than you on a disk with 75000 hours.


Check to make sure the Reallocated Sector count is zero. If it's not, you 
should probably start moving data off the disk.


Not sure what else would cause the input/output error you got. Bad cable 
maybe?


fsr





___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] But there is a problem, but my report was wrong.

[fsmithred via Dng]

On 8/10/19 2:51 PM, Hendrik Boom wrote:

Sorry for this post.  There is trouble, but the details are all wrong.
I was upgrading a machine that was differet from the machine I thought
I was upgrading.  Given that, it's no surprise that it appeared to be
upgrading ascii instead of beowulf, or that it had problems with gpt
disks -- there are gpt disks.

The real problem is that it seems to be unable to write to several
sectors at the start of device /dev/sdb.  I have no idea why, but it
keeps retrying for hours and hours.  Currently it's stuck trying to
write to sector 51.  This is while doing something to grub in the
course of the upgrade.

Anyone know how I can

  stop it from retrying?  By now retrying is
useless.


ctrl-c?



Perhaps that disk is defective and I have to replace it.



If you have smartmontools installed, you can check:

  smartctl -a /dev/whatever



As for not being able to stash grub onto a gpt disk, that *is* a
problem.  Presumably I have to do something to it to make it
possible, and t make it possible to boot from the gpt disk, but I have
no idea what.


Create a partition at least 1MB in size with no filesystem on it. 
(unformatted is the last choice in gparted) Give it a flag of bios_grub in 
gparted or type ef02 in gdisk. When it comes to grub-install, grub will 
know what to do with it.


Some howtos say it must be the first partition. I haven't found that to be 
true. I've put it in the middle and at the end. It works.


fsmithred
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] trouble with grub-pc during routine upgrade

[fsmithred via Dng]

On 8/9/19 2:16 PM, Hendrik Boom wrote:

OK.  Towards my usual ugrade, I'm told:

grub-install: warning: this GPT partition label contains no BIOS Boot 
Partition; embedding won't be possible.
grub-install: error: embedding is not possible, but this is required for RAID 
and LVM install.



At this point, it has failed to write to /dev/sdb twice, presumably because I 
have only one hard drive.  When it fails the second time and tries again I tell 
it to insatall to dev/sda which does exist.  It now complains about my GPT 
partition label.  I don't have a GPT partition label.  My machine is a bios 
machine.  See:


I've seen this error when the second disk is gpt, even though I'm 
installing to the first disk. I've also seen it when the disk was 
previously partitioned as gpt and then switched to dos partition table. 
Does yours fall into the second category?





What gives?

At this poiit I'm afraid to turn my machine off, lest it never start again.


If you have a grub boot CD or USB, you can boot from grub command line.


The machine is a Purism laptop, running Devuan beowulf.  Oddly, when
aptitude was updating, it kept mentioning ascii instead.  But my
/etc/apt/sources.lst is as follows:


You did run 'apt update' or the equivalent after editing sources.list, 
didn't you? (I'm hoping you forgot to do that, because then it's an easy fix.)
The other easy fix is to remove any mentions of ascii in any files in 
/etc/apt/sources.list.d/


That's all I have for ideas right now.

fsmithred
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Future of gNewSense: Debian or Devuan?

[fsmithred via Dng]

On 8/1/19 12:26 PM, Steve Litt wrote:


Anyway, if this is a suggestion to yank all nonfree out of Devuan and
call it something else, that's fine with me. As a matter of fact,
Devuan could slowly, selectively and judiciously make the same
substitutions as the child distro.


There's not really anything to yank out. Don't have a non-free repo and 
don't put non-free firmware on the installer isos. They probably also want 
to use a libre kernel. This is not a difficult task, and gnuinos already 
does this.


If devuan ever provides a free/libre repo and release, it will be in 
addition to the one that provides non-free firmware for the same reasons 
you state below. This is something that's been discussed at meetings 
several times, and I think we're all in agreement.






But if the suggestion is to yank out nonfree and call it Devuan, for
practical purposes that would make Devuan unbootable for a lot of
people. Malfunctions during boot can have causes depending on tens or
hundreds of factors, many hidden away. It's a bridge too far to
expect someone booting up a distro for the first time to 1)
Know all his hardware, 2) Know exactly what drivers and firmware to
use, 3) Know where to find those drivers and firmware, 4) Know all the
commands to correctly load those drivers and firmware from a thumb
drive, and 5) Have enough spare time to go through all this.



Anyone who thinks otherwise should search the list archives for 'broadcom'.

fsmithred
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Installing fresh copy of x86_64 Beowulf?

[fsmithred via Dng]

On 7/31/19 9:08 AM, Lars Noodén via Dng wrote:

On 7/28/19 6:33 PM, goli...@devuan.org wrote:

On 2019-07-28 09:29, rgsid...@sunrise.ch wrote:

Hi, with the actual image, I encountered only one problem. I tried to
install it from a USB-stick, but the installer mixed up the partitions
and installed on /dev/sdb instead of /dev/sda. You have to correct
grub and the fstab respectively to avoid a non bootable  system. And
be aware, that there won't be a gksu-package anymore and you should
check, if there aren't any consolekit-related packages installed
erroneously. Replace them with the whole lot of elogind-stuff and
everything will just work fine .

Sincerely


Roland


[...]



There is no official Beowulf image because Beowulf hasn't been released
yet.

golinux


Ok.  Thanks everybody

The approach I tried was to install a minimal Ascii setup and then
s/ascii/beowulf/ in sources.list then do an upgrade and a dist-upgrade.
It seem to work ok for a server, I've had it running the last few days..
  I've not run into new errors, just old ones.

/Lars



I've used the same method to upgrade a Refracta (ascii) install, and it 
worked well. This is with xfce and desktop apps installed without 
metapackages.


If you try to upgrade a desktop system that was installed from tasksel 
(with task--desktop), you'll probably run into 
dependency conflicts.


One other way to get there is to make a beowulf live-iso with live-sdk. I 
haven't tried it in a few months, but it worked fine when I did it.

Results of that are here (no-X):
https://get.refracta.org/files/testing/
and here (openbox, no dbus):
https://get.refracta.org/files/experimental/refracta10-nodbus_amd64-2019-04-16.iso
(Blend files available on request. Modify and make your own.)

fsmithred
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] reinstalling GRUB2

[fsmithred via Dng]

On 7/27/19 2:52 PM, Haines Brown wrote:

I'm installing Ascii->Beowulf on a separate hard disk, but obviously
would like to make my current disk bootable as well.





But still can't install GRUB:

   # grub-install
   bash: grub-install: command not found



Since your su is acting like it's from beowulf, you should probably treat 
it like it is. Did you try using 'su -' instead of 'su'? If not, then 
using the full path should work:

  /usr/sbin/grub-install




I will run # e2fsck -p -f and then reboot and try to install Grub
again. But given the problem might be a damaged hard disk, safest
would be to concentrate on getting my system working on the new disk
before experimenting with the old to get its GRUB working.


Good plan.

To test the drive, install smartmontools (on the new system) and run 
'smartctl -a /dev/sda' (or /dev/sdb, or do both.)




Incidentally, in pursuit of this problwm I encountered a site:
http://cdbug.org/file-system/linux-error-writing-read-only-file-system.php
The page title ls: "Linux Error Writing Read Only File System". A
pop-up that cannot be dismissed insisted I download a php automatic
repair utility before being able to read more of the page. What I did
read was that a reason for the error might be invalid entries in my
Windows registry. I suspected malware and ran away rather than
download the utility.



I'll bet your registry is exactly where it needs to be. (Reminds me of the 
guys who call me up to say my computer might have a virus.) Maybe you need 
better shielding on your browser. (noscript, ublock, something else?)


fsr
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] reinstalling GRUB2

[fsmithred via Dng]

On 7/25/19 7:46 AM, Haines Brown wrote:

On Thu, Jul 25, 2019 at 06:59:02AM -0400, fsmithred via Dng wrote:

On 7/24/19 4:40 PM, Haines Brown wrote:

I've no idea what's going on.


I think you got a non-devuanized util-linux from ascii-security. That
package has been replaced. You should be able to get the right one with the
following commands.



or if those fail,
apt-get install util-linux=2.29.2-1+devuan2.1


util-linux-2.29.2-1+devuan2.1 is the version I'm already currently
running. But thanks for the suggetion.

Haines



Uh... yeah, right. Twilight Zone.

As user:
  which su

Also as user:
  aptitude search ~i -F"%p# %v# %t#"
and see if you have packages from testing or unstable.

fsr

___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] reinstalling GRUB2

[fsmithred via Dng]

On 7/24/19 4:40 PM, Haines Brown wrote:
  
I've no idea what's going on. 


I think you got a non-devuanized util-linux from ascii-security. That 
package has been replaced. You should be able to get the right one with 
the following commands.


su -
apt-get update
apt-get install util-linux

or
apt-get upgrade

or if those fail,
apt-get install util-linux=2.29.2-1+devuan2.1


fsmithred
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] reinstalling GRUB2

[fsmithred via Dng]

On 7/24/19 4:40 PM, Haines Brown wrote:


When I become root with "su", I get the following:

   # grub-install
   bash: grub-install: command not found

   # /usr/sbin/grub-install
   bash: /usr/sbin/grub-install: No such file or directory


How are you becoming root? In ascii, either 'su' or 'su -' will give you
*/sbin in your path.


When I am root by means of su - I get the following:

   $ su -
   # grub-install
   Installing for i386-pc platform.
   grub-install: error: install device isn't specified.

   # /usr/sbin/grub-install
   Installing for i386-pc platform.
   /usr/sbin/grub-install: error: install device isn't specified.


In the second case (su -) it finds the command and fails because you 
didn't tell it where to put the bootloader. Like this:


  grub-install /dev/sdb

And then you can run update-grub (for which you do not specify a device.)

Please also run/check the following:

uname -r
cat /etc/issue
cat /etc/devuan_version
apt-cache policy util-linux

fsmithred

___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] reinstalling GRUB2

[fsmithred via Dng]

On 7/24/19 10:45 AM, Haines Brown wrote:

I seem to be loosing ground. Someone helped me with the chroot method,
but then:

# grub2-install /dev/sdb
bash: grub2-install: command not found

# grub-install /dev/sdb
bash: grub-install: command not found

# ls -la /usr/sbin | grep grub-install
ls: cannot access '/usr/sbin': No such file or directory

# ls -la /usr | grep sbin
[no return]

$ ls -la /usr | grep sbin
drwxr-xr-x   2 root root  12288 Jul 24 08:30 sbin

I've no idea what's going on. I was told to use the grub2-install
command, but on my system (Ascii) there is only
/usr/sbin/grub-install. 


grub-install is all I've ever used or seen mentioned in debian.


It seems my grub-install command can be run
by user, 


Please describe what happens when user runs grub-install. And what do you 
get when you run

echo $PATH
as user and as root?

but not by root becasue root has no path to /usr/sbin.

That was my first thought, until I read the  following in your previous post:


# /usr/sbin/grub-install /dev/sdb
# bash: /usr/sbin/grub-install: No such file or directory


It should run when you call it with the full path, even if /usr/sbin is 
not in your path.


How are you becoming root? In ascii, either 'su' or 'su -' will give you 
*/sbin in your path. In beowulf, only 'su -' will give you root's path. 
Just plain 'su' leaves you with user's path.


(OT) Does anyone know why they changed the behavior of su? Is there a 
reason why root should have /usr/share/games in the path?





Probably not relevant is that every morning I get this cron error:
/etc/cron.daily/apt-compat:
Cache has broken packages, exiting



What happens if you empty the cache with 'apt-get clean' or the equivalent?

fsmithred
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] reinstalling GRUB2

[fsmithred via Dng]

On 7/22/19 12:40 PM, Haines Brown wrote:


So I do
 ...

 # chroot /sysroot

 # grub-install /dev/sdb
 bash grub-install: command not found

 # ls -la /usr/sbin | grep grub-install
 -rwxr-xr-x 1 root root 102046 Oct 28 2018 grub-install

 # /usr/sbin/grub-install /dev/sdb
 # bash: /usr/sbin/grub-install: No such file or directory

At my wits end I remove and reinstall grub2-common. Did not help.



That's pretty weird. If you reinstall the grub-pc package, it will run a 
debconf dialog and ask you where to put the bootloader. I don't know if it 
operates like that in alternate realities, and i think you might be in one.


Check the size on your grub-install. It looks small. (Copy/paste error?)

/usr/sbin/grub-install:
ascii/uefi   1020496 Oct 28  2018


fsmithred
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] reinstalling GRUB2

[fsmithred via Dng]

On 7/22/19 1:48 AM, Steve Litt wrote:

On Sun, 21 Jul 2019 20:25:42 +0100
Simon Hobson  wrote:





2) use these incantations, lifted from a post elsewhere :

mkdir /sysroot
mount /dev/your-root-dev /sysroot
mount /dev/your-boot-dev /sysroot/boot
mount --bind /dev /sysroot/dev
mount --bind /sys /sysroot/sys
mount --bind /proc /sysroot/proc
mount --bind /run /sysroot/run (recommended if you are using systemd)
chroot /sysroot
grub-install /dev/your-grub-boot-device (may be grub2-install on some
distro)


*Exactly* what do you mean by "your-grub-boot-device"? Does it vary
depending on MBR vs UEFI?


Yes, it varies depending on BIOS vs. UEFI boot. For bios boot, the grub 
boot device is the drive whose mbr you want to use, like /dev/sda or /dev/sdb.


For UEFI, you don't name the device. Grub knows to put the bootloader in 
the efi partition. In that case, an extra step above would be to mount the 
efi partition to /sysroot/boot/efi




So now you've installed Grub(2), but then how do you configure grub?


While you are still in the chroot, run:

update-grub

And that will make a new boot menu.



fsmithred



___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Systemd depends on random numbers in order to work properly

[fsmithred via Dng]

On 7/9/19 5:07 AM, Martin Steigerwald wrote:

Martin Steigerwald - 09.07.19, 10:54:


Just *booting* the system should not depend on enough entropy being
available. Starting services that need entropy may be delayed, but
just booting should not depend on entropy being available.


This is enlightening:

Openssh taking minutes to become available, booting takes half an hour
... because your server waits for a few bytes of randomness

https://daniel-lange.com/archives/152-hello-buster.html

According Daniel Systemd developers are basically getting it wrong to
the maximum extent possible.



Live-isos with openssh-server hang on boot while waiting for enough 
entropy to make new host keys. I get this with sysvinit (in Devuan). I 
made a live-config script to start haveged before openssh-server starts to 
fix it.


fsmithred

___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Firefox-esr freezes ASCII

[fsmithred via Dng]

On 7/9/19 4:34 AM, Edward Bartolo via Dng wrote:

For the information of everyone:

I would like to inform all those concerned that firefox-esr is causing
ASCII to freeze. Getting access to a terminal is almost impossible.
Yesterday, I had to power off the machine. I did not investigate why
the issue is happening as the system became extremely unresponsive.
Recalling when I used MS Windows 95/98/Millenium, this is worse than
those.




I get the same in jessie. It starts when memory use gets to around 75% or 
more. It hasn't happened to me in ascii, but the box that has ascii also 
has 8G ram.


Recently, I read something that said firefox will require 2-3G of memory 
in the near future. We can look forward to more of this happening.


What I do when it starts to slow down is ctrl-alt-F2, log in and start 
killing programs. Thunderbird is usually on that kill list, because it 
takes a lot of ram, too. If I wait too long to do that, it freezes. At 
some point, even sysrq keys won't work.


fsmithred


___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] ..so Debian is Busting postgresql, evolution-ews inboxes and history itself?, was: Runit service depend another script not daemon

[fsmithred via Dng]

On 7/7/19 10:29 AM, Arnt Karlsen wrote:



..5.3.8.  Calamares installer leaves disk encryption keys readable:
https://www.debian.org/releases/buster/amd64/release-notes/ch-information.en.html#calamares-creates-readable-key



Is this referring to the use of a keyfile in the initrd? Or is this the 
case in all encrypted debian-based systems, whether /boot is part of the 
encrypted volume or not?



Bug report says:

"It installs an encryption key in the initramfs, the problem is
that in Debian, the initramfs is world readable by default, which
means that a user on an unlocked system could retrieve the unlock
key."


/etc/cryptsetup-initramfs/conf-hook says:

# KEYFILE_PATTERN: ...
#
# The value of this variable is interpreted as a shell pattern.
# Matching key files from the crypttab(5) are included in the initramfs
# image.  The associated devices can then be unlocked without manual
# intervention.  (For instance if /etc/crypttab lists two key files
# /etc/keys/{root,swap}.key, you can set KEYFILE_PATTERN="/etc/keys/*.key"
# to add them to the initrd.)


Thanks to anyone who can shed some light on this.

fsmithred



___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] UEFI support in the live-sdk

[fsmithred via Dng]

On 7/6/19 7:16 AM, aitor_czr wrote:


First of all, are you using the latest sources:

$ git clone https://git.devuan.org/aitor_czr/live-sdk.git



No, I'm using the copy I cloned at the end of May. It worked for me then; 
I did not change anything, so I expect it should work now.



On the other hand, i must admit that i didn't update the repository of 
gnuinos during weeks; so, it couldn't work. did you select this choice?


I selected Devuan, stable, main. Same as last time. Today I tried changing 
the mirror from deb.devuan.org to pkgmaster.devuan.org but it didn't make 
any difference. It pulls down Packages.gz and then stops.



--2019-07-06 12:28:41-- 
http://pkgmaster.devuan.org/merged/dists/ascii/main/debian-installer/binary-amd64/Packages.gz

Resolving pkgmaster.devuan.org (pkgmaster.devuan.org)... 5.196.38.18
Connecting to pkgmaster.devuan.org 
(pkgmaster.devuan.org)|5.196.38.18|:80... connected.

HTTP request sent, awaiting response... 200 OK
Length: 62636 (61K) [text/plain]
Saving to: ‘Packages.gz’

Packages.gz 
100%[===>]  61.17K   246KB/sin 
0.2s


2019-07-06 12:28:42 (246 KB/s) - ‘Packages.gz’ saved [62636/62636]

  .  libdevuansdk v1.0 loaded
  .  devuan blend leaded
livesdk@ascii  %


fsr
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] UEFI support in the live-sdk

[fsmithred via Dng]

On 5/30/19 4:54 PM, aitor_czr wrote:

Hi fsmithred,

On 30/5/19 15:30, fsmithred via Dng wrote:




Reboot into the system looks good. It installed the full system from the 
iso (without network)

:) :) :)

Now I have to look at it and figure out what you did.

fsmithred 


All these changes have been commited in the git repository. I'll build 
another image during this night...


Thanks a lot for your help, fsmithred :)

Cheers,

Aitor.



I'm just getting back to this now. I tried running it again without making 
any changes. Ran the following commands including the trivial steps to 
select repo, suite, etc. and it did not build.



# zsh -f

# source sdk

# load

the following steps are trivial. You can choose between the repository of 
devuan or gnuinos (a fully amprolla setup). Debian is a work in progress.



After the dialog, it just dumped me back to the zsh prompt. What am I 
missing? I tried build_iso_dist and it said "command not found."


Thanks,
fsmithred
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] installing Ascii on ryzen 7 1800x machine

[fsmithred via Dng]

On 5/31/19 1:47 AM, Gregory Nowak wrote:

Hi all.

I will be building a machine based on the ryzen 7 1800x CPU. From what
I've read, support for ryzen 7 starts with the 4.11.x kernel, however
Ascii comes with the 4.9.x kernel. My question is will I be able to do
a full install of Ascii on this machine without problems,


I made a live-iso of ascii with a backports kernel for this purpose. You 
could either install ascii from the media or use it to do a debootstrap 
install without removing the hard drive from the computer.

https://get.refracta.org/files/experimental/refracta-test-oblx-bpo-20180913_1952.iso

The build has openbox, lxpanel and very few apps.

fsmithred




___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng