Re: Kuren bij starten van Testing

2021-04-01 Thread Geert Stappers
On Thu, Apr 01, 2021 at 10:39:30PM +0200, Sjoerd wrote:
> Geert Stappers:
> > Sjoerd:
> > > Wanneer ik Bullseye (testing) start, dan is er een kans van zo'n 2/3
> > > dat het goed gaat.  Maar in 1/3 van de gevallen verschijnt
> > > onderstaande tekst. Dan druk ik maar op de reset-knop en is er opnieuw
> > > een kans van 2/3 dat het goed gaat.
> > > Enig idee wat er aan de hand is? En of het eenvoudig te verhelpen is?
> > > 
> > > 
> > >   Booting `Debian GNU/Linux'
> > > 
> > > Loading Linux 5.10.0-4-amd64 ...
> > > Loading initial ramdisk ...
> > > mount: mounting /dev on /root/dev failed: No such file or directory
> > > mount: mounting /run on /root/run failed: No such file or directory
> > > run-init: can't execute '/sbin/init': No such file or directory
> > > Target filesystem doesn't have requested /sbin/init.
> > > run-init: can't execute '/sbin/init': No such file or directory
> > > run-init: can't execute '/etc/init': No such file or directory
> > > run-init: can't execute '/bin/init': No such file or directory
> > > run-init: can't execute '/bin/sh': No such file or directory
> > > run-init: can't execute '': No such file or directory
> > > No init found. Try passing init= bootarg.
> > > 
> > > BusyBox v1.30.1 (Debian 1:1.30.1-6+b1) built-in shell (ash)
> > > Enter 'help' for a list of built-in commands.
> > > (initramfs) _
> >
> > Vertel meer over de hardware in kwestie.
> 
> Hier de output van hwinfo, korte versie: https://paste.debian.net/1192040/
 
Een stukje daarvan

disk:
  /dev/sdb ST1000DM003-1ER1
  /dev/sdc Generic STORAGE DEVICE
  /dev/sda Samsung SSD 840

> En als je zin en interesse hebt om naar de complete output van hwinfo te
> kijken:  https://pastebin.com/H1C2TXvA  (230 kB tekst!)
 
Nee, dank je.


> Maar als dit toch een lastige kwestie blijkt te zijn, dan zou ik zeggen:
> laat maar zitten. Het is testing, dus mogelijk herstelt zich dit weer eens.
> En ik heb altijd nog stable om op terug te vallen.

:-)


Mijn inschatting dat de bootdisk niet de bootdisk blijft.
Dat de "/dev/sda" vooraan in het bootprocess
verder in het bootprocess niet meer "/dev/sda" is.

Oplossing daarvoor is iets als "root=/dev/sda2"
te vervangen door "root=UUID=uniek1D"
 

 
Groeten
Geert Stappers
Die graag leert hoe het verder is gegaan
-- 
Silence is hard to parse


signature.asc
Description: PGP signature


Re: Request: A Debian public Wiki repository/bank for complex code lines with examples, scripts, self-explanatory with terminal, otherwise Minimal explanatory texts

2021-04-01 Thread Susmita/Rajib
On Thu, 1 Apr 2021 09:38:07 -0400, rhkra...@gmail.com wrote:
> To: debian-user@lists.debian.org
[...]
> Message-id: <[] 202104010938.07787.rhkra...@gmail.com>
> In-reply-to:
> 
> References:
> 
> 
> 

[...]
>* There are wikis available that you could start making pages for -- one
> might be Greg Wooledge's wiki on bash (with his permission, and if he is
> willing to allow subjects other than bash to be discussed).
>
>Another is my WikiLearn [t]wiki which was / is intended as my learning
> notebook (I have a lot more content offline, which I haven't put online for
> a
> variety of reasons).
>
>It is at https://twiki.org/cgi-bin/view/Wikilearn/WebHome.
[...]

Thank you, Dr./Mr. Kramer, for taking time to post your kind inputs.
To me, the best possible option would be an organisationally hosted
wiki site with strict posting guidelines, and pages as described.

Best



Re: Converting markdown to PDF

2021-04-01 Thread Ryan Nowakowski



On April 1, 2021 4:45:03 PM CDT, Paul M Foster  wrote:
>On Thu, Apr 01, 2021 at 10:46:09PM +0200, Linux-Fan wrote:
>
>> Paul M Foster writes:
>> 
>> > I'm trying to use pandoc to convert markdown files to PDF. But when
>I try,
>> > pandoc dumps out with an error that it needs "pdflatex" or some
>other
>> > similar converter to do its job. No such "pdflatex" package exists
>in the
>> > Buster stable archives. I'm sure something does this, but I don't
>know what
>> > it is. Does anyone else know?
>> 
>> pdflatex is provided by package texlive-latex-base.
>> 
>> Some hints about which packages might be needed can be seen in
>pandoc's
>> "Suggests":
>> 
>> ~$ aptitude show pandoc
>
>[snip]
>
>Thanks. When I used "-t latex" and tried outputting to PDF after
>installing
>some of these dependencies, I did get a PDF. Unfortunately, it looks
>about
>as horrible as most LaTeX docs. I'll keep tweaking it.

I like the markdown -> docbook -> formatting objects(fo) -> PDF pipeline. It 
tends to produce PDF documents that look more "business" and less "academic" 
than the latex pipeline.



Re: Converting markdown to PDF

2021-04-01 Thread David Wright
On Thu 01 Apr 2021 at 17:22:31 (-0400), Paul M Foster wrote:
> On Thu, Apr 01, 2021 at 09:41:30PM +0100, Tixy wrote:
> > On Thu, 2021-04-01 at 16:34 -0400, Paul M Foster wrote:
> > > I'm trying to use pandoc to convert markdown files to PDF. But when I
> > > try,
> > > pandoc dumps out with an error that it needs "pdflatex" or some other
> > > similar converter to do its job. No such "pdflatex" package exists in
> > > the
> > > Buster stable archives. I'm sure something does this, but I don't
> > > know what
> > > it is. Does anyone else know?
> > > 
> > 
> > I just Google "debian pdflatex" and the top hit was Debian's search
> > page...
> > 
> > https://packages.debian.org/search?searchon=contents=pdflatex
> > 
> > I'm sure someone will be along shortly to give an example of how the
> > search can be done from a commandline using Debian's packaging tools or
> > similar... :-)
> 
> Cute but uncalled for. To wit...

In view of what you tried to install, I can only assume that you
didn't actually visit the link, which would give you the name of the
package within the following list:

  You have searched for paths that end with pdflatex in suite buster,
  all sections, and all architectures. Found 8 results.

  File  Packages
  /usr/bin/bg5+pdflatex  latex-cjk-chinese
  /usr/bin/bg5pdflatex   latex-cjk-chinese
  /usr/bin/cef5pdflatex  latex-cjk-chinese
  /usr/bin/cefpdflatex   latex-cjk-chinese
  /usr/bin/cefspdflatex  latex-cjk-chinese
  /usr/bin/gbkpdflatex   latex-cjk-chinese
  /usr/bin/pdflatex  texlive-latex-base   ←
  /usr/bin/sjispdflatex  latex-cjk-japanese

In any case, you might bookmark https://packages.debian.org/,
which gives you the wherewithal to construct your own searches.

> paulf@dudley:~$ uname -a
> Linux dudley 4.19.0-13-amd64 #1 SMP Debian 4.19.160-2 (2020-11-28) x86_64
> GNU/Linux
> paulf@dudley:~$ sudo apt install pdflatex
> Reading package lists... Done
> Building dependency tree   
> Reading state information... Done
> E: Unable to locate package pdflatex

On Thu 01 Apr 2021 at 17:45:03 (-0400), Paul M Foster wrote:
> On Thu, Apr 01, 2021 at 10:46:09PM +0200, Linux-Fan wrote:
> > Paul M Foster writes:
> > 
> > > I'm trying to use pandoc to convert markdown files to PDF. But when I try,
> > > pandoc dumps out with an error that it needs "pdflatex" or some other
> > > similar converter to do its job. No such "pdflatex" package exists in the
> > > Buster stable archives. I'm sure something does this, but I don't know 
> > > what
> > > it is. Does anyone else know?
> > 
> > pdflatex is provided by package texlive-latex-base.
> > 
> > Some hints about which packages might be needed can be seen in pandoc's
> > "Suggests":
> > 
> > ~$ aptitude show pandoc
> 
> [snip]
> 
> Thanks. When I used "-t latex" and tried outputting to PDF after installing
> some of these dependencies, I did get a PDF. Unfortunately, it looks about
> as horrible as most LaTeX docs. I'll keep tweaking it.

I assume that using   -o foo.pdf   doesn't produce what you want, so
is it the LaTeX code that you're tweaking, or the original markdown?

Cheers,
David.



Re: xsane can't see Brother ADS-2700W scanner

2021-04-01 Thread Charlie Gibbs

On 2021-04-01 3:51 a.m., Brian Potkin wrote:


Hello Charlie,

It would appear that you are not subscribed to debian-user. Have you
seen all the replies to your post that await you there?


Yes, I have.  I just haven't had time to act on them.  I did download
a driver from the Brother site but it had no effect.  I suspect there's
something I'll have to do with xsane to get it to find the scanner.
(And then I'll have to go through it again with my wife's Macbook.)
Meanwhile I tried setting it up to use sftp, but I haven't managed
to get the authentication worked out yet.  Oh well, worst case I can
scan to a thumb drive.  It does that well - and fast.


Apologies for the intrusion.


No worries.  Thanks for the note.  I'm hoping to find time this
weekend to try out some of the things that have come through on
the list.  I'll post a summary of my results when I get them.

--
/~\  Charlie Gibbs  |  Microsoft is a dictatorship.
\ /|  Apple is a cult.
 X   I'm really at ac.dekanfrus |  Linux is anarchy.
/ \  if you read it the right way.  |  Pick your poison.



MATE window list

2021-04-01 Thread Glenn Holmer
I switched to MATE w/Compiz (on Bullseye) a few weeks ago and I'm really
liking it. I love the exotic effects, like windows turning into paper
airplanes and flying away when you close them. But I have a problem with
the airplanes: when I hover over an item in the window list (a.k.a. task
bar), I get a thumbnail of the app, and when I mouse away... it turns into
a paper airplane and flies away! Love the airplanes, but that's a bit much.

I know it's MATE and not Compiz that's doing the thumbnails, because in
Compiz Config under Extras, Window Previews are disabled, and if I enable
them, I get *two* thumbnails from the window list. So is there a way to
disable MATE from showing these thumbnails?

It looks like this may have been added in MATE 1.24 (which I'm running),
based on this URL:

https://mate-desktop.org/blog/2020-02-10-mate-1-24-released/

("The *window list* applet now supports window thumbnails on hover.")

-- 
Glenn Holmer (Linux registered user #16682)
"After the vintage season came the aftermath -- and Cenbe."


Re: Converting markdown to PDF

2021-04-01 Thread Paul M Foster
On Thu, Apr 01, 2021 at 10:46:09PM +0200, Linux-Fan wrote:

> Paul M Foster writes:
> 
> > I'm trying to use pandoc to convert markdown files to PDF. But when I try,
> > pandoc dumps out with an error that it needs "pdflatex" or some other
> > similar converter to do its job. No such "pdflatex" package exists in the
> > Buster stable archives. I'm sure something does this, but I don't know what
> > it is. Does anyone else know?
> 
> pdflatex is provided by package texlive-latex-base.
> 
> Some hints about which packages might be needed can be seen in pandoc's
> "Suggests":
> 
> ~$ aptitude show pandoc

[snip]

Thanks. When I used "-t latex" and tried outputting to PDF after installing
some of these dependencies, I did get a PDF. Unfortunately, it looks about
as horrible as most LaTeX docs. I'll keep tweaking it.

Paul

-- 
Paul M. Foster
http://noferblatz.com
http://quillandmouse.com



Re: Converting markdown to PDF

2021-04-01 Thread Paul M Foster
On Thu, Apr 01, 2021 at 05:12:40PM -0400, Celejar wrote:

> On Thu, 01 Apr 2021 21:41:30 +0100
> Tixy  wrote:
> 
> > On Thu, 2021-04-01 at 16:34 -0400, Paul M Foster wrote:
> > > I'm trying to use pandoc to convert markdown files to PDF. But when I
> > > try,
> > > pandoc dumps out with an error that it needs "pdflatex" or some other
> > > similar converter to do its job. No such "pdflatex" package exists in
> > > the
> > > Buster stable archives. I'm sure something does this, but I don't
> > > know what
> > > it is. Does anyone else know?
> > > 
> > 
> > I just Google "debian pdflatex" and the top hit was Debian's search
> > page...
> > 
> > https://packages.debian.org/search?searchon=contents=pdflatex
> > 
> > I'm sure someone will be along shortly to give an example of how the
> > search can be done from a commandline using Debian's packaging tools or
> > similar... :-)
> 
> 'apt-file search pdflatex'
> 
> 'apt-file' is in the 'apt-file' package - it keeps a local database,
> which one updates periodically / occasionally via 'apt-file update'.
> 
> Celejar
> 

Thanks. The actual package is texlive-latex-base to provide pdflatex.
Unfortunately, pandoc still balks, but in a different way. I'll have to do
more research.

Paul


-- 
Paul M. Foster
http://noferblatz.com
http://quillandmouse.com



Re: Converting markdown to PDF

2021-04-01 Thread Paul M Foster
On Thu, Apr 01, 2021 at 09:41:30PM +0100, Tixy wrote:

> On Thu, 2021-04-01 at 16:34 -0400, Paul M Foster wrote:
> > I'm trying to use pandoc to convert markdown files to PDF. But when I
> > try,
> > pandoc dumps out with an error that it needs "pdflatex" or some other
> > similar converter to do its job. No such "pdflatex" package exists in
> > the
> > Buster stable archives. I'm sure something does this, but I don't
> > know what
> > it is. Does anyone else know?
> > 
> 
> I just Google "debian pdflatex" and the top hit was Debian's search
> page...
> 
> https://packages.debian.org/search?searchon=contents=pdflatex
> 
> I'm sure someone will be along shortly to give an example of how the
> search can be done from a commandline using Debian's packaging tools or
> similar... :-)

Cute but uncalled for. To wit...

paulf@dudley:~$ uname -a
Linux dudley 4.19.0-13-amd64 #1 SMP Debian 4.19.160-2 (2020-11-28) x86_64
GNU/Linux
paulf@dudley:~$ sudo apt install pdflatex
Reading package lists... Done
Building dependency tree   
Reading state information... Done
E: Unable to locate package pdflatex


-- 
Paul M. Foster
http://noferblatz.com
http://quillandmouse.com



Re: Converting markdown to PDF

2021-04-01 Thread Celejar
On Thu, 01 Apr 2021 21:41:30 +0100
Tixy  wrote:

> On Thu, 2021-04-01 at 16:34 -0400, Paul M Foster wrote:
> > I'm trying to use pandoc to convert markdown files to PDF. But when I
> > try,
> > pandoc dumps out with an error that it needs "pdflatex" or some other
> > similar converter to do its job. No such "pdflatex" package exists in
> > the
> > Buster stable archives. I'm sure something does this, but I don't
> > know what
> > it is. Does anyone else know?
> > 
> 
> I just Google "debian pdflatex" and the top hit was Debian's search
> page...
> 
> https://packages.debian.org/search?searchon=contents=pdflatex
> 
> I'm sure someone will be along shortly to give an example of how the
> search can be done from a commandline using Debian's packaging tools or
> similar... :-)

'apt-file search pdflatex'

'apt-file' is in the 'apt-file' package - it keeps a local database,
which one updates periodically / occasionally via 'apt-file update'.

Celejar



Re: Converting markdown to PDF

2021-04-01 Thread Linux-Fan

Paul M Foster writes:


I'm trying to use pandoc to convert markdown files to PDF. But when I try,
pandoc dumps out with an error that it needs "pdflatex" or some other
similar converter to do its job. No such "pdflatex" package exists in the
Buster stable archives. I'm sure something does this, but I don't know what
it is. Does anyone else know?


pdflatex is provided by package texlive-latex-base.

Some hints about which packages might be needed can be seen in pandoc's  
"Suggests":


~$ aptitude show pandoc
Package: pandoc
[...]
Suggests: texlive-latex-recommended, texlive-xetex, texlive-luatex,
 pandoc-citeproc, texlive-latex-extra, context, wkhtmltopdf,
 librsvg2-bin, groff, ghc, nodejs, php, perl, python, ruby,
 r-base-core, libjs-mathjax, node-katex
[...]

I personally have the following texlive packages installed:

~$ aptitude search ~itexlive
i A texlive - TeX Live: A decent selection of the TeX Li
i A texlive-base- TeX Live: Essential programs and files
i A texlive-binaries- Binaries for TeX Live 
i A texlive-extra-utils - TeX Live: TeX auxiliary programs  
i A texlive-font-utils  - TeX Live: Graphics and font utilities 
i A texlive-fonts-extra - TeX Live: Additional fonts
i A texlive-fonts-extra-links   - TeX Live: 
i A texlive-fonts-recommended   - TeX Live: Recommended fonts   
i A texlive-games   - TeX Live: Games typesetting   
i A texlive-generic-extra   - TeX Live: transitional dummy package  
i A texlive-generic-recommended - TeX Live: transitional dummy package  
i A texlive-lang-german - TeX Live: German  
i A texlive-lang-greek  - TeX Live: Greek   
i A texlive-latex-base  - TeX Live: LaTeX fundamental packages  
i A texlive-latex-extra - TeX Live: LaTeX additional packages   
i A texlive-latex-recommended   - TeX Live: LaTeX recommended packages  
i A texlive-pictures- TeX Live: Graphics, pictures, diagrams
i A texlive-plain-generic   - TeX Live: Plain (La)TeX packages  
i A texlive-pstricks- TeX Live: PSTricks
i A texlive-science - TeX Live: Mathematics, natural sciences, c


I am pretty sure that not all of them are needed. It might be sufficient to  
begin with `texlive-latex-base` and only install others if pandoc keeps  
complaining.


HTH
Linux-Fan

öö


pgpxlIqHwvT_f.pgp
Description: PGP signature


Re: Converting markdown to PDF

2021-04-01 Thread Tixy
On Thu, 2021-04-01 at 16:34 -0400, Paul M Foster wrote:
> I'm trying to use pandoc to convert markdown files to PDF. But when I
> try,
> pandoc dumps out with an error that it needs "pdflatex" or some other
> similar converter to do its job. No such "pdflatex" package exists in
> the
> Buster stable archives. I'm sure something does this, but I don't
> know what
> it is. Does anyone else know?
> 

I just Google "debian pdflatex" and the top hit was Debian's search
page...

https://packages.debian.org/search?searchon=contents=pdflatex

I'm sure someone will be along shortly to give an example of how the
search can be done from a commandline using Debian's packaging tools or
similar... :-)

-- 
Tixy



Re: Kuren bij starten van Testing

2021-04-01 Thread Sjoerd
Geert Stappers:
> Sjoerd:
> > Wanneer ik Bullseye (testing) start, dan is er een kans van zo'n 2/3
> > dat het goed gaat.  Maar in 1/3 van de gevallen verschijnt
> > onderstaande tekst. Dan druk ik maar op de reset-knop en is er opnieuw
> > een kans van 2/3 dat het goed gaat.
> > Enig idee wat er aan de hand is? En of het eenvoudig te verhelpen is?
> > 
> > 
> >   Booting `Debian GNU/Linux'
> > 
> > Loading Linux 5.10.0-4-amd64 ...
> > Loading initial ramdisk ...
> > mount: mounting /dev on /root/dev failed: No such file or directory
> > mount: mounting /dev on /root/dev failed: No such file or directory
> > mount: mounting /run on /root/run failed: No such file or directory
> > run-init: can't execute '/sbin/init': No such file or directory
> > Target filesystem doesn't have requested /sbin/init.
> > run-init: can't execute '/sbin/init': No such file or directory
> > run-init: can't execute '/etc/init': No such file or directory
> > run-init: can't execute '/bin/init': No such file or directory
> > run-init: can't execute '/bin/sh': No such file or directory
> > run-init: can't execute '': No such file or directory
> > No init found. Try passing init= bootarg.
> > 
> > 
> > BusyBox v1.30.1 (Debian 1:1.30.1-6+b1) built-in shell (ash)
> > Enter 'help' for a list of built-in commands.
> > 
> > (initramfs) _
>
> Vertel meer over de hardware in kwestie.

