update debian file

[arko roy]

dear sir ! to day i am talk about you .. i am a iphone user . my iphone is
running ios version 12.1.2 . so, that is problem i am download a debian
file and instail via ifile with cydia . my debian file properly instail ios
device but application not open ...there is a prbolem "SB GAME HACKER" need
to be update
The developer of this app needs to be update it to work with ios 11.

Re: Netiquette [Was: Re: pmount could perhaps be of greater utility?

[Erik Christiansen]

On 07.05.19 09:05, rhkra...@gmail.com wrote:
> So, I'll use "publicly" -- I was going to do that, but it just seemed wrong 
> at 
> the time ;-)

It seems harder to remember uncommon spelling now than when I was
younger, and until the spellchecker disagreed, I'd gone with your
spelling - it's more consistent. But then English isn't famous for that.

Erik

Re: notify-send script messed up my environment

[Gene Heskett]

On Tuesday 07 May 2019 07:56:35 pm Dan Ritter wrote:

> Gene Heskett wrote:
> > I've had a problem, I think with dbus that smells a bit like this.
> >
> > I've a bash script that sends  inotifywait to watch the mail dir in
> > /var, and when one of the files is closed after writing and incoming
> > mail to it, returns to my script with the name of the file and sends
> > kmail a dbus message to go get mail $name. At the same time it
> > relaunches inotifywait to resume the watch. kmail goes and gets the
> > mail, zeroing out the contents of /var/mail/$name. But on wheezy
> > that got iffy after 20+ days of uptime and I had to reboot to
> > "clean" house or whatever was muching things up. In that 20 days,
> > dbus probably handled 350 to 600 cycles a day.  Now I haven't enough
> > uptime on 64 bit stretch to test it yet.
>
> You're watching /var/mail/gheskett for new mail?
>
> Kmail can probably do that by itself.

Yes it can pull from /var/mail/$name all by itself, but thats not in step 
with the incoming, and kmail freezes while its doing that, sometime for 
a minute+ at a time.  This is essentially instant reaction to an 
incoming mail, with a kmail freeze in milliseconds. kmail is a single 
threaded program.
>
> https://docs.kde.org/stable5/en/pim/kmail2/configure-appearance.html#c
>onfigure-appearance-systemtray
>
> says
>
> If you enable the system tray icon then a small KMail icon
> with the number of unread messages will be shown in the system
> tray. You can enable KMail's system tray icon with Enable system
> tray icon, and with System Tray Mode you can specify whether the
> tray icon should always be shown or only if you have unread
> messages.
>
> If the icon is visible then you can hide KMail's main window by
> clicking on the icon or by clicking on the window close button.
> By clicking on the icon you can make KMail's main window visible
> again. If you click on the icon with the right mousebutton then
> you get a menu with a few useful commands. You can check for new
> mail, create a new message or quit KMail. Additionally, there is
> the entry New Messages In which lists all folders containing
> unread messages. If you choose one of those folders then this
> folder will be selected in KMail's main window.


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

Re: notify-send script messed up my environment

[Dan Ritter]

Gene Heskett wrote: 
> I've had a problem, I think with dbus that smells a bit like this.
> 
> I've a bash script that sends  inotifywait to watch the mail dir in /var, 
> and when one of the files is closed after writing and incoming mail to 
> it, returns to my script with the name of the file and sends kmail a 
> dbus message to go get mail $name. At the same time it relaunches 
> inotifywait to resume the watch. kmail goes and gets the mail, zeroing 
> out the contents of /var/mail/$name. But on wheezy that got iffy after 
> 20+ days of uptime and I had to reboot to "clean" house or whatever was 
> muching things up. In that 20 days, dbus probably handled 350 to 600 
> cycles a day.  Now I haven't enough uptime on 64 bit stretch to test it 
> yet.

You're watching /var/mail/gheskett for new mail?

Kmail can probably do that by itself.

https://docs.kde.org/stable5/en/pim/kmail2/configure-appearance.html#configure-appearance-systemtray

says 

If you enable the system tray icon then a small KMail icon
with the number of unread messages will be shown in the system
tray. You can enable KMail's system tray icon with Enable system
tray icon, and with System Tray Mode you can specify whether the
tray icon should always be shown or only if you have unread
messages.

If the icon is visible then you can hide KMail's main window by
clicking on the icon or by clicking on the window close button.
By clicking on the icon you can make KMail's main window visible
again. If you click on the icon with the right mousebutton then
you get a menu with a few useful commands. You can check for new
mail, create a new message or quit KMail. Additionally, there is
the entry New Messages In which lists all folders containing
unread messages. If you choose one of those folders then this
folder will be selected in KMail's main window. 

Re: notify-send script messed up my environment

[Gene Heskett]

On Tuesday 07 May 2019 07:17:11 pm Esteban L wrote:

> Thanks Mr. Ritter for sharing your expertise.
>
> I think the one thing that kind of mystifies me a little is the bus
> pipe. I am not familiar with that. A simple logout and log back in
> made my "environment" return to "normal."
>
> As you recommended, I simply ran the bash script on it's own. It
> worked fine. But, as I was debugging it, over time, it stopped
> working. Perhaps based, as you say, on nautilus getting confused.
>
> It frustrated me a bit. Because, at that point, not even running the
> script, alone, would work.
>
> I found a better solution. I found a python API that was coded
> specifically for this purpose, and I am more familiar with python than
> I am with Bash (though I admit, Bash probably is better suited for
> many tasks at this level). What's the saying about the "devil you
> know?" =)
>
> Thanks again!
>
>
> -Original Message-
> From: Dan Ritter 
> To: Esteban L 
> Cc: debian-user 
> Subject: Re: notify-send script messed up my environment
> Date: Tue, 7 May 2019 18:12:01 -0400
>
> Esteban L wrote: 
>
> > I stepped in poo, and broke a cardinal sin, trying a script that I
> > didn't 100% understand. Now my environment is a little bit jacked.
> > Not
> > bad, still generally functioning. 
> >
> > I was trying to get notifications to run from the command line,
> > namely
> > crontab. No easy task, at least, not as easy as I would have
> > thought.
> >
> > I created and ran this script I found online:
> > #!/bin/bash
> > username=$(/usr/bin/whoami)
> > pid=$(pgrep -u $username nautilus)
> > dbus=$(grep -z DBUS_SESSION_BUS_ADDRESS /proc/$pid/environ | sed
> > 's/DBUS_SESSION_BUS_ADDRESS=//' )
> > export DBUS_SESSION_BUS_ADDRESS=$dbus
> > /usr/bin/notify-send "$(today)"
> >
> > It seemed simple enough.
> >
> > It even worked a few half dozen times. Until, it didn't.
> >
> > I couldn't even run the script anymore, from the command line.
> > I get the following error:
> > grep: /proc/1700: Is a directory
> > grep: 25836/environ: No such file or directory
> >
> > I tried to "man" up but can't find anything on dbus, dbus_session
> > etc.
> >
> > I think it's as simple as messing up my environment.
> >
> > Can someone throw me a bone? I guess I could restart, and I assume
> > that
> > should work, but that doesn't really explain to me why it broke,
> > which
> > interests me more.
>
> Let's go through the script and see if we can explain it.
>
> #!/bin/bash
> this is a bash script; please use /bin/bash to run it.
> username=$(/usr/bin/whoami)
> run the command /usr/bin/whoami and put the output in the
> variable "username"
> pid=$(pgrep -u $username nautilus)
> run pgrep, look for a process named nautilus owned by that
> username. Put the process ID in the variable "pid".
> dbus=$(grep -z DBUS_SESSION_BUS_ADDRESS /proc/$pid/environ | sed
> 's/DBUS_SESSION_BUS_ADDRESS=//' )
> look through the contents of the file in /proc/ (process id)
> /environ and find the line which contains the word
>    DBUS_SESSION_BUS_ADDRESS. pipe that line through the stream
>    editor to remove a bunch of characters and leave the rest.
>    Put the value in the variable "dbus".
> export DBUS_SESSION_BUS_ADDRESS=$dbus
> Make that "dbus" variable available to programs I run.
> /usr/bin/notify-send "$(today)"
> Run "notify-send" with a value that comes from a program
> called "today".
>
>
> Here are my suggestions:
>
> Test running 
> /usr/bin/notify-send "Boo!"
> If you get a notification, it's working. If not, you have deeper
> problems.
>
> Test with echo.
> After each variable assignment, run
> echo $username
> or
> echo $pid
> and so forth, as appropriate, to see what values you are
> getting.
>
> Spaces and linebreaks are important.
>
> "Nautilus" is not a foolproof way of knowing which X session is
> wanted.
>
> $(today) probably doesn't do what you want.
>
> -dsr-
I've had a problem, I think with dbus that smells a bit like this.

I've a bash script that sends  inotifywait to watch the mail dir in /var, 
and when one of the files is closed after writing and incoming mail to 
it, returns to my script with the name of the file and sends kmail a 
dbus message to go get mail $name. At the same time it relaunches 
inotifywait to resume the watch. kmail goes and gets the mail, zeroing 
out the contents of /var/mail/$name. But on wheezy that got iffy after 
20+ days of uptime and I had to reboot to "clean" house or whatever was 
muching things up. In that 20 days, dbus probably handled 350 to 600 
cycles a day.  Now I haven't enough uptime on 64 bit stretch to test it 
yet.

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

Re: notify-send script messed up my environment

[Esteban L]

Thanks Mr. Ritter for sharing your expertise.

I think the one thing that kind of mystifies me a little is the bus
pipe. I am not familiar with that. A simple logout and log back in made
my "environment" return to "normal."

As you recommended, I simply ran the bash script on it's own. It worked
fine. But, as I was debugging it, over time, it stopped working.
Perhaps based, as you say, on nautilus getting confused.

It frustrated me a bit. Because, at that point, not even running the
script, alone, would work.

I found a better solution. I found a python API that was coded
specifically for this purpose, and I am more familiar with python than
I am with Bash (though I admit, Bash probably is better suited for many
tasks at this level). What's the saying about the "devil you know?" =)

Thanks again!


-Original Message-
From: Dan Ritter 
To: Esteban L 
Cc: debian-user 
Subject: Re: notify-send script messed up my environment
Date: Tue, 7 May 2019 18:12:01 -0400

Esteban L wrote: 
> I stepped in poo, and broke a cardinal sin, trying a script that I
> didn't 100% understand. Now my environment is a little bit jacked.
> Not
> bad, still generally functioning. 
> 
> I was trying to get notifications to run from the command line,
> namely
> crontab. No easy task, at least, not as easy as I would have thought.
> 
> I created and ran this script I found online:
> #!/bin/bash
> username=$(/usr/bin/whoami)
> pid=$(pgrep -u $username nautilus)
> dbus=$(grep -z DBUS_SESSION_BUS_ADDRESS /proc/$pid/environ | sed
> 's/DBUS_SESSION_BUS_ADDRESS=//' )
> export DBUS_SESSION_BUS_ADDRESS=$dbus
> /usr/bin/notify-send "$(today)"
> 
> It seemed simple enough.
> 
> It even worked a few half dozen times. Until, it didn't.
> 
> I couldn't even run the script anymore, from the command line.
> I get the following error:
> grep: /proc/1700: Is a directory
> grep: 25836/environ: No such file or directory
> 
> I tried to "man" up but can't find anything on dbus, dbus_session
> etc.
> 
> I think it's as simple as messing up my environment.
> 
> Can someone throw me a bone? I guess I could restart, and I assume
> that
> should work, but that doesn't really explain to me why it broke,
> which
> interests me more.

