Re: clone d'un système: problème avec systemd au boot

[Simon Cavey]

Si le nouveau disque dur a été formaté, il doit y avoir un problème d'UUID.

Solution booter sur un système live. exécuter la commande

sudo blkid

identifier les UUID des partitions.
monter le disque dur fraichement restauré
mettre à jour les fichier de config avec les nouveau UUID:

/boot/grub/grub.cfg
et surtout
/etc/fstab

Et ça devrait pouvoir fonctionner à nouveau correctement.


Le 08/03/2016 01:06, Gaëtan PERRIER a écrit :
> Bonjour,
>
> Je viens de changer le disque dur de mon portable en clonant (avec fsarchiver
> savedir/restdir) son disque vers le nouveau puis en réinstallant grub avec un
> chroot. Mais au boot suivant, bien que la machine démarre, j'ai plein 
> d'erreurs
> systemd du genre:
>
> Failed to mount Configuration File System
>
> Failed to mount FUSE Control File System
>
> Failed to start File System Check on Root Device
>
> etc.
>
> Vu que j'entrave que dalle à systemd je ne sais pas trop quoi faire ?
>
> A+
>
> Gaëtan
>

Re: clone d'un système: problème avec systemd au boot

[pmenier]

Le 08/03/2016 01:06, Gaëtan PERRIER a écrit :

Bonjour,

Je viens de changer le disque dur de mon portable en clonant (avec fsarchiver
savedir/restdir) son disque vers le nouveau puis en réinstallant grub avec un
chroot. Mais au boot suivant, bien que la machine démarre, j'ai plein d'erreurs
systemd du genre:

Failed to mount Configuration File System

Failed to mount FUSE Control File System

Failed to start File System Check on Root Device

etc.

Vu que j'entrave que dalle à systemd je ne sais pas trop quoi faire ?

A+

Gaëtan



Salut

J'ai déjà fait ce genre de manip avec clonezilla sans rencontrer de 
problemes. Si tu as toujours l'ancien disque sous la main ça pourrait 
valoir le coup d'essayer ...

De plus pas besoin de bouiner pour réinstaller GRUB avec cet outil.

Patrick

Problemas al actualizar chrome

[Omar Pacheco]

Buenas noches lista,

Tengo instalado tanto en debian(8.3) como en ubunto(14.04) el
navegador google chrome, esta noche al intentar actualizar ambos
sistemas me encontré con este mensaje:


W: Imposible obtener
http://dl.google.com/linux/chrome/deb/dists/stable/Release  No se pudo
encontrar la entrada esperada «main/binary-i386/Packages» en el
archivo Release (entrada incorrecta en sources.list o archivo mal
formado)

E: Algunos archivos de índice fallaron al descargar. Se han ignorado,
o se han utilizado unos antiguos en su lugar

¿A alguien le ha pasado algo parecido, a qué se debe?, para dejar de
ver el mensaje borré la entrada de google en /etc/apt/sources.list.d/
pero con eso también dejaré de recibir actualizaciones para el
navegador (da igual porque no se estaba actualizando de acuerdo al
mensaje anterior) pero, ¿hay alguna solución diferente?

-- 
Saludos,

Does anyone know how to configure a Brother MFC-J5720DW with cups?

[Jarle Aase]

Hi all,

I read some good reviews about this network printer/scanner, and noticed 
that it can scan to email or FTP. So I made the flawed(?) assumption 
that the printer would work independently without a software suite / 
drivers from Brother.


I tried to install it with the kde "Print Settings" front-end to cups. 
"Print Settings" finds the printer and lists several interfaces - 
however, I am unable to print anything no matter what configuration 
(combination of network protocol / printer driver) I use.


I know that I can download a bash script from Brother.com and run it as 
root - and then the printer is supposed to work with Debian. However, 
I'm not comfortable doing that. Actually, I'll rather scrap the printer 
and get another one that support lpd/ps natively than risk compromising 
/ messing up my system.


So my question is really if anyone have experience with recent Brother 
network printers and know a cups configuration that works with one of 
the standard Debian/Linux drivers.


I'm using both Debian Testing and Debian Stable on different machines 
right now.


Best regards,

jgaa

Re: LVM chiffré et passage de Wheezie à Jesssie.

[Randy11]

Merci beaucoup !

Je suis vraiment heureux de l'aide qui m'a été apportée.

Bonne journée.

Randy11

On 07/03/2016 23:51, Pascal Hambourg wrote:

Randy11 a écrit :

[  504.460680] EXT4-fs (sda4): unable to read superblock
[  504.462564] EXT4-fs (sda4): unable to read superblock
[  504.464474] EXT4-fs (sda4): unable to read superblock
[  504.475289] FAT-fs (sda4): bogus number of reserved sectors
[  504.477480] FAT-fs (sda4): bogus number of reserved sectors
[  504.487249] qnx4: no qnx4 filesystem (no root dir).

(...)

Device Boot  StartEndSectors  Size Id Type
/dev/sda1  *63  209728574  209728512  100G  7 HPFS/NTFS/exFAT
/dev/sda2209728575  734025914  524297340  250G  7 HPFS/NTFS/exFAT
/dev/sda3734025915  797514794   6340 30,3G  c W95 FAT32 (LBA)
/dev/sda4797515774 3907028991 3109513218  1,5T  5 Extended
/dev/sda5797515776 3906828992 3109313217  1,5T 8e Linux LVM
/dev/sda6   3906832384 3907028991 196608   96M 83 Linux

Que cela signifie-t-il ?

Que sda4 n'est pas une partition ext4, FAT ou QNX. Pas étonnant puisque
c'est une partition étendue.


Est-ce grave docteur ?

Non.

Fonts appearing with evince but not okular

[Dylan Thurston]

Hello,

On my Debian unstable system, I have a document which evince displays
correctly, but for which okular does not display much of the
text. This strikes me as odd, since (as I understand it) both
ultimately use the poppler back end, correct?

'gv' also displays the document correctly.

Unfortunately I can't share the document, as it is my credit card
bill. Below is the output from pdffonts and pdfinfo. Any guidance? How
can I get sufficient info to file a bug?

Many thanks,
Dylan Thurston

***

% pdfinfo 201511.pdf
Title:  
Subject:
Keywords:   
Author: 
Creator:
Producer:   Actuate Document Transform - 5.1.12 

CreationDate:   Mon Jan  4 19:04:03 2016
ModDate:Mon Jan  4 19:04:03 2016
Tagged: no
UserProperties: no
Suspects:   no
Form:   none
JavaScript: no
Pages:  4
Encrypted:  no
Page size:  612 x 1008 pts
Page rot:   0
File size:  354623 bytes
Optimized:  no
PDF version:1.4
% pdffonts 201511.pdf 
name type  encoding emb sub 
uni object ID
 -  --- --- 
--- -
[none]   Type 3Custom   yes no  
yes 39  0
[none]   Type 3Custom   yes no  
yes 38  0
[none]   Type 3Custom   yes no  
yes 34  0
Helvetica-Bold   Type 1WinAnsi  no  no  
no  40  0
[none]   Type 3Custom   yes no  
yes 76  0

***

Re: Cannot Load Changelogs!

[Martin Read]

On 07/03/16 03:13, maddonkeyk...@safe-mail.net wrote:

In Synaptic, I can't load any Changelogs, it gives this message:

This change is not coming from a source that supports changelogs.

Failed to fetch the changelog for cpio

URI was: 
http://packages.debian.org/changelogs/pool/main/c/cpio/cpio_2.11+dfsg-4.1+deb8u1/changelog

[apt-get changelog package] -> this fails too!


How does apt-get changelog fail - what error message does it display?

Also, have you tried using a *non-Tor* web browser to access the URI 
being printed for the changelog? This might help clarify whether you 
have a network access problem or a configuration problem with your 
package tools.

clone d'un système: problème avec systemd au boot

[Gaëtan PERRIER]

Bonjour,

Je viens de changer le disque dur de mon portable en clonant (avec fsarchiver
savedir/restdir) son disque vers le nouveau puis en réinstallant grub avec un
chroot. Mais au boot suivant, bien que la machine démarre, j'ai plein d'erreurs
systemd du genre:

Failed to mount Configuration File System

Failed to mount FUSE Control File System

Failed to start File System Check on Root Device

etc.

Vu que j'entrave que dalle à systemd je ne sais pas trop quoi faire ?

A+

Gaëtan

Re: GLPI - extjs: sous-répertoire manquant

[Jean-Marc]

Mon, 7 Mar 2016 15:38:43 +0100
Sébastien NOBILI  écrivait :

> [...]
> Tu parles d’un « access denied », sur quelle URL ?

C'est le tag  du html que GLPI me retourne.

Donc, en gros, je poste la forme de login et GLPI me retourne ceci comme HTML 
body :
The action you have requested is not 
allowed. Reload previous page before doing action 
again.GLPI version  
0.84.8 Copyright (C) 2003-2016 INDEPNET Development Team.

> 
> D’où te vient la configuration Nginx ? Du paquet Debian, d’un tuto sur le Web,
> de ta production ?

Config' perso basée sur une conversation précédente et d'autres configs.

La voilà :

location /glpi/ {
root /usr/share;
index index.php;
error_log /var/log/nginx/glpi-errors.log; # debug;

location ~ \.php$ {
include snippets/fastcgi-php.conf;
# With php5-fpm:
fastcgi_pass unix:/var/run/php5-fpm.sock;
}

}


> 
> Sébastien
> 


Jean-Marc 


pgpR2Kj_mXROC.pgp
Description: PGP signature

Re: Recherche DSI

[MENGUAL Jean-Philippe]

Bonjour,


Le 07/03/2016 15:09, andre_deb...@numericable.fr a écrit :
> On Sunday 06 March 2016 23:50:37 MENGUAL Jean-Philippe wrote:
>> Une commune de proche-banlieue parisienne cherche un DSI pour
>> accompagner son plan de migration au logiciel libre. Budget de 5
>> millions d'euros à gérer, personne pragmatique mais connaissant le
>> libre. L'élu en charge du numérique souhaite migrer vers libreoffice,
>> Zimbra, puis les serveurs. Une connaissance de Windows et une approche
>> du libre pragmatique est souhaitée. Salaire substantiel attendu.
>> N'hésitez pas à me répondre en privé avec vos coordonnées tél si vous
>> êtes intéressé.
> 
> Bonjour,
> 
> Sympa de communiquer cette annonce.
> 
> Est-il possible de connaître la commune, ne mairie je pense ?

Etant une demande "réseau", voire politique, mieux vaut réserver ça à un
échange privé.

> Comment procéder si on est intéressé ?

Me contacTer en me laissant un tél, un CV/profil Linkedin. Je redirige
vers l'élu en charge du numérique qui porte le projet.

Amitiés,

> Merci.
> 
> André
> 
> 

-- 

Jean-Philippe MENGUAL

HYPRA, progressons ensemble

Tél.: 01 84 73 06 61
Mail: cont...@hypra.fr

Site Web: http://hypra.fr

Re: wireless not working in strech

[Jude DaShiell]

