Re: portable CD players

2018-11-09 Thread mick crane

On 2018-11-10 06:52, Brad Rogers wrote:

On Sat, 10 Nov 2018 06:11:34 +
mick crane  wrote:

Hello mick,


If I put them on a CD will Discman play them, with a menu selection ?


Portable CD players of that type are usually audio CD players, they 
won't

play .mp3, .ogg, or any other file type, for that matter.  Insert a
non-audio disc and most simply report 'no disc'.


that's what I wondered and what exactly is an "audio disc" ?
Can I make one from mp3 ?
I'm not very good at audio.

mick

--
Key ID4BFEBB31



Re: portable CD players

2018-11-09 Thread Brad Rogers
On Sat, 10 Nov 2018 06:11:34 +
mick crane  wrote:

Hello mick,

>If I put them on a CD will Discman play them, with a menu selection ?

Portable CD players of that type are usually audio CD players, they won't
play .mp3, .ogg, or any other file type, for that matter.  Insert a
non-audio disc and most simply report 'no disc'.

-- 
 Regards  _
 / )   "The blindingly obvious is
/ _)radnever immediately apparent"
Age of destruction, age of oblivion
Neuromancer - Billy Idol


pgpGnSWUBWCdf.pgp
Description: OpenPGP digital signature


portable CD players

2018-11-09 Thread mick crane

Does anybody know about these portable CD players like Sony Discman ?
On the PC I
"play stories.m3u"
where "stories.m3u" is just a list of mp3 files from librivox.org

If I put them on a CD will Discman play them, with a menu selection ?
Are they ATRAC or something ?
Any particular format needed ?
Any recommendations for CD player ?

mick

--
Key ID4BFEBB31



Re: Pulseaudio as bluetooth Headset Audio Gateway (HSP/HFP)

2018-11-09 Thread dekks herton

On 11/09, Martin wrote:

Hi folks,

I wonder if some of you uses pulseaudio with cell phone telephony. For me, I 
see in the pulseaudio configuration window a Headset Audio Gateway (HSP/HFP) 
with is offered by an Android phone. But the Buetooth blueman-manager refuses 
to set this audio profile. A2DP works fine though.



Which cellphone which headphhones and which sink is active

--
regards.

Thinkpad T60p 2.33Ghz 2GB SXGA+

Jabber IM: dekkz...@jabber.hot-chilli.net


signature.asc
Description: PGP signature


Re: pushd/popd

2018-11-09 Thread Jonathan Dowland

On Fri, Nov 09, 2018 at 11:26:37AM -0500, Greg Wooledge wrote:

On Fri, Nov 09, 2018 at 04:20:57PM +, Jonathan Dowland wrote:

One of dash's design goals is to be a purely POSIX compatible shell*,


Not quite.


Fear not, I'm not confusing it with posh(1). That's my reading of the
dash(1) manpage:


The current version of dash is in the process of being changed to
conform with the POSIX 1003.2 and 1003.2a specifications for the
shell.

…

Only features designated by POSIX, plus a few Berkeley extensions, are
being incorporated into this shell.


Greg:

Yeah.  It's not meant to be a litmus test for whether your script refrains
from using any extensions.  It's not a compliance-testing tool.


It isn't indeed, that would be posh(1).

--

⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Jonathan Dowland
⢿⡄⠘⠷⠚⠋⠀ https://jmtd.net
⠈⠳⣄ Please do not CC me, I am subscribed to the list.



Re: Pulseaudio as bluetooth Headset Audio Gateway (HSP/HFP)

2018-11-09 Thread deloptes
Martin wrote:

> I wonder if some of you uses pulseaudio with cell phone telephony. For me,
> I see in the pulseaudio configuration window a Headset Audio Gateway
> (HSP/HFP) with is offered by an Android phone. But the Buetooth
> blueman-manager refuses to set this audio profile. A2DP works fine though.

Hi,
this topic is PITA for me since many moons.
I use Sailfish OS on the phone, but also spent some time recently on BT
integration with TDE. So to put it short, I recommend compiling and
installing PA 11.99 and higher. Someone reported that in 12.2 most of the
issues are resolved. Of course if you can get a backport is also fine.
The other thing is HSP/HFP profile. The protocols are different, I didn't go
into the details, but both should work fine - you need ofono installed for
this.
I actually tested the phone with recent car (I think it was KIA) and it
worked fine. Also the access to the phone book from the car was working
fine.

