Re: [DNG] Redhat CEO answers questions

2017-11-01 Thread Adam Borowski 
On Thu, Nov 02, 2017 at 12:27:37AM +0100, Alessandro Selli wrote:
> On Wed, 1 Nov 2017 at 08:57:30 -0400
> Hendrik Boom  wrote:
> 
> > On Tue, Oct 31, 2017 at 08:24:34PM -0400, taii...@gmx.com wrote:
> >> There is always one reason or another for "a start job is running for -
> >> network interfaces/disks/etc)" which halts the entire boot process
> >> "faster", even without those it still is much slower than devuan.  
> >
> > Wow!  Systemd even halts faster!
> 
>   Only if you keep the power button pressed long enough.

Faster way: echo o >/proc/sysrq-trigger

And unlike systemd, it doesn't randomly wait for 90 seconds for no reason,
with no guarantee it won't wait forever.

You might also want to write s and u first, but that'd be an unfair
comparison as this would be above feature parity.

(Only slightly trolling.)


Meow!
-- 
⢀⣴⠾⠻⢶⣦⠀ Laws we want back: Poland, Dz.U. 1921 nr.30 poz.177 (also Dz.U. 
⣾⠁⢰⠒⠀⣿⡁ 1920 nr.11 poz.61): Art.2: An official, guilty of accepting a gift
⢿⡄⠘⠷⠚⠋⠀ or another material benefit, or a promise thereof, [in matters
⠈⠳⣄ relevant to duties], shall be punished by death by shooting.
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Google abandons UEFI in Chromebooks

2017-11-01 Thread zap 

>> You might consider the Purism laptops, one of which has a detachable
>> keyboard.  https://puri.sm/products/
> https://www.reddit.com/r/linux/comments/3anjgm/on_the_librem_laptop_purism_doesnt_believe_in/
>
> They aren't worth it.
Yep mhm, they are deliberately lying too people saying they have the
intel me 100% disabled. but its more like 95% disabled. which is not
completely removed and therefore a lie.

They shouldn't call themselves purism unless they do what they say.
which in this case they don't.

the Eoma68 standard is much, much closer to such a point. and it also is
very energy efficient too.

I at one point believed them, but libreboot's claims and coreboots
claims on this set me straight.

Intel is almost impossible to remove the me on in later gens.  maybe
even impossible once everything is signed at least for the next 50+ years.

irony is not lost on me...

copyright = *H*azarous *A*nd *D*ownright *E*vil *S*cum


> ___
> Dng mailing list
> Dng@lists.dyne.org
> https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Redhat CEO answers questions

2017-11-01 Thread zap 

>> Wow!  Systemd even halts faster!
>   Only if you keep the power button pressed long enough.
Yay, someone else is a joker. ;)
>
> Alessandro
> ___
> Dng mailing list
> Dng@lists.dyne.org
> https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Google abandons UEFI in Chromebooks

2017-11-01 Thread taii...@gmx.com 

On 11/01/2017 08:23 AM, Hendrik Boom wrote:


On Tue, Oct 31, 2017 at 01:56:06PM +0100, Martin Steigerwald wrote:

As my next music playback machine I may even use such a Pine64. As anything
from ThinkPad X240 and upwards appears to be "protected" by Intel Boot Guard
Verified Boot crap, instead of just offering the Measured Boot feature for
those who want it. Or I go with a ThinkPad X230 where it appears that Intel ME
cleaner can do its work. May still be better the Pine64 appears to be a tad
bit limited especially by memory, although for music playback it would be
enough if expanded with a large MicroSD card. And it would have the advantage
that I would not have to mess with removing crap as it does not appear to have
crap inside. And cheaper too.

Other alternative may be a Chromebook if I can rid it easily enough of Chrome
OS and install my distro of choice on it.
I would get a Lenovo G505S, it is the last and best owner controlled 
x86-64 laptop. No ME/PSP and no hardware code signing enforcement. There 
is a blob for video and power but they are removable.
If you want a dock or better build quality the X230 (with an x220 
keyboard) is a good choice if you don't mind ME (please note ME cleaner 
is nerfing not disabling it)


An affordable desktop/server choice is the KCMA-D8 ($250) with a $20 
CPU, features include IOMMU, OpenBMC remote access and a 100% libre init 
coreboot.

You might consider the Purism laptops, one of which has a detachable
keyboard.  https://puri.sm/products/

https://www.reddit.com/r/linux/comments/3anjgm/on_the_librem_laptop_purism_doesnt_believe_in/
They aren't worth it.
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Redhat CEO answers questions

2017-11-01 Thread Alessandro Selli 
On Wed, 1 Nov 2017 at 08:57:30 -0400
Hendrik Boom  wrote:

> On Tue, Oct 31, 2017 at 08:24:34PM -0400, taii...@gmx.com wrote:
>> There is always one reason or another for "a start job is running for -
>> network interfaces/disks/etc)" which halts the entire boot process
>> "faster", even without those it still is much slower than devuan.  
>
> Wow!  Systemd even halts faster!

  Only if you keep the power button pressed long enough.


Alessandro
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Google abandons UEFI in Chromebooks

2017-11-01 Thread Alessandro Selli 
On Wed, 1 Nov 2017 at 15:27:48 -0400
Steve Litt  wrote:

> On Tue, 31 Oct 2017 11:47:51 +0100
> Martin Steigerwald  wrote:
>
>> Steve Litt - 30.10.17, 12:08:  
>>> On Mon, 30 Oct 2017 12:53:45 +0100
>>>
>>> Martin Steigerwald  wrote:
 Actually I´d make firmware pretty dumb and implement as much as I
 can in loaded software. Just enough firmware to actually
 install / boot a bootloader which loads an operating kernel and
 initial ram disk.
