Re: Laptop randomly reboots

[Sam Smith]

On 08/28/2017 03:32 PM, Sam Smith wrote:

On 06/13/2017 02:27 PM, Sam Smith wrote:

On 05/12/2017 03:38 PM, Sam Smith wrote:

On 01/20/2017 08:04 PM, Sam Smith wrote:
I'll try to keep this short. I bought a used Lenovo T520 back in 
May. It

had the motherboard with nvidia GPU. Because it sucks power and doesn't
really have good suspend/resume support, I bought a used mother board
off of ebay that only had intel integrated graphics and I swapped it
out. All was well and I had installed in it 8gb +4gb of ram.

It ran like that for about 8 weeks before I bought an 8gb stick and
stuck that in, so then I had 8gb + 8gb of ram. After about 6 weeks of
running like, it randomly rebooted overnight. I shrugged it off and
thought maybe the power went out or something (even though it had a
battery in it). But then about 2 weeks later it did it again..and then
two weeks after that. So I pulled out the new 8gb stick I had put in 
and

let it run with just one 8gb stick. It ran like that for about 10 weeks
without a problem. I put the old 4gb stick in just for fun, bringing it
back to the original 8gb + 4gb configuration. But about 2 weeks 
later it

rebooted again. At that point I bought a matched 16gb kit (8gb + 8gb)
from new egg that seemed to come recommended from google searching for
compatible ram for this model. But just a couple of days ago (about 3
weeks after installing it), it rebooted by itself.

I am kind of at a loss here now. I can buy another motherboard and swap
it out again, but that takes a few hours and I don't feel like doing 
it.
The cooling and thermal stuff is all good on the laptop,I've ran 
prime95

and video encoding for hours and it is fine (temps stay below 80* at
least, normal usage is 40-55*). I've also ran memtest for a few hours.

What I find weird is that the machine suddenly reboots. At least a few
years ago, ram issues would just lead to a kernel panic screen. But 
with

this, the machine is just like someone pulled the plug and rebooted it.
I started to wonder if there is some built in watchdog somewhere that
will reboot the machine if it hangs, but I can't tell? Other than that,
if this is the kernel that is rebooting the machine, is there any way I
can get it to dump some info somewhere before it fully reboots? 
Before I
go through the pain of swapping the board again, I'd just like to 
really

know that this is a hardware issue and not the kernel detecting
something and just choosing to reboot...

Thanks for any info,

Sam



Just an update. My uptime is now 80 days and I haven't had any random
reboots. The only thing I did was pull in the latest apt-get updates
(which took me from Jessie 6.6 to 6.7 I think, but also installed a
newer xorg-intel driver from backports). I also read somewhere that
there were some "issues" with having the hardware virtualization
extensions enabled in BIOS (can't remember what the issues were) so I
disabled those after running the apt-get upgrade and rebooting.

Never gone this long without a reboot so I guess perhaps I'm good. But
if this was indeed a software caused reboot, I'd like to know what
setting I need to change so that debian would just hang at a kernel
panic screen (or something similar) instead of just an instant dump and
reboot leaving me thinking that it is hardware issues (which it may
still be)


Regards,
Samuel Smith




Guess I spoke too soon. About 10 days after I posted the above, the 
laptop randomly rebooted. :sigh:






And for my hopefully final update. I upgraded from jessie to stretch 
and about 2 weeks after that I got a random reboot. Figured that ruled 
out any software issue. Went ahead and bought a new board off of ebay 
and judging by the lack of a serial number in the bios screen, I'd say 
it was from an old stock pile destined for RMA warranty repairs. 
Nonetheless, after a month of swapping the board, I've not had any 
further problems.






Well I guess I really spoke too soon Just got a random reboot a 
minute ago... Pretty much at a loss now. The only thing that hasn't been 
replaced now is the CPU, battery, and power adapter. I do have a spare 
battery and power adapter. Guess I'll try running with those for a month 
or so and see what happens. Though not really sure how either one of 
those would make the computer reboot randomly once a month. Laptop is 
mounted in a docking station. At least for the last 6 months, every 
reboot was while it was docked. But I do remember times last year 
sitting at the kitchen table undocked and getting a reboot so I don't 
think the docking station is the issue.. But have no idea now :/


Regards,

Re: Répéteur wifi

[Cyrille]

Bsr,
jette un oeil là
http://www.ldlc.com/fiche/PB00168684.html

++
C

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

[Glenn English]

On Mon, Sep 4, 2017 at 4:16 AM, Long Wind  wrote:
> Thanks!
>
> I finds today that it's really not jessie
> it's wheezy
>
> it seems that wheezy is not too old for me


Wheezy works good. Reliable piece of software. That's what's on my server.

Jessie's OK. One of my virtual websites didn't work -- don't know why
or who was to blame. Wheezy works good, as I find I've said before.

Stretch sux, big time. I had far too many troubles with that one.

But you might take a look at Buster. I installed it on a new laptop in
the past few days, and it's looking reasonably civilized.


--
Glenn English

Re: [testing] Gnome Evolution / problème de certificat Orange

[Gaëtan Perrier]

Le mardi 05 septembre 2017 à 00:23 +0200, jérémy prego a écrit :
> > 
> 
> Le 05/09/2017 à 00:20, Gaëtan Perrier a écrit :
> > Le lundi 04 septembre 2017 à 23:55 +0200, Ph. Gras a écrit :
> > > Salut,
> > > 
> > > > Avec Evolution, j'ai régulièrement des messages d'erreur de certificat
> > > > avec
> > > > les
> > > > comptes Orange (en imap). J'ai le message suivant:
> > > > 
> > > > «Le certificat ne correspond pas à l'identité attendue du site duquel
> > > > il
> > > > provient.»
> > > 
> > > tu peux tester les domaines concernés ainsi :
> > > openssl s_client -host www.avoirun.com -port 443 -prexit
> > 
> > J'ai tenté un :
> > 
> > openssl s_client -host imap.orange.fr -port 143 -prexit
> 
> moi je tenterai sur le port 993
> 
> jerem


Effectivement ça semble mieux fonctionner sur ce port ...

Gaëtan

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

Re: [testing] Gnome Evolution / problème de certificat Orange

[jérémy prego]

Le 05/09/2017 à 00:20, Gaëtan Perrier a écrit :

Le lundi 04 septembre 2017 à 23:55 +0200, Ph. Gras a écrit :

Salut,


Avec Evolution, j'ai régulièrement des messages d'erreur de certificat avec
les
comptes Orange (en imap). J'ai le message suivant:

«Le certificat ne correspond pas à l'identité attendue du site duquel il
provient.»

tu peux tester les domaines concernés ainsi :
openssl s_client -host www.avoirun.com -port 443 -prexit

J'ai tenté un :

openssl s_client -host imap.orange.fr -port 143 -prexit


moi je tenterai sur le port 993

jerem

CONNECTED(0003)
140165697930496:error:1408F10B:SSL routines:ssl3_get_record:wrong version
number:../ssl/record/ssl3_record.c:252:
---
no peer certificate available
---
No client certificate CA names sent
---
SSL handshake has read 5 bytes and written 176 bytes
Verification: OK
---
New, (NONE), Cipher is (NONE)
Secure Renegotiation IS NOT supported
Compression: NONE
Expansion: NONE
No ALPN negotiated
SSL-Session:
 Protocol  : TLSv1.2
 Cipher: 
 Session-ID:
 Session-ID-ctx:
 Master-Key:
 PSK identity: None
 PSK identity hint: None
 SRP username: None
 Start Time: 1504563284
 Timeout   : 7200 (sec)
 Verify return code: 0 (ok)
 Extended master secret: no
---
---
no peer certificate available
---
No client certificate CA names sent
---
SSL handshake has read 5 bytes and written 176 bytes
Verification: OK
---
New, (NONE), Cipher is (NONE)
Secure Renegotiation IS NOT supported
Compression: NONE
Expansion: NONE
No ALPN negotiated
SSL-Session:
 Protocol  : TLSv1.2
 Cipher: 
 Session-ID:
 Session-ID-ctx:
 Master-Key:
 PSK identity: None
 PSK identity hint: None
 SRP username: None
 Start Time: 1504563284
 Timeout   : 7200 (sec)
 Verify return code: 0 (ok)
 Extended master secret: no
---


Que pensez-vous de l'erreur au début ?


(D'ailleurs, ce domaine a un problème actuellement…)

Ou vérifier la conformité du certificat ici :
https://www.ssllabs.com/ssltest/analyze.html?d=www.avoirun.com

(Là, c'est bizarre il n'en a plus !)


Quant à:
https://www.ssllabs.com/ssltest/analyze.html?d=imap.orange.fr
ça trouve 10 serveurs auquel il est incapable de se connecter ...

Gaëtan

Re: [testing] Gnome Evolution / problème de certificat Orange

[Gaëtan Perrier]

Le lundi 04 septembre 2017 à 23:55 +0200, Ph. Gras a écrit :
> Salut,
> 
> > Avec Evolution, j'ai régulièrement des messages d'erreur de certificat avec
> > les
> > comptes Orange (en imap). J'ai le message suivant:
> > 
> > «Le certificat ne correspond pas à l'identité attendue du site duquel il
> > provient.»
> 
> tu peux tester les domaines concernés ainsi :
> openssl s_client -host www.avoirun.com -port 443 -prexit

J'ai tenté un :

openssl s_client -host imap.orange.fr -port 143 -prexit
CONNECTED(0003)
140165697930496:error:1408F10B:SSL routines:ssl3_get_record:wrong version
number:../ssl/record/ssl3_record.c:252:
---
no peer certificate available
---
No client certificate CA names sent
---
SSL handshake has read 5 bytes and written 176 bytes
Verification: OK
---
New, (NONE), Cipher is (NONE)
Secure Renegotiation IS NOT supported
Compression: NONE
Expansion: NONE
No ALPN negotiated
SSL-Session:
Protocol  : TLSv1.2
Cipher: 
Session-ID: 
Session-ID-ctx: 
Master-Key: 
PSK identity: None
PSK identity hint: None
SRP username: None
Start Time: 1504563284
Timeout   : 7200 (sec)
Verify return code: 0 (ok)
Extended master secret: no
---
---
no peer certificate available
---
No client certificate CA names sent
---
SSL handshake has read 5 bytes and written 176 bytes
Verification: OK
---
New, (NONE), Cipher is (NONE)
Secure Renegotiation IS NOT supported
Compression: NONE
Expansion: NONE
No ALPN negotiated
SSL-Session:
Protocol  : TLSv1.2
Cipher: 
Session-ID: 
Session-ID-ctx: 
Master-Key: 
PSK identity: None
PSK identity hint: None
SRP username: None
Start Time: 1504563284
Timeout   : 7200 (sec)
Verify return code: 0 (ok)
Extended master secret: no
---


Que pensez-vous de l'erreur au début ?

> 
> (D'ailleurs, ce domaine a un problème actuellement…)
> 
> Ou vérifier la conformité du certificat ici :
> https://www.ssllabs.com/ssltest/analyze.html?d=www.avoirun.com
> 
> (Là, c'est bizarre il n'en a plus !)
> 

Quant à:
https://www.ssllabs.com/ssltest/analyze.html?d=imap.orange.fr
ça trouve 10 serveurs auquel il est incapable de se connecter ...

Gaëtan

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

Re: [testing] Gnome Evolution / problème de certificat Orange

[Ph. Gras]

Salut,

> Avec Evolution, j'ai régulièrement des messages d'erreur de certificat avec 
> les
> comptes Orange (en imap). J'ai le message suivant:
> 
> «Le certificat ne correspond pas à l'identité attendue du site duquel il
> provient.»

tu peux tester les domaines concernés ainsi :
openssl s_client -host www.avoirun.com -port 443 -prexit

(D'ailleurs, ce domaine a un problème actuellement…)

Ou vérifier la conformité du certificat ici :
https://www.ssllabs.com/ssltest/analyze.html?d=www.avoirun.com

(Là, c'est bizarre il n'en a plus !)

Bonne pioche,

Ph. Gras

Re: Répéteur wifi

[kaliderus]

Ok David je crois que je vais opter pour un modèle équivalent de chez Netgear.
Je pensais qu'il amplifiait l'ensemble du spectre wifi mais si on peut
choisir le SSID c'est aussi bien.


Le 4 septembre 2017 à 19:31, David Pinson  a écrit :
> Bonjour,
> Voici un exemple que j'utilise chez moi pour aider ma voisine âgée avec
> sa tablette
> Netgear genie  EX3700 Répéteur WiFi
> Facile à mettre en place et on peut étendre le SSID ou mettre un autre
> nom avec la même clé WPA.
> Les grandes surfaces comme Carrouf ou Le Clerc y vendent dans leur rayon
> Informatique.
>
> Sinon un Orange Pi Zéro avec une clé Wifi USB et un peu de patience dans
> les paramétrages à la mano pour les audacieux !
>
> Librement vôtre,
> David P.
>
>
>
>
> Le 04/09/2017 à 18:51, kaliderus a écrit :
>> Re,
>>
>> Il s'agit bien d'un répéteur de signal dont j'ai besoin, le routeur j'ai 
>> déjà.
>>
>> Merci.
>>
>> Le 4 septembre 2017 à 17:32,   a écrit :
>>>
>>> - Mail original -
 De: "kaliderus" 
 À: "debian" 
 Envoyé: Lundi 4 Septembre 2017 15:37:57
 Objet: Répéteur wifi

 Le bonjour,

 Auriez-vous une référence de répéteur wifi à me conseiller (ou
 déconseiller) ?
 Le besoin : Augmenter la porter du signal d'une freebox de +- 10m
 pour
 3-4 utilisateurs entre 2 maisons.
 Je n'ai jamais utiliser ce type d'équipement, il y a des points
 particuliers à vérifier ?

 Merci la liste.


>>> bonjour,
>>>
>>> pour un repair café j'ai fait une liste :
>>>
>>> http://happy-tux.org/repair-cafe/
>>>
>>> pour ton cas le routeur tplink fera l'affaire
>>>
>>>
>>> slt
>>> bernard
>>
>
> --
> Linuxement vôtre,
>
> --
> dptech ~ David Pinson
> http://www.linux-azur.org
> --
>
>var beer = new beer();
>if (beer.empty)  {
>beer.refill();
>} else {
>beer.drink();
>}
>

Re: Recommended editor for novice programmers?

[The Wanderer]

On 2017-09-04 at 17:23, rhkra...@gmail.com wrote:

>> On 9/2/17, 7:29 PM, Doug wrote:
>> 
>>> There must be something simpler than emacs or vi that will still
>>> allow coding formatting!
> 
> There are quite a few GUI editors that support coding formatting,
> some by an interface to something like a pretty printer, and some by
> autoindent in various flavors.
> 
> I'll be surprised if there are no GUI editors that do C / C++ (or
> other language) code completion, but I haven't looked for such a
> feature.

Just tested with a JS file I happen to have open in geany, and that
feature (what I believe was named, elsewhere in this thread, as
"semantic autocompletion") appears to be present and functioning there.

-- 
   The Wanderer

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



signature.asc
Description: OpenPGP digital signature

Re: Recommended editor for novice programmers?

[rhkramer]

> On 9/2/17, 7:29 PM, Doug wrote:
> > There must be something simpler than emacs or vi that will still allow
> > coding formatting!

There are quite a few GUI editors that support coding formatting, some by an 
interface to something like a pretty printer, and some by autoindent in 
various flavors.

I'll be surprised if there are no GUI editors that do C / C++ (or other 
language) code completion, but I haven't looked for such a feature.

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

[Luis Speciale]

Le 04/09/2017 à 19:56, Thomas Schmitt a écrit :

That's a good sign. If it does not offer resistence then it s not worth.


Como en el truco. Lo que cuesta, vale.

;)

Luis

[testing] Gnome Evolution / problème de certificat Orange

[Gaëtan Perrier]

Bonjour,

Avec Evolution, j'ai régulièrement des messages d'erreur de certificat avec les
comptes Orange (en imap). J'ai le message suivant:

«Le certificat ne correspond pas à l'identité attendue du site duquel il
provient.»

Les mêmes comptes configurés de la même façon sur mon smartphone avec K9-Mail
ou avec Thunderbird sous testing ne posent pas de problème de certificats.

J'en déduis que le problème est lié à Evolution. Qu'en pensez-vous ?

Gaëtan

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

Security updates (Was: (solved) how to roll back to jessie)

[Mario Castelán Castro]

On 04/09/17 02:58, Long Wind wrote:
> i do not install security update
> and it not cause trouble for me
Hello. I am wondering: Why do you choose to not to install security
updates? There seems to be nothing to gain and much to lose with that
choice.

-- 
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: Install on hp-pavilion-g6-2100 stops at 98%

[Thomas Schmitt]

Hi,

Brian wrote:
> Rate art?

"Raten" = to guess. "Kunst" = art. But together it's more down-home.
Guesscraft, maybe.

Lecture announcement: Guesscraft II. Room 201, monday and thursday 10:00 ct.


> "casemate" is to do with gun emplacements.

In german it sounds like the words for cheese and pad.
(Actually english language has the nearly correct greek transcript spelling
 for the correct meaning of the original term. I wonder why en.wikipedia
 mumbles about italian false houses.)


Have a nice day :)