Hier de output van hwinfo, korte versie: https://paste.debian.net/1192040/

En als je zin en interesse hebt om naar de complete output van hwinfo te
kijken:  https://pastebin.com/H1C2TXvA  (230 kB tekst!)

Maar als dit toch een lastige kwestie blijkt te zijn, dan zou ik zeggen:
laat maar zitten. Het is testing, dus mogelijk herstelt zich dit weer eens.
En ik heb altijd nog stable om op terug te vallen.



Converting markdown to PDF

2021-04-01 Thread Paul M Foster
I'm trying to use pandoc to convert markdown files to PDF. But when I try,
pandoc dumps out with an error that it needs "pdflatex" or some other
similar converter to do its job. No such "pdflatex" package exists in the
Buster stable archives. I'm sure something does this, but I don't know what
it is. Does anyone else know?

Paul

-- 
Paul M. Foster
http://noferblatz.com
http://quillandmouse.com



Nettoyage du spam : mars 2021

2021-04-01 Thread Jean-Pierre Giraud
Bonjour,
Comme nous sommes en avril, il est désormais possible de
traiter les archives du mois de mars 2021 des listes francophones.

N'oubliez bien sûr pas d'ajouter votre nom à la liste des relecteurs
pour que nous sachions où nous en sommes.

Détails du processus de nettoyage du spam sur :