>>>
>>> Which is pretty much what we had in MBR. Which is why I always try
>>> to boot MBR.
>>
>> I now read through the slides about NERF and well… it appears that
>> with non extensible they have simplicity in mind. They relay all the
>> extensibility to the go based user space Initramfs. I am not sure
>> whether some go based thing would have been needed her but I am
>> thankful for any efforts to rid systems of proprietary firmware crap.
>> Even better tough: Not putting in the crap in the first place. No
>> crap inside? No effort needed to rip it out again.  
>
> Initramfs is another mess.

  It's just a (sometimes compressed) cpio archive.

> You can't debug it directly:

  What do you mean by this?

> You sort of
> have to take a time machine back (or forward) to ultra-early boot.
>
> I've lost the battle to keep your average Linux distro sans-initramfs,
> so now I'm fighting a lesser battle: How much stuff do you want in your
> initramfs, where realtime debugging is increasingly difficult and
> increasingly owned by Redhat?

  Initramfs is indispensable when you boot a system:
*) on an encrypted root partition;
*) having a merged root and usr partitions and /usr on it's own partition;
*) both of the above.

  I fact most embedded Linux systems do not have it.

  Red Hat used dracut to manage initramfs, De*an and like distros use
initramfs-tools.


Alessandro
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Bluetooth headset on Devuan?

2017-11-01 Thread Mike Schmitz 
On Wed, Nov 01, 2017 at 02:14:27PM -0700, Mike Schmitz wrote:
> On Wed, Nov 01, 2017 at 01:43:32PM -0700, Mike Schmitz wrote:
> > On Wed, Nov 01, 2017 at 08:31:55AM -0500, dev wrote:
> > > On 10/31/2017 12:42 PM, Mike Schmitz wrote:
> > > 
> > > > 
> > > > Another project has picked up the ball and run with it, though. It works
> > > > for me (SoundBot SB220)
> > > > 
> > > > https://github.com/Arkq/bluez-alsa
> > > > 
> > > 
> > > Nice! I've got it almost working. I'm stuck on "Couldn't get BlueALSA
> > > transport: No such device" Any thoughts?  From what I've googled so far,
> > > solutions involve pulseaudio, or reference a pulseaudio conflict.  I
> > > have some libpulse scattieness installed[0] for apulse support, but
> > > maybe I cannot have both? Perhaps I should remove those?
> > > 
> > > So far, I've installed alsa and development libs[1] but had to add the
> > > debian jessie repo[2] in order to get libfdk-aac-dev. Is there another
> > > place for this?
> > > 
> > > I cloned the bluez-alsa git repo and built per git page[3]. Configured
> > > ~/.asoundrc for my bluetooth headset MAC[4]. The alsa-lib directory
> > > installed to a location unknown to Devaun[5] so I sylinked[6] the new
> > > libraries to a good location. I did 'echo /usr/lib/alsa-lib >
> > > /etc/ld.so.conf.d/alsa-lib.conf' but this did not seem to help after
> > > issuing ldconfig.
> > > 
> > > The bluealsa "server" seems to start ok and generates no errors[7] when
> > > trying to play a sound via aplay, however aplay does not seem to know[8]
> > > yet how to use the headset. I did have an issue with permissions on[9]
> > > on /var/run/bluealsa but I think I fixed those[9]. Right now, aplay
> > > cannot "get BlueALSA transport"[10]. Any thoughts?
> > > 
> > > Thank you!
> > > 
> > > [0]
> > > i   apulse  - PulseAudio emulation for ALSA
> > > 
> > > i   libpulse-mainloop-glib0 - PulseAudio client libraries (glib
> > > support)
> > > i   libpulse0   - PulseAudio client libraries
> > > 
> > > i   libpulsedsp - PulseAudio OSS pre-load library
> > > 
> > > i   pulseaudio-utils- Command line tools for the
> > > PulseAudio soun
> > > i   vlc-plugin-pulse- transitional dummy package for vlc
> > > 
> > > 
> > > 
> > > [1]
> > > aptitude install libalsaplayer-dev bluez bluez-tools libsbc-dev
> > > libfdk-aac-dev alsa-tools alsaplayer-alsa libasound2-dev bluez-hcidump
> > > checkinstall libusb-dev  libbluetooth-dev  libbluetooth-dev
> > > libbluetooth3-dev
> > > libglib2.0-dev
> > > 
> > > [2]
> > > Add debian jessie rep for libfdk-aac-dev
> > > 
> > > libfdk-aac-dev required repo:
> > >deb http://httpredir.debian.org/debian/ jessie main contrib non-free
> > > 
> > > aptitude install libfdk-aac-dev
> > > 
> > > [3]
> > > git clone https://github.com/Arkq/bluez-alsa.git
> > > cd bluez-alsa; mkdir build; autoreconf --install; cd build; ../configure
> > > --enable-aac --enable-debug
> > > make
> > > make install
> > > 
> > > 
> > > [4]
> > > $ cat ~/.asoundrc
> > > defaults.bluealsa.interface "hci0"
> > > defaults.bluealsa.device "02:FC:9F:F8:13:94"
> > > defaults.bluealsa.profile "a2dp"
> > > 
> > > [5]
> > > $ aplay -D bluealsa:HCI=hci0,DEV=02:FC:9F:F8:13:94,PROFILE=a2dp
> > > /usr/share/sounds/purple/Windows\ Notify.wav
> > > ALSA lib dlmisc.c:252:(snd1_dlobj_cache_get) Cannot open shared library
> > > /usr/lib/x86_64-linux-gnu/alsa-lib/libasound_module_pcm_bluealsa.so
> > > aplay: main:722: audio open error: No such device or address
> > > 
> > > [6]
> > > # ldconfig -v | grep alsa
> > > 
> > > /usr/lib/alsa-lib:
> > >   libasound_module_ctl_bluealsa.so -> libasound_module_ctl_bluealsa.so
> > >   libasound_module_pcm_bluealsa.so -> libasound_module_pcm_bluealsa.so
> > > 
> > > # ln -s /usr/lib/alsa-lib/libasound_module_*
> > > /usr/lib/x86_64-linux-gnu/alsa-lib/
> > > 
> > > 
> > > [7]
> > > $ bluealsa --disable-hfp
> > > bluealsa: ../../src/ctl.c:489: Starting controller loop
> > > bluealsa: ../../src/bluez.c:680: Registering endpoint: 
> > > /A2DP/MPEG24/Source/1
> > > bluealsa: ../../src/bluez.c:680: Registering endpoint: /A2DP/MPEG24/Sink/1
> > > bluealsa: ../../src/bluez.c:680: Registering endpoint: /A2DP/SBC/Source/1
> > > bluealsa: ../../src/bluez.c:680: Registering endpoint: /A2DP/SBC/Sink/1
> > > bluealsa: ../../src/bluez.c:910: Registering profile: /HSP/Headset
> > > bluealsa: ../../src/bluez.c:910: Registering profile: /HSP/AudioGateway
> > > bluealsa: ../../src/main.c:225: Starting main dispatching loop
> > > bluealsa: ../../src/ctl.c:550: New client accepted: 8
> > > bluealsa: ../../src/ctl.c:571: +-+-
> > > bluealsa: ../../src/ctl.c:571: +-+-
> > > bluealsa: ../../src/ctl.c:521: Client closed connection: 8
> > > bluealsa: ../../src/ctl.c:571: +-+-
> > > 
> > > 
> > > [8]
> > > $ aplay -D bluealsa:HCI=hci0,DEV=02:FC:9F:F8:13:94,PROFILE=a2dp
> > > /usr/share/sounds/purple/Windows\ Notify.wav
> > >

