date:20141215

On Mon, 15 Dec 2014 08:01:07 + (UTC)
Curt cu...@free.fr wrote:

  In Europe we have 220 Volts between phase and neutre, and 380 Volts
  between two phases (if your house is wired for three-phase current).  
   
 Paraguay is in Europe now?

Never claimed it was, why ?
 
Cheers,
 
Ron.

PS Paraguay is also 220/380 Volts.
-- 
  Documentation is like sex:
   when it is good, it is very, very good;
and when it is bad, it is better than nothing.
   -- Dick Brandon

   -- http://www.olgiati-in-paraguay.org --
 


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20141215062250.28187...@ron.cerrocora.org

Re: music based applications in debian?

I use the free prog Bagpipe, by Philippe Corgier 
http://r.fifi.free.fr/BagPipe/english.htm but it is rather specialized, as it 
caters to the needs of the Scottish Highland Bagpipe player  ;-3)
 
Cheers,
 
Ron.
-- 
  Documentation is like sex:
   when it is good, it is very, very good;
and when it is bad, it is better than nothing.
   -- Dick Brandon

   -- http://www.olgiati-in-paraguay.org --
 


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20141215062622.22cf0...@ron.cerrocora.org

Re: Unable to install bootloader on software raid

2014-12-15 Thread Darac Marjal

On Sat, Dec 13, 2014 at 11:36:58AM +0200, Johann Spies wrote:
After two of my hard disks failed, I decided to use a software raid in
future and tried to install Debian Testing on the raid.  The configuration
of the raid and software installation went well until I tried to install
the bootloader.  Both Grub and Lilo refused to install.
 
If it is not possible to install Grub or Lilo onto a software raid, why is
the option available in Grub?
 
I have seen several efforts to solve this problem on the internet, but
none of them worked for me.
 
What is the way to install Debian onto a software raid?

I think the problem is that, depending on the RAID level, the BIOS won't
be able to read the disks in order to load GRUB. If you're running
RAID0, then you're in luck; both drives appear as normal disks and all
that RAID does is ensure they are kept identical. If you're running
RAID1, though, then each disk is a chopped-up mess of data and you NEED
the RAID to provide the hint that half the data is on another device.

Now, once grub is loaded, it CAN assemble the RAID to a sufficient point
to load all the pieces of the kernel, but if the BIOS can't make enough
sense out of the disk to load GRUB then you have a problem. In that
case, you would normally leave a portion of the disk unRAIDed and
install GRUB onto that.

 
Regards
Johann
--
Because experiencing your loyal love is better than life itself,
my lips will praise you.  (Psalm 63:3)


signature.asc
Description: Digital signature

Re: How is typical home computer used today?

2014-12-15 Thread Erwan David

On Mon, Dec 15, 2014 at 10:22:50AM CET, Renaud OLGIATI 
ren...@olgiati-in-paraguay.org said:
 On Mon, 15 Dec 2014 08:01:07 + (UTC)
 Curt cu...@free.fr wrote:
 
   In Europe we have 220 Volts between phase and neutre, and 380 Volts
   between two phases (if your house is wired for three-phase current).  

  Paraguay is in Europe now?
 
 Never claimed it was, why ?
  
 Cheers,
  
 Ron.
 
 PS Paraguay is also 220/380 Volts.

Europe is officialy 230 V, which with the allowed interval around the
nominal value permitted to accept continental 220 V and UK 240 V.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20141215103610.gb7...@rail.eu.org

Re: How is typical home computer used today?

2014-12-15 Thread Lisi Reisz

On Monday 15 December 2014 09:22:50 Renaud  OLGIATI wrote:
 On Mon, 15 Dec 2014 08:01:07 + (UTC)

 Curt cu...@free.fr wrote:
   In Europe we have 220 Volts between phase and neutre, and 380 Volts
   between two phases (if your house is wired for three-phase current).
 
  Paraguay is in Europe now?

 Never claimed it was, why ?

In Europe *we* *have* I think he meant.

Lisi


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/201412151046.49831.lisi.re...@gmail.com

Re: multihomed server with ipv6

2014-12-15 Thread oneman


 On 13 dec. 2014, at 21:25, Martinx - ジェームズ thiagocmarti...@gmail.com wrote:
 
 On 12 December 2014 at 12:07,  li...@onemanifest.net wrote:
 
 I’m trying to setup a multi-homed server with dual stack networking.
 
 I’ve setup static adressing for both NICs for ipv4 and ipv6 like this:
 
  # The primary LAN network interface
  allow-hotplug eth0
  iface eth0 inet static
address 192.168.1.xx
netmask 255.255.255.0
network 192.168.1.0
broadcast 192.168.1.255
gateway 192.168.1.1
# dns-* options are implemented by the resolvconf package, if installed
dns-nameservers 192.168.1.1
dns-search somedomain.tld
 
  iface eth0 inet6 static
address 2001:::3::20
netmask 64
gateway 2001:::3::1
dns-nameservers 2001:::3::1
dns-search somedomain.tld
 
 
  # The secondary DMZ network interface
  allow-hotplug eth1
  iface eth1 inet static
address 192.168.0.xx
netmask 255.255.255.0
network 192.168.0.0
broadcast 192.168.0.255
gateway 192.168.0.1
# dns-* options are implemented by the resolvconf package, if installed
dns-nameservers 192.168.0.1
dns-search somedomain.tld
 
  iface eth1 inet6 static
address 2001:::2::20
netmask 64
gateway 2001:::2::1
dns-nameservers 2001:::2::1
dns-search somedomain.tld
 
 The NICs are configured fine, but only _one_ ipv6 gets assigned. After a 
 reboot either
 eth0 or eth1 gets it’s ipv6 assigned, never both. I can add the missing ip 
 manually with
 
  ip -6 addr add 2001:::2::20/64 dev eth1
 
 But I can’t get it to be assigned automatically. What am I doing wrong here? 
 I’ve been googling for multi homed servers, but can’t find anything on this 
 issue.
 
 Also, I noticed that if I ping6 a host is subnet A from a NIC in subnet B, 
 the servers ip6 in subnet A is used as source ip, even if an ipv6 in subnet 
 B is available on that NIC. Does this mean that the return traffic is routed 
 over subnet A in stead of B? This is not desirable since I’d like the 
 traffic between both subnets to be fire-walled by the router.
 
 
 Thanks
 
 Hi!
 
 You need to read this:
 http://lartc.org/howto/lartc.rpdb.multiple-links.html;-)
 
 Also, AFAIK, `ifupdown` doesn't handle multi-gateways, with load
 balance and etc, so, you'll need to configure it using up ip ...,
 or, via /etc/rc.local (i.e., don't use gateway entry on
 /etc/network/interfaces on this case).
 
 I have a similar setup working here (multi-wan), I can share the
 confs if you want.
 
 Best!
 Thiago

Thanks, that article is very informative. As Pascal Hambourg also mentioned, 
it’s a little silly to add two default routes :-) 

Your link shows clearly how to handle both interfaces simultaniously with 
routes. The thing is, in my case there will not be any load balancing since the 
machine will run openvz containers that will be either using eth0 or eth1 (the 
server will be sort of split in two, running internet and LAN facing 
containers, both groups isolated from one another). So, I’ll be in fact 
connecting 4 networks; two virtual ones (one for each group of containers, 
venet0 and venet1) and the two NICs. Each virtual network will have to be 
routed to a single NIC… then mix in some iptables. 

I’ll just have to dive into this and report back when I’m stuck…

Thanks so far.


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/0a4837c6-b43d-4b31-992f-32042b908...@onemanifest.net

Re: music based applications in debian?

On Mon, 15 Dec 2014 06:48:20 +0100
Francesco Ariis fa...@ariis.it wrote:

 I use abc notation [1]. It is lean, has everything I need composition
 wise and it is text based. Relevant Debian packages:
 
 abcm2ps - to typeset your music
 abcmidi - to convert abc files to midi
 
 Useful resources:
 
 - a page with abc examples [2]
 - abc-users mailing list [3]
 - more complex example: a transcription of Beethoven's Symphony
   No. 7 in abc notation [4]

