Re: question about ls

[Richard Hector]

On 28/09/18 1:14 AM, Greg Wooledge wrote:
> On Thu, Sep 27, 2018 at 07:55:56AM -0500, Kent West wrote:
>> But also note the difference when using the letter "l" vs the numeral "1":
>>
>> westk@westkbox:/opt$ ls -la | wc
>>  7  56 321
>> westk@westkbox:/opt$ ls -1a | wc
>>  6   6  54
> 
> But also note that using ls -l gives a completely wrong answer.
> 
> wooledg:~$ mkdir /tmp/x && cd "$_"
> wooledg:/tmp/x$ touch $'this\nis\none\nfile'
> wooledg:/tmp/x$ ls -l | wc -l
> 5

Eww. Tab completion also gets screwed up by this:

richard@zircon:~/test$ rm 
file  isone   this

.. but you can't actually complete from any of those.

Richard



signature.asc
Description: OpenPGP digital signature

Re: How to react on a factually wrong Debian wiki change ?

[Richard Hector]

On 28/09/18 8:00 AM, Thomas Schmitt wrote:
> Hi,
> 
> Greg Wooledge wrote:
>> In the case of the BurnCd page, I actually *do* think that it would be
>> of general interest to readers to have a paragraph explaining the limits
>> of wodim, and when not to use it.
> 
> Let me try ... hrr-umm ... 
> 
> wodim was cloned from cdrecord in 2006. At that time, cdrecord had few
> clue about DVD burning and hid this behind a 1 GB size limit of the
> free program version. The full size version was not available at all.
> wodim got implanted DVD-related code from an earlier cdrecord clone
> which hacked around the size limitation.
> 
> But still wodim is handling any DVD as if it was a large CD-R.
> This works halfways with DVD-R and, depending the medium state, with
> other media after due rejection of inappropriate SCSI commands by the
> drive.
> But it is awful, specs-wise !
> 
> wodim is factually abandoned by its cloners Joerg Jaspert, Steve McIntyre,
> and Eduard Bloch. Its home page is gone, its change history is gone.
> 
> In contrast to that, the doings of dvd+rw-tools (growisofs) and of libburn
> can be justified by the MMC-5 specs. In case of libburn there is even an
> active upstream developer (myself).
> 
> -
> 
> But who wants to read about 12 year old quarrels between Debian Developers
> and the upstream developer of cdrecord ?
> 
> My way to express the current technical situation was the statement:
> 
>   "wodim should better not be used with DVD or BD media."
> 
> which now became
> 
>   "Some believe it would be better if wodim were not used with DVD or BD
>media. Perhaps so, but there are many variables involved, most
>especially burner types and condition, and media quality.
>'''Burn on one does not necessarily mean readable on another.'''"
> 
> It is not the opinion of "some". It is the opionion of me, the expert (tm).
> 
> And yes, there are ill burners and media which produce poorly readble
> results. But this is _not_ normal. If hardware behaves that way, then
> it is to blame, and not the burn program.
> (Even wodims's failures are repeatable.)

How about something like:

"wodim may sometimes work with DVD or BD media, but the results will not
meet the relevant specifications."

or perhaps s/work/appear to work/

Note: I have no expertise in this area; I'm merely interpreting the
comments above.

Richard



signature.asc
Description: OpenPGP digital signature

Re: Which kernel should I use?

[Dennis Wicks]

Dennis Wicks wrote on 09/27/2018 06:40 PM:
> I notice that there is available two different kernels;
> 
>   linux-image-4.9.0-8-686-pae
> 
> and
> 
>   linux-image-4.9.0-8-rt-686-pae
> 
> I am running on a Pentium 4.
> 
> Which one of these should I be using? And just for
> curiosities sake, why?
> 
> TIA!
> Dennis
> 
> 
>

Thanks guys! Unless RT would give me millisecond response
time on Firefox and Thunderbird it doesn't sound like I need
it. So I will just forget that I ever saw that entry in the
apt list!

Thanks again!
Dennis

Re: Debian 9 no reconoce mousepad notebook toshiba L55-A5278

[Alejandro F. Guzzo]

gracias por responder. ya está fue una tontera mia. la opcion de
activar en el teclado(fn) el mousepad. se ve que viene por defecto
apagada esa funcion en esta notebook.
El jue, 27-09-2018 a las 14:54 +0200, Galvatorix Torixgalva escribió:
> Hola,
> 
> en cuestion de hardware es importante tener en cuenta que no por
> funcionar en windows en debian tambien va a hacerlo.
> 
> No todo el hardware funciona en Debian; pueden existir varios
> motivos:
> - es reciente y aun no tiene soporte
> - hay algun problema con la licencia
> - etc
> 
> Por norma general debian soporta un hardware relativamente reciente,
> tengamos en cuenta que debian esta enfocada a la seguridad y a la
> estabilidad, y eso incluye al hardware.
> 
> Que hacer con esto?. Podrias mirarte el kernel de debian y ver si
> tienes algo que sea compatible (ojo, he dicho compatible). Puede que
> se lo "trague" y lo tome por otro dispositivo y puedas usarlo
> razonablemente bien. Tambien puede ser que encuentres alguno
> compatible, que puede que no funcione como la seda pero es algo.
> 
> En la web del fabricante puede que encuentres algun soporte. Hay
> fabricantes que publican drivers para linux pero te avisan de que no
> dan soporte para linux (a veces solo dan soporte para windows). Te
> diria que tengas mucho cuidado con esta opcion porque puede pasar de
> todo.
> 
> Y por ultimo queda el kernel estable de kernel.org, si quieres probar
> suerte ahi.
> 
> Un saludo
> 

Re: Debian 9 no reconoce mousepad notebook toshiba L55-A5278

[Alejandro F. Guzzo]

la verdad sos un groso y yo un boludo jajaja. es verdad esta notebook
me la dieron en el trabajo y vi sin prestar atencion esa opcion. como
en windows se activa directamente ni me imagine que en debian quedaba
desactivada.
mil gracias a todos por responder.
te debo una crux jaja.

El jue, 27-09-2018 a las 15:07 -0300, CruxoM escribió:
> El 27/9/18 a las 08:58, eduardo gil escribió:
> >   Buenos
> >   dias.hace un mes instale debian 9 en mi pc. Estoy
> >   tratando de poder hacer funcionar el mousepad pero no pude
> >   lograrlo. revise varias paginas con diferentes opciones para
> >   realizar pero no hay caso. aparentemente no reconoce el
> >   dispositivo.en windows anda
> >   perfectamente.les dejo por las dudas la salida de
> >   xinput que es algo que se pide normalmente:
> >   
> > 
> 
> Perdón, lo que voy a decir es muy básico pero por ahí te ayude: Yo
> uso 
> como Notebook un Toshiba Satellite L755. La misma posee un botón que 
> sirve para anular el touchpad (conecta o desconecta el mismo). 
> Verificaste que la tuya no tuviera algo similar ?
> 
> 
> Saludos.
> 
> 
> > -- 
> > CruxoM [a.k.a. Omar Murray]
> > crux@gmail.com
> > JID: c...@jabber.freenet.de
> > ICQ: 711672117
> > http://mysteriouswaystg.blogspot.com
> > 
> > Powered by Antergos Linux - Kernel 4.17.10
> > 
> 
> 

Re: Debian 9 no reconoce mousepad notebook toshiba L55-A5278

[Alejandro F. Guzzo]

cuando hago 
echo $XDG_SESSION_TYPE
sale wayland.

El jue, 27-09-2018 a las 18:49 -0300, Felix Perez escribió:
> Wayland o Xorg

Re: Which kernel should I use?

[Gene Heskett]

On Thursday 27 September 2018 19:40:59 Dennis Wicks wrote:

> I notice that there is available two different kernels;
>
>   linux-image-4.9.0-8-686-pae
>
> and
>
>   linux-image-4.9.0-8-rt-686-pae
>
> I am running on a Pentium 4.
>
> Which one of these should I be using? And just for
> curiosities sake, why?
>
> TIA!
> Dennis

The rt vesion is for apps such as LinuxCNC, where at least millisecond 
IRQ response time can be assured. That may, or may not impinge on other  
services, but as I'm running 5 copies of an older rt without any 
showstoppers I'll not say which would be preferred until we are told 
what your most important app is and expects.

Both of those are built for 32  bit installs, and will run on almost any 
cpu.
-- 
Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page 

Re: Which kernel should I use?

[Dan Ritter]

On Thu, Sep 27, 2018 at 06:40:59PM -0500, Dennis Wicks wrote:
> I notice that there is available two different kernels;
> 
>   linux-image-4.9.0-8-686-pae
> 
> and
> 
>   linux-image-4.9.0-8-rt-686-pae
> 
> I am running on a Pentium 4.
> 
> Which one of these should I be using? And just for
> curiosities sake, why?

"rt" is for realtime.

Do not confuse "realtime" with "performance"; it actually means
that there are guaranteed bounds on certain kernel procedures,
not that everything will be fast.

You don't need realtime unless you are writing software for precisely
timed things on underpowered hardware. Say, running an engine controller.

Realtime will not help with things like audio or video editing.

-dsr-

Which kernel should I use?

[Dennis Wicks]

I notice that there is available two different kernels;

linux-image-4.9.0-8-686-pae

and

linux-image-4.9.0-8-rt-686-pae

I am running on a Pentium 4.

Which one of these should I be using? And just for
curiosities sake, why?

TIA!
Dennis

Re: Scribus has stopped importing PDF files

[rv riveravaldez]

On Tue, Sep 25, 2018 at 5:50 PM, Gary Dale  wrote:
> For the last few days, some Scribus documents I work with have stopped
> accepting PDF files within image frames. Prior to this, they would display a
> preview. Now new image frames that I create show just the file name, but
> some older frames within the document still show the preview.
>
> When I export the document as a PDF, the frames that just display the file
> name export as empty/blank. The older frame that shows a preview causes the
> export to stop with an error saying it was unable to load the image.
>
> I'm not sure if this is related to something in the PDFs or not. However it
> is happening on two documents I am working on.
>

Have you checked there?

https://www.scribus.net/how-to-get-support-or-contact-the-team/

https://bugs.scribus.net/my_view_page.php

Good luck!

Re: Debian 9 no reconoce mousepad notebook toshiba L55-A5278

[Felix Perez]

El jue., 27 de sep. de 2018 a la(s) 07:44, Alejandro F. Guzzo
(guzz...@gmail.com) escribió:
>
> Buenos dias.
> hace un mes instale debian 9 en mi pc. Estoy tratando de poder hacer 
> funcionar el mousepad pero no pude lograrlo. revise varias paginas con 
> diferentes opciones para realizar pero no hay caso. aparentemente no reconoce 
> el dispositivo.
> en windows anda perfectamente.
> les dejo por las dudas la salida de xinput que es algo que se pide 
> normalmente:
>
> alejandro@debian:~$ xinput
> ⎡ Virtual core pointer id=2 [master ointer  (3)]
> ⎜   ↳ Virtual core XTEST pointer   id=4 [slave  pointer  (2)]
> ⎜   ↳ xwayland-pointer:13  id=6 [slave  pointer  (2)]
> ⎜   ↳ xwayland-relative-pointer:13 id=7 [slave  pointer  (2)]
> ⎣ Virtual core keyboardid=3 [master keyboard (2)]
> ↳ Virtual core XTEST keyboard  id=5 [slave  keyboard (3)]
> ↳ xwayland-keyboard:13 id=8 [slave  keyboard (3)]
>
> si alguien puede darme una mano se lo agradezco mucho.
>
>
Wayland o Xorg?

-- 
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: Relayer les alertes de sites distants

[Pierre L.]

Salut,

oui comme l'écrit David,
perso dans un script .sh, je mets à la fin la commande décrite pour
faire envoyer un sms sur le portable.

Du fait, les scripts ressemblent à :
#!/bin/bash
commande_personnalisée(ensuite je passe à la ligne)
curl
"https://smsapi.free-mobile.fr/sendmsg?user=000=000=;
exit 0




Le 22/09/2018 à 15:45, G2PC a écrit :
> Émettre un SMS, ce serait possible ?
> Si quelqu'un utilise cette solution, comment est t'elle mise en place ?
>
> Zer00CooL
>




signature.asc
Description: OpenPGP digital signature

Re: modifier une image iso

[Hugues MORIN]

Salut


Merci Bernard, Merci deTheGeek pour vos reponses

J'ai pour l'instant pas trop le temps de me lancer la dedans, je me garde
ca pour cet hiver au coin du feu ;-)

