Re: [Dng] straw poll, non-free firmware for installers

2015-06-07 Thread Didier Kryn

Le 06/06/2015 21:01, Alberto Zuin - liste a écrit :
When we have to install a distro on "special hardware" (an old dell 
server?) it's always an annoying thing to use a second pc to download 
the ethernet drivers, copy them to an USB key and so on. 


Not even an old Dell server :-) The stock Dell server. Probably all 
models.


Firmware in devices is the opposite of an old feature; it is a new, 
very sensible, industrial trend which is going to reach pretty much 
every piece of hardware. It is important for Devuan to devise a 
sustainable policy with regard to them.


Didier

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


[Dng] upgrade problem

2015-06-07 Thread fsmithred
I tried to do a dist-upgrade or full-upgrade on devuan today, and I'm
running into a problem:

 bsdutils : Breaks: bash-completion (< 1:2.1-4.1~) but 1:2.1-4 is installed.
 util-linux : Breaks: bash-completion (< 1:2.1-4.1~) but 1:2.1-4 is installed.

But the newer version of bash-completion is not available, not even in
debian sid. Is this a typo in the control file, or is there a 1:2.1-4.1~
coming soon in devuan?

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


Re: [Dng] upgrade problem

2015-06-07 Thread Irrwahn
fsmithred wrote on 07.06.2015 15:13:
> I tried to do a dist-upgrade or full-upgrade on devuan today, and I'm
> running into a problem:
> 
>  bsdutils : Breaks: bash-completion (< 1:2.1-4.1~) but 1:2.1-4 is installed.
>  util-linux : Breaks: bash-completion (< 1:2.1-4.1~) but 1:2.1-4 is installed.
> 
> But the newer version of bash-completion is not available, not even in
> debian sid. 

bash-completion 1:2.1-4.1 is available in Debian stretch and sid, 
and thus in Devuan ascii and ceres, too.

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


Re: [Dng] Building Postfix 3.0.1

2015-06-07 Thread Anto



On 06/06/15 14:59, Anto wrote:



On 06/06/15 12:37, Anto wrote:

Hello Everybody,

I have been trying to adapt the Debian build script of Postfix 2.11.3 
for Postfix 3.0.1, but I still cannot have it compiled so far.


Is there any of you manage to do that? If so, would you care to share 
the build script? Or do you have any information related to this?


Thanks in advance for your help.

Cheers,

Anto



I just found out that somebody has already done this for Ubuntu, 
https://launchpad.net/~mamarley/+archive/ubuntu/updates/+sourcepub/4943122/+listing-archive-extra. 
I will play around with tonight.




Hello Everybody,

I am sorry for the noise that I make here.

I have managed to build postfix 3.0.1 using the source from 
ftp://ftp.porcupine.org/mirrors/postfix-release/official/postfix-3.0.1.tar.gz, 
and using the Debian build script based on the one from 
https://launchpad.net/~mamarley/+archive/ubuntu/updates/+files/postfix_3.0.1-0ubuntu0%7Eppa0%7Evivid.tar.gz.


However, there are some warning from dpkg-shlibdeps as below which I do 
not understand the reasons.


.

.
LD_LIBRARY_PATH=$(pwd)/lib:${LD_LIBRARY_PATH} dh_shlibdeps -a
dpkg-shlibdeps: warning: can't extract name and version from library 
name 'libpostfix-util.so'
dpkg-shlibdeps: warning: can't extract name and version from library 
name 'libpostfix-util.so'
dpkg-shlibdeps: warning: can't extract name and version from library 
name 'libpostfix-util.so'
dpkg-shlibdeps: warning: can't extract name and version from library 
name 'libpostfix-global.so'
dpkg-shlibdeps: warning: can't extract name and version from library 
name 'libpostfix-global.so'
dpkg-shlibdeps: warning: can't extract name and version from library 
name 'libpostfix-global.so'
dpkg-shlibdeps: warning: can't extract name and version from library 
name 'libpostfix-master.so'
dpkg-shlibdeps: warning: can't extract name and version from library 
name 'libpostfix-master.so'
dpkg-shlibdeps: warning: can't extract name and version from library 
name 'libpostfix-master.so'

.

.

The same warnings are also shown on Ubuntu PPA buildlog file: 
https://launchpadlibrarian.net/197953325/buildlog_ubuntu-vivid-amd64.postfix_3.0.0-0ubuntu0~ppa0~vivid_UPLOADING.txt.gz.


Could anybody please explain the reason why that warnings come up and 
the impact of that?


Thanks in advance for your help.

Cheers,

Anto

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


Re: [Dng] upgrade problem

2015-06-07 Thread David Hare


root@exe-jessv:/# apt install bash-completion

WARNING: apt does not have a stable CLI interface yet. Use with caution 
in scripts.