There is a very useful program called Easyabc, but alas the present release no 
longer works, some dependency is buggered  ;-3(

$ /usr/bin/easyabc
Traceback (most recent call last):
  File /usr/share/easyabc/easy_abc.py, line 197, in module
import wx
ImportError: No module named wx
 
Cheers,
 
Ron.
-- 
  Documentation is like sex:
   when it is good, it is very, very good;
and when it is bad, it is better than nothing.
   -- Dick Brandon

   -- http://www.olgiati-in-paraguay.org --
 


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20141215081545.233c8...@ron.cerrocora.org

Re: How is typical home computer used today?

On Mon, 15 Dec 2014 10:46:49 +
Lisi Reisz lisi.re...@gmail.com wrote:

In Europe we have 220 Volts between phase and neutre, and 380 Volts
between two phases (if your house is wired for three-phase current).  

   Paraguay is in Europe now?  

  Never claimed it was, why ?  

 In Europe *we* *have* I think he meant.

Well, I lived in Europe for over fifty years...
 
Cheers,
 
Ron.
-- 
 A diplomat is man who always remembers a woman's birthday but never her age.
  -- Robert Frost

   -- http://www.olgiati-in-paraguay.org --
 


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20141215081846.4dbc1...@ron.cerrocora.org

Machine hangs at boot

My machine hangs at boot, so i'd like someone to take a look at my log. Thanks

http://pastebin.com/3crkJgnE

Re: Upgrading from squeeze to wheezy

What happens when you run apt-get -f install?

-- 
http://markorandjelovic.hopto.org

One should not be afraid of humans.
Well, I am not afraid of humans, but of what is inhuman in them.
Ivo Andric, Signs near the travel-road


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20141215123700.49ec4...@eunet.rs

Re: How is typical home computer used today?

2014-12-15 Thread mourik jan heupink



On 12/15/2014 11:36, Erwan David wrote:

Europe is officialy 230 V, which with the allowed interval around the
nominal value permitted to accept continental 220 V and UK 240 V.

Yes, that's exactly my understanding of things here at the moment.


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

Archive: https://lists.debian.org/548ec87f.3000...@merit.unu.edu

Re: Machine hangs at boot

On Mon, 15 Dec 2014 14:37:10 +0400
German gentger...@gmail.com wrote:

 My machine hangs at boot, so i'd like someone to take a look at my log. Thanks
 
 http://pastebin.com/3crkJgnE

 939. [   34.070472] EXT4-fs (sda2): re-mounted. Opts: errors=remount-ro

What's sda2? Looks like it has errors. Do fsck on sda2.

-- 
http://markorandjelovic.hopto.org

One should not be afraid of humans.
Well, I am not afraid of humans, but of what is inhuman in them.
Ivo Andric, Signs near the travel-road


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20141215124552.19a9b...@eunet.rs

Re: Machine hangs at boot

Fsck says sda2 is clean. Thanks

Marko Randjelovic marko...@eunet.rs wrote:

On Mon, 15 Dec 2014 14:37:10 +0400
German gentger...@gmail.com wrote:

 My machine hangs at boot, so i'd like someone to take a look at my log. 
 Thanks
 
 http://pastebin.com/3crkJgnE

 939. [   34.070472] EXT4-fs (sda2): re-mounted. Opts: errors=remount-ro

What's sda2? Looks like it has errors. Do fsck on sda2.

-- 
http://markorandjelovic.hopto.org

One should not be afraid of humans.
Well, I am not afraid of humans, but of what is inhuman in them.
Ivo Andric, Signs near the travel-road


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20141215124552.19a9b...@eunet.rs

Re: How Not to Install systemd to Begin With.

On Sun, 14 Dec 2014 15:49:57 -0800
Patrick Bartek nemomm...@gmail.com wrote:

 After the lively debate here that replacing systemd after it's installed
 is not the same as not installing it in the first place:  Here's the
 solution, more or less.  Although, it seems, one will never be truly
 free from parts of systemd in Testing-Jessie.
 
 http://without-systemd.org/wiki/index.php/How_to_remove_systemd_from_the_Netinst_CD
 
 I haven't tested this myself.  So, no guarantees.
 
 B
 
 

What to do with sections config-deb, config-rel, config-udeb?

-- 
http://markorandjelovic.hopto.org

One should not be afraid of humans.
Well, I am not afraid of humans, but of what is inhuman in them.
Ivo Andric, Signs near the travel-road


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20141215124313.597ff...@eunet.rs

Re: Machine hangs at boot

On Monday 15 December 2014 14:37:10 German wrote:
 My machine hangs at boot, so i'd like someone to take a look at my log.
 Thanks
 
 http://pastebin.com/3crkJgnE

Let's try another wild guess.

sdb looks corrupted or not initialized

[2.147780]  sdb: unknown partition table

Can you unplug that 500GB disk to see if the kernel isn't chocking on a 
hardware error?

Beware that it will shift sdc to sdb. Depending on the system configuration, it 
might be necessary to boot in single user/rescue mode. You may also want to 
unplug sdc to prevent it from being accessed as sdb.

Frederic


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/1601304.9eq4r7q...@fmarchal.edpnet.be

Re: Machine hangs at boot

Do you refer to SDB as 500GB disk?

Frederic Marchal frederic.marc...@wowtechnology.com wrote:

On Monday 15 December 2014 14:37:10 German wrote:
 My machine hangs at boot, so i'd like someone to take a look at my log.
 Thanks
 
 http://pastebin.com/3crkJgnE

Let's try another wild guess.

sdb looks corrupted or not initialized

[2.147780]  sdb: unknown partition table

Can you unplug that 500GB disk to see if the kernel isn't chocking on a 
hardware error?

Beware that it will shift sdc to sdb. Depending on the system configuration, 
it 
might be necessary to boot in single user/rescue mode. You may also want to 
unplug sdc to prevent it from being accessed as sdb.

Frederic


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/1601304.9eq4r7q...@fmarchal.edpnet.be

Re: Machine hangs at boot

On Monday 15 December 2014 15:40:23 German wrote:
 Do you refer to SDB as 500GB disk?

It looks so:

[2.128658] scsi 1:0:0:0: Direct-Access ATA  ST500LM021-1KJ15 0001 
PQ: 0 ANSI: 5
[2.130695] sd 1:0:0:0: [sdb] 976773168 512-byte logical blocks: (500 
GB/465 GiB)


Frederic

 Frederic Marchal frederic.marc...@wowtechnology.com wrote:
 On Monday 15 December 2014 14:37:10 German wrote:
  My machine hangs at boot, so i'd like someone to take a look at my log.
  Thanks
  
  http://pastebin.com/3crkJgnE
 
 Let's try another wild guess.
 
 sdb looks corrupted or not initialized
 
 [2.147780]  sdb: unknown partition table
 
 Can you unplug that 500GB disk to see if the kernel isn't chocking on a
 hardware error?
 
 Beware that it will shift sdc to sdb. Depending on the system
 configuration, it might be necessary to boot in single user/rescue mode.
 You may also want to unplug sdc to prevent it from being accessed as sdb.
 
 Frederic


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/709327382.yorfe8e...@fmarchal.edpnet.be

Re: Machine hangs at boot

Oh OK, there really is such a disk. Unfortunately I can't remove it. My machine 
was running smoothly for about two months and after kernel update this thing 
happened.

Frederic Marchal frederic.marc...@wowtechnology.com wrote:

On Monday 15 December 2014 15:40:23 German wrote:
 Do you refer to SDB as 500GB disk?

It looks so:

[2.128658] scsi 1:0:0:0: Direct-Access ATA  ST500LM021-1KJ15 0001 
PQ: 0 ANSI: 5
[2.130695] sd 1:0:0:0: [sdb] 976773168 512-byte logical blocks: (500 
GB/465 GiB)


Frederic

 Frederic Marchal frederic.marc...@wowtechnology.com wrote:
 On Monday 15 December 2014 14:37:10 German wrote:
  My machine hangs at boot, so i'd like someone to take a look at my log.
  Thanks
  
  http://pastebin.com/3crkJgnE
 
 Let's try another wild guess.
 
 sdb looks corrupted or not initialized
 
 [2.147780]  sdb: unknown partition table
 
 Can you unplug that 500GB disk to see if the kernel isn't chocking on a
 hardware error?
 
 Beware that it will shift sdc to sdb. Depending on the system
 configuration, it might be necessary to boot in single user/rescue mode.
 You may also want to unplug sdc to prevent it from being accessed as sdb.
 
 Frederic

Re: How Not to Install systemd to Begin With.

2014-12-15 Thread Reco

 Hi.

On Mon, Dec 15, 2014 at 12:43:13PM +0100, Marko Randjelovic wrote:
 On Sun, 14 Dec 2014 15:49:57 -0800
 Patrick Bartek nemomm...@gmail.com wrote:
 
  After the lively debate here that replacing systemd after it's installed
  is not the same as not installing it in the first place:  Here's the
  solution, more or less.  Although, it seems, one will never be truly
  free from parts of systemd in Testing-Jessie.
  
  http://without-systemd.org/wiki/index.php/How_to_remove_systemd_from_the_Netinst_CD
  
  I haven't tested this myself.  So, no guarantees.
  
  B
  
  
 
 What to do with sections config-deb, config-rel, config-udeb?

Create them as files, use said files by means of invoking update-cdrom.sh.
Seems obvious, isn't it?

Reco


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20141215123112.GA15377@x101h

Re: Machine hangs at boot

On Monday 15 December 2014 15:48:40 German wrote:
 Oh OK, there really is such a disk. Unfortunately I can't remove it. My
 machine was running smoothly for about two months and after kernel update
 this thing happened.

Is sdb supposed to contain a valid partition?

If it is supposed to be a valid disk, then, I would say it is now corrupted…

How frequently do you reboot your computer? If you reboot it infrequently and 
just rebooted it after the kernel update, then the disk failure may have been 
noticed only then.

As the kernel driver handling that disk is a generic scsi, I doubt a kernel 
bug affects your system.

The ata driver can't be blamed here either as it is recognizing sda just fine.

Now, something else may be holding the boot sequence for 26 seconds just 
before mounting the swap partition on sda3 but you ruled out a corruption on 
sda2. And we lack evidences that any other peripheral is behaving strangely.

Frederic


 Frederic Marchal frederic.marc...@wowtechnology.com wrote:
 On Monday 15 December 2014 15:40:23 German wrote:
  Do you refer to SDB as 500GB disk?
 
 It looks so:
 
 [2.128658] scsi 1:0:0:0: Direct-Access ATA  ST500LM021-1KJ15
 0001 PQ: 0 ANSI: 5
 [2.130695] sd 1:0:0:0: [sdb] 976773168 512-byte logical blocks: (500
 GB/465 GiB)
 
 
 Frederic
 
  Frederic Marchal frederic.marc...@wowtechnology.com wrote:
  On Monday 15 December 2014 14:37:10 German wrote:
   My machine hangs at boot, so i'd like someone to take a look at my
   log.
   Thanks
   
   http://pastebin.com/3crkJgnE
  
  Let's try another wild guess.
  
  sdb looks corrupted or not initialized
  
  [2.147780]  sdb: unknown partition table
  
  Can you unplug that 500GB disk to see if the kernel isn't chocking on a
  hardware error?
  
  Beware that it will shift sdc to sdb. Depending on the system
  configuration, it might be necessary to boot in single user/rescue mode.
  You may also want to unplug sdc to prevent it from being accessed as
  sdb.
  
  Frederic


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/8251684.iwjy9h4...@fmarchal.edpnet.be

Removing USB entry in /etc/fstab in standard installations

2014-12-15 Thread Christoph Baumhardt

Hi,

I had problems a while ago with several USB sticks on Debian Jessie. For
all non-root users they were automounted read-only. But there was no way of
writing something onto the sticks for a non-privileged user. Fiddling
around with user permissions and such didn't help. The simple solution
finally was to comment out the following line in /etc/fstab:

/dev/sdb1   /media/usb0 autorw,user,noauto  0   0

After commenting out this line all normal users could write to all USB
sticks, just as you would expect it to work. Someone suggested that the
fstab entry existed in the first place because I had installed Jessie from
a USB stick as root, but I can't judge that.

If you look in the forums, many people face the same problem - they can
read, but not write to a USB stick plugged in. The same solution as above
works for them. Examples:

http://forums.debian.net/viewtopic.php?f=5t=119254
http://forums.debian.net/viewtopic.php?f=30t=119061
http://forums.debian.net/viewtopic.php?f=30t=119423
http://forums.debian.net/viewtopic.php?f=10t=107470

So I have two questions now:

1. Is it necessary/a good thing that in a standard Debian installation this
/etc/fstab USB entry appears?
2. Can developers or maintainers do something about this issue, so that
novice users don't experience the same problems as I and several others
did? I think being able to write to an USB stick should work out of the box
for a non-root user. Perhaps there are ways to not let the fstab entry
appear at all if it isn't necessary or remove it after installation.

Re: Machine hangs at boot

SDB is ext4. It is just a disk I use for data. Under normal circumstances, when 
system operating normally it isn't mounted for some reason and it gets mounted 
when I just click on it in LXDE. I guess that's why it's not initialized

Frederic Marchal frederic.marc...@wowtechnology.com wrote:

On Monday 15 December 2014 15:48:40 German wrote:
 Oh OK, there really is such a disk. Unfortunately I can't remove it. My
 machine was running smoothly for about two months and after kernel update
 this thing happened.

Is sdb supposed to contain a valid partition?

If it is supposed to be a valid disk, then, I would say it is now corrupted…

How frequently do you reboot your computer? If you reboot it infrequently and 
just rebooted it after the kernel update, then the disk failure may have been 
noticed only then.

As the kernel driver handling that disk is a generic scsi, I doubt a kernel 
bug affects your system.

The ata driver can't be blamed here either as it is recognizing sda just fine.

Now, something else may be holding the boot sequence for 26 seconds just 
before mounting the swap partition on sda3 but you ruled out a corruption on 
sda2. And we lack evidences that any other peripheral is behaving strangely.

Frederic


 Frederic Marchal frederic.marc...@wowtechnology.com wrote:
 On Monday 15 December 2014 15:40:23 German wrote:
  Do you refer to SDB as 500GB disk?
 
 It looks so:
 
 [2.128658] scsi 1:0:0:0: Direct-Access ATA  ST500LM021-1KJ15
 0001 PQ: 0 ANSI: 5
 [2.130695] sd 1:0:0:0: [sdb] 976773168 512-byte logical blocks: (500
 GB/465 GiB)
 
 
 Frederic
 
  Frederic Marchal frederic.marc...@wowtechnology.com wrote:
  On Monday 15 December 2014 14:37:10 German wrote:
   My machine hangs at boot, so i'd like someone to take a look at my
   log.
   Thanks
   
   http://pastebin.com/3crkJgnE
  
  Let's try another wild guess.
  
  sdb looks corrupted or not initialized
  
  [2.147780]  sdb: unknown partition table
  
  Can you unplug that 500GB disk to see if the kernel isn't chocking on a
  hardware error?
  
  Beware that it will shift sdc to sdb. Depending on the system
  configuration, it might be necessary to boot in single user/rescue mode.
  You may also want to unplug sdc to prevent it from being accessed as
  sdb.
  
  Frederic


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/8251684.iwjy9h4...@fmarchal.edpnet.be

Re: 9p/plumber to replace D-Bus?

2014-12-15 Thread Richard Owlett


berenger.mo...@neutralite.org wrote:



Le 12.12.2014 14:54, Richard Owlett a écrit :

I.E. Who is responsible for the integrity of *MY* system?
The correct answer is the proverbial Me, Myself, and I.
It is most definitely not an individual nor group whom I've
never met.
There is most definitely a need for such systems as the vast
majority
do not have the needed experience/expertise.


Yes, but, since you post on this list, I would tend to think you
are someone with administration knowledge.


That implys too much in my favor.


At least basic one,
especially since you are here since longer than me, you probably
have learn tons of things from various threads.


That is the value of mailing lists over web based fora - its easy 
to save and index gems of information.




For someone which does not even know what is a mailing list, I
would not think that they have or want to have enough knowledge
of their computers to simply understand what installing an
application really means.
Remember: there are people able to trust phishing mails!

And I did not even spoke about the fact that, around here, lot of
people seems unable to feel responsible for their own actions...
I would like to be wrong, or if not, that this feeling is only
because I'm in the wrong place of the world, but I doubt it.


That is how I operate ~100% of the time. Security is a
non-issue, I
have the only key to my house. It needs only one password to
cove case
of physical malicious access.


The above has suffered multiple trims. I, the OP, said:
] There is a market (how large???) for a single user single task 
computer and OS.
] That is how I operate ~100% of the time. Security is a 
non-issue, I have
] the only key to my house. It needs only one password to cover 
case of physical
] malicious access. There would be advantages to a maintenance 
password to guard
] me from making careless/dumb errors on *MY OWN* machine. It 
would be extremely

] useful if its kernel supported running unmodified Debian packages.