Thomas

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

[Brian]

On Mon 04 Sep 2017 at 21:23:57 +0200, Thomas Schmitt wrote:

> Hi,
> 
> Brian wrote:
> > A stochastic guy?
> 
> German wikipedia says it's greek: stochastikē technē = The Art of Guessing.

Something similar with en.

> Some mathematician obviously thought that Ratekunst does not sound

Rate art?

> impressive enough. Back then, greek was mandatory for getting to university.
> So the word got unearthed and re-used in math.
> (Still better than the fate of the word that ended up as "casemate".)

I'll bite. "casemate" is to do with gun emplacements.

-- 
Brian.

Re: Anunci 2a mà

[Lluís Gras]

A finals de juny varen traure una versió del seu programari per a Linux (
http://www.mblock.cc/download/) i funciona amb alguna que altra correcció (
http://www.makeblock.es/foro/topic/25/mblock-con-linux/2#post-862) però jo
no diria que sigui massa "lliure".

2017-09-04 20:49 GMT+02:00 Narcis Garcia :

> __
> I'm using this express-made address because personal addresses aren't
> masked enough at this mail public archive. Public archive administrator
> should fix this against automated addresses collectors.
> El 04/09/17 a les 19:21, Alfonso Correa ha escrit:
> > Hola a tots,
> > He pensat que això podria ser de l'interès d'algú.
> > Tinc això a la venta per 100€.
> > http://store.makeblock.com/product/mbot-ranger-robot-kit
> > Alfonso
> > Sent from my Android device with K-9 Mail. Please excuse my brevity.
>
> Suposo que ho envies per aquí perquè funciona amb programari lliure
> (FOSS), no?
>
>

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

[Thomas Schmitt]

Hi,

Brian wrote:
> A stochastic guy?

German wikipedia says it's greek: stochastikē technē = The Art of Guessing.

Some mathematician obviously thought that Ratekunst does not sound
impressive enough. Back then, greek was mandatory for getting to university.
So the word got unearthed and re-used in math.
(Still better than the fate of the word that ended up as "casemate".)


Have a nice day :)

Thomas

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

[Brian]

On Mon 04 Sep 2017 at 20:17:58 +0200, Luis Speciale wrote:

> I'm beginning to believe that you overestimate my skills. I'm not
> complaining, but I need some time to read all this.
> Anyway, I must admit that I don't have a solid theoretical background, I'm
> mostly an stochastic guy. I mean that if it doesn't explodes, I keep
> advancing.
> I insist, I can't find the words to thank you enough, all of you.

A stochastic guy? Your private life is your own.

Glad you got Debian installed on your machine. Don't waste it.

-- 
Brian.

Re: Anunci 2a mà

[Narcis Garcia]

__
I'm using this express-made address because personal addresses aren't
masked enough at this mail public archive. Public archive administrator
should fix this against automated addresses collectors.
El 04/09/17 a les 19:21, Alfonso Correa ha escrit:
> Hola a tots,
> He pensat que això podria ser de l'interès d'algú.
> Tinc això a la venta per 100€.
> http://store.makeblock.com/product/mbot-ranger-robot-kit
> Alfonso
> Sent from my Android device with K-9 Mail. Please excuse my brevity.

