Re: [HS]Mesures techniques comme le téléchargement illégal

[Txo]

Le 11/11/2016 à 01:51, humbert.olivie...@free.fr a écrit :
> Point godwin validé.

Allons, allons, la Stasi ce n'est ni Hitler ni le nazisme. 


-- 
-+-  Dominique Marin http://txodom.free.fr -+-
  «Si vous croyez que les hackers ne sont qu'une bande d'anarchistes
prêts à tout mettre à feu et à sang, vous vous trompez du tout au tout,
-+- nous sommes bien pire que ça !» (No One Is Innocent)   -+-

Re: Problem attempting to use xorriso

[David Wright]

On Thu 10 Nov 2016 at 17:05:06 (-0600), Richard Owlett wrote:
> On 11/10/2016 1:52 PM, David Wright wrote:
> >On Thu 10 Nov 2016 at 04:53:47 (-0600), Richard Owlett wrote:
> >
> >>Yes, but not in the context of a sub-project from last few days.
> >>I suspect what I aiming at might look like - the groups and
> >>permission bits set at time partition created, thus avoiding games
> >>with /etc/fstab .
> >>
> >>richard@jessie-defaults:~$
> >>richard@jessie-defaults:~$ ls -l /dev/sd*
> >>brw-rw 1 root disk 8,  0 Nov 10 03:35 /dev/sda
> >>brw-rw 1 root owl  8,  1 Nov 10 03:35 /dev/sda1
> >>brw-rw-r-- 1 root owl  8,  2 Nov 10 03:35 /dev/sda2
> >>brw-rw 1 root disk 8,  3 Nov 10 03:35 /dev/sda3
> >>brw-rw 1 root disk 8,  5 Nov 10 03:35 /dev/sda5
> >>brw-rw 1 root disk 8, 16 Nov 10 04:43 /dev/sdb
> >>br--rw-r-- 1 root owl  8, 17 Nov 10 04:43 /dev/sdb1
> >
> > ↑ is there a purpose behind the missing w ?
> 
> Yes. My rational is in my rather verbose post
> https://lists.debian.org/debian-user/2016/11/msg00361.html .
> Linux evidently does not do things "my way" [apologies to a fast
> food chain].

Should I take it that last sentence means you are aware root can write
over a file even if the permission is - , let alone r ,
so you have no precaution as well as no protection.

Cheers,
David.

Re: Problem attempting to use xorriso

[Lisi Reisz]

On Thursday 10 November 2016 22:56:41 Richard Owlett wrote:
> I pre-date the Harvard MarkI

But not, I think, Colossus.

Lisi

[HS] Re: Mesures techniques comme le téléchargement illégal

[humbert . olivier . 1]

"On" m'a envoyé ce message en privé à la suite de mon précédent message de 3 
mots
(voir en bas de ce courriel) :

> j'ai reporté votre indésirable commentaire comme SPAM.
> pourquoi ne postez-vous pas sur la mailing-list allemande ou juive ou usa:uk ?
> qu'est-ce que la Stasi vient faire avec godwin ?

Alors j'ai 3 réflexions :

1. c'est marrant comme en fait, la dénonciation de "On" de mon message me fait 
tout à
   coup chavirer sur l'idée que cette liste debian est peut être en train de 
devenir une
   succursale de la Stasi si le fait d'envoyer un message de 3 mots suffit pour 
se faire
   dénoncé comme indésirable et spam :) (t'énerves pas "On" hein, y'a un smiley)

2. si "On" ou quelqu'un d'autre veut bien m'expliquer (en privé, pas la peine 
de polluer
   la liste avec ça) pourquoi "On" me recommande de poster sur une liste de 
diffusion
   "allemande", ou "juive" (d'ailleurs, j'imagine bien volontiers qu'une liste 
israélienne
   existe, mais une liste "juive" ça m'étonnerai un peu), ou une liste 
"usa:uk", alors je
   veux bien parce que là, après avoir tourné 3 ou 4 fois cette partie du 
message de "On"
   dans ma tête, je ne comprends vraiment pas.

3. évidemment, la Stasi est historiquement arrivée après l'effondrement de 
l'Allemagne nazie.
   Fin des années 40 il me semble. Je comptais ici sur l'intelligence des 
lecteurs pour
   comprendre qu'il n'y avait pas énormément de différence entre un point 
godwin (comparaison
   à Hitler ou au régime nazi) et une comparaison à la Stasi. M'enfin, si le 
colistier "On" à
   envie de se dire que la Stasi c'était tellement différent des RG chez les SS 
... enfin bref.

Allez, sans rancune de ma part, internet c'est aussi ça.
Olivier


- Mail original -
Envoyé: Vendredi 11 Novembre 2016 01:51:10
Objet: Re: Mesures techniques comme le téléchargement illégal

> ... Debian devient la Stasi ...

Point godwin validé.

Re: Mesures techniques comme le téléchargement illégal

[humbert . olivier . 1]

> ... Debian devient la Stasi ...

Point godwin validé.

Re: Problem attempting to use xorriso

[Richard Owlett]

On 11/10/2016 1:52 PM, David Wright wrote:

On Thu 10 Nov 2016 at 04:53:47 (-0600), Richard Owlett wrote:


Yes, but not in the context of a sub-project from last few days.
I suspect what I aiming at might look like - the groups and
permission bits set at time partition created, thus avoiding games
with /etc/fstab .

richard@jessie-defaults:~$
richard@jessie-defaults:~$ ls -l /dev/sd*
brw-rw 1 root disk 8,  0 Nov 10 03:35 /dev/sda
brw-rw 1 root owl  8,  1 Nov 10 03:35 /dev/sda1
brw-rw-r-- 1 root owl  8,  2 Nov 10 03:35 /dev/sda2
brw-rw 1 root disk 8,  3 Nov 10 03:35 /dev/sda3
brw-rw 1 root disk 8,  5 Nov 10 03:35 /dev/sda5
brw-rw 1 root disk 8, 16 Nov 10 04:43 /dev/sdb
br--rw-r-- 1 root owl  8, 17 Nov 10 04:43 /dev/sdb1


 ↑ is there a purpose behind the missing w ?

Cheers,
David.


Yes. My rational is in my rather verbose post
https://lists.debian.org/debian-user/2016/11/msg00361.html .
Linux evidently does not do things "my way" [apologies to a fast 
food chain].

Re: Problem attempting to use xorriso

[Richard Owlett]

On 11/10/2016 9:41 AM, Greg Wooledge wrote:


Well, let's see if I can shed some light here.  Probably not, but
I'll try.
[snip detailed essay]


Yes, you did shed needed light.
Thank you.

Re: Problem attempting to use xorriso

[Richard Owlett]

On 11/10/2016 8:53 AM, Lisi Reisz wrote:

On Thursday 10 November 2016 10:53:47 Richard Owlett wrote:

On 11/9/2016 5:16 PM, Lisi Reisz wrote:

On Sunday 06 November 2016 16:47:00 Richard Owlett wrote:

[snip]
Based on responses to previous posts titled "Trivial script will
NOT execute" and "Permissions for an entire PARTITION" I have
multiple problems understanding Linux file systems generally.


I imagine you have seen this lot - especially the top three??
https://www.google.co.uk/search?q=basic+debian+file+system=basic+debia
n+file+system=chrome..69i57.7617j0j7=chrome=UTF-8

Lisi


Yes, but not in the context of a sub-project from last few days.
I suspect what I aiming at might look like - the groups and
permission bits set at time partition created, thus avoiding
games with /etc/fstab .

richard@jessie-defaults:~$
richard@jessie-defaults:~$ ls -l /dev/sd*
brw-rw 1 root disk 8,  0 Nov 10 03:35 /dev/sda
brw-rw 1 root owl  8,  1 Nov 10 03:35 /dev/sda1
brw-rw-r-- 1 root owl  8,  2 Nov 10 03:35 /dev/sda2
brw-rw 1 root disk 8,  3 Nov 10 03:35 /dev/sda3
brw-rw 1 root disk 8,  5 Nov 10 03:35 /dev/sda5
brw-rw 1 root disk 8, 16 Nov 10 04:43 /dev/sdb
br--rw-r-- 1 root owl  8, 17 Nov 10 04:43 /dev/sdb1
richard@jessie-defaults:~$


My current homework is to now re-read ~40 posts and a to be
determined number of referenced links. Keywords will likely
include path, working directory, inode and mount ;/

--
If retirement isn't for learning, what use is it.


Richard - are you clear that the permissions are not for the partitions but
for the directories on the mount points on the filing system on which those
partitions have been hung??  This can be hard to grasp, but it can and does
sometimes make a difference, e.g. if the same partition or device gets
mounted somewhere else.


I'm getting the drift. It just one of things under the heading of 
"reality is a nuisance". There are a number of ways to tackle the 
problem that triggered my search. But they just ain't 
aesthetically pleasing.




Being slightly older than you, Richard and coming from the pre-electronic
computer generation, I am hoping to grasp and understand the basic Unix
filing system finally some time before I keel over.  (I *think* that
electronic computers are slightly older than you are.) ;-)


It may be close, I pre-date the Harvard MarkI. I am definitely 
older than Linus Torvalds father ;)


Lisi

Re: Mesures techniques comme le téléchargement illégal

[e Lpe]

Il faut leur couper les doigts à tous ces étudiant. Debian devient la
Stasi. Ah, belle France, que de collabos sont en sommeil. Filtrons ci,
filtrons ça. Et vos petits sites pornos vous vous les octroyez ou vous les
filtrer via un control parental. Viva la revolution !
Trop naze, les p'tits soi-disant administrateurs réseaux...
Honte aux listes Debian France, comme d'hab...

Le 9 novembre 2016 à 06:25, Eric Bernard <
eric.bern...@saint-louis-saumur-ec49.org> a écrit :