What about software you ran as normal user with full rights doing
malicious access to your hardware, thus being able to corrupt
things like UEFI?


Hopefully I would learn from my errors. In any case the
responsibility is mine.


Not everyone is able or want to learn. Plus, to acquire
knowledge, you need to have bases which allows you to do so.
How could I learn what a virus is, if I do not know what a file
is? How could I learn what a worm is, without knowing that
applications can communicate?


It is all the want to learn factor. Ask questions!
When I was growing up, mid-20th century, a current saying was:
The only dumb question is the one that is not asked.

[For non-native speakers, the above is a pun on dumb. Dumb can 
mean mute or in informal usage stupid.]






There would be advantages to a
maintenance password to guard me from making careless/dumb
errors on
*MY OWN* machine. It would be extremely useful if its kernel
supported
running unmodified Debian packages.


Linux is built as a multi user kernel. I guess any software using
linux specific features, or multi-user based feature, like cups,
for example, would need changes. At least to not try to create
it's own user.




I assumed it would possibly require a quite different core and apt
substitute. How closely tied is content of a Debian package
tied to a
Linux kernel?


It depends.
Source package, or binary package?
Package installing low level, or high level stuff?

I'll bet on source package, so that I could not argue about the
libc.
Hopefully, high-level applications does not depends on linux
kernel-related stuff, but now, we've seen applications recently
which depends on features provided by systemd, which is, AFAIK,
not ported on non-linux kernels.
Also, a cat /etc/passwd could inform you about how many users are
present on your system, but remember that it's only your system:
other systems might have more, or less, depending on what was
installed in the past (do you know that, when you purge a
package, it won't remove the users it added?).

Simple example: databases. They often create their own users. Do
you have any package which depends on a database? I'm not sure,
but I think cups also uses it's own user.

Adapting Debian to a single user system might not be that hard,
but I am quite sure that it will be a ton of work, and that
strange issues will happen here and there.


I was just commenting on what I would like as an ideal. I doubt 
its practicality.



Now, I've heard about puppy linux, in terms like: users are root.
It might interest you.





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

Archive: https://lists.debian.org/548ede15.4090...@cloud85.net

Re: Machine hangs at boot

On Monday 15 December 2014 16:14:09 German wrote:
 SDB is ext4. It is just a disk I use for data. Under normal circumstances,
 when system operating normally it isn't mounted for some reason and it gets
 mounted when I just click on it in LXDE. I guess that's why it's not
 initialized

LXDE can't mount a ext4 partition if the disk partition table is unknown.

Could the partition table be in an unusual format and the new kernel doesn't 
support that format anymore? I doubt it. It is more likely that it got 
corrupted but you didn't notice until the system was rebooted.

Can you check that disk with a live cd, rescue mode or whatever you have at 
hand?

PS: I just saw your other mail where you write that catalyst is working fine. I 
expected that much. So sdb is again the most suspicious line reported by 
dmesg.

Frederic


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/1634361.thzh7cf...@fmarchal.edpnet.be

Re: Removing USB entry in /etc/fstab in standard installations

2014-12-15 Thread Patrick Wiseman

On Mon, Dec 15, 2014 at 7:46 AM, Christoph Baumhardt xt4...@gmail.com wrote:
Hi,

I had problems a while ago with several USB sticks on Debian Jessie. For all
non-root users they were automounted read-only. But there was no way of
writing something onto the sticks for a non-privileged user. Fiddling around
with user permissions and such didn't help. The simple solution finally was
to comment out the following line in /etc/fstab:

/dev/sdb1 /media/usb0 autorw,user,noauto 0 0

After commenting out this line all normal users could write to all USB
sticks, just as you would expect it to work. Someone suggested that the
fstab entry existed in the first place because I had installed Jessie from a
USB stick as root, but I can't judge that.

Thanks you! I'd puzzled over that for quite a while, but never been
sufficiently bothered to seek out a solution (as I can always use sudo
or become root to do what needed to be done). Once the offending line
is commented out (in my case, 2 such lines, one assigning /dev/sdc1 to
/media/usb0, the other assigning /dev/sdc2 to /media/usb1) my USB
stick mounted to /media/user/USB DISK/ and is owned by me (where
user is my username).

So, thanks again.

If you look in the forums, many people face the same problem - they can
read, but not write to a USB stick plugged in. The same solution as above
works for them. Examples:

http://forums.debian.net/viewtopic.php?f=5t=119254
http://forums.debian.net/viewtopic.php?f=30t=119061
http://forums.debian.net/viewtopic.php?f=30t=119423
http://forums.debian.net/viewtopic.php?f=10t=107470

So I have two questions now:

1. Is it necessary/a good thing that in a standard Debian installation this
/etc/fstab USB entry appears?

It is certainly not a good thing after installation, as it obviously
breaks expected behavior.

2. Can developers or maintainers do something about this issue, so that
novice users don't experience the same problems as I and several others did?
I think being able to write to an USB stick should work out of the box for a
non-root user. Perhaps there are ways to not let the fstab entry appear at
all if it isn't necessary or remove it after installation.

I agree.

Thanks again for the information.

Patrick

--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive:
https://lists.debian.org/cajvvksoodqnbzi7uqau1qffsh_mnxdfnldqvdc6v-4mx0hm...@mail.gmail.com

Re: How is typical home computer used today?

2014-12-15 Thread berenger . morel




Le 14.12.2014 22:48, mourik jan heupink - merit a écrit :

Hi,

berenger.morel writes:

In France, the electric network provide 220V to everyone.

Are you sure? Starting from 2000 or so, the whole of europe has
gradually changed to 230v, as a compromise between UK (240v) and the
rest of europe (220v).

MJ


I am not sure. But, how old is this reform? I have used voltmeters more 
than once, and have always read 220V. But, I have not had to find 
failures in an installation since at least few years, maybe 5-6 (which 
is a long time when you still are not 30 years old, so I'm not sure 
about how many years exactly I did not had to check).



--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/64a2ede654e4092092b64dbcd7141...@neutralite.org

Re: Machine hangs at boot

2014-12-15 Thread berenger . morel




Le 15.12.2014 14:00, Frederic Marchal a écrit :

On Monday 15 December 2014 15:48:40 German wrote:
Oh OK, there really is such a disk. Unfortunately I can't remove it. 
My
machine was running smoothly for about two months and after kernel 
update

this thing happened.


Is sdb supposed to contain a valid partition?

If it is supposed to be a valid disk, then, I would say it is now 
corrupted…


How frequently do you reboot your computer? If you reboot it
infrequently and
just rebooted it after the kernel update, then the disk failure may
have been
noticed only then.

As the kernel driver handling that disk is a generic scsi, I doubt a 
kernel

bug affects your system.

The ata driver can't be blamed here either as it is recognizing sda
just fine.

Now, something else may be holding the boot sequence for 26 seconds 
just
before mounting the swap partition on sda3 but you ruled out a 
corruption on
sda2. And we lack evidences that any other peripheral is behaving 
strangely.


Frederic


Well I had similar... lag... in testing, since few months, because of 
dbus. Several other people had it, too. It could be an update of udev 
which introduced it.



--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/c29b48063c885f15dc5a0863b5a44...@neutralite.org

Re: Machine hangs at boot

Rescue mode is the same as recovery mode? If so, yes I can go to recovery but 
not sure how to proceed to check cdb for errors. Unfortunaly I don't have a 
rescue cd

Frederic Marchal frederic.marc...@wowtechnology.com wrote:

On Monday 15 December 2014 16:14:09 German wrote:
 SDB is ext4. It is just a disk I use for data. Under normal circumstances,
 when system operating normally it isn't mounted for some reason and it gets
 mounted when I just click on it in LXDE. I guess that's why it's not
 initialized

LXDE can't mount a ext4 partition if the disk partition table is unknown.

Could the partition table be in an unusual format and the new kernel doesn't 
support that format anymore? I doubt it. It is more likely that it got 
corrupted but you didn't notice until the system was rebooted.

Can you check that disk with a live cd, rescue mode or whatever you have at 
hand?

PS: I just saw your other mail where you write that catalyst is working fine. 
I 
expected that much. So sdb is again the most suspicious line reported by 
dmesg.

Frederic


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/1634361.thzh7cf...@fmarchal.edpnet.be

Wheezy: mouse middle button issue

2014-12-15 Thread Jerome BENOIT

Hello Forum !

Since a couple of day, the middle button of my magic mouse (USB)
has experienced a major issue: I can more copy/past or open-in-new-tab.
A deeper investigation with xev shows that button 2 is no more existing:
any idea ?

My box is a Wheezy box that is daily updated.

Cheers,
Jerome


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/548eeb38.5060...@rezozer.net

Re: How is typical home computer used today?

2014-12-15 Thread mourik jan heupink


I am not sure. But, how old is this reform? I have used voltmeters more
than once, and have always read 220V. But, I have not had to find
failures in an installation since at least few years, maybe 5-6 (which
is a long time when you still are not 30 years old, so I'm not sure
about how many years exactly I did not had to check).


Google tells me:
http://en.wikipedia.org/wiki/Mains_electricity

Check the paragraph Standardisation.

But please note: I'm no electrician at all :-)


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

Archive: https://lists.debian.org/548eebd1.7060...@merit.unu.edu

Re: How is typical home computer used today?

2014-12-15 Thread Tony van der Hoff

On 15/12/14 14:30, berenger.mo...@neutralite.org wrote:
 
 
 Le 14.12.2014 22:48, mourik jan heupink - merit a écrit :
 Hi,

 berenger.morel writes:
 In France, the electric network provide 220V to everyone.
 Are you sure? Starting from 2000 or so, the whole of europe has
 gradually changed to 230v, as a compromise between UK (240v) and the
 rest of europe (220v).

 MJ
 
 I am not sure. But, how old is this reform? I have used voltmeters more
 than once, and have always read 220V. But, I have not had to find
 failures in an installation since at least few years, maybe 5-6 (which
 is a long time when you still are not 30 years old, so I'm not sure
 about how many years exactly I did not had to check).
 
 
The change was agreed by the Council of Europe in 1989, with a 15-year
implementation time.

A reading of 220V on a nominal 230V +/- 6% (i.e 216.2 .. 243.8) is quite
legitimate, and even to be expected

-- 
Tony van der Hoff  | mailto:t...@vanderhoff.org
Ariège, France |


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/548eeec1.8030...@vanderhoff.org

Re: multihomed server with ipv6

2014-12-15 Thread oneman


 On 13 dec. 2014, at 23:35, Pascal Hambourg pas...@plouf.fr.eu.org wrote:
 
 Hello,
 
 li...@onemanifest.net a écrit :
 
 I've setup static adressing for both NICs for ipv4 and ipv6 like this:
 
  # The primary LAN network interface
  allow-hotplug eth0
  iface eth0 inet static
address 192.168.1.xx
netmask 255.255.255.0
gateway 192.168.1.1
 
  iface eth0 inet6 static
address 2001:::3::20
netmask 64
gateway 2001:::3::1
 
  # The secondary DMZ network interface
  allow-hotplug eth1
  iface eth1 inet static
address 192.168.0.xx
netmask 255.255.255.0
gateway 192.168.0.1
 
  iface eth1 inet6 static
address 2001:::2::20
netmask 64
gateway 2001:::2::1
 
 The NICs are configured fine, but only _one_ ipv6 gets assigned. After a 
 reboot either
 eth0 or eth1 gets it's ipv6 assigned, never both.
 
 I could reproduce it on a test machine. This looks like a tricky
 side-effect of multiple IPv4 default gateways.
 
 Here is what happens :
 One interface is configured first. Since you used allow-hotplug
 insteald of auto, the order may vary, depending on the discovery order
 by udev. When the second interface is configured for IPv4, ifup adds the
 address, tries to add the default route and gets an error because a
 default route already exists. Then it stops trying to configure the
 interface, including the IPv6 configuration.
 
 Bottom line : don't define a gateway on multiple interfaces unless you
 are sure that only one interface is active at a time. It usually won't
 work the way you expect. Default means no other choice. If there are
 two active gateways then you still have to make a choice. Thus defining
 two active default gateways makes no sense.

I get it now, two defaults is a bit silly yes :-) You explanation is very 
clear. 