Re: [DNG] Google abandons UEFI in Chromebooks

2017-11-01 Thread Alessandro Selli 
On Tue, 31 Oct 2017 at 12:41:47 +0100
Adam Borowski  wrote:

[...]

> The "secure" world marks certain resources (memory regions, interrupts,
> peripherals, etc).  Upon an attempt to access a marked resource, there's a
> "world switch" that most of us would call an "interrupt" (except that they
> decided to invent a new word, to disambiguate from regular interrupts).

  I think speaking of a context switch is more appropriate, rather than of an
interrupt.


Alessandro


___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Bluetooth headset on Devuan?

2017-11-01 Thread Mike Schmitz 
On Wed, Nov 01, 2017 at 01:43:32PM -0700, Mike Schmitz wrote:
> On Wed, Nov 01, 2017 at 08:31:55AM -0500, dev wrote:
> > On 10/31/2017 12:42 PM, Mike Schmitz wrote:
> > 
> > > 
> > > Another project has picked up the ball and run with it, though. It works
> > > for me (SoundBot SB220)
> > > 
> > > https://github.com/Arkq/bluez-alsa
> > > 
> > 
> > Nice! I've got it almost working. I'm stuck on "Couldn't get BlueALSA
> > transport: No such device" Any thoughts?  From what I've googled so far,
> > solutions involve pulseaudio, or reference a pulseaudio conflict.  I
> > have some libpulse scattieness installed[0] for apulse support, but
> > maybe I cannot have both? Perhaps I should remove those?
> > 
> > So far, I've installed alsa and development libs[1] but had to add the
> > debian jessie repo[2] in order to get libfdk-aac-dev. Is there another
> > place for this?
> > 
> > I cloned the bluez-alsa git repo and built per git page[3]. Configured
> > ~/.asoundrc for my bluetooth headset MAC[4]. The alsa-lib directory
> > installed to a location unknown to Devaun[5] so I sylinked[6] the new
> > libraries to a good location. I did 'echo /usr/lib/alsa-lib >
> > /etc/ld.so.conf.d/alsa-lib.conf' but this did not seem to help after
> > issuing ldconfig.
> > 
> > The bluealsa "server" seems to start ok and generates no errors[7] when
> > trying to play a sound via aplay, however aplay does not seem to know[8]
> > yet how to use the headset. I did have an issue with permissions on[9]
> > on /var/run/bluealsa but I think I fixed those[9]. Right now, aplay
> > cannot "get BlueALSA transport"[10]. Any thoughts?
> > 
> > Thank you!
> > 
> > [0]
> > i   apulse  - PulseAudio emulation for ALSA
> > 
> > i   libpulse-mainloop-glib0 - PulseAudio client libraries (glib
> > support)
> > i   libpulse0   - PulseAudio client libraries
> > 
> > i   libpulsedsp - PulseAudio OSS pre-load library
> > 
> > i   pulseaudio-utils- Command line tools for the
> > PulseAudio soun
> > i   vlc-plugin-pulse- transitional dummy package for vlc
> > 
> > 
> > 
> > [1]
> > aptitude install libalsaplayer-dev bluez bluez-tools libsbc-dev
> > libfdk-aac-dev alsa-tools alsaplayer-alsa libasound2-dev bluez-hcidump
> > checkinstall libusb-dev  libbluetooth-dev  libbluetooth-dev
> > libbluetooth3-dev
> > libglib2.0-dev
> > 
> > [2]
> > Add debian jessie rep for libfdk-aac-dev
> > 
> > libfdk-aac-dev required repo:
> >deb http://httpredir.debian.org/debian/ jessie main contrib non-free
> > 
> > aptitude install libfdk-aac-dev
> > 
> > [3]
> > git clone https://github.com/Arkq/bluez-alsa.git
> > cd bluez-alsa; mkdir build; autoreconf --install; cd build; ../configure
> > --enable-aac --enable-debug
> > make
> > make install
> > 
> > 
> > [4]
> > $ cat ~/.asoundrc
> > defaults.bluealsa.interface "hci0"
> > defaults.bluealsa.device "02:FC:9F:F8:13:94"
> > defaults.bluealsa.profile "a2dp"
> > 
> > [5]
> > $ aplay -D bluealsa:HCI=hci0,DEV=02:FC:9F:F8:13:94,PROFILE=a2dp
> > /usr/share/sounds/purple/Windows\ Notify.wav
> > ALSA lib dlmisc.c:252:(snd1_dlobj_cache_get) Cannot open shared library
> > /usr/lib/x86_64-linux-gnu/alsa-lib/libasound_module_pcm_bluealsa.so
> > aplay: main:722: audio open error: No such device or address
> > 
> > [6]
> > # ldconfig -v | grep alsa
> > 
> > /usr/lib/alsa-lib:
> > libasound_module_ctl_bluealsa.so -> libasound_module_ctl_bluealsa.so
> > libasound_module_pcm_bluealsa.so -> libasound_module_pcm_bluealsa.so
> > 
> > # ln -s /usr/lib/alsa-lib/libasound_module_*
> > /usr/lib/x86_64-linux-gnu/alsa-lib/
> > 
> > 
> > [7]
> > $ bluealsa --disable-hfp
> > bluealsa: ../../src/ctl.c:489: Starting controller loop
> > bluealsa: ../../src/bluez.c:680: Registering endpoint: /A2DP/MPEG24/Source/1
> > bluealsa: ../../src/bluez.c:680: Registering endpoint: /A2DP/MPEG24/Sink/1
> > bluealsa: ../../src/bluez.c:680: Registering endpoint: /A2DP/SBC/Source/1
> > bluealsa: ../../src/bluez.c:680: Registering endpoint: /A2DP/SBC/Sink/1
> > bluealsa: ../../src/bluez.c:910: Registering profile: /HSP/Headset
> > bluealsa: ../../src/bluez.c:910: Registering profile: /HSP/AudioGateway
> > bluealsa: ../../src/main.c:225: Starting main dispatching loop
> > bluealsa: ../../src/ctl.c:550: New client accepted: 8
> > bluealsa: ../../src/ctl.c:571: +-+-
> > bluealsa: ../../src/ctl.c:571: +-+-
> > bluealsa: ../../src/ctl.c:521: Client closed connection: 8
> > bluealsa: ../../src/ctl.c:571: +-+-
> > 
> > 
> > [8]
> > $ aplay -D bluealsa:HCI=hci0,DEV=02:FC:9F:F8:13:94,PROFILE=a2dp
> > /usr/share/sounds/purple/Windows\ Notify.wav
> > ../../../src/asound/../shared/ctl-client.c:102: Connecting to socket:
> > /var/run/bluealsa/hci0
> > ALSA lib ../../../src/asound/bluealsa-pcm.c:645:(_snd_pcm_bluealsa_open)
> > BlueALSA connection failed: No such file or directory
> > aplay: main:722: audio open error: No such file or directory
> > 
> > 
> > [9]
> > chown