> Bonjour,
> Pour le DNS (bind) :
> j'ai mis en forwarder les ip de Norton ConnectSafe (il y a 3 niveaux de
> pré-filtrage) => https://support.norton.com/sp/
> fr/fr/home/current/solutions/v53246970_EndUserProfile_fr_fr
>
> pour google dans mon fichier db.nomdedomaine.
>
> google.com IN CNAME forcesafesearch.google.com.
> www.google.com IN CNAME forcesafesearch.google.com.
> google.fr IN CNAME forcesafesearch.google.com.
> www.google.fr IN CNAME forcesafesearch.google.com.
>
> et pour youtube :
> youtube.com IN CNAME forcesafesearch.google.com.
> www.youtube.com IN CNAME forcesafesearch.google.com.
>
> je pense ne rien oublier
>
> Après il y a aussi ce projet complet de filtrage par service DNS =>
> http://imyoufriend.fr/ServeurBind.html
>
> Cordialement
>
> --
>
>
>
>   Eric BERNARD
>   Responsable informatique
>   et multimédia
>   02 41 51 11 36
>
>
>
>
>
> Le 08/11/2016 à 14:50, Olivier a écrit :
>
> Bonjour,
>
> Le 7 novembre 2016 à 11:05, Eric Bernard  saumur-ec49.org> a écrit :
>
> Bonjour,
> voilà à mon avis ce qu'il faut faire :
>
> - mettre en place une charte informatique et la faire signer à chaque
> utilisateur ou l'inclure dans le règlement intérieur (fait dans mon
> établissement y compris pour des élèves majeurs (BTS).
> - mettre en place un filtrage internet (squid + squidGuard +
> squidanalyzer) avec authentification obligatoire sur le proxy (ici
> synchronisé avec un annuaire LDPAD.
> - Améliorer le filtrage avec un DNS en interne pour la redirection du
> HTTPS (je pense à google.. mais aussi les autres moteurs, et pas que les
> .fr car il y a les autres pays). On peut même avoir youtube en mode
> "restreint" !!!
>
>
> Peux-tu expliciter ce dernier point ?
>
>
>
> Il n'y a pas 36 solutions, soit on veut filtrer et on y met les moyens
> afin d'éviter des courriers indésirables, soit c'est la foire à
> "noeud-noeud" 
>
> En tout cas bon courage 
>
>
>
>
>
> Le 07/11/2016 à 10:20, Olivier a écrit :
>
> Merci à Jean pour ses quelques mots qui tempérent bien les choses:
> quand on reçoit une Xème lettre de menace de l'HADOPI ou d'ayant droits
> pour des actes que l'on a pas soi-même commis, les incantations ne
> suffisent pas, il faut faire un peu plus ;-)))
> Aller en cabane, parce ce qu'un tiers à mis à disposition sur le net une
> copie de "Les tortues Ninja à St-Tropez", c'est dur à accepter d'autant que
> ce film est nettement moins bon que "Les Tortues Ninja font du ski" ;-)))
>
> Comme nous utilisons souvent des box d'opérateur sur des lignes ADSL, nous
> ne maîtrisons pas le NAT.
> Ceci limite l'intérêt des logs dans la perspective de responsabiliser les
> utilisateurs sur leurs actes.
> Ma priorité va donc être de changer ça afin de pouvoir associer chaque
> flux sortant à une machine émettrice et son propriétaire.
>
> En d'autres termes, comme il ne semble pas y avoir de moyen facile comme
> l'interdiction d'un port précis, plutôt que de contrôler a priori
> l'utilisation du réseau, je vais améliorer son contrôle a posteriori.
> Chacun rendra des comptes sur ce qu'il fait sans que cela nuise aux autres.
>
> Merci à Jean-Michel pour sa mention de NXFilter: il est intéressant de
> savoir qu'il existe des moyens qui opèrent au niveau du DNS.
> L'éditeur de NXFilter est assez vague sur la façon dont sa blacklist est
> éditée.
>
>
> Le 6 novembre 2016 à 19:26, Jean Bernon  a écrit :
>
> OK mais alors il faut une vraie discussion.
> Je ne connais pas Olivier, mais il est face à un vrai problème que les
> incantations ne suffisent pas à régler. Je suis tout à fait d'accord avec
> ceux qui lui font observer que la technique n'est pas le droit, qu'aucune
> technique ne peut déterminer la légalité d'une action sur le réseau et
> qu'on peut au mieux gérer des listes noires. Je crois que faire signer des
> chartes est pratiquement la meilleure des solutions, même si elle a des
> limites évidentes. En même temps un administrateur réseau d'université ne
> peut pas ne pas réagir et ne pas être interpellé par la communauté
> universitaire lorsqu'il y a des téléchargements illégaux ou des contenus
> illégaux (racistes, sexistes etc.) émis par des membres de cette communauté
> depuis le réseau de l'université. Je suis convaincu qu'il y a des
> téléchargements juridiquement illégaux qui ne sont pas autorisés par une
> forme d'abus de pouvoir et qui sont en réalité utiles à la formation de
> tous et des étudiants en particulier. Mais il n'empêche qu'un
> administrateur ne peut pas 

[COLABORAÇÃO]: Monitoramento de ambiente com Centreon

[Henrique Fagundes]

Prezados colegas,

Gostaria de colaborar com a comunidade, fazendo uma explanação sobre o 
Centreon:


Segue o link:
https://www.aprendendolinux.com/monitoramento-de-ambiente-com-centreon/

Espero que seja útil para alguém.

Atenciosamente,

Henrique Fagundes
henri...@linuxadmin.com.br
Skype: magnata-br-rj
Linux User: 475399

http://www.aprendendolinux.com/
http://www.facebook.com/PortalAprendendoLinux
http://youtube.com/aprendendolinux/
http://twitter.com/aprendendolinux/
__
Participe do Grupo Aprendendo Linux
http://listas.aprendendolinux.com

Ou envie um e-mail para:
aprendendolinux-subscr...@listas.aprendendolinux.com

Re: Error Manual del Administrador de Debian

[Michael Milliman]

On 11/10/2016 10:00 AM, Marcos Aviles Luque wrote:
Muy buenas soy Marcos Avilés, he detectado un error o una errata en el 
ebook (Manual del Administrador de Debian), en el capítulo:



  6.2.4. Opciones de configuración

cuando tratamos de configuar el proxy para APT, y modificamos o 
creamos el archivo apt.conf la estructura de Acquire es la siguiente:


- Acquire::http::proxy::"http://su-proxy:3128;

Si consultamos el man de apt.conf en la sección de grupos ACQUIRE 
(línea 232) podemos verificar esta estructura.


Un coordial Saludo.



Gracias para esta informacion.  Pero, esta lista es para ellos que habla 
Engles.  El mayor de ellos que leyen esta lista no pueden leyer 
Espanol.  Hay una lista (debian-user-spanish) en Espanol.  Y tambien si 
es un error verdadero esta bien si reporte Usted un Bug con reportbug.


Por favor a escusar me Espanol, no he hablado (o escribido) Espanol in 
muchos anos.



--
73's
Mike, WB5VQX

samba

[Jose Alfredo Batista]

Saludos  lista  tengo instalado un samba  3 donde  se autentican bien  
la s PC de  win  el problema  es q tengo es el siguiente


las  PC de win xp se  unen  pero no guardan  el perfin el home/user  q 
es  la  idea  pero las  de win 7 y win8 si estan guardo el perfil y en  
ocaciones  no lo carga  cuando el usuario inicia  seccion alguna 
recomendacion de como desactivar  en  win 7 q s eguarde el perfil en el home



--
Este mensaje le ha llegado mediante el servicio de correo electronico que 
ofrece Infomed para respaldar el cumplimiento de las misiones del Sistema 
Nacional de Salud. La persona que envia este correo asume el compromiso de usar 
el servicio a tales fines y cumplir con las regulaciones establecidas

Infomed: http://www.sld.cu/

Re: Problem attempting to use xorriso

[David Wright]

On Thu 10 Nov 2016 at 04:53:47 (-0600), Richard Owlett wrote:

> Yes, but not in the context of a sub-project from last few days.
> I suspect what I aiming at might look like - the groups and
> permission bits set at time partition created, thus avoiding games
> with /etc/fstab .
> 
> richard@jessie-defaults:~$
> richard@jessie-defaults:~$ ls -l /dev/sd*
> brw-rw 1 root disk 8,  0 Nov 10 03:35 /dev/sda
> brw-rw 1 root owl  8,  1 Nov 10 03:35 /dev/sda1
> brw-rw-r-- 1 root owl  8,  2 Nov 10 03:35 /dev/sda2
> brw-rw 1 root disk 8,  3 Nov 10 03:35 /dev/sda3
> brw-rw 1 root disk 8,  5 Nov 10 03:35 /dev/sda5
> brw-rw 1 root disk 8, 16 Nov 10 04:43 /dev/sdb
> br--rw-r-- 1 root owl  8, 17 Nov 10 04:43 /dev/sdb1

↑ is there a purpose behind the missing w ?

Cheers,
David.

Re: xorriso: listing files+offsets in an ISO9660 image w/o RockRidge

[Thomas Schmitt]

Hi,

> Interestingly 1.4.7 can read one more of these ISOs, leaving 19 bad.

Was that already with -read_fs "norock" ?

If so: Do you still see the error message
  "Damaged RR/SUSP information."
?


> With 1.3.2 and this ISO in particular, it said
>libisofs: SORRY : Mandatory Rock Ridge PX entry is not present or it
>contains invalid values.

The error message still exists in 1.4.7. Somehow it must have avoided it.


> with 1.4.7, I get a few warnings
> libisofs: WARNING : Sum of resolved file name collisions: 159

Name collisions should not occur in any filesystem tree.
There is a limit of 255 characters per path component. Longer names get
truncated and could then collide. But that's very unlikely because the
truncated names contain a string with the MD5 of the untruncated name.

Are there preceeding warnings of form

  File name collision resolved with %s . Now: %s

?
The path and file name inserted into "%s" would be of interest.


> Boot record  : (system area only) , not-recognized APM

That's not a warning but a status summary:
"(system area only)" = No El Torito boot record is present.
"not-recognized" = none of the known hard disk boot sectors was recognized.
"APM" = an Apple Partition Map was found.

You might get more details about the APM with

  xorriso -indev ... -report_system_area plain