- I’ll use ‘auto’ to configure the interfaces, hot plug is not needed for this 
server.
- Since this server will be used for running openvz containers, I’ll probably 
have to create explicit routes for each (virtual) network to the subnets the 
NICs are connected to and define an explicit gateway for each subnet?

However, while doing some more research on this matter, it occurred to me that 
I can make life a lot easier on myself by using bridges. (Sorry if I sound very 
n00b-isch here) I think I could do the following:
- configure only the LAN NIC on the host, so I get admin access to the host 
from the LAN
- create a bridge on each NIC
- connect the containers to the appropriate bridge for either LAN or DMZ, 
setting up networking on each container independently.

This way the host is neatly isolated from the DMZ and the containers and the 
setup is far simpler. 

I’ll just dive into this and report back when I’m stuck. 

 
 Also, I noticed that if I ping6 a host is subnet A from a NIC in
 subnet B, the servers ip6 in subnet A is used as source ip, even if an
 ipv6 in subnet B is available on that NIC. Does this mean that the
 return traffic is routed over subnet A in stead of B? This is not
 desirable since I'd like the traffic between both subnets to be
 fire-walled by the router.
 
 I tried hard and failed to understand what you mean. Please describe
 more precisely what are the host, NIC, subnets, servers, router you're
 talking about, how they relate to the above, the commands you run and
 the results you observe.

My network is like this:
other
hosts
 ||
|NIC 2001:::3::1/64| == LAN subnet == |NIC eth0 
2001:::3::20/64|
internet == |  router  |  |Server   
   |
|NIC 2001:::2::1/64| == DMZ subnet == |NIC eth1 
2001:::2::20/64|
 ||
other
hosts

Configured with my half baked setup as described above, including adding the 
missing ipv6 due to the failure of ifup.

Then I did a ping6 to a host in LAN subnet, from the DMZ NIC on the server. I 
saw that the ping command reported using the LAN ip6 (2001:::3::20/64) 
as a source ip, instead of the DMZ one (2001:::2::20/64) as I expected 
it to do.

Hope this makes it clear.

thanks

--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/fda3f6bd-cef7-41ba-b084-41ce65352...@onemanifest.net

Re: How is typical home computer used today?

2014-12-15 Thread berenger . morel




Le 15.12.2014 15:22, Tony van der Hoff a écrit :

On 15/12/14 14:30, berenger.mo...@neutralite.org wrote:



Le 14.12.2014 22:48, mourik jan heupink - merit a écrit :

Hi,

berenger.morel writes:

In France, the electric network provide 220V to everyone.

Are you sure? Starting from 2000 or so, the whole of europe has
gradually changed to 230v, as a compromise between UK (240v) and 
the

rest of europe (220v).

MJ


I am not sure. But, how old is this reform? I have used voltmeters 
more

than once, and have always read 220V. But, I have not had to find
failures in an installation since at least few years, maybe 5-6 
(which

is a long time when you still are not 30 years old, so I'm not sure
about how many years exactly I did not had to check).


The change was agreed by the Council of Europe in 1989, with a 
15-year

implementation time.

A reading of 220V on a nominal 230V +/- 6% (i.e 216.2 .. 243.8) is 
quite

legitimate, and even to be expected


I can also read this:

In practice, this allows countries to continue to supply the same 
voltage (220 or 240 V)


In other words: yet another useless rule. I love bureaucracy.


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/bdda344f5b4da8be48bce4afff66d...@neutralite.org

Re: Unable to install bootloader on software raid

2014-12-15 Thread Sven Hartge

Darac Marjal mailingl...@darac.org.uk wrote:

 I think the problem is that, depending on the RAID level, the BIOS won't
 be able to read the disks in order to load GRUB. If you're running
 RAID0, then you're in luck; both drives appear as normal disks and all
 that RAID does is ensure they are kept identical. If you're running
 RAID1, though, then each disk is a chopped-up mess of data and you NEED
 the RAID to provide the hint that half the data is on another device.

It's the other way round: RAID0 is striped, aka chopped up mess and
RAID1 are mirrored disks.

S°

-- 
Sigmentation fault. Core dumped.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/7b7phlg9v...@mids.svenhartge.de

Re: Transición a Debian

2014-12-15 Thread Michael Fothergill

On Sat, Dec 13, 2014 at 6:21 PM, Renaud OLGIATI 
ren...@olgiati-in-paraguay.org wrote:

 On Sat, 13 Dec 2014 18:47:02 +0100
 Jerome BENOIT g62993...@rezozer.net wrote:

  Hola, this is an English Forum.
  Cheers, Jerome

 It pains me, especially at this Xmas time, to see this kind of un-helpful
 rebuke given without any sort of useful reply to the original query, or at
 least some pointer where the enquirer could find the answer, or help, in
 his own language.

 Cheers,

 Ron.

 I had thought to use google translate to reply to the query in the posting
but was not sure how well that work in practice so I decided against it.

Regards

Michael Fothergill

Benedicite , sancti et superexaltate systemd

Re: Unable to start kvm virtual machines after re-install of testing

2014-12-15 Thread Dave Bamford

I have got the same problem, after a reinstall of testing I get the 
message about
Unable to find a suitable CPU when trying to create a new VM (any 
flavour). It was working before the reinstall.


My CPU details are as follows.

processor: 7
vendor_id: AuthenticAMD
cpu family: 21
model: 2
model name: AMD FX(tm)-9590 Eight-Core Processor
stepping: 0
microcode: 0x6000822
cpu MHz: 4700.000
cache size: 2048 KB
physical id: 0
siblings: 8
core id: 7
cpu cores: 4
apicid: 23
initial apicid: 7
fpu: yes
fpu_exception: yes
cpuid level: 13
wp: yes
flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge 
mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext 
fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good nopl nonstop_tsc 
extd_apicid aperfmperf pni pclmulqdq monitor ssse3 fma cx16 sse4_1 
sse4_2 popcnt aes xsave avx f16c lahf_lm cmp_legacy svm extapic 
cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs xop skinit wdt 
lwp fma4 tce nodeid_msr tbm topoext perfctr_core perfctr_nb arat cpb 
hw_pstate npt lbrv svm_lock nrip_save tsc_scale vmcb_clean flushbyasid 
decodeassists pausefilter pfthreshold bmi1

bogomips: 9444.18
TLB size: 1536 4K pages
clflush size: 64
cache_alignment: 64
address sizes: 48 bits physical, 48 bits virtual
power management: ts ttp tm 100mhzsteps hwpstate cpb eff_freq_ro


Regards

Dave Bamford



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

Archive: https://lists.debian.org/548ef803.1010...@bdisystems.co.uk

Re: Wheezy: mouse middle button issue

On Mon, 15 Dec 2014 15:07:52 +0100
Jerome BENOIT g62993...@rezozer.net wrote:

 Hello Forum !
 
 Since a couple of day, the middle button of my magic mouse (USB)
 has experienced a major issue: I can more copy/past or open-in-new-tab.
 A deeper investigation with xev shows that button 2 is no more existing:
 any idea ?
 
 My box is a Wheezy box that is daily updated.
 
 Cheers,
 Jerome
 
 

Try your mouse in another computer to see if it's not hardware failure.

-- 
http://markorandjelovic.hopto.org

One should not be afraid of humans.
Well, I am not afraid of humans, but of what is inhuman in them.
Ivo Andric, Signs near the travel-road


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20141215174157.3de29...@eunet.rs

Re: change subject of emails on ISP's IMAP server

2014-12-15 Thread Darac Marjal

On Fri, Dec 12, 2014 at 08:53:51PM -0500, Rob Owens wrote:
 When my ISP encounters an email that it cannot scan for viruses, it
 prepends ***UNCHECKED*** to the subject.  This occurs on every encrypted
 email I receive.  It's highly annoying, and the ISP refuses to fix this.
 
 What tools can I use to detect this tag and delete it?  I'd prefer to
 modify the subject of the email as it resides on my ISP's IMAP server.
 But if I have to rely on my email client (mutt) to do that, that's ok
 too I guess.
 
 Any suggestions would be welcome.  