Let's go through the script and see if we can explain it.

#!/bin/bash
this is a bash script; please use /bin/bash to run it.
username=$(/usr/bin/whoami)
run the command /usr/bin/whoami and put the output in the
variable "username"
pid=$(pgrep -u $username nautilus)
run pgrep, look for a process named nautilus owned by that
username. Put the process ID in the variable "pid".
dbus=$(grep -z DBUS_SESSION_BUS_ADDRESS /proc/$pid/environ | sed
's/DBUS_SESSION_BUS_ADDRESS=//' )
look through the contents of the file in /proc/ (process id)
/environ and find the line which contains the word
   DBUS_SESSION_BUS_ADDRESS. pipe that line through the stream
   editor to remove a bunch of characters and leave the rest.
   Put the value in the variable "dbus".
export DBUS_SESSION_BUS_ADDRESS=$dbus
Make that "dbus" variable available to programs I run.
/usr/bin/notify-send "$(today)"
Run "notify-send" with a value that comes from a program
called "today".


Here are my suggestions:

Test running 
/usr/bin/notify-send "Boo!"
If you get a notification, it's working. If not, you have deeper
problems.

Test with echo.
After each variable assignment, run
echo $username
or
echo $pid
and so forth, as appropriate, to see what values you are
getting.

Spaces and linebreaks are important.

"Nautilus" is not a foolproof way of knowing which X session is
wanted.

$(today) probably doesn't do what you want.

-dsr-

Motivacion no Monetaria: Salario Emocional, Felicidad en el Trabajo, Flexibilidad

[Diana Flores Gil]

Necesario para evitar la fuga de talento que tanto daña a la Organización.

EMPLOYER BRANDING:

- Haciendo de mi Empresa 
el Mejor Lugar para Trabajar -

Fecha de inicio: 13 de Mayo 2019

Duración: 04 Semanas


ACCIONES CONCRETAS PARA ATRAER Y FIDELIZAR TALENTO HUMANO: Salario emocional, 
dinámicas happy-at-work, planes de carrera, work-life balance, flexibilidad de 
horario y muchas cosas más...


Favor de enviar toda la información referente a la Especialización en Employer 
Branding: Haciendo de mi Empresa el Mejor Lugar para Trabajar con atención 
personalizada para:

Nombre:
Empresa:
Teléfono:
Ciudad:

 

O mayores informes comuníquese directamente al: 01-800-890-86-65 / (33) 
36-32-63-11

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Este boletín informativo tiene como objetivo crear valor en usted y en su 
Organización, si desea dejar de recibir este tipo de información favor de 
contestar EmployerBAJA761 o en su defecto en el enlace que viene posteriormente.
unsubscribe from this list
 
 

Re: apache2 missing a file, won't run.

[Gene Heskett]

On Tuesday 07 May 2019 02:40:15 pm Dan Purgert wrote:

> Brian wrote:
> > On Tue 07 May 2019 at 13:29:39 -, Dan Purgert wrote:
> >> -BEGIN PGP SIGNED MESSAGE-
> >> Hash: SHA256
> >>
> >> Gene Heskett wrote:
> >> > On Tuesday 07 May 2019 05:28:26 am Dan Purgert wrote:
> >> >> Gene Heskett wrote:
> >> >>> [...]
> >> >>> Is that a lib/module I can install to a
> >> >>> 4.9.0-9-rt-amd64 #1 SMP PREEMPT RT Debian 4.9.168-1
> >> >>> kernel?
> >> >>
> >> >> Multiarch?  It's a dpkg setting so that you can get packages for
> >> >> a different architecture (e.g. 32-bit "i386" packages on a
> >> >> 64-bit machine).
> >> >>
> >> >> You didn't answer which printer it was, though.
> >> >
> >> > Brother MFC-J6920DW, it can handle up to 11x17 paper, handy when
> >>
> >> According to the driver install notes [1] (step2), there are some
> >> prereq procedures[2].  Prereq (5) on that page is for Debian /
> >> Ubuntu 64-bit machines.
> >>
> >> NOTE -- I just grabbed the LPR *deb package (as I prefer LPR over
> >> cups). You can go through the tool here[3] to select the
> >> cupswrapper driver, if you prefer.
> >
> > There is enough misinformation in Gene's post without adding more.
> > :) Both the LPR and the CUPSwrapper printer driver packages are
> > required. One contains a PPD and the other a driver for conversion
> > to the specific printer language.
>
> I have never pulled in the CUPSwrapper driver, and have never had a
> problem with the printer.
>
> >> Some features may require that you've connected the printer via USB
> >> (I have a MFC-L8860CDW connected to the network that "loses" a lot
> >> of the "from the PC" functionality due to that).
> >
> > MFC-L8860CDW? What features are missing from network connected
> > device?
>
> Mainly the "pushbutton scan" and other fancy scanning options from the
> "usb driver" -- I mean, I can walk over to the thing, and hit the
> "scan to SFTP" button and get a PDF, but that's about the extent of my
> "scan back to a PC" ability.  There are also a couple of "on the
> printer" options that require a windows compter (although, thinking
> about it, those may be more like "scan to SMB share").
>
> But scan-to-pdf is perfectly acceptable for my scanning needs.