Do not forget that you depend on the BT lower level, so look forward to have
the kernel (drivers), the BT adapter and the tools in good shape.

Perhaps you use the crap python/gtk manager - it might work if you install
ofono (after installing you probably need to restart this and that). If it
does not work, just use bluetoothctl and play with UUIDs.
The problem is usually it picks up the first one profile available, which is
Audio. Here are the UUIDs from my notes

{ "1108--1000-8000-00805f9b34fb", "Headset" },
{ "1112--1000-8000-00805f9b34fb", "Headset AG" },

{ "111e--1000-8000-00805f9b34fb", "Handsfree" },
{ "111f--1000-8000-00805f9b34fb", "Handsfree AG" },

I hope it helps

regards



Re: Mystery interface reported by ip.

2018-11-09 Thread Greg Wooledge
On Fri, Nov 09, 2018 at 08:11:06AM -0800, pe...@easthope.ca wrote:
> 1)
> egrep -v '(^ *#)|(^ *$)' $1
> ;;

https://mywiki.wooledge.org/Quotes



Re: Mystery interface reported by ip.

2018-11-09 Thread Reco
Hi.

On Fri, Nov 09, 2018 at 08:11:06AM -0800, pe...@easthope.ca wrote:
> From: pe...@easthope.ca
> Date: Fri, 02 Nov 2018 06:03:42 -0700
> > ... will have another look at this and make a better report.
> 
> So here is the effective content of 
> /etc/udev/rules.d/70-persistent-net.rules.  
> (The definition of collect follows and is in 
> http://easthope.ca/DebianPage.html .)
> 
> peter@joule:~$ collect /etc/udev/rules.d/70*
> SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", 
> ATTR{address}=="00:1d:7e:00:ee:9f", \
> ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="LocLCS1788"
> SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", 
> ATTR{address}=="e8:94:f6:24:83:52", \
> ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="wlan*", NAME="wlan0"
> SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", 
> ATTR{address}=="a0:f3:c1:0a:28:f7", \
> ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="wlan*", NAME="wlan1"
> 
> LocLCS1788 is present and LocLCS218301788 is absent.  Nevertheless, 
> LocLCS218301788 
> surfaces here.

Ok, let's do it the hard way.

udevadm info /sys/class/net/LocLCS218301788
udevadm trigger /sys/class/net/LocLCS218301788

and, while we're at it,

udevadm info /sys/class/net/rename4
udevadm trigger /sys/class/net/rename4

Reco



Re: Mystery interface reported by ip.

2018-11-09 Thread peter
From: pe...@easthope.ca
Date: Fri, 02 Nov 2018 06:03:42 -0700
> ... will have another look at this and make a better report.

So here is the effective content of /etc/udev/rules.d/70-persistent-net.rules.  
(The definition of collect follows and is in http://easthope.ca/DebianPage.html 
.)

peter@joule:~$ collect /etc/udev/rules.d/70*
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", 
ATTR{address}=="00:1d:7e:00:ee:9f", \
ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="LocLCS1788"
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", 
ATTR{address}=="e8:94:f6:24:83:52", \
ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="wlan*", NAME="wlan0"
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", 
ATTR{address}=="a0:f3:c1:0a:28:f7", \
ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="wlan*", NAME="wlan1"

LocLCS1788 is present and LocLCS218301788 is absent.  Nevertheless, 
LocLCS218301788 
surfaces here.

peter@joule:~$ ip link show
1: lo:  mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT
 group default qlen 1
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: LocLCS218301788:  mtu 1500 qdisc noop state DOWN mode DE
FAULT group default qlen 1000
link/ether 00:07:e9:78:a8:b0 brd ff:ff:ff:ff:ff:ff
3: LocLCS1788:  mtu 1500 qdisc pfifo_fast sta
te DOWN mode DEFAULT group default qlen 1000
link/ether 00:1d:7e:00:ee:9f brd ff:ff:ff:ff:ff:ff
4: rename4:  mtu 1500 qdisc noop state DOWN mode DEFAULT gr
oup default qlen 1000
link/ether 00:1d:7e:01:3d:c2 brd ff:ff:ff:ff:ff:ff
5: wlan0:  mtu 1500 qdisc mq state UP mode DORM
ANT group default qlen 1000
link/ether e8:94:f6:24:83:52 brd ff:ff:ff:ff:ff:ff

How does the system dredge up LocLCS218301788?  A cache?  Haven't seen 
a mention of wicd caching old device names.  Other ideas?

Thanks,... Peter E.

===
peter@joule:~$ declare -f collect
collect ()
{
case $# in
0)
echo "collect  "
;;
1)
egrep -v '(^ *#)|(^ *$)' $1
;;
*)
echo "Too many arguments."
;;
esac
}