Apparently, this is what imapfilter will do. You'll need to write a lua
script to tell it what to do, but it looks like it comes with some
hackable examples.

 
 -Rob




signature.asc
Description: Digital signature

Re: making sound work in Jessie - how?

2014-12-15 Thread Ric Moore


On 12/13/2014 09:40 PM, Paul E Condon wrote:

On 20141213_1926-0500, Ric Moore wrote:

On 12/13/2014 06:43 PM, Paul E Condon wrote:


What packages should I make sure are properly installed?


pavucontrol is usually missed. You need it to admin pulse. :) Ric
--
My father, Victor Moore (Vic) used to say:
There are two Great Sins in the world...
..the Sin of Ignorance, and the Sin of Stupidity.
Only the former may be overcome. R.I.P. Dad.
Linux user# 44256



Thanks for the email. But perhaps you could give me more.
I think my netinstall missed a whole bunch of stuff, like
the people configuring the install task package forgot
ot include a big bunch of stuff. When you installed the
sound on you computer what did you install manually,
not just the one that you are always kicking yourself for
forgetting, the nine yards.


You should have synaptic installed to help you select packages first. I 
couldn't live without it! Then make sure you have alsa installed 
completely. next search on pulse and install pavucontrol which is not 
installed by default. I've bitched about that, as you cannot admin pulse 
without it.


So, for sound, alsa is what everything depends on. So, run alsamixer 
from a terminal command line. Make sure your audio devices are not muted 
and sound levels a point or two from being 100% high. If alsa doesn't 
work, pulse has no chance since it sits on top of alsa.


Then run pavucontrol and you'll get a graphical admin front-end for 
pulse. .




--
My father, Victor Moore (Vic) used to say:
There are two Great Sins in the world...
..the Sin of Ignorance, and the Sin of Stupidity.
Only the former may be overcome. R.I.P. Dad.
Linux user# 44256


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

Archive: https://lists.debian.org/548f2156.4050...@gmail.com

Re: How is typical home computer used today?

2014-12-15 Thread Ric Moore


On 12/14/2014 04:38 PM, John Hasler wrote:

berenger.morel writes:

In France, the electric network provide 220V to everyone.


In the USA as well.  The normal wall outlets are 110 but 220 is brought
into the house and used for things like stoves.  The power utility's
transformer has a 220V secondary with a grounded center tap so that you
get 220V line to line or 110 from either line to neutral.  110V outlets
are distributed equally between the two sides so as to balance the load.
The usual service is 200 amps at 220V so you could run your mainframe.



Not without dimming the lights some. :) Ric



--
My father, Victor Moore (Vic) used to say:
There are two Great Sins in the world...
..the Sin of Ignorance, and the Sin of Stupidity.
Only the former may be overcome. R.I.P. Dad.
Linux user# 44256


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

Archive: https://lists.debian.org/548f25f8.3040...@gmail.com

Re: About Testing Freeze and KDE

The Wanderer wrote:
 Bob Proulx wrote:
  Good!  Then you saw that I did answer your question!  :-)
  
  As I said...  The reason that KDE 4.14.3 isn't in Jessie is because
  when Jessie froze KDE 4.14.2 was the latest available.  KDE 4.14.3
  was announced on 2014-Nov-11 several days *after* the freeze on
  2014-Nov-05.  That was after the freeze.  At the time of the freeze
  KDE 4.14.3 *did not exist*.  Asking why 4.14.3 isn't in Jessie is
  the same question as asking why 4.14.4 isn't in Jessie.  Because
  4.14.4 doesn't exist yet.
 
 No, it isn't the same question, because 4.14.3 does exist now; it just
 didn't when the freeze took place.

Uhm...  But that is the entire point of freeze!  What does freeze
mean to you?  Since Jessie is frozen and it was frozen *before* KDE
4.14.3 existed means that KDE 4.14.3 can't have been in it.

I think this is going to become a discussion of the process for
making a release.  That is okay.  But that does seem like a different
topic to me.

 Referring back to the OP, the original question was whether the version
 currently in testing would be updated prior to the release, and whether
 it wouldn't make sense to do so - the latter of which is essentially...

A couple of points.  One is that anyone is free to submit a wishlist
bug in the BTS requesting a newer version be packaged into the
archive.  Those requests happen all of the time.  If there is a newer
version and someone specifically wants it then they are free to submit
a bug asking for it.

However IMNHO it isn't enough to ask for it simply because the version
number has gotten larger.  Packaging takes effort.  A lot of upstreams
(talking random packages here) churn through a lot of releases and not
every release is suitable for packaging.  This can create a lot of
thrash and make-work for packagers.  Therefore packagers often wait
and see and then only package up what ends up becoming the good
versions and skipping the ones in between.

Therefore if someone wants a newer version with a BTS wishlist I think
they should say specifically what features or bug fixes they want from
the newer version.  Version X.Y fixes Bug#123 and includes the new
feature Z.  If they can enumerate out what they want then great.
That adds weight to why a new package should be made (and why in
freeze that the release team should approve the exception).  But if
they can't list anything specific they want from the new version then
that also says something too.

Another point is that asking us here on debian-user is going to get a
lot of opinions none of which matter.  The KDE maintainers are the
ones to ask this question.  They have been maintaining it.  They will
know what they are thinking they will do for the future.  Asking us is
fine but no one except the KDE maintainers will know what they are
planning.

Another point is that since Jessie is being prepared for release it
has entered freeze.  That changes the process for upgrades through Sid
Untable into Testing and now requires an exception from the release
team.

  This is really an extremely simple case.  In order to get a newer
  version of KDE into Jessie a) someone would need to package it into
  Debian Unstable which I am sure will happen and b) the release team
  would need to approve it into Jessie.  Unless the release team
  approves it Jessie will release with the version that existed at the
  time of the freeze.  Simple!
 
 ...asking why these steps would not happen. (Particularly given that
 something at least outwardly similar seems to have happened with GNOME,
 as pointed out in a response by Liam O'Toole.)

Talking about GNOME triggers two comments.  One is that the GNOME
maintainers are not the same people as the KDE maintainers as far as I
know.  The two groups don't need to operate the same.  Most of the
different groups in Debian have their own agenda and operate
differently.  And secondly I will say enough said about GNOME and
systemd in Debian.

 Possibly the answer is that it (probably) _will_ happen, or possibly the
 answer is that there are reasons why KDE 4.14.3 is not suitable for a
 freeze exception even though GNOME 3.14.2 was, or possibly the answer is
 something else. (I'm not attempting to address that myself.)

Complete agreement.

 But a flippant response with a generic because the freeze means no
 updates, which is essentially what I interpret you as having said
 (albeit without as much detail as you gave), does not seem to really
 address the question as I understand it.

I am sorry you read my postings as flippant.  They were not written
flippantly from my perspective.  I created them to be as factual and
as descriptive as I was capable of making them.

It is sometimes hard judgement to make between answering an X-Y
question by answering X or by guessing Y and answering about Y.
I think the real question here is, Why does Jessie need to freeze?

For users of Stable the goal is obvious.  It is part of the process of
making a new release.

For

Re: Machine hangs at boot

Just for the hack of it, I tried startx and the system hangs. So it seems to me 
that it is server issues. Is that possible to look at server logs? Where are 
they located?

berenger.mo...@neutralite.org wrote:



Le 15.12.2014 14:00, Frederic Marchal a écrit :
 On Monday 15 December 2014 15:48:40 German wrote:
 Oh OK, there really is such a disk. Unfortunately I can't remove it. 
 My
 machine was running smoothly for about two months and after kernel 
 update
 this thing happened.

 Is sdb supposed to contain a valid partition?

 If it is supposed to be a valid disk, then, I would say it is now 
 corrupted…

 How frequently do you reboot your computer? If you reboot it
 infrequently and
 just rebooted it after the kernel update, then the disk failure may
 have been
 noticed only then.

 As the kernel driver handling that disk is a generic scsi, I doubt a 
 kernel
 bug affects your system.

 The ata driver can't be blamed here either as it is recognizing sda
 just fine.

 Now, something else may be holding the boot sequence for 26 seconds 
 just
 before mounting the swap partition on sda3 but you ruled out a 
 corruption on
 sda2. And we lack evidences that any other peripheral is behaving 
 strangely.

 Frederic

Well I had similar... lag... in testing, since few months, because of 
dbus. Several other people had it, too. It could be an update of udev 
which introduced it.


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/c29b48063c885f15dc5a0863b5a44...@neutralite.org

Re: About Testing Freeze and KDE

Andrei POPESCU wrote:
 Stretch and Buster were only meant as example, please consider my 
 nitpick to have been:
 
 The name of the next release is generally known, latest by the time 
 of the freeze of the previous one.

Sure.  :-)

 In this particular case the Release Team was slightly late, but they 
 made up for it by announcing the name also for the next release, which 
 makes the lives of a few package maintainers easier.

I am curious.  How does knowing the names further in advance make some
things easier?

For my part I think it confusing that a release candidate will have a
lifecycle of two years (give or take).  During that lifecycle it will
start out identical to the previous and then grow into the new.  We
will have two years of email talking about Jessie and all of that will
be about something different than the Jessie that releases next year.

For example two years ago if you had installed Jessie you would have
gotten sysvinit and today if you install Jessie you will get systemd.
That both of those are facts make naming troublesome.  Later when
searching the archives for a problem in Jessie we find all manor of
postings that talk about Jessie but are actually referring to quite a
different set of bits.

It isn't practical to do so because the name gets embedded in various
places but in an ideal world I would dream of a process where the
release would always be referred to as $release or something and then
upon the day of freeze and release it then was given its name.  Then
we would have a Jessie that once named would then refer to the
release from that point forward.  Not practical to implement this in
any way I can imagine but I can still dream about it because it would
be better than we have now.

Bob


signature.asc
Description: Digital signature

Re: multihomed server with ipv6

li...@onemanifest.net wrote:
 I’ve setup static adressing for both NICs for ipv4 and ipv6 like this:

I see you have good answers from others.  Great.  But I didn't see
these comments that I am going to make.

   # The primary LAN network interface
   allow-hotplug eth0
   iface eth0 inet static
 address 192.168.1.xx
 netmask 255.255.255.0
 network 192.168.1.0
 broadcast 192.168.1.255
 gateway 192.168.1.1
 # dns-* options are implemented by the resolvconf package, if installed
 dns-nameservers 192.168.1.1
 dns-search somedomain.tld

Delete the network and broadcast lines.  Those are redundant with the
netmask.  Specify only the netmask and let the program calculate it's
own netmask and network values.  The ability to separately specify
network and broadcast is for flexibility but I have never personally
seen a configuration that needed those set separately from netmask.

   # The secondary DMZ network interface
   allow-hotplug eth1
   iface eth1 inet static
 address 192.168.0.xx
 netmask 255.255.255.0
 network 192.168.0.0
 broadcast 192.168.0.255
 gateway 192.168.0.1
 # dns-* options are implemented by the resolvconf package, if installed
 dns-nameservers 192.168.0.1
 dns-search somedomain.tld

Same thing here.  Delete the network and broadcast lines.

Bob


signature.asc
Description: Digital signature

Re: About Testing Freeze and KDE

2014-12-15 Thread Don Armstrong

On Mon, 15 Dec 2014, Bob Proulx wrote:
 I am curious. How does knowing the names further in advance make some
 things easier?

1) Tools can include support for releases which are +1 and +2.

