Re: Am I infected with a rootkit?

[David]

On Tue, 18 Apr 2023 at 04:42, David Wright  wrote:

> There is an option to timestamp entries in the history file. I've
> never used it, nor heard of its being used. That might disambiguate
> things if you ever suspect it might happen again.

Hi, on my machines I use Bash as interactive
shell, with:
HISTTIMEFORMAT=: %Y%m%d_%H%M%S ;

That provides a couple of benefits:

1) it writes a commented Unix timestamp with
each addition to the ~/.bash_history file, so that
the history file not only logs what commands were
run interactively, but also when.

2) when I run the 'history' command, the outpt
is formatted like this:
501  : 20230418_151124 ; help history
502  : 20230418_151406 ; env
503  : 20230418_151749 ; history
The colon and semicolon allow the timestamp
to function as a no-operation command.
That means that history expansion
can still function, for example entering !502
interactively will run line number 502, but
only the 'env' that comes after the semicolon
will have any effect.

Re: "Bug" in Debian Installer?

[David Wright]

On Mon 17 Apr 2023 at 15:26:58 (-0700), David Christensen wrote:
> On 4/17/23 07:41, David Wright wrote:
> > On Mon 17 Apr 2023 at 01:27:45 (-0700), David Christensen wrote:
> > > On 4/16/23 22:08, Max Nikulin wrote:
> > > > On 17/04/2023 09:18, David Christensen wrote:
> > > > > On 4/16/23 03:41, Max Nikulin wrote:
> > > > > > On 16/04/2023 05:51, David Christensen wrote:
> > > > > > > When I moved the 2.5" SATA SSD to a homebrew Intel
> > > > > > > DQ67SW computer and configured BIOS Setup:
> > > > > > > 
> > > > > > >   "Boot" -> "UEFI Boot" -> "Enable"
> > > > > > > 
> > > > > > > The SSD would not boot.
> > > > > > 
> > > > > > New boot entry usually should be created in such case from
> > > > > > EFI Shell,
> > > > 
> > > > I have realized that you may be confused by difference of MBR vs.
> > > > UEFI behavior. For MBR it is enough to choose a disk to boot in
> > > > BIOS, for UEFI it is necessary to add boot entries through EFI
> > > > variables in firmware. Boot entry consists of disk, partition (EFI
> > > > System partition) and path of an .efi file on this partition.
> > > > 
> > > > If so, you may suggest an additional subsection to
> > > > https://wiki.debian.org/UEFI#Troubleshooting_common_issues
> > > 
> > > Are you saying that d-i modifies the CMOS settings of UEFI computers?
> > 
> > I think the preferred name is NVRAM, but yes.
> 
> So, in addition to modifying disks without notifying me or obtaining
> my permission, d-i modified, or attempted to modify, NVRAM settings
> without notifying me or obtaining my permission.

When you run the d-i, there are steps that are generally irrevocable.
Examples would be partitioning, writing random data for an encrypted
filesystem, and writing the MBR. (If you boot the d-i from the hard
disk itself, you have no medium with which to boot the machine when
you screw up the MBR.) I don't think adding material to the ESP, or
running efibootmgr are necessarily seen that way.

> That is disappointing, but thank you for the information.
> 
> 
> > 
> > > > > > > I later discovered that the first install created a
> > > > > > > directory and put files into the Dell's ESP (!).  I
> > > > > > > did not select this, nor do I desire it.  This is a
> > > > > > > defect with d-i:
> > > > > > 
> > > > > > Why do you think it is wrong?
> > > > > 
> > > > > Because OS installers should not modify a disk unless the user
> > > > > authorizes it.
> > > > 
> > > > I agree if a computer is booted into MBR/BIOS/Compatibility mode
> > > > or if expert install is selected. For regular UEFI install it is a
> > > > trade-off since multiple OS loaders may coexist without conflicts.
> > > > User should be asked if new OS should be booted by default
> > > > (BootOrder), adding files to ESP is quite safe.
> > > 
> > > d-i should always ask before writing to disk.
> > 
> > You will certainly be used to this because of years of BIOS/MBR
> > experience. There's always a question of where to install Grub
> > because you might make another OS unbootable, or you might want
> > Grub placed on a particular partition.
> > 
> > With UEFI booting, that doesn't typically come into play, so to
> > provoke your question, you'd probably need low priority/Expert
> > Install, which I don't think you asked for.
> 
> 
> I asked for "Install":
> 
> On 4/15/23 15:51, David Christensen wrote:
> >  "Debian GNU/Linux UEFI Installer menu" -> "Install"

AIUI, from the first menu, that gives you Priority=medium.

> > > > > Here are my notes from a debian-9.9.0-amd64-xfce-CD-1 install
> > > > > on February 2, 2020:
> > > > > 
> > > > >   Install GRUB into master boot record    Yes
> > > > >   Device  /dev/sda
> > > > > 
> > > > > That was the proper way to do it.
> > > > 
> > > > Am I right that it was not UEFI install? Certainly overwriting of
> > > > MBR must be acknowledged by the user.
> > > 
> > > The point is that d-i asked before writing to disk.
> > 
> > Yes, it's MBR.
> > 
> > > > > > > The SSD would not boot.
> > 
> > I asked about the partitioning scheme earlier, but no response.
> 
> 
> Here is the current system disk configuration.  It should match the
> failed installation, except that I added the fifth "scratch" partition
> and file system later:
> 
> 2023-04-17 14:21:39 root@taz ~
> # parted /dev/sda u s p free
> Model: ATA INTEL SSDSC2CW06 (scsi)
> Disk /dev/sda: 117231408s
> Sector size (logical/physical): 512B/512B
> Partition Table: gpt
> Disk Flags:
> 
> Number  Start   End Size   File system  Name   Flags
> 34s 2047s   2014s  Free Space
>  1  2048s   1953791s1951744s   fat32ESPboot,
> esp
>  2  1953792s3907583s1953792s   ext4 taz_boot
>  3  3907584s5861375s1953792staz_swap_crypt
>  4  5861376s29298687s   23437312s   taz_root_crypt
>  5  29298688s   117229567s  87930880s   taz_scratch_crypt

Re: Debian Bookworm RC 1 installer- a Bug?

[David Wright]