Reading package lists...
Building dependency tree...
Reading state information...
The following packages were automatically installed and are no longer 
required:

  libatkmm-1.6-1 libboost-filesystem1.55.0 libboost-serialization1.55.0
  libcairomm-1.0-1 libglibmm-2.4-1c2a libgtkmm-2.4-1c2a libpangomm-1.4-1
  librlog5 libupower-glib3 libuuid-perl xfce4-power-manager-data
Use 'apt-get autoremove' to remove them.
The following extra packages will be installed:
  makedev
The following packages will be REMOVED:
  archivemount bsdmainutils bsdutils cryptsetup cryptsetup-bin curlftpfs
  dmeventd dmsetup e2fsprogs eject encfs fuse fuseiso gparted grub-common
  grub-pc grub-pc-bin grub2-common gvfs gvfs-backends gvfs-daemons
  initramfs-tools libcryptsetup4 libdevmapper-event1.02.1 
libdevmapper1.02.1

  liblvm2cmd2.02 libparted-fs-resize0 libparted2 linux-base
  linux-image-3.16.0-4-amd64 linux-image-amd64 live-boot
  live-boot-initramfs-tools live-tools man-db nfs-common ntfs-3g parted
  refracta2usb refractainstaller-base refractainstaller-gui
  refractasnapshot-base refractasnapshot-gui sshfs testdisk udev udisks2
  upower util-linux virtualbox-guest-x11 x11-apps xfce4-power-manager xorg
  xserver-xorg xserver-xorg-core xserver-xorg-input-all
  xserver-xorg-input-evdev xserver-xorg-input-mouse
  xserver-xorg-input-synaptics xserver-xorg-input-vmmouse
  xserver-xorg-video-all xserver-xorg-video-ati xserver-xorg-video-cirrus
  xserver-xorg-video-fbdev xserver-xorg-video-intel 
xserver-xorg-video-mach64

  xserver-xorg-video-mga xserver-xorg-video-modesetting
  xserver-xorg-video-neomagic xserver-xorg-video-nouveau
  xserver-xorg-video-openchrome xserver-xorg-video-r128
  xserver-xorg-video-radeon xserver-xorg-video-savage
  xserver-xorg-video-siliconmotion xserver-xorg-video-sisusb
  xserver-xorg-video-tdfx xserver-xorg-video-trident 
xserver-xorg-video-vesa

  xserver-xorg-video-vmware
The following NEW packages will be installed:
  bash-completion makedev
WARNING: The following essential packages will be removed.
This should NOT be done unless you know exactly what you are doing!
  bsdutils e2fsprogs util-linux (due to e2fsprogs)
0 upgraded, 2 newly installed, 80 to remove and 0 not upgraded.
Need to get 225 kB of archives.
After this operation, 246 MB disk space will be freed.
You are about to do something potentially harmful.
To continue type in the phrase 'Yes, do as I say!'
 ?]
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


Re: [Dng] upgrade problem

2015-06-07 Thread fsmithred
On 06/07/2015 08:31 PM, David Hare wrote:
> 
> root@exe-jessv:/# apt install bash-completion
> 
> WARNING: apt does not have a stable CLI interface yet. Use with caution in
> scripts.
> 
> Reading package lists...
> Building dependency tree...
> Reading state information...
> The following packages were automatically installed and are no longer
> required:
>   libatkmm-1.6-1 libboost-filesystem1.55.0 libboost-serialization1.55.0
>   libcairomm-1.0-1 libglibmm-2.4-1c2a libgtkmm-2.4-1c2a libpangomm-1.4-1
>   librlog5 libupower-glib3 libuuid-perl xfce4-power-manager-data
> Use 'apt-get autoremove' to remove them.
> The following extra packages will be installed:
>   makedev
> The following packages will be REMOVED:
>   archivemount bsdmainutils bsdutils cryptsetup cryptsetup-bin curlftpfs
>   dmeventd dmsetup e2fsprogs eject encfs fuse fuseiso gparted grub-common
>   grub-pc grub-pc-bin grub2-common gvfs gvfs-backends gvfs-daemons
>   initramfs-tools libcryptsetup4 libdevmapper-event1.02.1 libdevmapper1.02.1
>   liblvm2cmd2.02 libparted-fs-resize0 libparted2 linux-base
>   linux-image-3.16.0-4-amd64 linux-image-amd64 live-boot
>   live-boot-initramfs-tools live-tools man-db nfs-common ntfs-3g parted
>   refracta2usb refractainstaller-base refractainstaller-gui
>   refractasnapshot-base refractasnapshot-gui sshfs testdisk udev udisks2
>   upower util-linux virtualbox-guest-x11 x11-apps xfce4-power-manager xorg
>   xserver-xorg xserver-xorg-core xserver-xorg-input-all
>   xserver-xorg-input-evdev xserver-xorg-input-mouse
>   xserver-xorg-input-synaptics xserver-xorg-input-vmmouse
>   xserver-xorg-video-all xserver-xorg-video-ati xserver-xorg-video-cirrus
>   xserver-xorg-video-fbdev xserver-xorg-video-intel xserver-xorg-video-mach64
>   xserver-xorg-video-mga xserver-xorg-video-modesetting
>   xserver-xorg-video-neomagic xserver-xorg-video-nouveau
>   xserver-xorg-video-openchrome xserver-xorg-video-r128
>   xserver-xorg-video-radeon xserver-xorg-video-savage
>   xserver-xorg-video-siliconmotion xserver-xorg-video-sisusb
>   xserver-xorg-video-tdfx xserver-xorg-video-trident xserver-xorg-video-vesa
>   xserver-xorg-video-vmware
> The following NEW packages will be installed:
>   bash-completion makedev
> WARNING: The following essential packages will be removed.
> This should NOT be done unless you know exactly what you are doing!
>   bsdutils e2fsprogs util-linux (due to e2fsprogs)
> 0 upgraded, 2 newly installed, 80 to remove and 0 not upgraded.
> Need to get 225 kB of archives.
> After this operation, 246 MB disk space will be freed.
> You are about to do something potentially harmful.
> To continue type in the phrase 'Yes, do as I say!'
>  ?]
> ___