Re: [DNG] Bluetooth headset on Devuan?

2017-11-01 Thread Mike Schmitz 
On Wed, Nov 01, 2017 at 08:31:55AM -0500, dev wrote:
> On 10/31/2017 12:42 PM, Mike Schmitz wrote:
> 
> > 
> > Another project has picked up the ball and run with it, though. It works
> > for me (SoundBot SB220)
> > 
> > https://github.com/Arkq/bluez-alsa
> > 
> 
> Nice! I've got it almost working. I'm stuck on "Couldn't get BlueALSA
> transport: No such device" Any thoughts?  From what I've googled so far,
> solutions involve pulseaudio, or reference a pulseaudio conflict.  I
> have some libpulse scattieness installed[0] for apulse support, but
> maybe I cannot have both? Perhaps I should remove those?
> 
> So far, I've installed alsa and development libs[1] but had to add the
> debian jessie repo[2] in order to get libfdk-aac-dev. Is there another
> place for this?
> 
> I cloned the bluez-alsa git repo and built per git page[3]. Configured
> ~/.asoundrc for my bluetooth headset MAC[4]. The alsa-lib directory
> installed to a location unknown to Devaun[5] so I sylinked[6] the new
> libraries to a good location. I did 'echo /usr/lib/alsa-lib >
> /etc/ld.so.conf.d/alsa-lib.conf' but this did not seem to help after
> issuing ldconfig.
> 
> The bluealsa "server" seems to start ok and generates no errors[7] when
> trying to play a sound via aplay, however aplay does not seem to know[8]
> yet how to use the headset. I did have an issue with permissions on[9]
> on /var/run/bluealsa but I think I fixed those[9]. Right now, aplay
> cannot "get BlueALSA transport"[10]. Any thoughts?
> 
> Thank you!
> 
> [0]
> i   apulse  - PulseAudio emulation for ALSA
> 
> i   libpulse-mainloop-glib0 - PulseAudio client libraries (glib
> support)
> i   libpulse0   - PulseAudio client libraries
> 
> i   libpulsedsp - PulseAudio OSS pre-load library
> 
> i   pulseaudio-utils- Command line tools for the
> PulseAudio soun
> i   vlc-plugin-pulse- transitional dummy package for vlc
> 
> 
> 
> [1]
> aptitude install libalsaplayer-dev bluez bluez-tools libsbc-dev
> libfdk-aac-dev alsa-tools alsaplayer-alsa libasound2-dev bluez-hcidump
> checkinstall libusb-dev  libbluetooth-dev  libbluetooth-dev
> libbluetooth3-dev
> libglib2.0-dev
> 
> [2]
> Add debian jessie rep for libfdk-aac-dev
> 
> libfdk-aac-dev required repo:
>deb http://httpredir.debian.org/debian/ jessie main contrib non-free
> 
> aptitude install libfdk-aac-dev
> 
> [3]
> git clone https://github.com/Arkq/bluez-alsa.git
> cd bluez-alsa; mkdir build; autoreconf --install; cd build; ../configure
> --enable-aac --enable-debug
> make
> make install
> 
> 
> [4]
> $ cat ~/.asoundrc
> defaults.bluealsa.interface "hci0"
> defaults.bluealsa.device "02:FC:9F:F8:13:94"
> defaults.bluealsa.profile "a2dp"
> 
> [5]
> $ aplay -D bluealsa:HCI=hci0,DEV=02:FC:9F:F8:13:94,PROFILE=a2dp
> /usr/share/sounds/purple/Windows\ Notify.wav
> ALSA lib dlmisc.c:252:(snd1_dlobj_cache_get) Cannot open shared library
> /usr/lib/x86_64-linux-gnu/alsa-lib/libasound_module_pcm_bluealsa.so
> aplay: main:722: audio open error: No such device or address
> 
> [6]
> # ldconfig -v | grep alsa
> 
> /usr/lib/alsa-lib:
>   libasound_module_ctl_bluealsa.so -> libasound_module_ctl_bluealsa.so
>   libasound_module_pcm_bluealsa.so -> libasound_module_pcm_bluealsa.so
> 
> # ln -s /usr/lib/alsa-lib/libasound_module_*
> /usr/lib/x86_64-linux-gnu/alsa-lib/
> 
> 
> [7]
> $ bluealsa --disable-hfp
> bluealsa: ../../src/ctl.c:489: Starting controller loop
> bluealsa: ../../src/bluez.c:680: Registering endpoint: /A2DP/MPEG24/Source/1
> bluealsa: ../../src/bluez.c:680: Registering endpoint: /A2DP/MPEG24/Sink/1
> bluealsa: ../../src/bluez.c:680: Registering endpoint: /A2DP/SBC/Source/1
> bluealsa: ../../src/bluez.c:680: Registering endpoint: /A2DP/SBC/Sink/1
> bluealsa: ../../src/bluez.c:910: Registering profile: /HSP/Headset
> bluealsa: ../../src/bluez.c:910: Registering profile: /HSP/AudioGateway
> bluealsa: ../../src/main.c:225: Starting main dispatching loop
> bluealsa: ../../src/ctl.c:550: New client accepted: 8
> bluealsa: ../../src/ctl.c:571: +-+-
> bluealsa: ../../src/ctl.c:571: +-+-
> bluealsa: ../../src/ctl.c:521: Client closed connection: 8
> bluealsa: ../../src/ctl.c:571: +-+-
> 
> 
> [8]
> $ aplay -D bluealsa:HCI=hci0,DEV=02:FC:9F:F8:13:94,PROFILE=a2dp
> /usr/share/sounds/purple/Windows\ Notify.wav
> ../../../src/asound/../shared/ctl-client.c:102: Connecting to socket:
> /var/run/bluealsa/hci0
> ALSA lib ../../../src/asound/bluealsa-pcm.c:645:(_snd_pcm_bluealsa_open)
> BlueALSA connection failed: No such file or directory
> aplay: main:722: audio open error: No such file or directory
> 
> 
> [9]
> chown root:myuser /var/run/bluealsa
> chmod g+w+s /var/run/bluealsa
> 
> 
> [10]
> $ aplay -D bluealsa:HCI=hci0,DEV=02:FC:9F:F8:13:94,PROFILE=a2dp
> /usr/share/sounds/purple/Windows\ Notify.wav
> ../../../src/asound/../shared/ctl-client.c:102: Connecting to socket:
> /var/run/bluealsa/hci0
>