On Mon 17 Apr 2023 at 08:47:30 (-0700), Peter Ehlert wrote:
> On 4/16/23 09:29, David Wright wrote:
> > On Sun 16 Apr 2023 at 07:19:18 (-0700), Peter Ehlert wrote:
> > > On 4/9/23 08:57, David Wright wrote:
> > > > On Wed 05 Apr 2023 at 07:03:41 (-0700), Peter Ehlert wrote:
> > > > > Debian Bookworm RC 1 installer
> > > > > Damned nice, the improvements are appreciated.
> > > > I ran rc1 in my usual manner, and the only difference I noticed was
> > > > the one extra question about non-free firmware, to which I replied
> > > > yes. (There may well be improvements under the hood, so to speak.)
> > > > Oh, and the initrd is somewhat larger, as per usual.
> > > > 
> > > > > using the new debian-bookworm-DI-rc1-amd64-netinst.iso
> > > > > Legacy install, GPT partition
> > > > I assume Legacy means BIOS booting. Same here, but only one disk.
> > > correct. different term, same thing. Not UEFI
> > > > > graphic install, manual partitioning
> > > > > Mate Desktop (others were deselected)
> > > > Non-graphical here, a suitable partition existed, and only
> > > > standard and SSH server software was installed.
> > > > 
> > > > > WiFi firmware:
> > > > Untested as this machine is a 2006-vintage mini-tower lacking wifi.
> > > > 
> > > > [ snipped narrative of later network-switching ]
> > > > 
> > > > > Boot Loader:
> > > > > all disk drives were detected, however the one with the bios_grub
> > > > > partition was highlighted
> > > > I can't recall seeing anything other than the first item highlighted,
> > > > ie "Enter device manually", at least with the non-graphical installer
> > > > in expert mode. I selected the (sole) hard drive, item 2. The only
> > > > remaining item was the USB stick containing the installer ISO.
> > > > 
> > > > As expected nowadays, when the machine rebooted, the Grub menu
> > > > had only two lines, both pointing to the newly installed system.
> > > > (I hadn't made any attempt to counteract GRUB_DISABLE_OS_PROBER
> > > > during my installation.) So Grub was correctly installed in the
> > > > MBR, and the rest of Grub occupied d400 bytes of /dev/sda1 (the
> > > > 3MB BIOS boot partition on the single disk).
> > > > 
> > > > > =
> > > > > second try, using the debian-live-bkworm-DI-rc1-amd64-mate.iso
> > > > > same machine and again Legacy install, GPT partition
> > > > > however I did NOT install from the live session:
> > > > > I chose to go directly to install rather than the Calamares installer
> > > > > then manual partitioning
> > > > > 
> > > > > Boot Loader:
> > > > > all drives were detected, however the one with the bios_grub partition
> > > > > was NOT highlighted, but I did select it.
> > > > > GRUB was Not properly installed, my former grub menu was still active.
> > > > How did you determine that it was the previous menu. Wouldn't it look
> > > > just the same?
> > > I enable GRUB_DISABLE_OS_PROBER so that the various other operating
> > > systems are shown
> > > if the new GRUB is properly installed I get the "new" one item only
> > > GRUB display.
> > > then when I boot the new OS I again enable GRUB_DISABLE_OS_PROBER and
> > > update GRUB
> > > > > *** I tried a second time, same as above being super careful, same 
> > > > > result.
> > > > > 
> > > > > I then booted with my default system, ran grub-install /dev/sde &&
> > > > > update-grub
> > > > > then "new" system was on my boot menu.
> > > > > then booted and it ran as expected.
> > So you installed Grub on /dev/sde.
> > 
> > > > Which method did you use to boot the "default" system (which I assume
> > > > is bullseye, in a different partition on one or other of the disks),
> > > > in view of the rather sparse menu from grub.cfg on the new system?
> > > I boot with the "old" GRUB menu as explained above...it has Several
> > > operating systems listed, my old default OS is still at the top of the
> > > list.
> > > > > back to the WiFi dongle, again the obscure firmware was properly 
> > > > > installed
> > > > > 
> > > > > Is this a Bug or a user/hardware issue?
> > > > Presumably we are now back to talking about Grub.
> > > > 
> > > > If you still have access to the bookworm system, you can check whether
> > > > it claimed to have completed installing Grub successfully. You should
> > > > see lines like:
> > > > 
> > > > grub-installer: info: Installing grub on '/dev/sda'
> > > > grub-installer: info: grub-install does not support --no-floppy
> > > > grub-installer: info: Running chroot /target grub-install  --force 
> > > > "/dev/sda"
> > > > grub-installer: Installing for i386-pc platform.
> > > > grub-installer: Installation finished. No error reported.
> > > > grub-installer: info: grub-install ran successfully
> > > > 
> > > > in /var/log/installer/syslog.
> > > Thanks, I did not know where to look or what to look for.
> > I've tidied these lines:
> > 
> > > ===
> > > Apr  5 12:59:44 grub-installer: info: Identified partition label for
> > > /dev/sdb12: gpt
> > 

Re: Am I infected with a rootkit?

[David Wright]

On Sun 16 Apr 2023 at 16:39:13 (+0200), Jesper Dybdal wrote:
> On 2023-04-16 16:33, David Wright wrote:
> > On Sun 16 Apr 2023 at 14:19:34 (+0200), Jesper Dybdal wrote:
> > > The 4 lines were:
> > > > md5users
> > > > sp md5users
> > > > sp /x/md5users
> > > > ps /x/md5users
> > > 
> > Just FTR and clarity's sake, are the "> " characters (which my MUA has
> > unhelpfully doubled by quoting) part of what was typed in the putty
> > session, or did you type them into the post to make them stand out?
> They were not part of what was typed, and I did add them to make the
> lines stand out.  Sorry for the unclear text.
> 
> Here is a correct and clear, I hope, version:
> 
>  The 4 lines were:
> md5users
> sp md5users
> sp /x/md5users
> ps /x/md5users
>  End of the 4 lines

OK, you wrote that you "pressed up-arrow a few times. And there in the
bash history were 4 lines …". If those 4 lines were not the first
things to appear when you pressed up-arrow, then I would assume that
the commands you typed /just/ before you went out with the dog were
the first lines to appear, and then your 4 lines after more up-arrows.

If that's the case, then your 4 lines could have been typed
in a previous login as root, and that could have been some time
ago. They would have been languishing at the end of the file
/root/.bash_history before you logged in as root this time.

There is an option to timestamp entries in the history file. I've
never used it, nor heard of its being used. That might disambiguate
things if you ever suspect it might happen again.

Cheers,
David.

Re: [testing] shadow drive et debian

[Gaëtan Perrier]