Wow. You got my all-time favorite warning message. But I didn't go there
with this.

I upgraded and let bash-completion go, lost completion on package names,
and then I installed 1:2.1-4.1 from ascii on Irrwahn's recommendation, and
it seems to be working fine.

fsr

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


[Dng] libudev-compat update

2015-06-07 Thread Jude Nelson
Hey everyone,

I've just pushed my first stab at libudev-compat to the vdev repository.
It took a while to work out how to remove the need for udev to send libudev
clients device events, but I think I've figured out something that works.

Instead of sending events via a netlink multicast group, the device manager
is expected to atomically put a serialized struct udev_device message into
a set of process-specific directories (i.e. as strings that can be parsed
by udev_device_new_from_nulstr()).  Libudev-compat clients create these
directories when they create struct udev_monitor instances, so the device
manager need only write the event file somewhere privately, hard-link it
into each such directory (ensuring "atomic send" semantics), and then
unlink it.  This means that pretty much any program you want can trivially
send device messages to other programs as long as it can write to their
directories, and inspect or even re-order pending messages.

Instead of a netlink socket, a struct udev_monitor in libudev-compat
contains an epoll handle, an inotify handle, and a socket pair.  The epoll
handle is used to indicate the readiness of the inotify handle, the "sink"
end of the socket pair, or both, and is the pollable handle returned by
udev_monitor_get_fd().  Libudev-compat ensures that a struct udev_monitor's
handle will poll as ready-to-read if and only if there is at least one
unprocessed device event.

The inotify handle is set up to watch the process-specific directory for
IN_CREATE events, in a one-shot fashion (the directory itself is created as
part of udev_monitor_new()).  When a client program receives a device event
with udev_monitor_receive_device(), libudev-compat resets the one-shot
inotify handle, scans the directory, and sends as many files' contents as
it can as messages to the "source" end of the monitor's socket pair.
Libudev-compat filters unwanted devices on the socket pair using a BPF
program in the same way that libudev does for netlinks sockets (i.e. the
logic is the same in both libraries).  Devices events are sent in
lexicographic order by name, and are consumed from the "sink" end of the
socket pair.

Because we're not using netlink anymore, we have to preserve multicast
semantics across fork() as well--that is, if the process fork()'s and the
device manager subsequently sends a device event, both the parent and child
must receive it.  To do so, libudev-compat maintains a global table of all
existing monitors, which it does as part of udev_monitor_new() and
udev_monitor_unref().  Upon fork(), as part of a pthread_atfork() handler,
the libudev-compat child creates a new events directory, and re-targets all
of its monitors' inotify handles to watch it instead.  It also closes and
re-opens each monitor's socket pairs, so it will not accidentally consume
its parent's buffered device events.  This ensures that the next time the
child calls udev_monitor_receive_device(), it will look in its own
directory, and it will receive and consume events independently of its
parent, as desired.

I have lightly tested libudev-compat's ability to do all of the above with
a helper program for vdev (vdevd/helpers/LINUX/event-put.c), and with a
test program that can be compiled with the "test" target in libudev-compat/
(i.e. "cd libudev-compat && make test").  It appears to work so far, but I
invite the community to review the code and try it themselves.

What I need to do next is create vdev scripts that will cause it to send
off events to libudev-compat clients, using event-put.  To do so, I'll also
need to add helper scripts to generate and maintain /run/udev/, since the
struct udev_device's that libudev-compat clients will expect to receive
must include all of the metadata udev would generate for them.

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