Suspend show error

[sk]

I used debian 9 for 1 year and everything works fine. After update to 
debian 10 it works very slow but after some update it works somewhat ok. 
But suspension and hibernation not works . I use kde 5 as DE so if i 
suspend using menu i have blank screen and never resume . So i search 
internet and use pm-utils and (suspensd and hibernation works) . After 
resume from suspension i got error "


Message from syslogd@debian at Aug 3 08:11:43 ...
kernel:[ 840.096104] mce: [Hardware Error]: CPU 0: Machine Check: 0 Bank 6: 
ae40110a
Message from syslogd@debian at Aug 3 08:11:43 ...
kernel:[ 840.096105] mce: [Hardware Error]: TSC 0 ADDR fef81e00 MISC 38a086
Message from syslogd@debian at Aug 3 08:11:43 ...
kernel:[ 840.096109] mce: [Hardware Error]: PROCESSOR 0:40651 TIME 1627958501 SOCKET 
0 APIC 0 microcode 26 "

. I remove pm-utils and use systemctl suspend but after resuming same error. 
please help

Re: why 1G memory is missing?

[Jeremy Hendricks]

It’s bios/chipset dependent. Example: the Intel 945 will not allow more
than 3.25GB or so regardless if PAE is used. However, the Intel 965 chipset
will provide the full 4GB if used with PAE enabled and the BIOS allows it
by default or has a ‘remap’ option.

On Mon, Aug 2, 2021 at 7:15 PM  wrote:

> Jeremy Hendricks:
> Are you booting an x86 or x86_64 install? Run: “uname -a” without quotes
> and post the results to us.
>
>
> Linux debian 4.9.0-13-686-pae #1 SMP Debian 4.9.228-1 (2020-07-05) i686
> GNU/Linux
>
> Thanks, i thought pae can bypass 4G limit of 32-bit OS
>
>

Re: why 1G memory is missing?

[loushanguan2015]

Jeremy Hendricks:Are you booting an x86 or x86_64 install? Run: “uname -a” 
without quotes and post the results to us.

Linux debian 4.9.0-13-686-pae #1 SMP Debian 4.9.228-1 (2020-07-05) i686 
GNU/Linux
Thanks, i thought pae can bypass 4G limit of 32-bit OS

Re: `pv` rates

[Stefan Monnier]

>> If it weren't for the first sometimes changing to
>> 44.xKiB/s it'd be hard to know which is which (IIUC the average is
>> higher because occasionally the drive gives a more reasonable transfer
>> rate than that measly 45kB/s).
>
> So now we're left wondering how you came by this situation. Perhaps
> you slumped onto the Return key, then woke up after a few minutes,
> having missed the initial burst that gave rise to the average being
> more than 50% faster than the current rate.

I don't know either.  Reading the whole drive would take a few years, so
I'm only fetching the few parts which have changed since the last
backup, and when I look the rate seems to be always ~45kB/s, but
obviously there have to be bursts at higher speeds (presumably because
the drive's defect doesn't affect every cylinder in the same way or
something like that.  E.g. the average has moved up to ~80kB/s since my
last message).


Stefan

Re: Being concise [Re: Iso to Usb]

[Andrew M.A. Cater]

On Mon, Aug 02, 2021 at 05:30:30PM -0400, Polyna-Maude Racicot-Summerside wrote:
> Hi,
> What are you asking for here ? Or trying to achieve ?
> 
> On 2021-08-02 4:48 p.m., Gunnar Gervin wrote:
> > I cowarded out of Terminal, or not really, cos Gnome Multiwriter did it
> > in 5 minutes.
> > But later I`ll try it, if 64 bit doesn`t work in this old computer that
> > only Looks like a Mac. But is it, really? Not in my point of view; no
> Your point of view is irrelevant unless you are having a conversation
> with yourself.
> 
> What make a computer a "Mac" or not a "Mac" is totally unrelated to the
> software you run on it. No one asked you "Do you run MacOS".
> 
> What make your computer a Mac and still a Mac, and will be a Mac, was a
> Mac, continue to be a Mac is the plain fact that it's got produced on
> Apple's production line and is running all the software in ROM required
> to boot that make it a Mac. If it's not a Mac, then it's a PC and you
> either have BIOS or UEFI, which is not the case.
> 
> > Mac software, except some hotkey functions, a pretty good keyboard,
> > so-and-so dvd player, & a Toshiba SSD (original or not; did SSD exist in
> > 2007? Who cares? Philosophy, history, or both? What's "both"?
> Yes SSD existed in 2007 and what's the point ?
> 
> What's the link between SSD and what you are writing here ?
> 
> You seem to be part of a one-man show...
> 
> I've tried to give you a helping hand but don't seem much to get it.
> 
> And as I've seen other have tried too.
> 
> Linux is supported by dozen of architectures, does they all become PCs
> because they ain't running their original operating system. No they
> don't
> 
> > Psychology, haha; narrative philosophical walkthroughs PC pasts?)
> Only you seem to be making so deep heard philosophical problem with
> plain easy question
> > BR,
> > geg
> 
> -- 
> Polyna-Maude R.-Summerside
> -Be smart, Be wise, Support opensource development
> 

Gunnar,

You have Mac hardware from almost exactly the right vintage to use a 
specific for early Mac image. It boots in 32 bit EFI and then runs 64 bit.

https://wiki.debian.org/MacMiniIntel#Macmini_2.2C1

and the up to date Debian 10.10 image you need is at:

https://cdimage.debian.org/debian-cd/current/amd64/iso-cd/debian-mac-10.10.0-amd64-netinst.iso

This may solve your problems for installing on Mac hardware of that vintage.
It may not solve other problems but it should, at least, get you something
consistent. [If this image works for you, you will be one of a very few
people running this on that particular model - an installation report
would be very valuable.]

As Polyna says - you have Apple Mac hardware. That has its own peculiarities.

On 3G of memory in total, you may find problems in running anything intensive.

I can only recommend Dan Ritter's advice to go away and read and to tackle one
problem at a time. Allow yourself time to get one stable Debian system
running on that hardware. 14 year old hardware is pushing the boundaries
on reliability but, as you've seen, it is a learning experience.

All best, as ever,

Andy Cater

Re: why 1G memory is missing?

[IL Ka]

> i have 2 memory slots
> memtest86+ shows each has 2G, but total is 3G
> after booting linux, top shows total is 3G
>
why 1 G is missing? Thanks!
>


You probably have 32bit OS
https://en.wikipedia.org/wiki/3_GB_barrier

Re: why 1G memory is missing?

[Jeremy Hendricks]

Are you booting an x86 or x86_64 install? Run: “uname -a” without quotes
and post the results to us.

On Mon, Aug 2, 2021 at 6:12 PM  wrote:

> i have 2 memory slots
> memtest86+ shows each has 2G, but total is 3G
> after booting linux, top shows total is 3G
> why 1 G is missing? Thanks!
>

why 1G memory is missing?

[loushanguan2015]

i have 2 memory slotsmemtest86+ shows each has 2G, but total is 3Gafter booting 
linux, top shows total is 3Gwhy 1 G is missing? Thanks!

Re: Being concise [Re: Iso to Usb]

[Polyna-Maude Racicot-Summerside]

Hi,

On 2021-08-02 5:36 p.m., ellanios82 wrote:
> 
>> unless you are having a conversation
>> with yourself.
> 
> 
>  - from time-to-time, do enjoy Canadienne,
> 
All "Canadian" politicans enjoy having their own day-to-day,
conversation with themselves.

How did you know I was "canadienne" ?

Where you from ?

Always asked myself, how crazy do Amercian think we are ?

We don't have guns and go home at 20:00 when we do a riot.
>     "the Amazing Polly"  [youtube]
> 
> 
> .
> 
>  rgds
> 
> .
> 
> 
> 

-- 
Polyna-Maude R.-Summerside
-Be smart, Be wise, Support opensource development



OpenPGP_signature
Description: OpenPGP digital signature

Re: Being concise [Re: Iso to Usb]

[ellanios82]

unless you are having a conversation
with yourself.



 - from time-to-time, do enjoy Canadienne,

    "the Amazing Polly"  [youtube]


.

 rgds

.

Re: ISO to external SSD

[Polyna-Maude Racicot-Summerside]

Hi,