Le samedi 15 avril 2023 à 19:01 +0200, Haricophile a écrit :
> Le Wed, 12 Apr 2023 23:10:01 +0200,
> Gaëtan Perrier  a écrit :
> 
> > Bonjour,
> > 
> > Je viens d'essayer d'installer le paquet deb shadow 8.0.10059 sur ma
> > debian testing.
> > Y a eu une erreur à la fin de l'installation du paquet mais ça s'est
> > installé quand même. Ensuite quand je lance l'appli shadow PC ça
> > m'ouvre une fenêtre me proposant de me logger via un navigateur. Ce
> > que je fais et là j'ai une erreur me disant "Connection failed" et me
> > disant que je n'ai pas de plan souscrit. Pourtant j'ai bien un shadow
> > drive. Est-ce quelqu'un rencontre le même soucis ou a réussi à se
> > connecter ?
> > 
> > Gaëtan
> 
> Plusieurs choses: 
> 
> - Ne pas confondre Shadow (l'ordinateur «cloud») et Shadow Drive (le
>   stockage cloud) !  Le paquet Debian n'est pas pour Shadow Drive, mais
>   pour l'ordinateur virtuel.
>   Donc avec la version appimage de Shadow DRIVE ça fonctionne très bien
>   chez moi.

Aahh !! C'est super pas clair sur la page de
téléchargement !
Maintenant ça fonctionne nickel ! :)

Merci beaucoup !

A+

Gaëtan





signature.asc
Description: This is a digitally signed message part

Re: "Bug" in Debian Installer?

[David Christensen]

On 4/17/23 03:35, Max Nikulin wrote:

My point is that UEFI and MBR install may have different behavior. You 
might underestimate role of implicit conventions and agreements.



I used to think that d-i would inform me and get my permission before 
making changes to my computer.



It is unfortunate that Debian has shattered that belief, but thank you 
for the information.



David

Re: "Bug" in Debian Installer?

[David Christensen]

On 4/17/23 07:41, David Wright wrote:

On Mon 17 Apr 2023 at 01:27:45 (-0700), David Christensen wrote:

On 4/16/23 22:08, Max Nikulin wrote:

On 17/04/2023 09:18, David Christensen wrote:

On 4/16/23 03:41, Max Nikulin wrote:

On 16/04/2023 05:51, David Christensen wrote:

When I moved the 2.5" SATA SSD to a homebrew Intel
DQ67SW computer and configured BIOS Setup:

  "Boot" -> "UEFI Boot" -> "Enable"

The SSD would not boot.


New boot entry usually should be created in such case from
EFI Shell,


I have realized that you may be confused by difference of MBR vs.
UEFI behavior. For MBR it is enough to choose a disk to boot in
BIOS, for UEFI it is necessary to add boot entries through EFI
variables in firmware. Boot entry consists of disk, partition (EFI
System partition) and path of an .efi file on this partition.

If so, you may suggest an additional subsection to
https://wiki.debian.org/UEFI#Troubleshooting_common_issues


Are you saying that d-i modifies the CMOS settings of UEFI computers?


I think the preferred name is NVRAM, but yes.



So, in addition to modifying disks without notifying me or obtaining my 
permission, d-i modified, or attempted to modify, NVRAM settings without 
notifying me or obtaining my permission.



That is disappointing, but thank you for the information.





I later discovered that the first install created a
directory and put files into the Dell's ESP (!).  I
did not select this, nor do I desire it.  This is a
defect with d-i:


Why do you think it is wrong?


Because OS installers should not modify a disk unless the user
authorizes it.


I agree if a computer is booted into MBR/BIOS/Compatibility mode
or if expert install is selected. For regular UEFI install it is a
trade-off since multiple OS loaders may coexist without conflicts.
User should be asked if new OS should be booted by default
(BootOrder), adding files to ESP is quite safe.


d-i should always ask before writing to disk.


You will certainly be used to this because of years of BIOS/MBR
experience. There's always a question of where to install Grub
because you might make another OS unbootable, or you might want
Grub placed on a particular partition.

With UEFI booting, that doesn't typically come into play, so to
provoke your question, you'd probably need low priority/Expert
Install, which I don't think you asked for.



I asked for "Install":

On 4/15/23 15:51, David Christensen wrote:
>  "Debian GNU/Linux UEFI Installer menu" -> "Install"





Here are my notes from a debian-9.9.0-amd64-xfce-CD-1 install
on February 2, 2020:

  Install GRUB into master boot record    Yes
  Device  /dev/sda

That was the proper way to do it.


Am I right that it was not UEFI install? Certainly overwriting of
MBR must be acknowledged by the user.


The point is that d-i asked before writing to disk.


Yes, it's MBR.


The SSD would not boot.


I asked about the partitioning scheme earlier, but no response.



Here is the current system disk configuration.  It should match the 
failed installation, except that I added the fifth "scratch" partition 
and file system later:


2023-04-17 14:21:39 root@taz ~
# parted /dev/sda u s p free
Model: ATA INTEL SSDSC2CW06 (scsi)
Disk /dev/sda: 117231408s
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:

Number  Start   End Size   File system  Name 
  Flags

34s 2047s   2014s  Free Space
 1  2048s   1953791s1951744s   fat32ESP 
   boot, esp

 2  1953792s3907583s1953792s   ext4 taz_boot
 3  3907584s5861375s1953792staz_swap_crypt
 4  5861376s29298687s   23437312s   taz_root_crypt
 5  29298688s   117229567s  87930880s   taz_scratch_crypt
117229568s  117231374s  1807s  Free Space

2023-04-17 14:25:51 root@taz ~
# mount | egrep 'boot|mapper' | sort
/dev/mapper/sda4_crypt on / type ext4 (rw,relatime,errors=remount-ro)
/dev/mapper/sda5_crypt on /scratch type ext4 (rw,relatime)
/dev/sda1 on /boot/efi type vfat 
(rw,relatime,fmask=0077,dmask=0077,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro)

/dev/sda2 on /boot type ext4 (rw,relatime)

2023-04-17 14:27:06 root@taz ~
# swapon
NAME  TYPE  SIZE USED PRIO
/dev/dm-1 partition 954M   0B   -2



I'll hazard a guess that the second disk had no ESP on it, so the
original installer set up a dual boot system for Windows and Debian
by adding an entry to the original disk's ESP. No need to quiz the
operator as there would be with a Windows MBR.