-- 
Message composed and transmitted by software designed to avoid the 
need, overhead and vulnerability of antivirus software.

123456789 123456789 123456789 123456789 123456789 123456789 123456789
Tel: +1 360 639 0202  +1 
http://easthope.ca/Peter.html  Bcc: peter at easthope. ca



Re: pushd/popd

2018-11-09 Thread Greg Wooledge
On Fri, Nov 09, 2018 at 04:20:57PM +, Jonathan Dowland wrote:
> One of dash's design goals is to be a purely POSIX compatible shell*,

Not quite.

> * they actually *do* implement some carefully defined extensions
>  according to the man page

Yeah.  It's not meant to be a litmus test for whether your script refrains
from using any extensions.  It's not a compliance-testing tool.



Re: pushd/popd

2018-11-09 Thread Jonathan Dowland

On Fri, Nov 09, 2018 at 06:20:01AM -0800, pe...@easthope.ca wrote:

... not dash (by design) ...


Why?  Easy enough to use pushd/popd and easy enough to not it but
I'm interested in the reasoning behind this choice.


One of dash's design goals is to be a purely POSIX compatible shell*,
so it deliberately does not implement anything else.

* they actually *do* implement some carefully defined extensions
 according to the man page

--

⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Jonathan Dowland
⢿⡄⠘⠷⠚⠋⠀ https://jmtd.net
⠈⠳⣄ Please do not CC me, I am subscribed to the list.



Re: Installing nvidia-driver removes xorg

2018-11-09 Thread Gregory Sharp
On Fri, 09 Nov 2018 13:10:38 +0100
floris  wrote:

> Gregory Sharp schreef op 2018-11-08 19:01:
> > 
> > Questions:
> > 
> > 1) Why should xorg be uninstalled when nvidia-driver is installed?
> > 
> > 2) What might be a recommended upgrade path for me?  
> 
>  From bug 903770 [1]:
> 
> ... the nvidia packages in stretch-backports now require mesa+libglvnd
> from stretch-backports.
> 
> You could try to install mesa, libglvnd and xorg from backports first.
> 
> 
> [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903770

Aha.  That explains it.  Thank you much for the link.

I have verified that (1) removing backports from the list of
repositories allows upgrading stable, and (2) a dist-upgrade of nvidia-driver
from stable to stretch-backports installs mesa, etc., which allows upgrade
without removing important packages.

Greg



Re: pushd/popd

2018-11-09 Thread peter
From: Jonathan Dowland 
Date: Thu, 8 Nov 2018 09:46:34 +
> They are not POSIX, I don't think they are covered by any subsequent
> standard either ...

OK, thanks.

> ... not dash (by design) ... 

Why?  Easy enough to use pushd/popd and easy enough to not it but 
I'm interested in the reasoning behind this choice.

Thanks,  ... Peter E.


-- 
Message composed and transmitted by software designed to avoid the 
need, overhead and vulnerability of antivirus software.

123456789 123456789 123456789 123456789 123456789 123456789 123456789
Tel: +1 360 639 0202  +1 
http://easthope.ca/Peter.html  Bcc: peter at easthope. ca



Re: Mirror release file expired

2018-11-09 Thread Cindy-Sue Causey
On 11/9/18, Brian  wrote:
> On Fri 09 Nov 2018 at 08:32:57 -0500, Boyan Penkov wrote:
>
>> On apt-get update, I see:
>>
>> Reading package lists... Done
>> E: Release file for
>> http://mirror.cc.columbia.edu/debian/dists/buster/InRelease is expired
>> (invalid since 17h 5min 48s). Updates for this repository will not be
>> applied.
>>
>> What's the best way to communicate this to the folks who manage that
>> particular mirror -- the Columbia one?
>
> http://mirror.cc.columbia.edu/ has a contact address.


What he said... *grin*

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

* runs with duct tape *



Re: Mirror release file expired

2018-11-09 Thread Cindy-Sue Causey
On 11/9/18, Boyan Penkov  wrote:
> On apt-get update, I see:
>
> Reading package lists... Done
> E: Release file for
> http://mirror.cc.columbia.edu/debian/dists/buster/InRelease is expired
> (invalid since 17h 5min 48s). Updates for this repository will not be
> applied.
>
> What's the best way to communicate this to the folks who manage that
> particular mirror -- the Columbia one?


I've been playing around with mirrors myself the last couple days so
it quickly/easily came to mind to try "backing up" your link there to:

http://mirror.cc.columbia.edu/

They have a bold text message that says:

"NOTE: Public use of this service is permitted but UNSUPPORTED! DO NOT
contact the CUIT Help Desk if you encounter problems with this site;
use the contact information below."

The good news is that they offer an email address at the bottom of
that same page. Its expressed purpose is for it to be used "[t]o
report problems or make suggestions" regarding the mirror(s).

Hope that helps! :)

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