https://wiki.debian.org/I18n/FrenchSpamClean



Re: OT: wine y Siap

2021-04-01 Thread Marcelo Eduardo Giordano



On 28/3/21 13:15, JavierDebian wrote:



El 28/3/21 a las 05:28, Camaleón escribió:

Los errores no me sugieren nada, más allá de que por el nombre
«OLEPictureImpl_SaveAsFile» parece que la impresión de esa aplicación
genera un archivo, no una copia impresa (físicaente) del módulo con el
que estés trabajando (IVA, etc...). Y si no lo manda a una impresora
entonces CUPS no hace ninguna función aquí, es la apropia aplicación la
que pinta el formulario y lo almacanará en el disco duro.


Estaba pensando...
Lo que dice Camaleón es cierto; con el asunto este de la ecología y la 
burocracia sin papel, es lógico si el módulo es nuevo.

Algunos programas de la AFIP imprimen a un pdf en lugar de la impresora.
En general, luego del proceso de "impresión virtual" tienden a abrirlo 
con un navegador, pero no siempre.
Dentro de la misma botella de wine, instala un visor pdf de Windows 
como PDF Reader y configúralo para ser el lector por defecto; hay que 
ver cuál funciona en wine.



JAP



Estimado:

He tratado de configurar una impresora virtual para imprimir como pdf, 
que te parece esa opción, vale la pena?