> System id: APPLE COMPUTER, INC., TYPE: 0002
> Volume id: IPHOTOARCHIV_240206

Might "240206" be a date stamp ? (24 Feb 2006 ?)


Have a nice day :)

Thomas

[ANNOUNCE] apt-offline 1.7.2 Released

[Ritesh Raj Sarraf]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hello World,

It gives me immense pleasure to announce the release of apt-offline,
version 1.7.2

For a detailed release announcement, please visit:
https://www.researchut.com/blog/apt-offline-172


This release includes many bug fixes, code cleanups and major updates to the
GUI.

Given that major updates in this release focus on the GUI, I urge users to visit
the above release announcement link.

The release details and other details about bug fixes is available in
the git repository and the announcement page above. Packages for Debian should
be available soon.

- -- 
Ritesh Raj Sarraf | http://people.debian.org/~rrs
Debian - The Universal Operating System
-BEGIN PGP SIGNATURE-

iQIcBAEBCgAGBQJYJK2FAAoJEKY6WKPy4XVpw5gQAIbs9GUj88d+5im2rQyIzAh8
41s8rfef0i+g1K+0zdOcfsyXER/6HboB3bfd8jVciNdQv+FNiKy4mtJenlUCgQso
8r4Cc4uohrJ8lAJ5BYxttGvsk9JdlDcvjXWlVZEsoeyYs+LQvvVLaiOPuPTXeeY4
MjDNDC5Gs0bnKxZLAp2MqpN9e+MqPTRsQ/myp1PcW4W9SGyPHCbP/FIdZ4QywjeE
k1d8EWxkNWpq0+KjCn19iU5iaHfJz5kSVKS8/4cOv7tgYu+JuDAUjhRKmIp3eZSf
jDr+dNbekPst5g4ggoX2u+iwPaOBLa5KATiwsuL6ZnTnfAxmYVvD7wNOhU4xh1PR
SMGew+ErrpV2dg69h2XXTW29cjvqSHjODj8fPs1mw8f5DQpf1DEwp9E4ygV/+XfP
MFTBunLEglUpbR48dwYtLNRlmuQGcrbRtAYJv+EftX3fJQJzszecvWnerXwoC8o3
pMECTfkqjBI5Q/riMqKkqyjGreF0delHXGClDDJRgtnUaHkaxbvdS/aP0w8bMDDE
uLy68TnduEVcQLrWK3I23cNVy3u11zBCEISTccBTkjNUV6wBmYF7Ld3Dv+SXk0S9
AMWpsFrJBUn9LGEeKZZxA3CIHfMiqgk5pthfm7mHN88NyEITwnltKq25WfxIj9h6
RxGmGfFeDsJoKiAaFfv2
=+IOJ
-END PGP SIGNATURE-

Re: Problem attempting to use xorriso

[Lisi Reisz]

Thanks, Greg!  That's brilliant! \o/

Lisi

On Thursday 10 November 2016 15:41:02 Greg Wooledge wrote:
> On Thu, Nov 10, 2016 at 02:53:14PM +, Lisi Reisz wrote:
> > Richard - are you clear that the permissions are not for the partitions
> > but for the directories on the mount points on the filing system on which
> > those partitions have been hung??  This can be hard to grasp, but it can
> > and does sometimes make a difference, e.g. if the same partition or
> > device gets mounted somewhere else.
> >
> > Being slightly older than you, Richard and coming from the pre-electronic
> > computer generation, I am hoping to grasp and understand the basic Unix
> > filing system finally some time before I keel over.  (I *think* that
> > electronic computers are slightly older than you are.) ;-)
>
> Well, let's see if I can shed some light here.  Probably not, but
> I'll try.
>
> At the bottom layer of this whole thing, we've got actual hardware.
> The computer can make the disk retrieve ("read") or store ("write")
> information by modifying the voltage on various wires.  The kernel
> knows how to tell the computer to do this (by dark magic).  The kernel
> can, for example, read byte number 13543287 of the disk.
>
> Storing all of your information in one gigantic chunk is not always
> the best policy, so you have the ability to subdivide the disk into
> "partitions".  Each partition is then treated as a separate hunk of
> bytes.  The kernel also knows about these, and it can request byte
> number 9986351 of partition number 3.
>
> Even with partitions, retrieving information from a disk in this way
> would be terribly inconvenient for most applications, so this is almost
> never done.  Instead, there is another layer: the file system.  A disk,
> or a partition, can have an organizational structure laid on top of
> it which allows information to be stored in "files" which have names.
> Instead of requesting byte number 9986351 of partition number 3, you can
> request byte number 0 of the file named "bin/ls" inside the file system on
> partition number 3.  This is the layer at which most applications operate.
>
> Following the unix philosophy, the kernel presents an interface to each
> of these layers, including access controls.
>
> For the raw disk layer, there is a block device like /dev/sda.  You
> can read byte number 13543287 of /dev/sda and see what it is.  In
> order to do this, you need read permission on the /dev/sda file.
>
> At the partition layer, there are block devices like /dev/sda3.  You
> can read byte number 9986351 of /dev/sda3 and see what it is.  For
> this, you need read permission on the /dev/sda3 file.
>
> Those are simplistic layers, and not often used.  Pretty much the only
> time you would ever read from one of those devices is to retrieve the
> partition table from the disk, or to see what kind of file system is on
> a given partition.  Lower level tools like mkfs and fsck and fdisk and
> lsblk handle these details.
>
> Things become much more interesting when we move up to the file system
> layer.
>
> The first thing to know about file systems is that they have to be
> "mounted" in order to work.  The word "mount" comes from old tape drive
> technology (reel to reel), when operators would be requested to mount
> a tape, which is a physical act not dissimilar to hanging a picture on
> a wall.  It has been adopted for file systems, even though there isn't
> a physical movement of objects.
>
> In order to mount a file system, you need to know which disk or partition
> the file system is stored on, and what directory you want to attach it to.
> You also have to be root, because this is a potentially VERY intrusive
> thing to do.  If an ordinary user could mount a file system on /bin then
> he could easily take over the whole system, because users would be
> executing HIS version of /bin/ls and so on.
>
> Typically the directory where you mount a file system is just an empty
> stub.  But it doesn't have to be.  Let's say you have a single file
> system (/) mounted currently, and it has a directory called "home" in
> it.  Now let's say you've got some files in this directory.  If you mount
> /dev/sda3 on /home then the contents of /dev/sda3's file system become
> visible inside /home.  The files that you saw in /home BEFORE the mount
> are hidden.  They're still in the / file system but you can't see them
> or interact with them.
>
> The second thing you need to know about file systems is that they
> have their own metadata.  File ownerships, permissions, and so on are
> stored within the inodes (index nodes) of the file system.  When you
> mount the file system, you see only the files and the metadata from
> the mounted file system.  The metadata of the directory that you mounted
> it on is no longer relevant.  The metadata of the block device that
> stores the file system is also irrelevant.
>
> Before mounting:
> drwxr-xr-x 4 john doe 4096 Aug 22 11:41 /home
>
> After mounting:
> 

Re: Script conversió fotografies CR2 a DNG

[Xavi Llista]

Hola Andrés,
moltes gràcies per l'explicació detallada. És exactament així.
Salutacions,
Xavi

El dia 4 de novembre de 2016, 22:15, Andrés  ha
escrit:

> Hola llista,
>
> fa molt que no escric aquí ni m'ho miro gaire, menys avui... Crec que
> estàs de sort Xavi :)
>
> Am 04/11/2016 um 15:13 schrieb Narcis Garcia:
> > https://en.wikipedia.org/wiki/Phatch
> >
> > El 04/11/16 a les 14:45, Xavi Llista ha escrit:
> >> fa dies que miro de trobar la manera de crear un script (més o menys
> >> senzill) per convertir de forma massiva tots els fitxers de fotografia
> >> d'una determinada capreta en format CR2 a format DNG. He estat mirant
> >> moltes pàgines però he estat capaç de trobar cap eina que em permeti
> >> executar amb línia de comandes alguna instrucció per convertir els CR2 a
> >> DNG.
>
>
> Doncs mira, justament fa un parell de mesos vaig ocupar-m'hi amb aquests
> temes.
> Resulta que CR2 no és pas "un format" en el sentit que no és una cosa
> estandarditzada. Vol dir que cada fabricant de càmeres fa el que el
> rota. Això vol dir que el format d'un fitxer RAW de la càmera X pot ser
> diferent del fitxer RAW de la càmera Y, encara que siguin del mateix
> fabricant.
>
> Bàsicament l'estat actual de les coses és:
> - Reverse engineering per entendre com funcionen les diferents càmeres
> - Adaptació dels algorismes que interpreten aquests fitxers
>
> Havent fet aquesta introducció, sí que hi ha eines que tracten amb
> aquests fitxers; dcraw [1] és *EL* programa per tractar amb imatges RAW
> però estic bastant segur que només converteix a Bitmap d'algun tipus. Si
> trobes una llibreria per això, molt probablement és un "wrapper"
> respecte aquest programa.
>
> En Narcís mencionava Phatch per convertir entre formats RAW, però crec
> que això no és ben bé el que passa. Mirant les dependències de
> phatch-cli [2], diria que bàsicament fa servir dcraw per llegir les
> imatges RAW i per tant deu fer servir un Bitmap intermig.
>
> Per convertir entre formats RAW no sé de cap programa (lliure) en línia
> de comandes, per la pinta que fa DigiKam 2.7 tenia justament el que
> necessites [3] en un dels programes de 'test' per un plugin. La pregunta
> és si, com crec que fa el Phatch, fa servir un Bitmap intermig!
> La resposta està, és clar, en mirar-se el codi... Per això és programari
> lliure.
>
> En fi, el tema és més complicat del que hom s'espera... Jo et
> recomanaria que si t'interessa mantenir la fidelitat de les teves fotos
> i el format RAW de la teva càmera és suportat per dcraw, no facis cap
> tipus de conversió fins que realment les treballis; de fet hi ha gent a
> la xarxa que comença a desaconsellar convertir a DNG tot plegat [4] [5].
> Si la teva càmera suporta generar fitxers DNG, això seria la
> configuració ideal.
>
> Espero que tota aquesta parrafada et serveixi d'alguna cosa i si
> descobreixes més coses ens avisis :).
>
> Salut,
>
> [1]: http://www.cybercom.net/~dcoffin/dcraw/dcraw_ca.1.html
> [2]: https://packages.debian.org/jessie/phatch-cli
> [3]: https://searchcode.com/codesearch/view/20116600/
> [4]: https://photographylife.com/why-i-no-longer-convert-raw-files-to-dng
> [5]:
> http://petapixel.com/2015/07/16/why-i-stopped-using-the-dng-file-format/
> --
> Andrés
>
>

