Re: Partitionnement d'un serveur web

[Pierre L.]

Bonjour à tous,

Le 15/01/2019 à 07:29, Pascal Hambourg a écrit :
> Le 15/01/2019 à 00:46, Florian Blanc a écrit :
>> à chaque mise à jour du kernel "grub-install /dev/sda1" "grub-install
>> /dev/sdb1" (corrigé) c'est pas la mort.
>
> Je suppose que cela répond à l'objection que j'ai formulée à
> l'encontre de ton précédent message.
>
> Primo, il n'est pas nécessaire d'exécuter grub-install à chaque mise à
> jour du noyau. GRUB n'est pas LILO. Il faut seulement mettre à jour le
> fichier de configuration grub.cfg avec grub-mkconfig ou update-grub.
Humm, j'ai cette impression que la commande update-grub, suite à mise à
jour de kernel par exemple, ne mettra à jour que celui sur lequel la
machine a booté ?
En gros, si c'est GRUB2 qui est sur /dev/sda qui a lancé Debian, cette
commande ne mettra pas à jour l'amorçage dans /dev/sdb
Ou alors je suis à coté de la plaque ? Oui ca relève encore un peu du
mystique pour le moment, car pas encore pris le temps de me pencher sur
le sujet ;)

J'avoue que c'est pour cela que j'avais aussi ce petit workaround comme
Florian pour forcer aussi rapidement la mise à jour coté /dev/sdb...

> Secundo, l'exécution de grub-install sur d'autres disques lors d'une
> mise à jour du paquet grub-pc peut être automatisée dans la
> configuration du paquet avec dpkg-reconfigure.
C'est donc ici qu'il serait intéressant de cocher les 2 disques /dev/sda
et /dev/sdb afin d'avoir ce GRUB2 qui se mettrait à jour comme tu nous
le dis précédemment ?
(première image trouvée sur le net... histoire d'illustrer)
https://manual.siduction.org/static/images-common/images-grub2/grub2-convert-1.png

Et donc sur une installation déjà faite, un dpkg-reconfigure grub-pc
pourrait remédier à ce manque et automatiser cette MAJ de GRUB2 sur les
2 disques à chaque update de kernel. Humm humm, c'est bon ca ! (si j'ai
bien compris le principe ?)



signature.asc
Description: OpenPGP digital signature

Re: Partitionnement d'un serveur web

[Pascal Hambourg]

Le 15/01/2019 à 00:46, Florian Blanc a écrit :

à chaque mise à jour du kernel "grub-install /dev/sda1" "grub-install
/dev/sdb1" (corrigé) c'est pas la mort.


Je suppose que cela répond à l'objection que j'ai formulée à l'encontre 
de ton précédent message.


Primo, il n'est pas nécessaire d'exécuter grub-install à chaque mise à 
jour du noyau. GRUB n'est pas LILO. Il faut seulement mettre à jour le 
fichier de configuration grub.cfg avec grub-mkconfig ou update-grub.


Secundo, l'exécution de grub-install sur d'autres disques lors d'une 
mise à jour du paquet grub-pc peut être automatisée dans la 
configuration du paquet avec dpkg-reconfigure.


Tertio, le problème n'est pas là. grub-install n'installe qu'une partie 
de GRUB sur le disque spécifié. L'autre partie (dont le fichier de 
configuration du menu de démarrage), ainsi que le noyau et l'initramfs, 
sont dans /boot. Si le contenu de /boot n'est pas en RAID, donc sur un 
seul disque, alors la défaillance de ce disque entraîne l'impossibilité 
de démarrer le système, GRUB s'arrêtant sur le shell de secours limité 
"grub rescue>". Et toute solution à base de deux partitions /boot serait 
plus compliquée que /boot en RAID.

Re: Suppression de /etc/apt/trusted.gpg

[Jérôme]

Le lundi 14 janvier 2019 à 21:26 +0100, Étienne Mollier a écrit :
> Bonjour Benoit,
> 
> Naïvement, j'aurais fait en sorte que l'utilisateur en question
> « _apt » puisse lire le trousseau de clés GPG.  Après un coup
> d'œil dans mon installation Sid, le fichier /etc/apt/trusted.gpg
> n'est en fait pas présent.  À la place les clés sont stockées
> dans un ensemble de fichiers sous /etc/apt/trusted.gpg.d/.
> 
> Toujours aussi naïvement, j'aurais donc tendance à penser que
> l'utilité de ce fichier n'est plus, en tout cas pour une
> installation basique, et que donc vous n'avez pas mal fait.
> 
> Gardez tout de même le fichier à portée de main, des fois que...
> 
> Amicalement,

Ça m'étonnerait qu'il n'y ait pas eu une explication dans la mise a jour, et
un message a root. 