Or to a .jpeg, which generally satisfies my scanning needs. Or even a 
huge tiff if I'm going to OCR it. But I've not had to do that often 
enough its a habit, I have to learn how everytime. One of the hazards of 
old wet ram. :(

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

Help, windows dummy has bought one. I need it for a job or 100

[Gene Heskett]

Greetings all;

First it doesn't have a clue what to do with a wired network.
It sure wants to hook up to all the neighborhoods wifi, all of which are 
secured.
Second, its like stretch seems locked to ipv6 but its ipv4 for at least a 
hundred miles in any direction from  my 10-20 in North Central WV.

Third, I can't find a place to enter a netmask route or gateway, its been 
sleeping with dhcp for way too long.

I finally find what sort of looks like the old xp network configurator
but it error beeps at me to the entry of any address on my local net that 
isn't already taken.

So how do I convince this brand new unibody HP to use a static wired 
network setup? 

In the FWIW category, it takes winders 10 about 10x longer to boot than 
any of my linux machines. Makes me wonder if they should have named it 
window-0.1 because it is boringly slow.

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

Re: which mutt?

[David Jardine]

On Fri, May 03, 2019 at 02:57:10PM -0400, Dan Ritter wrote:
> Russell L. Harris wrote: 
> > On Fri, May 03, 2019 at 09:40:05AM -0700, Jimmy Johnson wrote:
> > > On 05/03/2019 04:43 AM, Francisco M Neto wrote:
> > > > AFAIK in Stretch Mutt actually means Neomutt. There was a flamewar...
> > 
> > I found the war in the threads, but I did not find the outcome.
> > 
> > 
> > > > In Buster, Mutt means Mutt, and Neomutt means Neomutt.
> > 
> > As it should be.
> > 
> > 
> > > > I suppose if you want to use "Vanilla" Mutt in Stretch you need to
> > > > get it some other way.
> > > > 
> > > > [1] https://jmtd.net/log/mutt_year_zero
> > > > [2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=870635
> > 
> > I am willing to wait for Buster to reach stable status; besides, that
> > gives me an impetus to upgrade.
> > 
> > 
> > P.S.  Would someone kindly tell me how, while in Mutt and reading a
> > message such as this, to launch a browser to open links such as [1]
> > and [2] above?
> 
> Two things:
> 
> in .muttrc:
> 
> auto_view text/html
> 
> in .mailcap or /etc/mailcap:
> 
> text/html; /usr/bin/sensible-browser %s; description=HTML Text; 
> nametemplate=%s.html
> text/html; /usr/bin/firefox-esr %s; description=HTML Text; test=test -n 
> "$DISPLAY";  nametemplate=%s.html
> text/html; /usr/bin/google-chrome-stable --incognito %s; test=test -n 
> "$DISPLAY"
> application/xhtml_xml; /usr/bin/google-chrome-stable --incognito %s; 
> test=test -n "$DISPLAY"
> text/html; /usr/bin/lynx -force_html %s; needsterminal; description=HTML 
> Text; nametemplate=%s.html
> text/html; /usr/bin/lynx -dump -force_html %s; copiousoutput; 
> description=HTML Text; nametemplate=%s.html
> 
> or similar.
> 
> -dsr-
> 

Or:  Pressing Ctrl-b while viewing the message brings up your browser
with a list of the links in the message.

Cheers,
David

Re: notify-send script messed up my environment

[Dan Ritter]

Esteban L wrote: 
> I stepped in poo, and broke a cardinal sin, trying a script that I
> didn't 100% understand. Now my environment is a little bit jacked. Not
> bad, still generally functioning. 
> 
> I was trying to get notifications to run from the command line, namely
> crontab. No easy task, at least, not as easy as I would have thought.
> 
> I created and ran this script I found online:
> #!/bin/bash
> username=$(/usr/bin/whoami)
> pid=$(pgrep -u $username nautilus)
> dbus=$(grep -z DBUS_SESSION_BUS_ADDRESS /proc/$pid/environ | sed
> 's/DBUS_SESSION_BUS_ADDRESS=//' )
> export DBUS_SESSION_BUS_ADDRESS=$dbus
> /usr/bin/notify-send "$(today)"
> 
> It seemed simple enough.
> 
> It even worked a few half dozen times. Until, it didn't.
> 
> I couldn't even run the script anymore, from the command line.
> I get the following error:
> grep: /proc/1700: Is a directory
> grep: 25836/environ: No such file or directory
> 
> I tried to "man" up but can't find anything on dbus, dbus_session etc.
> 
> I think it's as simple as messing up my environment.
> 
> Can someone throw me a bone? I guess I could restart, and I assume that
> should work, but that doesn't really explain to me why it broke, which
> interests me more.

Let's go through the script and see if we can explain it.

#!/bin/bash
this is a bash script; please use /bin/bash to run it.
username=$(/usr/bin/whoami)
run the command /usr/bin/whoami and put the output in the
variable "username"
pid=$(pgrep -u $username nautilus)
run pgrep, look for a process named nautilus owned by that
username. Put the process ID in the variable "pid".
dbus=$(grep -z DBUS_SESSION_BUS_ADDRESS /proc/$pid/environ | sed 
's/DBUS_SESSION_BUS_ADDRESS=//' )
look through the contents of the file in /proc/ (process id)
/environ and find the line which contains the word
   DBUS_SESSION_BUS_ADDRESS. pipe that line through the stream
   editor to remove a bunch of characters and leave the rest.
   Put the value in the variable "dbus".
export DBUS_SESSION_BUS_ADDRESS=$dbus
Make that "dbus" variable available to programs I run.
/usr/bin/notify-send "$(today)"
Run "notify-send" with a value that comes from a program
called "today".


Here are my suggestions:

Test running 
/usr/bin/notify-send "Boo!"
If you get a notification, it's working. If not, you have deeper
problems.

Test with echo.
After each variable assignment, run
echo $username
or
echo $pid
and so forth, as appropriate, to see what values you are
getting.

Spaces and linebreaks are important.

"Nautilus" is not a foolproof way of knowing which X session is
wanted.

$(today) probably doesn't do what you want.

-dsr-

notify-send script messed up my environment

[Esteban L]

Hello,

I stepped in poo, and broke a cardinal sin, trying a script that I
didn't 100% understand. Now my environment is a little bit jacked. Not
bad, still generally functioning. 

I was trying to get notifications to run from the command line, namely
crontab. No easy task, at least, not as easy as I would have thought.

I created and ran this script I found online:
#!/bin/bash
username=$(/usr/bin/whoami)
pid=$(pgrep -u $username nautilus)
dbus=$(grep -z DBUS_SESSION_BUS_ADDRESS /proc/$pid/environ | sed
's/DBUS_SESSION_BUS_ADDRESS=//' )
export DBUS_SESSION_BUS_ADDRESS=$dbus
/usr/bin/notify-send "$(today)"

It seemed simple enough.

It even worked a few half dozen times. Until, it didn't.

I couldn't even run the script anymore, from the command line.
I get the following error:
grep: /proc/1700: Is a directory
grep: 25836/environ: No such file or directory

I tried to "man" up but can't find anything on dbus, dbus_session etc.

I think it's as simple as messing up my environment.

Can someone throw me a bone? I guess I could restart, and I assume that
should work, but that doesn't really explain to me why it broke, which
interests me more.

Thanks in advance, to anyone that can throw me a bone.

Re: Configuration d'Alsa éphémère

[G2PC]

C'est bien ça.
Et, si tu démarres sur Windows, que tu test ton son sur Windows, ça
fonctionne ?

Ensuite, si tu redémarres sur Debian, le son fonctionne ?

J'ai ce problème sur Mint, lors des mises à jour de noyau notamment, je
perd le son sur Mint.
Malgré quelques bidouilles, je ne le récupère pas.

Quand je lance Windows puis que je retourne sur Mint, le son fonctionne.

On m'a parlé d'un soucis de bit matériel, j'avoue ne pas être à l'aise
avec l'explication, mais, en pratique, si je perd le son sur la Mint, je
suis presque obligé, semble t'il, de passer par Windows puis de rebooter
vers la Linux, pour avoir le son fonctionnel à nouveau.

Si tu peux tester de ton côté, et, faire un retour pour Debian, si tu
récupères le son ainsi, merci.


>> Tu aurais pas un dualboot Debian / Windows par hasard ?
> En effet je peux accéder à Debian ou à Windows par le menu Grub, je ne pense 
> pas que c'est le dualboot dont tu parles.
> Philippe Merlin

Re: apache2 missing a file, won't run.

[Brian]

On Tue 07 May 2019 at 20:03:33 +0100, mick crane wrote:

> On 2019-05-07 19:40, Dan Purgert wrote:
> 
> > Mainly the "pushbutton scan" and other fancy scanning options from the
> > "usb driver" -- I mean, I can walk over to the thing, and hit the "scan
> > to SFTP" button and get a PDF, but that's about the extent of my "scan
> > back to a PC" ability.  There are also a couple of "on the printer"
> > options that require a windows compter (although, thinking about it,
> > those may be more like "scan to SMB share").
> > 
> > But scan-to-pdf is perfectly acceptable for my scanning needs.
> 
> I was having some trouble printing something from something or other a while
> back and I forget exactly how but was suggested to use google print or
> something that required you to give google access to your printer.
> Well I thought not.
> This cloud stuff ( everything just works ) seems all very well but so far I
> have managed to avoid it.

That's enormously interesting, but does not relate to this thread.
Perhaps a new post would be indicted.

-- 
Brian.

Re: apache2 missing a file, won't run.

[Brian]

On Tue 07 May 2019 at 18:40:15 -, Dan Purgert wrote:

> > There is enough misinformation in Gene's post without adding more. :)
> > Both the LPR and the CUPSwrapper printer driver packages are required.
> > One contains a PPD and the other a driver for conversion to the specific
> > printer language.
> 
> I have never pulled in the CUPSwrapper driver, and have never had a
> problem with the printer.

You have a PPD in /etc/cups/ppd for the printer. What do the

*NicKName

and

*cupsFilter

lines give when you look at the PPD.

> >> Some features may require that you've connected the printer via USB (I
> >> have a MFC-L8860CDW connected to the network that "loses" a lot of the
> >> "from the PC" functionality due to that).
> >
> > MFC-L8860CDW? What features are missing from network connected device?
> >
> Mainly the "pushbutton scan" and other fancy scanning options from the
> "usb driver" -- I mean, I can walk over to the thing, and hit the "scan
> to SFTP" button and get a PDF, but that's about the extent of my "scan
> back to a PC" ability.  There are also a couple of "on the printer"
> options that require a windows compter (although, thinking about it,
> those may be more like "scan to SMB share").
> 
> But scan-to-pdf is perfectly acceptable for my scanning needs.

Thanks. Nothing to do with printing, of course.

-- 
Brian.

Re: apache2 missing a file, won't run.

[mick crane]

On 2019-05-07 19:40, Dan Purgert wrote:


Mainly the "pushbutton scan" and other fancy scanning options from the
"usb driver" -- I mean, I can walk over to the thing, and hit the "scan
to SFTP" button and get a PDF, but that's about the extent of my "scan
back to a PC" ability.  There are also a couple of "on the printer"
options that require a windows compter (although, thinking about it,
those may be more like "scan to SMB share").

But scan-to-pdf is perfectly acceptable for my scanning needs.


I was having some trouble printing something from something or other a 
while back and I forget exactly how but was suggested to use google 
print or something that required you to give google access to your 
printer.

Well I thought not.
This cloud stuff ( everything just works ) seems all very well but so 
far I have managed to avoid it.


mick
--
Key ID4BFEBB31

Shell game? was Re: pmount could perhaps be of greater utility?

[David Wright]

On Tue 07 May 2019 at 10:12:10 (+1000), David wrote:
> On Mon, 6 May 2019 at 23:53, Erik Christiansen  
> wrote:
> > On 06.05.19 09:03, Greg Wooledge wrote:
> > > On Sat, May 04, 2019 at 01:48:01PM +0200, Jonas Smedegaard wrote:
> > > > Quoting Erik Christiansen (2019-05-04 08:43:53)
> 
> > > > >  pmount $1 `e2label $1`
> 
> > > and is using the ancient deprecated command substitution syntax (which
> > > will work in this case, but is not a good habit).
> 
> > That does appear to remain opinion. The venerably traditional syntax is
> > still fully legal supported bash syntax, e.g.:
> >
> > http://pubs.opengroup.org/onlinepubs/009695399/utilities/xcu_chap02.html#tag_02_06_03
> >
> > The recent (late last century, IIRC) introduction of the $(...)
> > alternative syntax has admittedly brought newer *nix users who know
> > nothing else, and so delude themselves that there is nothing else. That
> > is a misapprehension. To each, his own, especially amongst adequately
> > equivalent alternatives.
> 
> Hi Erik
> 
> Maybe you would enjoy answering this question then?
> https://lists.gnu.org/archive/html/help-bash/2019-05/msg0.html
> 
> Because apparently no-one else has, hehe :D

My take on this problem goes as follows.

B is easy. man bash says "When the old-style backquote form of
substitution is used, backslash retains its literal meaning except
when followed by $, `, or \." So the \\ in B's inner echo becomes
\ in the outer echo. BB shows the result of running the outer echo
on the substitution made in B.

A is tricky, mainly because of the middle Quotation Mark¹. So the first
thing I would do is substitute a benign character, like x. The result
of that substitution is shown at J. Work with that, and then change x
back to Quotation Mark at the end.

So K runs the inner echo and shows the result. L then runs the outer
echo on that result (leaving out the [] brackets). Because \x is
meaningless in double quotes, it survives the outer echo untouched.

Now put back the Quotation Mark in place of x. man bash says "A double
quote may be quoted within double quotes by preceding it with a
backslash." And that's what we've got in M.

Now working outwards, I've added the [] brackets at LL and MM, where
they play no role. Finally the outer double quotes: because they pair
up with the double quotes from L, that leaves the \x exposed to the
outer echo and it becomes just x.

Who processed the \" into " in A? The outer echo (or, if you like, the
shell handing the arguments to the outer echo).

Over to Greg for checking.

¹ Quotation Mark rather than double quote because it never plays the
role of an active double quote as far as bash is concerned.

Cheers,
David.
#
echo
echo
echo ` echo \" \\" \" ` B# " " " B
 echo \" \" \"  BB   # " " " BB
echo
echo
echo "[` echo \" \\" \" `]" A# [ " ] A
echo "[` echo \" \\x \" `]" J# [ \x ] J
 echo \" \\x \"  K   # " \x " K
echo " \x " L#  \x  L
echo " \" " M#  "  M
echo
echo
echo "[` echo \" \\" \" `]" A# [ " ] A
echo "[` echo \" \\x \" `]" J# [ \x ] J
 echo \" \\x \"  K   # " \x " K
echo [" \x "] LL # [ \x ] LL
echo [" \" "] MM # [ " ] MM
echo
echo
echo "[` echo \" \\" \" `]" A# [ " ] A
echo "[` echo \" \\x \" `]" J# [ \x ] J
 echo \" \\x \"  K   # " \x " K
echo "[" \x "]" LLL  # [ x ] LLL
echo "[" \" "]" MMM  # [ " ] MMM
echo \x exposed  # x exposed
echo \" exposed  # " exposed
#

Re: apache2 missing a file, won't run.

[Dan Purgert]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Brian wrote:
> On Tue 07 May 2019 at 13:29:39 -, Dan Purgert wrote:
>
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA256
>> 
>> Gene Heskett wrote:
>> > On Tuesday 07 May 2019 05:28:26 am Dan Purgert wrote:
>> >> Gene Heskett wrote:
>> >>> [...]
>> >>> Is that a lib/module I can install to a
>> >>> 4.9.0-9-rt-amd64 #1 SMP PREEMPT RT Debian 4.9.168-1
>> >>> kernel?
>> >>
>> >> Multiarch?  It's a dpkg setting so that you can get packages for a
>> >> different architecture (e.g. 32-bit "i386" packages on a 64-bit
>> >> machine).
>> >>
>> >> You didn't answer which printer it was, though.
>> >
>> > Brother MFC-J6920DW, it can handle up to 11x17 paper, handy when 
>> 
>> According to the driver install notes [1] (step2), there are some prereq
>> procedures[2].  Prereq (5) on that page is for Debian / Ubuntu 64-bit
>> machines.
>> 
>> NOTE -- I just grabbed the LPR *deb package (as I prefer LPR over cups).
>> You can go through the tool here[3] to select the cupswrapper driver, if
>> you prefer.
>
> There is enough misinformation in Gene's post without adding more. :)
> Both the LPR and the CUPSwrapper printer driver packages are required.
> One contains a PPD and the other a driver for conversion to the specific
> printer language.

