Re: Latest kernel update for Wheezy not compatible

[Felix Miata]

Paul Zimmerman composed on 2018-01-09 23:43 (UTC):

> After running "aptitude update" and "aptitude safe-upgrade" on my Wheezy
> boxes, I find I have TWO kernels installed. One of them, the new patch for
> this "Meltdown" problem, does not boot. It hangs. Fortunately, they were
> smart enough to keep the old kernel and that still boots normally. Why would
> it be incompatible? Could there be missing dependencies? Or could it be that
> the CPU is very old? (Intel E8600 -- yes, from 2009, but at least it's a
> 'hybrid' motherboard that takes DDR3 memory :) Since Wheezy loses even
> long-term support in May, I guess they won't put much effort into fixing
> this. But I like my old Linux boxes. I hope there will be a kernel that they
> can run?

There's no reason to blame the age of your PC. 4 or 5 of of my newer PCs have
E8400 CPUs. I quit using Wheezy a long time ago, and mostly quit Jessie too. I
have multiple installations on PCs 4 or more years older than an E8600 running
fine on Stretch. The Stretch update I just did minutes ago was on a 32-bit PC
with DDR400 RAM, probably 6+ years older than yours.
-- 
"Wisdom is supreme; therefore get wisdom. Whatever else you
get, get wisdom." Proverbs 4:7 (New Living Translation)

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/

Re: Debian iso installation incorrectly sets sources.list

[The Wanderer]

On 2018-01-09 at 22:54, John Hosack wrote:

> Hello,
> 
> This is a bug report. I tried to use the reporting system, but it did not
> seem to be appropriate. So, I will give a narrative:

Bug reports need to be filed in the Debian bug tracker, on
bugs.debian.org, not mailed to debian-user. You can do that either by
E-mailing sub...@bugs.debian.org with an appropriately-formatted E-mail,
or with the 'reportbug' program (which in fact generates and attempts to
send such an E-mail).

In the case of bugs in the installer, the correct (pseudo-)package to
file the bug against is probably 'installation-report'.

> This is what happened.
> I decided to install Debian on my small machine (Asus eeePC 900A, 1GB
> ram, 4GB storage).  So I selected debian-9.3.0-i386-xfce-CD-1.iso and
> put it onto a flash memory stick.  Installation went ok, but
> later on when I did "apt install gcc", the installation program
> requested the insertion of the installation disk in the drive
> /media/cdrom. Why?
> 
> Examination.
> The /etc/apt/sources.list file had "deb: cdrom:[..." as
> the first entry, and was not commented out. My installation medium
> was wrong!
> 
> Solution.
> Comment out "deb: cdrom:[..." in sources.list.
> 
> Discussion.
> There are 2 problems:
> (1) Installation should not put the installation medium in the
> sources.list, at least not without asking the user,
> since the medium may be reused.

The installation medium has to be present in sources.list during the
install process, in order for apt to be able to find the repository
contained on that medium.

In some cases, the user may decide after the initial OS install to
install additional packages which were available on the install medium.
To facilitate doing that (rather than downloading the packages over the
network, which may be expensive or impossible in some cases), the
sources.list entry is retained post-install, but commented out.

If the entry was not changed to be commented out during the conclusion
of the initial OS install procedure, that sounds like an issue indeed,
although a relatively minor one. But the inclusion of the entry in
sources.list is not an error, and ceasing to include such entries there
at all would be problematic.

> (2) Installation should keep track of the installation medium;
> if necessary by asking the user.

How? What information should it record, and how would this information
be useful?

>   (2) reflects a wider problem: Debian has a legacy of
> assuming CD or DVD installation. But much is now done by
> flash memory sticks. Debian should change to reflect this.
> For example, the iso file names might be "large" (or "full")
> or "small" (or "base"), not "DVD" or "CD". References
> to "CD" or "DVD" should be replaced by  reference to the
> "installation medium", unless "CD" is actually necessary. Etc.

If I understand matters correctly, there is a not-purely-historical
reason for these names: the sizes of the images, particularly in the
case of multi-image sets, are determined based on what is expected to be
able to fit on a DVD or a CD.

Which is not to say that it would necessarily not be worth attempting to
modernize things here, as such optical media become more and more a
historical irrelevancy - just that it's not as trivial as you may think.

-- 
   The Wanderer

The reasonable man adapts himself to the world; the unreasonable one
persists in trying to adapt the world to himself. Therefore all
progress depends on the unreasonable man. -- George Bernard Shaw



signature.asc
Description: OpenPGP digital signature

Re: Debian iso installation incorrectly sets sources.list

[David Christensen]

On 01/09/18 19:54, John Hosack wrote:

This is a bug report. I tried to use the reporting system, but it did not
seem to be appropriate. So, I will give a narrative:

This is what happened.
I decided to install Debian on my small machine (Asus eeePC 900A, 1GB
ram, 4GB storage).  So I selected debian-9.3.0-i386-xfce-CD-1.iso and
put it onto a flash memory stick.  Installation went ok, but
later on when I did "apt install gcc", the installation program
requested the insertion of the installation disk in the drive
/media/cdrom. Why?

Examination.
The /etc/apt/sources.list file had "deb: cdrom:[..." as
the first entry, and was not commented out. My installation medium
was wrong!

Solution.
Comment out "deb: cdrom:[..." in sources.list.

Discussion.
There are 2 problems:
(1) Installation should not put the installation medium in the
sources.list, at least not without asking the user,
since the medium may be reused.
(2) Installation should keep track of the installation medium;
if necessary by asking the user.
(2) reflects a wider problem: Debian has a legacy of
assuming CD or DVD installation. But much is now done by
flash memory sticks. Debian should change to reflect this.
For example, the iso file names might be "large" (or "full")
or "small" (or "base"), not "DVD" or "CD". References
to "CD" or "DVD" should be replaced by  reference to the
"installation medium", unless "CD" is actually necessary. Etc.


That's a feature, not a bug -- Debian has been doing it that way since 
at least version 2 (when I started using Debian).



David

Debian iso installation incorrectly sets sources.list

[John Hosack]

Hello,

This is a bug report. I tried to use the reporting system, but it did not
seem to be appropriate. So, I will give a narrative:

This is what happened.
I decided to install Debian on my small machine (Asus eeePC 900A, 1GB
ram, 4GB storage).  So I selected debian-9.3.0-i386-xfce-CD-1.iso and
put it onto a flash memory stick.  Installation went ok, but
later on when I did "apt install gcc", the installation program
requested the insertion of the installation disk in the drive
/media/cdrom. Why?

Examination.
The /etc/apt/sources.list file had "deb: cdrom:[..." as
the first entry, and was not commented out. My installation medium
was wrong!

Solution.
Comment out "deb: cdrom:[..." in sources.list.

Discussion.
There are 2 problems:
(1) Installation should not put the installation medium in the
sources.list, at least not without asking the user,
since the medium may be reused.
(2) Installation should keep track of the installation medium;
if necessary by asking the user.
(2) reflects a wider problem: Debian has a legacy of
assuming CD or DVD installation. But much is now done by
flash memory sticks. Debian should change to reflect this.
For example, the iso file names might be "large" (or "full")
or "small" (or "base"), not "DVD" or "CD". References
to "CD" or "DVD" should be replaced by  reference to the
"installation medium", unless "CD" is actually necessary. Etc.

Regards,
John Hosack

Re: UID 1000 on Raspberry Pi (Was: Re: Embarrassing security bug in systemd)

[Erik Christiansen]

On 09.01.18 15:04, Christian Groessler wrote:
> I just edited the password file directly, "vipw" and "vipw -s", and renamed
> the pi user.

When doing that, there is merit in running pwck before any powerdown/reboot, 
as any illegality in a line stopped processing of all following when I
last tried mucking it up. (A good reason for the root entry to be first.)

And for vigr there's grpck.

That's all we had in the decades before the newfangled useradd stuff
came along.

Erik

Re: How to create a PDF-Printer from the command line

[Brian]

On Mon 08 Jan 2018 at 19:21:39 -0600, David Wright wrote:

> On Mon 08 Jan 2018 at 18:18:33 (+), Brian wrote:
> > 
> > Unlike David Wright, I've not noticed the font quality to be poor when
> > the magnification ability (left click with the mouse) of gv is used to
> > examine characters in the PDF.
> 
> What I was using with paps (and its maximum Unicode coverage when
> diagnostic printing) is FreeMono, which appears to substitute unifont
> characters where it needs to: freemono.png attached. This shows the
> font itself, some hex blobs, and some unifont substitutions.
> So *most* of a typical file will be printed with the quality of
> $ display /usr/share/fonts/opentype/freefont/FreeMono.otf
> 
> Commenting on your other post, yes, it *would* be nice if paps were
> papdf, but I merely have| ps2pdf - -   at the end of the bash
> function that sets the default font and margins etc to suit my
> printer. So being Unicode-aware is far more important to me than
> PS output.
> 
> ¹ attachments are scrot screenshots of xpdf set to 600%, which limits
> their crispness.

I am not attempting to dissuade anyone from using paps but trying to
explore why what appears to be a relatively simple process (text to PDF)
has so few utilities. Without a UTF-8 requirement we are awash with
Postscript programs, but not so with direct conversion to PDF. Having
said that, I have no deep understanding of either the PostScript or PDF
format, so perhaps it is more difficult than I imagine; especially when
it comes to producing an output with, for example, columns, headers etc.

However, there are utilities which can help with preprocessing a text
file beforehand.

As a UTF-8 Debian alternative to txt2pdf:

Create $HOME/.config/fontconfig/fonts.conf with the contents

  
  
  
   
 monospace
 
   freemono
 
   
  

(Is there anything better than FreeMono's UTF-8 glyph coverage?)

Then

  CHARSET=utf-8 /usr/lib/cups/filter/texttopdf 1 1 1 1 1 < text.txt> > out.pdf

out.pdf is not searchable, so continue with

  pdftocairo -pdf out.pdf searchable.pdf

A bonus is that searchable.pdf is about seven times smaller than out.pdf.

-- 
Brian.

Re: Latest kernel update for Wheezy not compatible

[Michael Lange]

Hi,

On Tue, 9 Jan 2018 23:43:23 + (UTC)
Paul Zimmerman  wrote:

> After running "aptitude update" and "aptitude safe-upgrade" on my
> Wheezy boxes, I find I have TWO kernels installed. One of them, the new
> patch for this "Meltdown" problem, does not boot. It hangs.
> Fortunately, they were smart enough to keep the old kernel and that
> still boots normally. Why would it be incompatible? Could there be
> missing dependencies? Or could it be that the CPU is very old? (Intel
> E8600 -- yes, from 2009, but at least it's a 'hybrid' motherboard that
> takes DDR3 memory :) Since Wheezy loses even long-term support in May,
> I guess they won't put much effort into fixing this. But I like my old
> Linux boxes. I hope there will be a kernel that they can run?

there was a thread here recently about a similar sounding problem, see:

https://lists.debian.org/debian-user/2018/01/msg00242.html

Not sure (of course) if this referred to the same problem as yours, and I
don't remember if this thread lead anywhere, but it might be a starting
point for you to investigate...

Best regards (and good luck!)

Michael


.-.. .. ...- .   .-.. --- -. --.   .- -. -..   .--. .-. --- ... .--. . .-.

Death, when unnecessary, is a tragic thing.
-- Flint, "Requiem for Methuselah", stardate 5843.7

Re: problème dkms et noyau 4.14.0-3-amd64

[Haricophile]

Le Tue, 9 Jan 2018 20:46:05 +0100,
jérémy prego  a écrit :

> Consult /var/lib/dkms/bbswitch/0.8/build/make.log for more
> information.

bbswitch c'est pas le truc qui passe de intel à nvidia ? bumblebee est
installé ?

(résolu) Re: problème dkms et noyau 4.14.0-3-amd64

[jérémy prego]

Le 10/01/2018 à 00:09, Étienne Mollier a écrit :

Du coup, est ce que votre version de linux-kbuild-4.14
provient aussi de Sid, ou est ce que vous utilisez
toujours la version de Testing ?


j'ai presque honte. Après mise à jour du paquet

linux-kbuild-4.14 de testing a sid, ça fonctionne :-)



