Re: Debian openssh option review: considering splitting out GSS-API key exchange

On Tue, Apr 02, 2024 at 01:30:10AM +0100, Colin Watson wrote: * add dependency-only packages called something like openssh-client-gsskex and openssh-server-gsskex, depending on their non-gsskex alternatives * add NEWS.Debian entry saying that people need to install these packages

Re: Debian openssh option review: considering splitting out GSS-API key exchange

On Tue, Apr 02, 2024 at 01:30:10AM +0100, Colin Watson wrote: * add dependency-only packages called something like openssh-client-gsskex and openssh-server-gsskex, depending on their non-gsskex alternatives * add NEWS.Debian entry saying that people need to install these packages

Bug#628815: coreutils: pinky makes crazy DNS queries

On Tue, Mar 19, 2024 at 03:27:52PM +0100, you wrote: /etc/acpi/lid.sh calls getXuser, that's defined in /usr/share/acpi-support/power-funcs which has on line 36 plist=$(pinky -fw) || pwf_error "pinky lost" I'd suggest a wishlist bug on acpi-support-base to use "who -us" in

Bug#628815: coreutils: pinky makes crazy DNS queries

On Tue, Mar 19, 2024 at 11:54:30AM +0100, you wrote: For example on a debian system with acpi-support, /etc/acpi/lid.sh will make many requests to find the host $WAYLAND_DISPLAY every time the lid is opened. I don't see anything in lid.sh that calls pinky.

Re: shred bug? [was: Unidentified subject!]

On Sun, Feb 11, 2024 at 08:02:12AM +0100, to...@tuxteam.de wrote: What Thomas was trying to do is to get a cheap, fast random number generator. Shred seems to have such. You're better off with /dev/urandom, it's much easier to understand what it's trying to do, vs the rather baroque logic in

Re: cli64 CPU segfaults

On Mon, Jan 29, 2024 at 07:20:14PM +, Adam Weremczuk wrote: I have 2 bare metal Debian 12.4 servers with fairly new Intel CPUs and plenty of memory. On both, dmesg continuously reports: (...) [Mon Jan 29 12:13:00 2024] cli64[1666090]: segfault at 0 ip 0040dd3b sp 7ffc2bfba630

bug#62572: Bug#1058752: bug#62572: cp --no-clobber behavior has changed

On Mon, Jan 29, 2024 at 04:11:05PM +, Pádraig Brady wrote: You've introduced a silent incompatibility and I'm trying to find some way to make that clear. If upstream would provide a better solution I would certainly use it. I have despaired of there being such since your attitude thus far

Bug#1058752: bug#62572: Bug#1058752: bug#62572: cp --no-clobber behavior has changed

On Mon, Jan 29, 2024 at 04:11:05PM +, Pádraig Brady wrote: You've introduced a silent incompatibility and I'm trying to find some way to make that clear. If upstream would provide a better solution I would certainly use it. I have despaired of there being such since your attitude thus far

Bug#1058752: bug#62572: Bug#1058752: bug#62572: cp --no-clobber behavior has changed

On Mon, Jan 29, 2024 at 04:11:05PM +, Pádraig Brady wrote: You've introduced a silent incompatibility and I'm trying to find some way to make that clear. If upstream would provide a better solution I would certainly use it. I have despaired of there being such since your attitude thus far

Bug#1058752: bug#62572: Bug#1058752: bug#62572: cp --no-clobber behavior has changed

On Sun, Jan 28, 2024 at 11:14:14PM -0800, Paul Eggert wrote: I'm not sure reverting would be best. It would introduce more confusion, and would make coreutils incompatible with FreeBSD again. Reverting makes more sense than the current situation. I do not understand why you seem to value

Bug#1058752: bug#62572: Bug#1058752: bug#62572: cp --no-clobber behavior has changed

On Sun, Jan 28, 2024 at 11:14:14PM -0800, Paul Eggert wrote: I'm not sure reverting would be best. It would introduce more confusion, and would make coreutils incompatible with FreeBSD again. Reverting makes more sense than the current situation. I do not understand why you seem to value

bug#62572: Bug#1058752: bug#62572: cp --no-clobber behavior has changed

On Sun, Jan 28, 2024 at 11:14:14PM -0800, Paul Eggert wrote: I'm not sure reverting would be best. It would introduce more confusion, and would make coreutils incompatible with FreeBSD again. Reverting makes more sense than the current situation. I do not understand why you seem to value