I have never pulled in the CUPSwrapper driver, and have never had a
problem with the printer.

>> Some features may require that you've connected the printer via USB (I
>> have a MFC-L8860CDW connected to the network that "loses" a lot of the
>> "from the PC" functionality due to that).
>
> MFC-L8860CDW? What features are missing from network connected device?
>
Mainly the "pushbutton scan" and other fancy scanning options from the
"usb driver" -- I mean, I can walk over to the thing, and hit the "scan
to SFTP" button and get a PDF, but that's about the extent of my "scan
back to a PC" ability.  There are also a couple of "on the printer"
options that require a windows compter (although, thinking about it,
those may be more like "scan to SMB share").

But scan-to-pdf is perfectly acceptable for my scanning needs.

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEBcqaUD8uEzVNxUrujhHd8xJ5ooEFAlzR0Q4ACgkQjhHd8xJ5
ooFSyQf+NgbwqvT+CttRaKmZxafKXHWHIREiWIldZeFxeT6UnWDBDU2EC1SmhUrV
aNiAZYbyalTPRnzRM+elMy0r5xFCSYg7edyA02Cg+krpqEfRZ5ML5Dy1jAefLKLd
yAzM5LyhmghMIHTzZYEdNrtM4OKCBQWm5wf98HYyA2ILdTY1fROYngx7Z6Rg0x/n
eaai+BSEfHfyWlqhRXs17sfBFRFPPNxyXD3eCougohNC445IDucF8b7zDPNML0/Q
utJrduUdZ7HItw3avBcpOCOordBoPLz/CTGYHb/e3jIskuNf9DfeaG0EId2uVdby
GaCJdj5mDaOPa3//qse5PxrYrJIclQ==
=0Mk+
-END PGP SIGNATURE-

-- 
|_|O|_| 
|_|_|O| Github: https://github.com/dpurgert
|O|O|O| PGP: 05CA 9A50 3F2E 1335 4DC5  4AEE 8E11 DDF3 1279 A281

Re: Configuration d'Alsa éphémère

[MERLIN Philippe]

Le mardi 7 mai 2019, 15:33:18 CEST G2PC a écrit :
> Tu aurais pas un dualboot Debian / Windows par hasard ?
En effet je peux accéder à Debian ou à Windows par le menu Grub, je ne pense 
pas que c'est le dualboot dont tu parles.
Philippe Merlin
> Le 06/05/2019 à 13:50, MERLIN Philippe a écrit :
> > Bonjour,
> > Mon système est un Debian Sid AMD64, depuis quelque temps au démarrage de
> > la session je constate la disparition  du son sur mon ordinateur.
> > Si j'utilise Alsamixer et modifie légèrement un des paramètres le son est
> > rétabli, au démarrage suivant je suis forcer de faire la même
> > manipulation.
> > C'est nouveau je ne sais pas ce qui cause ce problème.
> > J'ai fait avant l'arrêt de l'ordinateur un alsactl store sans succès.
> > En cherchant sur le net j'ai créé un fichier /etc/default/alsa avec le
> > paramètre alsactl_store_on_shutdown="always autosave"
> > également sans succès.
> > Autre info je n'utilise pas pulseaudio.
> > A l'avance merci pour votre aide.
> > Philippe Merlin

Re: A Basic Mount Observation

[Thomas Schmitt]

Hi,

Cindy Sue Causey wrote:
> $ ls
> $ *STILL. crickets.*

You need to re-enter the directory, because the thing which now has
its name is not the directory which you entered before mount.

All programs which show the mounted content have addressed the directory
by its name after the mount operation.
Those programs which show the empty mount point directory have resolved
the address to a directory inode before the mount operation.


Let's look at device and inode numbers rather than names:

  # stat --format='%d %i' /mnt/iso
  2051 11796486
  # cd /mnt/iso
  # ls -ldi .
  11796486 drwxr-xr-x 2 root root 4096 ...date... .

You see that the mount point directory has inode number 11796486 in its
filesystem on device 2051.
Now with mounting

  # mount test.iso /mnt/iso
  # stat --format='%d %i' /mnt/iso
  1792 1216
  # ls -ldi /mnt/iso
  1216 dr-xr-xr-x 1 root root 2048 ...other.date... /mnt/iso

The mounted directory has inode number 1216 in the mounted ISO filesystem
on device 1792.

But your working directory is still the other inode

  # ls -ldi .
  11796486 drwxr-xr-x 2 root root 4096 ...date... .

Now set your working directory to what is pointed to by path /mnt/iso:

  # cd /mnt/iso
  # ls -ldi .
  1216 dr-xr-xr-x 1 root root 2048 ...other.date... .

Now you are in the root inode of the ISO and normally cannot unmount
before you leave it.

Go away and unmount to see the inode numer in the disk filesystem again:

  # cd
  # umount /mnt/iso
  # ls -ldi /mnt/iso
  11796486 drwxr-xr-x 2 root root 4096 ...date... /mnt/iso


Have a nice day :)

Thomas

Re: A Basic Mount Observation

[Bob Weber]

On 5/7/19 12:02 PM, Cindy Sue Causey wrote:

I didn't fully *cognitively* grasp what you're saying, BUT I did grasp
enough to attempt the following via xfce4-terminal:

$ cd /mountpoint
$ ls
$ *(anticipated) crickets*
$ sudo (YEAH, I KNOW!) mount LABEL=buster-backup /mountpoint
$ ls
$ *mammoth-sized crickets*


I would never have thought to do it this way.  It always made more sense to be 
in the directory just above the actual mount point.  Say I have a directory 
/mnt/tom.  I would:


cd  /mnt

mount /dev/whatever tom

ls tom

... would show the contents of what was just mounted if there were no errors.

If you have the following line in /etc/fstab (and the fuse programs necessary):

sshfs#sue@cindyslaptop:/home/sue /mnt/sue fuse    user,noauto,rw    
0   0


and run:

cd /mnt

mount sue

ls sue

... would show sue's directory on cindyslaptop.  Notice that since there is an 
entry for /mnt/sue in fstab you only need to mount the directory /mnt/sue.


I use this to mount a directory on a remote machine locally after setting up 
public key authentication so it doesn't even ask for a password.   This could 
also be used with file systems in /dev but they would always need to be the same 
name (like /dev/sdc1) or some other way to identify the exact drive to be 
mounted like the drives UUID.



*...Bob*

Re: apache2 missing a file, won't run.

[Brian]

On Tue 07 May 2019 at 13:29:39 -, Dan Purgert wrote:

> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
> 
> Gene Heskett wrote:
> > On Tuesday 07 May 2019 05:28:26 am Dan Purgert wrote:
> >> Gene Heskett wrote:
> >>> [...]
> >>> Is that a lib/module I can install to a
> >>> 4.9.0-9-rt-amd64 #1 SMP PREEMPT RT Debian 4.9.168-1
> >>> kernel?
> >>
> >> Multiarch?  It's a dpkg setting so that you can get packages for a
> >> different architecture (e.g. 32-bit "i386" packages on a 64-bit
> >> machine).
> >>
> >> You didn't answer which printer it was, though.
> >
> > Brother MFC-J6920DW, it can handle up to 11x17 paper, handy when 
> 
> According to the driver install notes [1] (step2), there are some prereq
> procedures[2].  Prereq (5) on that page is for Debian / Ubuntu 64-bit
> machines.
> 
> NOTE -- I just grabbed the LPR *deb package (as I prefer LPR over cups).
> You can go through the tool here[3] to select the cupswrapper driver, if
> you prefer.

There is enough misinformation in Gene's post without adding more. :)
Both the LPR and the CUPSwrapper printer driver packages are required.
One contains a PPD and the other a driver for conversion to the specific
printer language.

> Some features may require that you've connected the printer via USB (I
> have a MFC-L8860CDW connected to the network that "loses" a lot of the
> "from the PC" functionality due to that).

MFC-L8860CDW? What features are missing from network connected device?

-- 
Brian.
> 
> 
> (Sorry for the wrap)
> [1]
> https://support.brother.com/g/b/downloadend.aspx?c=us=en=mfcj6920dw_us_eu_as=128=dlf100969_000=4=559
> [2]
> https://support.brother.com/g/b/faqend.aspx?c=us=en=mfcj6920dw_us_eu_as=faq00100548_000
> [3]
> https://support.brother.com/g/b/downloadtop.aspx?c=us=en=mfcj6920dw_us_eu_as
> 
> HTH :)
> 
> -BEGIN PGP SIGNATURE-
> 
> iQEzBAEBCAAdFiEEBcqaUD8uEzVNxUrujhHd8xJ5ooEFAlzRiEAACgkQjhHd8xJ5
> ooFB6ggAiP+oXRxcX2c9ayZgXPAT4KMzGXiB0pVrgGdXmndUPSnTPZyNDWDUNlsc
> 1TZG086HtcYFGLr9qPh+pEGQLSBFLra7fAaWy7YbVFVb/Qtfy5/ldTXsZvTqc6SW
> zywWNvw8EwoksHgLRjcTzUHsgIEUmzuq77VF2+b5GV6rMDPmAAhLjm7qb5UjQZku
> 79AKdcVli9Lpid0Yv3hpY4tXucq9/EAMl01vusdpOIC/ITQfZdDZYqKvPP5PkFOI
> VTdpFqYst756SWv+JB4JCSVp4HqZr4cYQLPnIXg/+C0nClq+Qpw31cuGmQPchKHx
> LjMQEADBJow1O5qp7HkpLrKQHx+Kmg==
> =qpXN
> -END PGP SIGNATURE-
> 
> -- 
> |_|O|_| 
> |_|_|O| Github: https://github.com/dpurgert
> |O|O|O| PGP: 05CA 9A50 3F2E 1335 4DC5  4AEE 8E11 DDF3 1279 A281
> 

Re: A Basic Mount Observation

[Dan Ritter]

Cindy Sue Causey wrote: 
> On 5/7/19, to...@tuxteam.de  wrote:
> >
> > Makes sense: the current shell (and that is from where we're looking
> > at things) keeps the current working directory, CWD, open. This inode
> > doesn't go away after a mount -- thus as long as the shell doesn't
> > close it (by, e.g., changing to another directory), it will keep
> > "seeing" that directory, even if a new process doing an open() will
> > "see" the result after the mount.
> 
> Oka.. It sounds like this is a good training point for learning
> interoperability that's occurring if there's any way to... maybe point
> to images or something that help drive that point on home. I'm almost
> already fully grasping at this second because I just worked my own
> thought process via terminal. I'm going to reread the above a few more
> times then wait for that Linux operation that finally draws it all
> together enough to invoke an *ah-HAAA* moment. :)