bon il arrive pas a me compilé nvidia-current, mais pas grave pour le moment, 
les autres fonctionnent


merci pour la piste !
jerem
jerem

Re: How to create a PDF-Printer from the command line

[tomas]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Tue, Jan 09, 2018 at 05:01:50PM -0600, David Wright wrote:
> On Tue 09 Jan 2018 at 23:20:55 (+0100), to...@tuxteam.de wrote:

[...]

> > Modern (La)TeX implementations should be able to cope with UTF-8

[...]

> Thanks. I feel ashamed that I'm wasting your time, and that of
> Ionel Mugurel Ciobîcă.

No worries: people here are not forced to answer :-)

>I'm only testing the methods being suggested
> here for conversion. It's proved valuable (for me) as I hadn't come
> across txt2pdf before, which is already wrapped up in my .bashrc,
> but one does see poor suggestions as well as good ones.
> 
> I've been a LaTeX user for over 30 years, so I've stripped out more
> Unicode workarounds than I care to mention over the years. Remember
> this sort of stuff?
> 
> \catcode`Æ=13 \defÆ{\AE}% handle Æ
> \catcode`æ=13 \defæ{\ae}% handle æ

[...]

You bet. My first TeX was on an Atari ST ($DEITY knows when: Wikipedia
says between 1985 and 1993). LaTeX wasn't around. UTF-8 much less.
Heck, even Latin-1 wasn't quite there, German tended to cannibalize
several ASCII codes for its special characters (you had to decide
whether you wanted '{' or 'ä' or something). The "upper half" tended
to be some weird graphical chars.

Oh, yes, I do remember. Dimly, though.

> I do remember \usepackage[utf8]{inputenc}, but even that has been
> superceded by \RequirePackage{fontspec} (yes, I moved on from
> using .sty files to .cls files about 5 years ago).

OK.

> Apologies again.

Again, no worries.

Cheers
- -- tomás
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAlpVUt8ACgkQBcgs9XrR2kaydQCaAlFVPsFZPn6AnEoXAWR+wkkx
mqMAn0HKgmqMjjMgPrH0reTz/SKIlC9m
=EFrm
-END PGP SIGNATURE-

Re: Kernel problem?

[Felix Miata]

Rob Hurle composed on 2018-01-07 13:58 (UTC+1100):

>   I'm running Stretch and yesterday I did my normal:

> sudo apt-get update
> sudo apt-get upgrade

> It seemed to install vmlinuz-4.9.0-5-686-pae (and associated config and
> image files, etc) in place of 4.9.0-4-686-pae versions.  Now the system
> won't boot at all.  I have reverted to 4.9.0-4-686-pae and all is well.  My
> questions are:

> 1.  Does anyone else see this?

> 2.  How can I revert without losing my working 4.9.0-4-686-pae system?  Can
> I just change the soft links for initrd.img and vmlinuz at / to point to
> the 4.9.0-4-686-pae versions instead of the 4.9.0-5-686-pae ones?  Will
> this break something else for a future upgrade?

> Any help much appreciated.  Thank you.


Here's a portion of /boot/ on one I just updated minutes ago:

lrwxrwxrwx  1   26 Jan  9 17:47 initrd -> initrd.img-4.9.0-5-686-pae
lrwxrwxrwx  1   26 Jan  9 17:47 initrd-cur -> initrd.img-4.9.0-5-686-pae
-rw-r--r--  1 17388979 Jan  9 17:45 initrd.img-4.9.0-4-686-pae
-rw-r--r--  1 17067283 Oct 21 03:00 .initrd.img-4.9.0-4-686-pae1
-rw-r--r--  1 17388194 Oct 21 04:51 .initrd.img-4.9.0-4-686-pae2
-rw-r--r--  1 17388979 Jan  9 17:45 .initrd.img-4.9.0-4-686-pae3
-rw-r--r--  1 17392772 Jan  9 17:44 initrd.img-4.9.0-5-686-pae
-rw-r--r--  1 17392772 Jan  9 17:44 .initrd.img-4.9.0-5-686-pae1
lrwxrwxrwx  1   26 Oct 21 03:18 initrd-prv -> initrd.img-4.9.0-4-686-pae
lrwxrwxrwx  1   23 Jan  9 17:47 vmlinuz -> vmlinuz-4.9.0-5-686-pae
-rw-r--r--  1  3643920 Dec 22 19:39 vmlinuz-4.9.0-4-686-pae
-rw-r--r--  1  3645296 Jan  4 06:12 vmlinuz-4.9.0-5-686-pae
lrwxrwxrwx  1   23 Jan  9 17:46 vmlinuz-cur -> vmlinuz-4.9.0-5-686-pae
lrwxrwxrwx  1   23 Oct 21 03:18 vmlinuz-prv -> vmlinuz-4.9.0-4-686-pae

Note the additional symlinks, and the in-place initrd backups. If what happened
to you happened to me, and I was unable to rebuild the 4.9.0.5 initrd or
anything else to solve the problem, I would purge the 4.9.0.5 kernel, delete the
-cur symlinks, and copy the -prv symlinks back to vmlinuz and initrd. If and
when an update brings a 4.9.0.6 or newer kernel, the 4.9.0.4 would be retained,
as 4.9.0.5 would have if it hadn't been purged.
-- 
"Wisdom is supreme; therefore get wisdom. Whatever else you
get, get wisdom." Proverbs 4:7 (New Living Translation)

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/

Re: problème dkms et noyau 4.14.0-3-amd64

[Étienne Mollier]

On 01/09/2018 11:45 PM, jérémy prego wrote:
> pour répondre a Étienne, la réinstallation n'a pasrésolu le problème, je vais 
> rester sur le 4.14.0-2 pour le moment.

Merci pour le retour.

Toutes mes excuses, j'ai mentionné le répertoire kbuild
sans proposer de vérifier le paquet attenant.

Peut-être que les idées seront plus fraîches après une
bonne nuit de sommeil.

> et en effet, le noyau 4.14.0-3 vient de sid, effectivement, j'avais oublié ce 
> détail :-)

Du coup, est ce que votre version de linux-kbuild-4.14
provient aussi de Sid, ou est ce que vous utilisez
toujours la version de Testing ?

La ligne Depends ne précise pas le numéro de version :

$ apt show linux-headers-4.14.0-3-amd64
[...]
Depends: linux-headers-4.14.0-3-common (= 4.14.12-2), 
linux-kbuild-4.14, linux-compiler-gcc-7-x86
[...]

C'est peut-être ça qui coince.

Bonne nuit,
-- 
Étienne Mollier 

Re: How to create a PDF-Printer from the command line

[David Wright]

On Tue 09 Jan 2018 at 23:20:55 (+0100), to...@tuxteam.de wrote:
> On Tue, Jan 09, 2018 at 02:09:22PM -0600, David Wright wrote:
> 
> [...]
> 
> > For me, this is a new take on document conversion methods.
> > 
> > FWIW my test file produced 30819 "Missing character" errors which
> > is hardly surprising as TeX was released 40 years ago in the days
> > of 7 bit ASCII. The PDF had a single line of characters running
> > off the right hand side of the page.
> 
> Modern (La)TeX implementations should be able to cope with UTF-8
> input: \usepackage[utf8]{inputenc} is one of the recommended magic
> incantations (that said, reportedly Lua(La)TeX and Xe(La)TeX are
> said to cope even better; they are part of your TeX live distribution
> anyway).
> 
> Of course you have to make sure that your font supports the glyphs
> you actually use.

Thanks. I feel ashamed that I'm wasting your time, and that of
Ionel Mugurel Ciobîcă. I'm only testing the methods being suggested
here for conversion. It's proved valuable (for me) as I hadn't come
across txt2pdf before, which is already wrapped up in my .bashrc,
but one does see poor suggestions as well as good ones.

I've been a LaTeX user for over 30 years, so I've stripped out more
Unicode workarounds than I care to mention over the years. Remember
this sort of stuff?

