Be Seen Above Your Competition

2015-03-12 Thread Roger Henry




* Hello*, zeni.net Team,

* Hope you are doing well, **We can help your business/organization to earn
the identity it needs on the internet as it is the best platform for
marketing today. Our services web development in Web Designing includes*

1.   Android Development

2.   Asp.Net Development

3.   Content Management System

4.   Copy Writing Services

5.   Cross Browser Compatibility

6.   Custom E-Commerce Websites

7.   Custom Website Design

8.   Custom Websites Development

9.   Custom Word Press  design and theme development

10.Data Entry Services

11.E-Commerce Development

12.E-Commerce Solutions

13.Facebook Apps Development

14.Graphics Design

15.Iphone and Ipads Apps Development

16.Joomla Development

17.Landing Page Design

18.Magento Development

19.Mobile Development

20.Multimedia and Graphic

21.Newsletter Template

22.Open source Customization

23.Photo slideshow and Galleries

24.PHP Development

25.Search Engine Optimization

26.Social Media Presence

27.Social Network Development

28.Table Less Coding

29.Web Design and Development

30.Wordpress Development

31.Wordpress Blog Customization.

*Sounds interesting? Feel free to email us or alternatively you can provide
me with your phone number and the best time to call you.*

Thanks  Regards,
Roger Henry
Designing  Development Consultant

Note: If you are not interested, please email with the subject line
Remove and I will happy to update my data base

   ---usab---


Bug#780175: linux-image-3.16.0-4-686-pae: flags mismatch irq 6 00000080 (sata_sil) vs 00000000 (floppy)

2015-03-12 Thread Ben Hutchings
Control: tag -1 moreinfo

On Tue, 2015-03-10 at 00:09 -0600, Dan Brown wrote:
 Package: src:linux
 Version: 3.16.7-ckt7-1
 Severity: important
 
 Dear Maintainer,
 
 
 I have an old Dell (Dimension XPS B766r) which was previously running
 Debian 6 on it serving as a fileserver with 8 sata HDDs, 2 IDE HDDs,
 and an SD to IDE adapter running the OS. It has two PCI RAID cards
 running in jBOD to facilitate the numerous drives.  The MegaRAID PCI
 card is detected and it's drives all show up. The Silicon Image SiI
 3114 RAID card is detected but has a conflict with the IRQ for the
 floppy drive (which is disabled in BIOS).
[...]

Is the floppy _drive_ disabled (drive type set to 'none'), or the floppy
_controller_ (in an 'on-board devices' menu)?  In the latter case

In any case, the BIOS performs initial assignment of IRQs, so this
conflict is probably a BIOS bug.  Do any of the following workarounds
work for you?

- Disable/enable the floppy controller in the BIOS (i.e. invert the
  current setting)
- Disable assignment of IRQ#6 by the BIOS, if possible (probably an
  option in a menu labelled 'Plug and Play' or similar)
- Add kernel parameter 'pci=usepirqmask' (but the bug this works around
  seems to be mostly found in laptops)
- Blacklist the floppy driver:
  echo 'blacklist floppy'  /etc/modprobe.d/floppy-blacklist.conf

Ben.

-- 
Ben Hutchings
Any smoothly functioning technology is indistinguishable from a rigged demo.


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


Bug#780261: fsck scan of crypto-root on EVERY startup