Re: xorriso: listing files+offsets in an ISO9660 image w/o RockRidge

[Jonathan Dowland]

On Thu, Nov 10, 2016 at 11:56:36AM +, Jonathan Dowland wrote:
> On Thu, Nov 10, 2016 at 11:35:02AM +, Jonathan Dowland wrote:
> > I'll try the following command with both my current xorriso version and 
> > 1.4.6,
> > against all of my currently imported ISOs, and report back what my results
> > are:
> 
> With 1.3.2, at least, only 20/45 of my ISOs fail; the Application labels for 
> them
> are

Interestingly 1.4.7 can read one more of these ISOs, leaving 19 bad.

With 1.3.2 and this ISO in particular, it said

libisofs: SORRY : Mandatory Rock Ridge PX entry is not present or it 
contains invalid values.

with 1.4.7, I get a few warnings

...
libisofs: WARNING : Sum of resolved file name collisions: 159
Boot record  : (system area only) , not-recognized APM
Media summary: 1 session, 345484 data blocks,  675m data, 72.2g free
...

but it does enumerate the files in the image.

isoinfo(1) from genisoimage package gives the following metadata. This was 
almost certainly
burned on a Windows machine albeit with iPhoto or iTunes or something

CD-ROM is in ISO 9660 format
System id: APPLE COMPUTER, INC., TYPE: 0002
Volume id: IPHOTOARCHIV_240206
Volume set id:
Publisher id:
Data preparer id:
Application id:
Copyright File id:
Abstract File id:
Bibliographic File id:
Volume set size is: 1
Volume set sequence number is: 1
Logical block size is: 2048
Volume size is: 345484
Joliet with UCS level 1 found
Rock Ridge signatures version 1 found

-- 
Jonathan Dowland
Please do not CC me, I am subscribed to the list.


signature.asc
Description: Digital signature

Error Manual del Administrador de Debian

[Marcos Aviles Luque]

Muy buenas soy Marcos Avilés, he detectado un error o una errata en el
ebook (Manual del Administrador de Debian), en el capítulo:
6.2.4. Opciones de configuración

cuando tratamos de configuar el proxy para APT, y modificamos o creamos el
archivo apt.conf la estructura de Acquire es la siguiente:

- Acquire::http::proxy::"http://su-proxy:3128;

Si consultamos el man de apt.conf en la sección de grupos ACQUIRE (línea
232) podemos verificar esta estructura.

Un coordial Saludo.

Re: Connexion internet qui lâche avec Postfix

[Daniel Caillibaud]

Le 10/11/16 à 16:37, Alain Rpnpif  a écrit :
AR> Au pire un serveur DNS sur le poste de travail s'il est seul sur le
AR> réseau.

Je mets un unbound par machine sur le réseau, ça consomme vraiment rien 
(peut-être que sur un
rasperry c'est notable, et qu'il vaut mieux lui indiquer le unbound voisin, pas 
mesuré), et ça
accélère tout ce qui a besoin de résoudre des noms (soit quasi tous les services
utilisant le réseau).

L'autre avantage de unbound, c'est la simplicité pour installer une zone 
locale, j'ai comme ça
ma zone lan.monDomaine.tld, inconnue des dns publics, avec 
machine1.lan.monDomaine.tld qui
n'existe que sur le lan concerné (donc pour joindre machine1, si on est sur le 
lan on va
récupérer son ip privée, et sinon son ip publique si elle en a une via le dns 
public avec
machine1.monDomaine.tld).

Depuis j'ai un seul fichier txt pour mes ip privées, plutôt que d'aller 
bricoler les /etc/hosts
de ceux que ça intéresse.

-- 
Daniel

La justice militaire est a la justice ce que la musique
militaire est a la musique.
Groucho Marx

Re: Resolved: sound disappeared

[Tony Baldwin]

On 11/10/2016 04:40 AM, Darac Marjal wrote:

On Wed, Nov 09, 2016 at 05:08:28PM -0500, Anthony Baldwin wrote:

Still getting messages on this: issue resolve, brethren (and sisters,
too!)


I believe the analog to "brethren" is "sistren".


Never heard or saw the word in my life, but I just looked it up,
and, indeed, you are correct!
I guess you CAN learn something new every day!

Thanks for the tip
tony

--
http://tonybaldwin.me
all tony, all the time

Re: Problem attempting to use xorriso

[Greg Wooledge]

On Thu, Nov 10, 2016 at 02:53:14PM +, Lisi Reisz wrote:
> Richard - are you clear that the permissions are not for the partitions but 
> for the directories on the mount points on the filing system on which those 
> partitions have been hung??  This can be hard to grasp, but it can and does 
> sometimes make a difference, e.g. if the same partition or device gets 
> mounted somewhere else.
> 
> Being slightly older than you, Richard and coming from the pre-electronic 
> computer generation, I am hoping to grasp and understand the basic Unix 
> filing system finally some time before I keel over.  (I *think* that 
> electronic computers are slightly older than you are.) ;-)

Well, let's see if I can shed some light here.  Probably not, but
I'll try.

At the bottom layer of this whole thing, we've got actual hardware.
The computer can make the disk retrieve ("read") or store ("write")
information by modifying the voltage on various wires.  The kernel
knows how to tell the computer to do this (by dark magic).  The kernel
can, for example, read byte number 13543287 of the disk.

Storing all of your information in one gigantic chunk is not always
the best policy, so you have the ability to subdivide the disk into
"partitions".  Each partition is then treated as a separate hunk of
bytes.  The kernel also knows about these, and it can request byte
number 9986351 of partition number 3.

Even with partitions, retrieving information from a disk in this way
would be terribly inconvenient for most applications, so this is almost
never done.  Instead, there is another layer: the file system.  A disk,
or a partition, can have an organizational structure laid on top of
it which allows information to be stored in "files" which have names.
Instead of requesting byte number 9986351 of partition number 3, you can
request byte number 0 of the file named "bin/ls" inside the file system on
partition number 3.  This is the layer at which most applications operate.

Following the unix philosophy, the kernel presents an interface to each
of these layers, including access controls.

For the raw disk layer, there is a block device like /dev/sda.  You
can read byte number 13543287 of /dev/sda and see what it is.  In
order to do this, you need read permission on the /dev/sda file.

At the partition layer, there are block devices like /dev/sda3.  You
can read byte number 9986351 of /dev/sda3 and see what it is.  For
this, you need read permission on the /dev/sda3 file.

Those are simplistic layers, and not often used.  Pretty much the only
time you would ever read from one of those devices is to retrieve the
partition table from the disk, or to see what kind of file system is on
a given partition.  Lower level tools like mkfs and fsck and fdisk and
lsblk handle these details.

Things become much more interesting when we move up to the file system
layer.

The first thing to know about file systems is that they have to be
"mounted" in order to work.  The word "mount" comes from old tape drive
technology (reel to reel), when operators would be requested to mount
a tape, which is a physical act not dissimilar to hanging a picture on
a wall.  It has been adopted for file systems, even though there isn't
a physical movement of objects.

In order to mount a file system, you need to know which disk or partition
the file system is stored on, and what directory you want to attach it to.
You also have to be root, because this is a potentially VERY intrusive
thing to do.  If an ordinary user could mount a file system on /bin then
he could easily take over the whole system, because users would be
executing HIS version of /bin/ls and so on.

Typically the directory where you mount a file system is just an empty
stub.  But it doesn't have to be.  Let's say you have a single file
system (/) mounted currently, and it has a directory called "home" in
it.  Now let's say you've got some files in this directory.  If you mount
/dev/sda3 on /home then the contents of /dev/sda3's file system become
visible inside /home.  The files that you saw in /home BEFORE the mount
are hidden.  They're still in the / file system but you can't see them
or interact with them.

The second thing you need to know about file systems is that they
have their own metadata.  File ownerships, permissions, and so on are
stored within the inodes (index nodes) of the file system.  When you
mount the file system, you see only the files and the metadata from
the mounted file system.  The metadata of the directory that you mounted
it on is no longer relevant.  The metadata of the block device that
stores the file system is also irrelevant.

Before mounting:
drwxr-xr-x 4 john doe 4096 Aug 22 11:41 /home

After mounting:
drwxr-xr-x 4 root root 4096 Sep 22 11:41 /home

Block device:
brw-rw 1 root disk 8, 3 Nov  1 09:39 /dev/sda3

The group "disk" may have write access to /dev/sda3, but that doesn't
let them write to /home.  The permissions of /dev/sda3 are not relevant
when operating 

Re: Connexion internet qui lâche avec Postfix

[Alain Rpnpif]

Le 10 novembre 2016, Daniel Caillibaud a écrit :

> Il faut donc regarder du coté de ton serveur dns, et je t'encourage à 
> installer un résolveur
> local (unbound par ex), autrement plus efficace que le dns de ta box (surtout 
> si son nom
> commence par live, pour moi leur dns est simplement inutilisable, même pour 
> un usage
> personnel).

+1 !
Je l'ai fait et je n'ai plus aucun des problèmes de DNS qui arrivaient
deux ou trois fois par mois.

De plus,cela donne la liberté de choisir son relais.
Par exemple, une petite Raspberry Pi ou équivalent sous Debian ou
Raspbian dans un coin, ça dépanne très bien.
Au pire un serveur DNS sur le poste de travail s'il est seul sur le
réseau.

-- 
Alain Rpnpif