\catcode`Æ=13 \defÆ{\AE}% handle Æ
\catcode`æ=13 \defæ{\ae}% handle æ
\catcode`ß=13 \defß{\ss}% handle ß
\catcode`è=13 \defè{\`e}% handle è
\catcode`Î=13 \defÎ{\^I}% handle Î
\catcode`Œ=13 \defŒ{\OE}% handle Œ
\catcode`œ=13 \defœ{\oe}% handle œ
\catcode`Ř=13 \defŘ{\v R}% handle Ř
\catcode`ř=13 \defř{\v r}% handle ř

I do remember \usepackage[utf8]{inputenc}, but even that has been
superceded by \RequirePackage{fontspec} (yes, I moved on from
using .sty files to .cls files about 5 years ago).

Apologies again.

Cheers,
David.

[guignol]Le Libre et l'Opensource, ça plait pas à tout le monde

[ZERO]

- " Les commentaires sont acceptés en raison de la liberté d’expression." mais 
ne sont pas utiles.
- "quelqu'un a eu 3 ans de prison (torture 24/24 7/7) pour avoir eu un ticket 
d'avion en sa possession, le code d'entré n'a pas plu : sa dna non-plus."
- debian 9 est dédié à murdock et des hackers/dev ont été arretés à la 
defconf/lasvegas.

C'est lié au recrutement dans les métiers de l'informatique et de la haute 
administration (la grèce des colonels -fonds placés pour la construction 
europeene- en est un exemple-.

la liberté d'expression, ça n'existe pas.
-- 
Take back your privacy. Switch to www.StartMail.com

Re: problème dkms et noyau 4.14.0-3-amd64

[jérémy prego]

Le 09/01/2018 à 22:43, Gaëtan Perrier a écrit :

Sûrement lié à ces rapports de bugs:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886474
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886506


en effet, j'ai du installer le paquet désigné dans le rapport de bug, 
avant d'avoir l'erreur que j'ai copié dans mon premier message.



et en effet, le noyau 4.14.0-3 vient de sid, effectivement, j'avais oublié ce 
détail :-)


pour répondre a Étienne, la réinstallation n'a pas résolu le problème, 
je vais rester sur le 4.14.0-2 pour le moment.


merci pour vos réponses !

jerem

Re: How to create a PDF-Printer from the command line

[David Wright]

On Tue 09 Jan 2018 at 20:47:44 (+), Curt wrote:
> On 2018-01-09, Brian  wrote:
> >
> > Oh. pdftex is now being fed a latex file, not a plain text file.
> > Previously:
> >
> > > pdftex will actually create a pdf out of a *text file*
> 
> That's right. No contradiction. I just added a data point.

Perhaps before this protracted, tangential and niggling subthread
becomes acrimonious or invidious, it might be easier to just state
than TeX/LaTeX is a useless way to turn a *text* file into a PDF.
And that's without discussing whether having to install a TeX system
is any better than installing LibreOffice.

Cheers,
David.

Re: How to create a PDF-Printer from the command line

[tomas]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Tue, Jan 09, 2018 at 02:09:22PM -0600, David Wright wrote:

[...]

> For me, this is a new take on document conversion methods.
> 
> FWIW my test file produced 30819 "Missing character" errors which
> is hardly surprising as TeX was released 40 years ago in the days
> of 7 bit ASCII. The PDF had a single line of characters running
> off the right hand side of the page.

Modern (La)TeX implementations should be able to cope with UTF-8
input: \usepackage[utf8]{inputenc} is one of the recommended magic
incantations (that said, reportedly Lua(La)TeX and Xe(La)TeX are
said to cope even better; they are part of your TeX live distribution
anyway).

Of course you have to make sure that your font supports the glyphs
you actually use.

Cheers
- -- tomás
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAlpVQEcACgkQBcgs9XrR2kZ8cwCfXZs1xEtELlztcEcAQ0Qxyk6q
Q+sAniPTYAwwYqfB8M1BZMIZjYOUlbBN
=Dtm9
-END PGP SIGNATURE-

Re: System won't boot anymore after upgrade to jessie

[deloptes]

Elisabetta Falivene wrote:

> I did an upgrade from debian 7 wheezy to debian 8 jessie on the master of
> a cluster (1 master + 8 nodes). It seemed all went well. Then I rebooted
> the machine and the problems began. I can't boot the master anymore
> returning an error:
> 
> *Running scripts/local-block*
> 
> *Unable to find LVM volume*
> 
> 
> *Running scripts/local-block*
> 
> *Unable to find LVM volume*

looks like initrd and/or udev

There were similar issues with upgrade from wheezy to jessie in my upgrades
as well.

I usually boot with usb stick and fix the initrd - you might need to
configure or reconfigure few things. the easiest to try is to recreate
initrd.

But as you did not provide any information how system is setup regarding
lvm, its just guessing

regards

Re: System won't boot anymore after upgrade to jessie

[Don Armstrong]

On Tue, 09 Jan 2018, Elisabetta Falivene wrote:

> Hi,
> I did an upgrade from debian 7 wheezy to debian 8 jessie on the master of a
> cluster (1 master + 8 nodes). It seemed all went well. Then I rebooted the
> machine and the problems began. I can't boot the master anymore returning
> an error:
> 
> *Running scripts/local-block*
> 
> *Unable to find LVM volume*

[...]
> *modprobe: module ehci-pci not found in modules.dep*

[...]

> Truly, it boots correctly with the old kernel 3.2, but not with 3.16.
> 
> In the kernel 3.16 case, moreover, when the initramfs prompt is shown, it
> seems not to load the usb keyboard so i'm truly able to do anything.

This sounds like the initramfs doesn't have the appropriate modules
built into it.

I suspect that your /etc/initramfs-tools/initramfs.conf has MODULES=dep.
You should try changing that to MODULES=most; and then rebuild the
initramfs using something like:

update-initramfs -vu;

This should provide information on the modules that are being added to
the initramfs, which should include the lvm modules and the ehci
modules. [The missing ehci/ohci modules are likely what is causing your
USB keyboard to not work.]

-- 
Don Armstrong  https://www.donarmstrong.com

The major difference between a thing that might go wrong and a thing
that cannot possibly go wrong is that when a thing that cannot
possibly go wrong goes wrong it usually turns out to be impossible to
get at or repair.
 -- Douglas Adams  _Mostly Harmless_

Re: problème dkms et noyau 4.14.0-3-amd64

[Gaëtan Perrier]

Le mardi 09 janvier 2018 à 20:46 +0100, jérémy prego a écrit :
> bonjour,
> 
> depuis la sortie du noyau 4.14.0-3 sur ma testing, 

Testing est encore en 4.14.0-2 à ma connaissance.

Gaëtan

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

Re: problème dkms et noyau 4.14.0-3-amd64

[Gaëtan Perrier]

Le mardi 09 janvier 2018 à 20:46 +0100, jérémy prego a écrit :
> bonjour,
> 
> depuis la sortie du noyau 4.14.0-3 sur ma testing, il n'arrive plus a 
> compiler avec dkms. voici un extrait du message que je reçois:
> 
> Les paquets suivants seront RÉINSTALLÉS :
>linux-headers-4.14.0-3-amd64
> 0 paquets mis à jour, 0 nouvellement installés, 1 réinstallés, 0 à 
> enlever et 0 non mis à jour.
> Il est nécessaire de télécharger 0 o/465 ko d'archives. Après 
> dépaquetage, 0 o seront utilisés.
> (Lecture de la base de données... 127240 fichiers et répertoires déjà 
> installés.)
> Préparation du dépaquetage de 
> .../linux-headers-4.14.0-3-amd64_4.14.12-2_amd64.deb ...
> Dépaquetage de linux-headers-4.14.0-3-amd64 (4.14.12-2) sur (4.14.12-2) ...
> Paramétrage de linux-headers-4.14.0-3-amd64 (4.14.12-2) ...
> /etc/kernel/header_postinst.d/dkms:
> Error! Bad return status for module build on kernel: 4.14.0-3-amd64 (x86_64)
> Consult /var/lib/dkms/bbswitch/0.8/build/make.log for more information.
> 
> bon, du coup, je vais voir le log en question, et on y trouve:
> 
> DKMS make.log for bbswitch-0.8 for kernel 4.14.0-3-amd64 (x86_64)
> mardi 9 janvier 2018, 20:39:37 (UTC+0100)
> make -C /lib/modules/4.14.0-3-amd64/build M="$(pwd)" modules
> make[1] : on entre dans le répertoire 
> « /usr/src/linux-headers-4.14.0-3-amd64 »
> make[4]: ***  Aucune règle pour fabriquer la cible 
> « tools/objtool/objtool », nécessaire pour 
> « /var/lib/dkms/bbswitch/0.8/build/bbswitch.o ». Arrêt.
> /usr/src/linux-headers-4.14.0-3-common/Makefile:1525 : la recette pour 
> la cible « _module_/var/lib/dkms/bbswitch/0.8/build » a échouée
> make[3]: *** [_module_/var/lib/dkms/bbswitch/0.8/build] Erreur 2
> Makefile:146 : la recette pour la cible « sub-make » a échouée
> make[2]: *** [sub-make] Erreur 2
> Makefile:8 : la recette pour la cible « all » a échouée
> make[1]: *** [all] Erreur 2
> make[1] : on quitte le répertoire « /usr/src/linux-headers-4.14.0-3-amd64 »
> Makefile:13 : la recette pour la cible « default » a échouée
> make: *** [default] Erreur 2.
> 
> ça semble être la même erreur pour tous les autres modules, et sur le 
> net, j'ai rien trouvé de parlant pour moi ... ça fonctionne nickel avec 
> le noyau d'avant, le 4.14.0-2...
> 
> merci d'avance à vous, si vous savez.
> 
> jerem

Sûrement lié à ces rapports de bugs:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886474
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886506

Gaëtan


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

Re: problème dkms et noyau 4.14.0-3-amd64

[Étienne Mollier]

Jérémy Prego, le 2018-01-09:
> bonjour,
>
> depuis la sortie du noyau 4.14.0-3 sur ma testing, il n'arrive
> plus a compiler avec dkms. voici un extrait du message que je
> reçois:
>
> Les paquets suivants seront RÉINSTALLÉS :
>   linux-headers-4.14.0-3-amd64
[...]
> /etc/kernel/header_postinst.d/dkms:
> Error! Bad return status for module build on kernel: 4.14.0-3-amd64 (x86_64)
> Consult /var/lib/dkms/bbswitch/0.8/build/make.log for more information.
>
> bon, du coup, je vais voir le log en question, et on y trouve:
>
[...]
> make[1] : on entre dans le répertoire « /usr/src/linux-headers-4.14.0-3-amd64 
> »
> make[4]: ***  Aucune règle pour fabriquer la cible « tools/objtool/objtool », 
> nécessaire pour « /var/lib/dkms/bbswitch/0.8/build/bbswitch.o ». Arrêt.
[...]

Bonsoir,

Depuis une Debian Sid, si je tente de fabriquer à blanc la cible
« tools/objtool/objtool », j'arrive un peu plus loin (pas
beaucoup plus, en tant que simple utilisateur :-)

$ cd /usr/src/linux-headers-4.14.0-3-amd64
$ make tools/objtool/objtool
arch/x86/Makefile:156: CONFIG_X86_X32 enabled but no binutils support
/usr/src/linux-headers-4.14.0-3-common/scripts/Makefile.build:45: 
/usr/src/linux-headers-4.14.0-3-common/scripts/basic/Makefile: No such file or 
directory
mkdir: cannot create directory ‘scripts’: Permission denied
[...]

Le packaging des headers est un peu particulier, et peut-être que
quelque chose s'est mal passé précédemment dans
/usr/src/linux-headers-4.14.0-3-common/ ou linux-kbuild-4.14/
lors de la mise à jour.

Je vois la mention RÉINSTALLÉS dans votre copie d'écran,
pouvez vous tenter de réinstaller dans l'ordre :
linux-headers-4.14.0-3-common
linux-headers-4.14.0-3-amd64
si ça peut aider à rétablir la situation ?

À plus,
-- 
Étienne Mollier 

System won't boot anymore after upgrade to jessie

[Elisabetta Falivene]

Hi,
I did an upgrade from debian 7 wheezy to debian 8 jessie on the master of a
cluster (1 master + 8 nodes). It seemed all went well. Then I rebooted the
machine and the problems began. I can't boot the master anymore returning
an error:

*Running scripts/local-block*

*Unable to find LVM volume*


*Running scripts/local-block*

*Unable to find LVM volume*


*... (lot of times)*








*gave up waiting for root device. Common problems:- Boot args (cat
/proc/cmdline)- check rootdelay= (did the sistem wait long enouth?)- check
root= (did the sistem wait for the right device?)- missing modules (cat
/proc/modules; ls /dev)ALERT! /dev/mapper/system-root does not exist.
Dropping to a shell!"*
*modprobe: module ehci-pci not found in modules.dep*

*modprobe: module ehci-orion not found in modules.dep*

*modprobe: module ehci-hcd not found in modules.dep*

*modprobe: module ohci-hcd not found in modules.dep*

*Busybox v1.22.1 (Debian 1:1.22.0-9+deb8u1) built-in shell (ash)*
*Enter help for a list of built-in commands*


* /bin/sh can't access tty job control turned off  *
*(initramfs)*

Anyway, in grub there are two available kernel to boot

*kernel 3.2.0-4-amd64*

*kernel 3.16.0-4-amd64 (that is **3.16.43-2 kernel**)*


Truly, it boots correctly with the old kernel 3.2, but not with 3.16.

In the kernel 3.16 case, moreover, when the initramfs prompt is shown, it
seems not to load the usb keyboard so i'm truly able to do anything. I
tried to boot in 3.16 recovery mode and I get the same error. lvm2 module
is installed and up to date. The system has 6 hard disk in raid as far as i
know.


What is happening?

Thank you very much

Elisabetta

Re: How to create a PDF-Printer from the command line

[Curt]

On 2018-01-09, Brian  wrote:
>
> Oh. pdftex is now being fed a latex file, not a plain text file.
> Previously:
>
> > pdftex will actually create a pdf out of a *text file*

That's right. No contradiction. I just added a data point.


-- 
"Ruling a large nation is like cooking a small fish" - Lao Tzu

Re: Poner fondo en color blanco en la consola (BASH) de Debian 9.3.0 Net-install (sin entorno gráfico)

[Lividineitor]

Actualizo la información.


En Wikipedia:


https://en.wikipedia.org/wiki/ANSI_escape_code#graphics


Aprece lo siguiente, si tu terminal tolera el color verdadero "True 
color", puedes usar para el color de texto "38;2..." en vez de "38;5..." 
ya que esto te premite especificar el color RGB para desplegar en tu 
terminal, recordando que 38 es para el frente (letras) y 48 para el fondo.