For example, debootstrap needs to know the names of the release so you
can install it. Lots of other tools too.

 That both of those are facts make naming troublesome. Later when
 searching the archives for a problem in Jessie we find all manor of
 postings that talk about Jessie but are actually referring to quite a
 different set of bits.

There's not really anything that can be done about this, beyond people
avoiding describing what is currently testing as what will be the stable
release Jessie.

And frankly, even Jessie will have changes over its lifetime. Older
posts are always going to be old; they may be accurate now, or they may
not be.

-- 
Don Armstrong  http://www.donarmstrong.com

Clean living is less fun
and you wind up feeling stupid
when you still die.
 -- a softer world #489
http://www.asofterworld.com/index.php?id=489


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20141215194749.gs31...@rzlab.ucr.edu

Re: Upgrading from squeeze to wheezy

James Allsopp wrote:
 I've not had access to my machine for a while, and I've just tried to do an
 upgrade from squeeze to wheezy using the instructions found here;
 http://www.howtoforge.com/how-to-upgrade-debian-squeeze-to-wheezy

Why are you using those instructions instead of the official Debian
ones?

  https://www.debian.org/releases/stable/amd64/release-notes/index.en.html

 and I got to the
 aptitude full-upgrade
 part which seemed to hang

If you read the howtoforge instructions carefully you will see that it
says:

  Instead of using apt-get upgrade and apt-get dist-upgrade, you can
  also use the following commands, but please note that on
  http://www.debian.org/releases/wheezy/amd64/release-notes/ch-upgrading.en.html
  it reads The upgrade process for some previous releases recommended
  the use of aptitude for the upgrade. This tool is not recommended for
  upgrades from squeeze to wheezy.. For me, aptitude has worked fine
  for all Squeeze to Wheezy upgrades so far.

Therefore when you are using the aptitude full-upgrade part above
you are explicitly going outside of the official recommended
procedure.

I strongly recommend the apt-get upgrade and apt-get dist-upgrade
approach instead as documented in the offical Debian release notes.

 I've tried
 dpkg --configure -a
 apt-get -f install
 
 but can't get anything to work.

Did you forget to apt-get update after changing the sources.list file.

  apt-get update

Systems can be complex with complex interactions.  If every system
were identical then it would be easy to test those and produce a plan
that would work for everyone.  So first let me say that it is hard
because only your system is your system.

 Here's a list of the objections, but I don't know how to solve them, short
 of installing every package manually.
 
 If you've any ideas, I would be grateful to receive them,

My official recommendation would be to follow the instructions in the
release notes as that is the best complete source of knowledge on how
to upgrade.

I will guess that your problem here is some additional undesired
source in your /etc/apt/sources.list or /etc/apt/sources.list.d/*
files.

Ensure you have a good system back.

Reset sources.list back to Squeeze:
  apt-get update
  apt-get upgrade
  apt-get dist-upgrade  # check removal list carefully!
  apt-get autoremove
  dpkg -l | grep ^rc
  apt-get purge ...
  find /etc -name '*.dpkg-*' -o -name '*.ucf-*'
  rm ...
  dpkg-query -W -f='${Conffiles}\n' | awk '$NF==obsolete{print$1}'
  apt-get purge ...

Reset sources.list to Wheezy:
  apt-get update
  apt-get upgrade
  apt-get dist-upgrade  # check removal list carefully!
  apt-get autoremove
  dpkg -l | grep ^rc
  apt-get purge ...
  find /etc -name '*.dpkg-*' -o -name '*.ucf-*'
  rm ...
  dpkg-query -W -f='${Conffiles}\n' | awk '$NF==obsolete{print$1}'
  apt-get purge ...

As you can see I suggest cleaning to be very important.  Leaving a lot
of the lint behind can and does often cause real upgrade problems that
does not exist on a clean system.

When there is a conflict here I defer to the official Debian release
notes.

Bob


signature.asc
Description: Digital signature

Is something wrong with Debian mirrors today (12/15/2014)?


Hi,

I'm running Debian testing fully updated as of 12/14. Contents of 
/etc/apt/sources.list:


deb http://ftp.us.debian.org/debian testing main contrib non-free
deb-src http://ftp.us.debian.org/debian testing main contrib non-free

deb http://ftp.debian.org/debian/ jessie-updates main contrib non-free
deb-src http://ftp.debian.org/debian/ jessie-updates main contrib non-free

deb http://security.debian.org/ jessie/updates main contrib non-free
deb-src http://security.debian.org/ jessie/updates main contrib non-free

This version reflects editing I did to it while doing a dist-upgrade 
from Wheezy to Jessie immediately after installation of Wheezy from a 
live CD.


Upgrades have been working flawlessly ever since the date of 
installation some weeks ago.


Today, both apt-get and aptitude fail to update.

apt-get output from apt-get update (It just stops. You can see the 
Ctrl-C I issue to interrupt the process after it hangs.)


0% [Connecting to ftp.us.debian.org (2610:148:1f10:3::89)] [Connecting 
to ftp.debian.org (2001:610:1908:b000::148:12)] [Connecting to s^C


aptitude output in interactive mode after issuing u update keypress
(Please excuse the line reformatting of the third line due to allowed 
line length set in my mail client.)


Connecting to ftp.us.debian.org (2610:148:1f10:3::89)
Connecting to ftp.debian.org (2001:610:1908:b000::148:12)
Connecting to security.debian.org (2607:ea00:101:3c0b:207:e9ff:fe00:e595)

A quick look at https://mirror.debian.org/status shows the mirrors to be 
unavailable.


I cannot get to https://www.google.com, but http://www.bing.com comes up 
instantly.


Pinging of anything by name or by IP works perfectly.

Logging into a remotely located VPN and trying all of these functions 
from there results in exactly the same findings.


Is the Internet broken, and if so, I'm wondering why am I seeing no 
traffic about that here on debian-user or at any news site?


Did I miss an announcement or something?

8-)

Thanks,
JP


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

Archive: https://lists.debian.org/548f494f.9030...@comcast.net

Re: Is something wrong with Debian mirrors today (12/15/2014)?

2014-12-15 Thread Lisi Reisz

On Monday 15 December 2014 20:49:19 Jape Person wrote:
 A quick look at https://mirror.debian.org/status shows the mirrors to be
 unavailable.

 I cannot get to https://www.google.com, but http://www.bing.com comes up
 instantly.

Just tried.  There is no problem with google or bing, but a problem with 
https://mirror.debian.org/status

However, I just did an aptitude update followed by a full-upgrade (for one 
security uopdate!) without any problems at all.  Sources.list:
quote
deb http://ftp.uk.debian.org/debian wheezy main contrib non-free
deb-src http://ftp.uk.debian.org/debian wheezy main contrib non-free

deb http://ftp.debian.org/debian/ wheezy-updates main contrib non-free
deb-src http://ftp.debian.org/debian/ wheezy-updates main contrib non-free

deb http://security.debian.org/ wheezy/updates main contrib non-free
deb-src http://security.debian.org/ wheezy/updates main contrib non-free

deb http://ftp.at.debian.org/debian wheezy-backports main contrib non-free

deb http://mozilla.debian.net/ wheezy-backports iceweasel-release

# deb http://ppa.launchpad.net/chromium-daily/ppa/ubuntu lucid main

deb http://www.deb-multimedia.org wheezy main non-free

# deb http://depot-trinity.dotriver.eu/trinity-v3.5.13/debian wheezy main
# deb http://depot-trinity.dotriver.eu/trinity-builddeps-v3.5.13/debian wheezy 
main

deb http://mirror.ntmm.org/trinity/trinity-v3.5.13/debian wheezy main
deb http://mirror.ntmm.org/trinity/trinity-builddeps-v3.5.13/debian wheezy 
main

deb http://ppa.quickbuild.pearsoncomputing.net/slavek-banko/axis/ubuntu wheezy 
main
/quote

Lisi


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/201412152115.18144.lisi.re...@gmail.com

Re: Is something wrong with Debian mirrors today (12/15/2014)?

2014-12-15 Thread chris

Do you actually have working ipv6 connectivity because those hostnames are
resolving to v6 IP addresses
On Dec 15, 2014 3:50 PM, Jape Person jap...@comcast.net wrote:

 Hi,

 I'm running Debian testing fully updated as of 12/14. Contents of
 /etc/apt/sources.list:

 deb http://ftp.us.debian.org/debian testing main contrib non-free
 deb-src http://ftp.us.debian.org/debian testing main contrib non-free

 deb http://ftp.debian.org/debian/ jessie-updates main contrib non-free
 deb-src http://ftp.debian.org/debian/ jessie-updates main contrib non-free

 deb http://security.debian.org/ jessie/updates main contrib non-free
 deb-src http://security.debian.org/ jessie/updates main contrib non-free

 This version reflects editing I did to it while doing a dist-upgrade from
 Wheezy to Jessie immediately after installation of Wheezy from a live CD.

 Upgrades have been working flawlessly ever since the date of installation
 some weeks ago.

 Today, both apt-get and aptitude fail to update.

 apt-get output from apt-get update (It just stops. You can see the
 Ctrl-C I issue to interrupt the process after it hangs.)

 0% [Connecting to ftp.us.debian.org (2610:148:1f10:3::89)] [Connecting to
 ftp.debian.org (2001:610:1908:b000::148:12)] [Connecting to s^C

 aptitude output in interactive mode after issuing u update keypress
 (Please excuse the line reformatting of the third line due to allowed line
 length set in my mail client.)

 Connecting to ftp.us.debian.org (2610:148:1f10:3::89)
 Connecting to ftp.debian.org (2001:610:1908:b000::148:12)
 Connecting to security.debian.org (2607:ea00:101:3c0b:207:e9ff:fe00:e595)

 A quick look at https://mirror.debian.org/status shows the mirrors to be
 unavailable.

 I cannot get to https://www.google.com, but http://www.bing.com comes up
 instantly.

 Pinging of anything by name or by IP works perfectly.

 Logging into a remotely located VPN and trying all of these functions from
 there results in exactly the same findings.

 Is the Internet broken, and if so, I'm wondering why am I seeing no
 traffic about that here on debian-user or at any news site?

 Did I miss an announcement or something?

 8-)

 Thanks,
 JP


 --
 To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a
 subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
 Archive: https://lists.debian.org/548f494f.9030...@comcast.net

Re: multihomed server with ipv6

2014-12-15 Thread Pascal Hambourg

one...@onemanifest.net a écrit :
 - Since this server will be used for running openvz containers, I'll probably 
 have to create explicit routes for each (virtual) network to the subnets the 
 NICs are connected to and define an explicit gateway for each subnet?

If the server does routing for the containers, you'll run into the same
problem as above. You'll have to use advanced routing and setup multiple
routing tables based on source address or inbound interface, containing
each a different default route.

 However, while doing some more research on this matter, it occurred to me 
 that I can make life a lot easier on myself by using bridges. (Sorry if I 
 sound very n00b-isch here) I think I could do the following:
 - configure only the LAN NIC on the host, so I get admin access to the host 
 from the LAN
 - create a bridge on each NIC
 - connect the containers to the appropriate bridge for either LAN or DMZ, 
 setting up networking on each container independently.

When adding interfaces to a bridge, you must configure IP only on the
bridge, not on the bridged interfaces. There are exceptions, but only
used in very special cases such as brouters (bridge-routers) when you
know exactly what you are doing.

 This way the host is neatly isolated from the DMZ and the containers and the 
 setup is far simpler. 

Yes, the server does not have to do routing for the containers.

 Then I did a ping6 to a host in LAN subnet, from the DMZ NIC on the server.

What exact command did you use ? ping6 -I interface ?
I don't think you can do that and override the routing table. All you
can do is force the source address.

 I saw that the ping command reported using the LAN ip6 
 (2001:::3::20/64) as a source ip, instead of the DMZ one 
 (2001:::2::20/64) as I expected it to do.

It probably sent the packets on the LAN interface.
I know there are different versions of ping6, but mine (from
iputils-ping) just seems to ignore the interface passed with -I.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/548f544d@plouf.fr.eu.org

Re: Unable to install bootloader on software raid

2014-12-15 Thread Pascal Hambourg

Sven Hartge a écrit :
 Darac Marjal mailingl...@darac.org.uk wrote:
 
 I think the problem is that, depending on the RAID level, the BIOS won't
 be able to read the disks in order to load GRUB. If you're running
 RAID0, then you're in luck; both drives appear as normal disks and all
 that RAID does is ensure they are kept identical. If you're running
 RAID1, though, then each disk is a chopped-up mess of data and you NEED
 the RAID to provide the hint that half the data is on another device.
 
 It's the other way round: RAID0 is striped, aka chopped up mess and
 RAID1 are mirrored disks.

Besides, the Linux RAID arrays usually do no reside on whole raw disks
but on RAID partitions. GRUB's boot image and core image are usually
installed on each disk outside these partitions. This way all the
sectors needed to load GRUB's core image can be found on each single
disk, regardless of the RAID level.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/548f5683.6010...@plouf.fr.eu.org

Re: How to print duplex when using lpr

2014-12-15 Thread Kevin O'Gorman

On Thu, Dec 11, 2014 at 11:27 AM, Don Armstrong d...@debian.org wrote:

 On Thu, 11 Dec 2014, Kevin O'Gorman wrote:
  I sometimes use lpr in a pipeline getting postscript from groff. My
  printer (HP CP2025dn) has a duplexer and I'd like to use it. I could
  look up the Postscript for that, but I'm wondering if there's a way to
  force either of groff or lpr to do it for me.

 If you're using cups, you can do the following:

 lp -o sides=two-sided-long-edge filename;

 man lp; for details.

 Nice.  Works on lpr too, but the man page doesn't show it.
Thanks.

-- 
Kevin O'Gorman
#define QUESTION ((bb) || (!bb))   /* Shakespeare */