Re: xorriso: listing files+offsets in an ISO9660 image w/o RockRidge

[Brian]

On Thu 10 Nov 2016 at 15:21:42 +0100, Thomas Schmitt wrote:

> Hi,
> 
> two hours ago, i sent the mail below as reply to
>   https://lists.debian.org/debian-user/2016/11/msg00355.html
> Subject line was:
>   LDO_SUBSCRIBER, was Re: xorriso: listing files+offsets in an ISO9660 image 
> w/o RockRidge
> Date: Thu, 10 Nov 2016 12:59:10 +0100
> 
> But it did not arrive in my mailbox and does not show up in the archive.

It didn't arive here either.

> So another try. This time with the thread's original subject line.
> 
> 
> 
> Jonathan Dowland wrote:
> > I've never heard of LDO_SUBSCRIBER, but I am subscribed 
> 
> My mails (and those of most other regular posters) have it in their
> X-Spam-Status when they arrive in my mailbox something like:
> 
>   X-Spam-Status: No, score=-16.9 required=4.0 tests=FOURLA,FREEMAIL_FROM,
>   FVGT_m_MULTI_ODD,LDOSUBSCRIBER,LDO_WHITELIST,RCVD_IN_DNSWL_LOW,
>   RCVD_IN_MSPIKE_H2,RCVD_IN_SORBS_SPAM,
>   RP_MATCHES_RCVD autolearn=unavailable
>   autolearn_force=no version=3.4.0
> 
> The word "LDOSUBSCRIBER" seems to be the indication for a sunscribed
> sender.

A reasonable assumption. However, a lack of LDOSUBSCRIBER tells you
nothing about whether the sender is a subscriber to the list or not.

-- 
Brian.

Re: Problem attempting to use xorriso

[tomas]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Thu, Nov 10, 2016 at 02:53:14PM +, Lisi Reisz wrote:
> On Thursday 10 November 2016 10:53:47 Richard Owlett wrote:
> > On 11/9/2016 5:16 PM, Lisi Reisz wrote:
> > > On Sunday 06 November 2016 16:47:00 Richard Owlett wrote:
> > >> [snip]
> > >> Based on responses to previous posts titled "Trivial script will
> > >> NOT execute" and "Permissions for an entire PARTITION" I have
> > >> multiple problems understanding Linux file systems generally.
> > >
> > > I imagine you have seen this lot - especially the top three??
> > > https://www.google.co.uk/search?q=basic+debian+file+system=basic+debia
> > >n+file+system=chrome..69i57.7617j0j7=chrome=UTF-8
> > >
> > > Lisi
> >
> > Yes, but not in the context of a sub-project from last few days.
> > I suspect what I aiming at might look like - the groups and
> > permission bits set at time partition created, thus avoiding
> > games with /etc/fstab .
> >
> > richard@jessie-defaults:~$
> > richard@jessie-defaults:~$ ls -l /dev/sd*
> > brw-rw 1 root disk 8,  0 Nov 10 03:35 /dev/sda
> > brw-rw 1 root owl  8,  1 Nov 10 03:35 /dev/sda1
> > brw-rw-r-- 1 root owl  8,  2 Nov 10 03:35 /dev/sda2
> > brw-rw 1 root disk 8,  3 Nov 10 03:35 /dev/sda3
> > brw-rw 1 root disk 8,  5 Nov 10 03:35 /dev/sda5
> > brw-rw 1 root disk 8, 16 Nov 10 04:43 /dev/sdb
> > br--rw-r-- 1 root owl  8, 17 Nov 10 04:43 /dev/sdb1
> > richard@jessie-defaults:~$
> >
> > >> My current homework is to now re-read ~40 posts and a to be
> > >> determined number of referenced links. Keywords will likely
> > >> include path, working directory, inode and mount ;/
> > >>
> > >> --
> > >> If retirement isn't for learning, what use is it.
> 
> Richard - are you clear that the permissions are not for the partitions but 
> for the directories on the mount points on the filing system on which those 
> partitions have been hung??

Now I'm confused: what Richard shows up there are the permissions of the
*device files* in which (presumably, sometimes) some file system might
reside. Those file systems might (or might not) be mounted on some directory
in the file system tree (which we don't see here).

I think I didn't understand you.

Regards
- -- t
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAlgkjjkACgkQBcgs9XrR2kZc3QCdHwipsWGXye5IS2jXoIuaGfGO
nD0AniRApYYpR0N5yrPLIbrODNIUHbND
=U0+T
-END PGP SIGNATURE-

Re: Connexion internet qui lâche avec Postfix

[Eric Degenetais]

> [...] autrement plus efficace que le dns de ta box
> (surtout si son nom
> commence par live, pour moi leur dns est simplement inutilisable, même pour
> un usage
> personnel).

A une époque leur bousin gérait mal le protocole de transition IPV6
(en répondant "hôte inconnu" au lieu de "IPV6 non supporté") si bien
que sous un noyau linux non paramétré avec IPV6 actif, la résolution
de nom tombait en panne ou en marche en fonction des aléas qui
faisaient arriver en premier soit la réponse correcte à la requête de
nom IPV4 soit la f**k you exception en réponse à la requête IPV6.
Je ne suis pas franchement convaincu qu'il ne traîne pas encore ce
type de lézards dans les serveurs DNS intégrés des box...

cordialement

Éric Dégenètais

Re: Problem attempting to use xorriso

[Lisi Reisz]

On Thursday 10 November 2016 10:53:47 Richard Owlett wrote:
> On 11/9/2016 5:16 PM, Lisi Reisz wrote:
> > On Sunday 06 November 2016 16:47:00 Richard Owlett wrote:
> >> [snip]
> >> Based on responses to previous posts titled "Trivial script will
> >> NOT execute" and "Permissions for an entire PARTITION" I have
> >> multiple problems understanding Linux file systems generally.
> >
> > I imagine you have seen this lot - especially the top three??
> > https://www.google.co.uk/search?q=basic+debian+file+system=basic+debia
> >n+file+system=chrome..69i57.7617j0j7=chrome=UTF-8
> >
> > Lisi
>
> Yes, but not in the context of a sub-project from last few days.
> I suspect what I aiming at might look like - the groups and
> permission bits set at time partition created, thus avoiding
> games with /etc/fstab .
>
> richard@jessie-defaults:~$
> richard@jessie-defaults:~$ ls -l /dev/sd*
> brw-rw 1 root disk 8,  0 Nov 10 03:35 /dev/sda
> brw-rw 1 root owl  8,  1 Nov 10 03:35 /dev/sda1
> brw-rw-r-- 1 root owl  8,  2 Nov 10 03:35 /dev/sda2
> brw-rw 1 root disk 8,  3 Nov 10 03:35 /dev/sda3
> brw-rw 1 root disk 8,  5 Nov 10 03:35 /dev/sda5
> brw-rw 1 root disk 8, 16 Nov 10 04:43 /dev/sdb
> br--rw-r-- 1 root owl  8, 17 Nov 10 04:43 /dev/sdb1
> richard@jessie-defaults:~$
>
> >> My current homework is to now re-read ~40 posts and a to be
> >> determined number of referenced links. Keywords will likely
> >> include path, working directory, inode and mount ;/
> >>
> >> --
> >> If retirement isn't for learning, what use is it.

Richard - are you clear that the permissions are not for the partitions but 
for the directories on the mount points on the filing system on which those 
partitions have been hung??  This can be hard to grasp, but it can and does 
sometimes make a difference, e.g. if the same partition or device gets 
mounted somewhere else.

Being slightly older than you, Richard and coming from the pre-electronic 
computer generation, I am hoping to grasp and understand the basic Unix 
filing system finally some time before I keel over.  (I *think* that 
electronic computers are slightly older than you are.) ;-)

Lisi

Re: Problem attempting to use xorriso

[tomas]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Thu, Nov 10, 2016 at 08:27:58AM -0600, Richard Owlett wrote:
> On 11/10/2016 7:58 AM, to...@tuxteam.de wrote:

[...]

> >>I don't understand.
> >
> >Hm. Too concise (both of us ;-)
> >
> >I'll give it a shot. By "you" I meant "user owl, i.e. any program running
> >under that user". Was that the unclear part?
> 
> If not, it was likely related. "owl" was not intended to be a user
> ID, but a group ID.
> That's why in my long winded response I changed "owl" to one of
> "proj1", "proj2", or "proj3" and clairified that I am user "richard"
> of group "richard".

I think I got it. Thanks.

regards
- -- t
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAlgkiEEACgkQBcgs9XrR2kaRwACeJqga5uC/HAUD5aBlEStGhxbC
PrUAnirvzib6abAcQEv1Cigy+QuJGI0Z
=Y/Bu
-END PGP SIGNATURE-

Re: xorriso: listing files+offsets in an ISO9660 image w/o RockRidge

[Jonathan Dowland]

On Thu, Nov 10, 2016 at 03:21:42PM +0100, Thomas Schmitt wrote:
> My mails (and those of most other regular posters) have it in their
> X-Spam-Status when they arrive in my mailbox something like:
...
> The word "LDOSUBSCRIBER" seems to be the indication for a sunscribed
> sender.
...
> My best theory for now is that your @debian.org sender address is processed
> differently from other @domain addresses.

Ah yes, I see. @debian.org is forward-only: it forwards to a private address
of mine, from which I send, although the From: is set to @debian.org (you can
see the semi-private address in my Envelope-From). I'm going to hazard a guess
that the list server's spamassassin is marking mails as LDOSUBSCRIBER if the
envelope-from (rather than From: header) matches an address that is known to be
subscribed (which my semi-private address is not).

-- 
Jonathan Dowland
Please do not CC me, I am subscribed to the list.


signature.asc
Description: Digital signature

Re: WINS - name resolution error

[Alexandre GRIVEAUX]

Hello,

Why did you use WINS instead DNS ?

Are you inside a WINS network ?

Thanks