Ejemplo:


PS1='${debian_chroot:+($debian_chroot)}\[\033[*48;2;249;40;105*m\]\u@\h\[\033[00m\]:\[\033[01;34m\]\w\[\033[00m\]\$ 
'


Creo que no lo soporta la TTY de Debian, pero los emuladores como 
xfce4-terminal sí.


Se debe especificar cada canal con su valor correspodiente de 0-255, en 
el ejemplo fue Rojo=249, Verde=40 y Azul=105, puedes usar la aplicación 
"gcolor2" para obtener dichos valores, pero requieres un entorno gráfico.

Re: Poner fondo en color blanco en la consola (BASH) de Debian 9.3.0 Net-install (sin entorno gráfico)

[Bienvenido Sánchez Robles]

Gracias Lividineitor por tu aportación.

Anoche, tras varios días investigando y probando cosas, ya lo hemos
resuelto.

Mira aquí: https://exdebian.org/comment/4586#comment-4586

El 9 de enero de 2018, 21:29, Lividineitor 
escribió:

> Hola, no hago esto seguido, espero que sí se conteste de está manera.
>
>
> Bueno, puede ser que exista una solución más elegante, pero al menos
> funciona.
>
>
> Buscando un poco, encontré lo siguiente:
>
>
> https://bbs.archlinux.org/viewtopic.php?id=167717
>
>
>  Coincide con el enlace que tú tienes:
>
>
> https://wiki.archlinux.org/index.php/User:Isacdaavid/Linux_Console
>
>
> En la sección donde dice "if [ "$TERM" = "linux" ]; then..." aparecen los
> comandos de "echo" con los que puedes modificar el color. Fíjate que en la
> línea dos está el cambio de color de fondo, que prácticamente redefine el
> valor de la variable para el color de fondo. Cabe remarcar que debes ser
> cuidadoso al cambiar los colores, ya que si pones el fondo del mismo color
> que tu texto activo, todo se va a ver del mismo color, pero basta con
> cambiar de tty (Ctrl+Alt+F1-6). Por otro lado, si modificas la línea de
> PS1, como dice uno de tus enlaces, el color de fondo que elijas no cambia
> si nada más modificas los colores del texto, lo que es cómodo si ya tienes
> el color deseado, pero también se puede cambiar el color de fondo
> directamente ahí, usando los valores como dice en:
>
>
> https://misc.flogisoft.com/bash/tip_colors_and_formatting
>
>
> También recuerda que si haces un cambio de color tienes que recargar bash
> y si el cambio aparece de manera automática, como en el caso de usar el
> comando "echo", es bueno usar el comando "clear" para "refrescar" la
> pantalla del tty.
>
>
> Por otro lado:
>
>
> if [ "$TERM" = "linux" ]; then
> echo -en "\e]P022" #black-> this is the background color as
> well.
> echo -en "\e]P1803232" #darkred
> echo -en "\e]P25b762f" #darkgreen
> echo -en "\e]P3aa9943" #brown
> echo -en "\e]P4324c80" #darkblue
> echo -en "\e]P5706c9a" #darkmagenta
> echo -en "\e]P692b19e" #darkcyan
> echo -en "\e]P7ff" #lightgray
> echo -en "\e]P822" #darkgray
> echo -en "\e]P9982b2b" #red
> echo -en "\e]PA89b83f" #green
> echo -en "\e]PBefef60" #yellow
> echo -en "\e]PC2b4f98" #blue
> echo -en "\e]PD826ab1" #magenta
> echo -en "\e]PEa1cdcd" #cyan
> echo -en "\e]PFdedede" #white-> this is the foreground color as
> well.
> clear  #repaint the whole background with the new color
> fi
>
>
> Modifica el color asociado a los 16 colores básicos que asignan a las
> secuencias de escape ANSI del 30-37 y 90-97 (que son las que aparecen en el
> primero de tus enlaces ^-^¡), por lo que puedes usar las secuencias para
> 256 colores.
>
>
> Ahora, en qué parte están definidos los valores para cada uno de los 256
> colores?, personalmente lo busqué hace tiempo y no encontré la solución,
> pero supongo que sería en el mismo lugar en donde los comandos "echo"
> realizan el cambio.
>
>
> Recuerda que al reiniciar el sistema, los colores establecidos con el
> comando "echo" regresan a los valores por defecto. Y para cabiar el color
> de fondo nada más requieres escribir echo -en "\e]P0##", donde los
> símbolos # son para el valor hexadecimal del color que buscas "ff".
>
>
> Lo probé en mi equipo y finciona, los cambios se aplican en la TTY que
> estás ejecutando hasta que los definas en tu .bashrc.
>
>

Re: How to create a PDF-Printer from the command line

[Brian]

On Tue 09 Jan 2018 at 20:36:23 +, Brian wrote:

> I am not playing your games. Exotica is outside my field of interest.
   ^ 
   ^are

Just in case there is a nitpick.

-- 
Brian.

Re: How to create a PDF-Printer from the command line

[Brian]

On Tue 09 Jan 2018 at 19:41:35 +, Curt wrote:

> On 2018-01-09, Brian  wrote:
> >
> > There are quite a few in this thread. Clue us in?
> 
> The person who responded directly to David's question quoted above,
> whose name, exotic in the regions from which I hail, escapes my
> remembrance.

I am not playing your games. Exotica is outside my field of interest.
Your private life is your own.
 
> >> pdftex will actually create a pdf out of a text file without complaint
> >> if you put '\end' on a newline at the end of the text file (I wouldn't
> >> recommend such a bare-bones approach, though, in my extremely limited
> >> experience, for formatting reasons). Or you can just type '\end' in the
> >> little interactive mode that comes up in the terminal when errors or
> >> omissions are encountered.
> >
> > My pdftex complained madly about this and eventually threw the towel
> > in.
> 
> I can't account for it. If I feed pdftex a latex file, it whines for
> every latex command it encounters, but if I press enter on each
> encountered command error in the interactive console (if that is indeed
> the term for it) it eventually exits completely (maybe it wants me to
> '\end') , producing a pdf file (the text of which comprises both the
> unknown latex commands as plain old text as well as the text as, well,
> pdf-style text, if you catch my drift).

Oh. pdftex is now being fed a latex file, not a plain text file.
Previously:

 > pdftex will actually create a pdf out of a *text file*

(The "*"s are mine. Just in case you fail to notice we are talking
about different things).

Boats. Midstrem.

> >> All roads lead to Rome, I reckon.
> >
> > You always learn something new on this list. I thought it was Grimsby.

On second thoughts (everyone can have them), maybe it was Scunthorpe.

-- 
Brian.

Re: Poner fondo en color blanco en la consola (BASH) de Debian 9.3.0 Net-install (sin entorno gráfico)

[Lividineitor]

Hola, no hago esto seguido, espero que sí se conteste de está manera.


Bueno, puede ser que exista una solución más elegante, pero al menos 
funciona.



Buscando un poco, encontré lo siguiente:


https://bbs.archlinux.org/viewtopic.php?id=167717


 Coincide con el enlace que tú tienes:


https://wiki.archlinux.org/index.php/User:Isacdaavid/Linux_Console


En la sección donde dice "if [ "$TERM" = "linux" ]; then..." aparecen 
los comandos de "echo" con los que puedes modificar el color. Fíjate que 
en la línea dos está el cambio de color de fondo, que prácticamente 
redefine el valor de la variable para el color de fondo. Cabe remarcar 
que debes ser cuidadoso al cambiar los colores, ya que si pones el fondo 
del mismo color que tu texto activo, todo se va a ver del mismo color, 
pero basta con cambiar de tty (Ctrl+Alt+F1-6). Por otro lado, si 
modificas la línea de PS1, como dice uno de tus enlaces, el color de 
fondo que elijas no cambia si nada más modificas los colores del texto, 
lo que es cómodo si ya tienes el color deseado, pero también se puede 
cambiar el color de fondo directamente ahí, usando los valores como dice en:



https://misc.flogisoft.com/bash/tip_colors_and_formatting


También recuerda que si haces un cambio de color tienes que recargar 
bash y si el cambio aparece de manera automática, como en el caso de 
usar el comando "echo", es bueno usar el comando "clear" para 
"refrescar" la pantalla del tty.



Por otro lado:


if [ "$TERM" = "linux" ]; then
    echo -en "\e]P022" #black    -> this is the background color as 
well.

    echo -en "\e]P1803232" #darkred
    echo -en "\e]P25b762f" #darkgreen
    echo -en "\e]P3aa9943" #brown
    echo -en "\e]P4324c80" #darkblue
    echo -en "\e]P5706c9a" #darkmagenta
    echo -en "\e]P692b19e" #darkcyan
    echo -en "\e]P7ff" #lightgray
    echo -en "\e]P822" #darkgray
    echo -en "\e]P9982b2b" #red
    echo -en "\e]PA89b83f" #green
    echo -en "\e]PBefef60" #yellow
    echo -en "\e]PC2b4f98" #blue
    echo -en "\e]PD826ab1" #magenta
    echo -en "\e]PEa1cdcd" #cyan
    echo -en "\e]PFdedede" #white    -> this is the foreground color as 
well.

    clear  #repaint the whole background with the new color
fi


Modifica el color asociado a los 16 colores básicos que asignan a las 
secuencias de escape ANSI del 30-37 y 90-97 (que son las que aparecen en 
el primero de tus enlaces ^-^¡), por lo que puedes usar las secuencias 
para 256 colores.



Ahora, en qué parte están definidos los valores para cada uno de los 256 
colores?, personalmente lo busqué hace tiempo y no encontré la solución, 
pero supongo que sería en el mismo lugar en donde los comandos "echo" 
realizan el cambio.



Recuerda que al reiniciar el sistema, los colores establecidos con el 
comando "echo" regresan a los valores por defecto. Y para cabiar el 
color de fondo nada más requieres escribir echo -en "\e]P0##", donde 
los símbolos # son para el valor hexadecimal del color que buscas "ff".



Lo probé en mi equipo y finciona, los cambios se aplican en la TTY que 
estás ejecutando hasta que los definas en tu .bashrc.

Re: How to create a PDF-Printer from the command line

[David Wright]

On Tue 09 Jan 2018 at 19:41:35 (+), Curt wrote:
> On 2018-01-09, Brian  wrote:
> >> >> 
> >> >> If you're dealing with latex files, as I have taken some minutes to
> >> >> discover (cough), you need 'pdflatex', not pdftex, which will barf
> >> >> immediately upon encountering latex commands.
> >> >
> >> > So could you now elaborate on step 1 of this "one-step" process?
> >> >
> >> > Cheers,
> >> > David.
> >> 
> >> Like the other, more knowledgeable guy said.
> >
> > There are quite a few in this thread. Clue us in?
> 
> The person who responded directly to David's question quoted above,
> whose name, exotic in the regions from which I hail, escapes my
> remembrance.
> 
> >> pdftex will actually create a pdf out of a text file without complaint
> >> if you put '\end' on a newline at the end of the text file (I wouldn't
> >> recommend such a bare-bones approach, though, in my extremely limited
> >> experience, for formatting reasons). Or you can just type '\end' in the
> >> little interactive mode that comes up in the terminal when errors or
> >> omissions are encountered.
> >
> > My pdftex complained madly about this and eventually threw the towel
> > in.
> 
> I can't account for it. If I feed pdftex a latex file, it whines for
> every latex command it encounters, but if I press enter on each
> encountered command error in the interactive console (if that is indeed
> the term for it) it eventually exits completely (maybe it wants me to
> '\end') , producing a pdf file (the text of which comprises both the
> unknown latex commands as plain old text as well as the text as, well,
> pdf-style text, if you catch my drift).