When you took the second disk out, it was unbootable as there was
no ESP on it. (That's my guess.) 



During the failed installation, d-i put the directory and files onto the 
primary disk:


On 4/15/23 15:51, David Christensen wrote:
> 2023-04-15 15:10:34 root@taz ~
> # ls -ld /mnt/nvme0n1p1/EFI/debian
> drwxr-xr-x 2 root root 4096 Mar 16 22:19 

Re: hi res pdf needs posterized

[gene heskett]

On 4/17/23 16:41, Peter Ehlert wrote:


On 4/17/23 12:02, Fred wrote:

On 4/17/23 11:55, gene heskett wrote:

Greetings all printing experts;

I have an extremely high res pdf of a 3d printer controller board.
I need to print it in the same or close, resolution I can see it on 
screen in libreoffice draw. But its equ to 26" wide! So the ideal 
printout would be posterized on 2 sheets of photo paper at about 85% 
size. But I can't find a poster recipe in OO-draw.


What the next best way to handle such a pdf to get an image big 
enough to easily read pin numbers etc ? cut in half down the middle 
and put on 2 pages of foto paper would be ideal. poster reads like it 
but expects ps  or better eps src. I found pdfposter but it will not 
accept letter as a -m BOX definition. This image it claim will be 
rotated to portrait mode, and 2 8.5x11 pages high laid landscape 
would be just right with -s .80 option to reduce the height to 2 page 
tall.


Cheers, Gene Heskett.

Hi Gene,

If you live close to a large city there will be printing shops that 
serve surveyors that can print large format files. 

exactly
in California the mandated size is 18" x 26" for subdivision maps of 
various flavors.

engineering drawings are variable, 24" x 36" is really common.
I used to have a 36" printer that used 36" wide roll stock, but when it 
died I went to 24"... then after I "retired"
later I started using a Kikos or some such... email them the file, pick 
up the product at the store.

dunno who is better, but lots of people shop it out.

Some Office Max stores can also print large format files.

Best regards,
Fred
There may be something in Clarksburg or Bridgeport that could do that, 
but my truck gets 14.4 mpg and it is a 50+ mile round trip. I have a 
printer that can do tabloid if pushed, but does an excellent job on 
8.5x11 photo paper. And it is done. ;o)>





.


Cheers, Gene Heskett.
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

Re: hi res pdf needs posterized

[Peter Ehlert]

On 4/17/23 12:02, Fred wrote:

On 4/17/23 11:55, gene heskett wrote:

Greetings all printing experts;

I have an extremely high res pdf of a 3d printer controller board.
I need to print it in the same or close, resolution I can see it on 
screen in libreoffice draw. But its equ to 26" wide! So the ideal 
printout would be posterized on 2 sheets of photo paper at about 85% 
size. But I can't find a poster recipe in OO-draw.


What the next best way to handle such a pdf to get an image big 
enough to easily read pin numbers etc ? cut in half down the middle 
and put on 2 pages of foto paper would be ideal. poster reads like it 
but expects ps  or better eps src. I found pdfposter but it will not 
accept letter as a -m BOX definition. This image it claim will be 
rotated to portrait mode, and 2 8.5x11 pages high laid landscape 
would be just right with -s .80 option to reduce the height to 2 page 
tall.


Cheers, Gene Heskett.

Hi Gene,

If you live close to a large city there will be printing shops that 
serve surveyors that can print large format files. 

exactly
in California the mandated size is 18" x 26" for subdivision maps of 
various flavors.

engineering drawings are variable, 24" x 36" is really common.
I used to have a 36" printer that used 36" wide roll stock, but when it 
died I went to 24"... then after I "retired"
later I started using a Kikos or some such... email them the file, pick 
up the product at the store.

dunno who is better, but lots of people shop it out.

Some Office Max stores can also print large format files.

Best regards,
Fred

Re: hi res pdf needs posterized

[Fred]

On 4/17/23 11:55, gene heskett wrote:

Greetings all printing experts;

I have an extremely high res pdf of a 3d printer controller board.
I need to print it in the same or close, resolution I can see it on 
screen in libreoffice draw. But its equ to 26" wide! So the ideal 
printout would be posterized on 2 sheets of photo paper at about 85% 
size. But I can't find a poster recipe in OO-draw.


What the next best way to handle such a pdf to get an image big enough 
to easily read pin numbers etc ? cut in half down the middle and put on 
2 pages of foto paper would be ideal. poster reads like it but expects 
ps  or better eps src. I found pdfposter but it will not accept letter 
as a -m BOX definition. This image it claim will be rotated to portrait 
mode, and 2 8.5x11 pages high laid landscape would be just right with -s 
.80 option to reduce the height to 2 page tall.


Cheers, Gene Heskett.

Hi Gene,

If you live close to a large city there will be printing shops that 
serve surveyors that can print large format files.  Some Office Max 
stores can also print large format files.


Best regards,
Fred

Re: hi res pdf needs posterized

[gene heskett]

On 4/17/23 15:07, Dan Ritter wrote:

gene heskett wrote:

Greetings all printing experts;

I have an extremely high res pdf of a 3d printer controller board.
I need to print it in the same or close, resolution I can see it on screen
in libreoffice draw. But its equ to 26" wide! So the ideal printout would be
posterized on 2 sheets of photo paper at about 85% size. But I can't find a
poster recipe in OO-draw.

What the next best way to handle such a pdf to get an image big enough to
easily read pin numbers etc ? cut in half down the middle and put on 2 pages
of foto paper would be ideal. poster reads like it but expects ps  or better
eps src. I found pdfposter but it will not accept letter as a -m BOX
definition. This image it claim will be rotated to portrait mode, and 2
8.5x11 pages high laid landscape would be just right with -s .80 option to
reduce the height to 2 page tall.


The package mupdf-tools has mutool, which has a poster
subcommand with:

-x: this many horizontal pieces
-y: this many vertical pieces

and -r for resolution, -h and -w for height and width
specifications.

-dsr-
.

Very very close to what I wanted, Dan, better than I expected in fact.

Thank you a bunch.  The help screen says -x and -y is the decimation 
value so I told it .8 for both, okular then printed the out.pdf as 2 
landscape pages missing about 1/16" at the junction then I gave it a -s 
.75, but it must query the printer for exact paper size and I now have 2 
identical copies of 2 pages each in glorious color. Very helpful.


Take care & stay well.

Cheers, Gene Heskett.
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

Re: hi res pdf needs posterized

[Dan Ritter]

gene heskett wrote: 
> Greetings all printing experts;
> 
> I have an extremely high res pdf of a 3d printer controller board.
> I need to print it in the same or close, resolution I can see it on screen
> in libreoffice draw. But its equ to 26" wide! So the ideal printout would be
> posterized on 2 sheets of photo paper at about 85% size. But I can't find a
> poster recipe in OO-draw.
> 
> What the next best way to handle such a pdf to get an image big enough to
> easily read pin numbers etc ? cut in half down the middle and put on 2 pages
> of foto paper would be ideal. poster reads like it but expects ps  or better
> eps src. I found pdfposter but it will not accept letter as a -m BOX
> definition. This image it claim will be rotated to portrait mode, and 2
> 8.5x11 pages high laid landscape would be just right with -s .80 option to
> reduce the height to 2 page tall.

The package mupdf-tools has mutool, which has a poster
subcommand with:

-x: this many horizontal pieces
-y: this many vertical pieces

and -r for resolution, -h and -w for height and width
specifications.