Le 09/11/2016 à 19:50, Felipe Salvador a écrit :
> Hi,
> starting from 2016-11-07 whit the daily upgrade (detail attached) I
> spot these errors:
>
> ~$ ping google.com
> ping: debian.com: Errore di sistema # literally "System error"
>
> and, in the attempt to download email:
>
> mpop: cannot locate host pop.*.com: File o directory non esistente #
> file or directory not found
>
>
> These errors seems to be related to wins, a workaround I found is to
> remove or move back "wins" in /etc/nsswitch.conf, form:
>
> hosts:  files wins dns mdns4_minimal [NOTFOUND=continue] mdns4
>
> to
>
> hosts:  files dns mdns4_minimal [NOTFOUND=continue] wins mdns4
>
> I have tired, without success, to edit STATUS>ACTION field as follow:
>
> hosts:  files wins [UNAVAIL=continue] dns mdns4_minimal 
> [NOTFOUND=continue] mdns4
>
>
> I would open a bug report but cannot figure out who is the culprit, it must 
> be among the upgraded
> packages, among these I suspect libwbclient0, I've done some tests
> whit strace and ldd, but I'm not sure. 
>
> Regards
>

Re: how to make vlc to default videoplayer in gnome

[Alexandre GRIVEAUX]

Hello,

A easy fix:

Try a right click on the files you want to open, select tab 'open with'
and choose VLC



Le 10/11/2016 à 12:40, Fekete Tamás a écrit :
> Dear all,
>
> I have problems with setting up the default video player program in GNOME.
>
> I tried to vi /etc/gnome/defaults.list as root.
>
> I modified a line first like this:
> video/flv=vlc.Totem
>
> I quit from my gnome session, than started the X again.
>
> The default app still wasn't vlc, so I tried to edit
> /etc/gnome/defaults.list like this:
> video/flv=vlc.Totem.desktop
>
> A repeated the gnome restart procedure, but the default player still
> hasn't change.
>
> Can anyone help me, what is the correct text has to be in
> defaults.list to make vlc to my default player?
> Or is there any other file I have to modify?
>
> I use debian 8.6 amd64 version which is upgraded from debian 8.5
>
> - Tamas Fekete
>

Re: xorriso: listing files+offsets in an ISO9660 image w/o RockRidge

[Thomas Schmitt]

Hi,

two hours ago, i sent the mail below as reply to
  https://lists.debian.org/debian-user/2016/11/msg00355.html
Subject line was:
  LDO_SUBSCRIBER, was Re: xorriso: listing files+offsets in an ISO9660 image 
w/o RockRidge
Date: Thu, 10 Nov 2016 12:59:10 +0100

But it did not arrive in my mailbox and does not show up in the archive.

So another try. This time with the thread's original subject line.



Jonathan Dowland wrote:
> I've never heard of LDO_SUBSCRIBER, but I am subscribed 

My mails (and those of most other regular posters) have it in their
X-Spam-Status when they arrive in my mailbox something like:

  X-Spam-Status: No, score=-16.9 required=4.0 tests=FOURLA,FREEMAIL_FROM,
  FVGT_m_MULTI_ODD,LDOSUBSCRIBER,LDO_WHITELIST,RCVD_IN_DNSWL_LOW,
  RCVD_IN_MSPIKE_H2,RCVD_IN_SORBS_SPAM,
  RP_MATCHES_RCVD autolearn=unavailable
  autolearn_force=no version=3.4.0

The word "LDOSUBSCRIBER" seems to be the indication for a sunscribed
sender.

The headers in mails from you look like:

  X-Spam-Status: No, score=-10.0 required=4.0
  tests=HEADER_FROM_DIFFERENT_DOMAINS,LDO_WHITELIST,PGPSIGNATURE,
  RCVD_IN_DNSWL_NONE autolearn=unavailable autolearn_force=no
  version=3.4.0

My best theory for now is that your @debian.org sender address is processed
differently from other @domain addresses.


> (I put something like that in my signature to make things clear, but
> I guess most people don't get that far)

At least not when technical eagerness has taken over. :))


Have a nice day :)

Thomas

Re: Debian repository: no updates for PygreSQL package

[Greg Wooledge]

On Thu, Nov 10, 2016 at 09:01:22AM +0900, Mark Fletcher wrote:
> Current stable is Debian 8 (Jessie). And it is not likely to pick up new 
> versions either. It became stable a couple of years back (sorry I don't 
> remember exactly when and don't have time to look it up, but you can see 
> on Debian's website).

Remember, remember,
The Fifth of November,
Gunpowder treason and plot;
For I see no reason
Why Gunpowder Treason
Should ever be forgot.

Jessie was frozen on November 5, 2014.  The date is also known as Guy
Fawkes Day in the UK.

Stretch's "transition freeze" was initiated on November 5, 2016.
Or at least it was supposed to have been.

Re: xorriso: listing files+offsets in an ISO9660 image w/o RockRidge

[Thomas Schmitt]

Hi,

i have now uploaded
  http://www.gnu.org/software/xorriso/xorriso-1.4.7.tar.gz
for testing of improved xorriso command -read_fs "norock".


Have a nice day :)

Thomas

Re: Problem attempting to use xorriso

[tomas]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Thu, Nov 10, 2016 at 07:40:06AM -0600, Richard Owlett wrote:
> On 11/10/2016 5:20 AM, to...@tuxteam.de wrote:
> >-BEGIN PGP SIGNED MESSAGE-
> >Hash: SHA1
> >
> >On Thu, Nov 10, 2016 at 04:53:47AM -0600, Richard Owlett wrote:
> >>On 11/9/2016 5:16 PM, Lisi Reisz wrote:
> >>>On Sunday 06 November 2016 16:47:00 Richard Owlett wrote:
> [snip]
> Based on responses to previous posts titled "Trivial script will
> NOT execute" and "Permissions for an entire PARTITION" I have
> multiple problems understanding Linux file systems generally.
> >>>
> >>>I imagine you have seen this lot - especially the top three??
> >>>https://www.google.co.uk/search?q=basic+debian+file+system=basic+debian+file+system=chrome..69i57.7617j0j7=chrome=UTF-8
> >>>
> >>>Lisi
> >>
> >>Yes, but not in the context of a sub-project from last few days.
> >>I suspect what I aiming at might look like - the groups and
> >>permission bits set at time partition created, thus avoiding games
> >>with /etc/fstab .
> >>
> >>richard@jessie-defaults:~$
> >>richard@jessie-defaults:~$ ls -l /dev/sd*
> >>brw-rw 1 root disk 8,  0 Nov 10 03:35 /dev/sda
> >>brw-rw 1 root owl  8,  1 Nov 10 03:35 /dev/sda1
> >>brw-rw-r-- 1 root owl  8,  2 Nov 10 03:35 /dev/sda2
> >>brw-rw 1 root disk 8,  3 Nov 10 03:35 /dev/sda3
> >>brw-rw 1 root disk 8,  5 Nov 10 03:35 /dev/sda5
> >>brw-rw 1 root disk 8, 16 Nov 10 04:43 /dev/sdb
> >>br--rw-r-- 1 root owl  8, 17 Nov 10 04:43 /dev/sdb1
> >
> >Note that with this setting, "you" can thrash whatever is in /dev/sda
> >through /dev/sdb (write access).
> 
> I don't understand.

Hm. Too concise (both of us ;-)

I'll give it a shot. By "you" I meant "user owl, i.e. any program running
under that user". Was that the unclear part?

[...]

> It doesn't "scare" me for a very good reason - the system in
> question has no network capability, let alone internet access. In
> fact the particular laptop had its disk wiped and a fresh install of
> Debian 3 times yesterday.

I know. Just refining some points to keep in mind: not every "malware"
comes "directly" from the Internet. It may be through a malicious
USB stick; it may be that neat Emacs Lisp given to you, it may be
a PostScript file or a PDF, it may be (given suitable vulnerabilities)
a JPEG or a video.

But yeah, I'm all for "keep your eyes open, and whenever you miss
one of your feet, learn from it". I practice that myself :-)

regards
- -- t
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAlgkfOsACgkQBcgs9XrR2kYChACeIqPJ6dJcz2JmCosiF4nnPAP4
YwYAnRLlgs0fs3EKdbMLxgelFviXRv4w
=S+f0
-END PGP SIGNATURE-

Re: Problem attempting to use xorriso

[Richard Owlett]

On 11/10/2016 5:20 AM, to...@tuxteam.de wrote:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Thu, Nov 10, 2016 at 04:53:47AM -0600, Richard Owlett wrote:

On 11/9/2016 5:16 PM, Lisi Reisz wrote:

On Sunday 06 November 2016 16:47:00 Richard Owlett wrote:

[snip]
Based on responses to previous posts titled "Trivial script will
NOT execute" and "Permissions for an entire PARTITION" I have
multiple problems understanding Linux file systems generally.


I imagine you have seen this lot - especially the top three??
https://www.google.co.uk/search?q=basic+debian+file+system=basic+debian+file+system=chrome..69i57.7617j0j7=chrome=UTF-8

Lisi


Yes, but not in the context of a sub-project from last few days.
I suspect what I aiming at might look like - the groups and
permission bits set at time partition created, thus avoiding games
with /etc/fstab .

richard@jessie-defaults:~$
richard@jessie-defaults:~$ ls -l /dev/sd*
brw-rw 1 root disk 8,  0 Nov 10 03:35 /dev/sda
brw-rw 1 root owl  8,  1 Nov 10 03:35 /dev/sda1
brw-rw-r-- 1 root owl  8,  2 Nov 10 03:35 /dev/sda2
brw-rw 1 root disk 8,  3 Nov 10 03:35 /dev/sda3
brw-rw 1 root disk 8,  5 Nov 10 03:35 /dev/sda5
brw-rw 1 root disk 8, 16 Nov 10 04:43 /dev/sdb
br--rw-r-- 1 root owl  8, 17 Nov 10 04:43 /dev/sdb1


Note that with this setting, "you" can thrash whatever is in /dev/sda
through /dev/sdb (write access).


I don't understand.


Besides "everyone" can peek into /dev/sda2 and /dev/sdb1.