Bug#1061612: coreutils: cp -n deprecation warning gives questionable advice

On Sun, Jan 28, 2024 at 12:26:13PM +, Pádraig Brady wrote: That is a very aggressive deprecation. IMHO it would have been better for debian to have -n behave like it did previously and (silently) skip files and not set an error exit status. If it was a mess, this is a mess squared. I guess

Re: Monospace fonts, Re: Changing The PSI Definition

On Fri, Jan 26, 2024 at 01:50:38PM -0600, David Wright wrote: On Fri 26 Jan 2024 at 07:25:13 (-0500), Dan Ritter wrote: Greg Wooledge wrote: > On Thu, Jan 25, 2024 at 07:32:38PM -0500, Thomas George wrote: > > The current PSI works perfectly but I don't like the pale green prompt. > > > > Tried

Bug#1061612: coreutils: cp -n deprecation warning gives questionable advice

On Sat, Jan 27, 2024 at 02:00:14PM +0100, Sven Joachim wrote: Package: coreutils Version: 9.4-3+b1 , | $ cp -n /bin/true tmp | cp: warning: behavior of -n is non-portable and may change in future; use --update=none instead ` The advice to use the --update=none option is highly

Re: standardize uid:gid?

On Thu, Jan 18, 2024 at 07:31:05AM -0500, Greg Wooledge wrote: This is one of those "the boat has already left the dock" situations. If this were going to happen, it would have to have happened in the early 1990s. There is no feasible way to make it happen now. It's also a pointless endeavor,

Re: Seeking a Terminal Emulator on Debian for "Passthrough" Printing

On Sun, Jan 21, 2024 at 10:44:35PM +, phoebus phoebus wrote:   A filter in between that in response to escape-code-1 starts sending data to the serial port instead of the terminal application and switches back to the terminal application on receiving of escape-code-2.   Development of a

Re: SMART Uncorrectable_Error_Cnt rising - should I be worried?

On Thu, Jan 11, 2024 at 03:25:51PM -0500, Stefan Monnier wrote: manufacturers in different memory banks, but since it's always possible to power down, replace or just remove memory, and power up again, Hmm... "always"? What about long running computations like that simulation (or LLM

Re: SOLVED FOR GENE

On Sun, Jan 07, 2024 at 06:37:08AM -0500, Felix Miata wrote: Doing so is called a defensive response, something to be expected in response to (needless) offensive behavior. Browsers have default fonts selectable by users for good reason. Websites shouldn't be assuming user settings are wrong.

Re: disable auto-linking of /bin -> /usr/bin/

On Wed, Jan 10, 2024 at 11:49:02AM -0800, Mike Castle wrote: To some extent, it will make it easier for packaging. No, not at all--new packages have not had to worry about putting things anywhere but /usr for a long time. Only old packages (for which the work you described had been done

Bug#1055694: initramfs-tools: After updating coreutils cp: not replacing in console when running update-initramfs

On Sat, Nov 11, 2023 at 01:32:59AM +0100, Thorsten Glaser wrote: On Fri, 10 Nov 2023, Sven Joachim wrote: | 'cp -n' and 'mv -n' now exit with nonzero status if they skip their | action because the destination exists, and likewise for 'cp -i', Ouch! Nonzero? That’s harsh, and bad as it’s

Bug#1055694: initramfs-tools: After updating coreutils cp: not replacing in console when running update-initramfs

On Sat, Nov 11, 2023 at 01:32:59AM +0100, Thorsten Glaser wrote: On Fri, 10 Nov 2023, Sven Joachim wrote: | 'cp -n' and 'mv -n' now exit with nonzero status if they skip their | action because the destination exists, and likewise for 'cp -i', Ouch! Nonzero? That’s harsh, and bad as it’s

Bug#1058752: bug#62572: cp --no-clobber behavior has changed

On Sun, Dec 17, 2023 at 12:34:11AM -0800, Paul Eggert wrote: On 2023-12-16 13:46, Bernhard Voelker wrote: Whether the implementation is race-prone or not is an internal thing. I wasn't referring to the internal implementation. I was referring to cp users. With the newer Coreutils (FreeBSD)

Bug#1058752: bug#62572: cp --no-clobber behavior has changed

On Sun, Dec 17, 2023 at 12:34:11AM -0800, Paul Eggert wrote: On 2023-12-16 13:46, Bernhard Voelker wrote: Whether the implementation is race-prone or not is an internal thing. I wasn't referring to the internal implementation. I was referring to cp users. With the newer Coreutils (FreeBSD)

bug#62572: cp --no-clobber behavior has changed

On Sun, Dec 17, 2023 at 12:34:11AM -0800, Paul Eggert wrote: On 2023-12-16 13:46, Bernhard Voelker wrote: Whether the implementation is race-prone or not is an internal thing. I wasn't referring to the internal implementation. I was referring to cp users. With the newer Coreutils (FreeBSD)

Bug#1058752: bug#62572: cp --no-clobber behavior has changed

On Fri, Dec 15, 2023 at 11:21:06AM -0800, Paul Eggert wrote: Stlll, Pádraig gave a reasonable summary of why the change was made, despite its incompatibility with previous behavior. (One thing I'd add is that the FreeBSD behavior is inherently less race-prone.) It seemed like a good idea at

Bug#1058752: bug#62572: cp --no-clobber behavior has changed

On Fri, Dec 15, 2023 at 11:21:06AM -0800, Paul Eggert wrote: Stlll, Pádraig gave a reasonable summary of why the change was made, despite its incompatibility with previous behavior. (One thing I'd add is that the FreeBSD behavior is inherently less race-prone.) It seemed like a good idea at

bug#62572: cp --no-clobber behavior has changed

On Fri, Dec 15, 2023 at 11:21:06AM -0800, Paul Eggert wrote: Stlll, Pádraig gave a reasonable summary of why the change was made, despite its incompatibility with previous behavior. (One thing I'd add is that the FreeBSD behavior is inherently less race-prone.) It seemed like a good idea at

Re: differences among amd64 and i386

On Fri, Dec 15, 2023 at 09:36:19AM -0500, Jeffrey Walton wrote: Also see x32, . It takes advantage of amd64 benefits, and tries to reduce the memory pressures. x32 hasn't really gone anywhere and is unlikely to at this point; amd64 is the only reasonable

Bug#1058752: bug#62572: cp --no-clobber behavior has changed

been widely deployed, which makes now the time to fix it. Michael Stone

Bug#1058752: bug#62572: cp --no-clobber behavior has changed

been widely deployed, which makes now the time to fix it. Michael Stone

bug#62572: cp --no-clobber behavior has changed

been widely deployed, which makes now the time to fix it. Michael Stone

Bug#1058752: cp --no-clobber behavior has changed

m reluctant to do so as that will likely lead to divergent behavior between distributions, but breaking scripts without a compelling reason is also not good. I would encourage coreutils to reconsider the change and finding a non-breaking way forward. Michael Stone

Bug#1058752: cp --no-clobber behavior has changed

m reluctant to do so as that will likely lead to divergent behavior between distributions, but breaking scripts without a compelling reason is also not good. I would encourage coreutils to reconsider the change and finding a non-breaking way forward. Michael Stone

bug#62572: cp --no-clobber behavior has changed

m reluctant to do so as that will likely lead to divergent behavior between distributions, but breaking scripts without a compelling reason is also not good. I would encourage coreutils to reconsider the change and finding a non-breaking way forward. Michael Stone

Re: Linking coreutils against OpenSSL

On Sat, Nov 11, 2023 at 11:50:31AM +0100, Andreas Metzler wrote: you seem to have missed/deleted the paragraph where Ansgar suggested how to do this *without* tradeoff. ("explicitly disable/enable build options per arch") No, I didn't. That was in my original email and is one of the

Re: Linking coreutils against OpenSSL

On Fri, Nov 10, 2023 at 03:10:42PM +0100, Ansgar wrote: Please avoid producing different results depending on the build environment. That just results in non-reproducible issues in unclean environments (suddenly different dependencies, different features, ...). I think that is an acceptable

Re: Linking coreutils against OpenSSL

On Fri, Nov 10, 2023 at 10:38:13AM +, Luca Boccassi wrote: Per-architecture dependencies are possible though, so maybe starting to add the libssl dependency only on amd64 is a good starting point, and then users of other architectures can request to be added too if it is beneficial for them.

Re: du enhancement

On Fri, Oct 20, 2023 at 04:47:59PM +0100, Pádraig Brady wrote: Yes coloring is a plausible addition to du, and would make sense to follow the same options, env vars as ls. I'd argue that the use of colors in coreutils shouldn't really expand unless/until there's a more robust & generic

Re: Looking for a good "default" font (small 'L' vs. capital 'i' problem)

On Sat, Aug 19, 2023 at 09:19:48PM +0200, Christoph K. wrote: Could you please recommend a "suitable" sans-serif font that A lot of your criteria are rather subjective. For packaged fonts you might look at "hack" (https://source-foundry.github.io/Hack/font-specimen.html) or "go"

Re: Potential MBF: packages failing to build twice in a row

On Mon, Aug 14, 2023 at 09:40:52PM +0100, Wookey wrote: On 2023-08-14 10:19 -0400, Michael Stone wrote: On Thu, Aug 10, 2023 at 02:38:17PM +0200, Lucas Nussbaum wrote: > On 08/08/23 at 10:26 +0200, Helmut Grohne wrote: > > Are we ready to call for consensus on dropping the re

Re: Potential MBF: packages failing to build twice in a row

On Thu, Aug 10, 2023 at 02:38:17PM +0200, Lucas Nussbaum wrote: On 08/08/23 at 10:26 +0200, Helmut Grohne wrote: Are we ready to call for consensus on dropping the requirement that `debian/rules clean; dpkg-source -b` shall work or is anyone interested in sending lots of patches for this? My

Re: Proposed MBF - removal of pcre3 by Bookworm

On Sat, Jul 01, 2023 at 09:44:27AM -0400, Michael Stone wrote: On Thu, Jun 29, 2023 at 08:55:11PM +0100, Matthew Vernon wrote: Bookworm is now out; I will shortly be increasing the severity of the outstanding bugs to RC, with the intention being to remove src:pcre3 from Debian before

Re: Proposed MBF - removal of pcre3 by Bookworm

On Thu, Jun 29, 2023 at 08:55:11PM +0100, Matthew Vernon wrote: Bookworm is now out; I will shortly be increasing the severity of the outstanding bugs to RC, with the intention being to remove src:pcre3 from Debian before the trixie release. You don't think that marking packages for removal

Re: A hypervisor for a headless server?

On Fri, Jun 02, 2023 at 05:18:38PM +0200, zithro wrote: On 02 Jun 2023 14:31, Michael Stone wrote: I don't recommend xen for new projects. It has more pieces and tends to be more fragile than qemu+kvm, for no real benefits these days. (IMO) Define "more pieces" and "more f

Re: A hypervisor for a headless server?

On Fri, Jun 02, 2023 at 05:34:58PM +0200, Mario Marietto wrote: Excuse me,but there is something within your argumentation that I don't like and I want to express what it is. Let's take Linux as an example of what I want to say. Linux is well known to be an OS that can be installed on the old

Re: A hypervisor for a headless server?

On Fri, Jun 02, 2023 at 03:24:13PM +0200, Mario Marietto wrote: I mean. I cant use qemu on that I5 cpu because is slow without kvm. Kvm does not work on that cpu because it is needs some extensions from the cpu that there arent. Bhyve is the only alternative because it is a mix between qemu and

Re: A hypervisor for a headless server?

On Fri, Jun 02, 2023 at 03:01:04PM +0200, Mario Marietto wrote: Using qemu is out of discussion,because it is very slow. But as I said,bhyve works better than qemu alone. kvm literally uses qemu as its user space, so it's very much not out of the discussion. If you can't use the kvm kernel

Re: A hypervisor for a headless server?

On Fri, Jun 02, 2023 at 08:41:44AM +, Victor Sudakov wrote: Interestingly, libvirt claims to support bhyve, I just never felt a need for such sophisticated tools to run just several VMs. Yes, it sounds like you should just ignore libvirt entirely and just install qemu-system-x86 (and not

Re: A hypervisor for a headless server?

On Fri, Jun 02, 2023 at 11:21:45AM +0200, Mario Marietto wrote: wait wait. for sure the option should be enabled on the bios,but bhyve works in a different way than kvm,so it works even if my cpu does not have all the virt. parameters respected. Infact kvm does not work on that cpu. But how many

Re: A hypervisor for a headless server?

On Fri, Jun 02, 2023 at 11:09:36AM +0200, Paul Leiber wrote: +1 for Xen, AFAIK the standard apt installation doesn't include any management GUI. This is the howto which helped me getting started: https://wiki.xenproject.org/wiki/Xen_Project_Beginners_Guide I don't recommend xen for new

Re: A hypervisor for a headless server?

On Thu, Jun 01, 2023 at 11:53:26PM -0400, Brian Sammon wrote: "virt-manager", on the other hand, appears to be fundamentally a GUI tool. But virsh from libvirt-clients isn't.

Re: update-initramfs

On Thu, Apr 13, 2023 at 01:57:04PM -0500, David Wright wrote: os-prober no longer scours all the other partitions for OSes any more.¹ Which is wonderful--that was one of the most annoying misfeatures to have ever been enabled.

Re: Playing Card Symbols

On Mon, Mar 27, 2023 at 02:13:35PM -0400, Jude DaShiell wrote: You know, if all of those symbols were in some font set and had text labels attached to them that could speak when a screen reader was used a whole bunch of playing card applications would suddenly become accessible for screen reader

Re: Playing Card Symbols

On Mon, Mar 27, 2023 at 02:13:35PM -0400, Jude DaShiell wrote: You know, if all of those symbols were in some font set and had text labels attached to them that could speak when a screen reader was used a whole bunch of playing card applications would suddenly become accessible for screen reader

Re: Which takes priority, ipv4, or ipv6?

On Mon, Mar 27, 2023 at 12:48:13PM +0100, Richmond wrote: I have configured an ipv6 tunnel. If I visit this site: http://ip6.me/ The "normal" test shows my ipv4 address, and the: http://ip6only.me/ shows the ipv6 address. However if I switch my DNS from opendns to the one provided by my ISP

Re: No /

On Wed, Mar 15, 2023 at 05:05:49PM +0100, Michael Lee wrote: Is there a way to fix this, or is a re-installation the only remedy? For all the things people like about btrfs, IME it's not as good at recovery from adverse events as are ext4 or xfs. In your circumstance your best bet is

Re: Partitioning an SSD?

On Thu, Feb 16, 2023 at 02:22:56AM -0500, Felix Miata wrote: What physical boundaries do SSDs have to report? All I know about that are exposed are sector size and sector count. I have yet to find one where logical/physical were not 512B/512B. Don't worry about it; modern partition tools

Re: Partitioning an SSD?

On Wed, Feb 15, 2023 at 11:23:52PM -0500, pa...@quillandmouse.com wrote: Here's why you would partition a drive. Reinstalling (which I end up having to do every time Debian comes out with a new version) means overwriting the storage. I already acknowleged that people can do what they want

Re: ipv6 maybe has arrived.

On Wed, Feb 15, 2023 at 11:49:51AM +0100, to...@tuxteam.de wrote: On Tue, Feb 14, 2023 at 03:07:08PM -0500, Michael Stone wrote: On Fri, Feb 10, 2023 at 02:33:12PM +, Tim Woodall wrote: > On Fri, 10 Feb 2023, jeremy ardley wrote: > > you can ping them as in > > > > pin

Re: Partitioning an SSD?

On Wed, Feb 15, 2023 at 05:58:47PM -0500, PMA wrote: I'm preparing to install Debian 11.5.0 on a new computer. Its drives are SSDs, not the HDDs I've been accustomed to and have always fastidiously *partitioned*. With my file groupings already well differentiated c/o directory-tree layout, is

Re: ipv6 maybe has arrived.

On Wed, Feb 15, 2023 at 04:24:36PM -0500, gene heskett wrote: you basically just made this up No Michael, just recalling our interaction history, the general tone being to give me hell for using hosts files instead of running a dns. I have not told you that you need to use bind instead of

Re: OpenMPI 5.0 to be 32-bit only ?

On Wed, Feb 15, 2023 at 11:29:25AM +, Alastair McKinstry wrote: The counterpoint is if someone does a high-core-count 32-bit arch for HPC; x32 could (have been) such an architecture, but its development looks stalled. That may have been a possibility 15-20 years ago, but today anything

Re: ipv6 maybe has arrived.

On Wed, Feb 15, 2023 at 10:12:32AM -0500, Greg Wooledge wrote: Sorry, Gene's line was actually "search hosts, nameserver". So, "ping coyote" should have triggered name resolution for "coyote.hosts" and/or "coyote.nameserver". It's just barely conceivable that *something* might have created a

Re: ipv6 maybe has arrived.

On Wed, Feb 15, 2023 at 09:30:57AM -0500, gene heskett wrote: True. But I'd also suggest that if you do not want to support /etc/hosts files name resolution methods /etc/hosts works and has worked fine on debian for decades to. Your attitude that everybody with a two machine home network

Re: ipv6 maybe has arrived.

On Wed, Feb 15, 2023 at 03:46:21PM +0300, Reco wrote: libnss-myhostname does that. Why it chooses ipv6 link-local over ipv4 static IP is another question. perhaps because ipv6 is preferred and there is no public ip6. it doesn't really matter because normal users won't notice or care whether

Re: ipv6 maybe has arrived.

On Wed, Feb 15, 2023 at 07:57:09AM -0500, gene heskett wrote: And this disclosed that I had not properly added coyote.coyote.den to the /etc/hosts file on that machine. That mistake, fixed, now makes the local net pingable. The rest of it, whats powered up, was/is all pingable. It just wasn't

Re: ipv6 maybe has arrived.

On Wed, Feb 15, 2023 at 07:30:44AM -0500, Greg Wooledge wrote: That said, I'm curious about this part oF Gene's result: > gene@bpi54:~$ grep -i bpi54 /etc/hosts > 192.168.71.12 bpi54.coyote.denbpi54 > gene@bpi54:~$ getent hosts bpi54 > fe80::4765:bca4:565d:3c6 bpi54

Re: ipv6 maybe has arrived.

On Fri, Feb 10, 2023 at 02:33:12PM +, Tim Woodall wrote: On Fri, 10 Feb 2023, jeremy ardley wrote: you can ping them as in ping fe80::87d:c6ff:fea4:a6fc ooh, I didn't know that worked. Same as ping fe80::87d:c6ff:fea4:a6fc%eth0 on my machines at least. No idea how it picks the

Re: ipv6 maybe has arrived.

On Thu, Feb 09, 2023 at 03:02:22PM -0500, gene heskett wrote: Yes Greg, you keep telling me that. But I'm in the process of bringing up a 3dprinter farm, each printer with a bpi5 to manage octoprint. Joing the other 4 on this net running buster and linuxcnc. Just last week I added another

Re: ipv6 maybe has arrived.

On Tue, Feb 14, 2023 at 07:42:59PM +, Brian wrote: I was attracted by this idea and it gave me pause for thought. Leaving aside printers that include a network interface, the IPP-over-USB standard applies to a non-network-capable printer. The specs require IPP (put in firmware, I suppose)

Re: How can I check (and run) if an *.exe is a DOS or a Windows program?

On Sat, Jan 07, 2023 at 11:33:44AM +, Ottavio Caruso wrote: $ file test2/sm/SM.EXE test2/sm/SM.EXE: MS-DOS executable, MZ for MS-DOS Which makes me think it's DOS but it could be a false positive. Nope, that's it. If it was windows it would say something like "PE32+ executable (GUI)

Re: tbird broken

On Fri, Nov 18, 2022 at 06:14:23PM -0500, gene heskett wrote: Since when does a total lack of html content, disable MIME handling?? That seems like a whopper of a bug to me since MIME was around and working quite well in the later '80's. MIME was standardized in 1992 and wasn't particularly

Re: ZFS performance (was: Re: deduplicating file systems: VDO withDebian?)

On Mon, Nov 14, 2022 at 08:40:47PM +0100, hw wrote: Not really, it was just an SSD. Two of them were used as cache and they failed was not surprising. It's really unfortunate that SSDs fail particulary fast when used for purposes they can be particularly useful for. If you buy hard drives

Re: definiing deduplication

On Sat, Nov 12, 2022 at 01:39:56PM -0500, Stefan Monnier wrote: But as I mentioned, higher-layers (the filesystem layer, and the applications running on top of that) *should* try and make sure that a hard failure (kernel crash, power failure, ... these and up taking a snapshot of your block

Re: ZFS performance (was: Re: deduplicating file systems: VDO withDebian?)

On Fri, Nov 11, 2022 at 02:05:33PM -0500, Dan Ritter wrote: 300TB/year. That's a little bizarre: it's 9.51 MB/s. Modern high end spinners also claim 200MB/s or more when feeding them continuous writes. Apparently WD thinks that can't be sustained more than 5% of the time. Which makes sense for

Re: else or Debian (Re: ZFS performance (was: Re: deduplicating file systems: VDO with Debian?))

On Fri, Nov 11, 2022 at 09:03:45AM +0100, hw wrote: On Thu, 2022-11-10 at 23:12 -0500, Michael Stone wrote: The advantage to RAID 6 is that it can tolerate a double disk failure. With RAID 1 you need 3x your effective capacity to achieve that and even though storage has gotten cheaper

Re: ZFS performance (was: Re: deduplicating file systems: VDO withDebian?)

On Fri, Nov 11, 2022 at 07:15:07AM +0100, hw wrote: There was no misdiagnosis. Have you ever had a failed SSD? They usually just disappear. Actually, they don't; that's a somewhat unusual failure mode. I have had a couple of ssd failures, out of hundreds. (And I think mostly from a

Re: else or Debian (Re: ZFS performance (was: Re: deduplicating file systems: VDO with Debian?))

On Thu, Nov 10, 2022 at 08:32:36PM -0500, Dan Ritter wrote: * RAID 5 and 6 restoration incurs additional stress on the other disks in the RAID which makes it more likely that one of them will fail. I believe that's mostly apocryphal; I haven't seen science backing that up, and it hasn't

Re: ZFS performance (was: Re: deduplicating file systems: VDO withDebian?)

On Thu, Nov 10, 2022 at 06:55:27PM +0100, hw wrote: On Thu, 2022-11-10 at 11:57 -0500, Michael Stone wrote: On Thu, Nov 10, 2022 at 05:34:32PM +0100, hw wrote: > And mind you, SSDs are *designed to fail* the sooner the more data you write > to > them.  They have their uses, m

Re: ZFS performance (was: Re: deduplicating file systems: VDO withDebian?)

On Thu, Nov 10, 2022 at 05:34:32PM +0100, hw wrote: And mind you, SSDs are *designed to fail* the sooner the more data you write to them. They have their uses, maybe even for storage if you're so desperate, but not for backup storage. It's unlikely you'll "wear out" your SSDs faster than you

Bug#1023725: rasdaemon: kernel null pointer dereference oops with rasdaemon

Package: rasdaemon Version: 0.6.7-1+b1 Severity: important Tags: upstream With linux-image-6.0.0-2-amd64 rasdaemon causes a kernel oops with a signature similar to this: BUG: kernel NULL pointer dereference, address: 01c8 #PF: supervisor write access in kernel mode #PF:

Re: support for ancient peripherals

On Sun, Nov 06, 2022 at 06:31:04AM -0500, Dan Ritter wrote: 3. An HP LaserJet 5MP printer from 1995 with a parallel-port connector. StarTech sells a $42 PCIe card with a parallel port and two serial ports. If you're getting a desktop, this might be your preferred path. Two other options: The

Bug#1013259: samba-libs: Possible policy violation (now with libndr.so.2 => libndr.so.3)

On Tue, Nov 01, 2022 at 10:59:11AM +0300, Michael Tokarev wrote: And this revealed one more issue here, now with samba 4.17. Where, the same libndr.so again, has changed soname from libndr.so.2 to libndr.so.3! And it looks like *this* is what you're talking about now, once 4.17 with this new

Bug#1013259: samba-libs: Possible policy violation (now with libndr.so.2 => libndr.so.3)

On Tue, Nov 01, 2022 at 10:59:11AM +0300, Michael Tokarev wrote: And this revealed one more issue here, now with samba 4.17. Where, the same libndr.so again, has changed soname from libndr.so.2 to libndr.so.3! And it looks like *this* is what you're talking about now, once 4.17 with this new

Bug#1013259: samba-libs: Possible policy violation

compatibility but not providing that. One way or another samba-libs either needs to not suggest that linked binaries will work with future versions, or make sure that they do. -- Michael Stone (From phone, please excuse typos)

Bug#1013259: samba-libs: Possible policy violation

The issue here is that packages built against samba-libs get a dependency on samba-libs >= version, and they really either need a dependency on samba-libs == version or the samba-libs package needs to be versioned (e.g., samba-libs2, samba-libs3, etc.) and conflict with other versions, or

Bug#1023204: sssd-ipa: sssd fails to start due to broken dependency

Package: sssd-ipa Version: 2.7.4-1+b1 Severity: critical Justification: breaks the whole system After upgrade of samba-libs syslog has messages like ... sssd[448823]: /usr/libexec/sssd/sssd_pac: error while loading shared libraries: libndr.so.2: cannot open shared object file: No such file or

Bug#1023204: sssd-ipa: sssd fails to start due to broken dependency

Package: sssd-ipa Version: 2.7.4-1+b1 Severity: critical Justification: breaks the whole system After upgrade of samba-libs syslog has messages like ... sssd[448823]: /usr/libexec/sssd/sssd_pac: error while loading shared libraries: libndr.so.2: cannot open shared object file: No such file or

Re: Firmware GR result - what happens next?

On Fri, Oct 14, 2022 at 10:52:01AM +0200, Santiago Ruano Rincón wrote: 5. transitional packages along with a helper package (that fails or success during install) to prompt the user so they add non-free-firmware section when needed. Is there any reason why you are not considering 5.? The

Re: Firmware GR result - what happens next?

On Fri, Oct 14, 2022 at 10:52:01AM +0200, Santiago Ruano Rincón wrote: 5. transitional packages along with a helper package (that fails or success during install) to prompt the user so they add non-free-firmware section when needed. Is there any reason why you are not considering 5.? The

Re: Unification of discussion-forum types (was Re: signing up to fourms)

On Wed, Oct 19, 2022 at 08:57:54AM -0400, The Wanderer wrote: If that doesn't happen in practice, I'd be all for the idea, but as far as I can recall I have yet to encounter a case where it doesn't. We already get too many examples of people failing to quote correctly even here on this mailing

Re: How to configure (aka deal with) /tmp in the best way?

On Wed, Oct 05, 2022 at 02:07:17PM +0100, Tixy wrote: I seem to remember many releases ago playing with this, and there was a config file to set /tmp to tmpfs. A quick google leads me to to look at 'man tmpfs' which says: /tmp Previously configured using RAMTMP in /etc/default/rcS. Note that

Re: Firmware GR result - what happens next?

On Sun, Oct 02, 2022 at 08:21:31PM +0100, Steve McIntyre wrote: Plus, as Shengjing Zhu points out: we already expect people to manage the sources.list anyway on upgrades. We also try to avoid silent install problems that might or might not result in a system that doesn't boot properly.

Re: Firmware GR result - what happens next?

On Sun, Oct 02, 2022 at 08:21:31PM +0100, Steve McIntyre wrote: Plus, as Shengjing Zhu points out: we already expect people to manage the sources.list anyway on upgrades. We also try to avoid silent install problems that might or might not result in a system that doesn't boot properly.

Re: usrmerge

On Sun, Oct 02, 2022 at 06:12:45PM +0100, billium wrote: may be I am idiot for keeping it so long since a re-install. I think stretch was the install, and it is now on bookworm. FYI, skipping releases is not supported; in future, go through each release in order when upgrading. Whether that

Re: Firmware GR result - what happens next?

On Sun, Oct 02, 2022 at 03:53:00PM +0100, Steve McIntyre wrote: On Sun, Oct 02, 2022 at 04:43:47PM +0200, Michael Biebl wrote: What's the plan for upgraded systems with an existing /etc/apt/sources.list. Will the new n-f-f section added on upgrades automatically(if non-free was enabled before)?

Re: Firmware GR result - what happens next?

On Sun, Oct 02, 2022 at 03:53:00PM +0100, Steve McIntyre wrote: On Sun, Oct 02, 2022 at 04:43:47PM +0200, Michael Biebl wrote: What's the plan for upgraded systems with an existing /etc/apt/sources.list. Will the new n-f-f section added on upgrades automatically(if non-free was enabled before)?

Re: Switch default from PulseAudio to PipeWire (and WirePlumber) for audio

On Thu, Sep 29, 2022 at 04:26:45PM +0200, Vincent Bernat wrote: On 2022-09-29 15:01, Michael Stone wrote: On Wed, Sep 28, 2022 at 09:02:15PM -0600, Sam Hartman wrote: * Finally, I can use bluetooth on linux with reasonably good audio  quality! Aren't they both using the same backend? ldac

Re: Switch default from PulseAudio to PipeWire (and WirePlumber) for audio

On Wed, Sep 28, 2022 at 09:02:15PM -0600, Sam Hartman wrote: * Finally, I can use bluetooth on linux with reasonably good audio quality! Aren't they both using the same backend? ldac/aptx weren't in pulseaudio for a long time, but they are now. Or is there something else?

  1   2   3   4   5   6   7   8   9   10   >