Suposo que ho envies per aquí perquè funciona amb programari lliure
(FOSS), no?

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

[Thomas Schmitt]

Hi,

> I need some time to read all this.

It took me a while to learn it. We grow with our challenges. :))

I must emphasize that one can be a great Debian expert without knowing
any of those details.
On the other hand, i am a rather mediocre admin of my Debian system.
"apt-file search" and "apt-get install" is my whole repertoire.


> I mean that if it doesn't explodes, I keep advancing.

That's the right spirit. There is always the next day to revisit a problem.


Have a nice day :)

Thomas

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

[Luis Speciale]

Le 04/09/2017 à 19:56, Thomas Schmitt a écrit :

Hi,

i wrote:

This would be a preparation for a method that works by unpacking.


Luis Speciale wrote:

?


There are two ways to bring a bootable ISO onto a USB stick:

- The old way is to create a partition with a filesystem (FAT32 is not
   the best choice because it has so poor filenames),
   to copy the files out of the ISO into the created filesystem,
   and to install a boot loader which starts the same programs as the boot
   loader in the ISO would do if the ISO gets booted from a DVD.
   This needs knowlege about how the software in the ISO works. So you
   normally find instructions for a particular GNU/Linux distro like
   Debian, Ubuntu, Fedora, OpenSuSE, Arch, Gentoo, ...

- The new way needs a hybrid ISO image with a Master Boot Record and a
   partition table with EFI system partition. These two structures get used
   by PC BIOS or EFI, respectively, when they encounter the ISO on a hard
   disk or USB stick.
   To become recognizable by the firmware, the MBR has to sit at block 0
   of the disk or USB stick. It also hosts the partition table or the
   indication that there is a GUID partition table (GPT). So both firmwares
   demand that the ISO image copy begins at block 0.
   Thus the ISO needs to be copied onto the overall disk device file,
   not onto a disk partition device file, and especially not into the
   directory where some filesystem of the USB stick is mounted.
   No filesystem of the USB stick should be mounted when it gets overwritten,
   because afterwards its old data are likely to be gone.



I expect that now your self-made FAT32 is gone from the USB stick,
because the partition table was overwritten by the ISO.
Nevertheless, there is again a FAT filesystem, which contains initial EFI
boot equipment of the ISO.



??


By using the second way, you overwrote the MBR and partition table of the
USB stick. So now it bears the MBR and partition table of the ISO.
The partition table of the ISO contains this

   $ /sbin/fdisk -l firmware-9.1.0-amd64-netinst.iso
   
   Disk firmware-9.1.0-amd64-netinst.iso: 325 MiB, 340787200 bytes, 665600 sectors

   Units: sectors of 1 * 512 = 512 bytes
   Sector size (logical/physical): 512 bytes / 512 bytes
   I/O size (minimum/optimal): 512 bytes / 512 bytes
   Disklabel type: dos
   Disk identifier: 0x7db1c45b

   DeviceBoot StartEnd Sectors  Size Id Type
   firmware-9.1.0-amd64-netinst.iso1 *0 665599  665600  325M  0 Empty
   firmware-9.1.0-amd64-netinst.iso2   3984   4815 832  416K ef EFI 