Re: [DNG] Redhat CEO answers questions

2017-11-01 Thread zap 

> Sorry for interrupting, but I was wondering whether this discussion is
> useful at all to Devuan. Please don't get me wrong: you are free to
> continue, but really, what's the point? 
Sorry, couldn't resist making some humor out of an annoying situation.
>
> systemd is a reality, and making sad or smart jokes about it does not
> make it more palatable, or less of a threat.
yep, you are right systemd is a reality, I just needed to vent somehow.
and making my jokes is one way of doing so...
>
> A modest proposal: if people have some time to spare for Devuan, it
> would be useful at this point to start testing all the possible
> upgrade paths to Devuan Ascii, e.g., a) from Debian Jessie, b) from
> Devuan Jessie, c) from Debian Stretch, with as many different
> configurations as possible, and report any issue they find to
> http://bugs.devuan.org. Even upgrades of VMs would be informative.
>
> TIA
>
> KatolaZ
Good point.
>
>
> ___
> Dng mailing list
> Dng@lists.dyne.org
> https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Google abandons UEFI in Chromebooks

2017-11-01 Thread Steve Litt 
On Tue, 31 Oct 2017 11:47:51 +0100
Martin Steigerwald  wrote:

> Steve Litt - 30.10.17, 12:08:
> > On Mon, 30 Oct 2017 12:53:45 +0100
> > 
> > Martin Steigerwald  wrote:  
> > > Actually I´d make firmware pretty dumb and implement as much as I
> > > can in loaded software. Just enough firmware to actually
> > > install / boot a bootloader which loads an operating kernel and
> > > initial ram disk.  
> > 
> > Which is pretty much what we had in MBR. Which is why I always try
> > to boot MBR.  
> 
> I now read through the slides about NERF and well… it appears that
> with non extensible they have simplicity in mind. They relay all the
> extensibility to the go based user space Initramfs. I am not sure
> whether some go based thing would have been needed her but I am
> thankful for any efforts to rid systems of proprietary firmware crap.
> Even better tough: Not putting in the crap in the first place. No
> crap inside? No effort needed to rip it out again.

Initramfs is another mess. You can't debug it directly: You sort of
have to take a time machine back (or forward) to ultra-early boot.

I've lost the battle to keep your average Linux distro sans-initramfs,
so now I'm fighting a lesser battle: How much stuff do you want in your
initramfs, where realtime debugging is increasingly difficult and
increasingly owned by Redhat?

The stated purpose of initramfs is to boot far enough to mount the root
partition, after which everything else can be mounted via /etc/fstab.
Unless the executables do do such mounting have been placed off the
root's tree, in which case those must be available on the initramfs.
The more that goes in initramfs, the higher the barrier to entry for
the DIY Linux person.

SteveT

Steve Litt 
October 2017 featured book: Rapid Learning for the 21st Century
http://www.troubleshooters.com/rl21
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Fresh install of Ascii (was Re: Redhat CEO answers questions)