-dsr-

hi res pdf needs posterized

[gene heskett]

Greetings all printing experts;

I have an extremely high res pdf of a 3d printer controller board.
I need to print it in the same or close, resolution I can see it on 
screen in libreoffice draw. But its equ to 26" wide! So the ideal 
printout would be posterized on 2 sheets of photo paper at about 85% 
size. But I can't find a poster recipe in OO-draw.


What the next best way to handle such a pdf to get an image big enough 
to easily read pin numbers etc ? cut in half down the middle and put on 
2 pages of foto paper would be ideal. poster reads like it but expects 
ps  or better eps src. I found pdfposter but it will not accept letter 
as a -m BOX definition. This image it claim will be rotated to portrait 
mode, and 2 8.5x11 pages high laid landscape would be just right with 
-s .80 option to reduce the height to 2 page tall.


Cheers, Gene Heskett.
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

Re: Am I infected with a rootkit?

[Tim Woodall]

On Mon, 17 Apr 2023, Stefan Monnier wrote:


That said, using one computer as router, firewall, file server, name server,
web server, and more represents "all of your eggs in one basket".  I suggest
using dedicated hardware for networking, network segmentation (e.g. DMZ),
and kernel or hypervisor compartmentalization of services.


Dedicated hardware has its upsides, indeed, but it also
has its downsides (e.g. in terms of impact to the planet).



This is very true.

I switched to using one of these:
https://www.asrockrack.com/general/productdetail.asp?Model=J1900D2Y
in a xen configuration, from multiple hardware - but multiple services
on one hardware instance.

it's low power and fanless and has built in IPMI.

For me that ticks all the boxes I need. Having each of nameserver, dhcp
server, web server, firewall, "file server"[1] etc, running on separate
guests makes upgrading so much simpler too. I used to dread upgrades,
now they're relatively painless.

[1] I don't really run a fileserver but I do run iscsi targets.

Re: Am I infected with a rootkit?

[Stefan Monnier]

> That said, using one computer as router, firewall, file server, name server,
> web server, and more represents "all of your eggs in one basket".  I suggest
> using dedicated hardware for networking, network segmentation (e.g. DMZ),
> and kernel or hypervisor compartmentalization of services.

Dedicated hardware has its upsides, indeed, but it also
has its downsides (e.g. in terms of impact to the planet).


Stefan

Re: Am I infected with a rootkit?

[Curt]