* runs with duct tape *



Re: Mirror release file expired

2018-11-09 Thread Brian
On Fri 09 Nov 2018 at 08:32:57 -0500, Boyan Penkov wrote:

> On apt-get update, I see:
> 
> Reading package lists... Done
> E: Release file for
> http://mirror.cc.columbia.edu/debian/dists/buster/InRelease is expired
> (invalid since 17h 5min 48s). Updates for this repository will not be
> applied.
> 
> What's the best way to communicate this to the folks who manage that
> particular mirror -- the Columbia one?

http://mirror.cc.columbia.edu/ has a contact address.

-- 
Brian.



Re: 100Base-FX (SC) card PCI/PCIe

2018-11-09 Thread Michael Stone

On Fri, Nov 09, 2018 at 12:40:03PM +0200, Michelle Konzack wrote:

Gigabit, as someone sugested, would require OM4 cables which are
twice as expensive and also the Networkcards and switches.


That's not correct; gigabit over this distance would require OM2 at 
most, and may even work over FDDI grade fiber (not that I'd run FDDI 
grade fiber in 2018). OM4 would be required for 10gbase-sr for the 
longest run (and I'd personally go with single mode instead if you think 
you might ever want to upgrade past gigabit) but OM3 would suffice for 
the shorter runs.




Pulseaudio as bluetooth Headset Audio Gateway (HSP/HFP)

2018-11-09 Thread Martin
Hi folks,

I wonder if some of you uses pulseaudio with cell phone telephony. For me, I 
see in the pulseaudio configuration window a Headset Audio Gateway (HSP/HFP) 
with is offered by an Android phone. But the Buetooth blueman-manager refuses 
to set this audio profile. A2DP works fine though.



Mirror release file expired

2018-11-09 Thread Boyan Penkov
On apt-get update, I see:

Reading package lists... Done
E: Release file for
http://mirror.cc.columbia.edu/debian/dists/buster/InRelease is expired
(invalid since 17h 5min 48s). Updates for this repository will not be
applied.

What's the best way to communicate this to the folks who manage that
particular mirror -- the Columbia one?

Cheers!

-- 
Boyan Penkov



Re: 100Base-FX (SC) card PCI/PCIe

2018-11-09 Thread Joe
On Fri, 9 Nov 2018 12:40:03 +0200
"Michelle Konzack"  wrote:

> Hi Dan,
> 
> Am 2018-11-09 hackte Dan Ritter in die Tasten:
> > 802.11(abcgnhjklq%) is plausible but suffers from a lot of
> > interference.  
> 
> We have (like in the USA) problems with criminals, using Wifi-Jammer.
> 
> > Fiber is reasonably cheap,  
> 
> Yeah, I found  which seems VERY cheap even for
> customised lenghts of OM3 SC/SC cables.
> 
> Gigabit, as someone sugested, would require OM4 cables which are
> twice as expensive and also the Networkcards and switches.
> 

How much is single-mode fibre? The cheapest single-mode SFPs are
1.25GB/s, and the fibre will handle sixteen 3GB/s signals optically
multiplexed, if not more. I've been out of it for four or five years.

-- 
Joe



Re: Installing nvidia-driver removes xorg

2018-11-09 Thread floris

Gregory Sharp schreef op 2018-11-08 19:01:

I am currently running stretch with the nvidia display driver.  The
nvidia-driver package is not installed.  Instead, the 
nvidia-kernel-dkms

package and other packages needed for the display driver and CUDA are
installed.

While attempting an upgrade to CUDA 9 in backport, I learned that 
installing
nvidia-driver (either version: 384.130 or 390.87) would uninstall xorg, 
gdm3,