On 2021-08-02 3:35 p.m., Gunnar Gervin wrote:
> Hi again.
> This is an unusual question &/or project, maybe utterly stupid, maybe
> temporary:
> I bought a 1 TB external SSD (Intenso) for later commercial use -in my
> company.
> Meanwhile I want to use it for something else: To burn an entire Debian
> distro on it.
> I guess it`ll be more than enough space to let it stay afterwards.
> Points of doing it:
> 1. After the Big job is done, less time to lose each time a program is
> needed.
true
> 2. More security that necessary software is available, even if software
> is off internet
> 
not so true
will still be needing to contact the security updates repository to keep
yourself up to date.
> Any advice, suggestions, or thoughts in this matter? Is it not new at
> all, just trivial?
plain trivial
will need to use the command line

debmirror --all --getcontents --progress --verbose --method=http
--dist=buster,buster-updates,buster-backports
--section=main,contrib,non-free --arch=amd64,i386 --rsync-extra=none
--source --i18n --keyring /usr/share/keyrings/debian-archive-keyring.gpg
--root=debian --diff=mirror --host=debian.mirror.iweb.ca /mnt/mirror/debian


replace /mnt/mirror/debian with the folder of destination
replace debian.mirror.iweb.ca with your local mirror

> BR,
> Geg.

-- 
Polyna-Maude R.-Summerside
-Be smart, Be wise, Support opensource development



OpenPGP_signature
Description: OpenPGP digital signature

Being concise [Re: Iso to Usb]

[Polyna-Maude Racicot-Summerside]

Hi,
What are you asking for here ? Or trying to achieve ?

On 2021-08-02 4:48 p.m., Gunnar Gervin wrote:
> I cowarded out of Terminal, or not really, cos Gnome Multiwriter did it
> in 5 minutes.
> But later I`ll try it, if 64 bit doesn`t work in this old computer that
> only Looks like a Mac. But is it, really? Not in my point of view; no
Your point of view is irrelevant unless you are having a conversation
with yourself.

What make a computer a "Mac" or not a "Mac" is totally unrelated to the
software you run on it. No one asked you "Do you run MacOS".

What make your computer a Mac and still a Mac, and will be a Mac, was a
Mac, continue to be a Mac is the plain fact that it's got produced on
Apple's production line and is running all the software in ROM required
to boot that make it a Mac. If it's not a Mac, then it's a PC and you
either have BIOS or UEFI, which is not the case.

> Mac software, except some hotkey functions, a pretty good keyboard,
> so-and-so dvd player, & a Toshiba SSD (original or not; did SSD exist in
> 2007? Who cares? Philosophy, history, or both? What's "both"?
Yes SSD existed in 2007 and what's the point ?

What's the link between SSD and what you are writing here ?

You seem to be part of a one-man show...

I've tried to give you a helping hand but don't seem much to get it.

And as I've seen other have tried too.

Linux is supported by dozen of architectures, does they all become PCs
because they ain't running their original operating system. No they
don't

> Psychology, haha; narrative philosophical walkthroughs PC pasts?)
Only you seem to be making so deep heard philosophical problem with
plain easy question
> BR,
> geg

-- 
Polyna-Maude R.-Summerside
-Be smart, Be wise, Support opensource development



OpenPGP_signature
Description: OpenPGP digital signature

`pv` rates (was: burn iso to usb)

[Stefan Monnier]

Anssi Saari [2021-08-02 19:04:59] wrote:
> David Wright  writes:
>> On Mon 02 Aug 2021 at 16:14:15 (+0300), Anssi Saari wrote:
>>> Stefan Monnier  writes:
>>> >>> > cp /path/to/file.iso /dev/sdX
>>> >>> dd if=whatever.iso of=/dev/sdX  
>>> >> It's up to taste.
>>> >
>>> > Not at all.  The only right answer is:
>>> >
>>> > pv -parIe /dev/sdX
>>> 
>>> Actually I'm not sure how good it is to have both -a and -r, pv doesn't
>>> really show which rate counter is which...
>>
>> No need: the rate is far more variable than its average, as time passes.
>
> I guess it depends. Before that comment I tried it on an old USB
> stick. Read speed was pretty much constant if low. So I think it was the
> left rate counter that showed current rate but wouldn't bet on it.

[ I'm glad my silly intervention brings up a more constructive
  discussion ;-)  ]

If they're both pretty much constant, they're presumably both pretty
much equal, so it doesn't matter which is which ;-)

But indeed, it's not always the case.  I'm right now using `pv` to read
data off of a broken drive (a 2TB 2½" drive which apparently has
problems seeking, resulting in a transfer rate of about 45kB/s), and
it's currently showing me 45.0KiB/s and 70.6KiB/s both of which are
quite stable.  If it weren't for the first sometimes changing to
44.xKiB/s it'd be hard to know which is which (IIUC the average is
higher because occasionally the drive gives a more reasonable transfer
rate than that measly 45kB/s).


Stefan

Re: Updating kernels impossible when /boot is getting full

[David Christensen]

On 8/2/21 12:47 PM, Greg Wooledge wrote:

On Mon, Aug 02, 2021 at 12:43:27PM -0700, David Christensen wrote:

I'd rather not install dracut.


Me too.  So why not use lsinitramfs -l ?  Why keep reinventing the wheel?

unicorn:~$ lsinitramfs -l /boot/initrd.img-5.10.0-8-amd64 | head -12
drwxr-xr-x   2 root root0 Apr 25 08:00 kernel
drwxr-xr-x   2 root root0 Apr 25 08:00 kernel/x86
drwxr-xr-x   2 root root0 Apr 25 08:00 kernel/x86/microcode
drwxr-xr-x   2 root root0 Apr 25 08:00 
kernel/x86/microcode/.enuineIntel.align.0123456789abc
-rw-r--r--   1 root root  4609024 Apr 25 08:00 
kernel/x86/microcode/GenuineIntel.bin
drwxr-xr-x   7 root root0 Aug  2 14:37 .
lrwxrwxrwx   1 root root7 Aug  2 14:37 bin -> usr/bin
drwxr-xr-x   3 root root0 Aug  2 14:37 conf
-rw-r--r--   1 root root   16 Aug  2 14:37 conf/arch.conf
drwxr-xr-x   2 root root0 Aug  2 14:37 conf/conf.d
-rw-r--r--   1 root root   49 Jan 11  2018 conf/conf.d/resume
-rw-r--r--   1 root root 1365 Sep 13  2020 conf/initramfs.conf

No dracut needed.



Did you not make a post that lsinitrd.sh and lsinitramfs produced 
different output?


https://lists.debian.org/debian-user/2021/08/msg00057.html


They seem to produce the same output on my machine.  So, yes, 
lsinitramfs(8) is preferable:


$ lsinitramfs -l /boot/initrd.img-4.19.0-17-amd64 | sort -k 9 > 
initrd.img-4.19.0-17-amd64.lsinitramfs


$ diff -s initrd.img-4.19.0-17-amd64.txt 
initrd.img-4.19.0-17-amd64.lsinitramfs
Files initrd.img-4.19.0-17-amd64.txt and 
initrd.img-4.19.0-17-amd64.lsinitramfs are identical



David

Iso to Usb

[Gunnar Gervin]

I cowarded out of Terminal, or not really, cos Gnome Multiwriter did it in
5 minutes.
But later I`ll try it, if 64 bit doesn`t work in this old computer that
only Looks like a Mac. But is it, really? Not in my point of view; no Mac
software, except some hotkey functions, a pretty good keyboard, so-and-so
dvd player, & a Toshiba SSD (original or not; did SSD exist in 2007? Who
cares? Philosophy, history, or both? What's "both"? Psychology, haha;
narrative philosophical walkthroughs PC pasts?)
BR,
geg

Re: burn iso to usb

[tomas]

On Mon, Aug 02, 2021 at 03:44:03PM -0400, Greg Wooledge wrote:
> On Mon, Aug 02, 2021 at 10:02:18PM +0300, Gunnar Gervin wrote:
> > pv -parle /dev/sdX
> > would rather be:
> > sudo pv -parle /dev/sdb
> 
> No, that won't work.
> 
> https://mywiki.wooledge.org/BashPitfalls#pf53
> 
> If you want to use redirections with sudo, you either need to wrap
> things in "sh -c" a lot, or else get a full interactive shell first
> (sudo -s), and *then* run your commands with redirections.

Another nice use for 'dd', btw :-)

  pv -parle < ... | sudo dd of=/dev/sdb 

One charming property of that is that only the 'dd' runs as root.

(the usual solution is to use 'tee', but then you have to get rid
of stdout).

Cheers
 - t


signature.asc
Description: Digital signature

Re: burn iso to usb

[Nicolas George]

Greg Wooledge (12021-08-02):
> No, that won't work.
> 
> https://mywiki.wooledge.org/BashPitfalls#pf53
> 
> If you want to use redirections with sudo, you either need to wrap
> things in "sh -c" a lot, or else get a full interactive shell first
> (sudo -s), and *then* run your commands with redirections.

That! And sudo was addressed in the very first mail:

"I advise it over using root privileges for the cp: you could wipe your
install if you get the device wrong."

Regards,

-- 
  Nicolas George


signature.asc
Description: PGP signature

Re: Updating kernels impossible when /boot is getting full

[Greg Wooledge]

On Mon, Aug 02, 2021 at 12:43:27PM -0700, David Christensen wrote:
> I'd rather not install dracut.

Me too.  So why not use lsinitramfs -l ?  Why keep reinventing the wheel?

unicorn:~$ lsinitramfs -l /boot/initrd.img-5.10.0-8-amd64 | head -12
drwxr-xr-x   2 root root0 Apr 25 08:00 kernel
drwxr-xr-x   2 root root0 Apr 25 08:00 kernel/x86
drwxr-xr-x   2 root root0 Apr 25 08:00 kernel/x86/microcode
drwxr-xr-x   2 root root0 Apr 25 08:00 
kernel/x86/microcode/.enuineIntel.align.0123456789abc
-rw-r--r--   1 root root  4609024 Apr 25 08:00 
kernel/x86/microcode/GenuineIntel.bin
drwxr-xr-x   7 root root0 Aug  2 14:37 .
lrwxrwxrwx   1 root root7 Aug  2 14:37 bin -> usr/bin
drwxr-xr-x   3 root root0 Aug  2 14:37 conf
-rw-r--r--   1 root root   16 Aug  2 14:37 conf/arch.conf
drwxr-xr-x   2 root root0 Aug  2 14:37 conf/conf.d
-rw-r--r--   1 root root   49 Jan 11  2018 conf/conf.d/resume
-rw-r--r--   1 root root 1365 Sep 13  2020 conf/initramfs.conf

No dracut needed.

Re: burn iso to usb

[Greg Wooledge]

On Mon, Aug 02, 2021 at 10:02:18PM +0300, Gunnar Gervin wrote:
> pv -parle /dev/sdX
> would rather be:
> sudo pv -parle /dev/sdb

No, that won't work.

https://mywiki.wooledge.org/BashPitfalls#pf53

If you want to use redirections with sudo, you either need to wrap
things in "sh -c" a lot, or else get a full interactive shell first
(sudo -s), and *then* run your commands with redirections.

Re: Updating kernels impossible when /boot is getting full

[David Christensen]

On 8/2/21 11:29 AM, Greg Wooledge wrote:

On Mon, Aug 02, 2021 at 11:11:11AM -0700, David Christensen wrote:



Please post your console session showing how you created
initrd.img-5.10.0-8-amd64.txt.gz.


I didn't.  It was created automatically when I installed dracut-core.

Prior to that, it was created automatically every time I did anything
with apt-get which touched the "low level stuff" (kernel, firmware,
microcode, busybox, other tools that live in the initrd, and so on).



I'd rather not install dracut.


The source for lsinitrd.sh is available on github:

https://github.com/dracutdevs/dracut/blob/master/lsinitrd.sh


The cpio(1) listing incantation appears on line 177.  Reworking my 
previous command:


$ gunzip -c /boot/initrd.img-4.19.0-17-amd64 | cpio --extract --verbose 
--list | sort -k9 | gzip -9 > initrd.img-4.19.0-17-amd64.txt.gz

246741 blocks


Please see initrd.img-4.19.0-17-amd64.txt.gz, attached.


If the OP would care to run the above command and post the result, 
perhaps we can see what is bloating their initrd.img.



David


initrd.img-4.19.0-17-amd64.txt.gz
Description: application/gzip

Re: ISO to external SSD

[Dan Ritter]

Gunnar Gervin wrote: 
> Hi again.
> This is an unusual question &/or project, maybe utterly stupid, maybe
> temporary:
> I bought a 1 TB external SSD (Intenso) for later commercial use -in my
> company.
> Meanwhile I want to use it for something else: To burn an entire Debian
> distro on it.
> I guess it`ll be more than enough space to let it stay afterwards. Points
> of doing it:
> 1. After the Big job is done, less time to lose each time a program is
> needed.
> 2. More security that necessary software is available, even if software is
> off internet
> 
> Any advice, suggestions, or thoughts in this matter? Is it not new at all,
> just trivial?

By distro, do you mean the complete package repository?

https://www.debian.org/mirror/size

-dsr-

ISO to external SSD

[Gunnar Gervin]

Hi again.
This is an unusual question &/or project, maybe utterly stupid, maybe
temporary:
I bought a 1 TB external SSD (Intenso) for later commercial use -in my
company.
Meanwhile I want to use it for something else: To burn an entire Debian
distro on it.
I guess it`ll be more than enough space to let it stay afterwards. Points
of doing it:
1. After the Big job is done, less time to lose each time a program is
needed.
2. More security that necessary software is available, even if software is
off internet

Any advice, suggestions, or thoughts in this matter? Is it not new at all,
just trivial?
BR,
Geg.

Confirmacion Entrevistas Miercoles 11 de Agosto

[Karina Acosta Palacios]

Favor de contarnos sobre una situación en específico donde tuvo que actuar sin 
el consentimiento de su jefe.

Workshop:
Cómo Diseñar y Aplicar Entrevistas Laborales Conductuales y Situacionales
Online en Vivo
11 de Agosto 2021

El modelo de entrevista tradicional quedó en el pasado...
¡APRENDE DE MANERA PRÁCTICA CÓMO FORMULAR PREGUNTAS Y ESCENARIOS PARA 
DESARROLLAR ENTREVISTAS CONDUCTUALES Y SITUACIONALES!
 
DESCARGAR FOLLETO COMPLETO
>>>Deseo mayores informes a través de WhatsApp

Mayores informes comuníquese con alguno de nuestros ejecutivos:

Ciudad de México / 55 2450 6187
Guadalajara, Jal. / 33 2005 0994
Monterrey, N.L. / 81 2974 7731














 

Este boletín informativo tiene como objetivo generar valor en su Empresa, si 
usted y su Organización desean dejar de recibir este tipo de correo electrónico 
conteste con la palabra BAJACONDUCTUAL340. O en su defecto haga click en el 
siguiente enlace: unsubscribe from this list

Re: burn iso to usb

[Gunnar Gervin]

Hi.
The different suggestions are not complete, are they??
Like:
pv -parle /dev/sdX
would rather be:
sudo pv -parle /dev/sdb
And even not sure on that example as being correct. Please correct my
possible failure/s in the above try.
As you can see, I`m trying a -64bit- because Macbook 2.1 might fit it. And
Gnome because it seems more complete.
Saw another (relative) newbie said something similar concerning man pages
in terminal: "Would be nice with example/s".
BR,
geg

On Mon, 2 Aug 2021 at 16:14, Anssi Saari  wrote:

> Stefan Monnier  writes:
>
> >>> > cp /path/to/file.iso /dev/sdX
> >>> dd if=whatever.iso of=/dev/sdX
> >> It's up to taste.
> >
> > Not at all.  The only right answer is:
> >
> > pv -parIe /dev/sdX
>
> Actually I'm not sure how good it is to have both -a and -r, pv doesn't
> really show which rate counter is which...
>
>
>

Re: Google sites don't work

[Kent West]

On Mon, Aug 2, 2021 at 7:52 AM Ivan Krylov  wrote:

> > Similar problem here, only with Google sites like Gmail, Docs, and
> > Chat (via a[n?] university/Google system).
>
> Interesting. Do you see any relevant errors if you press F12 and take a
> look at the JavaScript console on the affected pages, compared to the
> unaffected pages? What about the Network tab, any failed requests there?
>
> --
> Best regards,
> Ivan
>
>
When press F12, and then click on the "Console" tab, I get the following,
which means nothing to me:

Some cookies are misusing the recommended “SameSite“ attribute 105
Some cookies are misusing the recommended “SameSite“ attribute 24
Content Security Policy: Ignoring “'unsafe-inline'” within script-src:
‘strict-dynamic’ specified
Content Security Policy: Ignoring “https:” within script-src:
‘strict-dynamic’ specified
Content Security Policy: Ignoring “http:” within script-src:
‘strict-dynamic’ specified
Content Security Policy: Ignoring “'unsafe-inline'” within script-src:
‘strict-dynamic’ specified
Content Security Policy: Ignoring “https:” within script-src:
‘strict-dynamic’ specified
Content Security Policy: Ignoring “http:” within script-src:
‘strict-dynamic’ specified
Content Security Policy: Ignoring “'unsafe-inline'” within script-src:
‘strict-dynamic’ specified
Content Security Policy: Ignoring “https:” within script-src:
‘strict-dynamic’ specified
Content Security Policy: Ignoring “http:” within script-src:
‘strict-dynamic’ specified
Content Security Policy: Ignoring “'unsafe-inline'” within script-src:
‘strict-dynamic’ specified
Content Security Policy: Ignoring “https:” within script-src:
‘strict-dynamic’ specified
Content Security Policy: Ignoring “http:” within script-src:
‘strict-dynamic’ specified
Content Security Policy: Ignoring “'unsafe-inline'” within script-src or
style-src: nonce-source or hash-source specified
Content Security Policy: Ignoring ‘x-frame-options’ because of
‘frame-ancestors’ directive.
Content Security Policy: Ignoring “'unsafe-inline'” within script-src:
‘strict-dynamic’ specified
Content Security Policy: Ignoring “https:” within script-src:
‘strict-dynamic’ specified
Content Security Policy: Ignoring “http:” within script-src:
‘strict-dynamic’ specified
Content Security Policy: Ignoring “'unsafe-inline'” within script-src or
style-src: nonce-source or hash-source specified
Content Security Policy: Ignoring “'unsafe-inline'” within script-src:
‘strict-dynamic’ specified
Content Security Policy: Ignoring “https:” within script-src:
‘strict-dynamic’ specified
Content Security Policy: Ignoring “http:” within script-src:
‘strict-dynamic’ specified
Content Security Policy: Ignoring “'unsafe-inline'” within script-src:
‘strict-dynamic’ specified
Content Security Policy: Ignoring “https:” within script-src:
‘strict-dynamic’ specified
Content Security Policy: Ignoring “http:” within script-src:
‘strict-dynamic’ specified
Content Security Policy: Ignoring “'unsafe-inline'” within script-src:
‘strict-dynamic’ specified
Content Security Policy: Ignoring “https:” within script-src:
‘strict-dynamic’ specified
Content Security Policy: Ignoring “http:” within script-src:
‘strict-dynamic’ specified
Content Security Policy: Ignoring “'unsafe-inline'” within script-src:
‘strict-dynamic’ specified
Content Security Policy: Ignoring “https:” within script-src:
‘strict-dynamic’ specified
Content Security Policy: Ignoring “http:” within script-src:
‘strict-dynamic’ specified
Content Security Policy: Ignoring “'unsafe-inline'” within script-src or
style-src: nonce-source or hash-source specified
Content Security Policy: Ignoring ‘x-frame-options’ because of
‘frame-ancestors’ directive.
Content Security Policy: Ignoring “'unsafe-inline'” within script-src:
‘strict-dynamic’ specified
Content Security Policy: Ignoring “https:” within script-src:
‘strict-dynamic’ specified
Content Security Policy: Ignoring “http:” within script-src:
‘strict-dynamic’ specified
Content Security Policy: Ignoring “'unsafe-inline'” within script-src or
style-src: nonce-source or hash-source specified
Empty string passed to getElementById(). 3 m=b:1168:137