Please consider the environment before printing this email.

Re: fsck on boot in Jessie

2014-12-15 Thread Andrei POPESCU

On Vi, 12 dec 14, 21:29:47, Jape Person wrote:
 
 At least I think I've got that right. I'm sleepy, and I'm even dumber than
 normal because of antihistamines. If I'm wrong, I'm sure someone will offer
 a correction.

Yes, you are giving me too much credit :)

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser
Offtopic discussions among Debian users and developers:
http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic
http://nuvreauspam.ro/gpg-transition.txt


signature.asc
Description: Digital signature

Re: fsck on boot in Jessie

2014-12-15 Thread Andrei POPESCU

On Vi, 12 dec 14, 19:08:37, Paul E Condon wrote:
 
 Was there no one in the group discussion who was aware of
 systemd-fsck ?? Surely, if there was (s)he would have
 enlighten the rest of us as to this fact and the discussion
 would have been far less looong.

The discussion started because systemd-fsck doesn't allow interruptions 
;)

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser
Offtopic discussions among Debian users and developers:
http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic
http://nuvreauspam.ro/gpg-transition.txt


signature.asc
Description: Digital signature

Re: Is something wrong with Debian mirrors today (12/15/2014)?


On 12/15/2014 04:15 PM, Lisi Reisz wrote:

On Monday 15 December 2014 20:49:19 Jape Person wrote:

A quick look at https://mirror.debian.org/status shows the mirrors to be
unavailable.

I cannot get to https://www.google.com, but http://www.bing.com comes up
instantly.


Just tried.  There is no problem with google or bing, but a problem with
https://mirror.debian.org/status

However, I just did an aptitude update followed by a full-upgrade (for one
security uopdate!) without any problems at all.  Sources.list:
quote
deb http://ftp.uk.debian.org/debian wheezy main contrib non-free
deb-src http://ftp.uk.debian.org/debian wheezy main contrib non-free

deb http://ftp.debian.org/debian/ wheezy-updates main contrib non-free
deb-src http://ftp.debian.org/debian/ wheezy-updates main contrib non-free

deb http://security.debian.org/ wheezy/updates main contrib non-free
deb-src http://security.debian.org/ wheezy/updates main contrib non-free

deb http://ftp.at.debian.org/debian wheezy-backports main contrib non-free

deb http://mozilla.debian.net/ wheezy-backports iceweasel-release

# deb http://ppa.launchpad.net/chromium-daily/ppa/ubuntu lucid main

deb http://www.deb-multimedia.org wheezy main non-free

# deb http://depot-trinity.dotriver.eu/trinity-v3.5.13/debian wheezy main
# deb http://depot-trinity.dotriver.eu/trinity-builddeps-v3.5.13/debian wheezy
main

deb http://mirror.ntmm.org/trinity/trinity-v3.5.13/debian wheezy main
deb http://mirror.ntmm.org/trinity/trinity-builddeps-v3.5.13/debian wheezy
main

deb http://ppa.quickbuild.pearsoncomputing.net/slavek-banko/axis/ubuntu wheezy
main
/quote

Lisi



Hi, Lisi!

Thanks for the response.

Yeah it worked for -- and for everybody else that didn't have a moron 
(namely me) setting up their local network.


;)

What happened was that our Comcast modem died yesterday and got replaced 
by a tech. The new modem had IPv6 enabled, and I didn't notice.


So...when half of the Internet looks broken, and the local network looks 
okay, and no one is talking about the half-broken Internet 
online...yeah, it's misconfiguration of the local network.




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

Archive: https://lists.debian.org/548f6022.30...@comcast.net

Re: Is something wrong with Debian mirrors today (12/15/2014)?


On 12/15/2014 04:22 PM, chris wrote:

Do you actually have working ipv6 connectivity because those hostnames are
resolving to v6 IP addresses
On Dec 15, 2014 3:50 PM, Jape Person jap...@comcast.net wrote:



Hi, Chris.

Thanks for the reply. It put me on the right track. I don't know why I 
wasn't paying attention to the actual content of what I was seeing. It 
was the other issues I was seeing plus the weird findings at the mirror 
status site that misled my feeble mind.


No, I don't use IPv6, but the new replacement cable modem installed by a 
Comcast tech yesterday had it enabled.


I looked at the new modem's settings, turned off IPv6 there (and in my 
router and in my network settings), and everything's okay now. That'll 
teach to me to let the default settings sit in network-manager and the 
router's IPv6 settings!


You fixed about half of the Internet today -- at least for me! Yay!

;)

Thanks,
JP



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

Archive: https://lists.debian.org/548f64fa.5000...@comcast.net

Re: Is Debian live 7.7 will run on athlon 5350?

2014-12-15 Thread Dan Ritter

On Sun, Dec 14, 2014 at 04:12:16PM +0400, German wrote:
 I am asking this because I was unable to boot the previous version a couple 
 month ago. Thanks

Yes, I have a full Debian 7.7 running on a 5350 right now. The
motherboard is an MSI AM1I. Everything I've tried on it works -
I have not tried sound or X11, but I wouldn't expect any 
problems with either.

-dsr-


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20141215224614.gn30...@randomstring.org

Re: System is stuck at boot

2014-12-15 Thread Dan Ritter

On Sun, Dec 14, 2014 at 09:40:09PM +0400, German wrote:
 While the system mentioned is lubuntu, I am wondering if are there any 
 experts who can look at my dmesg.log file and tell me what is wrong. This 
 would be extremely appreciated.

There are no errors in that boot sequence. What are you
experiencing?

If you get a black, unresponsive screen, it is likely that X is 
not configured properly. Try passing init=/bin/sh to the
kernel. If it boots to a root prompt, then you can go and 
experiment on X.

-dsr-


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20141215224933.go30...@randomstring.org

Re: Is Debian live 7.7 will run on athlon 5350?

Thank you, I guess it is a time to install

Dan Ritter d...@randomstring.org wrote:

On Sun, Dec 14, 2014 at 04:12:16PM +0400, German wrote:
 I am asking this because I was unable to boot the previous version a couple 
 month ago. Thanks

Yes, I have a full Debian 7.7 running on a 5350 right now. The
motherboard is an MSI AM1I. Everything I've tried on it works -
I have not tried sound or X11, but I wouldn't expect any 
problems with either.

-dsr-

Re: System is stuck at boot

Yes, I got a black, unresponsive screen. I went to recovery mode already, so I 
have a shell root access. Are any x logs that can be examined? Thanks

Dan Ritter d...@randomstring.org wrote:

On Sun, Dec 14, 2014 at 09:40:09PM +0400, German wrote:
 While the system mentioned is lubuntu, I am wondering if are there any 
 experts who can look at my dmesg.log file and tell me what is wrong. This 
 would be extremely appreciated.

There are no errors in that boot sequence. What are you
experiencing?

If you get a black, unresponsive screen, it is likely that X is 
not configured properly. Try passing init=/bin/sh to the
kernel. If it boots to a root prompt, then you can go and 
experiment on X.

-dsr-

Re: fsck on boot in Jessie


On 12/15/2014 05:22 PM, Andrei POPESCU wrote:

On Vi, 12 dec 14, 21:29:47, Jape Person wrote:


At least I think I've got that right. I'm sleepy, and I'm even dumber than
normal because of antihistamines. If I'm wrong, I'm sure someone will offer
a correction.


Yes, you are giving me too much credit :)

Kind regards,
Andrei



Well, I have mentioned you a few times lately -- not only in the spirit 
of recognizing you for helping me with my particular problem, but also 
to help others find the context of that help in the thread.


Besides, it would be kind of hard to give you too much credit. You're 
one of the most helpful people on the list, and you manage to be one of 
the more tactful participants here, too.


Best regards,
JP


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

Archive: https://lists.debian.org/548f6ce3.4030...@comcast.net

Re: Upgrading from squeeze to wheezy

2014-12-15 Thread James Allsopp

Thanks Bob,
Hit a snag, I thought the upgrade would update the kernel and it's left me
with a mismatch. I can't now log into the machine, no ssh and no keyboard.
I think I'm going to try and use a netinst disk to rescue the system,
unless you've any other ideas? I remember in Linux a long time ago there
was a method to step through the boot sequence item by item. Could I wait
until the network came up, then drop into a shell?

Thanks
James