2017-11-01 Thread KatolaZ 
On Wed, Nov 01, 2017 at 04:48:46PM +0100, Juergen Moebius wrote:
> On Wed, Nov 01, 2017 at 16:16:58PM GMT KatolaZ wrote:
> > It is nevertheless possible to install ascii from scratch using the
> > jessie netinst image in expert mode, and fiddling with the repos on
> > /target before the actual installation starts, but it's not
> > recommended, and it will not be useful at all, since there will be an
> > ascii installer in place for that.
> >
> > Trying all the possible upgrade paths would be very useful, instead.
> 
> ok, thanks for your answer. Then i will upgrade a Devuan Jessie
> installed on a testing system.
> 

Thanks. Please keep in mind that ascii is still to be considered
a "testing" release.

HND

KatolaZ

-- 
[ ~.,_  Enzo Nicosia aka KatolaZ - Devuan -- Freaknet Medialab  ]  
[ "+.  katolaz [at] freaknet.org --- katolaz [at] yahoo.it  ]
[   @)   http://kalos.mine.nu ---  Devuan GNU + Linux User  ]
[ @@)  http://maths.qmul.ac.uk/~vnicosia --  GPG: 0B5F062F  ] 
[ (@@@)  Twitter: @KatolaZ - skype: katolaz -- github: KatolaZ  ]


signature.asc
Description: Digital signature
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Fresh install of Ascii (was Re: Redhat CEO answers questions)

2017-11-01 Thread Juergen Moebius 
On Wed, Nov 01, 2017 at 16:16:58PM GMT KatolaZ wrote:
> It is nevertheless possible to install ascii from scratch using the
> jessie netinst image in expert mode, and fiddling with the repos on
> /target before the actual installation starts, but it's not
> recommended, and it will not be useful at all, since there will be an
> ascii installer in place for that.
>
> Trying all the possible upgrade paths would be very useful, instead.

ok, thanks for your answer. Then i will upgrade a Devuan Jessie
installed on a testing system.

Greetings,
Juergen

___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Fresh install of Ascii (was Re: Redhat CEO answers questions)

2017-11-01 Thread Svante Signell 
On Wed, 2017-11-01 at 17:06 +0200, Lars Noodén wrote:
> On 11/01/2017 05:04 PM, Juergen Moebius wrote:
> > it is possible to install a fresh "full" copy of ascii, not an update?
> > I neverless updated my systems, sorry. A new installation is allways
> > the better way for my.
> 
> Not yet.  rsyslog is still missing.  So that has to be carried forward
> from Jessie.

rsyslog is available by now (8.24.0-1+devuan2.0)
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Fresh install of Ascii (was Re: Redhat CEO answers questions)

2017-11-01 Thread Lars Noodén 
On 11/01/2017 05:16 PM, KatolaZ wrote:
> On Wed, Nov 01, 2017 at 05:06:58PM +0200, Lars Nood�n wrote:
>> On 11/01/2017 05:04 PM, Juergen Moebius wrote:
>>> it is possible to install a fresh "full" copy of ascii, not an update?
>>> I neverless updated my systems, sorry. A new installation is allways
>>> the better way for my.
>>
>> Not yet.  rsyslog is still missing.  So that has to be carried forward
>> from Jessie.
> 
> Not true. The new version of rsyslog has been available in the repos
> since a few weeks ago (8.24.0-1+devuan2.0), 
[snip]

Thanks.  I stand (happily) corrected on that.

I had been doing 'apt-get upgrade' and watching rsyslog stay held back
all this time.  However, explicitly installing it puts it in place.

/Lars

$ apt-cache policy rsyslog
rsyslog:
  Installed: 8.24.0-1+devuan2.0
  Candidate: 8.24.0-1+devuan2.0
  Version table:
 *** 8.24.0-1+devuan2.0 500
500 http://pkgmaster.devuan.org/merged ascii/main amd64 Packages
500 http://packages.devuan.org/merged ascii/main amd64 Packages
100 /var/lib/dpkg/status

$ lsb_release -rd
Description:Devuan GNU/Linux 2.0 (ascii)
Release:2.0

$ grep -E '^\w' /etc/apt/sources.list
deb http://pkgmaster.devuan.org/merged ascii main
deb http://pkgmaster.devuan.org/merged ascii-updates main
deb http://pkgmaster.devuan.org/merged ascii-security main
deb http://packages.devuan.org/merged ascii main




___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Fresh install of Ascii (was Re: Redhat CEO answers questions)

2017-11-01 Thread KatolaZ 
On Wed, Nov 01, 2017 at 05:06:58PM +0200, Lars Noodén wrote:
> On 11/01/2017 05:04 PM, Juergen Moebius wrote:
> > it is possible to install a fresh "full" copy of ascii, not an update?
> > I neverless updated my systems, sorry. A new installation is allways
> > the better way for my.
> 
> Not yet.  rsyslog is still missing.  So that has to be carried forward
> from Jessie.
> 

Not true. The new version of rsyslog has been available in the repos
since a few weeks ago (8.24.0-1+devuan2.0), but atm we don't have an
easy way to install ascii from scratch, because we don't have an ascii
installer ready as yet.

It is nevertheless possible to install ascii from scratch using the
jessie netinst image in expert mode, and fiddling with the repos on
/target before the actual installation starts, but it's not
recommended, and it will not be useful at all, since there will be an
ascii installer in place for that.

Trying all the possible upgrade paths would be very useful, instead.

HND

KatolaZ

-- 
[ ~.,_  Enzo Nicosia aka KatolaZ - Devuan -- Freaknet Medialab  ]  
[ "+.  katolaz [at] freaknet.org --- katolaz [at] yahoo.it  ]
[   @)   http://kalos.mine.nu ---  Devuan GNU + Linux User  ]
[ @@)  http://maths.qmul.ac.uk/~vnicosia --  GPG: 0B5F062F  ] 
[ (@@@)  Twitter: @KatolaZ - skype: katolaz -- github: KatolaZ  ]


signature.asc
Description: Digital signature
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

[DNG] Fresh install of Ascii (was Re: Redhat CEO answers questions)

2017-11-01 Thread Lars Noodén 
On 11/01/2017 05:04 PM, Juergen Moebius wrote:
> it is possible to install a fresh "full" copy of ascii, not an update?
> I neverless updated my systems, sorry. A new installation is allways
> the better way for my.

Not yet.  rsyslog is still missing.  So that has to be carried forward
from Jessie.

/Lars
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Redhat CEO answers questions

2017-11-01 Thread Juergen Moebius 
Hi KatolaZ,

On Wed, Nov 01, 2017 at 15:32:53AM GMT 15:32 KatolaZ wrote:
> A modest proposal: if people have some time to spare for Devuan, it
> would be useful at this point to start testing all the possible
> upgrade paths to Devuan Ascii

it is possible to install a fresh "full" copy of ascii, not an update?
I neverless updated my systems, sorry. A new installation is allways
the better way for my.

Thanks,
Juergen from Germany

___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Redhat CEO answers questions

2017-11-01 Thread KatolaZ 
On Wed, Nov 01, 2017 at 10:12:53AM -0400, zap wrote:
> I like to think of systemd as the lazy man's solution to init.  I am not
> really a developer persay, but you guys seem to convey what I just said
> and what I am about to say,
> 
> systemd slogan, "*IF it isn't broken*... *Break IT!*"
> 
> Also another slogan for systemd: "*The**Donald Trump**of **Init*!"
> 
> and last but not least, "*The lazy Developer's way out!*"
> 
> but seriously, is laziness really the only reason so many distros
> switched to systemd?
> 
> If so... that is frankly in the words of the orange unstable man of hot
> air: "*SAD*!"
> 
> *):*

Sorry for interrupting, but I was wondering whether this discussion is
useful at all to Devuan. Please don't get me wrong: you are free to
continue, but really, what's the point? 

systemd is a reality, and making sad or smart jokes about it does not
make it more palatable, or less of a threat.

A modest proposal: if people have some time to spare for Devuan, it
would be useful at this point to start testing all the possible
upgrade paths to Devuan Ascii, e.g., a) from Debian Jessie, b) from
Devuan Jessie, c) from Debian Stretch, with as many different
configurations as possible, and report any issue they find to
http://bugs.devuan.org. Even upgrades of VMs would be informative.