For me, this is a new take on document conversion methods.

FWIW my test file produced 30819 "Missing character" errors which
is hardly surprising as TeX was released 40 years ago in the days
of 7 bit ASCII. The PDF had a single line of characters running
off the right hand side of the page.

Cheers,
David.

problème dkms et noyau 4.14.0-3-amd64

[jérémy prego]

bonjour,

depuis la sortie du noyau 4.14.0-3 sur ma testing, il n'arrive plus a 
compiler avec dkms. voici un extrait du message que je reçois:


Les paquets suivants seront RÉINSTALLÉS :
  linux-headers-4.14.0-3-amd64
0 paquets mis à jour, 0 nouvellement installés, 1 réinstallés, 0 à 
enlever et 0 non mis à jour.
Il est nécessaire de télécharger 0 o/465 ko d'archives. Après 
dépaquetage, 0 o seront utilisés.
(Lecture de la base de données... 127240 fichiers et répertoires déjà 
installés.)
Préparation du dépaquetage de 
.../linux-headers-4.14.0-3-amd64_4.14.12-2_amd64.deb ...

Dépaquetage de linux-headers-4.14.0-3-amd64 (4.14.12-2) sur (4.14.12-2) ...
Paramétrage de linux-headers-4.14.0-3-amd64 (4.14.12-2) ...
/etc/kernel/header_postinst.d/dkms:
Error! Bad return status for module build on kernel: 4.14.0-3-amd64 (x86_64)
Consult /var/lib/dkms/bbswitch/0.8/build/make.log for more information.

bon, du coup, je vais voir le log en question, et on y trouve:

DKMS make.log for bbswitch-0.8 for kernel 4.14.0-3-amd64 (x86_64)
mardi 9 janvier 2018, 20:39:37 (UTC+0100)
make -C /lib/modules/4.14.0-3-amd64/build M="$(pwd)" modules
make[1] : on entre dans le répertoire 
« /usr/src/linux-headers-4.14.0-3-amd64 »
make[4]: ***  Aucune règle pour fabriquer la cible 
« tools/objtool/objtool », nécessaire pour 
« /var/lib/dkms/bbswitch/0.8/build/bbswitch.o ». Arrêt.
/usr/src/linux-headers-4.14.0-3-common/Makefile:1525 : la recette pour 
la cible « _module_/var/lib/dkms/bbswitch/0.8/build » a échouée

make[3]: *** [_module_/var/lib/dkms/bbswitch/0.8/build] Erreur 2
Makefile:146 : la recette pour la cible « sub-make » a échouée
make[2]: *** [sub-make] Erreur 2
Makefile:8 : la recette pour la cible « all » a échouée
make[1]: *** [all] Erreur 2
make[1] : on quitte le répertoire « /usr/src/linux-headers-4.14.0-3-amd64 »
Makefile:13 : la recette pour la cible « default » a échouée
make: *** [default] Erreur 2.

ça semble être la même erreur pour tous les autres modules, et sur le 
net, j'ai rien trouvé de parlant pour moi ... ça fonctionne nickel avec 
le noyau d'avant, le 4.14.0-2...


merci d'avance à vous, si vous savez.

jerem

Re: How to create a PDF-Printer from the command line

[Curt]

On 2018-01-09, Brian  wrote:
>> >> 
>> >> If you're dealing with latex files, as I have taken some minutes to
>> >> discover (cough), you need 'pdflatex', not pdftex, which will barf
>> >> immediately upon encountering latex commands.
>> >
>> > So could you now elaborate on step 1 of this "one-step" process?
>> >
>> > Cheers,
>> > David.
>> 
>> Like the other, more knowledgeable guy said.
>
> There are quite a few in this thread. Clue us in?

The person who responded directly to David's question quoted above,
whose name, exotic in the regions from which I hail, escapes my
remembrance.

>> pdftex will actually create a pdf out of a text file without complaint
>> if you put '\end' on a newline at the end of the text file (I wouldn't
>> recommend such a bare-bones approach, though, in my extremely limited
>> experience, for formatting reasons). Or you can just type '\end' in the
>> little interactive mode that comes up in the terminal when errors or
>> omissions are encountered.
>
> My pdftex complained madly about this and eventually threw the towel
> in.

I can't account for it. If I feed pdftex a latex file, it whines for
every latex command it encounters, but if I press enter on each
encountered command error in the interactive console (if that is indeed
the term for it) it eventually exits completely (maybe it wants me to
'\end') , producing a pdf file (the text of which comprises both the
unknown latex commands as plain old text as well as the text as, well,
pdf-style text, if you catch my drift).

>> All roads lead to Rome, I reckon.
>
> You always learn something new on this list. I thought it was Grimsby.
>


-- 
"Ruling a large nation is like cooking a small fish" - Lao Tzu

Re: How to create a PDF-Printer from the command line

[Brian]

On Tue 09 Jan 2018 at 15:29:08 +, Curt wrote:

> On 2018-01-09, David Wright  wrote:
> >> 
> >> If you're dealing with latex files, as I have taken some minutes to
> >> discover (cough), you need 'pdflatex', not pdftex, which will barf
> >> immediately upon encountering latex commands.
> >
> > So could you now elaborate on step 1 of this "one-step" process?
> >
> > Cheers,
> > David.
> >
> >
> 
> Like the other, more knowledgeable guy said.

There are quite a few in this thread. Clue us in?

> pdftex will actually create a pdf out of a text file without complaint
> if you put '\end' on a newline at the end of the text file (I wouldn't
> recommend such a bare-bones approach, though, in my extremely limited
> experience, for formatting reasons). Or you can just type '\end' in the
> little interactive mode that comes up in the terminal when errors or
> omissions are encountered.

My pdftex complained madly about this and eventually threw the towel in.
 
> All roads lead to Rome, I reckon.

You always learn something new on this list. I thought it was Grimsby.

-- 
Brian.

Re: Problème de configuration de carte son

[BERTRAND Joël]

MERLIN Philippe a écrit :

Le mardi 9 janvier 2018, 16:29:53 CET BERTRAND Joël a écrit :

Bon, ça progresse :

Linux est un peu bête et considère que la carte par défaut est celle
qui a l'id de périphérique à 0 (indépendamment du numéro de carte s'il
n'y a qu'un seul ip de périphérique nul.). On va dire que c'est une feature.

aplay -D plughw:0,3 /usr/share/sounds/alsa/Front_Center.wav
=> son sur l'écran droit

aplay -D plughw:0,7 /usr/share/sounds/alsa/Front_Center.wav
=> son sur l'écran gauche

La question est maintenant de savoir (outre comment régler le volume)
comment faire comprendre au système qu'il doit utiliser par défaut cette
interface.

Je sais comment forcer une carte plutôt qu'une autre, mais comment
forcer une interface de carte ?

Bien cordialement,

JKB


alsamixer ?
Philippe Merlin


	Marche pas. C'est la première chose que j'ai essayée. J'ai l'impression 
que l'interface par défaut est celle qui est notée 0,0. Or je n'ai pas 
de 0,0 sur mon système, mais un 0,3, un 0,7 et à la rigueur un 1,0.


	Remarque bien, ça risque de se terminer avec l'interface PCM à 
l'ancienne... puisque je ne sais pas pourquoi, mais je n'arrive pas à 
régler le volume des interfaces numériques.


Cordialement,

JKB

Re: Problème de configuration de carte son

[MERLIN Philippe]

Le mardi 9 janvier 2018, 16:29:53 CET BERTRAND Joël a écrit :
>   Bon, ça progresse :
> 
>   Linux est un peu bête et considère que la carte par défaut est celle
> qui a l'id de périphérique à 0 (indépendamment du numéro de carte s'il
> n'y a qu'un seul ip de périphérique nul.). On va dire que c'est une feature.
> 
> aplay -D plughw:0,3 /usr/share/sounds/alsa/Front_Center.wav
> => son sur l'écran droit
> 
> aplay -D plughw:0,7 /usr/share/sounds/alsa/Front_Center.wav
> => son sur l'écran gauche
> 
>   La question est maintenant de savoir (outre comment régler le volume)
> comment faire comprendre au système qu'il doit utiliser par défaut cette
> interface.
> 
>   Je sais comment forcer une carte plutôt qu'une autre, mais comment
> forcer une interface de carte ?
> 
>   Bien cordialement,
> 
>   JKB

alsamixer ?
Philippe Merlin

Re: Noms partitions /dev/sdaX modifiés en /dev/sdcX : résolu

[Eric Degenetais]

Le 9 janv. 2018 3:36 PM, "Pierre L."  a écrit :



Le 09/01/2018 à 12:57, hamster a écrit :
> mais toi tu manque de bienveillance.
>
Cette réponse manque elle aussi un peu de "bienveillance" :p
Bien à vous.

Le problème de communication est bien regrettable, car si "mv /dev/sdc
/dev/sda" semble fonctionner sans effet secondaire (je ne m'y risquerais
pas pour ma part), au prochain reboot les noms de partition vont rechanger.
En conséquence, s'il y a des liens techniques explicites vers /dev/sda, ils
vont casser, avec des conséquences +/- graves.

Re: vbox cannot find headers, although they are installed

[Curt]

On 2018-01-07, Harry Putnam  wrote:
>
> Building the main Guest Additions module ...fail!
> (Look at /var/log/vboxadd-install.log to find out what went wrong)
> Doing non-kernel setup of the Guest Additions ...done.
>

You have performed

 apt-get install build-essential module-assistant

and

 m-a prepare

as suggested by virtualboxes.org?

-- 
"Ruling a large nation is like cooking a small fish" - Lao Tzu

Re: UID 1000 on Raspberry Pi (Was: Re: Embarrassing security bug in systemd)

[Christian Groessler]

On 01/09/18 16:01, Roberto C. Sánchez wrote:

Don't forget about occurrences of 'pi' in the group files (use 'vigr'
and 'vigr -s' to catch those).



Yep. Forgot to mention that.

regards,
chris

Re: old Wheezy will not upgrade linux-kernel

[Greg Wooledge]

On Tue, Jan 09, 2018 at 06:51:22AM +, Bonno Bloksma wrote:
> I understand the difference between upgrade and dist-upgrade, but could not 
> find a reason for needing dist-upgrade

A new package is being installed.

RE: old Wheezy will not upgrade linux-kernel

[Bonno Bloksma]

Hello Roberto,


>> After apt-get update I do an upgrade and it seems the kernel package 
>> will not install but is held back [] 
>> # apt-get upgrade -V The following packages have been kept back:
>>linux-image-686-pae (3.2+46 => 3.2+46+deb7u1)

[]

I understand the difference between upgrade and dist-upgrade, but could not 
find a reason for needing dist-upgrade

> The reason that you are encountering this issue is because the changes to the 
> kernel necessitated an ABI change. 
> The Linux kernel package name includes the ABI version to allow you to have 
> multiple versions of the same 
> kernel with different ABIs. 
> Plus, it makes it easy to boot back into the previous version with any custom 
> built modules (e.g., through
> DKMS) that may not work or be built for the new kernel ABI.

Ok, so it is not a dependency in the kernel module itself but more everything 
else that is dependent on it. Ok now I understand the reason for dist-upgrade.
In my mind I could find anything the kernel was dependent on so why would it be 
held back due to a dependency issue

Bonno Bloksma

Re: How to create a PDF-Printer from the command line

[Curt]

On 2018-01-09, David Wright  wrote:
>> 
>> If you're dealing with latex files, as I have taken some minutes to
>> discover (cough), you need 'pdflatex', not pdftex, which will barf
>> immediately upon encountering latex commands.
>
> So could you now elaborate on step 1 of this "one-step" process?
>
> Cheers,
> David.
>
>

