Re: [DNG] gcc-doc
On Wed, 1 Sep 2021 12:33:38 +0200 "Antonio A. Rendina via Dng" wrote: > Hi, > > I remember that there was a discussion about this, but I'm no able to > find it anymore. The question is how do I install the gcc-doc package? > > For what I understand Debian put it on non-free, but on Devuan a have > non-free and contrib enabled and I still don't find it. On my Beowulf install, it's in backports. B ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] APT upgrade, was USB mount problem
On Thu, 8 Jul 2021 17:59:46 +0200 Alessandro Vesely via Dng wrote: > On Wed 07/Jul/2021 23:10:15 +0200 Patrick Bartek via Dng wrote: > > On Mon, 5 Jul 2021 19:41:43 +0200 > > Alessandro Vesely wrote: > >> > >> Here's the sequence of what I did: I wrote to the list each time, > >> so I know the exactly when. > >> > >> 4 January 2020: migrate from debian/stretch to beowulf > >> https://lists.dyne.org/lurker/message/20200104.101800.7b0f18cb.en.html > >> Beowulf was the stable version at the time. Afterwards, I upgraded > >> it regularly and smoothly. > > > > I'm assuming you didn't try to migrate from Stretch to Beowulf > > directly before doing the ascii migration. > > > Hm.. yes, you must be right. > > > > And I keep detailed logs of what I do. > > > On a server, I used to run release dist-upgrades under script. I > gave up after realizing I never dug into those files. The last time > I just kept the tripwire log. (Albeit tripwire leaves something to > be desired w.r.t., say, subversion.) > > None on those on a client, which is this case. My install log is very "low tech": I just write everything I installed, troubleshooted, fixed, etc step-by-step on yellow, legal-size paper even though apt-get has its own logs. I find a paper log easier to reference. > > >>> How did you remove those packages? > >> > >> No idea. Didn't remove them intentionally. Not even sure /when/ > >> they were removed. > > > > During your migration to Beowulf and dist-upgrade to Chimaera, and > > if you followed instructions, autoremove could have removed them as > > part of the cleanup. > > > >>> [snip] > >>> > >>> Upgrade by design won't install major upgrades to apps, system > >>> files, etc. which can occur with Testing. > >> > >> However, apt should still keep back unupgraded packages, so that if > >> you issue a dist-upgrade afterwards, it can find them and upgrade > >> them, correct? > > > > It should, but if you used autoremove, those "held back" packages > > will be removed and forgotten. > > > Ugh, the man page says: > > Packages which you have installed explicitly via install are also > never proposed for automatic removal. That's my understanding, too, but it doesn't apply to anything that's installed as a dependency. If the main application is dist-upgraded to a major version higher replacing the app you originally installed, then those old dependencies probably will show as held-back and autoremove will remove them since the old app which needed them is no longer installed. I get this when old kernels get removed by a regular upgrade (I have my system set up to only retain the previous kernel and no older ones), then all the old headers, etc are no longer needed, show as held-back, and autoremove removes them. > Inkscape must have been installed explicitly. It could have been installed as a dependency. When I initially installed my file manager, xfe, a lot (quite a lot, actually) of other utilities and apps were installed, so xfe could do its job. B ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] APT upgrade, was USB mount problem
On Mon, 5 Jul 2021 19:41:43 +0200 Alessandro Vesely wrote: > Hi, > > On Sun 04/Jul/2021 21:09:01 +0200 Patrick Bartek wrote: > > On Sat, 3 Jul 2021 13:01:52 +0200 > > Alessandro Vesely via Dng wrote: > >> On Sat 26/Jun/2021 01:10:08 +0200 Patrick Bartek Via Dng wrote: > >>> On Fri, 25 Jun 2021 11:34:32 +0200 > >>> Alessandro Vesely via Dng wrote: > >>>> After I did a system upgrade, I couldn't mount an USB key any > >>>> more, until I manually installed udevil. What happened, > >>>> dependency changes? > >>> > >>> This is one of the "gotchas" that can happen when running an "in > >>> development" version. As far as why it happen: could be a number > >>> of things. Most of the time, it's because a dependency, like > >>> udevil to spacefm, become mismatched version-wise. That is, > >>> udevil has become "too old" to work with spacefm, and the upgrade > >>> process uninstalls it. Try "full-grade" instead of just "upgrade" > >>> to get the newer version of the dependencies when "upgrading." In > >>> fact, this is the recommended procedure when running an "in > >>> development" or testing version. > >> > >> I tried apt-get dist-upgrade afterwards, but it didn't bring up > >> much staff. Later on, I found that some software that I don't use > >> very often was removed from my system. I had to install anew > >> Inkscape and MariaDB server. > > > > Without knowing the particulars of how you installed Chimaera or how > > it's configured, it's going to be difficult to diagnose your > > problems. However, the main problem is that you are using Chimaera > > which is still in development, and that can introduce problems. > > Although, usually, they correct themselves when the developers do > > the next round of "fixes." > > > > Did you do a clean install or upgrade from a previous version? IIRC, > > you dist-upgraded from a Debian distro, but I've forgotten which > > one. This can and does introduce problems even if done correctly. > > > Here's the sequence of what I did: I wrote to the list each time, so > I know the exactly when. > > 4 January 2020: migrate from debian/stretch to beowulf > https://lists.dyne.org/lurker/message/20200104.101800.7b0f18cb.en.html > Beowulf was the stable version at the time. Afterwards, I upgraded > it regularly and smoothly. I'm assuming you didn't try to migrate from Stretch to Beowulf directly before doing the ascii migration. I've avoid dist-upgrades between releases unless I had no other choice. Too many chances for problems even if everything is done correctly. Something you have already discovered. I prefer clean installs. And I keep detailed logs of what I do. So, when I "upgraded" from Wheezy to Stretch to Beowulf, I knew what was and was not installed initially, and in what sequence and when. But back to your glitches . . . When you dist-upgraded from ascii to Beowulf -- Beowulf was still Testing, that is, it wasn't Stable at that time, right? -- you should have continued to use dist-upgrade with Beowulf until it became Stable, then switch to upgrade. If you didn't, this have could cause problems. You should be doing the same with Chimeara until it becomes Stable. > > 19 April 2021: upgrade from beowulf to chimaera. > https://lists.dyne.org/lurker/message/20210419.111049.2c050382.en.html > As I wrote at the time: > > Everything incredibly smooth! > > I don't know why I rebooted between upgrade and dist-upgrade. > The graphics didn't come up, so I run dist-upgrade on the tty > terminal. That's the only annoyance I had. See what can happen when upgrade is used when dist-upgrade should have been. > Heck, the process took an inordinate amount of time. autoremove > is still running for 435 packages... Isn't there a way to remove > packages not used for more than one year? This is normal after a dist-upgrade and autoremove. You should also autoclean as well. > > 24 June 2021: apt-get update + apt-get upgrade > https://lists.dyne.org/lurker/message/20210625.093432.02c220e2.en.html > I hadn't updated the system since April. > > Network printer and usb key access were damaged by the upgrade. I'm > sure I used both between Apr 19 and Jun 24. For the printer, I just > deleted and discovered it again. For spacefm, I installed udevil. I > found no relevant differences in spacefm dependencies. I'm not sure > whether udevil was installed before (it is suggested). Perhaps usb > access was granted
Re: [DNG] APT upgrade, was USB mount problem
On Mon, 5 Jul 2021 07:19:50 -0400 Hendrik Boom wrote: > On Sun, Jul 04, 2021 at 12:09:01PM -0700, Patrick Bartek via Dng > wrote: > > On Sat, 3 Jul 2021 13:01:52 +0200 > > Alessandro Vesely via Dng wrote: > > > > > Hi, > > > > > > On Sat 26/Jun/2021 01:10:08 +0200 Patrick Bartek Via Dng wrote: > > > > On Fri, 25 Jun 2021 11:34:32 +0200 > > > > Alessandro Vesely via Dng wrote: > > > >> After I did a system upgrade, I couldn't mount an USB key any > > > >> more, until I manually installed udevil. What happened, > > > >> dependency changes? > > > > > This is one of the "gotchas" that can happen when running an "in > > > > development" version. As far as why it happen: could be a > > > > number of things. Most of the time, it's because a dependency, > > > > like udevil to spacefm, become mismatched version-wise. That > > > > is, udevil has become "too old" to work with spacefm, and the > > > > upgrade process uninstalls it. Try "full-grade" instead of just > > > > "upgrade" to get the newer version of the dependencies when > > > > "upgrading." In fact, this is the recommended procedure when > > > > running an "in development" or testing version. > > > > > > > > > I tried apt-get dist-upgrade afterwards, but it didn't bring up > > > much staff. Later on, I found that some software that I don't > > > use very often was removed from my system. I had to install anew > > > Inkscape and MariaDB server. > > > > Without knowing the particulars of how you installed Chimaera or how > > it's configured, it's going to be difficult to diagnose your > > problems. However, the main problem is that you are using Chimaera > > which is still in development, and that can introduce problems. > > Although, usually, they correct themselves when the developers do > > the next round of "fixes." > > > > Did you do a clean install or upgrade from a previous version? IIRC, > > you dist-upgraded from a Debian distro, but I've forgotten which > > one. This can and does introduce problems even if done correctly. > > > > Post your /etc/apt/sources.list and anything that is > > in /etc/apt/sources.list.d/, too. If they are not set up properly, > > that can cause problems. > > > > > I remember many release changes done in two steps, apt-get > > > upgrade followed by apt-get dist-upgrade for the rest. This time > > > it seems that the system forgot about removed packages. Is it so > > > because chimaera is not yet released? > > > > How did you remove those packages? > > > > No. Chimaera still being Testing shouldn't be a cause.. > > > > When using Testing, don't use apt-get upgrade, but only apt-get > > dist-upgrade or apt full-upgrade. This is recommended when > > running Testing instead of Stable. Upgrade by design won't install > > major upgrades to apps, system files, etc. which can occur with > > Testing. > > How does it distinguish between an upgrade and a major upgrade? By the version number of the files already installed. So, AnApplication-1.0.2 to AnApplication-1.0.5, apt-get upgrade will upgrade (So, will dist-upgrade), but apt-get upgrade won't upgrade 1.0.x to 1.1.y, but dist-upgrade will. Neither will upgrade 1.x to 2.y. B ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] APT upgrade, was USB mount problem
On Sat, 3 Jul 2021 13:01:52 +0200 Alessandro Vesely via Dng wrote: > Hi, > > On Sat 26/Jun/2021 01:10:08 +0200 Patrick Bartek Via Dng wrote: > > On Fri, 25 Jun 2021 11:34:32 +0200 > > Alessandro Vesely via Dng wrote: > >> After I did a system upgrade, I couldn't mount an USB key any > >> more, until I manually installed udevil. What happened, > >> dependency changes? > > > This is one of the "gotchas" that can happen when running an "in > > development" version. As far as why it happen: could be a number of > > things. Most of the time, it's because a dependency, like udevil to > > spacefm, become mismatched version-wise. That is, udevil has become > > "too old" to work with spacefm, and the upgrade process uninstalls > > it. Try "full-grade" instead of just "upgrade" to get the newer > > version of the dependencies when "upgrading." In fact, this is the > > recommended procedure when running an "in development" or testing > > version. > > > I tried apt-get dist-upgrade afterwards, but it didn't bring up much > staff. Later on, I found that some software that I don't use very > often was removed from my system. I had to install anew Inkscape and > MariaDB server. Without knowing the particulars of how you installed Chimaera or how it's configured, it's going to be difficult to diagnose your problems. However, the main problem is that you are using Chimaera which is still in development, and that can introduce problems. Although, usually, they correct themselves when the developers do the next round of "fixes." Did you do a clean install or upgrade from a previous version? IIRC, you dist-upgraded from a Debian distro, but I've forgotten which one. This can and does introduce problems even if done correctly. Post your /etc/apt/sources.list and anything that is in /etc/apt/sources.list.d/, too. If they are not set up properly, that can cause problems. > I remember many release changes done in two steps, apt-get upgrade > followed by apt-get dist-upgrade for the rest. This time it seems > that the system forgot about removed packages. Is it so because > chimaera is not yet released? How did you remove those packages? No. Chimaera still being Testing shouldn't be a cause.. When using Testing, don't use apt-get upgrade, but only apt-get dist-upgrade or apt full-upgrade. This is recommended when running Testing instead of Stable. Upgrade by design won't install major upgrades to apps, system files, etc. which can occur with Testing. After Testing (Chimaera) becomes Stable, then use only apt-get upgrade or apt upgrade. There are times when dist-upgrade needs to be used to "fix" something, but we'll deal with that later. B ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] USB mount problem
On Sat, 26 Jun 2021 04:45:46 -0500 o1bigtenor wrote: > On Fri, Jun 25, 2021 at 6:10 PM Patrick Bartek via Dng > wrote: > > > > On Fri, 25 Jun 2021 11:34:32 +0200 > > Alessandro Vesely via Dng wrote: > > > > > On Tue 15/Jun/2021 20:41:09 +0200 Patrick Bartek via Dng wrote: > > > > > > > > I have found that each desktop uses its own method of > > > > automounting. PCManFM may have the mounting code built-in. Or > > > > it may use udiskie. Check PCManFM's dependencies and see if > > > > udiskie is listed. Did you install udiskie yourself? If not, > > > > then some other app did and it's probably needed. If it's not > > > > causing problems, leave it be. > > > > > > > > > Right. For spacefm it is udevil. > > > > > > Curiously, spacefm was mounting smoothly until yesterday, on > > > chimaera > > > + openbox. After I did a system upgrade, I couldn't mount an USB > > > key any more, until I manually installed udevil. What happened, > > > dependency changes? > > > > This is one of the "gotchas" that can happen when running an "in > > development" version. As far as why it happen: could be a number of > > things. Most of the time, it's because a dependency, like udevil to > > spacefm, become mismatched version-wise. That is, udevil has become > > "too old" to work with spacefm, and the upgrade process uninstalls > > it. Try "full-grade" instead of just "upgrade" to get the newer > > version of the dependencies when "upgrading." In fact, this is the > > recommended procedure when running an "in development" or testing > > version. > > Please - - - not understanding the command(s) suggested. > I usually use : > # apt update > # apt upgrade > > so you're suggesting the use of > # apt update > # apt full-grade > or is that > # apt full-upgrade? > > TIA full-upgrade. Sorry. Or apt-get dist-upgrade will accomplish the same thing. B ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] USB mount problem
On Fri, 25 Jun 2021 11:34:32 +0200 Alessandro Vesely via Dng wrote: > On Tue 15/Jun/2021 20:41:09 +0200 Patrick Bartek via Dng wrote: > > > > I have found that each desktop uses its own method of automounting. > > PCManFM may have the mounting code built-in. Or it may use udiskie. > > Check PCManFM's dependencies and see if udiskie is listed. Did you > > install udiskie yourself? If not, then some other app did and it's > > probably needed. If it's not causing problems, leave it be. > > > Right. For spacefm it is udevil. > > Curiously, spacefm was mounting smoothly until yesterday, on chimaera > + openbox. After I did a system upgrade, I couldn't mount an USB key > any more, until I manually installed udevil. What happened, > dependency changes? This is one of the "gotchas" that can happen when running an "in development" version. As far as why it happen: could be a number of things. Most of the time, it's because a dependency, like udevil to spacefm, become mismatched version-wise. That is, udevil has become "too old" to work with spacefm, and the upgrade process uninstalls it. Try "full-grade" instead of just "upgrade" to get the newer version of the dependencies when "upgrading." In fact, this is the recommended procedure when running an "in development" or testing version. B ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] ntp setup
On Sat, 19 Jun 2021 09:31:23 -0500 o1bigtenor via Dng wrote: > Greetings > > Noticed that my new Beowulf install time was not accurate. > > Went looking for a tips page and all I could find was information > relating to using systemd and or its tools to do such. I know there is > a way to do this without systemd - - - - - just - - - its been a very > long time since I've done that. > > Please - - - anyone for a short writeup on how to > install/start/whatever else to ntp without using systemd? apt install ntp-doc Then load in your browser file:///usr/share/doc/ntp-doc/html/quick.html That should get you started. B ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] [OT] historical note
On Thu, 17 Jun 2021 18:46:27 -0700 Marc Shapiro via Dng wrote: > On 6/17/21 4:59 PM, Patrick Bartek via Dng wrote: > > On Wed, 16 Jun 2021 20:02:35 -0400 > > Hendrik Boom wrote: > > > >> On Wed, Jun 16, 2021 at 01:29:12PM -0700, Patrick Bartek via Dng > >> wrote: ... > >> ... > >>> Jessie was the first Debian version to use systemd by default as > >>> the init. Perhaps, something was installed as a systemd dependency > >>> that wouldn't have been installed with the new Beowulf computer > >>> under sysvinit that carried forward with a dist-upgrade of Jessie > >>> to Beowulf. Or you installed something on the old system that > >>> wasn't installed on the new one, and that is doing the > >>> automounting. > >> Historical note. > >> > >> And the first Devuan release was called Jessie because it was > >> almost identical to the Debian release with the same name -- it > >> differed primarily in that it did not use systemd as an init. > >> This was the last Debian relese that had no problems running > >> without systemd. > > I run Debian Stretch with sysvinit without problems even though some > > systemd libraries and udev-systemd remained after converting to > > sysvinit. Even updates-upgrades don't result in systemd-init being > > reinstalled like with Buster. > > > > B > > I ran Debian from Bo through Stretch. I had no real problems > upgrading through the releases until I got to Buster. Then I hit a > wall. It MAY be possible to run a very minimal system (with no > chance of running X) and still avoid systemd. While I have been told > that this is the case, I have no personal evidence of this. > > That is what caused me to switch to Devuan. When testing Buster, I was able to run a terminal only system with sysvinit which survived update-upgrade; however, when I tried to install X, sysvinit was uninstalled and systemd init replaced it. I could replace with sysvinit, but whenever I did an update-upgrade systemd init would again be reinstalled. What caused it was a dependency. Some file (dbus. IIRC) that was an X dependency had a systemd library dependency which was present by the way; however, systemd init got installed, too. Never discovered why. And if I tried to "block" systemd init from installing, the upgrade would fail. Systemd had finally become too pervasive to deal with easily as I figured it eventually would be. Like you, I abandoned Debian and went to Devuan. B ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] [OT] historical note
On Wed, 16 Jun 2021 20:02:35 -0400 Hendrik Boom wrote: > On Wed, Jun 16, 2021 at 01:29:12PM -0700, Patrick Bartek via Dng > wrote: ... > ... > > > > Jessie was the first Debian version to use systemd by default as > > the init. Perhaps, something was installed as a systemd dependency > > that wouldn't have been installed with the new Beowulf computer > > under sysvinit that carried forward with a dist-upgrade of Jessie to > > Beowulf. Or you installed something on the old system that wasn't > > installed on the new one, and that is doing the automounting. > > Historical note. > > And the first Devuan release was called Jessie because it was almost > identical to the Debian release with the same name -- it differed > primarily in that it did not use systemd as an init. This was the > last Debian relese that had no problems running without systemd. I run Debian Stretch with sysvinit without problems even though some systemd libraries and udev-systemd remained after converting to sysvinit. Even updates-upgrades don't result in systemd-init being reinstalled like with Buster. B ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] USB mount problem
On Thu, 17 Jun 2021 09:04:06 +0200 al3xu5 wrote: > Tue, 15 Jun 2021 11:41:09 -0700 - Patrick Bartek > : > > > On Mon, 14 Jun 2021 17:59:24 +0200 > > al3xu5 wrote: > > > > > [...] > > > I have openbox+lxde & PCManFM: usb drives are automatically > > > mounted (by udisks2) and are shown and usable (open and umount) > > > thanks to PCManFM. > > > > > > I have also udiskie, which i nice, but not strictly necessary in > > > my case... Am I right? > > > > I have found that each desktop uses its own method of automounting. > > PCManFM may have the mounting code built-in. Or it may use udiskie. > > Check PCManFM's dependencies and see if udiskie is listed. > > No: PCManFM do not require udiskie. I think you are right saying it > should have the mounting code built-in. Or it uses some other method. As long as it works. :) B ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] USB mount problem
On Tue, 15 Jun 2021 12:32:25 -0700 Fred wrote: > On 6/15/21 11:28 AM, Patrick Bartek via Dng wrote: > > On Mon, 14 Jun 2021 07:56:39 -0700 > > Fred wrote: > > > >> On 6/13/21 9:37 PM, Patrick Bartek via Dng wrote: > > > >>>>>>> [big snip] > >>>>>> Hi, > >>>>>> I found udisks2 installed on the computer that automatically > >>>>>> mounts USB devices but there is no man page so I would not know > >>>>>> how to use it if installed on the other computer. > >>>>> > >>>>> Not much to using it: apt-get install udisks2 and everything > >>>>> gets set up. I used the defaults. Devices are mounted > >>>>> under /media/"your username". If you run a panel, the udisks2 > >>>>> gadget shows up there with additional options. Manual unmounting > >>>>> is necessary, but I use only a window manager (Openbox) and > >>>>> lxpanel for my GUI, so your mileage may vary if you use a > >>>>> desktop environment. > >>>>> > >>>>> Others have shown you how to access the mans. So, I won't > >>>>> repeat that. > >>>>> > >>>>> B > >>>>> ___ > >>>>> Dng mailing list > >>>>> Dng@lists.dyne.org > >>>>> https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng > >>>>> > >>>> Hello, > >>>> I still need some help with this. > >>>> I installed udisks2. The last line of the installation dialog > >>>> showed what I believe is a warning, maybe of no consequence: > >>> > >>> I did some checking -- It's been a while since I installed Beowulf > >>> and udisks2 -- and I discovered that you need to use a "front end" > >>> for udisks2 for it to truly automount. I used udiskie > >>> (https://pypi.org/project/udiskie/) which must be started > >>> manually. Installing it doesn't automatically set it up to > >>> start. I just added a stanza to Openbox's autostart script. > >>> Since I use lxpanel in addition to Openbox, I added the > >>> "--smart-tray" option, so udiskie will appear in the panel when > >>> it's in use. > >> > >> The computer that was upgraded from Debian Jessie to Beowulf x86 > >> doesn't have any "front end" for udisks2 installed unless it was > >> installed automagically. This computer automounts USB devices > >> in /media as one of usb0-7. The one I am having trouble with is a > >> new install of Beowulf AMD64. > > > > What desktop was the Jessie computer running before your > > dist-upgrade to Beowulf? And after? Many times desktops have their > > own way of handling automounting usb devices. > > > > The usb mountpoint as /media/usb[0-7] is contrary to the default > > that udisks2 uses, namely: /media//. Jessie > > may have been using udev rules to mount usb. That's the way you > > automounted external devices with Wheezy at least. Jessie came > > with improvements. Check /etc/udev/rules.d to see if there is > > anything there. udev rules should survive a dist-upgrade. > > > > If there is a udev rule to automount, copying it over to your new > > Beowulf computer should work. > > > Hi, > The Jessie computer has never used any desktop/DE. Only openbox and > xterms. I never installed any utility to mount usb devices. > /etc/udev/rules.d has 70-persistent-net.rules which has one line > concerning ethernet. Jessie was the first Debian version to use systemd by default as the init. Perhaps, something was installed as a systemd dependency that wouldn't have been installed with the new Beowulf computer under sysvinit that carried forward with a dist-upgrade of Jessie to Beowulf. Or you installed something on the old system that wasn't installed on the new one, and that is doing the automounting. Of course, this is all speculation. It would have been nice if you had notes of what you installed on both systems. Right now, I doubt if you'll be able to discover (in a timely manner) what's causing the old system to automount and the new one not. B ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] USB mount problem
On Mon, 14 Jun 2021 17:59:24 +0200 al3xu5 wrote: > Sun, 13 Jun 2021 21:37:45 -0700 - Patrick Bartek > : > > > [...] > > > I did some checking -- It's been a while since I installed Beowulf > > and udisks2 -- and I discovered that you need to use a "front end" > > for udisks2 for it to truly automount. I used udiskie > > (https://pypi.org/project/udiskie/) which must be started manually. > > Installing it doesn't automatically set it up to start. I just > > added a stanza to Openbox's autostart script. Since I use lxpanel > > in addition to Openbox, I added the "--smart-tray" option, so > > udiskie will appear in the panel when it's in use. > > Hi Patrick > > I have openbox+lxde & PCManFM: usb drives are automatically mounted > (by udisks2) and are shown and usable (open and umount) thanks to > PCManFM. > > I have also udiskie, which i nice, but not strictly necessary in my > case... Am I right? I have found that each desktop uses its own method of automounting. PCManFM may have the mounting code built-in. Or it may use udiskie. Check PCManFM's dependencies and see if udiskie is listed. Did you install udiskie yourself? If not, then some other app did and it's probably needed. If it's not causing problems, leave it be. B ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] USB mount problem
On Mon, 14 Jun 2021 07:56:39 -0700 Fred wrote: > On 6/13/21 9:37 PM, Patrick Bartek via Dng wrote: > >>>>> [big snip] > >>>> Hi, > >>>> I found udisks2 installed on the computer that automatically > >>>> mounts USB devices but there is no man page so I would not know > >>>> how to use it if installed on the other computer. > >>> > >>> Not much to using it: apt-get install udisks2 and everything gets > >>> set up. I used the defaults. Devices are mounted > >>> under /media/"your username". If you run a panel, the udisks2 > >>> gadget shows up there with additional options. Manual unmounting > >>> is necessary, but I use only a window manager (Openbox) and > >>> lxpanel for my GUI, so your mileage may vary if you use a desktop > >>> environment. > >>> > >>> Others have shown you how to access the mans. So, I won't repeat > >>> that. > >>> > >>> B > >>> ___ > >>> Dng mailing list > >>> Dng@lists.dyne.org > >>> https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng > >>> > >> Hello, > >> I still need some help with this. > >> I installed udisks2. The last line of the installation dialog > >> showed what I believe is a warning, maybe of no consequence: > > > > I did some checking -- It's been a while since I installed Beowulf > > and udisks2 -- and I discovered that you need to use a "front end" > > for udisks2 for it to truly automount. I used udiskie > > (https://pypi.org/project/udiskie/) which must be started manually. > > Installing it doesn't automatically set it up to start. I just > > added a stanza to Openbox's autostart script. Since I use lxpanel > > in addition to Openbox, I added the "--smart-tray" option, so > > udiskie will appear in the panel when it's in use. > > The computer that was upgraded from Debian Jessie to Beowulf x86 > doesn't have any "front end" for udisks2 installed unless it was > installed automagically. This computer automounts USB devices > in /media as one of usb0-7. The one I am having trouble with is a > new install of Beowulf AMD64. What desktop was the Jessie computer running before your dist-upgrade to Beowulf? And after? Many times desktops have their own way of handling automounting usb devices. The usb mountpoint as /media/usb[0-7] is contrary to the default that udisks2 uses, namely: /media//. Jessie may have been using udev rules to mount usb. That's the way you automounted external devices with Wheezy at least. Jessie came with improvements. Check /etc/udev/rules.d to see if there is anything there. udev rules should survive a dist-upgrade. If there is a udev rule to automount, copying it over to your new Beowulf computer should work. > > [snip] > >> The udisksd man page says the daemon is started by dbus-daemon or > >> systemd. However, it is not started by inserting a USB device. I > >> tried starting it manually (with USB device inserted) and received > >> this: > > > > It does. You shouldn't have to manually start it. To see if > > udisks2 is running and working, inset a usb thumb drive, and in a > > terminal enter "udisksctl status". The thumb drive should show in > > the list of other mounted devices. > > udisksctl does see the thumb drive. The udisksd daemon is running > but it doesn't mount the thumb drive anywhere I can find. It does > show up in /dev as sdb. Okay. Udisks2 is working correctly: it sees the drive; but udisks2 won't automount by itself without using a frontend utility or udev rule. Try mounting manually using the udisksctl "mount" command to see if it mounts. See the udisksctl man for the details of using the mount command. If that works install udiskie (or set up a udev rule), start it and see if works. PS: There are other frontends besides udiskie. I just used it because it was the simplest one at the time -- When I upgraded from Wheezy to Stretch. Kept same set up when I did a clean install of Beowulf a year ago. B ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] USB mount problem
On Sun, 13 Jun 2021 12:37:00 -0700 Fred wrote: > On 6/11/21 7:05 AM, Patrick Bartek via Dng wrote: > > On Thu, 10 Jun 2021 17:37:13 -0700 > > Fred wrote: > > > >> On 6/10/21 1:48 PM, Patrick Bartek via Dng wrote: > >>> On Thu, 10 Jun 2021 08:49:24 -0700 > >>> Fred wrote: > >>> > >>>> Hello, > >>>> > >>>> I have a new Beowulf AMD64 install and am having trouble mounting > >>>> USB storage devices. > >>>> > >>>> The USB keyboard and mouse work ok. lsusb shows the storage > >>>> device is present. The usbmount program is apparently no longer > >>>> available and I haven't been able to find what took its place. > >>>> I have another computer that had Debian Jessie installed then was > >>>> upgraded to Beowulf x86. It has usbmount and will automatically > >>>> mount USB storage devices. > >>>> > >>>> What do I need to install? > >>> > >>> I use udisks2 to automount external USB devices. > >>> > >>> B > >>> ___ > >>> Dng mailing list > >>> Dng@lists.dyne.org > >>> https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng > >>> > >> Hi, > >> I found udisks2 installed on the computer that automatically mounts > >> USB devices but there is no man page so I would not know how to use > >> it if installed on the other computer. > > > > Not much to using it: apt-get install udisks2 and everything gets > > set up. I used the defaults. Devices are mounted under /media/"your > > username". If you run a panel, the udisks2 gadget shows up there > > with additional options. Manual unmounting is necessary, but I use > > only a window manager (Openbox) and lxpanel for my GUI, so your > > mileage may vary if you use a desktop environment. > > > > Others have shown you how to access the mans. So, I won't repeat > > that. > > > > B > > ___ > > Dng mailing list > > Dng@lists.dyne.org > > https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng > > > Hello, > I still need some help with this. > I installed udisks2. The last line of the installation dialog showed > what I believe is a warning, maybe of no consequence: I did some checking -- It's been a while since I installed Beowulf and udisks2 -- and I discovered that you need to use a "front end" for udisks2 for it to truly automount. I used udiskie (https://pypi.org/project/udiskie/) which must be started manually. Installing it doesn't automatically set it up to start. I just added a stanza to Openbox's autostart script. Since I use lxpanel in addition to Openbox, I added the "--smart-tray" option, so udiskie will appear in the panel when it's in use. > W: > http://deb.debian.org/debian/pool/main/libb/libblockdev/libblockdev-crypto2_2.20-7+deb10u1_amd64.deb: > > Automatically disabled Acquire::http::Pipeline-Depth due to incorrect > response from server/proxy. (man 5 apt.conf) > > The udisksd man page says the daemon is started by dbus-daemon or > systemd. However, it is not started by inserting a USB device. I > tried starting it manually (with USB device inserted) and received > this: It does. You shouldn't have to manually start it. To see if udisks2 is running and working, inset a usb thumb drive, and in a terminal enter "udisksctl status". The thumb drive should show in the list of other mounted devices. > root@aragog:/home/fred# /usr/lib/udisks2/udisksd & > [1] 523 > root@aragog:/home/fred# udisks-Message: 07:27:15.642: udisks daemon > version 2.8.1 starting > > ** (udisksd:523): WARNING **: 07:27:15.773: failed to load module > mdraid: libbd_mdraid.so.2: cannot open shared object file: No such > file or directory > sh: 1: dmidecode: not found > > (udisksd:523): udisks-WARNING **: 07:27:15.776: Failed to load the > 'mdraid' libblockdev plugin > udisks-Message: 07:27:16.017: Acquired the name > org.freedesktop.UDisks2 on the system message bus > > If that library file was needed it should have been loaded by the > installer. I don't know what to do from here. Do you have a RAID set up? If not, disregard the warnings. > I use openbox and xterms if that info. is needed. Me, too, with a single lxpanel with menus. I do not have any desktop environments, in whole or part, installed. Neither a display manager. I boot to and login in a terminal and, then, run startx. B ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] USB mount problem
On Thu, 10 Jun 2021 17:37:13 -0700 Fred wrote: > On 6/10/21 1:48 PM, Patrick Bartek via Dng wrote: > > On Thu, 10 Jun 2021 08:49:24 -0700 > > Fred wrote: > > > >> Hello, > >> > >> I have a new Beowulf AMD64 install and am having trouble mounting > >> USB storage devices. > >> > >> The USB keyboard and mouse work ok. lsusb shows the storage device > >> is present. The usbmount program is apparently no longer available > >> and I haven't been able to find what took its place. I have > >> another computer that had Debian Jessie installed then was > >> upgraded to Beowulf x86. It has usbmount and will automatically > >> mount USB storage devices. > >> > >> What do I need to install? > > > > I use udisks2 to automount external USB devices. > > > > B > > ___ > > Dng mailing list > > Dng@lists.dyne.org > > https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng > > > Hi, > I found udisks2 installed on the computer that automatically mounts > USB devices but there is no man page so I would not know how to use > it if installed on the other computer. Not much to using it: apt-get install udisks2 and everything gets set up. I used the defaults. Devices are mounted under /media/"your username". If you run a panel, the udisks2 gadget shows up there with additional options. Manual unmounting is necessary, but I use only a window manager (Openbox) and lxpanel for my GUI, so your mileage may vary if you use a desktop environment. Others have shown you how to access the mans. So, I won't repeat that. B ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] USB mount problem
On Thu, 10 Jun 2021 08:49:24 -0700 Fred wrote: > Hello, > > I have a new Beowulf AMD64 install and am having trouble mounting USB > storage devices. > > The USB keyboard and mouse work ok. lsusb shows the storage device > is present. The usbmount program is apparently no longer available > and I haven't been able to find what took its place. I have another > computer that had Debian Jessie installed then was upgraded to > Beowulf x86. It has usbmount and will automatically mount USB > storage devices. > > What do I need to install? I use udisks2 to automount external USB devices. B ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Request for assistance with install
On Mon, 24 May 2021 20:46:06 -0500 o1bigtenor via Dng wrote: > On Mon, May 24, 2021 at 4:51 PM o1bigtenor > wrote: > > > > Greetings > > > > Tried a migration from Debian Buster to Beowulf - - - nope. > > Downloaded the DVD and got almost all the way through the install. > > Got stuck when the install demands a place to install grub and this > > is an EFI setup. > > > > Thought I'd check things. > You bet - - - - had it on legacy boot not efi boot. > Changed that and did another install. > At the boot after install - - - oops - - - no joy. > > Complaints of no run init: can't execute /sbin/init: no such file or > directory. > > Now this I have no ideas on how to fix - - - - please advise. > > (This is using the devuan dvd to install from. If this doesn't work > - - - - well - - - I'm now out of my depth!) For my clean install of Beowulf, I had to use Expert Mode to get the EFI boot choice. Having Legacy Mode on or off in BIOS made no difference. You also need a dedicated EFI partition (type ef00, EFI System type) formatted FAT32 mounted on /boot/efi which should show in the installer partitioner tool. You don't need a dedicated /boot partition. The boot folder under / is sufficient. Thoroughly study the install instructions, especially about setting up efi. B ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Beowulf installation skipped networking. Quickest fix? SOLVED
On Sat, 27 Mar 2021 17:28:37 +1030 dva...@internode.on.net wrote: > On 26.03.21 06:54, Patrick Bartek wrote: > > On Fri, 26 Mar 2021 15:49:13 +1030 > > dva...@internode.on.net wrote: > > > > > My shiny new Beowulf 3.0.0 install on an Intel NUC skipped > ethernet > > > stuff, perhaps because the ethernet cable wasn't inserted at the > time? > > > > > > Now, I can start hacking /etc/network/interfaces, /etc/hosts, > > > resolv.conf, > > > etc., but will that reveal so much missing that I'm better off > doing > > > another > > > install with the LAN plugged in? Heck, are there kernel modules > > > missing? > > > > Have your tried juat rebooting with the ethernet cable plugged > > in? > > I probably should have, but on finding no mention of eth0 in the /etc > files, I reinstalled Beowulf with the cable plugged in. It was so > quick > compared to the old days, that am dazed that it's all there. Then > networking just worked ... even though there was still no mention of > eth0. Some systems have weird designation for the ethernet port. Mine is enp1s0. > I hadn't been asked for an ethernet address or subnet mask - it was > all > magic. Linux has gotten smarter. It can now set all that up without user input. > I've only had Beowulf for a few hours, but it is immediately > comfortable. I'd been using Debian for years (since Sarge), but when they switched to systemd from sysvinit, I started looking for an alternative. Luckily, Devuan Beowulf came along and I abandoned Debian. Happy with it. All working well. And I have a customized system: no desktop, just a window manager, a single panel, etc. > Whoever thought of leaving the release notes on the desktop deserves a > medal. That was the first thing I was going to hunt for, as I'd read > the > note on pulseaudio prior to install. The problem line is commented > out, > but I still have no audio; will have to poke at that a bit. But first > to > move email to the new host, so I can get off this webmail horror. All I did to enable sound was to use alsamixer to turn on the master volume. Volumes for all sound channels is zero by default. B ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Beowulf installation skipped networking. Quickest fix?
On Fri, 26 Mar 2021 15:49:13 +1030 dva...@internode.on.net wrote: > My shiny new Beowulf 3.0.0 install on an Intel NUC skipped ethernet > stuff, perhaps because the ethernet cable wasn't inserted at the time? > > Now, I can start hacking /etc/network/interfaces, /etc/hosts, > resolv.conf, > etc., but will that reveal so much missing that I'm better off doing > another > install with the LAN plugged in? Heck, are there kernel modules > missing? Have your tried juat rebooting with the ethernet cable plugged in? B ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Beowulf installation skipped networking. Quickest fix?
On Fri, 26 Mar 2021 15:49:13 +1030 dva...@internode.on.net wrote: > My shiny new Beowulf 3.0.0 install on an Intel NUC skipped ethernet > stuff, perhaps because the ethernet cable wasn't inserted at the time? > > Now, I can start hacking /etc/network/interfaces, /etc/hosts, > resolv.conf, > etc., but will that reveal so much missing that I'm better off doing > another > install with the LAN plugged in? Heck, are there kernel modules > missing? First, try running the Network section of tasksel (as root) with the ethernet cable plugged in. B ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] How to firewall on Devuan?
On Wed, 24 Feb 2021 07:01:58 -0500 Steve Litt wrote: > Hi all, > > I'm now at the stage where I need a firewall on my Devuan VM guest, > and I don't know how to do it. I have the iptables package installed, > and /usr/sbin/iptables is a command, but I have no idea where to go > from there. Is there a file that iptables uses to define which ports > are blocked? > > I'm used to iptables being a daemon, and that seems not to be the case > in Devuan. I've been using ufw for years. It's a commandline front-end for iptables. There's also a GUI for it, too. Simple and easy to set up, configure, etc. B ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] X startup error
On Sat, 23 Jan 2021 09:53:15 -0700 Fred wrote: > Hello, > > I installed Beowulf amd64 netinst and then installed Xorg and openbox > with apt-get. Startx grinds for a while then exits with an error. > Here is the end of the Xorg.0.log file: I'm assuming you installed a basic terminal only system first, then installed xorg and openbox which is exactly how I installed my Beowulf set up. I experienced no problems. What packages EXACTLY did you install for the X environment? Were you root when you did the installs? B > [261220.123] (==) modeset(0): DPI set to (96, 96) > [261220.123] (II) Loading sub module "fb" > [261220.123] (II) LoadModule: "fb" > [261220.123] (II) Loading /usr/lib/xorg/modules/libfb.so > [261220.123] (II) Module fb: vendor="X.Org Foundation" > [261220.123] compiled for 1.20.4, module version = 1.0.0 > [261220.123] ABI class: X.Org ANSI C Emulation, version 0.4 > [261220.123] (II) UnloadModule: "fbdev" > [261220.123] (II) Unloading fbdev > [261220.123] (II) UnloadSubModule: "fbdevhw" > [261220.123] (II) Unloading fbdevhw > [261220.123] (II) UnloadModule: "vesa" > [261220.123] (II) Unloading vesa > [261220.123] (EE) modeset(0): drmSetMaster failed: Permission denied > [261220.123] (EE) > Fatal server error: > [261220.123] (EE) AddScreen/ScreenInit failed for driver 0 > [261220.123] (EE) > [261220.123] (EE) > Please consult the The X.Org Foundation support >at http://wiki.x.org > for help. > [261220.123] (EE) Please also check the log file at > "/home/fred/.local/share/xorg/Xorg.0.log" for additional information. > [261220.124] (EE) > [261220.135] (EE) Server terminated with error (1). Closing log file. > > I don't know what drmSetMaster is. Where should I look for the > problem? Best regards, > Fred ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Beowulf: 32bit or 64 bit?
On Wed, 25 Nov 2020 17:34:16 -0700 Fred wrote: > On 11/25/20 4:56 PM, Patrick Bartek via Dng wrote: > > On Wed, 25 Nov 2020 16:07:24 -0700 > > Fred wrote: > > > >> Hello, > >> > >> I recently upgraded from Debian Jessie to Devuan Beowulf. I tried > >> to run a program (ClipGrab-3.9.2-x86_64.AppImage) which would not > >> run. > >> > >> bash: ./ClipGrab-3.9.2-x86_64.AppImage: cannot execute binary file: > >> Exec format error > >> > >> I asked for help on the Debian user mail list (because of previous > >> discussion) and was told I am running a 32 bit version. > >> > >> uname -m > >> i686 > >> > >> lspci > >> Architecture:i686 > >> CPU op-mode(s): 32-bit, 64-bit > >> (the rest cut) > >> > >> So, is Beowulf 32 bit or 64 bit? > > > > It can be either or both, that is, Multi-Architecture. It depends > > on which version you chose to install. Evidently, you installed or > > upgraded to the 32-bit version. Perhaps, your Jessie install was > > 32-bit to begin with. > > > > B > > > > ___ > > Dng mailing list > > Dng@lists.dyne.org > > https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng > > > I think Debian Jessie is 32 bit. To upgrade to Beowulf I just > followed instructions that didn't say anything about 32 or 64. I > just assumed Beowulf was 64 bit. > > My CPU appears to be able to do 64 so how do I change over? The least problematical way is to back up your data, wipe the current install and do a clean install of Beowulf 64-bit and all your apps. However, I surmise, what you want is "the quick fix." Okay. Here's what I'd do, generally speaking -- after considerable research, but mind you, it's been about 10 years since I set up and ran a 32-bit, 64-bit multi-arch system: Back up your data!!! Add AMD64 multi-architecture to get the 64-bit libraries. This will also work with Intel CPUs. Install the 64-bit kernel, if it hasn't been installed. Check that during the kernel install, a new vmlinuz and initrd.img for it was created. Do an apt update. Reboot with the 64-bit kernel. It won't be the default. So, you'll have to choose it at the boot menu. Hopefully it will boot. (If not, troubleshoot.) If system boots, check you're running the 64-bit kernel. If so, do an apt update and upgrade. Install the necessary and wanted 64-bit kernel headers, utilities, apps, etc. When all is running well, make the 64-bit kernel your default boot kernel in grub. I'd leave all the 32-bit kernels, etc. alone. Don't try to purge them to get a 100% 64-bit system. May cause problems and as long as you're running 64-bit, all those files will just sit there and do nothing except take up space on the hard drive. This will get you started: https://wiki.debian.org/Multiarch/HOWTO https://wiki.debian.org/Multiarch/Implementation Good luck B ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Beowulf: 32bit or 64 bit?
On Wed, 25 Nov 2020 16:07:24 -0700 Fred wrote: > Hello, > > I recently upgraded from Debian Jessie to Devuan Beowulf. I tried to > run a program (ClipGrab-3.9.2-x86_64.AppImage) which would not run. > > bash: ./ClipGrab-3.9.2-x86_64.AppImage: cannot execute binary file: > Exec format error > > I asked for help on the Debian user mail list (because of previous > discussion) and was told I am running a 32 bit version. > > uname -m > i686 > > lspci > Architecture:i686 > CPU op-mode(s): 32-bit, 64-bit > (the rest cut) > > So, is Beowulf 32 bit or 64 bit? It can be either or both, that is, Multi-Architecture. It depends on which version you chose to install. Evidently, you installed or upgraded to the 32-bit version. Perhaps, your Jessie install was 32-bit to begin with. B ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Jessie to Ascii upgrade
On Sat, 21 Nov 2020 13:08:52 -0500 Steve Litt wrote: > On Fri, 20 Nov 2020 07:55:17 -0800 > Patrick Bartek via Dng wrote: > > > > I do run a little file manager -- xfe. Lightweight. Make things so > > much easier. I'd dread having to use the commandline instead. :) > > Comes with text editor, image viewer and package manager. > > > > B > > I just did some experiments with xfe, pcmanfm and thunar. Thunar is by > far the most reliable for dragging a file into an existing window and > having the file become open in that window. That's one of the few > things I use a file manager for. I tested those as well as several other file managers, too, before choosing xfe some 7 years ago to run on Debian Wheezy on then 7 year old hardware. I needed one that ran well on a lightweight, custom installed system without a desktop environment -- just X and a window manager. All the others seemed too heavy. Their performance was noticeably slower as well. Xfe just zipped along and even though it did have limitations as my needs were basic, I hardly noticed. When I switched to Devuan Beowulf and a new Ryzen system this year from Debian Stretch and that old system (now almost 14 years old*), I just stayed with xfe. B *That old system still runs just fine. Plan to turn it into a NAS running Beowulf terminal only system and OpenMediaVault. Waste not, want not! ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Jessie to Ascii upgrade
On Fri, 20 Nov 2020 15:10:24 + (GMT) Jim Jackson wrote: > > > Some question(s) on that. > > > It would seem that gnome is important to Beowulf - - -yes? > > > I have been running light weight desktops like LXMT (I think it > > > was) and now LXQT > > > after I found the KDE was just too weighty. > > > So I'll start with that one question - - - - does Beowulf mean > > > that I need to run Gnome? > > > > No. I'm running a custom installed Beowulf (started with a basic > > terminal system) with just a window manager (Openbox) and a single > > panel with menu (LXPanel). Works just fine. Lightweight, too. > > > > I'll second that - doing exactly the same - openbox and lxpanel, not > even a filemanager. I do run a little file manager -- xfe. Lightweight. Make things so much easier. I'd dread having to use the commandline instead. :) Comes with text editor, image viewer and package manager. B ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Jessie to Ascii upgrade
On Sat, 14 Nov 2020 14:36:36 -0700 Fred wrote: > Hello, > > I want to upgrade from Debian Jessie to Devuan. Apparently all I > need to do is change the sources list and do a dist-upgrade. > > > Is this likely to go smoothly? If there are any problems I would > probably not have Internet to ask for help. > > How does the upgrade get rid of systemd and everything associated > with it? Or how does one do that? First, before you do ANYTHING: download, read and study Devuan's upgrade from Debian to Devuan instructions. Personally, for safety, I'd do a dual boot: leave Jessie as is and do a clean install of Ascii (or Beowulf). That way, if something goes wrong, you still have a working system to fallback on. B ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Jessie to Ascii upgrade
On Sat, 14 Nov 2020 20:13:15 -0600 o1bigtenor via Dng wrote: > On Sat, Nov 14, 2020 at 7:29 PM Gastón via Dng > wrote: > > > > On Sat, Nov 14, 2020 at 02:36:36PM -0700, Fred wrote: > > > Hello, > > > > > > I want to upgrade from Debian Jessie to Devuan. Apparently all I > > > need to do is change the sources list and do a dist-upgrade. > > > > > > Is this likely to go smoothly? If there are any problems I would > > > probably not have Internet to ask for help. > > > > > > How does the upgrade get rid of systemd and everything associated > > > with it? Or how does one do that? > > > > Migrate from Debian Jessie to Beowulf guide: > > https://git.devuan.org/devuan/documentation/src/branch/master/dev1fanboy/en/jessie-to-beowulf.md > > > > > Some question(s) on that. > It would seem that gnome is important to Beowulf - - -yes? > I have been running light weight desktops like LXMT (I think it was) > and now LXQT > after I found the KDE was just too weighty. > So I'll start with that one question - - - - does Beowulf mean that I > need to run Gnome? No. I'm running a custom installed Beowulf (started with a basic terminal system) with just a window manager (Openbox) and a single panel with menu (LXPanel). Works just fine. Lightweight, too. B ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