On 2023-04-16, Jesper Dybdal  wrote:
>
> On 2023-04-16 15:08, Greg Wooledge wrote:
>> On Sun, Apr 16, 2023 at 02:19:34PM +0200, Jesper Dybdal wrote:
>>> And there in the bash history were 4 lines that I had not written :-(
>> I would initially ask "who else lives with you"
>
> So would I - if I didn't know that the few people with physical access 
> to my apartment, including my wife, haven't the faintest idea that there 
> is a thing called "md5".

Maybe it's some trivial corollary of the infinite monkey theorem, and
it's really the dog.

-- 

Re: Debian Bookworm RC 1 installer- a Bug?

[Peter Ehlert]

On 4/16/23 09:29, David Wright wrote:

On Sun 16 Apr 2023 at 07:19:18 (-0700), Peter Ehlert wrote:

On 4/9/23 08:57, David Wright wrote:

On Wed 05 Apr 2023 at 07:03:41 (-0700), Peter Ehlert wrote:

Debian Bookworm RC 1 installer
Damned nice, the improvements are appreciated.

I ran rc1 in my usual manner, and the only difference I noticed was
the one extra question about non-free firmware, to which I replied
yes. (There may well be improvements under the hood, so to speak.)
Oh, and the initrd is somewhat larger, as per usual.


using the new debian-bookworm-DI-rc1-amd64-netinst.iso
Legacy install, GPT partition

I assume Legacy means BIOS booting. Same here, but only one disk.

correct. different term, same thing. Not UEFI

graphic install, manual partitioning
Mate Desktop (others were deselected)

Non-graphical here, a suitable partition existed, and only
standard and SSH server software was installed.


WiFi firmware:

Untested as this machine is a 2006-vintage mini-tower lacking wifi.

[ snipped narrative of later network-switching ]


Boot Loader:
all disk drives were detected, however the one with the bios_grub
partition was highlighted

I can't recall seeing anything other than the first item highlighted,
ie "Enter device manually", at least with the non-graphical installer
in expert mode. I selected the (sole) hard drive, item 2. The only
remaining item was the USB stick containing the installer ISO.

As expected nowadays, when the machine rebooted, the Grub menu
had only two lines, both pointing to the newly installed system.
(I hadn't made any attempt to counteract GRUB_DISABLE_OS_PROBER
during my installation.) So Grub was correctly installed in the
MBR, and the rest of Grub occupied d400 bytes of /dev/sda1 (the
3MB BIOS boot partition on the single disk).


=
second try, using the debian-live-bkworm-DI-rc1-amd64-mate.iso
same machine and again Legacy install, GPT partition
however I did NOT install from the live session:
I chose to go directly to install rather than the Calamares installer
then manual partitioning

Boot Loader:
all drives were detected, however the one with the bios_grub partition
was NOT highlighted, but I did select it.
GRUB was Not properly installed, my former grub menu was still active.

How did you determine that it was the previous menu. Wouldn't it look
just the same?

I enable GRUB_DISABLE_OS_PROBER so that the various other operating
systems are shown
if the new GRUB is properly installed I get the "new" one item only
GRUB display.
then when I boot the new OS I again enable GRUB_DISABLE_OS_PROBER and
update GRUB

*** I tried a second time, same as above being super careful, same result.

I then booted with my default system, ran grub-install /dev/sde &&
update-grub
then "new" system was on my boot menu.
then booted and it ran as expected.

So you installed Grub on /dev/sde.


Which method did you use to boot the "default" system (which I assume
is bullseye, in a different partition on one or other of the disks),
in view of the rather sparse menu from grub.cfg on the new system?

I boot with the "old" GRUB menu as explained above...it has Several
operating systems listed, my old default OS is still at the top of the
list.

back to the WiFi dongle, again the obscure firmware was properly installed

Is this a Bug or a user/hardware issue?

Presumably we are now back to talking about Grub.

If you still have access to the bookworm system, you can check whether
it claimed to have completed installing Grub successfully. You should
see lines like:

grub-installer: info: Installing grub on '/dev/sda'
grub-installer: info: grub-install does not support --no-floppy
grub-installer: info: Running chroot /target grub-install  --force 
"/dev/sda"
grub-installer: Installing for i386-pc platform.
grub-installer: Installation finished. No error reported.
grub-installer: info: grub-install ran successfully

in /var/log/installer/syslog.

Thanks, I did not know where to look or what to look for.

I've tidied these lines:


===
Apr  5 12:59:44 grub-installer: info: Identified partition label for
/dev/sdb12: gpt
Apr  5 13:01:03 grub-installer: info: Installing grub on '/dev/sdb'
Apr  5 13:01:03 grub-installer: info: grub-install does not support
--no-floppy
Apr  5 13:01:03 grub-installer: info: Running chroot /target
grub-install  --force "/dev/sdb"
Apr  5 13:01:03 grub-installer: Installing for i386-pc platform.
Apr  5 13:01:13 grub-installer: grub-install: warning: this GPT
partition label contains no BIOS Boot Partition; embedding won't be
possible.
Apr  5 13:01:13 grub-installer: grub-install: warning: Embedding is
not possible.  GRUB can only be installed in this setup by using
blocklists.  However, blocklists are UNRELIABLE and their use is
discouraged..
Apr  5 13:01:13 grub-installer: Installation finished. No error reported.
Apr  5 13:01:13 grub-installer: info: grub-install ran successfully



So that was installing Grub 

Re: Am I infected with a rootkit?

[Michel Verdier]

Le 17 avril 2023 David Christensen a écrit :

> That said, using one computer as router, firewall, file server, name server,
> web server, and more represents "all of your eggs in one basket".  I suggest
> using dedicated hardware for networking, network segmentation (e.g. DMZ), and
> kernel or hypervisor compartmentalization of services.  Qubes looks very
> appealing:

What are its advantages vs debian ? Debian can chroot most services. Some
are chrooted by default (postfix, etc). And you can use Xen and tor on
debian.

Re: Apt sources.list

[Jeffrey Walton]

On Mon, Apr 17, 2023 at 12:45 AM  wrote:
>
> On Sun, Apr 16, 2023 at 09:20:22PM -0400, Jeffrey Walton wrote:
>
> [...]
> > > Corporations don't need browser cooperation for Data Loss Prevention
> > > (DLP) (but they already have it). Corporations just run an
> > > interception proxy, like NetSkope. The NetScope Root CA is loaded into
> > > every browser trust store. The application will terminate all traffic,
> > > inspect it, and forward the request if it looks innocuous.
> >
> > To be clear... The NetSkope Root CA is loaded into browsers for
> > computers owned by the corporation. I.e., part of the corporation's
> > standard image.
>
> Heh. You made me search for it in my browser's root CA store ;-)
>
> Anyway, your points are all valid. I do recommend to have a look
> at the browser's default root CA store before saying "you're safe
> with TLS". This is just marketing. TLS is but one tool.

Yeah, I call it the "CA Zoo." The Browsers will let just about anyone
into the store. All you need to do is check the boxes. If interested
in the day-to-day operations, subscribe to Mozilla's
dev-security-policy list at
https://groups.google.com/a/mozilla.org/g/dev-security-policy. It is
where CAs come to join the store.

There are some efforts to reduce the risk from the CA Zoo. For
example, VISA restricts the list as detailed at
https://developer.visa.com/pages/trusted_certifying_authorities .
VISA's list is 41 in size. It is better than the 150+ in Mozilla's and
Chrome's lists.

> Don't get me wrong: I think widespread use of TLS is a Good Thing.
> But going about it as if it was Redemption is paternalistic to the
> point of being counterproductive.
>
> Security is a process, not a product, as Schneier says.

Jeff

Re: "Bug" in Debian Installer?

[David Wright]

On Mon 17 Apr 2023 at 01:27:45 (-0700), David Christensen wrote:
> On 4/16/23 22:08, Max Nikulin wrote:
> > On 17/04/2023 09:18, David Christensen wrote:
> > > On 4/16/23 03:41, Max Nikulin wrote:
> > > > On 16/04/2023 05:51, David Christensen wrote:
> > > > > When I moved the 2.5" SATA SSD to a homebrew Intel
> > > > > DQ67SW computer and configured BIOS Setup:
> > > > > 
> > > > >  "Boot" -> "UEFI Boot" -> "Enable"
> > > > > 
> > > > > The SSD would not boot.
> > > > 
> > > > New boot entry usually should be created in such case from
> > > > EFI Shell,
> > 
> > I have realized that you may be confused by difference of MBR vs.
> > UEFI behavior. For MBR it is enough to choose a disk to boot in
> > BIOS, for UEFI it is necessary to add boot entries through EFI
> > variables in firmware. Boot entry consists of disk, partition (EFI
> > System partition) and path of an .efi file on this partition.
> > 
> > If so, you may suggest an additional subsection to
> > https://wiki.debian.org/UEFI#Troubleshooting_common_issues
> 
> Are you saying that d-i modifies the CMOS settings of UEFI computers?

I think the preferred name is NVRAM, but yes.

> > > > > I later discovered that the first install created a
> > > > > directory and put files into the Dell's ESP (!).  I
> > > > > did not select this, nor do I desire it.  This is a
> > > > > defect with d-i:
> > > > 
> > > > Why do you think it is wrong?
> > > 
> > > Because OS installers should not modify a disk unless the user
> > > authorizes it.
> > 
> > I agree if a computer is booted into MBR/BIOS/Compatibility mode
> > or if expert install is selected. For regular UEFI install it is a
> > trade-off since multiple OS loaders may coexist without conflicts.
> > User should be asked if new OS should be booted by default
> > (BootOrder), adding files to ESP is quite safe.
> 
> d-i should always ask before writing to disk.

You will certainly be used to this because of years of BIOS/MBR
experience. There's always a question of where to install Grub
because you might make another OS unbootable, or you might want
Grub placed on a particular partition.

With UEFI booting, that doesn't typically come into play, so to
provoke your question, you'd probably need low priority/Expert
Install, which I don't think you asked for.

> > > Here are my notes from a debian-9.9.0-amd64-xfce-CD-1 install
> > > on February 2, 2020:
> > > 
> > >  Install GRUB into master boot record    Yes
> > >  Device  /dev/sda
> > > 
> > > That was the proper way to do it.
> > 
> > Am I right that it was not UEFI install? Certainly overwriting of
> > MBR must be acknowledged by the user.
> 
> The point is that d-i asked before writing to disk.

Yes, it's MBR.

> > > > > The SSD would not boot.

I asked about the partitioning scheme earlier, but no response.
I'll hazard a guess that the second disk had no ESP on it, so the
original installer set up a dual boot system for Windows and Debian
by adding an entry to the original disk's ESP. No need to quiz the
operator as there would be with a Windows MBR.

When you took the second disk out, it was unbootable as there was
no ESP on it. (That's my guess.) So you zeroed it and reinstalled.

My experience, from having a mixed bag of BIOS/UEFI computers with
GPT disks, has been to always create a BIOS Boot Partition (3MB,
at the start, giving 4MB alignment for the rest of the drive), and
always create a potential ESP ½GB immediately following. On a BIOS
machine, it can make an extra swap as they have less memory anyway,
but the disk is then suitable for conversion to a UEFI environment.
With GPT, you don't have to worry about running out of primary
partitions.

I have one ESP-less laptop, dating from 2004, so I don't think
I'll be moving its 60GB GPT disk into a different machine when
it finally dies.

I did convert one BIOS laptop to UEFI without even reinstalling its
Debian, with encouragement from Felix. That was back in 2022-02 too.

From the UEFI wiki:

 "Once the normal installation process has been completed, the second
  major component with UEFI support comes into play: grub-installer.
  It will install the grub-efi bootloader to the right location in the
  ESP and will use efibootmgr to register that bootloader with the
  firmware. On correctly-working systems, this should work without
  needing any user interaction. This module will automatically find
  the ESP and install its files in the right place, leaving no space
  for confusion on where boot files are saved (as can happen with
  MBR/MS-DOS systems)."

Cheers,
David.

Re: Accesar a disco sin necesidad de root

[José María]

El 16/4/23, CAMP  escribió:
> Tengo debian en una laptop sony vaio, debido a que la unidad de DVD
> de descompuso, opte por ponerle un disco duro con un adaptador en la
> unidad de DVD, todo muy bien, pero ¿como le puedo hacer para que
> cuando acceso a dicho disco no me pida el password root?
>

Como te dicen, lo tendrás que añadir al fstab para que cuando inicies
el PC se te monte automáticamente... Pero primero tendrás que conocer
el UUID del disco y que opciones de montaje ponerle.

En la wiki de Arch te lo explica bastante bien.

https://wiki.archlinux.org/title/Fstab

Un saludo,
Jose

Bookworm: how to set default clang to clang-15?

[Joost Kraaijeveld]

Hi,

The default clang version for Bookworm is clang-14. An installable
version of clang-15 is also available. How can I change the default
version of clang to clang-15? "update-alternatives" provides no means
of doing that? Is replacing all the symbolic links the only way?

TIA

-- 
Groeten,

Joost



signature.asc
Description: This is a digitally signed message part

Re: Email clients and IMAP search support

[André Rodier]

Hi, Byung-Hee.

This is definitely not what I asked, and we don't ask for a Gmail advertisement.

I don't understand what prompted you to write such an answer, this is a waste 
of resource and time.

Moreover, I have found my answer.

Andre.


17 Apr 2023 06:29:12 Byung-Hee HWANG :

> Andre Rodier  writes:
> 
>> On Sun, 2023-04-16 at 17:01 +0100, Andre Rodier wrote:
>>> Hi,
>>> 
>>> Is there any desktop email client on Debian, that supports server
>>> side IMAP search, please ?
>>> 
>>> I have an email server that support indexing attachment contents,
>>> and when I run a query from the command line using
>>> doveadm search or even TELNET, it is returning the correct email indexes.
>>> 
>>> However, when I try the same search with a desktop client, nothing
>>> is returned. I tried Thunderbird, Balsa, Claws and
>>> Geary. None of them is satisfactory.
>>> 
>>> Thanks for your help.
>>> 
>>> Thanks,
>>> André
>>> 
>> 
>> OK, I am answering to myself, Gnome Evolution works, it is sending the
>> search query to the server.
>> 
>> Even in some advanced RTL languages like Arabic.
>> 
>> Great!
> 
> Hellow Andre,
> 
> Searching for IMAP is good with Gmail web interface, i think. If you
> have web browser such as mozilla firefox, chromium browser. Try to
> gmail, just with web browser. It is not bad in my experience. And also i
> am Debian user (Debian 11 Bullseye under Chromebook).
> 
> As you know, Gmail is good with UTF-8 support / Searching / Labeling.
> 
> See here:
> https://gitlab.com/soyeomul/Gnus/-/commit/314e84446d1002726aec0ccf81a756d54568bfbb
> 
> In real world, i use both Gmail and Emacs Gnus for email.
> 
> Sincerely, Byung-Hee
> 
> -- 
> ^고맙습니다 _地平天成_ 감사합니다_^))//