Each process opens files and closes them. In this case, a
directory counts as a special kind of file.

An "open" is a process telling the kernel that it wants to use
a file. If it's successful, the kernel gives the process a file
handle, which is a bit of identifying data. When the process
"closes" the file, it hands the file handle back to the kernel. 
In the meantime, it may have called for read or write operations
on the handle.

Your shell is a process. When you issue a 'cd' command, it
opens the new directory, and when that works, closes the old
directory. If it fails, it still has the old directory's file
handle and doesn't close it, so you have a "place" to be.

When a mount happens, that doesn't change the file handles that
have already been issued. They are still valid. When an unmount
happens, issued file handles will become invalid if they were
part of the mounted filesystem which has now gone away.

Does that help? 

-dsr-

Re: A Basic Mount Observation

[Cindy Sue Causey]

On 5/7/19, to...@tuxteam.de  wrote:
> On Tue, May 07, 2019 at 11:20:57AM -0400, Dan Ritter wrote:
>> Martin McCormick wrote:
>> >I may just be remembering things the wrong way [...]
>
> [about not immediatlely "seeing" the results of a mount on the CWD]
>
> [...]
>
>> mkdir point
>> cd point
>> touch original
>> ls
>
> [practical demonstration illustrating that]
>
>> This behavior has always been consistent in Linux, as far as I am aware.
>>
>> The handle to your current directory cannot be changed out from
>> underneath you; only when you move away from it can it be
>> released, and from then on you see the new mount.
>
> Makes sense: the current shell (and that is from where we're looking
> at things) keeps the current working directory, CWD, open. This inode
> doesn't go away after a mount -- thus as long as the shell doesn't
> close it (by, e.g., changing to another directory), it will keep
> "seeing" that directory, even if a new process doing an open() will
> "see" the result after the mount.
>
> You can achieve similarly funny results by removing a file (or directory)
> while it's kept open by a process.


Oka.. It sounds like this is a good training point for learning
interoperability that's occurring if there's any way to... maybe point
to images or something that help drive that point on home. I'm almost
already fully grasping at this second because I just worked my own
thought process via terminal. I'm going to reread the above a few more
times then wait for that Linux operation that finally draws it all
together enough to invoke an *ah-HAAA* moment. :)

Cindy :)
-- 
Cindy-Sue Causey
Talking Rock, Pickens County, Georgia, USA

* runs with birdseed *

Re: A Basic Mount Observation

[Cindy Sue Causey]

On 5/7/19, Martin McCormick  wrote:
> This Summer will mark 30 years since I first laid hands on a
> unix-like system.  I probably was introduced to unix mount points
> very shortly after starting in the unix world which reminded me a
> lot of MSDOS except that there aren't nearly as many gotchas and
> things worked like one would dream they should work so I was
> probably introduced to the concept of the mount point somewhere
> in those early days.
>
>   I may just be remembering things the wrong way but it
> seems like that for most of my memory, one could be root and, if
> you cd'd to a mount point, one could mount /dev/whatever on that
> mount point and immediately see the top of the new tree you had
> just mounted.  If you cd'd in to that tree and tried to umount,
> you got the error that the file system was busy which makes sense
> because you are trying to saw off the limb you are sitting on, so
> to speak.
>
>   If you cd'd out of the mount point and nobody else was in
> it, you could umount and all was well.
>
>   I accidentally discovered now that I can become the root
> user, cd to a mount point and mount something with a subsequent
> ls of my current directory yielding nothing new.  One doesn't see
> the new mount.
>
>   If you open another session and look at the mount point,
> the new mount is there.  You can even create a file under the new
> mount which is only visible to you if you didn't cd out of the
> mount point.  Everybody else who looks at that point will see
> what's mounted there and not the test file slipped in under the
> mount.
>
>   Has this always been the normal behavior of mount or has
> there been a change?
>
>   I see this behavior as being useful like self-modifying
> code which is usually a huge thing to avoid but it was kind of
> interesting to notice.


I didn't fully *cognitively* grasp what you're saying, BUT I did grasp
enough to attempt the following via xfce4-terminal:

$ cd /mountpoint
$ ls
$ *(anticipated) crickets*
$ sudo (YEAH, I KNOW!) mount LABEL=buster-backup /mountpoint
$ ls
$ *mammoth-sized crickets*

*hm* so I next

$ thunar /mountpoint

That same mountpoint via Thunar file manager (opened via the terminal
at that same mountpoint) is now chock full of the expected
directories, initrd's, vmlinuz's...

*HM* so I next closed Thunar with the thought process being that maybe
opening Thunar finally brought everything to Life. I once again
ran

$ ls
$ *STILL. crickets.*

Nothin' comes back in answer to "ls". I actually figured this NEXT
attempt would FINALLY work. INSTEAD, that which "always does work" has
now been amended to... "almost always does work":

$ ls -ld *
ls: cannot access '*': No such file or directory

??? LOL. In the past, "ls -ld *" has ALWAYS presented query feedback
at times when "ls *" has failed for (system ordained) reasons that so
far zip on by overhead.

Was still not ready to give up SO THEN I lastly tried

CTRL+SHIFT+T to open a new terminal tab. By default in xfce4-terminal,
that opens up in the same directory that the last active tab was
using. Directories and files now all pull up for "ls" while sitting in
/mountpoint.

There was another something I did a while back that I can't remember
now, but you had to exit the terminal then reopen it for the desired
effect to take place. I'm halfway thinking it might be something from
Linux From Scratch (LFS) or similar Linux self-education type
exercises. Whatever I'm not remembering, that's what this feels
like...

If it's not quite what you were saying, it's still showing a...
not-quite-anticipated twist on things so that's why I posted. The last
few steps came to mind to test as I was typing this up. :)

Cindy :)
-- 
Cindy-Sue Causey
Talking Rock, Pickens County, Georgia, USA

* runs with birdseed *

Re: A Basic Mount Observation

[tomas]

On Tue, May 07, 2019 at 11:20:57AM -0400, Dan Ritter wrote:
> Martin McCormick wrote: 
> > I may just be remembering things the wrong way [...]

[about not immediatlely "seeing" the results of a mount on the CWD]

[...]

> mkdir point
> cd point
> touch original
> ls

[practical demonstration illustrating that]

> This behavior has always been consistent in Linux, as far as I am aware.
> 
> The handle to your current directory cannot be changed out from
> underneath you; only when you move away from it can it be
> released, and from then on you see the new mount.

Makes sense: the current shell (and that is from where we're looking
at things) keeps the current working directory, CWD, open. This inode
doesn't go away after a mount -- thus as long as the shell doesn't
close it (by, e.g., changing to another directory), it will keep
"seeing" that directory, even if a new process doing an open() will
"see" the result after the mount.

You can achieve similarly funny results by removing a file (or directory)
while it's kept open by a process.

Cheers
-- tomás


signature.asc
Description: Digital signature

Re: How to configure the hugepages group in Debian?

[Mikhail Morfikov]

On 07/05/2019 14:06, Jonas Smedegaard wrote:
> You probably use systemd: system/dev-hugepages.mount
Yes that was it. Thanks.




signature.asc
Description: OpenPGP digital signature

Re: How to configure the hugepages group in Debian?

[Mikhail Morfikov]

On 07/05/2019 13:51, Reco wrote:
> This particular systemd part is called dev-hugepages.mount.
I see, yes now it works well. Thanks for the info.




signature.asc
Description: OpenPGP digital signature

Way OT: “Publicly” and “publically” (was: Re: Netiquette [Was: Re: pmount could perhaps be of greater utility?])

[rhkramer]

> On Tuesday, May 07, 2019 08:41:16 AM Erik Christiansen wrote:
> > P.S. s/publically/publicly   (Yep, spellchecking in Vim in Mutt is OK
> > 
> >   with that. Caveat: I use a British
> >   dictionary. Haven't checked for possible
> >   USA divergent spelling.)

A somewhat Interesting (to me, anyway ;-) discussion on “Publicly” vs. 
“publically”, not all quoted here:

