Re: Erro ao recuperar grub de um Debian com LVM Criptografado.

[Linux - Junior Polegato]

Olá!

Seguindo os passos que passei, antes do grub-install e update-grub, tente
iniciar os serviços de lvm que estão em /etc/rc5.d, deve ter um .service
que deve funcionar.

Mais um ponto, aconselho utilizar o CD de instalação do Debian, iniciando
em modo de recuperação ou instalação até o ponto em que são reconhecidas
todas as partições do HD, então no Shell que abrir (Ctrl+Alt+F2) siga os
passos que passei, lembrando ser importante que o kernel do instalador seja
da mesma arquitetura do instalado no HD, i386 ou amd64, se for versão
próxima ou igual, melhor ainda.

[]'s

Junior Polegato

Em 3 de set de 2017 11:36 PM, "Luiz Carlos"  escreveu:

> # systemctl start lvm2-lvmetad.socket
> Running in chroot, ignoring request.
>
>
> Em 4 de setembro de 2017 02:32,  escreveu:
>
>> Experimenta rodar os mesmos comandos, só que após dar o chroot, inicie os
>> serviços de lvmetad que estão faltando de acordo com a sua mensagem de
>> erro:
>>
>>
>> systemctl start lvm2-lvmetad.service
>> systemctl start lvm2-lvmetad.socket
>>
>> E só daí o grub-install ou updategrub
>>
>> Faz isso com e sem o GRUB_ENABLE_CRYPTODISK habilitado, só por via das
>> dúvidas, o log disse que precisava disso habilitado, e que o lvmetad não
>> foi contactado. Deve resolver.
>>
>> Abracos
>>
>> Henry
>>
>>
>>
>> Enviado do meu smartphone BlackBerry 10.
>> *De: *Luiz Carlos
>> *Enviada: *domingo, 3 de setembro de 2017 21:38
>> *Para: *DUP
>> *Assunto: *Re: Erro ao recuperar grub de um Debian com LVM Criptografado.
>>
>> Henrique e Junior, executei os seguintes comandos:
>> mint mint # modprobe dm-crypt
>> mint mint # cryptsetup luksOpen /dev/sda5 linux
>> Enter passphrase for /dev/sda5:
>> mint mint # vgscan
>>   Reading all physical volumes.  This may take a while...
>>   Found volume group "lvmc" using metadata type lvm2
>> mint mint # lvscan
>>   ACTIVE'/dev/lvmc/swap' [1.86 GiB] inherit
>>   ACTIVE'/dev/lvmc/root' [37.25 GiB] inherit
>>   ACTIVE'/dev/lvmc/home' [327.60 GiB] inherit
>> mint mint # mkdir /media/linux
>> mint mint # mount /dev/lvmc/root /media/linux/
>> mint mint # mount -o bind /dev/ /media/linux/dev
>> mint mint # mount -o bind /proc/ /media/linux/proc
>> mint mint # chroot /media/linux /bin/bash
>> root@mint:/# grub-install /dev/sda
>> Installing for i386-pc platform.
>>   Failed to find sysfs mount point
>>   WARNING: Failed to connect to lvmetad. Falling back to device scanning.
>>   dev/block/252:2/holders/: opendir failed: Not a directory
>>   dev/block/252:1/holders/: opendir failed: Not a directory
>>   dev/block/252:3/holders/: opendir failed: Not a directory
>>   dev/block/252:0/holders/: opendir failed: Not a directory
>>   dev/block/8:33/holders/: opendir failed: Not a directory
>>   dev/block/8:32/holders/: opendir failed: Not a directory
>>   dev/block/8:16/holders/: opendir failed: Not a directory
>>   dev/block/8:3/holders/: opendir failed: Not a directory
>>   dev/block/8:5/holders/: opendir failed: Not a directory
>>   dev/block/11:0/holders/: opendir failed: Not a directory
>>   dev/block/8:1/holders/: opendir failed: Not a directory
>>   dev/block/8:2/holders/: opendir failed: Not a directory
>>   dev/block/8:4/holders/: opendir failed: Not a directory
>>   dev/block/8:0/holders/: opendir failed: Not a directory
>>   dev/block/1:7/holders/: opendir failed: Not a directory
>>   dev/block/1:6/holders/: opendir failed: Not a directory
>>   dev/block/1:9/holders/: opendir failed: Not a directory
>>   dev/block/1:8/holders/: opendir failed: Not a directory
>>   dev/block/1:5/holders/: opendir failed: Not a directory
>>   dev/block/1:4/holders/: opendir failed: Not a directory
>>   dev/block/1:10/holders/: opendir failed: Not a directory
>>   dev/block/1:11/holders/: opendir failed: Not a directory
>>   dev/block/1:3/holders/: opendir failed: Not a directory
>>   dev/block/1:15/holders/: opendir failed: Not a directory
>>   dev/block/1:2/holders/: opendir failed: Not a directory
>>   dev/block/1:13/holders/: opendir failed: Not a directory
>>   dev/block/1:14/holders/: opendir failed: Not a directory
>>   dev/block/1:12/holders/: opendir failed: Not a directory
>>   dev/block/1:0/holders/: opendir failed: Not a directory
>>   dev/block/1:1/holders/: opendir failed: Not a directory
>>   dev/block/7:0/holders/: opendir failed: Not a directory
>>   dev/block/7:7/holders/: opendir failed: Not a directory
>>   dev/block/7:1/holders/: opendir failed: Not a directory
>>   dev/block/7:6/holders/: opendir failed: Not a directory
>>   dev/block/7:5/holders/: opendir failed: Not a directory
>>   dev/block/7:3/holders/: opendir failed: Not a directory
>>   dev/block/7:4/holders/: opendir failed: Not a directory
>>   dev/block/7:2/holders/: opendir failed: Not a directory
>>   dev/block/252:2/holders/: opendir failed: Not a directory
>>   dev/block/252:1/holders/: opendir failed: Not a directory
>>   dev/block/252:3/holders/: opendir failed: Not 

Re: network trouble on stretch

[Ben Caradoc-Davies]

On 04/09/17 10:27, Fungi4All wrote:

Before you get a long lecture on the merits of long unique names try this:
Edit your /etc/default/grub change GRUB_CMDLINE_LINUX=”” to :
GRUB_CMDLINE_LINUX="net.ifnames=0" If the biosdevname is installed you need to 
add :
GRUB_CMDLINE_LINUX="net.ifnames=0 biosdevname=0"
$ sudo update-grub
$ sudo reboot
Now check your /dev/interfaces, they should be eth0 and wlan0 and they will stay
this way.


Thank you. I have wanted this for so long.

Kind regards,

--
Ben Caradoc-Davies 
Director
Transient Software Limited 
New Zealand

Re: (solved) how to roll back to jessie

[Felix Miata]

Long Wind composed on 2017-09-04 04:16 (UTC):

> I finds today that it's really not jessieit's wheezy
> it seems that wheezy is not too old for me 

Wheezy support is scheduled to terminate less than 9 months from today. Maybe
now is a good time to consider at least Jessie if not Stretch, since you're
installing fresh.
-- 
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/

Re: UI inconsistency: unlocking LUKS-encrypted drives

[Mario Castelán Castro]

On 03/09/17 21:15, Sam Kuper wrote:
> On 03/09/2017, Sam Kuper  wrote:
>> 1. is this inconsistency intended, and if so, why?
> 
> The cause of the inconsistency seems to have been that the
> "HintSystem" property[1] was set differently between the various
> devices concerned.

Thanks for reporting what you found.

-- 
Do not eat animals; respect them as you respect people.
https://duckduckgo.com/?q=how+to+(become+OR+eat)+vegan



signature.asc
Description: OpenPGP digital signature

Re: Laptop recommendation

[Joe Pfeiffer]

I'm very happy with a Dell Inspiron 13 7000 series I picked up at Best
Buy a month or so ago.  It appears to meet your requirements, and is
also a convertible (I can fold the screen back over to put it in "tent"
mode), has a touch-screen, supports an active pen, and has a backlit
keyboard.  The key feel is terrible but the keyboard is full-size; it's
been a long time since I've seen a laptop with a keyboard that felt
good.

Re: network trouble on stretch

[Zenaan Harkness]

On Sun, Sep 03, 2017 at 06:27:12PM -0400, Fungi4All wrote:
> > From: ghe2...@gmail.com
> > The WiFi works, but the Ethernet doesn"t, and I can"t figure out why.
> > ip addr:
...

> Before you get a long lecture on the merits of long unique names try this:
> 
> Edit your /etc/default/grub change GRUB_CMDLINE_LINUX=”” to :
> GRUB_CMDLINE_LINUX="net.ifnames=0" If the biosdevname is installed you need 
> to add :
> GRUB_CMDLINE_LINUX="net.ifnames=0 biosdevname=0"
> $ sudo update-grub
> $ sudo reboot
> 
> Now check your /dev/interfaces, they should be eth0 and wlan0 and they will 
> stay
> this way.

VERY nice hint - jotted away for future :)

That should hopefully solve the OP's problem. If not, the next step I
would personally take is to:

1) determine which ifnames are which type

2) drop into a terminal and use ip (or ifconfig still?) to manually
   configure each eth dev, one by one, with a static address, and see
   if ping works from another host;
   if not work, then "ifconfig down" or "ip link set $DEVNAME down"
   and try the next one...

This way also means that specific commands are either failing or
succeeding - I know it's lower level, but can make debugging ones
problem a little easier from my oh-so-incredibly-humble experiences
:)

Good luck,

Re: Erro ao recuperar grub de um Debian com LVM Criptografado.

[Luiz Carlos]

Acho que vou suportar mais 2 dias, se não conseguir, eu vou ter que baixar
o Linux e instalar tudo do zero.
Que merda, o grub só reconheceu o Windows e o Linux não, será que meu
sistema está corrompido? Tem uma solução pra isso?

# grub-install /dev/sda
Installing for i386-pc platform.
Installation finished. No error reported.
root@mint:/# update-grub
Generating grub configuration file ...
Found background image: .background_cache.png
  WARNING: Failed to connect to lvmetad. Falling back to device scanning.
  WARNING: Failed to connect to lvmetad. Falling back to device scanning.
  WARNING: Failed to connect to lvmetad. Falling back to device scanning.
  WARNING: Failed to connect to lvmetad. Falling back to device scanning.
  WARNING: Failed to connect to lvmetad. Falling back to device scanning.
  WARNING: Failed to connect to lvmetad. Falling back to device scanning.
  WARNING: Failed to connect to lvmetad. Falling back to device scanning.
Found Windows 10 on /dev/sda1
done


Em 4 de setembro de 2017 02:56, Luiz Carlos  escreveu:

> Que estranho, não estou conseguindo fazer que o grub reconheça o Linux,
> isso é um caso bem raro, não sei se tenho solução.
>
> Em 4 de setembro de 2017 02:35, Luiz Carlos  escreveu:
>
>> # systemctl start lvm2-lvmetad.socket
>> Running in chroot, ignoring request.
>>
>>
>> Em 4 de setembro de 2017 02:32,  escreveu:
>>
>>> Experimenta rodar os mesmos comandos, só que após dar o chroot, inicie
>>> os serviços de lvmetad que estão faltando de acordo com a sua mensagem de
>>> erro:
>>>
>>>
>>> systemctl start lvm2-lvmetad.service
>>> systemctl start lvm2-lvmetad.socket
>>>
>>> E só daí o grub-install ou updategrub
>>>
>>> Faz isso com e sem o GRUB_ENABLE_CRYPTODISK habilitado, só por via das
>>> dúvidas, o log disse que precisava disso habilitado, e que o lvmetad não
>>> foi contactado. Deve resolver.
>>>
>>> Abracos
>>>
>>> Henry
>>>
>>>
>>>
>>> Enviado do meu smartphone BlackBerry 10.
>>> *De: *Luiz Carlos
>>> *Enviada: *domingo, 3 de setembro de 2017 21:38
>>> *Para: *DUP
>>> *Assunto: *Re: Erro ao recuperar grub de um Debian com LVM
>>> Criptografado.
>>>
>>> Henrique e Junior, executei os seguintes comandos:
>>> mint mint # modprobe dm-crypt
>>> mint mint # cryptsetup luksOpen /dev/sda5 linux
>>> Enter passphrase for /dev/sda5:
>>> mint mint # vgscan
>>>   Reading all physical volumes.  This may take a while...
>>>   Found volume group "lvmc" using metadata type lvm2
>>> mint mint # lvscan
>>>   ACTIVE'/dev/lvmc/swap' [1.86 GiB] inherit
>>>   ACTIVE'/dev/lvmc/root' [37.25 GiB] inherit
>>>   ACTIVE'/dev/lvmc/home' [327.60 GiB] inherit
>>> mint mint # mkdir /media/linux
>>> mint mint # mount /dev/lvmc/root /media/linux/
>>> mint mint # mount -o bind /dev/ /media/linux/dev
>>> mint mint # mount -o bind /proc/ /media/linux/proc
>>> mint mint # chroot /media/linux /bin/bash
>>> root@mint:/# grub-install /dev/sda
>>> Installing for i386-pc platform.
>>>   Failed to find sysfs mount point
>>>   WARNING: Failed to connect to lvmetad. Falling back to device scanning.
>>>   dev/block/252:2/holders/: opendir failed: Not a directory
>>>   dev/block/252:1/holders/: opendir failed: Not a directory
>>>   dev/block/252:3/holders/: opendir failed: Not a directory
>>>   dev/block/252:0/holders/: opendir failed: Not a directory
>>>   dev/block/8:33/holders/: opendir failed: Not a directory
>>>   dev/block/8:32/holders/: opendir failed: Not a directory
>>>   dev/block/8:16/holders/: opendir failed: Not a directory
>>>   dev/block/8:3/holders/: opendir failed: Not a directory
>>>   dev/block/8:5/holders/: opendir failed: Not a directory
>>>   dev/block/11:0/holders/: opendir failed: Not a directory
>>>   dev/block/8:1/holders/: opendir failed: Not a directory
>>>   dev/block/8:2/holders/: opendir failed: Not a directory
>>>   dev/block/8:4/holders/: opendir failed: Not a directory
>>>   dev/block/8:0/holders/: opendir failed: Not a directory
>>>   dev/block/1:7/holders/: opendir failed: Not a directory
>>>   dev/block/1:6/holders/: opendir failed: Not a directory
>>>   dev/block/1:9/holders/: opendir failed: Not a directory
>>>   dev/block/1:8/holders/: opendir failed: Not a directory
>>>   dev/block/1:5/holders/: opendir failed: Not a directory
>>>   dev/block/1:4/holders/: opendir failed: Not a directory
>>>   dev/block/1:10/holders/: opendir failed: Not a directory
>>>   dev/block/1:11/holders/: opendir failed: Not a directory
>>>   dev/block/1:3/holders/: opendir failed: Not a directory
>>>   dev/block/1:15/holders/: opendir failed: Not a directory
>>>   dev/block/1:2/holders/: opendir failed: Not a directory
>>>   dev/block/1:13/holders/: opendir failed: Not a directory
>>>   dev/block/1:14/holders/: opendir failed: Not a directory
>>>   dev/block/1:12/holders/: opendir failed: Not a directory
>>>   dev/block/1:0/holders/: opendir failed: Not a directory
>>>   dev/block/1:1/holders/: 

Re: network trouble on stretch

[Cindy-Sue Causey]

