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

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

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

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

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

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

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 > >

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

[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

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

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

[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

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 &

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

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 >

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

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

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. 

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

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

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. >

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

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

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:?

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

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

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

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

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

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

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.  :-)).

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

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

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

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

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