Like the other, more knowledgeable guy said.

pdftex will actually create a pdf out of a text file without complaint
if you put '\end' on a newline at the end of the text file (I wouldn't
recommend such a bare-bones approach, though, in my extremely limited
experience, for formatting reasons). Or you can just type '\end' in the
little interactive mode that comes up in the terminal when errors or
omissions are encountered.

All roads lead to Rome, I reckon.

-- 
"Ruling a large nation is like cooking a small fish" - Lao Tzu

Re: Problème de configuration de carte son

[BERTRAND Joël]

Bon, ça progresse :

	Linux est un peu bête et considère que la carte par défaut est celle 
qui a l'id de périphérique à 0 (indépendamment du numéro de carte s'il 
n'y a qu'un seul ip de périphérique nul.). On va dire que c'est une feature.


aplay -D plughw:0,3 /usr/share/sounds/alsa/Front_Center.wav
=> son sur l'écran droit

aplay -D plughw:0,7 /usr/share/sounds/alsa/Front_Center.wav
=> son sur l'écran gauche

	La question est maintenant de savoir (outre comment régler le volume) 
comment faire comprendre au système qu'il doit utiliser par défaut cette 
interface.


	Je sais comment forcer une carte plutôt qu'une autre, mais comment 
forcer une interface de carte ?


Bien cordialement,

JKB

Re: Managing font size issues between apps

[tony mollica]

Thanks.

I'll look through the info in the links and continue the font fight.
I'm feeling like the only reason to post here is to complain, but after 
using Debian for over twenty years, meaning Linux in general and the 
endless configurability claims (yeah, I can get it to look just like 
windoze), I still can't resolve font size issues between panels within 
an application much less between two or more apps running at the same time.
I think everyone knows the issue.  It appears there's no real resolution 
or easy config in place.  So not to take up any more bandwidth I'll 
consider this thread finished.


Thanks again,
Tony

On 01/08/2018 01:14 PM, Felix Miata wrote:

tony mollica composed on 2018-01-08 09:29 (UTC-0800):


I'd like to find out how users are managing the font size issues between
applications.
What prompts me to ask is applying system or application updates
sometimes changes the display of fonts, some larger, some smaller, both
between applications and also within the applications, Thunderbird being
one of the worst.

Am I missing some configuration utility or is this still a widespread
problem?


Focusing on TB, because it's a Mozilla.org application, yes, it is a common
problem. Factors affecting fonts include, but are not limited to:

1-which DE or WM you are using

2-which themes you have installed

3-source of the package that provided the application

4-physical display density

5-logical display density

6-toolkit used to build application

I don't use TB, but I do use other mozilla.org apps, some provided by the
distribution, some provided directly from mozilla.org.

Subject to correction by those using TB or otherwise having better knowledge:
1-TB 45 upstream was still using the mature GTK2 tookit, which had ample, mature
theme support. TB 52 upstream has been switched to GTK3, with more limited theme
support.
2-Individual Linux distros still have the option with 52 to build using GTK2, as
do those self-compiling TB.

One method of managing fonts in TB is described here:
http://kb.mozillazine.org/index.php?title=UserChrome.css=yes
http://kb.mozillazine.org/Pane_and_menu_fonts

Re: UID 1000 on Raspberry Pi (Was: Re: Embarrassing security bug in systemd)

[Roberto C . Sánchez]

On Tue, Jan 09, 2018 at 03:04:03PM +0100, Christian Groessler wrote:
> On 01/09/18 04:49, Jason wrote:
> > > This I'd guess is important, if you have several users. I don't, except
> > > for amanda and nut, and thats only on this machine. All the rest have
> > > one user, me, known under various aliases because the idiot installer is
> > > now set to give the first user the machines name like pi or rock64. I
> > > spent a month trying to fix user 1000 to be me instead of pi on the pi.
> > On the Pi, this is what worked for me:
> > 
> > 1. Add a new user (and add him to group sudo). This user gets ID 1001.
> > $ sudo adduser tempuser
> > $ sudo adduser tempuser sudo
> > 
> > 2. Log out of user pi and log in as the newly created user.
> > 3. Delete user pi (pi must not have any processes running)
> > $ sudo deluser pi
> > 
> > 4. Add the desired username:
> > $ sudo adduser gene
> 
> 
> I just edited the password file directly, "vipw" and "vipw -s", and renamed
> the pi user.
> 
Don't forget about occurrences of 'pi' in the group files (use 'vigr'
and 'vigr -s' to catch those).

Regards,

-Roberto

-- 
Roberto C. Sánchez

Re: Problème de configuration de carte son

[BERTRAND Joël]

Haricophile a écrit :

Le Tue, 9 Jan 2018 09:53:47 +0100,
BERTRAND Joël  a écrit :


Bonjour à tous,

Je suis en train de m'installer un nouveau poste de travail
(carte-mère thin mini ITX de récupération Asus Q87T, i7 4790, 16 Go
de mémoire, biécran HDMI/DP). Tout fonctionne sauf la configuration
de la carte son. J'aimerais que le son sorte par les deux interfaces
DP et HDMI (si ce n'est pas possible par l'une des deux par défaut).

J'ai viré pulseaudio qui dysfonctionne généralement à pleins
tubes pour ne garder qu'Alsa (avec l'émulation OSS).


Dommage, pulseaudio sait faire ;)

Tu peux peut-être regarder du côté de jack si tu cherches quelque
chose d'un peu moins automatisme pour grand public que pulseaudio.

https://linuxmao.org/Jack


Si j'ai bien compris la doc que j'ai lue, la carte 0 est la
carte par défaut du système. Or il n'en est rien :


https://debian-facile.org/doc:materiel:cartes-son:depannage


	Merci, ça fait partie des nombreux sites que j'ai lus... :-( Sans 
résultat d'ailleurs. La carte 0 est bien la sortie HDMI, la carte 1, la 
sortie analogique.


	La question est : "pourquoi la carte 0 n'est-elle pas prise par défaut 
?" sachant que je n'ai aucun moyen de supprimer la carte PCM ou de jouer 
sur les pilotes...


	La question subsidiaire est "comment régler le volume sans 
tripatouiller les boutons des écrans ?"


Cordialement,

JKB

Re: How to create a PDF-Printer from the command line

[Ionel Mugurel Ciobîcă]

On  9-01-2018, at 07h 35'28", David Wright wrote about "Re: How to create a 
PDF-Printer from the command line"
> On Tue 09 Jan 2018 at 13:06:44 (+), Curt wrote:
> > On 2018-01-09, Curt  wrote:
> > > On 2018-01-09, Ionel Mugurel Ciobîcă  wrote:
> > >> On  9-01-2018, at 06h 52'16", davidson wrote about "Re: How to create a 
> > >> PDF-Printer from the command line"
> > >>> >
> > >>> >How does one convert a text file to a PDF using the command line?
> > >>> 
> > >>> Step 1. Make sure the text file is also a latex document.
> > >>> Step 2. Use latex.
> > >>
> > >> Assuming step 1 is reached, step 2 will make a dvi file. That was not
> > >> what the OP asked for...
> > >
> > > pdftex (your one step road to a pdf)?
> > >
> > >  DESCRIPTION
> > >Run  the  pdfTeX  typesetter  on  file,  usually creating
> > >file.pdf.  
> > >
> > > Of course, B. will inform us that this amounts to eradicating a microbe 
> > > with a
> > > gorilla (or vice-versa?).
> > >
> > >>
> > >> Ionel
> > >>
> > 
> > If you're dealing with latex files, as I have taken some minutes to
> > discover (cough), you need 'pdflatex', not pdftex, which will barf
> > immediately upon encountering latex commands.
> 
> So could you now elaborate on step 1 of this "one-step" process?
> 
> Cheers,
> David.


For the non-LaTeX people, the easiest is to create a tex file (or ltx,
if you wish) that contains this lines before the text:

  \documentclass[a4paper,12pt]{article}
  \pagenumbering{arabic}
  \begin{document}

and this line after the text:

  \end{document}

LaTeX will ignore spaces and newlines. So if you wish a newline
somewhere you need to add it with \newline. If the text is UTF-8, add
also \usepackage[utf8x]{inputenc} before \begin{document}. 
You can make a title with:
  \title{Title}
  \author{Me}
  \date{\today}
  \maketitle
after \begin{document}

``%'' is a comment in LaTeX, so you need to escaped it with \. The
same goes for few other characters (&, etc.) $ and [ are for
equations. < and > will not work, use $<$ and $>$ instead.

Good luck.

Ionel

P.S. I am not the one that suggested to go via LaTeX!

Re: Problème de configuration de carte son

[Haricophile]

Le Tue, 9 Jan 2018 09:53:47 +0100,
BERTRAND Joël  a écrit :

>   Bonjour à tous,
> 
>   Je suis en train de m'installer un nouveau poste de travail
> (carte-mère thin mini ITX de récupération Asus Q87T, i7 4790, 16 Go
> de mémoire, biécran HDMI/DP). Tout fonctionne sauf la configuration
> de la carte son. J'aimerais que le son sorte par les deux interfaces
> DP et HDMI (si ce n'est pas possible par l'une des deux par défaut).
> 
>   J'ai viré pulseaudio qui dysfonctionne généralement à pleins
> tubes pour ne garder qu'Alsa (avec l'émulation OSS).

Dommage, pulseaudio sait faire ;)

Tu peux peut-être regarder du côté de jack si tu cherches quelque
chose d'un peu moins automatisme pour grand public que pulseaudio.

https://linuxmao.org/Jack

>   Si j'ai bien compris la doc que j'ai lue, la carte 0 est la
> carte par défaut du système. Or il n'en est rien :

https://debian-facile.org/doc:materiel:cartes-son:depannage

Re: UID 1000 on Raspberry Pi (Was: Re: Embarrassing security bug in systemd)

[Christian Groessler]

On 01/09/18 04:49, Jason wrote:

This I'd guess is important, if you have several users. I don't, except
for amanda and nut, and thats only on this machine. All the rest have
one user, me, known under various aliases because the idiot installer is
now set to give the first user the machines name like pi or rock64. I
spent a month trying to fix user 1000 to be me instead of pi on the pi.

On the Pi, this is what worked for me:

1. Add a new user (and add him to group sudo). This user gets ID 1001.
$ sudo adduser tempuser
$ sudo adduser tempuser sudo

2. Log out of user pi and log in as the newly created user.

3. Delete user pi (pi must not have any processes running)

$ sudo deluser pi

4. Add the desired username:
$ sudo adduser gene



I just edited the password file directly, "vipw" and "vipw -s", and 
renamed the pi user.


regards,
chris

Re: Noms partitions /dev/sdaX modifiés en /dev/sdcX : résolu

[Pierre L.]

Le 09/01/2018 à 12:57, hamster a écrit :
> mais toi tu manque de bienveillance.
>
Cette réponse manque elle aussi un peu de "bienveillance" :p
Bien à vous.



signature.asc
Description: OpenPGP digital signature

Re: How to create a PDF-Printer from the command line

[Ionel Mugurel Ciobîcă]

