[Dng] Newbie questions re installing a devuan image
I'm running debian wheezy on a 32-bit machine. Given the appearance of Jessie last Saturday, it seemed time to try out devuan. Because I don't know what to do with the qcow2 files of the current builds, I went back to the Valentine ISO. I installed qemu-kvn and placed the qemu virtual disk into /usb/local/share/Devuan/. Installation of the image is where things go sour. I cd to this Devuan directory and do: $ qemu-system-x86 -enable-kvm -hda devuan_disk -boot c -net nic -net \ user,hostfwd=tcp::5556-:22 -m 1024 -vnc 127.0.0.1:0 -localtime & The command not known even though qemu-img is installed. I tried qemu-system-x86_64, but still not known. I tried as root but still no luck. The man qemu-img says nothing about this command and it does not seem to be on my system. Haines Brown ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [Dng] Announcing i386 netboot iso for Devuan (Alpha 2)
On Wed, Jun 03, 2015 at 01:12:01AM +1200, Daniel Reurich wrote: > You can find it at: > > http://packages.devuan.org/alpha-iso-cd/devuan-jessie-netboot-i386-alpha2.iso Great! I installed successfully to some degree. > Known issues: > * if 'standard utilities' are left selected in task-select the > installation step fails (dependency conflict between nfs-common and > libdevmapper) In Software Selection, there is a heading Debian Desktop Environment followed by specific environments. I wanted no desktop environment (I rely on just the fluxbox window manager) and so did not select the Debian Desktop Environment and installed xorg and fluxbox after booting the virtual machine. Should that first line in Software Selection have been named "X windows system" instead of "desktop environment"? ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] OFFLIST (from debian-user): No-systemd Debian
This thread has been quiet for a while, and so I thought I could hijack it. Problem is that I'm replacing an old Thinkpad with a new one. To gain driver support for its newer hardware features I'm more or less forced to install Sid. On the other hand, I want to avoid systemd and udev. While I don't mind apps relying on a simulated systemd, I don't use a desktop environment or a network manager. Any way in coming year to have my cake and eat it too with a devuan-experimental? ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Proposed defaults changes
On Tue, Jul 14, 2015 at 10:53:50PM -0700, Isaac Dunham wrote: > On Wed, Jul 15, 2015 at 02:59:51AM +0200, Franco Lanza wrote: > May I suggest that at this point, changes of this significance should be > planned for the next cycle rather than thrown in at the last moment? Yes, that makes sense. What is the "next cycle"? Alpha 1? On the other hand, it seems that abandonment of systemd and udev is itself very ambitious and the bugs fully worked out before tossing in an array of secondary changes. I suppose the core target is debianites who might want to migrate to devuan with the least change in their usual habits. > > nano -> vim As a nano and emacs user, the notion of having to use vim as well as emacs seems likely to confuse. Although space less of a concern these days, nano was always nice when you need to fit an editor into a small device. Other than the mentioned limitation, why switch? > > exim -> postfix Same question here: are there significant reasons to change? Why was the idea of dumping udev in favor of vdev etc. not mentioned? That strikes me as a more fundamental issue and should be tried out in next cycle. As for desktop environment, I assume the option of having none will remain. With all this talk of xfce, I hope those who use none will be accommodated. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[DNG] alpha 2 ISO missing parameter
I downloaded Alpha 2 and placed it on a USB key with unetbootin. When I boot a Thinkpad x250 with Alpha 2 iso, it comes up with "Missing parameter error". However, when I provide Install at the "Boot:" prompt, it boots to the installer. However, on a i386 desktop machine for which I would really like to install devuan, booting the key comes up with "Missing parameter in configuration file: Keyword: path". In this case, there is no Boot: prompt. I don't understand these messages or if they are compatible. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] alpha 2 ISO missing parameter
On Thu, Aug 13, 2015 at 09:37:57AM +1200, Daniel Reurich wrote: > Hi Haines, > > On 13/08/15 01:22, Haines Brown wrote: > >I downloaded Alpha 2 and placed it on a USB key with unetbootin. > > > Why didn't you just use dd (or even cat) to just dump the iso onto > the usbstick. Lazy? I guess I was in habit of using inetbootin. But you are right, dd method produced a usable installation menu. Thanks. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[DNG] Alpha2 without desktop environment Reply-To:
www.historicalMaterialism.info I installed Alpha 2 jessie in expert mode so that I could avoid installing a desktop environment. In package selection, I deselect a desktop environment. When installation finished I install fluxbox and use # update-alternatives --config x-window-manager to select fluxbox manual. Nevertheless, in spite of that when I reboot I'm taken to a graphical log in screen and then to some kind of desktop environment. Xfce4 is not installed. What is this environment (it has a chartreuse background), and how do I get rid of it? How do I get rid of the gui login (xdm, gdm, kdm etc not installed) so that I can run the machine from console without X system? ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Alpha2 without desktop environment
On Thu, Aug 13, 2015 at 01:57:58PM -0400, Steve Litt wrote: > On Thu, 13 Aug 2015 13:01:14 -0400 > Haines Brown , "To:dng"@lists.dyne.org, > "Cc:Bcc:"@tupac2.dyne.org wrote: > > > > What is this environment (it has a chartreuse background), and how do > > I get rid of it? How do I get rid of the gui login (xdm, gdm, kdm etc > > not installed) so that I can run the machine from console without X > > system? > > Hi Haines, > > You can find out what Display Manager you're running by doing this: > > ps axjf | less I tries this and was unsure how to identify a display manager. I found xdg/xfce4/xinitrc xfce4-power-manager xfce4-session xfce4-panel thunar Aptitude tells me that xfce4 and these specific utilities are not installed. I do # ps -axjf | grep power-manager, and it seems to say that it is running: 1 2905 2905 2905 ? -l Ssl 1000 0:00 xfce4-power-manager I do # dpkg -l | grep power-manager, and it is not present. Likewise for xfce4. # aptitude update did not change anything. However, # which xfce4-power-manager tells me it is in /usr/bin. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Alpha2 without desktop environment
On Thu, Aug 13, 2015 at 09:28:04PM +0200, Riccardo Boninsegna wrote: > Il 13/ago/2015 09:16 PM, "Haines Brown" ha scritto: > > However, # which xfce4-power-manager tells me it is in /usr/bin. > > The next step would be ‘dpkg -S /usr/bin/xfce4-power-manager’ to check if it > belongs to some weird package... # which xfce4-power-manager /usr/bin/xfce4-power-manager # dpkg -S /usr/bin/xfce4-power-manager dpkg-querry: no path found matching patter /usr/bin/xcfe4-power-manager # ls /usr/bin | grep xfce4-power-manager xfce4-power-manager xfce4-power-manager-settings # echo $PATH /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] which alpha2?
On Thu, Aug 13, 2015 at 03:36:26PM -0400, Hendrik Boom wrote: > (1) I plan to dd an iso to a usb stick and boot from there. > Does the iso need to be modified in some way to boot from a USB stick? > The valentine alpha did. I just dd's that alpha2 to stick and it worked. I also was worried whether the iso is hybrid. Apparently it is. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[DNG] [rboninsegna2+dev...@gmail.com: Re: Alpha2 without desktop environment]
- Forwarded message from Riccardo Boninsegna - Date: Thu, 13 Aug 2015 22:02:13 +0200 From: Riccardo Boninsegna To: Haines Brown Cc: Dng@lists.dyne.org Subject: Re: [DNG] Alpha2 without desktop environment Il 13/ago/2015 09:48 PM, "Haines Brown" ha scritto: > # which xfce4-power-manager > /usr/bin/xfce4-power-manager > > # dpkg -S /usr/bin/xfce4-power-manager > dpkg-querry: no path found matching patter /usr/bin/xcfe4-power-manager So it's not in a package... Unless you installed over an existing root (without reformatting), deliberately installed Xfce without using a package, or one of dpkg's database files is corrupted in a very weird way, I honestly don't have an idea of this happened... I guess I'll just try to reinstall. I initially tried to install testing/ascii, but couldn't complete install software. So I retreated to jessie, and had the same problem, but after choosing not to install CUPS (and no desktop manager), I finally succeeded but for the problem under discussion. When I redo, I'll repartition and not use the default partitioning scheme. I'll report on my success. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] which alpha2?
On Thu, Aug 13, 2015 at 04:17:55PM -0400, Hendrik Boom wrote: > On Thu, Aug 13, 2015 at 03:54:24PM -0400, Haines Brown wrote: > > On Thu, Aug 13, 2015 at 03:36:26PM -0400, Hendrik Boom wrote: > > > > > (1) I plan to dd an iso to a usb stick and boot from there. > > > Does the iso need to be modified in some way to boot from a USB stick? > > > The valentine alpha did. > > > > I just dd's that alpha2 to stick and it worked. I also was worried > > whether the iso is hybrid. Apparently it is. > > Good. Which one did you use? devuan-jessie-netboot-i386-alpha2.iso from http://files.devuan.org/ ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Alpha2 without desktop environment
On Thu, Aug 13, 2015 at 05:13:46PM -0400, Steve Litt wrote: > On Thu, 13 Aug 2015 15:16:21 -0400 > Haines Brown wrote: > > > On Thu, Aug 13, 2015 at 01:57:58PM -0400, Steve Litt wrote: > > > On Thu, 13 Aug 2015 13:01:14 -0400 > > > Haines Brown , "To:dng"@lists.dyne.org, > > > "Cc:Bcc:"@tupac2.dyne.org wrote: > > Aptitude tells me that xfce4 and these specific utilities are not > > installed. > > I suspect that aptitude is wrong, or you are interpreting it wrong. But > anyway... No I'm interpreting it correctly. The mystery won't be solved because I reinstalled. > Rereading your original post: Do you want to not have a Display Manager > such as lightdm, kdm, gdm etc, or do you want your computer not to have > X at all? If the latter, just deinstall X. If the former, you need to > find your display manager, based on ps axjf. The aim is to boot to a console prompt, log in as root, install xorg and fluxbox. That gives me X and a window manager but no desktop environment. At present I get a log in prompt and can log in as user in console, but for some reason root log in not working. I suppose that when I provided a password I mistyped. > Anyway, luckily for you, you're on Devuan with sysvinit, so I'm pretty > sure almost any way that you could disable plymouth and lightdm would > bring you to CLI, from which you could run startx which would work with > a properly configured ~/.xinitrc. You describe a complicated scenario. I've never had to go through all that because I've always simply done expert install, avoided installing a desktop environment, and then in console install xorg and fluxbox. Over the years never had a problem. Thanks, Haines ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Alpha2 without desktop environment
On Thu, Aug 13, 2015 at 11:54:48PM +0200, Riccardo Boninsegna wrote: > Il 13/ago/2015 10:21 PM, "Haines Brown" ha scritto: > > I guess I'll just try to reinstall. I initially tried to install > > testing/ascii, but couldn't complete install software. So I retreated to > > jessie, and had the same problem, but after choosing not to install CUPS > > (and no desktop manager), I finally succeeded but for the problem under > > discussion. When I redo, I'll repartition and not use the default > > partitioning scheme. I'll report on my success. > > Now I understand: you went through "Install the base system" (if not more, > most > likely given the issue is with Xfce), then went back to "choose a mirror" to > switch releases, then back again to base system/package manager/install > software without going back to partitioning to reformat root? > > That's where it went wrong, then: "install the base system" blindly overwrites > dpkg's status file with one matching the debootstrap that happens for the most > of that step (before it says to select a kernel package)! > > There is a warning if you "install the base system" on a non-empty partition > but it's easy to miss if you went through partitioning again without > reformatting, as it immediately follows "warnings" such as saving the > partition > table and complaining about not using a swap partition! Yes, you spotted the problem. Perhaps only when I did chroot (cross) installations, but it seems I used to partition and format a hard disk before installing, and then skip the partitioning step in the installation. But Devuan installation routine insisted that I partition the drive because it seems to have removed mount points and filesystem. I defined them and wrote to disk but I suspect without re-formatting. That was my mistake. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[DNG] [hai...@histomat.net: Re: Alpha2 without desktop environment]
I reiinstalled (avoiding past missteps), to a console, and from it installed xorg and fluxbox. I then ran xstart from console and all went well. With one exception. I'm in what looks like VGA mode with large crude characters. It seems a problem (or symptom) is that installation did not create a /etc/X11/xorg.conf.d/ directory that should holding, I presume, a 20-nvidia.conf file. I created them by hand, but startx failed with error in log to effect that there is no server section. I suspect this is not the file that should have a Server section. I purged and reinstalled xorg without luck. Installed were libglu1-mesa, x11-apps, x11-session-utils, x11-server-utils, xinit, xorg, xorg-docs-core. The xorg log tells me that it is using as system configuration directory, /usr/share/X11/xorg.c. Because this file does not exist, the log complains about missing layout, screen and monitor definitions. It seems xorg is using defaults. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] [hai...@histomat.net: Re: Alpha2 without desktop environment]
On Sat, Aug 15, 2015 at 12:04:32PM -0400, Steve Litt wrote: > On Sat, 15 Aug 2015 07:43:04 -0400 > Haines Brown wrote: > > > > I purged and reinstalled xorg without luck. Installed were > > libglu1-mesa, x11-apps, x11-session-utils, x11-server-utils, xinit, > > xorg, xorg-docs-core. > > > > The xorg log tells me that it is using as system configuration > > directory, /usr/share/X11/xorg.c. > > What happens when you try it after manually creating the directory? Let me start by noting that I'm unclear about the device configuration file. On another disk on the same machine that I'm running devuan, there is a Wheezy installation that has no no /etc/X11/xorg.conf.d/ directory, and off hand the configuration files in /usr/share/X11/xorg.conf.d/ don't have a Device section. I also run Wheezy on another machine, and it has a 20-nvidia.conf file with a Device section. I don't recall that I did anything different for the installations, but nevertheless one uses the nouveau module and the other must somehow use a default Section definition. I did as you suggest, creating a /etc/X11/xorg.conf.d directory and putting into it a 20-nouveau.conf file with: Section "Device" Identifier "MSI NX 8500GT" Driver "nouveau" EndSection For the Identifier I just put my card name as a guess. The Xorg log shows that the nouveau driver loads and so I guess the Identifier works, but not sure. When I startx, I'm still in vesa (?) mode. The Xorg log file says it is using configuration directory /etc/X11/xorg.conf.d/ directory. The only error is: (EE) NOUVEAU(0): [COPY] failed to allocate class don't know what this means, and the Xorg wiki site no help. I did a # Xorg -configure to create a /root/xorg.conf.new. It has Section "Device" Identifier "Card(0)" Driver "nouveau" EndSection When I do # X -config /root/xconf.new, I'm taken to a blank screen and I'm hung there and so have to delete the xorg.conf.new file and do a hot reboot. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[DNG] [arthur.ma...@internode.on.net: Re: Interesting comment from a kernel developer]
- Forwarded message from Arthur Marsh - Date: Mon, 17 Aug 2015 23:35:15 +0930 From: Arthur Marsh To: dng@lists.dyne.org Subject: Re: [DNG] Interesting comment from a kernel developer User-Agent: Mozilla/5.0 (X11; Linux i686; rv:31.0) Gecko/20100101 Icedove/31.7.0 Adam Borowski wrote on 23/07/15 07:45: > On Wed, Jul 22, 2015 at 03:03:55PM -0500, T.J. Duchene wrote: >> Yes, Debian has adopted systemd. As a quick fix, you can stick with >> Wheezy; or you can install Jessie and then install systemd-shim and >> sysvinit. After you install systemd-shim and sysvinit, Jessie should work >> more or less as expected. Just a side note. I installed Sid on a x250 Thinkpad and then replaced systemd with sysVinit. Things seem to be working just fine, although admittedly I didn't install any desktop environment. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] [arthur.ma...@internode.on.net: Re: Interesting comment from a kernel developer]
On Mon, Aug 17, 2015 at 04:22:26PM +0100, Simon Hobson wrote: > Haines Brown wrote: > > > Just a side note. I installed Sid on a x250 Thinkpad and then replaced > > systemd with sysVinit. Things seem to be working just fine, although > > admittedly I didn't install any desktop environment. > > Did you also try removing the rest of SystemD ? No. I installed sysvinit-core sysvinit sysvinit-utils, rebooted, and then did: # apt-get remove --purge --auto-remove systemd # echo -e '\n\nPackage: *systemd*\nPin: origin ""\nPin-Priority: \ -1' >> /etc/apt/preferences.d/systemd ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Alpha2 without desktop environment]
On Sat, Aug 15, 2015 at 02:50:03PM -0700, Isaac Dunham wrote: > On Sat, Aug 15, 2015 at 07:43:04AM -0400, Haines Brown wrote: > > I reiinstalled (avoiding past missteps), to a console, and from it > > installed xorg and fluxbox. I then ran xstart from console and all went > > well. > > > > With one exception. I'm in what looks like VGA mode with large crude > > characters. It seems a problem (or symptom) is that installation did not > > create a /etc/X11/xorg.conf.d/ directory > Xorg looks in /etc/X11/xorg.conf.d/, then /usr/share/X11/xorg.conf.d/. > If you would rather use a single-file xorg.conf, you can create it via > "Xorg -configure" (IIRC). Thanks, Isaac. That I tried again on my test machine. It creates /root/xorg.conf.new, which I presume is a configuration to test. This file has an array of sections, but I have the feeling that most configuration sections are found in various files in /usr/share/X11/xorg.conf.d/ and that the file with just a Devices section is normally /etc/X11/xorg.conf.d/xorg.conf. Or at least that is what my current machine running Wheezy has except the config file is 20-nvidia.conf. The Devices section in /root/xorg.conf.new built by # Xorg -configure is" Section "Device" Identifier "Card0" Driver "nouveau" BusID "PCI:1:0:0" EndSection I copy this section into a file and directory I create /etc/X11/xorg.conf.d/xorg.conf. Apparently using Card0 as identifier rather than provide the name of the card is OK, for there's only one video card in the machine. The nouveau was the only driver that seemed appropriate for the old MSI card I'm using on the test machine. The file name I used is xorg.conf because the test configuration file was named xorg.conf.new. When I startx, I'm still in vesa mode. I tried to comment the BusID line. I tried changing the name of the config file to 20-nouveau.conf. I tried to copy /etc/X11/xorg.conf/xorg.conf to /usr/share/X11/xorg.conf.d/20-xorg.conf. I tried Identifier "MSI NX 8500GT". In all cases, startx still comes up in VESA mode, and there are no (EE) or significant (WW) in the Xorg log file. When I do # Xorg -config /etc/X11/xorg.conf.d/20-nouveau.conf I get a black screen and have to do a hard reboot. > But besides that, I'm wondering about a couple things. > 1: You refer to "20-nvidia.conf". I'd assume that this would come from > the nvidia driver, which I see no reference to in your list of packages. Correct. I changed that to nouveau fairly early on when I realized that the MSI card on my test machine is not supported by nvidia driver. > 2: You refer to "/usr/share/X11/xorg.c." Is this a typo/abbreviation, > or is Xorg misconfigured? No, when I originally installed, this file showed up as the sole config file. I didn't think to inspect its contents before deleting it once I knew it was not the configuration file I needed. Haines ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[DNG] replacing kernel 3.16.0-4
I've already tried your patience with a query about why xrandr tells me my display uses VGA 1024x768 when it shows my video card supports DVI 1920x1080. I hope you will bear with me if I pursue the matter. I am told that because selection of optimal resolution is today done by the kernel, my 3.16.0-4 kernel therefore has a bug. I find significant that kernel.org skips this kernel for possible downloading. Is anyone else experiencing this problem? I'm loading fluxbox on devuan-jessie without a desktop environment. When I edit the linux line in the GRUB menu by appending video=VGA-1:d, the display comes up with the proper DVI 1920x1080 resolution. Does this not show that the kernel is sick? So I'd like to use a different kernel, but there are no alternatives in the devuan repository. How then should I install an alternative kernel? Some time ago I tried to install devuan testing and it failed right away for reasons I forget. Is the testing installation option actually working? Haines Brown ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Office pack
On Mon, Nov 02, 2015 at 05:16:20PM +0100, Stefan Mark wrote: > On 02.11.2015 16:50, Mitt Green wrote: > > Hi, > > > > I'm in search for an office pack. Considering Gnumeric as a decent > > spreadsheet > > application (even better than LibreOffice's one?), I can't be sure about > > word > > processor, speaking of numerous AbiWord issues. > > > > LibreOffice has too many dependencies, as well as AbiWord, while I'd like > > to remain minimalistic. I'm undoubtedly biased, but I have come to find plain LaTeX easier than a word processor. My wife, a computer newbie, has a Mac laptop that came with a word processor (Page, I think), and she was struggling with it. I set her up with LaTeX, and life became easier for her, using a simple template. Some people (but not I) might recommend LyX as a compromise. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Please Adopt Bastille Linux Security Script for Devuan. Please.
On Sun, Jan 03, 2016 at 05:25:39PM +, Go Linux wrote: > Great way to start the new year. Looks like Gregory Smith might be back. > Ugh . . . Your frustration may be justified, but you are doing less sophisticated readers like myself a disservice. I've not thought about bastille for many years, and this thread encouraged me to see what became of it. My impression, right or wrong, is that bastille has been superseded by the harden-tools package. Does harden-tools incorporate or improve on bastille? Is the question then whether bastille needs to be placed in the Devuan archive or that hardenk-tools should be installed automatically? Haines Brown ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Devuan Weekly News LX
On Mon, Jan 04, 2016 at 02:43:57PM +0100, Didier Kryn wrote: > ... > We are discovering day after day that "init freedom" is about > the emerged part of the iceberg. Debian still pretends to offer init > freedom. What is under the sea level is a whole monolithic operating > system absorbing all critical Linux subsystems like a black hole. > Therefore escaping this monster means much more than init freedom, > it is something like keeping a free Linux/Gnu OS. Didier, as a lurker, can I ask what elements besides systemd and udev do you think define this black hole? Is there a consensus over this? Haines Brown ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[DNG] systemd is haunting me
I have been running Debian Sid on a laptop with a purged systemd for quite a few months. Maybe when I now ran # aptitude update or safe-upgrade for the first time after several months since the Sid installation systemd-udevd seems to have switched my wireless interface from wlan0 to wlp3s0. Changing the entry in /etc/network/interfaces fixed that problem. So now I could do a wireless aptitude update and safe-upgrade. Even though in /etc/apt/preferences.d/systemd I have: Package: "systemd" Pin: origin "" Pin-Priority: -1 Systemd was re-installed. Why didn't this systemd file prevent it? Then I found that while root can run starx with no problem, when user does it the desktop comes up frozen along with mouse and keyboard input. I found this: $ cat /var/log/Xorg.0.log | grep EE (EE) systemd-logind: failed to gete session: The name \ org.freedesktop.login1 was not provided by any .service \ files. Systemd is not on the system, so where did systemd-logind come from? How can I block it and recover a usable virtual desktop for user? Haines Brown ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] systemd is haunting me
I was asked why I do not run Devuan rather than Sid on the laptop. When I installed Sid, Devuan was not even in Alpha. I am not anxious to reinstall Sid, but but when Devuan beta comes out I'll install it. Mitt Green pointed out that the /etc/apt/preferences.d/systemd script I've been using is incorrect. Perhaps this is why I acquired systemd-udevd and sysdend-logind even without systemd. I suspect I could remove the /lib/systemd/ directory entirely, and it might block any systemd-udev from changing network interface name, and systemd=logind from freezing user's frozen desktop. So let me ask: if I delete the directory and its contents, will I still have a functioning Sid system? ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] systemd is haunting me
On Sun, Jan 31, 2016 at 08:04:26AM -0500, Haines Brown wrote: > I suspect I could remove the /lib/systemd/ directory entirely, and it > might block any systemd-udev from changing network interface name, and > systemd=logind from freezing user's frozen desktop. > > So let me ask: if I delete the directory and its contents, will I still > have a functioning Sid system? Not having received an answer, I went ahead and did it. It had several effects: a) the reported bug that had made it difficult to shutdown the X server disappeared, b) the boot no longer goes over the a higher resolution but remains VGA, c) trying to startx as user now produces error that screen can't be found, d) now the freeze of the desktop affects root as well. I have a choice: re-install Sid from scratch or install devuan. I'd much rather do the latter, but I'd prefer to wait for the beta. So let me ask the question that can't be answered: when is the beta likely to surface? Within a month or so or not likely until well after mid year? ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] systemd is haunting me
On Wed, Feb 03, 2016 at 03:05:52PM +, Rainer Weikusat wrote: > Haines Brown writes: > > On Sun, Jan 31, 2016 at 08:04:26AM -0500, Haines Brown wrote: > > Not having received an answer, > > I answered both of your questions. My apologies. Your message for some reason did not show up, but I managed to find get it. Your helpful reply has convinced me to replace my Debian Sid with Devuan alpha2. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Speaking of Window Managers
On Sun, Feb 28, 2016 at 12:20:50PM +, Dave Turner wrote: > I hate hotkeys in GUIs and never use them. At all. Ever. Give me a > menu and a mouse. I can understand that, but there seems no reason not to provide both hot keys and menus. My sense is that switching between mouse and keyboard is inefficient, and that is why people prefer one or the other. For example, folks that are used to typing text may naturally use hot keys, while those who usually let applications do work prefer the mouse. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[DNG] problem installing JRE
I'm running devuan alpha4 on a Thinkpad x250, and so far everything has worked well. But now a problem. I need to convert PDFs to Word, and the obvious utility is (proprietary) easyConverter. Problem is that I can't install default-jre because the tzdata-java package on which it depends can't be found. This is a known bug. Is there a work-around or will that bug soon be resolved? I need to go from LaTeX to Word. I find that lwarp does an excellent job converting TeX to HTML, but HTML format does not convert well to Word. This is why I need to convert PDF directly to Word. Haines Brown ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] problem installing JRE
On Mon, Apr 18, 2016 at 11:49:39AM +0200, Florian Zieboll wrote: > On Sun, 17 Apr 2016 21:30:53 -0400 > Haines Brown wrote: > > > I'm running devuan alpha4 > > I assume that there is no other alpha4 than the current Jessie... > > > Problem is that I can't install > > default-jre because the tzdata-java package on which it depends can't > > be found. > > I have the default-jre (and tzdata-java) installed on two Devuan Jessie > systems and I am not aware of any bugs. Also, a > > $ apt-get install --reinstall tzdata-java > > with the .deb removed from /var/cache/apt/archives, returns without > errors. > > > This is a known bug. > > Couldn't find a bug report. Can you provide a link? > > > Is there a work-around > > Without being able to reproduce your problem, I would suggest to > download the tzdata-java package from > https://packages.debian.org/jessie/tzdata-java and manually install it > with dpkg. > > Florian Florian, found my problem. I had not updated debian alpha4 since installing it, and when I do so now, I discover the original apt sources.list used for installation is no longer correct. I had: deb http://us.mirror.devuan.org/merged jessie main When I replaced it with deb http://packages.devuan.org/merged jessie main things went much better. JRE now installs. Haines ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] What do we want for ascii ?
On Mon, Apr 18, 2016 at 09:46:36PM +, Noel Torres wrote: > Go Linux escribió: > > > >This is putting the cart before the horse IMO. It would be nice > >to get the beta out the door before focusing on ascii. Any > >chance some of that energy could be directed towards the beta > >release? > > > My energy is mostly useless for Jessie beta, as it is now. The best > I can do at this stage is report bugs (and we don't have a bug > tracker) and think about things when I have a little time. And this > is what I'm doing :D I have not followed things very closely. Is the implication that "beta" is now being named testing/Ascii? I'm still running debian Wheezie on my main system and devuan Jessie on a secondary system. While I could install Jessie on the main system and remove systemd, there's so many other problems with Jessie that I hesitate to do so and await Devuan beta/Ascii. But this has been a long wait. Is there any sense of when beta/testing/Ascii will be ready? This year? In six months? Haines Brown ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[DNG] debootstrap requires key
This has come up before, but I still don't know the basic procedure. I've installed debootstrap on a new disk and run: # debootstrap --arch amd64 jessie /mnt/debinst \ https://packages.devuan.org/devuan I: Retrieving Release I: Retrieving Release.gpg I: Checking Release signature E: Release signed by unknown key (key id 94532124541922FB) No change when I downloaded and ran # dpkg -i devuan-keyring_2015.05.05_all.deb Do I have the right keyring? Was the alpha4 release date c. 2015.05.05? In simple step by step terms, what do I do? ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[DNG] devuan-jessie-i386-alpha4-netboot.iso has AMD64 files?
I downloaded devuan-jessie-i386-alpha4-netboot.iso and installed it on a key with unetbootin. However, it would not boot, and when I looked more closely at it I find that its /boot directory has the initrd0.amd vmlinuz0.amd. Was the reason for my key not booting that it is for an AMD64 system? Is not devuan-jessie-i386-alpha4-netboot.iso for a 32 bit system? Haines Brown ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] debootstrap requires key
On Sat, Apr 23, 2016 at 05:46:10PM +0100, dev1fanboy wrote: > If I remember right... You can parse the option --no-check-gpg to > debootstrap, and you might need to use > --exclude=devuan-keyring,gpgv,gnupg as well and just install > devuan-keyring after the debootstrap to make sure you are using the > gpg key for the install. > > Cheers, > > chillfan > > On Saturday, April 23, 2016 1:13 PM, Haines Brown > wrote: > > This has come up before, but I still don't know the basic > > procedure. I've installed debootstrap on a new disk and run: > > > > # debootstrap --arch amd64 jessie /mnt/debinst \ > > https://packages.devuan.org/devuan Besides correcting my typo (removing --arch amd option), and adding the --no-check-gpg option, debootstrap ran better. That is, a bunch of files were validated and extracted. But at the end this appeared: W: /lib/i386-linux-gnu/i686/cmov/libc.so.6: version 'GLIB_2.17' not found (required by /lib-i3896-linux-gnu/libmount.so.1) And when I try # chroot /mnt/debinst /bin/bash: /lib/i386-linux-gnu/i686/cmov/libc.so.6: version `GLIBC_2.15' not found (required by /bin/bash) I gather glibc is provided by libc. This looks like some kind of version incompatibility. Hoever, While in target drive archive is libc6_2.19-18+deb8u4_i386.deb, there's no libc* in target /lib. So rather than version problem, it may be that libc was not installed for some reason. If I simply do # dpkg -i libc_6.19-18+deb8u4_i386.deb will it install on the target drive rather than messing up my current Wheezy library? Haines Brown ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] devuan-jessie-i386-alpha4-netboot.iso has AMD64 files?
On Sun, Apr 24, 2016 at 05:53:38AM +0200, aitor_czr wrote: > > On 04/24/2016 12:57 AM, Haines Brown wrote: > > I downloaded devuan-jessie-i386-alpha4-netboot.iso and installed it on a > key with unetbootin. However, it would not boot, and when I looked more > closely at it I find that its /boot directory has the initrd0.amd > vmlinuz0.amd. > > Was the reason for my key not booting that it is for an AMD64 system? > Is not devuan-jessie-i386-alpha4-netboot.iso for a 32 bit system? > > Haines Brown > > > Unetbootin generates a file named syslinux.cfg in the parent directory of the > USB stick. You can modify it because the stick is not protected, unlike using > dd. Here you are an example: > > default menu.c32 > prompt 0 > menu title [...] > timeout 100 > > label ubnentry0 > menu label ^[...] > kernel /live/vmlinuz > append initrd=/live/initrd.img boot=live config locales=en_US.UTF-8 keyb=es > quiet splash > > label ubnentry1 > [... etc ...] > > Use the content of isolinux/menu.cfg for that. Aitor, I had a little trouble following your suggestion. I assume the second and third stanza in the example is what appears in menu.cfg and so does affect what gets booted. Syslinux automatically boots the /linux file although bootloaders usually load a vmlinuz file, which in the present case is boot/vmlinuz0.amd. That's a strange name for a vmlinuz file in a i386 system. If it is loaded and is an AMD64 file, it is not surprising the bootloader fails to work. Or rather, because the linux file is booted, are the vmlinuz0.amd and initrd0.amd files simply ignored? I understand the two label stanzas above are in menu.cfg. The example of the syslinux.cfg you describe is essentially what I already have. Your example: default menu.c32 prompt 0 menu title [...] timeout 100 What I have: path include menu.cfg default /menu.c32 prompt 0 timeout 0 I could change prompt to 1 and timeout to 5, bring my system down, and at the boot: prompt try: boot: /linux or boot: vmlinuz0.amd. Haines Brown ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] debootstrap requires key
On Sun, Apr 24, 2016 at 03:41:51PM +0100, dev1fanboy wrote: > When you say installed debootstrap on a new disk, you mean the host > OS? What architecture is the host and the 'target' disk, are they > different? Sorry I was not clearer. I meant debootstrap installed a base system on a new disk. # debootstrap --no-check-gpg jessie /mnt/debinst \ https://packages.devuan.org/devuan The host, my currently running machine, runs debootstrap, targetting a new partitioned disk mounted on /mnt/debinst. I'm assuming debootstrap can be run anywhere, and it installs a base system wherever it is told to do it. Years ago I did cross installations, but the process has gotten a lot more complicated. Haines Brown ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] debootstrap requires key
On Sun, Apr 24, 2016 at 09:37:24PM +0200, parazyd wrote: > Yes, debootstrap works on any system. Note that if you wish to bootstrap > devuan systems, use devuan's debootstrap (which was fixed): > https://packages.devuan.org/devuan/pool/main/d/debootstrap/ Yes, I unarchived debootstrap_1.0.75-1+devuan1.debian.tar.gz in the target disk (/mnt/debinst/usr/share) and ran: # debootstrap --no-check-gpg jessie /mnt/debinst \ http://packages.devuan.org/merged It installed a base system on the target disk mounted on /mnt/debinst. But that base system is apparently broken because of a version inconsistency: W: /lib/i386-linux-gnu/i686/cmov/libc.so.6: version 'GLIB_2.17' not found (required by /lib-i386-linux-gnu/libmount.so.1) If you are implying the version clash is because I used the debian rather than the devuan debootstrap, that is not the case. I need to correct this problem in order to chroot into the new system to configure and develop it. > Also, for next steps, I'd recommend you to see how the ARM SDK works, > particularly the devuan profile: > https://git.devuan.org/devuan/arm-sdk/blob/master/arm/profiles/common-devuan This is a program you wrote. Much appreciated, but I have no idea what it is for or how to use it. Haines Brown ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] debootstrap requires key
On Mon, Apr 25, 2016 at 12:55:45PM +0200, parazyd wrote: > On Mon, 25 Apr 2016, Haines Brown wrote: > > > It installed a base system on the target disk mounted on > > /mnt/debinst. But that base system is apparently broken because of a > > version inconsistency: > > > > W: /lib/i386-linux-gnu/i686/cmov/libc.so.6: version 'GLIB_2.17' not > > found (required by /lib-i386-linux-gnu/libmount.so.1) > > > > If you are implying the version clash is because I used the debian > > rather than the devuan debootstrap, that is not the case. I need to > > correct this problem in order to chroot into the new system to configure > > and develop it. > > > > > Also, for next steps, I'd recommend you to see how the ARM SDK works, > > > particularly the devuan profile: > > > https://git.devuan.org/devuan/arm-sdk/blob/master/arm/profiles/common-devuan > > > > This is a program you wrote. Much appreciated, but I have no idea what > > it is for or how to use it. > > > > Once you do debootstrap once, you also need to do the second and the > third stage, respectively, to get a working system. > > This is why I linked to "common-devuan" because in there you can see > what you have to do. Go to the bottom, and look at the for-loop. These > are the complete steps on how to get a fully bootable system. I apologize for being so slow, but problems abound. I decided to try the devuan installation with the installer ISO on a key. I used the devuan-jessie-i386-alpha4-netboot.iso. However, when it came time to download installation components from the devuan archive, it failed: "Bad archive mirror". The archive it tried was us.mirror.devuan.org. Shouldn't it be us.mirror.devuan.org? When I used debootstrap to produce the broken base system, it created a sources.list with the entry: deb http://debootstrap.invalid/ jessie main. As for your script, I remain lost (I'm not a programmer, but a social scientist). I don't know what the variable "device-name" refers to. Perhaps to the /dev/sda1 to which I'm trying to install devuan. I assume that second and third stage refer to phases in the installation process, but I have no idea what they are. If you are simply suggesting I rerun debootstrap several times, I actually did it at least twice, and still get the message that seems to imply my libc version is wrong. Perhaps my problem was that I unpacked the devuan.debian.tar.gz archive on the target /mnt/debinist/usr/share. If instead I run # dpkg -i debootstrap_1.0.75-1+devuan1_all.deb I fear it will overwrite the debootstrap on my current Wheezy Debian system and break it. Haines ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] debootstrap requires key
On Mon, Apr 25, 2016 at 05:47:15PM +0200, parazyd wrote: > On Mon, 25 Apr 2016, Haines Brown wrote: > > Perhaps my problem was that I unpacked the devuan.debian.tar.gz archive > > on the target /mnt/debinist/usr/share. If instead I run > > > > # dpkg -i debootstrap_1.0.75-1+devuan1_all.deb > > > > I fear it will overwrite the debootstrap on my current Wheezy Debian > > system and break it. > > The debootstrap from devuan is safe to install. It differs only in > having a few bugfixes. Besides, you can always grab the package from > wheezy and overwrite. Again, please excuse my ignorance. You appear to say that I can use dpkg to install the dpkg -i debootstrap_1.0.75-1+devuan1_all.deb on my running Wheezy system, for it is essentially the same. But when I do that and run: # debootstrap -no-check-gpg jessie /mnt/debinst/ \ http://packages.devuan.org/merged E: No such script: http://packages.devuan.org/merged > Anyway, sorry if there is too much 'tech talk'. Try looking at this > forum thread: > http://www.linuxquestions.org/questions/debian-26/how-to-install-debian-using-debootstrap-4175465295/ Yes, thanks. What confused me was that when I did cross installation in years past, there were no stages to worry about. But the immediate problem is that I can't even get started with the above command. Haines ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[DNG] problems with devuan iso on key
Having too little time to spend struggling with a debootstrap cross install, I built a devuan installation USB key, first with unetbootin and then with a dd copy. Results the same in either case, so I'll just describe my experience with the second. I did # dd if=devuan-jessie-i386-alpha4-netboot.iso of=/dev/sda bs=4M; sync I booted to the key and I choose expert install. When it said to insert a key with my WiFi card driver, I did, but it did not seem to see or query the key. So had to hook up an ethernet cable. When I got to this point with ethernet, the installer failed to automatically configure the network. Had to do it manually by entering my host's IP address. Network configuration now succeeded. Now there is a download of files needed for a base system. It checked the mirror, it downloaded release files, and after some time the progress bar reached 100%. Then I get "Bad archive mirror". I tried FTP, I tried a more distant mirror, etc, but result was the same. Why does the error appear after it seems to have already successfully downloaded the files? Haines Brown ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[DNG] chroot sees wrong version of libc
A question I raised was left unanswered because the thread drifted into other issues. So let me repose the question in an appropriately named thread. I'm doing a cross install of devuan Alpha 4 onto a newly partitioned hard disk (/dev/sda1) in same box as my running Debian Wheezy system (/dev/sdb1). I partitioned, formatted and mounted the needed new disk's partitions; I downloaded debootstrap_1.0.75-1*.deb to a working directory in my current sytem; I unpacked the data tarball, Finally I ran the devuan debootstrap to install a base system on the target drive. # debootstrap --no-check-gpg jessie /mnt/debinst \ http://packages.devuan.org/merged Basically this went well, and in about 5-10 minutes I had the files for a basic devuan system on the target drive. However, some hiccups along the way: W: Couldn't download package mount (ver 2.26.2-6+devuan arch i386) ... W: Couldn't download package coreutils (ver 8.23-r arch i386) ... W: Retrying failed download of http://packages.devuan/org/merged/pool/DEBIAN/main/g/gnutls28/ \ libgnutls-deb0028_3.3.8-6+debv8ud_i386.deb ... W: Couldn't download package insserv (ver 1.14.0-5 qrch i386) ... I: Validating libpam-modules 1.1.8-3.1+deb8u1+b1 W: Retrying failed download of http://packages.devuan.org/merged/pool/DEBIAN/main/p/ \ pam/libpam-modules_1.1.8-3.1+deb8u1+b1_i386.deb ... I: Retrieving startpar 0.59-3 W: Couldn't download package startpar (ver 0.59-3 arch i386) ... I: Retrieving udev 215-17+deb8u4 W: Couldn't download package udev (ver 215-17+deb8u4 arch i386) I: Retrieving tar 1.27.1-2+b1 I: Validating tar 1.27.1-2+b1 W: Retrying failed download of http://packages.devuan.org/merged/pool/DEBIAN/main/t/tar/ \ tar_1.27.1-2+b1_i386.deb I: Retrieving tar 1.27.1-2+b1 ... E: Couldn't download packages: mount coreutils insserv startpar udev Why were these five packages not found? They are obviously critical. When I go to https://packages.devuan.org/merged/, the pool directory is empty. A puzzle. But I suppose none of this is relevant to my effort next to chroot into the new system: # LANG=C.UTF-8 chroot /mnt/debinst /bin/bash /bin/bash: /lib/i386-linux-gnu/i686/cmov/libc.so.6: version `GLIBC_2.15' not found (required by /bin/bash) /bin/bash: /lib/i386-linux-gnu/i686/cmov/libc.so.6: version `GLIBC_2.15' not found (required by /lib/i386-linux-gnu/libncurses.so.5) /bin/bash: /lib/i386-linux-gnu/i686/cmov/libc.so.6: version `GLIBC_2.15' not found (required by /lib/i386-linux-gnu/libtinfo.so.5) This seems to be a problem running chroot from my running machine and is irrelevant to the lean devuan target I just installed. If so, failure to download some packages is irrelevant to the chroot problem. I gather glibc is part of libc. So do these errors indicate that the libc version on my running machine is incompatible with its version of chroot? I do: $ ldd /bin/bash ... libc.so.6 => /lib/i386-linux-gnu/i686/cmov/libc.so.6 (0xb7609000) $ ldd /usr/sbin/chroot ... libc.so.6 => /lib/i386-linux-gnu/i686/cmov/libc.so.6 (0xb7643000) Haines Brown ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] chroot sees wrong version of libc
On Wed, Apr 27, 2016 at 06:05:56PM +0200, Didier Kryn wrote: > Le 27/04/2016 17:47, Haines Brown a écrit : > > > >I'm doing a cross install of devuan Alpha 4 onto a newly partitioned > >hard disk (/dev/sda1) in same box as my running Debian Wheezy system > >(/dev/sdb1). I partitioned, formatted and mounted the needed new disk's > >partitions; I downloaded debootstrap_1.0.75-1*.deb to a working > >directory in my current sytem; I unpacked the data tarball, Finally I > >ran the devuan debootstrap to install a base system on the target > >drive. > > > > # debootstrap --no-check-gpg jessie /mnt/debinst \ > > http://packages.devuan.org/merged > > > > I think you should use the --foreign option of debootstrap. > > first 'debootstrap --no-check-gpg jessie /mnt/debinst' > > then 'chroot /mnt/debinst debootstrap --second-stage' Didier, thanks! That was the answer. I was confused by the debootstrap man page because it sounded like the --foreign option was for non-matching architectures. But adding that option to debootstrap allowe me to go through the entire devuan installation. There were a couple hiccups, but I await the devuan installation guide before bringing them up. I found I had to bind mount /sys before I could install grub2. My /dev directly already well populated; I had no /proc directory, but mount tells me: none on /proc type proc (rw,relatime). The /sys directory exists, but is empty, so I do # mount -o bind /sys/ /mnt/debinst/sys and grub installation then went smoothly. Finally I decided to beef things up with tasksel. I wanted at this point to install print server and SSH server. I select and try to install them. But I get: "tasksel: apt-get failed (100)". This error often because of error in sources.list. All I have in it is one line: deb http://packages.devuan.org/merged jessie main However, I have no problem installing cups-client (the equivalent of printer-server?), xorg and fluxbox individually. Whenever I install packages I'm warned that that the packages are untrusted and I have to tell aptitude to proceed anyway. I wonder if tasksel fails because it cannot convey a willingness to risk installing untrustworthy package? I should now have a bootable system thanks to your help. Haines ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[DNG] Missing packages
I've been installing alpha 4, and find that the firmware-iwlwifi and task-mail-server packages are not available. While I can work around this, before I do I wonder if there a reason why they are unavailable? Haines Brown ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[DNG] dist upgrade from alpha4 to beta
I just installed alpha4, unfortunately just hours before beta became available. Naturally I want to upgrade from alpha to beta. In my alpha 4 sources.list I have: deb http://packages.devuan.org/merged jessie main non-free contrib However, if the beta is jessie, then I should already be at beta level. That is, a simple aptitude update/safe upgrade would be all I need to do, rather than a dist-upgrade. Is that so? Haines Brown ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Missing packages
On Fri, Apr 29, 2016 at 06:32:44AM -0400, Haines Brown wrote: > I've been installing alpha 4, and find that the firmware-iwlwifi and > task-mail-server packages are not available. While I can work around > this, before I do I wonder if there a reason why they are unavailable? > > Haines Brown Let me elaborate. In debian, the firmware-iwlwifi package is found in the pool/non-free/f/firmware-nonfree/ subdirectory. In packages.devuan.org/pool/, there is only a main directory, no non-free directory. Why is that? What is the work-around? Haines ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[DNG] invalid security certificate
I've got beta running. To avoid annoying security warnings each time I install a package, I tried to visit security.devuan.org, but got this error: security.devuan.org uses an invalid security certificate. The certificate is only valid for the following names: devuan.org, www.devuan.org (Error code: ssl_error_bad_cert_domain) How do I resolve this? Haines Brown ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[DNG] [helle...@dyne.org: Re: Missing packages]
- Forwarded message from hellekin - Date: Fri, 29 Apr 2016 15:12:29 + From: hellekin To: dng@lists.dyne.org Subject: Re: [DNG] Missing packages User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Icedove/38.5.0 > > On 04/29/2016 03:02 PM, Haines Brown wrote: > > packages.devuan.org is run by Amprolla, and provides overlays over > > existing package repositories. Forked packages that appear in the > > devuan-packages group on git.do are present in devuan/pool/main. If > > it's not forked, it comes from Debian mirrors instead, hence not from > > packages.do. > > What is the work-around? > > > Devuan only packages free software. The non-free archive comes from > Debian. Activate the non-free component, as you would in Debian, and > you should be set. Thank you. That solved the problem. I put this line into sources.list: deb http://ftp.us.debian.org/debian/ jessie non-free contrib and then had no trouble installing firmware-iwlwifi. However, another package excluded from devuan is task-mail-server. Adding the above line to sources.list did not provide access to this package. So am I compelled to install procmail, exim4, fetchmail, spamassassin individually? Haines ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] [helle...@dyne.org: Re: Missing packages]
On Fri, Apr 29, 2016 at 04:54:44PM +, hellekin wrote: > On 04/29/2016 04:24 PM, Haines Brown wrote: > > > > Thank you. That solved the problem. I put this line into > > sources.list: > > > > deb http://ftp.us.debian.org/debian/ jessie non-free contrib > > > This is wrong. You're using Debian repository directly: you're on > your own. You should use http://packages.devuan.org/merged/ for > Devuan sources. Not anything else. Let me see if I understand you correctly. the package firmware-iwlwifi is not open software, and so is not available from the devuan package archive. So a) The sources.list line deb http://packages.devuan.org/merged jessie main non-free contrib should not have non-free appended because devuan does not support non-free packages. b) The only way to get firmware-iwlwifi, an essential package I cannot do without, is to get it as I did from the Debian mirror, but I'm "on my own" because Devuan does not support it. c) The same for task-mail-server, which apparently has some non-free drivers. Is this why it is absent? I had to install the obvious applications such as exim4, procmail, mutt, spamassassin, individually. Haines Brown ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] [helle...@dyne.org: Re: Missing packages]
On Fri, Apr 29, 2016 at 05:41:18PM -0500, Nate Bargmann wrote: > * On 2016 29 Apr 16:53 -0500, Haines Brown wrote: > > > Let me see if I understand you correctly. the package firmware-iwlwifi > > is not open software, and so is not available from the devuan package > > archive. So > > > > a) The sources.list line > > deb http://packages.devuan.org/merged jessie main non-free contrib > > should not have non-free appended because devuan does not support > > non-free packages. > > I just posted a message to another thread where I have my sources.list > set as: > > deb http://packages.devuan.org/merged jessie main contrib non-free My line is the same: deb http://packages.devuan.org/merged jessie main non-free contrib > and firmware-iwlwifi is not shown to be in the obsolete and locally > installed packages section in Aptitude CUI which tells me that it is > in the list of available packages. Indeed, it is now present. > > c) The same for task-mail-server, which apparently has some > > non-free drivers. Is this why it is absent? I had to install the > > obvious applications such as exim4, procmail, mutt, spamassassin, > > individually. # aptitude show task-mail-server E: Unable to locate package task-mail-server > Ham radio, Linux, bikes, and more: http://www.n0nb.us KB1GRM, ET1(SS) ret. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Evince
I don't want divert the thread, but would like to widen it a bit. I have been using xpdf for viewing/printing PDF files, but it increasingly fails to print some PDFs, and so I look for alternatives. Appealing of MuPDF because of its simplicity and the quality of its display, but it lacks printing. I find qpdfview to be nice at first glance. It is simple and offers a print dialog. I see that it is automatically installed in Devuan Beta. In light of the discussion here, what is the difference between automatic installation and being default? If qpdfview is default, why do folks nevertheless turn to atril? Haines Brown ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Evince
On Mon, May 23, 2016 at 01:35:27PM -0400, Steve Litt wrote: > On Mon, 23 May 2016 08:59:15 -0400 > Haines Brown wrote: > > > > In light of the discussion here, what is the difference between > > automatic installation and being default? If qpdfview is default, why > > do folks nevertheless turn to atril? > > Ability to print. Does not seem to be true. I can display a pdf with gpdfview, and have no problem printing and even open some print options such as number of pages. Haines ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Evince
On Thu, May 26, 2016 at 02:03:26PM +0200, emnin...@riseup.net wrote: > I do not find the msg, but someone here suggested to use xpdf, possibly > with a more esthetic skin. > > I for one, would love that, since i find xpdf really very functional > and with acceptable print options too. I used xpdf for years because of its simplicity. However, recently (with Wheezy?), it sometimes cannot print a PDF. Blank pages come out of the printer. I've had to resort to $ lpr to print. Printing is about all I need from a PDF viewer. Mupdf is appealing, but I have yet to find any way to get it to print. I like qpdfview beause it is simple and prints, but I find that I one can't select text with a mouse for pasting elsewhere, which is crucial for me. I can select text in evince, and so installed atril. At this point it seems it is my only choice if I want to avoid dragging a lot of garbage in (okular). Haines Brown ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[DNG] Is kernel 4.5.0 flakey ?
I installed 64bit jessie on a new HDD, and initially used the 3.16.0 kernel. Then I installed the 4.50 kernel and ran into trouble. kernel:[25090.816205] NMI watchdog: BUG: soft lockup - CPU #7 stuck for 22!s [colord-sane:20969] This message is displayed every few seconds in whatever happens to have the focus and is accompanied with a beep. The keyboard and mouse hang so that I must do a hot reboot. Is this in fact a kernel bug? How (simply) do you tell GRUB to boot an earlier available kernel? Is there any reason not to purge Grub and install LILO in place of it? Grub is too difficult for me. Haines Brown ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Is kernel 4.5.0 flakey ?
On Wed, Jun 01, 2016 at 12:22:14PM +0200, Florian Zieboll wrote: > On Tue, 31 May 2016 16:14:58 -0400 > Haines Brown wrote: > > > How (simply) do you tell GRUB to boot an earlier available kernel? > > > If you want to leave the problematic kernel installed, you can make > grub2 default to another boot entry by adding/editing the line > > GRUB_DEFAULT=0 > > to /etc/default/grub and then running "update-grub". Thanks, Florian. I guess UEFI will become unavoidable and so I'll have to stick with GRUB. I'll pursue Grub customization. Meanwhile I'll block the new kernel as you suggest with GRUB_DEFAULT=1. With the new installation I did quite a few updates and safe-upgrades, but none brought in the 4.5.0 kernel as far as I know. It was only because for some reason I searched the archive for linux-image that I discovered it and installed it. Does not its presence in the Devuan beta Jessie repository mean that the 4.5.0 kernel is considered stable? Haines ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Is kernel 4.5.0 flakey ?
On Thu, Jun 02, 2016 at 12:32:15AM +1200, Daniel Reurich wrote: > > > With the new installation I did quite a few updates and safe-upgrades, > > but none brought in the 4.5.0 kernel as far as I know. It was only > > because for some reason I searched the archive for linux-image that I > > discovered it and installed it. Does not its presence in the Devuan beta > > Jessie repository mean that the 4.5.0 kernel is considered stable? > > It would only have been there if you either had the jessie-backports or > unstable/experimental repositories also setup, and in all those cases > there is no guarantee it is stable. > > Regards, Yes, that's the explanation. I had forgotten I had added backports to my sources.list for some reason. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Is kernel 4.5.0 flakey ?
Unfortunately, when I go back to kernel 3.16.0-4-am64, my X system
hung. No MNI hang (in the short time I was running the 3.16.0
kernel), but some application I start in .fluxbox/startup is being
disagreeable and causing X system to hang. Because of work pressure,
I'll have to put off dealing with this until the future.
Incidentally, just to play I appended this to /etc/grub.d/40_custom:
menuentry "a little experiment"{}
I expected the phrase to show up in Grub's menu, but instead it
caused a syntax error in Grub's configuration and I had to cut it.
Not sure why this was invalid (there were no end of line spaces).
Haines
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[DNG] eudev status
I just received an automated message informing me that I have not been active on the list for some time. This gives me an excuse to ask a question or two. I installed jessie-beta on a disk some time ago, and off hand it boots and runs just fine. However I didn't migrate it to from my current Debian Wheezy because I was waiting for the eudev/vdev/udev issue to be resolved, figuring that migrating up from present udev to one of the others could well be traumatic. I didn't want to do it on a system on which I relied for work. Two questions, if I may: Is eudev being actively worked on, and is it likely to be in the upcoming non-beta Jessie Devuan? I hear complaints that there insufficient work being put into the Devuan project. Is there a crisis because of lack of volunteers? Is it likely that a non-beta Devuan Jessie will make the light of day in first half of 2017? Haines Brown ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] New documentation on the Surf browser
Steve, your documentation much appreciated. I'm been toying with a migration to Surf, and was frustrated by not knowing how to do the simplest things. Now I'll give it another. Your instruction are in HTML format, and so naturally in Firefox I clicked to Save as PDF. In fact, most of my work on line uses that facility. But in your instruction I could not find any reference to it. Any hope for me? Haines Brown ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] New documentation on the Surf browser
Why do we need PDFs? In my case, I must load files into a database that works with PDF, not with HTML. I am aware of effective conversion tools, but a one-click Save As PDF saves the HTML file being viewed as PDF and puts just one file where I need it to move it to the database. Haines ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[DNG] installation of Jessie 1.0 fails (busybox)
With Jessie 1.0 out, I decided to move from the beta as a system to play with to make Jessie 1.0 my primary system. I dd copied the DVD ISO to a 8 G USB key and booted it. I didn't expect to have any installation (expert) problems, but did. After having the partitioner format all partitions, I began to install the new base system. This proceeded for a while. I chose the 3.16.0-4-amd64 kernel. Then installation of base system halted with the error: "An error was returned when trying to install the busybox package onto the target system." It suggested taking a look at syslog, but it was not informative. Immediately after it says klogd is installed, it says "syslogd started: BusyBox v1.22.1" Searching on line did not help. Could there be a problem with the ISO? If so, would it be best to download it anew or should I simply recopy it to the key? Haines Brown ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] installation of Jessie 1.0 fails (busybox)
It seems the download ISO was in fact damaged. I downloaded it again, did check sum, and installed without a problem. Thanks for the advice. Haines ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[DNG] Jessie 1.0.1 misconfigured GRUB
After installing Jessie 1.0.1, I tried to boot to it. I can do it from a GRUB menu on another disk (Debian Wheezy), but not the Devuan Jessie disk. I do not use UEFI, and I installed amd64 from ISO on a key. I get: "error: file `boot/grub/i386-pc/normal.mod not found' I assume the error means GRUB does not know where to find the normal command. That should be a simple matter of fixing GRUB configuration. However, no luck. The problem is that when I to bring up the GRUB menu with a boot, it takes me to grub rescue> prompt. I want grub> instead, but don't know how to get it. I tried SHFT, c and C as GRUB loaded, but still did not get the grub> prompt. I tried # update-grub and # aptitude install grub2, but that did not change things. How do I get the grub> prompt instead of grub rescue>? I don't understand why it seeks i386-pc normal command when I'm running amd64. Or is this normal? grub rescue> ls command lists the expected devices, but not vmlinuz etc. Haines Brown ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[DNG] lost ability to execute
Installation of Jessie 1.0.1 AMD64 went well. I did not install desktop packages during install, but instead xorg afterwards along with a lot of other packages. I went to starx: /usr/bin/mcookie: not found Couldn't create cookie $ ls /usr/bin/ | grep mcookie mcookie $ echo $PATH .../usr/bin:.. I rebooted, and now I can't run any executable. For example, $ aptitude search xorg -bash: /usr/bin/aptitude: No such file or directory No idea what happened. The executables are in PATH. The syslog no longer being written. Haines Brown ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] lost ability to execute
Ged, thank you for the reply. But it leaves questions in my mind. On Sat, Jun 03, 2017 at 02:04:05PM +0100, G.W. Haywood wrote: > >Installation of Jessie 1.0.1 AMD64 went well. > > Considering what you write below, I'm not entirely convinced. :) > > >I did not install desktop packages during install, but instead xorg > >afterwards along with a lot of other packages. > > This starts to look like Pilot Error, but in fairness I suspect that > what you're trying to do might also be beyond the capacity of the > system that you're trying to do it with at this stage in its life. > Devuan Jessie is, in software terms, rather new. If you stress the > package installation you can expect to break it in interesting ways, > which may make recovery difficult if you're not an expert. I have an installation routine I've used since Lenny and perhaps even Etch. I stuck to it, and generally accepts defaults. The system is a bit old (3 yrs), but has 32 G RAM and 1 T disks. It should be able to endure an install. Don't know what it means to "stress" package installation. It's the same set of packages I had not problem installing on earlier versions of Debian. Are you suggesting that Devuan Jessie might have some installation weaknesses not present in Debian Jessie? > >I rebooted, and now I can't run any executable. ... > > $ aptitude search xorg > > -bash: /usr/bin/aptitude: No such file or directory > >... > >No idea what happened. The executables are in PATH. ... > > The symptoms look to me like those of a broken library setup, I think > you have somehow mixed 32-bit and 64-bit packages. Perhaps you should > start the installation again without trying anything, er, creative. :) How can a package installation damage existing libraries? How is it possible to mix 32-bit and 64-bit if one follows the installer's defaults? I installed packages from the US Devuan repository. Perhaps I should instead have installed them from my USB key DVD ISO. I'll try that when I have the time. > Incidentally mailing list etiquette suggests replies on-list, not > private replies, to list posts. That way everyone can benefit. I'm > not upset or offended by off-list replies but my mail server will now > gently reject them as a reminder to those who forget the conventions. My apologies, I didn't see that you were answering my question off list. Haines ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] lost ability to execute
On Sun, Jun 04, 2017 at 09:54:38AM +0100, KatolaZ wrote: > I don't know exactly what your custom "installation routine" entails, > but since there have been a few dozen thousands successful Devuan > installations in the last few months, and nobody has reported anything > even remotely similar to the problems you talk about, shouldn't we > probably consider at least as a remote option the possibility that > there is something not entirely right in the custom procedure you are > using, or something peculiar in your specific system configuration, > that might have little to do with Devuan? Yes, I agree, but my "routine" for installation is not "custom", but follows installer defaults. I had no problem with the Jessie Beta install, and the first time I installed Jessie 1.0.1 I was able to install many packages before I lost the ability to execute. On subsequent installations I lost ability to execute anything right from start. I could run nano, but not aptititude. Bash found former but not later, although both in /user/bin. It is almost as if I broke hardware when I installed a package. Next time I'll first run mkfs.ext4 on the disk. I put the Jessie amd64 ISO on a key. Because I had incomplete ISO at one point, after doing # dd if=devuan_jessie)1.0.0_amd64_DVD.iso of=/dev/sdd bs=4M; sync I did checksum. I had no trouble booting to it, but could not install the installer components from "CD" because my key not recognized. So used Devuan repository for them instead. Among installer components, I installed the mbr-udeb for PCs because I assumed that meant to use the UBR. But now I wonder if it means to use MBR for 32-bit system. When it came to partitioning, I choose the default no to UEFI. I put /boot into / without breaking it out as I usually do. I don't quite follow the default partition order, and I add two custom partitions. When it came to configure APT, I chose a network mirror. Next time I'll try to get packages from my USB key. Found I had to use http protocol because ftp didn't work. In collections to install, I un-select desktop environment. I suppose the justification for Devuan is to avoid such bloat. After installing GRUB2 the last two times, I go immediately to a shell instead of a reboot. I find that in the /boot/grub/ directory the i386-pc directory is missing, and so was unable to boot the last two installations. This strikes me as a problem of 32/64-bit confusion, but don't know how that is possible. Haines ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] lost ability to execute
On Sun, Jun 04, 2017 at 02:54:22PM +0100, G.W. Haywood wrote: > Hello Haines, > > On Sun, 4 Jun 2017, Haines Brown wrote: > > >I have an installation routine I've used since Lenny and perhaps > >even Etch. I stuck to it, and generally accepts defaults. > > A list of exactly what you started with and exactly what you did, > step-by-step, would be more useful to the problem-finding. You've > made a start in your reply to KatolaZ although it's a bit woolly. I will do that. > It looks like the problem (if it's only one, and I'm starting to > wonder) happened independently of installing sets of packages. Yes, I've come to that conclusion as well. > I'm almost sure that the damage is that you have mixed architectures. > You have either a 32-bit binary looking for 32-bit executables or a > 64-bit binary looking for 64-bit executables and in neither case is it > finding them. When you look in the directory tree you see files which > you take to be the executables, but they are not executable by your > running system so it perfectly properly ignores them. > > >How is it possible to mix 32-bit and 64-bit if one follows the > >installer's defaults? > > You tell us. The list I mentioned above might become the basis of a > bug report, or it might be the answer to many of the questions, but at > the moment I don't know if there's enough information for anyone to be > able to replicate the issue and that's crucial. I have two disks, one with an old Debian Wheezy, my working system, and a new one on which I am trying to install Jessie 1.0.1. To facilitate setup, on my old debian I had created a set of mount points /mnt/devuan/... which fstab automatically mounts when I boot the old debian. I wonder if this could somehow result in a mongrel 32-bit/64-bit installation. When I try a new re-install of Devuan Jessie 1.0.1 later and record exactly what I do, I'll first umount all these mount points and comment their mounts in fstab. Another anomaly is what when I boot the old devuan, the boot goes to recovery mode despite what is selected in the GRUB menu. A control-D continues the boot normally. It showed up only fairly recently. But since I seldom reboot it, I didn't worry much about the issue. The two disks are almost the same, one being a bit older than the other. My Debian is on /dev/sdb and I'm installing to /dev/sda, I wonder whether the mongrolized install might be not be some kind of cross over between the two devices caused by BIOS. > >I installed packages from the US Devuan repository. Perhaps I should > >instead have installed them from my USB key DVD ISO. I'll try that > >when I have the time. > > It could be you've mixed architectures that way but it seems to me more > likely that at some point you weren't running the executables that you > thought you were running because you had more than one architecture on > various operating systems lying around on the drives in your system. Yes, that's the case. The problem is to figure out how they might influence each other. Haines ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] lost ability to execute
Did a re-install from DVD ISO on key. I first commented all commands to boot Devuan partitions from my Debian fstab. In BIOS I changed disk priority so that the Debian disk would boot. I booted the Devuan installer and choose expert install. I select all defaults unless otherwise noted. Detect CD drive does see my key with its Jessie 1.0.1 amd64 ISO. I do not choose any installer components. I had assigned the same machine name for both disks, but now change the name for the target disk. In partitioning, I realize that I have a backup USB drive connected, and so disconnect it at this point. Next time I'll remember to have it disconnected, but doubt it makes any difference. The backup disk does not hold a copy of the root partition. I install base system defaults. I configure the package manager. This time I have no problem accessing the DVD ISO for packages. I deselect Desktop Environment for installation. I install GRUB on my target disk. I go to a shell and see that I still don't have a i386-pc directory in /boot/grub, and so naturally when I reboot, the boot fails. I'm about to do another installation, but this time don't do it as expert, but follow all defaults, including auto partitioning and Desktop Environment to see what happens. Haines ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] lost ability to execute
Interim report. Without USB back drive installed, I installed the Jessie DVD ISO from key. Do simply installation routine. When it came to partitioning, I accepted a single partition on entire target disk. Oddly my backup USB drive still reported as a possible target even though it is disconnected. I do the installation from the key rather than Devuan repository. I should note that on one prior installation I had installed mbr-pc because I thought it was asking if I wanted to use the MBR. Could this have messed up my disk? When I reboot to the target disk, all I get is a blinking line cursor upper left. Apparently kernel not seen. I try boot Devuan Jessie from my old disk GRUB menu, but is says no such disk. I suspect I need do a hard disk recovery. I suppose mkfs.ext4 on it would be of no help. Haines ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] lost ability to execute
On Sun, Jun 04, 2017 at 10:42:43PM -0400, Robert Marmorstein wrote: > Am I understanding correctly that you are running the Devuan installer > executable from a running 32-bit Debian system? No. The 32-bit Debian system is shutdown down, the Devuan installer key is inserted and it is booted. I often upgraded Debian by installing a new version on a new disk and do it with a chroot cross install. It seems one can't chroot a 64 system from a 32 bit system, or at least I haven't figured out how to do it. Haines ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] lost ability to execute (somewhat resolved)
The problem was more worked around than resolved. After having no grub modules with an installation on a new disk, whether DVD or netinst ISO, I knew the problem wasn't with the disk. I installed Devuan Jessie more or less successfully on a new disk without the old disk being connected. Then I reconnected the old disk and now can boot either operating system successfully. If anyone has an idea of what might be the problem, I'd appreciate knowing. Perhaps with both disks attached, the presence of one preoccupies the SATA port needed by the other. Incidentally, the key on which the ISO is installed names itself UEFI. I have both UEFI and legacy selected in BIOS. If I have just legacy, nothing boots. Haines Brown ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] lost ability to execute (somewhat resolved)
On Thu, Jun 08, 2017 at 01:40:39PM +0100, G.W. Haywood wrote: > Hello again, > > On Thu, 8 Jun 2017, Haines Brown wrote: > > >The problem was more worked around than resolved. > > > >After having no grub modules with an installation on a new disk, whether > >DVD or netinst ISO, I knew the problem wasn't with the disk. I installed > >Devuan Jessie more or less successfully on a new disk without the old > >disk being connected. Then I reconnected the old disk and now can boot > >either operating system successfully. > > Sounds a lot like what I recommended on 4th June. :) GRUB is working fine. I can boot either disk from either GRUB menu. Why I had to isolate the target disk in order to install Devuan remains a mystery, but it does not seem to have to do with GRUB, which is working. > >Incidentally, the key on which the ISO is installed names itself UEFI. I > >have both UEFI and legacy selected in BIOS. If I have just legacy, > >nothing boots. > > I'd have expected that you could select just legacy and then do a > clean install, although I don't think I've never cared which it uses. I had tried that, but failed. Forget the error, but it may have been the blinking cursor indicating that no operating system found. The usb key from which I install describes itself as UEFI, which may make it unusable unless I have both legacy and UEFI in BIOS. I just installed Devuan on another machine that already had a Debian (Etch?) disk on it. After installation I could not boot Devaun because of partition table error. However, testdisk says the partition structure is OK. I'm doing a "deeper search". As for my main Devuan install, I'm having trouble installing the xserver. But aptitude tells me xorg is not a real package. I'm moving from Debian Wheezy 32-bit to Debuan Jessie 64-bit, and perhaps I'm missing something. Is xorg still the way to install xserver? Haines ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] lost ability to execute
On Fri, Jun 09, 2017 at 01:47:54PM +0100, G.W. Haywood wrote: > Hello Haines, > > On Fri, 9 Jun 2017, Haines Brown wrote: > > >I'm moving from Debian Wheezy 32-bit to Devuan Jessie 64-bit ... [*] > > I'd say that probably does qualify as stressing the installer, even if > it's only ever so slightly. :) > > * Apologies, spelling of 'Devuan' corrected for the search engines. > > >... aptitude tells me xorg is not a real package. [...] > >Is xorg still the way to install xserver? > > https://git.devuan.org/dev1fanboy/Upgrade-Install-Devuan/wikis/Minimal-xorg-install Wow! That was it! I missed the fact that I could no longer simply install xorg as on Wheezy. Must of missed the relevant README. With the information you kindly supplied, xserver and window manager install without any problem. Many thanks. Haines ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[DNG] what looks for gsettings?
Not a real problem, but annoying. I have a new installation of Devuan Jessie that has an X server, the fluxbox window manager, but no desktop environment. When I boot, just before the log in prompt is the message: "-bash: gsettings: command not found" Why do I have anything gnomish in the system? What might seeking gsettings even before X server is started? How can I get rid of the alert? Haines Brown ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] what looks for gsettings?
On Mon, Jun 19, 2017 at 02:37:42PM +0200, Joachim Fahrner wrote: > Am 2017-06-19 13:26, schrieb Haines Brown: > >I found no gsettings in Devuan, but there is one in Debian: > >/usr/share/bash-completion/completions/gsettings. It is a simple > >non-executable script. > I suspect a missing dependency. You can install libglib2.0-bin, or > you can try to find out what will call /usr/bin/gsettings. You can > place a little shell script as /usr/bin/gsettings and echo some > information about the calling process. > > Since you have no desktop environment, calling gsettings makes no > sense. So I would try to find the reason for this. Jochen, thanks. Installing libglib2.0-bin solved the problem. Haines ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[DNG] flash player for browser
I know the issue of flash player has often come up, but I don't normally watch videos and so did not pay attention. I need access an online database, but when I try to do it I get the error message that I don't have the latest version of Macromedia Flash Player. The site needs Macromedia Flash Player 11.1 or higher. Is the Flash Player the same as a flash player plugin for my Iceweasel browser? The browser flash plugins seem just for playing YouTube. I already have the YouTube Flashplayer extension installed in my browser. Discussions simply say to install flashplugin-nonfree. That I've done. However, that does not provide access to the database. Still get the error message. Haines Brown ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] flash player for browser
On Wed, Jul 26, 2017 at 07:49:56PM +0200, Joachim Fahrner wrote: > Am 2017-07-26 19:40, schrieb Haines Brown: > >I need access an online database, but when I try to do it I get the > >error message that I don't have the latest version of Macromedia Flash > >Player. The site needs Macromedia Flash Player 11.1 or higher. > > Adobe ceased the flash player supoort for Linux long time ago. And now they > announced the end of flash player for all platforms. Flash is dead! > > https://blogs.adobe.com/conversations/2017/07/adobe-flash-update.html Ah! Thank you. So then how do I access the database? The files I need to access are newspaper images. Haines Brown ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] OT: most processors are insecure (was Re: Nvidia Drivers)
It would be naive to think that CPU producers don't build in a backdoor. This is why I take an interest in Chinese CPUs. At this point they are only RISC processors, but before long they should produce a product competitive with Intel. I suppose it will also have a back door, door, but China seems less threatening than the U.S. Haines ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[DNG] D-Bus and systemd
I'm happily running Devuan Jessie with the fluxbox window manager but no desktop environment. There is an oddity that causes no problems so far, but I would like to understand it. When I boot and before logging in or starting the X server, the boot message ends with this warning: dconf-WARNING failed to commit changes to dconf: Cannot autolaunch D-Bus without X11 display. D-Dus is automatically launched as part of the boot process. In my boot log there is: Wed Sep 6 16:49:11 2017: [] Starting system message bus: dbus^[[?25l^[[?1c^[7^[[1G[^[[32m ok ^[[39;49m^[8^[[?25h^[[?0c. Wed Sep 6 16:51:29 2017: [] Starting system message bus: dbus^[[?25l^[[?1c^[7^[[1G[^[[32m ok ^[[39;49m^[8^[[?25h^[[?0c. Do if dbus is automatically launched and does in fact get launched, why the warning that autolaunch failed? What kind of changes get reported to dbus configuration? And why do they depend on the X display or perhaps its getting a 0:0 value? I'm not using systemd, but there are still systemd related files needed by some functions. Could the warning be an artifact that something is expecting a real systemd, but it is not getting it? Haines Brown ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Documentation format philosophies
On Sat, Nov 11, 2017 at 01:33:28PM -0500, Steve Litt wrote: > On Sat, 11 Nov 2017 12:15:44 + > LaTeX is wonderful *for what it does*, which is make beautifully > typeset documents whose linefeeds are determined at compile time, not > at read time (like ePub, HTML or Xhtml). The problem is that you can't > reasonably convert LaTeX to XML, HTML, Xhtml or the like. Conversion of TeX to HTML etc. is a challenge. These did not work very well for me: $ htlatex universal.tex "xhtml,ooffice" "ooffice/! -cmozhtf" "-coo" "-cvalidate" $ latex2html source $ tex4ht ... I had better luck with the lwarp TeX package. It stumbled on some aspects of my TeX document, but that was a year ago, and at that point it was still under early development. I believe today it does better, but have not checked. Haines Brown ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Documentation format philosophies
On Sun, Nov 12, 2017 at 09:35:09PM -0500, Steve Litt wrote: > On Sun, 12 Nov 2017 00:39:34 +0100 > Svante Signell wrote: > > > On Sat, 2017-11-11 at 13:33 -0500, Steve Litt wrote: > > > > > > > We use LaTEX in technical documents, > > > > > > LaTeX is wonderful *for what it does*, which is make beautifully > > > typeset documents whose linefeeds are determined at compile time, > > > not at read time (like ePub, HTML or Xhtml). The problem is that > > > you can't reasonably convert LaTeX to XML, HTML, Xhtml or the > > > like. > > > > Ever heard about latex2html? Tried them all, and only one that was successful in most respects was the lwarp package. Haines Brown ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[DNG] broken PDF display
Recently and not in association with any system changes, atril and xpdf no longer displays the content of perhaps half my PDF files. They see all the pages, but they are blank. An exception is that sometimes a cover page, TOC, download notice at bottom of pages, or the graphics are displayed, but not the text. This is consistent: a failure or success repeats on subsequent tries. This happens whether the PDF is version 1.4, 1.5, and 1.6. It happens on my desktop machine whether using atril or xpdf. It does not happen if I copy a problematic PDF to USB key and display it with xpdf on a laptop that has the same version of Devuan Jessie, kernel and xpdf. However, that same file on key fails to be displayed by my desktop machine. The desktop has auto-upgrades, but not the laptop. However both machines running Devuan Jessie with 3.16.0-4-amd64, The version of xpdf the same on both desktop and laptop. I've got 32 Gb RAM on this machine and no other PDFs are being displayed. I tried to reboot to clean things out, but that didn't help. The xpdf Find utility can find words in the body of a text, but displays them only as black rectangle. So the problem seems to be the display of the font. $ xpdf -fg black Abrams1995.pdf error: "black" file not found Printing the PDF has same result as its display. Haines Brown ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] broken PDF display
On Fri, Mar 23, 2018 at 06:55:46PM +, Adam Sampson wrote: > Haines Brown writes: > > > Recently and not in association with any system changes, atril and xpdf > > no longer displays the content of perhaps half my PDF files. > > I'm seeing the same problem on plain Debian with xpdf and evince -- it's > one of several problems that were introduced as part of security fixes > in libpoppler46 0.26.5-2+deb8u2. ...+deb8u1 works OK, if you don't need > the security fixes. > > There are a couple of Debian bugs about this already: > https://bugs.debian.org/886798 > https://bugs.debian.org/890826 Thank you. Mupdf displays the documents OK, and I'll probably rely on it until the ASCII upgrade becomes stable. I gather its version of libpoppler does not have the bug. Haines ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[DNG] no display of GRUB menu
I installed Jessie on a new disk on a new machine. I can boot it from the GRUB menu on another disk on that machine, but when I try to boot the new disk directly, all I get is a blinking cursor at upper left. Holding down SHFT or ESC during post did not bring up its menu. I tried redoing # update-grub. I find that /boot/grub/grub.cfg has a fully developed menu in which is: set root='hd0,mddos2'. This seems correct. BIOS sees this disk as number 0. In \ is a vmlinuz symlink that points to the vmlinuz file in a broken out /boot. Parted print shows partition 1 to be primary and flagged bootable. Partition 2 is also primary. It seems that one way to display the menu is to change to these values in these lines in /etc/default/grub to: GRUB_HIDDEN_TIMEOUT=10 GRUB_HIDDEN_TIMEOUT_QUIET=false in /etc/default/grub, but these lines do not appear and what I have instead is: GRUB_DEFAULT=0 GRUB_TIMEOUT=5 Haines Brown ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] no display of GRUB menu
On Fri, Jun 01, 2018 at 11:21:06PM +0200, Florian Zieboll wrote: > Am 1. Juni 2018 22:24:47 MESZ schrieb Haines Brown : > > > I installed Jessie on a new disk on a new machine. I can boot it from > > the GRUB menu on another disk on that machine, but when I try to boot > > the new disk directly, all I get is a blinking cursor at upper left. > > Holding down SHFT or ESC during post did not bring up its menu. > > > > I tried redoing # update-grub. > > > Depending on how you finished the installation routine, you might need to not only "update-grub", but also run "grub-install /dev/sdx", where "x" is the drive letter (without partition number) of your new disk. Florian, thanks for the suggestion. I ran # grub-install /dev/sda and this was returned: installing for i386-pc platform Installation Finished. No errors reported. I assume that "i386-pc" is appropriate for my 64bit system. The GRUB2 grub-common on this old machine (Devuan Jessie) is same version as that on the new machine. Doing Ctl-Alt-F2 while the cursor was blinking did nothing. Incidentally, I also rechecked the UUID numbers for the / and boot partitions. Haines ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] no display of GRUB menu
On Sat, Jun 02, 2018 at 11:10:02AM +0200, Didier Kryn wrote: > Le 02/06/2018 à 01:55, Haines Brown a écrit : > >On Fri, Jun 01, 2018 at 11:21:06PM +0200, Florian Zieboll wrote: > >>Am 1. Juni 2018 22:24:47 MESZ schrieb Haines Brown : > >> > >>>I installed Jessie on a new disk on a new machine. I can boot it from > >>>the GRUB menu on another disk on that machine, but when I try to boot > >>>the new disk directly, all I get is a blinking cursor at upper left. > Hi Haines. > > Could you describe more acurately the situation? You have two disks, > each with an installed OS. I suppose your working system is on /dev/sdb and > your new, non-booting one is on sda. On which OS are you running update-grub > and grub-install? Let's clarify this before going further. I would like also > to know how you reach this situation because it canhappen, but I've never > seen that after a direct install from the installer. > > Didier I somehow managed to get my new principle disk to boot directly. Access to its grub menu does not seem to have been the result of an update-grub or redoing grub-install. So I have no idea why the menu comes up now. The machine has three disks and four operating systems. The grub menu from which I previously booted disks is that of a Debian Wheezy system on an old disk. Its menu gives access to four operating systems on three disks. a) One disk holds my new installation of Devuan Jessie that now can be booted directly, b) second disk has Debian Wheezy with a workable grub menu with which to boot the other disks, c) Devuan Jessie on a disk that can't be booted directly (blinking cursor). I don't worry about it because it was an auto-installation and I don't know how to use the Xfce desktop. At some point I'll be installed Devuan Ascii on it. The fourth operating system, a Devuan Jessie base system (no x server or grub) is on partition 15 of disk (b) or disk (c). I apologize for having raising a problem that then resolved itself without my knowing why. Haines ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[DNG] ascii installation key exchange problem
I'm installing with devuan_ascii_2.0.0-rc_amd64_dvd-1.iso on a key to a new machine. I entered the wlan ESSID with care. I choose WPA/WPA2 PSK. When the installer attempts to find my wireless network, it fails. I'm currently accessing my router with may current machine running Devuan Jessie. I'm also running Devuan Jessie on a different disk on the new machine. It took three attempts to get an association, a key exchange. I'm simply reporting that association can be difficult with ascii. Haines Brown ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[DNG] ascii 2.0 installation confused by mount points
I'm installing ascii on a disk, sdc, in a machine that has two other disks, one of which, sda already has a bootable devuan jessie on it. The installation goes well until I go to write my partitioning of sdc to disk. I get the error message: "Two file systems are assigned to the same mount point (/): SCSII (0,0,0), partition #1 (sda) and SCSI3 (0,0,0), partition #1, (sdc). It is true that partition 1 of sda is a bootable primary partition, and I want to do the same for sdc. I've always had multiple independently bootable disks with their own GRUB on a machine. This is the first time I've run into trouble with it. In installation options for sdc, I did ask to have a MBR installed. Why does an installation on one disk care about what happens to be on another unmounted disk? Haines Brown ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] ascii 2.0 installation confused by mount points
On Sat, Jun 09, 2018 at 10:19:01PM +0200, Didier Kryn wrote: > Le 09/06/2018 à 22:13, Haines Brown a écrit : > >I'm installing ascii on a disk, sdc, in a machine that has two other disks, > >one of which, sda already has a bootable devuan jessie on it. > > > >The installation goes well until I go to write my partitioning of sdc to > >disk. I get the error message: "Two file systems are assigned to the same > >mount point (/): SCSII (0,0,0), partition #1 (sda) and SCSI3 (0,0,0), > >partition #1, (sdc). > > > >It is true that partition 1 of sda is a bootable primary partition, and > >I want to do the same for sdc. I've always had multiple independently > >bootable disks with their own GRUB on a machine. This is the first time > >I've run into trouble with it. In installation options for sdc, I did > >ask to have a MBR installed. > > > >Why does an installation on one disk care about what happens to be on > >another unmounted disk? > > First, check carefull y what you do in the partitionning dialog. sda > shouldn't be used at all by the system you install, but I suspect you have > maybe marked it as used in some way. Thanks, Didier, In the partitioning scheme, sda is HD ST1000DX002-2DV1. It has a primary partition that is bootable and the mount point /. When I edit this partition, it says it is on sda. Disk sdc is ST1000MN0011, and it also has a bootable partition #1. When I edit it, it says I'm editing disk ST1000MN0011 partition #1 of sdc. I give it / as mount point, make it bootable, and the label "root". Partition #1 on sda is has mount point /, the mount options I leave as the defaults, label I left out the label, but now label it "root". This should make no difference as far as I can see. I leave typical usage as "stardard". I don't know what standard options refers to, but I should think standard option would not cause this disk to interfere with others. But I get the error, "Identical mount points for two file systems." Haines ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] ascii 2.0 installation confused by mount points
On Sat, Jun 09, 2018 at 10:36:46PM +0100, Simon Hobson wrote: > Haines Brown wrote: > > > In the partitioning scheme, sda is HD ST1000DX002-2DV1. It has a primary > > partition that is bootable and the mount point /. > You probably want to set this partition to unused (or whatever it's called, it's a looong time since I last did this) so that it doesn't appear in the mount point table (eventually in fstab of the new install). I think what you are telling it is that you want sda1 to mounted as / IN THIS INSTALLATION and that then clashes with your new / (on sdc) that you're trying to install to. In "typical usage:" option when configuring the root partition, there is no option that would disable it. In any case, I don't want to disable it, but to be able to boot any disk and use its grub menu to boot it or any other disk. I've always been able to do that. It occurs to me that I could simply disconnect the SATA cable from my sda and then partition sdc and after installation reconnect sda and run update-grub on the disks. But I hesitate to do it because then the sda/sdc identity of the disk would change and I might end up unable to boot either disk. Another approach might be to boot sda run fdisk on sdc and then do an installation on sdc without partitioning it. Incidentally, on sdb I have have installed an old Debian (Etch?). When I try to partition sdc it does not want to use its root partition. only the root partition of sda. I suspect something has changed between Jessie and Ascii. The partitioner in devuan install I suppose is parted, but not sure. Haines ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] ascii 2.0 installation confused by mount points
On Sun, Jun 10, 2018 at 10:05:48AM +0200, Didier Kryn wrote: > Le 10/06/2018 à 04:01, Haines Brown a écrit : > >On Sat, Jun 09, 2018 at 10:36:46PM +0100, Simon Hobson wrote: > >>Haines Brown wrote: > >> > >>>In the partitioning scheme, sda is HD ST1000DX002-2DV1. It has a primary > >>>partition that is bootable and the mount point /. > >>You probably want to set this partition to unused (or whatever it's > > called, it's a looong time since I last did this) so that it doesn't > > appear in the mount point table (eventually in fstab of the new > > install). I think what you are telling it is that you want sda1 to > > mounted as / IN THIS INSTALLATION and that then clashes with your new > > / (on sdc) that you're trying to install to. > In the partitionner (which is not only a partitionner, but generates the > fstab and the filesystems), you should select "dont use the partition" on > every partition which is not in sdc. Click on "use partition as" and > select "dont use the partition". Didier, that seems to have done the trick. I apologize for having been too hasty. Where the partitioner asks what to use a partition as, because the top options were simply file systems, I interpreted it to be merely for selecting file system and did not notice the "don't use" option at the bottom. When I marked sda partitions not to be used, I was able to save the sdc partition table and proceed with the installation. Now that installation of ascii 2.0 on sdc is underway and before going further I must figure out how to recover a use of partitions on sda. I assume that were I to use the menu to revert to partitioning and restore usage of sda partitions I'll just end up with the same problem of a competition of sda and sdc for use of /. When I execute a shell toward the end of installation, can I use it to run the command "parted /dev/sda set 1 boot on" both to enable sda1 and to make it bootable at the same time? Would the command "parted /dev/sda set 2 on" simply re-enable the second partition? I found the parted manual unclear on this point. Haines ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] ascii 2.0 installation confused by mount points
On Sun, Jun 10, 2018 at 12:36:02PM +0100, Simon Hobson wrote: > I think you may be confused about what this section is doing. You are > telling the installer a) what to do with a disk & it's partitions (eg, > should it format a partition), and b) where they should be mounted. > So for your partitions on sda, you tell it NOT to format them and not > to mount them anywhere - I certainly recall those being options in the > Debian installer, you may need to go into expert mode. Alternatively, > tell the installer NOT to format them and set a different mount point > (eg /jessie, /jessie/boot, ...) When you set a mount point, it's > telling the installer two things : where to mount the filesystem > during the install, and what to put in the installed system's > fstab. If you tell it to do nothing with the partitions/filesystems on > sda, then they will simply be left alone - but watch put for grub > install later on, you don't want to damage the grub that's already > installed. So don't format the partitions on sda, don't mount them > anywhere, and you'll end up with a new install on sdc that just > ignores the system already on sda - but as mentioned, be careful when > it comes to grub install time. Then (I assume through the system > BIOS) you'll be able to boot using the old system & it's grub on sda, > or the new system & it's grub on sdc. Don't underestimate my ability to get confused, especially when a practice I've followed for years no longer works. It may be the difficulty arises now because two of the machine's disks are for ascii (one rc and the other stable), and jessie is on sdb. Does the conflict over use of \ only happen if operating system versions happen to be the same? If so, I wonder if an expert installer could be warned of this and what to do about it. For example, the error message that pops up could be more informative. In the partitioner, when I go to edit a partition, one option is to "use as:" If I specify to use as ext4, then the additional settings become available of whether to format the partition and set its mount point. If instead I chose "do not use", I no longer have the option to format and define a mount point. That is as you say, but your comment about watching out for GRUB later on in the installation worries me. You warn me that I should not allow grub to "damage" (confuse?) the grub on sda, but the installer asks a question that I do not find to be clear. When installing GRUB and after the installer discovers what operating systems happen to be accessible for the installation, it tells me it is safe to install GRUB in the mbr of the first drive, which in my case is sda. My intent is to leave GRUB as it is on sda and to install it instead on sdc. However, it then asks whether to install it in the mbr. To which drive does this refer? Is it asking if I want to install GRUB in the mbr of the first drive, sda, or is it asking simply whether to install GRUB the mbr on whatever drive I next install GRUB? Haines ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] ascii 2.0 installation confused by mount points
On Sun, Jun 10, 2018 at 04:07:17PM +0100, Rowland Penny wrote: > What you are talking about doing is akin to dual-booting, just on > different disks i.e. you will only be able to boot one distro. > > Rowland Yes. In the past I've always had multiple hard drives in one machine, each with an operating system and its own boot menu. This because I've become paranoid over the years and always want the option of which drive on the machine to boot. I suspect, though, that these disks always had at least different versions of the operating system, and what I'm doing now is trying to install ascii 2.0 on a disk in a system that already has a disk with ascii-rc on it. Do you know if I wouldn't have had the problem had I tried to install devuan testing or experimental on sdc with ascii on sda? The suggestion to disconnect the sda drive while I install the same version of the operating system on sdc occurred to me, but I worried about the effect of the resulting change in drive designations. In my case, by disconnecting sda my sdb becomes sda and my sdc becomes sdb. Will all of this sort itself out when I reconnect the old sda drive and boot it? After installing ascii on sdc I probably will have to select sda as the drive to boot in BIOS and then run update-grub after it is up. Haines ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[DNG] elogind and startx
I installed ascii 2.0.0 without desktop. Usually I have installed the packages associated with the xserver: xserver-xorg-video-dummy, xserver-xorg-input-void, xserver-xorg-core, xinit and x11-xserver-utils. But in ascii release notes it says, "In Devuan 2.0 ASCII it is sufficient to install 'elogind' and 'libpam-elogind', and then use either 'startx' or 'xinit' as usual from a regular user account." Is this implying that I do not need to install the xserver files listed above? Or must they be installed, and the elogind simply relocates the X server log? Haines Brown ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] elogind and startx
On Fri, Jun 15, 2018 at 07:41:52PM +0100, Dave Turner wrote: > You must install the xserver files to get X working. > > More precisely, they MUST be installed. Whether elogind and libpam-elogind > drag them in as dependencies I do not know. I did as you suggest, but with an unhappy outcome. I installed these packages on a raw ascii 2.0.0 system: aptitude xserver-xorg-video-dummy, xserver-xorg-input-void, xserver-xorg-core xinit, x11-xserver-utils xfonts-100dpi, xfonts-75dpi, xfonts-scalable fluxbox, xfonts-terminus, feh Result is that when xserver is run by user, it brings up a frozen fluxbox window manager. No keyboard or mouse input. My keyboard is dead. So had to do a hot shutdown. After rebooting I take a look at ~/.local/share/xorg/Xorg.0.log and find ... mouseset 0: Damage tracking initialized config udev; adding input device device Power Button (/dev/input/event5) No input driver specified, ignoring this device This device may have been added with another device file. This stanza is repeated for many devices such as device Video Bus, Power Button, device Sleep Button, device logitek USB Receiver, and many others. The last is device BRLTTY Linux 5.4 Screen Driver Keyboard I find udev and eudev to be both installed, but apparently udev is being used. Haines ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] elogind and startx
On Sat, Jun 16, 2018 at 11:27:31AM +0200, Martin Steigerwald wrote: > Install > > xserver-xorg-input-libinput > > and a graphics driver, unless you like to use the in-built modesettings > driver which is usually just about fine for Intel integrated graphics. > For AMD or NVidia you may like or need to use something different tough. Martin, that did the trick. Thanks! I used to rely on xorg, but somewhere got the impression that it had been deprecated and I should instead install the individual xserver packages instead. In carrying this out I managed to omit the xserver-xorg-input-libinput package. Apparently xorg package remains fine to use. Haines ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[DNG] what happened to usbmount?
I go to install usbmount on ascii 2.0.0 and I get "E: Unable to locate package usbmount". Has an alternative been developed without the problems associated with usbmount? Haines Brown ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] what happened to usbmount?
On Sun, Jun 17, 2018 at 05:39:02AM +0200, Arnt Karlsen wrote: > On Sat, 16 Jun 2018 18:29:27 -0400, Haines wrote in message > <20180616222927.gk1...@engels.historicalmaterialism.info>: > > > I go to install usbmount on ascii 2.0.0 and I get "E: Unable to locate > > package usbmount". > > ..you have 'dpkg -l |grep usbmount ' and 'apt-cache search usbmount' > turn out nothing? On my jessie machine, dpkg -l grep usbmount returns: ii usbmount 0.0.22 all automatically mount and unmount USB mass ... On my ascii 2.0.0. nothing is returned. On my jessie machine $ aptitude show usbmount returns: Package: usbmount New: yes State: installed Automatically installed: no Version: 0.0.22 ... On my ascii machine apt-cache search usbmount returns nothing. $ aptitude show usbmount returns: E: Unable to locate package usbmount > ..https://wiki.debian.org/usbmount and > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=774149 says Debian > ditched it, https://github.com/rbrito/usbmount says we can pick it up. Am I wrong, but does the restored usbmount depend on systemd? If so that may be why it does not show up on my ascii system. > > Has an alternative been developed without the problems associated with > > usbmount? > > ..pmount, xmount, mountpy, or maybe a lucky combination that > tricked me into my mistaken belief I had usbmount installed. Pmount usefully allows users to mount/umount a device, but it is not an auto-mount. But it us useful enough that I can live without auto-mounting. xmount seems a tool to switch between hard disk images, not to automount. mountpy seems like # mount -a, and so is not an automounter that might mount a usb key on insertion, but a shortcut for mounting multiple devices in fstab. A long time ago I used ivman but stopped for some reason. It seems to have disappeared because it depended on HAL. Today I gather an auto-mounter should instead use udisks. autofs is an automounter that relies on udev rather than HAL, Its multitude of configuration files seemed a challenge to set up, and I did not pursue because I was too pressed with other duties to dedicate the time needed to get on top of all the complication. But I guess it is an automounter that can automount USB keys. udisks-glue is another automount daemon that glues udisk events to user actions. At this point it is apparently limited to mounting and unmounting events. It mounts with udisk and uses policykit to allow user to do it. You need an init script to have it started upon boot. I have not tried it. I'm profoundly ignorant, but these two seem the only automount utilities accessible to ascii. Haines > > -- > ..med vennlig hilsen = with Kind Regards from Arnt Karlsen > ...with a number of polar bear hunters in his ancestry... > Scenarios always come in sets of three: > best case, worst case, and just in case. > ___ > Dng mailing list > Dng@lists.dyne.org > https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] what happened to usbmount?
On Sun, Jun 17, 2018 at 03:25:34PM +0200, J. Fahrner wrote: > Am 2018-06-17 15:14, schrieb Haines Brown: > >Am I wrong, but does the restored usbmount depend on systemd? If so that > >may be why it does not show up on my ascii system. > > It's not in Ascii because it's not in Debian Stretch: > https://packages.debian.org/search?keywords=usbmount > > Jochen Curious. I wonder how to reconcile that with the following: $ cat /etc/devuan_version jessie $ aptitude show usbmount Package: usbmount New: yes State: installed Automatically installed: no Version: 0.0.22 ... Depends: lockfile-progs, udev, util-linux (> 2.16) Haines ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[DNG] systemd and wlan0 interface problem
I've long struggled with a problem with a new installation of ascii. I
can get an ethernet connection, but with a usb WiFi dongle using an
Atheros chip, my wlan0 interface gets automatically changed to wl, and so cannot communicate with DHCP.
This can tie into a bug in Network Manager, but I use wicd.
I get the impression that with systemd, udev automatically assigns
predictable stable interface names, I suppose so that you can have
multiple cards or USB devices for WiFi. I am using Wireless N USB
Adapter (TPE-N150USB) dongle from ThinkPenguin.
The suggestions to deal with this is to change the udev rule for
defining the WiFi interface name. There are three methods suggested:
a) append the line "net.ifnames=0" to /etc/default/grub. I did this and
rebooted to no effect.
b) manually create your own naming scheme to name interfaces wlan0 and
place it before the default policy file. For example, name the file
/etc/udev/rules.d/70-my-net-names.rule. I did not attempt this because
I'm in over my head when it comes to defining udev rules.
c) alter the default policy for picking a different naming
scheme by copying /lib/udev/rules.d/80-net-link-setup.rules to
/etc/udev/rules.d/ and then edit it appropriately.
In my devuan jessie machine, there is such a file and it has
two lines. One is:
# PCI device 0x1814:0x0601 (rt2800pci) \
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", \
ATTR{address}=="68:1c:a2:04:21:74", ATTR{dev_id}=="0x0", \
ATTR{type}=="1", KERNEL=="wlan*", NAME="wlan0"
There is another line # PCI device 0x8086:0x153b (e1000e) \
SUBSYSTEM=="net", ...
However, on my new ascii machine, the directory /etc/udev/rules.d/ is
empty. Can I simply copy the 70-persistent-net.rules file from my old
Devuan jessie machine to the new ascii machine and uncomment the two
lines?
Haines Brown
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] systemd and wlan0 interface problem
On Sun, Jul 01, 2018 at 11:30:46AM +0200, Stefan Krusche wrote:
> Am Samstag 30 Juni 2018 schrieb Haines Brown:
> > c) alter the default policy for picking a different naming
> > scheme by copying /lib/udev/rules.d/80-net-link-setup.rules to
> > /etc/udev/rules.d/ and then edit it appropriately.
> >
> > In my devuan jessie machine, there is such a file and it has
> > two lines. One is:
> >
> > # PCI device 0x1814:0x0601 (rt2800pci) \
> > SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", \
> > ATTR{address}=="68:1c:a2:04:21:74", ATTR{dev_id}=="0x0", \
> > ATTR{type}=="1", KERNEL=="wlan*", NAME="wlan0"
> >
> > There is another line # PCI device 0x8086:0x153b (e1000e) \
> > SUBSYSTEM=="net", ...
> >
> > However, on my new ascii machine, the directory /etc/udev/rules.d/ is
> > empty. Can I simply copy the 70-persistent-net.rules file from my old
> > Devuan jessie machine to the new ascii machine and uncomment the two
> > lines?
>
> Hello Haines,
>
> I have two network interfaces, one integrated and one additional networkcard,
> which of the names got switched by udev. I applied exactly the solution which
> you describe with placed these udev rules, so, I believe, the configuration
> from your jessie system will work. Just make sure that the MAC address
> matches
> on the new system. My lines:
>
> # PCI device 0x10ec:0x8139 (8139too)
> SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", \
> ATTR{address}=="00:ac:bd:ce:df:xz", ATTR{dev_id}=="0x0", ATTR{type}=="1", \
> KERNEL=="eth*", NAME="net0"
>
> # PCI device 0x10ec:0x8168 (r8169)
> SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", \
> ATTR{address}=="01:ac:bd:ce:df:xz", ATTR{dev_id}=="0x0", ATTR{type}=="1", \
> KERNEL=="eth*", NAME="lan0"
>
> Regards,
> Stefan
Stefan, sorry to be dense. I tried to copy the 70-persistent-net-rules
file from jessie /etc/udev/rules.d/ to the empty ascii
/etc/udev/rules.d/ directory. I changed the mac address to that of the
jessie wireless dongle (the value of ether that shows up with #
ifconfig).
Still No DHCPOFFERS.
I've assumed that the 70-persistent-net-rules file in /etc/udev/rules.d)
overwrites /lib/udev/rules.d/75-persistent-net-rules file.
Does not a /etc/udev/rules.d/70-persistent-net-rules file with the
following content not force udev to assign wlan0 to the interface rather
than use wlx?
# PCI device 0x1814:0x0601 (rt2800pci)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="wlan*", \
NAME="wlan0"
If on the other hand I change the interface file on the ascii machine to
use the wireless dongle's mac address, such as wlx2123ff1a1794, by making
the first two lines of the interface read:
auto wlx2123ff1a1794
iface wlx2123ff1a1794 inet dhcp
...
wpa_supplicant fails to bring up wlx2123ff1a1794.
Haines
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