ca va deja me permettre de faire quelques recherches et si vraiment je
trouve pas certaines solutions, je posterai sur la liste.
Comme ca tout le monde en profite.


Cordialement
Hugues

Le 25 septembre 2018 à 16:32, Bernard Schoenacker <
bernard.schoenac...@free.fr> a écrit :

>
> - Mail original -
>
> > De: "Hugues MORIN" 
> > À: "Liste Debian" 
> > Envoyé: Mardi 25 Septembre 2018 14:03:34
> > Objet: Re: modifier une image iso
>
> > Salut a tous
>
> > Je suis un peu hors sujet mais comme bernard j ai un Asus T100TAF qui
> > traine dans un coin avec W8 dessus et je confirme ca rame
> > grave
>
> > Ca fait quelques temps que je me dis que j installerai bien une
> > debian (ou unbutu) dessus.
>
> > Est ce que vous auriez sous la main des liens avec des infos et des
> > conseils pour le faire?
>
> > Cordialement
> > Hugues
>
> bonjour,
>
> j'ai connecté la bête en ethernet pour pouvoir faire les manips ...
>
> https://www.amazon.fr/Syncwire-Adaptateur-Ethernet-
> Gigabit-Windows/dp/B074CDL78M/
>
> et j'ai pris un hub usb pour pouvoir brancher quelques accessoires
> supplémentaires
> https://www.amazon.fr/CSL-ordinateurs-Ultrabooks-
> lalimentation-électrique/dp/B01HGA9TG2/
>
>
> je ne fait aucune objection si tu veut en discuter de vive voix
>
> merci
>
> slt
> bernard
>

