Re: Can't mount non-/ partition using Thunar because of grsecurity patched 4.9.65-2 amd64 linux kernel

[TemTem]

> You must first "open" the encrypted volume with cryptsetup luksOpen, then 
> mount it (not the partition) with mount.

After I managed to learn how cryptsetup works, I succeeded in decrypting and 
mounting my volume. I am going to use this as a workaround while waiting for 
the solution regarding Thunar. Thanks :)

Re: Can't mount non-/ partition using Thunar because of grsecurity patched 4.9.65-2 amd64 linux kernel

[Pascal Hambourg]

Le 22/12/2017 à 03:41, TemTem a écrit :

I also tried mounting using the terminal, and it works, except for the encrypted 
partition. It seems mount doesn't recognize "crypto-LUKS". How can I make it 
recognize it so that I can mount my encrypted partition via terminal?


You must first "open" the encrypted volume with cryptsetup luksOpen, 
then mount it (not the partition) with mount.

Re: mplayer changed behaviour in stretch

[Charlie Gibbs]

On 19/12/17 09:45 AM, Greg Wooledge wrote:


On Tue, Dec 19, 2017 at 09:36:11AM -0800, Charlie Gibbs wrote:

>

Follow-up: I've just come across MP3 files in my collection for which the
new mplayer _does_ display the tags.  Maybe it's just becoming more picky -
which isn't really a Good Thing.  Postel's Law says, "Be conservative in
what you do, be liberal in what you accept from others."


Could be id3v1 vs. id3v2 tags.  Try some of the command-line tools to
see which tags are present on which songs.


The files which display have both ID3V1 and ID3V2 tags.  The ones which 
don't display only have ID3V2 tags.  Could the latest mplayer have lost 
the ability to handle ID3V2 tags?


The old version on my Jessie machine reports:
Mplayer2 2.0-728-g2c378c7-4+b1