(FAT-12

Partition 1 can be used to mount the ISO. Its type 0 = "Empty" is
a necessity of our crammed hybrid ISO. We need to please EFI firmware.

As you can see, partition 2 is a FAT12 of type 0xef = "EFI". Let's have a
look into it:

   $ sudo mount -o loop firmware-9.1.0-amd64-netinst.iso /mnt/iso
   mount: /dev/loop0 is write-protected, mounting read-only

Being involved expert, i know that /boot/grub/efi.img is the ISO filename
of the data file which is marked by partition 2:

   $ sudo mount -o loop /mnt/iso/boot/grub/efi.img /mnt/fat

(There are ways to find out the name or to mount it by its partition info.)

Now i can list the files in the FAT filesystem

   $ find /mnt/fat
   /mnt/fat
   /mnt/fat/efi
   /mnt/fat/efi/boot
   /mnt/fat/efi/boot/bootx64.efi

So the FAT12 filesystem contains just the single data file which EFI will
look for on a amd64 machine, normally known by its DOS name:
   \EFI\BOOT\BOOTX64.EFI

This file was made by program grub-mkimage. Its only purpose is to find
the device on which the ISO is presented and to load and start the GRUB2
configuration in the ISO directory /boot. At its end one can see these
GRUB2 configuration commands as human readable text:
   search --file --set=root /.disk/info
   set prefix=($root)/boot/grub
   source $prefix/x86_64-efi/grub.cfg
   (memdisk)/boot/grub
The existence of file /.disk/info is considered a unique property of the
Debian ISO (Steve: Is this really good enough ?). So the first filesystem
with that file gets used as source of further GRUB brain.
The starting point of that brain is file
   /mnt/iso/boot/grub/x86_64-efi/grub.cfg
which loads
   /mnt/iso/boot/grub/grub.cfg
In there you will find texts which you also can see in the first menu
of the booting Debian ISO:
   menuentry --hotkey=g 'Graphical install' {
   menuentry --hotkey=i 'Install' {
   submenu --hotkey=a 'Advanced options ...' {
   menuentry --hotkey=s 'Install with speech synthesis' {

Let's revoke "sudo mount" before we go on:

   $ sudo umount /mnt/fat
   $ sudo umount /mnt/iso



I forgot to tell that I omited this jessie part. I only did
apt-get update
apt-get install firmware-realtek
apt-get install firmware-linux-nonfree


First:
Very very good you skipped the reference to the old-stable system.
Obviously the non-free-firmware ISO already is prepared to use the
non-free repository of Debian 9.

Second:
I 

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

[Thomas Schmitt]

Hi,

i wrote:
> > This would be a preparation for a method that works by unpacking.

Luis Speciale wrote:
> ?

There are two ways to bring a bootable ISO onto a USB stick:

- The old way is to create a partition with a filesystem (FAT32 is not
  the best choice because it has so poor filenames),
  to copy the files out of the ISO into the created filesystem,
  and to install a boot loader which starts the same programs as the boot
  loader in the ISO would do if the ISO gets booted from a DVD.
  This needs knowlege about how the software in the ISO works. So you
  normally find instructions for a particular GNU/Linux distro like
  Debian, Ubuntu, Fedora, OpenSuSE, Arch, Gentoo, ...

- The new way needs a hybrid ISO image with a Master Boot Record and a
  partition table with EFI system partition. These two structures get used
  by PC BIOS or EFI, respectively, when they encounter the ISO on a hard
  disk or USB stick.
  To become recognizable by the firmware, the MBR has to sit at block 0
  of the disk or USB stick. It also hosts the partition table or the
  indication that there is a GUID partition table (GPT). So both firmwares
  demand that the ISO image copy begins at block 0.
  Thus the ISO needs to be copied onto the overall disk device file,
  not onto a disk partition device file, and especially not into the
  directory where some filesystem of the USB stick is mounted.
  No filesystem of the USB stick should be mounted when it gets overwritten,
  because afterwards its old data are likely to be gone.


> > I expect that now your self-made FAT32 is gone from the USB stick,
> > because the partition table was overwritten by the ISO.
> > Nevertheless, there is again a FAT filesystem, which contains initial EFI
> > boot equipment of the ISO.

> ??

By using the second way, you overwrote the MBR and partition table of the
USB stick. So now it bears the MBR and partition table of the ISO.
The partition table of the ISO contains this

  $ /sbin/fdisk -l firmware-9.1.0-amd64-netinst.iso
  
  Disk firmware-9.1.0-amd64-netinst.iso: 325 MiB, 340787200 bytes, 665600 
sectors
  Units: sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 512 bytes
  I/O size (minimum/optimal): 512 bytes / 512 bytes
  Disklabel type: dos
  Disk identifier: 0x7db1c45b

  DeviceBoot StartEnd Sectors  Size Id Type
  firmware-9.1.0-amd64-netinst.iso1 *0 665599  665600  325M  0 Empty
  firmware-9.1.0-amd64-netinst.iso2   3984   4815 832  416K ef EFI 
(FAT-12

Partition 1 can be used to mount the ISO. Its type 0 = "Empty" is
a necessity of our crammed hybrid ISO. We need to please EFI firmware.

As you can see, partition 2 is a FAT12 of type 0xef = "EFI". Let's have a
look into it:

  $ sudo mount -o loop firmware-9.1.0-amd64-netinst.iso /mnt/iso
  mount: /dev/loop0 is write-protected, mounting read-only

Being involved expert, i know that /boot/grub/efi.img is the ISO filename
of the data file which is marked by partition 2:

  $ sudo mount -o loop /mnt/iso/boot/grub/efi.img /mnt/fat

(There are ways to find out the name or to mount it by its partition info.)

Now i can list the files in the FAT filesystem

  $ find /mnt/fat
  /mnt/fat
  /mnt/fat/efi
  /mnt/fat/efi/boot
  /mnt/fat/efi/boot/bootx64.efi

So the FAT12 filesystem contains just the single data file which EFI will
look for on a amd64 machine, normally known by its DOS name:
  \EFI\BOOT\BOOTX64.EFI

This file was made by program grub-mkimage. Its only purpose is to find
the device on which the ISO is presented and to load and start the GRUB2
configuration in the ISO directory /boot. At its end one can see these
GRUB2 configuration commands as human readable text:
  search --file --set=root /.disk/info
  set prefix=($root)/boot/grub
  source $prefix/x86_64-efi/grub.cfg
  (memdisk)/boot/grub
The existence of file /.disk/info is considered a unique property of the
Debian ISO (Steve: Is this really good enough ?). So the first filesystem
with that file gets used as source of further GRUB brain.
The starting point of that brain is file
  /mnt/iso/boot/grub/x86_64-efi/grub.cfg
which loads
  /mnt/iso/boot/grub/grub.cfg
In there you will find texts which you also can see in the first menu
of the booting Debian ISO:
  menuentry --hotkey=g 'Graphical install' {
  menuentry --hotkey=i 'Install' {
  submenu --hotkey=a 'Advanced options ...' {
  menuentry --hotkey=s 'Install with speech synthesis' {

Let's revoke "sudo mount" before we go on:

  $ sudo umount /mnt/fat
  $ sudo umount /mnt/iso


> I forgot to tell that I omited this jessie part. I only did
> apt-get update
> apt-get install firmware-realtek
> apt-get install firmware-linux-nonfree

First:
Very very good you skipped the reference to the old-stable system.
Obviously the non-free-firmware ISO already is prepared to use the
non-free repository of Debian 9.

Second:
I understand you got no good graphics but were able to enter shell
commands like apt-get.

Re: Répéteur wifi

[David Pinson]

Bonjour,
Voici un exemple que j'utilise chez moi pour aider ma voisine âgée avec
sa tablette
Netgear genie  EX3700 Répéteur WiFi
Facile à mettre en place et on peut étendre le SSID ou mettre un autre
nom avec la même clé WPA.
Les grandes surfaces comme Carrouf ou Le Clerc y vendent dans leur rayon
Informatique.

Sinon un Orange Pi Zéro avec une clé Wifi USB et un peu de patience dans
les paramétrages à la mano pour les audacieux !

Librement vôtre,
David P.




Le 04/09/2017 à 18:51, kaliderus a écrit :
> Re,
>
> Il s'agit bien d'un répéteur de signal dont j'ai besoin, le routeur j'ai déjà.
>
> Merci.
>
> Le 4 septembre 2017 à 17:32,   a écrit :
>>
>> - Mail original -
>>> De: "kaliderus" 
>>> À: "debian" 
>>> Envoyé: Lundi 4 Septembre 2017 15:37:57
>>> Objet: Répéteur wifi
>>>
>>> Le bonjour,
>>>
>>> Auriez-vous une référence de répéteur wifi à me conseiller (ou
>>> déconseiller) ?
>>> Le besoin : Augmenter la porter du signal d'une freebox de +- 10m
>>> pour
>>> 3-4 utilisateurs entre 2 maisons.
>>> Je n'ai jamais utiliser ce type d'équipement, il y a des points
>>> particuliers à vérifier ?
>>>
>>> Merci la liste.
>>>
>>>
>> bonjour,
>>
>> pour un repair café j'ai fait une liste :
>>
>> http://happy-tux.org/repair-cafe/
>>
>> pour ton cas le routeur tplink fera l'affaire
>>
>>
>> slt
>> bernard
>

-- 
Linuxement vôtre,

-- 
dptech ~ David Pinson
http://www.linux-azur.org
--

   var beer = new beer();
   if (beer.empty)  {
   beer.refill();
   } else {
   beer.drink();
   }

Anunci 2a mà

[Alfonso Correa]

Hola a tots,
He pensat que això podria ser de l'interès d'algú. 
Tinc això a la venta per 100€.
http://store.makeblock.com/product/mbot-ranger-robot-kit
Alfonso 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

gksu pcmanfm no se abre como root

[franiortiz hotmail]

Hola he instalado firmware-9.1.0-amd64-netinst.iso descargado desde 
https://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/current/amd64/iso-cd/
en una maquina virtual con virtualbox 4.3.36 la instalacion correcta sin ningun 
escritorio, 
tan solo las utilidades del sistema, ssh-server, build-essential 
module-assistant linux-headers-$(uname -r) dkms 
pero cuando intento instalar:
http://download.virtualbox.org/virtualbox/4.3.36/VBoxGuestAdditions_4.3.36.iso 
me aparecen errores:
Building the main Guest Additions module ...fail!
...
Warning: unknown version of the x Window System installed. Not installing X 
Window System drivers

Tambien instalo lxde-core (el cual ahora instala lightdm, en jessie no lo hacia)
una vez instalado ejecuto con alt+f2: gksu pcmanfm , introduzco  pass de root  
y este se abre pero no 
en modo root (ie sin permisos), probe tambien a abrir una consola root y 
ejecutar directamente pcmanfm, lo mismo, se abre pero sin permisos.
la maquina anfitrion es: Linux debian 3.16.0-4-amd64 #1 SMP Debian 
3.16.43-2+deb8u2 (2017-06-26) x86_64 GNU/Linux
gracias

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

[Luis Speciale]

Le 04/09/2017 à 18:27, Thomas Schmitt a écrit :

Hi,

Cindy-Sue Causey wrote:

Are you saying that it looks like he copied straight to
the device instead of to a mount point?


Yes, i believe it is so.
I cannot be totally sure, because i have no MacOS at hand.
But /dev/disk1 is a whole disk device, according to web and other
confirmations. No Unix puts a file into the filesystem of a disk if
you copy it to the disk device file.
On GNU/Linux, "cp" does the same as "dd" in such a case. It copies the
ISO image bytes plainly onto the disk device, overwriting the partition
table and possibly establishing an own partition table.


That's what I think too. That's maybe also the reason why I had the 
message "The disk you inserted was not readable by this computer." at 
the end of the cp command. My iMac did not understood the animal




This plain copying of the ISO to the disk device is the recommended way
to use a Debian i386 or amd64 installation ISO on a USB stick.
Unpacking and installing to the hard disk happens by a GNU/Linux system
which gets booted out of the ISO. Either by bootloader ISOLINUX on PC BIOS
firmware, or by bootloader GRUB2 on EFI firmware. Both are ready in the ISO.

So no need to unpack the ISO before booting the USB stick.
There are old instructions around to do so. They might still have a benefit
if you want to boot more than one system from the USB stick.



I regularly mount partitions to do debootstrap installs so I do
understand that method.


That's an alternative way to install Debian without a bootable ISO but
rather by help of an already running operating system (must it be a
GNU/Linux ?) and access to a Debian repository.
One could possibly use a Live-CD ISO as such a running operating system.


Have a nice day :)

Thomas

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

[Luiz Carlos]

Eu não baixei a live cd do debian onde vc inicia o sistema sem fazer
alterações como foi o linux mint, baixei o DVD de instalação mesmo e fui na
opção de recuperação, mas mesmo assim é intuitivo, recomendo.

Na verdade nem eu sabia desse rescue, é excelente.

Em 4 de setembro de 2017 08:21, Ricardo Ramos 
escreveu:

> Bom saber que deu tudo certo, não sabia que o live do Debian no rescue
> mode recuperava ate com LVM criptografado, mais uma pra ter guardado em
> caso de emergência.
>
> On Seg, 4 de set de 2017, 05:28 Luiz Carlos  wrote:
>
>> Consegui resolver, a solução foi ter baixado a mesma versão do versão do
>> Debian, dar boot pelo DVD e entrar no modo rescue, eu achei bem intuitivo
>> aquilo, eu pensei que era pra digitar linha de comando, mas não foi assim,
>> o modo rescue restaura com criptografia e tudo, se for ver nem era preciso
>> usar a live cd, o grub foi restaurado pro estado que estava antes de
>> instalar o Windows 10, ou  seja aparecia no grub o Windows 7, mas nada que
>> um update-grub no Debian não resolvesse, está tudo ok agora.
>>
>> Que alivio em saber que recuperei meu sistema, e meu windows está
>> atualizado, obrigado a todos por tudo e desculpe o incomodo.
>>
>> Pra quem pode sofrer com isso, restaurar no modo rescue tem que ter noção
>> de qual é a partição raiz, qual partição instalar o grub e por ai vai, a
>> parte da live cd me ajudou um pouco a pegar a noção disso.
>>
>> Em 4 de setembro de 2017 03:20, Luiz Carlos  escreveu:
>>
>>> O Debian que estou não é live cd, é só pra ver o lance de rescue, mas
>>> será possível restaurar com partições criptografadas?
>>>
>>> Em 4 de setembro de 2017 03:16, Luiz Carlos 
>>> escreveu:
>>>
 Estou aqui baixando uma distro do Debian equivalente a minha versão,
 vamos ver no que vai dar.
 Será que danifiquei a minha partição do Linux? Bem, eu consigo montar a
 raiz e a home, n sei se tenho esperanças de arrumar.

 Em 4 de setembro de 2017 02:39, Linux - Junior Polegato <
 li...@juniorpolegato.com.br> escreveu:

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

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

[Luis Speciale]

Le 04/09/2017 à 14:05, Thomas Schmitt a écrit :

I don't understand some things you wrote, so I'll mark this items by a 
question mark…



I formated the USB as FAT32 in my iMac


This would be a preparation for a method that works by unpacking.


?


I downloaded the firmware version firmware-9.1.0-amd64-netinst.iso


This could have been the decisive trick. Laptop and the need for
non-free firmware are a known combination.


Good!


sudo cp firmware-9.1.0-amd64-netinst.iso /dev/disk1


You copy to the device file, not to the mount directory. At least on
GNU/Linux this is like "dd". On MacOS it might differ but it will not
put the ISO as file into the FAT32 fileystem and not unpack the ISO
into the FAT32 filesystem.

I expect that now your self-made FAT32 is gone from the USB stick,
because the partition table was overwritten by the ISO.
Nevertheless, there is again a FAT filesystem, which contains initial EFI
boot equipment of the ISO.


??


"The disk you inserted was not readable by this computer."
diskutil unmountDisk /dev/disk1


Looks like you slightly confused the operating system.
One should unmount the filesystem before overwriting it, not afterwards.


My bad. I forgot that before the cp command I unmonted de disk. The 
system saw it after that the command ends and asks what to do with the 
stranger





Then all went well. But not the resolution.
So after a little Googling I found this
https://gist.github.com/ed-flanagan/929633981ea548e97f1d


Indeed a firmware issue then. But not solved by the non-free firmware ISO.
Maybe one should file a bug towards that ISO ?


I don't know what to say. I believe that it must be a myriad of firmwares


https://wiki.debian.org/Firmware could need an update about Debian 9
and a hint what package is in charge of bugs.

I assume that after equipping your Debian 9 "stretch" with
/etc/apt/sources.list content for Debian 8 "jessie", you have to expect
trouble.


I forgot to tell that I omited this jessie part. I only did
apt-get update
apt-get install firmware-realtek
apt-get install firmware-linux-nonfree


Better return to the original state of that file now.
(If you are in trouble already, better repeat the installation and
  take care to use that "jessie" repository only for getting the firmware,
  and only if you cannot get it from a "stretch" repository.)


I wonder, though, how you could execute apt-get when your installation
did not finish.
Is there some step missing, e.g. how to get to a shell prompt of the
incompletely installed system ?


Sure thing. I spend all my weekend in a fierce battle with this monster 
and I was near (a couple of times) of giving up.



Whatever: Welcome, fellow Debian user.


Yes, you can call me that now!

Thanks for your answers

Luis

Re: Répéteur wifi

[kaliderus]

Re,

Il s'agit bien d'un répéteur de signal dont j'ai besoin, le routeur j'ai déjà.

Merci.

Le 4 septembre 2017 à 17:32,   a écrit :
>
>
> - Mail original -
>> De: "kaliderus" 
>> À: "debian" 
>> Envoyé: Lundi 4 Septembre 2017 15:37:57
>> Objet: Répéteur wifi
>>
>> Le bonjour,
>>
>> Auriez-vous une référence de répéteur wifi à me conseiller (ou
>> déconseiller) ?
>> Le besoin : Augmenter la porter du signal d'une freebox de +- 10m
>> pour
>> 3-4 utilisateurs entre 2 maisons.
>> Je n'ai jamais utiliser ce type d'équipement, il y a des points
>> particuliers à vérifier ?
>>
>> Merci la liste.
>>
>>
>
> bonjour,
>
> pour un repair café j'ai fait une liste :
>
> http://happy-tux.org/repair-cafe/
>
> pour ton cas le routeur tplink fera l'affaire
>
>
> slt
> bernard

Re: (solved) how to roll back to jessie

[Cindy-Sue Causey]

On 9/4/17, Long Wind  wrote:
>
> 
> On Mon, 9/4/17, Felix Miata  wrote:
>
>
>>  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.
>
> i have used debian for long time (since rex)
> all support i need comes from this list
> i do not install security update
> and it not cause trouble for me
>
> and font in text mode in wheezy seems cool
>
> i have an wheezy in /dev/sda2
> and have installed iceweasel today


Would you consider posting a screen capture of the font effect as
you're seeing it? You could upload to Debian itself *for posterity*:

https://paste.debian.net/

Maybe someone can help bring your fave into future releases... or
maybe something already exists but just got buried under the surface
over time.

I can *empathize*, i.e. have experienced this first hand. I can
remember favored features, just such as a font's almost "naive"
onscreen appearance, changing as all these projects grew up. :)

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

* runs with duct tape *

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

[Thomas Schmitt]

Hi,

Cindy-Sue Causey wrote:
> Are you saying that it looks like he copied straight to
> the device instead of to a mount point?

Yes, i believe it is so.
I cannot be totally sure, because i have no MacOS at hand.
But /dev/disk1 is a whole disk device, according to web and other
confirmations. No Unix puts a file into the filesystem of a disk if
you copy it to the disk device file.
On GNU/Linux, "cp" does the same as "dd" in such a case. It copies the
ISO image bytes plainly onto the disk device, overwriting the partition
table and possibly establishing an own partition table.

This plain copying of the ISO to the disk device is the recommended way
to use a Debian i386 or amd64 installation ISO on a USB stick. 
Unpacking and installing to the hard disk happens by a GNU/Linux system
which gets booted out of the ISO. Either by bootloader ISOLINUX on PC BIOS
firmware, or by bootloader GRUB2 on EFI firmware. Both are ready in the ISO.

So no need to unpack the ISO before booting the USB stick.
There are old instructions around to do so. They might still have a benefit
if you want to boot more than one system from the USB stick.


> I regularly mount partitions to do debootstrap installs so I do
> understand that method.

That's an alternative way to install Debian without a bootable ISO but
rather by help of an already running operating system (must it be a
GNU/Linux ?) and access to a Debian repository.
One could possibly use a Live-CD ISO as such a running operating system.


Have a nice day :)

Thomas

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

[Gene Heskett]

On Monday 04 September 2017 11:57:19 Cindy-Sue Causey wrote:

> On 9/4/17, Thomas Schmitt  wrote:
> > Hi,
> >
> > Luis Speciale wrote:
> >> sudo cp firmware-9.1.0-amd64-netinst.iso /dev/disk1
> >
> > You copy to the device file, not to the mount directory. At least on
> > GNU/Linux this is like "dd". On MacOS it might differ but it will
> > not put the ISO as file into the FAT32 fileystem and not unpack the
> > ISO into the FAT32 filesystem.
> >
> > I expect that now your self-made FAT32 is gone from the USB stick,
> > because the partition table was overwritten by the ISO.
> > Nevertheless, there is again a FAT filesystem, which contains
> > initial EFI boot equipment of the ISO.
>
> I'm understanding what you're saying, but then again I might not be
> understanding. Are you saying that it looks like he copied straight to
> the device instead of to a mount point? That's what I'm understanding
> your words to be saying.
>
This s/b correct, the iso is an image, complete with filesystem, designed 
to be written to the device starting at LSN0.  IOW, it obliterates 
whatever may have been there before.

> I regularly mount partitions to do debootstrap installs so I do
> understand that method. That's how I am a-suming this should be done,
> too.
>
> All the times I've done that correctly, I have still wasted a
> ridiculous amount of time... repeatedly... tracking down the... device
> name to use when that's not what we use. *smacking my head (in
> hindsight)*
>
> That's an important point that I now wonder how often gets missed
> versus caught when people are having problems installing to other
> media. I know it never crosses my mind to consciously check off that
> specific detail when people are writing about their problems. :)
>
> That's also why people trying to help want to know the *exact* steps a
> user took to try to do something. The person helping is not being
> nosey. Seeing exact details might just help them catch a whoops such
> as that device name standing in place of a mount point.
>
> Cindy :)


Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page 

Re: Recommended editor for novice programmers?

[Morten Bo Johansen]

On 2017-09-02 Tom Browder wrote:

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

Jed, http://www.jedsoft.org/jed/, is highly recommendable!

  Morten
  

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

[Cindy-Sue Causey]

On 9/4/17, Thomas Schmitt  wrote:
> Hi,
>
> Luis Speciale wrote:
>
>> sudo cp firmware-9.1.0-amd64-netinst.iso /dev/disk1
>
> You copy to the device file, not to the mount directory. At least on
> GNU/Linux this is like "dd". On MacOS it might differ but it will not
> put the ISO as file into the FAT32 fileystem and not unpack the ISO
> into the FAT32 filesystem.
>
> I expect that now your self-made FAT32 is gone from the USB stick,
> because the partition table was overwritten by the ISO.
> Nevertheless, there is again a FAT filesystem, which contains initial EFI
> boot equipment of the ISO.


I'm understanding what you're saying, but then again I might not be
understanding. Are you saying that it looks like he copied straight to
the device instead of to a mount point? That's what I'm understanding
your words to be saying.

I regularly mount partitions to do debootstrap installs so I do
understand that method. That's how I am a-suming this should be done,
too.

All the times I've done that correctly, I have still wasted a
ridiculous amount of time... repeatedly... tracking down the... device
name to use when that's not what we use. *smacking my head (in
hindsight)*

That's an important point that I now wonder how often gets missed
versus caught when people are having problems installing to other
media. I know it never crosses my mind to consciously check off that
specific detail when people are writing about their problems. :)

That's also why people trying to help want to know the *exact* steps a
user took to try to do something. The person helping is not being
nosey. Seeing exact details might just help them catch a whoops such
as that device name standing in place of a mount point.

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

* runs with duct tape *

Re: network trouble on stretch

[Glenn English]

Very sorry. I told you guys some horrible lies yesterday about Buster.

ifupdown is there.

route is back.

ifconfig is back.

Thanks much, Fungi4All, for the name fix, I haven't implemented it
yet, and I'm not sure I will because who knows what'll happen in the
next release. I'm going to try to live with the peculiar interface
names until the proper ones come back like the utilities did.

However:

The interface names are still broken, as is the man page.

The interface file with the Ethernet address that worked yesterday
doesn't seem to work this morning. Systemd claims the file is written
incorrectly (it isn't, according to the man page; and it worked
yesterday) Ifup doesn't like it either. I can bring up the interface
and assign it an address with ifconfig.

And I can fix (and see) the routing table with route.

--
Glenn English

Re: external USB hard drive mount permissions

[James H. H. Lampert]

On 9/2/17, 6:01 AM, Eduardo M KALINOWSKI wrote:

On 02-09-2017 09:29, Federico Beffa wrote:

I'm using Debian Stretch with Gnome. When I plug-in an external USB
hard drive (ext4) it gets automatically mounted at /media/beffa/label.


but the device is still only writable by root.

How can I tell the system to make it writable for the user owning the
Gnome session


You might also consider adding an FSTAB entry, using a "LABEL=" 
drive-ID, to map it to a mount point of your own choosing.


That's what I ended up doing.

--
JHHL

Re: Recommended editor for novice programmers?

[James H. H. Lampert]

On 9/2/17, 7:29 PM, Doug wrote:


There must be something simpler than emacs or vi that will still allow
coding formatting!


Personally, I use nano from a terminal session, or GEdit from a Gnome 
session.


--
JHHL

74 % av alla säljare suger

[Månadens Säljbok]

Nya boken av Bruce King och Max Söderpalm - För dig som vill dubbla 
försäljningen
Läs på webben 
[http://www.epostservice.se/aspnet/v3/page/read.ashx?issueid=350874=33797228=907687834BE6=3362380923]
 

Kunderna tycker att 74 % av alla säljare suger!

Det visar undersökningar som har gjorts av mer än
1 miljon säljare.

Det är goda nyheter för dig, för det innebär att 74 %
av dina konkurrenter suger. Och det kan göra dig till
en vinnare!

Två av Europas bästa säljcoacher, Bruce King och Max Söderpalm, fick den 
informationen och bestämde sig för
att göra något åt det.

För första gången har dom skrivit en bok tillsammans. Med 
fokus på vad du ska göra för att INTE vara en av dom som
suger utan istället dubbla din försäljning.

Allt du behöver för att lyckas hittar du i nya boken!

Beställ till dig och hela säljkåren och få bästa starten
på säljhösten!

BESTÄLL HÄR 
[http://www.epostservice.se/aspnet/v3/pub/link.ashx?issueid=350874userid=33797228linkid=22732469readid=907687834BE6test=0umailid=3362380923]





                    
[http://www.epostservice.se/aspnet/v3/pub/link.ashx?issueid=350874userid=33797228linkid=22732469readid=907687834BE6test=0umailid=3362380923]


Båda författarna är internationellt erfarna säljare, företags-
ledare och säljtränare. Dom har skrivit 10 böcker vardera.

Bruce King 
[http://www.epostservice.se/aspnet/v3/pub/link.ashx?issueid=350874userid=33797228linkid=22732469readid=907687834BE6test=0umailid=3362380923]
 har bl a skrivit som Psychoselling, Sälj så det ryker, Referenser och Så blir 
du en Superbjörn.

Max Söderpalm 
[http://www.epostservice.se/aspnet/v3/pub/link.ashx?issueid=350874userid=33797228linkid=22732469readid=907687834BE6test=0umailid=3362380923]
 har bla skrivit 30 sätt att göra affärer,
Det är i backarna man rycker, Våga sälja hälsa och Tvärtom

Precis som deras tidigare böcker är 74 % 
[http://www.epostservice.se/aspnet/v3/pub/link.ashx?issueid=350874userid=33797228linkid=22732469readid=907687834BE6test=0umailid=3362380923]
 lättläst, tydlig,
konkret och skriven som en säljare vill läsa. 

Beställ till dig och hela säljkåren och få bästa starten
på säljhösten!
 
BESTÄLL HÄR 
[http://www.epostservice.se/aspnet/v3/pub/link.ashx?issueid=350874userid=33797228linkid=22732469readid=907687834BE6test=0umailid=3362380923]
 
 
 
Trevlig läsning!
 
Månadens säljbok
 
 
 
 
 
Adresskälla: Månadens säljbok
avanmälan [http://www.epostservice.com/unsub.asp?33797228&75A249A29919&350874]
[_]

Re: Recommended editor for novice programmers?

[solitone]

On Sunday, 3 September 2017 21:33:55 CEST Dejan Jocic wrote:
> On 03-09-17, solitone wrote:
> > 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.
> 
> For Vim:
> 
> http://valloric.github.io/YouCompleteMe/
> 
> [...]
> 
> Something like that?

Yes, I see it's got semantic autocompletion, which is what I meant. It 
supports C++ natively, while for Java you would need Eclim.

I fear I'll need to convert to vim, so  :-)  Haven't checked the emacs 
alternative yet...
-- 
⢀⣴⠾⠻⢶⣦⠀ 
⣾⠁⢠⠒⠀⣿⡁Sent from my brain using neurons fueled by glucose.
⢿⡄⠘⠷⠚⠋⠀ 
⠈⠳⣄

Répéteur wifi

[kaliderus]

Le bonjour,

Auriez-vous une référence de répéteur wifi à me conseiller (ou déconseiller) ?
Le besoin : Augmenter la porter du signal d'une freebox de +- 10m pour
3-4 utilisateurs entre 2 maisons.
Je n'ai jamais utiliser ce type d'équipement, il y a des points
particuliers à vérifier ?

Merci la liste.

Re: Xerrada sobre Debian al DLP el 16 de setembre

[Ernest Adrogué]

2017-09- 4, 00:05 (+0200); Julio Amorós escriu:
> 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.

Suposo que depèn de cada persona, però el meu sistema Debian
probablement és bastant diferent del teu, i el teu diferent del d'algú
altre.  La configuració que utilitzo actualment l'he anat fent al llarg
dels anys, i si algun cop he d'utilitzar una instal·lació nova amb la
configuració per defecte de seguida noto mil coses que funcionen
diferent de com estic acostumat que funcionin.

Amb altres distribucions, com Ubuntu, no cal que l'usuari dediqui tant
temps a configurar el sistema, perquè tot ja està més o menys configurat
de manera que s'ajusti a les preferències de la majoria d'usuaris.

Per tant no veig cap problema en recomanar Ubuntu o Mint a usuaris poc
experimentats o usuaris que no volen "perdre el temps" fent ajustaments.

Re: Passage de Jessie à Stretch avec backports

[Georges]

Le Mon, 4 Sep 2017 14:03:26 +0200,

DT a écrit :

> Bonjour,
> 
> Comme prévu ça s'est très bien passé.
> 
> Pour info George, mon rsync ressemble à ça :

 Bon, merci j'ai de quoi comparer avec le mien ;-) et expérimenter. 
> 
> ###
> 
> #!/bin/bash
> # Unset des variables utilisées
> unset RSYNCROOT_REPERTOIRE_SOURCE
> unset RSYNCROOT_REPERTOIRE_DESTINATION
> unset RSYNCROOT_EXCLUDE_FILE
> unset RSYNCROOT_INCLUDE_FILE
> 
> # Définition des variables
> RSYNCROOT_REPERTOIRE_SOURCE="/"
> RSYNCROOT_REPERTOIRE_DESTINATION="/media/damien/SauvegardeRS/root/"
> RSYNCROOT_EXCLUDE_FILE="/root/scripts/rsync/exclude"
> RSYNCROOT_INCLUDE_FILE="/root/scripts/rsync/include"
> 
> # Détecter la présence du volume de destination et interrompre 
> l'opération si nécessaire
> if [ ! -e "$RSYNCROOT_REPERTOIRE_DESTINATION" ]
> then
> echo "Attention, le disque de sauvegarde n'est pas présent"
> exit
> fi
> 
> # Détecter l'existence du fichier d'exclusion
> if [ ! -e "$RSYNCROOT_EXCLUDE_FILE" ]
> then
> echo "Attention, fichier d'exclusion non trouvé"
> exit
> fi
> 
> # Détecter l'existence du fichier d'inclusion (files-from)
> if [ ! -e "${RSYNCROOT_INCLUDE_FILE}" ]
> then
> echo "Attention, fichier d'inclusion (files-from) non trouvé"
> exit
> fi
> 
> 
> rsync -arh --stats --progress --delete 
> --files-from="${RSYNCROOT_INCLUDE_FILE}" 
> "${RSYNCROOT_REPERTOIRE_SOURCE}" "${RSYNCROOT_REPERTOIRE_DESTINATION}"
> 
> # rsync -ah --stats --progress --delete 
> --exclude-from="${RSYNCROOT_EXCLUDE_FILE}" 
> "${RSYNCROOT_REPERTOIRE_SOURCE}" "${RSYNCROOT_REPERTOIRE_DESTINATION}"
> 
> # Pour les tests, ajouter le paramètre 'n' sur les commandes rsync
> #echo "/!\ DRY RUN /!\ "
> 
> echo "La commande de sauvegarde a terminé son travail..."
> echo "Vérifiez dans le terminal s'il n'y a pas eu d'erreur !"
> 
> #Sauvegarde de dpkg --get-selections comme conseillé par la doc Debian
> dpkg --get-selections "*"  > 
> ${RSYNCROOT_REPERTOIRE_DESTINATION}dpkg_get-selections
> 
> 
> ###
> 
> Je l'ai modifié au cours du temps donc c'est un peu fouilli, et je 
> n'utilise plus le fichier exclude car avant je sauvegardais tout sauf 
> quelque trucs, et maintenant je préfère sauvegarder que ce que je
> sais avoir besoin au risque d'oublier quelque chose.
> J'ai quand même laissé l'ancienne commande qui utilisais le fichier 
> exclude qui contient :
> 
> /home
> /cdrom
> /dev
> /lost+found
> /media
> /mnt
> /proc
> /sys
> /tmp
> /run
> /var/lib/docker
> 
> Pour sa part le fichier include (très mal nommé) ne contient que :
> 
> /etc/
> /var/lib/dpkg/
> /var/lib/apt/extended_states
> /var/lib/aptitude/pkgstates
> /root/
> 
> Et c'est donc tout ce que je sauvegarde avec en plus le dpkg 
> --get-selections
> 
> A bientôt,
> Damien
> 
> Le 03/09/2017 à 08:44, Georges a écrit :
> > Le Sat, 2 Sep 2017 22:36:59 +0200,
> >
> > DT a écrit :
> >  
> >> Oui merci,
> >>
> >> de toute façon mon script de backup rsync backup ce qui est
> >> préconisé par Debian + 2/3 trucs à moi.  
> >   Chez moi aussi un script rsync depuis woody mais (+ 2/3 trucs à
> > moi) sa m’intéresse si on peu développer ;-)
> > [coupé..]  
> >> Merci et à bientôt,
> >> Damien  
> >   De rien
> >
> >Georges
> >  
> >> Le 02/09/2017 à 20:42, Gaëtan Perrier a écrit :  
> > [coupé..]  
> >> Bonjour,
> >>
> >> Je suis sur Jessie avec notamment le noyau et les firmware et
> >> librairies graphiques en backports (Intel i5 série 6), et
> >> quelques autres petites appli en backports aussi (mais aucune
> >> n'est critique, seule docker l'est et il n'est pas en bpo).
> >>
> >> Est-ce que je peux passer à Stretch sans m'en soucier ou pas ?
> >>
> >>
> >> J'avoue que c'est la première fois que j'ai autant de paquets
> >> en bpo pour faire fonctionner ma machine, donc je me demande un
> >> peu...
> >>
> >>
> >> 
> > J'ai mis à jour en stretch ma machine de boulot qui avait bien
> > plus de paquets backports sans aucun problème.
> > Il faut bien suivre la procédure: upgrade, puis dist-upgrade et
> > ne pas attaquer par le dist-upgrade direct.
> >
> > A+
> >
> > Gaëtan  
>  Bonsoir,
>  Si je peu me permettre, je fais toujours :
> 
> En ce qui concerne la sauvegarde, je ferais aussi un petit
>   "dpkg --get-selections > fichier"
>  pour stocker dans ledit fichier l'état des paquets (installé ou
>  non). Ça permet, en cas de sinistre majeur de n'avoir à
>  réinstaller que le système de base,
> 
> Ce qui permet de faire :
> 
>  puis un petit
>   "dpkg --set-selections < fichier"
> suivi d'un
>   "apt-get dselect-upgrade"
> te réinstallera tout seul tous les paquets qui étaient
>  installés.
> 
>  Si je me trompe, corrigez moi ;-)
> 
>  Georges  
> >>> C'est effectivement une sage précaution sur une machine
> >>> importante. 

Re :Re: Comment appuyer sur la touche espace avec un script shell

[Andreï V . Fomitchev]

Salut.
Sinon, dans un script, j'avais fait Echo ''o'' | scriptquiabesoinJe ne sais pas 
si cela peut fonctionner pour deux espaces

Envoyé depuis Yahoo Mail pour Android 
 
  Le sam., sept. 2, 2017 à 21:11, G2PC a écrit :   Le 
02/09/2017 à 17:18, Christophe Moille a écrit :
> startup_message off 
C'est parfait ! Merci !
Résolu.

  

Re: network trouble on stretch

[Felix Miata]

Fungi4All composed on 2017-09-04 07:16 (UTC-0400):

>> From: mrma...@earthlink.net To: debian-user@lists.debian.org

>> Erik Christiansen composed on 2017-09-04 18:06 (UTC+1000):

>>> But Fungi4All"s solution is so easy to use that I"m won over, and have
>>> implemented it here.

>> I think I started putting net.ifnames=0 on the kernel command line close to
>> 3 years ago. :-)

> You mean on grub.cfg on the linux command line.  This is what the above
> mentioned procedure does when grub updates.  If you don't place the modifier
> in etc/grub then it may vanish again, meaning you will have to do it again.
> The same with other modifiers of grub, like default # entry, background,
> timeout.

I disregard what update scripts do.
menu.lst is moved to menu.lst.## and menu.00 copied back to menu.ls

title Debian 9 Stretch defkernel on sda26
root (hd0,25)
kernel /boot/vmlinuz showopts ro root=LABEL=26deb9 ipv6.disable=1
net.ifnames=0 noresume plymouth.enable=0 vga=791 video=1024x768@60
video=1440x900@60
initrd /boot/initrd

-- 
"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: Install on hp-pavilion-g6-2100 stops at 98%

[Thomas Schmitt]

Hi,

Luis Speciale wrote:
> I formated the USB as FAT32 in my iMac

This would be a preparation for a method that works by unpacking.


> I downloaded the firmware version firmware-9.1.0-amd64-netinst.iso

This could have been the decisive trick. Laptop and the need for
non-free firmware are a known combination.


> sudo cp firmware-9.1.0-amd64-netinst.iso /dev/disk1

You copy to the device file, not to the mount directory. At least on
GNU/Linux this is like "dd". On MacOS it might differ but it will not
put the ISO as file into the FAT32 fileystem and not unpack the ISO
into the FAT32 filesystem.

I expect that now your self-made FAT32 is gone from the USB stick,
because the partition table was overwritten by the ISO.
Nevertheless, there is again a FAT filesystem, which contains initial EFI
boot equipment of the ISO.


> "The disk you inserted was not readable by this computer."
> diskutil unmountDisk /dev/disk1

Looks like you slightly confused the operating system.
One should unmount the filesystem before overwriting it, not afterwards.


> Then all went well. But not the resolution.
> So after a little Googling I found this
> https://gist.github.com/ed-flanagan/929633981ea548e97f1d

Indeed a firmware issue then. But not solved by the non-free firmware ISO.
Maybe one should file a bug towards that ISO ?
https://wiki.debian.org/Firmware could need an update about Debian 9
and a hint what package is in charge of bugs.

I assume that after equipping your Debian 9 "stretch" with
/etc/apt/sources.list content for Debian 8 "jessie", you have to expect
trouble.
Better return to the original state of that file now.
(If you are in trouble already, better repeat the installation and
 take care to use that "jessie" repository only for getting the firmware,
 and only if you cannot get it from a "stretch" repository.)


I wonder, though, how you could execute apt-get when your installation
did not finish.
Is there some step missing, e.g. how to get to a shell prompt of the
incompletely installed system ?


Whatever: Welcome, fellow Debian user.


Have a nice day :)

Thomas

Re: Passage de Jessie à Stretch avec backports

[Damien TOURDE]

Bonjour,

Comme prévu ça s'est très bien passé.

Pour info George, mon rsync ressemble à ça :

###

#!/bin/bash
# Unset des variables utilisées
unset RSYNCROOT_REPERTOIRE_SOURCE
unset RSYNCROOT_REPERTOIRE_DESTINATION
unset RSYNCROOT_EXCLUDE_FILE
unset RSYNCROOT_INCLUDE_FILE

# Définition des variables
RSYNCROOT_REPERTOIRE_SOURCE="/"
RSYNCROOT_REPERTOIRE_DESTINATION="/media/damien/SauvegardeRS/root/"
RSYNCROOT_EXCLUDE_FILE="/root/scripts/rsync/exclude"
RSYNCROOT_INCLUDE_FILE="/root/scripts/rsync/include"

# Détecter la présence du volume de destination et interrompre 
l'opération si nécessaire

if [ ! -e "$RSYNCROOT_REPERTOIRE_DESTINATION" ]
then
echo "Attention, le disque de sauvegarde n'est pas présent"
exit
fi

# Détecter l'existence du fichier d'exclusion
if [ ! -e "$RSYNCROOT_EXCLUDE_FILE" ]
then
echo "Attention, fichier d'exclusion non trouvé"
exit
fi

# Détecter l'existence du fichier d'inclusion (files-from)
if [ ! -e "${RSYNCROOT_INCLUDE_FILE}" ]
then
echo "Attention, fichier d'inclusion (files-from) non trouvé"
exit
fi


rsync -arh --stats --progress --delete 
--files-from="${RSYNCROOT_INCLUDE_FILE}" 
"${RSYNCROOT_REPERTOIRE_SOURCE}" "${RSYNCROOT_REPERTOIRE_DESTINATION}"


# rsync -ah --stats --progress --delete 
--exclude-from="${RSYNCROOT_EXCLUDE_FILE}" 
"${RSYNCROOT_REPERTOIRE_SOURCE}" "${RSYNCROOT_REPERTOIRE_DESTINATION}"


# Pour les tests, ajouter le paramètre 'n' sur les commandes rsync
#echo "/!\ DRY RUN /!\ "

echo "La commande de sauvegarde a terminé son travail..."
echo "Vérifiez dans le terminal s'il n'y a pas eu d'erreur !"

#Sauvegarde de dpkg --get-selections comme conseillé par la doc Debian
dpkg --get-selections "*"  > 
${RSYNCROOT_REPERTOIRE_DESTINATION}dpkg_get-selections



###

Je l'ai modifié au cours du temps donc c'est un peu fouilli, et je 
n'utilise plus le fichier exclude car avant je sauvegardais tout sauf 
quelque trucs, et maintenant je préfère sauvegarder que ce que je sais 
avoir besoin au risque d'oublier quelque chose.
J'ai quand même laissé l'ancienne commande qui utilisais le fichier 
exclude qui contient :


/home
/cdrom
/dev
/lost+found
/media
/mnt
/proc
/sys
/tmp
/run
/var/lib/docker

Pour sa part le fichier include (très mal nommé) ne contient que :

/etc/
/var/lib/dpkg/
/var/lib/apt/extended_states
/var/lib/aptitude/pkgstates
/root/

Et c'est donc tout ce que je sauvegarde avec en plus le dpkg 
--get-selections


A bientôt,
Damien

Le 03/09/2017 à 08:44, Georges a écrit :

Le Sat, 2 Sep 2017 22:36:59 +0200,

DT a écrit :


Oui merci,

de toute façon mon script de backup rsync backup ce qui est préconisé
par Debian + 2/3 trucs à moi.

  Chez moi aussi un script rsync depuis woody mais (+ 2/3 trucs à moi)
  sa m’intéresse si on peu développer ;-)
[coupé..]

Merci et à bientôt,
Damien

  De rien

   Georges


Le 02/09/2017 à 20:42, Gaëtan Perrier a écrit :

[coupé..]

Bonjour,

Je suis sur Jessie avec notamment le noyau et les firmware et
librairies graphiques en backports (Intel i5 série 6), et
quelques autres petites appli en backports aussi (mais aucune
n'est critique, seule docker l'est et il n'est pas en bpo).

Est-ce que je peux passer à Stretch sans m'en soucier ou pas ?


J'avoue que c'est la première fois que j'ai autant de paquets en
bpo pour faire fonctionner ma machine, donc je me demande un
peu...


  

J'ai mis à jour en stretch ma machine de boulot qui avait bien
plus de paquets backports sans aucun problème.
Il faut bien suivre la procédure: upgrade, puis dist-upgrade et ne
pas attaquer par le dist-upgrade direct.

A+

Gaëtan

Bonsoir,
Si je peu me permettre, je fais toujours :

   En ce qui concerne la sauvegarde, je ferais aussi un petit
"dpkg --get-selections > fichier"
pour stocker dans ledit fichier l'état des paquets (installé ou
non). Ça permet, en cas de sinistre majeur de n'avoir à
réinstaller que le système de base,

   Ce qui permet de faire :

puis un petit
"dpkg --set-selections < fichier"
   suivi d'un
"apt-get dselect-upgrade"
   te réinstallera tout seul tous les paquets qui étaient installés.

Si je me trompe, corrigez moi ;-)

Georges

C'est effectivement une sage précaution sur une machine importante.
Dans ce cas il faut aussi en plus sauvegarder /etc et une partie
de /var si je ne m'abuse. Il me semble que c'est indiqué dans la
doc d'installation.

Gaëtan

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

[Luis Speciale]

Oups. Forgot to mark this thread as SOLVED

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

[Luis Speciale]

Le 03/09/2017 à 19:40, Thomas Schmitt a écrit

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


Don't forget it.




I formated the USB as FAT32 in my iMac

I downloaded the firmware version

firmware-9.1.0-amd64-netinst.iso

Then I did

sudo cp firmware-9.1.0-amd64-netinst.iso /dev/disk1

When this command finished I had a system message:

"The disk you inserted was not readable by this computer."

and I did

diskutil unmountDisk /dev/disk1

Then all went well. But not the resolution.

So after a little Googling I found this

https://gist.github.com/ed-flanagan/929633981ea548e97f1d

and now it's working like a charm.


And thanks again to all of you


Luis

Re: (solved) how to roll back to jessie

[Fungi4All]

> From: longwi...@yahoo.com
> To: debian-user@lists.debian.org
>>On Mon, 9/4/17, Felix Miata  wrote:
>
>> 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.
>
>> Thanks!
>
> i have used debian for long time (since rex) all support i need comes from 
> this list
> i do not install security update and it not cause trouble for me
>
> and font in text mode in wheezy seems cool
>
> i have an wheezy in /dev/sda2
> and have installed iceweasel today

Not to mention that "upgrading" from wheezy to Devuan Jessie is even simpler 
than
from Jessie 8 to Jessie 1, since there is not so much Junk to remove.

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

[Ricardo Ramos]

Bom saber que deu tudo certo, não sabia que o live do Debian no rescue mode
recuperava ate com LVM criptografado, mais uma pra ter guardado em caso de
emergência.

On Seg, 4 de set de 2017, 05:28 Luiz Carlos  wrote:

> Consegui resolver, a solução foi ter baixado a mesma versão do versão do
> Debian, dar boot pelo DVD e entrar no modo rescue, eu achei bem intuitivo
> aquilo, eu pensei que era pra digitar linha de comando, mas não foi assim,
> o modo rescue restaura com criptografia e tudo, se for ver nem era preciso
> usar a live cd, o grub foi restaurado pro estado que estava antes de
> instalar o Windows 10, ou  seja aparecia no grub o Windows 7, mas nada que
> um update-grub no Debian não resolvesse, está tudo ok agora.
>
> Que alivio em saber que recuperei meu sistema, e meu windows está
> atualizado, obrigado a todos por tudo e desculpe o incomodo.
>
> Pra quem pode sofrer com isso, restaurar no modo rescue tem que ter noção
> de qual é a partição raiz, qual partição instalar o grub e por ai vai, a
> parte da live cd me ajudou um pouco a pegar a noção disso.
>
> Em 4 de setembro de 2017 03:20, Luiz Carlos  escreveu:
>
>> O Debian que estou não é live cd, é só pra ver o lance de rescue, mas
>> será possível restaurar com partições criptografadas?
>>
>> Em 4 de setembro de 2017 03:16, Luiz Carlos  escreveu:
>>
>>> Estou aqui baixando uma distro do Debian equivalente a minha versão,
>>> vamos ver no que vai dar.
>>> Será que danifiquei a minha partição do Linux? Bem, eu consigo montar a
>>> raiz e a home, n sei se tenho esperanças de arrumar.
>>>
>>> Em 4 de setembro de 2017 02:39, Linux - Junior Polegato <
>>> li...@juniorpolegato.com.br> escreveu:
>>>
 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 

Re: network trouble on stretch

[Fungi4All]

> From: mrma...@earthlink.net
> To: debian-user@lists.debian.org
>
> Erik Christiansen composed on 2017-09-04 18:06 (UTC+1000):
>
>> But Fungi4All"s solution is so easy to use that I"m won over, and
>> have implemented it here.
>
> I think I started putting net.ifnames=0 on the kernel command line close to 3
> years ago. :-)

You mean on grub.cfg on the linux command line.  This is what the above 
mentioned procedure does
when grub updates.  If you don't place the modifier in etc/grub then it may 
vanish again, meaning you
will have to do it again.  The same with other modifiers of grub, like default 
# entry, background, timeout.

Re: network trouble on stretch

[Erik Christiansen]

On 04.09.17 04:42, Felix Miata wrote:
> Erik Christiansen composed on 2017-09-04 18:06 (UTC+1000):
> 
> > But Fungi4All's solution is so easy to use that I'm won over, and
> > have implemented it here. 
> 
> I think I started putting net.ifnames=0 on the kernel command line close to 3
> years ago. :-)
> 
> More than that it's been around:
> 

Crikey, there's a lot of very literal people on this list.
My courtesy to another poster on_this_thread does not logically preclude
the existence of xxx in other parts of the universe, present or past.

Get a life.

Erik

Re: network trouble on stretch

[Felix Miata]

Erik Christiansen composed on 2017-09-04 18:06 (UTC+1000):

> But Fungi4All's solution is so easy to use that I'm won over, and
> have implemented it here. 

I think I started putting net.ifnames=0 on the kernel command line close to 3
years ago. :-)

More than that it's been around:

-- 
"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: Meu Debian não reconhece DVD Virgem Elgin 16x.

[Luiz Carlos]

Ah, ignorem, já foi resolvido, deve ter sido problema com a outra mídia.

Em 4 de setembro de 2017 05:30, Luiz Carlos  escreveu:

> Galera, tenho dual boot com Windows 10 agora, ele também reconhece o DVD
> virgem, mas aqui no Debian não está dando certo, alguém sabe como resolver?
> Valeu.
>
> Em 2 de setembro de 2017 20:47, Luiz Carlos  escreveu:
>
>> DVD e CD com dados reconhece de boa, mas agora DVD virgem não reconheceu,
>> eu tenho um Dual Boot com Windows Seven e reconheceu normalmente, dai eu
>> gravei e deu certo.
>>
>> Como eu faço pro meu Debian reconhecer DVD virgens?
>>
>
>

Re: Meu Debian não reconhece DVD Virgem Elgin 16x.

[Luiz Carlos]

Galera, tenho dual boot com Windows 10 agora, ele também reconhece o DVD
virgem, mas aqui no Debian não está dando certo, alguém sabe como resolver?
Valeu.

Em 2 de setembro de 2017 20:47, Luiz Carlos  escreveu:

> DVD e CD com dados reconhece de boa, mas agora DVD virgem não reconheceu,
> eu tenho um Dual Boot com Windows Seven e reconheceu normalmente, dai eu
> gravei e deu certo.
>
> Como eu faço pro meu Debian reconhecer DVD virgens?
>

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

[Luiz Carlos]

Consegui resolver, a solução foi ter baixado a mesma versão do versão do
Debian, dar boot pelo DVD e entrar no modo rescue, eu achei bem intuitivo
aquilo, eu pensei que era pra digitar linha de comando, mas não foi assim,
o modo rescue restaura com criptografia e tudo, se for ver nem era preciso
usar a live cd, o grub foi restaurado pro estado que estava antes de
instalar o Windows 10, ou  seja aparecia no grub o Windows 7, mas nada que
um update-grub no Debian não resolvesse, está tudo ok agora.

Que alivio em saber que recuperei meu sistema, e meu windows está
atualizado, obrigado a todos por tudo e desculpe o incomodo.

Pra quem pode sofrer com isso, restaurar no modo rescue tem que ter noção
de qual é a partição raiz, qual partição instalar o grub e por ai vai, a
parte da live cd me ajudou um pouco a pegar a noção disso.

Em 4 de setembro de 2017 03:20, Luiz Carlos  escreveu:

> O Debian que estou não é live cd, é só pra ver o lance de rescue, mas será
> possível restaurar com partições criptografadas?
>
> Em 4 de setembro de 2017 03:16, Luiz Carlos  escreveu:
>
>> Estou aqui baixando uma distro do Debian equivalente a minha versão,
>> vamos ver no que vai dar.
>> Será que danifiquei a minha partição do Linux? Bem, eu consigo montar a
>> raiz e a home, n sei se tenho esperanças de arrumar.
>>
>> Em 4 de setembro de 2017 02:39, Linux - Junior Polegato <
>> li...@juniorpolegato.com.br> escreveu:
>>
>>> 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
>   

Re: Laptop recommendation

[Byung-Hee HWANG (황병희, 黃炳熙)]

In Article <20170903133817.hppdseouwbc3kvjk@grond>,
 Jonas Hedman  writes:

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

There is no option for intalling under chromebook. People should install Linux
always with chromebook. That is why i did buy chromebook. Someone did
try to install FreeBSD, but it is very very very hard. 

Actually i am happy with Linux in chromebook~  

Sincerely, Byung-Hee.

-- 
^고맙습니다 _救濟蒼生_ 감사합니다_^))//