Empty string passed to getElementById(). 6 m=b:1168:137

Empty string passed to getElementById(). 2 m=b:1168:137

Re: `pv` rates (was: burn iso to usb)

[David Wright]

On Mon 02 Aug 2021 at 13:26:19 (-0400), Stefan Monnier wrote:
> Anssi Saari [2021-08-02 19:04:59] wrote:
> > David Wright  writes:
> >> On Mon 02 Aug 2021 at 16:14:15 (+0300), Anssi Saari wrote:
> >>> Stefan Monnier  writes:
> >>> >>> > cp /path/to/file.iso /dev/sdX
> >>> >>> dd if=whatever.iso of=/dev/sdX  
> >>> >> It's up to taste.
> >>> >
> >>> > Not at all.  The only right answer is:
> >>> >
> >>> > pv -parIe /dev/sdX
> >>> 
> >>> Actually I'm not sure how good it is to have both -a and -r, pv doesn't
> >>> really show which rate counter is which...
> >>
> >> No need: the rate is far more variable than its average, as time passes.
> >
> > I guess it depends. Before that comment I tried it on an old USB
> > stick. Read speed was pretty much constant if low. So I think it was the
> > left rate counter that showed current rate but wouldn't bet on it.
> 
> [ I'm glad my silly intervention brings up a more constructive
>   discussion ;-)  ]
> 
> If they're both pretty much constant, they're presumably both pretty
> much equal, so it doesn't matter which is which ;-)
> 
> But indeed, it's not always the case.  I'm right now using `pv` to read
> data off of a broken drive (a 2TB 2½" drive which apparently has
> problems seeking, resulting in a transfer rate of about 45kB/s), and
> it's currently showing me 45.0KiB/s and 70.6KiB/s both of which are
> quite stable.

Writing "quite stable" cloaks the information nicely. The average can
never move away from the rate: a change in the least significant digit
gives the game away.

> If it weren't for the first sometimes changing to
> 44.xKiB/s it'd be hard to know which is which (IIUC the average is
> higher because occasionally the drive gives a more reasonable transfer
> rate than that measly 45kB/s).

So now we're left wondering how you came by this situation. Perhaps
you slumped onto the Return key, then woke up after a few minutes,
having missed the initial burst that gave rise to the average being
more than 50% faster than the current rate.

Cheers,
David.

Re: listing initrd content

[David Wright]

On Tue 03 Aug 2021 at 02:03:57 (+1000), David wrote:
> On Tue, 3 Aug 2021 at 01:45, David Wright  wrote:
> 
> > BTW I encrypt only /home and swap, and AFAICT my initrd.img doesn't
> > contain crypt stuff except for /usr/bin/cryptroot-unlock (5686B).
> > So I ignore a polite warning at every rebuild:
> >
> >   update-initramfs: Generating /boot/initrd.img-4.19.0-17-amd64
> >   cryptsetup: WARNING: The initramfs image may not contain cryptsetup 
> > binaries
> >   nor crypto modules. If that's on purpose, you may want to uninstall 
> > the
> >   'cryptsetup-initramfs' package in order to disable the cryptsetup 
> > initramfs
> >   integration and avoid this warning.
> >   Log ended: 2021-07-20  10:07:25
> 
> As the warning says, it and /usr/bin/cryptroot-unlock will go away
> if you uninstall 'cryptsetup-initramfs', which is pulled in by 'cryptsetup',
> which describes itself as a transitional dummy package that
> can be removed. You probably only need 'cryptsetup-run' and
> 'cryptsetup-bin'. I learned this by running
>   apt show 'cryptsetup*'
> and tried it and it works fine where appropriate.

I was really just pointing out that having the encryption packages
installed on the system doesn't mean that any extra functionality
gets included in the initrd.img file. So I can't quite see the
point of removing packages from the system in order to reduce the
initrd.img's size.

I don't know, without seeing a list of differences in the file
content, whether dracut is doing its job (reducing the size),
because, for example, is it reading the same configuration info
on compression. That alone could account for a 6MB difference,
I presume.

(BTW I omitted to say that swap has a random key, so RESUME=none
makes that a non-issue.)

Cheers,
David.

Re: Updating kernels impossible when /boot is getting full

[Greg Wooledge]

On Mon, Aug 02, 2021 at 11:11:11AM -0700, David Christensen wrote:
> On 8/1/21 3:51 PM, Greg Wooledge wrote:
> > On Sun, Aug 01, 2021 at 03:29:07PM -0700, David Christensen wrote:
> > > 2021-08-01 13:52:37 root@dipsy ~
> 
> > > # gunzip -c /boot/initrd.img-4.19.0-17-amd64 | cpio -i -d -H newc
> > > --no-absolute-filenames
> > > 246741 blocks
> > 
> > That may not extract the full content of the initrd.  It only reads
> > one of the concatenated CPIO archives.  Also, the first archive may not
> > be gzipped.  Also also, hard-coding the input archive format is weird;
> > I'd prefer to let cpio auto-detect it.
> > 
> > To get a full listing, either use "lsinitramfs -l", or write a command
> > that reads *all* of the CPIO archives, not just the first one.  I'd
> > advise using lsinitramfs -l, because it'll be a lot easier.
> 
> 
> Please post your console session showing how you created
> initrd.img-5.10.0-8-amd64.txt.gz.

I didn't.  It was created automatically when I installed dracut-core.

Prior to that, it was created automatically every time I did anything
with apt-get which touched the "low level stuff" (kernel, firmware,
microcode, busybox, other tools that live in the initrd, and so on).

Here's an example:

unicorn:~$ sudo apt-get purge dracut-core cryptsetup
[sudo] password for greg: 
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following packages will be REMOVED:
  cryptsetup* cryptsetup-initramfs* cryptsetup-run* dracut-core*
0 upgraded, 0 newly installed, 4 to remove and 0 not upgraded.
After this operation, 1,847 kB disk space will be freed.
Do you want to continue? [Y/n] 
(Reading database ... 157820 files and directories currently installed.)
Removing cryptsetup-run (2:2.3.5-1) ...
Removing cryptsetup-initramfs (2:2.3.5-1) ...
update-initramfs: deferring update (trigger activated)
Removing cryptsetup (2:2.3.5-1) ...
Removing dracut-core (051-1) ...
Processing triggers for man-db (2.9.4-2) ...
Processing triggers for initramfs-tools (0.140) ...
update-initramfs: Generating /boot/initrd.img-5.10.0-8-amd64
(Reading database ... 157360 files and directories currently installed.)
Purging configuration files for cryptsetup (2:2.3.5-1) ...
Purging configuration files for dracut-core (051-1) ...
Purging configuration files for cryptsetup-initramfs (2:2.3.5-1) ...
unicorn:~$ ls -l /boot/initrd*
-rw-r--r-- 1 root root 30924690 Jan 29  2021 /boot/initrd.img-4.19.0-13-amd64
-rw-r--r-- 1 root root 34310935 Jul 21 07:30 /boot/initrd.img-5.10.0-7-amd64
-rw-r--r-- 1 root root 39491974 Aug  2 14:26 /boot/initrd.img-5.10.0-8-amd64

Gah.  It's still inflated.

Re: Updating kernels impossible when /boot is getting full

[David Christensen]

On 8/1/21 3:51 PM, Greg Wooledge wrote:

On Sun, Aug 01, 2021 at 03:29:07PM -0700, David Christensen wrote:

2021-08-01 13:52:37 root@dipsy ~



# gunzip -c /boot/initrd.img-4.19.0-17-amd64 | cpio -i -d -H newc
--no-absolute-filenames
246741 blocks


That may not extract the full content of the initrd.  It only reads
one of the concatenated CPIO archives.  Also, the first archive may not
be gzipped.  Also also, hard-coding the input archive format is weird;
I'd prefer to let cpio auto-detect it.

To get a full listing, either use "lsinitramfs -l", or write a command
that reads *all* of the CPIO archives, not just the first one.  I'd
advise using lsinitramfs -l, because it'll be a lot easier.



Please post your console session showing how you created 
initrd.img-5.10.0-8-amd64.txt.gz.



David

Confirmacion Entrevistas Miercoles 11 de Agosto

[Karina Acosta Palacios]

Favor de contarnos sobre una situación en específico donde tuvo que actuar sin 
el consentimiento de su jefe.

Workshop:
Cómo Diseñar y Aplicar Entrevistas Laborales Conductuales y Situacionales
Online en Vivo
11 de Agosto 2021

El modelo de entrevista tradicional quedó en el pasado...
¡APRENDE DE MANERA PRÁCTICA CÓMO FORMULAR PREGUNTAS Y ESCENARIOS PARA 
DESARROLLAR ENTREVISTAS CONDUCTUALES Y SITUACIONALES!
 
DESCARGAR FOLLETO COMPLETO
>>>Deseo mayores informes a través de WhatsApp

Mayores informes comuníquese con alguno de nuestros ejecutivos:

Ciudad de México / 55 2450 6187
Guadalajara, Jal. / 33 2005 0994
Monterrey, N.L. / 81 2974 7731














 

Este boletín informativo tiene como objetivo generar valor en su Empresa, si 
usted y su Organización desean dejar de recibir este tipo de correo electrónico 
conteste con la palabra BAJACONDUCTUAL340. O en su defecto haga click en el 
siguiente enlace: unsubscribe from this list

Re: burn iso to usb

[Anssi Saari]

David Wright  writes:

> On Mon 02 Aug 2021 at 16:14:15 (+0300), Anssi Saari wrote:
>> Stefan Monnier  writes:
>> 
>> >>> > cp /path/to/file.iso /dev/sdX
>> >>> dd if=whatever.iso of=/dev/sdX  
>> >> It's up to taste.
>> >
>> > Not at all.  The only right answer is:
>> >
>> > pv -parIe /dev/sdX
>> 
>> Actually I'm not sure how good it is to have both -a and -r, pv doesn't
>> really show which rate counter is which...
>
> No need: the rate is far more variable than its average, as time passes.

I guess it depends. Before that comment I tried it on an old USB
stick. Read speed was pretty much constant if low. So I think it was the
left rate counter that showed current rate but wouldn't bet on it.

Re: listing initrd content

[David]

On Tue, 3 Aug 2021 at 01:45, David Wright  wrote:

> BTW I encrypt only /home and swap, and AFAICT my initrd.img doesn't
> contain crypt stuff except for /usr/bin/cryptroot-unlock (5686B).
> So I ignore a polite warning at every rebuild:
>
>   update-initramfs: Generating /boot/initrd.img-4.19.0-17-amd64
>   cryptsetup: WARNING: The initramfs image may not contain cryptsetup binaries
>   nor crypto modules. If that's on purpose, you may want to uninstall the
>   'cryptsetup-initramfs' package in order to disable the cryptsetup 
> initramfs
>   integration and avoid this warning.
>   Log ended: 2021-07-20  10:07:25

As the warning says, it and /usr/bin/cryptroot-unlock will go away
if you uninstall 'cryptsetup-initramfs', which is pulled in by 'cryptsetup',
which describes itself as a transitional dummy package that
can be removed. You probably only need 'cryptsetup-run' and
'cryptsetup-bin'. I learned this by running
  apt show 'cryptsetup*'
and tried it and it works fine where appropriate.

Re: what binds to port

[Brian]

On Mon 02 Aug 2021 at 17:35:46 +0200, Nicolas George wrote:

> Brian (12021-08-02):
> > Helpful remarks, but I did not think printers used kernel drivers.
> 
> AFAIR, USB printers appear as a special device, unlike generic USB
> devices, that makes one layer of drivers, but then you need an userland
> driver, probably GhostScript, to talk the proper language to that
> device, and that makes a second layer of drivers.

My thinking is that a USB printer uses libusb, just as a scanner does.
No kernel driver involved. The printer drivers are "internal" to CUPS.

-- 
Brian.

Re: Updating kernels impossible when /boot is getting full

[David Wright]

On Mon 02 Aug 2021 at 08:04:25 (+0300), Teemu Likonen wrote:
> * 2021-08-01 16:00:24-0400, Greg Wooledge wrote:
> 
> > Someone who knows what makes initrd images swell up, please step in
> > and advise. And no, it's not "try using a different compression
> > algorithm". It's something in the *content*.
> 
> Initrd image is large when the pairing kernel is compiled with debugging
> symbols. I can't tell if this is the case with the original poster.

I always thought they were in the System.map file, which is sizeable
but not excessive as far as 500MB is concerned.

> Large unneeded files can be deleted with "rm". It's rough but pretty
> much the only option if the package manager can't work anymore on a full
> partition. I would use "rm" to delete the oldest not running kernel and
> initrd file and update the kernel with package manager. Then I would
> delete the old kernel and related packages with the package manager.

That seems like a dangerous strategy here. We've had two upgrades of
the kernel recently where the version number hasn't changed. So you'd
be overwriting your sole kernel with the upgrade, and totally reliant
on that process working perfectly.

Cheers,
David.

Re: listing initrd content

[Greg Wooledge]

On Mon, Aug 02, 2021 at 10:45:25AM -0500, David Wright wrote:
> You posted here their precise sizes before you installed dracut.
> What's the size of your new initrd.img—has dracut done its job?