On 15 December 2014 at 20:10, Bob Proulx b...@proulx.com wrote:

 James Allsopp wrote:
  I've not had access to my machine for a while, and I've just tried to do
 an
  upgrade from squeeze to wheezy using the instructions found here;
  http://www.howtoforge.com/how-to-upgrade-debian-squeeze-to-wheezy

 Why are you using those instructions instead of the official Debian
 ones?

   https://www.debian.org/releases/stable/amd64/release-notes/index.en.html

  and I got to the
  aptitude full-upgrade
  part which seemed to hang

 If you read the howtoforge instructions carefully you will see that it
 says:

   Instead of using apt-get upgrade and apt-get dist-upgrade, you can
   also use the following commands, but please note that on

 http://www.debian.org/releases/wheezy/amd64/release-notes/ch-upgrading.en.html
   it reads The upgrade process for some previous releases recommended
   the use of aptitude for the upgrade. This tool is not recommended for
   upgrades from squeeze to wheezy.. For me, aptitude has worked fine
   for all Squeeze to Wheezy upgrades so far.

 Therefore when you are using the aptitude full-upgrade part above
 you are explicitly going outside of the official recommended
 procedure.

 I strongly recommend the apt-get upgrade and apt-get dist-upgrade
 approach instead as documented in the offical Debian release notes.

  I've tried
  dpkg --configure -a
  apt-get -f install
 
  but can't get anything to work.

 Did you forget to apt-get update after changing the sources.list file.

   apt-get update

 Systems can be complex with complex interactions.  If every system
 were identical then it would be easy to test those and produce a plan
 that would work for everyone.  So first let me say that it is hard
 because only your system is your system.

  Here's a list of the objections, but I don't know how to solve them,
 short
  of installing every package manually.
 
  If you've any ideas, I would be grateful to receive them,

 My official recommendation would be to follow the instructions in the
 release notes as that is the best complete source of knowledge on how
 to upgrade.

 I will guess that your problem here is some additional undesired
 source in your /etc/apt/sources.list or /etc/apt/sources.list.d/*
 files.

 Ensure you have a good system back.

 Reset sources.list back to Squeeze:
   apt-get update
   apt-get upgrade
   apt-get dist-upgrade  # check removal list carefully!
   apt-get autoremove
   dpkg -l | grep ^rc
   apt-get purge ...
   find /etc -name '*.dpkg-*' -o -name '*.ucf-*'
   rm ...
   dpkg-query -W -f='${Conffiles}\n' | awk '$NF==obsolete{print$1}'
   apt-get purge ...

 Reset sources.list to Wheezy:
   apt-get update
   apt-get upgrade
   apt-get dist-upgrade  # check removal list carefully!
   apt-get autoremove
   dpkg -l | grep ^rc
   apt-get purge ...
   find /etc -name '*.dpkg-*' -o -name '*.ucf-*'
   rm ...
   dpkg-query -W -f='${Conffiles}\n' | awk '$NF==obsolete{print$1}'
   apt-get purge ...

 As you can see I suggest cleaning to be very important.  Leaving a lot
 of the lint behind can and does often cause real upgrade problems that
 does not exist on a clean system.

 When there is a conflict here I defer to the official Debian release
 notes.

 Bob

Re: fsck on boot in Jessie

2014-12-15 Thread Lisi Reisz

On Monday 15 December 2014 23:21:07 Jape Person wrote:
 Besides, it would be kind of hard to give you too much credit. You're
 one of the most helpful people on the list, and you manage to be one of
 the more tactful participants here, too.

Hear, hear.

Lisi


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/201412160010.42729.lisi.re...@gmail.com

Re: Kernel failure

2014-12-15 Thread Go Linux

No one?  FWIW.  Haven’t had a problem since I posted this several days ago.  
Any thoughts?



On Sat, 12/13/14, golinux goli...@riseup.net wrote:

 Subject: Kernel failure
 To: Debian User debian-user@lists.debian.org
 Date: Saturday, December 13, 2014, 1:40 AM

On squeeze LTS.  Upgraded the kernel 2 days ago.  Everything was going
OK.  Then out of nowhere I get a kernel failure popup after coming out
of suspend. Everything seems to be working OK so I've just gone on about
my business.  But don't want to get bit down the road.  What should I
do?  This has never happened in the 10 years I've been using Linux so
I'm a little lost.  Here's the log:

Kernel failure message 1:
[ cut here ]
WARNING: at
/build/linux-2.6-bBJNRm/linux-2.6-2.6.32/debian/build/source_i386_none/kernel/rcutree.c:277
rcu_exit_nohz+0x43/0x5d()
Hardware name: P35-DS3L
Modules linked in:
ata_piix :00:1f.5: PCI INT B - GSI 19 (level, low) - IRQ 19
  xt_limit xt_tcpudp ipt_LOG
ata_piix :00:1f.5: setting latency timer to 64
  ipt_MASQUERADE xt_DSCP ipt_REJECT nf_conntrack_irc nf_conntrack_ftp
xt_state sco bridge stp bnep rfcomm acpi_cpufreq l2cap bluetooth
cpufreq_powersave rfkill cpufreq_conservative cpufreq_stats
cpufreq_userspace ppdev lp binfmt_misc fuse iptable_nat nf_nat
nf_conntrack_ipv4 nf_conntrack nf_defrag_ipv4 iptable_mangle
iptable_filter ip_tables x_tables ext4 jbd2 crc16 it87 hwmon_vid
coretemp loop snd_hda_codec_realtek snd_hda_intel i2c_i801 nvidia(P)
snd_hda_codec snd_hwdep parport_pc i2c_core processor snd_pcm snd_seq
snd_timer snd_seq_device evdev parport snd soundcore snd_page_alloc
pcspkr psmouse serio_raw ext3 jbd mbcache sg sr_mod cdrom sd_mod
crc_t10dif ata_generic uhci_hcd r8169 mii pata_jmicron thermal ata_piix
thermal_sys ehci_hcd libata button scsi_mod usbcore nls_base [last
unloaded: scsi_wait_scan]
Pid: 0, comm: swapper Tainted: PW  2.6.32-5-686 #1
Call Trace:
  [c10308fd] ? warn_slowpath_common+0x5e/0x8a
  [c1030933] ? warn_slowpath_null+0xa/0xc
  [c106f5b7] ? rcu_exit_nohz+0x43/0x5d
  [c104f6a5] ? tick_nohz_restart_sched_tick+0x6d/0x12d
  [c1002338] ? cpu_idle+0x9b/0xa3
---[ end trace 150783a4a64aa323 ]---

Please cc to the above address.


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/1418693852.46886.yahoomailba...@web163403.mail.gq1.yahoo.com

Re: Kernel failure

2014-12-15 Thread Burhan Hanoglu

On Tue, Dec 16, 2014 at 3:37 AM, Go Linux goli...@yahoo.com wrote:

 No one?  FWIW.  Haven’t had a problem since I posted this several days
 ago.  Any thoughts?

 

 On Sat, 12/13/14, golinux goli...@riseup.net wrote:

  Subject: Kernel failure
  To: Debian User debian-user@lists.debian.org
  Date: Saturday, December 13, 2014, 1:40 AM

 On squeeze LTS.  Upgraded the kernel 2 days ago.  Everything was going
 OK.  Then out of nowhere I get a kernel failure popup after coming out
 of suspend. Everything seems to be working OK so I've just gone on about
 my business.  But don't want to get bit down the road.  What should I
 do?  This has never happened in the 10 years I've been using Linux so
 I'm a little lost.  Here's the log:

 Kernel failure message 1:
 [ cut here ]
 WARNING: at

 /build/linux-2.6-bBJNRm/linux-2.6-2.6.32/debian/build/source_i386_none/kernel/rcutree.c:277
 rcu_exit_nohz+0x43/0x5d()
 Hardware name: P35-DS3L
 Modules linked in:
 ata_piix :00:1f.5: PCI INT B - GSI 19 (level, low) - IRQ 19
   xt_limit xt_tcpudp ipt_LOG
 ata_piix :00:1f.5: setting latency timer to 64
   ipt_MASQUERADE xt_DSCP ipt_REJECT nf_conntrack_irc nf_conntrack_ftp
 xt_state sco bridge stp bnep rfcomm acpi_cpufreq l2cap bluetooth
 cpufreq_powersave rfkill cpufreq_conservative cpufreq_stats
 cpufreq_userspace ppdev lp binfmt_misc fuse iptable_nat nf_nat
 nf_conntrack_ipv4 nf_conntrack nf_defrag_ipv4 iptable_mangle
 iptable_filter ip_tables x_tables ext4 jbd2 crc16 it87 hwmon_vid
 coretemp loop snd_hda_codec_realtek snd_hda_intel i2c_i801 nvidia(P)
 snd_hda_codec snd_hwdep parport_pc i2c_core processor snd_pcm snd_seq
 snd_timer snd_seq_device evdev parport snd soundcore snd_page_alloc
 pcspkr psmouse serio_raw ext3 jbd mbcache sg sr_mod cdrom sd_mod
 crc_t10dif ata_generic uhci_hcd r8169 mii pata_jmicron thermal ata_piix
 thermal_sys ehci_hcd libata button scsi_mod usbcore nls_base [last
 unloaded: scsi_wait_scan]
 Pid: 0, comm: swapper Tainted: PW  2.6.32-5-686 #1
 Call Trace:
   [c10308fd] ? warn_slowpath_common+0x5e/0x8a
   [c1030933] ? warn_slowpath_null+0xa/0xc
   [c106f5b7] ? rcu_exit_nohz+0x43/0x5d
   [c104f6a5] ? tick_nohz_restart_sched_tick+0x6d/0x12d
   [c1002338] ? cpu_idle+0x9b/0xa3
 ---[ end trace 150783a4a64aa323 ]---

 Please cc to the above address.

 Hmmm; Read-Copy Update Mechanism Looks like a disk drive is having
trouble waking up from suspend and resuming. Could be a bad disk drive, mb,
cable, or lack of enough power/current... I have seen this before with some
internal drives advertised as green, and with some external usb drives...

Burhan

Re: Upgrading from squeeze to wheezy

James Allsopp wrote:
 Thanks Bob,
 Hit a snag, I thought the upgrade would update the kernel and it's left me
 with a mismatch. I can't now log into the machine, no ssh and no keyboard.
 I think I'm going to try and use a netinst disk to rescue the system,
 unless you've any other ideas?

Using the install disk in rescue mode is an excellent idea.

 I remember in Linux a long time ago there was a method to step
 through the boot sequence item by item. Could I wait until the
 network came up, then drop into a shell?

I think using rescue mode would be easier than using single user mode
and trying to repair your system that way.  Both should work.  But the
installer will boot to a fully working rescue mode.  Then using it I
think would be easier than trying to single step through a broken
non-booting system.

Here is the official documentation for rescue mode:

  http://www.debian.org/releases/stable/i386/ch08s07.html.en

But that is fairly terse.  Let me say that the rescue mode looks just
like the install mode initially.  It will ask you keyboard and locale
questions and you might wonder if you are rescuing or installing!  But
it will have Rescue in the corners so that you can tell and be
assured.  Get the tool set up with keyboard, locale, timezone, and
similar and eventually it will give you a menu with a list of actions.

  Advanced options...
  Rescue mode
  keyboard
  ...starts networking...
  hostname
  domainname
  ...apt update release files...
  ...loading additional components, Retrieving udebs...
  ...detecting disks...

Then eventually it will get to a menu Enter rescue mode that will
ask what device to use as a root file system.  It will list the
partitions that it has automatically detected.  Select the appropriate
for your system.  Then continue.  At that point it presents a menu
Execute a shell in /dev/  That should get you a shell on your
system.  At that point you can execute apt-get commands and
grub-install and other things as needed.

Hopefully that will get you back to a point where you can then debug
and recover your system fully.

Good luck!

Bob



signature.asc
Description: Digital signature

Re: System is stuck at boot