On 9/3/17, Glenn English  wrote:
> Working on a Dell 5414 laptop, Stretch.
>
> The WiFi works, but the Ethernet doesn't, and I can't figure out why.
>
> ip addr:
>
> 1: lo:  mtu 65536 qdisc noqueue state UNKNOWN
> group default qlen 1
> link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
> inet 127.0.0.1/8 scope host lo
>valid_lft forever preferred_lft forever
> inet6 ::1/128 scope host
>valid_lft forever preferred_lft forever
> 2: enp0s31f6:  mtu 1500 qdisc noop state DOWN
> group default qlen 1000
> link/ether 10:05:01:40:f4:43 brd ff:ff:ff:ff:ff:ff
> 3: wwp0s20f0u2i12:  mtu 1500 qdisc noop
> state DOWN group default qlen 1000
> link/ether 4e:8a:3a:22:b3:df brd ff:ff:ff:ff:ff:ff
> 4: wlp1s0:  mtu 1500 qdisc noop state DOWN group
> default qlen 1000
> link/ether f4:8c:50:17:bc:0e brd ff:ff:ff:ff:ff:ff
> 5: enx10050149649d:  mtu 1500 qdisc noop state
> DOWN group default qlen 1000
> link/ether 10:05:01:49:64:9d brd ff:ff:ff:ff:ff:ff
>
> /etc/network/interfaces:
>
> # This file describes the network interfaces available on your system
> # and how to activate them. For more information, see interfaces(5).
>
> source /etc/network/interfaces.d/*
>
> # The loopback network interface
> auto lo
> iface lo inet loopback
>
> auto wwp0s20f0u2i12
> iface wwp0s20f0u2i12 inet static
> address 216.17.134.202/29
> gateway 216.17.134.201
>
> First I tried with wicd, a network manager (the static def wasn't in
> interfaces)
>
> It said the wired interface was up, and assigned the requested IP. It
> wasn't checking after assignment to see if it worked. I turned that
> on, and it never came back.
>
> I removed the network monitor and added the static paragraph to the
> interface file. ifup and ifdown worked, and ip addr said
> wwp0s20f0u2i12 was up.
>
> There are two Ethernet ports on this thing, and I tried both with no
> success. I swapped out the Ethernet cable with the same result.
>
> I replaced Stretch with Buster. It works. dhcp (Comcast) or static (my
> T1). Using the interfaces file.
>
> BTW. ifconfig fans, wait till you get to Buster -- no ifup or down.
> Buster seems to boot using a commented out dhcp paragraph, though.
> Running by hand, '/etc/init.d/network reload' loads the correct
> config.
>
> The 'man interfaces' on Stretch talks a lot about the ethn interfaces.
> It does on Buster, too.
>
> This is less than optimal.
>
> What's going on here? This is Linux, not Winders; Debian, not Ubuntu;
> stable, not Sid. This is what we're supposed to put on Internet
> servers? They had time to make something as simple as this work while
> it was testing. And to correct the man pages, too.
>
> If they didn't have time, the release should have been postponed until
> it was ready for prime time, IMHO.
>
> I looked on the 'Net, asking why the interface names were changed. I
> found a good reason: sometimes the ethn names aren't reliably
> consistent. Fine, I say, you've figured how to make them consistent.
> That's no reason to change the names from a meaningful 4 or 5 chars to
> 11, chosen by /dev/urandom.
>
> Somebody's selling the Debian management a pile of bull excrement.


You mentioned wicd, but I'm not quite able to tell where you made your
change. My apologies if you have already done what I've written below.
I'm going to post anyway on that off chance that it might help someone
else.

I changed mine by clicking that drop down arrow on the right of *my*
wicd interface. This is one of those cases where the window default is
smaller sized so something important is buried behind a non-invasive,
i.e. cognitively almost invisible, drop down arrow.

There's a Preferences option buried there when that window is smaller.
Mine has Preferences, About, and Quit hiding under that arrow.

Under Preferences, there's a General Settings tab. At the top of that
is Network Interfaces for Wireless Interface and Wired Interface.
That's where I changed mine a while back, and it's been working.

DISCLAIMER is that my setup is extremely basic. When all those fancier
settings have to be made for multiple computer systems networking
together, my successful, quick fix setting there may have no effect at
all for that something fancier.

Cindy :)
-- 
Cindy-Sue Causey
Talking Rock, Pickens County, Georgia, USA

* runs with duct tape *

Re: Erro ao recuperar grub de um Debian com LVM Criptografado.

[Luiz Carlos]

Que estranho, não estou conseguindo fazer que o grub reconheça o Linux,
isso é um caso bem raro, não sei se tenho solução.

Em 4 de setembro de 2017 02:35, Luiz Carlos  escreveu:

> # systemctl start lvm2-lvmetad.socket
> Running in chroot, ignoring request.
>
>
> Em 4 de setembro de 2017 02:32,  escreveu:
>
>> Experimenta rodar os mesmos comandos, só que após dar o chroot, inicie os
>> serviços de lvmetad que estão faltando de acordo com a sua mensagem de
>> erro:
>>
>>
>> systemctl start lvm2-lvmetad.service
>> systemctl start lvm2-lvmetad.socket
>>
>> E só daí o grub-install ou updategrub
>>
>> Faz isso com e sem o GRUB_ENABLE_CRYPTODISK habilitado, só por via das
>> dúvidas, o log disse que precisava disso habilitado, e que o lvmetad não
>> foi contactado. Deve resolver.
>>
>> Abracos
>>
>> Henry
>>
>>
>>
>> Enviado do meu smartphone BlackBerry 10.
>> *De: *Luiz Carlos
>> *Enviada: *domingo, 3 de setembro de 2017 21:38
>> *Para: *DUP
>> *Assunto: *Re: Erro ao recuperar grub de um Debian com LVM Criptografado.
>>
>> Henrique e Junior, executei os seguintes comandos:
>> mint mint # modprobe dm-crypt
>> mint mint # cryptsetup luksOpen /dev/sda5 linux
>> Enter passphrase for /dev/sda5:
>> mint mint # vgscan
>>   Reading all physical volumes.  This may take a while...
>>   Found volume group "lvmc" using metadata type lvm2
>> mint mint # lvscan
>>   ACTIVE'/dev/lvmc/swap' [1.86 GiB] inherit
>>   ACTIVE'/dev/lvmc/root' [37.25 GiB] inherit
>>   ACTIVE'/dev/lvmc/home' [327.60 GiB] inherit
>> mint mint # mkdir /media/linux
>> mint mint # mount /dev/lvmc/root /media/linux/
>> mint mint # mount -o bind /dev/ /media/linux/dev
>> mint mint # mount -o bind /proc/ /media/linux/proc
>> mint mint # chroot /media/linux /bin/bash
>> root@mint:/# grub-install /dev/sda
>> Installing for i386-pc platform.
>>   Failed to find sysfs mount point
>>   WARNING: Failed to connect to lvmetad. Falling back to device scanning.
>>   dev/block/252:2/holders/: opendir failed: Not a directory
>>   dev/block/252:1/holders/: opendir failed: Not a directory
>>   dev/block/252:3/holders/: opendir failed: Not a directory
>>   dev/block/252:0/holders/: opendir failed: Not a directory
>>   dev/block/8:33/holders/: opendir failed: Not a directory
>>   dev/block/8:32/holders/: opendir failed: Not a directory
>>   dev/block/8:16/holders/: opendir failed: Not a directory
>>   dev/block/8:3/holders/: opendir failed: Not a directory
>>   dev/block/8:5/holders/: opendir failed: Not a directory
>>   dev/block/11:0/holders/: opendir failed: Not a directory
>>   dev/block/8:1/holders/: opendir failed: Not a directory
>>   dev/block/8:2/holders/: opendir failed: Not a directory
>>   dev/block/8:4/holders/: opendir failed: Not a directory
>>   dev/block/8:0/holders/: opendir failed: Not a directory
>>   dev/block/1:7/holders/: opendir failed: Not a directory
>>   dev/block/1:6/holders/: opendir failed: Not a directory
>>   dev/block/1:9/holders/: opendir failed: Not a directory
>>   dev/block/1:8/holders/: opendir failed: Not a directory
>>   dev/block/1:5/holders/: opendir failed: Not a directory
>>   dev/block/1:4/holders/: opendir failed: Not a directory
>>   dev/block/1:10/holders/: opendir failed: Not a directory
>>   dev/block/1:11/holders/: opendir failed: Not a directory
>>   dev/block/1:3/holders/: opendir failed: Not a directory
>>   dev/block/1:15/holders/: opendir failed: Not a directory
>>   dev/block/1:2/holders/: opendir failed: Not a directory
>>   dev/block/1:13/holders/: opendir failed: Not a directory
>>   dev/block/1:14/holders/: opendir failed: Not a directory
>>   dev/block/1:12/holders/: opendir failed: Not a directory
>>   dev/block/1:0/holders/: opendir failed: Not a directory
>>   dev/block/1:1/holders/: opendir failed: Not a directory
>>   dev/block/7:0/holders/: opendir failed: Not a directory
>>   dev/block/7:7/holders/: opendir failed: Not a directory
>>   dev/block/7:1/holders/: opendir failed: Not a directory
>>   dev/block/7:6/holders/: opendir failed: Not a directory
>>   dev/block/7:5/holders/: opendir failed: Not a directory
>>   dev/block/7:3/holders/: opendir failed: Not a directory
>>   dev/block/7:4/holders/: opendir failed: Not a directory
>>   dev/block/7:2/holders/: opendir failed: Not a directory
>>   dev/block/252:2/holders/: opendir failed: Not a directory
>>   dev/block/252:1/holders/: opendir failed: Not a directory
>>   dev/block/252:3/holders/: opendir failed: Not a directory
>>   dev/block/252:0/holders/: opendir failed: Not a directory
>>   dev/block/8:33/holders/: opendir failed: Not a directory
>>   dev/block/8:32/holders/: opendir failed: Not a directory
>>   dev/block/8:16/holders/: opendir failed: Not a directory
>>   dev/block/8:3/holders/: opendir failed: Not a directory
>>   dev/block/8:5/holders/: opendir failed: Not a directory
>>   dev/block/11:0/holders/: opendir failed: Not a directory
>>   

Re: Erro ao recuperar grub de um Debian com LVM Criptografado.

[Luiz Carlos]

# systemctl start lvm2-lvmetad.socket
Running in chroot, ignoring request.


Em 4 de setembro de 2017 02:32,  escreveu:

> Experimenta rodar os mesmos comandos, só que após dar o chroot, inicie os
> serviços de lvmetad que estão faltando de acordo com a sua mensagem de
> erro:
>
>
> systemctl start lvm2-lvmetad.service
> systemctl start lvm2-lvmetad.socket
>
> E só daí o grub-install ou updategrub
>
> Faz isso com e sem o GRUB_ENABLE_CRYPTODISK habilitado, só por via das
> dúvidas, o log disse que precisava disso habilitado, e que o lvmetad não
> foi contactado. Deve resolver.
>
> Abracos
>
> Henry
>
>
>
> Enviado do meu smartphone BlackBerry 10.
> *De: *Luiz Carlos
> *Enviada: *domingo, 3 de setembro de 2017 21:38
> *Para: *DUP
> *Assunto: *Re: Erro ao recuperar grub de um Debian com LVM Criptografado.
>
> Henrique e Junior, executei os seguintes comandos:
> mint mint # modprobe dm-crypt
> mint mint # cryptsetup luksOpen /dev/sda5 linux
> Enter passphrase for /dev/sda5:
> mint mint # vgscan
>   Reading all physical volumes.  This may take a while...
>   Found volume group "lvmc" using metadata type lvm2
> mint mint # lvscan
>   ACTIVE'/dev/lvmc/swap' [1.86 GiB] inherit
>   ACTIVE'/dev/lvmc/root' [37.25 GiB] inherit
>   ACTIVE'/dev/lvmc/home' [327.60 GiB] inherit
> mint mint # mkdir /media/linux
> mint mint # mount /dev/lvmc/root /media/linux/
> mint mint # mount -o bind /dev/ /media/linux/dev
> mint mint # mount -o bind /proc/ /media/linux/proc
> mint mint # chroot /media/linux /bin/bash
> root@mint:/# grub-install /dev/sda
> Installing for i386-pc platform.
>   Failed to find sysfs mount point
>   WARNING: Failed to connect to lvmetad. Falling back to device scanning.
>   dev/block/252:2/holders/: opendir failed: Not a directory
>   dev/block/252:1/holders/: opendir failed: Not a directory
>   dev/block/252:3/holders/: opendir failed: Not a directory
>   dev/block/252:0/holders/: opendir failed: Not a directory
>   dev/block/8:33/holders/: opendir failed: Not a directory
>   dev/block/8:32/holders/: opendir failed: Not a directory
>   dev/block/8:16/holders/: opendir failed: Not a directory
>   dev/block/8:3/holders/: opendir failed: Not a directory
>   dev/block/8:5/holders/: opendir failed: Not a directory
>   dev/block/11:0/holders/: opendir failed: Not a directory
>   dev/block/8:1/holders/: opendir failed: Not a directory
>   dev/block/8:2/holders/: opendir failed: Not a directory
>   dev/block/8:4/holders/: opendir failed: Not a directory
>   dev/block/8:0/holders/: opendir failed: Not a directory
>   dev/block/1:7/holders/: opendir failed: Not a directory
>   dev/block/1:6/holders/: opendir failed: Not a directory
>   dev/block/1:9/holders/: opendir failed: Not a directory
>   dev/block/1:8/holders/: opendir failed: Not a directory
>   dev/block/1:5/holders/: opendir failed: Not a directory
>   dev/block/1:4/holders/: opendir failed: Not a directory
>   dev/block/1:10/holders/: opendir failed: Not a directory
>   dev/block/1:11/holders/: opendir failed: Not a directory
>   dev/block/1:3/holders/: opendir failed: Not a directory
>   dev/block/1:15/holders/: opendir failed: Not a directory
>   dev/block/1:2/holders/: opendir failed: Not a directory
>   dev/block/1:13/holders/: opendir failed: Not a directory
>   dev/block/1:14/holders/: opendir failed: Not a directory
>   dev/block/1:12/holders/: opendir failed: Not a directory
>   dev/block/1:0/holders/: opendir failed: Not a directory
>   dev/block/1:1/holders/: opendir failed: Not a directory
>   dev/block/7:0/holders/: opendir failed: Not a directory
>   dev/block/7:7/holders/: opendir failed: Not a directory
>   dev/block/7:1/holders/: opendir failed: Not a directory
>   dev/block/7:6/holders/: opendir failed: Not a directory
>   dev/block/7:5/holders/: opendir failed: Not a directory
>   dev/block/7:3/holders/: opendir failed: Not a directory
>   dev/block/7:4/holders/: opendir failed: Not a directory
>   dev/block/7:2/holders/: opendir failed: Not a directory
>   dev/block/252:2/holders/: opendir failed: Not a directory
>   dev/block/252:1/holders/: opendir failed: Not a directory
>   dev/block/252:3/holders/: opendir failed: Not a directory
>   dev/block/252:0/holders/: opendir failed: Not a directory
>   dev/block/8:33/holders/: opendir failed: Not a directory
>   dev/block/8:32/holders/: opendir failed: Not a directory
>   dev/block/8:16/holders/: opendir failed: Not a directory
>   dev/block/8:3/holders/: opendir failed: Not a directory
>   dev/block/8:5/holders/: opendir failed: Not a directory
>   dev/block/11:0/holders/: opendir failed: Not a directory
>   dev/block/8:1/holders/: opendir failed: Not a directory
>   dev/block/8:2/holders/: opendir failed: Not a directory
>   dev/block/8:4/holders/: opendir failed: Not a directory
>   dev/block/8:0/holders/: opendir failed: Not a directory
>   dev/block/1:7/holders/: opendir failed: Not a directory
>   dev/block/1:6/holders/: 

Res: Erro ao recuperar grub de um Debian com LVM Criptografado.

[jmhenrique]

  Experimenta rodar os mesmos comandos, só que após dar o chroot, inicie os serviços de lvmetad que estão faltando de acordo com a sua mensagem de erro: systemctl start lvm2-lvmetad.servicesystemctl start lvm2-lvmetad.socketE só daí o grub-install ou updategrub Faz isso com e sem o GRUB_ENABLE_CRYPTODISK habilitado, só por via das dúvidas, o log disse que precisava disso habilitado, e que o lvmetad não foi contactado. Deve resolver. AbracosHenry Enviado do meu smartphone BlackBerry 10.De: Luiz CarlosEnviada: domingo, 3 de setembro de 2017 21:38Para: DUPAssunto: Re: Erro ao recuperar grub de um Debian com LVM Criptografado.Henrique e Junior, executei os seguintes comandos:mint mint # modprobe dm-cryptmint mint # cryptsetup luksOpen /dev/sda5 linuxEnter passphrase for /dev/sda5: mint mint # vgscan  Reading all physical volumes.  This may take a while...  Found volume group "lvmc" using metadata type lvm2mint mint # lvscan  ACTIVE            '/dev/lvmc/swap' [1.86 GiB] inherit  ACTIVE            '/dev/lvmc/root' [37.25 GiB] inherit  ACTIVE            '/dev/lvmc/home' [327.60 GiB] inheritmint mint # mkdir /media/linuxmint mint # mount /dev/lvmc/root /media/linux/mint mint # mount -o bind /dev/ /media/linux/devmint mint # mount -o bind /proc/ /media/linux/procmint mint # chroot /media/linux /bin/bashroot@mint:/# grub-install /dev/sdaInstalling for i386-pc platform.  Failed to find sysfs mount point  WARNING: Failed to connect to lvmetad. Falling back to device scanning.  dev/block/252:2/holders/: opendir failed: Not a directory  dev/block/252:1/holders/: opendir failed: Not a directory  dev/block/252:3/holders/: opendir failed: Not a directory  dev/block/252:0/holders/: opendir failed: Not a directory  dev/block/8:33/holders/: opendir failed: Not a directory  dev/block/8:32/holders/: opendir failed: Not a directory  dev/block/8:16/holders/: opendir failed: Not a directory  dev/block/8:3/holders/: opendir failed: Not a directory  dev/block/8:5/holders/: opendir failed: Not a directory  dev/block/11:0/holders/: opendir failed: Not a directory  dev/block/8:1/holders/: opendir failed: Not a directory  dev/block/8:2/holders/: opendir failed: Not a directory  dev/block/8:4/holders/: opendir failed: Not a directory  dev/block/8:0/holders/: opendir failed: Not a directory  dev/block/1:7/holders/: opendir failed: Not a directory  dev/block/1:6/holders/: opendir failed: Not a directory  dev/block/1:9/holders/: opendir failed: Not a directory  dev/block/1:8/holders/: opendir failed: Not a directory  dev/block/1:5/holders/: opendir failed: Not a directory  dev/block/1:4/holders/: opendir failed: Not a directory  dev/block/1:10/holders/: opendir failed: Not a directory  dev/block/1:11/holders/: opendir failed: Not a directory  dev/block/1:3/holders/: opendir failed: Not a directory  dev/block/1:15/holders/: opendir failed: Not a directory  dev/block/1:2/holders/: opendir failed: Not a directory  dev/block/1:13/holders/: opendir failed: Not a directory  dev/block/1:14/holders/: opendir failed: Not a directory  dev/block/1:12/holders/: opendir failed: Not a directory  dev/block/1:0/holders/: opendir failed: Not a directory  dev/block/1:1/holders/: opendir failed: Not a directory  dev/block/7:0/holders/: opendir failed: Not a directory  dev/block/7:7/holders/: opendir failed: Not a directory  dev/block/7:1/holders/: opendir failed: Not a directory  dev/block/7:6/holders/: opendir failed: Not a directory  dev/block/7:5/holders/: opendir failed: Not a directory  dev/block/7:3/holders/: opendir failed: Not a directory  dev/block/7:4/holders/: opendir failed: Not a directory  dev/block/7:2/holders/: opendir failed: Not a directory  dev/block/252:2/holders/: opendir failed: Not a directory  dev/block/252:1/holders/: opendir failed: Not a directory  dev/block/252:3/holders/: opendir failed: Not a directory  dev/block/252:0/holders/: opendir failed: Not a directory  dev/block/8:33/holders/: opendir failed: Not a directory  dev/block/8:32/holders/: opendir failed: Not a directory  dev/block/8:16/holders/: opendir failed: Not a directory  dev/block/8:3/holders/: opendir failed: Not a directory  dev/block/8:5/holders/: opendir failed: Not a directory  dev/block/11:0/holders/: opendir failed: Not a directory  dev/block/8:1/holders/: opendir failed: Not a directory  dev/block/8:2/holders/: opendir failed: Not a directory  

Re: Laptop recommendation

[tv.deb...@googlemail.com]

On 03/09/2017 19:08, Jonas Hedman wrote:

Hello I hope that is not OT for this list.

Basically I'm on the hunt for a newish laptop on which I naturally want
to run Debian. I'm a student and I spend most of my daily outandabout
computer time reading pdfs, writing LaTeX docs, surfing and doing some
light coding, no heavy duty stuff in other words. I use i3vm and I
generally like to keep things as light and minimal as feasibly possible.

I really value light weight and good battery life and my upper bound on prize
is somewhere around 875$ (~7K SEK). Memory should be greater than or
equal to 2GB and an sdd would be nice.

I know very little about hardware and I'm not quite sure where or how to
start looking. I though the Lenovo Thinkpad 13 looked promising but it's a bit
over my price target. Could chromeboosk be something to look into? I
know the older thinkpads has good debian support but if I remember
correctly they are also very heavy.

As a small reference: I made due with a Asus EEE PC 1005HA for a number
of years and it generally worked well for my purposes but it died and
surfing was a pain so I'm looking to upgrade a bit from that.

Any suggestions?

Best regards



Hi, I recently installed Debian 9 on an Asus "Zenbook" X430-UA (Intel 
graphics) and it runs beautifully. It's my son study laptop and it's 
performing well so far, battery life is excellent. Everything works, I 
installed in UEFI mode alongside Win, grub is managing the boot process 
for both OS, no problem outside of Win clobbering the bootloader already 
once during an upgrade, but easy to fix. The keyboard is by my standards 
(using Thinkpads and mechanical keyboard on desktops) awful, the space 
bar stands out as particularly bad and spongy, but it is my only serious 
complaint. Screen is too bright and blue, but easily fixed by applying a 
color profile with "dispcalgui". It is not free since it requires 
firmwares for Intel hardware, but everything is included in Debian 
non-free. No ethernet port, tested a usb-c > ethernet adapter and it 
worked well. Card reader works, webcam+mic too, touchpad (clickpad) is 
good and very precise, click is not "clicky" enough for me but ok. I 
didn't test the fingerprint reader but assume it doesn't work, I have no 
use for it anyway. Sound is unexpectedly good for such a thin and light 
laptop. My son loves it.


Happy shopping.

Re: UI inconsistency: unlocking LUKS-encrypted drives

[Sam Kuper]

On 03/09/2017, Sam Kuper  wrote:
> For some LUKS-encrypted partitions, when I unlock them from Debian,
> the computer only asks me for the passphrase for the encrypted
> partition. For other such partitions, when I unlock them, the computer
> also asks me for my user password.* See detailed description below.
>
> My questions are:
>
> 1. is this inconsistency intended, and if so, why?

The cause of the inconsistency seems to have been that the
"HintSystem" property[1] was set differently between the various
devices concerned.

[1]: 
https://people.freedesktop.org/~david/udisks2-20110929/gdbus-org.freedesktop.UDisks2.Block.html

Re: (solved) Re: how to roll back to jessie

[Cindy-Sue Causey]

On 9/3/17, songbird  wrote:
> Long Wind wrote:
> ...
>> I have decided re-install jessie from scratch
>> Thanks to all those who reply!
>
>   you're welcome.  it's really the easiest way to
> go if you want quickest and easiest approach.


It's about the "cleanest" route. You get to start all over with a
fresh, clean slate. Being able to easily save the .deb archive files
makes reinstalling favorite programs *so easy*, too.

Tools are making it easier to keep tabs primarily on the /etc
directory where we fiddle around in there, too. Beyond that, much of
what we don't want to lose ends up under /home/[user]. It has been a
very long time since I've lost anything setting wise so things are
really seeming user friendly.

You can always save the problem child install somewhere off to the
side... and then either play around with it later to learn something
new from it

Or just delete it down the road and teach yourself something even
newer than that because Time is too precious these days.
*kernelnewbies, cough-cough* :D

Cindy :)
-- 
Cindy-Sue Causey
Talking Rock, Pickens County, Georgia, USA

* runs with duct tape *

Re: Erro ao recuperar grub de um Debian com LVM Criptografado.

[Ricardo Ramos]

Tenta desabilitar o lvmetad conforme indicado nesse post pra ver se ele
reconhece pelo menos a instalação do Debian.

https://superuser.com/questions/1093509/kali-linux-2-0-failed-to-connect-to-lvmetad-falling-back-to-device-scanning

On Dom, 3 de set de 2017, 22:50 Luiz Carlos  wrote:

> Esse foi os comandos que usei até agora:
> modprobe dm-crypt
> cryptsetup luksOpen /dev/sda5 linux
> mkdir /media/linux
> mount /dev/lvmc/root /media/linux/
> mount -o bind /dev/ /media/linux/dev
> mount -o bind /proc/ /media/linux/proc
> mount -o bind /sys/ /media/linux/sys/
> mount -o bind /dev/pts/ /media/linux/dev/pts/
> chroot /media/linux /bin/bash
> mount /dev/sda1 /boot
> grub-install /dev/sda
>
> Em 4 de setembro de 2017 01:48, Luiz Carlos  escreveu:
>
>> Eu dou um update-grub e olha o que aparece:
>> # update-grub
>> Generating grub configuration file ...
>> Found background image: .background_cache.png
>>   WARNING: Failed to connect to lvmetad. Falling back to device scanning.
>>   WARNING: Failed to connect to lvmetad. Falling back to device scanning.
>>   WARNING: Failed to connect to lvmetad. Falling back to device scanning.
>>   WARNING: Failed to connect to lvmetad. Falling back to device scanning.
>>   WARNING: Failed to connect to lvmetad. Falling back to device scanning.
>>   WARNING: Failed to connect to lvmetad. Falling back to device scanning.
>>   WARNING: Failed to connect to lvmetad. Falling back to device scanning.
>> Found Windows 10 on /dev/sda1
>>
>> E o grub foi instalado, mas ele só reconhece o Windows, o Linux ele não
>> reconhece.
>>
>> Antes disso eu desabilietei o GRUB_ENABLE_CRYPTODISK=y, isso faz o grub
>> iniciar pedindo senha que nem sei.
>>
>> Em 4 de setembro de 2017 01:29, Ricardo Ramos 
>> escreveu:
>>
>>> Cara, pelo que consegui encontrar da pesquisa rápida que fiz foi que
>>> esse FlexNet é um programa de DRM, ele parece ter bloqueado o sector 32 do
>>> seu HD (provavelmente algum programa dentro do Windows ou o próprio Windows
>>> instalou ele). A única solução que vi foi literalmente zerar o sector que
>>> ele ocupou e seguir com a instalação do grub de novo.
>>>
>>> dd if=/dev/zero of=/dev/sda bs=512 count=1 seek=32
>>>
>>> Tente limpar o sector no HD, mesmo que não consiga montar a partição,
>>> tente identificar correctamente ele e depois zere ele, depois tenta
>>> reinstalar o grub e diz como correu.
>>>
>>> On Dom, 3 de set de 2017, 22:06 Luiz Carlos  wrote:
>>>
 Cara, eu sai do chroot e fiz isso e editei o arquivo do grub colocando
 GRUB_ENABLE_CRYPTODISK=y, voltando no chroot, olha o que deu:
 # grub-install /dev/sda
 Installing for i386-pc platform.
   WARNING: Failed to connect to lvmetad. Falling back to device
 scanning.
   WARNING: Failed to connect to lvmetad. Falling back to device
 scanning.
   WARNING: Failed to connect to lvmetad. Falling back to device
 scanning.
 grub-install: warning: Sector 32 is already in use by the program
 `FlexNet'; avoiding it.  This software may cause boot or other problems in
 future.  Please ask its authors not to store data in the boot track.

 Em 4 de setembro de 2017 01:04, Luiz Carlos 
 escreveu:

> Cara, eu sai do chroot e fiz isso e editei o arquivo do grub colocando
> GRUB_ENABLE_CRYPTODISK=y, voltando no chroot, olha o que deu:
> # grub-install /dev/sda
> Installing for i386-pc platform.
>   WARNING: Failed to connect to lvmetad. Falling back to device
> scanning.
>   WARNING: Failed to connect to lvmetad. Falling back to device
> scanning.
>   WARNING: Failed to connect to lvmetad. Falling back to device
> scanning.
> grub-install: warning: Sector 32 is already in use by the program
> `FlexNet'; avoiding it.  This software may cause boot or other problems in
> future.  Please ask its authors not to store data in the boot track.
> Installation finished. No error reported.
>
>
> Em 4 de setembro de 2017 00:55, Ricardo Ramos <
> cesar.ricki...@gmail.com> escreveu:
>
>> Procura no manual do grub see e possível especificar a arquitetura,
>> no erro ele indica que tenta instalar pra arquitetura i386-pc, tenta
>> especificar amd64, e tenta também dentro do chroot procurar o arquivo
>> "default/grub" pra ver se consegue habilitar essa opção.
>>
>> On Dom, 3 de set de 2017, 21:51 Luiz Carlos 
>> wrote:
>>
>>> AMD64, mas eu não estou conseguindo abrir o arquivo pra fazer a
>>> edição, não sei como habilitar essa GRUB_ENABLE_CRYPTODISK=y
>>> # xedit /etc/default/grub
>>> No protocol specified
>>>
>>>
>>> Em 4 de setembro de 2017 00:47, Ricardo Ramos <
>>> cesar.ricki...@gmail.com> escreveu:
>>>
 Qual é a arquitetura que VC tinha instalada?

 On Dom, 3 de set de 2017, 21:45 Luiz 

Re: Erro ao recuperar grub de um Debian com LVM Criptografado.

[Luiz Carlos]

Esse foi os comandos que usei até agora:
modprobe dm-crypt
cryptsetup luksOpen /dev/sda5 linux
mkdir /media/linux
mount /dev/lvmc/root /media/linux/
mount -o bind /dev/ /media/linux/dev
mount -o bind /proc/ /media/linux/proc
mount -o bind /sys/ /media/linux/sys/
mount -o bind /dev/pts/ /media/linux/dev/pts/
chroot /media/linux /bin/bash
mount /dev/sda1 /boot
grub-install /dev/sda

Em 4 de setembro de 2017 01:48, Luiz Carlos  escreveu:

> Eu dou um update-grub e olha o que aparece:
> # update-grub
> Generating grub configuration file ...
> Found background image: .background_cache.png
>   WARNING: Failed to connect to lvmetad. Falling back to device scanning.
>   WARNING: Failed to connect to lvmetad. Falling back to device scanning.
>   WARNING: Failed to connect to lvmetad. Falling back to device scanning.
>   WARNING: Failed to connect to lvmetad. Falling back to device scanning.
>   WARNING: Failed to connect to lvmetad. Falling back to device scanning.
>   WARNING: Failed to connect to lvmetad. Falling back to device scanning.
>   WARNING: Failed to connect to lvmetad. Falling back to device scanning.
> Found Windows 10 on /dev/sda1
>
> E o grub foi instalado, mas ele só reconhece o Windows, o Linux ele não
> reconhece.
>
> Antes disso eu desabilietei o GRUB_ENABLE_CRYPTODISK=y, isso faz o grub
> iniciar pedindo senha que nem sei.
>
> Em 4 de setembro de 2017 01:29, Ricardo Ramos 
> escreveu:
>
>> Cara, pelo que consegui encontrar da pesquisa rápida que fiz foi que esse
>> FlexNet é um programa de DRM, ele parece ter bloqueado o sector 32 do seu
>> HD (provavelmente algum programa dentro do Windows ou o próprio Windows
>> instalou ele). A única solução que vi foi literalmente zerar o sector que
>> ele ocupou e seguir com a instalação do grub de novo.
>>
>> dd if=/dev/zero of=/dev/sda bs=512 count=1 seek=32
>>
>> Tente limpar o sector no HD, mesmo que não consiga montar a partição,
>> tente identificar correctamente ele e depois zere ele, depois tenta
>> reinstalar o grub e diz como correu.
>>
>> On Dom, 3 de set de 2017, 22:06 Luiz Carlos  wrote:
>>
>>> Cara, eu sai do chroot e fiz isso e editei o arquivo do grub colocando
>>> GRUB_ENABLE_CRYPTODISK=y, voltando no chroot, olha o que deu:
>>> # grub-install /dev/sda
>>> Installing for i386-pc platform.
>>>   WARNING: Failed to connect to lvmetad. Falling back to device scanning.
>>>   WARNING: Failed to connect to lvmetad. Falling back to device scanning.
>>>   WARNING: Failed to connect to lvmetad. Falling back to device scanning.
>>> grub-install: warning: Sector 32 is already in use by the program
>>> `FlexNet'; avoiding it.  This software may cause boot or other problems in
>>> future.  Please ask its authors not to store data in the boot track.
>>>
>>> Em 4 de setembro de 2017 01:04, Luiz Carlos 
>>> escreveu:
>>>
 Cara, eu sai do chroot e fiz isso e editei o arquivo do grub colocando
 GRUB_ENABLE_CRYPTODISK=y, voltando no chroot, olha o que deu:
 # grub-install /dev/sda
 Installing for i386-pc platform.
   WARNING: Failed to connect to lvmetad. Falling back to device
 scanning.
   WARNING: Failed to connect to lvmetad. Falling back to device
 scanning.
   WARNING: Failed to connect to lvmetad. Falling back to device
 scanning.
 grub-install: warning: Sector 32 is already in use by the program
 `FlexNet'; avoiding it.  This software may cause boot or other problems in
 future.  Please ask its authors not to store data in the boot track.
 Installation finished. No error reported.


 Em 4 de setembro de 2017 00:55, Ricardo Ramos  escreveu:

> Procura no manual do grub see e possível especificar a arquitetura, no
> erro ele indica que tenta instalar pra arquitetura i386-pc, tenta
> especificar amd64, e tenta também dentro do chroot procurar o arquivo
> "default/grub" pra ver se consegue habilitar essa opção.
>
> On Dom, 3 de set de 2017, 21:51 Luiz Carlos  wrote:
>
>> AMD64, mas eu não estou conseguindo abrir o arquivo pra fazer a
>> edição, não sei como habilitar essa GRUB_ENABLE_CRYPTODISK=y
>> # xedit /etc/default/grub
>> No protocol specified
>>
>>
>> Em 4 de setembro de 2017 00:47, Ricardo Ramos <
>> cesar.ricki...@gmail.com> escreveu:
>>
>>> Qual é a arquitetura que VC tinha instalada?
>>>
>>> On Dom, 3 de set de 2017, 21:45 Luiz Carlos 
>>> wrote:
>>>
 Saí do chroot e mountei /dev/pts e a sys, deu isso daqui:
 mint mint # mount -o bind /dev/pts/ /media/linux/dev/pt
 ptmx  pts/
 mint mint # mount -o bind /dev/pts/ /media/linux/dev/pts/
 mint mint # chroot /media/linux /bin/bash
 root@mint:/# grub-install /dev/sda
 Installing for i386-pc platform.
   WARNING: Failed to connect to 

Re: Erro ao recuperar grub de um Debian com LVM Criptografado.

[Luiz Carlos]

Eu dou um update-grub e olha o que aparece:
# update-grub
Generating grub configuration file ...
Found background image: .background_cache.png
  WARNING: Failed to connect to lvmetad. Falling back to device scanning.
  WARNING: Failed to connect to lvmetad. Falling back to device scanning.
  WARNING: Failed to connect to lvmetad. Falling back to device scanning.
  WARNING: Failed to connect to lvmetad. Falling back to device scanning.
  WARNING: Failed to connect to lvmetad. Falling back to device scanning.
  WARNING: Failed to connect to lvmetad. Falling back to device scanning.
  WARNING: Failed to connect to lvmetad. Falling back to device scanning.
Found Windows 10 on /dev/sda1

E o grub foi instalado, mas ele só reconhece o Windows, o Linux ele não
reconhece.

Antes disso eu desabilietei o GRUB_ENABLE_CRYPTODISK=y, isso faz o grub
iniciar pedindo senha que nem sei.

Em 4 de setembro de 2017 01:29, Ricardo Ramos 
escreveu:

> Cara, pelo que consegui encontrar da pesquisa rápida que fiz foi que esse
> FlexNet é um programa de DRM, ele parece ter bloqueado o sector 32 do seu
> HD (provavelmente algum programa dentro do Windows ou o próprio Windows
> instalou ele). A única solução que vi foi literalmente zerar o sector que
> ele ocupou e seguir com a instalação do grub de novo.
>
> dd if=/dev/zero of=/dev/sda bs=512 count=1 seek=32
>
> Tente limpar o sector no HD, mesmo que não consiga montar a partição,
> tente identificar correctamente ele e depois zere ele, depois tenta
> reinstalar o grub e diz como correu.
>
> On Dom, 3 de set de 2017, 22:06 Luiz Carlos  wrote:
>
>> Cara, eu sai do chroot e fiz isso e editei o arquivo do grub colocando
>> GRUB_ENABLE_CRYPTODISK=y, voltando no chroot, olha o que deu:
>> # grub-install /dev/sda
>> Installing for i386-pc platform.
>>   WARNING: Failed to connect to lvmetad. Falling back to device scanning.
>>   WARNING: Failed to connect to lvmetad. Falling back to device scanning.
>>   WARNING: Failed to connect to lvmetad. Falling back to device scanning.
>> grub-install: warning: Sector 32 is already in use by the program
>> `FlexNet'; avoiding it.  This software may cause boot or other problems in
>> future.  Please ask its authors not to store data in the boot track.
>>
>> Em 4 de setembro de 2017 01:04, Luiz Carlos  escreveu:
>>
>>> Cara, eu sai do chroot e fiz isso e editei o arquivo do grub colocando
>>> GRUB_ENABLE_CRYPTODISK=y, voltando no chroot, olha o que deu:
>>> # grub-install /dev/sda
>>> Installing for i386-pc platform.
>>>   WARNING: Failed to connect to lvmetad. Falling back to device scanning.
>>>   WARNING: Failed to connect to lvmetad. Falling back to device scanning.
>>>   WARNING: Failed to connect to lvmetad. Falling back to device scanning.
>>> grub-install: warning: Sector 32 is already in use by the program
>>> `FlexNet'; avoiding it.  This software may cause boot or other problems in
>>> future.  Please ask its authors not to store data in the boot track.
>>> Installation finished. No error reported.
>>>
>>>
>>> Em 4 de setembro de 2017 00:55, Ricardo Ramos 
>>> escreveu:
>>>
 Procura no manual do grub see e possível especificar a arquitetura, no
 erro ele indica que tenta instalar pra arquitetura i386-pc, tenta
 especificar amd64, e tenta também dentro do chroot procurar o arquivo
 "default/grub" pra ver se consegue habilitar essa opção.

 On Dom, 3 de set de 2017, 21:51 Luiz Carlos  wrote:

> AMD64, mas eu não estou conseguindo abrir o arquivo pra fazer a
> edição, não sei como habilitar essa GRUB_ENABLE_CRYPTODISK=y
> # xedit /etc/default/grub
> No protocol specified
>
>
> Em 4 de setembro de 2017 00:47, Ricardo Ramos <
> cesar.ricki...@gmail.com> escreveu:
>
>> Qual é a arquitetura que VC tinha instalada?
>>
>> On Dom, 3 de set de 2017, 21:45 Luiz Carlos 
>> wrote:
>>
>>> Saí do chroot e mountei /dev/pts e a sys, deu isso daqui:
>>> mint mint # mount -o bind /dev/pts/ /media/linux/dev/pt
>>> ptmx  pts/
>>> mint mint # mount -o bind /dev/pts/ /media/linux/dev/pts/
>>> mint mint # chroot /media/linux /bin/bash
>>> root@mint:/# grub-install /dev/sda
>>> Installing for i386-pc platform.
>>>   WARNING: Failed to connect to lvmetad. Falling back to device
>>> scanning.
>>>   WARNING: Failed to connect to lvmetad. Falling back to device
>>> scanning.
>>> grub-install: error: attempt to install to encrypted disk without
>>> cryptodisk enabled. Set `GRUB_ENABLE_CRYPTODISK=y' in file
>>> `/etc/default/grub'.
>>>
>>>
>>> Em 4 de setembro de 2017 00:42, Ricardo Ramos <
>>> cesar.ricki...@gmail.com> escreveu:
>>>
 Tenta de novo, mas primeiro faz o recomendado pelo erro.

 grub-install: error: attempt to install to encrypted disk without

Re: Erro ao recuperar grub de um Debian com LVM Criptografado.

[Ricardo Ramos]

Cara, pelo que consegui encontrar da pesquisa rápida que fiz foi que esse
FlexNet é um programa de DRM, ele parece ter bloqueado o sector 32 do seu
HD (provavelmente algum programa dentro do Windows ou o próprio Windows
instalou ele). A única solução que vi foi literalmente zerar o sector que
ele ocupou e seguir com a instalação do grub de novo.

dd if=/dev/zero of=/dev/sda bs=512 count=1 seek=32

Tente limpar o sector no HD, mesmo que não consiga montar a partição, tente
identificar correctamente ele e depois zere ele, depois tenta reinstalar o
grub e diz como correu.

On Dom, 3 de set de 2017, 22:06 Luiz Carlos  wrote:

> Cara, eu sai do chroot e fiz isso e editei o arquivo do grub colocando
> GRUB_ENABLE_CRYPTODISK=y, voltando no chroot, olha o que deu:
> # grub-install /dev/sda
> Installing for i386-pc platform.
>   WARNING: Failed to connect to lvmetad. Falling back to device scanning.
>   WARNING: Failed to connect to lvmetad. Falling back to device scanning.
>   WARNING: Failed to connect to lvmetad. Falling back to device scanning.
> grub-install: warning: Sector 32 is already in use by the program
> `FlexNet'; avoiding it.  This software may cause boot or other problems in
> future.  Please ask its authors not to store data in the boot track.
>
> Em 4 de setembro de 2017 01:04, Luiz Carlos  escreveu:
>
>> Cara, eu sai do chroot e fiz isso e editei o arquivo do grub colocando
>> GRUB_ENABLE_CRYPTODISK=y, voltando no chroot, olha o que deu:
>> # grub-install /dev/sda
>> Installing for i386-pc platform.
>>   WARNING: Failed to connect to lvmetad. Falling back to device scanning.
>>   WARNING: Failed to connect to lvmetad. Falling back to device scanning.
>>   WARNING: Failed to connect to lvmetad. Falling back to device scanning.
>> grub-install: warning: Sector 32 is already in use by the program
>> `FlexNet'; avoiding it.  This software may cause boot or other problems in
>> future.  Please ask its authors not to store data in the boot track.
>> Installation finished. No error reported.
>>
>>
>> Em 4 de setembro de 2017 00:55, Ricardo Ramos 
>> escreveu:
>>
>>> Procura no manual do grub see e possível especificar a arquitetura, no
>>> erro ele indica que tenta instalar pra arquitetura i386-pc, tenta
>>> especificar amd64, e tenta também dentro do chroot procurar o arquivo
>>> "default/grub" pra ver se consegue habilitar essa opção.
>>>
>>> On Dom, 3 de set de 2017, 21:51 Luiz Carlos  wrote:
>>>
 AMD64, mas eu não estou conseguindo abrir o arquivo pra fazer a edição,
 não sei como habilitar essa GRUB_ENABLE_CRYPTODISK=y
 # xedit /etc/default/grub
 No protocol specified


 Em 4 de setembro de 2017 00:47, Ricardo Ramos  escreveu:

> Qual é a arquitetura que VC tinha instalada?
>
> On Dom, 3 de set de 2017, 21:45 Luiz Carlos  wrote:
>
>> Saí do chroot e mountei /dev/pts e a sys, deu isso daqui:
>> mint mint # mount -o bind /dev/pts/ /media/linux/dev/pt
>> ptmx  pts/
>> mint mint # mount -o bind /dev/pts/ /media/linux/dev/pts/
>> mint mint # chroot /media/linux /bin/bash
>> root@mint:/# grub-install /dev/sda
>> Installing for i386-pc platform.
>>   WARNING: Failed to connect to lvmetad. Falling back to device
>> scanning.
>>   WARNING: Failed to connect to lvmetad. Falling back to device
>> scanning.
>> grub-install: error: attempt to install to encrypted disk without
>> cryptodisk enabled. Set `GRUB_ENABLE_CRYPTODISK=y' in file
>> `/etc/default/grub'.
>>
>>
>> Em 4 de setembro de 2017 00:42, Ricardo Ramos <
>> cesar.ricki...@gmail.com> escreveu:
>>
>>> Tenta de novo, mas primeiro faz o recomendado pelo erro.
>>>
>>> grub-install: error: attempt to install to encrypted disk without
>>> cryptodisk enabled. Set ***`GRUB_ENABLE_CRYPTODISK=y'*** in file
>>> `/etc/default/grub'.
>>>
>>> Tenta habilitando essa opção no grub antes de instalar, depois diz
>>> como correu.
>>>
>>> Força
>>>
>>> On Dom, 3 de set de 2017, 21:38 Luiz Carlos 
>>> wrote:
>>>
 Henrique e Junior, executei os seguintes comandos:
 mint mint # modprobe dm-crypt
 mint mint # cryptsetup luksOpen /dev/sda5 linux
 Enter passphrase for /dev/sda5:
 mint mint # vgscan
   Reading all physical volumes.  This may take a while...
   Found volume group "lvmc" using metadata type lvm2
 mint mint # lvscan
   ACTIVE'/dev/lvmc/swap' [1.86 GiB] inherit
   ACTIVE'/dev/lvmc/root' [37.25 GiB] inherit
   ACTIVE'/dev/lvmc/home' [327.60 GiB] inherit
 mint mint # mkdir /media/linux
 mint mint # mount /dev/lvmc/root /media/linux/
 mint mint # mount -o bind /dev/ /media/linux/dev
 

Re: Laptop recommendation

[Ben Finney]

Mario Castelán Castro  writes:

> On 03/09/17 08:38, Jonas Hedman wrote:
> > Basically I'm on the hunt for a newish laptop on which I naturally
> > want to run Debian. [...]
> > 
> > Any suggestions?
>
> Yes. Think Penguin  sells computers
> compatible with GNU/Linux that do not need proprietary drivers.

Seconded. Think Penguin is one of very few vendors that actively source
components by working with manufacturers to ensure they need no
proprietary drivers.

> They claim to donate part of the profit to the development of free
> software (I can neither confirm nor deny this claim).

Think Penguin do indeed spend hours of paid work to *increase* the
number of hardware devices that will work with only free software. See

as an example, the TPE-R1100.

> Use H-node  to check for hardware compatibility
> and contribute an entry for your hardware if you can.

The H-node project is a great community resource. More contributions
keep it humming.

-- 
 \ “Try adding “as long as you don't breach the terms of service – |
  `\  according to our sole judgement” to the end of any cloud |
_o__)  computing pitch.” —Simon Phipps, 2010-12-11 |
Ben Finney

Re: (solved) Re: how to roll back to jessie

[songbird]

Long Wind wrote:
...
> I have decided re-install jessie from scratch
> Thanks to all those who reply!

  you're welcome.  it's really the easiest way to
go if you want quickest and easiest approach.


  songbird

Re: Erro ao recuperar grub de um Debian com LVM Criptografado.

[Luiz Carlos]

Cara, eu sai do chroot e fiz isso e editei o arquivo do grub colocando
GRUB_ENABLE_CRYPTODISK=y, voltando no chroot, olha o que deu:
# grub-install /dev/sda
Installing for i386-pc platform.
  WARNING: Failed to connect to lvmetad. Falling back to device scanning.
  WARNING: Failed to connect to lvmetad. Falling back to device scanning.
  WARNING: Failed to connect to lvmetad. Falling back to device scanning.
grub-install: warning: Sector 32 is already in use by the program
`FlexNet'; avoiding it.  This software may cause boot or other problems in
future.  Please ask its authors not to store data in the boot track.

Em 4 de setembro de 2017 01:04, Luiz Carlos  escreveu:

> Cara, eu sai do chroot e fiz isso e editei o arquivo do grub colocando
> GRUB_ENABLE_CRYPTODISK=y, voltando no chroot, olha o que deu:
> # grub-install /dev/sda
> Installing for i386-pc platform.
>   WARNING: Failed to connect to lvmetad. Falling back to device scanning.
>   WARNING: Failed to connect to lvmetad. Falling back to device scanning.
>   WARNING: Failed to connect to lvmetad. Falling back to device scanning.
> grub-install: warning: Sector 32 is already in use by the program
> `FlexNet'; avoiding it.  This software may cause boot or other problems in
> future.  Please ask its authors not to store data in the boot track.
> Installation finished. No error reported.
>
>
> Em 4 de setembro de 2017 00:55, Ricardo Ramos 
> escreveu:
>
>> Procura no manual do grub see e possível especificar a arquitetura, no
>> erro ele indica que tenta instalar pra arquitetura i386-pc, tenta
>> especificar amd64, e tenta também dentro do chroot procurar o arquivo
>> "default/grub" pra ver se consegue habilitar essa opção.
>>
>> On Dom, 3 de set de 2017, 21:51 Luiz Carlos  wrote:
>>
>>> AMD64, mas eu não estou conseguindo abrir o arquivo pra fazer a edição,
>>> não sei como habilitar essa GRUB_ENABLE_CRYPTODISK=y
>>> # xedit /etc/default/grub
>>> No protocol specified
>>>
>>>
>>> Em 4 de setembro de 2017 00:47, Ricardo Ramos 
>>> escreveu:
>>>
 Qual é a arquitetura que VC tinha instalada?

 On Dom, 3 de set de 2017, 21:45 Luiz Carlos  wrote:

> Saí do chroot e mountei /dev/pts e a sys, deu isso daqui:
> mint mint # mount -o bind /dev/pts/ /media/linux/dev/pt
> ptmx  pts/
> mint mint # mount -o bind /dev/pts/ /media/linux/dev/pts/
> mint mint # chroot /media/linux /bin/bash
> root@mint:/# grub-install /dev/sda
> Installing for i386-pc platform.
>   WARNING: Failed to connect to lvmetad. Falling back to device
> scanning.
>   WARNING: Failed to connect to lvmetad. Falling back to device
> scanning.
> grub-install: error: attempt to install to encrypted disk without
> cryptodisk enabled. Set `GRUB_ENABLE_CRYPTODISK=y' in file
> `/etc/default/grub'.
>
>
> Em 4 de setembro de 2017 00:42, Ricardo Ramos <
> cesar.ricki...@gmail.com> escreveu:
>
>> Tenta de novo, mas primeiro faz o recomendado pelo erro.
>>
>> grub-install: error: attempt to install to encrypted disk without
>> cryptodisk enabled. Set ***`GRUB_ENABLE_CRYPTODISK=y'*** in file
>> `/etc/default/grub'.
>>
>> Tenta habilitando essa opção no grub antes de instalar, depois diz
>> como correu.
>>
>> Força
>>
>> On Dom, 3 de set de 2017, 21:38 Luiz Carlos 
>> wrote:
>>
>>> Henrique e Junior, executei os seguintes comandos:
>>> mint mint # modprobe dm-crypt
>>> mint mint # cryptsetup luksOpen /dev/sda5 linux
>>> Enter passphrase for /dev/sda5:
>>> mint mint # vgscan
>>>   Reading all physical volumes.  This may take a while...
>>>   Found volume group "lvmc" using metadata type lvm2
>>> mint mint # lvscan
>>>   ACTIVE'/dev/lvmc/swap' [1.86 GiB] inherit
>>>   ACTIVE'/dev/lvmc/root' [37.25 GiB] inherit
>>>   ACTIVE'/dev/lvmc/home' [327.60 GiB] inherit
>>> mint mint # mkdir /media/linux
>>> mint mint # mount /dev/lvmc/root /media/linux/
>>> mint mint # mount -o bind /dev/ /media/linux/dev
>>> mint mint # mount -o bind /proc/ /media/linux/proc
>>> mint mint # chroot /media/linux /bin/bash
>>> root@mint:/# grub-install /dev/sda
>>> Installing for i386-pc platform.
>>>   Failed to find sysfs mount point
>>>   WARNING: Failed to connect to lvmetad. Falling back to device
>>> scanning.
>>>   dev/block/252:2/holders/: opendir failed: Not a directory
>>>   dev/block/252:1/holders/: opendir failed: Not a directory
>>>   dev/block/252:3/holders/: opendir failed: Not a directory
>>>   dev/block/252:0/holders/: opendir failed: Not a directory
>>>   dev/block/8:33/holders/: opendir failed: Not a directory
>>>   dev/block/8:32/holders/: opendir failed: Not a directory
>>>   dev/block/8:16/holders/: 

Re: Erro ao recuperar grub de um Debian com LVM Criptografado.

[Ricardo Ramos]

Procura no manual do grub see e possível especificar a arquitetura, no erro
ele indica que tenta instalar pra arquitetura i386-pc, tenta especificar
amd64, e tenta também dentro do chroot procurar o arquivo "default/grub"
pra ver se consegue habilitar essa opção.

On Dom, 3 de set de 2017, 21:51 Luiz Carlos  wrote:

> AMD64, mas eu não estou conseguindo abrir o arquivo pra fazer a edição,
> não sei como habilitar essa GRUB_ENABLE_CRYPTODISK=y
> # xedit /etc/default/grub
> No protocol specified
>
>
> Em 4 de setembro de 2017 00:47, Ricardo Ramos 
> escreveu:
>
>> Qual é a arquitetura que VC tinha instalada?
>>
>> On Dom, 3 de set de 2017, 21:45 Luiz Carlos  wrote:
>>
>>> Saí do chroot e mountei /dev/pts e a sys, deu isso daqui:
>>> mint mint # mount -o bind /dev/pts/ /media/linux/dev/pt
>>> ptmx  pts/
>>> mint mint # mount -o bind /dev/pts/ /media/linux/dev/pts/
>>> mint mint # chroot /media/linux /bin/bash
>>> root@mint:/# grub-install /dev/sda
>>> Installing for i386-pc platform.
>>>   WARNING: Failed to connect to lvmetad. Falling back to device scanning.
>>>   WARNING: Failed to connect to lvmetad. Falling back to device scanning.
>>> grub-install: error: attempt to install to encrypted disk without
>>> cryptodisk enabled. Set `GRUB_ENABLE_CRYPTODISK=y' in file
>>> `/etc/default/grub'.
>>>
>>>
>>> Em 4 de setembro de 2017 00:42, Ricardo Ramos 
>>> escreveu:
>>>
 Tenta de novo, mas primeiro faz o recomendado pelo erro.

 grub-install: error: attempt to install to encrypted disk without
 cryptodisk enabled. Set ***`GRUB_ENABLE_CRYPTODISK=y'*** in file
 `/etc/default/grub'.

 Tenta habilitando essa opção no grub antes de instalar, depois diz como
 correu.

 Força

 On Dom, 3 de set de 2017, 21:38 Luiz Carlos  wrote:

> Henrique e Junior, executei os seguintes comandos:
> mint mint # modprobe dm-crypt
> mint mint # cryptsetup luksOpen /dev/sda5 linux
> Enter passphrase for /dev/sda5:
> mint mint # vgscan
>   Reading all physical volumes.  This may take a while...
>   Found volume group "lvmc" using metadata type lvm2
> mint mint # lvscan
>   ACTIVE'/dev/lvmc/swap' [1.86 GiB] inherit
>   ACTIVE'/dev/lvmc/root' [37.25 GiB] inherit
>   ACTIVE'/dev/lvmc/home' [327.60 GiB] inherit
> mint mint # mkdir /media/linux
> mint mint # mount /dev/lvmc/root /media/linux/
> mint mint # mount -o bind /dev/ /media/linux/dev
> mint mint # mount -o bind /proc/ /media/linux/proc
> mint mint # chroot /media/linux /bin/bash
> root@mint:/# grub-install /dev/sda
> Installing for i386-pc platform.
>   Failed to find sysfs mount point
>   WARNING: Failed to connect to lvmetad. Falling back to device
> scanning.
>   dev/block/252:2/holders/: opendir failed: Not a directory
>   dev/block/252:1/holders/: opendir failed: Not a directory
>   dev/block/252:3/holders/: opendir failed: Not a directory
>   dev/block/252:0/holders/: opendir failed: Not a directory
>   dev/block/8:33/holders/: opendir failed: Not a directory
>   dev/block/8:32/holders/: opendir failed: Not a directory
>   dev/block/8:16/holders/: opendir failed: Not a directory
>   dev/block/8:3/holders/: opendir failed: Not a directory
>   dev/block/8:5/holders/: opendir failed: Not a directory
>   dev/block/11:0/holders/: opendir failed: Not a directory
>   dev/block/8:1/holders/: opendir failed: Not a directory
>   dev/block/8:2/holders/: opendir failed: Not a directory
>   dev/block/8:4/holders/: opendir failed: Not a directory
>   dev/block/8:0/holders/: opendir failed: Not a directory
>   dev/block/1:7/holders/: opendir failed: Not a directory
>   dev/block/1:6/holders/: opendir failed: Not a directory
>   dev/block/1:9/holders/: opendir failed: Not a directory
>   dev/block/1:8/holders/: opendir failed: Not a directory
>   dev/block/1:5/holders/: opendir failed: Not a directory
>   dev/block/1:4/holders/: opendir failed: Not a directory
>   dev/block/1:10/holders/: opendir failed: Not a directory
>   dev/block/1:11/holders/: opendir failed: Not a directory
>   dev/block/1:3/holders/: opendir failed: Not a directory
>   dev/block/1:15/holders/: opendir failed: Not a directory
>   dev/block/1:2/holders/: opendir failed: Not a directory
>   dev/block/1:13/holders/: opendir failed: Not a directory
>   dev/block/1:14/holders/: opendir failed: Not a directory
>   dev/block/1:12/holders/: opendir failed: Not a directory
>   dev/block/1:0/holders/: opendir failed: Not a directory
>   dev/block/1:1/holders/: opendir failed: Not a directory
>   dev/block/7:0/holders/: opendir failed: Not a directory
>   dev/block/7:7/holders/: opendir failed: Not a directory
>   

Re: Erro ao recuperar grub de um Debian com LVM Criptografado.

[Luiz Carlos]

AMD64, mas eu não estou conseguindo abrir o arquivo pra fazer a edição, não
sei como habilitar essa GRUB_ENABLE_CRYPTODISK=y
# xedit /etc/default/grub
No protocol specified


Em 4 de setembro de 2017 00:47, Ricardo Ramos 
escreveu:

> Qual é a arquitetura que VC tinha instalada?
>
> On Dom, 3 de set de 2017, 21:45 Luiz Carlos  wrote:
>
>> Saí do chroot e mountei /dev/pts e a sys, deu isso daqui:
>> mint mint # mount -o bind /dev/pts/ /media/linux/dev/pt
>> ptmx  pts/
>> mint mint # mount -o bind /dev/pts/ /media/linux/dev/pts/
>> mint mint # chroot /media/linux /bin/bash
>> root@mint:/# grub-install /dev/sda
>> Installing for i386-pc platform.
>>   WARNING: Failed to connect to lvmetad. Falling back to device scanning.
>>   WARNING: Failed to connect to lvmetad. Falling back to device scanning.
>> grub-install: error: attempt to install to encrypted disk without
>> cryptodisk enabled. Set `GRUB_ENABLE_CRYPTODISK=y' in file
>> `/etc/default/grub'.
>>
>>
>> Em 4 de setembro de 2017 00:42, Ricardo Ramos 
>> escreveu:
>>
>>> Tenta de novo, mas primeiro faz o recomendado pelo erro.
>>>
>>> grub-install: error: attempt to install to encrypted disk without
>>> cryptodisk enabled. Set ***`GRUB_ENABLE_CRYPTODISK=y'*** in file
>>> `/etc/default/grub'.
>>>
>>> Tenta habilitando essa opção no grub antes de instalar, depois diz como
>>> correu.
>>>
>>> Força
>>>
>>> On Dom, 3 de set de 2017, 21:38 Luiz Carlos  wrote:
>>>
 Henrique e Junior, executei os seguintes comandos:
 mint mint # modprobe dm-crypt
 mint mint # cryptsetup luksOpen /dev/sda5 linux
 Enter passphrase for /dev/sda5:
 mint mint # vgscan
   Reading all physical volumes.  This may take a while...
   Found volume group "lvmc" using metadata type lvm2
 mint mint # lvscan
   ACTIVE'/dev/lvmc/swap' [1.86 GiB] inherit
   ACTIVE'/dev/lvmc/root' [37.25 GiB] inherit
   ACTIVE'/dev/lvmc/home' [327.60 GiB] inherit
 mint mint # mkdir /media/linux
 mint mint # mount /dev/lvmc/root /media/linux/
 mint mint # mount -o bind /dev/ /media/linux/dev
 mint mint # mount -o bind /proc/ /media/linux/proc
 mint mint # chroot /media/linux /bin/bash
 root@mint:/# grub-install /dev/sda
 Installing for i386-pc platform.
   Failed to find sysfs mount point
   WARNING: Failed to connect to lvmetad. Falling back to device
 scanning.
   dev/block/252:2/holders/: opendir failed: Not a directory
   dev/block/252:1/holders/: opendir failed: Not a directory
   dev/block/252:3/holders/: opendir failed: Not a directory
   dev/block/252:0/holders/: opendir failed: Not a directory
   dev/block/8:33/holders/: opendir failed: Not a directory
   dev/block/8:32/holders/: opendir failed: Not a directory
   dev/block/8:16/holders/: opendir failed: Not a directory
   dev/block/8:3/holders/: opendir failed: Not a directory
   dev/block/8:5/holders/: opendir failed: Not a directory
   dev/block/11:0/holders/: opendir failed: Not a directory
   dev/block/8:1/holders/: opendir failed: Not a directory
   dev/block/8:2/holders/: opendir failed: Not a directory
   dev/block/8:4/holders/: opendir failed: Not a directory
   dev/block/8:0/holders/: opendir failed: Not a directory
   dev/block/1:7/holders/: opendir failed: Not a directory
   dev/block/1:6/holders/: opendir failed: Not a directory
   dev/block/1:9/holders/: opendir failed: Not a directory
   dev/block/1:8/holders/: opendir failed: Not a directory
   dev/block/1:5/holders/: opendir failed: Not a directory
   dev/block/1:4/holders/: opendir failed: Not a directory
   dev/block/1:10/holders/: opendir failed: Not a directory
   dev/block/1:11/holders/: opendir failed: Not a directory
   dev/block/1:3/holders/: opendir failed: Not a directory
   dev/block/1:15/holders/: opendir failed: Not a directory
   dev/block/1:2/holders/: opendir failed: Not a directory
   dev/block/1:13/holders/: opendir failed: Not a directory
   dev/block/1:14/holders/: opendir failed: Not a directory
   dev/block/1:12/holders/: opendir failed: Not a directory
   dev/block/1:0/holders/: opendir failed: Not a directory
   dev/block/1:1/holders/: opendir failed: Not a directory
   dev/block/7:0/holders/: opendir failed: Not a directory
   dev/block/7:7/holders/: opendir failed: Not a directory
   dev/block/7:1/holders/: opendir failed: Not a directory
   dev/block/7:6/holders/: opendir failed: Not a directory
   dev/block/7:5/holders/: opendir failed: Not a directory
   dev/block/7:3/holders/: opendir failed: Not a directory
   dev/block/7:4/holders/: opendir failed: Not a directory
   dev/block/7:2/holders/: opendir failed: Not a directory
   dev/block/252:2/holders/: opendir failed: Not a directory
   

Re: Erro ao recuperar grub de um Debian com LVM Criptografado.

[Ricardo Ramos]

Qual é a arquitetura que VC tinha instalada?

On Dom, 3 de set de 2017, 21:45 Luiz Carlos  wrote:

> Saí do chroot e mountei /dev/pts e a sys, deu isso daqui:
> mint mint # mount -o bind /dev/pts/ /media/linux/dev/pt
> ptmx  pts/
> mint mint # mount -o bind /dev/pts/ /media/linux/dev/pts/
> mint mint # chroot /media/linux /bin/bash
> root@mint:/# grub-install /dev/sda
> Installing for i386-pc platform.
>   WARNING: Failed to connect to lvmetad. Falling back to device scanning.
>   WARNING: Failed to connect to lvmetad. Falling back to device scanning.
> grub-install: error: attempt to install to encrypted disk without
> cryptodisk enabled. Set `GRUB_ENABLE_CRYPTODISK=y' in file
> `/etc/default/grub'.
>
>
> Em 4 de setembro de 2017 00:42, Ricardo Ramos 
> escreveu:
>
>> Tenta de novo, mas primeiro faz o recomendado pelo erro.
>>
>> grub-install: error: attempt to install to encrypted disk without
>> cryptodisk enabled. Set ***`GRUB_ENABLE_CRYPTODISK=y'*** in file
>> `/etc/default/grub'.
>>
>> Tenta habilitando essa opção no grub antes de instalar, depois diz como
>> correu.
>>
>> Força
>>
>> On Dom, 3 de set de 2017, 21:38 Luiz Carlos  wrote:
>>
>>> Henrique e Junior, executei os seguintes comandos:
>>> mint mint # modprobe dm-crypt
>>> mint mint # cryptsetup luksOpen /dev/sda5 linux
>>> Enter passphrase for /dev/sda5:
>>> mint mint # vgscan
>>>   Reading all physical volumes.  This may take a while...
>>>   Found volume group "lvmc" using metadata type lvm2
>>> mint mint # lvscan
>>>   ACTIVE'/dev/lvmc/swap' [1.86 GiB] inherit
>>>   ACTIVE'/dev/lvmc/root' [37.25 GiB] inherit
>>>   ACTIVE'/dev/lvmc/home' [327.60 GiB] inherit
>>> mint mint # mkdir /media/linux
>>> mint mint # mount /dev/lvmc/root /media/linux/
>>> mint mint # mount -o bind /dev/ /media/linux/dev
>>> mint mint # mount -o bind /proc/ /media/linux/proc
>>> mint mint # chroot /media/linux /bin/bash
>>> root@mint:/# grub-install /dev/sda
>>> Installing for i386-pc platform.
>>>   Failed to find sysfs mount point
>>>   WARNING: Failed to connect to lvmetad. Falling back to device scanning.
>>>   dev/block/252:2/holders/: opendir failed: Not a directory
>>>   dev/block/252:1/holders/: opendir failed: Not a directory
>>>   dev/block/252:3/holders/: opendir failed: Not a directory
>>>   dev/block/252:0/holders/: opendir failed: Not a directory
>>>   dev/block/8:33/holders/: opendir failed: Not a directory
>>>   dev/block/8:32/holders/: opendir failed: Not a directory
>>>   dev/block/8:16/holders/: opendir failed: Not a directory
>>>   dev/block/8:3/holders/: opendir failed: Not a directory
>>>   dev/block/8:5/holders/: opendir failed: Not a directory
>>>   dev/block/11:0/holders/: opendir failed: Not a directory
>>>   dev/block/8:1/holders/: opendir failed: Not a directory
>>>   dev/block/8:2/holders/: opendir failed: Not a directory
>>>   dev/block/8:4/holders/: opendir failed: Not a directory
>>>   dev/block/8:0/holders/: opendir failed: Not a directory
>>>   dev/block/1:7/holders/: opendir failed: Not a directory
>>>   dev/block/1:6/holders/: opendir failed: Not a directory
>>>   dev/block/1:9/holders/: opendir failed: Not a directory
>>>   dev/block/1:8/holders/: opendir failed: Not a directory
>>>   dev/block/1:5/holders/: opendir failed: Not a directory
>>>   dev/block/1:4/holders/: opendir failed: Not a directory
>>>   dev/block/1:10/holders/: opendir failed: Not a directory
>>>   dev/block/1:11/holders/: opendir failed: Not a directory
>>>   dev/block/1:3/holders/: opendir failed: Not a directory
>>>   dev/block/1:15/holders/: opendir failed: Not a directory
>>>   dev/block/1:2/holders/: opendir failed: Not a directory
>>>   dev/block/1:13/holders/: opendir failed: Not a directory
>>>   dev/block/1:14/holders/: opendir failed: Not a directory
>>>   dev/block/1:12/holders/: opendir failed: Not a directory
>>>   dev/block/1:0/holders/: opendir failed: Not a directory
>>>   dev/block/1:1/holders/: opendir failed: Not a directory
>>>   dev/block/7:0/holders/: opendir failed: Not a directory
>>>   dev/block/7:7/holders/: opendir failed: Not a directory
>>>   dev/block/7:1/holders/: opendir failed: Not a directory
>>>   dev/block/7:6/holders/: opendir failed: Not a directory
>>>   dev/block/7:5/holders/: opendir failed: Not a directory
>>>   dev/block/7:3/holders/: opendir failed: Not a directory
>>>   dev/block/7:4/holders/: opendir failed: Not a directory
>>>   dev/block/7:2/holders/: opendir failed: Not a directory
>>>   dev/block/252:2/holders/: opendir failed: Not a directory
>>>   dev/block/252:1/holders/: opendir failed: Not a directory
>>>   dev/block/252:3/holders/: opendir failed: Not a directory
>>>   dev/block/252:0/holders/: opendir failed: Not a directory
>>>   dev/block/8:33/holders/: opendir failed: Not a directory
>>>   dev/block/8:32/holders/: opendir failed: Not a directory
>>>   dev/block/8:16/holders/: opendir failed: Not a 

Re: Erro ao recuperar grub de um Debian com LVM Criptografado.

[Luiz Carlos]

Saí do chroot e mountei /dev/pts e a sys, deu isso daqui:
mint mint # mount -o bind /dev/pts/ /media/linux/dev/pt
ptmx  pts/
mint mint # mount -o bind /dev/pts/ /media/linux/dev/pts/
mint mint # chroot /media/linux /bin/bash
root@mint:/# grub-install /dev/sda
Installing for i386-pc platform.
  WARNING: Failed to connect to lvmetad. Falling back to device scanning.
  WARNING: Failed to connect to lvmetad. Falling back to device scanning.
grub-install: error: attempt to install to encrypted disk without
cryptodisk enabled. Set `GRUB_ENABLE_CRYPTODISK=y' in file
`/etc/default/grub'.


Em 4 de setembro de 2017 00:42, Ricardo Ramos 
escreveu:

> Tenta de novo, mas primeiro faz o recomendado pelo erro.
>
> grub-install: error: attempt to install to encrypted disk without
> cryptodisk enabled. Set ***`GRUB_ENABLE_CRYPTODISK=y'*** in file
> `/etc/default/grub'.
>
> Tenta habilitando essa opção no grub antes de instalar, depois diz como
> correu.
>
> Força
>
> On Dom, 3 de set de 2017, 21:38 Luiz Carlos  wrote:
>
>> Henrique e Junior, executei os seguintes comandos:
>> mint mint # modprobe dm-crypt
>> mint mint # cryptsetup luksOpen /dev/sda5 linux
>> Enter passphrase for /dev/sda5:
>> mint mint # vgscan
>>   Reading all physical volumes.  This may take a while...
>>   Found volume group "lvmc" using metadata type lvm2
>> mint mint # lvscan
>>   ACTIVE'/dev/lvmc/swap' [1.86 GiB] inherit
>>   ACTIVE'/dev/lvmc/root' [37.25 GiB] inherit
>>   ACTIVE'/dev/lvmc/home' [327.60 GiB] inherit
>> mint mint # mkdir /media/linux
>> mint mint # mount /dev/lvmc/root /media/linux/
>> mint mint # mount -o bind /dev/ /media/linux/dev
>> mint mint # mount -o bind /proc/ /media/linux/proc
>> mint mint # chroot /media/linux /bin/bash
>> root@mint:/# grub-install /dev/sda
>> Installing for i386-pc platform.
>>   Failed to find sysfs mount point
>>   WARNING: Failed to connect to lvmetad. Falling back to device scanning.
>>   dev/block/252:2/holders/: opendir failed: Not a directory
>>   dev/block/252:1/holders/: opendir failed: Not a directory
>>   dev/block/252:3/holders/: opendir failed: Not a directory
>>   dev/block/252:0/holders/: opendir failed: Not a directory
>>   dev/block/8:33/holders/: opendir failed: Not a directory
>>   dev/block/8:32/holders/: opendir failed: Not a directory
>>   dev/block/8:16/holders/: opendir failed: Not a directory
>>   dev/block/8:3/holders/: opendir failed: Not a directory
>>   dev/block/8:5/holders/: opendir failed: Not a directory
>>   dev/block/11:0/holders/: opendir failed: Not a directory
>>   dev/block/8:1/holders/: opendir failed: Not a directory
>>   dev/block/8:2/holders/: opendir failed: Not a directory
>>   dev/block/8:4/holders/: opendir failed: Not a directory
>>   dev/block/8:0/holders/: opendir failed: Not a directory
>>   dev/block/1:7/holders/: opendir failed: Not a directory
>>   dev/block/1:6/holders/: opendir failed: Not a directory
>>   dev/block/1:9/holders/: opendir failed: Not a directory
>>   dev/block/1:8/holders/: opendir failed: Not a directory
>>   dev/block/1:5/holders/: opendir failed: Not a directory
>>   dev/block/1:4/holders/: opendir failed: Not a directory
>>   dev/block/1:10/holders/: opendir failed: Not a directory
>>   dev/block/1:11/holders/: opendir failed: Not a directory
>>   dev/block/1:3/holders/: opendir failed: Not a directory
>>   dev/block/1:15/holders/: opendir failed: Not a directory
>>   dev/block/1:2/holders/: opendir failed: Not a directory
>>   dev/block/1:13/holders/: opendir failed: Not a directory
>>   dev/block/1:14/holders/: opendir failed: Not a directory
>>   dev/block/1:12/holders/: opendir failed: Not a directory
>>   dev/block/1:0/holders/: opendir failed: Not a directory
>>   dev/block/1:1/holders/: opendir failed: Not a directory
>>   dev/block/7:0/holders/: opendir failed: Not a directory
>>   dev/block/7:7/holders/: opendir failed: Not a directory
>>   dev/block/7:1/holders/: opendir failed: Not a directory
>>   dev/block/7:6/holders/: opendir failed: Not a directory
>>   dev/block/7:5/holders/: opendir failed: Not a directory
>>   dev/block/7:3/holders/: opendir failed: Not a directory
>>   dev/block/7:4/holders/: opendir failed: Not a directory
>>   dev/block/7:2/holders/: opendir failed: Not a directory
>>   dev/block/252:2/holders/: opendir failed: Not a directory
>>   dev/block/252:1/holders/: opendir failed: Not a directory
>>   dev/block/252:3/holders/: opendir failed: Not a directory
>>   dev/block/252:0/holders/: opendir failed: Not a directory
>>   dev/block/8:33/holders/: opendir failed: Not a directory
>>   dev/block/8:32/holders/: opendir failed: Not a directory
>>   dev/block/8:16/holders/: opendir failed: Not a directory
>>   dev/block/8:3/holders/: opendir failed: Not a directory
>>   dev/block/8:5/holders/: opendir failed: Not a directory
>>   dev/block/11:0/holders/: opendir failed: Not a directory
>>   dev/block/8:1/holders/: opendir 

Re: Erro ao recuperar grub de um Debian com LVM Criptografado.

[Ricardo Ramos]

Tenta de novo, mas primeiro faz o recomendado pelo erro.

grub-install: error: attempt to install to encrypted disk without
cryptodisk enabled. Set ***`GRUB_ENABLE_CRYPTODISK=y'*** in file
`/etc/default/grub'.

Tenta habilitando essa opção no grub antes de instalar, depois diz como
correu.

Força

On Dom, 3 de set de 2017, 21:38 Luiz Carlos  wrote:

> Henrique e Junior, executei os seguintes comandos:
> mint mint # modprobe dm-crypt
> mint mint # cryptsetup luksOpen /dev/sda5 linux
> Enter passphrase for /dev/sda5:
> mint mint # vgscan
>   Reading all physical volumes.  This may take a while...
>   Found volume group "lvmc" using metadata type lvm2
> mint mint # lvscan
>   ACTIVE'/dev/lvmc/swap' [1.86 GiB] inherit
>   ACTIVE'/dev/lvmc/root' [37.25 GiB] inherit
>   ACTIVE'/dev/lvmc/home' [327.60 GiB] inherit
> mint mint # mkdir /media/linux
> mint mint # mount /dev/lvmc/root /media/linux/
> mint mint # mount -o bind /dev/ /media/linux/dev
> mint mint # mount -o bind /proc/ /media/linux/proc
> mint mint # chroot /media/linux /bin/bash
> root@mint:/# grub-install /dev/sda
> Installing for i386-pc platform.
>   Failed to find sysfs mount point
>   WARNING: Failed to connect to lvmetad. Falling back to device scanning.
>   dev/block/252:2/holders/: opendir failed: Not a directory
>   dev/block/252:1/holders/: opendir failed: Not a directory
>   dev/block/252:3/holders/: opendir failed: Not a directory
>   dev/block/252:0/holders/: opendir failed: Not a directory
>   dev/block/8:33/holders/: opendir failed: Not a directory
>   dev/block/8:32/holders/: opendir failed: Not a directory
>   dev/block/8:16/holders/: opendir failed: Not a directory
>   dev/block/8:3/holders/: opendir failed: Not a directory
>   dev/block/8:5/holders/: opendir failed: Not a directory
>   dev/block/11:0/holders/: opendir failed: Not a directory
>   dev/block/8:1/holders/: opendir failed: Not a directory
>   dev/block/8:2/holders/: opendir failed: Not a directory
>   dev/block/8:4/holders/: opendir failed: Not a directory
>   dev/block/8:0/holders/: opendir failed: Not a directory
>   dev/block/1:7/holders/: opendir failed: Not a directory
>   dev/block/1:6/holders/: opendir failed: Not a directory
>   dev/block/1:9/holders/: opendir failed: Not a directory
>   dev/block/1:8/holders/: opendir failed: Not a directory
>   dev/block/1:5/holders/: opendir failed: Not a directory
>   dev/block/1:4/holders/: opendir failed: Not a directory
>   dev/block/1:10/holders/: opendir failed: Not a directory
>   dev/block/1:11/holders/: opendir failed: Not a directory
>   dev/block/1:3/holders/: opendir failed: Not a directory
>   dev/block/1:15/holders/: opendir failed: Not a directory
>   dev/block/1:2/holders/: opendir failed: Not a directory
>   dev/block/1:13/holders/: opendir failed: Not a directory
>   dev/block/1:14/holders/: opendir failed: Not a directory
>   dev/block/1:12/holders/: opendir failed: Not a directory
>   dev/block/1:0/holders/: opendir failed: Not a directory
>   dev/block/1:1/holders/: opendir failed: Not a directory
>   dev/block/7:0/holders/: opendir failed: Not a directory
>   dev/block/7:7/holders/: opendir failed: Not a directory
>   dev/block/7:1/holders/: opendir failed: Not a directory
>   dev/block/7:6/holders/: opendir failed: Not a directory
>   dev/block/7:5/holders/: opendir failed: Not a directory
>   dev/block/7:3/holders/: opendir failed: Not a directory
>   dev/block/7:4/holders/: opendir failed: Not a directory
>   dev/block/7:2/holders/: opendir failed: Not a directory
>   dev/block/252:2/holders/: opendir failed: Not a directory
>   dev/block/252:1/holders/: opendir failed: Not a directory
>   dev/block/252:3/holders/: opendir failed: Not a directory
>   dev/block/252:0/holders/: opendir failed: Not a directory
>   dev/block/8:33/holders/: opendir failed: Not a directory
>   dev/block/8:32/holders/: opendir failed: Not a directory
>   dev/block/8:16/holders/: opendir failed: Not a directory
>   dev/block/8:3/holders/: opendir failed: Not a directory
>   dev/block/8:5/holders/: opendir failed: Not a directory
>   dev/block/11:0/holders/: opendir failed: Not a directory
>   dev/block/8:1/holders/: opendir failed: Not a directory
>   dev/block/8:2/holders/: opendir failed: Not a directory
>   dev/block/8:4/holders/: opendir failed: Not a directory
>   dev/block/8:0/holders/: opendir failed: Not a directory
>   dev/block/1:7/holders/: opendir failed: Not a directory
>   dev/block/1:6/holders/: opendir failed: Not a directory
>   dev/block/1:9/holders/: opendir failed: Not a directory
>   dev/block/1:8/holders/: opendir failed: Not a directory
>   dev/block/1:5/holders/: opendir failed: Not a directory
>   dev/block/1:4/holders/: opendir failed: Not a directory
>   dev/block/1:10/holders/: opendir failed: Not a directory
>   dev/block/1:11/holders/: opendir failed: Not a directory
>   dev/block/1:3/holders/: opendir failed: Not a directory
>   

Re: Erro ao recuperar grub de um Debian com LVM Criptografado.

[Luiz Carlos]

Henrique e Junior, executei os seguintes comandos:
mint mint # modprobe dm-crypt
mint mint # cryptsetup luksOpen /dev/sda5 linux
Enter passphrase for /dev/sda5:
mint mint # vgscan
  Reading all physical volumes.  This may take a while...
  Found volume group "lvmc" using metadata type lvm2
mint mint # lvscan
  ACTIVE'/dev/lvmc/swap' [1.86 GiB] inherit
  ACTIVE'/dev/lvmc/root' [37.25 GiB] inherit
  ACTIVE'/dev/lvmc/home' [327.60 GiB] inherit
mint mint # mkdir /media/linux
mint mint # mount /dev/lvmc/root /media/linux/
mint mint # mount -o bind /dev/ /media/linux/dev
mint mint # mount -o bind /proc/ /media/linux/proc
mint mint # chroot /media/linux /bin/bash
root@mint:/# grub-install /dev/sda
Installing for i386-pc platform.
  Failed to find sysfs mount point
  WARNING: Failed to connect to lvmetad. Falling back to device scanning.
  dev/block/252:2/holders/: opendir failed: Not a directory
  dev/block/252:1/holders/: opendir failed: Not a directory
  dev/block/252:3/holders/: opendir failed: Not a directory
  dev/block/252:0/holders/: opendir failed: Not a directory
  dev/block/8:33/holders/: opendir failed: Not a directory
  dev/block/8:32/holders/: opendir failed: Not a directory
  dev/block/8:16/holders/: opendir failed: Not a directory
  dev/block/8:3/holders/: opendir failed: Not a directory
  dev/block/8:5/holders/: opendir failed: Not a directory
  dev/block/11:0/holders/: opendir failed: Not a directory
  dev/block/8:1/holders/: opendir failed: Not a directory
  dev/block/8:2/holders/: opendir failed: Not a directory
  dev/block/8:4/holders/: opendir failed: Not a directory
  dev/block/8:0/holders/: opendir failed: Not a directory
  dev/block/1:7/holders/: opendir failed: Not a directory
  dev/block/1:6/holders/: opendir failed: Not a directory
  dev/block/1:9/holders/: opendir failed: Not a directory
  dev/block/1:8/holders/: opendir failed: Not a directory
  dev/block/1:5/holders/: opendir failed: Not a directory
  dev/block/1:4/holders/: opendir failed: Not a directory
  dev/block/1:10/holders/: opendir failed: Not a directory
  dev/block/1:11/holders/: opendir failed: Not a directory
  dev/block/1:3/holders/: opendir failed: Not a directory
  dev/block/1:15/holders/: opendir failed: Not a directory
  dev/block/1:2/holders/: opendir failed: Not a directory
  dev/block/1:13/holders/: opendir failed: Not a directory
  dev/block/1:14/holders/: opendir failed: Not a directory
  dev/block/1:12/holders/: opendir failed: Not a directory
  dev/block/1:0/holders/: opendir failed: Not a directory
  dev/block/1:1/holders/: opendir failed: Not a directory
  dev/block/7:0/holders/: opendir failed: Not a directory
  dev/block/7:7/holders/: opendir failed: Not a directory
  dev/block/7:1/holders/: opendir failed: Not a directory
  dev/block/7:6/holders/: opendir failed: Not a directory
  dev/block/7:5/holders/: opendir failed: Not a directory
  dev/block/7:3/holders/: opendir failed: Not a directory
  dev/block/7:4/holders/: opendir failed: Not a directory
  dev/block/7:2/holders/: opendir failed: Not a directory
  dev/block/252:2/holders/: opendir failed: Not a directory
  dev/block/252:1/holders/: opendir failed: Not a directory
  dev/block/252:3/holders/: opendir failed: Not a directory
  dev/block/252:0/holders/: opendir failed: Not a directory
  dev/block/8:33/holders/: opendir failed: Not a directory
  dev/block/8:32/holders/: opendir failed: Not a directory
  dev/block/8:16/holders/: opendir failed: Not a directory
  dev/block/8:3/holders/: opendir failed: Not a directory
  dev/block/8:5/holders/: opendir failed: Not a directory
  dev/block/11:0/holders/: opendir failed: Not a directory
  dev/block/8:1/holders/: opendir failed: Not a directory
  dev/block/8:2/holders/: opendir failed: Not a directory
  dev/block/8:4/holders/: opendir failed: Not a directory
  dev/block/8:0/holders/: opendir failed: Not a directory
  dev/block/1:7/holders/: opendir failed: Not a directory
  dev/block/1:6/holders/: opendir failed: Not a directory
  dev/block/1:9/holders/: opendir failed: Not a directory
  dev/block/1:8/holders/: opendir failed: Not a directory
  dev/block/1:5/holders/: opendir failed: Not a directory
  dev/block/1:4/holders/: opendir failed: Not a directory
  dev/block/1:10/holders/: opendir failed: Not a directory
  dev/block/1:11/holders/: opendir failed: Not a directory
  dev/block/1:3/holders/: opendir failed: Not a directory
  dev/block/1:15/holders/: opendir failed: Not a directory
  dev/block/1:2/holders/: opendir failed: Not a directory
  dev/block/1:13/holders/: opendir failed: Not a directory
  dev/block/1:14/holders/: opendir failed: Not a directory
  dev/block/1:12/holders/: opendir failed: Not a directory
  dev/block/1:0/holders/: opendir failed: Not a directory
  dev/block/1:1/holders/: opendir failed: Not a directory
  dev/block/7:0/holders/: opendir failed: Not a directory
  dev/block/7:7/holders/: opendir failed: Not a directory
  

Re: Serveur bloqué par de multiples CRON -f ?

[Charles Plessy]

> Le 16/03/17 à 11:27, Charles Plessy  a écrit :
> CP> 
> CP> (Résumé des épisodes précédents, j'ai une machine virtuelle sur laquelle 
> il
> CP> devient parfois impossible de se connecter.  Les sessions existantes 
> continuent
> CP> de fonctionner normalement, une grande partie des logs ne sont plus 
> écrits, et
> CP> un processus cron par heure se lance, semble bloquer et s'accumule.)

Le Fri, Mar 17, 2017 at 08:30:21AM +0100, Daniel Caillibaud a écrit :
> 
> Tu peux installer atop sur le host, et le régler avec une mesure par minute 
> (10 par défaut,
> dans /etc/default/atop mettre `INTERVAL=60`), ça devrait te permettre après 
> coup de voir à
> chaque minute l'état complet du host, par ex atop -r 
> /var/log/atop/atop_mmdd -b hh:mm
> pour avoir un top amélioré de cette minute là, que tu peux trier par conso 
> RAM, CPU, disque,
> etc. (man atop pour les détails).

Merci beaucoup pour la suggestion (et merci aussi à François pour sa
réponse); c'est assez formidable de pouvoir faire un « top » à rebours !

Nouveau plantage, mais cette fois-ci j'avais une fenêtre root ouverte.
Comme d'habitude, de nombreux processus « CRON -f » et impossibilité de
créer de nouvelles sessions (SSH, sudo, ...).  Cause ou conséquence,
cette fois-ci un démon gitlab-ci-multi-runner (source:
https://packages.gitlab.com/runner) accumulait des dizaines d'instances
(car il plantait naturellement suite à une différence de compatibilité
avec notre serveur local).  Je l'ai désinstallé, j'ai tué tous les
processus cron, j'ai relancé le service cron avec systemctl et j'ai
fini par un « systemctl reset-failed ».  Je peux de nouveau me connecter
à la machine sans avoir eu besoin de la redémarrer.

Un inspection avec atop de l'état de la machine au moment ou elle a
cessé d'enregistrer ses logs (sauf -- MARK --) ne montre rien de
spécial...  Mais ceci dit merci encore de m'avoir fait apprendre atop.

Je ne comprends toujours pas ce qui peut empêcher la machine de créer de
nouvelles sessions alors qu'il y a assez de mémoire, d'espace disque et
de temps processeur...

Bonne journée,

Charles

-- 
Charles Plessy
Tsurumi, Kanagawa, Japon

Re: Recommended editor for novice programmers?

[Zenaan Harkness]

On Mon, Sep 04, 2017 at 09:42:20AM +1200, Ben Caradoc-Davies wrote:
> On 03/09/17 06:21, Tom Browder wrote:
> > I would especially appreciate other ideas for programming editors for
> > novice programmers.
> 
> I use and recommend geany. And Eclipse.

+1 geany

I use geany for note taking, and when I want to print out text files
"nicely". I've also installed geany for others (3+ years happy
campers). Perfect for novice programmers.

However for Java programming, I always recommend Eclipse - as long as
you've got >= 1GiB RAM, Eclipse is fine for novices, the bees knees
for Java GUI IDEs, -and- has C and C++ support these days (besides a
zillion other languages).

I also have Eclipse installed, but for day to day coding I actually
prefer vim for two main reasons:

1) The "extreme lightweight" feel of vim (and geany for that matter
   which I alias to "n" for "n"otepad (I've changed "notepad"s a few
   times over the years, and keep the same alias of course...)) -
   opening a file always seems close to instantaneous.

2) The mindset, and consequent feeling engendered within me, from cmd
   line based edit-compile-run cycle development.

The only place I still intend to personally use Eclipse is either
developing a plugin for others to use, or developing actual GUI front
ends to software I've written (I'm confident one or both of these
will happen one day :)

Good luck,

Re: Laptop recommendation

[Zenaan Harkness]

On Sun, Sep 03, 2017 at 12:39:18PM -0400, Dan Ritter wrote:
> On Sun, Sep 03, 2017 at 03:38:17PM +0200, Jonas Hedman wrote:
> > Hello I hope that is not OT for this list.
> > 
> > Basically I'm on the hunt for a newish laptop on which I naturally want
> > to run Debian. I'm a student and I spend most of my daily outandabout 
> > computer time reading pdfs, writing LaTeX docs, surfing and doing some 
> > light coding, no heavy duty stuff in other words. I use i3vm and I
> > generally like to keep things as light and minimal as feasibly possible.
> > 
> > I really value light weight and good battery life and my upper bound on 
> > prize
> > is somewhere around 875$ (~7K SEK). Memory should be greater than or
> > equal to 2GB and an sdd would be nice.
> > 
> > I know very little about hardware and I'm not quite sure where or how to 
> > start looking. I though the Lenovo Thinkpad 13 looked promising but it's a 
> > bit 
> > over my price target. Could chromeboosk be something to look into? I
> > know the older thinkpads has good debian support but if I remember
> > correctly they are also very heavy.
> 
> System76 (www.system76.com) makes laptops that run Ubuntu; it
> has generally been easy to retrofit Debian on them. They have 
> several models that fit in your price range including more RAM
> and an SSD.

+1

Even "multimedia" keys and other things they generally ensure are
supported.

Re: One-line password generator

[Zenaan Harkness]

On Sat, Sep 02, 2017 at 09:33:10AM -0500, Mario Castelán Castro wrote:
> On 01/09/17 22:33, Zenaan Harkness wrote:
> > I am not mathematically literate enough to even properly parse that
> > sentence!
> 
> Here (and through the rest of your message) you are admitting that you
> do not understand the meaning of entropy in probability theory. Yet you
> are making statements about entropy. This is intellectually dishonest,
> to say the least.

Touché :)

Res: Erro ao recuperar grub de um Debian com LVM Criptografado.

[jmhenrique]

  Olá, boa noite! Antes de dar o chroot, vc precisa: 1 - abrir a partição criptografada (vi que vc fez isso) 2 - verificar se o seu livecd tem o lvm instalado, se não tiver, instale 3 - ativar o lvm com vgscan e verificar com lvscan ; 4 - montar o raiz do lvm : mount /dev/mapper/seuraizlvm /mnt/suafakeroot‎5 -  montar o proc e o dev com : mount -o bind /dev/  /mnt/suafakeroot/dev ‎mount -o bind /proc/ /mnt/suafakeroot/proc Só daí dar o chroot /mnt/suafakeroot, e instalar o grub normalmente. Deve funcionar sem maiores problemas. AbracosHenry Enviado do meu smartphone BlackBerry 10.De: Luiz CarlosEnviada: domingo, 3 de setembro de 2017 18:47Para: DUPAssunto: Re: Erro ao recuperar grub de um Debian com LVM Criptografado.# mount bootmount: can't find UUID=e7d99f42-7b2a-4afb-9a4a-009003c9f447Ta foda.Em 3 de setembro de 2017 21:39, Luiz Carlos  escreveu:É computador, aqui eu estou tentando novamente:root@mint:/# grub-install /dev/sdaInstalling for i386-pc platform.grub-install: error: cannot find a device for /boot/grub (is /dev mounted?).root@mint:/# mount /dev/sda2 /bootmount: /boot: mount failed: Unknown error -1root@mint:/# mount /dev/sda2 /boot/mount: /boot: mount failed: Unknown error -1root@mint:/# mount /dev/sda2 /boot/mount: /boot: mount failed: Unknown error -1root@mint:/# root@mint:/# mount /dev/sda2 /boot/mount: /boot: mount failed: Unknown error -1Em 3 de setembro de 2017 21:36, Rodolfo  escreveu:Uma pergunta, é computador ou notebook? é novo?Tipo, quando comprei meu notebook pesquisei bem sobre a dificuldade de usar linux nele, porque justamente não queria ter problemas, eu decidi comprar um notebook que fosse compatível com linux(o que na minha opinião nem deveria existir, pra mim qualquer computador/notebook tem que ser compatível com qualquer sistema, na prática parece que isso não acontece). Enfim, dê uma pesquisada sobre isso também.Em 3 de setembro de 2017 17:28, Luiz Carlos  escreveu:A droga do Seven estava uma merda que tinha vezes que não reconhecia o mouse e precisava ficar reiniciando toda pra isso resolver, por isso que tentei instalar o 10.Em 3 de setembro de 2017 21:27, Rodolfo  escreveu:Eu uso aqui dual boot windows 7 + debian 9, só tenho windows pra jogar alguns jogos, hehehe.Em 3 de setembro de 2017 17:25, Luiz Carlos  escreveu:A real é que a Microsoft é um lixo em fazer esse tipo de prática, pior que vou ter que instalar o Linux do zero pra ver se resolve, se não detectar o Windows 10, eu vou ter que voltar aquele dual boot com o seven como era antes. Desativei a hibernação tbm e nada.Em 3 de setembro de 2017 20:51, Rodolfo  escreveu:Isso, eu desativo esse secureboot. Bom, no seu caso você usa LVM, realmente pode ser algo que não conheço.Em 3 de setembro de 2017 16:46, Luiz Carlos  escreveu:Estou a ponto de desistir, acho que não tem jeito pra essa merda.Em 3 de setembro de 2017 20:19, Luiz Carlos  escreveu:Você fala de secureboot na UEFI né? Eu fui lá,  de "Windows" marquei pra Other OS, mas mesmo assim não resolveu.Antes disso eu já tentei o boot-repair, eles falam que restauram o sistema, mas na pratica instalam um grub sem nada, aqui está o log deles:http://paste.ubuntu.com/25460229/2017-09-03 19:00 GMT+00:00 Rodolfo :Seu computador tem UEFI? Verifica isso também, no meu tive que desabilitar na BIOS um negócio de safe lá.2017-09-03 14:58 GMT-04:00 Luiz Carlos :Ele instala normalmente, mas ele não reconhece as partições.2017-09-03 18:55 GMT+00:00 Rodolfo :Faz isso, remove o grub:# apt-get remove --purge grubdepois# apt-get install grubObs.: Não lembro o nome do pacote do grub.2017-09-03 14:53 GMT-04:00 Luiz Carlos :Estou na live cd sim, saí do chroot e tentei o seguinte comando:mint mint # grub-install --root-directory=/media/linux /dev/sdagrub-probe: error: failed to get canonical path of `/cow'.Installing for i386-pc platform.grub-install.real: error: attempt to install to encrypted disk without cryptodisk enabled. Set `GRUB_ENABLE_CRYPTODISK=1' in file `/etc/default/grub'..Ou seja, deu merda, acho que nem o Windows vai iniciar depois dessa.Em 3 de setembro de 2017 18:46, Rodolfo  escreveu:Você chegou a usar um 

Re: Erro ao recuperar grub de um Debian com LVM Criptografado.

[Linux - Junior Polegato]

Olá!

Antes do chroot, execute mount para ver as partições de sistema, geralmente
são /dev, /dev/pts, /sys, /proc, /run e por aí vai, então monte essas
dentro do seu novo root:

mount -t   

No final, antes do chroot, terá uma réplica das montagens do sistema dentro
do diretório do seu novo root, e também se tiver /home, /var, /boot, /usr e
outros no seu HD, monte-os também no seu novo root nos devidos diretórios,
e agora sim um chroot te coloca no seu sistema de arquivos original.

Execute bash para executar o bash do seu HD e também "su -" para carregar o
usuário root com todas as variáveis de ambiente.

Boa sorte!

[]'s

Junior Polegato

Em 3 de set de 2017 6:47 PM, "Luiz Carlos"  escreveu:

# mount boot
mount: can't find UUID=e7d99f42-7b2a-4afb-9a4a-009003c9f447

Ta foda.

Em 3 de setembro de 2017 21:39, Luiz Carlos  escreveu:

> É computador, aqui eu estou tentando novamente:
> root@mint:/# grub-install /dev/sda
> Installing for i386-pc platform.
> grub-install: error: cannot find a device for /boot/grub (is /dev
> mounted?).
> root@mint:/# mount /dev/sda2 /boot
> mount: /boot: mount failed: Unknown error -1
> root@mint:/# mount /dev/sda2 /boot/
> mount: /boot: mount failed: Unknown error -1
> root@mint:/# mount /dev/sda2 /boot/
> mount: /boot: mount failed: Unknown error -1
> root@mint:/#
> root@mint:/# mount /dev/sda2 /boot/
> mount: /boot: mount failed: Unknown error -1
>
>
> Em 3 de setembro de 2017 21:36, Rodolfo  escreveu:
>
>> Uma pergunta, é computador ou notebook? é novo?
>>
>> Tipo, quando comprei meu notebook pesquisei bem sobre a dificuldade de
>> usar linux nele, porque justamente não queria ter problemas, eu decidi
>> comprar um notebook que fosse compatível com linux(o que na minha opinião
>> nem deveria existir, pra mim qualquer computador/notebook tem que ser
>> compatível com qualquer sistema, na prática parece que isso não acontece).
>> Enfim, dê uma pesquisada sobre isso também.
>>
>> Em 3 de setembro de 2017 17:28, Luiz Carlos  escreveu:
>>
>>> A droga do Seven estava uma merda que tinha vezes que não reconhecia o
>>> mouse e precisava ficar reiniciando toda pra isso resolver, por isso que
>>> tentei instalar o 10.
>>>
>>> Em 3 de setembro de 2017 21:27, Rodolfo  escreveu:
>>>
 Eu uso aqui dual boot windows 7 + debian 9, só tenho windows pra jogar
 alguns jogos, hehehe.

 Em 3 de setembro de 2017 17:25, Luiz Carlos 
 escreveu:

> A real é que a Microsoft é um lixo em fazer esse tipo de prática, pior
> que vou ter que instalar o Linux do zero pra ver se resolve, se não
> detectar o Windows 10, eu vou ter que voltar aquele dual boot com o seven
> como era antes.
> Desativei a hibernação tbm e nada.
>
> Em 3 de setembro de 2017 20:51, Rodolfo  escreveu:
>
>> Isso, eu desativo esse secureboot. Bom, no seu caso você usa LVM,
>> realmente pode ser algo que não conheço.
>>
>> Em 3 de setembro de 2017 16:46, Luiz Carlos 
>> escreveu:
>>
>>> Estou a ponto de desistir, acho que não tem jeito pra essa merda.
>>>
>>> Em 3 de setembro de 2017 20:19, Luiz Carlos 
>>> escreveu:
>>>
 Você fala de secureboot na UEFI né? Eu fui lá,  de "Windows"
 marquei pra Other OS, mas mesmo assim não resolveu.

 Antes disso eu já tentei o boot-repair, eles falam que restauram o
 sistema, mas na pratica instalam um grub sem nada, aqui está o log 
 deles:
 http://paste.ubuntu.com/25460229/

 2017-09-03 19:00 GMT+00:00 Rodolfo :

> Seu computador tem UEFI? Verifica isso também, no meu tive que
> desabilitar na BIOS um negócio de safe lá.
>
> 2017-09-03 14:58 GMT-04:00 Luiz Carlos :
>
>> Ele instala normalmente, mas ele não reconhece as partições.
>>
>> 2017-09-03 18:55 GMT+00:00 Rodolfo :
>>
>>> Faz isso, remove o grub:
>>>
>>> # apt-get remove --purge grub
>>>
>>> depois
>>>
>>> # apt-get install grub
>>>
>>> Obs.: Não lembro o nome do pacote do grub.
>>>
>>> 2017-09-03 14:53 GMT-04:00 Luiz Carlos :
>>>
 Estou na live cd sim, saí do chroot e tentei o seguinte comando:
 mint mint # grub-install --root-directory=/media/linux /dev/sda
 grub-probe: error: failed to get canonical path of `/cow'.
 Installing for i386-pc platform.
 grub-install.real: error: attempt to install to encrypted disk
 without cryptodisk enabled. Set `GRUB_ENABLE_CRYPTODISK=1' in file
 `/etc/default/grub'..

 Ou seja, deu merda, acho que nem o 

Re: network trouble on stretch

[Fungi4All]

> From: ghe2...@gmail.com
> To: debianUsers 
>
> Working on a Dell 5414 laptop, Stretch.
>
> The WiFi works, but the Ethernet doesn"t, and I can"t figure out why.
>
> ip addr:
>
> 1: lo:  mtu 65536 qdisc noqueue state UNKNOWN
> group default qlen 1
> link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
> inet 127.0.0.1/8 scope host lo
> valid_lft forever preferred_lft forever
> inet6 ::1/128 scope host
> valid_lft forever preferred_lft forever
> 2: enp0s31f6:  mtu 1500 qdisc noop state DOWN
> group default qlen 1000
> link/ether 10:05:01:40:f4:43 brd ff:ff:ff:ff:ff:ff
> 3: wwp0s20f0u2i12:  mtu 1500 qdisc noop
> state DOWN group default qlen 1000
> link/ether 4e:8a:3a:22:b3:df brd ff:ff:ff:ff:ff:ff
> 4: wlp1s0:  mtu 1500 qdisc noop state DOWN group
> default qlen 1000
> link/ether f4:8c:50:17:bc:0e brd ff:ff:ff:ff:ff:ff
> 5: enx10050149649d:  mtu 1500 qdisc noop state
> DOWN group default qlen 1000
> link/ether 10:05:01:49:64:9d brd ff:ff:ff:ff:ff:ff
>
> /etc/network/interfaces:
>
> # This file describes the network interfaces available on your system
> # and how to activate them. For more information, see interfaces(5).
>
> source /etc/network/interfaces.d/*
>
> # The loopback network interface
> auto lo
> iface lo inet loopback
>
> auto wwp0s20f0u2i12
> iface wwp0s20f0u2i12 inet static
> address 216.17.134.202/29
> gateway 216.17.134.201
>
> First I tried with wicd, a network manager (the static def wasn"t in 
> interfaces)
>
> It said the wired interface was up, and assigned the requested IP. It
> wasn"t checking after assignment to see if it worked. I turned that
> on, and it never came back.
>
> I removed the network monitor and added the static paragraph to the
> interface file. ifup and ifdown worked, and ip addr said
> wwp0s20f0u2i12 was up.
>
> There are two Ethernet ports on this thing, and I tried both with no
> success. I swapped out the Ethernet cable with the same result.
>
> I replaced Stretch with Buster. It works. dhcp (Comcast) or static (my
> T1). Using the interfaces file.
>
> BTW. ifconfig fans, wait till you get to Buster -- no ifup or down.
> Buster seems to boot using a commented out dhcp paragraph, though.
> Running by hand, "/etc/init.d/network reload" loads the correct
> config.
>
> The "man interfaces" on Stretch talks a lot about the ethn interfaces.
> It does on Buster, too.
>
> This is less than optimal.
>
> What"s going on here? This is Linux, not Winders; Debian, not Ubuntu;
> stable, not Sid. This is what we"re supposed to put on Internet
> servers? They had time to make something as simple as this work while
> it was testing. And to correct the man pages, too.
>
> If they didn"t have time, the release should have been postponed until
> it was ready for prime time, IMHO.
>
> I looked on the "Net, asking why the interface names were changed. I
> found a good reason: sometimes the ethn names aren"t reliably
> consistent. Fine, I say, you"ve figured how to make them consistent.
> That"s no reason to change the names from a meaningful 4 or 5 chars to
> 11, chosen by /dev/urandom.
>
> Somebody"s selling the Debian management a pile of bull excrement.

Before you get a long lecture on the merits of long unique names try this:

Edit your /etc/default/grub change GRUB_CMDLINE_LINUX=”” to :
GRUB_CMDLINE_LINUX="net.ifnames=0" If the biosdevname is installed you need to 
add :
GRUB_CMDLINE_LINUX="net.ifnames=0 biosdevname=0"
$ sudo update-grub
$ sudo reboot

Now check your /dev/interfaces, they should be eth0 and wlan0 and they will stay
this way.

> Glenn English

Cryptsetup - problem when booting the Jessie machine

[roger . tarani]

Hi
I use a Jessie machine since approx oct 2016. 
LVM + cryptsetup (standard options of the Debian installer). 
I've done updates each time it was possible. 
I shut up this machine approx in march-may. When i came to boot in in june, i 
was stuck with cryptsetup :
My passphrase is not ok for cryptsetup. 
«No key available for this passphrase.
cryptsetup: cryptsetup failed, bad password or options?»

I'm 100% sure of my passphrase. 
I've seen on some forums that a Debian update can sometimes lead to this 
situation. 

I've done nothing on that disk. 

i just tried to enter my passphrase assuming the keyboard is qwerty instead of 
azerty I use. Howerver, I'm not sure I coul enter special and accentuated 
characters.  

Is there a way to make visible the characters of my passphrase when typing it?

Thanks for your help

Regards 
Roger 

Re: Xerrada sobre Debian al DLP el 16 de setembre

[Julio Amorós]

Hola Àlex,
segurament no em vaig explicar be.

Si les circumstàncies que es donen són les que tú descrius estic d'acord
amb la teva elecció. És a dir si el que volem és que algú de fora del mon
GNU/Linux comenci amb alguna distro, ja sigui amb la nostra tutorització o
ell tot solet, Ubuntu o Linux Mint em semblen les opcions més naturals. Res
a dir.

Però parlo d'un grup d'usuaris de distribucions linux, on hi ha uns quants
que fan servir Debian, potser la majoria, que seran els instal·ladors i
segurament els encarregats de resoldre els possibles futurs problemes que
hi hagi als ordinadors d'un nou casal/associació.

Els usuaris (no linuxeros) utilitzaran l'escriptori Mate, que no el domino
gaire però que em fa la sensació que varia molt poc d'una distro a una
altra.

Per la meva experiència personal jo escolliria Debian per estabilitat. Però
insisteixo que és la meva experiència.

Si aquest raonament no és compartit llavors l'altra qüestió que em feia ja
no tenen sentit, però serà bo per a mi saber-ho.

En canvi, si és compartit per la majoria, llavors sí que em continuo fent
la mateixa pregunta.

Vagi be
Julio


El dia 2 de setembre de 2017 a les 20:55, Àlex  ha escrit:

> El 30/08/17 a las 22:33, julio escribió:
>
> > Si, ja sé que no existeix una distro única per a tothom (per cert quina
> > documentació tan xula fan els de archlinux) però si algú em digués "ho
> > sento tio, t'has de mullar, quina distro recomanes segons la teva
> > experiència? Només pots dir una."
> > Doncs ja fa temps que sempre penso el mateix: Debian. La seva
> > estabilitat (imagino que per la seva qualitat) no té color.
> > I llavors em pregunto, perquè quan a un casal volem decidir quina distro
> > instal•lar s'acaba instal•lant ubuntu? (Fet real i de fa molt poc temps)
> > I no ho dic com una crítica per haver escollit Ubuntu, ja que al final
> > tots vam estar d'acord.
>
>
> Hola Julio,
>
> treballo amb Debian estable i testing, pero quan algú no informàtic em
> demana d'instalar-li Linux busco una distribució:
>
> * Molt senzilla d'instal.lar, per que se la pugui instal.lar ell/a sol/a.
>
> * Que li reconegui fàcilment el seu hardware.
>
> * Amb un escriptori intuitiu on no es perdi.
>
> Aquesta distribució no és Debian. Debian es una distribució molt bona
> per usuaris iniciats, o per servir de base per crear altres distribucions.
>
> Per usuaris no informàtics actualment els dono una Linux Mint, que a més
> a més del que he dit:
>
> * Està basada en Debian així que jo em sento a gust si haig d'ajudar a
> modificar coses.
>
> * Té el mateix instal.lador que la Ubuntu. S'instal.la amb dos clics.
> L'usuari només ha de conneixer el concepte de partició, com a qualsevol
> instal.lador de qualsevol sistema operatiu.
>
> * Té de base una Ubuntu estable (LTS)
>
> Ja no estem als temps de la Debian Potato amb la que vaig començar.
> Tanmateix, crec que un usuari sense tenir ni idea necessita una guia per
> instal.lar i configurar una Debian. Amb altres distribucions això no passa.
>
> Salut
>
>
> Àlex
>
>


-- 
*“No hay puerta de atrás. Punto final. […] Si hubiera una puerta de atrás,
entonces entiendo que no podría decirlo por que es parte del secretismo, de
las normas que tengo que respetar para no hablar, pero le digo que no hay
puerta de atrás”*
Dorothee Belz, vicepresidenta de *Microsoft*

Re: Erro ao recuperar grub de um Debian com LVM Criptografado.

[Luiz Carlos]

# mount boot
mount: can't find UUID=e7d99f42-7b2a-4afb-9a4a-009003c9f447

Ta foda.

Em 3 de setembro de 2017 21:39, Luiz Carlos  escreveu:

> É computador, aqui eu estou tentando novamente:
> root@mint:/# grub-install /dev/sda
> Installing for i386-pc platform.
> grub-install: error: cannot find a device for /boot/grub (is /dev
> mounted?).
> root@mint:/# mount /dev/sda2 /boot
> mount: /boot: mount failed: Unknown error -1
> root@mint:/# mount /dev/sda2 /boot/
> mount: /boot: mount failed: Unknown error -1
> root@mint:/# mount /dev/sda2 /boot/
> mount: /boot: mount failed: Unknown error -1
> root@mint:/#
> root@mint:/# mount /dev/sda2 /boot/
> mount: /boot: mount failed: Unknown error -1
>
>
> Em 3 de setembro de 2017 21:36, Rodolfo  escreveu:
>
>> Uma pergunta, é computador ou notebook? é novo?
>>
>> Tipo, quando comprei meu notebook pesquisei bem sobre a dificuldade de
>> usar linux nele, porque justamente não queria ter problemas, eu decidi
>> comprar um notebook que fosse compatível com linux(o que na minha opinião
>> nem deveria existir, pra mim qualquer computador/notebook tem que ser
>> compatível com qualquer sistema, na prática parece que isso não acontece).
>> Enfim, dê uma pesquisada sobre isso também.
>>
>> Em 3 de setembro de 2017 17:28, Luiz Carlos  escreveu:
>>
>>> A droga do Seven estava uma merda que tinha vezes que não reconhecia o
>>> mouse e precisava ficar reiniciando toda pra isso resolver, por isso que
>>> tentei instalar o 10.
>>>
>>> Em 3 de setembro de 2017 21:27, Rodolfo  escreveu:
>>>
 Eu uso aqui dual boot windows 7 + debian 9, só tenho windows pra jogar
 alguns jogos, hehehe.

 Em 3 de setembro de 2017 17:25, Luiz Carlos 
 escreveu:

> A real é que a Microsoft é um lixo em fazer esse tipo de prática, pior
> que vou ter que instalar o Linux do zero pra ver se resolve, se não
> detectar o Windows 10, eu vou ter que voltar aquele dual boot com o seven
> como era antes.
> Desativei a hibernação tbm e nada.
>
> Em 3 de setembro de 2017 20:51, Rodolfo  escreveu:
>
>> Isso, eu desativo esse secureboot. Bom, no seu caso você usa LVM,
>> realmente pode ser algo que não conheço.
>>
>> Em 3 de setembro de 2017 16:46, Luiz Carlos 
>> escreveu:
>>
>>> Estou a ponto de desistir, acho que não tem jeito pra essa merda.
>>>
>>> Em 3 de setembro de 2017 20:19, Luiz Carlos 
>>> escreveu:
>>>
 Você fala de secureboot na UEFI né? Eu fui lá,  de "Windows"
 marquei pra Other OS, mas mesmo assim não resolveu.

 Antes disso eu já tentei o boot-repair, eles falam que restauram o
 sistema, mas na pratica instalam um grub sem nada, aqui está o log 
 deles:
 http://paste.ubuntu.com/25460229/

 2017-09-03 19:00 GMT+00:00 Rodolfo :

> Seu computador tem UEFI? Verifica isso também, no meu tive que
> desabilitar na BIOS um negócio de safe lá.
>
> 2017-09-03 14:58 GMT-04:00 Luiz Carlos :
>
>> Ele instala normalmente, mas ele não reconhece as partições.
>>
>> 2017-09-03 18:55 GMT+00:00 Rodolfo :
>>
>>> Faz isso, remove o grub:
>>>
>>> # apt-get remove --purge grub
>>>
>>> depois
>>>
>>> # apt-get install grub
>>>
>>> Obs.: Não lembro o nome do pacote do grub.
>>>
>>> 2017-09-03 14:53 GMT-04:00 Luiz Carlos :
>>>
 Estou na live cd sim, saí do chroot e tentei o seguinte comando:
 mint mint # grub-install --root-directory=/media/linux /dev/sda
 grub-probe: error: failed to get canonical path of `/cow'.
 Installing for i386-pc platform.
 grub-install.real: error: attempt to install to encrypted disk
 without cryptodisk enabled. Set `GRUB_ENABLE_CRYPTODISK=1' in file
 `/etc/default/grub'..

 Ou seja, deu merda, acho que nem o Windows vai iniciar depois
 dessa.

 Em 3 de setembro de 2017 18:46, Rodolfo 
 escreveu:

> Você chegou a usar um live-cd?
>
> Eu tive um problema parecido, entrei pelo live-cd(ou pelo cd
> de instalação do Debian, pois tem uma parte que consigo acessar a
> instalação que tinha pelo terminal) e reinstalei o grub, isso 
> mesmo,
> reinstalei, não fiz nenhum comando, só fiz reinstalar.
>
>
>
> 2017-09-03 14:29 GMT-04:00 Luiz Carlos :
>
>> Eu desabilitei o fastboot do 

Re: Recommended editor for novice programmers?

[Ben Caradoc-Davies]

On 03/09/17 06:21, Tom Browder wrote:

I would especially appreciate other ideas for programming editors for
novice programmers.


I use and recommend geany. And Eclipse.

Kind regards,

--
Ben Caradoc-Davies 
Director
Transient Software Limited 
New Zealand

Re: Install on hp-pavilion-g6-2100 stops at 98%

[Ben Caradoc-Davies]

On 03/09/17 21:07, Luis Speciale wrote:

Le 03/09/2017 à 10:28, Dominique Dumont a écrit :
Assuming disk naming is the same on Mac compared to Debian, you've 
written the
iso image in the first partition (/dev/disk1) instead of writing it to 
the

device (/dev/disk).
I don't know if both name the volumes the same way. Looking at this with 
a command that lists the volumes, I have this

➜  ~ diskutil list
/dev/disk0 (internal, physical):
    #:   TYPE NAME   SIZE   IDENTIFIER
    0:  GUID_partition_scheme    *1.0 TB disk0
    1:    EFI EFI    209.7 MB   disk0s1
    2:  Apple_HFS 999    999.3 GB   disk0s2
    3: Apple_Boot Recovery HD    650.0 MB   disk0s3
/dev/disk1 (external, physical):
    #:   TYPE NAME   SIZE   IDENTIFIER
    0: Apple_partition_scheme    *16.0 GB    disk1
    1:    Apple_partition_map    4.1 KB disk1s1
    2:  Apple_HFS    426.0 KB   disk1s2


That is interesting. macOS is derived from BSD via NeXT and here I 
suspect shows a BSD-like naming convention. The "s" stands for slice.


Kind regards,

--
Ben Caradoc-Davies 
Director
Transient Software Limited 
New Zealand

Re: Erro ao recuperar grub de um Debian com LVM Criptografado.

[Luiz Carlos]

É computador, aqui eu estou tentando novamente:
root@mint:/# grub-install /dev/sda
Installing for i386-pc platform.
grub-install: error: cannot find a device for /boot/grub (is /dev mounted?).
root@mint:/# mount /dev/sda2 /boot
mount: /boot: mount failed: Unknown error -1
root@mint:/# mount /dev/sda2 /boot/
mount: /boot: mount failed: Unknown error -1
root@mint:/# mount /dev/sda2 /boot/
mount: /boot: mount failed: Unknown error -1
root@mint:/#
root@mint:/# mount /dev/sda2 /boot/
mount: /boot: mount failed: Unknown error -1


Em 3 de setembro de 2017 21:36, Rodolfo  escreveu:

> Uma pergunta, é computador ou notebook? é novo?
>
> Tipo, quando comprei meu notebook pesquisei bem sobre a dificuldade de
> usar linux nele, porque justamente não queria ter problemas, eu decidi
> comprar um notebook que fosse compatível com linux(o que na minha opinião
> nem deveria existir, pra mim qualquer computador/notebook tem que ser
> compatível com qualquer sistema, na prática parece que isso não acontece).
> Enfim, dê uma pesquisada sobre isso também.
>
> Em 3 de setembro de 2017 17:28, Luiz Carlos  escreveu:
>
>> A droga do Seven estava uma merda que tinha vezes que não reconhecia o
>> mouse e precisava ficar reiniciando toda pra isso resolver, por isso que
>> tentei instalar o 10.
>>
>> Em 3 de setembro de 2017 21:27, Rodolfo  escreveu:
>>
>>> Eu uso aqui dual boot windows 7 + debian 9, só tenho windows pra jogar
>>> alguns jogos, hehehe.
>>>
>>> Em 3 de setembro de 2017 17:25, Luiz Carlos 
>>> escreveu:
>>>
 A real é que a Microsoft é um lixo em fazer esse tipo de prática, pior
 que vou ter que instalar o Linux do zero pra ver se resolve, se não
 detectar o Windows 10, eu vou ter que voltar aquele dual boot com o seven
 como era antes.
 Desativei a hibernação tbm e nada.

 Em 3 de setembro de 2017 20:51, Rodolfo  escreveu:

> Isso, eu desativo esse secureboot. Bom, no seu caso você usa LVM,
> realmente pode ser algo que não conheço.
>
> Em 3 de setembro de 2017 16:46, Luiz Carlos 
> escreveu:
>
>> Estou a ponto de desistir, acho que não tem jeito pra essa merda.
>>
>> Em 3 de setembro de 2017 20:19, Luiz Carlos 
>> escreveu:
>>
>>> Você fala de secureboot na UEFI né? Eu fui lá,  de "Windows" marquei
>>> pra Other OS, mas mesmo assim não resolveu.
>>>
>>> Antes disso eu já tentei o boot-repair, eles falam que restauram o
>>> sistema, mas na pratica instalam um grub sem nada, aqui está o log 
>>> deles:
>>> http://paste.ubuntu.com/25460229/
>>>
>>> 2017-09-03 19:00 GMT+00:00 Rodolfo :
>>>
 Seu computador tem UEFI? Verifica isso também, no meu tive que
 desabilitar na BIOS um negócio de safe lá.

 2017-09-03 14:58 GMT-04:00 Luiz Carlos :

> Ele instala normalmente, mas ele não reconhece as partições.
>
> 2017-09-03 18:55 GMT+00:00 Rodolfo :
>
>> Faz isso, remove o grub:
>>
>> # apt-get remove --purge grub
>>
>> depois
>>
>> # apt-get install grub
>>
>> Obs.: Não lembro o nome do pacote do grub.
>>
>> 2017-09-03 14:53 GMT-04:00 Luiz Carlos :
>>
>>> Estou na live cd sim, saí do chroot e tentei o seguinte comando:
>>> mint mint # grub-install --root-directory=/media/linux /dev/sda
>>> grub-probe: error: failed to get canonical path of `/cow'.
>>> Installing for i386-pc platform.
>>> grub-install.real: error: attempt to install to encrypted disk
>>> without cryptodisk enabled. Set `GRUB_ENABLE_CRYPTODISK=1' in file
>>> `/etc/default/grub'..
>>>
>>> Ou seja, deu merda, acho que nem o Windows vai iniciar depois
>>> dessa.
>>>
>>> Em 3 de setembro de 2017 18:46, Rodolfo 
>>> escreveu:
>>>
 Você chegou a usar um live-cd?

 Eu tive um problema parecido, entrei pelo live-cd(ou pelo cd de
 instalação do Debian, pois tem uma parte que consigo acessar a 
 instalação
 que tinha pelo terminal) e reinstalei o grub, isso mesmo, 
 reinstalei, não
 fiz nenhum comando, só fiz reinstalar.



 2017-09-03 14:29 GMT-04:00 Luiz Carlos :

> Eu desabilitei o fastboot do windows 10, mas mando esses
> comandos e simplesmente dá erro:
> mint@mint ~ $ sudo su
> mint mint # modprobe dm-crypt
> mint mint # cryptsetup luksOpen /dev/sda5 linux
> Enter passphrase for /dev/sda5:
> mint 

Re: Erro ao recuperar grub de um Debian com LVM Criptografado.

[Rodolfo]

Uma pergunta, é computador ou notebook? é novo?

Tipo, quando comprei meu notebook pesquisei bem sobre a dificuldade de usar
linux nele, porque justamente não queria ter problemas, eu decidi comprar
um notebook que fosse compatível com linux(o que na minha opinião nem
deveria existir, pra mim qualquer computador/notebook tem que ser
compatível com qualquer sistema, na prática parece que isso não acontece).
Enfim, dê uma pesquisada sobre isso também.

Em 3 de setembro de 2017 17:28, Luiz Carlos  escreveu:

> A droga do Seven estava uma merda que tinha vezes que não reconhecia o
> mouse e precisava ficar reiniciando toda pra isso resolver, por isso que
> tentei instalar o 10.
>
> Em 3 de setembro de 2017 21:27, Rodolfo  escreveu:
>
>> Eu uso aqui dual boot windows 7 + debian 9, só tenho windows pra jogar
>> alguns jogos, hehehe.
>>
>> Em 3 de setembro de 2017 17:25, Luiz Carlos  escreveu:
>>
>>> A real é que a Microsoft é um lixo em fazer esse tipo de prática, pior
>>> que vou ter que instalar o Linux do zero pra ver se resolve, se não
>>> detectar o Windows 10, eu vou ter que voltar aquele dual boot com o seven
>>> como era antes.
>>> Desativei a hibernação tbm e nada.
>>>
>>> Em 3 de setembro de 2017 20:51, Rodolfo  escreveu:
>>>
 Isso, eu desativo esse secureboot. Bom, no seu caso você usa LVM,
 realmente pode ser algo que não conheço.

 Em 3 de setembro de 2017 16:46, Luiz Carlos 
 escreveu:

> Estou a ponto de desistir, acho que não tem jeito pra essa merda.
>
> Em 3 de setembro de 2017 20:19, Luiz Carlos 
> escreveu:
>
>> Você fala de secureboot na UEFI né? Eu fui lá,  de "Windows" marquei
>> pra Other OS, mas mesmo assim não resolveu.
>>
>> Antes disso eu já tentei o boot-repair, eles falam que restauram o
>> sistema, mas na pratica instalam um grub sem nada, aqui está o log deles:
>> http://paste.ubuntu.com/25460229/
>>
>> 2017-09-03 19:00 GMT+00:00 Rodolfo :
>>
>>> Seu computador tem UEFI? Verifica isso também, no meu tive que
>>> desabilitar na BIOS um negócio de safe lá.
>>>
>>> 2017-09-03 14:58 GMT-04:00 Luiz Carlos :
>>>
 Ele instala normalmente, mas ele não reconhece as partições.

 2017-09-03 18:55 GMT+00:00 Rodolfo :

> Faz isso, remove o grub:
>
> # apt-get remove --purge grub
>
> depois
>
> # apt-get install grub
>
> Obs.: Não lembro o nome do pacote do grub.
>
> 2017-09-03 14:53 GMT-04:00 Luiz Carlos :
>
>> Estou na live cd sim, saí do chroot e tentei o seguinte comando:
>> mint mint # grub-install --root-directory=/media/linux /dev/sda
>> grub-probe: error: failed to get canonical path of `/cow'.
>> Installing for i386-pc platform.
>> grub-install.real: error: attempt to install to encrypted disk
>> without cryptodisk enabled. Set `GRUB_ENABLE_CRYPTODISK=1' in file
>> `/etc/default/grub'..
>>
>> Ou seja, deu merda, acho que nem o Windows vai iniciar depois
>> dessa.
>>
>> Em 3 de setembro de 2017 18:46, Rodolfo 
>> escreveu:
>>
>>> Você chegou a usar um live-cd?
>>>
>>> Eu tive um problema parecido, entrei pelo live-cd(ou pelo cd de
>>> instalação do Debian, pois tem uma parte que consigo acessar a 
>>> instalação
>>> que tinha pelo terminal) e reinstalei o grub, isso mesmo, 
>>> reinstalei, não
>>> fiz nenhum comando, só fiz reinstalar.
>>>
>>>
>>>
>>> 2017-09-03 14:29 GMT-04:00 Luiz Carlos :
>>>
 Eu desabilitei o fastboot do windows 10, mas mando esses
 comandos e simplesmente dá erro:
 mint@mint ~ $ sudo su
 mint mint # modprobe dm-crypt
 mint mint # cryptsetup luksOpen /dev/sda5 linux
 Enter passphrase for /dev/sda5:
 mint mint # mkdir /media/linux
 mint mint # mount /dev/lvmc/root /media/linux/
 mint mint # chroot /media/linux /bin/bash
 root@mint:/# mount /dev/sda2 /boot
 mount: /boot: mount failed: Unknown error -1

 Se não consigo montar a droga da /boot não vou conseguir
 instalar o grub.

 2017-09-03 17:53 GMT+00:00 Rodolfo :

> Tentou bootar via live-cd?
>
> 2017-09-03 12:17 GMT-04:00 Luiz Carlos :
>
>> Que desgraça de vida, horas no google pesquisando e não
>> consigo resolver porra nenhuma, maldita 

Re: Erro ao recuperar grub de um Debian com LVM Criptografado.

[Luiz Carlos]

A droga do Seven estava uma merda que tinha vezes que não reconhecia o
mouse e precisava ficar reiniciando toda pra isso resolver, por isso que
tentei instalar o 10.

Em 3 de setembro de 2017 21:27, Rodolfo  escreveu:

> Eu uso aqui dual boot windows 7 + debian 9, só tenho windows pra jogar
> alguns jogos, hehehe.
>
> Em 3 de setembro de 2017 17:25, Luiz Carlos  escreveu:
>
>> A real é que a Microsoft é um lixo em fazer esse tipo de prática, pior
>> que vou ter que instalar o Linux do zero pra ver se resolve, se não
>> detectar o Windows 10, eu vou ter que voltar aquele dual boot com o seven
>> como era antes.
>> Desativei a hibernação tbm e nada.
>>
>> Em 3 de setembro de 2017 20:51, Rodolfo  escreveu:
>>
>>> Isso, eu desativo esse secureboot. Bom, no seu caso você usa LVM,
>>> realmente pode ser algo que não conheço.
>>>
>>> Em 3 de setembro de 2017 16:46, Luiz Carlos 
>>> escreveu:
>>>
 Estou a ponto de desistir, acho que não tem jeito pra essa merda.

 Em 3 de setembro de 2017 20:19, Luiz Carlos 
 escreveu:

> Você fala de secureboot na UEFI né? Eu fui lá,  de "Windows" marquei
> pra Other OS, mas mesmo assim não resolveu.
>
> Antes disso eu já tentei o boot-repair, eles falam que restauram o
> sistema, mas na pratica instalam um grub sem nada, aqui está o log deles:
> http://paste.ubuntu.com/25460229/
>
> 2017-09-03 19:00 GMT+00:00 Rodolfo :
>
>> Seu computador tem UEFI? Verifica isso também, no meu tive que
>> desabilitar na BIOS um negócio de safe lá.
>>
>> 2017-09-03 14:58 GMT-04:00 Luiz Carlos :
>>
>>> Ele instala normalmente, mas ele não reconhece as partições.
>>>
>>> 2017-09-03 18:55 GMT+00:00 Rodolfo :
>>>
 Faz isso, remove o grub:

 # apt-get remove --purge grub

 depois

 # apt-get install grub

 Obs.: Não lembro o nome do pacote do grub.

 2017-09-03 14:53 GMT-04:00 Luiz Carlos :

> Estou na live cd sim, saí do chroot e tentei o seguinte comando:
> mint mint # grub-install --root-directory=/media/linux /dev/sda
> grub-probe: error: failed to get canonical path of `/cow'.
> Installing for i386-pc platform.
> grub-install.real: error: attempt to install to encrypted disk
> without cryptodisk enabled. Set `GRUB_ENABLE_CRYPTODISK=1' in file
> `/etc/default/grub'..
>
> Ou seja, deu merda, acho que nem o Windows vai iniciar depois
> dessa.
>
> Em 3 de setembro de 2017 18:46, Rodolfo 
> escreveu:
>
>> Você chegou a usar um live-cd?
>>
>> Eu tive um problema parecido, entrei pelo live-cd(ou pelo cd de
>> instalação do Debian, pois tem uma parte que consigo acessar a 
>> instalação
>> que tinha pelo terminal) e reinstalei o grub, isso mesmo, 
>> reinstalei, não
>> fiz nenhum comando, só fiz reinstalar.
>>
>>
>>
>> 2017-09-03 14:29 GMT-04:00 Luiz Carlos :
>>
>>> Eu desabilitei o fastboot do windows 10, mas mando esses
>>> comandos e simplesmente dá erro:
>>> mint@mint ~ $ sudo su
>>> mint mint # modprobe dm-crypt
>>> mint mint # cryptsetup luksOpen /dev/sda5 linux
>>> Enter passphrase for /dev/sda5:
>>> mint mint # mkdir /media/linux
>>> mint mint # mount /dev/lvmc/root /media/linux/
>>> mint mint # chroot /media/linux /bin/bash
>>> root@mint:/# mount /dev/sda2 /boot
>>> mount: /boot: mount failed: Unknown error -1
>>>
>>> Se não consigo montar a droga da /boot não vou conseguir
>>> instalar o grub.
>>>
>>> 2017-09-03 17:53 GMT+00:00 Rodolfo :
>>>
 Tentou bootar via live-cd?

 2017-09-03 12:17 GMT-04:00 Luiz Carlos :

> Que desgraça de vida, horas no google pesquisando e não
> consigo resolver porra nenhuma, maldita hora que fui inventar de 
> instalar
> Windows 10 e achar que ia conseguir recuperar o Grub.
>
> 2017-09-03 14:19 GMT+00:00 Luiz Carlos :
>
>> Estou até agora tentando, tentei o comando:
>> # grub-install --boot-directory=/boot /dev/sda
>> Installing for i386-pc platform.
>> grub-install.real: warning: Sector 32 is already in use by
>> the program `FlexNet'; avoiding it.  This software may cause 
>> boot or other
>> problems in future.  Please ask its authors not to store data in 

Re: Erro ao recuperar grub de um Debian com LVM Criptografado.

[Rodolfo]

Eu uso aqui dual boot windows 7 + debian 9, só tenho windows pra jogar
alguns jogos, hehehe.

Em 3 de setembro de 2017 17:25, Luiz Carlos  escreveu:

> A real é que a Microsoft é um lixo em fazer esse tipo de prática, pior que
> vou ter que instalar o Linux do zero pra ver se resolve, se não detectar o
> Windows 10, eu vou ter que voltar aquele dual boot com o seven como era
> antes.
> Desativei a hibernação tbm e nada.
>
> Em 3 de setembro de 2017 20:51, Rodolfo  escreveu:
>
>> Isso, eu desativo esse secureboot. Bom, no seu caso você usa LVM,
>> realmente pode ser algo que não conheço.
>>
>> Em 3 de setembro de 2017 16:46, Luiz Carlos  escreveu:
>>
>>> Estou a ponto de desistir, acho que não tem jeito pra essa merda.
>>>
>>> Em 3 de setembro de 2017 20:19, Luiz Carlos 
>>> escreveu:
>>>
 Você fala de secureboot na UEFI né? Eu fui lá,  de "Windows" marquei
 pra Other OS, mas mesmo assim não resolveu.

 Antes disso eu já tentei o boot-repair, eles falam que restauram o
 sistema, mas na pratica instalam um grub sem nada, aqui está o log deles:
 http://paste.ubuntu.com/25460229/

 2017-09-03 19:00 GMT+00:00 Rodolfo :

> Seu computador tem UEFI? Verifica isso também, no meu tive que
> desabilitar na BIOS um negócio de safe lá.
>
> 2017-09-03 14:58 GMT-04:00 Luiz Carlos :
>
>> Ele instala normalmente, mas ele não reconhece as partições.
>>
>> 2017-09-03 18:55 GMT+00:00 Rodolfo :
>>
>>> Faz isso, remove o grub:
>>>
>>> # apt-get remove --purge grub
>>>
>>> depois
>>>
>>> # apt-get install grub
>>>
>>> Obs.: Não lembro o nome do pacote do grub.
>>>
>>> 2017-09-03 14:53 GMT-04:00 Luiz Carlos :
>>>
 Estou na live cd sim, saí do chroot e tentei o seguinte comando:
 mint mint # grub-install --root-directory=/media/linux /dev/sda
 grub-probe: error: failed to get canonical path of `/cow'.
 Installing for i386-pc platform.
 grub-install.real: error: attempt to install to encrypted disk
 without cryptodisk enabled. Set `GRUB_ENABLE_CRYPTODISK=1' in file
 `/etc/default/grub'..

 Ou seja, deu merda, acho que nem o Windows vai iniciar depois dessa.

 Em 3 de setembro de 2017 18:46, Rodolfo 
 escreveu:

> Você chegou a usar um live-cd?
>
> Eu tive um problema parecido, entrei pelo live-cd(ou pelo cd de
> instalação do Debian, pois tem uma parte que consigo acessar a 
> instalação
> que tinha pelo terminal) e reinstalei o grub, isso mesmo, reinstalei, 
> não
> fiz nenhum comando, só fiz reinstalar.
>
>
>
> 2017-09-03 14:29 GMT-04:00 Luiz Carlos :
>
>> Eu desabilitei o fastboot do windows 10, mas mando esses comandos
>> e simplesmente dá erro:
>> mint@mint ~ $ sudo su
>> mint mint # modprobe dm-crypt
>> mint mint # cryptsetup luksOpen /dev/sda5 linux
>> Enter passphrase for /dev/sda5:
>> mint mint # mkdir /media/linux
>> mint mint # mount /dev/lvmc/root /media/linux/
>> mint mint # chroot /media/linux /bin/bash
>> root@mint:/# mount /dev/sda2 /boot
>> mount: /boot: mount failed: Unknown error -1
>>
>> Se não consigo montar a droga da /boot não vou conseguir instalar
>> o grub.
>>
>> 2017-09-03 17:53 GMT+00:00 Rodolfo :
>>
>>> Tentou bootar via live-cd?
>>>
>>> 2017-09-03 12:17 GMT-04:00 Luiz Carlos :
>>>
 Que desgraça de vida, horas no google pesquisando e não consigo
 resolver porra nenhuma, maldita hora que fui inventar de instalar 
 Windows
 10 e achar que ia conseguir recuperar o Grub.

 2017-09-03 14:19 GMT+00:00 Luiz Carlos :

> Estou até agora tentando, tentei o comando:
> # grub-install --boot-directory=/boot /dev/sda
> Installing for i386-pc platform.
> grub-install.real: warning: Sector 32 is already in use by the
> program `FlexNet'; avoiding it.  This software may cause boot or 
> other
> problems in future.  Please ask its authors not to store data in 
> the boot
> track.
> Installation finished. No error reported.
> mint mint # grub-install --boot-directory=/boot /dev/sda2
> Installing for i386-pc platform.
> grub-install.real: warning: File system `ntfs' doesn't support
> embedding.
> grub-install.real: warning: 

Re: Erro ao recuperar grub de um Debian com LVM Criptografado.

[Luiz Carlos]

A real é que a Microsoft é um lixo em fazer esse tipo de prática, pior que
vou ter que instalar o Linux do zero pra ver se resolve, se não detectar o
Windows 10, eu vou ter que voltar aquele dual boot com o seven como era
antes.
Desativei a hibernação tbm e nada.

Em 3 de setembro de 2017 20:51, Rodolfo  escreveu:

> Isso, eu desativo esse secureboot. Bom, no seu caso você usa LVM,
> realmente pode ser algo que não conheço.
>
> Em 3 de setembro de 2017 16:46, Luiz Carlos  escreveu:
>
>> Estou a ponto de desistir, acho que não tem jeito pra essa merda.
>>
>> Em 3 de setembro de 2017 20:19, Luiz Carlos  escreveu:
>>
>>> Você fala de secureboot na UEFI né? Eu fui lá,  de "Windows" marquei pra
>>> Other OS, mas mesmo assim não resolveu.
>>>
>>> Antes disso eu já tentei o boot-repair, eles falam que restauram o
>>> sistema, mas na pratica instalam um grub sem nada, aqui está o log deles:
>>> http://paste.ubuntu.com/25460229/
>>>
>>> 2017-09-03 19:00 GMT+00:00 Rodolfo :
>>>
 Seu computador tem UEFI? Verifica isso também, no meu tive que
 desabilitar na BIOS um negócio de safe lá.

 2017-09-03 14:58 GMT-04:00 Luiz Carlos :

> Ele instala normalmente, mas ele não reconhece as partições.
>
> 2017-09-03 18:55 GMT+00:00 Rodolfo :
>
>> Faz isso, remove o grub:
>>
>> # apt-get remove --purge grub
>>
>> depois
>>
>> # apt-get install grub
>>
>> Obs.: Não lembro o nome do pacote do grub.
>>
>> 2017-09-03 14:53 GMT-04:00 Luiz Carlos :
>>
>>> Estou na live cd sim, saí do chroot e tentei o seguinte comando:
>>> mint mint # grub-install --root-directory=/media/linux /dev/sda
>>> grub-probe: error: failed to get canonical path of `/cow'.
>>> Installing for i386-pc platform.
>>> grub-install.real: error: attempt to install to encrypted disk
>>> without cryptodisk enabled. Set `GRUB_ENABLE_CRYPTODISK=1' in file
>>> `/etc/default/grub'..
>>>
>>> Ou seja, deu merda, acho que nem o Windows vai iniciar depois dessa.
>>>
>>> Em 3 de setembro de 2017 18:46, Rodolfo 
>>> escreveu:
>>>
 Você chegou a usar um live-cd?

 Eu tive um problema parecido, entrei pelo live-cd(ou pelo cd de
 instalação do Debian, pois tem uma parte que consigo acessar a 
 instalação
 que tinha pelo terminal) e reinstalei o grub, isso mesmo, reinstalei, 
 não
 fiz nenhum comando, só fiz reinstalar.



 2017-09-03 14:29 GMT-04:00 Luiz Carlos :

> Eu desabilitei o fastboot do windows 10, mas mando esses comandos
> e simplesmente dá erro:
> mint@mint ~ $ sudo su
> mint mint # modprobe dm-crypt
> mint mint # cryptsetup luksOpen /dev/sda5 linux
> Enter passphrase for /dev/sda5:
> mint mint # mkdir /media/linux
> mint mint # mount /dev/lvmc/root /media/linux/
> mint mint # chroot /media/linux /bin/bash
> root@mint:/# mount /dev/sda2 /boot
> mount: /boot: mount failed: Unknown error -1
>
> Se não consigo montar a droga da /boot não vou conseguir instalar
> o grub.
>
> 2017-09-03 17:53 GMT+00:00 Rodolfo :
>
>> Tentou bootar via live-cd?
>>
>> 2017-09-03 12:17 GMT-04:00 Luiz Carlos :
>>
>>> Que desgraça de vida, horas no google pesquisando e não consigo
>>> resolver porra nenhuma, maldita hora que fui inventar de instalar 
>>> Windows
>>> 10 e achar que ia conseguir recuperar o Grub.
>>>
>>> 2017-09-03 14:19 GMT+00:00 Luiz Carlos :
>>>
 Estou até agora tentando, tentei o comando:
 # grub-install --boot-directory=/boot /dev/sda
 Installing for i386-pc platform.
 grub-install.real: warning: Sector 32 is already in use by the
 program `FlexNet'; avoiding it.  This software may cause boot or 
 other
 problems in future.  Please ask its authors not to store data in 
 the boot
 track.
 Installation finished. No error reported.
 mint mint # grub-install --boot-directory=/boot /dev/sda2
 Installing for i386-pc platform.
 grub-install.real: warning: File system `ntfs' doesn't support
 embedding.
 grub-install.real: 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..
 grub-install.real: error: will not proceed with blocklists.


 Em 3 

Re: Erro ao recuperar grub de um Debian com LVM Criptografado.

[Rodolfo]

Isso, eu desativo esse secureboot. Bom, no seu caso você usa LVM, realmente
pode ser algo que não conheço.

Em 3 de setembro de 2017 16:46, Luiz Carlos  escreveu:

> Estou a ponto de desistir, acho que não tem jeito pra essa merda.
>
> Em 3 de setembro de 2017 20:19, Luiz Carlos  escreveu:
>
>> Você fala de secureboot na UEFI né? Eu fui lá,  de "Windows" marquei pra
>> Other OS, mas mesmo assim não resolveu.
>>
>> Antes disso eu já tentei o boot-repair, eles falam que restauram o
>> sistema, mas na pratica instalam um grub sem nada, aqui está o log deles:
>> http://paste.ubuntu.com/25460229/
>>
>> 2017-09-03 19:00 GMT+00:00 Rodolfo :
>>
>>> Seu computador tem UEFI? Verifica isso também, no meu tive que
>>> desabilitar na BIOS um negócio de safe lá.
>>>
>>> 2017-09-03 14:58 GMT-04:00 Luiz Carlos :
>>>
 Ele instala normalmente, mas ele não reconhece as partições.

 2017-09-03 18:55 GMT+00:00 Rodolfo :

> Faz isso, remove o grub:
>
> # apt-get remove --purge grub
>
> depois
>
> # apt-get install grub
>
> Obs.: Não lembro o nome do pacote do grub.
>
> 2017-09-03 14:53 GMT-04:00 Luiz Carlos :
>
>> Estou na live cd sim, saí do chroot e tentei o seguinte comando:
>> mint mint # grub-install --root-directory=/media/linux /dev/sda
>> grub-probe: error: failed to get canonical path of `/cow'.
>> Installing for i386-pc platform.
>> grub-install.real: error: attempt to install to encrypted disk
>> without cryptodisk enabled. Set `GRUB_ENABLE_CRYPTODISK=1' in file
>> `/etc/default/grub'..
>>
>> Ou seja, deu merda, acho que nem o Windows vai iniciar depois dessa.
>>
>> Em 3 de setembro de 2017 18:46, Rodolfo 
>> escreveu:
>>
>>> Você chegou a usar um live-cd?
>>>
>>> Eu tive um problema parecido, entrei pelo live-cd(ou pelo cd de
>>> instalação do Debian, pois tem uma parte que consigo acessar a 
>>> instalação
>>> que tinha pelo terminal) e reinstalei o grub, isso mesmo, reinstalei, 
>>> não
>>> fiz nenhum comando, só fiz reinstalar.
>>>
>>>
>>>
>>> 2017-09-03 14:29 GMT-04:00 Luiz Carlos :
>>>
 Eu desabilitei o fastboot do windows 10, mas mando esses comandos e
 simplesmente dá erro:
 mint@mint ~ $ sudo su
 mint mint # modprobe dm-crypt
 mint mint # cryptsetup luksOpen /dev/sda5 linux
 Enter passphrase for /dev/sda5:
 mint mint # mkdir /media/linux
 mint mint # mount /dev/lvmc/root /media/linux/
 mint mint # chroot /media/linux /bin/bash
 root@mint:/# mount /dev/sda2 /boot
 mount: /boot: mount failed: Unknown error -1

 Se não consigo montar a droga da /boot não vou conseguir instalar o
 grub.

 2017-09-03 17:53 GMT+00:00 Rodolfo :

> Tentou bootar via live-cd?
>
> 2017-09-03 12:17 GMT-04:00 Luiz Carlos :
>
>> Que desgraça de vida, horas no google pesquisando e não consigo
>> resolver porra nenhuma, maldita hora que fui inventar de instalar 
>> Windows
>> 10 e achar que ia conseguir recuperar o Grub.
>>
>> 2017-09-03 14:19 GMT+00:00 Luiz Carlos :
>>
>>> Estou até agora tentando, tentei o comando:
>>> # grub-install --boot-directory=/boot /dev/sda
>>> Installing for i386-pc platform.
>>> grub-install.real: warning: Sector 32 is already in use by the
>>> program `FlexNet'; avoiding it.  This software may cause boot or 
>>> other
>>> problems in future.  Please ask its authors not to store data in 
>>> the boot
>>> track.
>>> Installation finished. No error reported.
>>> mint mint # grub-install --boot-directory=/boot /dev/sda2
>>> Installing for i386-pc platform.
>>> grub-install.real: warning: File system `ntfs' doesn't support
>>> embedding.
>>> grub-install.real: 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..
>>> grub-install.real: error: will not proceed with blocklists.
>>>
>>>
>>> Em 3 de setembro de 2017 06:03, Luiz Carlos 
>>> escreveu:
>>>
 Olá amigos, estou em desespero, agora mesmo estou numa live cd
 tentando recuperar o grub, eu havia instalado o WIndows 10, estou 
 com o
 Debian criptografado, tentei recuperar com esses seguintes 
 comandos:


 # modprobe dm-crypt
 # 

Re: Erro ao recuperar grub de um Debian com LVM Criptografado.

[Luiz Carlos]

Estou a ponto de desistir, acho que não tem jeito pra essa merda.

Em 3 de setembro de 2017 20:19, Luiz Carlos  escreveu:

> Você fala de secureboot na UEFI né? Eu fui lá,  de "Windows" marquei pra
> Other OS, mas mesmo assim não resolveu.
>
> Antes disso eu já tentei o boot-repair, eles falam que restauram o
> sistema, mas na pratica instalam um grub sem nada, aqui está o log deles:
> http://paste.ubuntu.com/25460229/
>
> 2017-09-03 19:00 GMT+00:00 Rodolfo :
>
>> Seu computador tem UEFI? Verifica isso também, no meu tive que
>> desabilitar na BIOS um negócio de safe lá.
>>
>> 2017-09-03 14:58 GMT-04:00 Luiz Carlos :
>>
>>> Ele instala normalmente, mas ele não reconhece as partições.
>>>
>>> 2017-09-03 18:55 GMT+00:00 Rodolfo :
>>>
 Faz isso, remove o grub:

 # apt-get remove --purge grub

 depois

 # apt-get install grub

 Obs.: Não lembro o nome do pacote do grub.

 2017-09-03 14:53 GMT-04:00 Luiz Carlos :

> Estou na live cd sim, saí do chroot e tentei o seguinte comando:
> mint mint # grub-install --root-directory=/media/linux /dev/sda
> grub-probe: error: failed to get canonical path of `/cow'.
> Installing for i386-pc platform.
> grub-install.real: error: attempt to install to encrypted disk without
> cryptodisk enabled. Set `GRUB_ENABLE_CRYPTODISK=1' in file
> `/etc/default/grub'..
>
> Ou seja, deu merda, acho que nem o Windows vai iniciar depois dessa.
>
> Em 3 de setembro de 2017 18:46, Rodolfo  escreveu:
>
>> Você chegou a usar um live-cd?
>>
>> Eu tive um problema parecido, entrei pelo live-cd(ou pelo cd de
>> instalação do Debian, pois tem uma parte que consigo acessar a instalação
>> que tinha pelo terminal) e reinstalei o grub, isso mesmo, reinstalei, não
>> fiz nenhum comando, só fiz reinstalar.
>>
>>
>>
>> 2017-09-03 14:29 GMT-04:00 Luiz Carlos :
>>
>>> Eu desabilitei o fastboot do windows 10, mas mando esses comandos e
>>> simplesmente dá erro:
>>> mint@mint ~ $ sudo su
>>> mint mint # modprobe dm-crypt
>>> mint mint # cryptsetup luksOpen /dev/sda5 linux
>>> Enter passphrase for /dev/sda5:
>>> mint mint # mkdir /media/linux
>>> mint mint # mount /dev/lvmc/root /media/linux/
>>> mint mint # chroot /media/linux /bin/bash
>>> root@mint:/# mount /dev/sda2 /boot
>>> mount: /boot: mount failed: Unknown error -1
>>>
>>> Se não consigo montar a droga da /boot não vou conseguir instalar o
>>> grub.
>>>
>>> 2017-09-03 17:53 GMT+00:00 Rodolfo :
>>>
 Tentou bootar via live-cd?

 2017-09-03 12:17 GMT-04:00 Luiz Carlos :

> Que desgraça de vida, horas no google pesquisando e não consigo
> resolver porra nenhuma, maldita hora que fui inventar de instalar 
> Windows
> 10 e achar que ia conseguir recuperar o Grub.
>
> 2017-09-03 14:19 GMT+00:00 Luiz Carlos :
>
>> Estou até agora tentando, tentei o comando:
>> # grub-install --boot-directory=/boot /dev/sda
>> Installing for i386-pc platform.
>> grub-install.real: warning: Sector 32 is already in use by the
>> program `FlexNet'; avoiding it.  This software may cause boot or 
>> other
>> problems in future.  Please ask its authors not to store data in the 
>> boot
>> track.
>> Installation finished. No error reported.
>> mint mint # grub-install --boot-directory=/boot /dev/sda2
>> Installing for i386-pc platform.
>> grub-install.real: warning: File system `ntfs' doesn't support
>> embedding.
>> grub-install.real: 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..
>> grub-install.real: error: will not proceed with blocklists.
>>
>>
>> Em 3 de setembro de 2017 06:03, Luiz Carlos 
>> escreveu:
>>
>>> Olá amigos, estou em desespero, agora mesmo estou numa live cd
>>> tentando recuperar o grub, eu havia instalado o WIndows 10, estou 
>>> com o
>>> Debian criptografado, tentei recuperar com esses seguintes comandos:
>>>
>>>
>>> # modprobe dm-crypt
>>> # cryptsetup luksOpen /dev/sda5 linux
>>> # mkdir /media/linux
>>> # mount /dev/lvmc/root /media/linux/
>>> # chroot /media/linux /bin/bash
>>>
>>> Dai quando mando # grub-install /dev/sda
>>>
>>> Aparece: /dev/sda: Not found or not a block device.
>>>
>>>
>>> Eu 

Re: Laptop recommendation

[Sam Kuper]

Jonas Hedman  wrote:
> I'm on the hunt for a newish laptop on which I naturally want
> to run Debian.

Minifree, Vikings, and Technoethical all offer Respects Your Freedom
certified laptops:
https://www.fsf.org/resources/hw/endorsement/respects-your-freedom

These should all run Debian perfectly, avoiding the headaches of
proprietary drivers. Those supplied by Minifree (maybe the others,
too?) ship with a libre BIOS replacement as well, and perhaps even
with the Management Engine neutralised, leaving you as completely in
control of all aspects of your PC as is currently possible with the
x86-64 architecture.

Re: Erro ao recuperar grub de um Debian com LVM Criptografado.

[Luiz Carlos]

Você fala de secureboot na UEFI né? Eu fui lá,  de "Windows" marquei pra
Other OS, mas mesmo assim não resolveu.

Antes disso eu já tentei o boot-repair, eles falam que restauram o sistema,
mas na pratica instalam um grub sem nada, aqui está o log deles:
http://paste.ubuntu.com/25460229/

2017-09-03 19:00 GMT+00:00 Rodolfo :

> Seu computador tem UEFI? Verifica isso também, no meu tive que desabilitar
> na BIOS um negócio de safe lá.
>
> 2017-09-03 14:58 GMT-04:00 Luiz Carlos :
>
>> Ele instala normalmente, mas ele não reconhece as partições.
>>
>> 2017-09-03 18:55 GMT+00:00 Rodolfo :
>>
>>> Faz isso, remove o grub:
>>>
>>> # apt-get remove --purge grub
>>>
>>> depois
>>>
>>> # apt-get install grub
>>>
>>> Obs.: Não lembro o nome do pacote do grub.
>>>
>>> 2017-09-03 14:53 GMT-04:00 Luiz Carlos :
>>>
 Estou na live cd sim, saí do chroot e tentei o seguinte comando:
 mint mint # grub-install --root-directory=/media/linux /dev/sda
 grub-probe: error: failed to get canonical path of `/cow'.
 Installing for i386-pc platform.
 grub-install.real: error: attempt to install to encrypted disk without
 cryptodisk enabled. Set `GRUB_ENABLE_CRYPTODISK=1' in file
 `/etc/default/grub'..

 Ou seja, deu merda, acho que nem o Windows vai iniciar depois dessa.

 Em 3 de setembro de 2017 18:46, Rodolfo  escreveu:

> Você chegou a usar um live-cd?
>
> Eu tive um problema parecido, entrei pelo live-cd(ou pelo cd de
> instalação do Debian, pois tem uma parte que consigo acessar a instalação
> que tinha pelo terminal) e reinstalei o grub, isso mesmo, reinstalei, não
> fiz nenhum comando, só fiz reinstalar.
>
>
>
> 2017-09-03 14:29 GMT-04:00 Luiz Carlos :
>
>> Eu desabilitei o fastboot do windows 10, mas mando esses comandos e
>> simplesmente dá erro:
>> mint@mint ~ $ sudo su
>> mint mint # modprobe dm-crypt
>> mint mint # cryptsetup luksOpen /dev/sda5 linux
>> Enter passphrase for /dev/sda5:
>> mint mint # mkdir /media/linux
>> mint mint # mount /dev/lvmc/root /media/linux/
>> mint mint # chroot /media/linux /bin/bash
>> root@mint:/# mount /dev/sda2 /boot
>> mount: /boot: mount failed: Unknown error -1
>>
>> Se não consigo montar a droga da /boot não vou conseguir instalar o
>> grub.
>>
>> 2017-09-03 17:53 GMT+00:00 Rodolfo :
>>
>>> Tentou bootar via live-cd?
>>>
>>> 2017-09-03 12:17 GMT-04:00 Luiz Carlos :
>>>
 Que desgraça de vida, horas no google pesquisando e não consigo
 resolver porra nenhuma, maldita hora que fui inventar de instalar 
 Windows
 10 e achar que ia conseguir recuperar o Grub.

 2017-09-03 14:19 GMT+00:00 Luiz Carlos :

> Estou até agora tentando, tentei o comando:
> # grub-install --boot-directory=/boot /dev/sda
> Installing for i386-pc platform.
> grub-install.real: warning: Sector 32 is already in use by the
> program `FlexNet'; avoiding it.  This software may cause boot or other
> problems in future.  Please ask its authors not to store data in the 
> boot
> track.
> Installation finished. No error reported.
> mint mint # grub-install --boot-directory=/boot /dev/sda2
> Installing for i386-pc platform.
> grub-install.real: warning: File system `ntfs' doesn't support
> embedding.
> grub-install.real: 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..
> grub-install.real: error: will not proceed with blocklists.
>
>
> Em 3 de setembro de 2017 06:03, Luiz Carlos 
> escreveu:
>
>> Olá amigos, estou em desespero, agora mesmo estou numa live cd
>> tentando recuperar o grub, eu havia instalado o WIndows 10, estou 
>> com o
>> Debian criptografado, tentei recuperar com esses seguintes comandos:
>>
>>
>> # modprobe dm-crypt
>> # cryptsetup luksOpen /dev/sda5 linux
>> # mkdir /media/linux
>> # mount /dev/lvmc/root /media/linux/
>> # chroot /media/linux /bin/bash
>>
>> Dai quando mando # grub-install /dev/sda
>>
>> Aparece: /dev/sda: Not found or not a block device.
>>
>>
>> Eu não sei mais o que faço, aqui na live CD eu consigo ver minhas
>> partições e tudo mais.
>>
>> Meu Debian é de 64 bits.
>>
>
>

>>>
>>
>

>>>
>>
>

network trouble on stretch

[Glenn English]

Working on a Dell 5414 laptop, Stretch.

The WiFi works, but the Ethernet doesn't, and I can't figure out why.

ip addr:

1: lo:  mtu 65536 qdisc noqueue state UNKNOWN
group default qlen 1
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
   valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
   valid_lft forever preferred_lft forever
2: enp0s31f6:  mtu 1500 qdisc noop state DOWN
group default qlen 1000
link/ether 10:05:01:40:f4:43 brd ff:ff:ff:ff:ff:ff
3: wwp0s20f0u2i12:  mtu 1500 qdisc noop
state DOWN group default qlen 1000
link/ether 4e:8a:3a:22:b3:df brd ff:ff:ff:ff:ff:ff
4: wlp1s0:  mtu 1500 qdisc noop state DOWN group
default qlen 1000
link/ether f4:8c:50:17:bc:0e brd ff:ff:ff:ff:ff:ff
5: enx10050149649d:  mtu 1500 qdisc noop state
DOWN group default qlen 1000
link/ether 10:05:01:49:64:9d brd ff:ff:ff:ff:ff:ff

/etc/network/interfaces:

# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

source /etc/network/interfaces.d/*

# The loopback network interface
auto lo
iface lo inet loopback

auto wwp0s20f0u2i12
iface wwp0s20f0u2i12 inet static
address 216.17.134.202/29
gateway 216.17.134.201

First I tried with wicd, a network manager (the static def wasn't in interfaces)

It said the wired interface was up, and assigned the requested IP. It
wasn't checking after assignment to see if it worked. I turned that
on, and it never came back.

I removed the network monitor and added the static paragraph to the
interface file. ifup and ifdown worked, and ip addr said
wwp0s20f0u2i12 was up.

There are two Ethernet ports on this thing, and I tried both with no
success. I swapped out the Ethernet cable with the same result.

I replaced Stretch with Buster. It works. dhcp (Comcast) or static (my
T1). Using the interfaces file.

BTW. ifconfig fans, wait till you get to Buster -- no ifup or down.
Buster seems to boot using a commented out dhcp paragraph, though.
Running by hand, '/etc/init.d/network reload' loads the correct
config.

The 'man interfaces' on Stretch talks a lot about the ethn interfaces.
It does on Buster, too.

This is less than optimal.

What's going on here? This is Linux, not Winders; Debian, not Ubuntu;
stable, not Sid. This is what we're supposed to put on Internet
servers? They had time to make something as simple as this work while
it was testing. And to correct the man pages, too.

If they didn't have time, the release should have been postponed until
it was ready for prime time, IMHO.

I looked on the 'Net, asking why the interface names were changed. I
found a good reason: sometimes the ethn names aren't reliably
consistent. Fine, I say, you've figured how to make them consistent.
That's no reason to change the names from a meaningful 4 or 5 chars to
11, chosen by /dev/urandom.

Somebody's selling the Debian management a pile of bull excrement.

--
Glenn English

UI inconsistency: unlocking LUKS-encrypted drives

[Sam Kuper]

For some LUKS-encrypted partitions, when I unlock them from Debian,
the computer only asks me for the passphrase for the encrypted
partition. For other such partitions, when I unlock them, the computer
also asks me for my user password.* See detailed description below.

My questions are:

1. is this inconsistency intended, and if so, why?

2. is there a way to control this behaviour, i.e. to choose which
partitions require a user password upon unlocking?


The PC where I noticed this issue has the GNOME desktop environment.
All terminal transcripts in this email are from the "Terminal"
application. Here is the version of Debian the PC is running:

$ lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description:Debian GNU/Linux 9.1 (stretch)
Release:9.1
Codename:   stretch
$ cat /proc/version
Linux version 4.9.0-3-amd64 (debian-ker...@lists.debian.org) (gcc
version 6.3.0 20170516 (Debian 6.3.0-18) ) #1 SMP Debian
4.9.30-2+deb9u3 (2017-08-06)


Here are the block devices on this particular PC:

$ lsblk
NAME   MAJ:MIN RM   SIZE RO TYPE  MOUNTPOINT
sda  8:00   1.8T  0 disk
└─sda1   8:10   1.8T  0 part
sdb  8:16   0   1.8T  0 disk
└─sdb1   8:17   0   1.8T  0 part
sdc  8:32   0 232.9G  0 disk
├─sdc1   8:33   0   243M  0 part  /boot
├─sdc2   8:34   0 1K  0 part
└─sdc5   8:37   0 232.7G  0 part
  └─sdb5_crypt 253:00 232.7G  0 crypt
├─pc1--vg-root   253:10 224.7G  0 lvm   /
└─pc1--vg-swap_1 253:20   7.9G  0 lvm   [SWAP]
sdd  8:48   1  59.8G  0 disk
└─sdd1   8:49   1  59.8G  0 part


sda, sdb and sdc are all connected to the motherboard via the SATA
bus. sdd is connected via the Universal Serial Bus (USB). Maybe that
is a factor in the UI inconsistency I am reporting? As you will see,
unlocking a SATA device prompts for a user password; unlocking a USB
device does not.


Anyhow, here is an example of the behaviour I am reporting:

$ udisksctl unlock -b /dev/sdd1
Passphrase:
Unlocked /dev/sdd1 as /dev/dm-3.
$ udisksctl unlock -b /dev/sda1
Passphrase:
# After entering the passphrase for sda1, the screen darkens
# with a transulcent radial gradient overlay, and a Gnome
# modal window pops up: with the following text:
#
## Authentication Required
## Authentication is required to unlock the encrypted device
## XXX-XX (/dev/sda1).
## 
## Password: _
#
# After entering my user password, the modal window closes
# and the translucent overlay disappears, returning focus to
# Terminal.
Unlocked /dev/sda1 as /dev/dm-4.


I hope that illustrates the issue clearly. If not, please let me know.

In any case, please CC me in your reply, as I am not currently
subscribed to the debian-users mailing list. Thanks!


* This particular Debian installation does not have a root account, it
uses sudo instead. Perhaps the computer would ask for the root
password instead of the user password, if this particular Debian
installation *did* have a root account instead of having a user
account with sudo privileges, but I have not tested this.

Re: Recommended editor for novice programmers?

[John Hasler]

Dejan writes:
> For Emacs:

> https://www.emacswiki.org/emacs/AutoComplete

> Something like that?

There are also bunches more, many claiming to be IDEs.  I've not tried them.
-- 
John Hasler 
jhas...@newsguy.com
Elmwood, WI USA

Re: Recommended editor for novice programmers?

[Dejan Jocic]

On 03-09-17, solitone wrote:
> On Saturday, 2 September 2017 15:01:37 CEST The Wanderer wrote:
> > I'm not sure what you would qualify as a "programming editor", but what
> > I use to write code (when nano won't do) is geany, which is a graphical
> > syntax-highlighting editor with various other features useful to a
> > programmer.
> 
> But is there anything that can do code autocomplation, for C++ or Java for 
> instance? Like getting the list of methods available for an object, when 
> typing a dot, as a typical IDE would do.
> -- 
> ⢀⣴⠾⠻⢶⣦⠀ 
> ⣾⠁⢠⠒⠀⣿⡁Sent from my brain using neurons fueled by glucose.
> ⢿⡄⠘⠷⠚⠋⠀ 
> ⠈⠳⣄
> 

For Vim:

http://valloric.github.io/YouCompleteMe/

For Emacs:

https://www.emacswiki.org/emacs/AutoComplete

Something like that?

Re: Recommended editor for novice programmers?

[tomas]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Sun, Sep 03, 2017 at 08:48:08PM +0200, solitone wrote:
> On Saturday, 2 September 2017 15:01:37 CEST The Wanderer wrote:
> > I'm not sure what you would qualify as a "programming editor", but what
> > I use to write code (when nano won't do) is geany, which is a graphical
> > syntax-highlighting editor with various other features useful to a
> > programmer.
> 
> But is there anything that can do code autocomplation, for C++ or Java for 
> instance? Like getting the list of methods available for an object, when 
> typing a dot, as a typical IDE would do.

Never used it myself (I don't particularly care about autocompletion), but
Emacs Semantic[1] reportedly does.

If you are serious about programming, Emacs is definitely worth a look.

Editors are our most important tools. That's why there are so many choices.

Cheers

[1] 
https://www.gnu.org/software/emacs/manual/html_node/semantic/Using-Semantic.html

- -- tomás
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAlmsU2kACgkQBcgs9XrR2kb2ZwCffNs3ScZmJUhYQUgWDx3MjyEy
gagAnjYyzkeYgVirdD9RdBfOZrPe8RUd
=HrJW
-END PGP SIGNATURE-

Re: Erro ao recuperar grub de um Debian com LVM Criptografado.

[Rodolfo]

Seu computador tem UEFI? Verifica isso também, no meu tive que desabilitar
na BIOS um negócio de safe lá.

2017-09-03 14:58 GMT-04:00 Luiz Carlos :

> Ele instala normalmente, mas ele não reconhece as partições.
>
> 2017-09-03 18:55 GMT+00:00 Rodolfo :
>
>> Faz isso, remove o grub:
>>
>> # apt-get remove --purge grub
>>
>> depois
>>
>> # apt-get install grub
>>
>> Obs.: Não lembro o nome do pacote do grub.
>>
>> 2017-09-03 14:53 GMT-04:00 Luiz Carlos :
>>
>>> Estou na live cd sim, saí do chroot e tentei o seguinte comando:
>>> mint mint # grub-install --root-directory=/media/linux /dev/sda
>>> grub-probe: error: failed to get canonical path of `/cow'.
>>> Installing for i386-pc platform.
>>> grub-install.real: error: attempt to install to encrypted disk without
>>> cryptodisk enabled. Set `GRUB_ENABLE_CRYPTODISK=1' in file
>>> `/etc/default/grub'..
>>>
>>> Ou seja, deu merda, acho que nem o Windows vai iniciar depois dessa.
>>>
>>> Em 3 de setembro de 2017 18:46, Rodolfo  escreveu:
>>>
 Você chegou a usar um live-cd?

 Eu tive um problema parecido, entrei pelo live-cd(ou pelo cd de
 instalação do Debian, pois tem uma parte que consigo acessar a instalação
 que tinha pelo terminal) e reinstalei o grub, isso mesmo, reinstalei, não
 fiz nenhum comando, só fiz reinstalar.



 2017-09-03 14:29 GMT-04:00 Luiz Carlos :

> Eu desabilitei o fastboot do windows 10, mas mando esses comandos e
> simplesmente dá erro:
> mint@mint ~ $ sudo su
> mint mint # modprobe dm-crypt
> mint mint # cryptsetup luksOpen /dev/sda5 linux
> Enter passphrase for /dev/sda5:
> mint mint # mkdir /media/linux
> mint mint # mount /dev/lvmc/root /media/linux/
> mint mint # chroot /media/linux /bin/bash
> root@mint:/# mount /dev/sda2 /boot
> mount: /boot: mount failed: Unknown error -1
>
> Se não consigo montar a droga da /boot não vou conseguir instalar o
> grub.
>
> 2017-09-03 17:53 GMT+00:00 Rodolfo :
>
>> Tentou bootar via live-cd?
>>
>> 2017-09-03 12:17 GMT-04:00 Luiz Carlos :
>>
>>> Que desgraça de vida, horas no google pesquisando e não consigo
>>> resolver porra nenhuma, maldita hora que fui inventar de instalar 
>>> Windows
>>> 10 e achar que ia conseguir recuperar o Grub.
>>>
>>> 2017-09-03 14:19 GMT+00:00 Luiz Carlos :
>>>
 Estou até agora tentando, tentei o comando:
 # grub-install --boot-directory=/boot /dev/sda
 Installing for i386-pc platform.
 grub-install.real: warning: Sector 32 is already in use by the
 program `FlexNet'; avoiding it.  This software may cause boot or other
 problems in future.  Please ask its authors not to store data in the 
 boot
 track.
 Installation finished. No error reported.
 mint mint # grub-install --boot-directory=/boot /dev/sda2
 Installing for i386-pc platform.
 grub-install.real: warning: File system `ntfs' doesn't support
 embedding.
 grub-install.real: 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..
 grub-install.real: error: will not proceed with blocklists.


 Em 3 de setembro de 2017 06:03, Luiz Carlos 
 escreveu:

> Olá amigos, estou em desespero, agora mesmo estou numa live cd
> tentando recuperar o grub, eu havia instalado o WIndows 10, estou com 
> o
> Debian criptografado, tentei recuperar com esses seguintes comandos:
>
>
> # modprobe dm-crypt
> # cryptsetup luksOpen /dev/sda5 linux
> # mkdir /media/linux
> # mount /dev/lvmc/root /media/linux/
> # chroot /media/linux /bin/bash
>
> Dai quando mando # grub-install /dev/sda
>
> Aparece: /dev/sda: Not found or not a block device.
>
>
> Eu não sei mais o que faço, aqui na live CD eu consigo ver minhas
> partições e tudo mais.
>
> Meu Debian é de 64 bits.
>


>>>
>>
>

>>>
>>
>

Re: Erro ao recuperar grub de um Debian com LVM Criptografado.

[Luiz Carlos]

Ele instala normalmente, mas ele não reconhece as partições.

2017-09-03 18:55 GMT+00:00 Rodolfo :

> Faz isso, remove o grub:
>
> # apt-get remove --purge grub
>
> depois
>
> # apt-get install grub
>
> Obs.: Não lembro o nome do pacote do grub.
>
> 2017-09-03 14:53 GMT-04:00 Luiz Carlos :
>
>> Estou na live cd sim, saí do chroot e tentei o seguinte comando:
>> mint mint # grub-install --root-directory=/media/linux /dev/sda
>> grub-probe: error: failed to get canonical path of `/cow'.
>> Installing for i386-pc platform.
>> grub-install.real: error: attempt to install to encrypted disk without
>> cryptodisk enabled. Set `GRUB_ENABLE_CRYPTODISK=1' in file
>> `/etc/default/grub'..
>>
>> Ou seja, deu merda, acho que nem o Windows vai iniciar depois dessa.
>>
>> Em 3 de setembro de 2017 18:46, Rodolfo  escreveu:
>>
>>> Você chegou a usar um live-cd?
>>>
>>> Eu tive um problema parecido, entrei pelo live-cd(ou pelo cd de
>>> instalação do Debian, pois tem uma parte que consigo acessar a instalação
>>> que tinha pelo terminal) e reinstalei o grub, isso mesmo, reinstalei, não
>>> fiz nenhum comando, só fiz reinstalar.
>>>
>>>
>>>
>>> 2017-09-03 14:29 GMT-04:00 Luiz Carlos :
>>>
 Eu desabilitei o fastboot do windows 10, mas mando esses comandos e
 simplesmente dá erro:
 mint@mint ~ $ sudo su
 mint mint # modprobe dm-crypt
 mint mint # cryptsetup luksOpen /dev/sda5 linux
 Enter passphrase for /dev/sda5:
 mint mint # mkdir /media/linux
 mint mint # mount /dev/lvmc/root /media/linux/
 mint mint # chroot /media/linux /bin/bash
 root@mint:/# mount /dev/sda2 /boot
 mount: /boot: mount failed: Unknown error -1

 Se não consigo montar a droga da /boot não vou conseguir instalar o
 grub.

 2017-09-03 17:53 GMT+00:00 Rodolfo :

> Tentou bootar via live-cd?
>
> 2017-09-03 12:17 GMT-04:00 Luiz Carlos :
>
>> Que desgraça de vida, horas no google pesquisando e não consigo
>> resolver porra nenhuma, maldita hora que fui inventar de instalar Windows
>> 10 e achar que ia conseguir recuperar o Grub.
>>
>> 2017-09-03 14:19 GMT+00:00 Luiz Carlos :
>>
>>> Estou até agora tentando, tentei o comando:
>>> # grub-install --boot-directory=/boot /dev/sda
>>> Installing for i386-pc platform.
>>> grub-install.real: warning: Sector 32 is already in use by the
>>> program `FlexNet'; avoiding it.  This software may cause boot or other
>>> problems in future.  Please ask its authors not to store data in the 
>>> boot
>>> track.
>>> Installation finished. No error reported.
>>> mint mint # grub-install --boot-directory=/boot /dev/sda2
>>> Installing for i386-pc platform.
>>> grub-install.real: warning: File system `ntfs' doesn't support
>>> embedding.
>>> grub-install.real: 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..
>>> grub-install.real: error: will not proceed with blocklists.
>>>
>>>
>>> Em 3 de setembro de 2017 06:03, Luiz Carlos 
>>> escreveu:
>>>
 Olá amigos, estou em desespero, agora mesmo estou numa live cd
 tentando recuperar o grub, eu havia instalado o WIndows 10, estou com o
 Debian criptografado, tentei recuperar com esses seguintes comandos:


 # modprobe dm-crypt
 # cryptsetup luksOpen /dev/sda5 linux
 # mkdir /media/linux
 # mount /dev/lvmc/root /media/linux/
 # chroot /media/linux /bin/bash

 Dai quando mando # grub-install /dev/sda

 Aparece: /dev/sda: Not found or not a block device.


 Eu não sei mais o que faço, aqui na live CD eu consigo ver minhas
 partições e tudo mais.

 Meu Debian é de 64 bits.

>>>
>>>
>>
>

>>>
>>
>

Re: Erro ao recuperar grub de um Debian com LVM Criptografado.

[Rodolfo]

Faz isso, remove o grub:

# apt-get remove --purge grub

depois

# apt-get install grub

Obs.: Não lembro o nome do pacote do grub.

2017-09-03 14:53 GMT-04:00 Luiz Carlos :

> Estou na live cd sim, saí do chroot e tentei o seguinte comando:
> mint mint # grub-install --root-directory=/media/linux /dev/sda
> grub-probe: error: failed to get canonical path of `/cow'.
> Installing for i386-pc platform.
> grub-install.real: error: attempt to install to encrypted disk without
> cryptodisk enabled. Set `GRUB_ENABLE_CRYPTODISK=1' in file
> `/etc/default/grub'..
>
> Ou seja, deu merda, acho que nem o Windows vai iniciar depois dessa.
>
> Em 3 de setembro de 2017 18:46, Rodolfo  escreveu:
>
>> Você chegou a usar um live-cd?
>>
>> Eu tive um problema parecido, entrei pelo live-cd(ou pelo cd de
>> instalação do Debian, pois tem uma parte que consigo acessar a instalação
>> que tinha pelo terminal) e reinstalei o grub, isso mesmo, reinstalei, não
>> fiz nenhum comando, só fiz reinstalar.
>>
>>
>>
>> 2017-09-03 14:29 GMT-04:00 Luiz Carlos :
>>
>>> Eu desabilitei o fastboot do windows 10, mas mando esses comandos e
>>> simplesmente dá erro:
>>> mint@mint ~ $ sudo su
>>> mint mint # modprobe dm-crypt
>>> mint mint # cryptsetup luksOpen /dev/sda5 linux
>>> Enter passphrase for /dev/sda5:
>>> mint mint # mkdir /media/linux
>>> mint mint # mount /dev/lvmc/root /media/linux/
>>> mint mint # chroot /media/linux /bin/bash
>>> root@mint:/# mount /dev/sda2 /boot
>>> mount: /boot: mount failed: Unknown error -1
>>>
>>> Se não consigo montar a droga da /boot não vou conseguir instalar o grub.
>>>
>>> 2017-09-03 17:53 GMT+00:00 Rodolfo :
>>>
 Tentou bootar via live-cd?

 2017-09-03 12:17 GMT-04:00 Luiz Carlos :

> Que desgraça de vida, horas no google pesquisando e não consigo
> resolver porra nenhuma, maldita hora que fui inventar de instalar Windows
> 10 e achar que ia conseguir recuperar o Grub.
>
> 2017-09-03 14:19 GMT+00:00 Luiz Carlos :
>
>> Estou até agora tentando, tentei o comando:
>> # grub-install --boot-directory=/boot /dev/sda
>> Installing for i386-pc platform.
>> grub-install.real: warning: Sector 32 is already in use by the
>> program `FlexNet'; avoiding it.  This software may cause boot or other
>> problems in future.  Please ask its authors not to store data in the boot
>> track.
>> Installation finished. No error reported.
>> mint mint # grub-install --boot-directory=/boot /dev/sda2
>> Installing for i386-pc platform.
>> grub-install.real: warning: File system `ntfs' doesn't support
>> embedding.
>> grub-install.real: 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..
>> grub-install.real: error: will not proceed with blocklists.
>>
>>
>> Em 3 de setembro de 2017 06:03, Luiz Carlos 
>> escreveu:
>>
>>> Olá amigos, estou em desespero, agora mesmo estou numa live cd
>>> tentando recuperar o grub, eu havia instalado o WIndows 10, estou com o
>>> Debian criptografado, tentei recuperar com esses seguintes comandos:
>>>
>>>
>>> # modprobe dm-crypt
>>> # cryptsetup luksOpen /dev/sda5 linux
>>> # mkdir /media/linux
>>> # mount /dev/lvmc/root /media/linux/
>>> # chroot /media/linux /bin/bash
>>>
>>> Dai quando mando # grub-install /dev/sda
>>>
>>> Aparece: /dev/sda: Not found or not a block device.
>>>
>>>
>>> Eu não sei mais o que faço, aqui na live CD eu consigo ver minhas
>>> partições e tudo mais.
>>>
>>> Meu Debian é de 64 bits.
>>>
>>
>>
>

>>>
>>
>

Re: Erro ao recuperar grub de um Debian com LVM Criptografado.

[Luiz Carlos]

Estou na live cd sim, saí do chroot e tentei o seguinte comando:
mint mint # grub-install --root-directory=/media/linux /dev/sda
grub-probe: error: failed to get canonical path of `/cow'.
Installing for i386-pc platform.
grub-install.real: error: attempt to install to encrypted disk without
cryptodisk enabled. Set `GRUB_ENABLE_CRYPTODISK=1' in file
`/etc/default/grub'..

Ou seja, deu merda, acho que nem o Windows vai iniciar depois dessa.

Em 3 de setembro de 2017 18:46, Rodolfo  escreveu:

> Você chegou a usar um live-cd?
>
> Eu tive um problema parecido, entrei pelo live-cd(ou pelo cd de instalação
> do Debian, pois tem uma parte que consigo acessar a instalação que tinha
> pelo terminal) e reinstalei o grub, isso mesmo, reinstalei, não fiz nenhum
> comando, só fiz reinstalar.
>
>
>
> 2017-09-03 14:29 GMT-04:00 Luiz Carlos :
>
>> Eu desabilitei o fastboot do windows 10, mas mando esses comandos e
>> simplesmente dá erro:
>> mint@mint ~ $ sudo su
>> mint mint # modprobe dm-crypt
>> mint mint # cryptsetup luksOpen /dev/sda5 linux
>> Enter passphrase for /dev/sda5:
>> mint mint # mkdir /media/linux
>> mint mint # mount /dev/lvmc/root /media/linux/
>> mint mint # chroot /media/linux /bin/bash
>> root@mint:/# mount /dev/sda2 /boot
>> mount: /boot: mount failed: Unknown error -1
>>
>> Se não consigo montar a droga da /boot não vou conseguir instalar o grub.
>>
>> 2017-09-03 17:53 GMT+00:00 Rodolfo :
>>
>>> Tentou bootar via live-cd?
>>>
>>> 2017-09-03 12:17 GMT-04:00 Luiz Carlos :
>>>
 Que desgraça de vida, horas no google pesquisando e não consigo
 resolver porra nenhuma, maldita hora que fui inventar de instalar Windows
 10 e achar que ia conseguir recuperar o Grub.

 2017-09-03 14:19 GMT+00:00 Luiz Carlos :

> Estou até agora tentando, tentei o comando:
> # grub-install --boot-directory=/boot /dev/sda
> Installing for i386-pc platform.
> grub-install.real: warning: Sector 32 is already in use by the program
> `FlexNet'; avoiding it.  This software may cause boot or other problems in
> future.  Please ask its authors not to store data in the boot track.
> Installation finished. No error reported.
> mint mint # grub-install --boot-directory=/boot /dev/sda2
> Installing for i386-pc platform.
> grub-install.real: warning: File system `ntfs' doesn't support
> embedding.
> grub-install.real: 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..
> grub-install.real: error: will not proceed with blocklists.
>
>
> Em 3 de setembro de 2017 06:03, Luiz Carlos 
> escreveu:
>
>> Olá amigos, estou em desespero, agora mesmo estou numa live cd
>> tentando recuperar o grub, eu havia instalado o WIndows 10, estou com o
>> Debian criptografado, tentei recuperar com esses seguintes comandos:
>>
>>
>> # modprobe dm-crypt
>> # cryptsetup luksOpen /dev/sda5 linux
>> # mkdir /media/linux
>> # mount /dev/lvmc/root /media/linux/
>> # chroot /media/linux /bin/bash
>>
>> Dai quando mando # grub-install /dev/sda
>>
>> Aparece: /dev/sda: Not found or not a block device.
>>
>>
>> Eu não sei mais o que faço, aqui na live CD eu consigo ver minhas
>> partições e tudo mais.
>>
>> Meu Debian é de 64 bits.
>>
>
>

>>>
>>
>

Re: Recommended editor for novice programmers?

[solitone]

On Saturday, 2 September 2017 15:01:37 CEST The Wanderer wrote:
> I'm not sure what you would qualify as a "programming editor", but what
> I use to write code (when nano won't do) is geany, which is a graphical
> syntax-highlighting editor with various other features useful to a
> programmer.

But is there anything that can do code autocomplation, for C++ or Java for 
instance? Like getting the list of methods available for an object, when 
typing a dot, as a typical IDE would do.
-- 
⢀⣴⠾⠻⢶⣦⠀ 
⣾⠁⢠⠒⠀⣿⡁Sent from my brain using neurons fueled by glucose.
⢿⡄⠘⠷⠚⠋⠀ 
⠈⠳⣄

Re: Erro ao recuperar grub de um Debian com LVM Criptografado.

[Rodolfo]

Você chegou a usar um live-cd?

Eu tive um problema parecido, entrei pelo live-cd(ou pelo cd de instalação
do Debian, pois tem uma parte que consigo acessar a instalação que tinha
pelo terminal) e reinstalei o grub, isso mesmo, reinstalei, não fiz nenhum
comando, só fiz reinstalar.



2017-09-03 14:29 GMT-04:00 Luiz Carlos :

> Eu desabilitei o fastboot do windows 10, mas mando esses comandos e
> simplesmente dá erro:
> mint@mint ~ $ sudo su
> mint mint # modprobe dm-crypt
> mint mint # cryptsetup luksOpen /dev/sda5 linux
> Enter passphrase for /dev/sda5:
> mint mint # mkdir /media/linux
> mint mint # mount /dev/lvmc/root /media/linux/
> mint mint # chroot /media/linux /bin/bash
> root@mint:/# mount /dev/sda2 /boot
> mount: /boot: mount failed: Unknown error -1
>
> Se não consigo montar a droga da /boot não vou conseguir instalar o grub.
>
> 2017-09-03 17:53 GMT+00:00 Rodolfo :
>
>> Tentou bootar via live-cd?
>>
>> 2017-09-03 12:17 GMT-04:00 Luiz Carlos :
>>
>>> Que desgraça de vida, horas no google pesquisando e não consigo resolver
>>> porra nenhuma, maldita hora que fui inventar de instalar Windows 10 e achar
>>> que ia conseguir recuperar o Grub.
>>>
>>> 2017-09-03 14:19 GMT+00:00 Luiz Carlos :
>>>
 Estou até agora tentando, tentei o comando:
 # grub-install --boot-directory=/boot /dev/sda
 Installing for i386-pc platform.
 grub-install.real: warning: Sector 32 is already in use by the program
 `FlexNet'; avoiding it.  This software may cause boot or other problems in
 future.  Please ask its authors not to store data in the boot track.
 Installation finished. No error reported.
 mint mint # grub-install --boot-directory=/boot /dev/sda2
 Installing for i386-pc platform.
 grub-install.real: warning: File system `ntfs' doesn't support
 embedding.
 grub-install.real: 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..
 grub-install.real: error: will not proceed with blocklists.


 Em 3 de setembro de 2017 06:03, Luiz Carlos 
 escreveu:

> Olá amigos, estou em desespero, agora mesmo estou numa live cd
> tentando recuperar o grub, eu havia instalado o WIndows 10, estou com o
> Debian criptografado, tentei recuperar com esses seguintes comandos:
>
>
> # modprobe dm-crypt
> # cryptsetup luksOpen /dev/sda5 linux
> # mkdir /media/linux
> # mount /dev/lvmc/root /media/linux/
> # chroot /media/linux /bin/bash
>
> Dai quando mando # grub-install /dev/sda
>
> Aparece: /dev/sda: Not found or not a block device.
>
>
> Eu não sei mais o que faço, aqui na live CD eu consigo ver minhas
> partições e tudo mais.
>
> Meu Debian é de 64 bits.
>


>>>
>>
>

Re: Recommended editor for novice programmers?

[Tom Dial]

On 09/02/2017 12:21 PM, Tom Browder wrote:
> My Linux user group is setting up one desktop computer and one laptop
> computer for lending to our local library as an educational resource for
> folks who want to explore what Linux is all about.  We are using Debian
> 9 for now.
> 
> I am open to any suggestions for standard packages we should add. I have
> already installed gcc and friends as well as Scilab, R, Perl 6, and some
> other stuff, including emacs.
> 
> I would especially appreciate other ideas for programming editors for
> novice programmers.

If you are setting it up with Gnome, the included gedit isn't half bad
and pretty easy to use. A quick check for C, Python, Go, R, and Perl
shows useful and appropriate highlighting of comments, strings,
functions, and the like.

Tom Dial

> 
> Thanks.
> 
> Best regards,
> 
> -Tom

Re: Laptop recommendation

[Mario Castelán Castro]

On 03/09/17 08:38, Jonas Hedman wrote:
> Basically I'm on the hunt for a newish laptop on which I naturally want
> to run Debian. [...]
> 
> Any suggestions?

Yes. Think Penguin  sells computers
compatible with GNU/Linux that do not need proprietary drivers. They
claim to donate part of the profit to the development of free software
(I can neither confirm nor deny this claim).

Use H-node  to check for hardware compatibility and
contribute an entry for your hardware if you can.

-- 
Do not eat animals; respect them as you respect people.
https://duckduckgo.com/?q=how+to+(become+OR+eat)+vegan



signature.asc
Description: OpenPGP digital signature

Re: Erro ao recuperar grub de um Debian com LVM Criptografado.

[Luiz Carlos]

Eu desabilitei o fastboot do windows 10, mas mando esses comandos e
simplesmente dá erro:
mint@mint ~ $ sudo su
mint mint # modprobe dm-crypt
mint mint # cryptsetup luksOpen /dev/sda5 linux
Enter passphrase for /dev/sda5:
mint mint # mkdir /media/linux
mint mint # mount /dev/lvmc/root /media/linux/
mint mint # chroot /media/linux /bin/bash
root@mint:/# mount /dev/sda2 /boot
mount: /boot: mount failed: Unknown error -1

Se não consigo montar a droga da /boot não vou conseguir instalar o grub.

2017-09-03 17:53 GMT+00:00 Rodolfo :

> Tentou bootar via live-cd?
>
> 2017-09-03 12:17 GMT-04:00 Luiz Carlos :
>
>> Que desgraça de vida, horas no google pesquisando e não consigo resolver
>> porra nenhuma, maldita hora que fui inventar de instalar Windows 10 e achar
>> que ia conseguir recuperar o Grub.
>>
>> 2017-09-03 14:19 GMT+00:00 Luiz Carlos :
>>
>>> Estou até agora tentando, tentei o comando:
>>> # grub-install --boot-directory=/boot /dev/sda
>>> Installing for i386-pc platform.
>>> grub-install.real: warning: Sector 32 is already in use by the program
>>> `FlexNet'; avoiding it.  This software may cause boot or other problems in
>>> future.  Please ask its authors not to store data in the boot track.
>>> Installation finished. No error reported.
>>> mint mint # grub-install --boot-directory=/boot /dev/sda2
>>> Installing for i386-pc platform.
>>> grub-install.real: warning: File system `ntfs' doesn't support embedding.
>>> grub-install.real: 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..
>>> grub-install.real: error: will not proceed with blocklists.
>>>
>>>
>>> Em 3 de setembro de 2017 06:03, Luiz Carlos 
>>> escreveu:
>>>
 Olá amigos, estou em desespero, agora mesmo estou numa live cd tentando
 recuperar o grub, eu havia instalado o WIndows 10, estou com o Debian
 criptografado, tentei recuperar com esses seguintes comandos:


 # modprobe dm-crypt
 # cryptsetup luksOpen /dev/sda5 linux
 # mkdir /media/linux
 # mount /dev/lvmc/root /media/linux/
 # chroot /media/linux /bin/bash

 Dai quando mando # grub-install /dev/sda

 Aparece: /dev/sda: Not found or not a block device.


 Eu não sei mais o que faço, aqui na live CD eu consigo ver minhas
 partições e tudo mais.

 Meu Debian é de 64 bits.

>>>
>>>
>>
>

Re: Erro ao recuperar grub de um Debian com LVM Criptografado.

[Rodolfo]

Tentou bootar via live-cd?

2017-09-03 12:17 GMT-04:00 Luiz Carlos :

> Que desgraça de vida, horas no google pesquisando e não consigo resolver
> porra nenhuma, maldita hora que fui inventar de instalar Windows 10 e achar
> que ia conseguir recuperar o Grub.
>
> 2017-09-03 14:19 GMT+00:00 Luiz Carlos :
>
>> Estou até agora tentando, tentei o comando:
>> # grub-install --boot-directory=/boot /dev/sda
>> Installing for i386-pc platform.
>> grub-install.real: warning: Sector 32 is already in use by the program
>> `FlexNet'; avoiding it.  This software may cause boot or other problems in
>> future.  Please ask its authors not to store data in the boot track.
>> Installation finished. No error reported.
>> mint mint # grub-install --boot-directory=/boot /dev/sda2
>> Installing for i386-pc platform.
>> grub-install.real: warning: File system `ntfs' doesn't support embedding.
>> grub-install.real: 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..
>> grub-install.real: error: will not proceed with blocklists.
>>
>>
>> Em 3 de setembro de 2017 06:03, Luiz Carlos  escreveu:
>>
>>> Olá amigos, estou em desespero, agora mesmo estou numa live cd tentando
>>> recuperar o grub, eu havia instalado o WIndows 10, estou com o Debian
>>> criptografado, tentei recuperar com esses seguintes comandos:
>>>
>>>
>>> # modprobe dm-crypt
>>> # cryptsetup luksOpen /dev/sda5 linux
>>> # mkdir /media/linux
>>> # mount /dev/lvmc/root /media/linux/
>>> # chroot /media/linux /bin/bash
>>>
>>> Dai quando mando # grub-install /dev/sda
>>>
>>> Aparece: /dev/sda: Not found or not a block device.
>>>
>>>
>>> Eu não sei mais o que faço, aqui na live CD eu consigo ver minhas
>>> partições e tudo mais.
>>>
>>> Meu Debian é de 64 bits.
>>>
>>
>>
>

Re: Install on hp-pavilion-g6-2100 stops at 98%

[Thomas Schmitt]

Hi,

Luis Speciale wrote:
> I have a Debian installed with Cinnamon.

Congrats.

> I will explain (what I remember) what I did tomorrow.

Don't forget it.


Have a nice day :)

Thomas

estou a tua espera

[manuel martinscoelho]

‌

Re: Outil d'organisation du temps

[Dominique Asselineau]

Sébastien Dinot wrote on Sun, Sep 03, 2017 at 01:00:51PM +0200
> Bonjour Jean-Philippe,
> 
> MENGUAL Jean-Philippe a écrit :
> > Je cherche si Debian a un logiciel équivalent à Wunderlist. Evidemment
> > on peut me dire que org-mode est la solution, mais ça manque un peu de
> > convivialité pour un utilisateur d'interfaces graphiques. Existe-t-il
> > quelque chose de simialaire? Ou un greffon?
> 
> Je ne connais pas Wunderlist mais, après un rapide coup d'œil au site
> web de l'éditeur, cet outil me semble plus être un gestionnaire de
> tâches un tantinet évolué (et joli) qu'un gestionnaire de temps quel que
> je le définirais (un outil permettant la planification des tâches et des
> rendez-vous).
> 
> Pour ce qui est de la gestion des tâches, tu peux peut-être regarder du
> côté de Zanshin :
> 
> https://zanshin.kde.org/
> 
> Même si la dernière version officielle a un an, son développement reste
> actif :
> 
> https://phabricator.kde.org/source/zanshin/history/master/

Et c'est packagé Debiean

zanshin - to-do list manager

> 
> Quant à moi, pour gérer mon temps, j'utilise Lightning :
> 
> https://addons.mozilla.org/fr/thunderbird/addon/lightning/

Idem

lightning - Calendar Extension for Thunderbird

Dominique

> 
> Si une approche Kanban est plus susceptible de te séduire, tu peux
> regarder du côté de l'application web Wekan :
> 
> https://wekan.github.io/
> 
> 
> Sébastien
> 
> 
> -- 
> Sébastien Dinot, sebastien.di...@free.fr
> http://sebastien.dinot.free.fr/
> Ne goûtez pas au logiciel libre, vous ne pourriez plus vous en passer !
> 

-- 

Re: Install on hp-pavilion-g6-2100 stops at 98%

[Luis Speciale]

Guess what?

I have a Debian installed with Cinnamon.
I'm beginning to explore it.
I'm a little tired now but I will explain (what I remember) what I did 
tomorrow.


Thank you again to all of you. Without your help I should ended giving up.

Luis

Re: Laptop recommendation

[Dan Ritter]

On Sun, Sep 03, 2017 at 03:38:17PM +0200, Jonas Hedman wrote:
> Hello I hope that is not OT for this list.
> 
> Basically I'm on the hunt for a newish laptop on which I naturally want
> to run Debian. I'm a student and I spend most of my daily outandabout 
> computer time reading pdfs, writing LaTeX docs, surfing and doing some 
> light coding, no heavy duty stuff in other words. I use i3vm and I
> generally like to keep things as light and minimal as feasibly possible.
> 
> I really value light weight and good battery life and my upper bound on prize
> is somewhere around 875$ (~7K SEK). Memory should be greater than or
> equal to 2GB and an sdd would be nice.
> 
> I know very little about hardware and I'm not quite sure where or how to 
> start looking. I though the Lenovo Thinkpad 13 looked promising but it's a 
> bit 
> over my price target. Could chromeboosk be something to look into? I
> know the older thinkpads has good debian support but if I remember
> correctly they are also very heavy.

System76 (www.system76.com) makes laptops that run Ubuntu; it
has generally been easy to retrofit Debian on them. They have 
several models that fit in your price range including more RAM
and an SSD.

I have purchased a fair number of machines from them over the
last decade, for both work and home.

-dsr-

Re: Erro ao recuperar grub de um Debian com LVM Criptografado.

[Luiz Carlos]

Que desgraça de vida, horas no google pesquisando e não consigo resolver
porra nenhuma, maldita hora que fui inventar de instalar Windows 10 e achar
que ia conseguir recuperar o Grub.

2017-09-03 14:19 GMT+00:00 Luiz Carlos :

> Estou até agora tentando, tentei o comando:
> # grub-install --boot-directory=/boot /dev/sda
> Installing for i386-pc platform.
> grub-install.real: warning: Sector 32 is already in use by the program
> `FlexNet'; avoiding it.  This software may cause boot or other problems in
> future.  Please ask its authors not to store data in the boot track.
> Installation finished. No error reported.
> mint mint # grub-install --boot-directory=/boot /dev/sda2
> Installing for i386-pc platform.
> grub-install.real: warning: File system `ntfs' doesn't support embedding.
> grub-install.real: 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..
> grub-install.real: error: will not proceed with blocklists.
>
>
> Em 3 de setembro de 2017 06:03, Luiz Carlos  escreveu:
>
>> Olá amigos, estou em desespero, agora mesmo estou numa live cd tentando
>> recuperar o grub, eu havia instalado o WIndows 10, estou com o Debian
>> criptografado, tentei recuperar com esses seguintes comandos:
>>
>>
>> # modprobe dm-crypt
>> # cryptsetup luksOpen /dev/sda5 linux
>> # mkdir /media/linux
>> # mount /dev/lvmc/root /media/linux/
>> # chroot /media/linux /bin/bash
>>
>> Dai quando mando # grub-install /dev/sda
>>
>> Aparece: /dev/sda: Not found or not a block device.
>>
>>
>> Eu não sei mais o que faço, aqui na live CD eu consigo ver minhas
>> partições e tudo mais.
>>
>> Meu Debian é de 64 bits.
>>
>
>

Re: Recommended editor for novice programmers?

[Jude DaShiell]

emacs has succession arranged, vim does not.  If the creator of vim gets 
struck by lightning and has his brains fried, no succession exists to 
continue support of vim in the event of his incapacity.  Succession of 
emacs was passed along to three who are known by r.m.s. willing and able 
to handle that job already.
Now for my offering, has ne and e4 been considered yet?  The e4 editor 
may be named e3, but I think by now it's e4.  I don't know the status of 
elvis succession but that may be a possibility for vim users if it's 
been handled by now.


On Sun, 3 Sep 2017, rhkra...@gmail.com wrote:


Date: Sun, 3 Sep 2017 11:48:24
From: rhkra...@gmail.com
To: debian-user@lists.debian.org
Subject: Re: Recommended editor for novice programmers?
Resent-Date: Sun,  3 Sep 2017 15:48:48 + (UTC)
Resent-From: debian-user@lists.debian.org

On Sunday, September 03, 2017 11:30:09 AM Larry Dighera wrote:

On Sat, 2 Sep 2017 20:46:33 -0400, rhkra...@gmail.com wrote:

I do occasionally use vi (when
I'm stuck with no other editor), but I wouldn't wish either on a novice
programmer.  Further, I don't think they have any advantage over a good
GUI editor with features like a scripting language, keyboard macros,
outlining / folding, syntax highlighting, and such.


...


With regard to the missing features being lamented above:
https://www.ibm.com/developerworks/library/l-vim-script-1/index.html
http://www.thegeekstuff.com/2009/01/vi-and-vim-macro-tutorial-how-to-record
-and-play/ https://majutsushi.github.io/tagbar/

For syntax highlighting, simply write: "Esc:syntax on" to activate the
builtin.


Hmm, I guess I need to clarify--I wasn't lamenting or trying to imply any
missing features in vi/vim or Emacs, but rather trying to respond to others
who seemed to believe such features didn't exist in many GUI editors.




--

Re: Recommended editor for novice programmers?

[Larry Dighera]

On Sat, 2 Sep 2017 20:34:27 -0500, Mario Castelán Castro
 wrote:

>Assuming that people in the OP's library is representative of the
>general population, then most people in that library will never “develop
>a greater interest in computers” like you and me. Run-of-the-mill users
>do not care if software is very powerful, configurable, reliable, or
>other technical merits. They want something that is so simple to use
>that they will never need to even glance at the manual. Microsoft and
>Apple deliver that and that is why they have had so much commercial success.


If the OP wants to provide a GUI editor that resembles MS Write, with
which his attendees would likely be familiar, he might resort to Libre
Office https://www.libreoffice.org/ .  Libre Write
https://www.libreoffice.org/discover/writer/ is part of what is
essentially a free MS Office Suite, and runs on many platforms.  But
it's not a programmer's editor.  (If this has already been mentioned
in this thread, please forgive me.)

Re: Recommended editor for novice programmers?

[rhkramer]

On Sunday, September 03, 2017 11:30:09 AM Larry Dighera wrote:
> On Sat, 2 Sep 2017 20:46:33 -0400, rhkra...@gmail.com wrote:
> >I do occasionally use vi (when
> >I'm stuck with no other editor), but I wouldn't wish either on a novice
> >programmer.  Further, I don't think they have any advantage over a good
> >GUI editor with features like a scripting language, keyboard macros,
> >outlining / folding, syntax highlighting, and such.

...

> With regard to the missing features being lamented above:
> https://www.ibm.com/developerworks/library/l-vim-script-1/index.html
> http://www.thegeekstuff.com/2009/01/vi-and-vim-macro-tutorial-how-to-record
> -and-play/ https://majutsushi.github.io/tagbar/
> 
> For syntax highlighting, simply write: "Esc:syntax on" to activate the
> builtin.

Hmm, I guess I need to clarify--I wasn't lamenting or trying to imply any 
missing features in vi/vim or Emacs, but rather trying to respond to others 
who seemed to believe such features didn't exist in many GUI editors.

Re: que paso con debian-live-version-standard+nonfree.iso?

[Felix Perez]

El 2 de septiembre de 2017, 20:08, franiortiz hotmail
 escribió:
> Hola, donde esta esa version de debian 
> (debian-live-version-standard+nonfree.iso)
> es la que me he acostumbrado a usar y desde la version 9 no aparece mas:
> http://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/9.1.0-live+nonfree/i386/iso-hybrid/
> quiza me equivoque de enlace, pero por mas vueltas que doy no la encuentro.
> donde esta ? y si no se hace mas , porque?
>

http://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/

-- 
usuario linux  #274354
normas de la lista:  http://wiki.debian.org/es/NormasLista
como hacer preguntas inteligentes:
http://www.sindominio.net/ayuda/preguntas-inteligentes.html

Re: Recommended editor for novice programmers?

[Larry Dighera]

On Sat, 2 Sep 2017 20:46:33 -0400, rhkra...@gmail.com wrote:

>I do occasionally use vi (when 
>I'm stuck with no other editor), but I wouldn't wish either on a novice 
>programmer.  Further, I don't think they have any advantage over a good GUI 
>editor with features like a scripting language, keyboard macros, outlining / 
>folding, syntax highlighting, and such.

The vi (visual interface) editor was used by AT (the developers of
Unix under government contract) service personnel to administrate the
US telephone network over dial-up connections.  As there was no mouse
support in those early days, vi was designed to be used entirely from
the keyboard, a feature touch-typists will appreciate because it
doesn't require reaching for a mouse and abandoning the home-row hand
positions.  

With regard to the missing features being lamented above:
https://www.ibm.com/developerworks/library/l-vim-script-1/index.html
http://www.thegeekstuff.com/2009/01/vi-and-vim-macro-tutorial-how-to-record-and-play/
https://majutsushi.github.io/tagbar/

For syntax highlighting, simply write: "Esc:syntax on" to activate the
builtin.

[no subject]

[max vidocq]

   Bonjour Angelique
3. Figure tutélaire de la cathédrale d' Amiens, la Vierge du portail sud a fait 
l' objet de nombreux repeints au cours des siècles, comme en témoignent les 
pigments dans les plis de la robe.
4. Quadrilobe du soubassement du portail de la Mère diel, le Massacre des 
innocents.
5. La restauration exemplaire du portail de la Mère Dieu a permis de restituer 
une image assez vraisemblable de la polychromie médiévale.
Le portail de la Vierge dorée. On doit notamment à Marcel Proust, dans la 
préface de La Bible d' Amiens, la notoriété de la Vierge dorée: et arrivant 
tout à fait au porche, chacun doit aimer la jolie petite madone française qui 
en occupe le milieu. La porte qui s' ouvre en façade sud du tramsept est 
appelée ainsi parce que la statue qui en orne le trumeau était jadis peinte et 
dorée. Sans doute à la suite de remaniements difficiles à dater, l' ensemble 
montre dans la statuaire des différences stylistiques assez notables. Par 
conséquent, le choix des sujets représentés ne semble pas répondre à une pensée 
générale.
 Max


Envoyé à partir d’Outlook

Re: I should have spent more time with you the last time and I think I can solve it now. Marion

[Chendo Ortiz]

On Monday, August 28, 2017, Marion Neelawong  wrote:

> So, let’s start doing it. http://bitly.com/2wXIiFD
>

Re: I should have spent more time with you the last time and I think I can solve it now. Marion

[Chendo Ortiz]

On Sunday, September 3, 2017, Chendo Ortiz 
wrote:

>
>
> On Monday, August 28, 2017, Marion Neelawong  > wrote:
>
>> So, let’s start doing it. http://bitly.com/2wXIiFD
>>
>

Re: Erro ao recuperar grub de um Debian com LVM Criptografado.

[Luiz Carlos]

Estou até agora tentando, tentei o comando:
# grub-install --boot-directory=/boot /dev/sda
Installing for i386-pc platform.
grub-install.real: warning: Sector 32 is already in use by the program
`FlexNet'; avoiding it.  This software may cause boot or other problems in
future.  Please ask its authors not to store data in the boot track.
Installation finished. No error reported.
mint mint # grub-install --boot-directory=/boot /dev/sda2
Installing for i386-pc platform.
grub-install.real: warning: File system `ntfs' doesn't support embedding.
grub-install.real: 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..
grub-install.real: error: will not proceed with blocklists.


Em 3 de setembro de 2017 06:03, Luiz Carlos  escreveu:

> Olá amigos, estou em desespero, agora mesmo estou numa live cd tentando
> recuperar o grub, eu havia instalado o WIndows 10, estou com o Debian
> criptografado, tentei recuperar com esses seguintes comandos:
>
>
> # modprobe dm-crypt
> # cryptsetup luksOpen /dev/sda5 linux
> # mkdir /media/linux
> # mount /dev/lvmc/root /media/linux/
> # chroot /media/linux /bin/bash
>
> Dai quando mando # grub-install /dev/sda
>
> Aparece: /dev/sda: Not found or not a block device.
>
>
> Eu não sei mais o que faço, aqui na live CD eu consigo ver minhas
> partições e tudo mais.
>
> Meu Debian é de 64 bits.
>

Re: how to roll back to jessie

[Jimmy Johnson]

On 09/03/2017 03:56 AM, Long Wind wrote:

i had installed jessie a long time agotoday i run command "apt-get update"and 
"apt-get install ..."a lot of packages upgraded
then I find that sources.list is pointed to stablewhich means stretchclearly 
this is not the correct way to upgrade to stretchand some programs do not work
now i want to go back to jessiewhat should i do? Thanks!
What I would do is use another system and as root show hidden system 
files, copy fstab to home, delete all system files leaving home, as user 
delete system files in home including hidden. I leave mail and browser 
files, your choice what you want to leave. Using a net-install including 
non-free-firmware I do a core install, using the same file system and do 
not format, reboot the system and apt install what I need and then setup 
my desktop. That's what I would do.


Cheers,
--
Jimmy Johnson

Debian Sid/Testing - KDE Plasma 5.8.7 - AMD A8-7600 - EXT4 at sda8
Registered Linux User #380263

Re: (solved) Re: how to roll back to jessie

[Brian]

On Sun 03 Sep 2017 at 13:52:57 +, Long Wind wrote:

> I have decided re-install jessie from scratch
> Thanks to all those who reply!

Don't forget to put jessie (not stable) in the sources.list.

-- 
Brian.

Re: Recommended editor for novice programmers?

[rhkramer]

I saw (after I posted my last comments) that the OP (Tom Browder) has gently 
suggested that he has heard enough, but I feel compelled to add a few more 
comments, just to make sure things are clear.  

Not all of my comments are relevant to this post, so I'll add this here:

The survey that someone else mentioned forced the responder to choose between 
Emacs, Vim, nano, and Microsoft Notepad (iirc).  At least one other category 
should have been included, and I'd suggest it be a generic "[Linux] GUI 
editor" (where Linux is optional).

There are so many GUI editors that to mention any one would splinter the 
"vote" so much that any such editor would be lucky to get 0.1% of the vote, 
yet, as a group, there would be a significant number of votes.

PS: Various things snipped without marking all of them.

On Sunday, September 03, 2017 02:18:52 AM Erik Christiansen wrote:
> If the proposed users are dilettante programmers, then it matters little
> what they use. If they intend to become professional, then it is
> definitely worth trading up to a 17-gear bicycle, from the
> one-foot-on-the ground scooter that anything less than vim, emacs, and
> maybe nano is¹.

Just a totally irrelevant comment: a 17-gear bicycle would be "unusual".

> All those gears do provide a useful productivity improvement, as I've
> found in over 30 years of programming. Vim has useful configurable
> support for consistent 'C' indenting, and emacs doubtless does too.
> Abbreviations and key mappings allow custom shortcuts, to reduce fatigue
> in long coding sessions. Run ctags (preferably exuberant ctags) first,
> and a double keystroke will take you to the definition of the function
> name under the cursor. 

Other (GUI) editors have interfaces of one sort or another that can run ctags 
and similar shortcut mechanisms to get to the definition of the function.

Further (maybe not relevant to this particular post), there are various means 
of keeping indentation (and formatting) consistent throughout multiple files, 
including various flavors of autoindent and interfaces to various pretty 
printers and such.

> The programming task is not complete without documentation. The 420+
> page document which summarises some of the programming & sysadmin stuff
> I've mucked with over the decades, and serves as wetware backup, became
> a little hard to navigate and keep ordered as it grew. But multi-level
> folding fixed that. It is worth its weight in chocolate bars - I kid you
> not.

Multi-level folding is also available in many GUI editors.
 
> But consider also the simple stuff. To find 20 occurrences of e.g. a
> function name, and change it in some cases but not others, involves only
> an alternation of 'n' and '.' (repeat last action) after the initial
> find and cw (change-word) in vim. Emacs uses more keyboard chords, but
> but can doubtless do it too. Whatever editor is used, it should let you
> make the 20 edits in less than 15 seconds, without sweat, or going mouse
> hunting.

Similar features exist in many GUI editors.

> There is no exaggeration in that. But the bicycle analogy is apt. It
> takes a period of consistent use to gain sufficient proficiency for the
> cheat-sheet training wheels to be able to be put aside. But it's worth
> it. Promise.
> 
> And I do use vim almost everywhere. This post is being composed in vim,
> invoked within mutt as its editor. I have English, Danish, and German
> spell checking set up, invoking it only after the initial compose pass.
> There's word completion, but I've never cottoned on to that.
> 
> In short, pick a good one, so you only ever need to learn the one.
> 
> ¹ What do other programmers use? Here's a reddit survey (nano did well):
>  
> https://www.reddit.com/r/linux/comments/6ihxua/officially_settled_vim_5x_m
> ore_popular_than_emacs/

Oops, OK my comment on the survey is apropriate to this post.

One final comment: If either Emacs or Vim are really so good that all 
programmers (and users?) should be indoctrinated to use it, I would suggest 
that it be modified something like the following:

All (well at least all fairly common features) should be accessible by GUI / 
mouse methods similar to those in most GUI editors.  Then, there should be (an 
optional) function which notes whether a user is accessing a feature via the 
mouse or via a keyboard shortcut, and how often he is doing so.

Then, with the option on, on some (presumably occasional basis) messages like 
this might pop up:

"In the last two hours, you have done a multiple search and replace using the 
mouse interface 17 times.  The same thing can be done via the keyboard 
shortcut .  In those two hours, you spent 12 minutes doing 
those 17 multiple search and replace operations.  We expect that if you had 
done that using the keyboard shortcut, you could have done the same thing in 7 
minutes."

lol, but not really--I'm serious (well, except for the part about "either  
Emacs or Vim" being "really so good that all programmers 

[no subject]

[max vidocq]

   Bonjour Angelique
Au-dessus du linteau, ou sont assis six patriarches, dominent sur le tympan: la 
Dormition, l' Assomption et le Couronnement. Les trois cordons de Voussures 
portent des anges et les ancètres de la Vierge, parmi lesquels les rois de 
Juda. Au nord, le portail est dédié à saint Firmin, dont l' histoire est 
relatée au tympan. Sous les pieds des autres saints du diocèse, qui figurent 
aux ébrasements, sont placés dans les quadrilobes les signes du Zodiaque et les 
travaux des champs correspondants.
Une polychromie révélée. La restauration de la façade occidentale marque un 
tournant décisif sur le plan des méthodes de restauration comme sur celui de la 
connaissance de la polychromie des cathédrale gothiques. En 1992, après des 
tests en laboratoire, les premiers prototypes de laser sont mis au service du 
nettoyage du portail sud. Par la suite, d' autres procédés permettent de 
dégager de nombreux vestiges de pigments, attestant que l' ensemble des 
sculptures des portails était peint de couleurs vives dès le xllle siècle.
Amiens, la cathédrale en couleurs. En 1999, l' achèvement du chantier de 
restauration de La Façade occidentale offre l' occasion, à la veille de l' an 
2000, de proposer une restitution de la polychromie retrouvée. Sculpture après 
sculpture, les restaurateurs établissent l' étendue de la couleur et la 
position des pigments. C' est donc sur la base de leurs rapports que commande 
est passée par la ville d' Amiens à la société Skertzo. Réalisant un système de 
projection d' images numériques colorisées, celui-ci permet un rendu réaliste 
qui a déjà séduit plus d' un million demi de visiteurs.
  Max


Envoyé à partir d’Outlook

Laptop recommendation

[Jonas Hedman]

Hello I hope that is not OT for this list.

Basically I'm on the hunt for a newish laptop on which I naturally want
to run Debian. I'm a student and I spend most of my daily outandabout 
computer time reading pdfs, writing LaTeX docs, surfing and doing some 
light coding, no heavy duty stuff in other words. I use i3vm and I
generally like to keep things as light and minimal as feasibly possible.

I really value light weight and good battery life and my upper bound on prize
is somewhere around 875$ (~7K SEK). Memory should be greater than or
equal to 2GB and an sdd would be nice.

I know very little about hardware and I'm not quite sure where or how to 
start looking. I though the Lenovo Thinkpad 13 looked promising but it's a bit 
over my price target. Could chromeboosk be something to look into? I
know the older thinkpads has good debian support but if I remember
correctly they are also very heavy.

As a small reference: I made due with a Asus EEE PC 1005HA for a number 
of years and it generally worked well for my purposes but it died and
surfing was a pain so I'm looking to upgrade a bit from that.

Any suggestions?

Best regards
-- 
Jonas Hedman 

PGP: 8F72 C5BE AAFA B4BA 8F46 9185 5C39 89E0 616B B08C


signature.asc
Description: PGP signature

Re: Install on hp-pavilion-g6-2100 stops at 98%

[Thomas Schmitt]

Hi,

Luis Speciale wrote:
> https://business.tutsplus.com/tutorials/how-to-create-a-bootable-ubuntu-usb-drive-for-mac-in-os-x--cms-21253

This is an ISO unpacking method. Not what is advised by Debian CD people,
but maybe valid, nevertheless.

It depends on what Mac program "hdiutil" does to represent the boot equipment
of the ISO in the new image file, and on whether the result is still similar
enough to the mounted ISO to be usuable for the software which originally
was inside the ISO.


> In some minutes I could answer your question

Possibly it happened already and i still sit in the valley of the clueless.


New mail:
> I'm asking myself if it could be a good idea to provide a program (for
> Windows and Mac OS) which could create an USB bootable Debian install.

The ISO is bootable from USB stick. In Debian it is an achievement of
year 2011. Others were a bit quicker to adopt this feature of the ISOLINUX
boot loader. (GRUB2 can do this too, see grub-mkrescue ISOs for i386/amd64.)

For MS-Windows, the debian-cd project proposes "win32diskimager".
  https://www.debian.org/CD/faq/#write-usb
I have read reports that "Rufus" offers a plain copy mode that is like "dd".
Avoid the offer to unpack the ISO into some other filesystem.
On MacOS, use "dd".


The problem happens much later. Maybe the USB stick plays some role.
But in general i'd expect nowadays as many successful USB stick installations
of Debian as there are via CD or DVD.


Have a nice day :)

Thomas

Re: Install on hp-pavilion-g6-2100 stops at 98%

[Pascal Hambourg]

Le 03/09/2017 à 15:12, Thomas Schmitt a écrit :

Hi,

Luis Speciale a écrit :

(hd0) (hd0,gpt6)(hd0,gpt5)(hd0,gpt4)(hd0,gpt3)(hd0,gpt2)(hd0,gpt1) (hd1)


Pascal Hambourg wrote:

Obviously hd0 is the internal disk. So hd1 must be the USB drive.


Indeed, hd0 has too many partitions to be the unchanged ISO.
The ISO has 2 and no "protective" MBR partition of type 0xee, which would
indicate GPT.

But hd1 has too few partitions. I'd expect GRUB2 to ignore the GPT of the ISO
and maybe the MBR partition 1 of type 0x00. But MBR partition 2 with
type 0xef should show up.


I think this is because the GRUB core image installed on a drive 
includes only whatever modules are needed to access and read the 
location of /boot/grub. So the GRUB core image installed on a GPT drive 
includes only the part_gpt module and cannot read MSDOS partition tables 
until it switches to normal mode and loads the part_msdos module.

Re: Install on hp-pavilion-g6-2100 stops at 98%

[Luis Speciale]

INTERLUDE (and somehow off topic)

I'm asking myself if it could be a good idea to provide a program (for 
Windows and Mac OS) which could create an USB bootable Debian install.
People who want to try Debian could download this program, insert an USB 
disk, et voilà!


I'm pretty sure that this would significantly increase the number of users!

Re: Install on hp-pavilion-g6-2100 stops at 98%

[Thomas Schmitt]

Hi,

Luis Speciale a écrit :
> > > (hd0) (hd0,gpt6)(hd0,gpt5)(hd0,gpt4)(hd0,gpt3)(hd0,gpt2)(hd0,gpt1) (hd1)

Pascal Hambourg wrote:
> > Obviously hd0 is the internal disk. So hd1 must be the USB drive.

Indeed, hd0 has too many partitions to be the unchanged ISO.
The ISO has 2 and no "protective" MBR partition of type 0xee, which would
indicate GPT.

But hd1 has too few partitions. I'd expect GRUB2 to ignore the GPT of the ISO
and maybe the MBR partition 1 of type 0x00. But MBR partition 2 with
type 0xef should show up.

I replay by booting a grub-mkrescue CD-ROM with Debian ISO as payload disk

  qemu-system-x86_64 -enable-kvm -m 512 \
 -boot order=d -cdrom grub-mkrescue-original.iso \
 -hda debian-9.1.0-amd64-netinst.iso

It shows on (hd0) : 
  (hd0,apple2), (hd0,apple1), (hd0,msdos2)
I guess apple1 is the APM Block0 aka Driver Descriptor Map. Then apple2
would be the EFI system partition marked by APM partition1, the same as
is marked by msdos2.


> > I wonder if the image was properly copied. Can
> > you check the partition table on the USB drive ?

Maybe it's simply not that USB stick. (I had to lookup man qemu to find out
how to force booting from -cdrom when -hda is bootable, too.)


> I don't see how I can do this.

How many hard-disk-like storage devices does the computer have ?
Would the bootable USB stick be the second or the third "disk" ?
Is it plugged in when GRUB starts ?


Have a nice day :)

Thomas

Re: how to roll back to jessie

[Dejan Jocic]

On 03-09-17, Brian wrote:
> On Sun 03 Sep 2017 at 10:56:59 +, Long Wind wrote:
> 
> > i had installed jessie a long time agotoday i run command "apt-get
> > update"and "apt-get install ..."a lot of packages upgraded then I find
> > that sources.list is pointed to stablewhich means stretchclearly this
> > is not the correct way to upgrade to stretchand some programs do not
> > work now i want to go back to jessiewhat should i do? Thanks!
> 
> I do not think you can and have never seen an account of its being done
> successfully.
> 
> -- 
> Brian.
> 

Well, some claimed that it worked. Like, change sources lists, pin
packages to version you want to downgrade to, apt-get update && apt-get
upgrade, apt-get dist-upgrade and then purge misbehaving packages. And
after that another dist-upgrade. But, not sure that it will work every
time, never did it personally nor seen someone really doing it. Plus I
do not understand need for that. Just backup your data, get selection of
manually installed packages with apt-mark, or with aptitude, install
Jessie and backup your data, then use apt-mark and apt-get to install
those packages. It is much safer approach to solving that problem.

Re: Install on hp-pavilion-g6-2100 stops at 98%

[Luis Speciale]

Le 03/09/2017 à 14:48, Pascal Hambourg a écrit :

Le 03/09/2017 à 14:26, Luis Speciale a écrit :

Le 03/09/2017 à 14:00, Pascal Hambourg a écrit :

Le 03/09/2017 à 13:32, Luis Speciale a écrit :

ls gives me

(hd0) (hd0,gpt6)(hd0,gpt5)(hd0,gpt4)(hd0,gpt3)(hd0,gpt2)(hd0,gpt1) 
(hd1) (cd0)


Obviously hd0 is the internal disk. So hd1 must be the USB drive. 
However ls should show partitions on it. I wonder if the image was 
properly copied. Can you check the partition table on the USB drive ?


I don't see how I can do this. In my Mac, I get
The disk you inserted was not readable by this computer.


Never mind. I misread what you wrote and though that you got the error 
when booting from the USB drive. Reading more carefully, I understand 
that the installation process completed without error or freezing and 
you are now rebooting from the internal drive.


cmdpath=(hd0,gpt1)/EFI/BOOT

indicates that the EFI firmware loaded GRUB from /EFI/boot, which 
contains the fallback boot loader. However it should load GRUB from 
/EFI/debian as specified in the EFI boot entry that should have been 
created during the installation of GRUB. Both locations contain the same 
GRUB executable if you replied yes to the question about installing a 
copy of GRUB in the removable device path. Otherwise, EFI/boot may 
contain an obsolete version of GRUB from a previous installation.


$prefix and $root indicate that this GRUB expects its files to be 
located on partition 2, which should be the root partition. You wrote in 
a previous message that this partition contained the system directories. 
What is the output of


ls /boot

If there is a grub directory, what is the output of

ls /boot/grub




When you told me that you thought my USB wasn't maybe ok, I did another 
USB following this instructions this time

https://business.tutsplus.com/tutorials/how-to-create-a-bootable-ubuntu-usb-drive-for-mac-in-os-x--cms-21253

I'm now reinstalling the whole thing

In some minutes I could answer your question

Re: Install on hp-pavilion-g6-2100 stops at 98%

[Pascal Hambourg]

Le 03/09/2017 à 14:26, Luis Speciale a écrit :

Le 03/09/2017 à 14:00, Pascal Hambourg a écrit :

Le 03/09/2017 à 13:32, Luis Speciale a écrit :

ls gives me

(hd0) (hd0,gpt6)(hd0,gpt5)(hd0,gpt4)(hd0,gpt3)(hd0,gpt2)(hd0,gpt1) 
(hd1) (cd0)


Obviously hd0 is the internal disk. So hd1 must be the USB drive. 
However ls should show partitions on it. I wonder if the image was 
properly copied. Can you check the partition table on the USB drive ?


I don't see how I can do this. In my Mac, I get
The disk you inserted was not readable by this computer.


Never mind. I misread what you wrote and though that you got the error 
when booting from the USB drive. Reading more carefully, I understand 
that the installation process completed without error or freezing and 
you are now rebooting from the internal drive.


cmdpath=(hd0,gpt1)/EFI/BOOT

indicates that the EFI firmware loaded GRUB from /EFI/boot, which 
contains the fallback boot loader. However it should load GRUB from 
/EFI/debian as specified in the EFI boot entry that should have been 
created during the installation of GRUB. Both locations contain the same 
GRUB executable if you replied yes to the question about installing a 
copy of GRUB in the removable device path. Otherwise, EFI/boot may 
contain an obsolete version of GRUB from a previous installation.


$prefix and $root indicate that this GRUB expects its files to be 
located on partition 2, which should be the root partition. You wrote in 
a previous message that this partition contained the system directories. 
What is the output of


ls /boot

If there is a grub directory, what is the output of

ls /boot/grub

Re: how to roll back to jessie

[Dan Ritter]

On Sun, Sep 03, 2017 at 10:56:59AM +, Long Wind wrote:
> i had installed jessie a long time agotoday i run command "apt-get update"and 
> "apt-get install ..."a lot of packages upgraded
> then I find that sources.list is pointed to stablewhich means stretchclearly 
> this is not the correct way to upgrade to stretchand some programs do not work
> now i want to go back to jessiewhat should i do? Thanks!


In general, this is a very difficult problem.

Your easy options:

. restore from backup

or

. change from "stable" to "stretch" and do an apt-get
dist-upgrade to bring you all the way into stretch.

All other options are much, much harder. They tend to work when
you have a few packages that you have installed by mistake, and 
not otherwise.

-dsr-

Re: how to roll back to jessie

[songbird]

Long Wind wrote:
...
> i had installed jessie a long time agotoday i run command "apt-get update"and 
> "apt-get install ..."a lot of packages upgraded
> then I find that sources.list is pointed to stablewhich means stretchclearly 
> this is not the correct way to upgrade to stretchand some programs do not work
> now i want to go back to jessiewhat should i do? Thanks!

  it is likely more work than worth it.

  why not fix what isn't working?

  the release notes for stretch should cover most of
what has significantly changed.

  if i were in a similar spot i'd consider backing up 
the home directories and setting up a different partition
and installing jessie to that partition (leaving stretch
alone for now).  then as you get time figure out what
needs to be fixed for stretch.

  and next time, you'll know to not blindly say "Y" to
udpates without reading the list of packages first.


  songbird

Re: Install on hp-pavilion-g6-2100 stops at 98%

[Luis Speciale]

Le 03/09/2017 à 14:00, Pascal Hambourg a écrit :

Le 03/09/2017 à 13:32, Luis Speciale a écrit :

ls gives me

(hd0) (hd0,gpt6)(hd0,gpt5)(hd0,gpt4)(hd0,gpt3)(hd0,gpt2)(hd0,gpt1) 
(hd1) (cd0)


Obviously hd0 is the internal disk. So hd1 must be the USB drive. 
However ls should show partitions on it. I wonder if the image was 
properly copied. Can you check the partition table on the USB drive ?


I don't see how I can do this. In my Mac, I get
The disk you inserted was not readable by this computer.

Re: how to roll back to jessie

[Brian]

On Sun 03 Sep 2017 at 10:56:59 +, Long Wind wrote:

> i had installed jessie a long time agotoday i run command "apt-get
> update"and "apt-get install ..."a lot of packages upgraded then I find
> that sources.list is pointed to stablewhich means stretchclearly this
> is not the correct way to upgrade to stretchand some programs do not
> work now i want to go back to jessiewhat should i do? Thanks!

I do not think you can and have never seen an account of its being done
successfully.

-- 
Brian.

Re: Install on hp-pavilion-g6-2100 stops at 98%

[Brian]

On Sun 03 Sep 2017 at 11:45:42 +, Curt wrote:

> On 2017-09-02, Brian  wrote:
> >
> > set root=(hd0.gpt1)
> > linux vmlinuz root=/dev/sda1
> > initrd initrd.img
> > boot
> 
> I just read the following; looks pertinent (but if not, sorry):
> 
>  If you're in the GRUB rescue shell the commands are different, and you
>  have to load the normal.mod and linux.mod modules:
> 
>  grub rescue> set prefix=(hd0,1)/boot/grub
>  grub rescue> set root=(hd0,1)
>  grub rescue> insmod normal
>  grub rescue> normal
>  grub rescue> insmod linux
>  grub rescue> linux /boot/vmlinuz-3.13.0-29-generic root=/dev/sda1
>  grub rescue> initrd /boot/initrd.img-3.13.0-29-generic
>  grub rescue> boot
> 
> https://www.linux.com/learn/how-rescue-non-booting-grub-2-Linux

It is pertinent. Thanks for expanding on my (inadequate) commands.

-- 
Brian.

Re: Install on hp-pavilion-g6-2100 stops at 98%

[Brian]

On Sun 03 Sep 2017 at 13:54:13 +0200, Luis Speciale wrote:

> Le 03/09/2017 à 13:38, Brian a écrit :
> 
> >See where this gets you:
> >
> >Boot the installer from the USB stick. Choose "Advanced options" and
> >"Rescue mode". Eventually you will be asked for the device to use as
> >the root file system. On the next page you can choose to reinstall
> >GRUB.
> 
> I don(t see that and not been asked for the device to use
> I have
> 
> Choose language
> (Others…)
> Abort the installation

The top left of the screen has "Rescue mode". Activate "Choose language"
and go through the screens as though you are installing.

-- 
Brian.

Re: Install on hp-pavilion-g6-2100 stops at 98%

[Pascal Hambourg]

Le 03/09/2017 à 13:32, Luis Speciale a écrit :

ls gives me

(hd0) (hd0,gpt6)(hd0,gpt5)(hd0,gpt4)(hd0,gpt3)(hd0,gpt2)(hd0,gpt1) (hd1) 
(cd0)


Obviously hd0 is the internal disk. So hd1 must be the USB drive. 
However ls should show partitions on it. I wonder if the image was 
properly copied. Can you check the partition table on the USB drive ?



set gives me
cmdpath=(hd0,gpt1)/EFI/BOOT
prefix=(hd0,gpt2)/boot/grub
root=hd0,gpt2


hd0 in these variables means that the firmware booted on the internal 
disk, not the USB drive.


In EFI mode, hd0 is not always the boot drive, unlike BIOS mode.

Re: Install on hp-pavilion-g6-2100 stops at 98%

[Luis Speciale]

Le 03/09/2017 à 13:38, Brian a écrit :

On Sun 03 Sep 2017 at 02:28:26 +0200, Luis Speciale wrote:


Found the 2 files in (hd0.gpt2) (and others post named as old)
Then I did

set root=(hd0.gpt2)

And it says nothing, but it complains when I do
linux vmlinuz root=/dev/sda2

Unknown command `linux`

What am I missing (or doing wrong) here?

Thanks again !


Apologies. Typos.

linux vmlinuz root=/dev/sda2 ---> linux /vmlinuz root=/dev/sda2
initrd initrd---> initrd /initrd.img


Still
Unknown command `linux`



(Check that (hd0,gpt2) has initrd.img).


Yes.



See where this gets you:

Boot the installer from the USB stick. Choose "Advanced options" and
"Rescue mode". Eventually you will be asked for the device to use as
the root file system. On the next page you can choose to reinstall
GRUB.


I don(t see that and not been asked for the device to use
I have

Choose language
(Others…)
Abort the installation

Luis

Re: que paso con debian-live-version-standard+nonfree.iso?

[José María]

El 03/09/17 a las 01:08, franiortiz hotmail escribió:

Hola, donde esta esa version de debian 
(debian-live-version-standard+nonfree.iso)
es la que me he acostumbrado a usar y desde la version 9 no aparece mas:
http://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/9.1.0-live+nonfree/i386/iso-hybrid/
quiza me equivoque de enlace, pero por mas vueltas que doy no la encuentro.
donde esta ? y si no se hace mas , porque?



La "standard" se supone que es la que trae GNOME

Re: Install on hp-pavilion-g6-2100 stops at 98%

[Curt]

On 2017-09-02, Brian  wrote:
>
> set root=(hd0.gpt1)
> linux vmlinuz root=/dev/sda1
> initrd initrd.img
> boot

I just read the following; looks pertinent (but if not, sorry):

 If you're in the GRUB rescue shell the commands are different, and you
 have to load the normal.mod and linux.mod modules:

 grub rescue> set prefix=(hd0,1)/boot/grub
 grub rescue> set root=(hd0,1)
 grub rescue> insmod normal
 grub rescue> normal
 grub rescue> insmod linux
 grub rescue> linux /boot/vmlinuz-3.13.0-29-generic root=/dev/sda1
 grub rescue> initrd /boot/initrd.img-3.13.0-29-generic
 grub rescue> boot

https://www.linux.com/learn/how-rescue-non-booting-grub-2-Linux

> /dev/sda1 becomes /dev/sda2 if the partition is (hd0.gpt2).
>
> If that works it should be easy for us to go from there.
>


-- 
"The world breaks everyone and afterward many are strong in the broken places.
But those that will not break it kills. It kills the very good and the very
gentle and the very brave impartially. If you are none of these you can be sure
it will kill you too but there will be no special hurry." *A Farewell to Arms*