2015-03-12 Thread Eduard Bloch
Hallo,
* Ben Hutchings [Wed, Mar 11 2015, 05:01:58PM]:
 Control: tag -1 moreinfo
 
 On Wed, 2015-03-11 at 11:40 +0100, Eduard Bloch wrote:
  Package: initramfs-tools
  Version: 0.119
  Severity: important
  
  Just what the topic says. I have encrypted root and plymouth and the
  bios clock runs in local time. And on every boot, fsck scans the
  rootfs in forced mode which takes a while.
  
  This started happening only after dist-upgrading today, and I also
  installed plymouth for other reasons.
 
 From the NEWS file:
 
   * If the RTC (real time clock) is set to local time and the local time is
 ahead of UTC, e2fsck will print a warning during boot about the time
 changing backward (bug #767040).  You can disable this by putting the
 following lines in /etc/e2fsck.conf:
 [options]
 broken_system_clock=1
 
 I don't know why you would see a forced fsck rather than only a warning.
 But does that configuration change work for you?

Correct, I don't understand this either. I entered the debug shell
(break=mount), configured the encrypted root, run 
e2fsck /dev/mapper/xroot and there was no warning, it just returned.
date displayed the correct BIOS date with incorrect timezone (UTC,
not UTC+1).

Setting the mentioned option in e2fsck.conf does help.

Regards,
Eduard.

-- 
Alfie Von sid wirds nie ein netinst geben.
hygl Alfie: darf ich dich damit zitieren, wenn sid stable ist?


signature.asc
Description: Digital signature


Bug#678696: Event based block device handling (fixes USB and nested devices problem)

2015-03-12 Thread Ben Hutchings
On Tue, 2015-03-10 at 12:47 +0100, Goswin von Brederlow wrote:
 On Wed, Mar 04, 2015 at 09:30:24PM +, Ben Hutchings wrote:
  Thanks for your work on this bug.  I ended up with a somewhat different
  implementation as I don't think it's necessary to duplicate the
  information that udev provides, and as we may now need to mount more
  than one filesystem.  But I should have credited you in the changelog
  for prototyping this, and I forgot to do so.
  
  Ben.
 
 The idea with the udev rule was to wait up to ROOTDELAY seconds
 without a new device apearing before giving up. Now you wait ROOTDELAY
 seconds in total, which then can depend on the number of devices.

It's now max(rootdelay, 30) because the rootdelay kernel parameter
wasn't meant for this purpose at all.

 Add  new disk and you have to increase the ROOTDELAY.

I hope not!

 Also it was ment so that block scripts could specifically target the
 new devices instead of having to scan all devices every time. For
 example say you have a crypt device and you forgot the password. Now I
 think you will be asked 30 times for the password before the initramfs
 gives up.

True, but so far as I could see you didn't send scripts that made use of
that.  We could still implement that later, I think.

And now that we potentially have to mount /usr (and possibly other
filesystems), not just root and swap, lvm2's script needed to be told
which device we're looking for, not which devices appeared.

Ben.

-- 
Ben Hutchings
Any smoothly functioning technology is indistinguishable from a rigged demo.


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


Bug#776409: initramfs-tools: Confirmed, same for me with initramfs-tolls 0.119

2015-03-12 Thread David Santoso
Package: initramfs-tools
Version: 0.119
Followup-For: Bug #776409

Dear Maintainer,


* What led up to the situation?
I have a system using cryptsetup (LUKS) and each of these are on different
volume:
/ - using password, entered at boot

/var - using keyfile stored on /etc/, specified on crypttab
/tmp - using keyfile stored on /etc/, specified on crypttab
/usr - using keyfile stored on /etc/, specified on crypttab
swap - using keyfile stored on /etc/, specified on crypttab


This afternoon after upgrading these packages (from /var/log/aptitude):
[UPGRADE] console-setup:amd64 1.116 - 1.118
[UPGRADE] console-setup-linux:amd64 1.116 - 1.118
[UPGRADE] dmeventd:amd64 2:1.02.90-2 - 2:1.02.90-2.1
[UPGRADE] dmsetup:amd64 2:1.02.90-2 - 2:1.02.90-2.1
[UPGRADE] emacs24:amd64 24.4+1-4.1 - 24.4+1-5
[UPGRADE] emacs24-bin-common:amd64 24.4+1-4.1 - 24.4+1-5
[UPGRADE] emacs24-common:amd64 24.4+1-4.1 - 24.4+1-5
[UPGRADE] initramfs-tools:amd64 0.116 - 0.119
[UPGRADE] keyboard-configuration:amd64 1.116 - 1.118
[UPGRADE] libdevmapper-dev:amd64 2:1.02.90-2 - 2:1.02.90-2.1
[UPGRADE] libdevmapper-event1.02.1:amd64 2:1.02.90-2 - 2:1.02.90-2.1
[UPGRADE] libdevmapper1.02.1:amd64 2:1.02.90-2 - 2:1.02.90-2.1
[UPGRADE] libjpeg-turbo-progs:amd64 1:1.3.1-11 - 1:1.3.1-11+deb7u1
[UPGRADE] libjpeg62-turbo:amd64 1:1.3.1-11 - 1:1.3.1-11+deb7u1
[UPGRADE] liblvm2cmd2.02:amd64 2.02.111-2 - 2.02.111-2.1
[UPGRADE] libturbojpeg1:amd64 1:1.3.1-11 - 1:1.3.1-11+deb7u1
[UPGRADE] lvm2:amd64 2.02.111-2 - 2.02.111-2.1
I rebooted the sysem and I got the message:
Gave up waiting for /usr device
and thrown into initramfs shell.

* What exactly did you do (or not do) that was effective (or ineffective)?
Perhaps [UPGRADE] initramfs-tools:amd64 0.116 - 0.119 and having
split /usr and encrypted system.

* What was the outcome of this action?
got the message:
Gave up waiting for /usr device
and thrown into initramfs shell.

* What outcome did you expect instead?
System boots normally like always.



-- Package-specific info:
-- initramfs sizes
-rw-r--r-- 1 root root 18M Mar 11 17:01 /boot/initrd.img-3.16.0-4-amd64
-- /proc/cmdline
BOOT_IMAGE=/vmlinuz-3.16.0-4-amd64 
root=UUID=278f734e-6e7c-4de8-bcfd-6f76169cac83 ro quiet

-- /proc/filesystems
btrfs
ext3
ext2
ext4
fuseblk
vfat

-- lsmod
Module  Size  Used by
ccm17577  2 
nfnetlink_queue17604  0 
bluetooth 374429  0 
6lowpan_iphc   16588  1 bluetooth
binfmt_misc16949  1 
ipt_MASQUERADE 12594  8 
iptable_nat12646  1 
nf_nat_ipv412912  1 iptable_nat
ipt_REJECT 12465  4 
iptable_mangle 12536  1 
iptable_raw12524  1 
nf_conntrack_ipv4  18448  143 
nf_defrag_ipv4 12483  1 nf_conntrack_ipv4
ipt_ULOG   12819  0 
nf_nat_tftp12422  0 
xt_recent  17246  2 
nf_nat_snmp_basic  16904  0 
nf_nat_sip 17053  0 
nf_nat_pptp12562  0 
ip6table_nat   12649  0 
nf_nat_proto_gre   12517  1 nf_nat_pptp
nf_nat_ipv612920  1 ip6table_nat
nf_nat_irc 12454  0 
nf_nat_h32316935  0 
nf_nat_ftp 12460  0 
nf_nat_amanda  12424  0 
nf_nat 18241  13 
nf_nat_ftp,nf_nat_irc,nf_nat_sip,nf_nat_amanda,ipt_MASQUERADE,nf_nat_proto_gre,nf_nat_h323,nf_nat_ipv4,nf_nat_ipv6,nf_nat_pptp,nf_nat_tftp,ip6table_nat,iptable_nat
xt_comment 12427  79 
ip6t_REJECT12468  4 
xt_addrtype12557  5 
xt_mark12453  2 
ip6table_mangle12540  1 
nf_conntrack_snmp  12443  3 nf_nat_snmp_basic
xt_tcpudp  12527  98 
xt_CT  12842  36 
ip6table_raw   12528  1 
xt_multiport   12518  8 
nf_conntrack_ipv6  13605  47 
nf_defrag_ipv6 33358  1 nf_conntrack_ipv6
xt_conntrack   12681  152 
xt_NFLOG   12462  0 
nfnetlink_log  17201  1 xt_NFLOG
xt_LOG 17171  24 
nf_conntrack_tftp  12433  5 nf_nat_tftp
nf_conntrack_sip   26053  5 nf_nat_sip
nf_conntrack_sane  12428  4 
nf_conntrack_proto_udplite12931  0 
nf_conntrack_proto_sctp17268  0 
nf_conntrack_pptp  12619  3 nf_nat_pptp
nf_conntrack_proto_gre13024  1 nf_conntrack_pptp
nf_conntrack_netlink35433  0 
nfnetlink  12989  3 
nfnetlink_log,nf_conntrack_netlink,nfnetlink_queue
nf_conntrack_netbios_ns12445  2 
nf_conntrack_broadcast12365  2 nf_conntrack_netbios_ns,nf_conntrack_snmp
nf_conntrack_irc   12427  3 nf_nat_irc
nf_conntrack_h323  58618  9 nf_nat_h323
nf_conntrack_ftp   16783  5 nf_nat_ftp
ts_kmp 12535  5 
nf_conntrack_amanda12437  5 nf_nat_amanda
nf_conntrack   87424  33 

Re: Replacing aufs with overlayfs

2015-03-12 Thread intrigeri
Hi Ben,

[dropping -live@ from the Cc list, as this is not specific to Live
systems, and affects e.g. some setups based on Linux containers.]

Ben Hutchings wrote (09 Dec 2014 19:55:10 GMT) :
 Please try the Linux 3.18 packages from experimental (they're not there
 yet, but should be soon) and check that overlayfs does what you need.

FYI, at the upstream AppArmor IRC meeting a few days ago, I've learnt
that overlayfs and AppArmor don't play well together yet.

* Some IRC log excerpts that provide more detail:
  https://labs.riseup.net/code/issues/9045

* The AppArmor bug that tracks this issue:
  https://bugs.launchpad.net/apparmor/+bug/1408106

Cheers,
-- 
intrigeri


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/85a8zi1cxa@boum.org



Bug#678696: Event based block device handling (fixes USB and nested devices problem)

2015-03-12 Thread Goswin von Brederlow
On Wed, Mar 11, 2015 at 06:09:50PM +, Ben Hutchings wrote:
 On Tue, 2015-03-10 at 12:47 +0100, Goswin von Brederlow wrote:
  On Wed, Mar 04, 2015 at 09:30:24PM +, Ben Hutchings wrote:
   Thanks for your work on this bug.  I ended up with a somewhat different
   implementation as I don't think it's necessary to duplicate the
   information that udev provides, and as we may now need to mount more
   than one filesystem.  But I should have credited you in the changelog
   for prototyping this, and I forgot to do so.
   
   Ben.
  
  The idea with the udev rule was to wait up to ROOTDELAY seconds
  without a new device apearing before giving up. Now you wait ROOTDELAY
  seconds in total, which then can depend on the number of devices.
 
 It's now max(rootdelay, 30) because the rootdelay kernel parameter
 wasn't meant for this purpose at all.
 
  Add  new disk and you have to increase the ROOTDELAY.
 
 I hope not!

On one system the PSU isn't big enough to spin up all disks at once.
So the SCSI controler is set to not start them on power on. Instead
they come up sequentially. So one disk takes 5s, 2 disks 10s, 3 disks
15s, ... accordingly you have to set the delay. Add another disk and
the total time goes up.
 
  Also it was ment so that block scripts could specifically target the
  new devices instead of having to scan all devices every time. For
  example say you have a crypt device and you forgot the password. Now I
  think you will be asked 30 times for the password before the initramfs
  gives up.
 
 True, but so far as I could see you didn't send scripts that made use of
 that.  We could still implement that later, I think.

 And now that we potentially have to mount /usr (and possibly other
 filesystems), not just root and swap, lvm2's script needed to be told
 which device we're looking for, not which devices appeared.
 
 Ben.

That isn't realy new. Debian already had root and swap. Adding a third
doesn't realy change anything. LVM should already have known what
devices to activate for root and swap.

The problem I see there is detecting what devices to bring up. The
/usr filesystem might be in a ZPOOL that uses a crypt device on a LVM
logical volume on a raid. Or any other complex nesting. Could be any
number of devices that are needed for /usr to become available. Again
nothing new for /usr, / and swap already have that problem.

Note: LVM has persistent metadata that tell it wether to bring up a
device or not. So I'm not sure it makes much sense to guess what
devices are needed and limiting lvm to only start those. The metadata
already has this functionality and is more reliable than guessing what
devices may be needed.

MfG
Goswin


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20150312140917.GA20402@frosties



Bug#780352: initramfs-tools: Can't force fsck on remote systems

2015-03-12 Thread jpw
Package: initramfs-tools
Version: 0.119
Severity: important

Dear Maintainer,

A basic change in function for fsck at boot time has resulted following upgrade
of this package from 0.116 to 0.119.

Following deprecation of touch /forcefsck earlier this past year for forcing 
fsck
at next reboot I started using a line in  rc.local (tune2fs -c 0 /dev/sda1) to 
set
maximum mount count so that in-depth file system checks would never occur 
unless I 
specified. I then issued tune2fs -c 1 /dev/sda1 from a root prompt on the 
remote
systems to force the in-depth fsck on next reboot.

The remote systems used to execute an in-depth fsck on the boot partition at 
next reboot when I followed this procedure. This function no longer works.

So far, the only solution I have found would seem to be to make temporary 
changes
in grub configuration on remote systems (via script or via manual editing) when 
I
want to force a file system check at boot time. This seems inadvisable to me.

Is there another solution, or can this functionality be restored by further
changes to initramfs-tools?

-- Package-specific info:
-- initramfs sizes
-rw-r--r-- 1 root root 15M Mar 11 10:03 /boot/initrd.img-3.16.0-4-amd64
-- /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-3.16.0-4-amd64 
root=UUID=d6c0ac59-8f7c-438a-a87d-9f4f79ea58a1 ro initrd=/install/initrd.gz 
quiet

-- resume
RESUME=UUID=fad10f9d-8fa7-4f12-ab5c-a4d1e7a1a764
-- /proc/filesystems
ext3
ext2
ext4
fuseblk

-- lsmod
Module  Size  Used by
tun26385  0 
binfmt_misc16949  1 
asix   35194  0 
usbnet 30844  1 asix
libphy 32268  1 asix
mii12675  2 asix,usbnet
udl23117  0 
drm_usb12469  1 udl
udlfb  22180  0 
nfsd  263032  2 
auth_rpcgss51211  1 nfsd
oid_registry   12419  1 auth_rpcgss
nfs_acl12511  1 nfsd
nfs   188136  0 
lockd  83389  2 nfs,nfsd
fscache45542  1 nfs
sunrpc237402  6 nfs,nfsd,auth_rpcgss,lockd,nfs_acl
joydev 17063  0 
ip6t_REJECT12468  1 
snd_usb_audio 135354  3 
snd_usbmidi_lib23388  1 snd_usb_audio
snd_rawmidi26806  1 snd_usbmidi_lib
snd_seq_device 13132  1 snd_rawmidi
x86_pkg_temp_thermal12951  0 
intel_powerclamp   17159  0 
arc4   12536  2 
iwldvm135156  0 
mac80211  474218  1 iwldvm
intel_rapl 17356  0 
coretemp   12820  0 
kvm_intel 139116  0 
kvm   388635  1 kvm_intel
snd_hda_codec_hdmi 45118  1 
xt_hl  12449  6 
iTCO_wdt   12831  0 
i915  837133  2 
snd_hda_codec_conexant17841  1 
snd_hda_codec_generic63107  1 snd_hda_codec_conexant
ip6t_rt12456  3 
iTCO_vendor_support12649  1 iTCO_wdt
evdev  17445  33 
nf_conntrack_ipv6  13605  7 
iwlwifi96547  1 iwldvm
snd_hda_intel  26327  4 
crc32_pclmul   12915  0 
cfg80211  405538  3 iwlwifi,mac80211,iwldvm
psmouse98616  0 
drm_kms_helper 49210  2 udl,i915
nf_defrag_ipv6 33358  1 nf_conntrack_ipv6
snd_hda_controller 26727  1 snd_hda_intel
serio_raw  12849  0 
ghash_clmulni_intel12978  0 
mei_me 17941  0 
thinkpad_acpi  69119  3 
drm   249955  6 udl,i915,drm_usb,drm_kms_helper
snd_hda_codec 104463  5 
snd_hda_codec_hdmi,snd_hda_codec_conexant,snd_hda_codec_generic,snd_hda_intel,snd_hda_controller
ipt_REJECT 12465  1 
nvram  13034  1 thinkpad_acpi
lpc_ich20768  0 
pcspkr 12595  0 
mfd_core   12601  1 lpc_ich
snd_hwdep  13148  2 snd_usb_audio,snd_hda_codec
snd_pcm88662  5 
snd_usb_audio,snd_hda_codec_hdmi,snd_hda_codec,snd_hda_intel,snd_hda_controller
mei74977  1 mei_me
cryptd 14516  1 ghash_clmulni_intel
snd_timer  26614  1 snd_pcm
xt_LOG 17171  10 
i2c_algo_bit   12751  1 i915
i2c_i801   16965  0 
i2c_core   46012  5 drm,i915,i2c_i801,drm_kms_helper,i2c_algo_bit
tpm_tis17182  0 
wmi17339  0 
snd65244  31 
snd_usb_audio,snd_hwdep,snd_timer,snd_hda_codec_hdmi,snd_hda_codec_conexant,snd_pcm,snd_rawmidi,snd_hda_codec_generic,snd_usbmidi_lib,snd_hda_codec,snd_hda_intel,thinkpad_acpi,snd_seq_device
shpchp 31121  0 
tpm31511  1 tpm_tis
battery13356  0 
ac 12715  0 
video  18096  1 i915
soundcore  13026  2 snd,snd_hda_codec
rfkill 18867  2 cfg80211,thinkpad_acpi

Bug#780295: net bridge devices no longer brought up correctly

2015-03-12 Thread Reinhard Karcher
It's a problem with kmod, module-init-tools and libkmod2 version 20-1.
Replacing these packages with version 18-3 removes that problem.

Reinhard


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/9770441.0vmQAbIFvV@apollon



Processed: reassign 780295 to kmod, forcibly merging 780255 780295

2015-03-12 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

 reassign 780295 kmod
Bug #780295 [src:linux] linux-image-3.19.0-trunk-amd64: net bridge devices no 
longer brought up correctly
Bug reassigned from package 'src:linux' to 'kmod'.
No longer marked as found in versions linux/3.19.1-1~exp1.
Ignoring request to alter fixed versions of bug #780295 to the same values 
previously set
 forcemerge 780255 780295
Bug #780255 [kmod] openconnect: kmod update from version 18 to 20 breaks 
openconnect
Bug #780256 [kmod] Stopped auto-loading tun module
Bug #780295 [kmod] linux-image-3.19.0-trunk-amd64: net bridge devices no longer 
brought up correctly
Severity set to 'grave' from 'normal'
780295 was not blocked by any bugs.
780295 was not blocking any bugs.
Added blocking bug(s) of 780295: 780263
Marked as found in versions kmod/20-1.
Added tag(s) upstream.
Bug #780256 [kmod] Stopped auto-loading tun module
Merged 780255 780256 780295
 thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
780255: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=780255
780256: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=780256
780295: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=780295
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/handler.s.c.14261748445248.transcr...@bugs.debian.org



Re: Replacing aufs with overlayfs

2015-03-12 Thread maximilian attems
On Thu, Mar 12, 2015 at 03:57:21PM +0100, intrigeri wrote:
 
 [dropping -live@ from the Cc list, as this is not specific to Live
 systems, and affects e.g. some setups based on Linux containers.]
 
 Ben Hutchings wrote (09 Dec 2014 19:55:10 GMT) :
  Please try the Linux 3.18 packages from experimental (they're not there
  yet, but should be soon) and check that overlayfs does what you need.
 
 FYI, at the upstream AppArmor IRC meeting a few days ago, I've learnt
 that overlayfs and AppArmor don't play well together yet.
 
 * Some IRC log excerpts that provide more detail:
   https://labs.riseup.net/code/issues/9045
 
 * The AppArmor bug that tracks this issue:
   https://bugs.launchpad.net/apparmor/+bug/1408106

Apparmor is not critical, hence it is not a regression blocker.
btw 3.19 is out and soon you'll have 3.20. Plenty of time to
fix such thingies.

Better check how it affects Selinux while you'd care about security!

-- 
maks


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20150312205204.GA7568@gluino



Bug#780295: net bridge devices no longer brought up correctly

2015-03-12 Thread Reinhard Karcher
It's a duplicate of bug 780255.

Reinhard


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/4184457.PkU13AxYZP@apollon



Bug#780295: net bridge devices no longer brought up correctly

2015-03-12 Thread Reinhard Karcher
I don't think that to be kernel problem. Booting linux-image-3.16.0-4-amd64
showed the same problem. Putting tun into /etc/modules restored
the old correct behavior.

Reinhard


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/1922533.syd8VeVLO4@apollon



Bug#776409: —Bug#767832— not fixed in cryptsetup 2:1.6.6-4 nor 2:1.6.6-5

2015-03-12 Thread zer0 divide

Hi,

Sorry, I forgot to reinstall the latest version.

See below the output the 0.119 version (the problem remains).

zero@debian:~$ *dpkg -l |grep -i initramfs-tools*
ii  initramfs-tools 0.119   all  
generic modular initramfs generator



*lsinitramfs /boot/initrd.img-$(uname -r)*

/boot/initrd.img-3.16.0-4-amd64
kernel
kernel/x86
kernel/x86/microcode
kernel/x86/microcode/GenuineIntel.bin
.
bin
bin/mkdir
bin/mkfifo
bin/true
bin/kill
bin/run-init
bin/umount
bin/sync
bin/ntfs-3g
bin/poweroff
bin/ipconfig
bin/cpio
bin/gzip
bin/halt
bin/kmod
bin/ls
bin/dmesg
bin/readlink
bin/insmod
bin/cat
bin/udevadm
bin/gunzip
bin/nuke
bin/mv
bin/fstype
bin/resume
bin/uname
bin/pivot_root
bin/ln
bin/nfsmount
bin/dd
bin/loadkeys
bin/minips
bin/losetup
bin/false
bin/mknod
bin/chroot
bin/sleep
bin/mount
bin/reboot
scripts
scripts/functions
scripts/local-bottom
scripts/local-bottom/ntfs_3g
scripts/local-bottom/cryptopensc
scripts/local-bottom/ORDER
scripts/nfs
scripts/init-top
scripts/init-top/blacklist
scripts/init-top/all_generic_ide
scripts/init-top/keymap
scripts/init-top/udev
scripts/init-top/ORDER
scripts/local-block
scripts/local-block/lvm2
scripts/local-block/cryptroot
scripts/local-block/ORDER
scripts/local-top
scripts/local-top/lvm2
scripts/local-top/cryptopensc
scripts/local-top/cryptroot
scripts/local-top/ORDER
scripts/local
scripts/local-premount
scripts/local-premount/ntfs_3g
scripts/local-premount/resume
scripts/local-premount/ORDER
scripts/init-bottom
scripts/init-bottom/udev
scripts/init-bottom/ORDER
conf
conf/conf.d
conf/conf.d/cryptroot
conf/conf.d/resume
conf/arch.conf
conf/initramfs.conf
conf/modules
lib
lib/cryptsetup
lib/cryptsetup/askpass
lib/klibc-IpHGKKbZiB_yZ7GPagmQz2GwVAQ.so
lib/systemd
lib/systemd/systemd-udevd
lib/x86_64-linux-gnu
lib/x86_64-linux-gnu/libacl.so.1
lib/x86_64-linux-gnu/libgpg-error.so.0
lib/x86_64-linux-gnu/libc.so.6
lib/x86_64-linux-gnu/libntfs-3g.so.852
lib/x86_64-linux-gnu/libkmod.so.2
lib/x86_64-linux-gnu/libattr.so.1
lib/x86_64-linux-gnu/libcrypt.so.1
lib/x86_64-linux-gnu/libreadline.so.5
lib/x86_64-linux-gnu/libpthread.so.0
lib/x86_64-linux-gnu/libdl.so.2
lib/x86_64-linux-gnu/libdevmapper-event.so.1.02.1
lib/x86_64-linux-gnu/libe2p.so.2
lib/x86_64-linux-gnu/libgcrypt.so.20
lib/x86_64-linux-gnu/libdevmapper.so.1.02.1
lib/x86_64-linux-gnu/libselinux.so.1
lib/x86_64-linux-gnu/libcom_err.so.2
lib/x86_64-linux-gnu/libblkid.so.1
lib/x86_64-linux-gnu/libcryptsetup.so.4
lib/x86_64-linux-gnu/libtinfo.so.5
lib/x86_64-linux-gnu/libext2fs.so.2
lib/x86_64-linux-gnu/libudev.so.1
lib/x86_64-linux-gnu/libmount.so.1
lib/x86_64-linux-gnu/librt.so.1
lib/x86_64-linux-gnu/libpopt.so.0
lib/x86_64-linux-gnu/libpcre.so.3
lib/x86_64-linux-gnu/libuuid.so.1
lib/udev
lib/udev/ata_id
lib/udev/scsi_id
lib/udev/hotplug.functions
lib/udev/rules.d
lib/udev/rules.d/60-persistent-storage-dm.rules
lib/udev/rules.d/56-lvm.rules
lib/udev/rules.d/80-drivers.rules
lib/udev/rules.d/60-persistent-storage.rules
lib/udev/rules.d/50-firmware.rules
lib/udev/rules.d/55-dm.rules
lib/udev/rules.d/50-udev-default.rules
lib/firmware
lib/firmware/tigon
lib/firmware/tigon/tg3_tso.bin
lib/firmware/tigon/tg3.bin
lib/firmware/tigon/tg3_tso5.bin
lib/firmware/cxgb4
lib/firmware/cxgb4/t4fw.bin
lib/firmware/cxgb4/t5fw.bin
lib/firmware/isci
lib/firmware/isci/isci_firmware.bin
lib/firmware/cis
lib/firmware/cis/PE520.cis
lib/firmware/cis/LA-PCM.cis
lib/firmware/cis/DP83903.cis
lib/firmware/cis/tamarack.cis
lib/firmware/cis/NE2K.cis
lib/firmware/cis/PCMLM28.cis
lib/firmware/cis/PE-200.cis
lib/firmware/e100
lib/firmware/e100/d101s_ucode.bin
lib/firmware/e100/d102e_ucode.bin
lib/firmware/e100/d101m_ucode.bin
lib/firmware/tehuti
lib/firmware/tehuti/bdx.bin
lib/firmware/ene-ub6250
lib/firmware/ene-ub6250/msp_rdwr.bin
lib/firmware/ene-ub6250/ms_rdwr.bin
lib/firmware/ene-ub6250/sd_init2.bin
lib/firmware/ene-ub6250/sd_init1.bin
lib/firmware/ene-ub6250/sd_rdwr.bin
lib/firmware/ene-ub6250/ms_init.bin
lib/firmware/advansys
lib/firmware/advansys/38C1600.bin
lib/firmware/advansys/3550.bin
lib/firmware/advansys/38C0800.bin
lib/firmware/advansys/mcode.bin
lib/firmware/rtl_nic
lib/firmware/rtl_nic/rtl8168d-1.fw
lib/firmware/rtl_nic/rtl8106e-2.fw
lib/firmware/rtl_nic/rtl8105e-1.fw
lib/firmware/rtl_nic/rtl8402-1.fw
lib/firmware/rtl_nic/rtl8168g-2.fw
lib/firmware/rtl_nic/rtl8106e-1.fw
lib/firmware/rtl_nic/rtl8168e-3.fw
lib/firmware/rtl_nic/rtl8168f-2.fw
lib/firmware/rtl_nic/rtl8168g-3.fw
lib/firmware/rtl_nic/rtl8411-2.fw
lib/firmware/rtl_nic/rtl8168e-1.fw
lib/firmware/rtl_nic/rtl8168e-2.fw
lib/firmware/rtl_nic/rtl8168f-1.fw
lib/firmware/rtl_nic/rtl8411-1.fw
lib/firmware/rtl_nic/rtl8168d-2.fw
lib/firmware/3com
lib/firmware/3com/typhoon.bin
lib/firmware/cxgb3
lib/firmware/cxgb3/ael2005_twx_edc.bin
lib/firmware/cxgb3/ael2005_opt_edc.bin
lib/firmware/cxgb3/t3b_psram-1.1.0.bin
lib/firmware/cxgb3/t3c_psram-1.1.0.bin
lib/firmware/cxgb3/t3fw-7.12.0.bin
lib/firmware/cxgb3/ael2020_twx_edc.bin
lib/modules

Volkswagen Golf Sportsvan: Compacte Buitenkant, Ruim Interieur

2015-03-12 Thread CrmConnect
Volkswagen Golf Sportsvan: Compacte Buitenkant, Ruim Interieur  

  Be Exclusive, Get Connected. 

  Als u deze e-mail in tekstformaat ontvangt, zonder 
afbeeldingen,
klik hier [1]! 

   [2] 

  [3]

  Volkswagen Golf Sportsvan: Compacte Buitenkant, Ruim 
Interieur.  

 Design Flank:  Op de flanken toont hij zijn sportieve silhouet:
Slank en vloeiend, met zijn grote deuren en een dynamische zijlijn. 
Design Voorzijde:  Charismatisch over de hele lijn: Radiatorrooster,
koplampen en bumper kenmerken de voorzijde van de Golf Sportsvan
Design Achterzijde:   Het overvloedige gebruik van glas benadrukt de
uniforme en elegante lijn van de Golf Sportsvan en verleent hem een
optimale uitstraling. 

Wagen bezichtigen en/of testrijden
 Kom deze wagen bezichtigen en/of testrijden bij 1 van onze
partner-garages.
 Vraag uw dichtsbijzijnde partner-garage aan via i...@crmconnect.be
[4]
   Prijs:  

Catalogusprijs:
EUR 29.323,14 incl. btw

Fleetprijs:
EUR 24.865,50 incl. btw

Uw voordeel:
 EUR 4.457,64 incl. btw
   

 Neem contact op via: e-mail: i...@crmconnect.be [5] Tel.: +32 (0)56
65 02 71  

 Ik wil meer informatie! [6]

  [7]

 

  [8]

 

  [9]

 CrmConnect levert NOOIT aan de eindklant. Wij werken als
tussenpersoon.  Vraag naar onze parnervoorwaarden.  

  [10]

 

  CrmConnect
 Gentseweg 203, 8792 Desselgem

 +32 056 65 02 71

www.crmconnect.be [11]
i...@crmconnect.be [12]  

 

  [13]   [14]   [15]

  powered by Addemar [16]

 

 Deze e-mail werd verstuurd naar debian-kernel@lists.debian.org [17].
Klik hier [18] om uit te schrijven. 

 

 privacy policy [19]



Links:
--
[1]
http://crmconnect.fb.email.addemar.com/c177/e1519292/h679c9/l42293/index.html
[2]
http://crmconnect.fb.email.addemar.com/c177/e1519292/h679c9/l42294/index.html
[3]
http://crmconnect.fb.email.addemar.com/c177/e1519292/h679c9/l42295/index.html
[4] mailto:i...@crmconnect.be
[5]
mailto:i...@crmconnect.be?subject=Meer%20info%20over%20de%20Volkswagen%20Golf%20Sportsvan
[6]
http://crmconnect.fb.email.addemar.com/c177/e1519292/h679c9/l42296/index.html
[7]
http://crmconnect.fb.email.addemar.com/c177/e1519292/h679c9/l42297/index.html
[8]
http://crmconnect.fb.email.addemar.com/c177/e1519292/h679c9/l42298/index.html
[9]
http://crmconnect.fb.email.addemar.com/c177/e1519292/h679c9/l42299/index.html
[10]
http://crmconnect.fb.email.addemar.com/c177/e1519292/h679c9/l42300/index.html
[11]
http://crmconnect.fb.email.addemar.com/c177/e1519292/h679c9/l42301/index.html
[12] mailto:i...@crmconnect.be
[13]
http://crmconnect.fb.email.addemar.com/c177/e1519292/h679c9/l42302/index.html
[14]
http://crmconnect.fb.email.addemar.com/c177/e1519292/h679c9/l42303/index.html
[15]
http://crmconnect.fb.email.addemar.com/c177/e1519292/h679c9/l42304/index.html
[16]
http://crmconnect.fb.email.addemar.com/c177/e1519292/h679c9/l42305/index.html
[17]
http://crmconnect.fb.email.addemar.com/c177/e1519292/h679c9/l42306/index.html
[18]
http://crmconnect.fb.email.addemar.com/c177/e1519292/h679c9/l42307/index.html
[19]
http://crmconnect.fb.email.addemar.com/c177/e1519292/h679c9/l42308/index.html