Re: "Bug" in Debian Installer?

[Max Nikulin]

On 17/04/2023 15:27, David Christensen wrote:

On 4/16/23 22:08, Max Nikulin wrote:

On 17/04/2023 09:18, David Christensen wrote:

On 4/16/23 03:41, Max Nikulin wrote:

On 16/04/2023 05:51, David Christensen wrote:
When I moved the 2.5" SATA SSD to a homebrew Intel DQ67SW computer 

...

The SSD would not boot.


New boot entry usually should be created in such case from EFI Shell, 


I have realized that you may be confused by difference of MBR vs. UEFI 
behavior. For MBR it is enough to choose a disk to boot in BIOS, for 
UEFI it is necessary to add boot entries through EFI variables in 
firmware. Boot entry consists of disk, partition (EFI System 
partition) and path of an .efi file on this partition.


Are you saying that d-i modifies the CMOS settings of UEFI computers?


I am unsure concerning precise meaning of CMOS in this context. UEFI 
provides non-volatile storage. Kernel exposes it as 
/sys/firmware/efi/efivars/ . For boot specific variables there is the 
efibootmgr tool. To make firmware aware of a bootable .efi file it is 
necessary to save it location to a variable like Boot. The role of 
the BootOrder variable is to define in which order boot entries are tried.


To make newly installed system bootable, the installer needs to call 
efibootmgr to adjust Boot and BootOrder variables.


At least HP laptops have no menu entry to configure Boot variables 
(OK, single entry may be configured in a rather inconvenient way) and 
shipped without EFI shell. That is why if installer does not modify the 
variables, Debian is not bootable.
I later discovered that the first install created a directory and 
put files into the Dell's ESP (!).  I did not select this, nor do I 
desire it.  This is a defect with d-i:


Why do you think it is wrong?


Because OS installers should not modify a disk unless the user 
authorizes it.


I agree if a computer is booted into MBR/BIOS/Compatibility mode or if 
expert install is selected. For regular UEFI install it is a trade-off 
since multiple OS loaders may coexist without conflicts. User should 
be asked if new OS should be booted by default (BootOrder), adding 
files to ESP is quite safe.


d-i should always ask before writing to disk.


I am not motivated enough to try debian installer in a similar 
configuration, even in a VM. Could you, please, confirm that after 
manual partitioning no one was configured as a ESP to be mounted at 
/boot/efi?