Re: network trouble on stretch

[Erik Christiansen]

On 03.09.17 20:09, Glenn English wrote:
> 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.

Most eloquently put, and you speak for thousands.

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

Noo-oo, I firmly believe they're smoking it.

In addition to Fungi4All's solution, there's also ifrename (in package
of same name):

DESCRIPTION
 Ifrename is a tool allowing you to assign a consistent name to each of
 your network interfaces.

But Fungi4All's solution is so easy to use that I'm won over, and
have implemented it here.

Erik

Re: (solved) how to roll back to jessie

[Long Wind]

On Mon, 9/4/17, Felix Miata  wrote:

 
 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/
 

Thanks!

i have used debian for long time (since rex)
all support i need comes from this list
i do not install security update
and it not cause trouble for me

and font in text mode in wheezy seems cool

i have an wheezy in /dev/sda2
and have installed iceweasel today

 

Re: Debian9 just showing me black screen after grub.

[tomas]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Mon, Sep 04, 2017 at 01:32:07PM +0800, Jaehong Park wrote:
> I just installed Debian 9 yesterday.
> And I gave a fatal problem with login screen.
> After grub it only showing me black screen, but enter my password it starts 
> showing me my desktop environment screen correctly.
> 
> What’s the cause?

Hm. It looks a bit as if your monitor isn't coping well with the video
mode your login screen has?