unicorn:~$ ls -l /boot/initrd*
-rw-r--r-- 1 root root 30924690 Jan 29  2021 /boot/initrd.img-4.19.0-13-amd64
-rw-r--r-- 1 root root 34310935 Jul 21 07:30 /boot/initrd.img-5.10.0-7-amd64
-rw-r--r-- 1 root root 40636944 Aug  2 07:24 /boot/initrd.img-5.10.0-8-amd64

For some reason, it only updated the "current" one.  It's 6 MB larger
now than it was before.

Re: burn iso to usb

[David Wright]

On Mon 02 Aug 2021 at 16:14:15 (+0300), Anssi Saari wrote:
> Stefan Monnier  writes:
> 
> >>> > cp /path/to/file.iso /dev/sdX
> >>> dd if=whatever.iso of=/dev/sdX  
> >> It's up to taste.
> >
> > Not at all.  The only right answer is:
> >
> > pv -parIe /dev/sdX
> 
> Actually I'm not sure how good it is to have both -a and -r, pv doesn't
> really show which rate counter is which...

No need: the rate is far more variable than its average, as time passes.

Cheers,
David.

Re: listing initrd content

[David Wright]

On Mon 02 Aug 2021 at 07:51:55 (-0400), Greg Wooledge wrote:
> On Mon, Aug 02, 2021 at 07:41:03AM -0400, The Wanderer wrote:
> > On 2021-08-02 at 07:25, Greg Wooledge wrote:
> > 
> > > unicorn:~$ lsinitrd /boot/initrd.img-5.10.0-8-amd64 | wc -l
> > > 1646
> > > unicorn:~$ lsinitramfs /boot/initrd.img-5.10.0-8-amd64 | wc -l
> > > 1635
> > > 
> > > Curious.
> > 
> > Try a diff between the lsinit* outputs? I don't have dracut-core
> > installed, or I'd run the test myself just out of curiosity.
> 
> I didn't have it either; I installed it specifically to test this thing.
> Unfortunately, installing it also brought in "cryptsetup" and related
> packages, which modified the initrd images.  Because of that, I don't
> recommend this test for anyone else.
> 
> unicorn:~$ lsinitramfs -l /boot/initrd.img-5.10.0-8-amd64 | head
> [ … ]
> unicorn:~$ lsinitrd /boot/initrd.img-5.10.0-8-amd64 | head
> [ … ]
> 
> At first glance, it looks like the difference in line count might be
> due to these headers and footers around each archive.
> 
> But if I actually do
> 
> diff -u <(lsinitramfs -l /boot/initrd.img-5.10.0-8-amd64) <(lsinitrd 
> /boot/initrd.img-5.10.0-8-amd64) | less
> 
> there are a whole bunch of other differences.  Some archive member files
> are moved around, which I cannot understand (the biggest offenders are
> the 0-length hard link indicators such as usr/bin/umount).  I'm not sure
> if those are the *only* differences, because there's so much noise due
> to that.

You posted here their precise sizes before you installed dracut.
What's the size of your new initrd.img—has dracut done its job?

  Package: dracut-core
  Description-md5: 5df7edfd996e6db7e65cd0435ed243c3
  Description-en: dracut is an event driven initramfs infrastructure (core 
tools)
   Unlike existing initramfs's, this is an attempt at having as little as
   possible hard-coded into the initramfs as possible.  The initramfs has
   (basically) one purpose in life -- getting the rootfs mounted so that
   we can transition to the real rootfs.  This is all driven off of
   device availability.  Therefore, instead of scripts hard-coded to do
   various things, we depend on udev to create device nodes for us and
   then when we have the rootfs's device node, we mount and carry on.
   Having the root on MD, LVM2, LUKS is supported as well as NFS, iSCSI,
   NBD and FCOE with dracut-network.

BTW I encrypt only /home and swap, and AFAICT my initrd.img doesn't
contain crypt stuff except for /usr/bin/cryptroot-unlock (5686B).
So I ignore a polite warning at every rebuild:

  update-initramfs: Generating /boot/initrd.img-4.19.0-17-amd64
  cryptsetup: WARNING: The initramfs image may not contain cryptsetup binaries 
  nor crypto modules. If that's on purpose, you may want to uninstall the 
  'cryptsetup-initramfs' package in order to disable the cryptsetup 
initramfs 
  integration and avoid this warning.
  Log ended: 2021-07-20  10:07:25

Cheers,
David.

Re: Updating kernels impossible when /boot is getting full

[David Wright]