TIA

KatolaZ

-- 
[ ~.,_  Enzo Nicosia aka KatolaZ - Devuan -- Freaknet Medialab  ]  
[ "+.  katolaz [at] freaknet.org --- katolaz [at] yahoo.it  ]
[   @)   http://kalos.mine.nu ---  Devuan GNU + Linux User  ]
[ @@)  http://maths.qmul.ac.uk/~vnicosia --  GPG: 0B5F062F  ] 
[ (@@@)  Twitter: @KatolaZ - skype: katolaz -- github: KatolaZ  ]


signature.asc
Description: Digital signature
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Runit for Devuan: was Debian testing drop redis

2017-11-01 Thread m712 


On October 28, 2017 11:22:49 AM GMT+03:00, Rick Moen  
wrote:
>(But sure, fixing the runit-init package
>would be a nice-to-have.)
I have a proposal for this. Basically, have an install script which does 
something like this (I'm not familiar with the Debian packaging scripts so 
assume it's sh):

# if upgrading, this doesn't run
if [ "$(pgrep runit -o)" != "1" ]; then
  mv -f /sbin/shutdown{,.old}
  mv -f /sbin/reboot{,.old}
fi

And then /sbin/reboot and /sbin/shutdown should point to a shell script like 
this:

if [ "$(pgrep runit -o)" != "1" ]; then
  exec "$0.old" $*
else
  if [ -e "$0.old" ]; then
rm "$0.old"
fi; fi

# ...do shutdown/reboot the runit way...

I don't think it's the best way of doing this, but I guess it'd work.
--- :^) --- :^) --- :^) --- :^) --- :^) --- :^) --- :^) --- :^) ---
https://nextchan.org - https://gitgud.io/m712/blazechan
I am awake between 7AM-12AM UTC, hit me up if something's wrong

signature.asc
Description: PGP signature
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Bluetooth headset on Devuan?

2017-11-01 Thread dev 
On 10/31/2017 12:42 PM, Mike Schmitz wrote:

> 
> Another project has picked up the ball and run with it, though. It works
> for me (SoundBot SB220)
> 
> https://github.com/Arkq/bluez-alsa
> 

Nice! I've got it almost working. I'm stuck on "Couldn't get BlueALSA
transport: No such device" Any thoughts?  From what I've googled so far,
solutions involve pulseaudio, or reference a pulseaudio conflict.  I
have some libpulse scattieness installed[0] for apulse support, but
maybe I cannot have both? Perhaps I should remove those?

So far, I've installed alsa and development libs[1] but had to add the
debian jessie repo[2] in order to get libfdk-aac-dev. Is there another
place for this?

I cloned the bluez-alsa git repo and built per git page[3]. Configured
~/.asoundrc for my bluetooth headset MAC[4]. The alsa-lib directory
installed to a location unknown to Devaun[5] so I sylinked[6] the new
libraries to a good location. I did 'echo /usr/lib/alsa-lib >
/etc/ld.so.conf.d/alsa-lib.conf' but this did not seem to help after
issuing ldconfig.

The bluealsa "server" seems to start ok and generates no errors[7] when
trying to play a sound via aplay, however aplay does not seem to know[8]
yet how to use the headset. I did have an issue with permissions on[9]
on /var/run/bluealsa but I think I fixed those[9]. Right now, aplay
cannot "get BlueALSA transport"[10]. Any thoughts?

Thank you!

[0]
i   apulse  - PulseAudio emulation for ALSA

i   libpulse-mainloop-glib0 - PulseAudio client libraries (glib
support)
i   libpulse0   - PulseAudio client libraries