Would you be willing to install Kalilinux?  I installed KaliLinux2.0 on 
a system and was shocked when it not only found my ralink wireless 
adapter but was able to configure it and go out on the network and 
install updates during installation.  You may also have similar luck 
using that version which is now on rolling release policy.  I have never 
had any luck installing wireless devices in command line environment on 
Debian.  One thing though about KaliLinux, it's a graphical user 
interface environment so if you don't like that kind of environment this 
won't be for you.  I'm agnostic about graphical user interface 
environments but don't use them much for productivity until I can get 
confident about my ability to use their accessibility effectively.  Your 
mileage probably will vary.  If I recall http://kali.org is where you 
get it and it's a debian fork which is really interested in security.


On Mon, 7 Mar 2016, nice sw123 wrote:


Date: Mon, 7 Mar 2016 15:50:37
From: nice sw123 
To: debian-user@lists.debian.org
Subject: wireless not working in strech
Resent-Date: Mon,  7 Mar 2016 21:06:12 + (UTC)
Resent-From: debian-user@lists.debian.org

After an upgrade, wireless is no longer working in stretch.
(I was using a wireless adapter and needed package: firmware-realtek).

* network-manager does not show wireless

*
 sudo iwconfig
... shows wlx008733553eaa instead of wlan0

*
 dmesg
...shows "renamed from wlan0"

*
issung the command
 sudo ln -s /dev/null /etc/udev/rules.d/80-net-setup-link.rules
changed the name back to "wlan0"

But wireless still does not show in network-manager.

What can one do?
Thanks.

n.




--

Re: LVM chiffré et passage de Wheezie à Jesssie.

[Pascal Hambourg]

Randy11 a écrit :
> 
> [  504.460680] EXT4-fs (sda4): unable to read superblock
> [  504.462564] EXT4-fs (sda4): unable to read superblock
> [  504.464474] EXT4-fs (sda4): unable to read superblock
> [  504.475289] FAT-fs (sda4): bogus number of reserved sectors
> [  504.477480] FAT-fs (sda4): bogus number of reserved sectors
> [  504.487249] qnx4: no qnx4 filesystem (no root dir).
(...)
> Device Boot  StartEndSectors  Size Id Type
> /dev/sda1  *63  209728574  209728512  100G  7 HPFS/NTFS/exFAT
> /dev/sda2209728575  734025914  524297340  250G  7 HPFS/NTFS/exFAT
> /dev/sda3734025915  797514794   6340 30,3G  c W95 FAT32 (LBA)
> /dev/sda4797515774 3907028991 3109513218  1,5T  5 Extended
> /dev/sda5797515776 3906828992 3109313217  1,5T 8e Linux LVM
> /dev/sda6   3906832384 3907028991 196608   96M 83 Linux
> 
> Que cela signifie-t-il ?

Que sda4 n'est pas une partition ext4, FAT ou QNX. Pas étonnant puisque
c'est une partition étendue.

> Est-ce grave docteur ?

Non.

Re: LVM chiffré et passage de Wheezie à Jesssie.

[Randy11]

C'est bien, mais le problème est que mes partitions cryptées qui 
doivent

correspondre à "/home" et "/swap" ne sont pas utilisées.


Le paquet cryptsetup est-il installé ?
As-tu essayé d'ouvrir les volumes chiffrés avec cryptsetup luksOpen... ?
Si cela fonctionne, tu pourras les ajouter au fichier /etc/crypttab 
(à moins que tu aies conservé celui de Wheezy) pour les ouvrir 
automatiquement au démarrage.




Merci pour les indications, j'ai récupéré l'ancien /etc/crypttab, 
refait ma swap cryptée, mis à jour /etc/crypttab avec le nouvel UID et 
ÇA MARCHE !!!


Après 15 jours de galère, je récupère enfin mon PC :-)

Un très grand MERCI à tous pour votre aide.

Randy11



On devrait toujours attendre avant de se réjouir :-(
J'allais mettre en veille mon PC quand l'idée m'est venue de faire 
"apt-get dist-upgrade", voilà

ce que j'obtiens (ce n'est que la fin) :

Paramétrage de linux-image-3.16.0-4-amd64 (3.16.7-ckt20-1+deb8u4) ...
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-3.16.0-4-amd64
/etc/kernel/postinst.d/zz-update-grub:
Création du fichier de configuration GRUB…
Found background image: /usr/share/images/desktop-base/desktop-grub.png
Image Linux trouvée : /boot/vmlinuz-3.16.0-4-amd64
Image mémoire initiale trouvée : /boot/initrd.img-3.16.0-4-amd64
[  504.460680] EXT4-fs (sda4): unable to read superblock
[  504.462564] EXT4-fs (sda4): unable to read superblock
[  504.464474] EXT4-fs (sda4): unable to read superblock
[  504.475289] FAT-fs (sda4): bogus number of reserved sectors
[  504.477480] FAT-fs (sda4): bogus number of reserved sectors
[  504.487249] qnx4: no qnx4 filesystem (no root dir).
Windows NT/2000/XP trouvé sur /dev/sda1
fait
Paramétrage de openssl (1.0.1k-3+deb8u4) ...
Paramétrage de python-pil:amd64 (2.6.1-2+deb8u2) ...
Paramétrage de python-imaging (2.6.1-2+deb8u2) ...
Traitement des actions différées (« triggers ») pour libc-bin 
(2.19-18+deb8u3) .


Pour mémoire, voici le partionnement :
Disque /dev/sda : 1,8 TiB, 2000398934016 octets, 3907029168 secteurs
Unités : secteur de 1 × 512 = 512 octets
Taille de secteur (logique / physique) : 512 octets / 512 octets
taille d'E/S (minimale / optimale) : 512 octets / 512 octets
Type d'étiquette de disque : dos
Identifiant de disque : 0x17121712

Device Boot  StartEndSectors  Size Id Type
/dev/sda1  *63  209728574  209728512  100G  7 HPFS/NTFS/exFAT
/dev/sda2209728575  734025914  524297340  250G  7 HPFS/NTFS/exFAT
/dev/sda3734025915  797514794   6340 30,3G  c W95 FAT32 (LBA)
/dev/sda4797515774 3907028991 3109513218  1,5T  5 Extended
/dev/sda5797515776 3906828992 3109313217  1,5T 8e Linux LVM
/dev/sda6   3906832384 3907028991 196608   96M 83 Linux



Que cela signifie-t-il ? Est-ce grave docteur ?

Re: LVM chiffré et passage de Wheezie à Jesssie.

[Randy11]

On 07/03/2016 00:37, Pascal Hambourg wrote:

Le 06/03/2016 23:35, Randy11 a écrit :


On 06/03/2016 13:01, Pascal Hambourg wrote:

- Créer une petite partition (5 Mo devraient suffire) formatée en 
ext2 à
monter sur /boot/grub, ce qui au mieux réduira suffisamment la 
taille de

l'image core pour qu'elle contienne dans l'espace post-MBR en évitant
l'intégration du module lvm, et au pire permettra à grub-install avec
l'option --force d'utiliser les listes de blocs.

(...)

J'ai créer une partition en etx2 /dev/sda6 en réduisant la taille de
mon volume groupe qui prenait toute la partition /dev/sda5.


Il n'était pas nécessaire que la partition contienne tout /boot ; 
/boot/grub suffisait et nécessitait une taille plus modeste.



C'est bien, mais le problème est que mes partitions cryptées qui doivent
correspondre à "/home" et "/swap" ne sont pas utilisées.


Le paquet cryptsetup est-il installé ?
As-tu essayé d'ouvrir les volumes chiffrés avec cryptsetup luksOpen... ?
Si cela fonctionne, tu pourras les ajouter au fichier /etc/crypttab (à 
moins que tu aies conservé celui de Wheezy) pour les ouvrir 
automatiquement au démarrage.




Merci pour les indications, j'ai récupéré l'ancien /etc/crypttab, refait 
ma swap cryptée, mis à jour /etc/crypttab avec le nouvel UID et ÇA 
MARCHE !!!


Après 15 jours de galère, je récupère enfin mon PC :-)

Un très grand MERCI à tous pour votre aide.

Randy11

Re: Le libre et les tablettes/smartphones

[andre_debian]

On Monday 07 March 2016 22:15:39 Jean Bernon wrote:
> Un article qui laisse songeur, où il est incidemment question de Debian. 
Qu'en dites-vous ? 
> 
http://www.numerama.com/tech/150130-le-monde-du-libre-face-a-une-nouvelle-ere-technologique.html

J'y vois surtout la suprématie d'Android (système non Libre selon l'article)
et l'échec d'Ubuntu, de FireFox-OS...

Ça ne vous fait pas penser à la suprématie de l'OS MS-Windows sur les PC,
dans les années 1990 ?
Tous les autres qui ont voulu se frotter au marché n'ont pas trop réussi.

Dans ces deux cas, deux sociétés milliardaires sont derrière, 
Microsoft et Google.

C'est Linus Tordvald qui a bien compris la situation.

André

Re: Le libre et les tablettes/smartphones

[jdd]

Le 07/03/2016 22:15, Jean Bernon a écrit :
Un article qui laisse songeur, où il est incidemment question de 
Debian. Qu'en dites-vous ?


http://www.numerama.com/tech/150130-le-monde-du-libre-face-a-une-nouvelle-ere-technologique.html

Aucun virus trouvé dans ce message.
Analyse effectuée par AVG - www.avg.fr 
Version: 2016.0.7442 / Base de données virale: 4540/11771 - Date: 
07/03/2016



article assez foutraque qui, surtout, mélange tablette et smartphone.

en smartphone, c'est android ou ios, rien d'autre.

mais en tablette, il y a d'autres choix, sauf que...

il y a les tablettes tactiles avec ios ou android qui utilisent des 
applis dédiées tactiles et le moins possible de clavier, et les 
tablettes intel/windows qui sont en fait des ordinateurs, successeurs 
des "netbooks", et qui recoivent assez bien linux, à quelques détails de 
pilotes près (elles sont très récentes).


La mienne fait tourner Debian et openSUSE.

par contre ni windows ni linux ne fait du touch screen réel, aucune 
application n'est touch only


jdd

Le libre et les tablettes/smartphones

[Jean Bernon]

Un article qui laisse songeur, où il est incidemment question de Debian. Qu'en 
dites-vous ? 

http://www.numerama.com/tech/150130-le-monde-du-libre-face-a-une-nouvelle-ere-technologique.html

Re: Is it possible to conduct a Debian install over wifi (iwlwifi)?

[Pascal Hambourg]

Andy Smith a écrit :
> 
> On Mon, Mar 07, 2016 at 03:39:26AM +, Andy Smith wrote:
>> As per
>> http://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/
>> I wrote an ISO of the current amd64 netinst including non-free
>> firmware to a USB and booted from it.
>>
>> At no point does it tell me that it requires additional firmware. It
>> also does not load iwlwifi or any of the associated wifi modules.
> 
> An off-list response said they had more success with a daily
> installer image.
> 
> I tried out:
> 
> 
> http://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/stretch_di_alpha5/amd64/iso-cd/
> 
> and indeed this now correctly says it requires firmware. It finds and
> configures the wlan device and is able to download things through
> wifi.

The 3.16 kernel included in Jessie is probably too old and lacks support
for this hardware. What does
$ lspci -nnk
report about the wireless adapter ?

wireless not working in strech

[nice sw123]

After an upgrade, wireless is no longer working in stretch.
(I was using a wireless adapter and needed package: firmware-realtek).

* network-manager does not show wireless

*
  sudo iwconfig
... shows wlx008733553eaa instead of wlan0

*
  dmesg
...shows "renamed from wlan0"

*
issung the command
  sudo ln -s /dev/null /etc/udev/rules.d/80-net-setup-link.rules
changed the name back to "wlan0"

But wireless still does not show in network-manager.

What can one do?
Thanks.

n.

Re: Is it possible to conduct a Debian install over wifi (iwlwifi)?

[Brian]

On Tue 08 Mar 2016 at 07:21:06 +1100, Andrew McGlashan wrote:

> 
> 
> On 8/03/2016 6:30 AM, Nicolas George wrote:
> > L'octidi 18 ventôse, an CCXXIV, Brian a écrit :
> >>> dpkg --fsys-tarfile /path/to/file.deb | tar x
> >>
> >> You've tried using dpkg from a console in the installer at the install
> >> stage we are considering? Feel free to report back on your experience.
> > 
> > No, but I am ready to bet public humiliation that this will work.
> 
> I'm sure you won't be humiliated  ... ;-)
> 
> 
> # dpkg --fsys-tarfile
> /var/cache/apt/archives/unzip_6.0-8+deb7u5_amd64.deb|tar t
> ./
> ./usr/
> ./usr/share/
> ./usr/share/man/
> ./usr/share/man/man1/
> ./usr/share/man/man1/unzip.1.gz
> ./usr/share/man/man1/unzipsfx.1.gz
> ./usr/share/man/man1/zipinfo.1.gz
> ./usr/share/man/man1/funzip.1.gz
> ./usr/share/man/man1/zipgrep.1.gz
> ./usr/share/doc/
> ./usr/share/doc/unzip/
> ./usr/share/doc/unzip/copyright
> ./usr/share/doc/unzip/BUGS
> ./usr/share/doc/unzip/ToDo
> ./usr/share/doc/unzip/History.600.gz
> ./usr/share/doc/unzip/changelog.Debian.gz
> ./usr/lib/
> ./usr/lib/mime/
> ./usr/lib/mime/packages/
> ./usr/lib/mime/packages/unzip
> ./usr/bin/
> ./usr/bin/zipinfo
> ./usr/bin/unzipsfx
> ./usr/bin/funzip
> ./usr/bin/zipgrep
> ./usr/bin/unzip
> ./usr/share/doc/unzip/changelog.gz

You got all of that output in an *installer environmemt* immediately
after the 'Load installer components from CD' stage of the stage?

Re: Is it possible to conduct a Debian install over wifi (iwlwifi)?

[Brian]

On Mon 07 Mar 2016 at 20:58:13 +0100, Nicolas George wrote:

> L'octidi 18 ventôse, an CCXXIV, Brian a écrit :
> > Over the years I've observed that statements based on some preconceived
> > idea take precedence over trying a procedure and coming to a conclusion
> > based on experience and what is documented.
> 
> Given your criticism, I suppose you did try. Can you copy-paste your
> attempt?

You suppose correctly, otherwise I would not put the effort into posting.
You (it would seem) haven't tried or tested what the installer does and
when dpkg becomes available. Asking me for the outcome of my attempt when
I have indicated it is impossible for it to work is not helpful.

I rather think the ball is in your court.

Re: Is it possible to conduct a Debian install over wifi (iwlwifi)?

[Andrew McGlashan]

On 8/03/2016 6:30 AM, Nicolas George wrote:
> L'octidi 18 ventôse, an CCXXIV, Brian a écrit :
>>> dpkg --fsys-tarfile /path/to/file.deb | tar x
>>
>> You've tried using dpkg from a console in the installer at the install
>> stage we are considering? Feel free to report back on your experience.
> 
> No, but I am ready to bet public humiliation that this will work.

I'm sure you won't be humiliated  ... ;-)


# dpkg --fsys-tarfile
/var/cache/apt/archives/unzip_6.0-8+deb7u5_amd64.deb|tar t
./
./usr/
./usr/share/
./usr/share/man/
./usr/share/man/man1/
./usr/share/man/man1/unzip.1.gz
./usr/share/man/man1/unzipsfx.1.gz
./usr/share/man/man1/zipinfo.1.gz
./usr/share/man/man1/funzip.1.gz
./usr/share/man/man1/zipgrep.1.gz
./usr/share/doc/
./usr/share/doc/unzip/
./usr/share/doc/unzip/copyright
./usr/share/doc/unzip/BUGS
./usr/share/doc/unzip/ToDo
./usr/share/doc/unzip/History.600.gz
./usr/share/doc/unzip/changelog.Debian.gz
./usr/lib/
./usr/lib/mime/
./usr/lib/mime/packages/
./usr/lib/mime/packages/unzip
./usr/bin/
./usr/bin/zipinfo
./usr/bin/unzipsfx
./usr/bin/funzip
./usr/bin/zipgrep
./usr/bin/unzip
./usr/share/doc/unzip/changelog.gz


Cheers
A.

Re: Problemas con la conexión inalámbrica en la instalación

[Paynalton]

-- 

 ___
< Llámala puta, pero no la llames fea.  >
 ---
\   ^__^
 \  (oo)\___
(__)\   )\/\
||w |
|| ||



El lun, 07-03-2016 a las 16:57 -0300, Felix Perez escribió:

> El día 7 de marzo de 2016, 12:23, Camaleón  escribió:
> > El Sun, 06 Mar 2016 19:31:18 +0100, Pablo Villacorta Pérez escribió:
> >
> > Pablo, acuérdate de configurar el cliente de correo para enviar los
> > mensajes en formato texto en lugar de html.
> >
> > Corrijo también el top-posting.
> >
> >> El 6 de marzo de 2016, 18:54, Camaleón  escribió:
> >>
> >>> El Sun, 06 Mar 2016 18:14:50 +0100, Pablo Villacorta Pérez escribió:
> >>>
> >>> (ese formato...)
> >>>
> >>> > Buenas Tardes:
> >>> >
> >>> > Os escribo para ver si me podéis solucionar un problema que estoy
> >>> > teniendo al instalar Debian Jessie.
> >>> > Al probar el sistema operativo si instalarlo en la versión Live me
> >>> > conecto correctamente a mi red inalámbrica, pero cuando comienzo la
> >>> > instalación y elijo la red a la que me quiero conectar me arroja el
> >>> > error "Failure of key exchange and association" aún cuando la clave
> >>> > WPA es correcta.
> >>>
> >>> No te recomiendo usar wifi en la instalación porque dependiendo del
> >>> tipo de adaptador de red que tengas necesitarás cargar algún firmware
> >>> adicional y el instalador no es un lugar "cómodo" para hacerlo :-)
> >
> > (...)
> >
> >> He pasado de configurar la conexión inalambrica durante la instalación y
> >> ahora me da otro error: "The 'grub-pc' package failed to install into
> >> /target/".
> >> ¿Cómo instalo el paquete?
> >
> > Insiste. Y asegúrate de tener configurada la red cableada y con acceso a
> > Internet y también de que tu equipo usa BIOS y no EFI.
> >
> > Recuerdo que cuando instalé Debian la primera vez tardó unas cuentas
> > veces en instalarse. Suena ridículo pero así fue. Vuelve al menú
> > principal del instalador y selecciona la opción de instalar el cargador
> > de arranque y elige las opciones predeterminadas (salvo que necesites
> > alguna otra configuración específica). Normalmente GRUB se instala en el
> > MBR del disco donde instalas el sistema.
> >
> 
> Primero vez que leo esto, he instalado Debian cientos de veces, desde
> potato en adelante y jamas he tenido que volver al menu del
> instalador.
> 

Bueno, recientemente con jessie tuve problemas al instalar en una MB con
UEFI, el cargador de arranque simplemente no funcionaba. Al final tuve
que desactivar UEFI para que debian pudiera iniciar normalmente.


> > De todas formas, no es imprescindible instalar ese paquete, podrás
> > iniciar desde el medio de instalación tras instalar el sistema y una vez
> > dentro ya podrás instalarlo manualmente.
> >
> 
> De acuerdo.
> 
> 
> 

Re: Is it possible to conduct a Debian install over wifi (iwlwifi)?

[Nicolas George]

L'octidi 18 ventôse, an CCXXIV, Brian a écrit :
> Over the years I've observed that statements based on some preconceived
> idea take precedence over trying a procedure and coming to a conclusion
> based on experience and what is documented.

Given your criticism, I suppose you did try. Can you copy-paste your
attempt?

Regards,

-- 
  Nicolas George


signature.asc
Description: Digital signature

Re: Problemas con la conexión inalámbrica en la instalación

[Felix Perez]

El día 7 de marzo de 2016, 12:23, Camaleón  escribió:
> El Sun, 06 Mar 2016 19:31:18 +0100, Pablo Villacorta Pérez escribió:
>
> Pablo, acuérdate de configurar el cliente de correo para enviar los
> mensajes en formato texto en lugar de html.
>
> Corrijo también el top-posting.
>
>> El 6 de marzo de 2016, 18:54, Camaleón  escribió:
>>
>>> El Sun, 06 Mar 2016 18:14:50 +0100, Pablo Villacorta Pérez escribió:
>>>
>>> (ese formato...)
>>>
>>> > Buenas Tardes:
>>> >
>>> > Os escribo para ver si me podéis solucionar un problema que estoy
>>> > teniendo al instalar Debian Jessie.
>>> > Al probar el sistema operativo si instalarlo en la versión Live me
>>> > conecto correctamente a mi red inalámbrica, pero cuando comienzo la
>>> > instalación y elijo la red a la que me quiero conectar me arroja el
>>> > error "Failure of key exchange and association" aún cuando la clave
>>> > WPA es correcta.
>>>
>>> No te recomiendo usar wifi en la instalación porque dependiendo del
>>> tipo de adaptador de red que tengas necesitarás cargar algún firmware
>>> adicional y el instalador no es un lugar "cómodo" para hacerlo :-)
>
> (...)
>
>> He pasado de configurar la conexión inalambrica durante la instalación y
>> ahora me da otro error: "The 'grub-pc' package failed to install into
>> /target/".
>> ¿Cómo instalo el paquete?
>
> Insiste. Y asegúrate de tener configurada la red cableada y con acceso a
> Internet y también de que tu equipo usa BIOS y no EFI.
>
> Recuerdo que cuando instalé Debian la primera vez tardó unas cuentas
> veces en instalarse. Suena ridículo pero así fue. Vuelve al menú
> principal del instalador y selecciona la opción de instalar el cargador
> de arranque y elige las opciones predeterminadas (salvo que necesites
> alguna otra configuración específica). Normalmente GRUB se instala en el
> MBR del disco donde instalas el sistema.
>

Primero vez que leo esto, he instalado Debian cientos de veces, desde
potato en adelante y jamas he tenido que volver al menu del
instalador.

> De todas formas, no es imprescindible instalar ese paquete, podrás
> iniciar desde el medio de instalación tras instalar el sistema y una vez
> dentro ya podrás instalarlo manualmente.
>

De acuerdo.



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

Re: Is it possible to conduct a Debian install over wifi (iwlwifi)?

[Brian]

On Mon 07 Mar 2016 at 20:30:19 +0100, Nicolas George wrote:

> L'octidi 18 ventôse, an CCXXIV, Brian a écrit :
> > > dpkg --fsys-tarfile /path/to/file.deb | tar x
> > 
> > You've tried using dpkg from a console in the installer at the install
> > stage we are considering? Feel free to report back on your experience.
> 
> No, but I am ready to bet public humiliation that this will work.

Over the years I've observed that statements based on some preconceived
idea take precedence over trying a procedure and coming to a conclusion
based on experience and what is documented.

dpkg is not installed with 'Load installer components from CD'.

If it is present the 'give-me-a-miracle=yes' option must have been
passed to d-i.

Re: Problemas con la conexión inalámbrica en la instalación

[Felix Perez]

El día 6 de marzo de 2016, 15:31, Pablo Villacorta Pérez
 escribió:
> He pasado de configurar la conexión inalambrica durante la instalación y
> ahora me da otro error: "The 'grub-pc' package failed to install into
> /target/".
> ¿Cómo instalo el paquete?

Por favor no hagas top posting, gracias.

ese error me parece que no tiene nada que ver con la red.

Revisa esto:
https://www.google.cl/?gws_rd=ssl#q=the+grub-pc+package+failed+to+install+into+%2Ftarget%2F+en+debian




>
> El 6 de marzo de 2016, 18:54, Camaleón  escribió:
>>
>> El Sun, 06 Mar 2016 18:14:50 +0100, Pablo Villacorta Pérez escribió:
>>
>> (ese formato...)
>>
>> > Buenas Tardes:
>> >
>> > Os escribo para ver si me podéis solucionar un problema que estoy
>> > teniendo al instalar Debian Jessie.
>> > Al probar el sistema operativo si instalarlo en la versión Live me
>> > conecto correctamente a mi red inalámbrica, pero cuando comienzo la
>> > instalación y elijo la red a la que me quiero conectar me arroja el
>> > error "Failure of key exchange and association" aún cuando la clave WPA
>> > es correcta.
>>
>> No te recomiendo usar wifi en la instalación porque dependiendo del tipo
>> de adaptador de red que tengas necesitarás cargar algún firmware
>> adicional y el instalador no es un lugar "cómodo" para hacerlo :-)
>>
>> Aún así, si quieres seguir por ese camino salta a una consola de
>> depuración cuando estés configurando la red vía wifi para ver qué te
>> dicen los registros.
>>
>> > He buscado en Google y no soy el único al que le ha sucedido esto, pero
>> > en ningún sitio encuentro una solución. ¿A alguién más le ha sucedido lo
>> > mismo o sabe cómo solucionarlo?
>>
>> Es un problema habitual. De hecho, ese escenario no estaba soportado
>> hasta hace poco, es decir, era habitual que fallara (y que lo siga
>> haciendo). Yo siempre uso la mini ISO y una conexión de red cableada o el
>> primer DVD como fuente de datos de la instalación.
>>
>> Saludos,
>>
>> --
>> Camaleón
>>
>



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

Re: Problemas con la conexión inalámbrica en la instalación

[Felix Perez]

El día 6 de marzo de 2016, 14:54, Camaleón  escribió:
> El Sun, 06 Mar 2016 18:14:50 +0100, Pablo Villacorta Pérez escribió:
>
> (ese formato...)
>
>> Buenas Tardes:
>>
>> Os escribo para ver si me podéis solucionar un problema que estoy
>> teniendo al instalar Debian Jessie.
>> Al probar el sistema operativo si instalarlo en la versión Live me
>> conecto correctamente a mi red inalámbrica, pero cuando comienzo la
>> instalación y elijo la red a la que me quiero conectar me arroja el
>> error "Failure of key exchange and association" aún cuando la clave WPA
>> es correcta.
>
> No te recomiendo usar wifi en la instalación porque dependiendo del tipo
> de adaptador de red que tengas necesitarás cargar algún firmware
> adicional y el instalador no es un lugar "cómodo" para hacerlo :-)

Eso no es correcto, si el equipo tiene usb, colocas el firmware en la
usb o cd, o dvd, y al preguntar si deseas instalar el firmare dile que
si y lo busca solo, lo instala solo y listo.  Obviamente todo esto en
modo experto, aunque en el modo simple sea igual.


>
> Aún así, si quieres seguir por ese camino salta a una consola de
> depuración cuando estés configurando la red vía wifi para ver qué te
> dicen los registros.
>
>> He buscado en Google y no soy el único al que le ha sucedido esto, pero
>> en ningún sitio encuentro una solución. ¿A alguién más le ha sucedido lo
>> mismo o sabe cómo solucionarlo?
>
> Es un problema habitual. De hecho, ese escenario no estaba soportado
> hasta hace poco, es decir, era habitual que fallara (y que lo siga
> haciendo). Yo siempre uso la mini ISO y una conexión de red cableada o el
> primer DVD como fuente de datos de la instalación.
>

Es lo preferible, pero a veces no se puede.

> Saludos,
>
> --
> Camaleón
>



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

Re: Is it possible to conduct a Debian install over wifi (iwlwifi)?

[Nicolas George]

L'octidi 18 ventôse, an CCXXIV, Brian a écrit :
> > dpkg --fsys-tarfile /path/to/file.deb | tar x
> 
> You've tried using dpkg from a console in the installer at the install
> stage we are considering? Feel free to report back on your experience.

No, but I am ready to bet public humiliation that this will work.

Regards,

-- 
  Nicolas George


signature.asc
Description: Digital signature

Re: exim4 maildir_tag

[Andrew McGlashan]

On 8/03/2016 4:31 AM, Darac Marjal wrote:
> On Tue, Mar 08, 2016 at 02:48:56AM +1100, Andrew McGlashan wrote:
>> Hi,
>>
>> I want to use this feature of dovecot [1].
>>
>> But it requires that each Maildir filename include ",S=$message_size" in
>> the file names.
>>
>> How can I get exim4 to create all new emails using the maildir_tag
>> format?

I've actually added the maildir_tag entry to these transports:
   /etc/exim4/conf.d/transport/35_exim4-config_address_directory
   /etc/exim4/conf.d/transport/20_save_local_message

That covers all saves done by the system_filter and also by any .forward
files that have "save $home/Maildir/" or subfolders.

Now I just need to work out how to gzip the files whilst keeping the
file names in tact so as not to effect any dovecot-uuidlist handling.

I'm still open to using dovecot-lda though if that works out to be the
best option.

Thanks
AndrewM



signature.asc
Description: OpenPGP digital signature

Re: Is it possible to conduct a Debian install over wifi (iwlwifi)?

[Brian]

On Mon 07 Mar 2016 at 16:19:37 +0100, Nicolas George wrote:

> L'octidi 18 ventôse, an CCXXIV, Brian a écrit :
> > 2. Unpack the .deb for the firmware you want:
> > 
> > ar -x /cdrom/pool/non-free/f/firmware-nonfree/
> > 
> > 3. Uncompress data.tar.xz:
> > 
> > unxz data.tar.xz
> > 
> > 4. Install the firmware in /lib/firmware:
> > 
> > tar xvf data.tar
> 
> What is the point of doing three steps with intermediate files when a single
> step is enough?

It makes things clearer for someone who doesn't mind doing step-by-step
processes. Walking before running springs to mind.

> For decompressing and detaring, everybody knows how to use a pipe:
> 
> unxz < data.tar.xz | tar x
> 
> With GNU tar, "tar xJ" will call unxz automatically, and if the input is a
> file, "tar xf" will detect the compression.

I'm positive this is good advice. Thanks for posting it.

> Furthermore, dpkg provides tools to handle deb packages:
> 
> dpkg --fsys-tarfile /path/to/file.deb | tar x

You've tried using dpkg from a console in the installer at the install
stage we are considering? Feel free to report back on your experience.

Re: exim4 maildir_tag

[Andrew McGlashan]

On 8/03/2016 4:31 AM, Darac Marjal wrote:
> On Tue, Mar 08, 2016 at 02:48:56AM +1100, Andrew McGlashan wrote:
> Probably the easiest way is to get dovecot to create the files. Look at
> either http://wiki.dovecot.org/LDA/Exim or
> http://wiki.dovecot.org/LMTP/Exim for how to tell Exim to deliver
> messages to dovecot. Dovecot will then store the file in whatever mail
> storage format you dictate (compress maildirs as you want, or its own
> dbox format).
> 
> Basically, LDA or LMTP allow you to decouple the mail delivery task
> (exim) from the mail storage task (dovecot).

So, mail queue handling will then be done by dovecot-lda instead of exim4.

Will mailq still give me results the same way?


Also, I do the following sometimes:
  exim4 -M msgid   # retry delivery
  exim4 -Mg msgid  # cancel delivery

  and others -Mvh  -Mvb and -Mvl

Will they all work the same or are there new ways to learn if I use
dovecot-lda ?

Thanks
AndrewM

Re: binary-i386 packages missing in Release file

[Lisi Reisz]

On Monday 07 March 2016 17:14:40 Haines Brown wrote:
> On Mon, Mar 07, 2016 at 02:54:22PM +, Lisi Reisz wrote:
> > On Monday 07 March 2016 00:30:44 Haines Brown wrote:
> > > On Sun, Mar 06, 2016 at 08:43:56PM -0300, Martinx - ジェームズ wrote:
> > > > Correct syntax is:
> > > >
> > > > --
> > > > deb [arch=amd64] http://dl.google.com/linux/chrome/deb/ stable main
> > > > --
> > > >
> > > > On 6 March 2016 at 20:10, Haines Brown  wrote:
> > > >
> > > > On Sun, Mar 06, 2016 at 10:47:26PM +0300, Reco wrote:
> > > > >       Hi.
> > > > >
> > > > > On Sun, 6 Mar 2016 14:34:25 -0500
> > > > >
> > > > > Haines Brown  wrote:
> > > > > > I have jessie installed on an AMD64 machine, which lacks any
> > > > > > desktop environment.
> > > > > >
> > > > > > I downloaded google-chrome AMD64 deb from the Chrome website
> > > > > > and installed by running dpkg -i on it. It works OK. But now
> > > > > > I want to add flashplugin-nonfree for it or, if that fails to
> > > > > > use it for my iceweasel. In order to install
> > > > > > flashplugin-nonfree I added contrib to the sources.list.
> > > > > >
> > > > > > When I do aptitude update, the contrib it hit, but the update
> > > > > > fails
>
> ...
>
> > > Progress, but not there yet. In sources.list I have the line:
> > >
> > >   deb [arch=amd64] http://dl.google.com/linux/chrome/deb/ stable main
> > >
> > > When I do # aptitude update, it starts with a warning:
> > >
> > >  W: Duplicate sources.list entry
> > >  http://dl.google.com/linus/chrome/deb stable/main amd64 Packages
> > >  (/var/lib/apt/lists/dl.google.com_linux_chrome_deb_dists_stable_ \
> > >  main_binary-amd64_packages)
> > >
> > >  W: You may want to update the packages lists to correct these
> > >  missing files
> > >
> > > then there are hits and gets and then 100% [working]. However, this
> > > is followed by a warning and errors:
> > >
> > >  W: Failed to fetch http://dl.google.com/linux/chrome/deb/dists/ \
> > >  stable/Release: Unable to find expected entry `main/binary-i386/ \
> > >  Packages' in Release file (Wrong sources.list entry or malformed
> > >  file)
> > >
> > >  E: Some index files failed to download. They have been ignored, or
> > >  old ones used instead
> > >
> > >  E: Couldn't rebuild package cache.
> > >
> > > This didn't stop me from installing the flashplugin-nonfree, but with
> > > aptitude update I still get more or less the same warnings and errors.
> > >
> > > Haines
> >
> > It sounds as though your Jessie is being identified as Wheezy.  You get
> > that warning with Wheezy, even if it is 64bit Wheezy with 64bit
> > Google-Chrome. Presumably because Google hasn't written a string of
> > different error messages for the various different things it has just
> > stopped supporting.
> >
> > Why Jessie is being identified as Wheezy is another question.  Is there
> > any reason why you might get identified as Ubuntu 12.04?  Another of the
> > things that has just dropped off Google's cliff.
> >
> > Lisi
>
> Lisi, I have to make a confession. The machine is actually running
> devuan Jessie. That is probably the reason.

Glad we have solved the mystery - though sadly not your problem. :-(

Lisi

Re: procomuns

[rita]

Hola a tothom!

Sóc la Rita i, fa poquet, m'he posat una Debian 8 Jessie (Dual-boot amb 
Windows 7). Hi ha moltes cosetes que no sé fer i, sovint, m'encallo, 
però vaig fent :)


Dues cosetes:

1. Fa cosa d'un parell de dies vau estar enviant uns mails per 
col·laborar però no vaig entendre de què tractava (netejar SPAM, crec, 
però no sé com es fa). Tot just aterro i no sé molt bé en què puc ser 
útil...


2. Contesto a un mail d'en Pedro que he trobat a l'SPAM... Jo també vull 
anar a les Jornades! Ara m'ho miraré molt rebé i m'inscriuré!


Seria xulo poder trobar a algú de la comunitat a les Jornades, així que 
he pensat que, -si no us sembla molt frikada-, per reconèixe'ns, les 
personetes de la llista podriem portar una Espiral de Debian a la solapa 
:)


Imatge espiral: 
https://commons.wikimedia.org/wiki/Debian#/media/File:Openlogo-debianV2.svg


Fins ben aviat! Una abraçada!,

---
rita :)

A 07/03/2016 17:10, Pedro escrigué:

És massa interessant per dir que no, i he vist que participa un membre
de Debian!

http://procomuns.net/en/

http://procomuns.net/participant/laura-arjona-reina/

ens hi veiem

Using a dedicated partition for VBox install

[Levi Darrell]

Has anybody had any luck using VBox to install a second system to a
dedicated partition on the host system, rather than a dynamically allocated
virtual hard disk? The reason I want to do this is that my computer has two
drives, a 120 GB SSD to which I have my host Debian system installed, and a
1 TB HDD. As much as I dislike it, I occasionally have to use Windows. I
have Debian installed on the SSD because it is much faster that way.
However, I don't want Windows to use any space on the SSD because space
there is limited. I could install Windows directly to the HDD, but I don't
want to do this because I already have an LFS system installed to the first
partition of that drive, and Windows will only install to the first
partition of a drive. I'd have to move things around in order to get that
to work. Secondly, I don't want to have to boot in and out of my Debian
system every time I need to use Windows for something. I want to be able to
use Windows through VBoxHeadless in a shell console, and then be able to
switch between shell consoles from Debian to Windows.

I installed VirtualBox version 5.0.16 from the VBox website, using the .run
file. I tried installing the .deb package first, but the installation
wouldn't complete because it wanted me to install packages that are no
longer in the repository. The .run installation completed successfully. I
successfully installed the extension pack. I was able to install both
Windows 10 and Windows 7 to a regular virtual hard disk on /dev/sda using
VBox. Everything is working fine.  However, I can't get VBox to install the
machine to /dev/sdb4, which is where I want to install the system.

I tried using the features described in this documentation:
https://www.virtualbox.org/manual/ch09.html#rawdisk. I tried issuing the
'VBoxManage internalcommands createrawvmdk -filename 
-rawdisk /dev/sdb -partitions 4' commands both with and without creating a
copy of the MBR and specifying the path to it (I don't think I should need
this, since I am doing a fresh install of Windows). I have changed the
permissions to 660 for /dev/sdb, /dev/sdb4, and all of the directories that
would contain the VMDK file. I have changed the ownership of /dev/sdb and
/dev/sdb4, as well as all of the directories, to . However, the
result of the command is sometimes 'Segmentation Fault' and sometimes
'Invalid command: 'createrawvmdk'.' I am obviously issuing the command as
 and not root, which as I understand it is proper.

I've searched in various forums and they all indicate this should work, but
all of the comments I have seen are pretty old and by users that are using
versions of VBox 4.0 or older. Is this feature no longer present in VBox,
and if not, is there some other way to accomplish this?

Thanks,

Levi

Business proposition

[Mike Jefferson]

Hello,

I am Mike Jefferson, and I am the digital marketing representative of 
several leading online sites and companies. 
These companies operate in various field that include: The gaming 
industry, Sports, Leisure industry and a Flower delivery brand.
I was impressed by your site: https://www.debian.org 
And would like to discuss the opportunity of hosting advertising 
space on it for one or some of my clients.
We have various propositions depends on the advertising options which 
include textural advertising, banner space and article publishing.

If that is something that interests you, please contact me and we can 
discuss the matter with greater detail and do business together.
Looking forward to hearing from you.

All the best,
Mike Jefferson
Digital Marketing Acquisition
www.media-buying.net

Re: exim4 maildir_tag

[Darac Marjal]

On Tue, Mar 08, 2016 at 02:48:56AM +1100, Andrew McGlashan wrote:

Hi,

I want to use this feature of dovecot [1].

But it requires that each Maildir filename include ",S=$message_size" in
the file names.

How can I get exim4 to create all new emails using the maildir_tag format?


Probably the easiest way is to get dovecot to create the files. Look at 
either http://wiki.dovecot.org/LDA/Exim or 
http://wiki.dovecot.org/LMTP/Exim for how to tell Exim to deliver 
messages to dovecot. Dovecot will then store the file in whatever mail 
storage format you dictate (compress maildirs as you want, or its own 
dbox format).


Basically, LDA or LMTP allow you to decouple the mail delivery task 
(exim) from the mail storage task (dovecot).




I believe that I need to add this in to my config, but I've tried to do
so and am not getting the right result.

maildir_tag = ,S=$message_size


[I am also not concerned about quotas right now.]


I have a split files configuration.

Dovecot version detail:
dovecot-common 1:2.1.7-7+deb7u1

Exim4 version detail:
exim4  4.80-7+deb7u1
exim4-base 4.80-7+deb7u1
exim4-config   4.80-7+deb7u1
exim4-daemon-heavy 4.80-7+deb7u1


[1] http://wiki2.dovecot.org/Plugins/Zlib

Kind Regards
AndrewM



--
For more information, please reread.


signature.asc
Description: PGP signature

Re: binary-i386 packages missing in Release file

[Haines Brown]

On Mon, Mar 07, 2016 at 02:54:22PM +, Lisi Reisz wrote:
> On Monday 07 March 2016 00:30:44 Haines Brown wrote:
> > On Sun, Mar 06, 2016 at 08:43:56PM -0300, Martinx - ジェームズ wrote:
> > > Correct syntax is:
> > >
> > > --
> > > deb [arch=amd64] http://dl.google.com/linux/chrome/deb/ stable main
> > > --
> > >
> > > On 6 March 2016 at 20:10, Haines Brown  wrote:
> > >
> > > On Sun, Mar 06, 2016 at 10:47:26PM +0300, Reco wrote:
> > > >       Hi.
> > > >
> > > > On Sun, 6 Mar 2016 14:34:25 -0500
> > > >
> > > > Haines Brown  wrote:
> > > > > I have jessie installed on an AMD64 machine, which lacks any
> > > > > desktop environment.
> > > > >
> > > > > I downloaded google-chrome AMD64 deb from the Chrome website and
> > > > > installed by running dpkg -i on it. It works OK. But now I want
> > > > > to add flashplugin-nonfree for it or, if that fails to use it for
> > > > > my iceweasel. In order to install flashplugin-nonfree I added
> > > > > contrib to the sources.list.
> > > > >
> > > > > When I do aptitude update, the contrib it hit, but the update
> > > > > fails

...

> > Progress, but not there yet. In sources.list I have the line:
> >
> >   deb [arch=amd64] http://dl.google.com/linux/chrome/deb/ stable main
> >
> > When I do # aptitude update, it starts with a warning:
> >
> >  W: Duplicate sources.list entry
> >  http://dl.google.com/linus/chrome/deb stable/main amd64 Packages
> >  (/var/lib/apt/lists/dl.google.com_linux_chrome_deb_dists_stable_ \
> >  main_binary-amd64_packages)
> >
> >  W: You may want to update the packages lists to correct these
> >  missing files
> >
> > then there are hits and gets and then 100% [working]. However, this
> > is followed by a warning and errors:
> >
> >  W: Failed to fetch http://dl.google.com/linux/chrome/deb/dists/ \
> >  stable/Release: Unable to find expected entry `main/binary-i386/ \
> >  Packages' in Release file (Wrong sources.list entry or malformed
> >  file)
> >
> >  E: Some index files failed to download. They have been ignored, or
> >  old ones used instead
> >
> >  E: Couldn't rebuild package cache.
> >
> > This didn't stop me from installing the flashplugin-nonfree, but with
> > aptitude update I still get more or less the same warnings and errors.
> >
> > Haines
> 
> It sounds as though your Jessie is being identified as Wheezy.  You get that 
> warning with Wheezy, even if it is 64bit Wheezy with 64bit Google-Chrome. 
> Presumably because Google hasn't written a string of different error messages 
> for the various different things it has just stopped supporting.
> 
> Why Jessie is being identified as Wheezy is another question.  Is there any 
> reason why you might get identified as Ubuntu 12.04?  Another of the things 
> that has just dropped off Google's cliff.
> 
> Lisi

Lisi, I have to make a confession. The machine is actually running
devuan Jessie. That is probably the reason.

Haines

Re: which files took the space

[Adam Wilson]

On Fri, 04 Mar 2016 08:11:43 +0100 Frédéric Marchal
 wrote:

> On Friday 04 March 2016 07:18:59 Adam Wilson wrote:
> > On Fri, 4 Mar 2016 04:03:01 +1100 Andrew McGlashan
> > 
> >  wrote:
> > > On 4/03/2016 3:07 AM, Adam Wilson wrote:
> > > > On Fri, 4 Mar 2016 03:03:53 +1100 Andrew McGlashan
> > > > 
> > > >  wrote:
> > > >> It also may have been files in the file system, but where
> > > >> another file system mount hides them
> > > > 
> > > > What does this mean? Mounts overlapping and hiding other mounts?
> > > > 
> > > > Explain, please.
> > > 
> > > Yes, this is more likely to happen to the root file system.
> > > 
> > > Say you have a bunch of files in /boot, but for some reason you
> > > have a /boot partition that wasn't mounted when those files were
> > > created  then you mount the /normal/ boot partition over it
> > > and now the other files are now hidden from view, but still
> > > taking up space.
> > 
> > So you're talking about creating files in an unmounted partition,
> > and then mounting it, but since file addition happened when the FS
> > was still in an unmounted state, the new files weren't written to
> > the journal?
> > 
> > Surely in that case the new files would simply not be registered and
> > act as free space (as if they had been deleted)?
> 
> This is not about a caching service. It is about the way the content
> of a mounted disk is made visible to you.
> 
> Have you ever wondered how a path name, on your main hard disk, such
> as /mnt/usb becomes a link to a USB disk known to the system
> as /dev/sdd1?
> 
> When you type
> 
> mount /dev/sdd1 /mnt/usb
> 
> It tells the system that, from now on, the directory named "/mnt/usb"
> becomes the entry point to the file system that sit at "/dev/sdd1".
> 
> Any call such as "ls /mnt/usb" will list the content of the USB disk
> instead of the usual content of /mnt/usb.
> 
> When the device is unmounted, the directory that serves as its mount
> point is restored as a regular directory.
> 
> Now, imagine /mnt/usb is not mounted. It is a directory just like any
> other. If you copy files to /mnt/usb, they will be copied to that
> directory and you have access to them as long as no device is mounted
> under /mnt/usb.

Ah. I see. Thank you for that- I was a little bit unsure as to what was
being referred to, until you came and gave an example.

Re: Is it possible to conduct a Debian install over wifi (iwlwifi)?

[Charlie Kravetz]

On Mon, 7 Mar 2016 16:19:37 +0100
Nicolas George  wrote:

>L'octidi 18 ventôse, an CCXXIV, Brian a écrit :
>> 2. Unpack the .deb for the firmware you want:
>> 
>> ar -x /cdrom/pool/non-free/f/firmware-nonfree/
>> 
>> 3. Uncompress data.tar.xz:
>> 
>> unxz data.tar.xz
>> 
>> 4. Install the firmware in /lib/firmware:
>> 
>> tar xvf data.tar  
>
>What is the point of doing three steps with intermediate files when a single
>step is enough?
>
>For decompressing and detaring, everybody knows how to use a pipe:
>

Actually, no, everybody does not know how to use a pipe. Many can not
even find the "|" on the keyboard.


>unxz < data.tar.xz | tar x
>
>With GNU tar, "tar xJ" will call unxz automatically, and if the input is a
>file, "tar xf" will detect the compression.
>
>Furthermore, dpkg provides tools to handle deb packages:
>
>dpkg --fsys-tarfile /path/to/file.deb | tar x
>
>Regards,
>


-- 
Charlie Kravetz
Linux Registered User Number 425914
[http://linuxcounter.net/user/425914.html]
Never let anyone steal your DREAM.   [http://keepingdreams.com]

Re: How to install wine (Was: empty subject)

[Linux-Fan]

[Mon, 7 Mar 2016 16:45:22 +0100] Milos Djeric 
wrote:
> How to install wine on debian 8 Jessie 64bit?Why is so hard and hear
> tearing to manage this?I searched on internet try ewerything
> installed from synaptic from terminal either works and when i tupe in
> terminall wine --version it show  wine 1.6.2 but on start meny on
> cinamon lxde xfce etc nowhere to find.Please if you hawe solution for
> this quide me because i not a expert for this kind of problem..

There is no need to have it in the menu.

Open a terminal and type `winecfg` (ENTER) to configure wine. Then, go
to a folder containing any windows executable and open a terminal
there. Enter `wine application.exe` (where `application.exe` is the
windows program file) to run it using wine.

HTH
Linux-Fan

-- 
http://masysma.lima-city.de/


pgp3DL2apTMFF.pgp
Description: OpenPGP digital signature

procomuns

[Pedro]

És massa interessant per dir que no, i he vist que participa un membre
de Debian!

http://procomuns.net/en/

http://procomuns.net/participant/laura-arjona-reina/

ens hi veiem

[no subject]

[Milos Djeric]

How to install wine on debian 8 Jessie 64bit?Why is so hard and hear
tearing to manage this?I searched on internet try ewerything installed from
synaptic from terminal either works and when i tupe in terminall wine
--version it show  wine 1.6.2 but on start meny on cinamon lxde xfce etc
nowhere to find.Please if you hawe solution for this quide me because i not
a expert for this kind of problem..

Sane/XSane on Debian Jessie (Error during device I/O)

[rmail]

After many hours of troubleshooting/googling, looking for some help:

I'm switching from Ubuntu to Debian Jessie, and am having problems
scanning via Sane. Oddly, I had no trouble with scanning on
Ubuntu/Xubuntu (14.04) with the same computer and same
scanner/printer. Printing is fine on both OS's.. It's just scanning
that won't work on Debian.

When I attempt a scan, I can hear the scanner moving, but then an error
appears before the image shows up on the computer.

I have tried both XSane (version: 0.998) and Simple Scan (3.14.0).

Here are the errors: XSane: Error during read: Error during device I/O.
Simple Scan: "Failed to scan Error communicating with scanner"

It makes no difference whether I run XSane/SimpleScan as "user" or
"root"; The same error occurs in both cases.

I also tried using Sane directly from command line, and this is
what I get:

#root@debianos:/home/me# sane-find-scanner found USB scanner
(vendor=0x040a [Eastman Kodak Company], product=0x4066 [KODAK ESP Office
2170 Series]) at libusb:001:008

#root@debianos:/home/me# scanimage -L device `v4l:/dev/video0' is a
Noname HD WebCam virtual device device `kodakaio:libusb:001:008' is a
Kodak KODAK ESP Office 2170 Series flatbed scanner

#root@debianos:/home/me# scanimage -d kodakaio --format pnm >
outfile.pnm scanimage: sane_read: Error during device I/O

On Debian Jessie I saw these files: /etc/sane.d/kodak.conf
/etc/sane.d/kodakaio.conf So to experiment, I tried replacing them with
the ones from my working Ubuntu. But that didn't help. And "diff" showed
almost no difference anyway.

Again, I have no trouble scanning using Ubuntu on the same
computer/scanner combo, so I'm thinking it should be possible on Debian.


Any help would be appreciated. Thanks in advance

exim4 maildir_tag

[Andrew McGlashan]

Hi,

I want to use this feature of dovecot [1].

But it requires that each Maildir filename include ",S=$message_size" in
the file names.

How can I get exim4 to create all new emails using the maildir_tag format?

I believe that I need to add this in to my config, but I've tried to do
so and am not getting the right result.

maildir_tag = ,S=$message_size


[I am also not concerned about quotas right now.]


I have a split files configuration.

Dovecot version detail:
dovecot-common 1:2.1.7-7+deb7u1

Exim4 version detail:
exim4  4.80-7+deb7u1
exim4-base 4.80-7+deb7u1
exim4-config   4.80-7+deb7u1
exim4-daemon-heavy 4.80-7+deb7u1


[1] http://wiki2.dovecot.org/Plugins/Zlib

Kind Regards
AndrewM

Re: [OT] sobre monitoring

[Camaleón]

El Mon, 07 Mar 2016 15:46:27 +0100, Alba Ferri escribió:

> Hola lista,

Ese formato...

> Mando esta consulta como OT porque no es algo de debian especificamente,
> pero como he visto que a veces se pregunta por temas relacionados con
> monitorizacion (nagios), queria preguntaros si sabeis si existe alguna
> lista en español donde se trate el tema...
> si no es así (que creo que no) que canales/webs/foros soleis usar?

La monitorización es un tema demasiado genérico, quizá alguna lista sobre 
redes te vendría bien. Por ejemplo, uno de los foros con más solera (y 
activo) es el de Linux Questions:

http://www.linuxquestions.org/questions/linux-networking-3/

Y obviamente también la lista de usuarios de Nagios:

http://lists.nagios.com/pipermail/nagios-users/

Por lo general, encontrar documentación y/o soporte en español es harto 
complicado, la mayoría de los recursos (y los más actualizados) suelen 
estar disponibles en inglés, pero podrías preguntar por aquí:

http://www.nagios-es.org/

Saludos,

-- 
Camaleón

Re: Problemas con la conexión inalámbrica en la instalación

[Camaleón]

El Sun, 06 Mar 2016 19:31:18 +0100, Pablo Villacorta Pérez escribió:

Pablo, acuérdate de configurar el cliente de correo para enviar los 
mensajes en formato texto en lugar de html.

Corrijo también el top-posting.

> El 6 de marzo de 2016, 18:54, Camaleón  escribió:
> 
>> El Sun, 06 Mar 2016 18:14:50 +0100, Pablo Villacorta Pérez escribió:
>>
>> (ese formato...)
>>
>> > Buenas Tardes:
>> >
>> > Os escribo para ver si me podéis solucionar un problema que estoy
>> > teniendo al instalar Debian Jessie.
>> > Al probar el sistema operativo si instalarlo en la versión Live me
>> > conecto correctamente a mi red inalámbrica, pero cuando comienzo la
>> > instalación y elijo la red a la que me quiero conectar me arroja el
>> > error "Failure of key exchange and association" aún cuando la clave
>> > WPA es correcta.
>>
>> No te recomiendo usar wifi en la instalación porque dependiendo del
>> tipo de adaptador de red que tengas necesitarás cargar algún firmware
>> adicional y el instalador no es un lugar "cómodo" para hacerlo :-)

(...)

> He pasado de configurar la conexión inalambrica durante la instalación y
> ahora me da otro error: "The 'grub-pc' package failed to install into
> /target/".
> ¿Cómo instalo el paquete?

Insiste. Y asegúrate de tener configurada la red cableada y con acceso a 
Internet y también de que tu equipo usa BIOS y no EFI.

Recuerdo que cuando instalé Debian la primera vez tardó unas cuentas 
veces en instalarse. Suena ridículo pero así fue. Vuelve al menú 
principal del instalador y selecciona la opción de instalar el cargador 
de arranque y elige las opciones predeterminadas (salvo que necesites 
alguna otra configuración específica). Normalmente GRUB se instala en el 
MBR del disco donde instalas el sistema.

De todas formas, no es imprescindible instalar ese paquete, podrás 
iniciar desde el medio de instalación tras instalar el sistema y una vez 
dentro ya podrás instalarlo manualmente.

Saludos,

-- 
Camaleón

Re: Is it possible to conduct a Debian install over wifi (iwlwifi)?

[Nicolas George]

L'octidi 18 ventôse, an CCXXIV, Brian a écrit :
> 2. Unpack the .deb for the firmware you want:
> 
> ar -x /cdrom/pool/non-free/f/firmware-nonfree/
> 
> 3. Uncompress data.tar.xz:
> 
> unxz data.tar.xz
> 
> 4. Install the firmware in /lib/firmware:
> 
> tar xvf data.tar

What is the point of doing three steps with intermediate files when a single
step is enough?

For decompressing and detaring, everybody knows how to use a pipe:

unxz < data.tar.xz | tar x

With GNU tar, "tar xJ" will call unxz automatically, and if the input is a
file, "tar xf" will detect the compression.

Furthermore, dpkg provides tools to handle deb packages:

dpkg --fsys-tarfile /path/to/file.deb | tar x

Regards,

-- 
  Nicolas George


signature.asc
Description: Digital signature

[ANNOUNCE] Laptop Mode Tools 1.69 Released

[Ritesh Raj Sarraf]

[For a web announcement, see: http://www.researchut.com/blog/laptop-mod
e-tools-1-69 ]

I am very pleased to announce the release of Laptop Mode Tools version
1.69.

This release adds on many bug fixes and some enhancements. There is a
new module (disabled by default) for cpuhotplug. The release tarball
also includes a basic PolicyKit file for convenience, that packagers
can use for the Laptop Mode Tools Graphical Configuration Interface.
Apart from the policykit file, the graphical invocation script has been
slightly fine tuned to work under pkexec and sudo. Some defaults have
been tuned based on user requests - This should improve in situations
where your External USB Mouse/Keyboard used to suspend after idle time
periods.

In January this year, I had the pleasure of meeting Bart Samwel in
person at his office in Amsterdam. For those who don't know, Bart
started off Laptop Mode Tools around 2004, and I took over maintenance
around 2008. Meeting in person has been a delight, especially with the
ones you work over email for years; This is something I cherished last
year at Debconf 15 too.

IMPORTANT:-  Until now, Laptop Mode Tools project was hosted on Bart's
webserver. Now, as you read, the homepage and mailing lists have
changed. I'd urge all users to subscribe to the new mailing list and
update their bookmarks.

Homepage: https://github.com/rickysarraf/laptop-mode-tools/wiki
Mailing List: https://groups.google.com/d/forum/laptop-mode-tools

Note: For users who are not comfortable with creating a google a/c for
mailing list subscription, you should still be able to subscribe with
your personal email address. Please follow the steps in the mentioned
homepage.

Since last couple releases, I've also been providing RPM packages for
Opensuse Tumbleweed and Fedora. The same should be available on the
github release page. The Debian package will follow shortly in the
Debian repository.

Thank you and a Happy Maha Shivaratri. Har Har Mahadev.

1.69 - Mon Mar  7 17:44:42 IST 2016
* Wait for all forked modules to complete
* Add new module: cputhotplug
* CPU online/offine is reverse here
* Fix shell syntax
* Install policykit file
* Detach polling daemon from main process
* Do NOT touch speed if throttling is not set
* Restore to MAX speed when back to AC Power
* Fix manpage about DISABLE_ETHERNET_ON_BATTERY setting
* Update documentation about ENABLE_LAPTOP_MODE_ON_AC setting
* Change powersaving default for USB class devices
* Drop usbhid from default (black)list
* Add usb keyboard driver to the list default list
* Be consistent with passing args to LMT from different invokers
* Honor device plug/unplug events on a per device basis;
  like how Chromium initially submitted this patch
* Also be consistent with option in the event parser
* Update links in README.md
* Update new github homepage location
* Add lmt-config-gui shell script


-- 
Ritesh Raj Sarraf
RESEARCHUT - http://www.researchut.com
"Necessity is the mother of invention."



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

Re: binary-i386 packages missing in Release file

[Lisi Reisz]

On Monday 07 March 2016 00:30:44 Haines Brown wrote:
> On Sun, Mar 06, 2016 at 08:43:56PM -0300, Martinx - ジェームズ wrote:
> > Correct syntax is:
> >
> > --
> > deb [arch=amd64] http://dl.google.com/linux/chrome/deb/ stable main
> > --
> >
> > On 6 March 2016 at 20:10, Haines Brown  wrote:
> >
> > On Sun, Mar 06, 2016 at 10:47:26PM +0300, Reco wrote:
> > >       Hi.
> > >
> > > On Sun, 6 Mar 2016 14:34:25 -0500
> > >
> > > Haines Brown  wrote:
> > > > I have jessie installed on an AMD64 machine, which lacks any
> > > > desktop environment.
> > > >
> > > > I downloaded google-chrome AMD64 deb from the Chrome website and
> > > > installed by running dpkg -i on it. It works OK. But now I want
> > > > to add flashplugin-nonfree for it or, if that fails to use it for
> > > > my iceweasel. In order to install flashplugin-nonfree I added
> > > > contrib to the sources.list.
> > > >
> > > > When I do aptitude update, the contrib it hit, but the update
> > > > fails
> > > >
> > > > because:
> > > > > W: Failed to fetch
> > > > > http://dl.google.com/linux/chrome/deb/dists/stable/Release:
> > > > > Unable to find expected entry 'main/binary-i386/Packages' in
> > > > > file
> > >
> > > 1) Locate the line like this in a file inside
> > > /etc/apt/sources.list.d:
> > >
> > > deb http://dl.google.com/linux/chrome/deb/
> > >
> > > 2) Change it to:
> > >
> > > deb [amd64] http://dl.google.com/linux/chrome/deb/
> > >
> > > This warning should go away.
> > >
> > > Reco
> >
> > Reco, your suggestion didn't work. When I do an update I get
> >
> > > E: Malformed line 14 in source list /etc/apt/sources.list ([amd64]
> > > is not an assignment)
> >
> > I did not have the dl.google.com line to start with. When I removed
> > the amd, and the line still malformed. When I comment the line
> > altogether, I get failed to fetch because there no
> > 'main/binary-i386/Pakages in release file. Why does it look for
> > dl.google.com? The line is not in sources.list.
> >
> > Haines
>
> Progress, but not there yet. In sources.list I have the line:
>
>   deb [arch=amd64] http://dl.google.com/linux/chrome/deb/ stable main
>
> When I do # aptitude update, it starts with a warning:
>
>  W: Duplicate sources.list entry
>  http://dl.google.com/linus/chrome/deb stable/main amd64 Packages
>  (/var/lib/apt/lists/dl.google.com_linux_chrome_deb_dists_stable_ \
>  main_binary-amd64_packages)
>
>  W: You may want to update the packages lists to correct these
>  missing files
>
> then there are hits and gets and then 100% [working]. However, this
> is followed by a warning and errors:
>
>  W: Failed to fetch http://dl.google.com/linux/chrome/deb/dists/ \
>  stable/Release: Unable to find expected entry `main/binary-i386/ \
>  Packages' in Release file (Wrong sources.list entry or malformed
>  file)
>
>  E: Some index files failed to download. They have been ignored, or
>  old ones used instead
>
>  E: Couldn't rebuild package cache.
>
> This didn't stop me from installing the flashplugin-nonfree, but with
> aptitude update I still get more or less the same warnings and errors.
>
> Haines

It sounds as though your Jessie is being identified as Wheezy.  You get that 
warning with Wheezy, even if it is 64bit Wheezy with 64bit Google-Chrome. 
Presumably because Google hasn't written a string of different error messages 
for the various different things it has just stopped supporting.

Why Jessie is being identified as Wheezy is another question.  Is there any 
reason why you might get identified as Ubuntu 12.04?  Another of the things 
that has just dropped off Google's cliff.

Lisi

[OT] sobre monitoring

[Alba Ferri]

Hola lista,

Mando esta consulta como OT porque no es algo de debian especificamente,
pero como he visto que a veces se pregunta por temas relacionados con
monitorizacion (nagios), queria preguntaros si sabeis si existe alguna
lista en español donde se trate el tema...
si no es así (que creo que no) que canales/webs/foros soleis usar?

Gracias!

Alba.

Re: GLPI - extjs: sous-répertoire manquant

[Sébastien NOBILI]

Le lundi 07 mars 2016 à 12:43, Jean-Marc a écrit :
> Quand j'essaie de me connecter, j'obtiens l'écran de login de GLPI, j'entre 
> le user/password glpi/glpi comme indiqué dans la doc et j'ai le message 
> suivant :
> « The action you have requested is not allowed. Reload previous page before 
> doing action again. »
> 
> Le seul élément trouvé jusqu'à présent est l'erreur 404.
> 
> Et là, je viens de jeter un œil en détail sur le trafic grâce à wireshark et 
> je viens de voir que la tentative de connexion reçoit un message "access 
> denied".
> 
> Ce n'est qu'ensuite que j'ai les erreurs 404.

Je pense (c’est purement théorique car je n’ai jamais installé / utilisé GLPI)
que tu ne devrais pas te focaliser sur ces erreurs 404 sur des fichiers JS /
CSS.

Tu parles d’un « access denied », sur quelle URL ?

D’où te vient la configuration Nginx ? Du paquet Debian, d’un tuto sur le Web,
de ta production ?

Sébastien

Re: Bluetooth: hardware detected but no device

[David Wright]

On Sun 06 Mar 2016 at 18:45:05 (+), Markos wrote:
> I'm using Jessie with a Dell laptop Latitude D430.
> 
> The system detect the hardware on boot:
> 
> dmesg | grep -i blue
> [9.685735] Bluetooth: Core ver 2.19
> [9.685759] Bluetooth: HCI device and connection manager initialized
> [9.685770] Bluetooth: HCI socket layer initialized
> [9.685773] Bluetooth: L2CAP socket layer initialized
> [9.685787] Bluetooth: SCO socket layer initialized
> [   20.010114] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
> [   20.010119] Bluetooth: BNEP filters: protocol multicast
> [   20.010135] Bluetooth: BNEP socket layer initialized
> 
> 
> But don't create a devide:
> 
> # hcitool dev
> Devices:

As pointed out in the thread, bluetooth may be switched off.
If the blue light (above F10, immediately R of green wifi) is
unlit, check if the sliding switch on the side (R of 
key) is in its central position. Towards the screen is off,
central is on, towards you is a momentary position that AIUI
requires configuring for a proprietary effect[1].

If you use wifi, then it'll be on already.

You might also check on:

$ /usr/sbin/rfkill list
0: dell-wifi: Wireless LAN
Soft blocked: no
Hard blocked: no
1: dell-bluetooth: Bluetooth
Soft blocked: no
Hard blocked: no
2: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
6: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
$ 

Cheers,
David.

[1] Quoting from the user guide page 53:

Dell Wi-Fi Catcher™ Network Locator
The wireless switch on your Dell computer uses the Dell Wi-Fi Catcher Network 
Locator to scan
specifically for WiFi WLAN in your vicinity. For more information about the 
wireless switch, see "Dell
Wi-Fi Catcher™ Network Locator" on page 53.

Re: Recherche DSI

[andre_debian]

On Sunday 06 March 2016 23:50:37 MENGUAL Jean-Philippe wrote:
> Une commune de proche-banlieue parisienne cherche un DSI pour
> accompagner son plan de migration au logiciel libre. Budget de 5
> millions d'euros à gérer, personne pragmatique mais connaissant le
> libre. L'élu en charge du numérique souhaite migrer vers libreoffice,
> Zimbra, puis les serveurs. Une connaissance de Windows et une approche
> du libre pragmatique est souhaitée. Salaire substantiel attendu.
> N'hésitez pas à me répondre en privé avec vos coordonnées tél si vous
> êtes intéressé.

Bonjour,

Sympa de communiquer cette annonce.

Est-il possible de connaître la commune, ne mairie je pense ?

Comment procéder si on est intéressé ?

Merci.

André

Re: GLPI - extjs: sous-répertoire manquant

[Jean-Marc]

Mon, 7 Mar 2016 11:23:43 +0100
Sébastien NOBILI  écrivait :

> Bonjour,
> 
salut Sébastien,

> Ça ne devrait pas empêcher le fonctionnement général de l’application, Nginx
> devrait renvoyer une erreur 404 au chargement de ce fichier et c’est tout
> (d’ailleurs le rapport de bug « reproche » la pollution des logs mais pas le
> mauvais fonctionnement de l’application).

Correct pour le rapport de bug mais c'est sous Apache, pas nginx.

> 
> Quel comportement obtiens-tu (dans ton navigateur) au juste ? Vois-tu des 
> choses
> intéressantes si tu charges les outils de dev. de ton navigateur (ou bien
> Firebug dans Iceweasel) ?

J'ai installé GLPI via le paquet Debian et fait un dpkg-reconfigure dans la 
foulée.

Apparemment, tout semble s'être bien passé.

Quand j'essaie de me connecter, j'obtiens l'écran de login de GLPI, j'entre le 
user/password glpi/glpi comme indiqué dans la doc et j'ai le message suivant :
« The action you have requested is not allowed. Reload previous page before 
doing action again. »

Le seul élément trouvé jusqu'à présent est l'erreur 404.

Et là, je viens de jeter un œil en détail sur le trafic grâce à wireshark et je 
viens de voir que la tentative de connexion reçoit un message "access denied".

Ce n'est qu'ensuite que j'ai les erreurs 404.

Bon, je retourne au charbon.

> 
> Sébastien
> 


Jean-Marc 


pgpii2zEOK9J0.pgp
Description: PGP signature

Re: Is it possible to conduct a Debian install over wifi (iwlwifi)?

[Andy Smith]

Hi Brian,

On Mon, Mar 07, 2016 at 10:46:47AM +, Brian wrote:
> 1. Stop at the 'Detect network hardware' stage and switch to a console.
> 
> 2. Unpack the .deb for the firmware you want:
> 
> ar -x /cdrom/pool/non-free/f/firmware-nonfree/

Because I was using the non-free firmware installers, the firmware
was already present in /lib/firmware and still the (jessie
net-)installer did not ask for it.

In my other follow-up I mentioned that a daily d-i stretch ISO
(again of the unofficial non-free firmware variety) did actually
work as far as wifi firmware was concerned, but bombed out with a
package conflict. It turns out that switching to the console and
doing "apt-get install -f" as it suggested did resolve that and the
install was able to proceed.

I have ended up with a successful install of stretch, entirely
installed over wifi, which is very encouraging.

I'm undecided whether to stay on testing though, so I might yet end
up trying a few different things to get stable installed…

Cheers,
Andy

Re: Depot Squeeze - apt-get update - erreur 404

[randy11]

Bonjour,

Petit avertissement (comme je viens d'être confronté au problème du passage de
Wheezy à Jessie) il faut vérifier le partitionnement.

J'ai une vieille installation dont le partitionnement a été fait par WindowsXP,
le passage de Wheezy (partions LVM) à Jessie m'a causé beaucoup de problèmes.
La cause : plus de place pour le bootloader. 

Il faut regarder à quel secteur commence la première partition :
- 63 -> ancien modèle, attention !
- 2048 -> nouveau modèle, aucun souci.

Le problème peut être contourné avec une toute petite partition normale, non
LVM.

Pour le détails, voir mon problème en cours de traitement sur la liste :
"LVM chiffré et passage de Wheezie à Jesssie."

J'ignore complètement comment Squeeze faisait le partitionnement, ma mise
en garde est peut-être sans objet.

Bonne journée.

Randy11

- Mail original -
De: "Hugues MORIN" 
À: "Liste Debian" 
Envoyé: Lundi 7 Mars 2016 09:01:06
Objet: Re: Depot Squeeze - apt-get update - erreur 404



Salut 

Au vue des retours d experiences que les membres de la liste ont eu, il 
semblerait que cela pose probleme. 

Surement du a de trop grande difference entre squeeze et jessie. 

Je profite de ce probleme pour apprendre a faire les upgrade car tout 
desinstaller puis tout reinstaller peut s averer problematique sur des serveurs 
en production. (Interruption de services, pertes de configuration, etc) 

Cordialement 
Hugues 
Le 4 mars 2016 12:24, "maderios" < mader...@gmail.com > a écrit : 


On 03/04/2016 10:45 AM, Hugues MORIN wrote: 
Bonjour 


Je vais potasser les releasenotes (qui ont l'air tres complete) et 
passer sous Wheezy. 
Je prends le train en marche, donc ce message est peut-être inutile. 
Une question me titille: pourquoi ne pas passer à la dernière stable, Jessie? 
Personnellement, quand j'ai des difficultés pour passer d'une version Debian à 
une autre, je désinstalle un maximum de paquets pour ne garder que le strict 
nécessaire puis je les réinstalle. Cela a toujours marché, aussi bien en 
upgrade qu'en downgrade. 
-- 
Maderios 

Re: Is it possible to conduct a Debian install over wifi (iwlwifi)?

[Brian]

On Mon 07 Mar 2016 at 03:39:26 +, Andy Smith wrote:

> Is there any way to force the debian-installer to realise it needs
> to load firmware for this wifi device? I have a feeling that it is
> seeing there is an eth0 and giving up at that point, assuming that
> is good enough.
> 
> All of my online research so far just shows instructions that say
> that the installer will ask for firmware if it thinks it needs it.
> 
> Is it even possible to do a Debian install over wifi alone?

1. Stop at the 'Detect network hardware' stage and switch to a console.

2. Unpack the .deb for the firmware you want:

ar -x /cdrom/pool/non-free/f/firmware-nonfree/

3. Uncompress data.tar.xz:

unxz data.tar.xz

4. Install the firmware in /lib/firmware:

tar xvf data.tar

5. Proceed with detecting network hardware and configuring the network.

Re: LVM chiffré et passage de Wheezie à Jesssie.

[MERLIN Philippe]

Bonjour,
Je te rappelle je ne suis pas un expert, cependant j'ai vécu à peu près le même 
souci sur mon 
portable lors d'une migration d'un disque sur un autre avec agrandissement des 
partitions. 
Je me suis trouvé avec Linux OK et Windows Vista OUT.
Dans ce cas il y a plusieurs solutions :
Réinstaller Windows XP  l'achat d'un Windows XP Pro ne doit pas être très cher, 
si tu ne l'as 
plus.
Deuxième solution utiliser des logiciels Gratuits (généralement pour 30 
jours)qui gèrent ce 
problème c'est ce que j'ai fait et le Windows Vista est à nouveau OK.

> Le partionnement a été fait lors de l'installation d'un WindowsXP...
> c'est vieux. J'ai gardé
> du Windows pour deux raisons : l'acquisition vidéo avec une carte
> Hauppauge et la
> récupérations de mes parcours enregistrés sur mon GPS Garmin Zumo 350LM.
> Le GPS
> est la dernière raison pour garder un Windows.
> 
Philippe Merlin

Re: GLPI - extjs: sous-répertoire manquant

[Sébastien NOBILI]

Bonjour,

Le dimanche 06 mars 2016 à 17:58, Jean-Marc a écrit :
> Mes premiers essais se heurtent à un soucis :
> 2016/03/06 17:37:37 [error] 19156#0: *10229 open() 
> "/usr/share/glpi/lib/extjs/locale/ext-lang-en.js" failed (2: No such file or 
> directory), client: 192.168.x.x, server: _, request: "GET 
> /glpi/lib/extjs/locale/ext-lang-en.js HTTP/1.1", host: "x.localdomain", 
> referrer: "http://x.localdomain/glpi/login.php;
> 
> Normal, dans le répertoire extjs, pas de sous-répertoire locale.
> 
> Et c'est repris comme un bug :
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766744
> 
> Apparemment, l'absence de ce sous-répertoire ne pose pas de soucis à GLPI et 
> pas de soucis non plus à certains web serveur comme Apache qui ont l'air plus 
> souples (mis à part les nombreux messages d'erreur).
> 
> Mais nginx semble moins tolérant.

Ça ne devrait pas empêcher le fonctionnement général de l’application, Nginx
devrait renvoyer une erreur 404 au chargement de ce fichier et c’est tout
(d’ailleurs le rapport de bug « reproche » la pollution des logs mais pas le
mauvais fonctionnement de l’application).

Quel comportement obtiens-tu (dans ton navigateur) au juste ? Vois-tu des choses
intéressantes si tu charges les outils de dev. de ton navigateur (ou bien
Firebug dans Iceweasel) ?

Sébastien

Re: Depot Squeeze - apt-get update - erreur 404

[Olivier]

Le 4 mars 2016 à 12:24, maderios  a écrit :

> On 03/04/2016 10:45 AM, Hugues MORIN wrote:
> Bonjour
>
>> Je vais potasser les releasenotes (qui ont l'air tres complete) et
>> passer sous Wheezy.
>>
> Je prends le train en marche, donc ce message est peut-être inutile.
> Une question me titille: pourquoi ne pas passer à la dernière stable,
> Jessie?
>

Il n'est pas possible de le faire directement :
on peut faire deux upgrades successifs mais pas passer directement de
Squeeze à Jessie


Personnellement, quand j'ai des difficultés pour passer d'une version
> Debian à une autre, je désinstalle un maximum de paquets pour ne garder que
> le strict nécessaire puis je les réinstalle. Cela a toujours marché, aussi
> bien en upgrade qu'en downgrade.
> --
> Maderios
>
>

Re: Depot Squeeze - apt-get update - erreur 404

[Hugues MORIN]

Salut

Au vue des retours d experiences que les membres de la liste ont eu, il
semblerait que cela pose probleme.

Surement du a de trop grande difference entre squeeze et jessie.

Je profite de ce probleme pour apprendre a faire les upgrade car tout
desinstaller puis tout reinstaller peut s averer problematique sur des
serveurs en production. (Interruption de services, pertes de configuration,
etc)

Cordialement
Hugues
Le 4 mars 2016 12:24, "maderios"  a écrit :

> On 03/04/2016 10:45 AM, Hugues MORIN wrote:
> Bonjour
>
>> Je vais potasser les releasenotes (qui ont l'air tres complete) et
>> passer sous Wheezy.
>>
> Je prends le train en marche, donc ce message est peut-être inutile.
> Une question me titille: pourquoi ne pas passer à la dernière stable,
> Jessie?
> Personnellement, quand j'ai des difficultés pour passer d'une version
> Debian à une autre, je désinstalle un maximum de paquets pour ne garder que
> le strict nécessaire puis je les réinstalle. Cela a toujours marché, aussi
> bien en upgrade qu'en downgrade.
> --
> Maderios
>
>