libreoffice, and many other seemingly useful packages.

Questions:

1) Why should xorg be uninstalled when nvidia-driver is installed?

2) What might be a recommended upgrade path for me?


From bug 903770 [1]:

... the nvidia packages in stretch-backports now require mesa+libglvnd
from stretch-backports.

You could try to install mesa, libglvnd and xorg from backports first.


[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903770

---
Floris



Re: Removing firefox-esr also removes gnome

2018-11-09 Thread Jonathan Dowland

On Fri, Nov 09, 2018 at 11:12:29AM +0900, John Crawley wrote:

Can a package depend on a non-existant virtual package?


It can, but this is likely a bug if it happens.

Is x-www-browser due to be added to the official Debian virtual 
package list?


I'm advocating for x-www-browser to exist, but haven't done the work
to make it so. Note that the authorative list of virtual package names
in policy is out of date. (I have some other ideas about fixing that
which I want to pick up too)

At the moment www-browser is a virtual package, but not a registered 
Debian alternative, while x-www-browser is an alternative but not a 
VP. :|


www-browser is an alternative, provided by (at least) lynx.

I suppose a workaround for the LXDE package would be to depend 
on/recommend/suggest any of a list of usable X browsers, like:

Suggests: firefox | firefox-esr | chromium ...
The choice of safe possibilities for that list might be quite limited.


Yes, but that is effectively doing the work of defining a virtual
package but in the LXDE dependencies. We might as well do it properly and
in the right place from the start.

BTW if a package ships a .desktop file evoking x-www-browser, is it 
not obliged to Depend on (rather than Recommend/Suggest) a package 
which provides that alternative? Or would a TryExec field in the 
.desktop file be enough to cover it?


Personally I agree that this should be a Depends:. I'm not sure the LXDE
maintainers agree. I think Recommends: would be acceptable *if* LXDE's
behaviour was to not show the button/shortcut if the path it was
pointing at was non-existent (perhaps this is achieved via TryExec=).
But that's not the current behaviour.


--

⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Jonathan Dowland
⢿⡄⠘⠷⠚⠋⠀ https://jmtd.net
⠈⠳⣄ Please do not CC me, I am subscribed to the list.



Re: Removing firefox-esr also removes gnome

2018-11-09 Thread Jonathan Dowland

On Thu, Nov 08, 2018 at 06:59:48PM +0300, Reco wrote:

lxde-core depends on www-browser already (Suggests, actually, but that's
irrelevant). So it might as well depend on this to-be-done
x-www-browser.


Yes. That's exactly what I am advocating in the bug I reported about
this (=833268, in 2016). I haven't yet re-assigned the bug to the
correct real package though.

--

⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Jonathan Dowland
⢿⡄⠘⠷⠚⠋⠀ https://jmtd.net
⠈⠳⣄ Please do not CC me, I am subscribed to the list.



Re: 100Base-FX (SC) card PCI/PCIe

2018-11-09 Thread Michelle Konzack
Hi Dan,

Am 2018-11-09 hackte Dan Ritter in die Tasten:
> 802.11(abcgnhjklq%) is plausible but suffers from a lot of
> interference.

We have (like in the USA) problems with criminals, using Wifi-Jammer.

> Fiber is reasonably cheap,

Yeah, I found  which seems VERY cheap even for
customised lenghts of OM3 SC/SC cables.

Gigabit, as someone sugested, would require OM4 cables which are
twice as expensive and also the Networkcards and switches.

I use for my "Serverbunker" a 16-port greenswitch (12V/2A) and for
every fiber cable a TP-Link MC100CM Media Converter.  On the other
end I use the Microsense MS453111 which has 7 x RJ45 100Mbit and 1 x
100BaseFX/SC (12V/1A).

I think this should work for all.

Oh, from the Server Bunker to the Portal I can use Fiber, but then
I can use my existing Cat5e Ethernet Earthcable to connect the first
4 IP-Cams and the SIP Interphone where I have not the need for any
protection pipes.

> although burying it in conduit or
> otherwise can get expensive or laborious.

I bought currently 400m protection pipe of 50mm diameter which I am
ongoing to place parallel with the HD-PE pipes and the electric cables.

> -dsr-

Thanks in advance

-- 
Michelle KonzackMiila ITSystems @ TDnet
GNU/Linux Developer 00372-54541400