Saludos



Re: Instalar scanner de Epson L3110

2021-04-01 Thread Marcelo Eduardo Giordano


On 1/4/21 16:21, Deiby Herrera wrote:

Es para que diferencie los que ya tenía con los nuevos

El jue., 1 de abril de 2021 1:11 p. m., Marcelo Eduardo Giordano 
mailto:marcelogiord...@gmail.com>> escribió:


On 27/3/21 14:30, Deiby Herrera wrote:

Descarga los de nuevo ponlos en una carpeta nueva


El sáb., 27 de marzo de 2021 11:26 a. m., Marcelo Eduardo
Giordano mailto:marcelogiord...@gmail.com>> escribió:

Estimados:
No puedo instalar el scanner de la multifunción Epson L3110.
He bajado los controladores de la página de epson y me da el
siguiente
error.
dpkg -i epsonscan2-bundle-6.6.2.3.x86_64.deb
dpkg: error: el archivo
'epsonscan2-bundle-6.6.2.3.x86_64.deb' no es un
fichero normal

También me da el mismo error al querer instalar un programa
que por lo
que leo es para buscar e instalar drivers de epson
dpkg -i imagescan-bundle-debian-10-3.65.0.x64.deb
dpkg: error: el archivo
'imagescan-bundle-debian-10-3.65.0.x64.deb' no
es un fichero normal

Saludos a todos los listeros


Hola amigo. Los bajé en nueva carpeta y me pasó lo mismo. Cual es
la intención de bajarlos en una nueva carpeta? Gracias por responder


Si, esos son los últimos drivers.

Alguna otra idea para probar?



Re: IANA port ups/401

2021-04-01 Thread Roger Price

On Wed, 31 Mar 2021, Dan Ritter wrote:


Roger Price wrote:

On Wed, 31 Mar 2021, to...@tuxteam.de wrote:


On Wed, Mar 31, 2021 at 04:51:55PM +0200, Roger Price wrote:

Has any reader of this list ever used IANA port ups/401
"Uninterruptible Power Supply" (other than the One Windows Trojan)?
I'm looking for protocol documentation or reports of usage. The port
was assigned in 2008 to Mr. Charles Bennett as both assignee and
contact. Mr. Bennett himself died in 2015.


Sysadmin-type since 1996ish, so: in the last 25 years, I believe
the only time I have encountered "ups/401" is in /etc/services.

SunOS
Solaris
DEC OSF/1
Harris Nighthawk something-or-another B3 (awful even for the
time)
VMS on a microVAX the size of a largish microwave oven
NetBSD and OpenBSD but somehow never FreeBSD
Linux in many distros


This is exactly what I have suspected.  ups/401 is widely known since it 
features in /etc/services, but it has no users.


In an I-D [1], I explain that I would like to use port name "ups" for UPS 
management over TLS 1.3 which is not available in the current NUT (Network UPS 
Tools) package 2.7.4.  Such a "take-over" is not evident, since for example 
direct transfers of IANA names and numbers are not allowed.  One of the hurdles 
to be overcome is demonstrating that "ups" is not being used.


Roger

[1]
https://www.ietf.org/archive/id/draft-rprice-ups-management-protocol-03.html#name-nut-project-requirement



Re: Instalar scanner de Epson L3110

2021-04-01 Thread Deiby Herrera
Es para que diferencie los que ya tenía con los nuevos

El jue., 1 de abril de 2021 1:11 p. m., Marcelo Eduardo Giordano <
marcelogiord...@gmail.com> escribió:

> On 27/3/21 14:30, Deiby Herrera wrote:
>
> Descarga los de nuevo ponlos en una carpeta nueva
>
>
> El sáb., 27 de marzo de 2021 11:26 a. m., Marcelo Eduardo Giordano <
> marcelogiord...@gmail.com> escribió:
>
>> Estimados:
>> No puedo instalar el scanner de la multifunción Epson L3110.
>> He bajado los controladores de la página de epson y me da el siguiente
>> error.
>> dpkg -i epsonscan2-bundle-6.6.2.3.x86_64.deb
>> dpkg: error: el archivo 'epsonscan2-bundle-6.6.2.3.x86_64.deb' no es un
>> fichero normal
>>
>> También me da el mismo error al querer instalar un programa que por lo
>> que leo es para buscar e instalar drivers de epson
>> dpkg -i imagescan-bundle-debian-10-3.65.0.x64.deb
>> dpkg: error: el archivo 'imagescan-bundle-debian-10-3.65.0.x64.deb' no
>> es un fichero normal
>>
>> Saludos a todos los listeros
>>
>> Hola amigo. Los bajé en nueva carpeta y me pasó lo mismo. Cual es la
> intención de bajarlos en una nueva carpeta? Gracias por responder
>


Re: OT: wine y Siap

2021-04-01 Thread Marcelo Eduardo Giordano



On 27/3/21 16:06, Parodper wrote:



O 27/03/21 ás 19:54, Marcelo Eduardo Giordano escribiu:


On 25/3/21 03:40, Camaleón wrote:

El 2021-03-24 a las 18:43 -0300, Marcelo Eduardo Giordano escribió:


On 24/3/21 12:17, Camaleón wrote:

El 2021-03-24 a las 11:51 -0300, Marcelo Eduardo Giordano escribió:


On 24/3/21 11:33, Camaleón wrote:

(...)

2. Revisa los registros que genera Wine por si tuvieras más 
datos del

error cuando intentas imprimir.
¿Donde se miran los registros de wine? porque quise ejecutarlo 
desde la

consola y no me fue posible
Tienes que ejecutar la aplicación y mandar la salida a un archivo, 
aquí

indican cómo:

Where are 'wine' program execution logs stored?
https://askubuntu.com/questions/707941/where-are-wine-program-execution-logs-stored 



wine programa.exe &>wine.log

