Re: [OT] Selling beer (was: Re: Working for free [was: Offensive variable names])

[tomas]

On Thu, Jul 15, 2021 at 09:55:50AM +0300, Andrei POPESCU wrote:
> On Mi, 14 iul 21, 08:02:19, Charlie Gibbs wrote:

[...]

> > If they didn't pay [for ads], companies would have stopped sinking vast 
> > amounts
> > of effort and expense into them a century ago.
> 
> You're giving (big) companies a lot of credit, possibly unwarranted:
> 
> 
> Does Advertising Actually Work? (Part 1: TV) (Ep. 440)
> https://freakonomics.com/podcast/advertising-part-1/
> 
> Does Advertising Actually Work? (Part 2: Digital) (Ep. 441)
> https://freakonomics.com/podcast/advertising-part-2/

Thanks for the links :)

I always say (somewhat with tongue-in-cheek, I don't have the time
or stamina to come up with anything even resembling a proof) that
ad industry is like the rain dance [1]. Probably many doubt it helps
at all, but you allocate resources for it... just in case.

I have the hunch that much of modern economics works at this level
(heck, even their "Nobel Prize" is fake).

Cheers
[1] https://en.wikipedia.org/wiki/Rain_dance
 - t


signature.asc
Description: Digital signature

Re: MDs & Dentists

[Weaver]

On 15-07-2021 17:48, ellanios82 wrote:
> On 7/15/21 2:03 AM, jeremy ardley wrote:
>> suggesting Windows is certified for any risk of life application!?
>>
>> It has a huge spectrum of vulnerabilities
> 
> 
> 
>  - believe wikipedia had mention : 100% of world's super-computers run on 
> Linux

https://top500.org/statistics/list/
Cheers!

Harry

