Bug#780733: fai-client: SSH login on installing client not possible as devpts is not mounted

2015-03-18 Thread Thomas Lange
 On Wed, 18 Mar 2015 17:07:27 +0100, John Paul Adrian Glaubitz 
 glaub...@physik.fu-berlin.de said:

 Logging into the system while it is being installed.
I cannot confirm this bug.

Using jessie inside the NFSROOT and fai 4.3.2 and dracut 040+1-1 and
doing a PXE boot of the install client I managed to log in via ssh
during installation.

root@xfcehost:~# mount|grep pts
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,mode=600,ptmxmode=000)
devpts on /target/dev/pts type devpts (rw,relatime,mode=600,ptmxmode=000)

Are you using dracut? And are you installing sysvinit-core into the
nfsroot (which is th default)?
-- 
regards Thomas


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#780707: unblock: icu/52.1-8

2015-03-18 Thread GCS
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Hi Release Team,

Please unblock the recent upload of icu, it contains the complete fix
for CVE-2014-7940 [1].
The debdiff is attached.

Thanks,
Laszlo/GCS

unblock icu/52.1-8

[1] http://bugs.debian.org/780503


icu_52.1-7.1_to_52.1-8.patch
Description: application/mbox


Bug#746224: Info received (Bug#746224: Info received ())

2015-03-18 Thread Cecil Ramirez
On Mar 15, 2015 7:15 PM, Debian Bug Tracking System ow...@bugs.debian.org
wrote:

 Thank you for the additional information you have supplied regarding
 this Bug report.

 This is an automatically generated reply to let you know your message
 has been received.

 Your message is being forwarded to the package maintainers and other
 interested parties for their attention; they will reply in due course.

 Your message has been sent to the package maintainer(s):
  Debian Libvirt Maintainers 
pkg-libvirt-maintain...@lists.alioth.debian.org

 If you wish to submit further information on this problem, please
 send it to 746...@bugs.debian.org.

 Please do not send mail to ow...@bugs.debian.org unless you wish
 to report a problem with the Bug-tracking system.

 --
 746224: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746224
 Debian Bug Tracking System
 Contact ow...@bugs.debian.org with problems


Bug#780705: udev: floating net device number on devices with ro rootfs

2015-03-18 Thread You-Sheng Yang
Typo in the proposed patch. Re-attach the correct one.

-- 
You-Sheng Yang (Vicamo)
From 6247d5017dcab60c1e1ae2b061fb6748765d1d1f Mon Sep 17 00:00:00 2001
From: You-Sheng Yang vic...@gmail.com
Date: Wed, 18 Mar 2015 11:33:32 +0800
Subject: [PATCH] Load tmp rules for persistent netdev names

On devices with read-only rootfs, e.g. mobile phones, nic device number
(wlanN) may increase every time disabled and re-enabled. To be more
precisely, this happens only on devices when disabling a nic removes the
corresponding driver.

/lib/udev/rules.d/75-persistent-net-generator.rules checks whether
NAME attribute has been assigned to wlanN device: if yes, skip all the
followed steps, or, call to /lib/udev/write_net_rules to generate a
persistent device name rule file. That persistent file should be created
under /etc/udev/rules.d and named 70-persistent-net.rules, so it
guarantees NAME attribute should be assigned if available before being
read. However, when rootfs was previously mounted as read-only, a file
/run/udev/tmp-ruiles--70-persistent-net.rules is created instead. This
temporary file is supposed to be moved back into /etc/udev/rules.d by
a systemd service udev-finish right after the system finishes start-up
chaos. Again, if rootfs is still mounted as read-only, this move will
certainly fail. One last important thing, /run/udev is _NOT_ included in
udev rules inclusion paths, so any rules written here will not be taken
into account when processing uevents.

So, when wlan0 is probed for the first time on a device with read-only
rootfs, udev creates /run/udev/tmp-ruiles--70-persistent-net.rules and
inserts one rule for it. When wlan0 is disabled and re-enabled, since
/run/udev/tmp-ruiles--70-persistent-net.rules is not taken into
account, its NAME attribute will not be set, and udev recognize it as a
new nic and tries to write another rule for it again. However, in this
time, wlan0 has been taken in the previously written temporary rules
file, so wlan1 is chosen instead, and an exactly the same matching
rule (except for NAME= part) is appended to
/run/udev/tmp-ruiles--70-persistent-net.rules. When the device is
again disabled and re-enabled, wlan2 will be assigned. And so on 

This patch add symlink from /lib/udev/rules.d/70-persistent-net.rules
to /run/udev/tmp-ruiles--70-persistent-net.rules.

Signed-off-by: You-Sheng Yang vic...@gmail.com
---
 debian/udev.links | 1 +
 1 file changed, 1 insertion(+)

diff --git a/debian/udev.links b/debian/udev.links
index 1a4356e..4e5ed91 100644
--- a/debian/udev.links
+++ b/debian/udev.links
@@ -2,3 +2,4 @@
 /lib/systemd/system/systemd-udevd.service /lib/systemd/system/udev.service
 /usr/share/man/man8/systemd-udevd.8 /usr/share/man/man8/udevd.8
 /bin/udevadm /sbin/udevadm
+/lib/udev/rules.d/70-persistent-net.rules 
/run/udev/tmp-ruiles--70-persistent-net.rules
-- 
2.1.4



<    1   2   3