On Sun 01 Aug 2021 at 13:21:11 (+0300), Ilkka Huotari wrote:
> Thanks. I should have said, that also apt-get autoremove fails:
> 
> $ sudo apt-get autoremove
> Reading package lists... Done
> Building dependency tree... Done
> Reading state information... Done
> 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
> 1 not fully installed or removed.
> After this operation, 0 B of additional disk space will be used.
> Setting up initramfs-tools (0.139ubuntu3) ...
> update-initramfs: deferring update (trigger activated)
> Processing triggers for initramfs-tools (0.139ubuntu3) ...
> update-initramfs: Generating /boot/initrd.img-5.11.0-25-generic
> Error 24 : Write error : cannot write compressed block
> E: mkinitramfs failure cpio 141 lz4 -9 -l 24
> update-initramfs: failed for /boot/initrd.img-5.11.0-25-generic with 1.
> dpkg: error processing package initramfs-tools (--configure):
>  installed initramfs-tools package post-installation script subprocess
> returned error exit status 1
> Errors were encountered while processing:
>  initramfs-tools
> E: Sub-process /usr/bin/dpkg returned an error code (1)
> 
> Maybe this is a bug in the dpkg?
> 
> This sounds like some disk (it's a few years old SSD) error, but I don't
> know:
> "Error 24 : Write error : cannot write compressed block"

If Ubuntu is parallelling Debian, I'd be very wary.

Would it be true to say that:
. You've got two kernels installed, 22 and 25, and 25 is running.
. You're trying to upgrade to a new version of 25, so the new
  version is overwriting the old one.

This is exactly why you need 22 as a backup, in case the new version
of 25 doesn't work, for whatever reason. So I would not remove it
unless you take action to be able to boot up with it from another
location.

Whatever you do now involves risk, so it's just a matter of choosing
the risk you can most easily cope with.

BTW, and AIUI, apt/dpkg doesn't like installing/removing packages
when the system is "broken", so it will try to finish configuring
that failed one first. This may explain your "bug".

I have no idea whether any of these alternatives would work:

. Copy initrd.img-5.11.0-25-generic somewhere safe and external,
  then delete it. Now reinstall 25, and the system should have
  room to rebuild the initrd.img.
  If it¹ doesn't work, restore the copy, and you've lost nothing.

. Reboot the system with 22. Now you can be more brutal with removing
  25's files in /boot, in order to either reinstall it, or remove and
  then install it.

. Copy the four *-5.11.0-22-generic files somewhere safe and external,
  then delete them. Now reinstall 25, and the system should have
  room to rebuild the initrd.img.
  If it¹ doesn't work, restore the copies, and you've lost nothing.

In addition to any of these, I would consider copying all the four
files for each installed kernel onto a safe, external device, and
adding a custom entry to /boot/grub/grub.cfg by means of
/etc/grub.d/40_custom,
copying the first menuentry, but mangling it so that it can find
the external device, and load the kernel-… and initrd.img-… from
there.

(NB I've no idea how ubuntu differs from debian.)

¹ "it" means the process just described.
  I don't mean "reboot the system and see if it works".
  Check everything is correctly back in place before rebooting.

Cheers,
David.

Re: what binds to port

[Nicolas George]

Brian (12021-08-02):
> Helpful remarks, but I did not think printers used kernel drivers.

AFAIR, USB printers appear as a special device, unlike generic USB
devices, that makes one layer of drivers, but then you need an userland
driver, probably GhostScript, to talk the proper language to that
device, and that makes a second layer of drivers.

Regards,

-- 
  Nicolas George


signature.asc
Description: PGP signature

Re: Updating kernels impossible when /boot is getting full

[Darac Marjal]

On 01/08/2021 23:51, Greg Wooledge wrote:
> On Sun, Aug 01, 2021 at 03:29:07PM -0700, David Christensen wrote:
>> 2021-08-01 13:52:37 root@dipsy ~
>> # file /boot/initrd.img-4.19.0-17-amd64
>> /boot/initrd.img-4.19.0-17-amd64: gzip compressed data, last modified: Sun
>> Jul 25 19:43:38 2021, from Unix, original size 126331392
> Your initrd image, *uncompressed*, is smaller than the OP's compressed
> images.  That should put to bed any more silly comments about "try
> switching from gzip to bzip2 or xz" that we always get whenever someone
> makes one of these threads.

I object slightly to the comments being "silly", but you are right
that,  although changing the compression will save some space, thinning
out the contents of the initrd is going to have a much bigger effect. I
stand corrected.




OpenPGP_signature
Description: OpenPGP digital signature

Re: what binds to port

[Brian]

On Mon 02 Aug 2021 at 10:36:22 +0200, Nicolas George wrote:

> Thomas Schmitt (12021-08-02):
> > Do you have any sg device left as suspect for the scanner's device file,
> > after you subtracted one for each hard disk and each optical drive ?
> > (I.e. are there two hard disks to occupy sg0 and sg1 and no other sgX left 
> > ?)
> 
> Have SCSI scanners been spotted since the 20th century, except in zoos?

I have one in captivity here :). 1990s vintage.
 
> Only USB mass storage devices are shown as SCSI devices, because they
> use mostly the same command set. Other USB devices either have their own
> kernel drivers (printers…) or appear as generic USB devices nodes to be
> accessed with libusb.

Helpful remarks, but I did not think printers used kernel drivers.

-- 
Brian.

Re: Google sites don't work

[Kleene, Steven (kleenesj)]

On Saturday, July 31, 2021 4:54 PM I wrote concerning firefox-esr:
> Neither translate.google.com nor images.google.com functions properly.

I have figured out the problem and solved it.

At some point I remembered that I have in place an old-fashioned way of
blocking sites.  In /etc/hosts, I have 68 entries of this sort:

127.0.0.1   ad.doubleclick.net

that redefine the URL of a pesky site to 127.0.0.1 (localhost).  Given a PC
at work that handles the Google sites well and a home machine that does not,
I compared the two /etc/hosts files.  The home (failing) machine had two
entries that the work (successful) machine did not:

127.0.0.1   gstatic.com
127.0.0.1   www.gstatic.com

I had added those in February, which is about when the failures began.  I
found that commenting out the second entry (www.gstatic.com) fixed my
problem, even if I left the first entry (gstatic.com) in place.

I also use a firefox add-on, Forget Me Not.  If I add *.gstatic.com to the
list of blocked sites, the Google sites still work.  This surprises me.  I
guess the /etc/hosts and Forget Me Not strategies must work at different
points.

Anyway, thanks to the three respondents for your replies.


From: Ivan Krylov 
Sent: Monday, August 2, 2021 8:51 AM
To: debian-user@lists.debian.org
Subject: Re: Google sites don't work

> Similar problem here, only with Google sites like Gmail, Docs, and
> Chat (via a[n?] university/Google system).

Interesting. Do you see any relevant errors if you press F12 and take a
look at the JavaScript console on the affected pages, compared to the
unaffected pages? What about the Network tab, any failed requests there?

--
Best regards,
Ivan

Re: Hard to understand, being clear [ was Re: MDs & Dentists]

[Gunnar Gervin]

Debian buster 32b i386 is the dysfunctional 1/2 part (that the scammer
might have access to until I am able to find acceptable dvd to burn 64bit
Debian 10.10 into (dropped Bullseye because of request I couldn't do; no
Grub)
So I can renew that half. For me a probable way to test different distros
and releases is simply a dualboot. I need now to build websites, not a
virtual machine.
I just didn't have a working PC -yet- that could build websites.
In Synaptic I found ASCII only.
Then I'd have to learn HTML? Heard about Wordpress & YAML
Geg

On Sun, 1 Aug 2021, 23:33 Polyna-Maude Racicot-Summerside, <
deb...@polynamaude.com> wrote:

> Hi,
> Here's some example of hard to understand posts...
> Maybe I ain't the only one following the thread, that tried to help
> Gunnar but got lost in the linguistics problems.
>
> On 2021-08-01 9:39 a.m., Gunnar Gervin wrote:
> > Dual boot'ed,
> > I forgot to tell you.
> > Thus the sucker(?) can sit 'alone' in a dysfunctional 1/2 of my PC,
> > maybe 'he' never returns anyway.
> *dysfunction 1/2 of your PC ?*
>
> Okay this could be related to the first sentence about dual booting.
> So you got one of the two system not working.
>
> Which one ?
> You know, how are we supposed to know.
>
> > After built up all in 1 'secret' 1/2, I plan to re-partition the 1t
> *all in 1 'secret' 1/2 ?*
>
> What is this supposed to mean
>
> > half, to clean out 'all' dysfunctions, in a Linux, & Linux Debian
> *clean out all dysfunction in a Linux & Linux Debian*
>
> So you have two Debian system ?
>
> > 'answer' to Factory Reset, a learning way, which FReset really isn't, or
> > little.
> *'answer' to Factory Reset* ?
>
> Where you answered what ?
>
> FReset ? Is it a typo for Reset or a way for you to say Factory Reset ?
>
> Trying to save a few letter won't help your case.
>
> Unless you are using a 300 baud modem, maybe you should let go the space
> saving acronym and use plain English.
>
> I won't go back to the list of messages...
>
> But here's one that is pretty much the top of line when we consider hard
> to understand.
>
> https://lists.debian.org/debian-user/2021/07/msg01033.html
>
> Thx for the request to help in this project even not knowing code. I'll
> firstly try it on my 14 yr old Debian Buster ex-macbook. Nice way to
> include more people &, probably, improve+stabilize the distro much faster.
> Learning Linux Debian is a nice hobby(feels more like a lifestyle)
>
> --
>
> *A ex-Macbook ? what make it change from a MacBook to a none-Macbook ?*
>
> https://lists.debian.org/debian-user/2021/07/msg01219.html
>
> >> On 2021-07-28 3:16 p.m., Gunnar Gervin wrote:
> >>> It is a Toshiba 160 gb hd in a 14 years old Macbook i386 ❤️/x86 32 b
> >>> booting from Bios not uefi. I'll give full report in 1-2 weeks, after
> >>> put in VM in it, faster internet to it to handle VM.
> >>> And built websites with it.
> >>> Geg
>
> 
>
> > One might assume from
> >
> > https://lists.debian.org/debian-user/2021/07/msg01033.html
> > https://lists.debian.org/debian-user/2021/07/msg01167.html
> >
> > that these deal with the same machine, and that Gunnar hasn't quite
> > mastered the technique of threading, but is keen to add to the
> > list of tested hardware.
> >
> One doesn't always read all the messages and only uses the subject to
> get a idea.
>
> Now is he saying his machine can WORK with Debian or is this related to
> the message I had with him earlier about a problem with his system NOT
> WORKING and CRASHING on update, requiring CLEAN REINSTALL.
>
> And this is the part that would be nice to know...
>
> 
>
> *And we still don't know !*
>
> > BR,
> > Geg.
> >
> > On Wed, 21 Jul 2021, 18:59 Dan Ritter,  > > wrote:
> >
> > Reco wrote:
> > > On Wed, Jul 21, 2021 at 10:51:40AM -0400, Celejar wrote:
> > > Numbers show that I was incorrect. Let's call it "unlikely"
> instead of
> > > "rare". Let the popcon graphs speak for themselves:
> > >
> > > https://qa.debian.org/popcon.php?package=firefox-esr
> > 
> > > vs
> > > https://qa.debian.org/popcon.php?package=openjdk-11
> > 
> >
> > Standard reminder: popcon vastly over-represents
> > individually-owned laptops and desktops over servers and
> > corporately-owned anything.
> >
> > In this case, individuals are sometimes infected with ransomware
> > by happenstance, but corporates are actually targets.
> >
> > > It won't by itself, of course. One sure way to beat ransomware is
> to
> > > take immutable backups (i.e. unmodifiable by host during and after
> the
> > > backup is taken), and as recent history shows us - ransomware
> victims
> > > apparently do not use this approach.
> >
> > Yes indeed.
> >
> > -dsr-
> >
>
> --
> Polyna-Maude R.-Summerside
> -Be smart, Be wise, Support opensource development
>
>

Re: Hard to understand, being clear [ was Re: MDs & Dentists]

[Gunnar Gervin]

My exMac looks like old Mac, but 1/2 of software/harddisk is Debian i386
32b Buster, another
1/2 of HD (Toshiba MK1655GS ssd 160gb, Intel, 3gb memory) is Linux Mint 32b
Ubuntu-based.
Wikipedia said it's the first Mac (Snow Leopard)to run on 64bit.
You asked what changed it from being a Macbook to an exmac.
Letting Linux Debian 10.9 take over 100% of 160gb software. It is now
impossible(?) to go back to Macbook 2.1 osx 10.6.8 Snow Leopard. The
hardware is Mac, which is the keyboard & screen.
Debian (& Mac) 'said' dvd player didn't work, neither the external dvd
player. Mint didn't 'complain'. The Apple symbol appears on screen starting
& a fanfare tune. Mac or not: Depends how you define it, external,
internal, both.
I didn't much think of it until now.
For me it's no longer a Mac. Because for me the main use of a computer is
the desktop look, the programs, the distribution. It's not a car, to get me
around. It's to get my brainwork done; it's main value is on the inside.
See?
BR,
Geg

BR,
Geg

On Sun, 1 Aug 2021, 23:33 Polyna-Maude Racicot-Summerside, <
deb...@polynamaude.com> wrote:

> Hi,
> Here's some example of hard to understand posts...
> Maybe I ain't the only one following the thread, that tried to help
> Gunnar but got lost in the linguistics problems.
>
> On 2021-08-01 9:39 a.m., Gunnar Gervin wrote:
> > Dual boot'ed,
> > I forgot to tell you.
> > Thus the sucker(?) can sit 'alone' in a dysfunctional 1/2 of my PC,
> > maybe 'he' never returns anyway.
> *dysfunction 1/2 of your PC ?*
>
> Okay this could be related to the first sentence about dual booting.
> So you got one of the two system not working.
>
> Which one ?
> You know, how are we supposed to know.
>
> > After built up all in 1 'secret' 1/2, I plan to re-partition the 1t
> *all in 1 'secret' 1/2 ?*
>
> What is this supposed to mean
>
> > half, to clean out 'all' dysfunctions, in a Linux, & Linux Debian
> *clean out all dysfunction in a Linux & Linux Debian*
>
> So you have two Debian system ?
>
> > 'answer' to Factory Reset, a learning way, which FReset really isn't, or
> > little.
> *'answer' to Factory Reset* ?
>
> Where you answered what ?
>
> FReset ? Is it a typo for Reset or a way for you to say Factory Reset ?
>
> Trying to save a few letter won't help your case.
>
> Unless you are using a 300 baud modem, maybe you should let go the space
> saving acronym and use plain English.
>
> I won't go back to the list of messages...
>
> But here's one that is pretty much the top of line when we consider hard
> to understand.
>
> https://lists.debian.org/debian-user/2021/07/msg01033.html
>
> Thx for the request to help in this project even not knowing code. I'll
> firstly try it on my 14 yr old Debian Buster ex-macbook. Nice way to
> include more people &, probably, improve+stabilize the distro much faster.
> Learning Linux Debian is a nice hobby(feels more like a lifestyle)
>
> --
>
> *A ex-Macbook ? what make it change from a MacBook to a none-Macbook ?*
>
> https://lists.debian.org/debian-user/2021/07/msg01219.html
>
> >> On 2021-07-28 3:16 p.m., Gunnar Gervin wrote:
> >>> It is a Toshiba 160 gb hd in a 14 years old Macbook i386 ❤️/x86 32 b
> >>> booting from Bios not uefi. I'll give full report in 1-2 weeks, after
> >>> put in VM in it, faster internet to it to handle VM.
> >>> And built websites with it.
> >>> Geg
>
> 
>
> > One might assume from
> >
> > https://lists.debian.org/debian-user/2021/07/msg01033.html
> > https://lists.debian.org/debian-user/2021/07/msg01167.html
> >
> > that these deal with the same machine, and that Gunnar hasn't quite
> > mastered the technique of threading, but is keen to add to the
> > list of tested hardware.
> >
> One doesn't always read all the messages and only uses the subject to
> get a idea.
>
> Now is he saying his machine can WORK with Debian or is this related to
> the message I had with him earlier about a problem with his system NOT
> WORKING and CRASHING on update, requiring CLEAN REINSTALL.
>
> And this is the part that would be nice to know...
>
> 
>
> *And we still don't know !*
>
> > BR,
> > Geg.
> >
> > On Wed, 21 Jul 2021, 18:59 Dan Ritter,  > > wrote:
> >
> > Reco wrote:
> > > On Wed, Jul 21, 2021 at 10:51:40AM -0400, Celejar wrote:
> > > Numbers show that I was incorrect. Let's call it "unlikely"
> instead of
> > > "rare". Let the popcon graphs speak for themselves:
> > >
> > > https://qa.debian.org/popcon.php?package=firefox-esr
> > 
> > > vs
> > > https://qa.debian.org/popcon.php?package=openjdk-11
> > 
> >
> > Standard reminder: popcon vastly over-represents
> > individually-owned laptops and desktops over servers and
> > corporately-owned anything.
> >
> > In this case, individuals are sometimes infected with ransomware
> > by happenstance, but corporates are actually targets.

Re: burn iso to usb

[Anssi Saari]

Stefan Monnier  writes:

>>> > cp /path/to/file.iso /dev/sdX
>>> dd if=whatever.iso of=/dev/sdX  
>> It's up to taste.
>
> Not at all.  The only right answer is:
>
> pv -parIe /dev/sdX

Actually I'm not sure how good it is to have both -a and -r, pv doesn't
really show which rate counter is which...

Re: MDs & Dentists

[Gunnar Gervin]

Scam:
Was from outside of this list.
This info because someone thought I accused this list.
Sorry for the confusion I made.
BR,
Geg.

On Sun, 1 Aug 2021, 23:46 Polyna-Maude Racicot-Summerside, <
deb...@polynamaude.com> wrote:

> Hi,
>
> On 2021-08-01 9:58 a.m., Gunnar Gervin wrote:
> > I expected that answer.
> > Debian is still 1/2 of it, but kinda dysfunctional, cos of me & scam
> > Trying to set up Debian in a VM in another Linux distro, with Chef
> > So I cannot really see irrelevance
> > of my question?? Like Nobody here knows how to fix this one, cos it's
> > slightly out of D. politics?
> > Geg
> >
>
> Not because of politics.
> Because you don't seem to take help when it's given to you.
>
> At least 3 persons (different ones) have gave you tips on how to
> properly identify the OS you are running over (not only Linux but the
> distribution itself) and been trying to find out what you are using.
>
> Including one person that wasn't sure if your laptop description was
> because it was running Bullseye and wanted to be added to the list of
> computer supported or something else.
>
> None got any answer.
>
> So this may be the start of the whole problem.
>
> Now if you have a belief that people are trying to scam you off, them I
> can assure you of two things.
>
> You probably aren't a interesting target unless you are a bank or some
> big corporation. And if it would be the case, you wouldn't be
> interacting this way on the mailing list.
>
> If you got offer by someone you don't know to pay 100$ and get refunded
> for BTC, then you are mostly the first person to blame. This trick has
> been around for a very long time, and it's quite public notoriety that
> the first thing to do is to hangup on those person.
>
> If you come here for help and put a doubt behind every answer that
> people will give you. Then it could be good to ask yourself why you came
> here first ?
>
> Maybe you never answered to the two other users who asked you to type
> some command on the shell so we can know what type of system you run,
> this way we'd know if it's Debian (as we don't seem to be sure yet) and
> what architecture too. Because you talked about ex-Macbook, using BIOS,
> etc... pretty unclear.
>
> Nobody can undo what happened in the past. But if you need help, the
> first thing will be some genuine cooperation from yourself. Or going out
> to your local computer store and paying someone to do the job.
>
> And surely stop using some acronym only you may understand. It's not a
> run against the clock. Take time to write complete word and people will
> maybe have more interest in helping too.
>
> Why shall we make effort if you don't do so. If all the energy we have
> is devoted trying to decrypt some message then there won't be any left
> for the computer helping part of the job.
>
> > On Sun, 1 Aug 2021, 16:50 Andrew M.A. Cater,  > > wrote:
> >
> > On Sun, Aug 01, 2021 at 04:30:45PM +0300, Gunnar Gervin wrote:
> > > Security.
> > > Rarely discussed in Linux(?)..
> > > Was scammed recently; naive me let a man w/Bad accent take over my
> > laptop
> > > to 'help refund BTC' & make me pay 100$.
> > > Because of that &/or me in Synaptic bloating (2 many) packages,
> > which led
> > > to "1t fix broken packages", "put in Debian 10.9 Netinst cdrom", &
> > "can't
> *lt fin broken packages* ?
> lt ?
>
> let ?
>
>
> > > find key file" messages (yes, all 3 !).
>
> find key file messages ?
>
> *yes, all 3!*
>
> what 3 ?
>
> > > After trying "all" workarounds, I installed another, more simple
> Linux
> > > distro, built up a new setup of relevant programs to build VM,
> > containers,
> > > websites, Debian iso image, & CHEF.
> >
> > Which distro - are you still using Debian?
>
> Again this question ?
>
> How many time will it take before getting a bit of cooperation !?
> >
> > If not, we can't really help you. Although many of us have run other
> > distributions in the past, all of the Debian/Ubuntu derivatives do
> > something slightly different - we can only really help with generic
> > Debian things. If we offer help with any other distribution, it's
> > only ever best efforts - Debian derivatives have their own support
> > infrastructure.
> >
> > > Now Chef asks me to give URL to continue setting up a VM etc.
> > > Plz advise &/or help to do it/this.
> >
> > It may not be relevant but the chef and chef-zero packages in Buster
> > appear
> > to no longer be packaged in Bullseye - the upcoming release due in
> > two weeks.
> >
> > Ask on a Chef list, perhaps?
> >
> A good shot would be to ask on a mailing list specific to this
> particular software (or a forum).
>
> > > BR,
> > > GEG
> >
> > All best, as ever,
> >
> > Andrew Cater
> >
> > >
> > > On Wed, 21 Jul 2021, 18:59 Dan Ritter,  > > wrote:
> > >
> > > > Reco 

Re: 32b upgrade to 64 b; Boot.plist

[Dan Ritter]

Gunnar Gervin wrote: 
> I meant
> "& run it all;
> VM, Docker containers, websites in/via a 24/7 Cloud service storage &
> website hotel provider".

Let's talk about the XY problem.

https://xyproblem.info/

Go read that, understand it, and then please come back and ask
questions.

-dsr-

Re: MDs & Dentists

[Gunnar Gervin]

I see.
It's now a dual boot;
Debian 10.9 i386 32b Buster (installed from netinst dvd), in which Synaptic
crashed 80%. Tried reinstall with above dvd, it was rejected, not sure why.
So I restored the machine with a DVD with Linux Mint, dual boot;
Debian above is 1/2 , Mint is 1/2 & set up Synaptic in Linux Mint, it works
fine, just like in Debian.
It is originally a Macbook 2.1, Intel, 2Core, 160GB, 3GB RAM, Version 3.0
Vesa Bios, 64 bit(!).
Seems to use a lot 32b software
Now I look for alternative VM builders to Chef. Synaptic programs seems
same in Mint as in Debian. Debian works better in this machine than LMDE4.
Mint runs better so far, than both Debian and Lmde4. But that's probably
cos of my total lack of knowledge of anything incl. doing Backups(!). I
took backups in Mac, not Linux.
Geg

On Sun, 1 Aug 2021, 23:46 Polyna-Maude Racicot-Summerside, <
deb...@polynamaude.com> wrote:

> Hi,
>
> On 2021-08-01 9:58 a.m., Gunnar Gervin wrote:
> > I expected that answer.
> > Debian is still 1/2 of it, but kinda dysfunctional, cos of me & scam
> > Trying to set up Debian in a VM in another Linux distro, with Chef
> > So I cannot really see irrelevance
> > of my question?? Like Nobody here knows how to fix this one, cos it's
> > slightly out of D. politics?
> > Geg
> >
>
> Not because of politics.
> Because you don't seem to take help when it's given to you.
>
> At least 3 persons (different ones) have gave you tips on how to
> properly identify the OS you are running over (not only Linux but the
> distribution itself) and been trying to find out what you are using.
>
> Including one person that wasn't sure if your laptop description was
> because it was running Bullseye and wanted to be added to the list of
> computer supported or something else.
>
> None got any answer.
>
> So this may be the start of the whole problem.
>
> Now if you have a belief that people are trying to scam you off, them I
> can assure you of two things.
>
> You probably aren't a interesting target unless you are a bank or some
> big corporation. And if it would be the case, you wouldn't be
> interacting this way on the mailing list.
>
> If you got offer by someone you don't know to pay 100$ and get refunded
> for BTC, then you are mostly the first person to blame. This trick has
> been around for a very long time, and it's quite public notoriety that
> the first thing to do is to hangup on those person.
>
> If you come here for help and put a doubt behind every answer that
> people will give you. Then it could be good to ask yourself why you came
> here first ?
>
> Maybe you never answered to the two other users who asked you to type
> some command on the shell so we can know what type of system you run,
> this way we'd know if it's Debian (as we don't seem to be sure yet) and
> what architecture too. Because you talked about ex-Macbook, using BIOS,
> etc... pretty unclear.
>
> Nobody can undo what happened in the past. But if you need help, the
> first thing will be some genuine cooperation from yourself. Or going out
> to your local computer store and paying someone to do the job.
>
> And surely stop using some acronym only you may understand. It's not a
> run against the clock. Take time to write complete word and people will
> maybe have more interest in helping too.
>
> Why shall we make effort if you don't do so. If all the energy we have
> is devoted trying to decrypt some message then there won't be any left
> for the computer helping part of the job.
>
> > On Sun, 1 Aug 2021, 16:50 Andrew M.A. Cater,  > > wrote:
> >
> > On Sun, Aug 01, 2021 at 04:30:45PM +0300, Gunnar Gervin wrote:
> > > Security.
> > > Rarely discussed in Linux(?)..
> > > Was scammed recently; naive me let a man w/Bad accent take over my
> > laptop
> > > to 'help refund BTC' & make me pay 100$.
> > > Because of that &/or me in Synaptic bloating (2 many) packages,
> > which led
> > > to "1t fix broken packages", "put in Debian 10.9 Netinst cdrom", &
> > "can't
> *lt fin broken packages* ?
> lt ?
>
> let ?
>
>
> > > find key file" messages (yes, all 3 !).
>
> find key file messages ?
>
> *yes, all 3!*
>
> what 3 ?
>
> > > After trying "all" workarounds, I installed another, more simple
> Linux
> > > distro, built up a new setup of relevant programs to build VM,
> > containers,
> > > websites, Debian iso image, & CHEF.
> >
> > Which distro - are you still using Debian?
>
> Again this question ?
>
> How many time will it take before getting a bit of cooperation !?
> >
> > If not, we can't really help you. Although many of us have run other
> > distributions in the past, all of the Debian/Ubuntu derivatives do
> > something slightly different - we can only really help with generic
> > Debian things. If we offer help with any other distribution, it's
> > only ever best efforts - Debian derivatives have their own support
> > infrastructure.
> >
> > 

Re: Google sites don't work

[Ivan Krylov]

> Similar problem here, only with Google sites like Gmail, Docs, and
> Chat (via a[n?] university/Google system).

Interesting. Do you see any relevant errors if you press F12 and take a
look at the JavaScript console on the affected pages, compared to the
unaffected pages? What about the Network tab, any failed requests there?

-- 
Best regards,
Ivan

Re: Google sites don't work

[Kent West]

On Sun, Aug 1, 2021 at 11:17 AM Kleene, Steven (kleenesj) <
kleen...@ucmail.uc.edu> wrote:

> On Saturday, July 31, 2021 4:54 PM I wrote concerning firefox-esr:
> >> Neither translate.google.com nor images.google.com functions properly.
>

Similar problem here, only with Google sites like Gmail, Docs, and Chat
(via a[n?] university/Google system).

I don't know that it's the same problem though. It only affects Firefox.
I've tried Debian Buster (with a moved .mozilla directory) on my desktop PC
and Debian Buster on a laptop, and at least three Windows computers, two of
which are in a different building (one on same VLAN as my desktop & laptop;
one on a different VLAN).

It only fails when using a wired Ethernet connection; if I unplug and use
wireless, those sites work. But our network folks haven't found an issue
(so far - it's summer time, and students are gone, and few-ish folks use
Firefox, so we haven't had a whole lot of complaints, forcing the issue).

It's really frustrating, 'cause I don't like using non-Firefox browsers,
but I'm having to use Chromium to type this message, 'cause FF has just
become unusable for me, when using Google products. As far as I can
discern, FF works fine on every other site/product.

-- 
Kent West<")))><
Westing Peacefully - http://kentwest.blogspot.com

Re: 32b upgrade to 64 b; Boot.plist

[Gunnar Gervin]

I meant
"& run it all;
VM, Docker containers, websites in/via a 24/7 Cloud service storage &
website hotel provider".
Geg

On Mon, 2 Aug 2021, 15:11 Gunnar Gervin,  wrote:

> Mac 2.1 2007. Version: 3.O, PVT
> Vesa Bios, Intel 82945 GM
> Notebook Mac 4208 VAA
> Software Rev: 256 Modes: 36
> Bootloader: Isolinux
> 2 Core 64 bit Mem: 3055 MB
> Needs now:
> VM builder alternatives to CHEF.
> BR,
> Geg.
>
> On Sat, 31 Jul 2021, 16:02 Gunnar Gervin,  wrote:
>
>> Tried Virtual Machine it, but the DVD player doesn work, cannot unzip (to
>> download & use Etcher to burn USB), Multiwriter doesn`t work.
>>
>> On Sat, 31 Jul 2021 at 14:59, Gunnar Gervin  wrote:
>>
>>> Andy,
>>> Thx for answering.
>>> I don't know which of them it is, except for a Macbook.
>>> It was a OS X 10.6.8 Snow Leopard.
>>> But it isn't a Mac now; it is a Debian 10.9 Buster w/ a 160 GB ATA
>>> Toshiba 1655GS. Many Mac hotkeys work, so some Mac software is left in it.
>>>
>>> https://www.hdsentinel.com/storageinfo_details.php?lang=en=TOSHIBA%20MK1655GSX
>>> https://support.apple.com/kb/SP575?locale=en_US
>>> Seems it is 64 Bit totally or in parts 64, parts 32.
>>> But my dvd player has stopped working, and it won't use the external dvd
>>> player; doesn`t see it seems.
>>> Multiwriter won't mount, which is requested before burning it to USB
>>> Flash drive. `Cause Multiwriter is not listed when clicking Mount.
>>> Terminal cannot burn the (lengthy) path in downloads. Basically the
>>> computer gets worse little by little.
>>> geg
>>>
>>> On Fri, 30 Jul 2021 at 16:40, Andrew M.A. Cater 
>>> wrote:
>>>
 On Fri, Jul 30, 2021 at 06:53:18AM +0200, Gunnar Gervin wrote:
 > Hi beautiful ideals!
 > Decided to install Virtual Machine & Docker in this 14 year old
 ex-Macbook.
 > In which I installed Debian "Buster" i386 32 bits. As some of you
 know, I
 > did some failures during installation, the dvd player "hung" a bit
 several
 > times, so I saw it installing at least 3 times. I made a puzzling
 > observation: 64 came up a lot of times, but the machine seemed to
 handle
 > it. ("Is it 64 bits anyway?" I wondered.)
 > Now I found the following information in Wikipedia:
 > " Mac OS X 10.6 
 is
 > the first version of macOS  that
 > supports a 64-bit kernel <
 https://en.wikipedia.org/wiki/Kernel_(computing)>.
 > "
 > n Snow Leopard, most built-in applications have been rebuilt to use
 the
 > 64-bit x86-64  architecture
 > 
 (excluding
 > iTunes , Front Row
 > , Grapher
 >  and DVD Player
 > 
 applications).[43]
 > 
 They
 > will run in 32-bit  mode on
 machines
 > with 32-bit processors, and in 64-bit mode on machines with 64-bit
 > processors.
 > A change to the com.apple.Boot.plist will also enable users with
 compatible
 > computers to permanently boot into 64-bit for those wishing to do so.
 > After upgrading the kernel from 32b to 64b, if advisable & possible.
 > How to do that? Clean reinstall I guess optional, but will that
 suffice?
 > Geg

 Straightforwardly:

 Which _model_ Macbook is it? [About this Mac under MacOS]

 If you run hwinfo under Debian- what does it say?

 If you run cpuinfo under Debian - what does it say

 For Macs of this vintage: (2006/2007 Core 2 Duo)

 iMac 5,1 – iMac 5,2 – iMac 6,1
 Macbook 2,1
 MacBook Pro 2,1 – MacBook Pro 2,2
 Mac Pro 1,1
 Xserve 1,1 (maybe)

 They have a 32 bit EFI and a 64 bit processor.

 You might want to try with the Debian multi-arch CD which might sort it
 out.


 https://cdimage.debian.org/debian-cd/current/multi-arch/iso-cd/debian-10.10.0-amd64-i386-netinst.iso

 or, in exceptional cases for only a couple of models:


 https://cdimage.debian.org/debian-cd/current/amd64/iso-cd/debian-mac-10.10.0-amd64-netinst.iso

 If you only have a small amount of memory, you may want to consider
 that
 running virtual machines / Docker may be quite frustrating.

 Hope this helps

 All the very best as ever,

 Andy Cater

Re: 32b upgrade to 64 b; Boot.plist

[Dan Ritter]

Gunnar Gervin wrote: 
> Mac 2.1 2007. Version: 3.O, PVT
> Vesa Bios, Intel 82945 GM
> Notebook Mac 4208 VAA
> Software Rev: 256 Modes: 36
> Bootloader: Isolinux
> 2 Core 64 bit Mem: 3055 MB
> Needs now:
> VM builder alternatives to CHEF.

Chef is not a VM builder, although it can be used that way.

Consider virt-p2v to convert a real machine, or fai, ansible or
nix for varying kinds of reproducible automated installs.

-dsr-

Re: 32b upgrade to 64 b; Boot.plist

[Gunnar Gervin]

Can't I just build VM/Docker & websites in the 3gb memory computer, & host
it all in Cloud?
Geg

On Mon, 2 Aug 2021, 15:11 Gunnar Gervin,  wrote:

> Mac 2.1 2007. Version: 3.O, PVT
> Vesa Bios, Intel 82945 GM
> Notebook Mac 4208 VAA
> Software Rev: 256 Modes: 36
> Bootloader: Isolinux
> 2 Core 64 bit Mem: 3055 MB
> Needs now:
> VM builder alternatives to CHEF.
> BR,
> Geg.
>
> On Sat, 31 Jul 2021, 16:02 Gunnar Gervin,  wrote:
>
>> Tried Virtual Machine it, but the DVD player doesn work, cannot unzip (to
>> download & use Etcher to burn USB), Multiwriter doesn`t work.
>>
>> On Sat, 31 Jul 2021 at 14:59, Gunnar Gervin  wrote:
>>
>>> Andy,
>>> Thx for answering.
>>> I don't know which of them it is, except for a Macbook.
>>> It was a OS X 10.6.8 Snow Leopard.
>>> But it isn't a Mac now; it is a Debian 10.9 Buster w/ a 160 GB ATA
>>> Toshiba 1655GS. Many Mac hotkeys work, so some Mac software is left in it.
>>>
>>> https://www.hdsentinel.com/storageinfo_details.php?lang=en=TOSHIBA%20MK1655GSX
>>> https://support.apple.com/kb/SP575?locale=en_US
>>> Seems it is 64 Bit totally or in parts 64, parts 32.
>>> But my dvd player has stopped working, and it won't use the external dvd
>>> player; doesn`t see it seems.
>>> Multiwriter won't mount, which is requested before burning it to USB
>>> Flash drive. `Cause Multiwriter is not listed when clicking Mount.
>>> Terminal cannot burn the (lengthy) path in downloads. Basically the
>>> computer gets worse little by little.
>>> geg
>>>
>>> On Fri, 30 Jul 2021 at 16:40, Andrew M.A. Cater 
>>> wrote:
>>>
 On Fri, Jul 30, 2021 at 06:53:18AM +0200, Gunnar Gervin wrote:
 > Hi beautiful ideals!
 > Decided to install Virtual Machine & Docker in this 14 year old
 ex-Macbook.
 > In which I installed Debian "Buster" i386 32 bits. As some of you
 know, I
 > did some failures during installation, the dvd player "hung" a bit
 several
 > times, so I saw it installing at least 3 times. I made a puzzling
 > observation: 64 came up a lot of times, but the machine seemed to
 handle
 > it. ("Is it 64 bits anyway?" I wondered.)
 > Now I found the following information in Wikipedia:
 > " Mac OS X 10.6 
 is
 > the first version of macOS  that
 > supports a 64-bit kernel <
 https://en.wikipedia.org/wiki/Kernel_(computing)>.
 > "
 > n Snow Leopard, most built-in applications have been rebuilt to use
 the
 > 64-bit x86-64  architecture
 > 
 (excluding
 > iTunes , Front Row
 > , Grapher
 >  and DVD Player
 > 
 applications).[43]
 > 
 They
 > will run in 32-bit  mode on
 machines
 > with 32-bit processors, and in 64-bit mode on machines with 64-bit
 > processors.
 > A change to the com.apple.Boot.plist will also enable users with
 compatible
 > computers to permanently boot into 64-bit for those wishing to do so.
 > After upgrading the kernel from 32b to 64b, if advisable & possible.
 > How to do that? Clean reinstall I guess optional, but will that
 suffice?
 > Geg

 Straightforwardly:

 Which _model_ Macbook is it? [About this Mac under MacOS]

 If you run hwinfo under Debian- what does it say?

 If you run cpuinfo under Debian - what does it say

 For Macs of this vintage: (2006/2007 Core 2 Duo)

 iMac 5,1 – iMac 5,2 – iMac 6,1
 Macbook 2,1
 MacBook Pro 2,1 – MacBook Pro 2,2
 Mac Pro 1,1
 Xserve 1,1 (maybe)

 They have a 32 bit EFI and a 64 bit processor.

 You might want to try with the Debian multi-arch CD which might sort it
 out.


 https://cdimage.debian.org/debian-cd/current/multi-arch/iso-cd/debian-10.10.0-amd64-i386-netinst.iso

 or, in exceptional cases for only a couple of models:


 https://cdimage.debian.org/debian-cd/current/amd64/iso-cd/debian-mac-10.10.0-amd64-netinst.iso

 If you only have a small amount of memory, you may want to consider
 that
 running virtual machines / Docker may be quite frustrating.

 Hope this helps

 All the very best as ever,

 Andy Cater

Re: 32b upgrade to 64 b; Boot.plist

[Gunnar Gervin]

Are there alternatives to VM, & does it help w/external ssd 1tb?
Are external RAM available?
Geg

On Mon, 2 Aug 2021, 15:11 Gunnar Gervin,  wrote:

> Mac 2.1 2007. Version: 3.O, PVT
> Vesa Bios, Intel 82945 GM
> Notebook Mac 4208 VAA
> Software Rev: 256 Modes: 36
> Bootloader: Isolinux
> 2 Core 64 bit Mem: 3055 MB
> Needs now:
> VM builder alternatives to CHEF.
> BR,
> Geg.
>
> On Sat, 31 Jul 2021, 16:02 Gunnar Gervin,  wrote:
>
>> Tried Virtual Machine it, but the DVD player doesn work, cannot unzip (to
>> download & use Etcher to burn USB), Multiwriter doesn`t work.
>>
>> On Sat, 31 Jul 2021 at 14:59, Gunnar Gervin  wrote:
>>
>>> Andy,
>>> Thx for answering.
>>> I don't know which of them it is, except for a Macbook.
>>> It was a OS X 10.6.8 Snow Leopard.
>>> But it isn't a Mac now; it is a Debian 10.9 Buster w/ a 160 GB ATA
>>> Toshiba 1655GS. Many Mac hotkeys work, so some Mac software is left in it.
>>>
>>> https://www.hdsentinel.com/storageinfo_details.php?lang=en=TOSHIBA%20MK1655GSX
>>> https://support.apple.com/kb/SP575?locale=en_US
>>> Seems it is 64 Bit totally or in parts 64, parts 32.
>>> But my dvd player has stopped working, and it won't use the external dvd
>>> player; doesn`t see it seems.
>>> Multiwriter won't mount, which is requested before burning it to USB
>>> Flash drive. `Cause Multiwriter is not listed when clicking Mount.
>>> Terminal cannot burn the (lengthy) path in downloads. Basically the
>>> computer gets worse little by little.
>>> geg
>>>
>>> On Fri, 30 Jul 2021 at 16:40, Andrew M.A. Cater 
>>> wrote:
>>>
 On Fri, Jul 30, 2021 at 06:53:18AM +0200, Gunnar Gervin wrote:
 > Hi beautiful ideals!
 > Decided to install Virtual Machine & Docker in this 14 year old
 ex-Macbook.
 > In which I installed Debian "Buster" i386 32 bits. As some of you
 know, I
 > did some failures during installation, the dvd player "hung" a bit
 several
 > times, so I saw it installing at least 3 times. I made a puzzling
 > observation: 64 came up a lot of times, but the machine seemed to
 handle
 > it. ("Is it 64 bits anyway?" I wondered.)
 > Now I found the following information in Wikipedia:
 > " Mac OS X 10.6 
 is
 > the first version of macOS  that
 > supports a 64-bit kernel <
 https://en.wikipedia.org/wiki/Kernel_(computing)>.
 > "
 > n Snow Leopard, most built-in applications have been rebuilt to use
 the
 > 64-bit x86-64  architecture
 > 
 (excluding
 > iTunes , Front Row
 > , Grapher
 >  and DVD Player
 > 
 applications).[43]
 > 
 They
 > will run in 32-bit  mode on
 machines
 > with 32-bit processors, and in 64-bit mode on machines with 64-bit
 > processors.
 > A change to the com.apple.Boot.plist will also enable users with
 compatible
 > computers to permanently boot into 64-bit for those wishing to do so.
 > After upgrading the kernel from 32b to 64b, if advisable & possible.
 > How to do that? Clean reinstall I guess optional, but will that
 suffice?
 > Geg

 Straightforwardly:

 Which _model_ Macbook is it? [About this Mac under MacOS]

 If you run hwinfo under Debian- what does it say?

 If you run cpuinfo under Debian - what does it say

 For Macs of this vintage: (2006/2007 Core 2 Duo)

 iMac 5,1 – iMac 5,2 – iMac 6,1
 Macbook 2,1
 MacBook Pro 2,1 – MacBook Pro 2,2
 Mac Pro 1,1
 Xserve 1,1 (maybe)

 They have a 32 bit EFI and a 64 bit processor.

 You might want to try with the Debian multi-arch CD which might sort it
 out.


 https://cdimage.debian.org/debian-cd/current/multi-arch/iso-cd/debian-10.10.0-amd64-i386-netinst.iso

 or, in exceptional cases for only a couple of models:


 https://cdimage.debian.org/debian-cd/current/amd64/iso-cd/debian-mac-10.10.0-amd64-netinst.iso

 If you only have a small amount of memory, you may want to consider
 that
 running virtual machines / Docker may be quite frustrating.

 Hope this helps

 All the very best as ever,

 Andy Cater

Re: 32b upgrade to 64 b; Boot.plist

[Gunnar Gervin]

Mac 2.1 2007. Version: 3.O, PVT
Vesa Bios, Intel 82945 GM
Notebook Mac 4208 VAA
Software Rev: 256 Modes: 36
Bootloader: Isolinux
2 Core 64 bit Mem: 3055 MB
Needs now:
VM builder alternatives to CHEF.
BR,
Geg.

On Sat, 31 Jul 2021, 16:02 Gunnar Gervin,  wrote:

> Tried Virtual Machine it, but the DVD player doesn work, cannot unzip (to
> download & use Etcher to burn USB), Multiwriter doesn`t work.
>
> On Sat, 31 Jul 2021 at 14:59, Gunnar Gervin  wrote:
>
>> Andy,
>> Thx for answering.
>> I don't know which of them it is, except for a Macbook.
>> It was a OS X 10.6.8 Snow Leopard.
>> But it isn't a Mac now; it is a Debian 10.9 Buster w/ a 160 GB ATA
>> Toshiba 1655GS. Many Mac hotkeys work, so some Mac software is left in it.
>>
>> https://www.hdsentinel.com/storageinfo_details.php?lang=en=TOSHIBA%20MK1655GSX
>> https://support.apple.com/kb/SP575?locale=en_US
>> Seems it is 64 Bit totally or in parts 64, parts 32.
>> But my dvd player has stopped working, and it won't use the external dvd
>> player; doesn`t see it seems.
>> Multiwriter won't mount, which is requested before burning it to USB
>> Flash drive. `Cause Multiwriter is not listed when clicking Mount.
>> Terminal cannot burn the (lengthy) path in downloads. Basically the
>> computer gets worse little by little.
>> geg
>>
>> On Fri, 30 Jul 2021 at 16:40, Andrew M.A. Cater 
>> wrote:
>>
>>> On Fri, Jul 30, 2021 at 06:53:18AM +0200, Gunnar Gervin wrote:
>>> > Hi beautiful ideals!
>>> > Decided to install Virtual Machine & Docker in this 14 year old
>>> ex-Macbook.
>>> > In which I installed Debian "Buster" i386 32 bits. As some of you
>>> know, I
>>> > did some failures during installation, the dvd player "hung" a bit
>>> several
>>> > times, so I saw it installing at least 3 times. I made a puzzling
>>> > observation: 64 came up a lot of times, but the machine seemed to
>>> handle
>>> > it. ("Is it 64 bits anyway?" I wondered.)
>>> > Now I found the following information in Wikipedia:
>>> > " Mac OS X 10.6 
>>> is
>>> > the first version of macOS  that
>>> > supports a 64-bit kernel <
>>> https://en.wikipedia.org/wiki/Kernel_(computing)>.
>>> > "
>>> > n Snow Leopard, most built-in applications have been rebuilt to use the
>>> > 64-bit x86-64  architecture
>>> > 
>>> (excluding
>>> > iTunes , Front Row
>>> > , Grapher
>>> >  and DVD Player
>>> > 
>>> applications).[43]
>>> > 
>>> They
>>> > will run in 32-bit  mode on
>>> machines
>>> > with 32-bit processors, and in 64-bit mode on machines with 64-bit
>>> > processors.
>>> > A change to the com.apple.Boot.plist will also enable users with
>>> compatible
>>> > computers to permanently boot into 64-bit for those wishing to do so.
>>> > After upgrading the kernel from 32b to 64b, if advisable & possible.
>>> > How to do that? Clean reinstall I guess optional, but will that
>>> suffice?
>>> > Geg
>>>
>>> Straightforwardly:
>>>
>>> Which _model_ Macbook is it? [About this Mac under MacOS]
>>>
>>> If you run hwinfo under Debian- what does it say?
>>>
>>> If you run cpuinfo under Debian - what does it say
>>>
>>> For Macs of this vintage: (2006/2007 Core 2 Duo)
>>>
>>> iMac 5,1 – iMac 5,2 – iMac 6,1
>>> Macbook 2,1
>>> MacBook Pro 2,1 – MacBook Pro 2,2
>>> Mac Pro 1,1
>>> Xserve 1,1 (maybe)
>>>
>>> They have a 32 bit EFI and a 64 bit processor.
>>>
>>> You might want to try with the Debian multi-arch CD which might sort it
>>> out.
>>>
>>>
>>> https://cdimage.debian.org/debian-cd/current/multi-arch/iso-cd/debian-10.10.0-amd64-i386-netinst.iso
>>>
>>> or, in exceptional cases for only a couple of models:
>>>
>>>
>>> https://cdimage.debian.org/debian-cd/current/amd64/iso-cd/debian-mac-10.10.0-amd64-netinst.iso
>>>
>>> If you only have a small amount of memory, you may want to consider that
>>> running virtual machines / Docker may be quite frustrating.
>>>
>>> Hope this helps
>>>
>>> All the very best as ever,
>>>
>>> Andy Cater
>>>
>>>

Re: what binds to port

[Brian]

On Mon 02 Aug 2021 at 13:21:22 +0200, Thomas Schmitt wrote:

> Hi,
> 
> Brian wrote:
> > Isn't /dev/sg0 the block device?
> 
> /dev/sgX are character devices.
> 
>   https://tldp.org/HOWTO/SCSI-Generic-HOWTO/intro.html
> says
>   "The driver's purpose is to allow SCSI commands to be sent directly to
>SCSI devices. [...] Various specialized applications for writing
>CD-Rs and document scanning use the sg driver."
> 
> This is still the case for optical drives (sr) and hard discs (sd) which get
> an sg device file additionaly to their block device file. But it seems that
> the statement about "document scanning" could need an update.
> 
> 
> The main call for sg devices is ioclt(SG_IO) which performs a single SCSI
> command transaction.
> Since about 15 years it is possible to use it directly with a /dev/srX
> device file. But a bug introduced in a late version of kernel 2.6 prevented
> concurrent use of SG_IO on multiple sr devices. This ended with
>   https://github.com/torvalds/linux/commit/51a8588
> which i assume went into kernel version 5.6.
> So with the currently released Debian versions, /dev/sgX is still of use
> if there is more than one sr device.

I misread sr0 as sg0; sorry to have put you to the trouble of posting.
On the bright side, you have helped clear up a misconception of mine.

-- 
Brian.

Re: listing initrd content

[The Wanderer]

On 2021-08-02 at 07:51, Greg Wooledge wrote:

> On Mon, Aug 02, 2021 at 07:41:03AM -0400, The Wanderer wrote:
>
>> On 2021-08-02 at 07:25, Greg Wooledge wrote:
>> 
>> > unicorn:~$ lsinitrd /boot/initrd.img-5.10.0-8-amd64 | wc -l
>> > 1646
>> > unicorn:~$ lsinitramfs /boot/initrd.img-5.10.0-8-amd64 | wc -l
>> > 1635
>> > 
>> > Curious.
>> 
>> Try a diff between the lsinit* outputs? I don't have dracut-core
>> installed, or I'd run the test myself just out of curiosity.
> 
> I didn't have it either; I installed it specifically to test this thing.
> Unfortunately, installing it also brought in "cryptsetup" and related
> packages, which modified the initrd images.  Because of that, I don't
> recommend this test for anyone else.

dracut-core has cryptsetup in Recommends:, so that could be avoided with
--no-install-recommends. Maybe try removing dracut-core, 'apt-get
autoremove' / 'apt-get remove $(deborphan)' etc. till nothing new is
removed, then install dracut-core again without Recommends and see if
that improves things any?

That's a bigger and more drastic operation than it sounded like when I
started writing out the steps, though, so maybe not worth bothering with.

-- 
   The Wanderer

The reasonable man adapts himself to the world; the unreasonable one
persists in trying to adapt the world to himself. Therefore all
progress depends on the unreasonable man. -- George Bernard Shaw



signature.asc
Description: OpenPGP digital signature

Re: listing initrd content

[Greg Wooledge]

On Mon, Aug 02, 2021 at 07:41:03AM -0400, The Wanderer wrote:
> On 2021-08-02 at 07:25, Greg Wooledge wrote:
> 
> > unicorn:~$ lsinitrd /boot/initrd.img-5.10.0-8-amd64 | wc -l
> > 1646
> > unicorn:~$ lsinitramfs /boot/initrd.img-5.10.0-8-amd64 | wc -l
> > 1635
> > 
> > Curious.
> 
> Try a diff between the lsinit* outputs? I don't have dracut-core
> installed, or I'd run the test myself just out of curiosity.

I didn't have it either; I installed it specifically to test this thing.
Unfortunately, installing it also brought in "cryptsetup" and related
packages, which modified the initrd images.  Because of that, I don't
recommend this test for anyone else.

unicorn:~$ lsinitramfs -l /boot/initrd.img-5.10.0-8-amd64 | head
drwxr-xr-x   2 root root0 Apr 25 08:00 kernel
drwxr-xr-x   2 root root0 Apr 25 08:00 kernel/x86
drwxr-xr-x   2 root root0 Apr 25 08:00 kernel/x86/microcode
drwxr-xr-x   2 root root0 Apr 25 08:00 
kernel/x86/microcode/.enuineIntel.align.0123456789abc
-rw-r--r--   1 root root  4609024 Apr 25 08:00 
kernel/x86/microcode/GenuineIntel.bin
drwxr-xr-x   8 root root0 Aug  2 07:24 .
lrwxrwxrwx   1 root root7 Aug  2 07:24 bin -> usr/bin
drwxr-xr-x   3 root root0 Aug  2 07:24 conf
-rw-r--r--   1 root root   16 Aug  2 07:24 conf/arch.conf
drwxr-xr-x   2 root root0 Aug  2 07:24 conf/conf.d

unicorn:~$ lsinitrd /boot/initrd.img-5.10.0-8-amd64 | head
Image: /boot/initrd.img-5.10.0-8-amd64: 39M

Early CPIO image

drwxr-xr-x   2 root root0 Apr 25 08:00 kernel
drwxr-xr-x   2 root root0 Apr 25 08:00 kernel/x86
drwxr-xr-x   2 root root0 Apr 25 08:00 kernel/x86/microcode
drwxr-xr-x   2 root root0 Apr 25 08:00 
kernel/x86/microcode/.enuineIntel.align.0123456789abc
-rw-r--r--   1 root root  4609024 Apr 25 08:00 
kernel/x86/microcode/GenuineIntel.bin


At first glance, it looks like the difference in line count might be
due to these headers and footers around each archive.

But if I actually do

diff -u <(lsinitramfs -l /boot/initrd.img-5.10.0-8-amd64) <(lsinitrd 
/boot/initrd.img-5.10.0-8-amd64) | less

there are a whole bunch of other differences.  Some archive member files
are moved around, which I cannot understand (the biggest offenders are
the 0-length hard link indicators such as usr/bin/umount).  I'm not sure
if those are the *only* differences, because there's so much noise due
to that.

Re: listing initrd content

[The Wanderer]

On 2021-08-02 at 07:25, Greg Wooledge wrote:

> unicorn:~$ lsinitrd /boot/initrd.img-5.10.0-8-amd64 | wc -l
> 1646
> unicorn:~$ lsinitramfs /boot/initrd.img-5.10.0-8-amd64 | wc -l
> 1635
> 
> Curious.

Try a diff between the lsinit* outputs? I don't have dracut-core
installed, or I'd run the test myself just out of curiosity.

-- 
   The Wanderer

The reasonable man adapts himself to the world; the unreasonable one
persists in trying to adapt the world to himself. Therefore all
progress depends on the unreasonable man. -- George Bernard Shaw



signature.asc
Description: OpenPGP digital signature

Re: listing initrd content (was: Updating kernels impossible...)

[Greg Wooledge]

On Mon, Aug 02, 2021 at 01:20:13AM -0400, Felix Miata wrote:
> David Christensen composed on 2021-08-01 15:29 (UTC-0700):
> 
> > 2021-08-01 14:10:24 root@dipsy /tmp/initrd.img-4.19.0-17-amd64
> > # gunzip -c /boot/initrd.img-4.19.0-17-amd64 | cpio -i -d -H newc 
> > --no-absolute-filenames
> > 246741 blocks
>   
> 
> If only searching whether a string is contained therein, or wanting a list,
> it can be simpler:
> 
> # uname -v
> #1 SMP Debian 5.10.46-3 (2021-07-28)
> # which lsinitrd
> /usr/bin/lsinitrd
> # apt-file search /usr/bin/lsinitrd
> dracut-core: /usr/bin/lsinitrd
> # lsinitrd /initrd.img | wc -l
> 455

unicorn:~$ lsinitrd /boot/initrd.img-5.10.0-8-amd64 | wc -l
1646
unicorn:~$ lsinitramfs /boot/initrd.img-5.10.0-8-amd64 | wc -l
1635

Curious.

Re: what binds to port

[Thomas Schmitt]

Hi,

Brian wrote:
> Isn't /dev/sg0 the block device?

/dev/sgX are character devices.

  https://tldp.org/HOWTO/SCSI-Generic-HOWTO/intro.html
says
  "The driver's purpose is to allow SCSI commands to be sent directly to
   SCSI devices. [...] Various specialized applications for writing
   CD-Rs and document scanning use the sg driver."

This is still the case for optical drives (sr) and hard discs (sd) which get
an sg device file additionaly to their block device file. But it seems that
the statement about "document scanning" could need an update.


The main call for sg devices is ioclt(SG_IO) which performs a single SCSI
command transaction.
Since about 15 years it is possible to use it directly with a /dev/srX
device file. But a bug introduced in a late version of kernel 2.6 prevented
concurrent use of SG_IO on multiple sr devices. This ended with
  https://github.com/torvalds/linux/commit/51a8588
which i assume went into kernel version 5.6.
So with the currently released Debian versions, /dev/sgX is still of use
if there is more than one sr device.


Have a nice day :)

Thomas

Re: runc CVEs in docker.io

[Dominique Dumont]

On Tuesday, 27 July 2021 18:07:53 CEST Gareth Evans wrote:
> Given that these are all fixed in Bullseye (and at least the grave
> apt-listbugs issue has been fixed in eg Ubuntu since March 2020 [1]) why
> not also Buster?

According to runc security tracker, a fixed runc is available for buster, 
albeit in buster's security repository.

I guess that security repo is missing from your /etc/apt/sources.list

See https://www.debian.org/security/#keeping-secure for instructions.

HTH

Dod

Re: what binds to port

[Brian]

On Mon 02 Aug 2021 at 09:55:17 +0200, Thomas Schmitt wrote:

> Hi,
> 
> i wrote:
> > > /dev/sg2 might be the generic SCSI device to which /dev/sr0 is connected.
> 
> mick crane wrote:
> > Drive type   : vendor 'PLDS' product 'DVD+-RW DS-8A9SH' revision 'ED11'
> 
> So it's clearly the DVD burner which is at sg2.
> 
> Do you have any sg device left as suspect for the scanner's device file,
> after you subtracted one for each hard disk and each optical drive ?
> (I.e. are there two hard disks to occupy sg0 and sg1 and no other sgX left ?)

Isn't /dev/sg0 the block device?

-- 
Brian.

Re: burn iso to usb

[Robbi Nespu]

On 8/1/21 1:30 AM, to...@tuxteam.de wrote:

On Sat, Jul 31, 2021 at 06:42:50PM +0200, Hans wrote:

Am Samstag, 31. Juli 2021, 14:05:59 CEST schrieb Nicolas George:

Gunnar Gervin (12021-07-31):



Just:

cp /path/to/file.iso /dev/sdX



Hi,

isn't it just2  :

dd if=whatever.iso of=/dev/sdX


It's up to taste. Some get worked up one way or the other.
This discussion comes around cyclically :)

Personally, I settled on dd, mainly because oflag=sync and
status=progress. But I'm OK with others using copy, cat or
whatever :)

Cheers
  - t



I prefer dd because opts of blocksize (bs) and status

sudo dd if=/path/to/iso of=/dev/sdX bs=4M status=progress

--
Robbi Nespu 
D311 B5FF EEE6 0BE8 9C91 FA9E 0C81 FA30 3B3A 80BA
https://robbinespu.gitlab.io | https://mstdn.social/@robbinespu

Re: what binds to port

[Nicolas George]

Thomas Schmitt (12021-08-02):
> Do you have any sg device left as suspect for the scanner's device file,
> after you subtracted one for each hard disk and each optical drive ?
> (I.e. are there two hard disks to occupy sg0 and sg1 and no other sgX left ?)

Have SCSI scanners been spotted since the 20th century, except in zoos?

Only USB mass storage devices are shown as SCSI devices, because they
use mostly the same command set. Other USB devices either have their own
kernel drivers (printers…) or appear as generic USB devices nodes to be
accessed with libusb.

Regards,

-- 
  Nicolas George


signature.asc
Description: PGP signature

Re: Updating kernels impossible when /boot is getting full

[Stefan Monnier]

> So really think hard before splitting off a filesystem outside of
> volume management. I believe it is more likely to cause problems
> than it is to avoid problems.

All my machines have a separate /boot partition (and everything
else in LVM).  These are all "historical accidents", because at the time
I set them up, the respective boot loader (LILO, Grub, U-Boot) didn't
know how to read LVM volumes, and I just never bothered to change.

But I fully agree with you: if your bootloader can read from LVM
(as is the case with Grub2), then you're better off without a separate
/boot partition.


Stefan "not sure if U-Boot can read from LVM yet"

Re: what binds to port

[mick crane]

On 2021-08-02 08:55, Thomas Schmitt wrote:

Hi,

i wrote:

> /dev/sg2 might be the generic SCSI device to which /dev/sr0 is connected.


mick crane wrote:
Drive type   : vendor 'PLDS' product 'DVD+-RW DS-8A9SH' revision 
'ED11'


So it's clearly the DVD burner which is at sg2.

Do you have any sg device left as suspect for the scanner's device 
file,

after you subtracted one for each hard disk and each optical drive ?
(I.e. are there two hard disks to occupy sg0 and sg1 and no other sgX 
left ?)


doesn't seem to be.
root@pumpkin:/dev# ls -la |grep sg
drwxr-xr-x   2 root root 180 Jul 31 18:20 bsg
crw-r--r--   1 root root  1,  11 Jul 31 17:20 kmsg
crw-rw   1 root disk 21,   0 Jul 31 17:20 sg0
crw-rw   1 root disk 21,   1 Jul 31 17:20 sg1
crw-rw+  1 root cdrom21,   2 Jul 31 17:20 sg2

lsusb
Bus 002 Device 004: ID 04c5:1095 Fujitsu, Ltd

I don't know anything about usb
Everything is working now. using the scanner button seems maybe a second 
or so slower than XSane to get going but I think I'll leave alone.

cheers
mick
--
Key ID4BFEBB31

Re: what binds to port

[Thomas Schmitt]

Hi,

i wrote:
> > /dev/sg2 might be the generic SCSI device to which /dev/sr0 is connected.

mick crane wrote:
> Drive type   : vendor 'PLDS' product 'DVD+-RW DS-8A9SH' revision 'ED11'

So it's clearly the DVD burner which is at sg2.

Do you have any sg device left as suspect for the scanner's device file,
after you subtracted one for each hard disk and each optical drive ?
(I.e. are there two hard disks to occupy sg0 and sg1 and no other sgX left ?)


Have a nice day :)

Thomas

Re: Apparmor: 1 processes are unconfined but have a profile defined

[didier gaumet]

Le lundi 2 août 2021 à 06:00:05 UTC+2, Ratan Gupta a écrit :
[...]
> In my case it is not at all complaining as it is because the process is 
> unconfined.
[...]

If I am not mistaken, the purpose of the complain mode is precisely to inform 
about policy violations without forbidding them (forbidding, that is the 
purpose of the enforce mode). So, to me, there is no contradiction between 
complaining and unconfined

I am not knowledgeable enough to really help you in this matter, so I would 
suggest you to take a look at the AppArmor doc:
- Profiling_with_tools
https://gitlab.com/apparmor/apparmor/-/wikis/Profiling_with_tools
- or Profiling_by_hand, if you prefer
https://gitlab.com/apparmor/apparmor/-/wikis/Profiling_by_hand
- AppArmorMonitoring
https://gitlab.com/apparmor/apparmor/-/wikis/AppArmorMonitoring

Good luck ;-)

Re: what binds to port

[mick crane]

On 2021-07-31 12:11, Thomas Schmitt wrote:

Hi,

mick crane wrote:

looking at those informative pages I think /dev/sg2 is the scanner
should that not be in group scanner ?
lrwxrwxrwx  1 root root   3 Jul 30 17:36 cdrom -> sr0
crw-rw+ 1 root cdrom21,   2 Jul 30 17:36 sg2
brw-rw+ 1 root cdrom11,   0 Jul 30 17:36 sr0


/dev/sg2 might be the generic SCSI device to which /dev/sr0 is 
connected.




Drive type   : vendor 'PLDS' product 'DVD+-RW DS-8A9SH' revision 'ED11'
cheers
mick
--
Key ID4BFEBB31