Do you have a desktop computer with separate monitor? Or a laptop?

Tell us a bit more about your monitor, your graphics card etc.

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

iEYEARECAAYFAlms+RoACgkQBcgs9XrR2kZ7CACfZg+HAuep3WrQjvLiIwEqNc8t
n0YAniX6oCJBmYZMcu/+BQK2dJBXd1lD
=KMLV
-END PGP SIGNATURE-

Debian9 just showing me black screen after grub.

[Jaehong Park]

I just installed Debian 9 yesterday.
And I gave a fatal problem with login screen.
After grub it only showing me black screen, but enter my password it starts 
showing me my desktop environment screen correctly.

What’s the cause?

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

[Luiz Carlos]

O Debian que estou não é live cd, é só pra ver o lance de rescue, mas será
possível restaurar com partições criptografadas?

Em 4 de setembro de 2017 03:16, Luiz Carlos  escreveu:

> Estou aqui baixando uma distro do Debian equivalente a minha versão, vamos
> ver no que vai dar.
> Será que danifiquei a minha partição do Linux? Bem, eu consigo montar a
> raiz e a home, n sei se tenho esperanças de arrumar.
>
> Em 4 de setembro de 2017 02:39, Linux - Junior Polegato <
> li...@juniorpolegato.com.br> escreveu:
>
>> 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/: 

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

[Luiz Carlos]

Estou aqui baixando uma distro do Debian equivalente a minha versão, vamos
ver no que vai dar.
Será que danifiquei a minha partição do Linux? Bem, eu consigo montar a
raiz e a home, n sei se tenho esperanças de arrumar.

Em 4 de setembro de 2017 02:39, Linux - Junior Polegato <
li...@juniorpolegato.com.br> escreveu:

> 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