Re: How to react on a factually wrong Debian wiki change ?

[Brian]

On Thu 27 Sep 2018 at 12:07:02 -0400, Greg Wooledge wrote:

> On Thu, Sep 27, 2018 at 05:59:42PM +0200, Thomas Schmitt wrote:
> > Alternatively:
> > - Does the wiki have means to discuss facts or to leave messages
> >   to other editors why a particular change was undone ?
> 
> The "Comment" box on the edit page is the obvious place to state your
> reason for reverting someone else's change.  If you need more space than

The "Comment" box is probably the only option. Neither StephenKeeling
nor ThomasSchmitt are contactable by email from the "Info" section. But
a complete reversion of the addition isn't necessarily the way to go.
(See below).

> the wiki revision comment box provides (I don't know how many characters
> that is in moinmoin off hand, but I think it's a few hundred), then it
> becomes more of an issue.  Moinmoin doesn't maintain a parallel "Talk"
> page namespace.  You can put your explanation directly onto the page
> itself, if you think it will be of general interest.

I've seen this done; I do not think wiki pages on technical topics are
the place for advocacy. 

> In the case of the BurnCd page, I actually *do* think that it would be
> of general interest to readers to have a paragraph explaining the limits
> of wodim, and when not to use it.  As well as the other tools, if they
> have important restrictions and limits.

Agreed.

"wodim should better not be used with DVD or BD media."

Perhaps a rewording:

 There is (strong? extensive?) evidence that wodim should not be used
 with DVD or BD media. However, the many variables involved, especially
 burner types and media type and quality, could result a successful
 burn.

-- 
Brian.

Re: How to react on a factually wrong Debian wiki change ?

[Thomas Schmitt]

Hi,

Greg Wooledge wrote:
> In the case of the BurnCd page, I actually *do* think that it would be
> of general interest to readers to have a paragraph explaining the limits
> of wodim, and when not to use it.

Let me try ... hrr-umm ... 

wodim was cloned from cdrecord in 2006. At that time, cdrecord had few
clue about DVD burning and hid this behind a 1 GB size limit of the
free program version. The full size version was not available at all.
wodim got implanted DVD-related code from an earlier cdrecord clone
which hacked around the size limitation.

But still wodim is handling any DVD as if it was a large CD-R.
This works halfways with DVD-R and, depending the medium state, with
other media after due rejection of inappropriate SCSI commands by the
drive.
But it is awful, specs-wise !

wodim is factually abandoned by its cloners Joerg Jaspert, Steve McIntyre,
and Eduard Bloch. Its home page is gone, its change history is gone.

In contrast to that, the doings of dvd+rw-tools (growisofs) and of libburn
can be justified by the MMC-5 specs. In case of libburn there is even an
active upstream developer (myself).

-

But who wants to read about 12 year old quarrels between Debian Developers
and the upstream developer of cdrecord ?

My way to express the current technical situation was the statement:

  "wodim should better not be used with DVD or BD media."

which now became

  "Some believe it would be better if wodim were not used with DVD or BD
   media. Perhaps so, but there are many variables involved, most
   especially burner types and condition, and media quality.
   '''Burn on one does not necessarily mean readable on another.'''"

It is not the opinion of "some". It is the opionion of me, the expert (tm).

And yes, there are ill burners and media which produce poorly readble
results. But this is _not_ normal. If hardware behaves that way, then
it is to blame, and not the burn program.
(Even wodims's failures are repeatable.)


Have a nice day :)

Thomas

Re: Debian 9 no reconoce mousepad notebook toshiba L55-A5278

[CruxoM]

El 27/9/18 a las 08:58, eduardo gil escribió:

  Buenos
  dias.hace un mes instale debian 9 en mi pc. Estoy
  tratando de poder hacer funcionar el mousepad pero no pude
  lograrlo. revise varias paginas con diferentes opciones para
  realizar pero no hay caso. aparentemente no reconoce el
  dispositivo.en windows anda
  perfectamente.les dejo por las dudas la salida de
  xinput que es algo que se pide normalmente:
  

Perdón, lo que voy a decir es muy básico pero por ahí te ayude: Yo uso 
como Notebook un Toshiba Satellite L755. La misma posee un botón que 
sirve para anular el touchpad (conecta o desconecta el mismo). 
Verificaste que la tuya no tuviera algo similar ?



Saludos.



--
CruxoM [a.k.a. Omar Murray]
crux@gmail.com
JID: c...@jabber.freenet.de
ICQ: 711672117
http://mysteriouswaystg.blogspot.com

Powered by Antergos Linux - Kernel 4.17.10

offre d'emploi sur toulouse et bordeaux

[Bernard Schoenacker]

bonjour,

"kernel panic" chez free pour Toulouse ...

merci
slt
bernard

- Mail transféré -

> À: linux...@culte.org
> Envoyé: Jeudi 27 Septembre 2018 19:33:05
> Objet: [Linux-31] offre d'emploi
> 
> Bonsoir,
> 
> j'ai eu cette après-midi une longue conversation avec une responsable
> de
> Free qui avait l'air de très bien connaître son sujet.
> 
> le principal de la conversation venait d'une panne de l'équipement
> Free
> au DSLAM (freebox en étape 2 depuis bientôt deux mois, défaut
> identifié
> chez Free)
> 
> ce qui peut vous intéresser c'est qu'il apparaît que Free n'arrive
> pas à
> recruter suffisamment...
> 
> Il s'agit de postes de technicien de niveau 3 (dans leur
> nomenclature),
> appelés à se déplacer dans une grande région. L'appel venait de
> Bordeaux
> et concernait Toulouse, on voit donc le périmètre.  Le recrutement
> serait de l'ordre de 50 par an.
> 
> Ils recrutent, mais les recrutés ne restent pas. Il ne semble pas que
> le
> salaire soit en cause, par contre les horaires de travail - j'imagine
> toujours sur les routes, astreintes, amplitude d'horaires importante
> -
> sont dissuasif
> 
> pourtant il me semble que le travail est plus intéressant que d'être
> derrière un bureau, et qu'on pas son patron sur le dos toute la
> journée :-)
> 
> moi j'ai passé l'âge, mais si vous êtes intéressés ou connaissez
> quelqu'un d'intéressé...
> 
> actuellement le délai de dépannage est de deux mois (avec un peu de
> chance je n'en ai plus pour longtemps, ca a démarré le 2 Août :-)
> 
> jdd
> NB: on m'a promis un dédommagement très substantiel
> 
> --
> http://dodin.org
> 

Re: How to react on a factually wrong Debian wiki change ?

[Greg Wooledge]

On Thu, Sep 27, 2018 at 05:59:42PM +0200, Thomas Schmitt wrote:
> Alternatively:
> - Does the wiki have means to discuss facts or to leave messages
>   to other editors why a particular change was undone ?

The "Comment" box on the edit page is the obvious place to state your
reason for reverting someone else's change.  If you need more space than
the wiki revision comment box provides (I don't know how many characters
that is in moinmoin off hand, but I think it's a few hundred), then it
becomes more of an issue.  Moinmoin doesn't maintain a parallel "Talk"
page namespace.  You can put your explanation directly onto the page
itself, if you think it will be of general interest.

In the case of the BurnCd page, I actually *do* think that it would be
of general interest to readers to have a paragraph explaining the limits
of wodim, and when not to use it.  As well as the other tools, if they
have important restrictions and limits.

How to react on a factually wrong Debian wiki change ?

[Thomas Schmitt]

Hi,

is perhaps the Debian wiki user StephenKeeling subscribed here ?
We need to discuss the recent wiki change
  https://wiki.debian.org/BurnCd?action=diff=30=31

Alternatively:
- Does the wiki have means to contact a particular Debian wiki user ?
- Does the wiki have means to discuss facts or to leave messages
  to other editors why a particular change was undone ?

If Steve McIntyre or Joerg Jaspert, the DDs involved with wodim, are
reading this: Could you please confirm this statement of mine ?
  "wodim should better not be used with DVD or BD media."


Have a nice day :)

Thomas

Re: Decrypting LUKS from initramfs; was: Re: ext2 for /boot ???

[deloptes]

Andrew McGlashan wrote:

> The biggest weakness with the Dropbear setup is that the initramfs is
> stored on an unencrypted partition (no matter which file system is
> used).  That means that someone with physical access can rebuild the
> initramfs and include their own key as well as other stuff to
> compromise the security of the server.
> 
Exactly what I was saying

> Aside from the fact that the IME is suspect, it would be great if grub
> can be, somehow, given a method that allows for full disk encryption
> which will include everything in /boot -- especially initramfs.
> 

but it would also mean that it should be accessible over the internet,
because I do not see any other way to reach the server and decrypt.


> Even so, then grub might have another attack vector of itself.  But it
> would at least allow for encrypted /boot ...

Well but again we shift from the boot partition to grub - hense if
probability that one has physical access to the server can be ignored,
dropbear is still practical solution.

regards

Re: question about ls

[Greg Wooledge]

On Thu, Sep 27, 2018 at 10:57:56AM -0400, Gene Heskett wrote:
> On Thursday 27 September 2018 08:31:27 Greg Wooledge wrote:
> 
> > On Tue, Sep 25, 2018 at 10:27:03PM +, Long Wind wrote:
> > > can ls show number of items in a folder?Thanks!
> >
> > https://mywiki.wooledge.org/BashFAQ/004
> 
> And finally, an "ls -l|wc -l" from the cli gives the answer to the 
> question asked.

The question that was asked was a yes-or-no question.  And the answer to
it is "no".  However, some people will not perceive "no" to be a USEFUL
answer, so I provided an answer with much more depth.

"ls -l|wc -l" gives you the number of newlines contained in a stream
generated by printing the names of SOME of the files in the current
working directory.

It omits all of the filenames that begin with a period.

It includes all of the newlines that are contained within filenames, and
thus gives an inaccurate count if any of the filenames contain newlines.

Since this is a Debian mailing list, I won't attempt to go into the
behaviors of ls on other Unix-based systems.  The two problems already
mentioned should suffice for this list.

Re: question about ls

[Michael Stone]

On Thu, Sep 27, 2018 at 09:59:58AM -0400, Greg Wooledge wrote:

All of the above give the wrong answers when filenames contain newlines.
Any solution that involves printing the filenames to a stream and then
trying to parse that stream to guess how many filenames are in the stream
is a non-starter -- unless of course the stream uses NUL delimiters
instead of newlines.

Sadly, the GNU coreutils maintainers have rejected every request, even
requests with patches attached, to add a --null option to ls.  So,
ls is not suited to this task.


Correct, find would be a better choice for programmatic use. E.g., 
something like 
find . -mindepth 1 -maxdepth 1 -printf '\n' | wc -l


ls should be considered a user interface, not an API. If ls were 
modified sufficiently to provide a rigorous programatic interface, it 
would basically become a very non-portable reimplementation of find.


Mike Stone

Re: question about ls

[Gene Heskett]

On Thursday 27 September 2018 08:31:27 Greg Wooledge wrote:

> On Tue, Sep 25, 2018 at 10:27:03PM +, Long Wind wrote:
> > can ls show number of items in a folder?Thanks!
>
> https://mywiki.wooledge.org/BashFAQ/004

And finally, an "ls -l|wc -l" from the cli gives the answer to the 
question asked. Change the -l to -lR if there are subdirs in that 
directory. Or if you want to know how many .jpg pix, use 
"ls -l *.jpg|wc -l".  The list goes on

The wiki is educational about how to make bash dance to your tune, but 
for this I'd druther use its default behavior.

bash can be and is a very powerfull scripting language, I've ported 
nearly everything I ever wrote in ARrexx, the universal do anything 
language for the Amiga from 25 years ago, to bash, and they've worked at 
least as good as on the Amiga.

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

Re: question about ls

[David Wright]

On Thu 27 Sep 2018 at 09:59:58 (-0400), Greg Wooledge wrote:
> On Thu, Sep 27, 2018 at 08:53:28AM -0500, David Wright wrote:
> > On Thu 27 Sep 2018 at 07:55:56 (-0500), Kent West wrote:
> > > westk@westkbox:/opt$ ls -la | wc
> > >  7  56 321
> > > westk@westkbox:/opt$ ls -1a | wc
> > >  6   6  54
> > 
> > But do use 1A, not 1a, if you want to know how many items are
> > in a folder, otherwise . and .. will be included in the count.
> 
> All of the above give the wrong answers when filenames contain newlines.
> Any solution that involves printing the filenames to a stream and then
> trying to parse that stream to guess how many filenames are in the stream
> is a non-starter -- unless of course the stream uses NUL delimiters
> instead of newlines.
> 
> Sadly, the GNU coreutils maintainers have rejected every request, even
> requests with patches attached, to add a --null option to ls.  So,
> ls is not suited to this task.

Sure, your FAQ is an invaluable resource for scripting, especially in
a "hostile" environment. But I think one also needs to be aware of
practical commands for use at the commandline in a benign environment.
Knowing which technique is appropriate comes with experience.

One has to be aware of the limitations of all the tools one uses.
Just as ls has weaknesses, so does wc if misused. Most people assume
that -l counts the lines in a file, but actually it counts the
newlines, which matters for the last line.

But here's another plug, and there are lots more goodies there too:

https://mywiki.wooledge.org/BashFAQ/004

Cheers,
David.

Re: question about ls

[Greg Wooledge]

On Thu, Sep 27, 2018 at 08:53:28AM -0500, David Wright wrote:
> On Thu 27 Sep 2018 at 07:55:56 (-0500), Kent West wrote:
> > westk@westkbox:/opt$ ls -la | wc
> >  7  56 321
> > westk@westkbox:/opt$ ls -1a | wc
> >  6   6  54
> 
> But do use 1A, not 1a, if you want to know how many items are
> in a folder, otherwise . and .. will be included in the count.

All of the above give the wrong answers when filenames contain newlines.
Any solution that involves printing the filenames to a stream and then
trying to parse that stream to guess how many filenames are in the stream
is a non-starter -- unless of course the stream uses NUL delimiters
instead of newlines.

Sadly, the GNU coreutils maintainers have rejected every request, even
requests with patches attached, to add a --null option to ls.  So,
ls is not suited to this task.

Re: question about ls

[David Wright]

On Thu 27 Sep 2018 at 07:55:56 (-0500), Kent West wrote:
> On Tue, Sep 25, 2018 at 6:14 PM Ben Caradoc-Davies  wrote:
> 
> > On 26/09/2018 10:55, Long Wind wrote:
> > > sorry! you're right.
> > > after checking ls manual, i find ls has option -1
> >
> > Note also that ls will behave like it has the "-1" option if its output
> > is piped to another command, even without this option. I like to use the
> > "-1" option even in this case because it is what I mean (counting
> > entries one per line).
> >
> >
> But also note the difference when using the letter "l" vs the numeral "1":
> 
> westk@westkbox:/opt$ ls -la | wc
>  7  56 321
> westk@westkbox:/opt$ ls -1a | wc
>  6   6  54
> 
> The difference is that the letter includes the total count of blocks used
> at the top of the list (adding one to the count), whereas the numeral does
> not.

But do use 1A, not 1a, if you want to know how many items are
in a folder, otherwise . and .. will be included in the count.

Cheers,
David.

Re: Debian 9 no reconoce mousepad notebook toshiba L55-A5278

[simartiren]

Primero sólo tenía touchpad con Cinnamon, desde hace poco tiempo ha comenzado a 
funcionar en Xfort. Depende de ls interaz gráfica aparentemente.


Enviado desde mi smartphone Samsung Galaxy.
 Mensaje original De: Galvatorix Torixgalva 
 Fecha: 27/9/18  09:54  (GMT-03:00) A: 
debian-user-spanish@lists.debian.org CC: lista-debian 
 Asunto: Re: Debian 9 no reconoce 
mousepad notebook toshiba L55-A5278 
Hola,
en cuestion de hardware es importante tener en cuenta que no por funcionar en 
windows en debian tambien va a hacerlo.
No todo el hardware funciona en Debian; pueden existir varios motivos:- es 
reciente y aun no tiene soporte- hay algun problema con la licencia- etc
Por norma general debian soporta un hardware relativamente reciente, tengamos 
en cuenta que debian esta enfocada a la seguridad y a la estabilidad, y eso 
incluye al hardware.
Que hacer con esto?. Podrias mirarte el kernel de debian y ver si tienes algo 
que sea compatible (ojo, he dicho compatible). Puede que se lo "trague" y lo 
tome por otro dispositivo y puedas usarlo razonablemente bien. Tambien puede 
ser que encuentres alguno compatible, que puede que no funcione como la 
seda pero es algo.
En la web del fabricante puede que encuentres algun soporte. Hay fabricantes 
que publican drivers para linux pero te avisan de que no dan soporte para linux 
(a veces solo dan soporte para windows). Te diria que tengas mucho cuidado con 
esta opcion porque puede pasar de todo.
Y por ultimo queda el kernel estable de kernel.org, si quieres probar suerte 
ahi.
Un saludo

Re: question about ls

[Greg Wooledge]

On Thu, Sep 27, 2018 at 07:55:56AM -0500, Kent West wrote:
> But also note the difference when using the letter "l" vs the numeral "1":
> 
> westk@westkbox:/opt$ ls -la | wc
>  7  56 321
> westk@westkbox:/opt$ ls -1a | wc
>  6   6  54

But also note that using ls -l gives a completely wrong answer.

wooledg:~$ mkdir /tmp/x && cd "$_"
wooledg:/tmp/x$ touch $'this\nis\none\nfile'
wooledg:/tmp/x$ ls -l | wc -l
5

Thus, .

Re: And yet another UEFI/BIOS question: Work on both.

[Pascal Hambourg]

Le 23/09/2018 à 18:18, Patrick Bartek a écrit :

On Sun, 23 Sep 2018 10:58:54 -0400
Wayne Sallee  wrote:


What do you recommend for setting up a system that will boot in
either UEFI or BIOS mode, so if it is moved back and forth between
UEFI and BIOS, it will boot every time?


I recommend you learn how to use Google or DuckDuckGo, etc. searches for
such basic queries.


This is not a basic query. I have spend quite some time doing 
experiments and have not come up with a perfect universal solution yet.


If you want your system to work with old 32-bit CPUs, you must install 
the i386 architecture. After the installation you can add the amd64 
architecture with dpkg and install a 64-bit kernel. Note that a 32-bit 
kernel can work with a 64-bit UEFI firmware but EFI variables will be 
available only with a 64-bit kernel. A 64-bit kernel can work with a 
32-bit UEFI firmware (if the CPU is 64-bit of course) and EFI variables 
will be available.


You must choose the partition table format between GPT and DOS/MBR.
I read that some broken BIOS may not boot a disk with a GPT partition 
table, although I haven't seen any yet.
I also read that some broken UEFI implementations may force boot in 
native EFI mode when a GPT partition table is present, and in 
BIOS/legacy mode when a DOS/MBR partition table is present, although I 
haven't see any either yet.


However I have observed that quite many BIOS or UEFI implementations 
operating in legacy mode won't boot a disk (either GPT or DOS/MBR) if no 
partition in the DOS partition table/protective MBR has the boot flag 
set. But setting the boot flag on the protective GPT partition is 
against the GPT specification, and I have one example of a UEFI 
implementation which will not boot such a disk in native EFI mode.


So I guess you get a better chance with a DOS/MBR partition table. Note 
that this is what the Debian installer/live ISO-hybrid images use.


If you choose GPT anyway, it is recommended to create a 1 MiB 
unformatted "BIOS boot" partition for GRUB BIOS.


Create a 10 to 100 MB EFI system partition formatted as FAT and mount it 
on /boot/efi.


In order to boot either in BIOS or EFI mode, you have to install both 
BIOS and EFI boot loaders. If you choose GRUB for both, the packages are

- grub-pc to install GRUB for PC with BIOS
- grub-efi-amd64 to install GRUB for PC with 64-bit UEFI firmware
- grub-efi-ia32 to install GRUB for PC with 32-bit UEFI firmware

But these packages conflict with one another so are mutually exclusive. 
You could install one and run grub-install, then uninstall it, install 
the next one and run grub-install again and so on. But I suggest to 
install one, say grub-pc, and install grub-efi-{amd64,ia32}-bin instead, 
which do not conflict with each other.


Now you can install the different GRUB boot loaders for each platform :
# BIOS
grub-install --target=i386-pc /dev/sda
# EFI 32 bit
grub-install --target=i386-efi --removable
# EFI 64 bit
grub-install --target=x86_64-efi --removable

These commands work regardless of whether the system was booted in EFI 
or BIOS mode or EFI variables are available.
The --removable option will install the boot loader in the "removable 
device" path /boot/efi/EFI/BOOT/boot{arch}.efi.



The following was the first result in the list of my
search. Total time spent: about 15 seconds.

https://truthseekers.io/everything-you-need-to-know-to-dual-boot-uefi-gpt-bios-mbr-partitions-swap-space-and-more/

Also, read up on "chainloading."


Dual boot and chainloading have nothing to do with Wayne's query.

Re: question about ls

[Kent West]

On Tue, Sep 25, 2018 at 6:14 PM Ben Caradoc-Davies  wrote:

> On 26/09/2018 10:55, Long Wind wrote:
> > sorry! you're right.
> > after checking ls manual, i find ls has option -1
>
> Note also that ls will behave like it has the "-1" option if its output
> is piped to another command, even without this option. I like to use the
> "-1" option even in this case because it is what I mean (counting
> entries one per line).
>
>
But also note the difference when using the letter "l" vs the numeral "1":

westk@westkbox:/opt$ ls -la | wc
 7  56 321
westk@westkbox:/opt$ ls -1a | wc
 6   6  54

The difference is that the letter includes the total count of blocks used
at the top of the list (adding one to the count), whereas the numeral does
not.



-- 
Kent West<")))><
Westing Peacefully - http://kentwest.blogspot.com

Re: Debian 9 no reconoce mousepad notebook toshiba L55-A5278

[Galvatorix Torixgalva]

Hola,

en cuestion de hardware es importante tener en cuenta que no por funcionar
en windows en debian tambien va a hacerlo.

No todo el hardware funciona en Debian; pueden existir varios motivos:
- es reciente y aun no tiene soporte
- hay algun problema con la licencia
- etc

Por norma general debian soporta un hardware relativamente reciente,
tengamos en cuenta que debian esta enfocada a la seguridad y a la
estabilidad, y eso incluye al hardware.

Que hacer con esto?. Podrias mirarte el kernel de debian y ver si tienes
algo que sea compatible (ojo, he dicho compatible). Puede que se lo
"trague" y lo tome por otro dispositivo y puedas usarlo razonablemente
bien. Tambien puede ser que encuentres alguno compatible, que puede que no
funcione como la seda pero es algo.

En la web del fabricante puede que encuentres algun soporte. Hay
fabricantes que publican drivers para linux pero te avisan de que no dan
soporte para linux (a veces solo dan soporte para windows). Te diria que
tengas mucho cuidado con esta opcion porque puede pasar de todo.

Y por ultimo queda el kernel estable de kernel.org, si quieres probar
suerte ahi.

Un saludo

Re: ncurses problem

[Greg Wooledge]

On Wed, Sep 26, 2018 at 10:38:53PM +, Grzesiek Sójka wrote:
> Hi there,
> 
> I compiled following test program:
> ==
> #include 
> #include 
[snip]

> It's supposed to show current window dimension when resizing terminal
> window. Unfortunately, dimensions are not updated and it shows initial
> geometry. Interesting thing is that it works perfectly after "ssh localhost"
> or "su -". I tested on both, sid and stretch. exactly the same result.
> 
> Any ideas??

My first thought is that your shell login profile,

> PS. I use xfce4 and lxdm.

... which is NOT how you normally log in, is turning on bash's
checkwinsize option, which causes bash to set the LINES and COLUMNS
variables upon receipt of a SIGWINCH (a signal that is sent when the
window changes size).

In the absence of that option, those variables might not be set at all,
or might be set to the wrong size, and won't be updated when the window
changes size while sitting in an idle shell.

(What an ncurses program does with this signal, I honestly do not know.)

So, just wild-ass guessing here, you might have put the necessaray
"shopt -s checkwinsize" and "export LINES COLUMNS" into ~/.profile
which is only read when you perform a shell login, and NOT when you
perform an lxdm login.  That's why something might "work" when you
first do "ssh localhost" to get a shell login environment.

Re: question about ls

[Greg Wooledge]

On Tue, Sep 25, 2018 at 10:27:03PM +, Long Wind wrote:
> can ls show number of items in a folder?Thanks! 

https://mywiki.wooledge.org/BashFAQ/004

Re: Debian 9 no reconoce mousepad notebook toshiba L55-A5278

[eduardo gil]

A MI me ocurrió una cosa parecida con una HP 1100
En Debian NO funcionaba el touchpad.
Pero con otros Linux Live CD sí lo hacía
Así que instalé primero Ubuntu (un desastre de LENNnt)
Luego instalé Xubuntu y funcionó.

Como para salir de dudas... instalé de nuevo Debian (en ese momento tenía 
tiempo para desperdiciar) y el problema se repitió, instalé XFCE como intefaz 
gráfica y saqué la que venía por defecto en Debian (creo que era la gNOME) y 
resultó que funcionó el touch en Debian

¿Qué tendrá que ver una intefaz gráfica con un touch? NI IDEA y además NO me 
interesa (ya dejé hace tiempo de romperme la cabeza, uso lo que anda y lo que 
no LO DESCARTO)

Bueno... esa ha sido MI experiencia y mi "solución" que bien puede NO ser muy 
técnica que digamos pero es ha sido la más práctica.
Repito: hace tiempo que dejé de hacerme problemas con cosas que fallan, o sea 
NO anda y si luego de probar algunas soluciones éstas no dan resultado, lo 
descarto y uso otra cosa. PUNTO.


El jue 27-sep-18, Alejandro F. Guzzo  escribió:

 Asunto: Debian 9 no reconoce mousepad notebook toshiba L55-A5278
 Para: debian-user-spanish@lists.debian.org
 Fecha: jueves, 27 de septiembre de 2018, 7:44
 
 Buenos
 dias.hace un mes instale debian 9 en mi pc. Estoy
 tratando de poder hacer funcionar el mousepad pero no pude
 lograrlo. revise varias paginas con diferentes opciones para
 realizar pero no hay caso. aparentemente no reconoce el
 dispositivo.en windows anda
 perfectamente.les dejo por las dudas la salida de
 xinput que es algo que se pide normalmente:
 alejandro@debian:~$
 xinput ⎡ Virtual core
 pointerid=2[master
 ointer  (3)]⎜   ↳
 Virtual core XTEST
 pointer    id=4[slave  pointer  (2)]⎜   ↳
 xwayland-pointer:13    id=6[slave  pointer  (2)]⎜  
 ↳
 xwayland-relative-pointer:13   id=7[slave  pointer  (2)]⎣
 Virtual core
 keyboard   id=3[master
 keyboard (2)]↳ Virtual
 core XTEST
 keyboard   id=5[slave  keyboard
 (3)]↳
 xwayland-keyboard:13   id=8[slave  keyboard
 (3)]
 si alguien puede darme una mano se lo agradezco
 mucho.
 
 

Re: Why does Debian allow all incoming traffic by default

[Pascal Hambourg]

Le 23/09/2018 à 10:41, Joe a écrit :

On Sat, 22 Sep 2018 17:07:59 +0200
Pascal Hambourg  wrote:


PPTP does require specific NAT support for the GRE protocol.
Use case : two clients of the same PPTP server share the same public
IP address.


It doesn't work, see below.


It can work if and only if the NAT device has specific support for PPTP.
The GRE header used by PPTP contains a "Call ID" field which acts as a 
sort of destination port and can be used to associate the packet with an 
existing PPTP session.



The second
person to make the attempt could not make contact until about two
minutes after the first had disconnected.


Yes, until the GRE mapping created for the previous session has expired.


The server sends a GRE packet to the public IP address. How does the
NAT device know which client the packet must be forwarded to ?


Because NAT requires the maintenance of a table of connections, with
source and destination IP addresses, which is exactly what is required
by both stateful firewalling and connection tracking. In this case, for
the first GRE packet, it is connection tracking which uses the table
data to route the packet to the machine with an existing TCP/1723
connection from the same source address.


If the NAT layer has no specific support for PPTP, there is no 
relationship between the TCP control connection and the GRE streams. If 
the first GRE packet is sent by the PPTP server, it is just discarded by 
the NAT box because no mapping exists yet. The first GRE packet sent by 
a private client creates a NAT mapping which is used to forward 
subsequent packets sent by the server.



What you can't do with PPTP is make multiple connections between the
same two NAT machines, for this same reason, because GRE doesn't have
the means for being tied to one particular TCP/1723 path. It doesn't
carry the same meta information as does the TCP protocol.


Actually it does, as I mentioned above. When establishing a session over 
the TCP control connection, the client and server exchange "Call ID" 
numbers which are present in the header of the GRE packets sent within 
that session. The Call ID field can be used by NAT as a destination port.


AFAIK, Netfilter PPTP/GRE conntrack and NAT helper modules use it.

Re: Sistema de archivos debian 9

[Antonio Trujillo Carmona]

El 17/09/18 a las 18:35, Gonzalo Garcia Dominguez escribió:
> Buenas tardes a todos,
>
> Estoy tratando de montar un sistema de archivos replicado entre varios
> nodos con debían 9.
>
> No encuentro una solución que se adapte a mis necesidades, que
> realmente son que sean todos los nodos master-master, y repliquen en
> los demás nodos en el menor tiempo posible.
>
> Podéis aconsejarme que puedo implementar?
> Muchas gracias de antemano, soy novato en la lista, si realice alguna
> operación que no es correcta díganmelo:)
> Saludos

Creo que lo que mejor te viene es drbd + o2cfs.

Si no necesitas nada mas con eso tienes bastante, si quieres volúmenes
lógicos añade pacemaker, corosync y clvm.

Hay mucha documentación en internet, yo no he usado drbd por que en el
trabajo tenemos cabina de discos, pero si que tengo discos compartidos
en alta disponibilidad, activos/activos con ocfs2.





signature.asc
Description: OpenPGP digital signature

Debian 9 no reconoce mousepad notebook toshiba L55-A5278

[Alejandro F. Guzzo]

Buenos dias.hace un mes instale debian 9 en mi pc. Estoy tratando de
poder hacer funcionar el mousepad pero no pude lograrlo. revise varias
paginas con diferentes opciones para realizar pero no hay caso.
aparentemente no reconoce el dispositivo.en windows anda
perfectamente.les dejo por las dudas la salida de xinput que es algo
que se pide normalmente:
alejandro@debian:~$ xinput ⎡ Virtual core pointer   
id=2[master ointer  (3)]⎜   ↳ Virtual core XTEST
pointer     id=4[slave  pointer  (2)]⎜   ↳
xwayland-pointer:13 id=6[slave  poi
nter  (2)]⎜   ↳ xwayland-relative-pointer:13id=7
[slave  pointer  (2)]⎣ Virtual core keyboard    
id=3[master keyboard (2)]↳ Virtual core XTEST
keyboard    id=5[slave  keyboard (3)]↳
xwayland-keyboard:13id=8[slave  key
board (3)]
si alguien puede darme una mano se lo agradezco mucho.