i   libpulsedsp - PulseAudio OSS pre-load library

i   pulseaudio-utils- Command line tools for the
PulseAudio soun
i   vlc-plugin-pulse- transitional dummy package for vlc



[1]
aptitude install libalsaplayer-dev bluez bluez-tools libsbc-dev
libfdk-aac-dev alsa-tools alsaplayer-alsa libasound2-dev bluez-hcidump
checkinstall libusb-dev  libbluetooth-dev  libbluetooth-dev
libbluetooth3-dev
libglib2.0-dev

[2]
Add debian jessie rep for libfdk-aac-dev

libfdk-aac-dev required repo:
   deb http://httpredir.debian.org/debian/ jessie main contrib non-free

aptitude install libfdk-aac-dev

[3]
git clone https://github.com/Arkq/bluez-alsa.git
cd bluez-alsa; mkdir build; autoreconf --install; cd build; ../configure
--enable-aac --enable-debug
make
make install


[4]
$ cat ~/.asoundrc
defaults.bluealsa.interface "hci0"
defaults.bluealsa.device "02:FC:9F:F8:13:94"
defaults.bluealsa.profile "a2dp"

[5]
$ aplay -D bluealsa:HCI=hci0,DEV=02:FC:9F:F8:13:94,PROFILE=a2dp
/usr/share/sounds/purple/Windows\ Notify.wav
ALSA lib dlmisc.c:252:(snd1_dlobj_cache_get) Cannot open shared library
/usr/lib/x86_64-linux-gnu/alsa-lib/libasound_module_pcm_bluealsa.so
aplay: main:722: audio open error: No such device or address

[6]
# ldconfig -v | grep alsa

/usr/lib/alsa-lib:
libasound_module_ctl_bluealsa.so -> libasound_module_ctl_bluealsa.so
libasound_module_pcm_bluealsa.so -> libasound_module_pcm_bluealsa.so

# ln -s /usr/lib/alsa-lib/libasound_module_*
/usr/lib/x86_64-linux-gnu/alsa-lib/


[7]
$ bluealsa --disable-hfp
bluealsa: ../../src/ctl.c:489: Starting controller loop
bluealsa: ../../src/bluez.c:680: Registering endpoint: /A2DP/MPEG24/Source/1
bluealsa: ../../src/bluez.c:680: Registering endpoint: /A2DP/MPEG24/Sink/1
bluealsa: ../../src/bluez.c:680: Registering endpoint: /A2DP/SBC/Source/1
bluealsa: ../../src/bluez.c:680: Registering endpoint: /A2DP/SBC/Sink/1
bluealsa: ../../src/bluez.c:910: Registering profile: /HSP/Headset
bluealsa: ../../src/bluez.c:910: Registering profile: /HSP/AudioGateway
bluealsa: ../../src/main.c:225: Starting main dispatching loop
bluealsa: ../../src/ctl.c:550: New client accepted: 8
bluealsa: ../../src/ctl.c:571: +-+-
bluealsa: ../../src/ctl.c:571: +-+-
bluealsa: ../../src/ctl.c:521: Client closed connection: 8
bluealsa: ../../src/ctl.c:571: +-+-


[8]
$ aplay -D bluealsa:HCI=hci0,DEV=02:FC:9F:F8:13:94,PROFILE=a2dp
/usr/share/sounds/purple/Windows\ Notify.wav
../../../src/asound/../shared/ctl-client.c:102: Connecting to socket:
/var/run/bluealsa/hci0
ALSA lib ../../../src/asound/bluealsa-pcm.c:645:(_snd_pcm_bluealsa_open)
BlueALSA connection failed: No such file or directory
aplay: main:722: audio open error: No such file or directory


[9]
chown root:myuser /var/run/bluealsa
chmod g+w+s /var/run/bluealsa


[10]
$ aplay -D bluealsa:HCI=hci0,DEV=02:FC:9F:F8:13:94,PROFILE=a2dp
/usr/share/sounds/purple/Windows\ Notify.wav
../../../src/asound/../shared/ctl-client.c:102: Connecting to socket:
/var/run/bluealsa/hci0
../../../src/asound/../shared/ctl-client.c:213: Getting transport for
02:FC:9F:F8:13:94 type 1
ALSA lib ../../../src/asound/bluealsa-pcm.c:658:(_snd_pcm_bluealsa_open)
Couldn't get BlueALSA transport: No such device
aplay: main:722: audio open error: No such device


___
Dng mailing list

Re: [DNG] Redhat CEO answers questions

2017-11-01 Thread Hendrik Boom 
On Tue, Oct 31, 2017 at 08:24:34PM -0400, taii...@gmx.com wrote:
> There is always one reason or another for "a start job is running for -
> network interfaces/disks/etc)" which halts the entire boot process
> "faster", even without those it still is much slower than devuan.

Wow!  Systemd even halts faster!

-- hendrik
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Google abandons UEFI in Chromebooks

2017-11-01 Thread Hendrik Boom 
On Tue, Oct 31, 2017 at 01:56:06PM +0100, Martin Steigerwald wrote:
> 
> As my next music playback machine I may even use such a Pine64. As anything 
> from ThinkPad X240 and upwards appears to be "protected" by Intel Boot Guard 
> Verified Boot crap, instead of just offering the Measured Boot feature for 
> those who want it. Or I go with a ThinkPad X230 where it appears that Intel 
> ME 
> cleaner can do its work. May still be better the Pine64 appears to be a tad 
> bit limited especially by memory, although for music playback it would be 
> enough if expanded with a large MicroSD card. And it would have the advantage 
> that I would not have to mess with removing crap as it does not appear to 
> have 
> crap inside. And cheaper too.
> 
> Other alternative may be a Chromebook if I can rid it easily enough of Chrome 
> OS and install my distro of choice on it.

You might consider the Purism laptops, one of which has a detachable 
keyboard.  https://puri.sm/products/

I don't know if price/performance and the set of I/O ports are in 
your range, though.

-- hendrik

___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng