Re: [DNG] WARNING: lvm2 > 2.02.173-1 breaks some systems and make them unbootable
Am Mittwoch, 8. November 2017 schrieb Steve Litt: > On Tue, 7 Nov 2017 21:30:02 +0100 > marc wrote: > > > Hello > > Hi Marc, > > === > Quote from John Hughes > > > I come from a Unix background -- separate /usr was deprecated in > > > the 1990's with SVR4.2, I'm kind of amazed it took Linux so long to > > > catch up. > === > > > Clearly I must have been working in a parallel universe - the > > commercial unix systems that I remember from the 90s did have > > /usr and / (some also had /opt and /usr/local in various forms) > > And what I can add as that when I was a Linux newbie around the turn of > the century, my much more experienced LUGmates were recommending a > separate /usr, separate /boot, and in fact a tiny, tiny / with all > major directories mounted. > *BSD has a seperate /usr now and I do not think it's going to vanish anytime soon. And when doing things in embedded world, it's handy, too :-) Nik -- Please do not email me anything that you are not comfortable also sharing with the NSA, CIA ... ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Problem with xorg on 6th gen Intel cpus
On Sat, Oct 15, 2016, jack wrote: I have been stumped by a problem with Devuan 1-beta running on 6th generation Intel processors [i5-6200u, celeron n3050]. You can try a linux kernel from backports. Jochen ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] WARNING: lvm2 > 2.02.173-1 breaks some systems and make them unbootable
Quoting John Hughes (j...@atlantech.com): > Wave Without a Shore by C.J. Cherryh Review by Randy Byers: http://randy-byers.livejournal.com/600709.html (This Cherryh short novel is most often found, these days, in omnibus volume _Alternate Realities_, with two other short novels.) Your implication that people using killfiles are risking solipsism or insularity is pretty obviously incorrect. Nobody has time and patience for everything and everyone -- and thus, as a listadmin for many LUGs, I have become a huge proponent of people employing either killfiles or scoring systems (an alternative design supported by, e.g., Emacs GNUS) to focus their attention on topics and contributors they find interesting, and to downgrade or discard topics and contributors they find annoying and/or wastes of time. Encouraging each participant to do _this_ is, among other advantages, a major aid to civility, and facilitates letting each contributor enjoy the experience he/she wants, without the need to impose top-down, centralised content control just to fix interpersonal problems. Or, as we say at Silicon Valley Linux User Group: SVLUG's listadmins normally intervene only to ensure lists' technical operation, to halt spam (incontrovertible spam, not postings someone merely dislikes), and to halt major eruptions of offtopic spew. Enforcement if any should always be minimal and public. (We don't do backroom politics, and our preferred means of social control is to help everyone apply his/her own well-tuned killfile.) http://www.svlug.org/policies/list-policy.php ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] WARNING: lvm2 > 2.02.173-1 breaks some systems and make them unbootable
On 08/11/17 03:33, Steve Litt wrote: 1) If a tree falls in the woods but there's nobody to hear it, did it make a sound? Recommended reading for Steve Litt and others who use a kill-file (not that he'll see this): Wave Without a Shore by C.J. Cherryh ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] WARNING: lvm2 > 2.02.173-1 breaks some systems and make them unbootable
Quoting Adam Borowski (kilob...@angband.pl): > Systemd is bad, but dropping the pretense that following the needs of _one_ > particular stone-age PDP install is sound design is not bad. It would be illogical to assert that the only conceivable justification for separate /usr was Thompson & Richie's 1971 need to spread a UNIX system across a pair of 1.5MB KR05 disk packs. I hope you're not asserting that? I would hope and expect that, 46 years further on, people would be implementing that split to further their 2017 needs, not Thompson & Richie's 1971 ones. > Of course, as always our dear Lennart does it wrong (it'd be much better to > follow Hurd instead and use /bin /sbin /lib), but it doesn't make split /usr > without an initrd any better. Watch the goalposts, folks: There's about to be moved. A moment ago, Adam was asserting that a /usr split no longer makes sense. He's about to switch arguments on the fly, asserting instead that it doesn't make sense as a _distro policy goal_. Observe the switcheroo: > Today, any system where you can realistically install a general-purpose > distribution has multiple GB of disk space. There's no gain to put / and > /usr on separate filesystem The second sentence doesn't really make sense, and is demonstrably untrue in isolation (as I will illustrate below). However, I'll bet if I challenged it, Adam would fall back on the first sentence, and frame the discussion as about 'install[ing] a general purpose distribution'. Et voila, goalpost relocation! Distributions are often obliged to make one size fit all, one policy not suck overmuch for all installing users. I, on the other hand, am not. I want my system's primary /bin and /sbin contents (specifically, the utilities for fsck, partitioning, backup, restore, mkfs, and similar) to be functional even if /usr for some reason cannot be mounted, or cannot be relied upon, at bootup. Where some of those utilites have been IMO erroneously compiled to have dynamic dependencies on /usr by distro packages, I create local $FOO-static packages to replace them. A normally quiescent / partition (given that, on my servers, I mount /usr, /var, and /home from other filesystems) is highly unlikely to be exposed to filesystem damage, and there is significant value in knowing that it will be usable by the superuser to repair, remake, backup, and restore the other filesystems. And yes, if that were not possible for some reason, I could doubtless PXE boot a maintenance ISO and use that instead -- but it's nonetheless worth some small amount of care and work to me to ensure that / can be used that way under pretty much all circumstances, and I consider that a normal expectation for a Unix system that I see no reason to cease expecting. And I expect my server systems to be able to boot with simple boot chains that includes kernels locally compiled by me appropriately to my system's specific hardware and needs, eliminating the need for an initramfs -- because I prefer that architectural simplicity. Objections that my approach doesn't scale to general-purpose distribution installers are unresponsive to my point. What I state is that I have what I consider a rational use-case for separate /usr without an initramfs for my server systems, and it's irrelevant to my point whether Devuan or any other distribution decides to facilitate creation of that specific configuration out of the box. I didn't _say_ this is something distro installers should do. All I said is that people claiming 'there's no gain' to such a configuration are grossly mistaken. (To reiterate what I said before: I am in no way addressing matters of policy of this or any other distribution.) > I don't get why you'd want to keep moving things around on the real > system if you can isolate it into initrd. OK, I believe you, Adam. You don't. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[DNG] Why not initrd: was lvm2 > 2.02.173-1 breaks some systems and make them unbootable
On Wed, 8 Nov 2017 06:20:40 +0100 Adam Borowski wrote: > I don't get why you'd want to keep moving things around on the real > system if you can isolate it into initrd. Because putting it into initramfs not only isolates it, but in fact hides it in a black box. You can't just pop up in your initramfs and tweak things: You need to tweak, recompile and rerun. Very slow process. But wait: It's worse. Although it's currently hip to say "The only thing we put in initramfs are the things needed to mount the root partition", this isn't really true, is it. Those initramfs systems are now so complex you need a product like dracut or initramfs-tools to create it. Have you ever used shorewall to create an iptables firewall? You end up with a monstrosity, just trying to do a simple firewall. Same with these initramfs builders: You end up with something taking several hours to fully understand, when all you really needed to do, in the simple case, is load the ext4 driver, mount the root partition, and run an rc file on the root partition to get everything else mounted. And now I hear talk of it being an excellent idea to run systemd inside the initramfs.[1] What could POSSIBLY go wrong? Besides all that: Your sentence starts with "I don't get why you'd want to". Well, I do. I don't see why anyone would want to use KDE, but that doesn't mean I suggest removing it from Devuan unless it becomes a human shield for systemd. If you don't speak up when they remove the use cases of others, one day *your* use case will be dispensed with. [1]https://www.freedesktop.org/wiki/Software/systemd/InitrdInterface/ SteveT Steve Litt October 2017 featured book: Rapid Learning for the 21st Century http://www.troubleshooters.com/rl21 ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] WARNING: lvm2 > 2.02.173-1 breaks some systems and make them unbootable
On Tue, Nov 07, 2017 at 09:33:30PM -0500, Steve Litt wrote: > John Hughes' sole function on DNG is to say, in many different ways, > "systemd isn't so bad." Given that systemd being bad is the > foundational belief that created the Devuan project thus the DNG list, > he knows he's just making trouble. He's a troll. Don't feed the troll. Systemd is bad, but dropping the pretense that following the needs of _one_ particular stone-age PDP install is sound design is not bad. Of course, as always our dear Lennart does it wrong (it'd be much better to follow Hurd instead and use /bin /sbin /lib), but it doesn't make split /usr without an initrd any better. Today, any system where you can realistically install a general-purpose distribution has multiple GB of disk space. There's no gain to put / and /usr on separate filesystem, all that you need is /boot (or an EFI partition). In the last case I'm aware of where someone tried a stock system with a split, Maemo, the /usr split was deemed inadequate and they instead decided to move most stuff to /opt while stuffing the usual places with symlinks -- adapting packages enough to have / capable of booting would require too much work. There's too many obscure use cases, and too much complexity to bother using the old way. There are two cases: * a regular simple system. No fanciness like split /usr, encrypted LVM on RAID6+0+1 over iSCSI over wifi. No initrd needed. * complex. Just plop anything you need into the initrd. I don't get why you'd want to keep moving things around on the real system if you can isolate it into initrd. Meow! -- ⢀⣴⠾⠻⢶⣦⠀ Laws we want back: Poland, Dz.U. 1921 nr.30 poz.177 (also Dz.U. ⣾⠁⢰⠒⠀⣿⡁ 1920 nr.11 poz.61): Art.2: An official, guilty of accepting a gift ⢿⡄⠘⠷⠚⠋⠀ or another material benefit, or a promise thereof, [in matters ⠈⠳⣄ relevant to duties], shall be punished by death by shooting. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] WARNING: lvm2 > 2.02.173-1 breaks some systems and make them unbootable
On Tue, 7 Nov 2017 21:30:02 +0100 marc wrote: > Hello Hi Marc, === Quote from John Hughes > > I come from a Unix background -- separate /usr was deprecated in > > the 1990's with SVR4.2, I'm kind of amazed it took Linux so long to > > catch up. === > Clearly I must have been working in a parallel universe - the > commercial unix systems that I remember from the 90s did have > /usr and / (some also had /opt and /usr/local in various forms) And what I can add as that when I was a Linux newbie around the turn of the century, my much more experienced LUGmates were recommending a separate /usr, separate /boot, and in fact a tiny, tiny / with all major directories mounted. > But regardless of this, what you are doing here is called an > "appeal to authority" and so of limited relevance. Pre-cisely. The "Appeal to Authority" (https://en.wikipedia.org/wiki/Argument_from_authority) is one of several informal logical falicies. Hughes claims expertise from his "Unix background", but we have no proof. He's saying "follow my lead, I'm knowledgeable." But wait, there's more: === In another recent post, Hughes said, in relation to the inability to run a mounted /usr without initramfs': > What does this have to do with systemd? === In the preceding, Hughes feigns ignorance, as if he doesn't know that systemd's tenticles go right into initramfs, to the extent systemd SHUTDOWN references initramfs. He pretends non-knowledge of the fact that the same guys tying Gnome and systemd together, FreeDesktop.Org, have been the driving force behind the great /bin, /sbin/, /usr/sbin and /usr/bin merge, and he pretends his thorough 1980's Unix knowledge doesn't include the fact that you need a separate /sbin with at least a static mount and a few other commands in order to mount /usr as part of the boot process. John Hughes' sole function on DNG is to say, in many different ways, "systemd isn't so bad." Given that systemd being bad is the foundational belief that created the Devuan project thus the DNG list, he knows he's just making trouble. He's a troll. Don't feed the troll. I /dev/nulled Hughes years ago, yet still see his words of wisdom. (Note to Rick: Your method gets more appealing by the day, but still has downsides.) Let me ask you a couple questions: 1) If a tree falls in the woods but there's nobody to hear it, did it make a sound? 2) If a troll trolls but everybody's /dev/nulled him, is there really a troll? There have forever been "systemd's not so bad" trolls on DNG, and my recommendation remains the same: When you encounter one, killile and move on. SteveT Steve Litt October 2017 featured book: Rapid Learning for the 21st Century http://www.troubleshooters.com/rl21 ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Problem with xorg on 6th gen Intel cpus
On Tue, 7 Nov 2017 12:08:08 -1000, Joel wrote in message <20171107220808.GA18903@sprite>: > Hi Jack, > > On Sat, Oct 15, 2016, jack wrote: > > I have been stumped by a problem with Devuan 1-beta running on 6th > > generation Intel processors [i5-6200u, celeron n3050]. I am using > > openbox as a window manager/desktop [but same happens with XFCE4], > > starting from a tty with: > > > > startx > > > > which brings up openbox and an lxterminal. All is fine until I > > attempt to exit xorg and return to the tty: the following errors > > are issued and the screen freezes, unresponsive to anything other > > than a power cycle: > > > > xinit: connection to X server lost > > waiting for X server to shut down XIO: fatal error 4 > > (Interrupted system call) on X server ":0" > > after 614 requests (614 known processed) with 0 events > > remaining > > .error setting MTRR (base = 0x..., size=0x..., type=1) > > invalid argument (22) > > (EE) server terminated succesfully (0). Closing log file. > > > > The /var/log/Xorg.0.log file is corrupted. > > > > my .xinitrc is a simple > > > > lxterminal& > > exec openbox > > > > From the error messages, you would think think xorg completed fine, > > but I put "echo" messages in "startx" before and after the "xinit" > > command, and the second does not appear. > > > > I am using Void Linux [4.5.2 kernel] on the 6200u laptop without > > problems, but I also installed Slitaz Linux, which has a 3-series > > kernel. > > > > I would appreciate any help that others here can give. > > I can offer a couple ideas. > > There is a choice of a couple of video drivers for X, > notably, the VESA driver is the most generic. > and may be worth trying out. You can specify that in > /etc/X11/xorg.conf, as detailed here: > > http://kimbriggs.com/computer/x11-xorg-conf-vesa-driver > > Of course you may want to see what video module is loaded. > I see that > > cat /proc/modules > > should work. I'm used to using 'lsmod' for that. > > You can set various video modes at boot time: > > https://unix.stackexchange.com/questions/71231/grub2-and-kernel-vga-parameter > > This could also make a difference. > > hth, > > joel > > > Jack ..in my messy case (Devuan Jessie with (experimental) vdev-0.1.2 and nouveau on a Dell Precision M4400 (G96GLM [Quadro FX 770M] video)), it first tries to load nvidia and fails, dumping me into a vga style console. I "usually" 'modprobe -vr nvidia ;sleep 2 ;modprobe -v \ nouveau' and then restart kdm, if I don't see Console: switching to colour frame buffer device 240x75 and X/kdm @ 1920x1200x32@59.*Hz, I just kill X and do a 'modprobe -vr nouveau ;sleep 2 ;modprobe -v \ nouveau', 2 may be a little short sleep time, but has failed me only once the last 5 years. ..I may be a wee bit old fashion, I "usually" ;o) reboot only on kernel upgrades and power grid downtime out-lasting my battery. -- ..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
Re: [DNG] WARNING: lvm2 > 2.02.173-1 breaks some systems and make them unbootable
Quoting John Hughes (j...@atlantech.com): > The separation of / and /usr is a relic of really, really tiny disk sizes. It _originated_ in everything not fitting on one disk on Ken Thompson and Dennis Ritchie's PDP-11, at a point in 1971, originally as a place for user home directories. Rob Landley has a good version of the story: http://lists.busybox.net/pipermail/busybox/2010-December/074114.html However, there are other compelling use-cases for it. (The freedesktop.org kiddies claiming those use-cases don't exist or shouldn't matter doesn't signify.) As to 'just use an initramfs for that', I'd personally prefer my servers not have them, towards the goal of simplifying system architecture. (Above is not an argument of any sort about distro policy. Distros are welcome to set policies according to their criteria. I will then ignore and override those policies to run my systems as I prefer.) ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Problem with xorg on 6th gen Intel cpus
Hi Jack, On Sat, Oct 15, 2016, jack wrote: > I have been stumped by a problem with Devuan 1-beta running on 6th > generation Intel processors [i5-6200u, celeron n3050]. I am using openbox > as a window manager/desktop [but same happens with XFCE4], starting from a > tty with: > > startx > > which brings up openbox and an lxterminal. All is fine until I attempt to > exit xorg and return to the tty: the following errors are issued and the > screen freezes, unresponsive to anything other than a power cycle: > > xinit: connection to X server lost > waiting for X server to shut down XIO: fatal error 4 > (Interrupted system call) on X server ":0" > after 614 requests (614 known processed) with 0 events > remaining > .error setting MTRR (base = 0x..., size=0x..., type=1) > invalid argument (22) > (EE) server terminated succesfully (0). Closing log file. > > The /var/log/Xorg.0.log file is corrupted. > > my .xinitrc is a simple > > lxterminal& > exec openbox > > From the error messages, you would think think xorg completed fine, but I > put "echo" messages in "startx" before and after the "xinit" command, and > the second does not appear. > > I am using Void Linux [4.5.2 kernel] on the 6200u laptop without problems, > but I also installed Slitaz Linux, which has a 3-series kernel. > > I would appreciate any help that others here can give. I can offer a couple ideas. There is a choice of a couple of video drivers for X, notably, the VESA driver is the most generic. and may be worth trying out. You can specify that in /etc/X11/xorg.conf, as detailed here: http://kimbriggs.com/computer/x11-xorg-conf-vesa-driver Of course you may want to see what video module is loaded. I see that cat /proc/modules should work. I'm used to using 'lsmod' for that. You can set various video modes at boot time: https://unix.stackexchange.com/questions/71231/grub2-and-kernel-vga-parameter This could also make a difference. hth, joel > Jack > ___ > Dng mailing list > Dng@lists.dyne.org > https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng -- Joel Roth ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Bluetooth headset on Devuan?
On Tue, Nov 07, 2017 at 09:09:27AM -0600, dev wrote: > > > On 11/06/2017 11:04 AM, Mike Schmitz wrote: > > > > I haven't had any problem with this. Well some choppiness when the > > computer/network is overworked doing something else... > > I'm wondering if it's due to buffer underruns. Are these buffer sizes > the same as yours:? > > ../../../src/asound/bluealsa-pcm.c:295: FIFO buffer size: 4096 > ../../../src/asound/bluealsa-pcm.c:301: Selected HW buffer: 6 periods x > 16000 bytes <= 96004 bytes ../../../src/asound/bluealsa-pcm.c:295: FIFO buffer size: 4096 ../../../src/asound/bluealsa-pcm.c:301: Selected HW buffer: 20 periods x 1920 bytes == 38400 bytes signature.asc Description: Digital signature ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] WARNING: lvm2 > 2.02.173-1 breaks some systems and make them unbootable
Hello > I come from a Unix background -- separate /usr was deprecated in the 1990's > with SVR4.2, I'm kind of amazed it took Linux so long to catch up. Clearly I must have been working in a parallel universe - the commercial unix systems that I remember from the 90s did have /usr and / (some also had /opt and /usr/local in various forms) But regardless of this, what you are doing here is called an "appeal to authority" and so of limited relevance. Having a small safe userland to boot up the full system allows one to recover from a number of mishaps and permits complex startup routines. In the past this was separated out with / and /usr, now most of the startup logic lives in an opaque mess called initrd/initramfs which every distribution hacks up in its own so special way. I don't regard this as progress. A wiser decision would have been to merge the initramfs with /, so that / could optionally live in RAM and linuxrc can be normal init right off the bat - that would allow one to eliminate the complicated and brittle mess that we know as mkinitrd. Yes, /etc would need to be made persistent somehow. That would still be simpler than the current mkinitrd. If done smartly it would even allow one to have a "safe" /etc version permitting rollbacks from config finger trouble. regards marc ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Advice?
On Tue, Nov 07, 2017 at 11:32:14AM -0600, R. W. Rodolico wrote: > Thank you. > > I performed the update yesterday and, with only a few minor changes, was > able to get the client's server back. This was, without a doubt, the > easiest dist-upgrade I have done in around 20 years of running Debian > systems. > Hi Rod, thanks a lot for the report. It's very useful. It would be easy to say "yeah, we knew it would work", but it's better to hear it from you ;) Welcome to your new family HND KatolaZ -- [ ~.,_ Enzo Nicosia aka KatolaZ - Devuan -- Freaknet Medialab ] [ "+. katolaz [at] freaknet.org --- katolaz [at] yahoo.it ] [ @) http://kalos.mine.nu --- Devuan GNU + Linux User ] [ @@) http://maths.qmul.ac.uk/~vnicosia -- GPG: 0B5F062F ] [ (@@@) Twitter: @KatolaZ - skype: katolaz -- github: KatolaZ ] signature.asc Description: Digital signature ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] WARNING: lvm2 > 2.02.173-1 breaks some systems and make them unbootable
On Tue, Nov 07, 2017 at 05:14:21PM +0100, Klaus Ethgen wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA512 > > #157 > > Regards >Klaus Good things happen to those who can wait ;) HND KatolaZ -- [ ~.,_ Enzo Nicosia aka KatolaZ - Devuan -- Freaknet Medialab ] [ "+. katolaz [at] freaknet.org --- katolaz [at] yahoo.it ] [ @) http://kalos.mine.nu --- Devuan GNU + Linux User ] [ @@) http://maths.qmul.ac.uk/~vnicosia -- GPG: 0B5F062F ] [ (@@@) Twitter: @KatolaZ - skype: katolaz -- github: KatolaZ ] signature.asc Description: Digital signature ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] WARNING: lvm2 > 2.02.173-1 breaks some systems and make them unbootable
On 11/07/2017 10:50 AM, John Hughes wrote: > Neither /home not /var are on /, for obvious reasons. / is for > mostly-static things that are owned by the OS or the admin. Ah, I misunderstood. Apologies for the static. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Advice?
Thank you. I performed the update yesterday and, with only a few minor changes, was able to get the client's server back. This was, without a doubt, the easiest dist-upgrade I have done in around 20 years of running Debian systems. Ran into a few minor issues, which I'll record here in case anyone has do do something similar. First, qemu-system-x86 is not installed as a dependency on xen-linux-system. Seems reasonable, since some people want a paravirt only setup and this appears to only affect hvm's (if I understand qemu's part in all this). Second, my configs were very old; I think I've used the same configs since lenny, or maybe earlier? So, I had to actually break down and RTFM and clean all the old cruft out of my config's. It appears 4.4 is a little more strict. Following is the procedure I used, based on See https://git.devuan.org/dev1fanboy/Upgrade-Install-Devuan/wikis/Upgrade-to-Devuan apt-get update && apt-get upgrade Change /etc/apt/source.list deb http://auto.mirror.devuan.org/merged jessie main deb http://auto.mirror.devuan.org/merged jessie-updates main deb http://auto.mirror.devuan.org/merged jessie-security main apt-get update && apt-get install devuan-keyring -y --allow-unauthenticated apt-get update -y apt-get dist-upgrade reboot apt-get install qemu-system-x86 Now, clean up the configs for each domu, and it all works well. I'll write this up and put it someplace for anyone else who ends up doing this. Again, thank you very much. I did not build the domu as you recommended since I already had a broken system that I would need to rebuild from scratch if this didn't work, and I already had backups of everything Rod On 11/06/2017 02:29 PM, Hector Gonzalez wrote: > > On 11/05/2017 09:49 PM, rodolico wrote: >> I've been watching devuan for a while, and like what I see. I had >> planned a migration of our servers from Debian to a combination of >> devuan and freebsd in the future, and have been leaving everything as >> LTS wheezy for now. >> >> Now, our plans have to be accelerated due to a recent problem with >> wheezy and Xen. >> >> My questions are: >> >> 1. is >> https://git.devuan.org/dev1fanboy/Upgrade-Install-Devuan/wikis/Upgrade-to-Devuan >> >> still the way to go? > I haven't had a problem with it, but you should try this with a virtual > server first. You can use a virtualbox machine as a Xen Dom0, and test > your process there (yes, I've done that). > >> 2. Has anyone tested Xen (as a DOM0) with devuan, or will we be doing >> this first. > > Yes, It works fine, I have several Xen Dom0 running in production, the > oldest one has been running devuan for over a year now, it has 20 DomU's > now. > >> Any suggestions/recommendations would be greatly appreciated. > Make backups, test your backups, and don't overwrite your backups with > new versions, and try out your process with virtual machines first. >> >> Rod > -- Rod Rodolico Daily Data, Inc. POB 140465 Dallas TX 75214-0465 214.827.2170 http://www.dailydata.net <>___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] WARNING: lvm2 > 2.02.173-1 breaks some systems and make them unbootable
On 07/11/17 17:50, John Hughes wrote: The separation of / and /usr is a relic of really, really tiny disk sizes. (The first machine I used had 8 megacharacter disks -- not megabyte, megacharacter. Six bit characters. Ok, it didn't run Unix. :-)). ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] WARNING: lvm2 > 2.02.173-1 breaks some systems and make them unbootable
On 07/11/17 17:41, dev wrote: On 11/07/2017 10:29 AM, John Hughes wrote: On 07/11/17 17:13, Klaus Ethgen wrote: [ separate / and /usr ] is the best way to keep your /usr flexible to further lvm grows for example. Personally I have a / on a lvm2 volume. Works OK for me, I see no loss in flexibility. Until a user fills up their home directory with kitten gifs and you can no longer login because syslog has no space to write to /var. Neither /home not /var are on /, for obvious reasons. / is for mostly-static things that are owned by the OS or the admin. The separation of / and /usr is a relic of really, really tiny disk sizes. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] WARNING: lvm2 > 2.02.173-1 breaks some systems and make them unbootable
On 11/07/2017 10:29 AM, John Hughes wrote: > On 07/11/17 17:13, Klaus Ethgen wrote: >> [ separate / and /usr ] is the best way to keep your /usr flexible to >> further lvm grows for example. > > Personally I have a / on a lvm2 volume. Works OK for me, I see no loss > in flexibility. Until a user fills up their home directory with kitten gifs and you can no longer login because syslog has no space to write to /var. The "everything on slash" mentality is a short-sighted partitioning workaround that never should have seen the light of day. Many commercial packages do this as well and those systems give me endless grief when applications running there either fill up /var or dump endless blobs in /tmp. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] WARNING: lvm2 > 2.02.173-1 breaks some systems and make them unbootable
On 07/11/17 17:13, Klaus Ethgen wrote: [ separate / and /usr ] is the best way to keep your /usr flexible to further lvm grows for example. Personally I have a / on a lvm2 volume. Works OK for me, I see no loss in flexibility. Like I say, SVR4.2 deprecated separate /usr in the 1990's. I haven't used a machine without the root filesystem being on a LVM type system (VXVM in fact) since around 1998. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] WARNING: lvm2 > 2.02.173-1 breaks some systems and make them unbootable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 #157 Regards Klaus - -- Klaus Ethgen http://www.ethgen.ch/ pub 4096R/4E20AF1C 2011-05-16Klaus Ethgen Fingerprint: 85D4 CA42 952C 949B 1753 62B3 79D0 B06F 4E20 AF1C -BEGIN PGP SIGNATURE- Comment: Charset: ISO-8859-1 iQGzBAEBCgAdFiEEMWF28vh4/UMJJLQEpnwKsYAZ9qwFAloB290ACgkQpnwKsYAZ 9qy4qgv7Bl/ZLp7QXyJQYt7K5PKTQW84rupI5exwPmQOi2c4FyBLtB0rCQ+ZFjIy O6KW7ZHqvJ2wpRs4jQMj9TppMPS7jbYME3UtWzsATnQSGqtEv2JXWTAwnSDkIq99 9gT0eFoPwh4timUmm4skP9qdXvPh7G5OZ33R5VFlWh64ejiybjw2l1Mp6sMa8xJy J7VW4ZvGlGGrv1UP8rsY3kV2NyIJ1xqHb2Le+t5orDXqN/8r7S7rkWJmMnlixo0O 8Z3QC56r2jzpFyfsVSYpUOH0nDtTqcm1ymUPBOfHkMddjOmmZfv/ntS/YGGxoYjs vyc964xerSNtyAAR+K7mA43rxTfdcWDW6V+bZl3a1R730nfiGcd+3aDMPjiIUEJx 5KoPpk4UwY0s0NAzZM5HyS5ABQkfRlBGpynfKjWUs6gRYTnellD3dJnaP2h16gxf LdS9/EXjCS0pIm86WBIjmT6p3r3wt2fOqckDv8lRLus4U2lrR9MBNYj1QRALcMQ7 3mhnSFgo =f//S -END PGP SIGNATURE- ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] WARNING: lvm2 > 2.02.173-1 breaks some systems and make them unbootable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Am Di den 7. Nov 2017 um 17:07 schrieb John Hughes: > > Well, Debian deprecated a separate /usr as systemd is not working good > > with a separate /usr. > > They actually deprecated it as many things were not working with a separate > /usr. systemd has no more or less problems than anything else that uses > things on /usr. > > I come from a Unix background -- separate /usr was deprecated in the 1990's > with SVR4.2, I'm kind of amazed it took Linux so long to catch up. Well, it was never a problem until they brought systemd into debian. All my systems have separate /usr and just a very small /. That SVR4.2 deprecated that was just the fact that proprietary packages often polite other path under / like /opt or even worse. It is the best way to keep your /usr flexible to further lvm grows for example. > In this particular case it's a bit irritating, it could be fixed by moving > liblz4 to /lib or by not linking the various lvm2 binaries against > libsystemd. Well, yes, the proper solution would be to not ling against libsystemd. Regards Klaus - -- Klaus Ethgen http://www.ethgen.ch/ pub 4096R/4E20AF1C 2011-05-16Klaus Ethgen Fingerprint: 85D4 CA42 952C 949B 1753 62B3 79D0 B06F 4E20 AF1C -BEGIN PGP SIGNATURE- Comment: Charset: ISO-8859-1 iQGzBAEBCgAdFiEEMWF28vh4/UMJJLQEpnwKsYAZ9qwFAloB26gACgkQpnwKsYAZ 9qyCSgwAi2+q0b0OW1PTlUHHGwigFg3kZFisXV2M5v6SCXyF6Eww6zZeYsnzJy8t FmE2WjCyxIECJLWiUBQfAMw5GpxVkHcVrKq2AKZfzdDvUV6rK6NE6CCQi+IqPx3O hi4AvG1LC6YlauHsOwVmB48wdVx+7TQmLu4Mth+E0hIPO+32PTfUhHLZlKoTMm0x MpUSBEr7LKnts2UjZnT0qcPzGtQV3g6w9ioqNsHytRgjgDSDIjZY7rf3A/J/89+Y EIotJuGwHNuEcpwZHm68YYaRO0UasZt2zEhOQozdm2dD0Vyn7wQKZpFIauHteGus RblSyPpdUtdKAfdEyjz8fi7UbvGn91tnWGr5VUmnOStqEwOJqJv9l46wzDZbqdyv b/Umfq54A1HGF6CS3jzF3h5E5mx59dboGLE/vfWGEqkTX4UH7jIYQDE2duedSbES uk4FCXE9AOV/KR1FwblAD6Ndqr1o7OCInSvCeRmgnW7t//MKG/F1X1RkbVZ3FOau vGSqYkbf =j9Jq -END PGP SIGNATURE- ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] WARNING: lvm2 > 2.02.173-1 breaks some systems and make them unbootable
On 07/11/17 16:50, Klaus Ethgen wrote: If you have an seperate /usr (what is not supported by the ignorance of systemd) and that /usr on lvm and a kernel with no initrd (what does not exist in the ignorance of systemd), then you are doomed and your system will not boot anymore. What does this have to do with systemd? Well, Debian deprecated a separate /usr as systemd is not working good with a separate /usr. They actually deprecated it as many things were not working with a separate /usr. systemd has no more or less problems than anything else that uses things on /usr. I come from a Unix background -- separate /usr was deprecated in the 1990's with SVR4.2, I'm kind of amazed it took Linux so long to catch up. In this particular case it's a bit irritating, it could be fixed by moving liblz4 to /lib or by not linking the various lvm2 binaries against libsystemd. Presumably devuan and debian will have differing ideas of how and whether this should be fixed. :-) ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] WARNING: lvm2 > 2.02.173-1 breaks some systems and make them unbootable
Am Di den 7. Nov 2017 um 17:00 schrieb Klaus Ethgen: > > So, could you please also file a bug report in Devuan with a link to > > Debian's bug report? Use bugs.devuan.org for that. > > Done. Hmm... Doesn't seem to work. I sent the attached mail but nothing happened. Regards Klaus -- Klaus Ethgen http://www.ethgen.ch/ pub 4096R/4E20AF1C 2011-05-16Klaus Ethgen Fingerprint: 85D4 CA42 952C 949B 1753 62B3 79D0 B06F 4E20 AF1C --- Begin Message --- -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Package: lvm2 Version: 2.02.175-1 Severity: critical Debian-Bug: #881057 - -- Klaus Ethgen http://www.ethgen.ch/ pub 4096R/4E20AF1C 2011-05-16Klaus Ethgen Fingerprint: 85D4 CA42 952C 949B 1753 62B3 79D0 B06F 4E20 AF1C -BEGIN PGP SIGNATURE- Comment: Charset: ISO-8859-1 iQGzBAEBCgAdFiEEMWF28vh4/UMJJLQEpnwKsYAZ9qwFAloB17cACgkQpnwKsYAZ 9qxZzAwAlFcMHa0sFqAbZ9jpltQv/jGqfqEaVJBJVRg1330QdDslv/AUg1hmU18A razNeKeUKjE7q4chuFT1B9YzRbDOGUKxUpL2jSD2K67TK1NgwPEK2XHZZw/NXv5X azO12eHHtkc4tQ4RVMJN0zQM9fr0fu5VjyfxoEtJHUcLJShqhFqPWebzJj26+eYB a5ruZ0cR2PDtfH6GD2l5Iq1aXaA6hYWbB+2e5j/g4aMkvglyCBnZ8hB7nTd2yxeY kRJSFFLfGz8GzE3gvaPQi61O/9YmNbgDtVzjltjpKx3Gvb88guMwoQQZL3QF7P+I 1uL2F874CUPajIQ2OOxtvrzYdjj6JU3P6lZI/piqG573+xwtG4HOf5LGi3pscs4M H+/O0uZw1/iM/Y27Kbj6YZuSbuJkEBQ44uFj2h4qF9AzG0E23HqWp3rEE/8gQLQM vV/pfKyPUMUOfJD0gkvEBftgl3sJ2KXEetGFvWKj9LoDErQ0xf7A9XmgMOZ7IOX/ H86dcVHX =d2Sf -END PGP SIGNATURE- --- End Message --- signature.asc Description: PGP signature ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] WARNING: lvm2 > 2.02.173-1 breaks some systems and make them unbootable
Am 07/11/2017 um 17:00 schrieb Klaus Ethgen: > The first broken version is 2.02.175-1, or other way, the last working > version is 2.02.173-1. > >> So, could you please also file a bug report in Devuan with a link to >> Debian's bug report? Use bugs.devuan.org for that. > Done. > >> Change log and WHATS_NEW file don't contain mentions of a >> similar-sounding issue. The only thing fixed regarding 2.02.175 is: >> - Fix detection of moved PVs in vgsplit. (2.02.175) >> Which doesn't sound like your problem. >> It wouldn't hurt to try to chroot your way into the system and upgrade >> the package though. > Well, The problem is that I _did_ an upgrade and ended with a unbootable > system. I had to boot with grml and installed version 2.02.173-1 what > fixed the problem. > > ldd do show the dependencies to /usr if you want to check yourself. Thank you! Actually, John's last email explains it all :) I didn't go that far in the troubleshooting right now. That bug report should help make sure we don't land that beyond our unstable regardless of what Debian does with it. -- Evilham ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] WARNING: lvm2 > 2.02.173-1 breaks some systems and make them unbootable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Am Di den 7. Nov 2017 um 16:50 schrieb John Hughes: > So, it seems some things depend on lz4. But nothing mentions it directly. > > But, here's the problem -- lvm2 depends on > /lib/x86_64-linux-gnu/libsystemd.so.0 and *that* depends on liblz4. > > This is sad. True. Especially as that dependency is absolutelly not needed. It is the way they want to bring systemd dependencies into any package. > To allow /usr-less booting either lvm2 should not depend on libsystemd, or > liblz4 should be moved to /lib. Well, nothing should depend on libsystemd. liblz4 is not needed by lvm. Regards Klaus - -- Klaus Ethgen http://www.ethgen.ch/ pub 4096R/4E20AF1C 2011-05-16Klaus Ethgen Fingerprint: 85D4 CA42 952C 949B 1753 62B3 79D0 B06F 4E20 AF1C -BEGIN PGP SIGNATURE- Comment: Charset: ISO-8859-1 iQGzBAEBCgAdFiEEMWF28vh4/UMJJLQEpnwKsYAZ9qwFAloB2WIACgkQpnwKsYAZ 9qyk+gwAuSkjN9X804keuhoyq99jkgkJZeD3ki4fiu1duuV6wa3FsBrGo6bbEFP9 8mKXGkb6yMjfAyylRU+xP646YuDZ4PKMVj8bHEzs2zW02LzUa1K7r7e5A4fOeSJ/ yMnwsB+xJurSKFoWtzzicysV/E8F8+BmDCv3jMnFfjg/w2BN9vpSnJBomp0EOdvL xR8DfvMXBLefmZYZHJ9M0r+ZH1nv5dK5759/3YhUa0QjUJXv2gdohFIe90drCWqY IEnyj/o3KcZWfP+kIdPgz0s+CCX01SdGUJYxsTXcwNlly3IZaBy6mYKfUBmm1ELX 1ExeJDpnuFV4EEJkIpGMNEZZ28Ix9kmkuxJvwMMj6kQNkso6AjlFxOq0gk1n7cK+ +t5WmbzT5eYQoQ+m97CsalSc264wlFzaFJQkVmT5keGA4KVM8mW5XV2SVcTDP0Xw W51WjS3b9S4tHHbhnsDurNBk7gyVoRaLEYXio/PtXYJ2mYb7zYhXbwqGaBbqz3cH OevxqmCo =byNB -END PGP SIGNATURE- ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] WARNING: lvm2 > 2.02.173-1 breaks some systems and make them unbootable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Am Di den 7. Nov 2017 um 16:22 schrieb Evilham: [broken lvm2 in debian] > This is quite serious. > > If you found the issue only appears with 2.02.175-1, Devuan Jessie and > Ascii would be safe, so no need to worry yet. We do have to keep track > of how (and if) it gets fixed in Debian. The first broken version is 2.02.175-1, or other way, the last working version is 2.02.173-1. > So, could you please also file a bug report in Devuan with a link to > Debian's bug report? Use bugs.devuan.org for that. Done. > Change log and WHATS_NEW file don't contain mentions of a > similar-sounding issue. The only thing fixed regarding 2.02.175 is: > - Fix detection of moved PVs in vgsplit. (2.02.175) > Which doesn't sound like your problem. > It wouldn't hurt to try to chroot your way into the system and upgrade > the package though. Well, The problem is that I _did_ an upgrade and ended with a unbootable system. I had to boot with grml and installed version 2.02.173-1 what fixed the problem. ldd do show the dependencies to /usr if you want to check yourself. Gruß Klaus - -- Klaus Ethgen http://www.ethgen.ch/ pub 4096R/4E20AF1C 2011-05-16Klaus Ethgen Fingerprint: 85D4 CA42 952C 949B 1753 62B3 79D0 B06F 4E20 AF1C -BEGIN PGP SIGNATURE- Comment: Charset: ISO-8859-1 iQGzBAEBCgAdFiEEMWF28vh4/UMJJLQEpnwKsYAZ9qwFAloB2LIACgkQpnwKsYAZ 9qxQ9gv+PDN9A7ry3uc23PDrMjUgZ0SkDlYT37KcSBGLdx+NmmWedKaBuqVRVogU +tt9gn9lbkEbs5d9xKHP+LnT5GIwa+vRjtkojh+zA8I8xsyBnAJoZdlcfNGBaqNs 1xfe8pQOPI6pP4vwPWVZcVRS1w0/2Unuos9QsP9A0Krs8nGMUEnx4ZJW1TIQsVLH E+t2p8ixw9UhcHLVNg3rqCtdZms/p/98/y9oGtPSLj+P96kmOY7FLIpuwrnX8zH6 75vfegz7ILq2WhKV/ogtZ97gmEC1uGutD+4Wfr7PzG+2nnJ5Vm01YlNLp5fo3HzP t8jAaPYnKqSgLx0G1MaHjACKCKvMJR6+SPp0LnH3l0IGPybNXHG1jqkhWaP2ywbc NkYGpAxDzuBk0kTtmGosOEWIccauIFll85B2W05qSSrmo6lubtPShoGCVJtheb/7 +TnBnZRFbOIq8W11m4UWPHYqb5BDidnNVZemyhUKNVhJuInvVkcE0N6U2f6XELHB zstCkphs =ei4u -END PGP SIGNATURE- ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] WARNING: lvm2 > 2.02.173-1 breaks some systems and make them unbootable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Am Di den 7. Nov 2017 um 16:21 schrieb John Hughes: > On 07/11/17 15:29, Klaus Ethgen wrote: > > > today I suffered by a heavy bug in lvm2. With version 2.02.175-1 it > > starts to depend on library in /usr. > > Which binary? What library in /usr? /sbin/lvm Lib /usr/lib/x86_64-linux-gnu/liblz4.so.1 > > If you have an seperate /usr (what is not supported by the ignorance of > > systemd) and that /usr on lvm and a kernel with no initrd (what does not > > exist in the ignorance of systemd), then you are doomed and your system > > will not boot anymore. > > What does this have to do with systemd? Well, Debian deprecated a separate /usr as systemd is not working good with a separate /usr. > If your system uses sysvinit instead of systemd does it manage to mount /usr > if /usr is on lvm? How? Well, lvm as all important binaries never depend on any in /usr. So why shouldn't that work? It was a common setup until systemd found the way into debian. Regards Klaus - -- Klaus Ethgen http://www.ethgen.ch/ pub 4096R/4E20AF1C 2011-05-16Klaus Ethgen Fingerprint: 85D4 CA42 952C 949B 1753 62B3 79D0 B06F 4E20 AF1C -BEGIN PGP SIGNATURE- Comment: Charset: ISO-8859-1 iQGzBAEBCgAdFiEEMWF28vh4/UMJJLQEpnwKsYAZ9qwFAloB1k8ACgkQpnwKsYAZ 9qy8AQv/e5BRGf5b6gzwESflesMkZVxS2eu3oDCarbjN+szC/sNN+mQHgEtsdQNt 0+uKYGq0a7lD90rJhjJdJG6MuR7UMtc0t3xFoqBwiXIyyM4brME3gwxWLPUrc6l3 ERY5zrDTirg+Z6dqiFyaMGVg04+C0lmSnTsvUWVxrF5QK6Dh+Vv8opjzvw+Iawlx UqB3lY4v2dvKeFshGJ71XYCkDq/0ed7to73MBrR5kqZDsugSmtekN4XvIFLEWZOK z2kA0V52FhFn9AIkz75J1cRSReg8lvD+BrzjyPu5NyGDkyGG3eKiuDX01V41xTO1 LGQYYwORi278Dt6uW9sAgP/fEJK1yaqJJqzApBBtkSs08OZELIt6/vMKt0bb+w6s LtK0kSVK53lJC85FSnwkKkx67yJmrWInEp15ebzcAziDCCOJDDqqLtE7Z0TM9B+f MbtNKCcYYnAlrdeHwbmgPdj+0ozOMKkglHuVi/Jhou0Q/MhUxksucj3FYI9xz7Hu +X8ocGHq =z6wT -END PGP SIGNATURE- ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] WARNING: lvm2 > 2.02.173-1 breaks some systems and make them unbootable
On 07/11/17 16:21, John Hughes wrote: On 07/11/17 15:29, Klaus Ethgen wrote: today I suffered by a heavy bug in lvm2. With version 2.02.175-1 it starts to depend on library in /usr. Which binary? What library in /usr? So, it seems some things depend on lz4. But nothing mentions it directly. But, here's the problem -- lvm2 depends on /lib/x86_64-linux-gnu/libsystemd.so.0 and *that* depends on liblz4. This is sad. To allow /usr-less booting either lvm2 should not depend on libsystemd, or liblz4 should be moved to /lib. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Expansion of the development team
On Mon, 06 Nov 2017 at 06:35:23 +0300 m712 wrote: > > On November 5, 2017 9:44:29 PM GMT+03:00, goli...@dyne.org wrote: > >The group decided, from the options suggested, that they will be > >collectively referred to as the 'Caretakers'. > They don't really need a group name, in my opinion. That gives me a What'd be wrong with that? :-) -- Alessandro Selli http://alessandro.route-add.net VOIP SIP: dhatarat...@ekiga.net Chiavi PGP/GPG keys: B7FD89FD, 4A904FD9 ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] WARNING: lvm2 > 2.02.173-1 breaks some systems and make them unbootable
Am 07/11/2017 um 16:22 schrieb Evilham: > This is currently the last pushed commit (Release 2.02.178-1): > https://gitlab.com/debian-lvm/lvm2/commit/90bc98f3828032a1ad24daf14e2e2f2f704f1bd6 I meant 2.02.175-1, of course. -- Evilham ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] WARNING: lvm2 > 2.02.173-1 breaks some systems and make them unbootable
Hallo Klaus, Am 07/11/2017 um 15:29 schrieb Klaus Ethgen: > today I suffered by a heavy bug in lvm2. With version 2.02.175-1 it > starts to depend on library in /usr. > > If you have an seperate /usr (what is not supported by the ignorance of > systemd) and that /usr on lvm and a kernel with no initrd (what does not > exist in the ignorance of systemd), then you are doomed and your system > will not boot anymore. > > How is that going in devuan? Will it be repaired? I already filled an > bugreport in debian but I believe it will be closed as wontfix by This is quite serious. If you found the issue only appears with 2.02.175-1, Devuan Jessie and Ascii would be safe, so no need to worry yet. We do have to keep track of how (and if) it gets fixed in Debian. So, could you please also file a bug report in Devuan with a link to Debian's bug report? Use bugs.devuan.org for that. Just mentioning that the current version in Debian Sid is 2.02.176 and I can't find a git repository that includes those changes... This is currently the last pushed commit (Release 2.02.178-1): https://gitlab.com/debian-lvm/lvm2/commit/90bc98f3828032a1ad24daf14e2e2f2f704f1bd6 Change log and WHATS_NEW file don't contain mentions of a similar-sounding issue. The only thing fixed regarding 2.02.175 is: - Fix detection of moved PVs in vgsplit. (2.02.175) Which doesn't sound like your problem. It wouldn't hurt to try to chroot your way into the system and upgrade the package though. -- Evilham signature.asc Description: OpenPGP digital signature ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] WARNING: lvm2 > 2.02.173-1 breaks some systems and make them unbootable
On 07/11/17 15:29, Klaus Ethgen wrote: today I suffered by a heavy bug in lvm2. With version 2.02.175-1 it starts to depend on library in /usr. Which binary? What library in /usr? If you have an seperate /usr (what is not supported by the ignorance of systemd) and that /usr on lvm and a kernel with no initrd (what does not exist in the ignorance of systemd), then you are doomed and your system will not boot anymore. What does this have to do with systemd? If your system uses sysvinit instead of systemd does it manage to mount /usr if /usr is on lvm? How? ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Bluetooth headset on Devuan?
On 11/06/2017 11:04 AM, Mike Schmitz wrote: > I haven't had any problem with this. Well some choppiness when the > computer/network is overworked doing something else... I'm wondering if it's due to buffer underruns. Are these buffer sizes the same as yours:? ../../../src/asound/bluealsa-pcm.c:295: FIFO buffer size: 4096 ../../../src/asound/bluealsa-pcm.c:301: Selected HW buffer: 6 periods x 16000 bytes <= 96004 bytes Thanks ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[DNG] WARNING: lvm2 > 2.02.173-1 breaks some systems and make them unbootable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hello, today I suffered by a heavy bug in lvm2. With version 2.02.175-1 it starts to depend on library in /usr. If you have an seperate /usr (what is not supported by the ignorance of systemd) and that /usr on lvm and a kernel with no initrd (what does not exist in the ignorance of systemd), then you are doomed and your system will not boot anymore. How is that going in devuan? Will it be repaired? I already filled an bugreport in debian but I believe it will be closed as wontfix by Biebl, the systemd priest in debian. Regards Klaus - -- Klaus Ethgen http://www.ethgen.ch/ pub 4096R/4E20AF1C 2011-05-16Klaus Ethgen Fingerprint: 85D4 CA42 952C 949B 1753 62B3 79D0 B06F 4E20 AF1C -BEGIN PGP SIGNATURE- Comment: Charset: ISO-8859-1 iQGzBAEBCgAdFiEEMWF28vh4/UMJJLQEpnwKsYAZ9qwFAloBw1MACgkQpnwKsYAZ 9qyktgv/UT/00niL0wDjdRUqDd1ddzSSbfgrP8t2jm7T9YNtC2n19xZsaZ0tQpFm NKUTrYog0mZHVKVSoqiDwin13LFNX0RwAslIN3bE/gHUiQ+RM/bZGcj0m/iX3Tgn nI7Eqp9cfiNWD8F3YPf1aSQyAmN3g4uxdWSjHRiUaHXif+b+4GBALutRCjIY+7Dx uSd5YyrbSurU44nVLxC+KwIBknxrtbV2EYcV9RnY6h8ICbXDzH+APC17XTxWeb/B DDhTjgdfWSrWawsopd/oK8VUCSUFSKBdvEjwstgmadl6Zmr+Bh84B24g36HUBci6 FqFaXcsebihECKsWPNk9CWQFm+4IljmQY0trQFyk2WCghL2VZFT1wxv35nzFhDIB 4TUHNozdrZabA9JS6Tz36fhT41dYOX68ZYWmoRcv2nguhJ2p72G7nUHYGrUHxYNW VsQdn1ktIfzGeZzZbgHCYdgJJuETIjndu+Nj4gPuQfMMW5fI04pdaI3t2NLcy7mB ObsmxFZ7 =X0xT -END PGP SIGNATURE- ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