Le principe des trucs.conf.d c'est de remplacer le fichier de config monobloc
truc.conf par des fichiers qui contiennent les blocs de configuration
nécessaires mis dans le dossier truc.conf.d/ ce qui est plus facile a gérer
pour les configurations dynamiques (au branchement d'un truc...) et évite de
tout charger inutilement.

Dans ce cas le fichier monobloc de configuration statique est supprimé. 

On peut toujours le remettre ou le trouver dans certains cas, mais l'idée est
là. Par exemple xorg.conf = statique   xorg.conf.d/* = dynamique (plug'n
play). C'est mieux de faire un xorg.conf.d/50-ma-souris-gamer.conf qui va se
charger au branchement de ce modèle de souris que de gérer de manière statique
tous les cas dans xorg.conf

Pour GPG il ne s'agit pas de brancher une souris, mais la gestion dynamique a
son intérêt pour la gestion automatisée.

cyrus-imapd not starting after upgrade from Jessie to Stretch

[Daniel Bareiro]

Hi all!

After quite some time, today I decided to update the mail server to
Debian Stretch.

All without problems until I reach the part of cyrus-imapd that does not
start. This is what I see in the log:

--
Jan 14 23:10:45 mail systemd[1]: Started Cyrus IMAP/POP3 daemons.
Jan 14 23:10:45 mail cyrus/ctl_cyrusdb[5318]: skiplist: clean shutdown
file missing, updating recovery stamp
Jan 14 23:10:45 mail cyrus/ctl_cyrusdb[5318]: recovering cyrus databases
Jan 14 23:10:45 mail cyrus/ctl_cyrusdb[5318]: done recovering cyrus
databases
Jan 14 23:10:46 mail cyrus/cyr_expire[5332]: Repacking mailbox
user.admin.TareasCron version 12
Jan 14 23:10:46 mail cyrus/cyr_expire[5332]: Expired 0 and expunged 0
out of 28809 messages from 80 mailboxes
Jan 14 23:10:46 mail cyrus/cyr_expire[5332]: duplicate_prune: pruning
back 3.00 days
Jan 14 23:10:46 mail cyrus/cyr_expire[5332]: duplicate_prune: purged 0
out of 438 entries
Jan 14 23:10:46 mail cyrus/tls_prune[5335]: twoskip: invalid magic
header: /var/lib/cyrus/tls_sessions.db
Jan 14 23:10:46 mail cyrus/tls_prune[5335]: cyrusdb: opening
/var/lib/cyrus/tls_sessions.db with backend skiplist (requested twoskip)
Jan 14 23:10:46 mail cyrus/tls_prune[5335]: skiplist: recovered
/var/lib/cyrus/tls_sessions.db (223 records, 41200 bytes) in 0 seconds
Jan 14 23:10:46 mail cyrus/tls_prune[5335]: skiplist: checkpointed
/var/lib/cyrus/tls_sessions.db (223 records, 41200 bytes) in 0.091 sec
Jan 14 23:10:46 mail cyrus/tls_prune[5335]: tls_prune: purged 2 out of
223 entries
Jan 14 23:10:46 mail cyrus/master[5311]: cannot find executable for
service 'nntp'
Jan 14 23:10:46 mail cyrus/master[5311]: exiting
Jan 14 23:10:46 mail systemd[1]: cyrus-imapd.service: Main process
exited, code=exited, status=78/n/a
Jan 14 23:10:46 mail systemd[1]: cyrus-imapd.service: Unit entered
failed state.
Jan 14 23:10:46 mail systemd[1]: cyrus-imapd.service: Failed with result
'exit-code'.
--

I'm not sure what the problem is but that "invalid magic header" makes
me think that maybe it changed the header format of
/var/lib/cyrus/tls_sessions.db and the migration process did not do the
corresponding conversion. Any ideas that can bring more light?

The associated problem is that because of this it seems that Postfix can
not deliver the mails since there is no /var/run/cyrus/socket/lmtp.


Thanks in advance.

Kind regards,
Daniel



signature.asc
Description: OpenPGP digital signature

Re: Unable to Access a Foreign Volume Group

[Jens Holzhäuser]

On Sun, Jan 13, 2019 at 05:39:20PM +0100, Martin wrote:
> Hi Jens,
> 
> my first shot would be setting the actual system id to
> 'zaphod1105820973' like described in the lvmsystemid man page. I'm not
> sure, how this uname or lvmlocal work, so I would try setting
> system_id_source to machineid or file.
> First, look if /etc/machine-id matches. If not, put is may be in a 
> /etc/lvm/system-id.

/etc/machine-id is a seemingly random 32 char hex string, bearing no
resemblance to the system ID of vg00.
/etc/lvm/system-id doesn't exist.

The server is explicitly configured with not having a system ID in
/etc/lvm/lvm.conf:

system_id_source = "none"


> As this alters nothing in the LVM itself, this should not be harmful as a try.

On the one hand, yes. On the other, I am very hesitant to mess with the
server lvm configuration, and potentially having lvm lose access to
vg01, which hosts all of the servers partitions.

I am going to read up more on this topic, and recovery options for the
case of any system ID issues during boot; just to be prepared.
I've not have had ever any trouble with lvm in all the years of using
it ("it just worked"), until now.

The lvmsystemid man page also mentions to use the lvmlocal.conf entry

   local {
   extra_system_ids = [ "my_other_name" ]
   }

instead the command line option; I might give that a try, as it seems
fairly safe.


> Am 13.01.19 um 17:10 schrieb Jens Holzhäuser:
> > Hello,
> > 
> > I have a buster/sid system with two volume groups that have made no
> > issue for years.
> 
> [...]
> 
> > 
> > # lvm systemid
> >   system ID:
> > # vgs -o systemid vg00
> >   Cannot access VG vg00 with system ID zaphod1105820973 with unknown local 
> > system ID.
> >   Cannot access VG vg00 with system ID zaphod1105820973 with unknown local 
> > system ID.
> > # vgs --foreign -o +systemid
> >   VG   #PV #LV #SN Attr   VSize   VFree   System ID
> >   vg00   1   8   0 wz--n- 930.55g  20.00g zaphod1105820973
> >   vg01   1   9   0 wz--n-  <1.50t 534.37g
> > # vgchange --config 'local/extra_system_ids=["zaphod1105820973"]' 
> > --systemid "" vg00
> >   Cannot access VG vg00 with system ID zaphod1105820973 with unknown local 
> > system ID.
> >   Cannot access VG vg00 with system ID zaphod1105820973 with unknown local 
> > system ID.
> > 
> > 
> > Any help is appreciated to get back acess to the VG, vgchange (and
> > vgexport) seem to be ignoring it despite providing the extra system id.
> 
> 
> [...]
> 
> > Thanks,
> > 
> > 
> > Jens
> 
> Martin

Jens

Re: Command line mounting all partitions of pluggable device

[Richard Owlett]

On 01/14/2019 02:18 PM, David Wright wrote:

On Mon 14 Jan 2019 at 10:20:51 (-0600), Richard Owlett wrote:

On 01/14/2019 09:22 AM, Thomas Schmitt wrote:

rhkra...@gmail.com wrote:

Assuming there are entries in fstab for each partition, [...]
for i in  /dev/sd*;  do  mount $i; done


Rchard Owlett wrote:

There are not.


In the most general case i would have a where-to-mount directory with
lots of directories for the various partitions (here 10 drives with
20 partitions each).


But thankfully I don't have to deal with the most general case as I am
as compulsive about giving all partitions a reasonably unique label as
Debian is about assigning UUIDs.


"Reasonably unique" doesn't really cut it.


For my current 2.2TB, the labels seem acceptably unique:
MainCdrive	my-big-dvd	fromdell	richardofdell	debversionricharProjects	F_drive	OldMachine		fullstretch	debian8.6		recover-common 
tomboy-testing	owlcommon	new-net-inst	good-fvwm	tst_mysql	tst_mariadb 
dummy		target		gddrescued_commo	jessie8-6-6	common		stretch-2nd 
17oct2017	common-bak		backup_homedirs			myhome		dectest		scratch_pad	 
FreeAgentGoFlexDrive		windows		GOFLEXPART5	recovered	mate-full 
post-failure	MISC-backups	

Re: Partitionnement d'un serveur web

[Florian Blanc]

à chaque mise à jour du kernel "grub-install /dev/sda1" "grub-install
/dev/sdb1" (corrigé) c'est pas la mort.
mais as you want fais toi plaisir mon ami.


Le lun. 14 janv. 2019 à 20:59, Pascal Hambourg  a
écrit :

> Le 14/01/2019 à 06:24, Fabrice Delvallée a écrit :
> >
> > faut-il mettre aussi LVM sur les SSD ?
>
> Oui, j'utiliserais LVM sur les SSD pour le système, mais dans un VG
> distinct des disques durs. On ne mélange pas les torchons et les
> serviettes. Mieux vaut utiliser LVM et ne pas en avoir besoin que
> l'inverse. Ses fonctionnalités (redimensionnement à chaud, snapshots...)
> peuvent être utiles un jour.
>
> > J'ai cru comprendre que grub
> > n'est pas compatible LVM, dans ce cas il me faut une partition /boot
> > séparée.
>
> GRUB 2, la version actuelle de GRUB, est compatible avec LVM, le RAID
> logiciel (sauf le RAID linear, bizarrement) et leurs combinaisons. Donc
> une partition ou un ensemble RAID séparé pour /boot n'est pas
> indispensable. Mais on peut préférer garder un /boot séparé hors LVM
> pour intervenir plus facilement en cas de problème avec LVM (on aura au
> moins le shell de secours de l'initramfs).
>
>

Re: We've got a problem. Debian "Jessie" box won't launch X or Tomcat, and USB drive won't mount

[Dan Ritter]

James H. H. Lampert wrote: 
> Ladies and Gentlemen:
> 
> We've got a Debian 8 box (an old Dell 400SC) that won't launch X (it boots
> to a command line) or Tomcat, nor mount a USB hard drive that we use for
> backups.
> 
> It will, however, accept ssh connections.
> 
> In the boot sequence, I see "Failed" where it tries to mount the USB drive.
> I also can't seem to get that drive to mount on anything else, which
> suggests that it has been corrupted.
> 
> Can somebody suggest where to start looking for the problem?

Clean it out. If it's old, it might be dusty.

Then: is it supposed to start X, and failing, or is it happily
coming up to a command line because that's what it's been told
to do?

Log in, and run startx. If you get X11, then the box is fine
with that and you might need to install or reconfigure a display
manager like xdm or lightdm.

If you get an error message instead, tell us about it. Also,
look for details in /var/log/Xorg.0.log

Tomcat: how does it fail when you start tomcat by hand?

USB for backups: the hard drive is dead. Get a new one. Test it.

-dsr-

We've got a problem. Debian "Jessie" box won't launch X or Tomcat, and USB drive won't mount

[James H. H. Lampert]

Ladies and Gentlemen:

We've got a Debian 8 box (an old Dell 400SC) that won't launch X (it 
boots to a command line) or Tomcat, nor mount a USB hard drive that we 
use for backups.


It will, however, accept ssh connections.

In the boot sequence, I see "Failed" where it tries to mount the USB 
drive. I also can't seem to get that drive to mount on anything else, 
which suggests that it has been corrupted.


Can somebody suggest where to start looking for the problem?

--
James H. H. Lampert

Re: Migrate Stretch to New UEFI Build?

[deloptes]

Patrick Bartek wrote:

>> Patrick Bartek wrote:
>> 
>> > I never could understand that type of "reasoning." With me, if there's
>> > no NEED, it's not done. I'm very much the pragmatist. Always have
>> > been even as a child, and never likely to change.
>> 
>> you need it but you don't know yet
> 
> Unlikely.  Haven't needed LVM (or RAID for that matter) in the almost 20
> years Linux has been my personal OS.
> 

For your private use, it might be OK, but when you need flexibility, you
understand what you were missing. And mostly you start thinking from there
and decide if it is worth implementing.

>> For example I leave some percentage of the disc unused and can increase
>> the any partition when needed - because I do not know which one will get
>> filled first. Now this can be challengeing without lvm and lvm does not
>> come with significant overhead. So why not?!
> 
> I'm VERY diligent about pruning and deleting old or unneed files, data,
> apps, etc.  For example, my Wheezy install which I used for 5 years
> (until support was dropped): / 16GB 45% full; /home 207GB 43% full. I'm
> not a gamer.  So, no humongous installs there.  I have no music, video
> or movies taking up space. I don't even use a desktop environment.
> Window manager and a single panel only. And I'm the only user of the
> system.  My Stretch install (about 6 months old) has even lower
> percentages, but that's to be expected.
> 
> Obviously, how and what you use for system for are very different from
> mine.

Obviously, but even for a smaller system it does not hurt to use LVM.
Encryption is worth using on notebook or when you have sensitive data. It
comes at a high price, but LVM is almost for free. 
I am also conservative in deleting history. I installed and tried couple of
distros between 1998 and 2002 on some older 686 then upgraded and moved to
amd64 with the time the system grew up - personal data, accounting, videos,
albums, software, development, open source, virtual machines ... this is
now 3x2TB and 2x1TB disks in RAID1, encrypted and with LVM on top.
Without good planning and flexibility to manage bigger amounts of data you
are doomed.

regards

Re: Migrate Stretch to New UEFI Build?

[Patrick Bartek]

On Sun, 13 Jan 2019 22:37:47 -0500
Stefan Monnier  wrote:

> >> > more research, I've concluded I have no need for LVM, but encryption
> >> Side note: whether I need LVM or not, I just always use it.  
> > I never could understand that type of "reasoning." With me, if there's
> > no NEED, it's not done.  I'm very much the pragmatist.  
> 
> Not sure if pragmatism has much to do with it: I use LVM because it's

You'd be surprised how much it can affect decisions and choices.  And
make logic easier.  Set your criteria and requirements, and stick to
them. Now I'm not saying it is any better than other methods, but it
does work best for me.  And it came naturally.

> more convenient, even if in the end what I do with it could have been
> done with partitions.

I keep my personal systems simple: /, /home, swap.  With 20 years
experience using Linux, I pretty much know how big my partitions need
to be and so once created never need to be resized.  However, with the
new system I'm building, there will be two additional partitions and
since they will be GPT/UEFI, no extended or logical partitions to fool
with.

B

Re: Migrate Stretch to New UEFI Build?

[Patrick Bartek]

On Sun, 13 Jan 2019 23:19:35 +0100
deloptes  wrote:

> Patrick Bartek wrote:
> 
> > I never could understand that type of "reasoning." With me, if there's
> > no NEED, it's not done. I'm very much the pragmatist. Always have
> > been even as a child, and never likely to change.  
> 
> you need it but you don't know yet

Unlikely.  Haven't needed LVM (or RAID for that matter) in the almost 20
years Linux has been my personal OS.

> For example I leave some percentage of the disc unused and can increase the
> any partition when needed - because I do not know which one will get filled
> first. Now this can be challengeing without lvm and lvm does not come with
> significant overhead. So why not?!

I'm VERY diligent about pruning and deleting old or unneed files, data,
apps, etc.  For example, my Wheezy install which I used for 5 years
(until support was dropped): / 16GB 45% full; /home 207GB 43% full. I'm
not a gamer.  So, no humongous installs there.  I have no music, video
or movies taking up space. I don't even use a desktop environment.
Window manager and a single panel only. And I'm the only user of the
system.  My Stretch install (about 6 months old) has even lower
percentages, but that's to be expected.

Obviously, how and what you use for system for are very different from
mine.

B 

Re: kernel "unsigned" in sid

[Richard Hector]

On 14/01/19 11:20 PM, Vincent Lefevre wrote:
> On 2019-01-11 09:52:04 -0500, Michael Stone wrote:
>> On Fri, Jan 11, 2019 at 09:55:45AM +0100, dot...@gmail.com wrote:
>>> I recently came across an inconsistency in sid that it seems difficult (to 
>>> me)
>>> to overcome.
>>>
>>> A kernel package named linux-image-4.19.0-1-amd64-unsigned provides the 
>>> running
>>> kernel but, since few days ago, it creates conflicts with the metapackage
>>> linux-image-amd64 (bercause it depends on linux-image-4.19.0-1-amd which, in
>>> turn, conflicts with the installed kernel).
>>>
>>> I can't trivially replace the "unsigned" (BTW, what does "unsigned" stand 
>>> for,
>>> anyway?) version with linux-image-4.19.0-1-amd because of the same version
>>> number.
>>>
>>> I'm not really worried because this will probably be solved when moving to 
>>> the
>>> next kernel release but the situation is a bit annoying.
>>>
>>> Is there any solution?
>>
>> How did you get the unsigned kernel installed in the first place? It's not
>> typically installed, and I don't see any dependencies that would pull it in.
> 
> Until a few weeks ago, it could be installed due to a "Provides:".
> See the following bug I had reported:
> 
>   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916927
> 
> This problem is now solved, i.e. the "Provides:" was dropped.
> But perhaps this is what is causing the *temporary* issue the
> user has above.

That's how I got that kernel via backports - the unsigned version of
4.19 is the only one available in stretch-backports.

What worries me more than it being unsigned is that it appears to be
Tainted - is that normal for bpo kernels? I don't remember seeing it in
the past.

Richard



signature.asc
Description: OpenPGP digital signature

Re: Como pagar mideuda

[qorg11]

On Mon, Jan 14, 2019 at 01:18:47PM -0500, alexcarvajalvargas2812 wrote:
> 
> 
> 
> 
> Enviado desde mi Samsung Mobile de Claro

Vale, supongamos que quieres que te enseñemos a pagar tu deuda.
Supondre que estás desesperado y acabaste por preguntar en una lista de correo 
de Debian-

¿Podrías ir al banco a pagarla?
-- 
GPG Key: https://vxempire.xyz/pgp.txt
Happy hacking

Re: Suppression de /etc/apt/trusted.gpg

[Étienne Mollier]

Benoit, au 2019-01-14 :
> Bonjour,
>
> J'ai voulu ajouter testing dans mon source.list(avec un
> Pin-Priority pour rester en stable) et j'avais des messages
> d'alerte quand je faisais
>
> apt update
>
> Une recherche avec le message me conduit à un post qui suggère
> de supprimer /etc/apt/trusted.gpg.
>
> Je le fais et ça fonctionne sans message d'alerte.
>
> apt n'a pas recréé un nouveau fichier...
>
> Est-ce que j'ai bien fait ?
>
> Si pas je l'ai toujours et peu le remettre à sa place.
>
> Voici le message que je recevais
>
> W: http://files2.eid.belgium.be/debian/dists/stretch/InRelease: The key(s) in 
> the keyring /etc/apt/trusted.gpg are ignored as the file is not readable by 
> user '_apt' executing apt-key.
[...]

Bonjour Benoit,

Naïvement, j'aurais fait en sorte que l'utilisateur en question
« _apt » puisse lire le trousseau de clés GPG.  Après un coup
d'œil dans mon installation Sid, le fichier /etc/apt/trusted.gpg
n'est en fait pas présent.  À la place les clés sont stockées
dans un ensemble de fichiers sous /etc/apt/trusted.gpg.d/.

Toujours aussi naïvement, j'aurais donc tendance à penser que
l'utilité de ce fichier n'est plus, en tout cas pour une
installation basique, et que donc vous n'avez pas mal fait.

Gardez tout de même le fichier à portée de main, des fois que...

Amicalement,
-- 
Étienne Mollier 

Re: Command line mounting all partitions of pluggable device

[Brian]

On Mon 14 Jan 2019 at 10:20:51 -0600, Richard Owlett wrote:

> On 01/14/2019 09:22 AM, Thomas Schmitt wrote:
> > Hi,
> > 
> > rhkra...@gmail.com wrote:
> > > > Assuming there are entries in fstab for each partition, [...]
> > > > for i in  /dev/sd*;  do  mount $i; done
> > 
> > Rchard Owlett wrote:
> > > There are not.
> > 
> > In the most general case i would have a where-to-mount directory with
> > lots of directories for the various partitions (here 10 drives with
> > 20 partitions each).
> 
> But thankfully I don't have to deal with the most general case as I am as
> compulsive about giving all partitions a reasonably unique label as Debian
> is about assigning UUIDs.

Would you like to say how you designate unique labels? Is there a
pattern to them on a particular device? As in: p1, p2 etc.

In the light of

 > Each device is normally associated with a specific function
 > (e.g. sneaker-net) or personal project.

do you distinguish between devices by means of the label? As in pers-p1,
pers-p2 etc.

-- 
Brian.

Re: Command line mounting all partitions of pluggable device

[David Wright]

On Mon 14 Jan 2019 at 10:20:51 (-0600), Richard Owlett wrote:
> On 01/14/2019 09:22 AM, Thomas Schmitt wrote:
> > rhkra...@gmail.com wrote:
> > > > Assuming there are entries in fstab for each partition, [...]
> > > > for i in  /dev/sd*;  do  mount $i; done
> > 
> > Rchard Owlett wrote:
> > > There are not.
> > 
> > In the most general case i would have a where-to-mount directory with
> > lots of directories for the various partitions (here 10 drives with
> > 20 partitions each).
> 
> But thankfully I don't have to deal with the most general case as I am
> as compulsive about giving all partitions a reasonably unique label as
> Debian is about assigning UUIDs.

"Reasonably unique" doesn't really cut it. You're better off
generating a nonce name for the real mount point like so:

Newmtpt=/media/richard/$(uuidgen)
mkdir -p "$Newmtpt"

and then making a symlink to it using your LABELs. That way, mounting
will always succeed even if creating the link fails (which tells you
to take some action to rectify things).

Cheers,
David.

Re: Partitionnement d'un serveur web

[Pascal Hambourg]

Le 14/01/2019 à 06:24, Fabrice Delvallée a écrit :


faut-il mettre aussi LVM sur les SSD ?


Oui, j'utiliserais LVM sur les SSD pour le système, mais dans un VG 
distinct des disques durs. On ne mélange pas les torchons et les 
serviettes. Mieux vaut utiliser LVM et ne pas en avoir besoin que 
l'inverse. Ses fonctionnalités (redimensionnement à chaud, snapshots...) 
peuvent être utiles un jour.



J'ai cru comprendre que grub
n'est pas compatible LVM, dans ce cas il me faut une partition /boot
séparée.


GRUB 2, la version actuelle de GRUB, est compatible avec LVM, le RAID 
logiciel (sauf le RAID linear, bizarrement) et leurs combinaisons. Donc 
une partition ou un ensemble RAID séparé pour /boot n'est pas 
indispensable. Mais on peut préférer garder un /boot séparé hors LVM 
pour intervenir plus facilement en cas de problème avec LVM (on aura au 
moins le shell de secours de l'initramfs).

Re: Partitionnement d'un serveur web

[Pascal Hambourg]

Le 14/01/2019 à 13:09, Florian Blanc a écrit :

3 partitions primaire :
(même taille sur les deux disques)
Une de environs 500Mo pour ( /boot )
Une de environs 4096Mo pour ( swap )
Le reste pour ( / )
Tu configure seulement le swap et / en raid1


Pourquoi pas /boot ?


Tu encrypt ton swap et / via l'interface d'installation.
Après tu peux utiliser LVM mais je trouve pas nécessaire.


L'avantage de LVM est qu'on peut mettre tous les volumes logiques dans 
un unique volume chiffré, donc une seule passphrase à taper au démarrage.



ensuite "grub-install /dev/sda1" "grub-install /dev/sda2"


Il y a un léger problème : si /boot n'est pas en RAID, alors il est sur 
un seul des deux disques et si ce disque tombe alors le GRUB présent sur 
le disque restant sans /boot ne pourra pas démarrer le système. Pour 
démarrer avec l'autre disque seul il faudrait synchroniser le contenu de 
sa partition de 500 Mo avec le contenu de /boot. C'est presque du RAID 1 
mais à gérer manuellement tout en maintenant les légères différences 
dans les deux grub.cfg (UUID). Bref, /boot en RAID 1 serait beaucoup 
plus simple et fiable, et GRUB sait le gérer.

error en Pacemaker

[Eduardo Visbal]

Saludos compañeros Debianitas

Queria realizarles una consulta, poseo 3 maquinas virtuales en qemu-kvm con
debian 9 cada una; cada maquina tiene 2 interfaz de red, a su vez tiene
instalado corosync pacemaker y postgresql...

Pero el dettalle es que me esta dando un error cuando consulto el status
del pacemaker y me arroja esto:

Failed Actions:
* fence_vm_node3_start_0 on server01 'unknown error' (1): call=24,
status=Error, exitreason='none',
last-rc-change='Mon Jan 14 16:13:52 2019', queued=1ms, exec=1464ms
* fence_vm_node3_start_0 on server2 'unknown error' (1): call=24,
status=Error, exitreason='none',
last-rc-change='Mon Jan 14 16:26:36 2019', queued=0ms, exec=1470ms

Reviso los logs y lo unico que puedo ver es que no hay conexion con el
nodo3...
No tengo mucha experiencia con alta disponiblidad, pero de lo que he leido
no consigo que pueda ser este error.




*Eduardo VisbalLinuxero #440451http://esdebianfritto.blogspot.com/
*

Como pagar miadeuduo

[alexcarvajalvargas2812]

Enviado desde mi Samsung Mobile de Claro

Como pagar lafactura120.000

[alexcarvajalvargas2812]

Enviado desde mi Samsung Mobile de Claro

Como pagar mideuda

[alexcarvajalvargas2812]

Enviado desde mi Samsung Mobile de Claro

Re: /dev/disk/by-id/ in testing

[Pascal Hambourg]

Le 14/01/2019 à 11:09, Vincent Lefevre a écrit :

On 2019-01-14 11:06:01 +0100, Vincent Lefevre wrote:

On 2019-01-08 20:12:43 +0100, Pascal Hambourg wrote:

This issue is not specific to lilo. It would affect grub-pc updates too,
because the boot device is specified by device id.

For example on my system :
$ debconf-show grub-pc
(...)
* grub-pc/install_devices: /dev/disk/by-id/ata-WDC_WD1200BEVE-00WZT0_...

The issue would happen less often - only when updating the grub-pc
package instead of on any kernel update - but it would still happen.


... which was what happened to me a few days ago!


BTW, a display bug in the terminal made the problem worse, because
I could not select a device for GRUB installation. So, currently,
new GRUB versions are no longer installed.


Which display bug ? During the system installation ?
You can install new versions of GRUB by hand with

# grub-install /dev/disk/by-id/...

Or you can reconfigure grub-pc with

# dpkg-reconfigure grub-pc

If the display bug is still present in the default "dialog" 
(curses-like) front-end, you can try to use the "readline" (command 
line-like) front-end  with "--frontend=readline" when running 
dpkg-reconfigure.

Re: Em podeu donar un cop de ma amb un bug?

[Robert Marsellés]

El 12/1/19 a les 12:40, a...@probeta.net ha escrit:
> Bon dia a tothom,
> 
> Fa molt de temps que em barallo amb un bug, que intento acorralar, però
> no hi ha manera.
> 
> Afecta a Debian Testing en el sistema gràfic, i aquí em veig molt
> perdut, entre controladors, servidors de finestres, gestors de
> finestres, compositors, mesas, cairos, egl, etc.

[...]
> 
> Crec que el bug afecta a molta gent, i que alguns missatges que es poden
> 

[...]

> 
> Treballo amb targeta gràfica [AMD/ATI] Turks XT [Radeon HD 6670/7670] a
> Debian Testing, actualment amb nucli 4.19
> 
> Fins al nucli 4.13 tot anava bé, però en actualitzar al nucli 4.14
> l’escriptori Gnome es «congelava» cada pocs minuts. A tots els següents
> nuclis fins el 4.19 el problema persisteix. A aquest enllaç hi ha els
> canvis que aporta el nucli 4.14 a Radeon, però no els sé interpretar:
> https://kernelnewbies.org/Linux_4.14#Graphics
> 
>  Pista: Es congelava Gnome amb Xorg, però no Gnome amb Wayland
> 

Jo també en tinc un de llarga durada i uso Debian Testin g des d'uns 3 -
4 mesos després del darrer canvi d'estable (juny o juliol 2017). El
primer nucli que vaig usar tot anava bé. A partir del següent (no
recordo quin) van començar els maldecaps.

El meu hardware no té rés a veure amb el teu. Tot i això, els problemes
que descrius són força similars als que a mi m'afecten i, en el meu cas,
estan relacionats amb la targeta gràfica [1,2].

De vegades ni tant sols es carregava el sistema gràfic. D'altres no
podia canviar entre entorn gràfic o no (usant CTRL+ALT+n), d'altres és
"gelava" la imatge, d'altres és bloquejava mentre parava la maquina.

L'únic en comú entre la multitud de diverses marques de proveïdors de
portàtils afectats sembla ser el fet de tenir el sistema gràfic integrat
Intel + targeta gràfica dedicada NVIDIA (diversos models):

$ lspci | egrep "VGA|3D"
00:02.0 VGA compatible controller: Intel Corporation HD Graphics 630
(rev 04)
01:00.0 3D controller: NVIDIA Corporation GP107M [GeForce GTX 1050 Ti
Mobile] (rev a1)


>
>  Pista: no es congelava XFCE
> 

Únicament he provat GNOME. Als "bugs" que jo he revisat no importa gaire
l'entorn gràfic usat però hi ha majoria de GNOMEs. Suposo que el motiu
és que és l'entorn majoritari.

>  Pista: fent CTRL+ALT+F8 i després CTRL+ALT+F7 tot tornava a funcionar
> 

No ho vaig provar això.

[...]

> 
> No sé ni per on començar. Algun consell?
> 

Jo vaig provar altres coses. Al final, solament funciona bé modificar
les opcions del nucli a /etc/default/grub. Concretament, jo tinc:

GRUB_CMDLINE_LINUX_DEFAULT="acpi_osi=!"

hi ha gent que ho combina amb diferents versions de Windows:

"acpi_osi='Windows '"

he vist molts 2009 i 2015 però altres també. Tots amb resultats
diversos. Jo vaig provar-ho amb 2009 i funciona de la mateixa manera que
sense.

Totes les noves versions del nucli que han sortit a Testing les provo
sense les opcions de nucli i es tornen a reproduir els problemes.

Salut i peles,

robert

[1] https://bugzilla.kernel.org/show_bug.cgi?id=156341
[2] https://github.com/Bumblebee-Project/Bumblebee/issues/764

Re: Em podeu donar un cop de ma amb un bug?

[Ernest Adrogué]

Àlex  writes:
> Sí així vaig fer. Vaig descarregar el nucli 4.9 de la Debian estable i
> el vaig instal.lar, i quan vull veure vídeo arrenco amb aquest nucli.
> Des de la versió 4.14 a la 4.19 la cosa ha anat malament i no sé si amb
> el temps es corregirà, però sempre puc canviar de hardware gràfic.
>
> A internet vaig llegir usuaris de Linux amb problemes semblants que
> comentaven que encara guardaven la partició de Windows per poder veure
> vídeos, i em va sabre greu.

A vegades hi ha algun problema, però en general les targetes AMD estan
ben suportades a Linux.  Un dels motius és que AMD col·labora amb els
programadors dels drivers oberts, a diferència d'altres fabricants.

Fa bastant temps vaig tenir un problema semblant al teu.  Al final els
de Xfce em van recomanar que utilitzés el driver X11 "modesetting" en
lloc del "radeon", i es va solucionar.  Tampoc tinc gaire idea de com
funciona el sistema gràfic de Linux, però em sembla entendre que
actualment el driver de X11 és un driver genèric per a totes les
targetes (el tal "modesetting"), i el driver específic per a cada
targeta ara es troba integrat en el kernel.  L'usuari no ha de
configurar res.  Si ho tens de l'altra manera, es van trencant coses
perquè els drivers antics de X11 actualment ja no es desenvolupen.

erreur d'interprétation dxf2gcode

[Bernard Schoenacker]

bonjour,

j'ai voulou utiliser un dessin existant et
voici le résultat :


Creating configuration window
Creating configuration window
New configuration applied
File: 
/home/bernard/Documents/Q-cad/torche-suedoise/grille-torche-suedoise-2.dxf 
selected
Loading file: 
/home/bernard/Documents/Q-cad/torche-suedoise/grille-torche-suedoise-2.dxf
Reading DXF Structure
Reading Block *Model_Space; Nr: 0
Reading Block *Paper_Space; Nr: 1
Reading Block *D16; Nr: 2
Found unsupported geometry type: SOLID !
Found unsupported geometry type: MTEXT !
Reading Block *D4; Nr: 3
Found unsupported geometry type: SOLID !
Reading Block *D6; Nr: 4
Found unsupported geometry type: SOLID !
Found unsupported geometry type: SOLID !
Found unsupported geometry type: MTEXT !
Reading Block *D2; Nr: 5
Found unsupported geometry type: SOLID !
Found unsupported geometry type: SOLID !
Found unsupported geometry type: MTEXT !
Reading Block *D5; Nr: 6
Found unsupported geometry type: SOLID !
Found unsupported geometry type: SOLID !
Found unsupported geometry type: MTEXT !
Reading Block *D3; Nr: 7
Found unsupported geometry type: SOLID !
Reading Block *D19; Nr: 8
Found unsupported geometry type: SOLID !
Found unsupported geometry type: SOLID !
Found unsupported geometry type: MTEXT !
Reading Block *D12; Nr: 9
Found unsupported geometry type: SOLID !
Found unsupported geometry type: MTEXT !
Reading Block *D21; Nr: 10
Found unsupported geometry type: SOLID !
Found unsupported geometry type: SOLID !
Found unsupported geometry type: MTEXT !
Reading Block *D23; Nr: 11
Found unsupported geometry type: SOLID !
Found unsupported geometry type: SOLID !
Found unsupported geometry type: MTEXT !
Reading Block *D1; Nr: 12
Found unsupported geometry type: SOLID !
Found unsupported geometry type: SOLID !
Found unsupported geometry type: MTEXT !
Reading Block *D22; Nr: 13
Found unsupported geometry type: SOLID !
Found unsupported geometry type: SOLID !
Found unsupported geometry type: MTEXT !
Reading Block *D11; Nr: 14
Found unsupported geometry type: SOLID !
Found unsupported geometry type: SOLID !
Found unsupported geometry type: MTEXT !
Reading Block *D20; Nr: 15
Found unsupported geometry type: SOLID !
Found unsupported geometry type: MTEXT !
Reading Block *D10; Nr: 16
Found unsupported geometry type: SOLID !
Found unsupported geometry type: MTEXT !
Reading Block *D8; Nr: 17
Found unsupported geometry type: SOLID !
Found unsupported geometry type: MTEXT !
Reading Block *D9; Nr: 18
Found unsupported geometry type: SOLID !
Found unsupported geometry type: SOLID !
Found unsupported geometry type: MTEXT !
Reading Block *D7; Nr: 19
Found unsupported geometry type: SOLID !
Found unsupported geometry type: SOLID !
Found unsupported geometry type: MTEXT !
Reading Block *D13; Nr: 20
Found unsupported geometry type: SOLID !
Found unsupported geometry type: MTEXT !
Reading Block *D15; Nr: 21
Found unsupported geometry type: SOLID !
Found unsupported geometry type: SOLID !
Found unsupported geometry type: MTEXT !
Reading Block *D14; Nr: 22
Found unsupported geometry type: SOLID !
Found unsupported geometry type: SOLID !
Found unsupported geometry type: MTEXT !
Reading Block *D18; Nr: 23
Found unsupported geometry type: SOLID !
Found unsupported geometry type: SOLID !
Found unsupported geometry type: MTEXT !
Reading Block *D17; Nr: 24
Found unsupported geometry type: SOLID !
Found unsupported geometry type: MTEXT !
Found unsupported geometry type: DIMENSION !
Found unsupported geometry type: DIMENSION !
Found unsupported geometry type: LEADER !
Found unsupported geometry type: LEADER !
Found unsupported geometry type: MTEXT !
Found unsupported geometry type: MTEXT !
Found unsupported geometry type: MTEXT !
Found unsupported geometry type: MTEXT !
Found unsupported geometry type: DIMENSION !
Found unsupported geometry type: DIMENSION !
Found unsupported geometry type: DIMENSION !
Found unsupported geometry type: DIMENSION !
Found unsupported geometry type: DIMENSION !
Found unsupported geometry type: DIMENSION !
Found unsupported geometry type: DIMENSION !
Found unsupported geometry type: DIMENSION !
Found unsupported geometry type: DIMENSION !
Found unsupported geometry type: DIMENSION !
Found unsupported geometry type: DIMENSION !
Found unsupported geometry type: DIMENSION !
Found unsupported geometry type: DIMENSION !
Found unsupported geometry type: DIMENSION !
Found unsupported geometry type: DIMENSION !
Found unsupported geometry type: DIMENSION !
Found unsupported geometry type: DIMENSION !
Found unsupported geometry type: DIMENSION !
Found unsupported geometry type: DIMENSION !
Creating Contours of Block Nr: 0
Creating Contours of Block Nr: 1
Creating Contours of Block Nr: 2
Creating Contours of Block Nr: 3
Creating Contours of Block Nr: 4
Creating Contours of Block Nr: 5
Creating Contours of Block Nr: 6
Creating Contours of Block Nr: 7
Creating Contours of Block Nr: 8
Creating Contours of Block Nr: 9
Creating Contours of Block Nr: 10
Creating Contours of Block 

convertir un dessin en G-code

[Bernard Schoenacker]

bonjour,

j'ai essayé un logiciel libre pour convertir
un dessin en G-code, malheureusement le 
logiciel plante lamentablement avec un 
dessin issu de librecad et je n'arrive
pas à trouver les traces ...

quelles sont les alternatives ?

attention, c'est pour couper du métal (inox 304L)

le site de référence est dans les choux :

https://alternativeto.net/software/dxf2gcode/

merci de votre aimable attention

slt
bernard

Re: Command line mounting all partitions of pluggable device

[Richard Owlett]

On 01/14/2019 09:22 AM, Thomas Schmitt wrote:

Hi,

rhkra...@gmail.com wrote:

Assuming there are entries in fstab for each partition, [...]
for i in  /dev/sd*;  do  mount $i; done


Rchard Owlett wrote:

There are not.


In the most general case i would have a where-to-mount directory with
lots of directories for the various partitions (here 10 drives with
20 partitions each).


But thankfully I don't have to deal with the most general case as I am 
as compulsive about giving all partitions a reasonably unique label as 
Debian is about assigning UUIDs.


I sketched a procedure in my response to rhkramer.

I have errands that must be run. When I return I will check to see if 
your scripts catches anything mine doesn't.






For once:

   mkdir /media/all_sd_dir
   for i in a b c d e f g h i j
   do
 for j in 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20
 do
   mkdir /media/all_sd_dir/sd"$i""$j"
 done
   done

Then i'd use a variation of the proposed loop (in a script, of course):

   for i in /dev/sd[a-j][1-9] /dev/sd[a-j]1[0-9] /dev/sd[a-j]20
   do

 # Skip unresolved patterns which still contain brackets
 if echo "$i" | fgrep ']' >/dev/null
 then
   continue
 fi
  
 # Skip already mounted partitions

 if mount | grep '^'"$i"' ' >/dev/null
 then
   continue
 fi

 # Obtain the drive letter and partition number from /dev/sd path
 dp=$(echo "$i" | sed -e 's/\/dev\/sd//')

 # Now try mounting and report success if mount did not fail
 if mount "$i" /media/all_sd_dir/sd"$dp"
 then
   echo "=== mounted:  $i  /media/all_sd_dir/sd$dp"
 fi
   done

Next, one could try to identify the content by skilled guessing and
create symbolic links to the mounted directories. (The risk is high
to end up with an systemd+udev revenant.)


Have a nice day :)

Thomas

Re: Command line mounting all partitions of pluggable device

[Richard Owlett]

On 01/14/2019 09:02 AM, rhkra...@gmail.com wrote:

Top posting intentionally:  I guess the key is something has to know where to
mount those devices, and you are the one that has to decide that and tell
mount in one way or another.


Using your scheme of "/dev/sd" the desired mount point 
can be "computed" by piping the output of "lsblk -l -o name,label" to 
appropriate script(s).

The input parameter would be "sd".
The desired mount point would be
 "/media/richard/>".
{Any 'partition' with a blank label is not to be mounted.}




On Monday, January 14, 2019 10:01:15 AM rhkra...@gmail.com wrote:

On Monday, January 14, 2019 09:12:30 AM Richard Owlett wrote:

On 01/14/2019 07:33 AM, rhkra...@gmail.com wrote:

On Monday, January 14, 2019 08:11:11 AM Richard Owlett wrote:

How do I mount all partitions of a specific device
(e.g. /dev/sdc)?


Assuming there are entries in fstab for each partition,


There are not. I have a varying number of devices. Each device is
normally associated with a specific function (e.g. sneaker-net) or
personal project. A specific physical device may be reformatted and
assigned a new purpose.


you could use a (bash) for loop, like:

for i in  /dev/sd*;  do  mount $i; done


Hmm, well, that makes it (for me) harder.

If they all have similar mounting options (e.g., RO, things like that), and
the mount points correspond to some system (e.g., /dev/sd
gets mounted on /mnt/), then you might modify the mount
command in that loop appropriately, e.g.:

mount  /dev/sd /mnt/ 

Or, if groups of those devices have mountpoints that correspond to some
system, then you could haved multiple for loops to do the groups.

Or you could put mount commands in a file, one line per file, and run  a
for loop on the lines of the file, or some variation of this.

Re: kernel parallel builds?

[Andrea Borgia]

I am sort of bound to using the packaged kernel source, since I wanted to
minimize the changes (applying only *ONE* known debugging patch) and also
get a nice deb to install on the laptop.

I'll have to check the earlier suggestion of the environment variable, if
that works with no further changes it's perfect for me :)


Il giorno lun 14 gen 2019 alle ore 16:19 Thomas Pircher 
ha scritto:

> Andrea Borgia wrote:
> > I'm using this command from within the unpacked kernel source:
> > fakeroot debian/rules binary
>
> If you are not bound to using Debian's packaged kernel source, then you
> could simply use the bindeb-pkg target of the vanilla kernel. For example:
>
> cp /path/to/working/kernel-config .config
> make -j 16 clean oldconfig bindeb-pkg
>
> Thomas
>
>

Re: Command line mounting all partitions of pluggable device

[Thomas Schmitt]

Hi,

rhkra...@gmail.com wrote:
> > Assuming there are entries in fstab for each partition, [...]
> > for i in  /dev/sd*;  do  mount $i; done

Rchard Owlett wrote:
> There are not.

In the most general case i would have a where-to-mount directory with
lots of directories for the various partitions (here 10 drives with
20 partitions each).

For once:

  mkdir /media/all_sd_dir
  for i in a b c d e f g h i j
  do
for j in 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20
do
  mkdir /media/all_sd_dir/sd"$i""$j"
done
  done

Then i'd use a variation of the proposed loop (in a script, of course):

  for i in /dev/sd[a-j][1-9] /dev/sd[a-j]1[0-9] /dev/sd[a-j]20
  do

# Skip unresolved patterns which still contain brackets
if echo "$i" | fgrep ']' >/dev/null
then
  continue
fi
 
# Skip already mounted partitions
if mount | grep '^'"$i"' ' >/dev/null
then
  continue
fi

# Obtain the drive letter and partition number from /dev/sd path
dp=$(echo "$i" | sed -e 's/\/dev\/sd//')

# Now try mounting and report success if mount did not fail
if mount "$i" /media/all_sd_dir/sd"$dp"
then
  echo "=== mounted:  $i  /media/all_sd_dir/sd$dp"
fi
  done

Next, one could try to identify the content by skilled guessing and
create symbolic links to the mounted directories. (The risk is high
to end up with an systemd+udev revenant.)


Have a nice day :)

Thomas

Re: kernel parallel builds?

[Thomas Pircher]

Andrea Borgia wrote:
> I'm using this command from within the unpacked kernel source:
> fakeroot debian/rules binary

If you are not bound to using Debian's packaged kernel source, then you
could simply use the bindeb-pkg target of the vanilla kernel. For example:

cp /path/to/working/kernel-config .config
make -j 16 clean oldconfig bindeb-pkg

Thomas

Re: Command line mounting all partitions of pluggable device

[rhkramer]

Top posting intentionally:  I guess the key is something has to know where to 
mount those devices, and you are the one that has to decide that and tell 
mount in one way or another.


On Monday, January 14, 2019 10:01:15 AM rhkra...@gmail.com wrote:
> On Monday, January 14, 2019 09:12:30 AM Richard Owlett wrote:
> > On 01/14/2019 07:33 AM, rhkra...@gmail.com wrote:
> > > On Monday, January 14, 2019 08:11:11 AM Richard Owlett wrote:
> > >> How do I mount all partitions of a specific device
> > >> (e.g. /dev/sdc)?
> > > 
> > > Assuming there are entries in fstab for each partition,
> > 
> > There are not. I have a varying number of devices. Each device is
> > normally associated with a specific function (e.g. sneaker-net) or
> > personal project. A specific physical device may be reformatted and
> > assigned a new purpose.
> > 
> > > you could use a (bash) for loop, like:
> > > 
> > > for i in  /dev/sd*;  do  mount $i; done
> 
> Hmm, well, that makes it (for me) harder.
> 
> If they all have similar mounting options (e.g., RO, things like that), and
> the mount points correspond to some system (e.g., /dev/sd
> gets mounted on /mnt/), then you might modify the mount
> command in that loop appropriately, e.g.:
> 
> mount  /dev/sd /mnt/ 
> 
> Or, if groups of those devices have mountpoints that correspond to some
> system, then you could haved multiple for loops to do the groups.
> 
> Or you could put mount commands in a file, one line per file, and run  a
> for loop on the lines of the file, or some variation of this.

Re: Command line mounting all partitions of pluggable device

[rhkramer]

On Monday, January 14, 2019 09:12:30 AM Richard Owlett wrote:
> On 01/14/2019 07:33 AM, rhkra...@gmail.com wrote:
> > On Monday, January 14, 2019 08:11:11 AM Richard Owlett wrote:

> >> How do I mount all partitions of a specific device
> >> (e.g. /dev/sdc)?
> > 
> > Assuming there are entries in fstab for each partition,
> 
> There are not. I have a varying number of devices. Each device is
> normally associated with a specific function (e.g. sneaker-net) or
> personal project. A specific physical device may be reformatted and
> assigned a new purpose.
> 
> > you could use a (bash) for loop, like:
> > 
> > for i in  /dev/sd*;  do  mount $i; done

Hmm, well, that makes it (for me) harder.

If they all have similar mounting options (e.g., RO, things like that), and 
the mount points correspond to some system (e.g., /dev/sd 
gets mounted on /mnt/), then you might modify the mount command 
in that loop appropriately, e.g.:

mount  /dev/sd /mnt/ 

Or, if groups of those devices have mountpoints that correspond to some 
system, then you could haved multiple for loops to do the groups.

Or you could put mount commands in a file, one line per file, and run  a for 
loop on the lines of the file, or some variation of this.

Re: Command line mounting all partitions of pluggable device

[Richard Owlett]

On 01/14/2019 07:33 AM, rhkra...@gmail.com wrote:

On Monday, January 14, 2019 08:11:11 AM Richard Owlett wrote:

I have competing mount requirements.
I have 2 1TB USB drives with a dozen or more partitions, only one of
which may be of current interest. Disabling automoun is a suitable
solution to mounted clutter.

However I have several USB drives (64GB - 250GB) with multiple
partitions. How do I mount all partitions of a specific device
(e.g. /dev/sdc)?

TIA


Assuming there are entries in fstab for each partition,


There are not. I have a varying number of devices. Each device is 
normally associated with a specific function (e.g. sneaker-net) or 
personal project. A specific physical device may be reformatted and 
assigned a new purpose.



you could use a (bash) for loop, like:

for i in  /dev/sd*;  do  mount $i; done

Re: kernel parallel builds?

[Andrea Borgia]

I'm using this command from within the unpacked kernel source:
fakeroot debian/rules binary

I'll have another look, thanks.


Il giorno lun 14 gen 2019 alle ore 13:59 Celejar  ha
scritto:

> On Mon, 14 Jan 2019 12:55:40 +0100
> Andrea Borgia  wrote:
>
> > Hi.
> >
> > How do I find out, and possibly tune, the degree of parallelization in
> the
> > kernel build process? The "Kernel Handbook" doesn't say.
> >
> > I've got a fairly recent PC with plenty of RAM and a NVME drive, so I was
> > shocked to find that rebuilding the debian kernel package took a few
> hours.
> > Shocked because the system is otherwise extremely fast.
>
> To set concurrency, use make's -j flag / option, or whatever the tool
> you're using uses to set concurrency. E.g., make-kpkg also has a -j
> flag / option (which it passes to make), as well as a CONCURRENCY_LEVEL
> environment variable.
>
> https://linux.die.net/man/1/make
> http://man.he.net/man1/make-kpkg
>
> Celejar
>
>

Re: apt won't put config files back

[Greg Wooledge]

On Mon, Jan 14, 2019 at 01:36:10PM +, aces and eights wrote:
> after failing to get my roundcube dovecot installations to work again, as a
> last resort I apt removed dovecot and also /etc/dovecot.
> Thinking "that's OK apt will put them back."
> except
> "Not replacing deleted config file /etc/dovecot/conf.d/20-managesieve.conf"
> for all the conf files which is not very helpful.
> Is there a way to persuade apt to put the config files back ?

This is an intentional feature.  If you delete a config file, the package
manager assumes you had a good reason for this, and that you want it to
stay deleted, so upgrading a package will not install a new version of
the config file.

If you WANT a new/default config file to be installed, the most obvious
way is to purge (not just remove) the package, and then reinstall it.

If that's too heavy-handed, the next most obvious way is:

1) Get the .deb file with "apt-get --reinstall install pkgname"
   (you might also add the --download-only option).  This places the
   .deb file in /var/cache/apt/archives/.

2) dpkg --install --force-confmiss /var/cache/apt/archives/yourfile

Re: Gnome-openbox [résolu ?]

[Jean Bernon]

Suite et fin de ce fil.

Je suis finalement parvenu à faire marcher la session Gnome-openbox, mais le 
paquet openbox-gnome-session est vraiment pourri et le résultat est 
inintéressant. On perd à la fois les avantages de Gnome et d'openbox loin de 
les cumuler. Il vaut mieux utiliser openbox seul.

Pour ceux qui voudraient tenter le coup, le script openbox-gnome-session 
présente les problèmes suivants :
- le script est en sh et le test de la version de gnome installée ne fonctionne 
pas avec bash (merci à Stéphane Ascoët). J'ai remplacé le test par "VER=3.22.2".
- la commande "gnome-session --choose-session=openbox-session" est obsolète, je 
l'ai remplacée par "gnome-session --session=openbox-gnome"
- ensuite la commande gnome-session cherche le fichier "openbox.desktop" 
qu'elle cherche dans divers répertoires, mais pas dans les deux où se trouve un 
fichier de ce nom /usr/share/gnome/wm-properties/ et /usr/share/xsessions/. 
J'ai copié tour à tour dans $HOME/.config/autostart chacun des deux fichiers 
qui sont différents et aboutissent au même résultat.
- ensuite la commande gnome-session cherche le fichier 
"gnome-flashback-services.desktop" sans le trouver car il n'existe nulle part. 
En revanche il y a dans le répertoire "/usr/share/applications" un fichier 
"gnome-flashback.desktop" et un fichier "gnome-flashback-init.desktop" que j'ai 
copié tour à tour sous le nom "gnome-flashback-services.desktop" dans le 
répertoire $HOME/.config/autostart. Le résultat est le même avec les deux.
Avec tout ça la session Gnome_openbox se lance enfin normalement (lol).

Mon install : Debian 4.9.130-2 (2018-10-27) x86_64 GNU/Linux ; Gnome 3.22.2

Jean


- Mail original - 

> De: "Jean Bernon" 
> À: "debian-user-french" 
> Envoyé: Jeudi 10 Janvier 2019 09:08:35
> Objet: Gnome-openbox

> Bonjour la liste,

> J'ai installé openbox et openbox-gnome-session. Gdm me propose deux
> nouveaux DE, openbox et GNOME-openbox. Le premier s'ouvre sans
> difficulté, le deuxième échoue toujours.

> Dans /var/log/messages je trouve ceci

> Jan 10 08:45:38 pc-jean-debian udev-acl.ck[9998]: g_slice_set_config:
> assertion 'sys_page_size == 0' failed
> Jan 10 08:45:38 pc-jean-debian udev-acl[1]: g_slice_set_config:
> assertion 'sys_page_size == 0' failed
> Jan 10 08:45:50 pc-jean-debian udev-acl.ck[10003]:
> g_slice_set_config: assertion 'sys_page_size == 0' failed
> Jan 10 08:45:50 pc-jean-debian udev-acl[10005]: g_slice_set_config:
> assertion 'sys_page_size == 0' failed

> Si je lance la commande openbox-gnome-session, j'obtiens ceci :

> *** jean@pc-jean-debian:~ *** $ openbox-gnome-session
> /usr/bin/openbox-gnome-session: 23: test: -lt: unexpected operator
> /usr/bin/openbox-gnome-session: 23: test: =: unexpected operator
> /usr/bin/openbox-gnome-session: 27: test: -lt: unexpected operator

> Une suggestion ?
> Merci
> Jean

apt won't put config files back

[aces and eights]

hello,
after failing to get my roundcube dovecot installations to work again, as a
last resort I apt removed dovecot and also /etc/dovecot.
Thinking "that's OK apt will put them back."
except
"Not replacing deleted config file /etc/dovecot/conf.d/20-managesieve.conf"
for all the conf files which is not very helpful.
Is there a way to persuade apt to put the config files back ?

mick

Re: Command line mounting all partitions of pluggable device

[rhkramer]

On Monday, January 14, 2019 08:11:11 AM Richard Owlett wrote:
> I have competing mount requirements.
> I have 2 1TB USB drives with a dozen or more partitions, only one of
> which may be of current interest. Disabling automoun is a suitable
> solution to mounted clutter.
> 
> However I have several USB drives (64GB - 250GB) with multiple
> partitions. How do I mount all partitions of a specific device
> (e.g. /dev/sdc)?
> 
> TIA

Assuming there are entries in fstab for each partition, you could use a (bash) 
for loop, like:

for i in  /dev/sd*;  do  mount $i; done

Command line mounting all partitions of pluggable device

[Richard Owlett]

I have competing mount requirements.
I have 2 1TB USB drives with a dozen or more partitions, only one of 
which may be of current interest. Disabling automoun is a suitable 
solution to mounted clutter.


However I have several USB drives (64GB - 250GB) with multiple 
partitions. How do I mount all partitions of a specific device

(e.g. /dev/sdc)?

TIA

Re: kernel parallel builds?

[Celejar]

On Mon, 14 Jan 2019 12:55:40 +0100
Andrea Borgia  wrote:

> Hi.
> 
> How do I find out, and possibly tune, the degree of parallelization in the
> kernel build process? The "Kernel Handbook" doesn't say.
> 
> I've got a fairly recent PC with plenty of RAM and a NVME drive, so I was
> shocked to find that rebuilding the debian kernel package took a few hours.
> Shocked because the system is otherwise extremely fast.

To set concurrency, use make's -j flag / option, or whatever the tool
you're using uses to set concurrency. E.g., make-kpkg also has a -j
flag / option (which it passes to make), as well as a CONCURRENCY_LEVEL
environment variable.

https://linux.die.net/man/1/make
http://man.he.net/man1/make-kpkg

Celejar

Re: Debian 9 /boot && /boot/efi partition

[Steve McIntyre]

Jonathan Dowland wrote:
>On Sun, Jan 13, 2019 at 02:00:02PM +0100, Pascal Hambourg wrote:
>>/boot can be the EFI partition in the systemd boot specification.
>>
>
>Thanks, I had seen in the past but had forgotten about it. Do you know
>whether Debian has plans to follow this spec?

No plans that I've seen, no. Strikes me very much like
https://xkcd.com/927/ , to be honest.

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
Who needs computer imagery when you've got Brian Blessed?

Re: Em podeu donar un cop de ma amb un bug?

[Eduard Selma]

El 14/1/19 a les 13:09, Àlex ha escrit:


El teu hardware gràfic és Radeon?


- Sí, és el AMD/ATI Richland (Radeon HD 8670D). Està integrat amb la 
CPU: Quad Core AMD A10-6800K, és el que anomenen APU. Deu ser del 2013 o 
14, tecnologia de 32 nm. Res de darrera generació. Evidenment, és un 
model diferent del teu.


Cordialment,

Eduard Selma.

redmine : Dépend: ruby-actionpack-xml-parser mais ne sera pas installé

[G2PC]

Bonjour.
J'ai un sushi sur la Debian SID, VPS OVH, suite à la dernière mise à
jour que j'ai effectuée ( je pense. )

Sur une machine virtuelle Debian SID, par contre, la mise à jour c'est
déroulée correctement.

Je ne comprend pas pourquoi, avec le même dépôt, mon serveur tombe en
carafe, et, la machine virtuelle elle, fonctionne.

Voilà le message que j'ai en production :


sudo apt-get install redmine
Lecture des listes de paquets... Fait
Construction de l'arbre des dépendances  
Lecture des informations d'état... Fait
Certains paquets ne peuvent être installés. Ceci peut signifier
que vous avez demandé l'impossible, ou bien, si vous utilisez
la distribution unstable, que certains paquets n'ont pas encore
été créés ou ne sont pas sortis d'Incoming.
L'information suivante devrait vous aider à résoudre la situation :

Les paquets suivants contiennent des dépendances non satisfaites :
 redmine : Dépend: ruby-actionpack-xml-parser mais ne sera pas installé
   Dépend: ruby-protected-attributes mais ne sera pas installé
E: Impossible de corriger les problèmes, des paquets défectueux sont en
mode « garder en l'état ».


sudo apt-get install ruby-actionpack-xml-parser
Lecture des listes de paquets... Fait
Construction de l'arbre des dépendances  
Lecture des informations d'état... Fait
Certains paquets ne peuvent être installés. Ceci peut signifier
que vous avez demandé l'impossible, ou bien, si vous utilisez
la distribution unstable, que certains paquets n'ont pas encore
été créés ou ne sont pas sortis d'Incoming.
L'information suivante devrait vous aider à résoudre la situation :

Les paquets suivants contiennent des dépendances non satisfaites :
 ruby-actionpack-xml-parser : Dépend: ruby-actionpack (< 2:5) mais
2:5.2.2+dfsg-1 devra être installé


Si vraiment je dois attendre la sortie de nouveaux paquets, comment puis
je faire pour connaître l'état des lieux d'avancement de la sortie de
ses paquets ? Est ce possible de pouvoir estimer quand seront proposées
les prochaines mises à jour ?

Re: APT candidate does not match package on Debian repo

[plataleas plataleas]

Hi Nik

Thanks for your reply. Is it possible to extract this information from the
mirror server (CentOS based)?

Where the information is stored on the repository server specifying a
package as stable?

regards
Martin



On Mon, Jan 14, 2019 at 11:49 AM Dominik George 
wrote:

> Hi,
>
> On Mon, Jan 14, 2019 at 11:18:55AM +0100, plataleas plataleas wrote:
> > Hello,
> >
> > We are upgrading our Debian servers (AMD64). We found that the following
> > kernels are available on public Debian mirrors:
> >
> > kernel-image-4.9.0-8-amd64-di_4.9.130-2_amd64.udeb
> > <
> http://ftp.cl.debian.org/debian/pool/main/l/linux/kernel-image-4.9.0-8-amd64-di_4.9.130-2_amd64.udeb
> >
> > 28-Oct-2018 05:46
> > 4522628kernel-image-4.9.0-8-amd64-di_4.9.144-1_amd64.udeb
> > <
> http://ftp.cl.debian.org/debian/pool/main/l/linux/kernel-image-4.9.0-8-amd64-di_4.9.144-1_amd64.udeb
> >
> > 04-Jan-2019 05:31 4529754
> >
> > URL: http://ftp.cl.debian.org/debian/pool/main/l/linux/
> >
> > We would expect that the latest 4.9.144-1 kernel would be the candidate.
> > However only 4.9.130-2 is listed as candidate:
>
> 4.9.144 is available on the mirrors, but not yet „active“ in the stable
> distribution:
>
> $ rmadison linux-image-4.9.0-8-amd64
> linux-image-4.9.0-8-amd64 | 4.9.130-2 | stable   | amd64
> linux-image-4.9.0-8-amd64 | 4.9.144-1 | proposed-updates | amd64
>
> It will be moved to the stable distribution with the next point release.
>
> -nik
>

Re: APT candidate does not match package on Debian repo

[Dominik George]

Hi,

> Thanks for your reply. Is it possible to extract this information from the
> mirror server (CentOS based)?
> 
> Where the information is stored on the repository server specifying a
> package as stable?

http://ftp.de.debian.org/debian/dists/stable/main/binary-amd64/Packages.xz

-nik


signature.asc
Description: PGP signature

Mettre à jour Androïd ?

[ptilou]

Bonjour et bonne année !

https://youtu.be/yLUITlkQ83E
Voilà j'ai la même box, et je me demandais comment si c'est possible flacher le 
firmware sous Linux ?

Je suis sous opens use, mais j'attend le mot de passe pour poser mes questions 
sur le forum qui m'a pas répondu depuis le 6 décembre ?
Je me demande si je dois remercier un debiantiste ?

@ +

-- 
Ptilou

Re: Partitionnement d'un serveur web

[Florian Blanc]

 Bonjour,
Premièrement je te conseillerais d'utiliser Proxmox tu installer le kernel
sans problème à partir de Debian :
https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_Stretch
Avant çà pour ce qui est de ton partitionnement :
Concernant les SSD
3 partitions primaire :
(même taille sur les deux disques)
Une de environs 500Mo pour ( /boot )
Une de environs 4096Mo pour ( swap )
Le reste pour ( / )
Tu configure seulement le swap et / en raid1
Tu encrypt ton swap et / via l'interface d'installation.
Après tu peux utiliser LVM mais je trouve pas nécessaire.
ensuite "grub-install /dev/sda1" "grub-install /dev/sda2"

Pour tes disques 1To tu peux faire raid1, encrypted, LVM.

L'avantage de proxmox est que ça te permettra des backups assez facilement
et tu pourras également isoler tes services.
Enfin, je te laisse découvrir.
Tu peux faire une VM Freenas utilisant tes disques de 1To.
à toi de voir.

Amicalement.

Le lun. 14 janv. 2019 à 06:24, Fabrice Delvallée 
a écrit :

> Bonjour
>
>
> J'ai le projet d'installer un serveur dans mon lycée pour :
>
> - héberger une plate-forme d'apprentissage en ligne (moodle)
>
> - créer à la volée des images dockers contenant des notebooks python
>
>
> je partirai sur :
>
> - 2x256GO SSD en raid1 pour l'os
>
> - 2x1TO SATA en raid1+LVM pour les données
>
> - 64Go de mémoire
>
>
> Je suis un peu perdu pour le partitionnement :(
>
>
> faut-il mettre aussi LVM sur les SSD ? J'ai cru comprendre que grub
>
> n'est pas compatible LVM, dans ce cas il me faut une partition /boot
>
> séparée.
>
>
> Merci pour votre aide
>
>

Re: Em podeu donar un cop de ma amb un bug?

[Àlex]

El 12/1/19 a les 18:33, Eduard Selma ha escrit:
> El 12/1/19 a les 12:40, a...@probeta.net ha escrit:
>> Bon dia a tothom,
>>
>> Fa molt de temps que em barallo amb un bug, que intento acorralar,
>> però no hi ha manera.
>>
>> Afecta a Debian Testing en el sistema gràfic, i aquí em veig molt
>> perdut, entre controladors, servidors de finestres, gestors de
>> finestres, compositors, mesas, cairos, egl, etc.
>
> - No crec que t'ajudi gaire, només són més dades... (i potser més
> "soroll"):
>
> Treballo amb Debian 9.6 (Stretch, stable) però amb nucli
> 4.17.0-0.bpo.3-amd64 (el que instal·la per omissió Neptune). El
> servidor gràfic és X.Org 1.19.6, gestor de finestres i compositor
> kwin-X11. L'Open GL és AMD ARUBA (DRM 2.50.0 / 4.17.0-0.bpo.3-amd64
> LLVM 6.0.0) v: 4.3 Mesa 18.2.6.
>
> El meu entorn d'escriptori és KDE/Plasma Frameworks 5.45.0 amb Qt 5.7.1.
>
> No uso cap altre compositor, panels virguers, ni rés més quant a
> gràfics. El meu reproductor VLC és el 3.0.3.
>
> Fins ara, no he observat el fenomen que ens descrius. 


Gràcies Eduard


El teu hardware gràfic és Radeon?


Salutacions



    Àlex

Re: Em podeu donar un cop de ma amb un bug?

[Àlex]

> Pel que dius, semblaria un problema del compositor, que no actualitza
> l'estat de la pantalla correctament.  Ara bé, si et passa amb Gnome i
> també amb Xfce, que utilitzen compositors diferents, aleshores m'inclino
> a pensar que és una altra cosa.


Sí, i amb Gnome amb Xorg es congelava tot l'escriptori i amb Gnome amb
Wayland no. Tot molt estrany.


La pròxima trobada Debian, si algú s'anima a fer una xerrada tècnica per
explicar tots els elements que formen el sistema gràfic de Linux, jo ho
agrairé molt.



> Probablement és més pràctic tornar a una versió anterior que saps que
> funciona i posar-la en estat "hold", i esperar que solucionin el
> problema a les versions més recents.


Sí així vaig fer. Vaig descarregar el nucli 4.9 de la Debian estable i
el vaig instal.lar, i quan vull veure vídeo arrenco amb aquest nucli.
Des de la versió 4.14 a la 4.19 la cosa ha anat malament i no sé si amb
el temps es corregirà, però sempre puc canviar de hardware gràfic.

A internet vaig llegir usuaris de Linux amb problemes semblants que
comentaven que encara guardaven la partició de Windows per poder veure
vídeos, i em va sabre greu.

A mi, que m'agrada buscar bugs, m'ha servit per no asumir que quan una
aplicació es "congela" es l'aplicació, sino que l'aplicació pot no estar
congelada i es tracta del sistema gràfic de Linux que ha deixat de
renovar el contingut de la finestra o de tot l'escriptori.


Salut

kernel parallel builds?

[Andrea Borgia]

Hi.

How do I find out, and possibly tune, the degree of parallelization in the
kernel build process? The "Kernel Handbook" doesn't say.

I've got a fairly recent PC with plenty of RAM and a NVME drive, so I was
shocked to find that rebuilding the debian kernel package took a few hours.
Shocked because the system is otherwise extremely fast.

Thanks,
Andrea.

Re: APT candidate does not match package on Debian repo

[plataleas plataleas]

 Hi Nik

Thanks for your reply. Is it possible to extract this information from the
mirror server (CentOS based)?

Where the information is stored on the repository server specifying a
package as stable?

regards
Martin

On Mon, Jan 14, 2019 at 12:12 PM plataleas plataleas 
wrote:

> Hi Nik
>
> Thanks for your reply. Is it possible to extract this information from the
> mirror server (CentOS based)?
>
> Where the information is stored on the repository server specifying a
> package as stable?
>
> regards
> Martin
>
>
>
> On Mon, Jan 14, 2019 at 11:49 AM Dominik George 
> wrote:
>
>> Hi,
>>
>> On Mon, Jan 14, 2019 at 11:18:55AM +0100, plataleas plataleas wrote:
>> > Hello,
>> >
>> > We are upgrading our Debian servers (AMD64). We found that the following
>> > kernels are available on public Debian mirrors:
>> >
>> > kernel-image-4.9.0-8-amd64-di_4.9.130-2_amd64.udeb
>> > <
>> http://ftp.cl.debian.org/debian/pool/main/l/linux/kernel-image-4.9.0-8-amd64-di_4.9.130-2_amd64.udeb
>> >
>> > 28-Oct-2018 05:46
>> > 4522628kernel-image-4.9.0-8-amd64-di_4.9.144-1_amd64.udeb
>> > <
>> http://ftp.cl.debian.org/debian/pool/main/l/linux/kernel-image-4.9.0-8-amd64-di_4.9.144-1_amd64.udeb
>> >
>> > 04-Jan-2019 05:31 4529754
>> >
>> > URL: http://ftp.cl.debian.org/debian/pool/main/l/linux/
>> >
>> > We would expect that the latest 4.9.144-1 kernel would be the candidate.
>> > However only 4.9.130-2 is listed as candidate:
>>
>> 4.9.144 is available on the mirrors, but not yet „active“ in the stable
>> distribution:
>>
>> $ rmadison linux-image-4.9.0-8-amd64
>> linux-image-4.9.0-8-amd64 | 4.9.130-2 | stable   | amd64
>> linux-image-4.9.0-8-amd64 | 4.9.144-1 | proposed-updates | amd64
>>
>> It will be moved to the stable distribution with the next point release.
>>
>> -nik
>>
>

Suppression de /etc/apt/trusted.gpg

[benoitlst]

Bonjour,

J'ai voulu ajouter testing dans mon source.list(avec un Pin-Priority 
pour rester en stable)

et j'avais des messages d'alerte quand je faisais

apt update

Une recherche avec le message me conduit à un post qui suggère de 
supprimer /etc/apt/trusted.gpg.


Je le fais et ça fonctionne sans message d'alerte.

apt n'a pas recréé un nouveau fichier...

Est-ce que j'ai bien fait ?

Si pas je l'ai toujours et peu le remettre à sa place.

Voici le message que je recevais

W: http://files2.eid.belgium.be/debian/dists/stretch/InRelease: The 
key(s) in the keyring /etc/apt/trusted.gpg are ignored as the file is 
not readable by user '_apt' executing apt-key.
W: http://deb.debian.org/debian/dists/testing/InRelease: The key(s) in 
the keyring /etc/apt/trusted.gpg are ignored as the file is not readable 
by user '_apt' executing apt-key.
W: http://files.eid.belgium.be/debian/dists/stretch/InRelease: The 
key(s) in the keyring /etc/apt/trusted.gpg are ignored as the file is 
not readable by user '_apt' executing apt-key.
W: http://deb.debian.org/debian/dists/testing-updates/InRelease: The 
key(s) in the keyring /etc/apt/trusted.gpg are ignored as the file is 
not readable by user '_apt' executing apt-key.
W: 
http://deb.debian.org/debian-security/dists/testing/updates/InRelease: 
The key(s) in the keyring /etc/apt/trusted.gpg are ignored as the file 
is not readable by user '_apt' executing apt-key.
W: 
https://deb.debian.org/debian-security/dists/stable/updates/InRelease: 
The key(s) in the keyring /etc/apt/trusted.gpg are ignored as the file 
is not readable by user '_apt' executing apt-key.
W: https://deb.debian.org/debian/dists/stable-updates/InRelease: The 
key(s) in the keyring /etc/apt/trusted.gpg are ignored as the file is 
not readable by user '_apt' executing apt-key.
W: https://deb.debian.org/debian/dists/stable/Release.gpg: The key(s) in 
the keyring /etc/apt/trusted.gpg are ignored as the file is not readable 
by user '_apt' executing apt-key.


Merci d'avance

--
Benoit

Re: APT candidate does not match package on Debian repo

[Dominik George]

Hi,

On Mon, Jan 14, 2019 at 11:18:55AM +0100, plataleas plataleas wrote:
> Hello,
> 
> We are upgrading our Debian servers (AMD64). We found that the following
> kernels are available on public Debian mirrors:
> 
> kernel-image-4.9.0-8-amd64-di_4.9.130-2_amd64.udeb
> 
> 28-Oct-2018 05:46
> 4522628kernel-image-4.9.0-8-amd64-di_4.9.144-1_amd64.udeb
> 
> 04-Jan-2019 05:31 4529754
> 
> URL: http://ftp.cl.debian.org/debian/pool/main/l/linux/
> 
> We would expect that the latest 4.9.144-1 kernel would be the candidate.
> However only 4.9.130-2 is listed as candidate:

4.9.144 is available on the mirrors, but not yet „active“ in the stable
distribution:

$ rmadison linux-image-4.9.0-8-amd64
linux-image-4.9.0-8-amd64 | 4.9.130-2 | stable   | amd64
linux-image-4.9.0-8-amd64 | 4.9.144-1 | proposed-updates | amd64

It will be moved to the stable distribution with the next point release.

-nik


signature.asc
Description: PGP signature

Re: Debian 9 /boot && /boot/efi partition

[Jonathan Dowland]

On Sun, Jan 13, 2019 at 02:00:02PM +0100, Pascal Hambourg wrote:

/boot can be the EFI partition in the systemd boot specification.



Thanks, I had seen in the past but had forgotten about it. Do you know
whether Debian has plans to follow this spec?

--

⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Jonathan Dowland
⢿⡄⠘⠷⠚⠋⠀ https://jmtd.net
⠈⠳⣄ Please do not CC me, I am subscribed to the list.

Re: kernel "unsigned" in sid

[Vincent Lefevre]

On 2019-01-11 09:52:04 -0500, Michael Stone wrote:
> On Fri, Jan 11, 2019 at 09:55:45AM +0100, dot...@gmail.com wrote:
> > I recently came across an inconsistency in sid that it seems difficult (to 
> > me)
> > to overcome.
> > 
> > A kernel package named linux-image-4.19.0-1-amd64-unsigned provides the 
> > running
> > kernel but, since few days ago, it creates conflicts with the metapackage
> > linux-image-amd64 (bercause it depends on linux-image-4.19.0-1-amd which, in
> > turn, conflicts with the installed kernel).
> > 
> > I can't trivially replace the "unsigned" (BTW, what does "unsigned" stand 
> > for,
> > anyway?) version with linux-image-4.19.0-1-amd because of the same version
> > number.
> > 
> > I'm not really worried because this will probably be solved when moving to 
> > the
> > next kernel release but the situation is a bit annoying.
> > 
> > Is there any solution?
> 
> How did you get the unsigned kernel installed in the first place? It's not
> typically installed, and I don't see any dependencies that would pull it in.

Until a few weeks ago, it could be installed due to a "Provides:".
See the following bug I had reported:

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916927

This problem is now solved, i.e. the "Provides:" was dropped.
But perhaps this is what is causing the *temporary* issue the
user has above.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

APT candidate does not match package on Debian repo

[plataleas plataleas]

Hello,

We are upgrading our Debian servers (AMD64). We found that the following
kernels are available on public Debian mirrors:

kernel-image-4.9.0-8-amd64-di_4.9.130-2_amd64.udeb

28-Oct-2018 05:46
4522628kernel-image-4.9.0-8-amd64-di_4.9.144-1_amd64.udeb

04-Jan-2019 05:31 4529754

URL: http://ftp.cl.debian.org/debian/pool/main/l/linux/

We would expect that the latest 4.9.144-1 kernel would be the candidate.
However only 4.9.130-2 is listed as candidate:

test:~# apt-cache policy linux-image-4.9.0-8-amd64

linux-image-4.9.0-8-amd64:

  Installed: 4.9.130-2

  Candidate: 4.9.130-2

  Version table:

*** 4.9.130-2 500

500 http://deb.debian.org/debian stretch/main amd64 Packages

100 /var/lib/dpkg/status


Could someone explain this behavior? (we did clean the apt cache)


Thanks and regards

Martin

Re: /dev/disk/by-id/ in testing

[Vincent Lefevre]

On 2019-01-14 11:06:01 +0100, Vincent Lefevre wrote:
> On 2019-01-08 20:12:43 +0100, Pascal Hambourg wrote:
> > This issue is not specific to lilo. It would affect grub-pc updates too,
> > because the boot device is specified by device id.
> > 
> > For example on my system :
> > $ debconf-show grub-pc
> > (...)
> > * grub-pc/install_devices: /dev/disk/by-id/ata-WDC_WD1200BEVE-00WZT0_...
> > 
> > The issue would be happen less often - only when updating the grub-pc
> > package instead of on any kernel update - but it would still happen.
> 
> ... which was what happened to be a few days ago!

Sorry, s/be/me/

BTW, a display bug in the terminal made the problem worse, because
I could not select a device for GRUB installation. So, currently,
new GRUB versions are no longer installed.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Re: /dev/disk/by-id/ in testing

[Vincent Lefevre]

On 2019-01-08 20:12:43 +0100, Pascal Hambourg wrote:
> This issue is not specific to lilo. It would affect grub-pc updates too,
> because the boot device is specified by device id.
> 
> For example on my system :
> $ debconf-show grub-pc
> (...)
> * grub-pc/install_devices: /dev/disk/by-id/ata-WDC_WD1200BEVE-00WZT0_...
> 
> The issue would be happen less often - only when updating the grub-pc
> package instead of on any kernel update - but it would still happen.

... which was what happened to be a few days ago!

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Re: /dev/disk/by-id/ in testing

[Vincent Lefevre]

On 2019-01-06 10:30:26 +, Johan en Katrien Dewaele wrote:
> Hi,
> 
> my weekly upgrade on testing failed yesterday as,  after an initrd.img was 
> generated, lilo could not run successfully.
> 
> 
> After checking my /etc/lilo.conf, where I had my boot disk identified by ID 
> as :
> 
> 
> "boot=/dev/disk/by-id/ata-ST3500320AS_9QM6D0TB" 
> 
> 
> and comparing it with what is in /dev/disk/by-id I noticed that this 
> identification-id had changed suddeny: see the additional underscores in the 
> names of both harddisks:
> 
> $ ls -alF /dev/disk/by-id/
> 
> total 0
> drwxr-xr-x 2 root root 700 jan  6 11:00 ./
> drwxr-xr-x 7 root root 140 jan  6 10:32 ../
> lrwxrwxrwx 1 root root   9 jan  6 10:32 ata-PIONEER_DVD_RW_DVR-107D -> 
> ../../sr0
> lrwxrwxrwx 1 root root   9 jan  6 10:32 ata-ST3500320AS9QM6D0TB -> 
> ../../sdb
[...]
> My question: is this change intentional?  I thought I was "save";-) 
> identifying my disks by ID ? Or did I miss something?

FYI, it was due to a bug in udev, fixed there:

systemd (240-3) unstable; urgency=medium
[...]
  * libudev-util: Make util_replace_whitespace() read only len characters.
Fixes a regression where /dev/disk/by-id/ names had additional
underscores.
[...]
 -- Michael Biebl   Wed, 09 Jan 2019 18:40:57 +0100

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)