That was intentional ;)
The project I have in mind is a very custom repository. The set 
of files on sda2 would be almost final versions for use on my 
local machine. The files on the flash drive would be final 
release for use on someone else's machine.


And by "you" I'm talking about any program running on your behalf,
i.e. an executable attachment to this mail which your mail reader
might let through, or a LaTeX class c'ed off the Interwebs.

This is not to scare you: just to help you tune your awareness
towards such things.


It doesn't "scare" me for a very good reason - the system in 
question has no network capability, let alone internet access. In 
fact the particular laptop had its disk wiped and a fresh install 
of Debian 3 times yesterday.


Also, as this is a publicly readable list, it is *EXTREMELY OK* 
to add warnings.,
I may be a raw newbie to Linux but have had much contact with 
"shoot self in foot" syndrome, both as subject and as rescuer ;/


Your response is encouraging, I am understanding more of how 
Debian reports information, even if I don't know how to put my 
system in the reported state.


Lets analyze the above *FICTITIOUS* system - "Am I interpreting 
each line correctly?"


I see no problem with the lines
   brw-rw 1 root disk 8,  0 Nov 10 03:35 /dev/sda
   brw-rw 1 root disk 8, 16 Nov 10 04:43 /dev/sdb
They are copied from a standard install. /dev/sda is my internal 
hard disk and /dev/sdb is a USB flash drive. They are owned by 
"root" and accessible by members of "disk".


These lines should be harmless
   brw-rw 1 root disk 8,  3 Nov 10 03:35 /dev/sda3
   brw-rw 1 root disk 8,  5 Nov 10 03:35 /dev/sda5
as they are also from defaults ( sda3 has Debian and sda5 is swap)

Now for my strange lines.

brw-rw 1 root proj2 8, 1 Nov 10 03:35 /dev/sda1
My previous use of "owl" as a group designation may have confused 
things.

On my system I am "richard" who is a member of group "richard".
"owl" was chosen as a group designation to avoid any accidental 
name collision.
In actual use there would likely be groups "proj1", "proj2", and 
"proj3" for separate projects. User "richard" would be a member 
of groups "richard" and "proj3" but not of "proj1" or "proj2".


I see no potential problem with this line. User "root" and 
members of "proj2" have read/write permissions. Execute 
permissions would be bogus as these partitions explicitly contain 
only data. No access for others.


As stated above sda2 is world readable as it contains a late 
pre-release copy of my custom repository.

brw-rw-r-- 1 root proj3 8, 2 Nov 10 03:35 /dev/sda2

Similarly for sdb1. Did not give "root" write permission as a 
precaution against accidental corruption as it is a removable 
drive which may be used anywhere. It is not intended to give 
protection from malicious changes.

br--rw-r-- 1 root proj3 8, 17 Nov 10 04:43 /dev/sdb1

These indicate desired results. How much effort required to 
obtain ?


Thank you for your time.












If retirement isn't for learning, what use is it.


:-)

regards

- -- tomás
"I'm a signature virus. Go ahead and copy me into your signature"
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)

iEUEARECAAYFAlgkV/4ACgkQBcgs9XrR2kZQSQCY+9nfiKPCIxbQ7Q2qedmSt1dS
NgCfYroYPuSLFKLe7SlsLN+vMBe1GH8=
=j2Ks
-END PGP SIGNATURE-

Re: Connexion internet qui lâche avec Postfix

[Daniel Caillibaud]

Le 09/11/16 à 22:23, andre_deb...@numericable.fr a écrit :
AF> En espaçant de 0.1 seconde entre chaque envoi de mails (Postfix),
AF> la déconnexion internet n'a plus lieu.
AF> 
AF> Mais cette solution n'explique pas pourquoi si l'espacement de temps
AF> est trop serré, la connexion internet se coupe.

Comme le disait une précédente réponse, c'est pas la connexion qui se coupe 
mais le dns qui ne
répond pas (ou mal).

Il faut donc regarder du coté de ton serveur dns, et je t'encourage à installer 
un résolveur
local (unbound par ex), autrement plus efficace que le dns de ta box (surtout 
si son nom
commence par live, pour moi leur dns est simplement inutilisable, même pour un 
usage
personnel).

Après install de unbound (ou bind9, mais je conseille plutôt unbound en 
resolver), configure
ton réseau pour qu'il utilise 127.0.0.1 (ou l'ip que tu auras mise pour 
unbound) comme serveur
dns (et pas celui que lui indique le dhcp).

-- 
Daniel

Ils m'ont mal sous-estimé !
Georges W. Bush (6/11/2000)

OT squid3+digest_ldap_auth+ldap

[Ariel Alvarez]

hola lista mis disculpas por el OT, tengo actualmente squid3 
autenticando contra ldap mediante el helper basic_ldap_auth eso me 
funciona perfecto, pero tengo entendido que la autenticacion viaja en 
texto plano, alguien me sugirio usar en cambio el helper 
digest_ldap_auth, pero no encuentro documentacion muy clara a fin con el 
tema, alguien tiene esto resuelto o alguna fuente fiable a la que pueda 
recurrir preferiblemente en español mi ingles no es muy bueno.


gracias de antemano por su acostumbrada ayuda.
y mil disculpas por secuestrar un hilo, no me di cuenta.

-
Consejo Nacional de Casas de Cultura
http://www.casasdecultura.cult.cu

Re: how to make vlc to default videoplayer in gnome

[Henning Follmann]

On Thu, Nov 10, 2016 at 12:40:22PM +0100, Fekete Tamás wrote:
> Dear all,
> 
> I have problems with setting up the default video player program in GNOME.
> 
> I tried to vi /etc/gnome/defaults.list as root.
> 
> I modified a line first like this:
> video/flv=vlc.Totem
> 
> I quit from my gnome session, than started the X again.
> 
> The default app still wasn't vlc, so I tried to edit
> /etc/gnome/defaults.list like this:
> video/flv=vlc.Totem.desktop
> 
> A repeated the gnome restart procedure, but the default player still hasn't
> change.
> 
> Can anyone help me, what is the correct text has to be in defaults.list to
> make vlc to my default player?
> Or is there any other file I have to modify?
> 
> I use debian 8.6 amd64 version which is upgraded from debian 8.5
> 
> - Tamas Fekete

In Gnome go to Settings (upper right corner and select the screwdriver &
wrench icon). There you go to Details. Under Default Application set the
application for video.

-H


-- 
Henning Follmann   | hfollm...@itcfollmann.com

Re: xorriso: listing files+offsets in an ISO9660 image w/o RockRidge

[Thomas Schmitt]

Hi,

Jonathan Dowland wrote:
>   4 Application:
>   1 Application:
>   ...
> The first one is completely empty labels. The second is roughly 64
> whitespace characters.

Looks like an interesting collection.
It would be nice if libisofs could exercise with it.

I am in the process of testing a xorriso-1.4.7 snapshot which is supposed
not to read the root node's SUSP entries if -read_fs is set to "norock".
(Actually the snapshot is about a bug in mkisofs emulation.)
Will give you a node when it is uploaded.


I let xorriso put its hallmark into the field "Preparer Identifier".
The description of both fields in ECMA-119 specs does not look like
"Application Identifier" is the right place.


> ...
>   2 Application: [pseudo chinese]
>   ...
> I doubt the label is really in Chinese,

Possibly 2-byte character set UCS-2 / UTF-16.


Have a nice day :)

Thomas

Re: xorriso: listing files+offsets in an ISO9660 image w/o RockRidge

[Jonathan Dowland]

On Thu, Nov 10, 2016 at 11:35:02AM +, Jonathan Dowland wrote:
> I'll try the following command with both my current xorriso version and 1.4.6,
> against all of my currently imported ISOs, and report back what my results
> are:

With 1.3.2, at least, only 20/45 of my ISOs fail; the Application labels for 
them
are

  4 Application:
  1 Application:
  1 Application: EASY CD CREATOR 5.3 (010) COPYRIGHT (C) 1999-2003 ROXIO, 
INC.
  1 Application: Nero - Burning ROM
  2 Application: NERO BURNING ROM
  4 Application: NERO___BURNING_ROM
  1 Application: TOAST ISO 9660 BUILDER COPYRIGHT (C) 1997 ADAPTEC, INC. - 
HAVE A NICE DAY
  2 Application: 
䍄啄䘠䙩汥祳瑥洠䅤慰瑥挠䥮挀

The first one is completely empty labels. The second is roughly 64 whitespace
characters.

That last one, I recognise those ISOs as my very earliest. They were burned by
a friend in around 1998 or 1999, so I don't know exactly what hardware or
software he used but it was definitely a Windows machine. I doubt the label is
really in Chinese, I'd imagine that's probably just the raw bytes being
interpreted in Unicode by my terminal.

The penultimate one was burned using a classic Mac of some sort.

All the Nero ones would have been burned on Windows machines.

Labels extracted with iso-info -i "$ISO"

-- 
Jonathan Dowland
Please do not CC me, I am subscribed to the list.


signature.asc
Description: Digital signature

how to make vlc to default videoplayer in gnome

[Fekete Tamás]

Dear all,

I have problems with setting up the default video player program in GNOME.

I tried to vi /etc/gnome/defaults.list as root.

I modified a line first like this:
video/flv=vlc.Totem

I quit from my gnome session, than started the X again.

The default app still wasn't vlc, so I tried to edit
/etc/gnome/defaults.list like this:
video/flv=vlc.Totem.desktop

A repeated the gnome restart procedure, but the default player still hasn't
change.

Can anyone help me, what is the correct text has to be in defaults.list to
make vlc to my default player?
Or is there any other file I have to modify?

I use debian 8.6 amd64 version which is upgraded from debian 8.5

- Tamas Fekete

Re: xorriso: listing files+offsets in an ISO9660 image w/o RockRidge

[Jonathan Dowland]

On Wed, Nov 09, 2016 at 02:29:25PM +0100, Thomas Schmitt wrote:
> I would be interested to examine such an ISO, if privacy permits.

Thanks for the offer!

Once I've narrowed down which of my ISOs suffer this problem, I'll see
which are not too private, some are basically just "Downloads" folders
from a long time ago, and probably just DOOM PWADs...