UPDATE - was [Re: Distinguish instances of GUI file manager by color]

[Richard Owlett]

On 09/26/2018 04:52 AM, Richard Owlett wrote:
I'm setting up a new machine and copying files from the old machine's 
home directory. At the same time I'm creating a new directory structure 
to better match how I work.


I found it expedient to have at least three instances of the file 
manager open - [one for source directory and at least two for 
destination (sub)directories].


Suggestions?
Is it even possible?

Brief web search was not encouraging. But my search terms may have been 
the problem. Suggested search terms?


TIA


I asked related questions on a LUG list and a Tcl/Tk group.
Suggestions tended to lead to a two pane file manager.
Having followed multiple chains of links caused me to rethink my work 
flow simplifying use of my current file manager (Caja).


Long term, I'll pursue a two pane solution.
I've installed Krusader and GNOME Commander for testing.

A chain of links led to 'filerunner' 
[https://sourceforge.net/projects/filerunner/] which I downloaded and am 
reading the documentation to chose which options to initially chose.


Usage appears to be intuitive - at least for my work style.
It is intrinsically highly configurable.
It is written in Tcl/Tk allowing/encouraging further customization.

It will likely be my long term solution.

Thanks for all the links.

Re: Decrypting LUKS from initramfs; was: Re: ext2 for /boot ???

[Andrew McGlashan]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256



On 27/09/18 03:17, Jonathan Dowland wrote:
> On Wed, Sep 26, 2018 at 06:14:42PM +0200, deloptes wrote:
>> so how can we do it with initram and without some external key
>> server? Imagine I have only boot not encrypted on the server. I
>> want to boot the machine and get a prompt via SSH or something
>> like SSH, where I can type in the password and decrypt root and
>> all other volumes. I do not want to store password or anything
>> sensitive in the boot directory. I can imagine one time ssh
>> created when you try to login, but it is still not secure
>> enough.
> 
> What you describe is exactly how the dropbear/initramfs
> integration works. The data stored in /boot is the initramfs, and
> within that, the only material you might consider sensitive is an
> SSH server keypair (public) for the SSHD instance in the
> initramfs environment - this does not need to be the same as for
> your running system; and an authorized_keys file, containing your
> SSH *public* key. Are those too sensitive for you?

The biggest weakness with the Dropbear setup is that the initramfs is
stored on an unencrypted partition (no matter which file system is
used).  That means that someone with physical access can rebuild the
initramfs and include their own key as well as other stuff to
compromise the security of the server.

Aside from the fact that the IME is suspect, it would be great if grub
can be, somehow, given a method that allows for full disk encryption
which will include everything in /boot -- especially initramfs.

Even so, then grub might have another attack vector of itself.  But it
would at least allow for encrypted /boot ...

Kind Regards
AndrewM
-BEGIN PGP SIGNATURE-

iHUEAREIAB0WIQTJAoMHtC6YydLfjUOoFmvLt+/i+wUCW6yMrQAKCRCoFmvLt+/i
+xPvAQCW/jz4Iq50mRaz4hJrUWIKqbJ/iUpCCcMXntPfcZDwRwD/SuPsHGGVjMCi
1Vk/BfTPN27cRE3CtHIntxItupUqzJ0=
=7lcL
-END PGP SIGNATURE-

Re: Distinguish instances of GUI file manager by color

[didier gaumet]

Gnome-Commander (packaged in Debian) could be of interest for you: GUI
but two-panel mc-like, several color themes, color set-up, advanced
search and rename tools, etc...
 https://gcmd.github.io/shots.html