On  9-01-2018, at 13h 06'44", Curt wrote about "Re: How to create a PDF-Printer 
from the command line"
> On 2018-01-09, Curt  wrote:
> > On 2018-01-09, Ionel Mugurel Ciobîcă  wrote:
> >> On  9-01-2018, at 06h 52'16", davidson wrote about "Re: How to create a 
> >> PDF-Printer from the command line"
> >>> >
> >>> >How does one convert a text file to a PDF using the command line?
> >>> 
> >>> Step 1. Make sure the text file is also a latex document.
> >>> Step 2. Use latex.
> >>
> >> Assuming step 1 is reached, step 2 will make a dvi file. That was not
> >> what the OP asked for...
> >
> > pdftex (your one step road to a pdf)?
> >
> If you're dealing with latex files, as I have taken some minutes to
> discover (cough), you need 'pdflatex', not pdftex, which will barf
> immediately upon encountering latex commands.
> 

I use LaTeX since 1997, so I know about this.

Dealing with step 1, if a text document is properly formated one can
use txt2html to generate a html file which then can be converted
further directly into LaTeX with gnuhtml2latex, or into ps (with
html2ps), pdf (with wkhtmltopdf), etc. I did not use any of the above,
so I can't say how good they work.

Converting text to pdf is something I did many times. In the past I
used enscript and a2ps. Then I experimented with u2ps and cedilla. I
use lately paps (with --font="Freemono 12") for a good UTF-8 coverage.
Of course I go via postscript, but that is not so bad.

In a single go, a pdf printer may still be the only option.


Ionel

Re: How to create a PDF-Printer from the command line

[David Wright]

On Tue 09 Jan 2018 at 13:06:44 (+), Curt wrote:
> On 2018-01-09, Curt  wrote:
> > On 2018-01-09, Ionel Mugurel Ciobîcă  wrote:
> >> On  9-01-2018, at 06h 52'16", davidson wrote about "Re: How to create a 
> >> PDF-Printer from the command line"
> >>> >
> >>> >How does one convert a text file to a PDF using the command line?
> >>> 
> >>> Step 1. Make sure the text file is also a latex document.
> >>> Step 2. Use latex.
> >>
> >> Assuming step 1 is reached, step 2 will make a dvi file. That was not
> >> what the OP asked for...
> >
> > pdftex (your one step road to a pdf)?
> >
> >  DESCRIPTION
> >Run  the  pdfTeX  typesetter  on  file,  usually creating
> >file.pdf.  
> >
> > Of course, B. will inform us that this amounts to eradicating a microbe 
> > with a
> > gorilla (or vice-versa?).
> >
> >>
> >> Ionel
> >>
> 
> If you're dealing with latex files, as I have taken some minutes to
> discover (cough), you need 'pdflatex', not pdftex, which will barf
> immediately upon encountering latex commands.

So could you now elaborate on step 1 of this "one-step" process?

Cheers,
David.

Re: How to create a PDF-Printer from the command line

[Curt]

On 2018-01-09, Curt  wrote:
> On 2018-01-09, Ionel Mugurel Ciobîcă  wrote:
>> On  9-01-2018, at 06h 52'16", davidson wrote about "Re: How to create a 
>> PDF-Printer from the command line"
>>> >
>>> >How does one convert a text file to a PDF using the command line?
>>> 
>>> Step 1. Make sure the text file is also a latex document.
>>> Step 2. Use latex.
>>
>> Assuming step 1 is reached, step 2 will make a dvi file. That was not
>> what the OP asked for...
>
> pdftex (your one step road to a pdf)?
>
>  DESCRIPTION
>Run  the  pdfTeX  typesetter  on  file,  usually creating
>file.pdf.  
>
> Of course, B. will inform us that this amounts to eradicating a microbe with a
> gorilla (or vice-versa?).
>
>>
>> Ionel
>>

If you're dealing with latex files, as I have taken some minutes to
discover (cough), you need 'pdflatex', not pdftex, which will barf
immediately upon encountering latex commands.

-- 
"Ruling a large nation is like cooking a small fish" - Lao Tzu

Re: Faulty .iso? No public key...

[Jonathan Dowland]

What does "apt policy debian-archive-keyring" show? Which version (if
any) do you have installed?

You could also try "apt install debian-archive-keyring"

This should clear up the issues with stretch-updates, but not the
virtualbox repository. For that you'll need to find, verify and import
the relevant key for that repository to get apt to accept it.

Note that virtualbox is available from Debian itself in stretch-
backports.

Re: Noms partitions /dev/sdaX modifiés en /dev/sdcX : résolu

[hamster]

Le 09/01/2018 à 12:00, Stephane Ascoet a écrit :
> Le probleme d'Andre est qu'il ne cherchait pas a obtenir une solution
> qui fonctionne, mais a avoir absolument son disque dur apparaitre en
> /dev/sda au lieu de /dev/sdc par une sorte d'obsession ideologique. Tant
> qu'il n'y etait pas arrive il ne se sentait pas bien, meme si son
> systeme fonctionnait parfaitement en appliquant les solutions qu'on lui
> a donne, qui par ailleurs etaient les bonnes.

Je te trouve bien rapide a juger alors que tu n'a eu qu'un point de vue
très sommaire et visiblement entaché de malentendus et
d'incompréhension. Est-tu dans sa tete pour prétendre si bien savoir ce
qu'il pense et ce qu'il veut ?

En résumé, il a manqué de clarté et peut etre même est-il un peu entêté,
mais toi tu manque de bienveillance.

Re: Client Debian Stretch 9 - Ansible - Docker - DemocracyOS OnPremises -- Serveur Distant Debian Stretch 9

[G2PC]

J'ai laissé Ansible de côté pour le moment.
Je tente déjà de faire tourner l'image de democracyos avec Docker.

Pour cela, j'ai installé MongoDB ( sans utiliser Docker. )

Quand j'arrive à la fin de l'installation du Docker de democracyos j'ai
le message d'erreur suivant :

# Production-ready image for running Democra...
Dans le cas du dépôt pour DemocracyOS : docker pull democracyos/democracyos

# Démarrer Democracyos
docker run --name demos -p 3000:3000 democracyos/democracyos

Le message d'erreur suivant est affiché :

(node:1) UnhandledPromiseRejectionWarning: Unhandled promise rejection 
(rejection id: 1): undefined
events.js:160
 throw er; // Unhandled 'error' event
 ^
MongoError: failed to connect to server [localhost:27017] on first connect 
[MongoError: connect ECONNREFUSED 127.0.0.1:27017]
   at Pool. 
(/usr/src/node_modules/mongoose/node_modules/mongodb-core/lib/topologies/server.js:328:35)
   at emitOne (events.js:96:13)
   at Pool.emit (events.js:188:7)
   at Connection. 
(/usr/src/node_modules/mongoose/node_modules/mongodb-core/lib/connection/pool.js:280:12)
   at Connection.g (events.js:292:16)
   at emitTwo (events.js:106:13)
   at Connection.emit (events.js:191:7)
   at Socket. 
(/usr/src/node_modules/mongoose/node_modules/mongodb-core/lib/connection/connection.js:177:49)
   at Socket.g (events.js:292:16)
   at emitOne (events.js:96:13)
   at Socket.emit (events.js:188:7)
   at emitErrorNT (net.js:1281:8)
   at _combinedTickCallback (internal/process/next_tick.js:80:11)
   at process._tickCallback (internal/process/next_tick.js:104:9)


https://www.visionduweb.eu/wiki/index.php?title=Ajouter_Docker_sur_GNU_Linux#Installer_une_image_Docker_democracyos

Re: Faulty .iso? No public key...

[didier gaumet]

Le 09/01/2018 à 07:33, Josh W. a écrit :
> I keep having the issue of no public key available and I don’t know what
> I should do…. Back up my computer and reinstall or is there a way to
> patch it up. I am attaching a file that shows what I am going through. I
> ran into all this this time will trying to install wine and adding to
> the sources.list file. I’ve had this problem with keys every since I
> downloaded the .iso for Debian Stretch… I am think that I might have
> gotten a faulty .iso file. Could some one point me in the direction of
> learning to check the checksum of a file or files. I would greatly
> appreciate it.
> 
> 
> 
> Joshua >

Maybe reconfiguring of reinstalling debian-archive-keyring package could
solve your problem?

Re: Noms partitions /dev/sdaX modifiés en /dev/sdcX : résolu

[Stephane Ascoet]

Le 02/01/2018 à 19:11, hamster a écrit :

J'en suis bien content pour toi, meme si je n'arrive toujours pas a
comprendre a quoi tu est arrivé, ni quel était ton problème, et ce
malgré les explications de ton dernier mail.


Bonjour et bonne annee a tous et tout particulierement au rongeur 
ecolo-libriste-decroissant :-)


Le probleme d'Andre est qu'il ne cherchait pas a obtenir une solution 
qui fonctionne, mais a avoir absolument son disque dur apparaitre en 
/dev/sda au lieu de /dev/sdc par une sorte d'obsession ideologique. Tant 
qu'il n'y etait pas arrive il ne se sentait pas bien, meme si son 
systeme fonctionnait parfaitement en appliquant les solutions qu'on lui 
a donne, qui par ailleurs etaient les bonnes. Je ne critique pas trop 
car je suis pareil sur d'autres choses qui me semblent fondamentales et 
qui sont des details pour d'autres, ce qui m'a valu des desaccords dans 
la communaute du libre. Et c'est valable pour de tout autres domaines 
egalement.


Le souci, c'est que la bidouille faite par Andre pour satisfaire son 
besoin n'est pas bonne du tout: il renomme a la main "sdc" en "sda" dans 
"/dev"!!! Qui sait vaguement comment Linux peuple /dev se doute que 
c'est une ignoble source de problemes futurs. Dans quelques 
semaines/mois/annees il va de nouveau avoir un systeme qui ne fonctionne 
plus car "sda" sera redevenu "sdc"... et s'il a oublie sa manipulation, 
il va encore rameuter tout le monde pour trouver une solution a un 
probleme qu'il a lui meme genere en ne respectant pas la logique de 
fonctionnement de GNU/Linux. Mais pire, s'il y a vraiment une raison 
vitale a ce que son disque soit "sdc", il risque carrement des 
plantages, des pertes de donnees, des problemes bizarres...


C'est exactement comme quelqu'un qui installerait des applications sans 
passer par le gestionnaire de paquets, ferait des personnalisations de 
fichiers de configurations divers et varies sans garder trace de ce 
qu'il a fait, qu'il fasse une mise a jour de version sans precautions et 
qu'ensuite il vienne demander pourquoi ses applications qu'il utilise de 
la meme facon depuis des annees ne se lancent plus du tout ou ne se 
comportent plus de la meme facon...

--
Cordialement, Stephane Ascoet

Re: Finding material with F1 or in "The Gnumeric Manual"

[Richard Owlett]

On 01/08/2018 01:21 PM, David Wright wrote:

On Mon 08 Jan 2018 at 10:58:35 (-0600), Richard Owlett wrote:

On 01/07/2018 11:34 AM, Richard Owlett wrote:

I'm new to gnumeric and have not used any spreadsheet since mid 70's.
I'm running Debian 9.1 with MATE desktop and gnumeric 1.12.32 .



I'm having a different problem now. But I see an common element -
not efficiently using available documentation.

I have a large rectangular region. I wish, on a per column basis, to
calculate the average of the values in that column. I found how to
get the average of a range in a particular column. But I don't see
how to simply do the same for a region.


Copy (^C) the cell with the average in it.
Paste (^V) it into the cells alongside this cell,
ie the ones where you want said averages to appear.


I eventually got there by using the R1C1 notation.
That is copying AVERAGE(R1C:R23C) was more intuitively more proper than 
copying  AVERAGE(A1:A23).




As this is about the second thing you learn about spreadsheet
behaviour (after summing and averaging, a column), it sounds
as if you need to find a simple guide to spreadsheet operations.



That may be the solution. From 40 years ago I remember *WHAT* 
spreadsheets can do rather than *HOW* to do it.


Thank you.

P.S. any way to force default notation to be R1C1?