---++

   * [[https://stroppyeditor.wordpress.com/2014/12/09/publicly-and-
publically/][“Publicly” and “publically”]]
` 
Peters connects this to the adverb situation:

The parity of adjectives in -ic and -ical helps to explain why the adverbs 
for both types end in -ically. So, for example, the adverbs for organic and 
tragic are organically and tragically. Even though the -ical forms of the 
adjectives have long since disappeared, their ghosts appear in the adverbs. 
The effect is there even for adjectives which never had a counterpart ending in 
-ical. So barbaric, basic, civic, drastic and others become barbarically, 
basically etc., and it’s as if -ally is the adverbial ending for them. This 
has become the general rule for all adjectives ending in -ic except public, 
whose adverb is still normally publicly.

This is interesting, but it doesn’t tell us why the adverb forms settled as “–
ically” rather than “–icly”.

So I looked at the OED historical citations for the 16 bullet-pointed examples 
above, and found that for 12 of them, the “–ical” form of the adjective pre-
dated the “–ic”. This kind of suggests that, if these pairs were 
interchangeable at the time (1400s–1600s in most of these cases), the “–ical” 
forms may have been better established and so had a dominant position when it 
came to forming adverbs. Hence the “–ically” convention.

Maybe.

But this doesn’t tell us why “publicly” now stands alone. It did appear 
earlier than most of the other adverbs above; the OED’s first “public” is in 
1394 and “publicly” 1534. So maybe it had managed to dig in by the time the “–
ically” convention was blossoming? The OED has a couple of “publical”s (one in 
1450, one in 1898) but they’re clearly rogue; “public” has always been the 
only accepted form of the adjective, and this fact may have pushed people 
towards “publicly”. (“Publically” doesn’t appear until 1797.)

A scrap of support for this theory comes from the fact that “publicly” hasn’t 
always stood alone. The now-dead “franticly”, which Peters mentions, used to 
be common. The OED’s first “frantic” was in 1390, “franticly” in 1549 and 
“frantically” in 1749; it has no record of “frantical”. The situation is very 
like that of “public” and its derivatives, except that “publicly” has managed 
to survive regularisation.
'

Re: A Basic Mount Observation

[Dan Ritter]

Martin McCormick wrote: 
>   I may just be remembering things the wrong way but it
> seems like that for most of my memory, one could be root and, if
> you cd'd to a mount point, one could mount /dev/whatever on that
> mount point and immediately see the top of the new tree you had
> just mounted.  If you cd'd in to that tree and tried to umount,
> you got the error that the file system was busy which makes sense
> because you are trying to saw off the limb you are sitting on, so
> to speak.
> 
>   If you cd'd out of the mount point and nobody else was in
> it, you could umount and all was well.
> 
>   I accidentally discovered now that I can become the root
> user, cd to a mount point and mount something with a subsequent
> ls of my current directory yielding nothing new.  One doesn't see
> the new mount.
> 
>   If you open another session and look at the mount point,
> the new mount is there.  You can even create a file under the new
> mount which is only visible to you if you didn't cd out of the
> mount point.  Everybody else who looks at that point will see
> what's mounted there and not the test file slipped in under the
> mount.
> 
>   Has this always been the normal behavior of mount or has
> there been a change?

mkdir point
cd point
touch original
ls
original
mount /dev/whatever .
ls 
original
cd ..
cd point
ls
whatever-was-in-whatever
cd ..
umount point
cd point
ls
original

This behavior has always been consistent in Linux, as far as I am aware.

The handle to your current directory cannot be changed out from
underneath you; only when you move away from it can it be
released, and from then on you see the new mount.

-dsr-

A Basic Mount Observation

[Martin McCormick]

This Summer will mark 30 years since I first laid hands on a
unix-like system.  I probably was introduced to unix mount points
very shortly after starting in the unix world which reminded me a
lot of MSDOS except that there aren't nearly as many gotchas and
things worked like one would dream they should work so I was
probably introduced to the concept of the mount point somewhere
in those early days.

I may just be remembering things the wrong way but it
seems like that for most of my memory, one could be root and, if
you cd'd to a mount point, one could mount /dev/whatever on that
mount point and immediately see the top of the new tree you had
just mounted.  If you cd'd in to that tree and tried to umount,
you got the error that the file system was busy which makes sense
because you are trying to saw off the limb you are sitting on, so
to speak.

If you cd'd out of the mount point and nobody else was in
it, you could umount and all was well.

I accidentally discovered now that I can become the root
user, cd to a mount point and mount something with a subsequent
ls of my current directory yielding nothing new.  One doesn't see
the new mount.

If you open another session and look at the mount point,
the new mount is there.  You can even create a file under the new
mount which is only visible to you if you didn't cd out of the
mount point.  Everybody else who looks at that point will see
what's mounted there and not the test file slipped in under the
mount.

Has this always been the normal behavior of mount or has
there been a change?

I see this behavior as being useful like self-modifying
code which is usually a huge thing to avoid but it was kind of
interesting to notice.

Martin McCormick

Re: Is Debian 9 supposed to work on a Geode?

[Stefan Monnier]

>> Most of those ARM SBCs come with a µSD slot plus other things.
>> Even if you connect a SATA disk, you'll often need a µSD because some
>> of those SBCs don't have any on-board flash memory, so you need the µSD
>> to hold the U-Boot (which plays the role of the BIOS) without which the
>> board doesn't even know how to read from the SATA disk.
> I see. Being able to replace the memory that holds the bootloader makes
> perfect sense. That's even a feature I would pay extra for.

Yup: µSD cards tend to suck when compared to SATA devices, but when you
compare them to on-board flash holding BIOS and other such read-only
firmware, they rock!


Stefan

Re: Configuration d'Alsa éphémère

[G2PC]

Tu aurais pas un dualboot Debian / Windows par hasard ?

Le 06/05/2019 à 13:50, MERLIN Philippe a écrit :
> Bonjour,
> Mon système est un Debian Sid AMD64, depuis quelque temps au démarrage de la 
> session je constate la disparition  du son sur mon ordinateur. 
> Si j'utilise Alsamixer et modifie légèrement un des paramètres le son est 
> rétabli, au démarrage suivant je suis forcer de faire la même manipulation.
> C'est nouveau je ne sais pas ce qui cause ce problème.
> J'ai fait avant l'arrêt de l'ordinateur un alsactl store sans succès.
> En cherchant sur le net j'ai créé un fichier /etc/default/alsa avec le 
> paramètre alsactl_store_on_shutdown="always autosave"
> également sans succès.
> Autre info je n'utilise pas pulseaudio.
> A l'avance merci pour votre aide.
> Philippe Merlin
>
>

Re: apache2 missing a file, won't run.

[Dan Purgert]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Gene Heskett wrote:
> On Tuesday 07 May 2019 05:28:26 am Dan Purgert wrote:
>> Gene Heskett wrote:
>>> [...]
>>> Is that a lib/module I can install to a
>>> 4.9.0-9-rt-amd64 #1 SMP PREEMPT RT Debian 4.9.168-1
>>> kernel?
>>
>> Multiarch?  It's a dpkg setting so that you can get packages for a
>> different architecture (e.g. 32-bit "i386" packages on a 64-bit
>> machine).
>>
>> You didn't answer which printer it was, though.
>
> Brother MFC-J6920DW, it can handle up to 11x17 paper, handy when 

According to the driver install notes [1] (step2), there are some prereq
procedures[2].  Prereq (5) on that page is for Debian / Ubuntu 64-bit
machines.

NOTE -- I just grabbed the LPR *deb package (as I prefer LPR over cups).
You can go through the tool here[3] to select the cupswrapper driver, if
you prefer.

Some features may require that you've connected the printer via USB (I
have a MFC-L8860CDW connected to the network that "loses" a lot of the
"from the PC" functionality due to that).


(Sorry for the wrap)
[1]
https://support.brother.com/g/b/downloadend.aspx?c=us=en=mfcj6920dw_us_eu_as=128=dlf100969_000=4=559
[2]
https://support.brother.com/g/b/faqend.aspx?c=us=en=mfcj6920dw_us_eu_as=faq00100548_000
[3]
https://support.brother.com/g/b/downloadtop.aspx?c=us=en=mfcj6920dw_us_eu_as

HTH :)

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEBcqaUD8uEzVNxUrujhHd8xJ5ooEFAlzRiEAACgkQjhHd8xJ5
ooFB6ggAiP+oXRxcX2c9ayZgXPAT4KMzGXiB0pVrgGdXmndUPSnTPZyNDWDUNlsc
1TZG086HtcYFGLr9qPh+pEGQLSBFLra7fAaWy7YbVFVb/Qtfy5/ldTXsZvTqc6SW
zywWNvw8EwoksHgLRjcTzUHsgIEUmzuq77VF2+b5GV6rMDPmAAhLjm7qb5UjQZku
79AKdcVli9Lpid0Yv3hpY4tXucq9/EAMl01vusdpOIC/ITQfZdDZYqKvPP5PkFOI
VTdpFqYst756SWv+JB4JCSVp4HqZr4cYQLPnIXg/+C0nClq+Qpw31cuGmQPchKHx
LjMQEADBJow1O5qp7HkpLrKQHx+Kmg==
=qpXN
-END PGP SIGNATURE-

-- 
|_|O|_| 
|_|_|O| Github: https://github.com/dpurgert
|O|O|O| PGP: 05CA 9A50 3F2E 1335 4DC5  4AEE 8E11 DDF3 1279 A281

Re: Netiquette [Was: Re: pmount could perhaps be of greater utility?

[rhkramer]

Thanks for your reply, and thanks for putting it on the list!

Oh, and thanks for checking the spelling (kmail, at least the version I use, 
doesn't check spelling (or maybe I haven't enabled spellcheck).

(I may check the US spelling at some point -- ah, ok, a quick google finds:


“Publicly” and “publically” | Stroppy Editor


https://stroppyeditor.wordpress.com/2014/12/09/publicly-and-publically/
Dec 9, 2014 - It's widely regarded as a mistake (although some dictionaries 
now list it as a variant spelling). But the approved spelling, “publicly”, is 
a unique ...


So, I'll use "publicly" -- I was going to do that, but it just seemed wrong at 
the time ;-)

Have a good day!

On Tuesday, May 07, 2019 08:41:16 AM Erik Christiansen wrote:
> If my judgemental wording has offended the author on the other list,
> then I will admit to careless use of language. The out-of-the-blue shot
> across my bow from David, using that awkwardly and unproductively
> constructed use case looked like a deliberate straw man attack, coming
> hot on the heels of a deprecation attempt. Where a shell provides syntax
> alternatives, all still documented and supported, it may be perceived as
> unwelcoming and unproductive to spontaneously hound one usage in favour
> of one's own bias. Still, it would be better if my response had been more
> sanguine.
> 
> Erik
> 
> P.S. s/publically/publicly   (Yep, spellchecking in Vim in Mutt is OK
>   with that. Caveat: I use a British
>   dictionary. Haven't checked for possible USA
>   divergent spelling.)

Re: apache2 missing a file, won't run.

[Gene Heskett]

On Tuesday 07 May 2019 05:28:26 am Dan Purgert wrote:

> Gene Heskett wrote:
> > On Monday 06 May 2019 01:46:36 pm Dan Purgert wrote:
> >> Gene Heskett wrote:
> >> > [...]
> >> > Logged out no, started a new konsole and ran ff from it yes.
> >> > Managed to get the little b laser working, but a 2 year old
> >> > 11x17 MFC? Won't configure, missing file although the latest
> >> > driver kit from brother is installed, so I find I have a nearly
> >> > $700
> >> > scanner/copier/printer thats been discontinued!  And they've
> >> > blocked or removed any access to the old files.  Thats generated
> >> > a nastygram to brother, its a 2 year old printer.
> >>
> >> Which printer was that? Don't forget that some of their printers
> >> require multiarch / i386 in order for the pre-processor to run
> >> properly.
> >
> > Is that a lib/module I can install to a
> > 4.9.0-9-rt-amd64 #1 SMP PREEMPT RT Debian 4.9.168-1
> > kernel?
>
> Multiarch?  It's a dpkg setting so that you can get packages for a
> different architecture (e.g. 32-bit "i386" packages on a 64-bit
> machine).
>
> You didn't answer which printer it was, though.

Brother MFC-J6920DW, it can handle up to 11x17 paper, handy when 
processing "rockhopper's" output which can if magnified by inkscape far 
enough to be readable, is then posterized and can occupy better than 
half a sheet of 1/4 plywood.  And apparently cups has upped the anti, 
needing a filter they name if you read the fine print in the error_log, 
but which is not part of cups, or the last driver download from brother 
that I pulled a fresh copy of less than a year ago. For 32 bit of 
coarse.

The error log:
/usr/lib/cups/filter/brother_lpdwrapper_mfcj6920dw\" not available: No 
such file or directory

What I have:
Is an installer that came with the last download. I had to chmod +x it to 
run it, and its 95% legal BS as it contains 3 or 4 brother licenses in 
addition to the usual gpl-v2 boiler plate, but I ran it and was amazed, 
successfull, so now I have test prints from 2 profiles, and the test 
page on photo paper looks better than it ever has. And after running it, 
I have that missing file, but it was built, it does not exist in any of 
the debs accompanying that download. So now maybe I have some color 
control, which was previously ignored, giving me very pastel prints. But 
I've about sucked the cyan tank dry, so I'd better get some ink before 
messing with the color further. I haven't tried to setup a profile for 
the rear feed slot taking 11x17 paper yet. I tried to make a feed tray 
to keep the paper straighter, a huge improvement but wasn't 100% 
successfull.

Yay! I don't have an expen$ive paperweight anymore. Woopee! 

Thanks for reading, and I'll keep this in case someone else needs it. Now 
to see if sane can find its scanner and ADF.

Thanks again.

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

Netiquette [Was: Re: pmount could perhaps be of greater utility?

[Erik Christiansen]

On 07.05.19 07:38, rhkra...@gmail.com wrote off-list:
> On Tuesday, May 07, 2019 12:01:49 AM Erik Christiansen wrote:
> >  only the author is dumb enough 
> 
> Why use language like that?  (It does not contribute to the welcoming 
> environment that I'd like to see cultivated here.)
> 
> Aside: I've replied privately, but I would like to reply publically (sp?) in 
> order to spread the message, but only if you feel comfortable with that 
> (which 
> I don't expect you will).)

If my judgemental wording has offended the author on the other list,
then I will admit to careless use of language. The out-of-the-blue shot
across my bow from David, using that awkwardly and unproductively
constructed use case looked like a deliberate straw man attack, coming
hot on the heels of a deprecation attempt. Where a shell provides syntax
alternatives, all still documented and supported, it may be perceived as
unwelcoming and unproductive to spontaneously hound one usage in favour
of one's own bias. Still, it would be better if my response had been more
sanguine.

Erik

P.S. s/publically/publicly   (Yep, spellchecking in Vim in Mutt is OK
  with that. Caveat: I use a British
  dictionary. Haven't checked for possible USA
  divergent spelling.)
-- 
Time is a great teacher, but unfortunately it kills all its pupils.
  - Hector Louis Berlioz

Re: pmount could perhaps be of greater utility?

[Greg Wooledge]

On Tue, May 07, 2019 at 10:12:10AM +1000, David wrote:
> Maybe you would enjoy answering this question then?
> https://lists.gnu.org/archive/html/help-bash/2019-05/msg0.html
> 
> Because apparently no-one else has, hehe :D

You didn't like my answer?

(The OP clarified in a subsequent post that (s)he is trying to implement
syntax highlighting for some kind of text editor.  (S)he wants to support
the behavior of this ridiculous code just in case some foolish end
user writes it.  (S)he's not actually writing a script.  For people who
*are* actually writing scripts, the solution is exactly as I described.)

Re: How to configure the hugepages group in Debian?

[Jonas Smedegaard]

Quoting Mikhail Morfikov (2019-05-07 13:12:47)
> There's an entry on the Debian wiki[1] where people can read about the 
> hugepages in Debian, but I don't really think this article is up to 
> date. Basically when you look at the mount points in the system, you 
> can also see this one:
> 
>#  mount | grep -i huge
>hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime,pagesize=2M)
> 
> I don't have any fstab entries that would allow to mount /dev/hugepages . 
> So something is mounting it automatically, but I couldn't find any info 
> what that would be.
> 
> It's not really a problem what and where mounts the resource, but I 
> wanted to configure the group that can be set via the 
> "vm.hugetlb_shm_group" sysctl parameter. There's info on the Debian wiki 
> how to do this, and I wanted to add the following entry to the 
> /etc/fstab file in order to configure the group:
> 
> hugetlbfs /dev/hugepages hugetlbfs 
> rw,relatime,pagesize=2M,mode=1770,gid= 0 0
> 
> But this doesn't really work. I mean, those mount options aren't 
> set or are reset. So how to configure this thing?
> 
> [1] https://wiki.debian.org/Hugepages

You probably use systemd: system/dev-hugepages.mount


 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private


signature.asc
Description: signature

Re: Can't install addons for firefox

[Greg Wooledge]

On Tue, May 07, 2019 at 12:42:27PM +0100, Joe wrote:
> On Tue, 7 May 2019 12:26:44 +0200
> Siard  wrote:
> 
> > On Sat, 4 May 2019 09:27:26 -0700, Ross Boylan wrote:
> > > Running firefox-esr on buster I don't seem to be able to install
> > > addons.  
> > 
> > I just read that they fixed it in a new release:
> > https://news.softpedia.com/news/mozilla-releases-firefox-66-0-4-for-pcs-and-android-to-fix-major-add-ons-issue-525888.shtml
> > 
> 
> I upgraded sid about 15 hours ago and it came in then.

The firefox-esr package in buster also got updated last night, to the
version that was already in sid.

wooledg:~$ apt-cache policy firefox-esr
firefox-esr:
  Installed: 60.6.2esr-1
  Candidate: 60.6.2esr-1
  Version table:
 *** 60.6.2esr-1 500
500 http://ftp.us.debian.org/debian buster/main amd64 Packages
100 /var/lib/dpkg/status

Re: How to configure the hugepages group in Debian?

[Reco]

Hi.

On Tue, May 07, 2019 at 01:12:47PM +0200, Mikhail Morfikov wrote:
>#  mount | grep -i huge
>hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime,pagesize=2M)
> 
> I don't have any fstab entries that would allow to mount /dev/hugepages . 
> So something is mounting it automatically, but I couldn't find any info 
> what that would be.

This particular systemd part is called dev-hugepages.mount.


> It's not really a problem what and where mounts the resource, but I 
> wanted to configure the group that can be set via the 
> "vm.hugetlb_shm_group" sysctl parameter. There's info on the Debian wiki 
> how to do this, and I wanted to add the following entry to the 
> /etc/fstab file in order to configure the group:
> 
> hugetlbfs /dev/hugepages hugetlbfs 
> rw,relatime,pagesize=2M,mode=1770,gid= 0 0
> 
> But this doesn't really work. I mean, those mount options aren't 
> set or are reset. So how to configure this thing?

By following the usual way of overriding systemd's unit (pagesize=2M is
redundant on i386/amd64 and is harmful on other arches):

mkdir /etc/systemd/system/dev-hugepages.mount.d

cat > systemd/system/dev-hugepages.mount.d/override.conf << EOF
[Mount]
Options=mode=1770,gid=
EOF

systemctl daemon-reload && systemctl restart dev-hugepages.mount

Reco

Re: Remove nautilus to stop automounts? [Was: Re: pmount could perhaps be of greater utility?

[Brian]

On Tue 07 May 2019 at 21:34:14 +1000, Erik Christiansen wrote:

> On 04.05.19 13:48, Jonas Smedegaard wrote:
> > Quoting Erik Christiansen (2019-05-04 08:43:53)
> > >  There doesn't seem to be an option for pmount to mount at
> > >  /media/label_read_from_the_media
> ...
> > I don't personally use pmount since some years, but that sure sounds 
> > like a nice suggestion: Please consider filing as a bugreport against 
> > pmount with severity "wishlist".
> 
> Hmmm, reportbug says:
> 
> Your version (0.9.23-2) of pmount appears to be out of date.
> The following newer release(s) are available in the Debian archive:
>   experimental: 0.9.99-alpha-1
>   unstable: 0.9.23-3+b2
> Do you still want to file a report [y|N|q|?]? N

Of course you want to file a report! You have looked at the changelogs
for unstable and experimental and read their manuals. There is no sign
of your issue being addressed. Edit the version you are reporting the
bug against to 0.9.23-3+b2.

-- 
Brian.

Re: Can't install addons for firefox

[Joe]

On Tue, 7 May 2019 12:26:44 +0200
Siard  wrote:

> On Sat, 4 May 2019 09:27:26 -0700, Ross Boylan wrote:
> > Running firefox-esr on buster I don't seem to be able to install
> > addons.  
> 
> I just read that they fixed it in a new release:
> https://news.softpedia.com/news/mozilla-releases-firefox-66-0-4-for-pcs-and-android-to-fix-major-add-ons-issue-525888.shtml
> 

I upgraded sid about 15 hours ago and it came in then.

-- 
Joe

Remove nautilus to stop automounts? [Was: Re: pmount could perhaps be of greater utility?

[Erik Christiansen]

On 04.05.19 13:48, Jonas Smedegaard wrote:
> Quoting Erik Christiansen (2019-05-04 08:43:53)
> >  There doesn't seem to be an option for pmount to mount at
> >  /media/label_read_from_the_media
...
> I don't personally use pmount since some years, but that sure sounds 
> like a nice suggestion: Please consider filing as a bugreport against 
> pmount with severity "wishlist".

Hmmm, reportbug says:

Your version (0.9.23-2) of pmount appears to be out of date.
The following newer release(s) are available in the Debian archive:
  experimental: 0.9.99-alpha-1
  unstable: 0.9.23-3+b2
Do you still want to file a report [y|N|q|?]? N

but

# apt-get update
# apt-get install pmount

gives:

pmount is already the newest version.

so I'd probably have to move from wheezy to something newer to be up to
date on that utility. No time for that now.

The nifty pmount feature becomes unnecessary if I instead disable the
automounter, eliminating label-defined mountpoints. But:

# apt-get install dconf-editor  # gives:

The following packages have unmet dependencies:
 dconf-editor : Depends: libdconf1 (>= 0.25.1) but it is not going to be 
installed
Depends: libglib2.0-0 (>= 2.55.1) but 2.33.12+really2.32.4-5 is 
to be installed
Depends: libgtk-3-0 (>= 3.22.0) but 3.4.2-7+deb7u1 is to be 
installed

so the easiest way might just be to remove nautilus, as it's never been
used here. The gnome DE wouldn't fall over without it?  

Erik

Re: Configuration d'Alsa éphémère

[Christophe Moille]

Le lundi 06 mai 2019 à 13:50:11 (+0200), MERLIN Philippe a écrit :
> Bonjour,
> Mon système est un Debian Sid AMD64, depuis quelque temps au démarrage de la 
> session je constate la disparition  du son sur mon ordinateur. 
> Si j'utilise Alsamixer et modifie légèrement un des paramètres le son est 
> rétabli, au démarrage suivant je suis forcer de faire la même manipulation.
> C'est nouveau je ne sais pas ce qui cause ce problème.
> J'ai fait avant l'arrêt de l'ordinateur un alsactl store sans succès.

Salut,

J'ai le même problème sur ma stretch (avec un peu de paquets sid quand même).
et les mêmes vaines tentatives


> En cherchant sur le net j'ai créé un fichier /etc/default/alsa avec le 
> paramètre alsactl_store_on_shutdown="always autosave"
> également sans succès.

ça je n'ai pas essayé encore.

-- 
« Religion is regarded by the common people as true, by the wise as false,
and by the rulers as useful. »
- Richard Dawkins - The God Delusion

Re: Re: Systemd with chroot and under unprivileged user

[Peter Viskup]

Opened bug report at mainstream.
https://github.com/systemd/systemd/issues/12498

On Tue, May 7, 2019 at 12:17 PM Peter Viskup  wrote:

> It is related to systemd processing of chroot, as with commenting the User
> setting, the service start up successfully.
>
> Want to mimic the startup of the service in init script on Debian8 (which
> is running fine):
> ~# start-stop-daemon --start --quiet --pidfile
> "/srv/inst/var/run/rsyslogd.pid" --chuid user:group --chroot "/srv/inst"
> --exec "/usr/sbin/rsyslogd" -- -i  /var/run/rsyslogd.pid -4 -x
>
> --
> Peter
>

Re: List attachments (was: Undelivered Mail Returned to Sender)

[Brad Rogers]

On Mon, 6 May 2019 08:53:56 -0400
Kenneth Parker  wrote:

Hello Kenneth,

>I don't notice any Advertising on ProtonMail.

The 'cost' will not necessarily be advertising.  Data-mining all emails
in and out of the account is far more likely and, potentially, more
lucrative (for the miner, obviously).

-- 
 Regards  _
 / )   "The blindingly obvious is
/ _)radnever immediately apparent"
Just stop and take a second
U & Ur Hand - P!nk


pgpXYs2NACnOe.pgp
Description: OpenPGP digital signature

How to configure the hugepages group in Debian?

[Mikhail Morfikov]

There's an entry on the Debian wiki[1] where people can read about the 
hugepages in Debian, but I don't really think this article is up to 
date. Basically when you look at the mount points in the system, you 
can also see this one:

   #  mount | grep -i huge
   hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime,pagesize=2M)

I don't have any fstab entries that would allow to mount /dev/hugepages . 
So something is mounting it automatically, but I couldn't find any info 
what that would be.

It's not really a problem what and where mounts the resource, but I 
wanted to configure the group that can be set via the 
"vm.hugetlb_shm_group" sysctl parameter. There's info on the Debian wiki 
how to do this, and I wanted to add the following entry to the 
/etc/fstab file in order to configure the group:

hugetlbfs /dev/hugepages hugetlbfs 
rw,relatime,pagesize=2M,mode=1770,gid= 0 0

But this doesn't really work. I mean, those mount options aren't 
set or are reset. So how to configure this thing?

[1] https://wiki.debian.org/Hugepages



signature.asc
Description: OpenPGP digital signature

Re: Re: Systemd with chroot and under unprivileged user

[Peter Viskup]

It is related to systemd processing of chroot, as with commenting the User
setting, the service start up successfully.

Want to mimic the startup of the service in init script on Debian8 (which
is running fine):
~# start-stop-daemon --start --quiet --pidfile
"/srv/inst/var/run/rsyslogd.pid" --chuid user:group --chroot "/srv/inst"
--exec "/usr/sbin/rsyslogd" -- -i  /var/run/rsyslogd.pid -4 -x

-- 
Peter

Re: Can't install addons for firefox

[Siard]

On Sat, 4 May 2019 09:27:26 -0700, Ross Boylan wrote:
> Running firefox-esr on buster I don't seem to be able to install
> addons.

I just read that they fixed it in a new release:
https://news.softpedia.com/news/mozilla-releases-firefox-66-0-4-for-pcs-and-android-to-fix-major-add-ons-issue-525888.shtml

Re: Systemd with chroot and under unprivileged user

[tomas]

On Tue, May 07, 2019 at 11:08:38AM +0200, Peter Viskup wrote:
> Running Debian9 with systemd 241-3~bpo9+1 from backports.
> Having trouble to start rsyslog service in chroot jail using the systemd
> service file with RootDirectory and User settings.
> Setting AmbientCapabilities=CAP_SYS_CHROOT does not help and still getting
> following errors:
> 
>  rsyslog-chroot@inst.service: Changing to the requested working directory
> failed: Operation not permitted
>  rsyslog-chroot@inst.service: Failed at step CHROOT spawning
> /usr/sbin/rsyslogd: Operation not permitted

This seems to indicate that rsyslogd is trying to chdir() to some
directory it is not allowed to...

>  rsyslog-chroot@inst.service: Main process exited, code=exited,
> status=210/CHROOT
> 
> Any idea how to get it working properly? Starting without the User setting
> is working just fine.

No idea about systemd, but rsyslogd man page says:

  OPTIONS

[...]
-C  This prevents rsyslogd from changing to the root directory.
This is almost never a good idea in production use. This
option was introduced  in  support  of  the internal testbed.

So perhaps it's just rsyslogd trying (and failing) to chdir() to /
while in a chroot jail (surprise?). A run under strace might confirm
that. Setting option -C might help in debugging that.

Whether (assuming my shot in the dark is a hit) you /want/ to do
something the doc qualifies as being "almost never a good idea"
would be left as an exercise to the reader ;-)

HTH
-- t


signature.asc
Description: Digital signature

Re: apache2 missing a file, won't run.

[Dan Purgert]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Gene Heskett wrote:
> On Monday 06 May 2019 01:46:36 pm Dan Purgert wrote:
>
>> Gene Heskett wrote:
>> > [...]
>> > Logged out no, started a new konsole and ran ff from it yes. Managed
>> > to get the little b laser working, but a 2 year old 11x17 MFC?
>> > Won't configure, missing file although the latest driver kit from
>> > brother is installed, so I find I have a nearly $700
>> > scanner/copier/printer thats been discontinued!  And they've blocked
>> > or removed any access to the old files.  Thats generated a nastygram
>> > to brother, its a 2 year old printer.
>>
>> Which printer was that? Don't forget that some of their printers
>> require multiarch / i386 in order for the pre-processor to run
>> properly.
>
> Is that a lib/module I can install to a 
> 4.9.0-9-rt-amd64 #1 SMP PREEMPT RT Debian 4.9.168-1 
> kernel?

Multiarch?  It's a dpkg setting so that you can get packages for a
different architecture (e.g. 32-bit "i386" packages on a 64-bit
machine).

You didn't answer which printer it was, though.

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEBcqaUD8uEzVNxUrujhHd8xJ5ooEFAlzRT7kACgkQjhHd8xJ5
ooElCwf+LCocheaW7b0gUtnWyBCeO1vWrXaFwkas4AzVYgj+tZqAkU6Kf4EYKNIy
dt5xZkzD5A8o/s9asJxXvdvKYszAYZ8nzBgwg2FdwNHW2bkeGzQKGEY6Yu6CWL63
58afChljWsUl/iY2EI0212SEjjsU/8shKYnMsQr9UIS6KicS0UaupCt1+VzVmkEy
KRKD1IZBu1UK5v7QTF068TX/6CXFIs78fdWgo/AqDBQywRGqN3l7a8JUTTyt6LEI
9jcVdMtG6JtAyOQB0d7L7NNJu4AJlq37IIlut5ZsgSMZo1W91T3tXGg+6FlOgzHL
x7JxNYPRjcrXx5Ru2XFdw6LZuwlsOw==
=MmR9
-END PGP SIGNATURE-

-- 
|_|O|_| 
|_|_|O| Github: https://github.com/dpurgert
|O|O|O| PGP: 05CA 9A50 3F2E 1335 4DC5  4AEE 8E11 DDF3 1279 A281

Systemd with chroot and under unprivileged user

[Peter Viskup]

Running Debian9 with systemd 241-3~bpo9+1 from backports.
Having trouble to start rsyslog service in chroot jail using the systemd
service file with RootDirectory and User settings.
Setting AmbientCapabilities=CAP_SYS_CHROOT does not help and still getting
following errors:

 rsyslog-chroot@inst.service: Changing to the requested working directory
failed: Operation not permitted
 rsyslog-chroot@inst.service: Failed at step CHROOT spawning
/usr/sbin/rsyslogd: Operation not permitted
 rsyslog-chroot@inst.service: Main process exited, code=exited,
status=210/CHROOT

Any idea how to get it working properly? Starting without the User setting
is working just fine.
The workaround might be to set the $PrivDropToUser setting in rsyslog
configutation.

Service file:
[Unit]
Description=System Logging Service in chroot /srv/%i
ConditionPathExists=/srv/%i

[Service]
Type=simple
User=eset
Group=eset
PermissionsStartOnly=true
WorkingDirectory=/var/spool/rsyslog
AmbientCapabilities=CAP_SYS_CHROOT
RootDirectory=/srv/%i
RootDirectoryStartOnly=true
ExecStart=/usr/sbin/rsyslogd -n
StandardOutput=journal

[Install]
WantedBy=multi-user.target
Alias=syslog-chroot.service

-- 
Peter

Re: apache2 missing a file, won't run.

[Brian]

On Mon 06 May 2019 at 17:29:01 -0400, Gene Heskett wrote:

> On Monday 06 May 2019 04:06:43 pm Dan Ritter wrote:
> 
> > Ulf Volmer wrote:
> > > On 06.05.19 20:10, Gene Heskett wrote:
> > > > On Sunday 05 May 2019 12:56:27 pm Gene Heskett wrote:
> > > >
> > > > I had other problems that overshadowed this, but much of that has
> > > > been resolved, so can we start over with this?
> > >
> > > There was already a reply from me. You have to explain why you have
> > > a 2.2 apache config on a debian stretch system.
> >
> > That's easy: because the system was configured in wheezy or
> > earlier, was upgraded to jessie and continued working, and was
> > upgraded to stretch and stopped working.
> >
> > -dsr-
> 
> No jessie. New stretch install on a new drive, data all copied over from 
> the old drive. And data apparently included /etc/apache2 since I did 
> want to keep the .conf file there. There are some things in it that help 
> put it in a rights sandbox.

Wholesale copying of data from one machine to another has caused trouble
for this user in the past. Some more documentation to criticise:

http://httpd.apache.org/docs/trunk/en/upgrading.html

 > These modules have been removed: mod_authn_default,
 > mod_authz_default, mod_mem_cache. If you were using
 > mod_mem_cache in 2.2, look at mod_cache_disk in 2.4.

-- 
Brian.

Re: Configuration d'Alsa éphémère

[Pierre L.]

Très juste !

Le 07/05/2019 à 09:20, David BERCOT a écrit :
> il est extrêmement intéressant d'avoir une version de Debian en mode "rolling 
> release"




signature.asc
Description: OpenPGP digital signature

Re: "missing pubkey" for buster-security

[Harald Dunkel]

Hi Ansgar,

I highly appreciate your detailed response. I had not expected
that the keyserver is restricted to developer keys.

Thanx very much
Harri

Re: Configuration d'Alsa éphémère

[David BERCOT]

Bonjour Francis,

Oui, Sid est une "vraie" distribution avec l'ensemble des paquets et des mises 
à jour très fréquentes (notamment dans le cas de failles de sécurité).
D'autre part, il est extrêmement intéressant d'avoir une version de Debian en 
mode "rolling release", sans ré-installation en cas de changement de version 
majeure (il n'y en a pas pour Sid).
Personnellement, c'est aussi cette version que j'utilise depuis des années en 
ayant néanmoins à l'esprit le fait qu'il peut, ponctuellement, y avoir des 
problèmes ;-)

Bien cordialement,

David.

Le 06/05/2019 à 23:37, fw a écrit :
> As-tu une raison particulière d'utiliser la distribution unstable
> (« Sid ») ?
> 
> Cordialement
> 
> "Dire que l'on s'en fiche du droit à la vie privée sous prétexte qu'on a rien 
> à cacher, c'est comme déclarer que l'on se fiche du droit à la liberté 
> d'expression sous prétexte qu'on a rien à dire." Edward Snowden
> 

Re: correctif pour mozilla firefox

[didier gaumet]

plus besoin de bricoler, la version modifiée par Mozilla pour corriger
le problème est arrivée dans Stretch.