-- 
Jonathan Dowland
Please do not CC me, I am subscribed to the list.


signature.asc
Description: Digital signature

Re: xorriso: listing files+offsets in an ISO9660 image w/o RockRidge

[Jonathan Dowland]

Hi Thomas, thanks for replying!

On Wed, Nov 09, 2016 at 02:02:48PM +0100, Thomas Schmitt wrote:
> your mail headers do not contain "LDO_SUBSCRIBER", so i Cc: you.

I've never heard of LDO_SUBSCRIBER, but I am subscribed - no need to CC
me. (I put something like that in my signature to make things clear, but
I guess most people don't get that far)

> Jonathan Dowland wrote:
> It is probably not about the "RR" records of Rock Ridge, but generally
> about the structure of System Use Protocol and its payload Rock Ridge.
> I have to investigate under which conditions this error message is
> emitted.

I see, thanks.

> Option -rockridge controls production of ISOs.
> The command not to use Rock Ridge while reading would be
> 
>   -read_fs norock
> 
> but it was introduced only with xorriso-1.4.2.
> You could try current GNU xorriso tarball
>   https://www.gnu.org/software/xorriso/xorriso-1.4.6.tar.gz

I'll try everything with 1.4.6 (more details on what I will try in the
other replies)

> Can you tell by which program you created the content of the media ?

A mixture - I'm importing home made CD-rs and DVD-Rs, burned by myself and
family and friends over a period of 18 years or so; so lots of different
platforms, and burning software. I've got 45 imported ISOs so far, with
hundreds more to do.
 
I'll try the following command with both my current xorriso version and 1.4.6,
against all of my currently imported ISOs, and report back what my results
are:

xorriso  -indev $ISO  -error_behavior image_loading best_effort
-abort_on NEVER -find . -exec report_lba

I'll also try -norock with 1.4.6  for any images that fail to see if that
makes any difference.


-- 
Jonathan Dowland
Please do not CC me, I am subscribed to the list.


signature.asc
Description: Digital signature

Re: Problem attempting to use xorriso

[tomas]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Thu, Nov 10, 2016 at 04:53:47AM -0600, Richard Owlett wrote:
> On 11/9/2016 5:16 PM, Lisi Reisz wrote:
> >On Sunday 06 November 2016 16:47:00 Richard Owlett wrote:
> >>[snip]
> >>Based on responses to previous posts titled "Trivial script will
> >>NOT execute" and "Permissions for an entire PARTITION" I have
> >>multiple problems understanding Linux file systems generally.
> >
> >I imagine you have seen this lot - especially the top three??
> >https://www.google.co.uk/search?q=basic+debian+file+system=basic+debian+file+system=chrome..69i57.7617j0j7=chrome=UTF-8
> >
> >Lisi
> 
> Yes, but not in the context of a sub-project from last few days.
> I suspect what I aiming at might look like - the groups and
> permission bits set at time partition created, thus avoiding games
> with /etc/fstab .
> 
> richard@jessie-defaults:~$
> richard@jessie-defaults:~$ ls -l /dev/sd*
> brw-rw 1 root disk 8,  0 Nov 10 03:35 /dev/sda
> brw-rw 1 root owl  8,  1 Nov 10 03:35 /dev/sda1
> brw-rw-r-- 1 root owl  8,  2 Nov 10 03:35 /dev/sda2
> brw-rw 1 root disk 8,  3 Nov 10 03:35 /dev/sda3
> brw-rw 1 root disk 8,  5 Nov 10 03:35 /dev/sda5
> brw-rw 1 root disk 8, 16 Nov 10 04:43 /dev/sdb
> br--rw-r-- 1 root owl  8, 17 Nov 10 04:43 /dev/sdb1

Note that with this setting, "you" can thrash whatever is in /dev/sda
through /dev/sdb (write access). Besides "everyone" can peek into
/dev/sda2 and /dev/sdb1.

And by "you" I'm talking about any program running on your behalf,
i.e. an executable attachment to this mail which your mail reader
might let through, or a LaTeX class c'ed off the Interwebs.

This is not to scare you: just to help you tune your awareness
towards such things.

> >>If retirement isn't for learning, what use is it.

:-)

regards

- -- tomás
   "I'm a signature virus. Go ahead and copy me into your signature"
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)

iEUEARECAAYFAlgkV/4ACgkQBcgs9XrR2kZQSQCY+9nfiKPCIxbQ7Q2qedmSt1dS
NgCfYroYPuSLFKLe7SlsLN+vMBe1GH8=
=j2Ks
-END PGP SIGNATURE-

Re: Problem attempting to use xorriso

[Richard Owlett]

On 11/9/2016 5:16 PM, Lisi Reisz wrote:

On Sunday 06 November 2016 16:47:00 Richard Owlett wrote:

[snip]
Based on responses to previous posts titled "Trivial script will
NOT execute" and "Permissions for an entire PARTITION" I have
multiple problems understanding Linux file systems generally.


I imagine you have seen this lot - especially the top three??
https://www.google.co.uk/search?q=basic+debian+file+system=basic+debian+file+system=chrome..69i57.7617j0j7=chrome=UTF-8

Lisi


Yes, but not in the context of a sub-project from last few days.
I suspect what I aiming at might look like - the groups and 
permission bits set at time partition created, thus avoiding 
games with /etc/fstab .


richard@jessie-defaults:~$
richard@jessie-defaults:~$ ls -l /dev/sd*
brw-rw 1 root disk 8,  0 Nov 10 03:35 /dev/sda
brw-rw 1 root owl  8,  1 Nov 10 03:35 /dev/sda1
brw-rw-r-- 1 root owl  8,  2 Nov 10 03:35 /dev/sda2
brw-rw 1 root disk 8,  3 Nov 10 03:35 /dev/sda3
brw-rw 1 root disk 8,  5 Nov 10 03:35 /dev/sda5
brw-rw 1 root disk 8, 16 Nov 10 04:43 /dev/sdb
br--rw-r-- 1 root owl  8, 17 Nov 10 04:43 /dev/sdb1
richard@jessie-defaults:~$









My current homework is to now re-read ~40 posts and a to be
determined number of referenced links. Keywords will likely
include path, working directory, inode and mount ;/

--
If retirement isn't for learning, what use is it.

Re: (deb-cat) Padrins pel tram?

[Leopold Palomo-Avellaneda]

On 10/11/16 10:52, Narcis Garcia wrote:
> Fa molts anys que no creo programari privatiu ni incompatible amb
> GNU/Linux; si hi ha alguna altra cosa publicada amb el mateix nom, no té
> res a veure amb mi.
> No l'he publicat mai, així que l'adjunto.
> 
> Crec que segueix les DFSG perquè és GPL
> https://es.wikipedia.org/wiki/Directrices_de_software_libre_de_Debian
> 
>>>
>>> Quines passes em convé donar per proposar-lo a Debian unstable?
>>>
>> - que compleixi amb dfsg
>> - que funcioni amb una debian també ajuda ...
>> podries passar la url, és que el que he vist només és windows i privatiu

doncs estaria bé publicar-ho en algun lloc tipus github per exemple.
També posar els comentaris del codi en anglès.

Leopold


-- 
--
Linux User 152692 GPG: 05F4A7A949A2D9AA
Catalonia
-
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

Re: (deb-cat) Padrins pel tram?

[Narcis Garcia]

Fa molts anys que no creo programari privatiu ni incompatible amb
GNU/Linux; si hi ha alguna altra cosa publicada amb el mateix nom, no té
res a veure amb mi.
No l'he publicat mai, així que l'adjunto.

Crec que segueix les DFSG perquè és GPL
https://es.wikipedia.org/wiki/Directrices_de_software_libre_de_Debian


__
I'm using this express-made address because personal addresses aren't
masked enough at lists.debian.org archives.
El 09/11/16 a les 09:55, Leopold Palomo-Avellaneda ha escrit:
> On 09/11/16 09:50, Narcis Garcia wrote:
>> Tinc diversos programes que m'agradaria compartir millor, però vull
>> començar per un de senzill:
>>
>> ntfsundelete-tree utilitza ntfsundelete per recuperar, no només fitxers,
>> sinó automàticament tota l'estructura de directoris i col·locació dels
>> fitxers esborrats d'un volum NTFS.
>>
>> Quines passes em convé donar per proposar-lo a Debian unstable?
>>
> - que compleixi amb dfsg
> - que funcioni amb una debian també ajuda ...
> podries passar la url, és que el que he vist només és windows i privatiu
> 
> 
> Leopold
> 


ntfsundelete-tree_1.0.0.tar.bz2
Description: application/bzip

Re: Resolved: sound disappeared

[Darac Marjal]

On Wed, Nov 09, 2016 at 05:08:28PM -0500, Anthony Baldwin wrote:

Still getting messages on this: issue resolve, brethren (and sisters, too!)


I believe the analog to "brethren" is "sistren".



--
For more information, please reread.

Re: parted is ALMOST suitable

[tomas]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Wed, Nov 09, 2016 at 04:56:36PM -0700, Joe Pfeiffer wrote:
> Brian  writes:

[...]

> >> Hopefully. But that's not because bash checks that (as parted is).
> >> It's because the permissions on the device file are set right!
> >
> > udev doesn't come into the picture for removable disks? It did on
> > pre-Jessie.
> 
> What is the relevance of udev here?  Yes, udev sets the permissions, but
> the issue is whether they're right not who sets them.

Exactly.

That was my take, too. It's udev's job to react to events generated by
the kernel and to set up things in user space (perms, symlinks, whatnot)
according to whatever policy the distro and the sysadmin have set up.

That's why the rules in /lib/udev (distribution) and /etc/udev (sysad,
override the distro's) exist. The kernel is no place to have those
rules, it's just the one enforcing them.

Layering, again :-)

- -- t
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAlgkN10ACgkQBcgs9XrR2kbR+gCdEXRyxAM6+Wx/mcZ4FSxf4LMl
T1sAn0yMoDTouLMigQyXHLvUFpP+RCbe
=ijKP
-END PGP SIGNATURE-