Te iba a decir que miraras también en el registro de cups
(/var/log/cups/*) pero por el error que te aparece en la 
aplicación me

da la sensación de que ni siquiera llega a hacer el intento de
impresión, es decir, que siap detecta «erróneamente» algún trabajo
pendiente de impresión o que la impresora está ocupada y aborta la
orden.

Hum... ¿tienes algún archivo de tipo .lock (bloqueo) en el directorio
donde has instalado siap?


Como hago para escribir "Program Files (x86)" ya que hay una 
carpeta en ese

directorio con el ejecutable.

Puedes ponerlo entre comillas:

wine "$HOME/.wine/drive_c/Program Files (x86)/siap.exe" &>wine.log

Saludos,


Hola Amigos:

Copio log a ver si me ayudan

wine: configuration in L"/home/marcelo/.wine" has been updated.
0024:fixme:olepicture:OLEPictureImpl_SaveAsFile 
(00176250)->(001884D8, 0, ), hacked stub.
0024:fixme:ntdll:NtQuerySystemInformation info_class 
SYSTEM_PERFORMANCE_INFORMATION
0024:fixme:olepicture:OLEPictureImpl_SaveAsFile 
(00214048)->(0020B8C0, 0, ), hacked stub.
0024:fixme:olepicture:OLEPictureImpl_SaveAsFile 
(0019F398)->(0020BD78, 0, ), hacked stub.
0138:fixme:olepicture:OLEPictureImpl_SaveAsFile 
(0017B438)->(0022AE10, 0, ), hacked stub.
0138:fixme:olepicture:OLEPictureImpl_SaveAsFile 
(0017B438)->(00B45C14, 1, ), hacked stub.
0138:fixme:ntdll:NtQuerySystemInformation info_class 
SYSTEM_PERFORMANCE_INFORMATION
0138:fixme:olepicture:OLEPictureImpl_SaveAsFile 
(0172DE58)->(0172A550, 0, ), hacked stub.
0138:fixme:olepicture:OLEPictureImpl_SaveAsFile 
(01716F18)->(0171F9A8, 0, ), hacked stub.

0138:fixme:richedit:IRichEditOle_fnInPlaceDeactivate stub 110A0088
0024:fixme:olepicture:OLEPictureImpl_FindConnectionPoint no 
connection point for {33ad4ed2-6699-11cf-b70c-00aa0060d393}
0024:fixme:olepicture:OLEPictureImpl_FindConnectionPoint no 
connection point for {33ad4f92-6699-11cf-b70c-00aa0060d393}
0024:fixme:olepicture:OLEPictureImpl_FindConnectionPoint no 
connection point for {33ad4f92-6699-11cf-b70c-00aa0060d393}
0024:fixme:olepicture:OLEPictureImpl_FindConnectionPoint no 
connection point for {33ad4f92-6699-11cf-b70c-00aa0060d393}
0024:fixme:olepicture:OLEPictureImpl_FindConnectionPoint no 
connection point for {33ad4ed2-6699-11cf-b70c-00aa0060d393}
0024:fixme:olepicture:OLEPictureImpl_FindConnectionPoint no 
connection point for {33ad4ed2-6699-11cf-b70c-00aa0060d393}
0024:fixme:olepicture:OLEPictureImpl_FindConnectionPoint no 
connection point for {33ad4ed2-6699-11cf-b70c-00aa0060d393}
0024:fixme:olepicture:OLEPictureImpl_FindConnectionPoint no 
connection point for {33ad4f92-6699-11cf-b70c-00aa0060d393}
0024:fixme:olepicture:OLEPictureImpl_FindConnectionPoint no 
connection point for {33ad4f92-6699-11cf-b70c-00aa0060d393}


Saludos



¿Aparece algo más en el registro? Por que los fixme son problemas del 
código del propio Wine 
(https://wiki.winehq.org/FAQ#I_get_lots_of_.22fixme:.22_messages_in_the_terminal_and_Wine_runs_a_bit_slow). 
Mira en https://wiki.winehq.org/Debug_Channels para ver si hay más 
problemas. En caso contrario el problema es interno de Wine, y lo 
único que se me ocurre es que pruebes a compilar la última versión de 
Wine.



Gracias por responder compañero.

Probé de nuevo y me salen nuevos errores en la consola, pero en la parte 
gráfica el error es el mismo. Copio el 
log0024:fixme:olepicture:OLEPictureImpl_SaveAsFile 
(001765E0)->(00188868, 0, ), hacked stub.
0024:fixme:ntdll:NtQuerySystemInformation info_class 
SYSTEM_PERFORMANCE_INFORMATION
0024:fixme:olepicture:OLEPictureImpl_SaveAsFile (002145C0)->(002176D8, 
0, ), hacked stub.
0024:fixme:olepicture:OLEPictureImpl_SaveAsFile (0019F728)->(00208E00, 
0, ), hacked stub.
010c:fixme:olepicture:OLEPictureImpl_SaveAsFile (0017B820)->(0022B1F8, 
0, ), hacked stub.
010c:fixme:olepicture:OLEPictureImpl_SaveAsFile (0017B820)->(00B45C14, 
1, ), hacked stub.
010c:fixme:ntdll:NtQuerySystemInformation info_class 
SYSTEM_PERFORMANCE_INFORMATION
010c:fixme:olepicture:OLEPictureImpl_SaveAsFile (0172E2F0)->(0172A9D8, 
0, ), hacked stub.
010c:fixme:olepicture:OLEPictureImpl_SaveAsFile 

Re: Instalar scanner de Epson L3110

2021-04-01 Thread Marcelo Eduardo Giordano

On 27/3/21 14:30, Deiby Herrera wrote:

Descarga los de nuevo ponlos en una carpeta nueva


El sáb., 27 de marzo de 2021 11:26 a. m., Marcelo Eduardo Giordano 
mailto:marcelogiord...@gmail.com>> escribió:


Estimados:
No puedo instalar el scanner de la multifunción Epson L3110.
He bajado los controladores de la página de epson y me da el siguiente
error.
dpkg -i epsonscan2-bundle-6.6.2.3.x86_64.deb
dpkg: error: el archivo 'epsonscan2-bundle-6.6.2.3.x86_64.deb' no
es un
fichero normal

También me da el mismo error al querer instalar un programa que por lo
que leo es para buscar e instalar drivers de epson
dpkg -i imagescan-bundle-debian-10-3.65.0.x64.deb
dpkg: error: el archivo 'imagescan-bundle-debian-10-3.65.0.x64.deb' no
es un fichero normal

Saludos a todos los listeros

Hola amigo. Los bajé en nueva carpeta y me pasó lo mismo. Cual es la 
intención de bajarlos en una nueva carpeta? Gracias por responder


Re: Kuren bij starten van Testing

2021-04-01 Thread Geert Stappers
On Thu, Apr 01, 2021 at 02:58:54PM +0200, Sjoerd wrote:
> Wanneer ik Bullseye (testing) start, dan is er een kans van zo'n 2/3 dat
> het goed gaat.  Maar in 1/3 van de gevallen verschijnt onderstaande tekst.
> Dan druk ik maar op de reset-knop en is er opnieuw een kans van 2/3 dat
> het goed gaat.
> Enig idee wat er aan de hand is? En of het eenvoudig te verhelpen is?
> 
> 
>   Booting `Debian GNU/Linux'
> 
> Loading Linux 5.10.0-4-amd64 ...
> Loading initial ramdisk ...
> mount: mounting /dev on /root/dev failed: No such file or directory
> mount: mounting /dev on /root/dev failed: No such file or directory
> mount: mounting /run on /root/run failed: No such file or directory
> run-init: can't execute '/sbin/init': No such file or directory
> Target filesystem doesn't have requested /sbin/init.
> run-init: can't execute '/sbin/init': No such file or directory
> run-init: can't execute '/etc/init': No such file or directory
> run-init: can't execute '/bin/init': No such file or directory
> run-init: can't execute '/bin/sh': No such file or directory
> run-init: can't execute '': No such file or directory
> No init found. Try passing init= bootarg.
> 
> 
> BusyBox v1.30.1 (Debian 1:1.30.1-6+b1) built-in shell (ash)
> Enter 'help' for a list of built-in commands.
> 
> (initramfs) _
> 


Vertel meer over de hardware in kwestie.


 
Groeten
Geert Stappers
-- 
Silence is hard to parse



Re: Creating my first LAN

2021-04-01 Thread Brian
On Tue 30 Mar 2021 at 19:29:49 +0100, Brian wrote:

> Personally, I see the idea of an ad-hoc network as interesting, but
> haven't the incentive to set one up. Not yet anyway!

I successfully and eadily implemented the ifupdown method at

  https://wiki.debian.org/WiFi/AdHoc

Put it top of a reading list!

-- 
A debian-user ad-hoc network convert.



Re: Temporary failure in name resolution

2021-04-01 Thread Greg Wooledge
On Thu, Apr 01, 2021 at 11:50:56AM -0500, David Wright wrote:
> > domain attlocal.net
> > search attlocal.net
> 
> I don't recall your answering Alexander's question: what benefit are
> you getting from those two lines? Do you have a number of machines
> at home that are being placed in that domain, whose names you
> resolve with att's help?

Most likely these lines simply do nothing at all.  They probably don't
have a conventional LAN with hosts that interact with each other.

For most home users, the contents of the search/domain lines are simply
unimportant.



Re: Temporary failure in name resolution

2021-04-01 Thread David Wright
On Wed 31 Mar 2021 at 18:28:52 (-0400), Dan Norton wrote:
> David Christensen wrote on Wed, 31 Mar 2021 13:49:56 -0700:
> 
> I would do 'apt-get update' and 'apt-get upgrade' ('autoremove',
> 'clean', etc.). Once apt-get(8) is done, I would revert the changes
> to /etc/resolv.conf and see if name resolution breaks or remains
> working. (I would test by renaming /etc/resolve.conf and rebooting.)
> 
> Here is what I did:
> # apt update
> # apt upgrade
> # apt autoremove
> # apt-get clean
> # cp /etc/resolv.conf /etc/resolv.confX
> # chattr -i /etc/resolv.conf
> ## to make resolv.conf *not* immutable
> # cat /etc/resolv.conf
> domain attlocal.net
> search attlocal.net

I don't recall your answering Alexander's question: what benefit are
you getting from those two lines? Do you have a number of machines
at home that are being placed in that domain, whose names you
resolve with att's help?

> nameserver 1.1.1.1
> nameserver 1.0.0.1
> nameserver 192.168.1.254

Yes, BT do this (use the highest host number rather than the lowest).

> Shutdown then power-on boot
> 
> ## rebooted with /etc/resolv.conf *not* immutable
> root@deb4:~# ping google.com
> ping: google.com: Temporary failure in name resolution
> root@deb4:~# cat /etc/resolv.conf
> domain attlocal.net
> search attlocal.net
> nameserver 192.168.1.254
> ## showing that /etc/resolv.conf has been clobbered

Normally, I would say that you'd expect that, because dhclient would
overwrite it with DHCP information returned from your router.

But we've a clue that your system is very different from, say, mine:

   '# systemctl status systemd-resolved
shows it being active and "Processing requests...".'

and in a parallel thread "Moritz Kempe: DNS problems on Raspberry Pi 400
(Debian 10.9)" we saw:

   "hosts: files mdns4_minimal [NOTFOUND=return] dns mymachines"

which smells of nss-resolve and, hence, systemd-resolved.

I notice that   man nss-resolve   also mentions placing "resolve"
early in the hosts: line.

Now, I'm not saying that any of this last applies to your system, but
it does suggest that, because you're using systemd-resolved, some of
the advice being given by users who aren't, might not directly apply.
BTW we haven't seen your own nsswitch.conf.

> After restoring resolv.conf so that it looks like this:
> # cat /etc/resolv.conf
> domain attlocal.net
> search attlocal.net
> nameserver 1.1.1.1
> nameserver 1.0.0.1
> nameserver 192.168.1.254
> # chattr +i /etc/resolv.conf
> ## making it immutable
> 
> Rebooted and posted this.

If you're going to file a bug, I would first start by reading up on
systemd-resolved, and checking that your configuration matches what
that service expects. If that doesn't fix it, then I'd file the bug
against systemd-resolved, ie libnss-resolve. I'm not sure whether
that was in the point-release, but the DDs can always reassign it.

Cheers,
David.



Re: Re : Re: probleme unsquash

2021-04-01 Thread steve

Le 01-04-2021, à 11:23:37 +0200, didier gaumet a écrit :


Le 01/04/2021 à 10:44, steve a écrit :
[...]

# cp debian.iso /dev/sdX
# sync

[...]

Je suis surpris de lire ça. En effet /dev/sdc n'est pas une partition et
n'a donc pas de système de fichiers et donc on ne peut pas utiliser la
commande « cp ». Ou alors j'ai raté quelque chose.

Pour copier une image iso sur un périphérique usb par exemple,
j'utilise (en root):

dd if=debian.iso of=/dev/sdc bs=8M status=progress


dd est ce que j'utilise, plus par flemme de changer mes habitudes ;-)

mais, en gros:
- philosophiquement, Linux découle d'Unix et a adopté son principe 
"tout est fichier" (c'est un peu approximatif et il y a des exceptions 
, mais bon...). /dev/sdc est donc un fichier périphérique
- ici on copie sur un périphérique une image déjà régie par un système 
de fichiers et non des fichiers sur un système de fichiers existant. 
On n'a donc besoin ni de partition, ni de système de fichiers existant 
sur le périphérique cible
- et un système de fichiers peut aussi résider sur un périphérique non 
partitionné, c'est le concept superfloppy (on peut l'utiliser sous 
Linix). Y a une page de Microsoft qui détaille le concept ici 
(chercher superfloppy dans la page):


https://docs.microsoft.com/en-us/previous-versions/windows/hardware/design/dn640535(v=vs.85)

"La culture c'est comme la confiture, moins on en a, plus on l'étale".
Ch'suis démasqué ;-)


Bon, et bien j'aurais appris quelque chose aujourd'hui, merci pour tes
explications.



Re: Request: A Debian public Wiki repository/bank for complex code lines with examples, scripts, self-explanatory with terminal, otherwise Minimal explanatory texts

2021-04-01 Thread rhkramer
Intentionally to posting, as it is a general comment to the entire thread, not 
anything specific in this email (I think).  My comments:

   * Some interesting ideas -- when are you going to implement them?  Or are 
you trying to get others to implement them?  It would be useful / helpful if 
you gave a start.

   * Dan Ritter's observations on how much work might be involved is useful 
information.  Your effort to suppress his comments (in some manner)  is a 
violation of the spirit of free and open communication which I expect on this 
list.

   * There are wikis available that you could start making pages for -- one 
might be Greg Wooledge's wiki on bash (with his permission, and if he is 
willing to allow subjects other than bash to be discussed).

   Another is my WikiLearn [t]wiki which was / is intended as my learning 
notebook (I have a lot more content offline, which I haven't put online for a 
variety of reasons).  

   It is at https://twiki.org/cgi-bin/view/Wikilearn/WebHome.

   If you decide to start adding content there, I would like to discuss naming 
conventions with you before you start adding pages.

   There are also web hosting alternatives, some of which support one or more 
types of wikis.  (There used to be things sometimes called "wikifarms" that 
were intended to allow anyone to easily start their own wiki -- I'm not sure 
any of those still exist.  But, a webhost that will set up the framework of a 
wiki for you is a good start.

As is often said about code, something like "code speaks" (i.e., she who 
writes the code somehow gets more say about what and how is written), I think 
the same applies to documentation -- "documentation speaks" (he who writes the 
documentation gets more say about what and how it is written).

Have a good day.



On Wednesday, March 31, 2021 05:46:43 AM Susmita/Rajib wrote:
> Follow Up from https://lists.debian.org/debian-user/2021/03/msg01459.html,



Kuren bij starten van Testing

2021-04-01 Thread Sjoerd
Wanneer ik Bullseye (testing) start, dan is er een kans van zo'n 2/3 dat
het goed gaat.  Maar in 1/3 van de gevallen verschijnt onderstaande tekst.
Dan druk ik maar op de reset-knop en is er opnieuw een kans van 2/3 dat
het goed gaat.
Enig idee wat er aan de hand is? En of het eenvoudig te verhelpen is?


  Booting `Debian GNU/Linux'

Loading Linux 5.10.0-4-amd64 ...
Loading initial ramdisk ...
mount: mounting /dev on /root/dev failed: No such file or directory
mount: mounting /dev on /root/dev failed: No such file or directory
mount: mounting /run on /root/run failed: No such file or directory
run-init: can't execute '/sbin/init': No such file or directory
Target filesystem doesn't have requested /sbin/init.
run-init: can't execute '/sbin/init': No such file or directory
run-init: can't execute '/etc/init': No such file or directory
run-init: can't execute '/bin/init': No such file or directory
run-init: can't execute '/bin/sh': No such file or directory
run-init: can't execute '': No such file or directory
No init found. Try passing init= bootarg.


BusyBox v1.30.1 (Debian 1:1.30.1-6+b1) built-in shell (ash)
Enter 'help' for a list of built-in commands.

(initramfs) _



Re: suivre bullseye en stable

2021-04-01 Thread yamo'
Salut,

Benoit B a tapoté le 30/03/2021 19:50:


> Y a-t-il quelque chose de spécial à faire pour suivre bullseye quand
> ça va basculer en stable ?
> Voici mon source.list
> 
> deb https://deb.debian.org/debian/ bullseye main #contrib non-free
> deb-src https://deb.debian.org/debian/ bullseye main
> deb https://deb.debian.org/debian/ bullseye-updates main

Il te manquera les mises à jour de sécurité :

deb http://security.debian.org/ bullseye/updates  main #contrib non-free

# ou

deb http://security.debian.org/debian-security bullseye/updates main
#contrib non-free

Et le deb-src idoine.

Je pense que la deuxième syntaxe est meilleure vu qu'elle provient de



-- 
Stéphane



debian-user list info and guidelines (FAQ) - posted monthly

2021-04-01 Thread Andrew M.A. Cater
debian-user is a mailing list provided for support for Debian users,
and to facilitate discussion on relevant topics.

Some guidelines which may help explain how the list works:

* The language on this mailing list is English. There may be other mailing 
  lists that are language-specific for example debian-user-french

* It is common for users to be redirected here from other lists - for example,
  from debian-project. It is also common for people to be posting here when 
  English is not their primary language. Please be considerate.

* The list is a Debian communication forum. As such, it is subject to both the
   Debian mailing list Code of Conduct and the main Debian Code of Conduct

 https://www.debian.org/MailingLists/#codeofconduct
 https://www.debian.org/code_of_conduct

* This is a fairly busy mailing list and you may have to wait for an
  answer - please be patient. Please post answers back to the list so
  others can benefit; private conversations don't benefit people who
  may be following along on the list or reading the archives later.

* Help and advice on this list is provided by volunteers in their own time. 
  It is common for there to be different opinions or answers provided.

 * Please try to stay on topic. Arguments for the sake of it are not
   welcome here. Partisan political / religious / cultural arguments
   do not belong here either. Debian's community is world wide; don't
   assume others will agree with your views or need to read them on a
   Debian list.

* There is an FAQ on the Debian wiki derived from some questions asked 
  on this list at https://wiki.debian.org/FAQsFromDebianUser

* One question that comes up on almost all Debian lists from time to time 
  is of the form:
  "I have done something wrong / included personal details in an email.
   Could you please delete my name / details / remove the mail"

  Practically, this is impossible: the mailing lists are archived, potentially
  cached by Google and so on. Unfortunately, there is nothing much we can do
  to ensure that all copies anywhere on the Internet are deleted. Asking to do
  this may only serve to draw further attention - the so-called "Streisand 
  effect"
  (see also: https://en.wikipedia.org/wiki/Streisand_effect )

Problems?
=

Complaints about inappropriate behaviour should be referred to the
Debian Community Team .

Inappropriate behaviour on the list may lead to warnings; repeated bad
behaviour may lead to temporary or permanent bans for offenders.



Re: Re : Re: probleme unsquash

2021-04-01 Thread didier gaumet

Le 01/04/2021 à 10:44, steve a écrit :
[...]

# cp debian.iso /dev/sdX
# sync

[...]

Je suis surpris de lire ça. En effet /dev/sdc n'est pas une partition et
n'a donc pas de système de fichiers et donc on ne peut pas utiliser la
commande « cp ». Ou alors j'ai raté quelque chose.

Pour copier une image iso sur un périphérique usb par exemple,
j'utilise (en root):

dd if=debian.iso of=/dev/sdc bs=8M status=progress


dd est ce que j'utilise, plus par flemme de changer mes habitudes ;-)

mais, en gros:
- philosophiquement, Linux découle d'Unix et a adopté son principe "tout 
est fichier" (c'est un peu approximatif et il y a des exceptions , mais 
bon...). /dev/sdc est donc un fichier périphérique
- ici on copie sur un périphérique une image déjà régie par un système 
de fichiers et non des fichiers sur un système de fichiers existant. On 
n'a donc besoin ni de partition, ni de système de fichiers existant sur 
le périphérique cible
- et un système de fichiers peut aussi résider sur un périphérique non 
partitionné, c'est le concept superfloppy (on peut l'utiliser sous 
Linix). Y a une page de Microsoft qui détaille le concept ici (chercher 
superfloppy dans la page):


https://docs.microsoft.com/en-us/previous-versions/windows/hardware/design/dn640535(v=vs.85)

"La culture c'est comme la confiture, moins on en a, plus on l'étale".
Ch'suis démasqué ;-)




Re: `apt list` output question

2021-04-01 Thread Andrei POPESCU
On Ma, 30 mar 21, 09:47:48, Victor Sudakov wrote:
> 
> # apt install yamllint/buster
> Reading package lists... Done
> Building dependency tree   
> Reading state information... Done
> Selected version '1.15.0-1' (Debian:10.9/stable [all]) for 'yamllint'
> ...
> 
> I just don't quite understand how this can be put to good use.

It's useful when you mix releases (dangerous).
 
> But at least I know now what the "unknown" suffix means:
> When you see unknown, that means the repository doesn’t have a "Suite"
> entry in its Release file.
> 
> It's also confusing that the suffix shows "stable" while in fact I'm
> tracking "buster" and have no intention to track "stable".
> Indeed "apt-cache policy yamllint" shows 
> "500 http://deb.debian.org/debian buster/main amd64 Packages", that is
> "buster", not "stable" as in "apt list" output.

But buster is (still) stable ;)


Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser


signature.asc
Description: PGP signature


Re: Re : Re: probleme unsquash

2021-04-01 Thread steve

Salut,

Le 01-04-2021, à 10:23:23 +0200, didier gaumet a écrit :



As-tu préparé ta clé USB avec un outil genre Unetbootin ou en suivant 
la méthode Debian? (ce genre d'outil peut ou pouvait avoir du mal à 
gérer les images hybrides et les images Debian -live ou install- sont 
des images hybrides, pas de pures images ISO)


en adaptant le nom de l'image à celle téléchargée (.iso) et le nom du 
périphérique de la clé (périphérique complet, pas partition. exemple 
/dev/sda pas /dev/sda1)


# cp debian.iso /dev/sdX
# sync

si ta clé est sur /dev/sdc ça donne (# indique que c'est à taper avec 
le compte root):

# cp debian-live-10.9.0-amd64-kde.iso /dev/sdc
# sync

cf https://www.debian.org/releases/stable/amd64/ch04s03.fr.html


Je suis surpris de lire ça. En effet /dev/sdc n'est pas une partition et
n'a donc pas de système de fichiers et donc on ne peut pas utiliser la
commande « cp ». Ou alors j'ai raté quelque chose.

Pour copier une image iso sur un périphérique usb par exemple,
j'utilise (en root):

dd if=debian.iso of=/dev/sdc bs=8M status=progress



Re: Cannot see update to recent linux kernel 5.10.19-1~bpo10+1 (from 5.10.13-1~bpo10+1)

2021-04-01 Thread didier gaumet

Le 01/04/2021 à 10:02, Andrei POPESCU a écrit :

On Mi, 31 mar 21, 22:54:59, l0f...@tuta.io wrote:

[...]

Is linux-signed-amd64 the source of linux-image-amd64?

[...]

I suppose there are some constraints here but it would be (apparently)
easier if the names were matching ^^


Using different source packages very likely involves more work for the
maintainers, so it was probably necessary.


I've counted 108 binary packages built from the one linux-signed-amd64 
source package: why would one create 108 identical source packages with 
different names when one is sufficient? ;-)



The process to create signed kernel images is "documented" somewhere
(possibly just mailing list post), so a web search should find it.

[...]

https://wiki.debian.org/SecureBoot#MOK_-_Machine_Owner_Key



Re: How I scan, was Re: xsane can't see Brother ADS-2700W scanner

2021-04-01 Thread David Pottage

On 2021-03-31 22:05, Stefan Monnier wrote:

Scanning the output to a server just seems plain obvious to me.
What's the downside?


It has its advantages, indeed.  On the downsides:

- the scanner usually has a very limited UI, making it
  difficult/inconvenient (if at all possible) to control and select the
  scanning options, compared to the comfort of a large screen.

- scanning to a server implies allowing the scanner device write access
  to a server, which either implies the users authenticating themselves
  on the scanner itself (which is rather problematic and is compounded
  with the previous downside), or making the scan result land on an
  "anonymous" area where anyone can see what anyone else scans.

- It usually means you're stuck with the functionality that the
  manufacturer decided to include in the scanner's software stack,
  because it's always proprietary or "walled" (it may contain Free
  Software for all I know, but I can't access nor modify the code).

The option I favour is that the scan is controlled by your own 
computer,

but you can trigger new scans by hitting buttons on the scanner
(i.e. the button-presses get sent to your computer who then decides
what action to take in response to them), so that you can comfortably
setup the scan parameters on your computer and then you can comfortably
scan the various documents without having to go back to your computer
between them.


Sounds like we have yet another use for a Raspberry Pi or similar small 
and cheap computer.


Hook it up to a dumb USB scanner, the local network and a touch screen.

Users can walk up, put their originals in the scanner, and use a much
richer UI to chose their scanning options. The scans are emailed to them
in their preferred file format using the email address they gave when
they authenticated.

I wonder if such an open source project already exists?

--
David Pottage



Re: Re : Re: probleme unsquash

2021-04-01 Thread didier gaumet



As-tu préparé ta clé USB avec un outil genre Unetbootin ou en suivant la 
méthode Debian? (ce genre d'outil peut ou pouvait avoir du mal à gérer 
les images hybrides et les images Debian -live ou install- sont des 
images hybrides, pas de pures images ISO)


en adaptant le nom de l'image à celle téléchargée (.iso) et le nom du 
périphérique de la clé (périphérique complet, pas partition. exemple 
/dev/sda pas /dev/sda1)


# cp debian.iso /dev/sdX
# sync

si ta clé est sur /dev/sdc ça donne (# indique que c'est à taper avec le 
compte root):

# cp debian-live-10.9.0-amd64-kde.iso /dev/sdc
# sync

cf https://www.debian.org/releases/stable/amd64/ch04s03.fr.html



Re: Cannot see update to recent linux kernel 5.10.19-1~bpo10+1 (from 5.10.13-1~bpo10+1)

2021-04-01 Thread Andrei POPESCU
On Mi, 31 mar 21, 22:54:59, l0f...@tuta.io wrote:
> Hi,
> 
> 30 mars 2021, 08:16 de andreimpope...@gmail.com:
> 
> > $ rmadison linux-signed-amd64
> > linux-signed-amd64 | 4.19.118+2+deb10u1~bpo9+1 | stretch-backports | source
> > linux-signed-amd64 | 4.19.171+2| stable| source
> > linux-signed-amd64 | 4.19.181+1| stable| source
> > linux-signed-amd64 | 5.9.15+1~bpo10+1  | buster-backports  | source
> > linux-signed-amd64 | 5.10.13+1~bpo10+1 | buster-backports  | source
> > linux-signed-amd64 | 5.10.19+1~bpo10+1 | backports-policy  | source
> > linux-signed-amd64 | 5.10.24+1 | testing   | source
> > linux-signed-amd64 | 5.10.24+1 | unstable  | source
> >
> Is linux-signed-amd64 the source of linux-image-amd64?

apt show linux-image-amd64

> I suppose there are some constraints here but it would be (apparently) 
> easier if the names were matching ^^

Using different source packages very likely involves more work for the 
maintainers, so it was probably necessary.

The process to create signed kernel images is "documented" somewhere 
(possibly just mailing list post), so a web search should find it.

> If I follow you, we have more information by inquiring about the 
> source package than the binary one?
 
It's easier to track source packages if the binary package name changes 
often.
 
> > The packages appears to be stuck in the backports-policy. If I recall 
> > correctly (see recent -backports archives) this is related to the 
> > freeze.
> >
> Very interesting. You have certainly something here...
> 
> But if true, why 
> https://lists.debian.org/debian-backports-changes/2021/03/msg00053.html 
> mentions 
> "Accepted linux 5.10.19-1~bpo10+1 (source) into 
> buster-backports->backports-policy, buster-backports" if it's just in 
> backports-policy?

It says 'linux', which is the source package for the -unsigned images, 
as discussed above.

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser


signature.asc
Description: PGP signature