My expectations is the following. At the partitioning stage installer 
detects available ESP and if just single one is recognized it is 
configured by default as /boot/efi mount point. If this configuration 
option is not changed by the user, it is considered as acknowledgment to 
write files to the EFI/debian folder on this partition.


I do not have strong opinion, but I consider it as acceptable that if 
expert install is not enabled then installer may write files to ESP. It 
simplifies procedure for regular installs.


Here are my notes from a debian-9.9.0-amd64-xfce-CD-1 install on 


 Install GRUB into master boot record    Yes
 Device  /dev/sda


Am I right that it was not UEFI install? Certainly overwriting of MBR 
must be acknowledged by the user.


The point is that d-i asked before writing to disk.


My point is that UEFI and MBR install may have different behavior. You 
might underestimate role of implicit conventions and agreements.

AW: EPSON ET M 1120 new printer: If You can read this, you are using the wrong driver

[Schwibinger Michael]

Good morning
Thank You.

I dont understand this email.

Is there a different driver software for

32 bit
64 bit?


Can You inform me about both, please.

Regards
Sophie



Von: The Wanderer
Gesendet: Freitag, 14. April 2023 22:22
Bis: debian-user@lists.debian.org
Betreff: Re: EPSON ET M 1120 new printer: If You can read this, you are using 
the wrong driver

On 2023-04-14 at 18:10, Brian wrote:

> On Fri 14 Apr 2023 at 14:40:33 +, Schwibinger Michael wrote:
>
>> Good afternoon.
>> The new printer is not  working.
>> EPSON is saying
>> You cant use EPSON with Linux.
>>
>> Is this true?
>
> You could consider:
>
>   * Stating the Debain OS being used.
>   * Giving the printer make and model.

The make *was* stated: Epson.

The model may also have been stated, albeig only in the Subject line: ET
M1120. From a bit of Googling, the "ET" appears to stand for "EcoTank".

>   * Specifying the connection method. USB. Network.
>   * Giving the exact error message and where it came from.

Also:

* Starting a new thread to discuss the matter, rather than replying to
an existing message deep in an existing thread, deleting the body, and
changing the Subject line before sending.

(This question, and its replies, are appearing as responses to a mail
from Michael Stone in the 'update-initramfs' thread.)

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

Re: "Bug" in Debian Installer?

[David Christensen]

On 4/16/23 22:08, Max Nikulin wrote:

On 17/04/2023 09:18, David Christensen wrote:

On 4/16/23 03:41, Max Nikulin wrote:

On 16/04/2023 05:51, David Christensen wrote:
When I moved the 2.5" SATA SSD to a homebrew Intel DQ67SW computer 
and configured BIOS Setup:


 "Boot" -> "UEFI Boot" -> "Enable"

The SSD would not boot.


New boot entry usually should be created in such case from EFI Shell, 


I have realized that you may be confused by difference of MBR vs. UEFI 
behavior. For MBR it is enough to choose a disk to boot in BIOS, for 
UEFI it is necessary to add boot entries through EFI variables in 
firmware. Boot entry consists of disk, partition (EFI System partition) 
and path of an .efi file on this partition.


If so, you may suggest an additional subsection to
https://wiki.debian.org/UEFI#Troubleshooting_common_issues



Are you saying that d-i modifies the CMOS settings of UEFI computers?


I later discovered that the first install created a directory and 
put files into the Dell's ESP (!).  I did not select this, nor do I 
desire it.  This is a defect with d-i:


Why do you think it is wrong?


Because OS installers should not modify a disk unless the user 
authorizes it.


I agree if a computer is booted into MBR/BIOS/Compatibility mode or if 
expert install is selected. For regular UEFI install it is a trade-off 
since multiple OS loaders may coexist without conflicts. User should be 
asked if new OS should be booted by default (BootOrder), adding files to 
ESP is quite safe.



d-i should always ask before writing to disk.


Here are my notes from a debian-9.9.0-amd64-xfce-CD-1 install on 
February 2, 2020:


 Install GRUB into master boot record    Yes
 Device  /dev/sda

That was the proper way to do it.


Am I right that it was not UEFI install? Certainly overwriting of MBR 
must be acknowledged by the user.



The point is that d-i asked before writing to disk.


David

Re: Accesar a disco sin necesidad de root

[Alfonso Camacho]

Saludos:

> El 2023-04-16 a las 13:51 -0600, CAMP escribió:
> 
>> Tengo debian en una laptop sony vaio, debido a que la unidad de DVD
>> de descompuso, opte por ponerle un disco duro con un adaptador en la
>> unidad de DVD, todo muy bien, pero ¿como le puedo hacer para que
>> cuando acceso a dicho disco no me pida el password root?
> 
> Yo los tengo montados en un punto de montaje dedicado que he creado en
> /data, no en /media, para evitar problemas.
> 
> Además, los discos duros fijos los tengo definidos en el archivo
> /etc/fstab pero no recuerdo haber tenido que hacer nada especial para
> que no pida contraseña de root al iniciar el sistema y montar las
> unidades :-?
> 
> # Disco datos #1
> UUID=8ab7cc61-8d69-42d6-bfb8-112f0e0f8a40 /data/backup1 ext3
> acl,user_xattr,noauto,nofail,x-systemd.automount,x-systemd.device-timeout=1 1 
> 2

Si, estas cosas mejor hacerlas directamente desde /etc/fstab. Al disco se le 
pueden pasar opciones para montar ese dispositivo haciéndolo propiedad de un 
usuario (indicando su uid), incluso también cambiando el modo de ficheros  y 
directorios. Por ejemplo:

/dev/sdb1 /mnt/data defaults,uid=1001,dir_mode=0750,file_mode=0640 
0 0



-- 
Alfonso 

Re: Accesar a disco sin necesidad de root

[Camaleón]

El 2023-04-16 a las 13:51 -0600, CAMP escribió:

> Tengo debian en una laptop sony vaio, debido a que la unidad de DVD
> de descompuso, opte por ponerle un disco duro con un adaptador en la
> unidad de DVD, todo muy bien, pero ¿como le puedo hacer para que
> cuando acceso a dicho disco no me pida el password root?

Yo los tengo montados en un punto de montaje dedicado que he creado en 
/data, no en /media, para evitar problemas.

Además, los discos duros fijos los tengo definidos en el archivo 
/etc/fstab pero no recuerdo haber tenido que hacer nada especial para 
que no pida contraseña de root al iniciar el sistema y montar las 
unidades :-?

# Disco datos #1
UUID=8ab7cc61-8d69-42d6-bfb8-112f0e0f8a40 /data/backup1 ext3 
acl,user_xattr,noauto,nofail,x-systemd.automount,x-systemd.device-timeout=1 1 2

Saludos, 

-- 
Camaleón