Problème de configuration de carte son

[BERTRAND Joël]

Bonjour à tous,

	Je suis en train de m'installer un nouveau poste de travail (carte-mère 
thin mini ITX de récupération Asus Q87T, i7 4790, 16 Go de mémoire, 
biécran HDMI/DP). Tout fonctionne sauf la configuration de la carte son. 
J'aimerais que le son sorte par les deux interfaces DP et HDMI (si ce 
n'est pas possible par l'une des deux par défaut).


	J'ai viré pulseaudio qui dysfonctionne généralement à pleins tubes pour 
ne garder qu'Alsa (avec l'émulation OSS).


Un lspci donne :
00:1b.0 Audio device: Intel Corporation 8 Series/C220 Series Chipset 
High Definition Audio Controller (rev 05)
00:03.0 Audio device: Intel Corporation Xeon E3-1200 v3/4th Gen Core 
Processor HD Audio Controller (rev 06)


aplay -l renvoit :
 Liste des Périphériques Matériels PLAYBACK 
carte 0: HDMI [HDA Intel HDMI], périphérique 3: HDMI 0 [HDMI 0]
  Sous-périphériques: 1/1
  Sous-périphérique #0:
carte 0: HDMI [HDA Intel HDMI], périphérique 7: HDMI 1 [HDMI 1]
  Sous-périphériques: 1/1
  Sous-périphérique #0: subdevice #0
carte 0: HDMI [HDA Intel HDMI], périphérique 8: HDMI 2 [HDMI 2]
  Sous-périphériques: 1/1
  Sous-périphérique #0: subdevice #0
carte 0: HDMI [HDA Intel HDMI], périphérique 9: HDMI 3 [HDMI 3]
  Sous-périphériques: 1/1
  Sous-périphérique #0: subdevice #0
carte 0: HDMI [HDA Intel HDMI], périphérique 10: HDMI 4 [HDMI 4]
  Sous-périphériques: 1/1
  Sous-périphérique #0: subdevice #0
carte 1: PCH [HDA Intel PCH], périphérique 0: ALC887-VD Analog 
[ALC887-VD Analog]

  Sous-périphériques: 1/1
  Sous-périphérique #0: subdevice #0

	Si j'ai bien compris la doc que j'ai lue, la carte 0 est la carte par 
défaut du système. Or il n'en est rien :


root@hilbert:/dev# aplay /usr/share/sounds/alsa/Noise.wav
ALSA lib pcm_dmix.c:1052:(snd_pcm_dmix_open) unable to open slave
aplay: main:788: erreur à l'ouverture audio: Aucun fichier ou dossier de 
ce type

root@hilbert:/dev#

	Audacious m'indique que la carte par défaut est la carte PCM (qui 
apparaît en carte 1 (?)). Si j'indique dans audacious que je veux sortir 
sur HDA Intel HDMI, ça fonctionne. Enfin, à peu près puisque je ne peux 
régler le volume, ce qui est mon second problème.


Quelques idées pour corriger tout ça ?

Bien cordialement,

JKB

Liderable News | 08 Jan 2018

[Liderable News]

Liderable News


Hola de nuevo

Por si te lo perdiste, NOqueriamos que te vayas sin que tengas las nuevas 
publicaciones.

¡Esperamos que la disfrutes!

Actualizaciones en Liderable

08 Jan 2018

[1] ▷ Ideas de oficinas en casa: trucos para maximizar tu productividad
By liderable
 / en Ideas Perfectas
 / el 08 Jan 2018 10:47 PM

Como tener una oficina en casa?. Esto te suena familiar verdad: necesitas 
aprovechar al máximo cada metro cuadrado de tu casa de dos dormitorios, por lo 
que terminas trasladando tu oficina en casa al ático o al sótano, un lugar con 
aspecto de OfiBrandCeo, ideal para un Emprendedor, pero no para los simples 
mortales. Es un sacrificio […]

La entrada [2] ▷ Ideas de oficinas en casa: trucos para maximizar tu 
productividadse publicó primero en [3] Liderable.

[4] Leer más
[5] ⭐ Pensamientos positivos para mejorar la personalidad
By liderable
 / en Para SER Mejor
 / el 08 Jan 2018 05:54 PM

Mejorar la personalidad es importante? Es la convicción de que se está lo 
suficientemente capacitado y preparado para poder hacer frente a cualquier 
situación que se nos presente aunque sea imprevista, puede ser personal o en 
nuestra vida empresarial. Aunque no se conozcan todas las respuestas, uno puede 
buscarlas y encontrarlas. Es una “sensación de […]

La entrada [6] ⭐ Pensamientos positivos para mejorar la personalidadse publicó 
primero en [7] Liderable.

[8] Leer más

Estamos convencidos que podemos hacer GRANDE a muchas personas mas, [9] 
registratepara [10] publicary seguir desde Liderable, hay algo único e 
interesante para personas con grandes ideas como Tú

[11] VER TODAS LAS ACTUALIZACIONES

[12]

[13]

[14]

[15]

[16]

[17]

[18]

[19] Vea este email en su navegador

Usted está recibiendo este correo debido a su relación con  Liderable. [20] Por 
favor confirmesu interés en recibir nuestra información.  Si no desea recibir 
más mensajes como este, puede [21] cancelar su suscripción aquí
Este mensaje fue enviado a t...@benchmarkemail.com por h...@liderable.com
Las Americas, Cuenca, Azuay  EC010204, Ecuador

Cancelar Suscripción| Administre su Suscripción| Remitir Email| Reportar Abuso


 References:

1. u=7801E1F
2. u=7801E1F
3. u=7801E20
4. u=7801E1F
5. u=7801E21
6. u=7801E21
7. u=7801E20
8. u=7801E21
9. u=7801E22
10. u=7801E23
11. u=7801E23
12. u=7801E24
13. u=7801E25
14. u=7801E26
15. u=7801E27
16. u=7801E28
17. u=7801E29
18. u=7801E23
19. 
http://viveser.bmetrack.com/c/v?e=C38827=9CFDD=0=46FAFD7C=fTHoM8aX4cmtTUXrKU%2BuFkH65JnmyxczA4N83Ddjj9tQoS1ahAwyIA%3D%3D
20. 
http://viveser.bmetrack.com/c/opt?e=C38827=9CFDD=0=46FAFD7C=fTHoM8aX4cmtTUXrKU%2BuFkH65JnmyxczA4N83Ddjj9tQoS1ahAwyIA%3D%3D
21. 
http://viveser.bmetrack.com/c/u?e=C38827=9CFDD=0=46FAFD7C=fTHoM8aX4cmtTUXrKU%2BuFkH65JnmyxczA4N83Ddjj9tQoS1ahAwyIA%3D%3D


Este mensaje fue enviado a debian-user-spanish@lists.debian.org por 
h...@liderable.com

Usted puede modificar / actualizar su suscripción a través del enlace de abajo. 
   

Cancelar suscripci n de cualquier env o futuro
http://viveser.bmetrack.com/c/su?e=C38827=9CFDD=46FAFD7C=fTHoM8aX4cmtTUXrKU%2BuFkH65JnmyxczA4N83Ddjj9tQoS1ahAwyIA%3D%3D=A0B1A8F


Las Americas, Cuenca, Azuay  EC010204, Ecuador

Email Marketing
benchmarkemail.com
 [http://viveser.bmetrack.com]



http://viveser.bmetrack.com/c/u?e=C38827=9CFDD=46FAFD7C=fTHoM8aX4cmtTUXrKU%2BuFkH65JnmyxczA4N83Ddjj9tQoS1ahAwyIA%3D%3D=A0B1A8F

Re: How to create a PDF-Printer from the command line

[Curt]

On 2018-01-09, Ionel Mugurel Ciobîcă  wrote:
> On  9-01-2018, at 06h 52'16", davidson wrote about "Re: How to create a 
> PDF-Printer from the command line"
>> >
>> >How does one convert a text file to a PDF using the command line?
>> 
>> Step 1. Make sure the text file is also a latex document.
>> Step 2. Use latex.
>
> Assuming step 1 is reached, step 2 will make a dvi file. That was not
> what the OP asked for...

pdftex (your one step road to a pdf)?

 DESCRIPTION
   Run  the  pdfTeX  typesetter  on  file,  usually creating
   file.pdf.  

Of course, B. will inform us that this amounts to eradicating a microbe with a
gorilla (or vice-versa?).

>
> Ionel
>
>


-- 
"Ruling a large nation is like cooking a small fish" - Lao Tzu

Re: Faulty .iso? No public key...

[Thomas Schmitt]

Hi,

besides the good advise of John Doe about verifying an ISO, it should be
stated that "no public key available" during installation is not a typical
sign for a damaged ISO.
I'd rather suspect its intentional content being not being correct or maybe
the package mirror server not being up to date.

Josh W. wrote:
> I keep having the issue of no public key available

Did you already report details ?
Which ISO image file exactly ? Can you tell the mirror server address ?


Have a nice day :)

Thomas

Re: How to create a PDF-Printer from the command line

[tomas]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Tue, Jan 09, 2018 at 09:52:08AM +0100, Ionel Mugurel Ciobîcă wrote:
> On  9-01-2018, at 06h 52'16", davidson wrote about "Re: How to create a 
> PDF-Printer from the command line"
> > >
> > >How does one convert a text file to a PDF using the command line?
> > 
> > Step 1. Make sure the text file is also a latex document.
> > Step 2. Use latex.
> 
> Assuming step 1 is reached, step 2 will make a dvi file. That was not
> what the OP asked for...

Use pdflatex. Or lualatex. Or whatever. In any case, whoever is
going that path (it *does* have its upsides: I'm going it all the
time) knows that already.

Cheers
- -- tomás
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAlpUjUgACgkQBcgs9XrR2kZ0WACffnNH8gdYmEmZwIAHiN98xlzE
HSUAmgOclsjR9e4tXppAFlh+O/oqv1Iy
=km+c
-END PGP SIGNATURE-

Re: How to create a PDF-Printer from the command line

[Ionel Mugurel Ciobîcă]

On  9-01-2018, at 06h 52'16", davidson wrote about "Re: How to create a 
PDF-Printer from the command line"
> >
> >How does one convert a text file to a PDF using the command line?
> 
> Step 1. Make sure the text file is also a latex document.
> Step 2. Use latex.

Assuming step 1 is reached, step 2 will make a dvi file. That was not
what the OP asked for...


Ionel

Re: Booting from USB on an old MacBook

[juh]

On 09.01.2018 08:39, john doe wrote:
> On 1/9/2018 8:30 AM, juh wrote:

>> Is there a hack to boot such a Macbook from USB or do I have to buy a
>> new cd drive?
>>
> 
> http://www.idownloadblog.com/2015/09/14/how-to-start-up-mac-from-bootable-media/

Strange. I tried this before and my stick was never displayed. Maybe I
used non-efi images.

Anyway, thanks a lot.
juh

Re: Booting from USB on an old MacBook

[David Christensen]

On 01/08/18 23:30, juh wrote:

... I would like to install debian on my
2009 (or so) 13" MacBook to prevent being vulnerable to Meltdown and
Spectre. Sadly the internal CD drive is broken and the notebook does not
boot from USB. I didn't find any hint in the Bios settings how to boot
from a usb device.

Is there a hack to boot such a Macbook from USB or do I have to buy a
new cd drive?


debian-9.2.1-amd64-xfce-CD-1.iso on a USB flash drive boots on the 
Macbook Pro's I tested.  The current version should work:


https://www.debian.org/distrib/


Also see:

https://support.apple.com/en-us/HT201255

https://support.apple.com/en-us/HT201065


David