The new Stretch version (which can't see ID3V2 tags) reports:
MPlayer 1.3.0 (Debian), built with gcc-6.2.1

Hmmm, looks like the newer release rolled back to an older version of 
mplayer.  There are no links, just the binary in /usr/bin.  I think I'll 
just copy the version on my Jessie machine over to my Stretch machine... 
 Arrgh!  mplayer: error while loading shared libraries: libquvi.so.7: 
cannot open shared object file: No such file or directory


Rather than risk the Linux equivalent of DLL hell, I'll roll back to the 
installed version and see whether a newer one comes along.


$ sudo apt-get install mplayer
Reading package lists... Done
Building dependency tree
Reading state information... Done
mplayer is already the newest version (2:1.3.0-6).
0 upgraded, 0 newly installed, 0 to remove and 360 not upgraded.

$ sudo apt-get install mplayer2

Aha!  That installed mpv and created a symbolic link to it from mplayer. 
 Now I can see my ID3V2 tags again.


--
cgi...@surfnaked.ca (Charlie Gibbs)

Can't mount non-/ partition using Thunar because of grsecurity patched 4.9.65-2 amd64 linux kernel

[TemTem]

Hi, when using the grsecurity patched 4.9.65-2 linux kernel from 
stretch-backports, I can't mount other partitions in my hard disk drive using 
Thunar. It says I don't have the permission to mount partitions even though I 
am a sudoer. I tried using the kernel without the patch, and mounting using 
Thunar works. I think the reason why this happens is because the appropriate 
PaX flags aren't set in the program which displays a root prompt. If that's the 
case, what is the name of the program which I should set and what PaX flags 
should I use? I also tried mounting using the terminal, and it works, except 
for the encrypted partition. It seems mount doesn't recognize "crypto-LUKS". 
How can I make it recognize it so that I can mount my encrypted partition via 
terminal?

Re: Reporting a bug that affects more than one package

[Terry Roy]

On 21/12/2017 19:18, Ben Finney wrote:

Terry Roy  writes:


I found a bug in Debian's latest 9.3 update where the postinst script
of a package contained the line:

"su - username do something"


I've just run this command:

 grep "su - " /var/lib/dpkg/info/*

which returned no results on a system with thousands of packages
installed. So I tentatively conclude that it's not a common pattern.



I've never run across it before although based on one of the bug reports 
I filed, others have. It's peculiar only to systems with files in 
/etc/profile.d. I've another server, virtually identical with respect to 
packages but with no file in /etc/profile.d and haven't experienced the 
issue.



I've just run across it again on a fresh install of another package.
I've reported that bug but clearly this seems to be an issue involving
the use of "su -" in postinst.


You should proceed this way, IMO. Report a bug against each package that
uses that invocation.


I note that a similar pattern, invoking ‘su’ to run commands as another
user, is in the ‘postgresql-common’ package:

 su -s /bin/sh postgres -c "… more commands …"

If you alter the postinst script to use that pattern instead, does it
avoid the problem you describe? If so, you can suggest that to the
package maintainer.


I have reported it for both sa-compile and tuptime. postgres hasn't 
cause us any problems since the -s is just specifying which shell. I 
believe the issue has to do with the fact that the hyphen makes it an 
interactive shell as opposed to not using the hyphen which just executes 
the command. I also found it in the spamassassin package so will report 
it there as well.


The debconf-doc package seems to contain a lot of information about 
using postinst so I'll file a report there as well.


Thanks.

--
Terry

Saving Sent Messages with Thunderbird

[Dan Norton]

By default, Thunderbird saves copies of sent emails in your email 
account with the ISP. You can to save them instead to a local folder by 
right-clicking on Local Folders and selecting "settings -> Copies and 
Folders -> When sending messages, automatically:". You can also make the 
reverse choice in this dialog.


Currently, web searches seem to turn up some out-dated info on how to do 
this.


 - Dan

Re: Reporting a bug that affects more than one package

[Terry Roy]

Hi,

On 21/12/2017 19:26, Andy Smith wrote:


From time to time Debian Developers scan for previously-known bugs

in the entire archive and apply a Mass Bug Filing to alert package
maintainers of the problem.

Good to know. Thanks.


I think you should report essentially the same bug in the other
package, with a mention to your previous bug number. If you have a
way to detect the presence of the bug then include details of that.
Hopefully someone with the ability to do an MBF will then be able to
do so.


I've reported it to both packages I've found it in as well as the fix 
for it.



Your quest for a way to find buggy packages might be helped by
https://codesearch.debian.net/

Cheers,
Andy


I did a search there but it seems it's for source code only.

Thanks.

--
Terry

Re: Reporting a bug that affects more than one package

[Andy Smith]

Hello,

On Thu, Dec 21, 2017 at 06:30:52PM -0600, Terry Roy wrote:
> […] reported the bug. I've just run across it again on a fresh
> install of another package. I've reported that bug but clearly
> this seems to be an issue involving the use of "su -" in postinst.
> 
> My problem is that I have no clue where I should report this. Does anyone
> have any suggestions? TIA

>From time to time Debian Developers scan for previously-known bugs
in the entire archive and apply a Mass Bug Filing to alert package
maintainers of the problem.

I think you should report essentially the same bug in the other
package, with a mention to your previous bug number. If you have a
way to detect the presence of the bug then include details of that.
Hopefully someone with the ability to do an MBF will then be able to
do so.

Your quest for a way to find buggy packages might be helped by
https://codesearch.debian.net/

Cheers,
Andy

-- 
https://bitfolk.com/ -- No-nonsense VPS hosting

Re: Reporting a bug that affects more than one package

[Ben Finney]

Terry Roy  writes:

> I found a bug in Debian's latest 9.3 update where the postinst script
> of a package contained the line:
>
> "su - username do something"

I've just run this command:

grep "su - " /var/lib/dpkg/info/*

which returned no results on a system with thousands of packages
installed. So I tentatively conclude that it's not a common pattern.

> I've just run across it again on a fresh install of another package.
> I've reported that bug but clearly this seems to be an issue involving
> the use of "su -" in postinst.

You should proceed this way, IMO. Report a bug against each package that
uses that invocation.


I note that a similar pattern, invoking ‘su’ to run commands as another
user, is in the ‘postgresql-common’ package:

su -s /bin/sh postgres -c "… more commands …"

If you alter the postinst script to use that pattern instead, does it
avoid the problem you describe? If so, you can suggest that to the
package maintainer.

-- 
 \  “Fox News gives you both sides of every story: the President's |
  `\  side and the Vice President's side.” —Steven Colbert, 2006-04-29 |
_o__)  |
Ben Finney

Reporting a bug that affects more than one package

[Terry Roy]

Hi folks,

I found a bug in Debian's latest 9.3 update where the postinst script of 
a package contained the line:


"su - username do something"

It broke the package upgrade because the use of the dash "-" invokes a 
full shell and we have a file in /etc/profile.d that somehow conflicted. 
I removed the /etc/profile.d file and reinstalled with no problem. Put 
my /etc/profile.d file back and reported the bug. I've just run across 
it again on a fresh install of another package. I've reported that bug 
but clearly this seems to be an issue involving the use of "su -" in 
postinst.


My problem is that I have no clue where I should report this. Does 
anyone have any suggestions? TIA


--
Terry

Re: montage disque externe SSD

[Gaëtan Perrier]

Le vendredi 22 décembre 2017 à 00:13 +0100, Pascal Hambourg a écrit :
> Le 21/12/2017 à 00:13, Gaëtan Perrier a écrit :
> > Bonjour,
> > 
> > Sur mes SSD internes j'utilise l'option discard lors du montage. Mais
> > comment
> > faire pour que cette option soit utilisée lors du montage automatique d'un
> > SSD
> > externe en USB3?
> 
> Si c'est un système de fichiers ext4 :
> 
> tune2fs -o discard /dev/sdXN

Le problème c'est que ça ne semble pas être pris en compte par le montage
automatique de Gnome ...

# tune2fs -l /dev/sde1
...
Default mount options:user_xattr acl discard
...

# mount
...
/dev/sde1 on /media/gpe/81367f6d-2ab4-400e-add1-e9887485f5e5 type ext4
(rw,nosuid,nodev,relatime,data=ordered,uhelper=udisks2)


Gaëtan

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

Re: NAT avec plusieurs interfaces publiques

[Pascal Hambourg]

Le 21/12/2017 à 18:25, Olivier a écrit :

Bonjour,

Je prépare une installation dans laquelle un routeur (une machine sous
Debian Stretch) aura 3 interfaces logiques:
une interface eth0.30 vers un réseau local
une interface eth0.20 vers un lien Internet
une interface eth0.10 vers un autre lien Internet

Je souhaite répartir, en fonction de leur adresse IP, les utilisateurs du
réseau local vers les deux liens Internet.:
si l'adresse de l'utilisateur est  dans le sous-réseau 10.50.0.0/24, sortir
sur Internet en nattant avec l'interface eth0.10,
si l'adresse de l'utilisateur est  dans le sous-réseau 10.50.1.0/24, sortir
sur Internet en nattant avec l'interface eth0.20.

Comment configurer cela ?


J'ai un script iptables qui marque le trafic entrant avec une règle du type
iptables -t mangle -A PREROUTING -s 10.50.1.0/24 -j MARK --set-mark 2


Le marquage des paquets est inutile.


J'ai une autre règle qui j'espérais, devrait NATer, le trafic dont la
marque est spécifique:
iptables -t nat -A POSTROUTING -m mark --mark 2 -o eth0.20 -j SNAT
--to-source 2.2.2.2


A condition que les paquets en question sortent par l'interface 
spécifiée. Mais dans ce cas, inutile de se baser sur la marque, 
l'interface de sortie suffit. Pour rappel l'option -o introduit un 
critère de correspondance, pas une action.



Cette dernière règle ne semble pas exécutée pour un utilisateur dont
l'adresse est bien dans le réseau 10.50.1.0/24.
À la place, c'est la règle "par défaut" comme celle ci-après qui semble
exécutée:
iptables -t nat -A POSTROUTING -o eth0.10 -j SNAT --to-source 2.2.2.2


Parce que c'est par eth0.10 que les paquets sortent.

Il faut faire du routage avancé. Pas besoin de marque puisqu'on peut se 
baser sur l'adresse source.


ip rule add from 10.50.1.0/24 table 2
ip route add default via  dev eth0.20 table 2
ip route add 10.50.0.0/23 dev eth0.30 table 2

Re: montage disque externe SSD

[Pascal Hambourg]

Le 21/12/2017 à 00:13, Gaëtan Perrier a écrit :

Bonjour,

Sur mes SSD internes j'utilise l'option discard lors du montage. Mais comment
faire pour que cette option soit utilisée lors du montage automatique d'un SSD
externe en USB3?


Si c'est un système de fichiers ext4 :

tune2fs -o discard /dev/sdXN

Re: on-screen artifacts (red pixels) at high resolution with Intel HD 630 (Kaby Lake)

[Felix Miata]

Alexandre Rossi composed on 2017-12-21 23:01 (UTC+0100):

>> How long is the cable? Do you have access to another to try? ~20% of the HDMI
>> cables I have are either useless or flaky with at least one device.

> Same symptoms with another cable.

>> Does the TV label any of its HDMI ports differently from the others? One of 
>> mine
>> does, labeling one HDMI-3/DVI. It does behave differently than the others.

> Same symptoms with the other TV ports, some being worse than others.

>>> Outputting to another 1920x1080 monitor works well.

>> Do you have another, to which you could connect using DisplayPort or HDMI?

> Yes, another screen is working perfectly through the same HDMI cable.
I didn't ask very well. What I was looking for was a display that gives you a
choice to use either DP or HDMI, idea being to see if the problem is avoided by
using the motherboard's DP output (if it has one, as mine with B250 chipset
does), even if a DP to HDMI adapter or cable would be required.

>> The log you previously attached reports "Indeterminate output size" from the
>> Samsung 659's EDID. I wonder if it would change anything to include an output
>> size in xorg.conf?

>> Same log shows both 60.0 and 59.9 1920x1080 modes. You could try forcing to 
>> use
>> the other, or 50.0, at least to see if the problem remains.

> $ xrandr # bad picture
> Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 8192 x 8192
> DP-1 disconnected primary (normal left inverted right x axis y axis)
> HDMI-1 disconnected (normal left inverted right x axis y axis)
> HDMI-2 connected 1920x1080+0+0 (normal left inverted right x axis y
> axis) 160mm x 90mm
>1920x1080 60.00*+  50.0059.9430.0025.0024.00
> 29.9723.98
>1920x1080i60.0050.0059.94
...
> DP-2 disconnected (normal left inverted right x axis y axis)
> HDMI-3 disconnected (normal left inverted right x axis y axis)

> $ xrandr -s 1920x1080 -r 30 # good picture, yeah! thanks!
> $ xrandr # seems like I switched to 1080i
> [...]
>1920x1080 60.00 +  50.0059.9430.0025.0024.00
> 29.9723.98
>1920x1080i60.00*   50.0059.94
> [...]

> The problem remains using xrandr -s 1920x1080 -r 50.

> What I do not understand is :
> $ xrandr -s 1920x1080 -r 59.94
> Rate 59.94 Hz not available for this size
> Because the refresh rate is listed. Seems like a rounded output?

> Also, documentation is lacking for xorg.conf.d (or I could not find
> it) because the following does not seem to be taken into account :
> $ cat /etc/X11/xorg.conf.d/20-samsung.conf
> Section "Monitor"
> Identifier "SAMSUNG"
> Option "PreferredMode" "1920x1080i" # or whatever value
> EndSection  
Sometimes without a logically connected 'Section "Device"', legitimate monitor
options don't produce expected behavior.

Try adding this to the section, in addition to "1920x1080" (without the i), or
instead of:

VertRefresh 29-51

> so I'm stuck with the xrandr call in ~/.xsession .  

Not likely. Any xrandr that works in ~/.xsession (user-specific) should work in
/etc/X11/ (global). :-) Try creating /etc/X11/Xsession.d/myscript if the
xorg.conf approach is too resistant.

>>> I would also love
>>> to get any other idea or pointer regarding solving this.

>> Bring it up on:
>> http://lists.freedesktop.org/mailman/listinfo/intel-gfx

> Will do when I understand refresh rate manipulation a bit more.

> Thanks _a lot_ for the pointers.

:-)

I've acquired a new Kaby Lake 630 since last thread reply, but I've only used it
with DisplayPort cable and on 2560x1080 and 1680x1050 screens so far. Current
dmesg running 4.9.65-3 kernel reports:

firmware: failed to load i915/kbl_dmc_ver1_01.bin (-2)
-- 
"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 8 and Debian 9 Dual Boot

[Felix Miata]

Dan Norton composed on 2017-12-21 16:53 (UTC-0500):

> Felix Miata wrote:

>> Dan Norton composed on 2017-12-21 14:07 (UTC-0500):

>>> There are still mysteries I have not solved. For some reason, GRUB has
>>> decided that after POST, you only need 3 seconds to choose which
>>> installation to boot. GRUB has resisted my efforts to change that
>>> timeout value. I've been able to change the boot order in NVRAM, but not
>>> the timeout.

>> efibootmgr -t ##

> Yes, it seems like that should work, but currently:

> # efibootmgr
> BootCurrent: 
> Timeout: 11 seconds  # ... and the actual timeout is 3
> BootOrder: 0003,0001,,0002,0006,0004,0005
> Boot* debian
> Boot0001* USB Floppy/CD
> Boot0002* USB Hard Drive
> Boot0003* ATAPI CD-ROM Drive
> Boot0004* Unknown Device
> Boot0005* USB Floppy/CD
> Boot0006* Hard Drive

> Doing it again (See definition of insanity [1])
> # efibootmgr -t 12
> BootCurrent: 
> Timeout: 12 seconds
> BootOrder: 0003,0001,,0002,0006,0004,0005
> Boot* debian
> Boot0001* USB Floppy/CD
> Boot0002* USB Hard Drive
> Boot0003* ATAPI CD-ROM Drive
> Boot0004* Unknown Device
> Boot0005* USB Floppy/CD
> Boot0006* Hard Drive

> Well, that changed it from 3 to 4 (!?). Strange.

> [1] "Insanity is doing the same thing over & over again and expecting a 
> different result." - Einstein

It's not so easy to figure out when POST is over with UEFI. Here, it seems
efibootmgr -t provides extra delay beyond what the BIOS defines for you to make
a selection from its own boot device selection menu, which requires an F12
keystroke here to see.

The timeout after appearance of Grub's menu is supposed to be controlled by
/etc/default/grub's GRUB_TIMEOUT=, which shows up here in Stretch's grub.cfg
first on line 86, a few lines before "### END /etc/grub.d/00_header ###".
-- 
"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 8 and Debian 9 Dual Boot

[Joe]

On Thu, 21 Dec 2017 16:53:19 -0500
Dan Norton  wrote:


> [1] "Insanity is doing the same thing over & over again and expecting
> a different result." - Einstein
> 

Probably the single most stupid thing he ever said, given that he also
said 'God does not play dice', showing that he knew what dice were and
what they were used for.

He also presumably had never had to fix an intermittent fault...

-- 
Joe

Re: on-screen artifacts (red pixels) at high resolution with Intel HD 630 (Kaby Lake)

[Alexandre Rossi]

>> Two other PCs (Linux and Windows) going through the same HDMI cable to
>> the same TV and same TV port using the same 1920x1080 resolution work
>> perfectly.
>
> How long is the cable? Do you have access to another to try? ~20% of the HDMI
> cables I have are either useless or flaky with at least one device.

Same symptoms with another cable.

> Does the TV label any of its HDMI ports differently from the others? One of 
> mine
> does, labeling one HDMI-3/DVI. It does behave differently than the others.

Same symptoms with the other TV ports, some being worse than others.

>> Outputting to another 1920x1080 monitor works well.
>
> Do you have another, to which you could connect using DisplayPort or HDMI?

Yes, another screen is working perfectly through the same HDMI cable.

>> I've tried multiple combinations of Xorg setup with no working setup :
>> - modesetting Xorg driver with glamor or none as AccelMethod
>> - intel Xorg driver with sna or uxa as AccelMethod, DRI 2 or 3.
>> I've also tried with i915.enable_rc6=0 and this does not change anything.
>
> The log you previously attached reports "Indeterminate output size" from the
> Samsung 659's EDID. I wonder if it would change anything to include an output
> size in xorg.conf?
>
> Same log shows both 60.0 and 59.9 1920x1080 modes. You could try forcing to 
> use
> the other, or 50.0, at least to see if the problem remains.

$ xrandr # bad picture
Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 8192 x 8192
DP-1 disconnected primary (normal left inverted right x axis y axis)
HDMI-1 disconnected (normal left inverted right x axis y axis)
HDMI-2 connected 1920x1080+0+0 (normal left inverted right x axis y
axis) 160mm x 90mm
   1920x1080 60.00*+  50.0059.9430.0025.0024.00
29.9723.98
   1920x1080i60.0050.0059.94
   1600x1200 60.00
   1680x1050 59.88
   1280x1024 75.0260.02
   1440x900  74.9859.90
   1280x960  60.00
   1360x768  60.02
   1280x800  59.91
   1152x864  75.00
   1280x720  60.0050.0059.94
   1024x768  75.0370.0760.00
   832x624   74.55
   800x600   72.1975.0060.32
   720x576   50.00
   720x480   60.0059.94
   640x480   75.0072.8166.6760.0059.94
   720x400   70.08
DP-2 disconnected (normal left inverted right x axis y axis)
HDMI-3 disconnected (normal left inverted right x axis y axis)

$ xrandr -s 1920x1080 -r 30 # good picture, yeah! thanks!
$ xrandr # seems like I switched to 1080i
[...]
   1920x1080 60.00 +  50.0059.9430.0025.0024.00
29.9723.98
   1920x1080i60.00*   50.0059.94
[...]

The problem remains using xrandr -s 1920x1080 -r 50.

What I do not understand is :
$ xrandr -s 1920x1080 -r 59.94
Rate 59.94 Hz not available for this size
Because the refresh rate is listed. Seems like a rounded output?

Also, documentation is lacking for xorg.conf.d (or I could not find
it) because the following does not seem to be taken into account :
$ cat /etc/X11/xorg.conf.d/20-samsung.conf
Section "Monitor"
Identifier "SAMSUNG"
Option "PreferredMode" "1920x1080i" # or whatever value
EndSection

so I'm stuck with the xrandr call in ~/.xsession .

>> I would also love
>> to get any other idea or pointer regarding solving this.
>
> Bring it up on:
> http://lists.freedesktop.org/mailman/listinfo/intel-gfx

Will do when I understand refresh rate manipulation a bit more.

Thanks _a lot_ for the pointers.

Alex

Re: A sox Question about the silence Module

[Andre Majorel]

On 2017-12-21 14:17 -0600, Martin McCormick wrote:

> sox -t .wav input.wav -t .wav output.wav silence -l 1 0 '-39d' -1 0.5 '-45d'
> 
> The field containing 0.5 which is the second-to-the-last  field
> is the only thing that does not work.  The script records while
> there is sound but the 0.5 seconds of blank recording after the
> sound doesn't happen.
> 
>   What you hear are 3 beeps with a tiny gap in between that
> never changes no matter what one sets that second-to-the-last
> field to. [...]

Are you sure that -l accepts real numbers for its 5th argument ?

-- 
André Majorel 
Discriminating spammers prefer lists.debian.org.

Re: aplay fails on amd64 laptop

[deloptes]

Pierre Frenkiel wrote:

> card 1: Generic [HD-Audio Generic], device 0: ALC233 Analog [ALC233
> Analog] Subdevices: 1/1
> Subdevice #0: subdevice #0

you need to use hw:1.0
as you target your second card, or configure snd module to initialize the
analog as first card

regards

Re: Debian 8 and Debian 9 Dual Boot

[Dan Norton]

On 12/21/2017 02:54 PM, Felix Miata wrote:

Dan Norton composed on 2017-12-21 14:07 (UTC-0500):


2. You will make extra work for yourself by having a common swap
partition for all installations. With the common swap, each new
installation gave rise to these messages:
    a. "gave up waiting for suspend/resume device"
    b. "a start job is running for dev-disk-by\..."
    c. "failed to connect to lvmetad"
STW can reveal ways to avoid these messages, but they are a PITA and
avoidable by each volume group having its own swap.

Except with a first Linux installation, I tell the partitioner not to use swap,
then add it by LABEL to fstab after installing. The problem is that the
installer insists that the swap partition needs to be formatted, destroying the
validity of swap's UUID in the fstabs of the previous installations.


There are still mysteries I have not solved. For some reason, GRUB has
decided that after POST, you only need 3 seconds to choose which
installation to boot. GRUB has resisted my efforts to change that
timeout value. I've been able to change the boot order in NVRAM, but not
the timeout.

efibootmgr -t ##


Yes, it seems like that should work, but currently:

# efibootmgr
BootCurrent: 
Timeout: 11 seconds  # ... and the actual timeout is 3
BootOrder: 0003,0001,,0002,0006,0004,0005
Boot* debian
Boot0001* USB Floppy/CD
Boot0002* USB Hard Drive
Boot0003* ATAPI CD-ROM Drive
Boot0004* Unknown Device
Boot0005* USB Floppy/CD
Boot0006* Hard Drive

Doing it again (See definition of insanity [1])
# efibootmgr -t 12
BootCurrent: 
Timeout: 12 seconds
BootOrder: 0003,0001,,0002,0006,0004,0005
Boot* debian
Boot0001* USB Floppy/CD
Boot0002* USB Hard Drive
Boot0003* ATAPI CD-ROM Drive
Boot0004* Unknown Device
Boot0005* USB Floppy/CD
Boot0006* Hard Drive


Well, that changed it from 3 to 4 (!?). Strange.

[1] "Insanity is doing the same thing over & over again and expecting a 
different result." - Einstein

Re: got a new one

[Gene Heskett]

On Thursday 21 December 2017 13:13:06 Brian wrote:

> On Thu 21 Dec 2017 at 12:37:04 -0500, Gene Heskett wrote:
> > On Thursday 21 December 2017 12:08:33 Brian wrote:
> > > On Thu 21 Dec 2017 at 11:41:01 -0500, Gene Heskett wrote:
> > > > I can turn that option off on a job by job basis I assume.
> > >
> > > You mean cupsdisable? You could, but it wouldn't ordinarily be
> > > used.
> >
> > No, I was referring to the rotate and fit option. About the only
> > place where I could actually make sense of that would be in printing
> > camera images where the camera may have been held up-down for a
> > portrait image.
>
> You can turn that option off and on on a job by job basis. It's
> default is on; personally, I would leave it like that. Note that the
> Portrait and Landscape options are not applied when Auto Rotate is on.

I had not noted that, figuring I clicked the wrong button.

Thanks.

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 

A sox Question about the silence Module

[Martin McCormick]

I am not new to sox but I am asking to see if I have
missed something because a sox script I am using is mostly
working but not quite.

I am attempting to remove long silent pauses in a
recording of people talking and what is supposed to happen is
that sound is recorded during voice or noises and the recording
should continue for a short period of time after the noise so as
to smooth out what one hears and make the conversation sound
more normal.  I test the script with a recording of 3 beeps with
dead silence in between of periods ranging from 4 or 5 seconds up
to a minute.  The silence parameters are such that one should
hear 3 beeps, each a half-second apart in the processed output.

For those familiar with an electronic voice operated
relay or VOX, the delay is set to 1/2 second and there is where
the trouble is.  

To get this effect, one sets a line of sox script as follows:

#! /bin/sh
sox -t .wav input.wav -t .wav output.wav silence -l 1 0 '-39d' -1 0.5 '-45d'

The field containing 0.5 which is the second-to-the-last  field
is the only thing that does not work.  The script records while
there is sound but the 0.5 seconds of blank recording after the
sound doesn't happen.

What you hear are 3 beeps with a tiny gap in between that
never changes no matter what one sets that second-to-the-last
field to.  If you set it to a negative number, sox exits with an
error so it is reading that value, but there is no vox delay so
the actual recordings of conversation can sometimes sound a bit
odd as nobody seems to ever take a breath. One can set that
duration field to just about any number of seconds, minutes or
hours and all the silence in the 3 beeps recording is still just
a slight gap between each beep.  It never varies.

Maybe one of you tried a script like this and got it to
work and can tell us what is wrong as I have been messing with
this script for a couple of days.

The manual pages for sox and soxeffects state that the -l
flag is supposed to further smooth out the sound by recovering a
little bit of the silence that was there before the next sound.
It seems to also have no effect.

Thanks for any good ideas.  It is almost good but not
quite.

Martin McCormick
WB5AGZ

Re: NAT avec plusieurs interfaces publiques

[Christophe]

Hello

Le 21/12/2017 à 18:25, Olivier a écrit :


Je prépare une installation dans laquelle un routeur (une machine sous 
Debian Stretch) aura 3 interfaces logiques:

une interface eth0.30 vers un réseau local
une interface eth0.20 vers un lien Internet
une interface eth0.10 vers un autre lien Internet

Je souhaite répartir, en fonction de leur adresse IP, les utilisateurs 
du réseau local vers les deux liens Internet.:
si l'adresse de l'utilisateur est  dans le sous-réseau 10.50.0.0/24 
, sortir sur Internet en nattant avec l'interface 
eth0.10,
si l'adresse de l'utilisateur est  dans le sous-réseau 10.50.1.0/24 
, sortir sur Internet en nattant avec l'interface 
eth0.20.


Comment configurer cela ?


J'ai un script iptables qui marque le trafic entrant avec une règle du type
iptables -t mangle -A PREROUTING -s 10.50.1.0/24  
-j MARK --set-mark 2


C'est un bon début :)



J'ai une autre règle qui j'espérais, devrait NATer, le trafic dont la 
marque est spécifique:
iptables -t nat -A POSTROUTING -m mark --mark 2 -o eth0.20 -j SNAT 
--to-source 2.2.2.2


C'est encore un bon début.



Cette dernière règle ne semble pas exécutée pour un utilisateur dont 
l'adresse est bien dans le réseau 10.50.1.0/24 .
À la place, c'est la règle "par défaut" comme celle ci-après qui semble 
exécutée:

iptables -t nat -A POSTROUTING -o eth0.10 -j SNAT --to-source 2.2.2.2



iptables ne se suffira pas à lui même pour gérer la question du routage 
des paquets. Ce sont bien deux étapes différentes vu du noyau Linux.


(
si ce n'est 3 :
mark à l'entrée sur une interface : iptables -t mangle (PREROUTING)
forward : ip route & ip rule
sortie de la machine avec NAT : iptables -t nat (POSTROUTING)
)

Il ne manque à mon avis pas grand chose à ton setup; il faut jouer un 
peu avec la commande "ip" : ajouter une table de routage spéciale par 
interface WAN , et ajouter des "rule" en fonction du trafic qui a été 
précédemment "marké" dans la mangle d'iptables en PREROUTING.


Je le fais de mémoire,

ip route add table 2 default via  dev eth0.20
ip rule add fwmark 2 table 2

Ca peut par contre se compliquer un peu plus si les deux interfaces 
"Wan" sont en adressage dynamique.


La bible pour ce genre d'utilisations, c'est le "LARTC"
http://lartc.org/


@+
Christophe.

Re: Debian networking - accessing public-side servers from a private network

[Pascal Hambourg]

Now you seem to have found a rather good solution (not based on some 
hackish NAT, convoluted routing or complex split DNS), it may be uselee 
to carry on this thread, but I am just interested and curious.


Le 21/12/2017 à 12:10, Phil Reynolds a écrit :

On Thu, 21 Dec 2017 07:23:06 +0100
Pascal Hambourg  wrote:


How are TCP/IP parameters configured on the client ?
Could you show its routing table ?


Output of "route" on it:

Destination 192.168.0.0 Gateway * Genmask 255.255.255.0 Flags U Metric
0 Ref 0 Use 0 Iface wlan0


Is that all ? No default route ?
How can it reach any address outside the private subnet ?


Output of "route -A inet6" is much longer - see
http://paste.debian.net/1001796 - note that this is "as is", I haven't
concealed anything.


That does not look like an IPv6 routing table, not even like any routing 
table. It rather looks like some key=value pair config file. Here are 
the few first lines of what I see :


activer_ajout_hosts="non"
activer_antispoofing="non"
activer_apache="non"
activer_bash_completion="oui"
activer_bonding_eth0="non"


All the IPv4 and IPv6 nameservers used by the client must resolve
the name into the private address. If they also serve the public
zone, you must set up "split DNS" to server different versions for
private and public clients.


Unfortunately I have found no way to override the radvd-provided DNS
server addresses - otherwise I would have done this.

Aren't you in control of the router configuration and which IPv6 DNS
servers are advertised in the RAs it sends (radvd ?), and of these
servers behaviour ?


I am in control but it's a case of "can it be done and if so how?".


If the IPv6 router advertisements are sent by radvd on the router, the 
RDNSS option advertising the IPv6 DNS addresses are defined in the 
config file /etc/radvd.conf. The defined DNS server(s), along with the 
IPv4 ones, should be under your control and set up to serve different 
records for the Asterisk server name based on the query source address. 
This is called split DNS. In BIND the feature is named "views".

Re: Debian 8 and Debian 9 Dual Boot

[Felix Miata]

Dan Norton composed on 2017-12-21 14:07 (UTC-0500):

> 2. You will make extra work for yourself by having a common swap 
> partition for all installations. With the common swap, each new 
> installation gave rise to these messages:

>    a. "gave up waiting for suspend/resume device"

>    b. "a start job is running for dev-disk-by\..."

>    c. "failed to connect to lvmetad"

> STW can reveal ways to avoid these messages, but they are a PITA and
> avoidable by each volume group having its own swap.

Except with a first Linux installation, I tell the partitioner not to use swap,
then add it by LABEL to fstab after installing. The problem is that the
installer insists that the swap partition needs to be formatted, destroying the
validity of swap's UUID in the fstabs of the previous installations.

> There are still mysteries I have not solved. For some reason, GRUB has 
> decided that after POST, you only need 3 seconds to choose which 
> installation to boot. GRUB has resisted my efforts to change that 
> timeout value. I've been able to change the boot order in NVRAM, but not 
> the timeout. 

efibootmgr -t ##
-- 
"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 8 and Debian 9 Dual Boot

[Dan Norton]

On 12/21/2017 04:36 AM, Felix Miata wrote:

Felix Miata composed on 2017-11-29 13:55 (UTC-0500):


Dan Norton composed on 2017-11-28 22:15 (UTC-0500):

dan@debian8:~$ sudo fdisk /dev/sda
Command (m for help): p
Disk /dev/sda: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: A615A904-0620-459F-BF44-5E53E54FDF24
Device Start    End    Sectors   Size Type
/dev/sda1   2048 411647 409600   200M BIOS boot
/dev/sda2 411648   16783359   16371712   7.8G Linux swap
/dev/sda3   16783360  151001087  134217728    64G Linux LVM
/dev/sda4  151001088  285218815  134217728    64G Linux LVM
/dev/sda5  285218816  419436543  134217728    64G Linux LVM
/dev/sda6  419436544  553654271  134217728    64G Linux LVM
/dev/sda7  553654272 1953525134 1399870863 667.5G Linux filesystem
Is there a problem here?

Maybe. I don't have any GPT-partitioned disks...

No longer the case. I bought a G250 Kaby Lake Intel motherboard. I currently
have Stretch, openSUSE Tumbleweed and openSUSE 15.0 Alpha installed. openSUSE
42.3's installer hangs in the bootloader configuration step.
https://bugzilla.opensuse.org/show_bug.cgi?id=1073201

http://fm.no-ip.com/Tmp/Dfsee/gb250L02.txt  is my partition log. The upper part
is generated by the partitioner I use. The bottom is gpart -l output for 
comparison.

I haven't seen you post the debian-user list in a while. How's multiboot going
for you?


Not bad, actually. I'm nearly ready to try multiboot with GPT again on 
my (elderly) HP desktop machine. It only has a 1T sda, but that seems 
like wretched excess.


Currently jessie, stretch, and buster are installed with primary/logical 
partitioning. Each is in a separate volume group, with logical volumes 
for /, /var, /tmp, /home, and swap. IMHO, the following guidelines are 
helpful:


1. Do all partitioning with the installer. Don't try to prepare the EFI 
for example with other partitioners. Partitioning can be daunting, but 
if you patiently and sometimes repeatedly use the installer UI, you can 
set up the desired partitioning. The installer UI could be improved. :-)


2. You will make extra work for yourself by having a common swap 
partition for all installations. With the common swap, each new 
installation gave rise to these messages:


  a. "gave up waiting for suspend/resume device"

  b. "a start job is running for dev-disk-by\..."

  c. "failed to connect to lvmetad"

STW can reveal ways to avoid these messages, but they are a PITA and 
avoidable by each volume group having its own swap.


There are still mysteries I have not solved. For some reason, GRUB has 
decided that after POST, you only need 3 seconds to choose which 
installation to boot. GRUB has resisted my efforts to change that 
timeout value. I've been able to change the boot order in NVRAM, but not 
the timeout.


Before moving on to multiboot with LVM and GPT, I'd like to change the 
menu entries to something more consistent. The last install is referred 
to as "Debian GNU/Linux" but that's ambiguous. Which Debian GNU/Linux? 
If each entry was in the form "Debian GNU/Linux 9 (stretch) (on 
/dev/mapper/vol2-root)" that would really be explicit. Also I want some 
more time to mull over which to boot.


 - Dan

aplay fails on amd64 laptop

[Pierre Frenkiel]

hi,
the sound works perfectly with vlc or audacity, but I can't make aplay to work.
the "aplay -l" output is:
    List of PLAYBACK Hardware Devices 
   card 0: HDMI [HDA ATI HDMI], device 3: Generic Digital [Generic Digital]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
   card 1: Generic [HD-Audio Generic], device 0: ALC233 Analog [ALC233 Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0

and both audacity and vlc actually use the  HD-Audio output.

After configuring ~/.aoundrc like this:

pcm.!default {
type hw
card 1
}

ctl.!default {
type hw
card 1
}

running "aplay file.wav" gives:
   aplay: set_params:1081: Sample format non available
   Available formats:
   - S16_LE
   - S32_LE

I get the same thing with all .wav files I try.

This problem is specific to my amd64 laptop, as I don't have it on my desktop,
running the same OS version (Stretch), and with the same files.

Looking at Google didn't gave me any useful information.
Has anybody an idea?

best regards,
--
Pierre Frenkiel

Re: Stretch: Greeter powers down and locks monitors

[David Christensen]

On 12/21/17 04:20, Roger Price wrote:

On Wed, 20 Dec 2017, David Christensen wrote:


On 12/20/17 02:49, Roger Price wrote:
Hi, I'm running stretch with Xfce.  Gnome is also installed.  The 
login greeter appears correctly, and allows login, but if I leave the 
"greeter" screen too long, then something intervenes and puts the two 
monitors into a sleep mode (iiyama E1700S orange light).  I cannot 
find any key combination which wakes up gdm3.


Have you tried right-clicking with the mouse?  My laptop with Stretch, 
Xfce, and the default login manager (lightdm?) requires this.


I tried mouse buttons 1, 2 and 3.  I also tried Ctl-Mouse 1/2/3, 
Ctl-Alt-Mouse 1/2/3, Ctl-RightAlt-Mouse 1/2/3, Shift-Mouse 1/2/3, etc. 
But no success.


Ok.  It was worth a try.


On 12/21/17 04:01, Roger Price wrote:
> In file /etc/X11/default-display-manager I replaced /usr/sbin/gdm3 with
> /usr/sbin/lightdm and restarted the box. It got as far as run level 5
> but with no display manager. journalctl reports that the "Gnome display
> Manager" could not be started, despite five attempts.

As I use Debian 9, I am finding that some things are configured by 
systemd, some things by old-school files, and many by both.  What a 
confusing mess...



If you like Xfce, I suggest you do a backup/ wipe/ install/ update/ 
restore cycle, selecting Xfce (and only Xfce) as your desktop.  That's 
what I do, and it works (mostly).



David

aqemu and network bridging.

[G]

Hi
Im trying to setup a VM with aqemu and i would like my vm to connect to
the local network via dhcp.

I followed the instructions at

https://wiki.debian.org/QEMU

> my /etc/network/interfaces is
> 
> 
> # This file describes the network interfaces available on your system
> # and how to activate them. For more information, see interfaces(5).
> 
> source /etc/network/interfaces.d/*
> 
> # The loopback network interface
> auto lo
> iface lo inet loopback
> 
> # The primary network interface
> #allow-hotplug enp1s0
> #iface enp1s0 inet dhcp
> 
> #allow-hotplug enp1s0
> iface enp1s0 inet manual
> 
> auto br0
> iface br0 inet dhcp
>pre-up ip tuntap add dev tap0 mode tap user gpdsb
>pre-up ip link set tap0 up
>bridge_ports all tap0
>bridge_stp off
>bridge_maxwait 0
>bridge_fd  0
>post-down ip link set tap0 down
>post-down ip tuntap del dev tap0 mode tap


I configured my aqemu
On the network section i got

Network card model:Default
Connection mode: Open a TUN/TAP interface
Mac address: 00:a1:0f:75:ff:b3 (this is generated)
TUN/TAP Script: (I unchecked this)
Interface Name: tap0



I have the following problems.

1.My computer takes too long to start.
It spends alot of time at

> Started Network Manager Wait Online
> A start job is running for Raiso network interface

2.Also i use a livecd on aqemu to test network and it doesn't connect to
the internet.



my dmesg is (i have some errors at the end)


> $ sudo dmesg
> [0.00] Linux version 4.9.0-4-amd64 (debian-ker...@lists.debian.org) 
> (gcc version 6.3.0 20170516 (Debian 6.3.0-18) ) #1 SMP Debian 4.9.65-3 
> (2017-12-03)
> [0.00] Command line: BOOT_IMAGE=/vmlinuz-4.9.0-4-amd64 
> root=/dev/mapper/laptop--vg-root ro quiet splash
> [0.00] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point 
> registers'
> [0.00] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
> [0.00] x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
> [0.00] x86/fpu: Supporting XSAVE feature 0x008: 'MPX bounds registers'
> [0.00] x86/fpu: Supporting XSAVE feature 0x010: 'MPX CSR'
> [0.00] x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
> [0.00] x86/fpu: xstate_offset[3]:  832, xstate_sizes[3]:   64
> [0.00] x86/fpu: xstate_offset[4]:  896, xstate_sizes[4]:   64
> [0.00] x86/fpu: Enabled xstate features 0x1f, context size is 960 
> bytes, using 'compacted' format.
> [0.00] x86/fpu: Using 'eager' FPU context switches.
> [0.00] e820: BIOS-provided physical RAM map:
> [0.00] BIOS-e820: [mem 0x-0x0009e7ff] usable
> [0.00] BIOS-e820: [mem 0x0009e800-0x0009] reserved
> [0.00] BIOS-e820: [mem 0x000e-0x000f] reserved
> [0.00] BIOS-e820: [mem 0x0010-0x707a0fff] usable
> [0.00] BIOS-e820: [mem 0x707a1000-0x707a1fff] ACPI NVS
> [0.00] BIOS-e820: [mem 0x707a2000-0x707cbfff] reserved
> [0.00] BIOS-e820: [mem 0x707cc000-0x70879fff] usable
> [0.00] BIOS-e820: [mem 0x7087a000-0x71179fff] reserved
> [0.00] BIOS-e820: [mem 0x7117a000-0x8738efff] usable
> [0.00] BIOS-e820: [mem 0x8738f000-0x87d7efff] reserved
> [0.00] BIOS-e820: [mem 0x87d7f000-0x87f7efff] ACPI NVS
> [0.00] BIOS-e820: [mem 0x87f7f000-0x87ffefff] ACPI 
> data
> [0.00] BIOS-e820: [mem 0x87fff000-0x87ff] usable
> [0.00] BIOS-e820: [mem 0x8800-0x880f] reserved
> [0.00] BIOS-e820: [mem 0x8880-0x8b7f] reserved
> [0.00] BIOS-e820: [mem 0xe000-0xefff] reserved
> [0.00] BIOS-e820: [mem 0xfd00-0xfe7f] reserved
> [0.00] BIOS-e820: [mem 0xfeb0-0xfeb03fff] reserved
> [0.00] BIOS-e820: [mem 0xfec0-0xfec00fff] reserved
> [0.00] BIOS-e820: [mem 0xfed0-0xfed00fff] reserved
> [0.00] BIOS-e820: [mem 0xfed1-0xfed19fff] reserved
> [0.00] BIOS-e820: [mem 0xfed84000-0xfed84fff] reserved
> [0.00] BIOS-e820: [mem 0xfee0-0xfee00fff] reserved
> [0.00] BIOS-e820: [mem 0xffa1-0x] reserved
> [0.00] BIOS-e820: [mem 0x0001-0x0002737f] usable
> [0.00] NX (Execute Disable) protection: active
> [0.00] SMBIOS 2.8 present.
> [0.00] DMI: LENOVO 80SR/Toronto 5A1, BIOS 0XCN42WW 04/21/2017
> [0.00] e820: update [mem 0x-0x0fff] usable ==> reserved
> [0.00] e820: remove [mem 0x000a-0x000f] usable
> [0.00] e820: last_pfn = 0x273800 max_arch_pfn = 0x4
> [

Re: got a new one

[Brian]

On Thu 21 Dec 2017 at 12:37:04 -0500, Gene Heskett wrote:

> On Thursday 21 December 2017 12:08:33 Brian wrote:
> 
> > On Thu 21 Dec 2017 at 11:41:01 -0500, Gene Heskett wrote:
> >
> > > I can turn that option off on a job by job basis I assume.
> >
> > You mean cupsdisable? You could, but it wouldn't ordinarily be used.
> 
> No, I was referring to the rotate and fit option. About the only place 
> where I could actually make sense of that would be in printing camera 
> images where the camera may have been held up-down for a portrait image.

You can turn that option off and on on a job by job basis. It's default
is on; personally, I would leave it like that. Note that the Portrait
and Landscape options are not applied when Auto Rotate is on.

-- 
Brian.

Re: Debian, FF & NavyFed

[Mike McClain]

On Wed, Dec 20, 2017 at 04:02:01PM +0300, Selim T. Erdo??an wrote:
>
> Try pressing ESC, or clicking on various points in the window.
>
> I sometimes see such overlaid stuff on websites and, on some, I can get
> it to go away, and see the underlying "real stuff", by such a press/click.

Thanks Selim.
Didn't work but was worth a try.
Hookem Horns.

Happy Holidays,
Mike
--
1984 was not meant as a blueprint for democratic governments.

Re: got a new one

[Gene Heskett]

On Thursday 21 December 2017 12:08:33 Brian wrote:

> On Thu 21 Dec 2017 at 11:41:01 -0500, Gene Heskett wrote:
> > On Thursday 21 December 2017 06:51:56 Brian wrote:
> > > Considering you have lead the discussion back to your invoice
> > > problem I'll ask whether the PDF evince produces is viewable,
> >
> > Yes, exactly as expected.
>
> Ok, you have just shown that evince produces a decent PDF which looks
> suitable to send to CUPS. In other words, the blank page you got does
> not apparently involve anything evince has done.
>
> Now send this PDF to CUPS with
>
>   lp -d  
>
>  will have to re-enabled with
>
>   cupsenable 
>
> Does this print?
>
> > > and shows what
> > > you expect, using what is outlined in
> > >
> > > https://lists.debian.org/debian-user/2017/12/msg00584.html
> >
> >  cupsdisable 
> >
> > and send the invoice from evince to be printed. Look in
> > /var/spool/cups for a file beginning with "d" and view it in a PDF
> > viewer. Also use pdfinfo and pdffonts to compare this PDF and the
> > original one.
> >
> > Use cupsenable to revert the first command.
> >
> > Its not possible, because a disabled printer is ghosted in the
> > printer selection menu, yes I do have additional printers, full
> > color and 2% of the speed of the $110 HL2140. It can do this is 30
> > seconds including drum warmup time. The tabloid sized 6920, an mfc,
> > hasn't even sorted out which paper tray to use in that same 30
> > seconds.
>
> Please see above. Maybe I should have spelled out the full command.
>
> > Would I get the same results sending to cups-pdf?
>
> No. cups-pdf uses CUPS; CUPS was disabled for the test you did. Its
> purpose was to determine whether evince was producing a blank PDF. It
> wasn't.
>
> > I can turn that option off on a job by job basis I assume.
>
> You mean cupsdisable? You could, but it wouldn't ordinarily be used.

No, I was referring to the rotate and fit option. About the only place 
where I could actually make sense of that would be in printing camera 
images where the camera may have been held up-down for a portrait image.

Thanks Brian.

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: regex en bash

[Pierre Malard]

Très drôle et instructif !

Il faut lire complètement le man pour comprendre :
An additional binary operator, =~, is available, with the same precedence as == 
and !=.
When it is used, the string to the right of the operator is considered an 
extended regular
expression and matched accordingly (as in regex(3)).  The return value is  0  
if  the
string  matches  the  pattern,  and 1 otherwise.

Du coup si :
[[ 'abcd' =~ '^ab' ]] && echo ok || echo KO
KO

On a ceci qui répond bien :
[[ 'abcd' =~ ^ab ]] && echo ok || echo KO
ok


petite blague de Noël…

> Le 21 déc. 2017 à 18:13, Daniel Caillibaud  a écrit :
> 
> Bonjour,
> 
> Je sais que bash a un opérateur =~ pour les regex, mais j'ai du mal à faire
> ce que je veux avec et je continue avec sed / awk / grep,
> 
> Mais faire du
>  [[ -z "$(echo $truc | sed -Ee 's/ma regex//')" ]]
> est assez idiot quand on pourrait faire du
>  [[ "$truc" =~ 'ma regex' ]]
> 
> mais je n'arrive pas à utiliser ^ et $ dans mes regex, alors que man bash
> semble dire que ça doit fonctionner comme d'habitude.
> 
> Pourquoi
> 
> $ [[ 'abcd' =~ '^ab' ]] && echo ok || echo KO
> KO
> 
> $ [[ 'abcd' =~ 'cd$' ]] && echo ok || echo KO
> KO
> 
> ??
> 
> (je sais, avec zsh ces deux commandes renvoient ok comme on pourrait s'y
> attendre…)
> 
> --
> Daniel
> 
> Vous ne sauriez croire avec quelle facilité l'impossible
> se fait dès qu'il est nécessaire.
> Anatole France
> 

--
Pierre Malard

   « Si, comme le disait le général de Gaulle, la France n'avait pas été la
   France... on peut logiquement penser que tous les français auraient été
   des étrangers » ;-)
   
Pierre Dac
   |\  _,,,---,,_
   /,`.-'`'-.  ;-;;,_
  |,4-  ) )-,_. ,\ (  `'-'
 '---''(_/--'  `-'\_)   πr

perl -e '$_=q#: 3|\ 5_,3-3,2_: 3/,`.'"'"'`'"'"' 5-.  ;-;;,_:  |,A-  ) )-,_. ,\ 
(  `'"'"'-'"'"': '"'"'-3'"'"'2(_/--'"'"'  `-'"'"'\_): 
24πr::#;y#:#\n#;s#(\D)(\d+)#$1x$2#ge;print'
- --> Ce message n’engage que son auteur <--



signature.asc
Description: Message signed with OpenPGP

NAT avec plusieurs interfaces publiques

[Olivier]

Bonjour,

Je prépare une installation dans laquelle un routeur (une machine sous
Debian Stretch) aura 3 interfaces logiques:
une interface eth0.30 vers un réseau local
une interface eth0.20 vers un lien Internet
une interface eth0.10 vers un autre lien Internet

Je souhaite répartir, en fonction de leur adresse IP, les utilisateurs du
réseau local vers les deux liens Internet.:
si l'adresse de l'utilisateur est  dans le sous-réseau 10.50.0.0/24, sortir
sur Internet en nattant avec l'interface eth0.10,
si l'adresse de l'utilisateur est  dans le sous-réseau 10.50.1.0/24, sortir
sur Internet en nattant avec l'interface eth0.20.

Comment configurer cela ?


J'ai un script iptables qui marque le trafic entrant avec une règle du type
iptables -t mangle -A PREROUTING -s 10.50.1.0/24 -j MARK --set-mark 2

J'ai une autre règle qui j'espérais, devrait NATer, le trafic dont la
marque est spécifique:
iptables -t nat -A POSTROUTING -m mark --mark 2 -o eth0.20 -j SNAT
--to-source 2.2.2.2

Cette dernière règle ne semble pas exécutée pour un utilisateur dont
l'adresse est bien dans le réseau 10.50.1.0/24.
À la place, c'est la règle "par défaut" comme celle ci-après qui semble
exécutée:
iptables -t nat -A POSTROUTING -o eth0.10 -j SNAT --to-source 2.2.2.2

Qu'en pensez-vous ?

Slts

regex en bash

[Daniel Caillibaud]

Bonjour,

Je sais que bash a un opérateur =~ pour les regex, mais j'ai du mal à faire
ce que je veux avec et je continue avec sed / awk / grep,

Mais faire du 
  [[ -z "$(echo $truc | sed -Ee 's/ma regex//')" ]]
est assez idiot quand on pourrait faire du 
  [[ "$truc" =~ 'ma regex' ]]

mais je n'arrive pas à utiliser ^ et $ dans mes regex, alors que man bash
semble dire que ça doit fonctionner comme d'habitude.

Pourquoi

$ [[ 'abcd' =~ '^ab' ]] && echo ok || echo KO
KO

$ [[ 'abcd' =~ 'cd$' ]] && echo ok || echo KO
KO

??

(je sais, avec zsh ces deux commandes renvoient ok comme on pourrait s'y
attendre…)

-- 
Daniel

Vous ne sauriez croire avec quelle facilité l'impossible 
se fait dès qu'il est nécessaire.
Anatole France

Re: Debian jigdo status

[Thomas Schmitt]

Hi,

Nicholas Geovanis wrote:
> many thanks to Thomas Schmitt and Phil Hands

You are welcome.
If you want to thank Philip Hands, then you will probably have to do this
to him directly or to debian-live list.


> A whole company's thanks actually.

GNU/Linux saved my financial neck long ago. From time to time i get an
opportunity to pay back an installment or two.


Have a nice day :)

Thomas

Re: got a new one

[Brian]

On Thu 21 Dec 2017 at 11:41:01 -0500, Gene Heskett wrote:

> On Thursday 21 December 2017 06:51:56 Brian wrote:
> 
> > Considering you have lead the discussion back to your invoice problem
> > I'll ask whether the PDF evince produces is viewable,
> 
> Yes, exactly as expected.

Ok, you have just shown that evince produces a decent PDF which looks
suitable to send to CUPS. In other words, the blank page you got does
not apparently involve anything evince has done.

Now send this PDF to CUPS with

  lp -d  

 will have to re-enabled with

  cupsenable 

Does this print?

> > and shows what 
> > you expect, using what is outlined in
> >
> > https://lists.debian.org/debian-user/2017/12/msg00584.html
> 
>  cupsdisable 
> 
> and send the invoice from evince to be printed. Look in /var/spool/cups
> for a file beginning with "d" and view it in a PDF viewer. Also use
> pdfinfo and pdffonts to compare this PDF and the original one.
> 
> Use cupsenable to revert the first command.
> 
> Its not possible, because a disabled printer is ghosted in the printer 
> selection menu, yes I do have additional printers, full color and 2% of 
> the speed of the $110 HL2140. It can do this is 30 seconds including 
> drum warmup time. The tabloid sized 6920, an mfc, hasn't even sorted out 
> which paper tray to use in that same 30 seconds.

Please see above. Maybe I should have spelled out the full command.

> Would I get the same results sending to cups-pdf?

No. cups-pdf uses CUPS; CUPS was disabled for the test you did. Its
purpose was to determine whether evince was producing a blank PDF. It
wasn't.

> I can turn that option off on a job by job basis I assume.

You mean cupsdisable? You could, but it wouldn't ordinarily be used.

-- 
Brian.

Modif de l'option -a de rsync dans stretch ?

[Daniel Caillibaud]

Bonjour,

Depuis stretch, la commande exécutée en remote par `rsync -a` devient
  rsync --server -logDtpre.iLsfxC
alors que c'était avant
  rsync --server -logDtpre.iLsfx

Que signifie ce qui suit le "e." et à quoi correspond ce C ajouté ?

Ça ne correspond pas à l'option -C de rsync, car dans ce cas (-aC) on a
  rsync --server -logDtprCe.iLsfxC

Pour voir ça, lancer rsync avec -e 'ssh -v' ou bien mettre dans le 
.ssh/authorized_keys
  command="/root/echoShell.sh" ssh-rsa ...la.clé

et dans /root/echoShell.sh
  #!/bin/bash
  echo -e "On aurait lancé la commande\n$SSH_ORIGINAL_COMMAND">&2
  exit 1


Pour mémoire
  -a, --archive   archive mode; equals -rlptgoD (no -H,-A,-X)
  -C, --cvs-exclude   auto-ignore files in the same way CVS does
  -e, --rsh=COMMAND   specify the remote shell to use
(tout le reste dans man rsync)

C'est juste par curiosité, parce que le shell maison dédié à un client s'est
mis à planter quand il est passé à stretch, c'est simple à régler mais
je me posais cette question…

Merci à ceux qui savent ;-)


PS: pour autoriser du ssh sous root (ou n'importe quel autre user, mais pour 
les autres on s'en sort en général avec la gestion habituelle des droits, le
pb se pose pour des choses permises à root seulement) mais ne permettre que 
certaines commandes, mettre un shell avec par ex

case "$SSH_ORIGINAL_COMMAND" in
  ping) echo "pong";;

  trucPerso)
# on fait un truc préétabli
  ;;

  autreCommande) 
# idem
  ;;

  # le reste
  *)
# tests divers sur $SSH_ORIGINAL_COMMAND
# si ok on lance 
# ionice -c3 $SSH_ORIGINAL_COMMAND && exit 0

# sinon, tout le reste est interdit
echo "Commande « $SSH_ORIGINAL_COMMAND » non autorisée" >&2
exit 1
  ;;

esac


-- 
Daniel

Les folies sont les seules choses qu’on ne regrette jamais.
Oscar Wilde

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

[Haricophile]

Le Thu, 21 Dec 2017 17:26:18 +0100,
andre_deb...@numericable.fr a écrit :

> Il fallait simplement répondre que ça m'oblige à une réinstallation
> du système ou sans doute une recompilation du noyau,
> pour avoir le disque dur en /dev/sda.
> 
> De grâce, stop, merci et j'arrête.
> 
> André

Je pense que tout le monde se demande quel est l'intérêt de s'acharner
à tout prix pour mettre de manière logique un disque sur une
adresse physique différente.

Je ne vois vraiment pas comment on pourrait apporter une réponse
satisfaisante à cette question physique si aucune réponse utilisant une
solution logique et non physique n'est acceptée.

Donc je donne la réponse très physique : Va voir ta machine, et fais ce
qu'il faut sur les branchements, modifie le bios ah pardon tu ne
peux pas, donc ça non plus ce n'est pas satisfaisant...

Bref, tu râle parce que ta question n'a pas de réponse dans des
contraintes que tu te fixe toi même et qui ne semblent pas avoir
raison d'être. C'est pas stressant comme manière de faire ?

-- 
haricoph...@aranha.fr 

Re: Sony Memory Stick problem on Debian 9 stable

[Cindy-Sue Causey]

On 12/21/17, Darac Marjal  wrote:
> On Thu, Dec 21, 2017 at 01:01:13PM +0330, Farhad Mohammadi Majd wrote:
>>Hello, I want to buy a old Sony compact digital camera which supports
>>only Memory Stick, a removable flash memory card format, before buy it,
>>I get its memory card to check is it supported under Linux or not.
>>
>>I inserted it into memory card reader and it is detected by system:
>>
> # lsblk
>>
> NAME   MAJ:MIN RM   SIZE RO TYPE
>>
> sdc  8:32   1 2T  0 disk
>
> 2 Terabytes in an old digital camera? Either you're planning on taking a
> LOT of pictures our your Memory Stick is not actually recognised by the
> system.
>
> First off, check that your card reader HARDWARE supports the MS. Have
> you read the Wikipedia page on Memory Sticks? There are almost as many
> variants as Secure Digital has.
> https://en.wikipedia.org/wiki/Memory_Stick
>
> Secondly, have you checked for physical switches on the Memory Stick?
> There might be a read-only switch; there might even be a bank-select
> switch.


Man, I was sitting here thinking *2 TERABYTES*?! Am I reading that
output wrong?! I'd LOVE for an older camera to take more than 1 or 2
GIGABYTES, let alone 2TB! :))

K/t abject poverty, I play around A LOT with older digital cameras
rather than cutting edge. One alternate trick that *sometimes* works
is that many (dare I say at least most?) of them use cables to
communicate with computers.

*SOMETIMES*, although not always 100% of the time, the communication
that goes on via that cable is what will get what you need even when
memory card readers don't register any given class/type of memory
stick that digital cameras might use.

As I write that, it occurs to me that some of that higher success
gained by going that route is because your "card reader" is then the
same instrument that wrote data to that card in the first place. Of
all the technology available right now, theoretically one would think
that the #1 go-to thing that should *always* be able to read that
card's data is that same instrument that put that data on that card.
One would think :)

But that's something one wouldn't know for sure until the camera is
physically in hand, unfortunately. A couple of us here on Debian-User
had problems going that cable route to transfer images around. Those
issues seem to have settled out, though, over the last year or so.

One hard lesson I learned on the fly was that everything on a camera
can *look* fabulous can put out all the cool digital readings you
want, can preview nice, sharp pics through the viewfinder or on the
LCD screen, etc..

BUT the internal memory card reader/writer and possibly attached
dedicated processor board inside the camera can be shot, fried,
useless. In that kind of case, it can cost as much in service fees and
parts to replace as it would for a newer, much more capable camera.

Nikon D1H is my experience there.. Total brick, but it sure is pretty
to look at and make pretends with. Everyone was sleeping the day I was
able to afford that one.. :)

In the case of a fried internal memory card slot, there would...
obviously... be a bit of card reading issues in that case, too. That
was (mostly) the intended point of bringing that part up.

You can find yourself running into a brick wall for hours trying
everything you can think of for why your memory stick keeps throwing
basic errors, e.g. card not present or card not formatted. Meanwhile
the problem could ultimately be traced to a broken dedicated processor
board or similar for that memory card slot. Nothin' is going to read
nothin' for nothin' in Debian until that gets fixed first. :)

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

* runs with #photog envy *

Re: got a new one

[Gene Heskett]

On Thursday 21 December 2017 06:51:56 Brian wrote:

> On Thu 21 Dec 2017 at 06:17:19 -0500, Gene Heskett wrote:
> > On Thursday 21 December 2017 05:52:11 Brian wrote:
> > > On Wed 20 Dec 2017 at 19:39:32 -0500, Gene Heskett wrote:
> > > > On Wednesday 20 December 2017 17:56:46 Brian wrote:
> > > > > On Wed 20 Dec 2017 at 17:06:35 -0500, Gene Heskett wrote:
> > > > > > Either one implies a 90 degree rotation of the page on the
> > > > > > paper, so that lng lines don't either get clipped off at
> > > > > > the right margin, or often as not line wrapped by the
> > > > > > printer which means on a multipage document, the pdf
> > > > > > interpretors page count doesn't get totally scrambled &
> > > > > > starts putting the headers and footers in the middle of the
> > > > > > page. Doesn't always help though, some of the hal files I've
> > > > > > hacked up over the years have effectively been north of 220
> > > > > > chars/line. There are ways to fix that, but they are
> > > > > > relatively new in linuxcnc's init functions. Those older
> > > > > > files usually get fixed if I have to revisit them, because
> > > > > > the hardware changed or something.
> > > > >
> > > > > What determines the choice of pages which suffer a 90 degree
> > > > > rotation?
> > > >
> > > > Not individual pages unless you want to jump thru some pretty
> > > > small hoops. You can select it for the whole, individual print
> > > > job, in the printer requester that pops up when you select print
> > > > from some application. I varies as to what tab its under but
> > > > will usually be a 4 choice. 2 of them will be labeled Portrait
> > > > and Landscape, the other 2 are further rotations at 180 and 270
> > > > degrees. The better versions of that requester will also let you
> > > > specify odd only or even only, or a page range in case you only
> > > > want a 10 page piece of a 750 pager.
> > >
> > > So the contention is that "printing in landscape" involves
> > > selecting the Landscape option in a drop-down menu of evince and
> > > then that will produce a 90 degree rotation of a PDF page.
> > >
> > > However, I observe (on unstable, jessie and stretch) that a page
> > > like this
> > >
> > > +--+
> > >
> > >
> > > +--+
> > >
> > > is not rotated. Auto Rotate and Center was unchecked and the
> > > technique in
> > >
> > > https://lists.debian.org/debian-user/2017/12/msg00584.html
> > >
> > > was used to examine the PDF to be sent to CUPS.
> > >
> > > It appears that "printing in landscape" doesn't always lead to a
> > > 90 degree rotation when using evince..
> >
> > I repeat, it was not requested as anything but Portrait for that job
> > that failed. okular uses a different requester, which does not show
> > that option in any menu, and it worked. Unfortunately, none of these
> > things have a help pulldown that identify's them so fingers can be
> > pointed at the guilty party.
>
> We were discussing the meaning and significance of the term "printing
> to landscape", not your particular issue. It takes us a little
> off-topic but, for evince. it does not seem to have the meaning people
> credit it with. As illustrated, rotation does not always take place.
> Does this lead to the conclusion thet "printing to landscape" (or for
> that matter, "printing to portrait") is too fuzzy a phrase to be
> useful? For evince, the Landscape option appears to be saying - rotate
> by 90 degrees sometimes.
>
> > Perhaps a better question, since this seems to be a well known bug,
> > is why has it not been fixed? And how is it turned of so as to
> > become the default?
>
> As you will see from the report, the bug Curt made reference to has
> been fixed.
>
> Considering you have lead the discussion back to your invoice problem
> I'll ask whether the PDF evince produces is viewable,

Yes, exactly as expected.

> and shows what 
> you expect, using what is outlined in
>
> https://lists.debian.org/debian-user/2017/12/msg00584.html

 cupsdisable 

and send the invoice from evince to be printed. Look in /var/spool/cups
for a file beginning with "d" and view it in a PDF viewer. Also use
pdfinfo and pdffonts to compare this PDF and the original one.

Use cupsenable to revert the first command.

Its not possible, because a disabled printer is ghosted in the printer 
selection menu, yes I do have additional printers, full color and 2% of 
the speed of the $110 HL2140. It can do this is 30 seconds including 
drum warmup time. The tabloid sized 6920, an mfc, hasn't even sorted out 
which paper tray to use in that same 30 seconds.

Would I get the same results sending to cups-pdf?

I can turn that option off on a job by job basis I assume.


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: Noms partitions /dev/sdaX modifiés en /dev/sdcX

[Eric Degenetais]

Non, vous n'avez besoin ni de réinstaller, ni de recompiler le noyau, ni de
vous soucier de savoir si le bloc device s'appelle /dev/sdc1 ou /dev/sda1.
Pour ne plus avoir de défaillances le mode opératoire est le suivant :
1) repérer, par exemple avec le ls dont j'ai parlé, qui est qui
2) à partir de là, en utilisant les liens présents dans /dev/by-label,
modifier les labels des partitions en quelque chose de signifiant pour
vous, par exemple quelque chose comme :
_root
_home
_swap
Etc
3) reconfigurer l'automontage en utilisant les labels, car eux ne
changeront pas si la détection des disques est modifiée par un événement
quelconque.
Bonus : /dev/by-label contiendra par la suite des noms correspondant aux
labels signifiants, ce qui est nettement plus facile à lire et moins sujet
aux erreurs

Cordialement

Éric Dégenètais


Le 21 déc. 2017 5:26 PM,  a écrit :

On Thursday 21 December 2017 09:34:36 Stephane Ascoet wrote:
> Bonjour, belle trouvaille, en fait les choses sont ainsi depuis cet été,
> ce disque dur n'a jamais été /dev/sda. Andre a du bidouillé les
> étiquettes mais comme on l'a tous dit dans ce dialogue de sourd qui
> tourne en boucle, ce ne sont que des étiquettes, ce disque a toujours
> été et sera toujours /dev/sdc. Visiblement André confond nom de bloc,
> étiquette et dossier de montage depuis le début (étonnant pour un
> membre historique de la liste comme lui)...

J'en en ai marre de ces remarques désobligeantes et injustes,
dont la dernière :

> André confond nom de bloc, étiquette, dossier de montage,
> depuis le début,
et ajouter cette mention bien inutile :
> (étonnant pour un membre historique de la liste comme lui)...

Je n'ai jamais fait cette confusion et il y a eu trop d'échanges de mails,
sans solution donnée.

Il fallait simplement répondre que ça m'oblige à une réinstallation
du système ou sans doute une recompilation du noyau,
pour avoir le disque dur en /dev/sda.

De grâce, stop, merci et j'arrête.

André

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

[andre_debian]

On Thursday 21 December 2017 09:34:36 Stephane Ascoet wrote:
> Bonjour, belle trouvaille, en fait les choses sont ainsi depuis cet été, 
> ce disque dur n'a jamais été /dev/sda. Andre a du bidouillé les 
> étiquettes mais comme on l'a tous dit dans ce dialogue de sourd qui 
> tourne en boucle, ce ne sont que des étiquettes, ce disque a toujours 
> été et sera toujours /dev/sdc. Visiblement André confond nom de bloc, 
> étiquette et dossier de montage depuis le début (étonnant pour un 
> membre historique de la liste comme lui)...

J'en en ai marre de ces remarques désobligeantes et injustes,
dont la dernière :

> André confond nom de bloc, étiquette, dossier de montage,
> depuis le début,
et ajouter cette mention bien inutile :
> (étonnant pour un membre historique de la liste comme lui)...

Je n'ai jamais fait cette confusion et il y a eu trop d'échanges de mails,
sans solution donnée.

Il fallait simplement répondre que ça m'oblige à une réinstallation
du système ou sans doute une recompilation du noyau,
pour avoir le disque dur en /dev/sda.

De grâce, stop, merci et j'arrête.

André

Re: Debian jigdo status

[Nicholas Geovanis]

I'm the OP so I thought I would follow-up.
It turned out that there were problems with some files in the Debian
archives. The traffic on the resolution
for that is on debian-cd:
https://lists.debian.org/debian-cd/2017/12/msg00014.html
There were also recently discovered problems in the jigdo tools (just fixed
a week or so before), but it
turned-out that that was not my problem. See
https://www.mail-archive.com/debian-bugs-dist@lists.debian.org/msg1526505.html

The actual point of using this ancient release, which I hadn't mentioned,
was to get a salt-minion installed and configured into
an existing salt complex and begin rectification. After an additional 3
days wrestling with the Debian and Saltstack repositories
and dealing with apt-get package resolution difficulties, I managed to
complete that on one server and it's in the complex. My
work-around is totally brain-dead, but it circumvents the resolution issues
with apt-get. It's possible that using apt, aptitude or
synaptic would have worked better, but I don't have time to find-out yet
(or perhaps an apt-get problem; I can't really touch
fundamental software on these servers yet, most are production).

Many, many thanks to Thomas Schmitt and Phil Hands for their help on this.
A whole company's thanks actually.
Now: In case anyone wonders, this is exactly how linux destroyed the old
unix vendors and microsloth in the data-center.
I get better support here for free than I ever got from them for thousands.
Once it was noodled-out, it was fixed in
under 24 hours. Carry on :-)

On Fri, Dec 15, 2017 at 3:12 PM, Brad Rogers  wrote:

> On Fri, 15 Dec 2017 22:10:12 +0100
> "Thomas Schmitt"  wrote:
>
> Hello Thomas,
>
> >Correction: It is now in "testing" after only 6 days in "unstable".
> >(Has the quarantine time been reduced ? Normally it is 10 or 11 days.)
>
> It's usually five days.  For some software it's extended to ten.
>
> --
>  Regards  _
>  / )   "The blindingly obvious is
> / _)radnever immediately apparent"
> You never listen to a word that I said
> Public Image - Public Image Ltd
>

Re: Sony Memory Stick problem on Debian 9 stable

[Stefan Monnier]

> Hello, I want to buy a old Sony compact digital camera which supports
> only Memory Stick, a removable flash memory card format, before buy it,
> I get its memory card to check is it supported under Linux or not.

FWIW, if you use a USB-connected card reader, then the physical media
doesn't actually matter: it's the card reader which handles the details
of the "Memory Stick" access and your computer will only see a standard
USB-connected disk.

Of course compatibility with GNU/Linux can still be relevant in terms of
the file-system used on those things.  I have an old Sony camera using
Memory Stick Pro and the file system used on it is FAT, so I have
absolutely no trouble reading it on my Debian boxes with a USB-connected
card reader.  But in your case, the "Input/output error" indicates the
problem comes before your computer has a chance to look at the
file-system.

Maybe the card you tried to use, or the card reader was faulty (in my
experience, both have fairly high failure rates).


Stefan

Re: Debian networking - accessing public-side servers from a private network

[Phil Reynolds]

On Thu, 21 Dec 2017 11:10:40 +
Phil Reynolds  wrote:

> On Thu, 21 Dec 2017 07:23:06 +0100
> Pascal Hambourg  wrote:
> > Just another thought : isn't it possible to set up Asterisk to
> > listen explicitly on both the private and public IPv4 addresses
> > instead of any local address, so that it opens two separate
> > sockets ? This way I think it would reply with the proper source
> > address.  
>  
> Not tried that yet but I will, a bit later.

That seems to be effective.

-- 
Phil Reynolds
mail: phil-deb...@tinsleyviaduct.com
Web: http://phil.tinsleyviaduct.com/

Re: Sony Memory Stick problem on Debian 9 stable

[deloptes]

Darac Marjal wrote:

> 2 Terabytes in an old digital camera? Either you're planning on taking a
> LOT of pictures our your Memory Stick is not actually recognised by the
> system.
> 
> First off, check that your card reader HARDWARE supports the MS. Have
> you read the Wikipedia page on Memory Sticks? There are almost as many
> variants as Secure Digital has.
> https://en.wikipedia.org/wiki/Memory_Stick
> 
> Secondly, have you checked for physical switches on the Memory Stick?
> There might be a read-only switch; there might even be a bank-select
> switch.

OP wrote "plan to buy". If you have Sony memory stick and know if it works
share, if not read twice before posting, please.

regards

Re: Sony Memory Stick problem on Debian 9 stable

[Joseph Loo]

On 12/21/2017 02:53 AM, Farhad Mohammadi Majd wrote:
>> First off, check that your card reader HARDWARE supports the MS. Have
> you read the Wikipedia page on Memory Sticks? There are almost as many
> variants as Secure Digital has.
> 
> Yes, I have read that article and my memory card reader claims that it
> supports Memory Stick and has a slot for it and I think when it is
> detected by system, this means my memory card reader can read this type
> of memory card.
> 
>> Secondly, have you checked for physical switches on the Memory Stick?
> There might be a read-only switch; there might even be a bank-select
> switch.
> 
> Yes, it has a *Lock* switch, it is set to open.
> 
I believe there is something wrong with your hardware.  I do not believe
there are any sdc much less memory stick that contains 2 tB. The largest
I heard is 256 gB and memory stick is old technology.

In addition be careful of the switch. In sdc cards, the switch does not
truly make the card read only, instead it is a bit to indicate the
switch is on or off. It is up to the software to ensure that you do not
write to it. Of course this may have changed

-- 
Joseph Loo
j...@acm.org

Re: Stretch: Greeter powers down and locks monitors

[Roger Price]

On Wed, 20 Dec 2017, David Christensen wrote:


On 12/20/17 02:49, Roger Price wrote:
Hi, I'm running stretch with Xfce.  Gnome is also installed.  The login 
greeter appears correctly, and allows login, but if I leave the "greeter" 
screen too long, then something intervenes and puts the two monitors into a 
sleep mode (iiyama E1700S orange light).  I cannot find any key combination 
which wakes up gdm3.


Have you tried right-clicking with the mouse?  My laptop with Stretch, Xfce, 
and the default login manager (lightdm?) requires this.


I tried mouse buttons 1, 2 and 3.  I also tried Ctl-Mouse 1/2/3, 
Ctl-Alt-Mouse 1/2/3, Ctl-RightAlt-Mouse 1/2/3, Shift-Mouse 1/2/3, etc. 
But no success.


Roger

Re: Stretch: Greeter powers down and locks monitors

[Roger Price]

On Wed, 20 Dec 2017, Thomas Amm wrote:


On Wed, 20 Dec 2017 11:49:33 +0100 (CET)
Roger Price  wrote:


Hi, I'm running stretch with Xfce.  Gnome is also installed.  The
login greeter appears correctly, and allows login, but if I leave the
"greeter" screen too long, then something intervenes and puts the two
monitors into a sleep mode (iiyama E1700S orange light).  I cannot
find any key combination which wakes up gdm3.


I'd try simply replacing GDM with lightdm. Just a workaround, but the
oroginal problem might by very hard to solve.


In file /etc/X11/default-display-manager I replaced /usr/sbin/gdm3 with 
/usr/sbin/lightdm and restarted the box. It got as far as run level 5 but 
with no display manager. journalctl reports that the "Gnome display 
Manager" could not be started, despite five attempts.


Roger

Re: got a new one

[Brian]

On Thu 21 Dec 2017 at 06:17:19 -0500, Gene Heskett wrote:

> On Thursday 21 December 2017 05:52:11 Brian wrote:
> 
> > On Wed 20 Dec 2017 at 19:39:32 -0500, Gene Heskett wrote:
> > > On Wednesday 20 December 2017 17:56:46 Brian wrote:
> > > > On Wed 20 Dec 2017 at 17:06:35 -0500, Gene Heskett wrote:
> > > > > Either one implies a 90 degree rotation of the page on the
> > > > > paper, so that lng lines don't either get clipped off at the
> > > > > right margin, or often as not line wrapped by the printer which
> > > > > means on a multipage document, the pdf interpretors page count
> > > > > doesn't get totally scrambled & starts putting the headers and
> > > > > footers in the middle of the page. Doesn't always help though,
> > > > > some of the hal files I've hacked up over the years have
> > > > > effectively been north of 220 chars/line. There are ways to fix
> > > > > that, but they are relatively new in linuxcnc's init functions. 
> > > > > Those older files usually get fixed if I have to revisit them,
> > > > > because the hardware changed or something.
> > > >
> > > > What determines the choice of pages which suffer a 90 degree
> > > > rotation?
> > >
> > > Not individual pages unless you want to jump thru some pretty small
> > > hoops. You can select it for the whole, individual print job, in the
> > > printer requester that pops up when you select print from some
> > > application. I varies as to what tab its under but will usually be a
> > > 4 choice. 2 of them will be labeled Portrait and Landscape, the
> > > other 2 are further rotations at 180 and 270 degrees. The better
> > > versions of that requester will also let you specify odd only or
> > > even only, or a page range in case you only want a 10 page piece of
> > > a 750 pager.
> >
> > So the contention is that "printing in landscape" involves selecting
> > the Landscape option in a drop-down menu of evince and then that will
> > produce a 90 degree rotation of a PDF page.
> >
> > However, I observe (on unstable, jessie and stretch) that a page like
> > this
> >
> > +--+
> >
> >
> > +--+
> >
> > is not rotated. Auto Rotate and Center was unchecked and the technique
> > in
> >
> > https://lists.debian.org/debian-user/2017/12/msg00584.html
> >
> > was used to examine the PDF to be sent to CUPS.
> >
> > It appears that "printing in landscape" doesn't always lead to a 90
> > degree rotation when using evince..
> 
> I repeat, it was not requested as anything but Portrait for that job that 
> failed. okular uses a different requester, which does not show that 
> option in any menu, and it worked. Unfortunately, none of these things 
> have a help pulldown that identify's them so fingers can be pointed at 
> the guilty party.

We were discussing the meaning and significance of the term "printing
to landscape", not your particular issue. It takes us a little off-topic
but, for evince. it does not seem to have the meaning people credit it
with. As illustrated, rotation does not always take place. Does this
lead to the conclusion thet "printing to landscape" (or for that matter,
"printing to portrait") is too fuzzy a phrase to be useful? For evince,
the Landscape option appears to be saying - rotate by 90 degrees
sometimes.

> Perhaps a better question, since this seems to be a well known bug, is 
> why has it not been fixed? And how is it turned of so as to become the 
> default?

As you will see from the report, the bug Curt made reference to has been
fixed.

Considering you have lead the discussion back to your invoice problem
I'll ask whether the PDF evince produces is viewable, and shows what
you expect, using what is outlined in

https://lists.debian.org/debian-user/2017/12/msg00584.html

-- 
Brian.

Re: got a new one

[Gene Heskett]

On Thursday 21 December 2017 05:52:11 Brian wrote:

> On Wed 20 Dec 2017 at 19:39:32 -0500, Gene Heskett wrote:
> > On Wednesday 20 December 2017 17:56:46 Brian wrote:
> > > On Wed 20 Dec 2017 at 17:06:35 -0500, Gene Heskett wrote:
> > > > Either one implies a 90 degree rotation of the page on the
> > > > paper, so that lng lines don't either get clipped off at the
> > > > right margin, or often as not line wrapped by the printer which
> > > > means on a multipage document, the pdf interpretors page count
> > > > doesn't get totally scrambled & starts putting the headers and
> > > > footers in the middle of the page. Doesn't always help though,
> > > > some of the hal files I've hacked up over the years have
> > > > effectively been north of 220 chars/line. There are ways to fix
> > > > that, but they are relatively new in linuxcnc's init functions. 
> > > > Those older files usually get fixed if I have to revisit them,
> > > > because the hardware changed or something.
> > >
> > > What determines the choice of pages which suffer a 90 degree
> > > rotation?
> >
> > Not individual pages unless you want to jump thru some pretty small
> > hoops. You can select it for the whole, individual print job, in the
> > printer requester that pops up when you select print from some
> > application. I varies as to what tab its under but will usually be a
> > 4 choice. 2 of them will be labeled Portrait and Landscape, the
> > other 2 are further rotations at 180 and 270 degrees. The better
> > versions of that requester will also let you specify odd only or
> > even only, or a page range in case you only want a 10 page piece of
> > a 750 pager.
>
> So the contention is that "printing in landscape" involves selecting
> the Landscape option in a drop-down menu of evince and then that will
> produce a 90 degree rotation of a PDF page.
>
> However, I observe (on unstable, jessie and stretch) that a page like
> this
>
> +--+
>
>
> +--+
>
> is not rotated. Auto Rotate and Center was unchecked and the technique
> in
>
> https://lists.debian.org/debian-user/2017/12/msg00584.html
>
> was used to examine the PDF to be sent to CUPS.
>
> It appears that "printing in landscape" doesn't always lead to a 90
> degree rotation when using evince..

I repeat, it was not requested as anything but Portrait for that job that 
failed. okular uses a different requester, which does not show that 
option in any menu, and it worked. Unfortunately, none of these things 
have a help pulldown that identify's them so fingers can be pointed at 
the guilty party.

Perhaps a better question, since this seems to be a well known bug, is 
why has it not been fixed? And how is it turned of so as to become the 
default?

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: Debian networking - accessing public-side servers from a private network

[Phil Reynolds]

On Thu, 21 Dec 2017 17:30:25 +0900
メット  wrote:


> Try setup asterisk address as ANY ie.
> 0.0.0.0.
> 
> Then asterisk will act on both addresses.

That is probably the equivalent of the default, i.e. no address
specified, which fails as indicated. I will however try it later.

-- 
Phil Reynolds
mail: phil-deb...@tinsleyviaduct.com
Web: http://phil.tinsleyviaduct.com/

Re: Debian networking - accessing public-side servers from a private network

[Phil Reynolds]

On Thu, 21 Dec 2017 07:23:06 +0100
Pascal Hambourg  wrote:

> How are TCP/IP parameters configured on the client ?
> Could you show its routing table ?

Output of "route" on it:

Destination 192.168.0.0 Gateway * Genmask 255.255.255.0 Flags U Metric
0 Ref 0 Use 0 Iface wlan0

Output of "route -A inet6" is much longer - see
http://paste.debian.net/1001796 - note that this is "as is", I haven't
concealed anything.

> >>> - If I could get the phone to pick up the private address of the
> >>> Asterisk box rather than the public one, that would probably
> >>> work. I have tried setting up to do this with dnsmasq, but the
> >>> IPv6 settings for DNS cause this to be overridden. If I could
> >>> somehow change the priority of this on the phone, it would help.  
> >>
> >> All the IPv4 and IPv6 nameservers used by the client must resolve
> >> the name into the private address. If they also serve the public
> >> zone, you must set up "split DNS" to server different versions for
> >> private and public clients.  
> > 
> > Unfortunately I have found no way to override the radvd-provided DNS
> > server addresses - otherwise I would have done this.  
> Aren't you in control of the router configuration and which IPv6 DNS 
> servers are advertised in the RAs it sends (radvd ?), and of these 
> servers behaviour ?

I am in control but it's a case of "can it be done and if so how?".

> Just another thought : isn't it possible to set up Asterisk to listen 
> explicitly on both the private and public IPv4 addresses instead of
> any local address, so that it opens two separate sockets ? This way I
> think it would reply with the proper source address.
 
Not tried that yet but I will, a bit later.

-- 
Phil Reynolds
mail: phil-deb...@tinsleyviaduct.com
Web: http://phil.tinsleyviaduct.com/

Re: LUKS password gets printed as stars

[Curt]

On 2017-12-21,   wrote:
>
> On Wed, Dec 20, 2017 at 01:02:51PM +, Curt wrote:
>
> [...]
>
>> Now we want to change the default. Give them the moon, and they want the
>> stars, too!
>
> Who is "them"? "Not us"?
>
> Perhaps you're trying to construe a conflict where, actually there
> isn't one.
>
> Now if I were in charge of systemd-ask-password, I'd be willing to
> incorporate suppression of the stars as a user-configurable option,
> but I'd be firmly against changing the default.
>
> YMMV.
  
We are in severe agreement.

>> Also, I'm uncertain whether suppression of the asterisk-echo qualifies
>> as "security by obscurity [...]
>
> I'm certain. It doesn't.

Here too.

> Cheers
> - -- t
>
>


-- 
"An autobiography is only to be trusted when it reveals something disgraceful.
A man who gives a good account of himself is probably lying, since any life
when viewed from the inside is simply a series of defeats."
— George Orwell

Re: got a new one

[Brian]

On Wed 20 Dec 2017 at 19:39:32 -0500, Gene Heskett wrote:

> On Wednesday 20 December 2017 17:56:46 Brian wrote:
> 
> > On Wed 20 Dec 2017 at 17:06:35 -0500, Gene Heskett wrote:
> > >
> > > Either one implies a 90 degree rotation of the page on the paper, so
> > > that lng lines don't either get clipped off at the right margin,
> > > or often as not line wrapped by the printer which means on a
> > > multipage document, the pdf interpretors page count doesn't get
> > > totally scrambled & starts putting the headers and footers in the
> > > middle of the page. Doesn't always help though, some of the hal
> > > files I've hacked up over the years have effectively been north of
> > > 220 chars/line. There are ways to fix that, but they are relatively
> > > new in linuxcnc's init functions.  Those older files usually get
> > > fixed if I have to revisit them, because the hardware changed or
> > > something.
> >
> > What determines the choice of pages which suffer a 90 degree rotation?
> 
> Not individual pages unless you want to jump thru some pretty small 
> hoops. You can select it for the whole, individual print job, in the 
> printer requester that pops up when you select print from some 
> application. I varies as to what tab its under but will usually be a 4 
> choice. 2 of them will be labeled Portrait and Landscape, the other 2 
> are further rotations at 180 and 270 degrees. The better versions of 
> that requester will also let you specify odd only or even only, or a 
> page range in case you only want a 10 page piece of a 750 pager.

So the contention is that "printing in landscape" involves selecting
the Landscape option in a drop-down menu of evince and then that will
produce a 90 degree rotation of a PDF page.

However, I observe (on unstable, jessie and stretch) that a page like
this

+--+
|  |
|  |
+--+

is not rotated. Auto Rotate and Center was unchecked and the technique
in

https://lists.debian.org/debian-user/2017/12/msg00584.html

was used to examine the PDF to be sent to CUPS.

It appears that "printing in landscape" doesn't always lead to a 90
degree rotation when using evince..

-- 
Brian.

Re: LUKS password gets printed as stars

[tomas]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Wed, Dec 20, 2017 at 01:02:51PM +, Curt wrote:

[...]

> Now we want to change the default. Give them the moon, and they want the
> stars, too!

Who is "them"? "Not us"?

Perhaps you're trying to construe a conflict where, actually there
isn't one.

Now if I were in charge of systemd-ask-password, I'd be willing to
incorporate suppression of the stars as a user-configurable option,
but I'd be firmly against changing the default.

YMMV.
 
> Also, I'm uncertain whether suppression of the asterisk-echo qualifies
> as "security by obscurity [...]

I'm certain. It doesn't.

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

iEYEARECAAYFAlo7kXQACgkQBcgs9XrR2kbpbACeNtmK2/fkBJwnA6VS/tm6SvYt
vyoAniDYtHG3m1RjVviijDze9FGoL/jT
=Edih
-END PGP SIGNATURE-

Re: got a new one

[Gene Heskett]

On Thursday 21 December 2017 04:58:24 Curt wrote:

> On 2017-12-21, Gene Heskett  wrote:
> > On Thursday 21 December 2017 04:20:51 Curt wrote:
> >> On 2017-12-21, Gene Heskett  wrote:
> >> > And I certainly wasn't doing landscape mode for an invoice
> >> > composed in letter format, aka Portrait mode.
> >>
> >> So you have unchecked the relevant default option in the print
> >> dialogue and determined that you have not been bitten by the bug to
> >> which I referred.
> >
> > No, I check that at every job, Portrait was checked.
> >
> > Cheers, Gene Heskett
>
> No, it was 'Page Handling/Auto Rotate and Center' that had to be
> unchecked.
>
> 'Portrait' is under 'Page Setup/Orientation', and it is not a checkbox
> option but rather a drop-down menu selection.
>
> Anywho.

Which does not exist in the requester kmail uses. But in the utility 
evince calls, it is on, and I can't find a way to make it stay off.

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: Sony Memory Stick problem on Debian 9 stable

[Darac Marjal]

On Thu, Dec 21, 2017 at 01:01:13PM +0330, Farhad Mohammadi Majd wrote:

Hello, I want to buy a old Sony compact digital camera which supports
only Memory Stick, a removable flash memory card format, before buy it,
I get its memory card to check is it supported under Linux or not.

I inserted it into memory card reader and it is detected by system:


# lsblk



NAME   MAJ:MIN RM   SIZE RO TYPE



sdc  8:32   1 2T  0 disk


2 Terabytes in an old digital camera? Either you're planning on taking a 
LOT of pictures our your Memory Stick is not actually recognised by the 
system.


First off, check that your card reader HARDWARE supports the MS. Have 
you read the Wikipedia page on Memory Sticks? There are almost as many 
variants as Secure Digital has. 
https://en.wikipedia.org/wiki/Memory_Stick


Secondly, have you checked for physical switches on the Memory Stick? 
There might be a read-only switch; there might even be a bank-select 
switch.




but fdisk can't do anything on it:


# fdisk /dev/sdc





fdisk: cannot open /dev/sdc: Input/output error







--
For more information, please reread.


signature.asc
Description: PGP signature

Re: got a new one

[Curt]

On 2017-12-21, Gene Heskett  wrote:
> On Thursday 21 December 2017 04:20:51 Curt wrote:
>
>> On 2017-12-21, Gene Heskett  wrote:
>> > And I certainly wasn't doing landscape mode for an invoice composed
>> > in letter format, aka Portrait mode.
>>
>> So you have unchecked the relevant default option in the print
>> dialogue and determined that you have not been bitten by the bug to
>> which I referred.
>
> No, I check that at every job, Portrait was checked.
>
> Cheers, Gene Heskett

No, it was 'Page Handling/Auto Rotate and Center' that had to be
unchecked.

'Portrait' is under 'Page Setup/Orientation', and it is not a checkbox
option but rather a drop-down menu selection.

Anywho.


-- 
"An autobiography is only to be trusted when it reveals something disgraceful.
A man who gives a good account of himself is probably lying, since any life
when viewed from the inside is simply a series of defeats."
— George Orwell

Re: got a new one

[Gene Heskett]

On Thursday 21 December 2017 04:20:51 Curt wrote:

> On 2017-12-21, Gene Heskett  wrote:
> > And I certainly wasn't doing landscape mode for an invoice composed
> > in letter format, aka Portrait mode.
>
> So you have unchecked the relevant default option in the print
> dialogue and determined that you have not been bitten by the bug to
> which I referred.

No, I check that at every job, Portrait was checked.

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 

Sony Memory Stick problem on Debian 9 stable

[Farhad Mohammadi Majd]

Hello, I want to buy a old Sony compact digital camera which supports
only Memory Stick, a removable flash memory card format, before buy it,
I get its memory card to check is it supported under Linux or not.

I inserted it into memory card reader and it is detected by system:

>>> # lsblk

>>> NAME   MAJ:MIN RM   SIZE RO TYPE

>>> sdc  8:32   1 2T  0 disk

but fdisk can't do anything on it:

>>> # fdisk /dev/sdc



>>> fdisk: cannot open /dev/sdc: Input/output error

Re: Debian 8 and Debian 9 Dual Boot

[Felix Miata]

Felix Miata composed on 2017-11-29 13:55 (UTC-0500):

> Dan Norton composed on 2017-11-28 22:15 (UTC-0500):

>> dan@debian8:~$ sudo fdisk /dev/sda
>> Command (m for help): p
>> Disk /dev/sda: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
>> Units: sectors of 1 * 512 = 512 bytes
>> Sector size (logical/physical): 512 bytes / 512 bytes
>> I/O size (minimum/optimal): 512 bytes / 512 bytes
>> Disklabel type: gpt
>> Disk identifier: A615A904-0620-459F-BF44-5E53E54FDF24

>> Device Start    End    Sectors   Size Type
>> /dev/sda1   2048 411647 409600   200M BIOS boot
>> /dev/sda2 411648   16783359   16371712   7.8G Linux swap
>> /dev/sda3   16783360  151001087  134217728    64G Linux LVM
>> /dev/sda4  151001088  285218815  134217728    64G Linux LVM
>> /dev/sda5  285218816  419436543  134217728    64G Linux LVM
>> /dev/sda6  419436544  553654271  134217728    64G Linux LVM
>> /dev/sda7  553654272 1953525134 1399870863 667.5G Linux filesystem

>> Is there a problem here?

> Maybe. I don't have any GPT-partitioned disks...  

No longer the case. I bought a G250 Kaby Lake Intel motherboard. I currently
have Stretch, openSUSE Tumbleweed and openSUSE 15.0 Alpha installed. openSUSE
42.3's installer hangs in the bootloader configuration step.
https://bugzilla.opensuse.org/show_bug.cgi?id=1073201

http://fm.no-ip.com/Tmp/Dfsee/gb250L02.txt is my partition log. The upper part
is generated by the partitioner I use. The bottom is gpart -l output for 
comparison.

I haven't seen you post the debian-user list in a while. How's multiboot going
for you?
-- 
"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: got a new one

[Curt]

On 2017-12-21, Gene Heskett  wrote:
>
> And I certainly wasn't doing landscape mode for an invoice composed in 
> letter format, aka Portrait mode.

So you have unchecked the relevant default option in the print dialogue
and determined that you have not been bitten by the bug to which I
referred.


-- 
"An autobiography is only to be trusted when it reveals something disgraceful.
A man who gives a good account of himself is probably lying, since any life
when viewed from the inside is simply a series of defeats."
— George Orwell

Re: LUKS password gets printed as stars

[Curt]

On 2017-12-20, Richard Hector  wrote:
>
> On 21/12/17 02:02, Curt wrote:
>> Also, I'm uncertain whether suppression of the asterisk-echo qualifies
>> as "security by obscurity"
>
> I think most people accept that obscurity is quite reasonable for
> passwords ...
>
> Richard
>

Wonderful, Dick, however, I was referring to the specific expression
"security by (or through) obscurity," which denotes something else.

https://en.wikipedia.org/wiki/Security_through_obscurity


-- 
"An autobiography is only to be trusted when it reveals something disgraceful.
A man who gives a good account of himself is probably lying, since any life
when viewed from the inside is simply a series of defeats."
— George Orwell

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

[Stephane Ascoet]

Le 20/12/2017 à 16:25, Sébastien NOBILI a écrit :

Bonjour,

Le mardi 19 décembre 2017 à 17:45, andre_deb...@numericable.fr a écrit :

Je ne  sais par quelle opération,
les noms des partitions de mon serveur sont
passés de /dev/sdaX à /dev/sdcX,
soit 8 partitions /dev/sda1 à 8 => /dev/sdc1 à 8.


https://lists.debian.org/debian-user-french/2017/08/msg00162.html

Bonjour, belle trouvaille, en fait les choses sont ainsi depuis cet ete, 
ce disque dur n'a jamais ete /dev/sda. Andre a du bidouille les 
etiquettes mais comme on l'a tous dit dans ce dialogue de sourd qui 
tourne en boucle, ce ne sont que des etiquettes, ce disque a toujours 
ete et sera toujours /dev/sdc. Visiblement Andre confond nom de bloc, 
etiquette et dossier de montage depuis le debut(etonnant pour un membre 
historique de la liste comme lui)...


--
Cordialement, Stephane Ascoet

Re: Debian networking - accessing public-side servers from a private network

[メット]

On 2017年12月21日 15:23:06 JST, Pascal Hambourg  wrote:
>Le 21/12/2017 à 01:48, Phil Reynolds a écrit :
>> 
 At no point does the router get involved in the communication
 between the phone and the Asterisk box. To do so might make things
 easier, or could just add an unnecessary layer of complexity.
>>>
>>> How does the private client know that the public server address is
>>> reachable directly on the LAN an not through the router ?
>> 
>> That I couldn't say, but it's plainly the case.
>
>How are TCP/IP parameters configured on the client ?
>Could you show its routing table ?
>
 - If I could get the phone to pick up the private address of the
 Asterisk box rather than the public one, that would probably
 work. I have tried setting up to do this with dnsmasq, but the IPv6
 settings for DNS cause this to be overridden. If I could somehow
 change the priority of this on the phone, it would help.
>>>
>>> All the IPv4 and IPv6 nameservers used by the client must resolve
>the
>>> name into the private address. If they also serve the public zone,
>>> you must set up "split DNS" to server different versions for private
>>> and public clients.
>> 
>> Unfortunately I have found no way to override the radvd-provided DNS
>> server addresses - otherwise I would have done this.
>Aren't you in control of the router configuration and which IPv6 DNS 
>servers are advertised in the RAs it sends (radvd ?), and of these 
>servers behaviour ?
>
>Just another thought : isn't it possible to set up Asterisk to listen 
>explicitly on both the private and public IPv4 addresses instead of any
>
>local address, so that it opens two separate sockets ? This way I think
>
>it would reply with the proper source address.


Sorry, I have been too fast on the last mail.
resiprocate is only sip and is for nat pbm.

Try setup asterisk address as ANY ie.
0.0.0.0.

Then asterisk will act on both addresses.

HTH

Re: Debian networking - accessing public-side servers from a private network

[メット]

On 2017年12月21日 15:23:06 JST, Pascal Hambourg  wrote:
>Le 21/12/2017 à 01:48, Phil Reynolds a écrit :
>> 
 At no point does the router get involved in the communication
 between the phone and the Asterisk box. To do so might make things
 easier, or could just add an unnecessary layer of complexity.
>>>
>>> How does the private client know that the public server address is
>>> reachable directly on the LAN an not through the router ?
>> 
>> That I couldn't say, but it's plainly the case.
>
>How are TCP/IP parameters configured on the client ?
>Could you show its routing table ?
>
 - If I could get the phone to pick up the private address of the
 Asterisk box rather than the public one, that would probably
 work. I have tried setting up to do this with dnsmasq, but the IPv6
 settings for DNS cause this to be overridden. If I could somehow
 change the priority of this on the phone, it would help.
>>>
>>> All the IPv4 and IPv6 nameservers used by the client must resolve
>the
>>> name into the private address. If they also serve the public zone,
>>> you must set up "split DNS" to server different versions for private
>>> and public clients.
>> 
>> Unfortunately I have found no way to override the radvd-provided DNS
>> server addresses - otherwise I would have done this.
>Aren't you in control of the router configuration and which IPv6 DNS 
>servers are advertised in the RAs it sends (radvd ?), and of these 
>servers behaviour ?
>
>Just another thought : isn't it possible to set up Asterisk to listen 
>explicitly on both the private and public IPv4 addresses instead of any
>
>local address, so that it opens two separate sockets ? This way I think
>
>it would reply with the proper source address.



Did u try to use stunt server? 
I had same pbm b4, 
solved with resiprocate stunt server
IIRC. 

Diff in my setup are: 
-asterisk and router are on same box, 
same OS
-using sip
Dont think that matters though. 

HTH