-- 
`When injustice becomes law, resistance becomes duty' 
-- Thomas Jefferson

Re: [OT] Selling beer (was: Re: Working for free [was: Offensive variable names])

[Andrei POPESCU]

On Mi, 14 iul 21, 08:02:19, Charlie Gibbs wrote:
> On Tue Jul 13 16:50:38 2021 Michael Lange  wrote:
> 
> > On Tue, 13 Jul 2021 21:25:17 +0100
> > Joe  wrote:
> >
> > (...)
> >
> >> Back when we had TV advertisements
> >> for beer, it was always the rubbish beers that got the publicity.
> >
> > here (Germany) we still have those TV ads for beer, and I can assure
> > you that the advertised brands (its not up to me to decide whether
> > they are rubbish or not) are the ones that are available virtually
> > everywhere, so I believe that it is safe to assume that they are
> > also the brands that sell.
> > So yes, unfortunately at least in some cases advertisements apparently
> > pay.
> 
> If they didn't pay, companies would have stopped sinking vast amounts
> of effort and expense into them a century ago.

You're giving (big) companies a lot of credit, possibly unwarranted:


Does Advertising Actually Work? (Part 1: TV) (Ep. 440)
https://freakonomics.com/podcast/advertising-part-1/

Does Advertising Actually Work? (Part 2: Digital) (Ep. 441)
https://freakonomics.com/podcast/advertising-part-2/

(the links contain the transcripts as well, for those who prefer 
reading)


Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser


signature.asc
Description: PGP signature

Re: MDs & Dentists

[Reco]

On Wed, Jul 14, 2021 at 06:26:58PM -0400, Polyna-Maude Racicot-Summerside wrote:
> Him
> 
> On 2021-07-14 3:42 p.m., ellanios82 wrote:
> > On 7/14/21 9:27 PM, Jude DaShiell wrote:
> >> Doctors and Dentists run windows as the base for all of their practice
> >> software.  I don't know of any linux software that could replace that
> >> software either.  Could it be some software house would be able to get
> >> linux versions available and make some money?
> > 
> >  - at one stage needed windows stuff : ran on Virtual-Box : perfect !!
> > 
> > 
> That's the usual "geek non-sense" answer.
> 
> Can you tell me one big advantage of using Linux in a medical practice ?

Sure, I can name two such advantages.

You cannot catch a ransomware cryptolocker using Linux on a desktop,
it's definitely Windows-only kind of software. In fact, any FOSS OS has
this advantage, unless you're using Wine (software).

Also, you can ensure that your patients' data won't be uploaded to M$ or
Apple, but that can be considered a common practice these days.

Reco

Re: MDs & Dentists

[ellanios82]

On 7/15/21 2:03 AM, jeremy ardley wrote:

suggesting Windows is certified for any risk of life application!?

It has a huge spectrum of vulnerabilities




 - believe wikipedia had mention : 100% of world's super-computers run 
on Linux





 rgds

.

Re: MDs & Dentists

[Jeremy Ardley]

On 15/7/21 4:00 pm, Weaver wrote:

On 15-07-2021 17:48, ellanios82 wrote:

On 7/15/21 2:03 AM, jeremy ardley wrote:

suggesting Windows is certified for any risk of life application!?

It has a huge spectrum of vulnerabilities



  - believe wikipedia had mention : 100% of world's super-computers run on Linux

https://top500.org/statistics/list/
Cheers!

Harry



I'm not sure how they differentiate Centos and RHEL from Linux, but yeah 
there doesn't seem to be much Windows in the space.


Also no Debian? Or is that in the 'Linux' fold, with Ubuntu sufficiently 
down-market to get it's own mentions?


--
Jeremy



OpenPGP_signature
Description: OpenPGP digital signature

Re: How do I mount the USB stick containing the installer in Rescue Mode?

[Joe]

On Thu, 15 Jul 2021 07:00:40 -0400
Greg Wooledge  wrote:

> On Thu, Jul 15, 2021 at 12:55:11PM +0300, Reco wrote:


> >  halt the boot
> > process (i.e. host is inaccessible by network, console access only)
> > even if a single filesystem mentioned in fstab fails to mount.  
> 
> This was the traditional behavior before systemd, so one can't really
> fault systemd for continuing the practice.
> 
> It's assumed that all file systems mentioned in /etc/fstab are
> essential to the correct operation of the system (unless otherwise
> specified).  If one of them doesn't mount, it means a disk is broken
> to the point where human intervention is required, so the operating
> system decides to play it safe and not continue.
> 

So when I switched my unstable installation from sysvinit to systemd and
it subsequently failed to boot because of a missing drive, that was just
coincidence, was it? My system had never been booting and for some
reason I'd never noticed?

OK, naming removable drives in /etc/fstab may not have been best
practice, but it never held up booting before systemd arrived. But to
be fair, consistent mounting of USB media was a shambles before
systemd, and naming USB drives in fstab was the only way to ensure that
it happened reliably. Remember usbmount and other bodges?

-- 
Joe

Nuevo

[Wilfredo Beyra]

Hola:
Soy nuevo en Debian. Acabo de instalar un CD co xfce pero no sale el
escritorio. La instalación se ejecutó sin problemas pero solo puedo usar la
consola. Por favor alguien que me explique como cargar el entorno de
escritorio. Gracias.
wbey...@gmail.com

Re: MDs & Dentists

[Polyna-Maude Racicot-Summerside]

Hi,

On 2021-07-15 7:01 a.m., Michael Lange wrote:
> Hi,
> 
> On Wed, 14 Jul 2021 18:26:58 -0400
> Polyna-Maude Racicot-Summerside  wrote:
> 
> (...)
>> Also can you find me one Linux distribution that is certified as medical
>> equipment for reliability ?
> 
> https://www.behnk.de/fully-automated-systems/
> 
> These lab machines run with debian (at least the Thrombolyzer XRC we
> once had in our lab did, Etch iirc), so apparently they are certified. I
> don't think these certifications are something the OS vendor has to do,
> it's the vendor of the machine that needs a certificate for the whole
> product.
> 
We finally get some sane words here.

Yes the certification is the "whole system" and not a piece by piece.
Sometime the OS supplier could get a certification / validation so it
gives him a commercial advantage but it's the whole system / stack that
require certification.

I never said there ain't any Linux device that do medical work in the
lab. One thing I do remember is that Germany is pushing for FOSS much
more than US/Canada.
> Regards
> 
> Michael
> 
> .-.. .. ...- .   .-.. --- -. --.   .- -. -..   .--. .-. --- ... .--. . .-.
> 
> When dreams become more important than reality, you give up travel,
> building, creating; you even forget how to repair the machines left
> behind by your ancestors.  You just sit living and reliving other lives
> left behind in the thought records.
>   -- Vina, "The Menagerie" ("The Cage"), stardate unknown
> 

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



OpenPGP_signature
Description: OpenPGP digital signature

[DEBIAN] Montar HD no boot automaticamente com permissão para usuários comuns

[Gilberto F da Silva]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Tue, Apr 13, 2021 at 02:29:42PM -0300, China wrote:
>Boa tarde.
>
>Instalei um SSD no notebook e o HD mecanico continua na máquina para
>ser usado como depósito de arquivos. O método que aparece para o
>acesso é clicar no Nautilus em "Outros locais" e clicar no HD, daí
>insere a senha de usuário e o HD é montado na pasta
>/media/$user/UID_do_HD. Não que este método não me atenda, mas quis
>fazer do jeito que conheço que é incluir a linha de montagem no
>/etc/fstab:
> "/dev/sda5 /home/china/Arquivos ext4 defauts 0 0"
>
>Com esta linha esperava o HD montado na pasta "Arquivos" dentro do meu
>/home, mas não funcionou, a máquina nem deu boot alegando violação do
>journal e parou na tela de manutenção. Só consegui dar o boot após
>comentar esta linha.
>
>No Google tem vários tutoriais ensinando este método e outros como
>usar a ferramenta "Discos" do Gnome, mas não funcionou para mim. Então
>pergunto: como montar o HD no boot que fique dentro do meu /home com
>permissões de usuário sem ter de clicar em lugar nenhum e colocar
>senha para montar?
>
>Ambiente Debian stable com kernel 5.10 do stech-backports.
>
>--
>Enviado de um dispositivo móvel
>

Eu tenho um HD externo que uso como /home e como partição de
dados. A partição de dados eu monto em /mnt/comum.

Você pode colocar sua partição em /mnt/Arquivos e depois criar um
link simbólico no seu home.

Talvez tenha de ajustar o dono dos seus arquivos com o chown.

- -- 

Stela dato:2.459.411,127  Loka tempo:2021-07-15 12:02:48 Ĵaŭdo
- -==-
"Deus é uma hipótese, e, como tal, depende de prova: o ônus da prova 
cabe ao teísta".
-- Percy Bysshe Shelley (1792-1822)
-BEGIN PGP SIGNATURE-
Comment: +-+
Comment: !   Gilberto F da Silva - ICQ 136.782.571 !
Comment: +-+

iF0EARECAB0WIQR6BybJIKBLy3+8xXcnG6Ba0yEbDgUCYPBPXwAKCRAnG6Ba0yEb
DvzbAKDsYe0pL54eZWhSPqJ6WzZsNT9uQwCfbVMbeDBLhRrkdrunPAba0nijw3M=
=Dmkf
-END PGP SIGNATURE-

Re: Donaciones y despedida de Debian

[Marcelo Eduardo Giordano]

Debian es un sistema increíble. Me parece un sistema muy recomendable 
para todo tipo de usuarios. Con tantos gustos que enamora. Tiene una 
estabilidad que llega a aburrir. Es como un tractor de Debian.


Saludos

El 14/7/21 a las 21:07, Marcelo P. Llanos C. escribió:
Chévere bro, adelante y éxitos en tu nuevo proyecto de aprendizaje, el 
conocimiento es universal


El sáb., 10 de jul. de 2021 10:21, Marcelo Eduardo Giordano 
mailto:contadorgiord...@gmail.com>> escribió:


Gracias amigo.

Seguimos en contacto

On 8/7/21 14:06, Raimundo Baravaglio wrote:

Ese link es una de las maneras de donación.
Aquí están todas las opciones: https://www.debian.org/donations


Saludos y éxitos en la incursión sobre Arch Linux !  ;)


Raimundo Baravaglio



El jue, 8 jul 2021 a las 12:38, Marcelo Eduardo Giordano
(mailto:contadorgiord...@gmail.com>>) escribió:

Amigos.

Le comento que he decido instalar Arch linux en mi PC
principal, aunque seguiré con Debian en otra computadora de
mi oficina.

Quedo muy agradecido de Debian con el cual empecé en el mundo
del open source, pero hoy quiero investigar otras cosas,
quizás mas profundas y deseo mucho estar a la última, con los
costes que esto trae.

Por eso quiero hacer una donación y tengo entendido que se
puede hacer en esta página. Quisiera que me corrijan si me
equivoco para ayudar a este hermoso proyecto.

https://www.spi-inc.org/donations/


Seguiré en contacto con ustedes y siempre estaré agradecido
de la ayuda que siempre me han dado.

-- 


Marcelo E. Giordano
//

Re: How do I mount the USB stick containing the installer in Rescue Mode?

[Stella Ashburne]

Hi guys,

There's a typo in my original post. Thanks to Reco for pointing it out to me.

> Sent: Thursday, July 15, 2021 at 9:43 AM
> From: "Stella Ashburne" 
> To: "debian-user mailing list" 
> Subject: How do I mount the USB stick containing the installer in Rescue Mode?
>
>
> When asked if I wanted to mount the separate /boot/efi partition, I entered 
> No.
>
> Next, I entered Executive a shell in /dev/perfect-vg/root
>

CORRECTION: Execute a shell in /dev/perfect-vg/root

Re: How do I mount the USB stick containing the installer in Rescue Mode?

[Reco]

Hi.

On Thu, Jul 15, 2021 at 01:52:12PM +0200, Stella Ashburne wrote:
> > A usual thing with the modern desktop environments.
> > Check the output of "mount" and "df -Th" and /dev/sdb1 will probably be
> > there. I'd like to see the output of these commands too, btw.
> >
> Output of mount is
> 
> root@perfect:/# mount
> /dev/mapper/perfect--vg-root on / type ext4 (rw,relatime)
> devtmpfs on /dev type devtmpfs 
> (rw,relatime,size=8137669k,nr_inodes=2034417,mode=755)
> proc on /proc type proc (rw,relatime)
> sysfs on /sys type sysfs (rw,relatime)
> tmpfs on /run type tmpfs (rw,nosuid,relatime,size=1629756k,mode=755)
> root@perfect:/#

And yet it fails to mount /dev/sdb1. Interesting.

Ok, how about this (I'm assuming that the USB stick in question is
plugged in):

lsblk

fdisk -l /dev/sdb

file -sL /dev/sdb1

ls -al /media/usbdisk

mountpoint /media/usbdisk

Reco

How do I mount the USB stick containing the installer in Rescue Mode?

[Stella Ashburne]

Debian Bullseye's installer is on a USB stick and I used it to boot into Rescue 
Mode. If it's of any relevance, the partition table type is GPT, with 
UEFI+Secure Boot enabled.

After booting into Rescue Mode and filling out the required details onscreen, I 
chose /dev/perfect-vg/root as the device to use as root file system. If you may 
recall, the volume group perfect-vg is LUKS-encrypted.

When asked if I wanted to mount the separate /boot/efi partition, I entered No.

Next, I entered Executive a shell in /dev/perfect-vg/root

I typed the command nano /etc/apt/sources.list and commented out all the lines 
therein.

I added the the following line:

deb [trusted=yes] file:/media/myusb bullseye main

I saved the sources.list file.

I created a directory called /media/myusb and issued the following command to 
mount the USB stick to it:

mount /dev/sdb1 /media/myusb

The error message is:

mount: /media/myusb: /dev/sdb1 already mounted or mount point busy

Below are the results of cat /etc/fstab

  

/dev/mapper/perfect--vg-root   /  ext4 errors-remount-ro   0   1
/boot/efi was on /dev/sda1 during installation
UUID=A30E-2C33/boot/efi vfatumask=0077  0  1
/dev/mapper/perfect--vg-swapnone   swapsw   0  0
/dev/sr0  /media/cdrom0 udf, iso9660 user, noauto   0  0
/media/myusb

I appreciate your help in this matter.

Re: How do I mount the USB stick containing the installer in Rescue Mode?

[Greg Wooledge]

On Thu, Jul 15, 2021 at 12:55:11PM +0300, Reco wrote:
> "nofail" is really needed for removable devices, because whoever
> designed systemd made an "interesting" decision to halt the boot process
> (i.e. host is inaccessible by network, console access only) even if a
> single filesystem mentioned in fstab fails to mount.

This was the traditional behavior before systemd, so one can't really
fault systemd for continuing the practice.

It's assumed that all file systems mentioned in /etc/fstab are essential
to the correct operation of the system (unless otherwise specified).  If
one of them doesn't mount, it means a disk is broken to the point where
human intervention is required, so the operating system decides to play
it safe and not continue.

Re: MDs & Dentists

[Michael Lange]

Hi,

On Wed, 14 Jul 2021 18:26:58 -0400
Polyna-Maude Racicot-Summerside  wrote:

(...)
> Also can you find me one Linux distribution that is certified as medical
> equipment for reliability ?

https://www.behnk.de/fully-automated-systems/

These lab machines run with debian (at least the Thrombolyzer XRC we
once had in our lab did, Etch iirc), so apparently they are certified. I
don't think these certifications are something the OS vendor has to do,
it's the vendor of the machine that needs a certificate for the whole
product.

Regards

Michael

.-.. .. ...- .   .-.. --- -. --.   .- -. -..   .--. .-. --- ... .--. . .-.

When dreams become more important than reality, you give up travel,
building, creating; you even forget how to repair the machines left
behind by your ancestors.  You just sit living and reliving other lives
left behind in the thought records.
-- Vina, "The Menagerie" ("The Cage"), stardate unknown

Re: How do I mount the USB stick containing the installer in Rescue Mode?

[Reco]

On Thu, Jul 15, 2021 at 07:00:40AM -0400, Greg Wooledge wrote:
> On Thu, Jul 15, 2021 at 12:55:11PM +0300, Reco wrote:
> > "nofail" is really needed for removable devices, because whoever
> > designed systemd made an "interesting" decision to halt the boot process
> > (i.e. host is inaccessible by network, console access only) even if a
> > single filesystem mentioned in fstab fails to mount.
> 
> This was the traditional behavior before systemd, so one can't really
> fault systemd for continuing the practice.

Not in Debian (sysvinit, upstart). RHEL, SuSE behaved exactly this way
indeed.

Reco

phone usb

[fxkl47BF]

does anyone know if the usb in this phone is supported by linux
https://www.lively.com/phones/lively-flip/

Re: Nuevo

[Debian]

El 15/7/21 a las 08:25, Wilfredo Beyra escribió:

Hola:
Soy nuevo en Debian. Acabo de instalar un CD co xfce pero no sale el 
escritorio. La instalación se ejecutó sin problemas pero solo puedo usar 
la consola. Por favor alguien que me explique como cargar el entorno de 
escritorio. Gracias.

wbey...@gmail.com 



Buen día y bienvenido.

Asumo que algo con la consola te defiendes.

Primero, veremos si está instalado el gestor de escritorio:
Prueba esta instrucción:
$ sudo cat /etc/X11/default-display-manager

Debe resultar en algo como
/usr/bin/sddm

Si no es así, ejecuta
$ apt install sddm
y luego reinicias el sistema.

Si sigues sin sesión gráfica, prueba lo siguiente:

$ sudo apt install task-xfce-desktop  --reinstall

Esto a verificar la instalación del entorno de escritorio xfce completo.
Luego, reinicia el sistema.

El Linux tienes que tener dos cosas para usar el escritorio: el gestor y 
el escritorio en sí; son independientes e "intercambables".


Mantenenos al tanto.

JAP

Re: How do I mount the USB stick containing the installer in Rescue Mode?

[Stella Ashburne]

Hi

> Sent: Thursday, July 15, 2021 at 9:55 AM
> From: "Reco" 
> To: debian-user@lists.debian.org
> Subject: Re: How do I mount the USB stick containing the installer in Rescue 
> Mode?
>
>   Hi.
>
> On Thu, Jul 15, 2021 at 11:43:26AM +0200, Stella Ashburne wrote:
> > Next, I entered Executive a shell in /dev/perfect-vg/root
>
> It's Superuser shell actually, not Supervisor/Executive one.
>
Thanks for pointing out my typo.
>
> Something has mounted your device elsewhere already.

I guess that when I used the USB-installer to boot my machine into Rescue Mode, 
the USB stick is mounted, yes?

> A usual thing with the modern desktop environments.
> Check the output of "mount" and "df -Th" and /dev/sdb1 will probably be
> there. I'd like to see the output of these commands too, btw.
>
Output of mount is

root@perfect:/# mount
/dev/mapper/perfect--vg-root on / type ext4 (rw,relatime)
devtmpfs on /dev type devtmpfs 
(rw,relatime,size=8137669k,nr_inodes=2034417,mode=755)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
tmpfs on /run type tmpfs (rw,nosuid,relatime,size=1629756k,mode=755)
root@perfect:/#

Output of dh -Th is

root@perfect:/# df -Th
FilesystemTypeSizeUsedAvailUse%   Mounted on
/dev/perfect-vg/root  ext436G 773M33G  3% /
devtmpfs  devtmpfs   7.8G0   7.8G  0% /dev
tmpfs tmpfs  1.6G  96K   1.6G  1% /run
root@perfect:/#

> If these are the full contents of /etc/fstab, it's incorrect.
> In addition to the mountpoint you should specify a block device (or its
> equivalent), filesystem type, mount points, dump/pass and that's the
> least.

Thanks for the mini instruction. I really appreciate it.

> I.e. this line is wrong:
>
> /media/myusb
>
> This line is correct:
>
> /dev/sdb1 /media/usb auto defaults,nofail 0 0
>
> "nofail" is really needed for removable devices, because whoever
> designed systemd made an "interesting" decision to halt the boot process
> (i.e. host is inaccessible by network, console access only) even if a
> single filesystem mentioned in fstab fails to mount.
> You may want to add "noauto" as well, see fstab(5).
>
I read fstab(5). Unfortunately such man pages don't contain examples to 
illustrate the arguments and options.
>
>

Re: MDs & Dentists

[Joe]

On Thu, 15 Jul 2021 07:03:18 +0800
jeremy ardley  wrote:


> You can't be seriously suggesting Windows is certified for any risk
> of life application!?
> 
> It has a huge spectrum of vulnerabilities and a constant stream of
> zero day exploits for both the O/S 

Yes, but most of them were placed there by Microsoft for the benefit of
the US government, and can be instantly removed when discovered (and
replaced by an alternative).

-- 
Joe

Re: MDs & Dentists

[tomas]

On Thu, Jul 15, 2021 at 10:27:25AM +0100, Joe wrote:
> On Thu, 15 Jul 2021 07:03:18 +0800
> jeremy ardley  wrote:
> 
> 
> > You can't be seriously suggesting Windows is certified for any risk
> > of life application!?
> > 
> > It has a huge spectrum of vulnerabilities and a constant stream of
> > zero day exploits for both the O/S 
> 
> Yes, but most of them were placed there by Microsoft for the benefit of
> the US government, and can be instantly removed when discovered (and
> replaced by an alternative).

Wrong.

They just want you to believe that, so that you come across as a
conspiracy theorist and people stop taking you seriously.

It's tuttles all the way down!

(tongue-in-cheek ;-P

 - tomás


signature.asc
Description: Digital signature

Re: How do I mount the USB stick containing the installer in Rescue Mode?

[Reco]

Hi.

On Thu, Jul 15, 2021 at 11:43:26AM +0200, Stella Ashburne wrote:
> Next, I entered Executive a shell in /dev/perfect-vg/root

It's Superuser shell actually, not Supervisor/Executive one.


> I created a directory called /media/myusb and issued the following command to 
> mount the USB stick to it:
> mount /dev/sdb1 /media/myusb
> 
> The error message is:
> mount: /media/myusb: /dev/sdb1 already mounted or mount point busy

Something has mounted your device elsewhere already.
A usual thing with the modern desktop environments.
Check the output of "mount" and "df -Th" and /dev/sdb1 will probably be
there. I'd like to see the output of these commands too, btw.


> Below are the results of cat /etc/fstab

If these are the full contents of /etc/fstab, it's incorrect.
In addition to the mountpoint you should specify a block device (or its
equivalent), filesystem type, mount points, dump/pass and that's the
least.

I.e. this line is wrong:

/media/myusb

This line is correct:

/dev/sdb1 /media/usb auto defaults,nofail 0 0

"nofail" is really needed for removable devices, because whoever
designed systemd made an "interesting" decision to halt the boot process
(i.e. host is inaccessible by network, console access only) even if a
single filesystem mentioned in fstab fails to mount.
You may want to add "noauto" as well, see fstab(5).

Reco

Re: How do I mount the USB stick containing the installer in Rescue Mode?

[The Wanderer]

On 2021-07-15 at 07:00, Greg Wooledge wrote:

> On Thu, Jul 15, 2021 at 12:55:11PM +0300, Reco wrote:
> 
>> "nofail" is really needed for removable devices, because whoever 
>> designed systemd made an "interesting" decision to halt the boot
>> process (i.e. host is inaccessible by network, console access only)
>> even if a single filesystem mentioned in fstab fails to mount.
> 
> This was the traditional behavior before systemd, so one can't
> really fault systemd for continuing the practice.
> 
> It's assumed that all file systems mentioned in /etc/fstab are
> essential to the correct operation of the system (unless otherwise
> specified).  If one of them doesn't mount, it means a disk is broken
> to the point where human intervention is required, so the operating
> system decides to play it safe and not continue.

Given the number of complaints I remember reading about cases where a
computer which had been working fine before failed to boot under
systemd, because there was a fstab entry which didn't have "nofail" set
where systemd needed it to be, I find the assertion that this was the
traditional behavior before systemd to be implausible.

-- 
   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: How do I mount the USB stick containing the installer in Rescue Mode?

[Stella Ashburne]

> Sent: Thursday, July 15, 2021 at 11:59 AM
> From: "Reco" 
> To: debian-user@lists.debian.org
> Subject: Re: How do I mount the USB stick containing the installer in Rescue 
> Mode?
>
> > Output of mount is
> >
> > root@perfect:/# mount
> > /dev/mapper/perfect--vg-root on / type ext4 (rw,relatime)
> > devtmpfs on /dev type devtmpfs 
> > (rw,relatime,size=8137669k,nr_inodes=2034417,mode=755)
> > proc on /proc type proc (rw,relatime)
> > sysfs on /sys type sysfs (rw,relatime)
> > tmpfs on /run type tmpfs (rw,nosuid,relatime,size=1629756k,mode=755)
> > root@perfect:/#
>
> And yet it fails to mount /dev/sdb1. Interesting.
>
I suppose the reason is that the USB stick is already mounted for booting into 
Rescue Mode.

> Ok, how about this (I'm assuming that the USB stick in question is
> plugged in):
>
Yes, it's always plugged in because I need it in Rescue Mode.

> lsblk
>
root@perfect:/# lsblk

NAME MAJ:MIN  RM   ROTYPEMOUNTPOINT
sda  8:0  00 disk
  sda1   8.1  00 part
  sda2   8:2  00 part
  sda3   8:3  00 part
sda3_crypt   253:000 crypt
  perfect--vg-swap   253:100 lvm
  perfect--vg-root   253:200 lvm /
sdb  8:16 10 disk
  sdb1   8:17 10 part
  sdb2   8:18 10 part
sr0  11:0 10 rom
root@perfect:/#

> fdisk -l /dev/sdb
>
root@perfect:/# fdisk -l /dev/sdb
Disk /dev/sdb

Device   BootStart End  SectorsSize  IdType
/dev/sdb1*   0 7677919  76779203.7G  0 Empty
/dev/sdb224260 294435184   2.5M  efEFI 
(FAT-12/16/32)
root@perfect:/#

> file -sL /dev/sdb1
>
root@perfect:/# file -sL /dev/sdb1
bash: file: command not found
root@perfect:/#


> ls -al /media/usbdisk
>
root@perfect:/# ls -al /media/usbdisk
ls: cannot access '/media/usbdisk' : No such file or directory

> mountpoint /media/usbdisk
>
root@perfect:/# mountpoint /media/usbdisk
mountpoint: /media/usbdisk : No such file or directory
root@perfect:/#

Re: How do I mount the USB stick containing the installer in Rescue Mode?

[David Wright]

On Thu 15 Jul 2021 at 11:43:26 (+0200), Stella Ashburne wrote:
> Debian Bullseye's installer is on a USB stick and I used it to boot into 
> Rescue Mode. If it's of any relevance, the partition table type is GPT, with 
> UEFI+Secure Boot enabled.
> 
> After booting into Rescue Mode and filling out the required details onscreen, 
> I chose /dev/perfect-vg/root as the device to use as root file system. If you 
> may recall, the volume group perfect-vg is LUKS-encrypted.
> 
> When asked if I wanted to mount the separate /boot/efi partition, I entered 
> No.
> 
> Next, I entered Executive a shell in /dev/perfect-vg/root
> 
> I typed the command nano /etc/apt/sources.list and commented out all the 
> lines therein.
> 
> I added the the following line:
> 
> deb [trusted=yes] file:/media/myusb bullseye main
> 
> I saved the sources.list file.
> 
> I created a directory called /media/myusb and issued the following command to 
> mount the USB stick to it:
> 
> mount /dev/sdb1 /media/myusb

Presumably given as root.

> The error message is:
> 
> mount: /media/myusb: /dev/sdb1 already mounted or mount point busy

Type:
$ ls -l /dev/disk/by-label/
to see what the kernel called your stick. Debian installers have LABELs.

> Below are the results of cat /etc/fstab
> 
>   
> 
> /dev/mapper/perfect--vg-root   /  ext4 errors-remount-ro   0  
>  1
> /boot/efi was on /dev/sda1 during installation

There's a # before that line

> UUID=A30E-2C33/boot/efi vfatumask=0077  0  1
> /dev/mapper/perfect--vg-swapnone   swapsw   0  0
> /dev/sr0  /media/cdrom0 udf, iso9660 user, noauto   0  0
> /media/myusb

That line looks spurious. If you put it there, I would remove it for
the time being. When you mount a USB stick as root, you don't need
an entry in fstab, but you do need to create a mount point first.
Of course, this has been done for you as a convenience: there is
a /mnt directory specifically for temporarily mounting a device.

Cheers,
David.

Re : Re: GPS, logiciels libres et Debian

[k6dedijon]

Bonjour Alexandre,
Il se peut que l'article que j'ai lu rapidement ait été l'objet d'une erreur de 
traduction.
Toutefois, ce n'est pas parce-que nous sommes 8 milliards qu'il ne devrait y 
avoir que 8 milliards d'appareils.
Certains ont 2 portables, nos armées sont équipées de Galliléo pour être 
indépendantes, les routiers ont des systèmes embarqués, l'aviation civile a 
aussi des systèmes embarqués, les pêcheurs, etc.

Bonne réflexion
Cassis



- Mail d'origine -
De: Alexandre Garreau 
À: debian-user-french@lists.debian.org
Envoyé: Tue, 13 Jul 2021 18:42:37 +0200 (CEST)
Objet: Re: GPS, logiciels libres et Debian

Le mardi 13 juillet 2021, 01:11:49 CEST k6dedi...@free.fr a écrit :
> Bonjour,
> Je suis surpris de cette réponse car il y a 1 billion d'utilisateurs.

Ça n’a jamais existé un billon d’humains simultanément en vie, 
actuellement on est que 8,5 milliards ou un truc du genre, pas 1000 fois 
plus.  Tu dois confondre avec l’anglais américain (qui utilise l’échelle 
courte) « billion », qui correspond au français et anglais européen (qui 
utilise l’échelle longue) « milliard ».

Et faut voir comment c’est compté.  Si ça se trouve c’est 1 milliards de 
GPS qui gèrent galileo en plus de gps, mais gps étant plus rapide ils 
utilisent en priorité GPS, même s’ils sont comptés dedans car gérant 
galiléo.  Ou alors, entre les deux, il utilise gps en priorité et galiléo 
sur les trucs plus lent/avec une latence plus longue, pour se corriger, 
chépa, un truc du genre u.u

Re: [OT] Selling beer (was: Re: Working for free [was: Offensive variable names])

[Polyna-Maude Racicot-Summerside]

Hi,

On 2021-07-14 11:29 a.m., Christian Groessler wrote:

> Here in Germany, near Munich, we have a beer brand (from Munich) which
> doesn't advertise but is the "standard beer" all around :-)
> 
WoW That's pretty cool, a "standard beer". Everyone get used to the same
beer and you don't risk being offered one of those bad tasting beer when
you go to a friend's house !

You go to a club and ask "the standard beer please". That will be good
for myself so I don't too much like a tourist.
> regards,
> chris
> 

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



OpenPGP_signature
Description: OpenPGP digital signature

Re: How do I mount the USB stick containing the installer in Rescue Mode?

[Brian]

On Thu 15 Jul 2021 at 20:01:05 +0200, Stella Ashburne wrote:

> root@perfect:/# file -sL /dev/sdb1
> bash: file: command not found
> root@perfect:/#

File is a standard utilty. It should be on your system.

 apt install file

-- 
Brian.

Re: How do I mount the USB stick containing the installer in Rescue Mode?

[Stella Ashburne]

> Sent: Thursday, July 15, 2021 at 3:49 PM
> From: "David Wright" 
> To: debian-user@lists.debian.org
> Subject: Re: How do I mount the USB stick containing the installer in Rescue 
> Mode?
>
> This
> might help the OP boot the system manually and recover the blue
> Grub menu.
>
That's very nice of you, David.

Re: [DEBIAN]__Montar_HD_no_boot automaticamente com permissão para usuários_comuns

[riesdra]

Olá, já tentou usar o "UUID" no lugar de "/dev/sda5"?



Pode haver incompatibildade com estas ordens dos dispositivos, usando UUID não 
teria este problema.





--
Ricardo Libanio






 Ativado Thu, 15 Jul 2021 12:08:26 -0300 Gilberto F da Silva 
<2458...@gmail.com> escreveu 


-BEGIN PGP SIGNED MESSAGE- 
Hash: SHA1 
 
On Tue, Apr 13, 2021 at 02:29:42PM -0300, China wrote: 
>Boa tarde. 
> 
>Instalei um SSD no notebook e o HD mecanico continua na máquina para 
>ser usado como depósito de arquivos. O método que aparece para o 
>acesso é clicar no Nautilus em "Outros locais" e clicar no HD, daí 
>insere a senha de usuário e o HD é montado na pasta 
>/media/$user/UID_do_HD. Não que este método não me atenda, mas quis 
>fazer do jeito que conheço que é incluir a linha de montagem no 
>/etc/fstab: 
> "/dev/sda5 /home/china/Arquivos ext4 defauts 0 0" 
> 
>Com esta linha esperava o HD montado na pasta "Arquivos" dentro do meu 
>/home, mas não funcionou, a máquina nem deu boot alegando violação do 
>journal e parou na tela de manutenção. Só consegui dar o boot após 
>comentar esta linha. 
> 
>No Google tem vários tutoriais ensinando este método e outros como 
>usar a ferramenta "Discos" do Gnome, mas não funcionou para mim. Então 
>pergunto: como montar o HD no boot que fique dentro do meu /home com 
>permissões de usuário sem ter de clicar em lugar nenhum e colocar 
>senha para montar? 
> 
>Ambiente Debian stable com kernel 5.10 do stech-backports. 
> 
>-- 
>Enviado de um dispositivo móvel 
> 
 
 Eu tenho um HD externo que uso como /home e como partição de 
 dados. A partição de dados eu monto em /mnt/comum. 
 
 Você pode colocar sua partição em /mnt/Arquivos e depois criar um 
 link simbólico no seu home. 
 
 Talvez tenha de ajustar o dono dos seus arquivos com o chown. 
 
- -- 
 
Stela dato:2.459.411,127  Loka tempo:2021-07-15 12:02:48 Ĵaŭdo 
- -==- 
"Deus é uma hipótese, e, como tal, depende de prova: o ônus da prova 
cabe ao teísta". 
 -- Percy Bysshe Shelley (1792-1822) 
-BEGIN PGP SIGNATURE- 
Comment: +-+ 
Comment: !   Gilberto F da Silva - ICQ 136.782.571 ! 
Comment: +-+ 
 
iF0EARECAB0WIQR6BybJIKBLy3+8xXcnG6Ba0yEbDgUCYPBPXwAKCRAnG6Ba0yEb 
DvzbAKDsYe0pL54eZWhSPqJ6WzZsNT9uQwCfbVMbeDBLhRrkdrunPAba0nijw3M= 
=Dmkf 
-END PGP SIGNATURE-

Re: Pas de prise en charge Bluetooth WiFi et carte graphique HD sur HP 15P R7

[François LE GAD]

Le 15/07/2021 à 10:11, I.N.R.I. a écrit :
J'utilise Debian 11 RC2 sur mon ordinateur portable HP pavillon modèle 
HP 15P R7 et je n'ai pas de prise en charge des drivers de BT WiFi et 
Carte vidéo HD.


Tape lspci dans un terminal, pour savoir ce qu'il y a sous le capot et 
poste la réponse ici. Il sera alors possible d'identifier les pilotes 
manquants.


Debian n'installe automatiquement que des pilotes libres. Les autres 
sont généralement dans les dépôts non-free, mais il faut aller les y 
chercher.


--
François

Re: How do I mount the USB stick containing the installer in Rescue Mode?

[David Wright]

On Thu 15 Jul 2021 at 14:59:36 (+0300), Reco wrote:
> On Thu, Jul 15, 2021 at 01:52:12PM +0200, Stella Ashburne wrote:
> > > A usual thing with the modern desktop environments.
> > > Check the output of "mount" and "df -Th" and /dev/sdb1 will probably be
> > > there. I'd like to see the output of these commands too, btw.
> > >
> > Output of mount is
> > 
> > root@perfect:/# mount
> > /dev/mapper/perfect--vg-root on / type ext4 (rw,relatime)
> > devtmpfs on /dev type devtmpfs 
> > (rw,relatime,size=8137669k,nr_inodes=2034417,mode=755)
> > proc on /proc type proc (rw,relatime)
> > sysfs on /sys type sysfs (rw,relatime)
> > tmpfs on /run type tmpfs (rw,nosuid,relatime,size=1629756k,mode=755)
> > root@perfect:/#
> 
> And yet it fails to mount /dev/sdb1. Interesting.
> 
> Ok, how about this (I'm assuming that the USB stick in question is
> plugged in):

It was probably plugged in for booting, and so it's likely /dev/sda,
demoting the system drive to /dev/sdb.

> lsblk
> 
> fdisk -l /dev/sdb
> 
> file -sL /dev/sdb1
> 
> ls -al /media/usbdisk
> 
> mountpoint /media/usbdisk

I think I saw in a previous post of yours in June that you have not
only an encrypted system but also physical volumes and that lvm stuff.
Perhaps you might post the contents of the first menuentry stanza in
your grub.cfg, and confirm that your volumes are contained in an
outer encrypted partition (if I expressed that correctly). This
might help the OP boot the system manually and recover the blue
Grub menu.

Cheers,
David.

programas

[Dilermando B. dos R. Monteiro]

Boa Tarde

Venho através desse comunicado, pedir suporte, pois os tutóriais não me 
ajudam no desenvolvimento de meus compromisso, vejo tutóriais, todos 
muito bem elaborados, mas, nada de acordo com o sistéma operacional de 
minha máquina.


A baixo programas que necessito em minha máquina, mas não consigo 
sufluir dos mesmo, sempre aparece uma janela informando que o sistéma 
operacional não é compativel com o programa, e assim fico sem recurso 
para poder trabalhar.


Vejo tutóriais falando a respeito de minha necessidade, mas, quando vou 
colocar em prática, acompanhado do tutórial e videos, não consigo 
executar, sempre da erro, ou não existente, por favor, preciso da ajuda 
de vocês


des de já agradeco.

Att: Dilermando Basilio dos Reis Monteiro.

Buster+Gnome on Pi4

[pcr]

Recently I flashed the 20200210 build of debian to a 128 GB A2 SanDisk 
micro sd card and I have been using in in in my raspberry pi.  I 
recently lost my desktop to a crash, so I am temporarily relying on the 
Pi.  So far it pretty good, about as fast as my old i3 laptop; one bug, 
however, is a black rectangle that appears on the middle of my screen 
occasionally.  It goes away if I right click-left click, or if I waggle 
the mouse pointer over the black rectangle, so it remains usable.  Ill 
let you know how it goes.

Re: How do I mount the USB stick containing the installer in Rescue Mode?

[Thomas Schmitt]

Hi,

Stella Ashburne wrote:
> root@perfect:/# mount /dev/sdb1 /mnt
> mount: /mnt: /dev/sdb1 already mounted or mount point busy

Well, since the case "already mounted" is quite outruled, it might be time
to explore "mount point busy".

  
https://codesearch.debian.net/search?q=package%3Autil-linux+already+mounted+or+mount+point+busy
shows that mount(8) emits this message if it gets error code EBUSY.
It is not so clear from where this code comes, but mount(2) would be a
fine candidate (or placeholder).

  EBUSY  [...]   Or,  it
 cannot  be mounted on target because target is still busy (it is
 the working directory of some thread, the mount point of another
 device, has open files, etc.).

So does it work with some other, newly created directory instead of /mnt ?


Have a nice day :)

Thomas

Re: How do I mount the USB stick containing the installer in Rescue Mode?

[Stella Ashburne]

Hi

> Sent: Thursday, July 15, 2021 at 7:07 PM
> From: "Reco" 
> To: debian-user@lists.debian.org
> Subject: Re: How do I mount the USB stick containing the installer in Rescue 
> Mode?

> Ok. Can you use this rescue mode to execute an ordinary shell, with full
> access to all filesystems?

Before I proceed with your suggestion, while in Resuce Mode, do I enter the 
encryption passphrase or not? If I don't enter the password, 
/dev/perfect-vg/root won't be mounted.

Even after I've entered the encryption passphrase, there are two ways to 
execute a shell: one is to execute it in /dev/perfect-vg/root environment and 
the other is to execute it in the installer environment. Which environment do 
you want me to executve a shell in please?

What did you mean by "full access to all filesystems"? When I was installing 
Debian 11, I first encrypted a free space with LUKS and then created two 
logical volumes in it: one whose mount point is / (the root file system. Debian 
installer requires it; otherwise the installation can't and won't proceed.) 
while the other is "used as" swap area.

> If you're using your USB stick to boot, you have its file system
> (/dev/sdb1 in this case) mounted.

That's a logical assumption because I needed the USB-installer to boot into 
Rescue Mode.

> If you're executing a shell in a
> logical volume, you're chrooted into that filesystem.

I had to enter the encryption passphrase first, followed by mounting 
/dev/perfect-vg/root as a root file system temporarily. Then I chose 'Execute a 
shell in the installer environment' and only then would I be able to chroot 
/target

> But it does not change that the filesystem from /dev/sdb1 is mounted
> already, it's just inaccessible from the chroot.
>
That's why I asked for help here.

> What you actually need is to bind mount the directory with packages into
> the mounted /dev/perfect-vg/root, and just chroot into it. No need to
> modify /etc/fstab at all.
>
Could you be so nice as to give me the command(s) to bind mount the directory 
with packages? Thank you.

Re: How do I mount the USB stick containing the installer in Rescue Mode?

[Reco]

Hi.

On Thu, Jul 15, 2021 at 11:30:10AM -0400, Stefan Monnier wrote:
> Greg Wooledge [2021-07-15 07:00:40] wrote:
> > On Thu, Jul 15, 2021 at 12:55:11PM +0300, Reco wrote:
> >> "nofail" is really needed for removable devices, because whoever
> >> designed systemd made an "interesting" decision to halt the boot process
> >> (i.e. host is inaccessible by network, console access only) even if a
> >> single filesystem mentioned in fstab fails to mount.
> > This was the traditional behavior before systemd, so one can't really
> > fault systemd for continuing the practice.
> 
> That's not my recollection.  AFAIK before systemd, you'd just get an
> error message and the boot would just (try to) continue.

My words exactly.


> I don't think systemd's decision is bad.

You have a remote server.
You modify fstab on that server.
You reboot a server after that, and maybe a lot of time had passed since
fstab modification.

Now you have a system that's inaccessible via SSH/VNC/whatever network
protocol you're using for remote access. Good luck unbricking this
system, especially if it does require a road trip. Or paying for renting
KVM. Or soldering UART, because manufacturer haven't exposed it to the
end user.

I cannot call that an improvement, because I do remember how it used to
work in Debian before systemd. To systemd's defence - RedHat version of
sysvinit did exactly the same in this regard.


Could be worse, I guess. One can render modern AIX unbootable by simply
adding inaccessible NFS mount to /etc/filesystems (they call /etc/fstab
this way). At least systemd is "smart" enough to avoid such pitfall.


> But I think it's implementation is not good enough: it should offer
> some kind of simple "continue y/n?" prompt.
> [ "Simple" for the user: the implementation might be not so simple.  ]

That'd change nothing important, really.
You'd have to be at the console to answer such question, you cannot just
boot somehow and fix things after via SSH.


> To be honest, I've added the `nofail` pretty much everywhere and hence
> haven't faced this problem recently, so for all I know, the
> implementation has already been improved.

Nope, it did not. I've faced similar problem just two days ago.
>From the upstream POV the current behaviour is correct, so there's
nothing to improve.

Reco

Re: How do I mount the USB stick containing the installer in Rescue Mode?

[Stella Ashburne]

Hello Thomas

> Sent: Thursday, July 15, 2021 at 7:30 PM
> From: "Thomas Schmitt" 
> To: debian-user@lists.debian.org
> Subject: Re: How do I mount the USB stick containing the installer in Rescue 
> Mode?
>
> Well, since the case "already mounted" is quite outruled, it might be time
> to explore "mount point busy".
>
>   
> https://codesearch.debian.net/search?q=package%3Autil-linux+already+mounted+or+mount+point+busy
> shows that mount(8) emits this message if it gets error code EBUSY.
> It is not so clear from where this code comes, but mount(2) would be a
> fine candidate (or placeholder).

In Rescue Mode, it's impossible for me to install packages such as the one 
whose link you had provided.

>
> So does it work with some other, newly created directory instead of /mnt ?
>

No, it doesn't work with other newly created directories in addition to /mnt.

> Have a nice day :)
>
You too.
> Thomas
>
Stella

Re: How do I mount the USB stick containing the installer in Rescue Mode?

[Greg Wooledge]

On Thu, Jul 15, 2021 at 10:15:59PM +0200, Stella Ashburne wrote:
> > From: "David Wright" 

> > Best I can do. (And I see that your kernel's naming of sda/sdb
> > is more stable than on at least a couple of my machines.)
> >
> What did you mean by "more stable"?

The reason we strongly discourage the use of /dev/sda1 (and similar
device names) in the /etc/fstab file is because those device names
are not stable.  This means they are not guaranteed to remain the same
each time you boot.  The disk that is called "sda" right now might be
called "sdb" next time you boot.

This can happen due to kernel changes, hardware changes, or simply race
conditions even if *nothing* has changed.

Because of this unreliable naming, various alternatives are suggested.
On most Debian installs, the fstab file is populated using the UUID of
each file system that's known at installation time.  That looks something
like this:

#
# / was on /dev/sda7 during installation
UUID=c4691ccb-2090-491e-8e82-d7cc822db04a /   ext4
errors=remount-ro 0   1
# /boot/efi was on /dev/sda1 during installation
UUID=4C30-7972  /boot/efi   vfatumask=0077  0   1
# /home was on /dev/sda8 during installation
UUID=19fb397b-a113-4536-a03d-d60e176cbfdf /home   ext4defaults  
  0   2
# /stuff was on /dev/sda9 during installation
UUID=95058c4a-44e2-4a90-87b5-2a5fe40d3cdb /stuff  ext4defaults  
  0   2
# swap was on /dev/sda6 during installation
UUID=08c87bdb-17f4-40ab-9b2f-5cb2f29149fb noneswapsw
  0   0
/dev/sr0/media/cdrom0   udf,iso9660 user,noauto 0   0


Another method is to put "labels" on each file system, and then use those
labels in the fstab file.  That works great for some people, especially
people who are very organized, and like to take charge of the details
themselves.

Another method is to identify some unique device that will always refer to
the device in question, and use that in the fstab file.  For example, you
might decide that on your particular system,

/dev/disk/by-path/pci-:00:17.0-ata-1-part9

is a reliable name, and will always refer to the partition that you want to
mount, and you may choose to use that in your fstab file.  (This is a
device that I pulled at random from my desktop PC, and it's referring to
a partition by referencing the PCI ID of the disk controller.  This is
actually *not* a stable name.  It's a very bad name.  PCI IDs change all
the time, and should not be relied upon.  *cough* network interface naming.)

Anyway, that's what "stable" means in this context.

Re: How do I mount the USB stick containing the installer in Rescue Mode?

[David Wright]

On Thu 15 Jul 2021 at 19:26:43 (+0100), Brian wrote:
> On Thu 15 Jul 2021 at 20:01:05 +0200, Stella Ashburne wrote:
> 
> > root@perfect:/# file -sL /dev/sdb1
> > bash: file: command not found
> > root@perfect:/#
> 
> File is a standard utilty. It should be on your system.

That's right, it's the 16th deb to be installed at the main
installation stage, but if you use the installer stick for
rescue, I don't think it's installed early enough.

>  apt install file

Chicken and egg: I think the OP is trying to set up some sort of
repository to install packages from. (I can't be sure. I would
have preferred it if they'd continued to try and boot their
actual installed system, but any help I might have given
fell short because I have no experience with LVM.)

Cheers,
David.

Re: programas

[tomas]

On Thu, Jul 15, 2021 at 12:41:11PM -0300, Dilermando B. dos R. Monteiro wrote:
> Boa Tarde

Boa tarde

En portugues, melhor https://lists.debian.org/debian-user-portuguese/

:-)

Saludos
 - tomás


signature.asc
Description: Digital signature

Re: How do I mount the USB stick containing the installer in Rescue Mode?

[Stella Ashburne]

Hi David

> Sent: Thursday, July 15, 2021 at 6:42 PM
> From: "David Wright" 
> To: debian-user@lists.debian.org
> Subject: Re: How do I mount the USB stick containing the installer in Rescue 
> Mode?
>
> That's right, it's the 16th deb to be installed at the main
> installation stage, but if you use the installer stick for
> rescue, I don't think it's installed early enough.
>
Based on the result of typing the 'file' command, it's appears that the package 
'file' isn't installed when one is using Rescue Mode.


> Chicken and egg: I think the OP is trying to set up some sort of
> repository to install packages from. (I can't be sure.

Your guess is right. I wish to install linux-image-5.10.0-7-amd64.deb onto 
chroot /target after entering Rescue Mode.

> I would
> have preferred it if they'd continued to try and boot their
> actual installed system,

At this moment I don't have a GRUB menu.

> but any help I might have given
> fell short because I have no experience with LVM.)

Oh..but you've helped me in other ways and for which I appreciate it very much.

Re: How do I mount the USB stick containing the installer in Rescue Mode?

[David Wright]

On Thu 15 Jul 2021 at 20:29:53 (+0200), Stella Ashburne wrote:
> > Sent: Thursday, July 15, 2021 at 3:49 PM
> > From: "David Wright" 
> > To: debian-user@lists.debian.org
> > Subject: Re: How do I mount the USB stick containing the installer in 
> > Rescue Mode?
> >
> > This
> > might help the OP boot the system manually and recover the blue
> > Grub menu.
> >
> That's very nice of you, David.

Best I can do. (And I see that your kernel's naming of sda/sdb
is more stable than on at least a couple of my machines.)

It might be worth posting a request for the stanza I asked for,
but as a new topic with a specific Subject line. I can't see
why you shouldn't be able to boot your system with manual Grub
commands. I was surprised how easy it was with an encrypted root
filesystem, needing no more than just the usual three lines:
set root=, linux and initrd. The only unusual thing was that
the foo in linux root=foo … is not visible with Grub>
commands (because it's still locked inside the encryption).

Cheers,
David.

Re: How do I mount the USB stick containing the installer in Rescue Mode?

[Reco]

Hi.

On Thu, Jul 15, 2021 at 08:38:59PM +0200, Stella Ashburne wrote:
> > Sent: Thursday, July 15, 2021 at 6:26 PM
> > From: "Brian" 
> > To: debian-user@lists.debian.org
> > Subject: Re: How do I mount the USB stick containing the installer in 
> > Rescue Mode?
> >
> > On Thu 15 Jul 2021 at 20:01:05 +0200, Stella Ashburne wrote:
> >
> > > root@perfect:/# file -sL /dev/sdb1
> > > bash: file: command not found
> > > root@perfect:/#
> >
> Nope, apparently it isn't available in Rescue Mode.
> 
> Entered encryption passphrase -> Choose a device to use as root file system 
> -> /dev/perfect-vg/root -> Execute a shell in /dev/perfect-vg/root

Ok. Can you use this rescue mode to execute an ordinary shell, with full
access to all filesystems?
I've been thinking about it, and it makes some sense.

If you're using your USB stick to boot, you have its file system
(/dev/sdb1 in this case) mounted. If you're executing a shell in a
logical volume, you're chrooted into that filesystem.

But it does not change that the filesystem from /dev/sdb1 is mounted
already, it's just inaccessible from the chroot.


What you actually need is to bind mount the directory with packages into
the mounted /dev/perfect-vg/root, and just chroot into it. No need to
modify /etc/fstab at all.

Reco

Re: How do I mount the USB stick containing the installer in Rescue Mode?

[Stefan Monnier]

Greg Wooledge [2021-07-15 07:00:40] wrote:
> On Thu, Jul 15, 2021 at 12:55:11PM +0300, Reco wrote:
>> "nofail" is really needed for removable devices, because whoever
>> designed systemd made an "interesting" decision to halt the boot process
>> (i.e. host is inaccessible by network, console access only) even if a
>> single filesystem mentioned in fstab fails to mount.
> This was the traditional behavior before systemd, so one can't really
> fault systemd for continuing the practice.

That's not my recollection.  AFAIK before systemd, you'd just get an
error message and the boot would just (try to) continue.

I don't think systemd's decision is bad.  But I think it's implementation is
not good enough: it should offer some kind of simple "continue
y/n?" prompt.
[ "Simple" for the user: the implementation might be not so simple.  ]

To be honest, I've added the `nofail` pretty much everywhere and hence
haven't faced this problem recently, so for all I know, the
implementation has already been improved.  But the behavior I saw back
when moving to systemd was definitely not pleasant.


Stefan

Re: How do I mount the USB stick containing the installer in Rescue Mode?

[Stella Ashburne]

Hello David

> Sent: Thursday, July 15, 2021 at 7:08 PM
> From: "David Wright" 
> To: debian-user@lists.debian.org
> Subject: Re: How do I mount the USB stick containing the installer in Rescue 
> Mode?
>
>
> Best I can do. (And I see that your kernel's naming of sda/sdb
> is more stable than on at least a couple of my machines.)
>
What did you mean by "more stable"?

> It might be worth posting a request for the stanza I asked for,
> but as a new topic with a specific Subject line.

What "stanza" were you referring to? Was it Reco who posted it? And you wrote 
that it was posted some time in June?

> I can't see
> why you shouldn't be able to boot your system with manual Grub
> commands.

I thought so too. GRUB developers would and should have built a "Rescue Mode" 
by just entering the commands.

Re: Buster+Gnome on Pi4

[Josef Strýček]

Hi,
Debian on Pi4 have disabled 3D acceleration, so it makes desktop slow and  
bugs. It can solve upgrade kernel to 5.10 from buster-backports or if you are 
on bullseye only upgrade.

Good luck, Josef


15. 7. 2021 20:50:46 pcr :

> Recently I flashed the 20200210 build of debian to a 128 GB A2 SanDisk
> micro sd card and I have been using in in in my raspberry pi.  I
> recently lost my desktop to a crash, so I am temporarily relying on the
> Pi.  So far it pretty good, about as fast as my old i3 laptop; one bug,
> however, is a black rectangle that appears on the middle of my screen
> occasionally.  It goes away if I right click-left click, or if I waggle
> the mouse pointer over the black rectangle, so it remains usable.  Ill
> let you know how it goes.

Re: How do I mount the USB stick containing the installer in Rescue Mode?

[Stella Ashburne]

> Sent: Thursday, July 15, 2021 at 6:26 PM
> From: "Brian" 
> To: debian-user@lists.debian.org
> Subject: Re: How do I mount the USB stick containing the installer in Rescue 
> Mode?
>
> On Thu 15 Jul 2021 at 20:01:05 +0200, Stella Ashburne wrote:
>
> > root@perfect:/# file -sL /dev/sdb1
> > bash: file: command not found
> > root@perfect:/#
>
Nope, apparently it isn't available in Rescue Mode.

Entered encryption passphrase -> Choose a device to use as root file system -> 
/dev/perfect-vg/root -> Execute a shell in /dev/perfect-vg/root


> File is a standard utilty. It should be on your system.

It isn't available in Rescue Mode.
>
>  apt install file
>
Unable to install now as I'm in Rescue Mode without an internet connection. The 
only way for me to install packages is to use the USB-installer (Debian 11) and 
I can't mount it.

Re: How do I mount the USB stick containing the installer in Rescue Mode?

[Stella Ashburne]

Hello David,

Nice to hear from you again.

> Sent: Thursday, July 15, 2021 at 4:05 PM
> From: "David Wright" 
> To: debian-user@lists.debian.org
> Subject: Re: How do I mount the USB stick containing the installer in Rescue 
> Mode?
>
> Presumably given as root.
>
A definite yes because I chose to mount /dev/perfect-vg/root as a root file 
system in Rescue Mode.

> > The error message is:
> >
> > mount: /media/myusb: /dev/sdb1 already mounted or mount point busy
>
> Type:
> $ ls -l /dev/disk/by-label/
> to see what the kernel called your stick. Debian installers have LABELs.

root@perfect:/# ls -l /dev/disk/by-label/
Total 0
lrwxrwxrwx 1 root root 10 Jul 15 17:00 'Debian\x20testing\x20amd64\x201' --> 
../../sdb1
root@perfect:/#

>
> > Below are the results of cat /etc/fstab
> >
> >  
> >  
> > /dev/mapper/perfect--vg-root   /  ext4 errors-remount-ro   
> > 0   1
> > /boot/efi was on /dev/sda1 during installation
>
> There's a # before that line
>
Which line please?

> > UUID=A30E-2C33/boot/efi vfatumask=0077  0  1
> > /dev/mapper/perfect--vg-swapnone   swapsw   0  0
> > /dev/sr0  /media/cdrom0 udf, iso9660 user, noauto   0  0
> > /media/myusb
>
> That line looks spurious. If you put it there, I would remove it for
> the time being.
>
Did you mean /media/myusb ?

> When you mount a USB stick as root, you don't need
> an entry in fstab, but you do need to create a mount point first.

I didn't know that I didn't need to create an entry in fstab if I mount a USB 
stick as root.

> Of course, this has been done for you as a convenience: there is
> a /mnt directory specifically for temporarily mounting a device.
>
root@perfect:/# mount /dev/sdb1 /mnt
mount: /mnt: /dev/sdb1 already mounted or mount point busy
root@perfect:/#

Re: Nuevo

[Wilfredo Beyra]

Realmente no se practicamente nada de consola. Se logearme, pero no se
apagar ni reiniciar. Estoy leyendo un tutorial que se llama paratorpes. La
cuestión es que no se apagar, ni reiniciar el equipo. Lei que el comando
para apagar es halt, pero cuando lo escribo me sale que esa orden no
existe. Cuando el sistema arranca se queda una pantalla oscura con un
cursor parpadeante en la esquina superior izquierda. Cuando presiono
Ctrl+Alt+F1 se cambia al modo consola, hasta ahí ok, sin embargo Alt+F7 que
debería cambiar a modo gráfico me devuelve a la pantalla oscura con el
cursor.
Traté con la orden que me enviaste pero entonces me pide password para la
sesión, pues la sesión que inicié es de usuario normal, no root. Estos son
mis primeros pasos en el mundo del software libre, por favor tenganme
paciencia. Gracias por responder tan rápido.
Wbeyras

El jue., 15 de jul. de 2021 7:38 AM, Debian 
escribió:

> El 15/7/21 a las 08:25, Wilfredo Beyra escribió:
> > Hola:
> > Soy nuevo en Debian. Acabo de instalar un CD co xfce pero no sale el
> > escritorio. La instalación se ejecutó sin problemas pero solo puedo usar
> > la consola. Por favor alguien que me explique como cargar el entorno de
> > escritorio. Gracias.
> > wbey...@gmail.com 
>
>
> Buen día y bienvenido.
>
> Asumo que algo con la consola te defiendes.
>
> Primero, veremos si está instalado el gestor de escritorio:
> Prueba esta instrucción:
> $ sudo cat /etc/X11/default-display-manager
>
> Debe resultar en algo como
> /usr/bin/sddm
>
> Si no es así, ejecuta
> $ apt install sddm
> y luego reinicias el sistema.
>
> Si sigues sin sesión gráfica, prueba lo siguiente:
>
> $ sudo apt install task-xfce-desktop  --reinstall
>
> Esto a verificar la instalación del entorno de escritorio xfce completo.
> Luego, reinicia el sistema.
>
> El Linux tienes que tener dos cosas para usar el escritorio: el gestor y
> el escritorio en sí; son independientes e "intercambables".
>
> Mantenenos al tanto.
>
> JAP
>
>

Re: Montar HD no boot automaticamente com permissão para usuários comuns

[Marcelo Medeiros Soares]

Desculpa a ignorância, mas como ficou a linha no seu fstab após acrescentar
o UUID?
Tenho um outro HD e sempre monto ele usando a opção de clicar no Nautilus
em "Outros locais"... Também gostaria que ele pudesse montar
automaticamente.
Obrigado.

Atenciosamente,

Marcelo Medeiros Soares
Consultor Imobiliário - CRECI nº 8457
Tel.: (71) 9265-8740 / 8887-3953

Visite nosso blog: *www.marcelomsoares.blogspot.com*


Em qua., 14 de abr. de 2021 às 14:03, China  escreveu:

> A resposta do Juscelino foi a solução para mim. Eu já tinha criado o
> ponto de montagem, mas não funcionou declarando o inode do HD como
> antigamente. Coloquei o UID e tá de boa. Obrigado!
>
> Em ter., 13 de abr. de 2021 às 15:17, Juscelino Cordeiro
>  escreveu:
> >
> > Tenta executar o comando sudo blkid e pegar o uid do disco. Coloca no
> fstab no lugar de /dev/sda5.
> > Talvez seja necessário criar a pasta onde vc quer o hd seja montado.
> >
> > Em ter, 13 de abr de 2021 14:48, China  escreveu:
> >>
> >> Boa tarde.
> >>
> >> Instalei um SSD no notebook e o HD mecanico continua na máquina para
> >> ser usado como depósito de arquivos. O método que aparece para o
> >> acesso é clicar no Nautilus em "Outros locais" e clicar no HD, daí
> >> insere a senha de usuário e o HD é montado na pasta
> >> /media/$user/UID_do_HD. Não que este método não me atenda, mas quis
> >> fazer do jeito que conheço que é incluir a linha de montagem no
> >> /etc/fstab:
> >>  "/dev/sda5 /home/china/Arquivos ext4 defauts 0 0"
> >>
> >> Com esta linha esperava o HD montado na pasta "Arquivos" dentro do meu
> >> /home, mas não funcionou, a máquina nem deu boot alegando violação do
> >> journal e parou na tela de manutenção. Só consegui dar o boot após
> >> comentar esta linha.
> >>
> >> No Google tem vários tutoriais ensinando este método e outros como
> >> usar a ferramenta "Discos" do Gnome, mas não funcionou para mim. Então
> >> pergunto: como montar o HD no boot que fique dentro do meu /home com
> >> permissões de usuário sem ter de clicar em lugar nenhum e colocar
> >> senha para montar?
> >>
> >> Ambiente Debian stable com kernel 5.10 do stech-backports.
> >>
> >> --
> >> Enviado de um dispositivo móvel
> >>
>
>
> --
>
> Enviado de um dispositivo móvel
>
>

Re: How do I mount the USB stick containing the installer in Rescue Mode?

[David Wright]

On Thu 15 Jul 2021 at 20:52:34 (+0200), Stella Ashburne wrote:
> > Sent: Thursday, July 15, 2021 at 4:05 PM
> > From: "David Wright" 
> >
> > Presumably given as root.
> >
> A definite yes because I chose to mount /dev/perfect-vg/root as a root file 
> system in Rescue Mode.
> 
> > > The error message is:
> > >
> > > mount: /media/myusb: /dev/sdb1 already mounted or mount point busy
> >
> > Type:
> > $ ls -l /dev/disk/by-label/
> > to see what the kernel called your stick. Debian installers have LABELs.
> 
> root@perfect:/# ls -l /dev/disk/by-label/
> Total 0
> lrwxrwxrwx 1 root root 10 Jul 15 17:00 'Debian\x20testing\x20amd64\x201' --> 
> ../../sdb1
> root@perfect:/#
> 
> >
> > > Below are the results of cat /etc/fstab
> > >
> > >
> > >
> > > /dev/mapper/perfect--vg-root   /  ext4 errors-remount-ro  
> > >  0   1
> > > /boot/efi was on /dev/sda1 during installation
> >
> > There's a # before that line
> >
> Which line please?

The last line quoted, ie the line should read

# /boot/efi was on /dev/sda1 during installation

> > > UUID=A30E-2C33/boot/efi vfatumask=0077  0  1
> > > /dev/mapper/perfect--vg-swapnone   swapsw   0  0
> > > /dev/sr0  /media/cdrom0 udf, iso9660 user, noauto   0  0
> > > /media/myusb
> >
> > That line looks spurious. If you put it there, I would remove it for
> > the time being.
> >
> Did you mean /media/myusb ?

Yes, an entry in fstab needs at least four fields:
Device   Mountpoint   FStype   Options

I presume you type /etc/fstab into your post, both because of the
missing # for the comment, and because the /dev/sr0 line has too
many fields. It should contain   udf,iso9660 user,noauto
without spaces after the commas.

> > When you mount a USB stick as root, you don't need
> > an entry in fstab, but you do need to create a mount point first.
> 
> I didn't know that I didn't need to create an entry in fstab if I mount a USB 
> stick as root.
> 
> > Of course, this has been done for you as a convenience: there is
> > a /mnt directory specifically for temporarily mounting a device.
> >
> root@perfect:/# mount /dev/sdb1 /mnt
> mount: /mnt: /dev/sdb1 already mounted or mount point busy
> root@perfect:/#

The principal function of fstab is to describe filesystems that need
mounting by the OS for it to carry out its normal functions.
A second function is to hold information so that filesystems can be
mounted merely by mentioning only the device or the mountpoint.
A third is to make it possible for users to do the same, but without
require root privilege.

But if you're prepared to type the whole mount command, root can mount
"any" device on "any" mountpoint (when sensible). And that's obviously
more flexible when you're trying things out. You don't want to have to
keep going back to fstab to tweak it all the time.

Cheers,
David.

Re: How do I mount the USB stick containing the installer in Rescue Mode?

[David Wright]

On Thu 15 Jul 2021 at 22:15:59 (+0200), Stella Ashburne wrote:
> > Sent: Thursday, July 15, 2021 at 7:08 PM
> > From: "David Wright" 
> >
> > Best I can do. (And I see that your kernel's naming of sda/sdb
> > is more stable than on at least a couple of my machines.)
> >
> What did you mean by "more stable"?

(Greg covered this.)

> > It might be worth posting a request for the stanza I asked for,
> > but as a new topic with a specific Subject line.
> 
> What "stanza" were you referring to? Was it Reco who posted it? And you wrote 
> that it was posted some time in June?

The /full/ stanza is next, but Grub probably makes this look more
complicated by adding more flexibility than any one user could
ever need. (It's GRand Unified …, after all.)

menuentry 'Debian GNU/Linux' --class debian --class gnu-linux --class gnu 
--class os $menuentry_id_option 
'gnulinux-simple-80318fa0-5915-4cc3-bc7c-99af2cfbfda9' {
load_video
insmod gzio
if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
insmod part_gpt
insmod ext2
set root='hd0,gpt2'
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt2 
--hint-efi=hd0,gpt2 --hint-baremetal=ahci0,gpt2  
700b607c-ffa6-4435-a4b6-10894928c764
else
  search --no-floppy --fs-uuid --set=root 
700b607c-ffa6-4435-a4b6-10894928c764
fi
echo'Loading Linux 5.10.0-7-amd64 ...'
linux   /vmlinuz-5.10.0-7-amd64 
root=UUID=80318fa0-5915-4cc3-bc7c-99af2cfbfda9 ro  quiet
echo'Loading initial ramdisk ...'
initrd  /initrd.img-5.10.0-7-amd64
}

That boots the encrypted root installation that I made the other day,
but I can boot the system manually just by typing C at the grub menu,
and then:

Grub> set root='hd0,gpt2'
Grub> linux /vmlinuz-5.10.0-7-amd64 ro quiet 
root=UUID=80318fa0-5915-4cc3-bc7c-99af2cfbfda9
Grub> initrd /initrd.img-5.10.0-7-amd64

or the second line can be shortened to:

Grub> linux /vmlinuz-5.10.0-7-amd64 ro quiet root=LABEL=viva05

or even:

Grub> linux /vmlinuz-5.10.0-7-amd64 ro quiet root=/dev/dm-0

because, once the disk's 5th partition has been unlocked,¹ any of
these properties describes the filesystem inside².

> > I can't see
> > why you shouldn't be able to boot your system with manual Grub
> > commands.
> 
> I thought so too. GRUB developers would and should have built a "Rescue Mode" 
> by just entering the commands.

They have, and you're using it. No, what I meant was that you should
be able to boot it, just giving the correct raw commands. The problem
is knowing what those correct commands are.

¹ Skip this; it's just for the record. Before I made this encrypted
  installation, I posted that you might need to load Grub modules
  like crypto, cryptodisk and luks. However, I now think that these
  modules may exist for unlocking /boot (which would have to be done
  by Grub) rather than / (which can be left for initrd to do).

² root=UUID=80318fa0-5915-4cc3-bc7c-99af2cfbfda9 was copied from grub.cfg,
  root=LABEL=viva05 was a LABEL set in the screen dialogue already posted,
  root=/dev/dm-0 was the device mapper I observed when I first booted the
  system (using Grub's menu).

Cheers,
David.

Re: How do I mount the USB stick containing the installer in Rescue Mode?

[David Wright]

On Thu 15 Jul 2021 at 22:19:23 (+0200), Stella Ashburne wrote:
> > Sent: Thursday, July 15, 2021 at 7:30 PM
> > From: "Thomas Schmitt" 
> >
> > Well, since the case "already mounted" is quite outruled, it might be time
> > to explore "mount point busy".
> >
> >   
> > https://codesearch.debian.net/search?q=package%3Autil-linux+already+mounted+or+mount+point+busy
> > shows that mount(8) emits this message if it gets error code EBUSY.
> > It is not so clear from where this code comes, but mount(2) would be a
> > fine candidate (or placeholder).
> 
> In Rescue Mode, it's impossible for me to install packages such as the one 
> whose link you had provided.
> >
> > So does it work with some other, newly created directory instead of /mnt ?
> >
> 
> No, it doesn't work with other newly created directories in addition to /mnt.

I can tell you why you can't mount it, but you're swimming in waters
too deep for me, so I can't tell you the "proper" way¹ to circumvent
the problem. Others probably can. I'll just suggest a workaround
(untested).

OK, you've just asked for a shell on /dev/perfect-vg/root which is the
root filesystem on your new installation. But up until this point,
the rescue root filesystem was in memory, created when you booted from
the stick. The rescue stick itself (/dev/sdb1) was mounted on /cdrom.
Your problem is: all that is still true, and it's still mounted there.

If you press Alt-F2, or Alt-F3 (or use Alt-arrows to achieve the
same), you can run a shell in the original rescue environment.
(You could actually have started one much earlier after booting.)

Type:
# mount
in *this* shell and you will see   /dev/sdb1 on /cdrom   in the list,
and that is the installation/rescue stick's mountpoint.

If you list /cdrom, you'll see /dists/ and /pool/ in there, which is
how repositories normally present themselves. The symlink debian->.
enables "debian" to be used as the name of the $ARCHIVE_ROOT,
thereby containing debian/dists/.

You should also see   /dev/perfect-vg/root on /target   in the list,
and /target is where your new root filesystem resides (as seen from
the Alt-F1 point of view).

To summarise, Alt-F2 and Alt-F3 shells show you the root filesystem
of the rescue environment (all the time), whereas Alt-F1 shows you
a root filesystem rooted at whatever you chose in the dialogue box.
This Alt-F1 root sits under /target in the Alt-F2 and Alt-F3 shells.

In this situation, my workaround would be (in Alt-F1) to create a
directory called /home/debian/.² You can now (in Alt-F2or3) copy
/dists and /pool into /target/home/debian/ which will make the
repository on the stick available in Alt-F1: the $ARCHIVE_ROOT
will be just /home/debian/.

BTW If you're wondering what Alt-F4 is, it's the system log: the
tail of of the file /var/log/syslog (as seen from Alt-F2or3).

¹ Perhaps some sort of bind mount?

² I'm assuming your own username is not debian, so it won't collide
  with your own home directory.

Cheers,
David.

Re: How do I mount the USB stick containing the installer in Rescue Mode?

[Reco]

On Thu, Jul 15, 2021 at 10:11:06PM +0200, Stella Ashburne wrote:
> Hi
> 
> > Sent: Thursday, July 15, 2021 at 7:07 PM
> > From: "Reco" 
> > To: debian-user@lists.debian.org
> > Subject: Re: How do I mount the USB stick containing the installer in 
> > Rescue Mode?
> 
> > Ok. Can you use this rescue mode to execute an ordinary shell, with full
> > access to all filesystems?
> 
> Before I proceed with your suggestion, while in Resuce Mode, do I
> enter the encryption passphrase or not? If I don't enter the password,
> /dev/perfect-vg/root won't be mounted.

You have to enter the encryption passphrase. It makes little sense to do
all this otherwise.


> Even after I've entered the encryption passphrase, there are two ways
> to execute a shell: one is to execute it in /dev/perfect-vg/root
> environment and the other is to execute it in the installer
> environment. Which environment do you want me to executve a shell in
> please?

First one definitely won't do it, so it's the "installer environment".


> What did you mean by "full access to all filesystems"? When I was
> installing Debian 11, I first encrypted a free space with LUKS and
> then created two logical volumes in it: one whose mount point is /
> (the root file system. Debian installer requires it; otherwise the
> installation can't and won't proceed.) while the other is "used as"
> swap area.

Compare the results of "mount" command from both shells. The difference
should be obvious.


> > If you're executing a shell in a
> > logical volume, you're chrooted into that filesystem.
> 
> I had to enter the encryption passphrase first, followed by mounting
> /dev/perfect-vg/root as a root file system temporarily. Then I chose
> 'Execute a shell in the installer environment' and only then would I
> be able to chroot /target

This. My suggestion is to use bind-mount before chrooting there.


> > What you actually need is to bind mount the directory with packages into
> > the mounted /dev/perfect-vg/root, and just chroot into it. No need to
> > modify /etc/fstab at all.
> >
> Could you be so nice as to give me the command(s) to bind mount the directory 
> with packages? Thank you.

mount --bind  \
/target/

Reco

Sala XMPP de usuários(as) GNU

[Dausacker]

Buenas, camaradas!

Tudo tranquilo?

Lhes convido a participar da nossa sala XMPP de usuários(as) GNU:

usuarios-...@salas.suchat.org


Saudações Livres!

Re: Nuevo

[Juan Lavieri]

Hola Wilfredo.

De nuevo bienvenido.

Varias cosas.

Primero, por favor no hagas top posting.  Responde entre líneas es lo 
apropiado en las listas para seguir el hilo de las respuestas.


Continúo mas adelante.

El 15/7/2021 a las 12:56 p. m., Wilfredo Beyra escribió:
Realmente no se practicamente nada de consola. Se logearme, pero no se 
apagar ni reiniciar. 


Asumo que cuando instalaste, creaste una cuenta se superusuario (root) y 
recuerdas la contraseña.


Algunos comandos no se ejecutan si no los ejecuta el superusuario.

Para ello, en el terminal, con tu usuario normal vas a escribir el 
siguiente comando:


su -

(Ese es el guión normal)  Te va a pedir la contraseña del superusuario; 
 la ingresas (el cursor no se va a mover) le das a la tecla enter y...


En donde escribiste ese comando, pasará de mostrarte el símbolo $ por #

Eso te dice que ahora debes tener cuidado porque tienes permisos para 
destrozar todo.


Ahora si vas a pode ingresar los comandos que te mencionó Javier al 
principo:


cat /etc/X11/default-display-manager

Para este comando no se requería ser superusuario pero como tenía el 
comando sudo por delante tal vez al no estar instalado te daba ese 
mensaje, prueba con el de arriba.


Como te comentó el compañero Javier debe decir algo como

/usr/bin/sddm

Volviendo a copiar lo que él escribió,

apt install sddm

y luego reinicias el sistema.  Ya deberías tener ambiente gráfico;  si no.

Vuelve a ingresar al terminal y vuelves a convertirte en superusuario 
(comando "su" de nuevo, como vimos arriba)


Ahora deberías ejecutar el otro comando que se te sugirió:

(recuerda que debe aparecerte un # que dice que eres superusuario, si no 
no funciona.


apt install task-xfce-desktop  --reinstall

Aqui debes reiniciar.

Sigo mas abajo con eso.

Estoy leyendo un tutorial que se llama paratorpes.
La cuestión es que no se apagar, ni reiniciar el equipo. Lei que el 
comando para apagar es halt, pero cuando lo escribo me sale que esa 
orden no existe. 


Porque no eres superusuario.

OJO:  A partir de ahora cada vez que escriba un comando lo comenzaré con 
$ si puede darlo un usuario normal o # si debes ser superusuario.


Para apagar lo mejor es:

#poweroff

También sirve

#halt

Pero es como si oprimieras el botón de apagado, el primero es mejor.

Para REINICIAR es:

#reboot

sí podrás probar de nuevo.

Cuando el sistema arranca se queda una pantalla oscura
con un cursor parpadeante en la esquina superior izquierda. Cuando 
presiono Ctrl+Alt+F1 se cambia al modo consola, hasta ahí ok, sin 
embargo Alt+F7 que debería cambiar a modo gráfico me devuelve a la 
pantalla oscura con el cursor.
Traté con la orden que me enviaste pero entonces me pide password para 
la sesión, pues la sesión que inicié es de usuario normal, no root. 
Estos son mis primeros pasos en el mundo del software libre, por favor 
tenganme paciencia. 


No te preocupes que todos empezamos desde cero alguna vez

Inténtalo y nos avisas

Saludos.

Gracias por responder tan rápido.

Wbeyras

El jue., 15 de jul. de 2021 7:38 AM, Debian 
mailto:javier.debian.bb...@gmail.com>> 
escribió:


El 15/7/21 a las 08:25, Wilfredo Beyra escribió:
 > Hola:
 > Soy nuevo en Debian. Acabo de instalar un CD co xfce pero no sale el
 > escritorio. La instalación se ejecutó sin problemas pero solo
puedo usar
 > la consola. Por favor alguien que me explique como cargar el
entorno de
 > escritorio. Gracias.
 > wbey...@gmail.com 
>


Buen día y bienvenido.

Asumo que algo con la consola te defiendes.

Primero, veremos si está instalado el gestor de escritorio:
Prueba esta instrucción:
$ sudo cat /etc/X11/default-display-manager

Debe resultar en algo como
/usr/bin/sddm

Si no es así, ejecuta
$ apt install sddm
y luego reinicias el sistema.

Si sigues sin sesión gráfica, prueba lo siguiente:

$ sudo apt install task-xfce-desktop  --reinstall

Esto a verificar la instalación del entorno de escritorio xfce completo.
Luego, reinicia el sistema.

El Linux tienes que tener dos cosas para usar el escritorio: el
gestor y
el escritorio en sí; son independientes e "intercambables".

Mantenenos al tanto.

JAP



--
Errar es de humanos, pero es mas humano culpar a los demás

Re: How do I mount the USB stick containing the installer in Rescue Mode?

[David]

On Fri, 16 Jul 2021 at 05:00, Stella Ashburne  wrote:

I'm getting a sense of possible XY problem here.
https://en.wikipedia.org/wiki/XY_problem

> > Chicken and egg: I think the OP is trying to set up some sort of
> > repository to install packages from. (I can't be sure.

> Your guess is right. I wish to install linux-image-5.10.0-7-amd64.deb
> onto chroot /target after entering Rescue Mode.

I suspect that 'I want to use rescue mode to install a kernel' is
question "Y", whereas ...

> > I would
> > have preferred it if they'd continued to try and boot their
> > actual installed system,

> At this moment I don't have a GRUB menu.

... previously we have been told that a grub boot failure is the
*actual* problem "X", unless something has changed from what
we've been told so far.

In my opinion, this is what needs to be fixed before making the situation
more confusing by trying to add another kernel to a broken installation.

My guess is that the reinstallation failed because it was
done in such a way that /boot was not the mount point
of the unencrypted boot partition at the time that the
installer configured grub and generated the initrd.

After chroot succeeds, the first goal must be to fix what originally
caused the grub menu breakage during the reinstall attempt.
That requires to check that /boot is the mount point of the
unencrypted boot partition

After that, run 'grub-update' and 'grub-install' as I have
already advised in previous messages.

'grub-install --boot-directory=/mount/point/of/boot/partition
/dev/hdd/specified/here'

Note that these commands must be run in a *linux* *shell*
environment. And the grub> prompt is *not* one of those.
grub is not an entire linux system, it is just a boot loader.

I would also make a backup of all the initrd files and then run
'update-initramfs -u -k all' and fix any errors it gives.

And then reboot and see if it works.

The time to install a new kernel will be after that.

Also as previously advised, if asking for help in future please
show the output of 'lsblk -f' because it shows all devices, whereas
'mount' and 'df' only give information about filesystems that
are mounted.