Re: Mass storage sizes (was: /dev/serial/by-id)

2025-01-09 Thread tomas
On Thu, Jan 09, 2025 at 06:44:30PM -0500, Michael Stone wrote: [...] > Baloney [...] "Baloney" == "things I don't like" (FWIW I'd prefer binaries in the computer context, but hey). Human communication is messy. Both multipliers come from different sources which were well established at the mom

Re: Mass storage sizes (was: /dev/serial/by-id)

2025-01-09 Thread David Wright
On Thu 09 Jan 2025 at 02:29:37 (-0500), Jeffrey Walton wrote: > On Tue, Jan 7, 2025 at 10:07 AM Stefan Monnier > wrote: > > > > > 8 TB is not that big. I have a external 18 TB drive. It is 18 TB in name > > > only though! After fromating it with ext4 it only had 15TB of usuable > > > space. > > >

Re: new computer arriving soon

2025-01-09 Thread David Wright
On Fri 03 Jan 2025 at 10:54:21 (-0500), Roy J. Tellason, Sr. wrote: > Heh. I remember a 300 baud modem where you had to dial the number on a phone > and then flip the switch on the modem when the other end answered. Whether > you selected the answer or originate mode was a crap shoot, there we

Re: Mass storage sizes

2025-01-09 Thread David Wright
On Tue 07 Jan 2025 at 21:00:39 (+0100), Nicolas George wrote: > Kushal Kumaran (12025-01-07): > > I point people to http://www.tarsnap.com/GB-why.html which is where I > > was first enlightened. > > Mostly something anybody should learn in junior high school physics, > freshman high-school at wors

Re: Mass storage sizes

2025-01-09 Thread David Wright
On Fri 10 Jan 2025 at 02:46:13 (+0100), Urs Thuermann wrote: > Michael Stone writes: > > On Tue, Jan 07, 2025 at 02:59:47PM -0700, Charles Curley wrote: > > >Mr. Tarsnap forgets something. The reason disks are addressed in powers > > >of two has to do with mathematics. Every hard and floppy disk o

Re: Mass storage sizes

2025-01-09 Thread Michael Stone
On Fri, Jan 10, 2025 at 02:46:13AM +0100, Urs Thuermann wrote: For example, my computers had 5.12 kB, 65.356 kB, 16.777216 MB, 67.108864 MB, 268.435456 MB, 1.073741824 GB, and 8.589934592 GB of RAM. Perfectly correct, but I prefer to say they had 5 kiB, 64 kiB, 16 MiB, 64 MiB, 256 MiB, 1 GiB, an

Re: getting started with pipewire

2025-01-09 Thread Max Nikulin
On 09/01/2025 21:15, Greg Wooledge wrote: Moral of the story: NEVER EVER run "wpctl". My guess is that it may be a consequence of "wireplumber" you executed earlier. Having no notion what particular components of pipewire/pulse do, I would avoid running random commands supposed to be started

Re: Mass storage sizes

2025-01-09 Thread Urs Thuermann
Michael Stone writes: > On Tue, Jan 07, 2025 at 02:59:47PM -0700, Charles Curley wrote: > >Mr. Tarsnap forgets something. The reason disks are addressed in powers > >of two has to do with mathematics. Every hard and floppy disk out there > >has flaws. To get around that, data is divided into sect

Re: Mass storage sizes (was: /dev/serial/by-id)

2025-01-09 Thread Timothy M Butterworth
On Thu, Jan 9, 2025 at 6:45 PM Michael Stone wrote: > On Thu, Jan 09, 2025 at 09:47:11PM +0100, Nicolas George wrote: > >For the people who need exact figures, on the other hand, binary units > >are much more convenient, not just to measure the size of memory > >modules: alignment requirements, m

Re: getting started with pipewire

2025-01-09 Thread Geoff
Greg Wooledge wrote: On Thu, Jan 09, 2025 at 07:39:29 -0500, Haines Brown wrote: I have pipewire-pulse intstalled, not puleaudio. Maybe change that? hobbit:~$ dpkg -l | grep pulse ii libpulse-mainloop-glib0:amd6416.1+dfsg1-2+b1amd64 PulseAudio client libraries

Re: Mass storage sizes (was: /dev/serial/by-id)

2025-01-09 Thread Heriberto Avelino
I agree it is important, may be a precision on the more general idea is helpful: "Communication of numbers between ordinary people generally happens in base 10." It turns out that the diversity of the notion of numerosity among *homo sapiens* is way far richer than the base-10. See https://wals.in

Re: Mass storage sizes (was: /dev/serial/by-id)

2025-01-09 Thread Jeffrey Walton
On Thu, Jan 9, 2025 at 6:45 PM Michael Stone wrote: > > On Thu, Jan 09, 2025 at 09:47:11PM +0100, Nicolas George wrote: > >For the people who need exact figures, on the other hand, binary units > >are much more convenient, not just to measure the size of memory > >modules: alignment requirements,

Re: Mass storage sizes (was: /dev/serial/by-id)

2025-01-09 Thread Michael Stone
On Thu, Jan 09, 2025 at 09:47:11PM +0100, Nicolas George wrote: For the people who need exact figures, on the other hand, binary units are much more convenient, not just to measure the size of memory modules: alignment requirements, maximum sizes of files and devices, size of stripes, they are al

Re: Mass storage sizes (was: /dev/serial/by-id)

2025-01-09 Thread Nicolas George
Michael Stone (12025-01-08): > For example...let's take the 18B drive discussed earlier. That's > 18TB or 16TiB. Annoying, but ok. Now that's also 18000MB but 16763MiB. And > it's 1800MB or 17166137MiB. So if you have a display in MB and you want > to know the value in TB you move t

Re: qt6-svg-plugins should be a hard dependency from kde-full or task-kde-desktop

2025-01-09 Thread Patrick Franz
Hej, Am Sonntag, 29. Dezember 2024, 04:21:57 MEZ schrieb Christopher Andrews: > I am unsure exactly what package to file this bug against, so per the > recommendation I am sending to this list. I suspect this should be > filed against libqt6gui6. > > I run debian/unstable, and my system somehow g

Re: Mass storage sizes

2025-01-09 Thread Dan Purgert
On Jan 09, 2025, Stefan Monnier wrote: > > For example...let's take the 18B drive discussed earlier. That's > > 18TB or 16TiB. Annoying, but ok. Now that's also 18000MB but 16763MiB. And > > it's 1800MB or 17166137MiB. So if you have a display in MB and you want > > to know the valu

Re: Mass storage sizes

2025-01-09 Thread Stefan Monnier
> For example...let's take the 18B drive discussed earlier. That's > 18TB or 16TiB. Annoying, but ok. Now that's also 18000MB but 16763MiB. And > it's 1800MB or 17166137MiB. So if you have a display in MB and you want > to know the value in TB you move the decimal 6 places. But if y

Re: getting started with pipewire

2025-01-09 Thread pocket
> Sent: Thursday, January 09, 2025 at 9:15 AM > From: "Greg Wooledge" > To: debian-user@lists.debian.org > Subject: Re: getting started with pipewire > > On Thu, Jan 09, 2025 at 09:00:24 -0500, Greg Wooledge wrote: > > > $ wpctl status > > > Could not connect to PipeWire > > > > hobbit:~$

Re: getting started with pipewire

2025-01-09 Thread tomas
On Thu, Jan 09, 2025 at 09:15:16AM -0500, Greg Wooledge wrote: > On Thu, Jan 09, 2025 at 09:00:24 -0500, Greg Wooledge wrote: > > > $ wpctl status > > > Could not connect to PipeWire > > > > hobbit:~$ wpctl status [...] > I tried everything I could immediately think of, including logging out

Re: getting started with pipewire

2025-01-09 Thread Greg Wooledge
On Thu, Jan 09, 2025 at 09:00:24 -0500, Greg Wooledge wrote: > > $ wpctl status > > Could not connect to PipeWire > > hobbit:~$ wpctl status > ^C > > It just "hung" with no output. > > After I pressed Ctrl-C, my audio stopped working. I'm never going > to do this one again! > > > # syste

Re: getting started with pipewire

2025-01-09 Thread Greg Wooledge
On Thu, Jan 09, 2025 at 07:39:29 -0500, Haines Brown wrote: > I have pipewire-pulse intstalled, not puleaudio. Maybe change that? hobbit:~$ dpkg -l | grep pulse ii libpulse-mainloop-glib0:amd6416.1+dfsg1-2+b1amd64 PulseAudio client libraries (glib support) ii li

Re: getting started with pipewire

2025-01-09 Thread Haines Brown
Now I get these lines from systemctl --user status pipewire.service Jan 02 09:39:26 iskra systemd[1518]: Started pipewire.service - PipeWire Multimedia Service. Jan 07 11:14:49 iskra pipewire[1534]: spa.alsa: 'front:0': playback open failed: Device or resource busy Jan 07 1