RE: ssh user@ipv6 address, connect: Network is unreachable

[Mike Viau]

 On Tue, 23 Jul 2013 22:57:27 +0200 debian_1...@chubig.net wrote: Dear 
 basti,
 
 basti wrote:
  ssh: connect to host ipv6_address port 22: Network is unreachable
 
 if ipv6_address is not in your local network, you will either need
 a tunnel or connectivity from your ISP to get IPv6. So this:
  
  my ISP offers only ipv4, can this be the error ?
 
 is indeed the problem.
 

Further for your knowledge:
In the Internet Protocol Version 6 (IPv6), the address block fe80::/10 has been 
reserved for link-local unicast addressing. The actual link local addresses are 
assigned with the prefix fe80::/64 which is what you see on your wireless 
interface.
With this link local addresses you will not be about the reach your vps. You 
may need to look into Tunnel Broker services. Check out:
http://en.wikipedia.org/wiki/Tunnel_brokerhttp://en.wikipedia.org/wiki/List_of_IPv6_tunnel_brokers
-M

RE: Bind wildcard and DNSsec

[Mike Viau]

 On Date: Tue, 23 Oct 2012 11:44:03 +0200 r...@sput.nl wrote:

 Hi there


 Rob van der Putten wrote:

  I filed a bug report;
  http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=690569
 
  Bind refers to this bug as 'RT #26200'

 Bind fixed this in January.
 I don't expect Debian to implement this fix soon.
 It's probably best to disable DNSsec in your resolver.



Thanks for you updates and efforts on this issue Rob!


-M

--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/bay002-w172b8208c745631539f1ab8ef...@phx.gbl

RE: Initramfs-tools forcefully stars md arrays. How to disable it?

[Mike Viau]

 On Sun, 5 Aug 2012 22:01:49 -0700 blac1...@gmail.com wrote:

 initramfs-tools (0.98.8, the one in squeeze) uses the command below to
 start up the array for the root filesystem (from line 91 of
 /usr/share/initramfs-tools/scripts/local-top/mdadm):

 $MDADM --assemble --scan --run --auto=yes $dev

 This specifies --run, which makes mdadm start the array even if it can
 only do so in degraded mode. This means, if I knock a SATA cable
 loose, my machine will still boot, but dirty the array. Once I
 notice, and reconnect the cable, I now have to run risky mdadm
 commands to add the drive back, and then I have to rebuild the whole
 array.

 What I'd actually like, is if my system failed to boot if any drive is
 missing from the array. Then I'd have the opportunity to check the
 cables, and if needed, boot a live CD for troubleshooting. I'd like
 to make my own determination when do I give up on a harddrive, and
 bring the array up in degraded mode. I understand, that probably for
 most people, this is not what they want. They want high availability,
 that's why they use raid. Maybe I'm using raid in the wrong
 situation? Anyways...

 My question is how can you control this behavior? I see no way of
 configuring initramfs-tools not to add the --run option. Would it
 make sense to have such an option somewhere in the configuration?
 Also, could we take this as far as giving a prompt if the array did
 not start in normal mode, to let the admin force the start in degraded
 mode right there, without any need for a live CD or other maintenance?
 I don't know how easy is it to do anything interactive from
 local-top, and how portable that would be.


Perhaps you can override the default behavior  with a md file/script in your 
initramfs.


if [ -e /scripts/local-top/md ]; then
  log_warning_msg old md initialisation script found, getting out of its 
way...
  exit 1
fi


-M

--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/bay148-w1226274a33f0f09c88dff6ef...@phx.gbl

RE: radeon+ opencl+ non-free-: HOWTO?

[Mike Viau]

 On Wed, 4 Jul 2012 00:56:20 +0700 oneing...@gmail.com wrote:
 
  Camaleón  noela...@gmail.com writes:
  On Tue, 03 Jul 2012 20:08:57 +0700, Ivan Shmakov wrote:
 
   Somehow, I've got the impression that OpenCL is supported by some
   free development tools (Clang?)  Now, I wonder, if I'm right on
   that, is there some kind of HOWTO on how to utilize OpenCL via the
   free AMD Radeon driver included in Debian?  (I hope it is possible,
   isn't it?)
 
   There's a Debian wiki page altough I'm not sure if this will help to
   solve your questions :-)
 
   http://wiki.debian.org/ATIStream
 
   Neither am I.
 

There is nothing really in the wiki about OpenCL (considering the initial 
standard was dated back on 18 November 2008).

I looked through the NVIDIA pages as well on the Debian Wiki.

Perhaps you got your notions about using OpenCL API with opensource development 
tools because of articles like these?

http://www.phoronix.com/scan.php?page=news_itempx=MTA1Mzk

http://www.phoronix.com/scan.php?page=news_itempx=MTA3MjY


-M


  

--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/bay148-w29b4515512d539a7502b04ef...@phx.gbl

RE: US Weather Bureau video displays have stopped working

[Mike Viau]

 On Sat, 24 Mar 2012 11:11:40 -0400 edcjo...@comcast.net wrote:
 
 My PC has up-to-date Debian stable on it. Although the CPU chip is 
 Intel, the kernel is AMD64. 

This is okay, and not a CPU problem

Here is an URL for a U. S. Weather Bureau radar site:
 
 http://radar.weather.gov/radar.php?rid=lwxproduct=N0Roverlay=1110loop=yes
 
 This should show a time-lapse loop for the radar in Sterling, Virginia.  
 Recently this has stopped working.  Does anybody know what the problem is?
 

It appears to be working fine for me


-M
  

--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/bay148-w1940d6a687954e7d22ccf7ef...@phx.gbl

RE: Network-manager woes (wifi)

[Mike Viau]

 On Thu, 1 Mar 2012 18:33:11 + noela...@gmail.com wrote:
 
 Hello,
 
 After a recent set of updates in wheezy (it could be the kernel package 
 that was updated to 3.2.6 but I'm not sure) network-manager is going 
 crazy asking for the AP password every five minutes (disconnects-asks-
 reconnects... disconnects-asks-reconnects... disconnects-asks-
 reconnects... disconnects-asks-reconnects, and so on).
 
 In addition, sometimes is unable to remember the password (which I have 
 to re-type again and again) and if I cancel the box dialog I get a second 
 one with a different color: the first is black -the usual for the new 
 gnome-shell adwaita theme- while the second is grey -the usual style for 
 GTK+2. 
 
 It was working pretty stable all this time but it's unusable in its 
 current state.
 
 Is anyone facing this issue?

Prior to the recent updates I have been experiencing the behaviours you've 
described above. I noticed that even though one is being asked for a password, 
if one switches the wifi radio off and then back on again, authentication 
is successful without needed to re-key the credentials.

I figure from your email that this issue has not been fixed yet...

Thanks.

-M

--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/bay148-w1fa444cdcc482b08d0e7fef...@phx.gbl

RE: hi, how to set gnome3 in fallback mode?

[Mike Viau]

 On Sat, 21 Jan 2012 11:38:26 + noela...@gmail.com wrote:
 
  On Fri, 20 Jan 2012 18:35:04 -0500, Mike Viau wrote:
 
 (please, no html, thanks)
 
  On Fri, 20 Jan 2012 18:42:49 + noela...@gmail.com wrote:
  
   On Fri, 20 Jan 2012 15:44:10 +0800, shiyao.ma wrote:
  
   On 2012年01月20日 15:34, shiyao.ma wrote:
   I did a fresh installation of debian tesing on my laptop. After
   first login, the gnome3 told me that due to hardware problem, gnome3
   was in fallback mode. Thus, I installed the linux-firmware-nonfree.
   After a restart, the gnome3 was in standard mode automatically.
   However, I found myself like the fallback mode more. I found System
   settings-System info-Graphics has no setting of fallback mode. It
   just shows that I am in standard experience. How can I set it to
   fallback mode again? Thanks.
  
   I found the solution. Though impossible to set in
   gnome-control-center, the mode can be chosen in gdm3.
  
  As the fallback mode won't be always there, I would start by getting
  used to gnome-shell or looking for another DE/WM :-)
  
  
  I am  using Gnome3 Classic as a choice from the gdm3 login in screen. Is
  this what fallback implies, or will the Gnome 3 classic option always be
  there?
  
  I am using GNOME 3.2.1 in Wheezy.
 
 Gnome classic is a new name for the fallback mode. Different name, same 
 thing so gnome classic has the days counted :-)
 

Thanks  Camaleón, that answered my question. I don't know why I was thinking 
rich text was the correct option for the list mail. Regardless I am trying the 
PLAIN text option from here on out.
  


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/bay148-w325d8babb4c2eefd3d824bef...@phx.gbl

RE: hi, how to set gnome3 in fallback mode?

[Mike Viau]

 On Fri, 20 Jan 2012 18:42:49 + noela...@gmail.com wrote:
 
  On Fri, 20 Jan 2012 15:44:10 +0800, shiyao.ma wrote:
 
  On 2012年01月20日 15:34, shiyao.ma wrote:
  I did a fresh installation of debian tesing on my laptop. After first
  login, the gnome3 told me that due to hardware problem, gnome3 was in
  fallback mode. Thus, I installed the linux-firmware-nonfree. After a
  restart, the gnome3 was in standard mode automatically. However, I
  found myself like the fallback mode more. I found System
  settings-System info-Graphics has no setting of fallback mode. It
  just shows that I am in standard experience. How can I set it to
  fallback mode again? Thanks.
 
  I found the solution. Though impossible to set in gnome-control-center,
  the mode can be chosen in gdm3.
 
 As the fallback mode won't be always there, I would start by getting used 
 to gnome-shell or looking for another DE/WM :-)
 

I am  using Gnome3 Classic as a choice from the gdm3 login in screen. Is this 
what fallback implies, or will the Gnome 3 classic option always be there?

I am using GNOME 3.2.1 in Wheezy.

Thanks.
  

RE: hi, how to set gnome3 in fallback mode?

[Mike Viau]

  *Please* don't do that.

My apologizes, this is the first time someone has mentioned that my mail 
appears like it was in HTML formatting from my email client, but I can tell you 
the email was sent as Rich Text message. Perhaps your email client is 
interpreting emails from me as HTML incorrectly? 

What I was inquiring about was that I am  using Gnome3 Classic as a choice from 
the gdm3 login in screen. Is this what fallback implies, or will the Gnome 3 
classic option always be there?

I am using GNOME 3.2.1 in Wheezy.

Thanks.
  

RE: Happy Christmas

[Mike Viau]

Ditto :)

On Sun, 25 Dec 2011 02:04:50 +0200 lolinux.so...@gmail.com wrote

Thank you, Richard,
I also want to thank everyone on this list, for asking questions I might have 
asked, and also for answering those questions. I really feel happy to be part 
of this community.
Thank you, everyone no matter what timezone or religion!
I wish you all a happy Christmas time!
Sent from my Brick (TM)


On Dec 25, 2011 1:53 AM, Richard richard.b...@blueyonder.co.uk wrote:

Hi A very happy Christmas to those that have helped me  this year

Thanks



--

Happy Christmas and a Happy New Year



Best wishes / 73

Richard Bown



e-mail: rich...@g8jvm.com   or   richard.b...@blueyonder.co.uk



nil carborundum a illegitemis

##

Ham Call G8JVM . OS Debian Wheezy/Sid amd64 on a Dual core AMD Athlon 5200, 4 
GB RAM

Maidenhead QRA: IO82SP38, LAT. 52 39.720' N LONG. 2 28.171 W ( degs mins )

QRV HF + VHF Microwave 23 cms:140W,13 cms:100W,6 cms:10W  3 cms:5W

##





--

To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org

with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Archive: http://lists.debian.org/20111224235323.7e93e...@g8jvm.com



  

RE: debian 6 support Intel Centrino Advanced-N 6205 Wireless Network Adapter?

[Mike Viau]

My Intel Centrino Advanced-N 6230 (like the 6205, but with bluetooth) seems to 
work with the iwlagn -- see http://wiki.debian.org/iwlagn
As for your videocard, the generic plain Jane vesa driver 'should' always work. 
I would also look at http://wiki.debian.org/NvidiaGraphicsDrivers to setup the 
nv or Nouveau driver instead though.
Last option of the video driver is to go with the vendor (non-free):
http://www.nvidia.com/object/linux-display-amd64-290.10-driver.html  -- 64 
bithttp://www.nvidia.com/object/linux-display-ia32-290.10-driver.html -- 32 
bit

-M


From: hoss...@gmail.com
Date: Mon, 12 Dec 2011 11:05:52 +0330
Subject: debian 6 support Intel Centrino Advanced-N 6205 Wireless Network 
Adapter?
To: debian-user@lists.debian.org

hello

can debian 6 support Intel  Centrino Advanced-N 6205 Wireless  Network Adapter
and Nvidia  NVS  4200M 1GB?   

RE: alternatives to aircrack-ng

[Mike Viau]

 On Sat, 22 Oct 2011 00:58:32 + marcus9...@gmail.com wrote:
 
  Celejar celejar at gmail.com writes:
 
  
  On Tue, 18 Oct 2011 00:02:48 +0100
  Brian ad44 at cityscape.co.uk wrote:
  
   On Mon 17 Oct 2011 at 15:22:57 -0400, Celejar wrote:
   
aircrack-ng has been removed from Debian, and part of the justification
for the request for removal is that Better alternatives exist.:

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=642934
   
   The reason for its removal appears to be a licensing issue.
   
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=588588
   
   If I read the report correctly, it has been resolved and aircrack-ng is
   elegible for inclusion in Debian.
  
  Interesting, but the report I linked to also mentions that it's not
  being maintained and that better alternatives exist.
  
  Celejar
 
 I too am trying to find an alternative to this software suite.
 Nothing I can find even comes close.
 Pyrit as was suggested is only a component and IIRC can be included as a
 component in the later versions of the aircrack-ng suite.
 
 I find this software invaluable in pointing out wireless vulnerabilities.
 It really helps credibility when you can easily demonstrate the problem.
 
 I usually use Debian sid on my in field laptop and this package removal,
 assuming the licensing issues are resolved, makes little sense to me.
 
 It would appeared to be maintained at least upstream. 
 http://www.aircrack-ng.org
 
 I can compile it from source there are nightly builds and an svn, but seeing 
 the
 depth of Debian repositories reduced by the removal of this software is
 disappointing.
 

I absolutely agree. I have been forced to use the checkinstall package to allow 
apt to track the installation from make install of the upstream sources.
-M

RE: debian hangs after grub

[Mike Viau]

 On Wed, 27 Apr 2011 15:00:40 +0300 ibo...@yahoo.gr wrote:

 On 04/26/2011 05:29 PM, Vangelis Katsikaros wrote:
  Hello
 
  I just installed debian 6.0.1.a amd64 with net install, with a clean
  install (before I had 5).
 
  The system goes to grub and when I select the non-recovery mode
  (2.6.32-5-amd64), I get a cursor that doesn't blink and no action at
  all. I waited about 5-6 mins (I thought it would be checking for a card
  or something else) but nothing happened. Ctrl+Alt+Del doesn't work.
 
  Now, if I turn off and on the machine and:
  - go to grub
  - boot the recovery mode, and then at the root prompt I do a reboot
  - go to grub
  - boot the non recovery mode everything works fine and I get X and
  everything.
 
  I wonder how I can find what happens.
 
  I have
  - an lshw (from the debian 5 installation that's not there anymore) for
  this machine http://pastebin.com/n7J8DWYZ
  - the dmesg from the recovery mode is http://pastebin.com/UmtkYR5x
 
  If you need any more info I can make it available.
 
  Vangelis
 
  PS the netinstall CD could not install with the simple installer or the
  graphical one (again it hanged after selecting the install option) , so
  I did the installation with expert install.
 
 

 Hi again

 I also installed an ubuntu on the same machine, the ubuntu works fine,
 the debian issue still remains. So, I started playing with editing grub
 commands.

 In the debian non-recovery mode I removed from the grub command
 linux /vmlinuz... root=... ro quiet
 the quiet part

 And then booting works fine. Does that make any sense?

 Vangelis

 PS In order to apply this change permanently I edited the
 /etc/default/grub from
 GRUB_CMDLINE_LINUX_DEFAULT=quiet
 to
 GRUB_CMDLINE_LINUX_DEFAULT=

 in the ubuntu (since it was the last to be installed)



Just a day or so ago I found a strange behaviour around kernel boot parmeters 
in Debian as well.

A little digression:

I have two computers (1x home server  1x notebook) both running Debian 
Squeeze. One day I must have added panic=30 to both grub boot-loader configs 
and ran the update-grub command after on both. My laptop was restarted many 
times and booted flawlessly with the new change so I felt comfortable with 
leaving the 'panic' parameter on the home server as well. When I eventually got 
around to rebooting the server, it seemed that all of a sudden the home server 
stopped booting completely and just hung without any real kernel 
errors/messages being printed to the screen. Not initially thinking about the 
kernel parameter change made, I ran e2fsck the linux partitions, and even 
installed the 2.6.38-2 kernel from wheezy booting the system with the recovery 
entries from the grub boot menu that did not contain the panic option. Lastly I 
removed the panic=30 kernel parameter all together from the grub configuration 
and the server started booting again like normal.


Conclusion:

I came to learn about the 'panic' option after reading the 
kernel-parameters.txt file from the Linux kernel documentation [1]. I see that 
the quiet option is also a KNL (or kernel start-up parameter. I figured these 
options should just work and well it seems it does on some installations but 
not other :S

That's wierd I must admit... perhaps you could added the panic=30 parameter to 
your boot entry as a test just to see if it hangs in the same place as it did 
with the quiet parameter.



KNL Is a kernel start-up parameter.
quiet   [KNL] Disable most log messages

panic=  [KNL] Kernel behaviour on panic: delay timeout
seconds before rebooting
Format: timeout


[1] - 
http://git.kernel.org/?p=linux/kernel/git/next/linux-next.git;a=blob_plain;f=Documentation/kernel-parameters.txt;hb=HEAD


-M
  

--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/bay148-w481a47f79c5b3d27a939aeef...@phx.gbl

RE: Why doesn't debian remove the proprietary software from it's servers?

[Mike Viau]

 On Wed, 27 Apr 2011 09:50:07 -0400 kjetil1...@gmail.com wrote:

 I ran this command on my laptop, and the returned list includes:

 gdb-doc - The GNU Debugger Documentation

 ?Why the hell is gdb-doc not free?


I was wondering the same thing about the gcc-doc package.



 On Wed, Apr 27, 2011 at 06:36, Andrei Popescu  wrote:
  On Mi, 27 apr 11, 12:09:56, Klistvud wrote:
 
  Seems a quite reasonable policy to me. Of course, we all wish we
  could run free software ponly on our machines, but the time doesn't
  seem ripe for that.
 
  But we are getting closer every year:
 
  $ aptitude search '~snon-free|contrib~i!~M'
  i   firmware-iwlwifi- Binary firmware for Intel Wireless 
  3945, 4
  i   flashplugin-nonfree - Adobe Flash Player - browser plugin
  i   nvidia-glx  - NVIDIA binary Xorg driver
  i   nvidia-settings - Tool for configuring the NVIDIA 
  graphics d
  i   opera   - A fast and secure web browser and 
  Internet
  i   skype   - Skype
  i   sun-java6-plugin- The Java(TM) Plug-in, Java SE 6
  i   unrar   - Unarchiver for .rar files (non-free 
  versio
 
  of these I could get rid of Opera anytime (I don't actually use it, but
  I test it from time to time) and probably the Java plugin (I don't even
  recall why it's installed).
 
  There is work in progress for replacements for the nvidia driver and the
  flash plugin (but still not entirely there).
 
  firmware-iwlwifi will be tough, because Intel claims it has to do with
  (FCC?) compliance and unrar because it's still quite widespread (but
  actually useless for compressed movies and mp3s, so it's more of a user
  education thing).
 
  Regards,
  Andrei
  --
  Offtopic discussions among Debian users and developers:
  http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic
 
  

--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/bay148-w6222c20f39e42d2e13017bef...@phx.gbl

RE: debian hangs after grub

[Mike Viau]

 On Wed, 27 Apr 2011 20:40:42 +0300 ibo...@yahoo.gr wrote:
  On 04/27/2011 04:50 PM, Mike Viau wrote:
  Hi again
 
  I also installed an ubuntu on the same machine, the ubuntu works fine,
  the debian issue still remains. So, I started playing with editing grub
  commands.
 
  In the debian non-recovery mode I removed from the grub command
  linux /vmlinuz... root=... ro quiet
  the quiet part
 
  And then booting works fine. Does that make any sense?
 
  Vangelis
 
  PS In order to apply this change permanently I edited the
  /etc/default/grub from
  GRUB_CMDLINE_LINUX_DEFAULT=quiet
  to
  GRUB_CMDLINE_LINUX_DEFAULT=
 
  in the ubuntu (since it was the last to be installed)
 
 
 
  Just a day or so ago I found a strange behaviour around kernel boot 
  parmeters in Debian as well.
 
  A little digression:
 
  I have two computers (1x home server 1x notebook) both running Debian 
  Squeeze. One day I must have added panic=30 to both grub boot-loader 
  configs and ran the update-grub command after on both. My laptop was 
  restarted many times and booted flawlessly with the new change so I felt 
  comfortable with leaving the 'panic' parameter on the home server as well. 
  When I eventually got around to rebooting the server, it seemed that all of 
  a sudden the home server stopped booting completely and just hung without 
  any real kernel errors/messages being printed to the screen. Not initially 
  thinking about the kernel parameter change made, I ran e2fsck the linux 
  partitions, and even installed the 2.6.38-2 kernel from wheezy booting the 
  system with the recovery entries from the grub boot menu that did not 
  contain the panic option. Lastly I removed the panic=30 kernel parameter 
  all together from the grub configuration and the server started booting 
  again like normal.
 
 
  Conclusion:
 
  I came to learn about the 'panic' option after reading the 
  kernel-parameters.txt file from the Linux kernel documentation [1]. I see 
  that the quiet option is also a KNL (or kernel start-up parameter. I 
  figured these options should just work and well it seems it does on some 
  installations but not other :S
 
  That's weird I must admit... perhaps you could added the panic=30 parameter 
  to your boot entry as a test just to see if it hangs in the same place as 
  it did with the quiet parameter.

 Hi Mike

 I set GRUB_CMDLINE_LINUX_DEFAULT=panic=30 or
 GRUB_CMDLINE_LINUX_DEFAULT=quiet panic=30 it boots just fine


 With GRUB_CMDLINE_LINUX_DEFAULT=quiet it just hangs...



Hmm thanks for testing that. It's odd thought that you say 'quiet' works when 
'panic=30' is placed after it. It doesn't really help explain what's going on 
here, but you could call it a solution if the quiet parameter still works as 
expected with the panic=30 trailing after it. You'll know its working because 
your screen will have less messages on start up :)

FYI, I thought that the reason the system bootup was hanging was becuase of how 
the scripts residing in initrd.img were designed to handle kernel parameters 
passed by boot-loader. In particular I was looking at local-top being a 
potential place of interest, but I found nothing online to support this :S


-M
  

--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/bay148-w620b14d5a6d89c8f85853fef...@phx.gbl

RE: Tell firefox to quit from a shell script

[Mike Viau]

 On Sat, 9 Apr 2011 16:06:13 -0400 tyler.sm...@eku.edu wrote:

 Tyler Smith  writes:

 
  Is there a way I can politely ask firefox to quit, less traumatically
  than pkill?

 Hi again,

 I think I answered my own question:

 wmctrl -c firefox

 appears to do what I need.

 Sorry for the noise,

 Tyler


Does that work (to exit gracefully) if Firefox/Iceweasel is running on Gnome or 
KDE as well?


-M
  

--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/bay148-w1272c48bd354de824c7ac5ef...@phx.gbl

RE: Xen-hypervisor doesn't boot

[Mike Viau]

 On Fri, 1 Apr 2011 14:34:30 +0300 arts...@ya.ru wrote:
 
 Hello,
 
 Xen hypervisor doesn't boot after upgrade following packages:
 
 linux-image-2.6.32-5-xen-amd64 2.6.32-32
 linux-libc-dev 2.6.32-32
 linux-base 2.6.32-32
 
 But boots ok after downgrade to:
 
 linux-image-2.6.32-5-xen-amd64 2.6.32-31
 linux-libc-dev 2.6.32-31
 linux-base 2.6.32-31
 
 Doesn't boot means that it quickly shows some text and goes to reboot. 
 Looks like it can not boot the kernel. I'm using  
 xen-hypervisor-4.0-amd64 4.0.1-2. Feel free to ask any further details 
 if need.
 

I'd try building a kernel mentioned on the Xen PVOPS wiki page to see if that 
solves the problem:

Current active branches are: xen/stable-2.6.32.x
 - this is the long term maintained branch, tracking upstream kernel.org
 2.6.32.x stable updates. This branch has Xen dom0 patches added. This 
is the recommended branch for most users. Changelog: 
http://git.kernel.org/?p=linux/kernel/git/jeremy/xen.git;a=shortlog;h=xen/stable-2.6.32.x
 . xen/next-2.6.32
 - This is a branch for next 2.6.32 version and gets migrated to the 
stable branch once automatic tests have succeeded. Changelog: 
http://git.kernel.org/?p=linux/kernel/git/jeremy/xen.git;a=shortlog;h=xen/next-2.6.32
 . devel/next-2.6.38 - this is the current development branch based on Linux 
2.6.38. Changelog: 
http://git.kernel.org/?p=linux/kernel/git/konrad/xen.git;a=shortlog;h=devel/next-2.6.38
 . 


  

RE: xen hypervisor on sid, no xen kernel

[Mike Viau]

 On Tue, 8 Mar 2011 13:39:34 -0600 hvw59...@care2.com wrote:

 Hi,

 In looking at Xen I see that the hypervisor is on Sid but no Xen kernel.
 Anyone venture a guess as to why?


Just a guess, perhaps the 2.6.38 pv-ops kernel is in the works :)


-M
  

--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/bay148-w41a45bdb7f7abb61d57133ef...@phx.gbl

RE: How do you use TCPDump?

[Mike Viau]

 On Wed, 2 Mar 2011 22:00:41 -0600 jhsu802...@jasonhsu.com wrote:
 
 I have it installed, and I can look up the parameters in the command.
 
 What I don't understand is how I use it to investigate intrusions.  Can 
 someone shed some light on this?
 

What kind of intrusions are you looking for? TCPDump is a packet analyze so 
what is analyzed is based on what filters you are looking for. TCPDump uses the 
libpcap library to capture packets. You can receive the packets based on the 
protocol type. You can specify
one of these protocols — fddi, tr, wlan, ip, ip6, arp, rarp, decnet,
tcp and udp.

You may also specify a port number to monitor which is nice if you are 
investigating a particular service. Or an IP address if you are interested in a 
specific host.

The filter may be used in combinations with and'ing / or'ing them together. I 
tend to wrap my filters in single quotes, for example: tcpdump -i eth0 -n  'tcp 
and port 80 and dst 10.0.0.1'

One tip is to pass the -n switch when running because DNS queries slow down 
captures.

Hope that helps :)


-M

  

--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/bay148-w174ae84d50a7f526d341e4ef...@phx.gbl

Removed drive from mdadm raid 5 array after reboot

[Mike Viau]

 Hello,

 I was wondering if anyone had come across an issue where after rebooting the 
 system, mdadm is failing to reassemble the entire raid 5 array with all the 
 drives. I am getting the array up with just /dev/sda and /dev/sdb, but the 
 array is degraded as a consequence to missing /dev/sdd (which I assume has 
 become the parity drive). Below is some information that I believe will help 
 display my situation. Your help is greatly appreciated, TIA :)

 mdadm -V
 mdadm - v3.1.4 - 31st August 2010
 (Debian Version: Version: 3.1.4-1+8efb9d1)


 uname -a
 Linux XEN-HOST 2.6.32.26-xen-amd64 #1 SMP Thu Dec 2 00:20:03 EST 2010 x86_64 
 GNU/Linux


 mdadm --detail /dev/md0
 /dev/md0:
 Version : 1.2
   Creation Time : Mon Dec 20 09:48:07 2010
  Raid Level : raid5
  Array Size : 1953517568 (1863.02 GiB 2000.40 GB)
   Used Dev Size : 976758784 (931.51 GiB 1000.20 GB)
Raid Devices : 3
   Total Devices : 2
 Persistence : Superblock is persistent

 Update Time : Fri Feb 18 12:27:09 2011
   State : clean, degraded
  Active Devices : 2
 Working Devices : 2
  Failed Devices : 0
   Spare Devices : 0

  Layout : left-symmetric
  Chunk Size : 512K

Name : XEN-HOST:0  (local to host XEN-HOST)
UUID : 7d8a7c68:95a230d0:0a8f6e74:4c8f81e9
  Events : 32122

 Number   Major   Minor   RaidDevice State
0   810  active sync   /dev/sda1
1   8   171  active sync   /dev/sdb1
2   002  removed  
  Missing drive



 fdisk -luc /dev/sda

 Disk /dev/sda: 1000.2 GB, 1000204886016 bytes
 255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors
 Units = sectors of 1 * 512 = 512 bytes
 Sector size (logical/physical): 512 bytes / 512 bytes
 I/O size (minimum/optimal): 512 bytes / 512 bytes
 Disk identifier: 0x411fb12e

Device Boot  Start End  Blocks   Id  System
 /dev/sda1  63  1953520064   976760001   fd  Linux raid autodetect



 fdisk -luc /dev/sdb

 Disk /dev/sdb: 1000.2 GB, 1000204886016 bytes
 255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors
 Units = sectors of 1 * 512 = 512 bytes
 Sector size (logical/physical): 512 bytes / 512 bytes
 I/O size (minimum/optimal): 512 bytes / 512 bytes
 Disk identifier: 0x02f65de3

Device Boot  Start End  Blocks   Id  System
 /dev/sdb1  63  1953520064   976760001   fd  Linux raid autodetect



 fdisk -luc /dev/sdd

 Disk /dev/sdd: 1000.2 GB, 1000204886016 bytes
 81 heads, 63 sectors/track, 382818 cylinders, total 1953525168 sectors
 Units = sectors of 1 * 512 = 512 bytes
 Sector size (logical/physical): 512 bytes / 512 bytes
 I/O size (minimum/optimal): 512 bytes / 512 bytes
 Disk identifier: 0x8b0c29c7

Device Boot  Start End  Blocks   Id  System
 /dev/sdd12048  1953525167   976761560   fd  Linux raid autodetect




 cat /etc/mdadm/mdadm.conf
 # mdadm.conf
 #
 # Please refer to mdadm.conf(5) for information about this file.
 #

 # by default, scan all partitions (/proc/partitions) for MD superblocks.
 # alternatively, specify devices to scan, using wildcards if desired.
 DEVICE partitions

 # auto-create devices with Debian standard permissions
 CREATE owner=root group=disk mode=0660 auto=yes

 # automatically tag new arrays as belonging to the local system
 HOMEHOST 

 # instruct the monitoring daemon where to send mail alerts
 MAILADDR root

 # definitions of existing MD arrays
 ARRAY /dev/md/0 metadata=1.2 UUID=7d8a7c68:95a230d0:0a8f6e74:4c8f81e9 
 name=XEN-HOST:0



Forgot to add this this:

cat /proc/mdstat 
Personalities : [raid6] [raid5] [raid4] 
md0 : active raid5 sda1[0] sdb1[1]
  1953517568 blocks super 1.2 level 5, 512k chunk, algorithm 2 [3/2] [UU_]
  
unused devices: none


Then after: 

mdadm --add /dev/md0 /dev/sdd1 
mdadm: re-added /dev/sdd1


cat /proc/mdstat 
Personalities : [raid6] [raid5] [raid4] 
md0 : active raid5 sdd1[3] sda1[0] sdb1[1]
  1953517568 blocks super 1.2 level 5, 512k chunk, algorithm 2 [3/2] [UU_]
  []  recovery =  0.0% (121732/976758784) 
finish=534.8min speed=30433K/sec



Thanks.

  

--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/bay148-w4658b4d2c63a5b2adaedbef...@phx.gbl

removed drive from mdadm raid 5 array after reboot

[Mike Viau]

Hello,

I was wondering if anyone had come across an issue where after rebooting the 
system, mdadm is failing to reassemble the entire raid 5 array with all the 
drives. I am getting the array up with just /dev/sda and /dev/sdb, but the 
array is degraded as a consequence to missing /dev/sdd (which I assume has 
become the parity drive). Below is some information that I believe will help 
display my situation. Your help is greatly appreciated, TIA :)

mdadm -V
mdadm - v3.1.4 - 31st August 2010
(Debian Version: Version: 3.1.4-1+8efb9d1)


uname -a
Linux XEN-HOST 2.6.32.26-xen-amd64 #1 SMP Thu Dec 2 00:20:03 EST 2010 x86_64 
GNU/Linux


mdadm --detail /dev/md0
/dev/md0:
    Version : 1.2
  Creation Time : Mon Dec 20 09:48:07 2010
 Raid Level : raid5
 Array Size : 1953517568 (1863.02 GiB 2000.40 GB)
  Used Dev Size : 976758784 (931.51 GiB 1000.20 GB)
   Raid Devices : 3
  Total Devices : 2
    Persistence : Superblock is persistent

    Update Time : Fri Feb 18 12:27:09 2011
  State : clean, degraded
 Active Devices : 2
Working Devices : 2
 Failed Devices : 0
  Spare Devices : 0

 Layout : left-symmetric
 Chunk Size : 512K

   Name : XEN-HOST:0  (local to host XEN-HOST)
   UUID : 7d8a7c68:95a230d0:0a8f6e74:4c8f81e9
 Events : 32122

    Number   Major   Minor   RaidDevice State
   0   8    1    0  active sync   /dev/sda1
   1   8   17    1  active sync   /dev/sdb1
   2   0    0    2  removed  
 Missing drive



fdisk -luc /dev/sda

Disk /dev/sda: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x411fb12e

   Device Boot  Start End  Blocks   Id  System
/dev/sda1  63  1953520064   976760001   fd  Linux raid autodetect



fdisk -luc /dev/sdb

Disk /dev/sdb: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x02f65de3

   Device Boot  Start End  Blocks   Id  System
/dev/sdb1  63  1953520064   976760001   fd  Linux raid autodetect



fdisk -luc /dev/sdd

Disk /dev/sdd: 1000.2 GB, 1000204886016 bytes
81 heads, 63 sectors/track, 382818 cylinders, total 1953525168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x8b0c29c7

   Device Boot  Start End  Blocks   Id  System
/dev/sdd1    2048  1953525167   976761560   fd  Linux raid autodetect




cat /etc/mdadm/mdadm.conf 
# mdadm.conf
#
# Please refer to mdadm.conf(5) for information about this file.
#

# by default, scan all partitions (/proc/partitions) for MD superblocks.
# alternatively, specify devices to scan, using wildcards if desired.
DEVICE partitions

# auto-create devices with Debian standard permissions
CREATE owner=root group=disk mode=0660 auto=yes

# automatically tag new arrays as belonging to the local system
HOMEHOST system

# instruct the monitoring daemon where to send mail alerts
MAILADDR root

# definitions of existing MD arrays
ARRAY /dev/md/0 metadata=1.2 UUID=7d8a7c68:95a230d0:0a8f6e74:4c8f81e9 
name=XEN-HOST:0


-M


  

--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/bay148-w38cae450fec67644025e33ef...@phx.gbl

RE: Autorun is VERY bad

[Mike Viau]

 On Mon, 7 Feb 2011 10:21:48 -0800 kellyr...@zoho.com wrote:
 


 How to disable autorun? Are there any hidden autorun features on a standard 
 Debian install??
 
 http://securitytube.net/USB-Autorun-attacks-against-Linux-at-Shmoocon-2011-video.aspx
 

In the gnome desktop manager open up the file manager, or run nautilus

Then, Edit  Preferences  Media  Never Prompt or start programs on media 
insertion

Hope that helps!


-M
  

RE: Autorun is VERY bad

[Mike Viau]

 On Mon, 7 Feb 2011 13:50:32 -0500 deb...@pcartwright.com wrote:
  On 02/07/2011 01:36 PM, Mike Viau wrote:
  In the gnome desktop manager open up the file manager, or run nautilus
 
  Then, Edit  Preferences  Media  Never Prompt or start programs on 
  media insertion
 
  Hope that helps!
 
 um, I just fired up Nautilus  I don't a have a MEDIA tab..
 
 mine says:Views, Behavior, Display, List Columns, Preview.
 Nautilus 2.20.0
 Debian Lenny, running gnome ..
 

Thanks for your report. I am running Nautilus 2.30.1 in Debian Squeeze which is 
now considered the stable release.

  Then, Edit  Preferences  Media  Never Prompt or start programs on 
  media insertion

Unfortunately I don't know what file is modified in changing this option. 


-M
  

RE: Squeeze Beta 2 upgrade

[Mike Viau]

 On Wed, 2 Feb 2011 16:36:05 + russ.mail.li...@gmail.com wrote:
 
 Hopefully a simple question to answer. I installed Squeeze beta 2
 AMD64 a few weeks ago and have accepted all updates. If I continue to
 take the updates will it morph into the release version when that is
 released or is it advisable to reinstall the final release?
 
 

The software packages will update (if necessary) to be the same ones as on the 
release medium packages. So a re-install is not necessary.

Then the official Debian apt repositories will become more up-to-date until the 
next point release.


-M
  

RE: Critical Xen bug on Debian Squeeze, suspecting package xen-hypervisor-4.0-amd64

[Mike Viau]

 On Tue, 1 Feb 2011 11:47:30 +0100 lambert.oliv...@gmail.com wrote:
 
 Hi,
 
 First, I will explain quickly the problem : on updated version
 Squeeze, I can't boot **any** DomU's, it hangs.
 
 Two cases:
 1) HVM DomU's : xm create sends a command to qemu, the parameter
 '-vcpu_avail'. But on newer version of qemu, parameters had changed
 (it's only 'vcpu_avail'): so HVM domain cannot be started.
 Here is the error line :
 /usr/lib/xen/bin/qemu-dm: invalid option -- '-vcpu_avail'
 
 2) Others DomU's (include pvops domains ! so not it's not the kernel):
 they freeze at startup, with cpu @ 100%. No specific logs, no errors
 reported, just only r status on xm list and no boot with cpu at max.
 
 Then, in my case, it's obvious these are regression on squeeze. Why ?
 Because on my 3 dom0's, only 2 of them are updated. And the old one
 works *perfectly*, both for HVM and Pvops DomU's. Dom0 are similar
 (same hardware, dell 2970 with  opteron 2423 HE)
 
 On old working Dom0 :
 
 $ aptitude show xen-hypervisor-4.0-amd64
 Version : 4.0.1-1
 
 $ aptitude show qemu-system
 Paquet : qemu-system
 Version : 0.12.5+dfsg-2
 
 -
 On updated Dom0's :
 
 $ aptitude show xen-hypervisor-4.0-amd64
 Version : 4.0.1-2
 
 $ aptitude show qemu-system
 Version : 0.12.5+dfsg-3
 
 
 I know this report is general, so if you want further details,
 I'll be ready to do some tests today.
 
 

Have you filed a bug over on the Debain BTS for what you believe to be a bug in 
the package xen-hypervisor-4.0-amd64?

Can you test if this behaviour exist in the i386 package?


  

RE: nameserver issues involving *.debian.org

[Mike Viau]

 On Mon, 31 Jan 2011 09:50:17 -0500 tomh0...@gmail.com wrote:
 
  On Mon, Jan 31, 2011 at 3:11 AM, Bob Proulx b...@proulx.com wrote:
 
   $ sudo apt-get install bind9
 
  Then ensure that 'nameserver 127.0.0.1' exists in /etc/resolv.conf and
  you should be set.  By ensure I mean that you should use either
  'resolvconf' to maintain that file or perhaps use a 'dns-nameservers'
  statement in /etc/network/interfaces or edit the resolv.conf file
  manually or whatever is appropriate for your system.
 
 FYI, dns-nameservers is a resolvconf customization of e-n-i so
 either...or's not quite right.
 

Thanks Tom,

I did some further digging on this info to discover:

If the original static resolver configuration file (/etc/resolv.conf)   
contains name server addresses, those addresses should be listed on 
dns-nameservers lines in /etc/network/interfaces. For more
information, please consult the resolvconf(8) man page and the README   
file.   

Until /etc/network/interfaces has been edited and the affected  
interfaces brought down and up again, the name server addresses will not
be included in the dynamically generated resolver configuration file.   

If you choose this option, a temporary workaround will be put in place: 
a symbolic link will be created (if it does not already exist) from 
/etc/resolvconf/resolv.conf.d/tail to   
/etc/resolvconf/resolv.conf.d/original. This will cause the whole of
that original resolver configuration file to be appended to the 
dynamically generated file. 

After the required dns-nameservers lines have been added to   
/etc/network/interfaces, the /etc/resolvconf/resolv.conf.d/tail link
should be replaced by one to /dev/null.  


-M
  

RE: networking

[Mike Viau]

 On Fri, 14 Jan 2011 12:54:49 -0700 b...@proulx.com wrote:
  Mihira Fernando wrote:
  Bonno Bloksma wrote:
   I have been wondering about this and have not seen any definitive
   documentation, or if there is, I have not understood it.
   Does auto imply allow-hotplug? If not, should I have both
  auto eth0 eth1
   and
  allow-hotplug eth0 eth1
   lines in my interfaces file?
 
  AFAIK, allow-hotplug makes the interface come up only when a cable
  is plugged in. auto makes the interface come up at boot time
  regardless of the cable state.
 
 You are exactly correct.  Having 'auto' is the old way that starts
 networking with '/etc/init.d/networking start'.  But that does not
 enable event driven actions such as link status change from plugging
 and unplugging the cable.  For that you need 'allow-hotplug'.  But
 that new way doesn't enable '/etc/init.d/networking restart' to do
 anything.
 
 Since hotplugging is the new way the debian-installer now sets that up
 for new systems.  Using an event driven network configuration is
 definitely an improvement in general and the right direction to go.
 But us old-timers who want to be able to restart the networking then
 find that '/etc/init.d/networking restart' doesn't do anything.  For
 that we also need 'auto' to be present.
 

Would executing '/etc/init.d/networking stop' followed by
'/etc/init.d/networking start' work to restart networking when using only
the new way ('allow-hotplug')?



I understand ifup/down can also be used, but what would t look like? I
have only used ifconfig to bring interface either up or down.



 This came up in discussion in the past.  I don't have the time at the
 moment to find a reference link however.  But it is okay to have both
 trigger conditions present.  Then both networking restart and link
 status changes will affect the network configuration.
 

This is something to keep in mind as it only adds minimal line to the 
/etc/network/interfaces file :)

Thanks.


 And of course for wicd or network-manager neither of auto or
 allow-hotplug can be present.  For those tools only configure
 interfaces that do not have any local configuration.

  

RE: Is squeeze compatible woth WD20EARS and other 2TB drives?

[Mike Viau]

 On Mon, 13 Dec 2010 21:46:59 +0100 m...@well-adjusted.de wrote:
 
  I'm planning to surprise my unsuspecting self with the above hard
  drive for Christmas, but have read some alarming reports about
  incompatibilities with GNU/Linux partitioning. Apparently, there are
  no less than two distinct problems with these drivers:

 I am running squeeze with two WD10EARS drives (plus another different
 drive) in a RAID10. When setting things up, I decided to ignore this
 issue completely because I thought the tools would do the right thing
 automatically. Apparently, they don't, although the drive reports its
 correct physical sector size:

 # fdisk -ul /dev/sdc

 Disk /dev/sdc: 1000.2 GB, 1000204886016 bytes
 255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors
 Units = sectors of 1 * 512 = 512 bytes
 Sector size (logical/physical): 512 bytes / 4096 bytes
 I/O size (minimum/optimal): 4096 bytes / 4096 bytes
 Disk identifier: 0x

 Device Boot Start End Blocks Id System
 /dev/sdc1 63 1953118439 976559188+ da Non-FS data
 Partition 1 does not start on physical sector boundary.



I don't understand the implied meaning of this error? Did you take any 
precautions as to the alignment of your partition? What about if you were 
planning on having multiple partitions?


 I don't have a serious performance issue, though. There's an encrypted
 LVM volume on top of it and throughput is limited by the CPU (Atom D510)
 at about 20-25MByte/s. An unencrypted volume I just created for this
 test yields 72MByte/s write and 98MByte/s read throughput on the RAID.


That sounds decent, how are you achieving RAID 1 over 0 (10) though with three 
drives? Perhaps that is another topic, but I typically see transfer rates of 
~100MB/s give or take from a single modern SATA drive.

 Just out of curiosity, I will try reformatting the drives and see
 whether the results for unencrypted access change. I am just not sure
 whether I would have to tweak RAID and/or LVM parameters as well. That
 wouldn't be that easy to pull off.

 J.
 --
 Thy lyrics in pop songs seem to describe my life uncannily accurately.
 [Agree] [Disagree]
 
  

--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/bay148-w119def71fdbfe9bb6f7edfef...@phx.gbl

RE: Towards a working initrd.img file

[Mike Viau]

 On Fri, 3 Dec 2010 07:15:38 -0500 tomh0...@gmail.com wrote:
  On Fri, Dec 3, 2010 at 1:12 AM, Peter Tenenbaum
  wrote:
 
  I've been having a problem since migrating my file system to RAID-1, which
  is that when I run update-initramfs, it produces an initrd.img file which
  doesn't work correctly; when I replace it with the initrd.img file which was
  constructed by the OS installer, I can boot correctly in my newly-RAIDified
  system.
 
  So my question:  how do I configure update-initramfs so that it
  automatically includes the kernel modules I need?  I note that there is a
  file, /etc/initramfs-tools/modules, which in my case has no module names in
  it; presumably I can look at /proc/modules and copy the names of all the
  modules shown in the latter into the former.  Would that solve my problem?
  Is there a better way?

 I assume that this won't return anything but what do you get when you run
 gzip --decompress --standout /boot/initrd.img-non-working | cpio
 --list | grep mdadm
 gzip --decompress --standout /boot/initrd.img-non-working | cpio
 --list | grep '/md/'

 I have an mdadm'd install of sid in which there isn't anything
 mdraid-related in /etc/initramfs-tools.

 Does /usr/share/initramfs-tools/hooks/mdadm exist?


FYI. This is my output of the given command, and mdadm works in my system.

gzip --decompress --stdout /boot/initrd.img-2.6.32-5-xen-amd64 | cpio --list | 
grep mdadm
57966 blocks
scripts/local-top/mdadm
etc/mdadm
etc/mdadm/mdadm.conf
sbin/mdadm


Wish I could have been of more help.

Good luck.
  

--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/bay148-w34842ebf314d23bc07aff6ef...@phx.gbl

RE: hdparm - dpkg error on update

[Mike Viau]

 On Tue, 30 Nov 2010 16:37:47 -0700 b...@proulx.com wrote:

 That reads like a similar problem to one reported in this (old) bug
 report:

 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=558478

  Has anyone else gotten this issue and did you come across a fix for
  this version or the dpkg system?

 I don't recognize the 'nxsensor' service in your output. Is that in
 the current Debian archive? 

'nxsensor was from a remote desktop software called no-machine.

I am guessing the problem exists in that
 script. What is the header for that script, the part between BEGIN
 INIT INFO and END INIT INFO? Because I think the problem is probably
 there.


You were absolutely correct!

I was pressed for time to troubleshoot the init script, so after simply purging 
the no-machine package I was able to complete the hdparm update.

Thanks Bob :)
  

--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/bay148-w198652c5c2a6604705e12ef...@phx.gbl

hdparm - dpkg error on update

[Mike Viau]

Hello,

This morning I discovered an update for the hdparm package on my debian squeeze 
system. Update have been perfect for numerous other packages.

When I tried to update this package I got errors and now the package is in a 
broken state.

I am not too sure where I should be fiddling to remedy there error messages.

They seem to be related to init scripts (update-rc.d: error: insserv rejected 
the script header),
and (insserv: exiting now without changing boot order!).

DPKG error output:
http://paste.debian.net/101135/

Has anyone else gotten this issue and did you come across a fix for this 
version or the dpkg system?

Thanks.


-M

  

--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/bay148-w179fc9be39e230fa9104d8ef...@phx.gbl

RE: How to recreate a dmraid RAID array with mdadm

[Mike Viau]

 OnTue, 23 Nov 2010 10:11:29 +1100 ne...@suse.de wrote:
 I see the problem now. And John Robinson was nearly there.

 The problem is that after assembling the container /dev/md/imsm,
 mdadm needs to assemble the RAID1, but doesn't find the
 container /dev/md/imsm to assemble it from.
 That is because of the
 DEVICE partitions
 line.
 A container is not a partition - it does not appear in /proc/partitions.
 You need

 DEVICE partitions containers

 which is the default if you don't have a DEVICE line (and I didn't have a
 device line in my testing).

 I think all the wrong uuid messages were because the device was busy (and
 so it didn't read a uuid), probably because you didn't mdadm -Ss first.

 So just remove the DEVICE partitions line, or add  containers to it, and
 all should be happy.

 NeilBrown


Yes thank you, that seems to be the correct fix.

mdadm -Asvv

mdadm: looking for devices for further assembly
mdadm: no RAID superblock on /dev/dm-3
mdadm: /dev/dm-3 has wrong uuid.
mdadm: no RAID superblock on /dev/dm-2
mdadm: /dev/dm-2 has wrong uuid.
mdadm: no RAID superblock on /dev/dm-1
mdadm: /dev/dm-1 has wrong uuid.
mdadm: no RAID superblock on /dev/dm-0
mdadm: /dev/dm-0 has wrong uuid.
mdadm: no RAID superblock on /dev/loop0
mdadm: /dev/loop0 has wrong uuid.
mdadm: cannot open device /dev/sdc7: Device or resource busy
mdadm: /dev/sdc7 has wrong uuid.
mdadm: cannot open device /dev/sdc6: Device or resource busy
mdadm: /dev/sdc6 has wrong uuid.
mdadm: cannot open device /dev/sdc5: Device or resource busy
mdadm: /dev/sdc5 has wrong uuid.
mdadm: no RAID superblock on /dev/sdc2
mdadm: /dev/sdc2 has wrong uuid.
mdadm: cannot open device /dev/sdc1: Device or resource busy
mdadm: /dev/sdc1 has wrong uuid.
mdadm: cannot open device /dev/sdc: Device or resource busy
mdadm: /dev/sdc has wrong uuid.
mdadm: /dev/sdb is identified as a member of /dev/md/imsm0, slot -1.
mdadm: /dev/sda is identified as a member of /dev/md/imsm0, slot -1.
mdadm: added /dev/sda to /dev/md/imsm0 as -1
mdadm: added /dev/sdb to /dev/md/imsm0 as -1
mdadm: Container /dev/md/imsm0 has been assembled with 2 drives
mdadm: looking for devices for /dev/md/OneTB-RAID1-PV
mdadm: no recogniseable superblock on /dev/dm-3
mdadm/dev/dm-3 is not a container, and one is required.
mdadm: no recogniseable superblock on /dev/dm-2
mdadm/dev/dm-2 is not a container, and one is required.
mdadm: no recogniseable superblock on /dev/dm-1
mdadm/dev/dm-1 is not a container, and one is required.
mdadm: no recogniseable superblock on /dev/dm-0
mdadm/dev/dm-0 is not a container, and one is required.
mdadm: no recogniseable superblock on /dev/loop0
mdadm/dev/loop0 is not a container, and one is required.
mdadm: cannot open device /dev/sdc7: Device or resource busy
mdadm/dev/sdc7 is not a container, and one is required.
mdadm: cannot open device /dev/sdc6: Device or resource busy
mdadm/dev/sdc6 is not a container, and one is required.
mdadm: cannot open device /dev/sdc5: Device or resource busy
mdadm/dev/sdc5 is not a container, and one is required.
mdadm: no recogniseable superblock on /dev/sdc2
mdadm/dev/sdc2 is not a container, and one is required.
mdadm: cannot open device /dev/sdc1: Device or resource busy
mdadm/dev/sdc1 is not a container, and one is required.
mdadm: cannot open device /dev/sdc: Device or resource busy
mdadm/dev/sdc is not a container, and one is required.
mdadm: cannot open device /dev/sdb: Device or resource busy
mdadm/dev/sdb is not a container, and one is required.
mdadm: cannot open device /dev/sda: Device or resource busy
mdadm/dev/sda is not a container, and one is required.
mdadm: looking in container /dev/md127
mdadm: found match on member /md127/0 in /dev/md127
mdadm: Started /dev/md/OneTB-RAID1-PV with 2 devices   -- The line I was 
looking for


ls -al /dev/md/

total 0
drwxr-xr-x  2 root root   80 Nov 23 09:47 .
drwxr-xr-x 21 root root 3480 Nov 23 09:47 ..
lrwxrwxrwx  1 root root8 Nov 23 09:47 imsm0 - ../md127
lrwxrwxrwx  1 root root8 Nov 23 09:47 OneTB-RAID1-PV - ../md126


I filed a bug[1] as I was just going along with default configurations, to see 
what is said about it.

Thanks soo much for your help Neil :)

[1] - http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=604702
  

--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/bay148-w292469b105a527bfd32aa0ef...@phx.gbl

RE: How to recreate a dmraid RAID array with mdadm

[Mike Viau]

 On Thu, 18 Nov 2010 16:38:49 +1100 ne...@suse.de wrote:
   On Thu, 18 Nov 2010 14:17:18 +1100  wrote:
   
 On Thu, 18 Nov 2010 13:32:47 +1100 wrote:
  ./mdadm -Ss
 
  mdadm: stopped /dev/md127
 
 
  ./mdadm -Asvvv
 
  mdadm: looking for devices for further assembly
  mdadm: no RAID superblock on /dev/dm-3
  mdadm: /dev/dm-3 has wrong uuid.
  want UUID-084b969a:0808f5b8:6c784fb7:62659383
  Segmentation fault

 Try this patch instead please.
   
Applied new patch and got:
   
./mdadm -Ss
   
mdadm: stopped /dev/md127
   
   
./mdadm -Asvvv
mdadm: looking for devices for further assembly
mdadm: no RAID superblock on /dev/dm-3
mdadm: /dev/dm-3 has wrong uuid.
want UUID-084b969a:0808f5b8:6c784fb7:62659383
tst=0x10dd010 sb=(nil)
Segmentation fault
  
   Sorry... I guess I should have tested it myself..
  
   The
   if (tst) {
  
   Should be
  
   if (tst  content) {
  
 
  Apply update and got:
 
  mdadm: /dev/sdb is identified as a member of /dev/md/imsm0, slot -1.
  mdadm: /dev/sda is identified as a member of /dev/md/imsm0, slot -1.
  mdadm: added /dev/sda to /dev/md/imsm0 as -1
  mdadm: added /dev/sdb to /dev/md/imsm0 as -1
  mdadm: Container /dev/md/imsm0 has been assembled with 2 drives
  mdadm: looking for devices for /dev/md/OneTB-RAID1-PV

 So just to clarify.

 With the Debian mdadm, which is 3.1.4, if you

 mdadm -Ss
 mdadm -Asvv

 it says (among other things) that /dev/sda has wrong uuid.
 and doesn't start the array.

Actually both compiled and Debian do not start the array. Or atleast create the 
/dev/md/OneTB-RAID1-PV device when running mdadm -I /dev/md/imsm0 does.

You are right about seeing a message on /dev/sda about having a wrong uuid 
somewhere though.  I went back to take a look at my output from the Debian 
mailing list to see that the mdadm did change slightly from this thread has 
begun.

The old output was copied verbatim on 
http://lists.debian.org/debian-user/2010/11/msg01234.html and says (among other 
things) that /dev/sda has wrong uuid.

The /dev/sd[ab] has wrong uuid messages are missing from the mdadm -Asvv output 
but

./mdadm -Ivv /dev/md/imsm0 
mdadm: UUID differs from /dev/md/OneTB-RAID1-PV.
mdadm: match found for member 0
mdadm: Started /dev/md/OneTB-RAID1-PV with 2 devices


I still have this UUID message when still using the mdadm -I command.


I'll attach the output of both the mdadm commands above as they run now on the 
system, but I noticed, but also that in the same thread link above, with the 
old output I was inqurying as to both /dev/sda and /dev/sdb (the drives which 
make up the raid1 array) do not appear to recognized as having a valid 
container when one is required.

What is take on GeraldCC (gcsgcatl...@bigpond.com) assistance about /dev/sd[ab] 
containing a 8e (for LVM) partition type, rather than the fd type to denote 
raid autodetect. If this was the magical fix (which I am not saying it can’t 
be) why is mdadm -I /dev/md/imsm0 able to bring up the array for use as an 
physical volume for LVM?




 But with the mdadm you compiled yourself, which is also 3.1.4,
 if you

 mdadm -Ss
 mdadm -Asvv

 then it doesn't give that message, and it works.

Again, actually both compiled and Debian do not start the array. Or atleast
create the /dev/md/OneTB-RAID1-PV device when running mdadm -I
/dev/md/imsm0 does.


 That is very strange. It seems that the Debian mdadm is broken somehow, but
 I'm fairly sure Debian hardly changes anything - they are *very* good at
 getting their changes upstream first.

 I don't suppose you have an /etc/mdadm.conf as well as /etc/mdadm/mdadm.conf
 do you? If you did and the two were different, the Debian's mdadm would
 behave a bit differently to upstream (they prefer different config files) but
 I very much doubt that is the problem.


There is no /etc/mdadm.conf on the filesystem only /etc/mdadm/mdadm.conf


 But I guess if the self-compiled one works (even when you take the patch
 out), then just
 make install

I wish this was the case...


 and be happy.

 NeilBrown


 
 
  Full output at: http://paste.debian.net/100103/
  expires:
 
  2010-11-21 06:07:30

Thanks

-M
  Compiled version

./mdadm -Ss

mdadm: stopped /dev/md127

===

./mdadm -Asvv

mdadm: looking for devices for further assembly
mdadm: no RAID superblock on /dev/dm-3
mdadm: /dev/dm-3 has wrong uuid.
 want UUID-084b969a:0808f5b8:6c784fb7:62659383
 tst=0x982010 sb=(nil)
mdadm: no RAID superblock on /dev/dm-2
mdadm: /dev/dm-2 has wrong uuid.
 want UUID-084b969a:0808f5b8:6c784fb7:62659383
 tst=0x982120 sb=(nil)
mdadm: no RAID superblock on /dev/dm-1
mdadm: /dev/dm-1 has wrong uuid.
 want UUID-084b969a:0808f5b8:6c784fb7:62659383
 tst=0x9821b0 sb=(nil)
mdadm: no RAID superblock on /dev/dm-0
mdadm: /dev/dm-0 has wrong uuid.
 want UUID-084b969a:0808f5b8:6c784fb7:62659383
 tst=0x9919a0 sb=(nil)
mdadm: no RAID superblock on 

RE: Release file expired

[Mike Viau]

On Mon, 22 Nov 2010 13:51:09 -0500 ckro...@frankensteinface.com worte:

 I've not seen this before, what does it mean?

 [attempt to hand format for easier reading]

 r...@mundo:/home/charles# apt-get update

 Get:1 http://mirror.rit.edu sid Release.gpg [835 B]

 Ign http://mirror.rit.edu/debian/ sid/contrib Translation-en
 Ign http://mirror.rit.edu/debian/ sid/contrib Translation-en_US
 Ign http://mirror.rit.edu/debian/ sid/main Translation-en

 Get:2 http://dl.google.com testing Release.gpg [189 B]

 Ign http://mirror.rit.edu/debian/ sid/main Translation-en_US
 Ign http://mirror.rit.edu/debian/ sid/non-free Translation-en
 Ign http://mirror.rit.edu/debian/ sid/non-free Translation-en_US
 Ign http://dl.google.com/linux/deb/ testing/non-free Translation-en

 Get:3 http://security.debian.org lenny/updates Release.gpg [835 B]

 Ign http://security.debian.org/ lenny/updates/contrib Translation-en

 Get:4 http://debian.corenetworks.net experimental Release.gpg [835 B]

 Hit http://mirror.rit.edu sid Release

 Ign http://security.debian.org/ lenny/updates/contrib Translation-en_US
 Ign http://security.debian.org/ lenny/updates/main Translation-en
 Ign http://security.debian.org/ lenny/updates/main Translation-en_US
 Ign http://security.debian.org/ lenny/updates/non-free Translation-en
 Ign http://security.debian.org/ lenny/updates/non-freeTranslation-en_US

 Get:5 http://security.debian.org lenny/updates Release [40.8 kB]

 Ign http://debian.corenetworks.net/debian/ experimental/contribTranslation-en

 E: Release file expired, ignoring
 http://mirror.rit.edu/debian/dists/sid/Release (invalid since 1d 21h
 21min 52s)


This seems to be a problem with the mirror itself, and hopefully to be fixed 
(if not fixed already).

This issue has also been reported on the debian-mirrors mailinglist.

http://lists.debian.org/debian-mirrors/2010/11/msg8.html
  

--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/bay148-w53d86750d5420e8d370379ef...@phx.gbl

RE: How to recreate a dmraid RAID array with mdadm

[Mike Viau]

 On Wed, 17 Nov 2010 14:15:14 +1100 ne...@suse.de wrote:

 This looks wrong. mdadm should be looking for the container as listed in
 mdadm.conf and it should find a matching uuid on sda and sdb, but it doesn't.

 Can you:

 mdadm -E /dev/sda /dev/sdb ; cat /etc/mdadm/mdadm.conf

 so I can compare the uuids?


Sure.

# definitions of existing MD arrays ( So you don't have to scroll down :P )


ARRAY metadata=imsm UUID=084b969a:0808f5b8:6c784fb7:62659383

ARRAY /dev/md/OneTB-RAID1-PV container=084b969a:0808f5b8:6c784fb7:62659383 
member=0 UUID=ae4a1598:72267ed7:3b34867b:9c56497a

mdadm -E /dev/sda /dev/sdb

/dev/sda:
  Magic : Intel Raid ISM Cfg Sig.
    Version : 1.1.00
    Orig Family : 601eee02
 Family : 601eee02
 Generation : 1187
   UUID : 084b969a:0808f5b8:6c784fb7:62659383
   Checksum : 2f91ce06 correct
    MPB Sectors : 1
  Disks : 2
   RAID Devices : 1

  Disk00 Serial : STF604MH0J34LB
  State : active
 Id : 0002
    Usable Size : 1953520654 (931.51 GiB 1000.20 GB)

[OneTB-RAID1-PV]:
   UUID : ae4a1598:72267ed7:3b34867b:9c56497a
 RAID Level : 1
    Members : 2
  Slots : [UU]
  This Slot : 0
 Array Size : 1953519616 (931.51 GiB 1000.20 GB)
   Per Dev Size : 1953519880 (931.51 GiB 1000.20 GB)
  Sector Offset : 0
    Num Stripes : 7630936
 Chunk Size : 64 KiB
   Reserved : 0
  Migrate State : idle
  Map State : normal
    Dirty State : clean

  Disk01 Serial : STF604MH0PN2YB
  State : active
 Id : 0003
    Usable Size : 1953520654 (931.51 GiB 1000.20 GB)
/dev/sdb:
  Magic : Intel Raid ISM Cfg Sig.
    Version : 1.1.00
    Orig Family : 601eee02
 Family : 601eee02
 Generation : 1187
   UUID : 084b969a:0808f5b8:6c784fb7:62659383
   Checksum : 2f91ce06 correct
    MPB Sectors : 1
  Disks : 2
   RAID Devices : 1

  Disk01 Serial : STF604MH0PN2YB
  State : active
 Id : 0003
    Usable Size : 1953520654 (931.51 GiB 1000.20 GB)

[OneTB-RAID1-PV]:
   UUID : ae4a1598:72267ed7:3b34867b:9c56497a
 RAID Level : 1
    Members : 2
  Slots : [UU]
  This Slot : 1
 Array Size : 1953519616 (931.51 GiB 1000.20 GB)
   Per Dev Size : 1953519880 (931.51 GiB 1000.20 GB)
  Sector Offset : 0
    Num Stripes : 7630936
 Chunk Size : 64 KiB
   Reserved : 0
  Migrate State : idle
  Map State : normal
    Dirty State : clean

  Disk00 Serial : STF604MH0J34LB
  State : active
 Id : 0002
    Usable Size : 1953520654 (931.51 GiB 1000.20 GB)

--
cat /etc/mdadm/mdadm.conf

# mdadm.conf
#
# Please refer to mdadm.conf(5) for information about this file.
#

# by default, scan all partitions (/proc/partitions) for MD superblocks.
# alternatively, specify devices to scan, using wildcards if desired.
DEVICE partitions

# auto-create devices with Debian standard permissions
CREATE owner=root group=disk mode=0660 auto=yes

# automatically tag new arrays as belonging to the local system
HOMEHOST system

# instruct the monitoring daemon where to send mail alerts
MAILADDR root

# definitions of existing MD arrays
ARRAY metadata=imsm UUID=084b969a:0808f5b8:6c784fb7:62659383
ARRAY /dev/md/OneTB-RAID1-PV container=084b969a:0808f5b8:6c784fb7:62659383 
member=0 UUID=ae4a1598:72267ed7:3b34867b:9c56497a

# This file was auto-generated on Fri, 05 Nov 2010 16:29:48 -0400
# by mkconf 3.1.4-1+8efb9d1


-M
  

--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/bay148-w18a88e7d84ce0213b44f26ef...@phx.gbl

RE: How to recreate a dmraid RAID array with mdadm

[Mike Viau]

 On Thu, 18 Nov 2010 11:11:49 +1100 ne...@suse.de wrote:

  On Wed, 17 Nov 2010 17:36:23 -0500 Mike Viau  wrote:
 
   On Wed, 17 Nov 2010 14:15:14 +1100
  
   This looks wrong. mdadm should be looking for the container as listed in
   mdadm.conf and it should find a matching uuid on sda and sdb, but it 
   doesn't.
  
   Can you:
  
   mdadm -E /dev/sda /dev/sdb ; cat /etc/mdadm/mdadm.conf
  
   so I can compare the uuids?
  
 
  Sure.
 
  # definitions of existing MD arrays ( So you don't have to scroll down :P )
 
  ARRAY metadata=imsm UUID=084b969a:0808f5b8:6c784fb7:62659383
 
  ARRAY /dev/md/OneTB-RAID1-PV container=084b969a:0808f5b8:6c784fb7:62659383 
  member=0 UUID=ae4a1598:72267ed7:3b34867b:9c56497a
 
 
 UUID : 084b969a:0808f5b8:6c784fb7:62659383
  [OneTB-RAID1-PV]:
 UUID : ae4a1598:72267ed7:3b34867b:9c56497a
 

 Yes, the uuids are definitely all correct.
 This really should work. I just tested a similar config and it worked
 exactly as exported.
 Weird.

 Whatever version of mdadm are you running???
 Can you try getting the latest (3.1.4) from
 http://www.kernel.org/pub/linux/utils/raid/mdadm/

I am running the same version, from a Debian Squeeze package which I presume is 
the same.

mdadm -V

mdadm - v3.1.4 - 31st August 2010


 and see how that works.
 Just
 make
 ./mdadm -Asvv

Regardless, I did recompile (attached is the make output -- no errors) and got 
similar mdadm output:

./mdadm -Asvv
mdadm: looking for devices for further assembly
mdadm: no RAID superblock on /dev/md126p1
mdadm: /dev/md126p1 has wrong uuid.
mdadm: no RAID superblock on /dev/md/OneTB-RAID1-PV
mdadm: /dev/md/OneTB-RAID1-PV has wrong uuid.
mdadm: no RAID superblock on /dev/dm-3
mdadm: /dev/dm-3 has wrong uuid.
mdadm: no RAID superblock on /dev/dm-2
mdadm: /dev/dm-2 has wrong uuid.
mdadm: no RAID superblock on /dev/dm-1
mdadm: /dev/dm-1 has wrong uuid.
mdadm: no RAID superblock on /dev/dm-0
mdadm: /dev/dm-0 has wrong uuid.
mdadm: no RAID superblock on /dev/loop0
mdadm: /dev/loop0 has wrong uuid.
mdadm: cannot open device /dev/sdc7: Device or resource busy
mdadm: /dev/sdc7 has wrong uuid.
mdadm: cannot open device /dev/sdc6: Device or resource busy
mdadm: /dev/sdc6 has wrong uuid.
mdadm: cannot open device /dev/sdc5: Device or resource busy
mdadm: /dev/sdc5 has wrong uuid.
mdadm: no RAID superblock on /dev/sdc2
mdadm: /dev/sdc2 has wrong uuid.
mdadm: cannot open device /dev/sdc1: Device or resource busy
mdadm: /dev/sdc1 has wrong uuid.
mdadm: cannot open device /dev/sdc: Device or resource busy
mdadm: /dev/sdc has wrong uuid.
mdadm: cannot open device /dev/sdb: Device or resource busy
mdadm: /dev/sdb has wrong uuid.
mdadm: cannot open device /dev/sda: Device or resource busy
mdadm: /dev/sda has wrong uuid.
mdadm: looking for devices for /dev/md/OneTB-RAID1-PV
mdadm: no recogniseable superblock on /dev/md126p1
mdadm/dev/md126p1 is not a container, and one is required.
mdadm: no recogniseable superblock on /dev/md/OneTB-RAID1-PV
mdadm/dev/md/OneTB-RAID1-PV is not a container, and one is required.
mdadm: no recogniseable superblock on /dev/dm-3
mdadm/dev/dm-3 is not a container, and one is required.
mdadm: no recogniseable superblock on /dev/dm-2
mdadm/dev/dm-2 is not a container, and one is required.
mdadm: no recogniseable superblock on /dev/dm-1
mdadm/dev/dm-1 is not a container, and one is required.
mdadm: no recogniseable superblock on /dev/dm-0
mdadm/dev/dm-0 is not a container, and one is required.
mdadm: no recogniseable superblock on /dev/loop0
mdadm/dev/loop0 is not a container, and one is required.
mdadm: cannot open device /dev/sdc7: Device or resource busy
mdadm/dev/sdc7 is not a container, and one is required.
mdadm: cannot open device /dev/sdc6: Device or resource busy
mdadm/dev/sdc6 is not a container, and one is required.
mdadm: cannot open device /dev/sdc5: Device or resource busy
mdadm/dev/sdc5 is not a container, and one is required.
mdadm: no recogniseable superblock on /dev/sdc2
mdadm/dev/sdc2 is not a container, and one is required.
mdadm: cannot open device /dev/sdc1: Device or resource busy
mdadm/dev/sdc1 is not a container, and one is required.
mdadm: cannot open device /dev/sdc: Device or resource busy
mdadm/dev/sdc is not a container, and one is required.
mdadm: cannot open device /dev/sdb: Device or resource busy
mdadm/dev/sdb is not a container, and one is required.
mdadm: cannot open device /dev/sda: Device or resource busy
mdadm/dev/sda is not a container, and one is required.


So what could this mean???


-M
  make

gcc -Wall -Werror -Wstrict-prototypes -Wextra -Wno-unused-parameter -ggdb 
-DSendmail=\/usr/sbin/sendmail -t\ -DCONFFILE=\/etc/mdadm.conf\ 
-DCONFFILE2=\/etc/mdadm/mdadm.conf\ -DMAP_DIR=\/dev/.mdadm\ 
-DMAP_FILE=\map\ -DMDMON_DIR=\/dev/.mdadm\ -DUSE_PTHREADS   -c -o mdadm.o 
mdadm.c
gcc -Wall -Werror -Wstrict-prototypes -Wextra -Wno-unused-parameter -ggdb 
-DSendmail=\/usr/sbin/sendmail -t\ -DCONFFILE=\/etc

RE: How to recreate a dmraid RAID array with mdadm

[Mike Viau]

 On Thu, 18 Nov 2010 12:28:47 +1100 ne...@suse.de wrote:
 
  I am running the same version, from a Debian Squeeze package which I 
  presume is the same.
 
  mdadm -V
 
  mdadm - v3.1.4 - 31st August 2010

 Yes, should be identical to what I am running.
 
  
   and see how that works.
   Just
   make
   ./mdadm -Asvv
 
  Regardless, I did recompile (attached is the make output -- no errors) and 
  got similar mdadm output:
 
  ./mdadm -Asvv
  mdadm: looking for devices for further assembly
  mdadm: no RAID superblock on /dev/md126p1
  mdadm: /dev/md126p1 has wrong uuid.
  mdadm: no RAID superblock on /dev/md/OneTB-RAID1-PV
  mdadm: /dev/md/OneTB-RAID1-PV has wrong uuid
 
  mdadm: cannot open device /dev/sdb: Device or resource busy
  mdadm: /dev/sdb has wrong uuid.
  mdadm: cannot open device /dev/sda: Device or resource busy
  mdadm: /dev/sda has wrong uuid.

 The arrays are clearly currently assembled. Trying to assemble them again is
 not likely to produce a good result :-) I should have said to ./mdadm -Ss
 first.

 Could you apply this patch and then test again with:

 ./mdadm -Ss
 ./mdadm -Asvvv


Applied the patch:

if (ident-uuid_set  (!update || strcmp(update, uuid)!= 0) 
    (!tst || !tst-sb ||
 same_uuid(content-uuid, ident-uuid, 
tst-ss-swapuuid)==0)) {
 if (report_missmatch) {
  char buf[200];
    fprintf(stderr, Name : %s has wrong uuid.\n,
    devname);
   fprintf(stderr,  want %s\n, 
__fname_from_uuid(ident-uuid, 0, buf, ':'));
   fprintf(stderr,  have %s\n, 
__fname_from_uuid(content-uuid, 0, buf, ':'));
   fprintf(stderr,  metadata=%s\n, tst-ss-name);
    }
    goto loop;
    }


And got:

./mdadm -Ss

mdadm: stopped /dev/md127


./mdadm -Asvvv

mdadm: looking for devices for further assembly
mdadm: no RAID superblock on /dev/dm-3
mdadm: /dev/dm-3 has wrong uuid.
 want UUID-084b969a:0808f5b8:6c784fb7:62659383
Segmentation fault


I took the liberty of extending the char buffer to 2000 bytes/chars and 64K 
(116) but got the same segfaults.


-M
  

--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/bay148-w149179108dc6d340247236ef...@phx.gbl

RE: How to recreate a dmraid RAID array with mdadm

[Mike Viau]

 On Thu, 18 Nov 2010 13:32:47 +1100 ne...@suse.de wrote:
  ./mdadm -Ss
 
  mdadm: stopped /dev/md127
 
 
  ./mdadm -Asvvv
 
  mdadm: looking for devices for further assembly
  mdadm: no RAID superblock on /dev/dm-3
  mdadm: /dev/dm-3 has wrong uuid.
   want UUID-084b969a:0808f5b8:6c784fb7:62659383
  Segmentation fault

 Try this patch instead please.

Applied new patch and got:

./mdadm -Ss

mdadm: stopped /dev/md127


./mdadm -Asvvv
mdadm: looking for devices for further assembly
mdadm: no RAID superblock on /dev/dm-3
mdadm: /dev/dm-3 has wrong uuid.
 want UUID-084b969a:0808f5b8:6c784fb7:62659383
 tst=0x10dd010 sb=(nil)
Segmentation fault


Again tried various buffer sizes (segfault above was with char buf[200];)


if (ident-uuid_set  (!update || strcmp(update, uuid)!= 0) 
    (!tst || !tst-sb ||
 same_uuid(content-uuid, ident-uuid, tst-ss-swapuuid)==0)) {
    if (report_missmatch) {
 char buf[116];
    fprintf(stderr, Name : %s has wrong uuid.\n,
    devname);
  fprintf(stderr,  want %s\n, __fname_from_uuid(ident-uuid, 0, buf, 
':'));
 fprintf(stderr,  tst=%p sb=%p\n, tst, tst?tst-sb:NULL);
 if (tst) {
   fprintf(stderr,  have %s\n, 
__fname_from_uuid(content-uuid, 0, buf, ':'));
    fprintf(stderr,  metadata=%s\n, tst-ss-name);
 }
    }
    goto loop;
}

  

--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/bay148-w494b0f5eb60cc742dfc817ef...@phx.gbl

RE: How to recreate a dmraid RAID array with mdadm

[Mike Viau]

 On Thu, 18 Nov 2010 14:17:18 +1100 ne...@suse.de wrote:
 
   On Thu, 18 Nov 2010 13:32:47 +1100  wrote:
./mdadm -Ss
   
mdadm: stopped /dev/md127
   
   
./mdadm -Asvvv
   
mdadm: looking for devices for further assembly
mdadm: no RAID superblock on /dev/dm-3
mdadm: /dev/dm-3 has wrong uuid.
want UUID-084b969a:0808f5b8:6c784fb7:62659383
Segmentation fault
  
   Try this patch instead please.
 
  Applied new patch and got:
 
  ./mdadm -Ss
 
  mdadm: stopped /dev/md127
 
 
  ./mdadm -Asvvv
  mdadm: looking for devices for further assembly
  mdadm: no RAID superblock on /dev/dm-3
  mdadm: /dev/dm-3 has wrong uuid.
   want UUID-084b969a:0808f5b8:6c784fb7:62659383
   tst=0x10dd010 sb=(nil)
  Segmentation fault

 Sorry... I guess I should have tested it myself..

 The
 if (tst) {

 Should be

 if (tst  content) {


Apply update and got:

mdadm: /dev/sdb is identified as a member of /dev/md/imsm0, slot -1.
mdadm: /dev/sda is identified as a member of /dev/md/imsm0, slot -1.
mdadm: added /dev/sda to /dev/md/imsm0 as -1
mdadm: added /dev/sdb to /dev/md/imsm0 as -1
mdadm: Container /dev/md/imsm0 has been assembled with 2 drives
mdadm: looking for devices for /dev/md/OneTB-RAID1-PV


Full output at: http://paste.debian.net/100103/
expires: 

2010-11-21 06:07:30
-M


  

--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/bay148-w508672292a737e86be8332ef...@phx.gbl

RE: How to recreate a dmraid RAID array with mdadm

[Mike Viau]

 On Thu, 18 Nov 2010 12:18:13 +1000 gcsgcatl...@bigpond.com wrote:
 
 Hi,
 I am just starting to use RAID on my systems and it was suggested that I make
 sure my drives were set to raid by: fdisk -l
 This should say that the relavent drives are set to raid auto-detect.
 Gerald



Where do you check raid auto-detect from fdisk?

fdisk -v

fdisk (util-linux-ng 2.17.2)


fdisk -l /dev/md/OneTB-RAID1-PV 

Disk /dev/md/OneTB-RAID1-PV: 1000.2 GB, 1000202043392 bytes
255 heads, 63 sectors/track, 121600 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x

 Device Boot  Start End  Blocks   Id  System
/dev/md/OneTB-RAID1-PV1   1  121600   976751968+  8e  Linux LVM


Also note that fdisk -l /dev/md/imsm0 returns nothing



-M
  

--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/bay148-w531bc61891b54bdc8cd34ef...@phx.gbl

RE: How to recreate a dmraid RAID array with mdadm (was: no subject)

[Mike Viau]

 On Mon, 15 Nov 2010 16:21:22 +1100 ne...@suse.de wrote:
  On Sun, 14 Nov 2010 01:50:42 -0500 Mike wrote:
  
  How does one fix the problem of not having the array not starting at boot?
 

 To be able to answer that one would need to know exactly what is in the
 initramfs. And unfortunately all distros are different and I'm not
 particularly familiar with Ubuntu.

 Maybe if you
 mkdir /tmp/initrd
 cd /tmp/initrd
 zcat /boot/initrd.img-2.6.32-5-amd64 | cpio -idv

 and then have a look around and particularly report etc/mdadm/mdadm.conf
 and anything else that might be interesting.

 If the mdadm.conf in the initrd is the same as in /etc/mdadm, then it
 *should* work.


Thanks again Neil. I got a chance to examine my systems initramfs to discover 
two differences in the local copy of mdadm.conf and the initramfs's copy.

The initramfs's copy contains:

DEVICE partitions
HOMEHOST system
ARRAY metadata=imsm UUID=084b969a:0808f5b8:6c784fb7:62659383
ARRAY /dev/md/OneTB-RAID1-PV container=084b969a:0808f5b8:6c784fb7:62659383 
member=0 UUID=ae4a1598:72267ed7:3b34867b:9c56497a

So both ARRAY lines got copied over to the initramfs's copy of mdadm.conf, but

CREATE owner=root group=disk mode=0660 auto=yes

and

MAILADDR root

were not carried over on the update-initramfs command.


To your clearly better understanding of all this, does the CREATE stanza NEED 
to be present in the initramfs's copy of mdadm.conf in order for the array to 
be created on boot? If so, how can one accomplish this, so that the line is 
added whenever a new initramfs is created for the kernel?


My diff findings between the local copy of mdadm.conf and the initramfs's copy 
pasted at:
http://debian.pastebin.com/5VNnd9g1


Thanks for your help.


-M
  

--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/bay148-w211ae8bf243615980ce527ef...@phx.gbl

RE: How to recreate a dmraid RAID array with mdadm (was: no subject)

[Mike Viau]

 On Wed, 17 Nov 2010 12:53:37 +1100 ne...@suse.de wrote:
 On Wed, 17 Nov 2010 01:39:39 +
 John Robinson  wrote:

  On 17/11/2010 01:26, Neil Brown wrote:
   On Tue, 16 Nov 2010 20:02:17 -0500
   Mike Viau wrote:
  [...]
   DEVICE partitions
   HOMEHOST
   ARRAY metadata=imsm UUID=084b969a:0808f5b8:6c784fb7:62659383
   ARRAY /dev/md/OneTB-RAID1-PV 
   container=084b969a:0808f5b8:6c784fb7:62659383 member=0 
   UUID=ae4a1598:72267ed7:3b34867b:9c56497a
  [...]
   I would really expect that mdadm.conf file to successfully assemble the
   RAID1.
 
  The only thing that strikes me is that DEVICE partitions line - surely
  imsm containers don't live in partitions?

 No, they don't.

 But DEVICE partitions actually means any devices listed
 in /proc/partitions, and that includes whole devices.
 :-(


I noticed both /dev/sda and /dev/sdb (the drives which make up the raid1 array) 
do not appear to recognized as having a valid container when one is required. 
The output of mdadm -Asvv shows:

mdadm -Asvv
mdadm: looking for devices for further assembly
mdadm: no RAID superblock on /dev/dm-3
mdadm: /dev/dm-3 has wrong uuid.
mdadm: no RAID superblock on /dev/dm-2
mdadm: /dev/dm-2 has wrong uuid.
mdadm: no RAID superblock on /dev/dm-1
mdadm: /dev/dm-1 has wrong uuid.
mdadm: no RAID superblock on /dev/dm-0
mdadm: /dev/dm-0 has wrong uuid.
mdadm: no RAID superblock on /dev/loop0
mdadm: /dev/loop0 has wrong uuid.
mdadm: cannot open device /dev/sdc7: Device or resource busy
mdadm: /dev/sdc7 has wrong uuid.
mdadm: cannot open device /dev/sdc6: Device or resource busy
mdadm: /dev/sdc6 has wrong uuid.
mdadm: cannot open device /dev/sdc5: Device or resource busy
mdadm: /dev/sdc5 has wrong uuid.
mdadm: no RAID superblock on /dev/sdc2
mdadm: /dev/sdc2 has wrong uuid.
mdadm: cannot open device /dev/sdc1: Device or resource busy
mdadm: /dev/sdc1 has wrong uuid.
mdadm: cannot open device /dev/sdc: Device or resource busy
mdadm: /dev/sdc has wrong uuid.
mdadm: cannot open device /dev/sdb: Device or resource busy
mdadm: /dev/sdb has wrong uuid.
mdadm: cannot open device /dev/sda: Device or resource busy
mdadm: /dev/sda has wrong uuid.
mdadm: looking for devices for /dev/md/OneTB-RAID1-PV
mdadm: no recogniseable superblock on /dev/dm-3
mdadm/dev/dm-3 is not a container, and one is required.
mdadm: no recogniseable superblock on /dev/dm-2
mdadm/dev/dm-2 is not a container, and one is required.
mdadm: no recogniseable superblock on /dev/dm-1
mdadm/dev/dm-1 is not a container, and one is required.
mdadm: no recogniseable superblock on /dev/dm-0
mdadm/dev/dm-0 is not a container, and one is required.
mdadm: no recogniseable superblock on /dev/loop0
mdadm/dev/loop0 is not a container, and one is required.
mdadm: cannot open device /dev/sdc7: Device or resource busy
mdadm/dev/sdc7 is not a container, and one is required.
mdadm: cannot open device /dev/sdc6: Device or resource busy
mdadm/dev/sdc6 is not a container, and one is required.
mdadm: cannot open device /dev/sdc5: Device or resource busy
mdadm/dev/sdc5 is not a container, and one is required.
mdadm: no recogniseable superblock on /dev/sdc2
mdadm/dev/sdc2 is not a container, and one is required.
mdadm: cannot open device /dev/sdc1: Device or resource busy
mdadm/dev/sdc1 is not a container, and one is required.
mdadm: cannot open device /dev/sdc: Device or resource busy
mdadm/dev/sdc is not a container, and one is required.
mdadm: cannot open device /dev/sdb: Device or resource busy
mdadm/dev/sdb is not a container, and one is required.
mdadm: cannot open device /dev/sda: Device or resource busy
mdadm/dev/sda is not a container, and one is required.


and cat /proc/partitions shows:

major minor  #blocks  name

   8    0  976762584 sda
   8   16  976762584 sdb
   8   32   78125000 sdc
   8   33 487424 sdc1
   8   34  1 sdc2
   8   37   20995072 sdc5
   8   38    7811072 sdc6
   8   39   48826368 sdc7
   7    0    4388218 loop0
 254    0   10485760 dm-0
 254    1   10485760 dm-1
 254    2   10485760 dm-2
 254    3   17367040 dm-3

  

--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/bay148-w57593947743ef205225d2aef...@phx.gbl

RE: How to recreate a dmraid RAID array with mdadm (was: no subject)

[Mike Viau]

 On Wed, 17 Nov 2010 12:26:47 +1100  wrote:

 On Mon, 15 Nov 2010 16:21:22 +1100  wrote:
 On Sun, 14 Nov 2010 01:50:42 -0500 Mike wrote:

 How does one fix the problem of not having the array not starting at boot?


 To be able to answer that one would need to know exactly what is in the
 initramfs. And unfortunately all distros are different and I'm not
 particularly familiar with Ubuntu.

 Maybe if you
 mkdir /tmp/initrd
 cd /tmp/initrd
 zcat /boot/initrd.img-2.6.32-5-amd64 | cpio -idv

 and then have a look around and particularly report etc/mdadm/mdadm.conf
 and anything else that might be interesting.

 If the mdadm.conf in the initrd is the same as in /etc/mdadm, then it
 *should* work.


 Thanks again Neil. I got a chance to examine my systems initramfs to 
 discover two differences in the local copy of mdadm.conf and the initramfs's 
 copy.

 The initramfs's copy contains:

 DEVICE partitions
 HOMEHOST
 ARRAY metadata=imsm UUID=084b969a:0808f5b8:6c784fb7:62659383
 ARRAY /dev/md/OneTB-RAID1-PV container=084b969a:0808f5b8:6c784fb7:62659383 
 member=0 UUID=ae4a1598:72267ed7:3b34867b:9c56497a

 So both ARRAY lines got copied over to the initramfs's copy of mdadm.conf, 
 but

 CREATE owner=root group=disk mode=0660 auto=yes

 and

 MAILADDR root

 were not carried over on the update-initramfs command.


 To your clearly better understanding of all this, does the CREATE stanza 
 NEED to be present in the initramfs's copy of mdadm.conf in order for the 
 array to be created on boot? If so, how can one accomplish this, so that the 
 line is added whenever a new initramfs is created for the kernel?

 No, those differences couldn't explain it not working.

 I would really expect that mdadm.conf file to successfully assemble the
 RAID1.

 As you have the same in /etc/mdadm/mdadm.conf you could see what is happening
 by:

 mdadm -Ss

 to stop all md arrays, then

 mdadm -Asvv

 to auto-start everything in mdadm.conf and be verbose about that is happening.

 If that fails to start the raid1, then the messages it produces will be
 helpful in understanding why.
 If it succeeds, then there must be something wrong with the initrd...
 Maybe '/sbin/mdmon' is missing... Or maybe it doesn't run
 mdadm -As
 (or equivalently: mdadm --assemble --scan)
 but doesn't something else. To determine what you would need to search for
 'mdadm' in all the scripts in the initrd and see what turns up.


Using mdadm -Ss stops the array:

mdadm: stopped /dev/md127


Where /dev/md127 is the imsm0 device and not the OneTB-RAID1-PV device.


Then executing mdadm -Asvv shows:

mdadm: looking for devices for further assembly
mdadm: no RAID superblock on /dev/dm-3
mdadm: /dev/dm-3 has wrong uuid.
mdadm: no RAID superblock on /dev/dm-2
mdadm: /dev/dm-2 has wrong uuid.
mdadm: no RAID superblock on /dev/dm-1
mdadm: /dev/dm-1 has wrong uuid.
mdadm: no RAID superblock on /dev/dm-0
mdadm: /dev/dm-0 has wrong uuid.
mdadm: no RAID superblock on /dev/loop0
mdadm: /dev/loop0 has wrong uuid.
mdadm: cannot open device /dev/sdc7: Device or resource busy
mdadm: /dev/sdc7 has wrong uuid.
mdadm: cannot open device /dev/sdc6: Device or resource busy
mdadm: /dev/sdc6 has wrong uuid.
mdadm: cannot open device /dev/sdc5: Device or resource busy
mdadm: /dev/sdc5 has wrong uuid.
mdadm: no RAID superblock on /dev/sdc2
mdadm: /dev/sdc2 has wrong uuid.
mdadm: cannot open device /dev/sdc1: Device or resource busy
mdadm: /dev/sdc1 has wrong uuid.
mdadm: cannot open device /dev/sdc: Device or resource busy
mdadm: /dev/sdc has wrong uuid.
mdadm: cannot open device /dev/sdb: Device or resource busy
mdadm: /dev/sdb has wrong uuid.
mdadm: cannot open device /dev/sda: Device or resource busy
mdadm: /dev/sda has wrong uuid.
mdadm: looking for devices for /dev/md/OneTB-RAID1-PV
mdadm: no recogniseable superblock on /dev/dm-3
mdadm/dev/dm-3 is not a container, and one is required.
mdadm: no recogniseable superblock on /dev/dm-2
mdadm/dev/dm-2 is not a container, and one is required.
mdadm: no recogniseable superblock on /dev/dm-1
mdadm/dev/dm-1 is not a container, and one is required.
mdadm: no recogniseable superblock on /dev/dm-0
mdadm/dev/dm-0 is not a container, and one is required.
mdadm: no recogniseable superblock on /dev/loop0
mdadm/dev/loop0 is not a container, and one is required.
mdadm: cannot open device /dev/sdc7: Device or resource busy
mdadm/dev/sdc7 is not a container, and one is required.
mdadm: cannot open device /dev/sdc6: Device or resource busy
mdadm/dev/sdc6 is not a container, and one is required.
mdadm: cannot open device /dev/sdc5: Device or resource busy
mdadm/dev/sdc5 is not a container, and one is required.
mdadm: no recogniseable superblock on /dev/sdc2
mdadm/dev/sdc2 is not a container, and one is required.
mdadm: cannot open device /dev/sdc1: Device or resource busy
mdadm/dev/sdc1 is not a container, and one is required.
mdadm: cannot open device /dev/sdc: Device or resource busy
mdadm/dev/sdc is not a container, and one is required.
mdadm: 

How to recreate a dmraid RAID array with mdadm (was: no subject)

[Mike Viau]

 On Sun, 14 Nov 2010 06:36:00 +1100 ne...@suse.de wrote:
 cat /proc/mdstat (showing what mdadm shows/discovers)

 Personalities :
 md127 : inactive sda[1](S) sdb[0](S)
 4514 blocks super external:imsm

 unused devices:

 As imsm can have several arrays described by one set of metadata, mdadm
 creates an inactive arrive just like this which just holds the set of
 devices, and then should create other arrays made of from different regions
 of those devices.
 It looks like mdadm hasn't done that you. You can ask it to with:

 mdadm -I /dev/md/imsm0

 That should created the real raid1 array in /dev/md/something.

 NeilBrown


Thanks for this information, I feel like I am getting closer to getting this 
working properly. After running the command above (mdadm -I /dev/md/imsm0), the 
real raid 1 array did appear as /dev/md/*

ls -al /dev/md
total 0
drwxr-xr-x  2 root root   80 Nov 14 00:53 .
drwxr-xr-x 21 root root 3480 Nov 14 00:53 ..
lrwxrwxrwx  1 root root    8 Nov 14 00:50 imsm0 - ../md127
lrwxrwxrwx  1 root root    8 Nov 14 00:53 OneTB-RAID1-PV - ../md126

---

And the kernel messages:

[ 4652.315650] md: bindsdb
[ 4652.315866] md: bindsda
[ 4652.341862] raid1: md126 is not clean -- starting background reconstruction
[ 4652.341958] raid1: raid set md126 active with 2 out of 2 mirrors
[ 4652.342025] md126: detected capacity change from 0 to 1000202043392
[ 4652.342400]  md126: p1
[ 4652.528448] md: md126 switched to read-write mode.
[ 4652.529387] md: resync of RAID array md126
[ 4652.529424] md: minimum _guaranteed_  speed: 1000 KB/sec/disk.
[ 4652.529464] md: using maximum available idle IO bandwidth (but not more than 
20 KB/sec) for resync.
[ 4652.529525] md: using 128k window, over a total of 976759940 blocks.
 
---

fdisk -ul /dev/md/OneTB-RAID1-PV 

Disk /dev/md/OneTB-RAID1-PV: 1000.2 GB, 1000202043392 bytes
255 heads, 63 sectors/track, 121600 cylinders, total 1953519616 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x

 Device Boot  Start End  Blocks   Id  System
/dev/md/OneTB-RAID1-PV1  63  1953503999   976751968+  8e  Linux LVM

---

pvscan 

  PV /dev/sdc7  VG XENSTORE-VG  lvm2 [46.56 GiB / 0    free]
  PV /dev/md126p1   VG OneTB-RAID1-VG   lvm2 [931.50 GiB / 0    free]
  Total: 2 [978.06 GiB] / in use: 2 [978.06 GiB] / in no VG: 0 [0   ]

---

pvdisplay 

 --- Physical volume ---
  PV Name   /dev/md126p1
  VG Name   OneTB-RAID1-VG
  PV Size   931.50 GiB / not usable 3.34 MiB
  Allocatable   yes (but full)
  PE Size   4.00 MiB
  Total PE  238464
  Free PE   0
  Allocated PE  238464
  PV UUID   hvxXR3-tV9B-CMBW-nZn2-N2zH-N1l6-sC9m9i



vgscan 

  Reading all physical volumes.  This may take a while...
  Found volume group XENSTORE-VG using metadata type lvm2
  Found volume group OneTB-RAID1-VG using metadata type lvm2

-

vgdisplay

--- Volume group ---
  VG Name   OneTB-RAID1-VG
  System ID 
  Format    lvm2
  Metadata Areas    1
  Metadata Sequence No  2
  VG Access read/write
  VG Status resizable
  MAX LV    0
  Cur LV    1
  Open LV   0
  Max PV    0
  Cur PV    1
  Act PV    1
  VG Size   931.50 GiB
  PE Size   4.00 MiB
  Total PE  238464
  Alloc PE / Size   238464 / 931.50 GiB
  Free  PE / Size   0 / 0   
  VG UUID   nCBsU2-VpgR-EcZj-lA15-oJGL-rYOw-YxXiC8



vgchange -a y OneTB-RAID1-VG

  1 logical volume(s) in volume group OneTB-RAID1-VG now active



lvdisplay 

--- Logical volume ---
  LV Name    /dev/OneTB-RAID1-VG/OneTB-RAID1-LV
  VG Name    OneTB-RAID1-VG
  LV UUID    R3TYWb-PJo1-Xzbm-vJwu-YpgP-ohZW-Vf1kHJ
  LV Write Access    read/write
  LV Status  available
  # open 0
  LV Size    931.50 GiB
  Current LE 238464
  Segments   1
  Allocation inherit
  Read ahead sectors auto
  - currently set to 256
  Block device   253:4



fdisk -ul /dev/OneTB-RAID1-VG/OneTB-RAID1-LV 

Disk /dev/OneTB-RAID1-VG/OneTB-RAID1-LV: 1000.2 GB, 1000190509056 bytes
255 heads, 63 sectors/track, 121599 cylinders, total 1953497088 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0xbda8e40b

 Device Boot  Start End  Blocks   
Id  System
/dev/OneTB-RAID1-VG/OneTB-RAID1-LV1  63  1953487934   976743936   

RE: how to resetup fake-raid

[Mike Viau]

So it looks like I can not even access the md device the system created on 
boot. 

Does anyone have a guide or tips to migrating from the older dmraid to mdadm 
for fake-raid?


fdisk -uc /dev/md127  (showing the block device is inaccessible)

Unable to read /dev/md127


dmesg (pieces of dmesg/booting)

[    4.214092] device-mapper: uevent: version 1.0.3
[    4.214495] device-mapper: ioctl: 4.15.0-ioctl (2009-04-01) initialised: 
dm-de...@redhat.com
[    5.509386] udev[446]: starting version 163
[    7.181418] md: md127 stopped.
[    7.183088] md: bindsdb
[    7.183179] md: bindsda


Thanks.

-M


 To: debian-user@lists.debian.org
 Subject: how to resetup fake-raid
 Date: Thu, 11 Nov 2010 08:10:55 -0500


 Hello,

 I am trying to re-setup my fake-raid (RAID1) volume with LVM2 like setup 
 previously. I had been using dmraid on a Lenny installation which gave me 
 (from memory) a block device like /dev/mapper/isw_xxx_ and also a 
 /dev/OneTB-RAID1, but have discovered that the mdadm has replaced the older 
 and believed to be obsolete dmraid for multiple disk/raid support.

 Automatically the fake-raid LVM physical volume does not seem to be set up. I 
 believe my data is safe as I can insert a knoppix live-cd in the system and 
 mount the fake-raid volume (and browse the files). I am planning on perhaps 
 purchasing another at least 1TB drive to backup the data before trying to 
 much fancy stuff with mdadm in fear of loosing the data.

 A few commands that might shed more light on the situation:


 pvdisplay (showing the /dev/md/[device] not recognized yet by LVM2)

 --- Physical volume ---
 PV Name /dev/sdc7
 VG Name XENSTORE-VG
 PV Size 46.56 GiB / not usable 2.00 MiB
 Allocatable yes (but full)
 PE Size 4.00 MiB
 Total PE 11920
 Free PE 0
 Allocated PE 11920
 PV UUID wRa8xM-lcGZ-GwLX-F6bA-YiCj-c9e1-eMpPdL


 cat /proc/mdstat (showing what mdadm shows/discovers)

 Personalities :
 md127 : inactive sda[1](S) sdb[0](S)
 4514 blocks super external:imsm

 unused devices:


 ls -l /dev/md/imsm0 (showing contents of /dev/md/* [currently only one 
 file/link ])

 lrwxrwxrwx 1 root root 8 Nov 7 08:07 /dev/md/imsm0 - ../md127


 ls -l /dev/md127 (showing the block device)

 brw-rw 1 root disk 9, 127 Nov 7 08:07 /dev/md127


 update-initramfs -u (Perhaps the most interesting error of them all)

 update-initramfs: Generating /boot/initrd.img-2.6.32-5-xen-amd64
 mdadm: cannot open /dev/md/OneTB-RAID1-PV: No such file or directory


 Thanks for any ones help :)


  

--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/bay148-w33734836710f9a769cd781ef...@phx.gbl

RE: how to resetup fake-raid

[Mike Viau]

 On Fri, 12 Nov 2010 19:48:48 -0500 tomh0...@gmail.com wrote:
 On Fri, Nov 12, 2010 at 7:13 PM, Mike V.  wrote:
  To: debian-user@lists.debian.org
  Date: Thu, 11 Nov 2010 08:10:55 -0500
 
  I am trying to re-setup my fake-raid (RAID1) volume with LVM2 like setup
  previously. I had been using dmraid on a Lenny installation which gave me
  (from memory) a block device like /dev/mapper/isw_xxx_ and also
  a /dev/OneTB-RAID1, but have discovered that the mdadm has replaced
  the older and believed to be obsolete dmraid for multiple disk/raid 
  support.
 
  Automatically the fake-raid LVM physical volume does not seem to be set up.
  I believe my data is safe as I can insert a knoppix live-cd in the system 
  and
  mount the fake-raid volume (and browse the files). I am planning on perhaps
  purchasing another at least 1TB drive to backup the data before trying too
  much fancy stuff with mdadm in fear of loosing the data.
 
  pvdisplay (showing the /dev/md/[device] not recognized yet by LVM2)
  --- Physical volume ---
  PV Name /dev/sdc7
  VG Name XENSTORE-VG
  PV Size 46.56 GiB / not usable 2.00 MiB
  Allocatable yes (but full)
  PE Size 4.00 MiB
  Total PE 11920
  Free PE 0
  Allocated PE 11920
  PV UUID wRa8xM-lcGZ-GwLX-F6bA-YiCj-c9e1-eMpPdL
 
  cat /proc/mdstat
  Personalities :
  md127 : inactive sda[1](S) sdb[0](S)
  4514 blocks super external:imsm
 
  ls -l /dev/md/imsm0
  lrwxrwxrwx 1 root root 8 Nov 7 08:07 /dev/md/imsm0 - ../md127
 
  ls -l /dev/md127
  brw-rw 1 root disk 9, 127 Nov 7 08:07 /dev/md127
 
  update-initramfs -u
  update-initramfs: Generating /boot/initrd.img-2.6.32-5-xen-amd64
  mdadm: cannot open /dev/md/OneTB-RAID1-PV: No such file or directory
 
  So it looks like I can not even access the md device the system created on
  boot. Does anyone have a guide or tips to migrating from the older dmraid
  to mdadm for fake-raid?
 
  fdisk -uc /dev/md127
  Unable to read /dev/md127
 
  dmesg
  [ 4.214092] device-mapper: uevent: version 1.0.3
  [ 4.214495] device-mapper: ioctl: 4.15.0-ioctl (2009-04-01) initialised: 
  dm-de...@redhat.com
  [ 5.509386] udev[446]: starting version 163
  [ 7.181418] md: md127 stopped.
  [ 7.183088] md: bind
  [ 7.183179] md: bind

 No necessarily being helpful but thought that I'd point out that
 pvdisplay shows /dev/sdc7 not /dev/md127 and cat /proc/mdstat
 shows both sda and sdb as spares...

 I'd ask on the mdraid list if I were you, especially since mdraid
 replacing dmraid must be a recent change.



Thanks for the feedback. The physical logical volume on /dev/sdc7 actually not 
part of the fake-raid that I am trying to setup again, but /dev/sd[ab] certain 
are.

I assume the '(S)' denoted them are spares? Do you know if there is any way to 
'activate' them both for use like in 'activating' a LVM volume group?

I noticed there is a Linux raid mailing list at: 
http://vger.kernel.org/vger-lists.html#linux-raid

Is this the mailing list you were referring too? It seems like a devel list 
with patch submissions and stuff by looking at the archives. That is why I 
thought I'd try my luck on a user list as I am running Debian squeeze.
  

--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/bay148-w46ec0af1b6bf1a06e0472bef...@phx.gbl

[no subject]

[Mike Viau]

Hello,

I am trying to re-setup my fake-raid (RAID1) volume with LVM2 like setup 
previously. I had been using dmraid on a Lenny installation which gave me (from 
memory) a block device like /dev/mapper/isw_xxx_ and also a 
/dev/One1TB, but have discovered that the mdadm has replaced the older and 
believed to be obsolete dmraid for multiple disk/raid support.

Automatically the fake-raid LVM physical volume does not seem to be set up. I 
believe my data is safe as I can insert a knoppix live-cd in the system and 
mount the fake-raid volume (and browse the files). I am planning on perhaps 
purchasing another at least 1TB drive to backup the data before trying to much 
fancy stuff with mdadm in fear of loosing the data.

A few commands that might shed more light on the situation:


pvdisplay (showing the /dev/md/[device] not recognized yet by LVM2, note sdc 
another single drive with LVM)

  --- Physical volume ---
  PV Name   /dev/sdc7
  VG Name   XENSTORE-VG
  PV Size   46.56 GiB / not usable 2.00 MiB
  Allocatable   yes (but full)
  PE Size   4.00 MiB
  Total PE  11920
  Free PE   0
  Allocated PE  11920
  PV UUID   wRa8xM-lcGZ-GwLX-F6bA-YiCj-c9e1-eMpPdL


cat /proc/mdstat (showing what mdadm shows/discovers)

Personalities :
md127 : inactive sda[1](S) sdb[0](S)
  4514 blocks super external:imsm

unused devices: 


ls -l /dev/md/imsm0 (showing contents of /dev/md/* [currently only one 
file/link ])

lrwxrwxrwx 1 root root 8 Nov  7 08:07 /dev/md/imsm0 - ../md127


ls -l /dev/md127 (showing the block device)

brw-rw 1 root disk 9, 127 Nov  7 08:07 /dev/md127




It looks like I can not even access the md device the system created on boot. 

Does anyone have a guide or tips to migrating from the older dmraid to mdadm 
for fake-raid?


fdisk -uc /dev/md127  (showing the block device is inaccessible)

Unable to read /dev/md127


dmesg (pieces of dmesg/booting)

[    4.214092] device-mapper: uevent: version 1.0.3
[    4.214495] device-mapper: ioctl: 4.15.0-ioctl (2009-04-01) initialised: 
dm-de...@redhat.com
[    5.509386] udev[446]: starting version 163
[    7.181418] md: md127 stopped.
[    7.183088] md: bindsdb
[    7.183179] md: bindsda



update-initramfs -u (Perhaps the most interesting error of them all, I can 
confirm this occurs with a few different kernels)

update-initramfs: Generating /boot/initrd.img-2.6.32-5-xen-amd64
mdadm: cannot open /dev/md/OneTB-RAID1-PV: No such file or directory


Revised my information, inital thread on Debian-users thread at:
http://lists.debian.org/debian-user/2010/11/msg01015.html

Thanks for any ones help :)

-M
  

--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/bay148-w34f1b0624b57b12374ac90ef...@phx.gbl

how to resetup fake-raid

[Mike Viau]

Hello,

I am trying to re-setup my fake-raid (RAID1) volume with LVM2 like setup 
previously. I had been using dmraid on a Lenny installation which gave me (from 
memory) a block device like /dev/mapper/isw_xxx_ and also a 
/dev/One1TB, but have discovered that the mdadm has replaced the older and 
believed to be obsolete dmraid for multiple disk/raid support.

Automatically the fake-raid LVM physical volume does not seem to be set up. I 
believe my data is safe as I can insert a knoppix live-cd in the system and 
mount the fake-raid volume (and browse the files). I am planning on perhaps 
purchasing another at least 1TB drive to backup the data before trying to much 
fancy stuff with mdadm in fear of loosing the data.

A few commands that might shed more light on the situation:


pvdisplay (showing the /dev/md/[device] not recognized yet by LVM2)

  --- Physical volume ---
  PV Name   /dev/sdc7
  VG Name   XENSTORE-VG
  PV Size   46.56 GiB / not usable 2.00 MiB
  Allocatable   yes (but full)
  PE Size   4.00 MiB
  Total PE  11920
  Free PE   0
  Allocated PE  11920
  PV UUID   wRa8xM-lcGZ-GwLX-F6bA-YiCj-c9e1-eMpPdL


cat /proc/mdstat (showing what mdadm shows/discovers)

Personalities :
md127 : inactive sda[1](S) sdb[0](S)
  4514 blocks super external:imsm

unused devices: 


ls -l /dev/md/imsm0 (showing contents of /dev/md/* [currently only one 
file/link ])

lrwxrwxrwx 1 root root 8 Nov  7 08:07 /dev/md/imsm0 - ../md127


ls -l /dev/md127 (showing the block device)

brw-rw 1 root disk 9, 127 Nov  7 08:07 /dev/md127


update-initramfs -u (Perhaps the most interesting error of them all)

update-initramfs: Generating /boot/initrd.img-2.6.32-5-xen-amd64
mdadm: cannot open /dev/md/OneTB-RAID1-PV: No such file or directory


Thanks for any ones help :)


-Mike Viau


  

--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/bay148-w5124f0ccd4fc01acff2434ef...@phx.gbl

RE: WiFi: nm-applet, nm-editor, replace NetworkManager

[Mike Viau]

 On Wed, 13 Oct 2010 10:04:37 +0200 sjo...@lorentz.leidenuniv.nl wrote:

 A question about Wicid.
 * ability to connect to (and maintain profiles for) both wired and
 wireless networks;
 So does this mean that wicid can _not_ control/setup network bridges (e.g: 
 with brctl)?

 Not sure. Try the wicd forum.

 It doesn't. I understood support for bridging networks is planned for
 some illustrious wicd v2


Thanks, may I inquire as to your source?

From another site it does not list the possibility of bridge support being 
added.

This includes connecting to multiple interfaces, and PPP, VPN, and Mobile 
Broadband. These are planned for Wicd v2. [1]


[1] - http://www.linuxadventures.net/reviews/wicd.html


Regards,
-M
  

--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/bay148-w4200e9ba9b222ede23ae6bef...@phx.gbl

RE: Nouveau

[Mike Viau]

 On Tue, 12 Oct 2010 22:27:39 +0200  wrote:

 I am running a 2.6.32.5 kernel using Nouveau on an nvidia pci-express card.
 Seems to me games like penguin racer and such should run fine on this (even if
 not as well as with the proprietary nvidia drivers). They run, however, as if
 there were no direct rendering at all. Even chromium which ran fine on my old
 system using a junk Matrox card bugs down here.

 Nouveau's bootup sequence says DRI active.

 Man page list three options for the driver and I let them all default.


I am running a similar setup see what you mean about video performance, but no 
guarantees are made by the nouveau developers in regards to 3D 
performance/rendering.

I was under the impression the chromium ran in 2D and thus should not have 
bogged down, I might be mistaken about this. Video playback within a web page 
is another story.

I am also unable to throw my laptop into sleep with this kernel/nouveau setup. 
Is this just an anomaly with just my hardware or does it happen on yours as 
well?


-M


  

--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/bay148-w410429ba94087a5f520d69ef...@phx.gbl

RE: WiFi: nm-applet, nm-editor, replace NetworkManager

[Mike Viau]

 OnTue, 12 Oct 2010 14:11:13 -0700 hol...@cox.net wrote:
 
 3. This is not the first time I am having problems with NetworkManager
 here on Debian, so I think I will get rid of it. The question is how to
 switch between available WiFi connections without NetworkManager.

 Wicd from the repos. Much more informative than nm.


A question about Wicid.
 * ability to connect to (and maintain profiles for) both wired and
   wireless networks;
So does this mean that wicid can _not_ control/setup network bridges (e.g: with 
brctl)?

Just wanted to be sure.


Thanks.


-M
  

--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/bay148-w286ed38980452a4b8e9a84ef...@phx.gbl

RE: nvidia-kernel-2.6-amd64 vs nvidia-kernel-dkms method

[Mike Viau]

 On Mon, 27 Sep 2010 23:45:01 -0500 m...@allums.com wrote:
 
 Has the nouveau code been stripped from the nvidia-kernel-2.6 packages
 so that it only used the NVIDIA driver module?

 They were still in staging, last I looked. That means that you have to
 enable staging drivers in the kernel source configuration and compile a
 custom kernel. This may not be the case for very recent kernels, such
 as 2.6.35/36, but I haven't checked lately.


I believe this is correct judging by:

24.3.2010 posted by xavier

Merge of 2.6.34-rc2.

 On Monday, nouveau git tree went straight from 2.6.32 to 2.6.34-rc2. One 
backlight API change
in 2.6.34-rc2 breaks compatibility with older kernels (
2.6.34-rc2), so people doing out-of-tree builds will have to update
their kernel to rc2. Alternatively, you could try to revert the backlight 
commit. 

[1] http://nouveau.freedesktop.org/wiki/
  

--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/bay148-w13737ed231a132f9f4e4b7ef...@phx.gbl

RE: [News] Flash player plugin (64 bits) comes back!

[Mike Viau]

 On Fri, 17 Sep 2010 15:20:12 -0500 m...@allums.com

 On Date: Fri, 17 Sep 2010 15:15:27 +0100 wrote:

 I dont know, they are normally pretty quick, but if you cant wait,
 purge any other flash plugins, and download the .so and drop it into
 /usr/lib/mozilla/plugins and it should be picked up by pretty much
 everything!

 Yes, the 64-bit shared lib, code-named square is pretty much a true
 drop-in replacement for the 32-bit version.

 Works for me.

 +1


And now its available on squeeze under the flashplugin-nonfree package:

http://packages.debian.org/squeeze/flashplugin-nonfree

Remember to remove your previous flashplugin .so file if you couldn't wait like 
me.

Enjoy!


-M

  

--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/bay148-w4940b7c090f2333c3bdd51ef...@phx.gbl

nvidia-kernel-2.6-amd64 vs nvidia-kernel-dkms method

[Mike Viau]

Hello,

I was just wondering what the advantages of using the nvidia-kernel-2.6 
packages were in contrast to what I am/have been using which is the nvidia-glx 
package which depends on nvidia-kernel-dkms to compile the NVIDIA driver module 
(with the kernel headers) into 
/lib/modules/${kernel_version}/updates/dkms/nvidia.ko

Has the nouveau code been stripped from the nvidia-kernel-2.6 packages so that 
it only used the NVIDIA driver module?

Thanks.


-M


  

--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/bay148-w53d03a384bffdf4675b8aaef...@phx.gbl

RE: Problem installing mount in Sid amd64!

[Mike Viau]

 On Mon, 27 Sep 2010 11:53:40 +0200 smu...@gmail.com wrote:

 Hey,

 Long time on again off again, user.

 Have a sid-box up and running, last time i did a apt-get update 
 apt-get -u upgrade it got stuck when it was trying to install 'mount'

 Preparing to replace mount 2.17.2-3.1 (using .../mount_2.17.2-3.2_amd64.deb) 
 ...
 Unpacking replacement mount ...

 and nothing happens, even tried to kill the dpkg process.. nothing happens.

 Known issue?

 yes, i run amd64 port..

 sorry if this is in the wrong list.


Do all packages seem to hang during the installation phase or is mount the only 
one?

Perhaps you could install another package temporarily to see if the same thing 
happens.


-M
  

--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/bay148-w442b425f9aedd09633a8f8ef...@phx.gbl

RE: Squeeze. nVidia video. How to change brightness with functional (Fn) keys?

[Mike Viau]

 On Mon, 27 Sep 2010 15:49:47 +0400 mark.goldsht...@gmail.com wrote:

 Hello, list!

 Lenovo Y450-3M laptop with:
 01:00.0 VGA compatible controller: nVidia Corporation GT216 [GeForce
 GT 240M] (rev a2)
 Subsystem: Lenovo Device 38fd
 Kernel driver in use: nvidia

 Would you, please, to explain how to configure a system or edit
 configuration files in order to bring laptop brightness funktional
 keys (Fn+key) to thier normal work? It is impossible to adjust
 brightness pressing Fn+UpArrow and Fn+DownArrow keys. The symbol of
 brightness is displaying well, but no adjust actually happen.

 Googling left me unsure about what I have to do to correct this issue.
 There are mostly comments from Ubuntu users. I know Ubuntu is Debian
 based but need to be understanding what I am doing with my system. If
 you have a little time, please, help.

 Thanks in advance!


On my Lenovo laptop with NVIDIA video, I find Fn+home and Fn+End work to 
control the LCD brightness on a stock installation of Squeeze so maybe you 
could give that a try?

I am running the GNOME DE. To save power while on battery, you may wish to 
install the laptop-mode-tools package as well.


-M
  

--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/bay148-w27eb2748144438fdea11acef...@phx.gbl

RE: Release File Expired on: csclub.uwaterloo.ca

[Mike Viau]

 On Date: Fri, 24 Sep 2010 11:49:36 -0400 pgalla...@gmail.com wrote:

 I emailed the KWLUG (Kitchener-Waterloo LUG) and some of the U.
 Waterloo CS Club members are also members of the KWLUG. Anyway, here's
 what Kyle had to say about it:

 Last week there was a power outage which forced us to shut off the
 mirror. We shutdown cleanly, but for some reason there was an error
 with the RAID array, so it has been rebuilding for the last few days.
 You can check the progress on http://mirror.csclub.uwaterloo.ca/.

 We are still an official mirror, we are just experiencing some very
 unfortunate downtime. :(

 http://mirror.csclub.uwaterloo.ca/ 

 At the time of this writing the array rebuild is at 95%.
 --

This is good info!

I look forward to restoring my sources back to this very fast Canadian mirror 
(at least for where I am located).

Thanks.


-M
  

--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/bay148-w214fb0067a5a5f1b4bd2cbef...@phx.gbl

Release File Expired on: csclub.uwaterloo.ca

[Mike Viau]

Hello,

I am not really sure to whom I should inform, but it is my understanding that 
mirror.csclub.waterloo.ca is (or at least was) an official Debian mirror in 
Canada.

I am in no way affiliated with the Waterloo university or aware of a contact 
for the mirror.

It appears as if their apt-repo has expired in some way?

After changing my sources to point to http.us.debian.org, the error went away 
immediately.

I thought I should mention it hear, as I am hoping at least one of the more 
enlighten Debian user might know whats going on, or what can be done to get the 
mirror back up!


Thanks


-M


  attachment: csclub.uwaterloo.ca.png

FW: [Xen-devel] xen 4 only seeing one keyboard and mouse, fixed in xen 4.0.2-rc-pre

[Mike Viau]

 On Mon, 20 Sep 2010 18:05:06 +0300 pa...@iki.fi wrote:
 
 On Mon, Sep 20, 2010 at 10:51:52AM -0400, Konrad Rzeszutek Wilk wrote:
 On Fri, Sep 17, 2010 at 11:49:02PM +0100, M A Young wrote:
 On Wed, 8 Sep 2010, Konrad Rzeszutek Wilk wrote:

Compared this to how Xen works it is pretty much exactly the same.
Except that I think Xen forces the IO APIC to be reset. Here it looks
as if it is untouched from the boot - but who knows?

I think you need to figure out who sets the IO APIC entries earlier
on. It might be as well that nobody does and this is what the BIOS
came up and under Xen we clear it up.

 The latest 4.0.2-rc1-pre fixes my problem. I saw the patch
 http://xenbits.xensource.com/xen-4.0-testing.hg?rev/965d47d5d7c2
 which looked relevant, so I tried a build including it and my laptop
 keyboard and mouse work again.

 Woot! Excellent!


 Yeah, good to hear this got resolved.

 Debian folks might want to include that patch in their Xen .deb packages
 for upcoming Squeeze (6.0) release..

 -- Pasi

Message forwarded from the Xen mailing list for both Debian Xen Developers and 
Users :)


-M
  

--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/bay148-w606f810a34b0ccc9f7a6b6ef...@phx.gbl

RE: Viewing Office 2007 files

[Mike Viau]

 On Sun, 19 Sep 2010 14:02:27 + noela...@gmail.com wrote:

 On Sun, 19 Sep 2010 13:41:40 +, T o n g wrote:

 It's so annoying that Ms changes its file format again and people
 started to jumping ships. I can't view any of the Office 2007 files that
 people sent me. What's your solution to it (word and excel)?

 OpenOffice 3.x (Go-oo) can handle most of them (.docx/.xlsx).

I agree with that. Additionally, I've found more formatting issue with office 
2010 files then I have with 2007, but some issues do exist with both Microsoft 
office suites in OpenOffice.


 What OOo version do you have?


  

--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/bay148-w45312fd43597103a98d4e0ef...@phx.gbl

RE: ps - Illegal Instruction

[Mike Viau]

 On Date: Sun, 19 Sep 2010 20:15:42 -0400 jstuc...@attglobal.net

 This is a new install of Lenny on Windows 7 Virtual PC. I basically
 took the defaults, with a couple of changes to get it to install and get
 gnome's display correct.

 I still have several problems, which may be related. The easiest one to
 find is an Illegal Instruction when I run a simple ps command. This
 occurs whether I run as a user or root.

 I've done a lot of looking, but don't seem to find anything similar.
 Does anyone have any ideas?

 I'm still pretty much a noob on Linux, so please be gentle :)


Have you tried any other Linux environments through your Virtual PC?

Or maybe even tried Virtual Box or VMware on Windows 7 to run Linux?

I have had sucess with both, but I never tried Microsoft's Virtual PC.


-M
  

--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/bay148-w53ae556bb674358520a3b3ef...@phx.gbl

RE: How can one compare two PDFs?

[Mike Viau]

 On Fri, 17 Sep 2010 08:05:40 + noela...@gmail.com wrote:
 
 On Thu, 16 Sep 2010 23:14:03 +0200, Merciadri Luca wrote:
 
  AFAIK, PDFs cannot be compared directly. Can diff (in Lenny repos)
  compare two PDFs? Are there any other solutions?
 
 I've only seen such advanced options in Adobe Acrobat Professional 
 products, but diffpdf suggested by Thierry is worth a try.
 

What is the closest GNU/Debian equivalent to Adobe Professional?

I have been enjoying cups PDF printer so soft copies of my document, but never 
found a good PDF edit in Debian.

My squeeze install uses document viewer with PDFs, which does not allow 
corrections to be made.


-M
  

RE: How can one compare two PDFs?

[Mike Viau]

 On Fri, 17 Sep 2010 23:07:52 +1000 prettyfly.producti...@gmail.com wrote:
 
 While it's not Adobe Professional I like flpsed - it'll do most of
what you require.

 Generally I find it easier to just do everything as a document and
export the pdf. Foomatic-rip is useful too.



 Cheers

Thanks for the find! Make more sense that way :)


-M
  

RE: [News] Flash player plugin (64 bits) comes back!

[Mike Viau]

 On Date: Fri, 17 Sep 2010 15:15:27 +0100 demide...@gmail.com wrote:
 
 I dont know, they are normally pretty quick, but if you cant wait,
 purge any other flash plugins, and download the .so and drop it into
 /usr/lib/mozilla/plugins and it should be picked up by pretty much
 everything!


+1

And the .so file for preview 64-bit adobe flash can be found inside the tarball 
for Linux.


-M
  

RE: make-kpkg (from kernel-package) does not build xen patched kernel

[Mike Viau]

Going to try a make-file patch when I get some time.

The patch was offered from a user on the Xen-user mailing list.

[1] http://lists.xensource.com/archives/html/xen-users/2010-09/msg00396.html


-M




 Subject: make-kpkg (from kernel-package) does not build xen patched kernel
 Date: Tue, 14 Sep 2010 16:16:31 -0400

 Hello list,

 I cannot get make-kpkg to build a Xenlinux type kernel into a Debian
 kernel binary on my Debian Squeeze x86_64 system.

 I am using GNU/Linux kernel sources tree (2.6.34.4) with Xen patches
 for this custom kernel. I am trying to use the make-kpkg command to
 build a working linux-image-2.6.34.4-xen-amd64 package for my system.

 The sources are vanilla (available from kernel.org) with patches
 available from:
 http://gentoo-xen-kernel.googlecode.com/files/xen-patches-2.6.34-4.tar.bz2

 These sources compile a Xenlinux kernel and not a pv_ops one so the bug
 report for XEN and the kernel-package is not applicable
 (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=574957)

 It seems that when the kernel_image target is used, a
 System.map-2.6.34.4-xen can not be generated, and therefore a FATAL
 error causes the make-kpkg process to fail!

 A System.map-2.6.34.4-xen can be generated when the kernel is built and
 packaged into a Debian binary with make deb-pkg.

 Can anyone else reproduce this problem?


 uname -a
 Linux BUBBLE 2.6.34.4-r61-xen #1 SMP Tue Sep 14 10:39:11 EDT 2010
 x86_64 GNU/Linux

 apt-cache policy kernel-package
 kernel-package:
 Installed: 12.036
 Candidate: 12.036
 Version table:
 *** 12.036 0
 500 http://mirror.csclub.uwaterloo.ca/debian/ squeeze/main
 amd64 Packages
 100 /var/lib/dpkg/status



 -M

  

--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/bay148-w26797a860546be0560a52ef...@phx.gbl

make-kpkg (from kernel-package) does not build xen patched kernel

[Mike Viau]

Hello list,

I cannot get make-kpkg to build a Xenlinux type kernel into a Debian kernel 
binary on my Debian Squeeze x86_64 system.

I am using GNU/Linux kernel sources tree (2.6.34.4) with Xen patches for this 
custom kernel. I am trying to use the make-kpkg command to build a working 
linux-image-2.6.34.4-xen-amd64 package for my system.

The sources are vanilla (available from kernel.org) with patches available 
from: http://gentoo-xen-kernel.googlecode.com/files/xen-patches-2.6.34-4.tar.bz2

These sources compile a Xenlinux kernel and not a pv_ops one so the bug report 
for XEN and the kernel-package is not applicable 
(http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=574957)

It seems that when the kernel_image target is used, a System.map-2.6.34.4-xen 
can not be generated, and therefore a FATAL error causes the make-kpkg process 
to fail! 

A System.map-2.6.34.4-xen can be generated when the kernel is built and 
packaged into a Debian binary with make deb-pkg.

Can anyone else reproduce this problem?


uname -a
Linux BUBBLE 2.6.34.4-r61-xen #1 SMP Tue Sep 14 10:39:11 EDT 2010 x86_64 
GNU/Linux

apt-cache policy kernel-package
kernel-package:
  Installed: 12.036
  Candidate: 12.036
  Version table:
 *** 12.036 0
500 http://mirror.csclub.uwaterloo.ca/debian/ squeeze/main amd64 
Packages
100 /var/lib/dpkg/status



-M

  

RE: NetworkManager Bridging devices

[Mike Viau]

Fri, 10 Sep 2010 23:14:41 +0200 nfs_2...@chubig.net wrote:
 
 Good evening,
 
 I’m using NetworkManager to automatically connect to a number of wifi
 networks as well as to ethernet networks at home and in university.
 I’m also using the dispatcher to run custom scripts depending on the
 network to which the computer just connected.
 
 Now it would be nice if I could put the wifi interface (Intel
 Wireless 4965) and the ethernet interface in one bridge, so that both
 devices get the same IP addresses and I could roam between wifi and
 ethernet by dynamically disabling one of them, with my connections
 persisting.
 
 Is something like this possible? I tried to manually create a bridge
 and set up the interfaces, but I seem to be unable to add wlan0 to
 the bridge, it just tells me that the operation is “not permitted”.

I understand that the upsteam project NetworkManager is working on adding 
network bridge support. 

The last ETA I read was late 2010 from there website [1] ... I was just 
wondering if anyone knew this was still the case.

Network bridging support would be very useful to me for running Xen on my 
Debian system.


[1] http://projects.gnome.org/NetworkManager/


-M
  

RE: Straw poll: What browser do you use?

[Mike Viau]

 On Fri, 10 Sep 2010 04:43:35 +0200 ed3lt...@googlemail.com wrote:
 
 Am 09/07/2010 03:16 PM, schrob B. Alexander:
 
  This morning, after idling all weekend, iceweasel on my work system was
  chewing up between 70 and 100% of my cpus, and scrolling pages were
  hesitating for several seconds.
  
  So what do others use?
 
 Plain Vanilla flavour of Firefox. Simply downloaded from Mozilla.com
 once extracted in /usr/local/share (and linked to
 /usr/local/bin/firefox) all it takes for an upgrade is getting the
 actual package from Mozilla, cd to /usr/local/share and unpack it.
 Pretty straightfoward. I tried this when I had some trouble with
 Iceweasel from testing and stuck with Firefox. Never had any issues, since,
 

Has anyone tried compiling 32 bit Firefox or Iceweasel in Debian 64 bit 
(testing for example)?

I found a link for fedora mainly. I was wondering what steps should be taken 
for squeeze specifically.

https://developer.mozilla.org/en/Compiling_32-bit_Firefox_on_a_Linux_64-bit_OS
  

RE: Upgrade of squeeze hangs on apt (0.7.26~exp3)

[Mike Viau]

 On Sun, 5 Sep 2010 07:52:29 -0400 bro...@historicalmaterialism.info wrote:
 
 With a brand new installation of squeeze, one of my first steps was to
 do a package update and a safe-upgrade. The former went well, but when
 I tried to upgrade the 22 updated packages, the upgrade proceedure
 terminated with:
 
   Reading changelogs ... done
 
   apt (0.7.26~exp3) experimental; urgency=low
 * apt-ftparchive now reads the standard configuration files in
   /etc/apt/apt.conf and /etc/apt/apt.conf.d 
 
 and after some more lines ends with 
 
   /tmp/tmp (END)
 
 and it takes a Ctl-C to break back to a command prompt. The upgrade
 process is terminated and nothing was actually upgraded. I can repeat,
 and each time only the tmp file id number changes, but the 22 packages
 are still not upgraded.
 
 A google search leaves me unclear, but it seems that some experimental
 features of apt are being merged into squeeze. 
 
 Should I just ignore this until such time as a clean upgrade becomes
 possible? Is there a work-around?
 

Yes! Push the 'q' key instead of ctrl-c or perhaps ':' then 'q', I forget if 
that update placed you in less or vi

Hope that helps.



-M
  

RE: uPnP state in debian ?

[Mike Viau]

 On Sun, 5 Sep 2010 13:35:10 -0500 greenfreedo...@gmail.com wrote:
  Mathieu Malaterre wrote at 2010-09-05 07:38 -0500:
  I would like to know if anyone has setup a uPnP server on a debian box ?
  
  I am looking at the following ITP: #469397  #450520  but it seems
  they have not been integrated in debian AFAIK
 
 You may also want to consider miniupnpd and linux-igd.  The latter is 
 available 
 in Debian and works okay but seems to be somewhat stagnant.

Miniupnpd seems to be platform friendly supporting
OpenBSD,
FreeBSD,
NetBSD and
(Open)Solaris
in combination with pf
or ipf
and Linux with
netfilter.

Anyone have any feedback in terms of the usuablily of miniupnpd in Debian or 
Linux?


-M
  

RE: What is the best way to migrate a server to new hardware?

[Mike Viau]

 On Wed, 1 Sep 2010 11:18:38 -0500 rac...@makeworld.com wrote:
 
  On Wed, Sep 1, 2010 at 9:57 AM, Chris rac...@makeworld.com wrote:
   I like the dpkg method myself. Of course this won't help if you
   have lots of custom conf file in etc.
  
   In that case, creating a tarball of etc would remedy that.
  
   Clonezilla is another option I like if you want an exact duplicate
   (I have used both methods and its a toss up for me what is the
   better solution)
  
  Thanks, I can  use a 'tar ball copy' in Debian without problems?
  Here's what I did in Gentoo, will this work in Debian. Is there
  another recommended way to tar and move an OS?
  
  # rm /etc/ssh/ssh_host*
  # rm -iv /etc/resolv.conf
  # tar cvjfp /mnt/usb/stage4.tar.bz2 / -X debian.excl
  
  # cat debian.excl
  /etc/ssh/ssh_host_*
  /home/*
  /mnt/*
  /media/*
  /lost+found
  /proc/*
  /sys/*
  /tmp/*
  /var/tmp/*
  
  
 
 Here's one way that I would do this:
 
 On the new box: 
 Install Debian per normal.
 
 Old Box:
 #sudo dpkg --get-selections *  installed_packages.txt
 copy the file, installed_packages.txt to the new box
 
 On Newly install Debian:
 #sudo dpkg --set-selections  installed_packages.txt
 #sudo apt-get -u dselect-upgrade
 
 This will read the file installed_packages.txt
 and will install these into the new Debian system.
 

Does this method mark the previously packages that were auto as such on the new 
system, or are they all considered installed manually?

 Once that's up to date, take your tarball of /etc from the old box, 
 dump it to a temp dir in the new, decompress it, copy the .conf files
 that you modified (and any other dirs/files you yourself have created
 to /etc on the new box.
 
 This method has a little work to be done (and thank you Howtoforge for
 the nifty little trick) but works pretty well for my needs.
 
 This same process will work for a workstation also. Then again,
 Clonezilla (again, one that I use often when I want to archive my
 system and need to restore on the same hardware at any given point)
 should work also. 
 
 But as others have pointed out, there are many ways to do this. You
 just need to blaze your own path and see what works best for you.
 
  

RE: building 2.6.35

[Mike Viau]

 On Wed, 11 Aug 2010 08:45:04 +0800 a...@samad.com.au wrote:
 
 [snip]
 
  I did trying using the packages for 2.6.35, but you can't install the
  headers because the linux-kbuild-2.6.35 is there
 
  Why do you want to install the headers if you already have the whole
  kernel source code?  What are you trying to accomplish besides
  building a custom kernel?
 
  I wanted the header file, so I could build the intel i915 modules, I
  was planning on taking the modules source that belong to that and try
  to compile against a debian kernel.
 
 okay here is the problem with this, there are some extra steps needed
 to use the kernel-source
 
 so I installed the linux-image and the kernel-source package, boots up
 great - but I can't compile my vb kernel modules - no header files
 - I point it to /usr/src/.. (unpacked kernel-source), doesn't
 work...
 
 What do I need to do :)
 

Maybe this will help... 
The make headers_install command exports the kernel's header files in a form 
suitable for use by userspace programs.

The kernel header files can be generated from the kernel sources.

Define INSTALL_HDR_PATH= for output location.
http://www.mjmwired.net/kernel/Documentation/make/headers_install.txt


  A Debian source package for 2.6.35 is also
  available in experimental: linux-source-2.6.35.
 [snip]
 
 
 -- 
 To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
 with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
 Archive: 
 http://lists.debian.org/aanlkti=+bse_c9pcxxegwgpmtzx1p0bs9zÿrq...@mail.gmail.com
 
  

RE: [Slightly OT] Laptop battery draining in Lenny

[Mike Viau]

Date: Fri, 30 Jul 2010 11:24:52 -0700
Subject: [Slightly OT] Laptop battery draining in Lenny
From: mamar...@gmail.com
To: debian-user@lists.debian.org

I am curious how others on this list manage their laptop batteries while using 
Debian.  From doing some research, there doesn't appear to be many (if any) 
software solutions for draining a laptop battery completely, before recharging. 
 So what do people on this list do - just keep running Debian on battery power 
until the battery totally dies, which sometimes doesn't give you ample time to 
shut down properly?  Or do you shutdown  when the battery reaches, say, 5%?


I just ordered a few laptop battery replacements off ebay and would like to 
manage them better than the ones I inherited, which were mostly dead by the 
time I got them.

Thanks for any ideas.

Mark


I use Tp_smapi (if you have a thinkpad that is compatible).


 It is available at: http://www.thinkwiki.org/wiki/Tp_smapi 


Then I run a script like this to load the kernel modules on-demand:

modprobe tp_smapi
if [ $? -ne 0 ]; then
echo Error loading tp_smapi
fi
if [ $? -eq 0  ]; then
echo Loaded tp_smapi
fi

modprobe hdaps
if [ $? -ne 0 ]; then
echo Error loading hdaps
fi
if [ $? -eq 0 ]; then
echo Loaded hdaps
fi
if [ $? -eq 0 ]; then
echo Loaded hdaps
fi

sleep 1
echo Setting up BAT0 charging thesholds
echo 40  /sys/devices/platform/smapi/BAT0/start_charge_thresh 
echo 70  /sys/devices/platform/smapi/BAT0/stop_charge_thresh 


I would be interested in knowing if other similar kernel modules exist to set 
laptop battery charging thresh-holds whether they be vendor specific or generic.


-M 
  
_
Learn more ways to connect with your buddies now
http://go.microsoft.com/?linkid=9734388

RE: Trouble compiling generic kernel

[Mike Viau]

 On Sat, 24 Jul 2010 22:22:29 -0500 s...@hardwarefreak.com wrote:
 
 Setting CONCURRENCY_LEVEL=4 in your user environment should fix this, at
 least, it used to.  From the bash command line, for the current session only:
 
 export CONCURRENCY_LEVEL=4
 
 To make it permanent you need to edit /home/[user]/.bash_profile and append:
 
 export CONCURRENCY_LEVEL=4
 
 If you regularly do your kernel work while logged on as root, you'd need to
 append it to /root/.bashrc or /root/.profile

You might also want to read http://www.wowway.com/~zlinuxman/Kernel.htm

or from google's cache at 
http://webcache.googleusercontent.com/search?q=cache:7D7TfZqA1wMJ:www.wowway.com/~zlinuxman/Kernel.htm+http://www.wowway.com/~zlinuxman/Kernel.htmcd=4hl=enct=clnkgl=ca


-M
  
_
Game on: Challenge friends to great games on Messenger
http://go.microsoft.com/?linkid=9734387

Debian way to essentially call block phone number

[Mike Viau]

Hello list,

I was wondering if anyone runs a system that essentially blocks unwanted calls 
from a list of programmed phone numbers. I have the caller display option on my 
phones service that returns the phone number of most incoming calls.

I came across this idea after reading:

If you want to go the freebie route, you can download free
software that claims to block unwanted calls. This software works by 
hooking up
your phone to your computer and letting the software screen incoming calls.
Some of these downloads require you to have other hardware though. [1]

Is there a package in Debian I should be aware of, something I can run on a 
personal computer? I was also considering designing embedded system to do the 
job, but I cringe at the thought of integrating a POTS (Plain Old Telephone 
System) modem in the embedded world.

Any help or further comments are welcomed :)

Thanks


[1] - http://communication.howstuffworks.com/blocking-incoming-call1.htm

  
_
Turn down-time into play-time with Messenger games
http://go.microsoft.com/?linkid=9734385

RE: Debian Network install disk doesn't find NIC

[Mike Viau]

 On Fri, 9 Jul 2010 20:14:07 -0400 From: titan8...@gmail.com wrote:
 
 Try the kmuto[1] installers. They have up-to-date kernels that are more
 likely to support new hardware. If that is the case, just install the
 lenny-backports kernel after installation is complete.
 
 
 [1] http://kmuto.jp/debian/d-i/
 


I would be interested in know how that goes. The other option would be to use 
the debian installation media you already have and:

1) to install with no network card and you may get some module for using 
ethernet over firewire 
2) then copy over the e1000e src tarball download from intel's website from a 
usb drive or other medium
3) install the build-essentials and kernel headers
4) uncompress the e1000e src tarball and compile the kernel module for your 
network card.


-M


  
_

RE: Debian support on newer 4K Advanced format drives (rather than 512 bytes)

[Mike Viau]

Does this mkfs work around work to preserve the performance of the drive? By 
using the -b 4096 (to signify the 4k sectors) when creating partitions such as:

mkfs -t ext4 -b 4096 /dev/sda1

Is there any implication for mounting a partition formatted with the above 
command (e.g: mounting in other systems)? 

Is there anything in fdisk that one should do to signify 4K sectors for 
partitions as well?

I understand that added layers to the partitions such as drive encryption 
and/or LVM volumes must also be setup to use 4K sectors too so that performance 
is not lost.

Thanks.


-M




From: vi...@sheridanc.on.ca
To: debian-user@lists.debian.org
Subject: Debian support on newer 4K Advanced format drives (rather than 512 
bytes)
Date: Fri, 2 Jul 2010 17:31:22 -0400













Hello List,

I was just wondering what some of the debian community users has been 
experiencing in regards to the new Western Digital 4K Advanced format drives? 
Has any one tried using one of these drives on the 2.6.26 (64/32 bit) kernel 
shipped with Lenny stable? How about with the 2.6.32 (64/32 bit) kernel shipped 
with squeeze testing?

Is the support more dependant on the kernel or does debian already support 
these drives?

Thanks in advance.



Specifications for the WD Caviar Green (Advanced Format) SATA internal 
hard drives


http://wdc.custhelp.com/cgi-bin/wdc.cfg/php/enduser/std_adp.php?p_faqid=5324p_created=1263858658p_sid=xbnV-uVjp_accessibility=0p_redirect=p_srch=1p_lva=p_sp=cF9zcmNoPTEmcF9zb3J0X2J5PSZwX2dyaWRzb3J0PSZwX3Jvd19jbnQ9MTk2LDE5NiZwX3Byb2RzPTIyNywyOTQmcF9jYXRzPSZwX3B2PTIuMjk0JnBfY3Y9JnBfcGFnZT0xp_li=p_topview=1


-M


  
_
Turn down-time into play-time with Messenger games
http://go.microsoft.com/?linkid=9734385

RE: Debian support on newer 4K Advanced format drives (rather than 512 bytes)

[Mike Viau]

 On Sat, 3 Jul 2010 12:01:40 -0500 ron.l.john...@cox.net wrote:
 
 I think that the partitioning tool (fdisk, cfdisk, parted, ...) is 
 what is really important.  That is because filesystems already use 
 4KB block sizes.
 
 Possibly also fsck.
 
 There was a recent IBM DeveloperWorks article on this very topic.
 

This I take it?

http://www.ibm.com/developerworks/linux/library/l-4kb-sector-disks/index.html
  
_
MSN Dating: Find someone special. Start now.
http://go.microsoft.com/?linkid=9734384

FW: Debian support on newer 4K Advanced format drives (rather than 512 bytes)

[Mike Viau]

On the link 
http://www.ibm.com/developerworks/linux/library/l-4kb-sector-disks/index.html

[snip]

Tip: If you want to dual-boot between Linux and an 
older operating system that
requires cylinder alignment, try aligning the starts of all your 
partitions on multiples
of eight cylinders. This translates to 8-sector alignment for optimum
disk performance as well as cylinder alignment for the older operating 
system.

[/snip]



It sounds like the term cylinders is used synonymously with sectors. Will this 
always be the case??




 On Sat, 3 Jul 2010 15:09:57 -0500 s...@hardwarefreak.com wrote:
 
 Ron Johnson put forth on 7/3/2010 2:36 PM:
 
  This is unrelated.  FS block size != sector size.
  
  It is when you use a 4KB drive
 
 Not according to man on Stable:
 
 mkfs.xfs [ -b block_size ] ... [ -s sector_size  ] [ -L label ] [ -N ] device
 
 -b block_size_options
 
 This option specifies the fundamental block size of the filesystem. The
 valid block_size_options are: log=value or size=value and only one can be
 supplied. The block size is specified either as a base two logarithm value
 with log=, or in bytes with size=. The default value is 4096 bytes (4 KiB),
 the minimum is 512, and the maximum is 65536 (64 KiB). XFS on Linux currently
 only supports pagesize or smaller blocks.
 
 -s sector_size
 This option specifies the fundamental sector size of the filesystem. The
 sector_size is specified either as a value in bytes with size=value or as a
 base two logarithm value with log=value. The default sector_size is 512 bytes.
 The minimum value for sector size is 512; the maximum is 32768 (32 KiB). The
 sector_size must be a power of 2 size and cannot be made larger than the
 filesystem block size.
 
 -- 
 Stan
 
 

That seems like a very clean way to prepare a XFS file system that is aware of 
the 4096 byte sector size with the -s option. Its like away to override the 
4096 byte sector size even if it gets read incorrectly as 512 by the 
/sys/block/sdX/queue/physical_block_size.

[snip]

In theory, the Linux kernel should return information on the physical
sector size in the /sys/block/sdX/queue/physical_block_size pseudo-file 
and
on the logical sector size in the 
/sys/block/sdX/queue/logical_block_size
pseudo-file, where sdX is your device's node name (normally sda, sdb, 
and
so on). In practice, however, the physical block size information is
spurious, at least for the first generation of Western Digital Advanced
Format drives. Unfortunately, this means that disk utilities cannot
properly detect the presence of such disks.

[/snip]


-M
  
Look 'em in the eye: FREE Messenger video chat Chat Now!
  
_
MSN Dating: Find someone special. Start now.
http://go.microsoft.com/?linkid=9734384

RE: Debian support on newer 4K Advanced format drives (rather than 512 bytes)

[Mike Viau]

On the link 
http://www.ibm.com/developerworks/linux/library/l-4kb-sector-disks/index.html

[snip]
Tip: If you want to dual-boot between Linux and an 
older operating system that
requires cylinder alignment, try aligning the starts of all your 
partitions on multiples
of eight cylinders. This translates to 8-sector alignment for optimum
disk performance as well as cylinder alignment for the older operating 
system.
[/snip]

It sounds like the term cylinders is used synonymously with sectors. Will this 
always be the case??


 On Sat, 3 Jul 2010 15:09:57 -0500 s...@hardwarefreak.com wrote:
 
 Ron Johnson put forth on 7/3/2010 2:36 PM:
 
  This is unrelated.  FS block size != sector size.
  
  It is when you use a 4KB drive
 
 Not according to man on Stable:
 
 mkfs.xfs [ -b block_size ] ... [ -s sector_size  ] [ -L label ] [ -N ] device
 
 -b block_size_options
 
 This option specifies the fundamental block size of the filesystem. The
 valid block_size_options are: log=value or size=value and only one can be
 supplied. The block size is specified either as a base two logarithm value
 with log=, or in bytes with size=. The default value is 4096 bytes (4 KiB),
 the minimum is 512, and the maximum is 65536 (64 KiB). XFS on Linux currently
 only supports pagesize or smaller blocks.
 
 -s sector_size
 This option specifies the fundamental sector size of the filesystem. The
 sector_size is specified either as a value in bytes with size=value or as a
 base two logarithm value with log=value. The default sector_size is 512 bytes.
 The minimum value for sector size is 512; the maximum is 32768 (32 KiB). The
 sector_size must be a power of 2 size and cannot be made larger than the
 filesystem block size.
 
 -- 
 Stan
 
 

That seems like a very clean way to prepare a XFS file system that is aware of 
the 4096 byte sector size with the -s option. Its like away to override the 
4096 byte sector size even if it gets read incorrectly as 512 by the 
/sys/block/sdX/queue/physical_block_size.

[snip]

In theory, the Linux kernel should return information on the physical
sector size in the /sys/block/sdX/queue/physical_block_size pseudo-file 
and
on the logical sector size in the 
/sys/block/sdX/queue/logical_block_size
pseudo-file, where sdX is your device's node name (normally sda, sdb, 
and
so on). In practice, however, the physical block size information is
spurious, at least for the first generation of Western Digital Advanced
Format drives. Unfortunately, this means that disk utilities cannot
properly detect the presence of such disks.

[/snip]


-M
  
_
Game on: Challenge friends to great games on Messenger
http://go.microsoft.com/?linkid=9734387

Debian support on newer 4K Advanced format drives (rather than 512 bytes)

[Mike Viau]

Hello List,

I was just wondering what some of the debian community users has been 
experiencing in regards to the new Western Digital 4K Advanced format drives? 
Has any one tried using one of these drives on the 2.6.26 (64/32 bit) kernel 
shipped with Lenny stable? How about with the 2.6.32 (64/32 bit) kernel shipped 
with squeeze testing?

Is the support more dependant on the kernel or does debian already support 
these drives?

Thanks in advance.



Specifications for the WD Caviar Green (Advanced Format) SATA internal 
hard drives


http://wdc.custhelp.com/cgi-bin/wdc.cfg/php/enduser/std_adp.php?p_faqid=5324p_created=1263858658p_sid=xbnV-uVjp_accessibility=0p_redirect=p_srch=1p_lva=p_sp=cF9zcmNoPTEmcF9zb3J0X2J5PSZwX2dyaWRzb3J0PSZwX3Jvd19jbnQ9MTk2LDE5NiZwX3Byb2RzPTIyNywyOTQmcF9jYXRzPSZwX3B2PTIuMjk0JnBfY3Y9JnBfcGFnZT0xp_li=p_topview=1


-M


  
_
Turn down-time into play-time with Messenger games
http://go.microsoft.com/?linkid=9734385

RE: Xen on Squeeze won't start

[Mike Viau]

 Date: Fri, 2 Jul 2010 13:51:14 -0700
 Subject: Re: Xen on Squeeze won't start
 From: rip...@woodlandschools.org
 To: debian-user@lists.debian.org
 CC: wa...@debian.org
 
 Well just in case someone else hits this... once my colleague
 suggested I look closer at what grub2 was doing, and after more time
 on Google and experimenting I came up with this... the actual xen 3.4
 hypervisor isn't being put into the grub2 boot list.  It's not good
 booting off the one that says ...-xen-... as that appears to be the
 paravirtualised kernel, not the hypervisor.  So, the following in
 /etc/grub.d/40_custom
 
 menuentry Xen 3.4 / Debian GNU/Linux, with Linux 2.6.32-5-xen-amd64 {
 insmod raid
 insmod mdraid
 insmod ext2
 set root='(md0)'
 search --no-floppy --fs-uuid --set 
 c924a87f-1ff0-4483-8029-a0e67dcc434f
 multiboot (md0)/boot/xen-3.4-amd64.gz dummy=dummy
 module (md0)/boot/vmlinuz-2.6.32-5-xen-amd64 dummy=dummy
 root=UUID=c924a87f-1ff0-4483-8029-a0e67dcc434f nomodeset
 module (md0)/boot/initrd.img-2.6.32-5-xen-amd64
 }
 
 (change md0 for your boot devic and get your uuid out of /etc/fstab), set
 
 GRUB_DEFAULT=Xen 3.4 / Debian GNU/Linux, with Linux 2.6.32-5-xen-amd64
 
 in /etc/default/grub, run update-grub and reboot.  Finally a ps -e |
 grep xen shows a bunch of xen processes!
 
 Now to see how it actually performs...
 
 
 
 
 On Thu, Jul 1, 2010 at 10:03 AM, Rippl, Steve
 rip...@woodlandschools.org wrote:
  Hi,
  We've been running Xen on Lenny for some time and it's worked great, but
  with a new server and some older Xen kernel issues around acpi we're trying
  the newer version on Squeeze.
  So, I did a base install of Squeeze alpha 1, then apt-get install
  xen-linux-system-2.6.32-5-xen-amd64 xen-tools.  After adjusting the Grub 2
  boot menu (installing the Xen kernel doesn't put it at the top of the boot
  menu, so by default Grub booted into the 'trunk' kernel) the server rebooted
  into the Xen kernel (uname -r gives 2.6.32-5-xen-amd64) and yet xend won't
  start!  Running xm create... I get Error: Unable to connect to xend: No
  such file or directory. Is xend running?.  Trying to start via /etc/init.d
  I get nothing!
  I've seen the close bug report
  (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=580500) where someone
  seems to have the same error as me, I also have Booting paravirtualized
  kernel on bare hardware in kern.log, and Bastian says it's user error, but
  doesn't explain how that's user error!?
  Any insight is much appreciated!
  Thanks,
  Steve
  --

Does the attached script help? It is an executable grub2 shell script.

-M

  
_
Turn down-time into play-time with Messenger games
http://go.microsoft.com/?linkid=9734385

20_linux_xen.in
Description: Binary data

RE: pygrub is failing to boot centos domu on Debian lenny dom0

[Mike Viau]

 On Fri, 28 May 2010 21:42:33 +0200 d.sastre.med...@gmail.com wrote:
 
 In case you are still reading this list, you might want to try this¹ tool.
 It is used to bootstrap RPM-based distros in Debian+Xen. CentOS 5 is 
 listed as supported.
 Maybe you reconsider your decision, and give Squeeze a try?
 You could even try latest xen version² :)
 
 ¹ http://xen-tools.noone.org/software/rinse/
 ² http://bits.xensource.com/oss-xen/release/4.0.0/xen-4.0.0.tar.gz

http://packages.debian.org/lenny/rinse

It appears this package is also available in Lenny too.


-M
  
_
MSN Dating: Find someone special. Start now.
http://go.microsoft.com/?linkid=9729707

Any file details on an executable binary file?

[Mike Viau]

Hello list,

I was wondering if anyone could suggest a package or means to look at any or 
all of the information from a given executable binary file:

- What compiler compiled it

- What (source) language was it compiled from

- What computer architecture the file was compiled for

- How many hardware bits was the file intended for (eg. 32-bit or 64-bit 
encoding)

- Endianness


If any of the above a simply not possible because of the nature all binary 
files, it would be helpful to know that too.

Thanks.
 

-M


  
_
MSN Dating: Find someone special. Start now.
http://go.microsoft.com/?linkid=9729707

RE: Any file details on an executable binary file?

[Mike Viau]

 On Fri, 14 May 2010 22:22:01 +0530  aspn...@gmail.com  wrote:
 
 Also you could try and analyze the output of the following  readelf -a 
 executable ldd executable strings executable For example most of the 
 files compiled with g++ has a dependability on libstdc++.so.6

 

Wow the output of readelf -a executable was really helpful, which contained 
information like:

ELF Header:
  Magic:   7f 45 4c 46 02 01 01 00 00 00 00 00 00 00 00 00
  Class: ELF64
  Data:  2's complement, little endian
  Version:   1 (current)
  OS/ABI:UNIX - System V
  ABI Version:   0
  Type:  EXEC (Executable file)
  Machine:   Advanced Micro Devices X86-64
  Version:   0x1
  Entry point address:   0x401210
  Start of program headers:  64 (bytes into file)
  Start of section headers:  15296 (bytes into file)
  Flags: 0x0
  Size of this header:   64 (bytes)
  Size of program headers:   56 (bytes)
  Number of program headers: 8
  Size of section headers:   64 (bytes)
  Number of section headers: 37
  Section header string table index: 34

  
_
30 days of prizes to be won with Hotmail.  Enter Here.
http://go.microsoft.com/?linkid=9729709

RE: adding 192.x with static IP

[Mike Viau]

 Mon, 3 May 2010 22:11:59 -0400 net...@gmail.com wrote:
 
 I have a static IP setup, I wish to add a router and it has a web
 interface, I can get to it if I start a DHCP server and then
 192.168.1.1 is setup, but I'd really prefer to not do this.

Why might DHCP be unacceptable in your setup?

 Is there a way I can setup devices such as this without needing to run
 DHCP? 

Absolutely, did you put you clients in the same network as you LAN interface on 
your router and set the default route on clients to be your router?

 Also I was generally curious if there is any program which will
 search my LAN and report the address of any network enabled devices it
 finds (firewalls, DSL modems, routers, etc.)? Thanks!
 

  
_
Hotmail  Messenger are available on your phone. Try now.
http://go.microsoft.com/?linkid=9724461

RE: Aptitude Error

[Mike Viau]

 On Fri, Apr 30, 2010 at 01:26:45PM -0400, Tom H tomh0...@gmail.com was 
 heard to say:
  On Fri, Apr 30, 2010 at 1:18 PM, Anand Sivaram aspn...@gmail.com wrote:
  
   You could find what all packages from sid are installed in your system by
   apt-show-versions |  grep unstable
  
  Or aptitude search ~Aunstable
 

aptitude search ~Aunstable seems to show all packages from sid (wheather 
installed or not)

try  aptitude search ~Aunstable | grep '^i' 



-M

  
_
Hotmail  Messenger are available on your phone. Try now.
http://go.microsoft.com/?linkid=9724461

RE: Aptitude Error

[Mike Viau]

 Fri, 30 Apr 2010 21:10:56 -0700 dburr...@debian.org wrote:
 On Sat, May 01, 2010 at 12:04:07AM -0400, Mike Viau vi...@sheridanc.on.ca 
 was heard to say:
  
   On Fri, Apr 30, 2010 at 01:26:45PM -0400, Tom H tomh0...@gmail.com was 
   heard to say:
On Fri, Apr 30, 2010 at 1:18 PM, Anand Sivaram aspn...@gmail.com 
wrote:

 You could find what all packages from sid are installed in your 
 system by
 apt-show-versions |  grep unstable

Or aptitude search ~Aunstable
   
  
  aptitude search ~Aunstable seems to show all packages from sid (wheather 
  installed or not)
  
  try  aptitude search ~Aunstable | grep '^i' 
 
   Ah, I missed that requirement.
 
   How about this:
 
  $ aptitude versions --group-by=none --show-package-name=always \
  -F '%p %d' '?archive(unstable)?installed'
 
   Or for earlier systems:
 
  $ aptitude search '?narrow('?archive(unstable), ?installed)'
 

debian01:~# aptitude search '?narrow('?archive(unstable), ?installed)'

-bash: syntax error near unexpected token `('

  
_
Live connected. Get Hotmail  Messenger on your phone.
http://go.microsoft.com/?linkid=9724462

RE: xen

[Mike Viau]

Sat, 17 Apr 2010 01:55:32 +0800 john...@hotmail.com wrote:








Hello there,  Ny name is Ian, from Perth Australia.
I have a question to be answered please.  I'm a linux user, so I use suse, 
debian, ubuntu and gentoo, and fedora.I'm interested in exploring the 
capabilities of xen and have done so an all the above.I'm in a brand new 
instance of squeeze and have just perused the packages in synaptic for the 
first time.I have recently used karmic lenny including a xen live cd which uses 
lenny as a dom host.This has lead to submitting bug reports because the 
collection of packages that are used to support virt-manager and xen are 
extensive and quite problem ridden.  I am now to try the latest packages 
provided by squeeze.
I can't help but notice  THERE IS NO XEN KERNEL.


 Lenny (backports)
 http://packages.debian.org/search?suite=lenny-backportsarch=amd64mode=pathsearchon=contentskeywords=xen-amd64

 Sid (unstable)
 http://packages.debian.org/search?suite=sidarch=amd64mode=pathsearchon=contentskeywords=xen-amd64


So, why is it so?  This is like karmic revisited.  No xen kernel.  I 
experimented extensively in karmic only to submit bug reports that were ignored 
because Ubuntu does not support xen as a host, dom0.  

 Why I don't know? You might have to look around for the answer to that 
 question.

What is the policy then?  Why has Ubuntu retracted supporting xen dom0?  Is it 
the same for debian?Why are all xen packages provided but no kernel?  I have a 
xen kernel in any case, but it is an important ommision.Ubuntu and debian have 
provided and supported xen kernels for previous versions.  Has it been 
unofficially left to SUSE to invest support in xen as a virtualisation form?


 This is a Debian mailing list so I think you should ask the Ubuntu specific 
 questions there. As for Debian the Xen hypervisor and tools are in squeeze 
 but note that the HVM support is not included because the amount of time 
 required for maintain the qemu if memory serves me correctly.
  
Australia's #1 job site If It Exists, You'll Find it on SEEK
  
_
Live connected. Get Hotmail  Messenger on your phone.
http://go.microsoft.com/?linkid=9724462

RE: C programming question

[Mike Viau]

 Tue, 13 Apr 2010 17:29:51 -0500 ron.l.john...@cox.net wrote:
 
 On 2010-04-13 17:16, Stephen Powell wrote:
  I realize that this is not a C forum, per se, but this is a Debian-specific
  C question.  I am trying to add support to the parted utility for 
  CMS-formatted
 [snip]
  
  I know how to do this in PL/I, but despite having spent the last two hours
  paging through a C language reference manual, I couldn't find any examples
  of overlaying two structures.  I did find reference to something called
  a union, but I don't have enough knowledge to know what to do.  Does
  anyone know how to do this?
  
 
 union is exactly what you need.
 

Yes thats absolutely right. Remember since C is a powerful, low level, and 
untyped programming language untagged unions are consider unsafe.

Good luck though! 

 I'm feeling lucky sample c code union
 
 http://www.wellho.net/resources/ex.php4?item=c209/union.c
 
 -- 
 Dissent is patriotic, remember?
 
 
 -- 
 To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
 with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
 Archive: http://lists.debian.org/4bc4f05f.6060...@cox.net
 
  
_
Hotmail  Messenger are available on your phone. Try now.
http://go.microsoft.com/?linkid=9724461

RE: Debian Lenny + Grub2 + kernel message log capturing

[Mike Viau]

 Sun, 11 Apr 2010 00:20:54 -0400
 







 Hello,
 
 I was hoping to get some feedback or tips on how to setup a PCI serial card 
 (not onboard) for kernel message log capturing. I am using Debian Lenny x64 
 with the grub2 bootloader.
 
 This might sound like an easy question, but does the Linux kernel module have 
 to be compiled with the running kernel in order to log messages at boot time? 
 I mean obviously the driver is required to be loaded in Debian GNU/Linux when 
 the serial/com device is used in conjunction
with /dev/ttyD[01].
 


Mainly I am asking if one needs to build the mcs9865-serial.ko
(kernel module) against the kernel source for the running kernel in
order to log kernel message during boot time or does grub implement a
generic driver to capture the kernel message?

The mcs9865 source code is here . It does not compile for me against the 
2.6.32-4-xen-amd64 kernel from the Sid repositories. 

I have installed both the appropriate linux-kernel and linux-headers package 
for the 2.6.32-4-xen-amd64 kernel.

Attached is also the output of the make command on the mcs9865 source code.

 I have found a website providing patches for the chip on the PCI serial card 
 I am using at:
 http://izto.org/mcs9865/
 
 Does Debian not include drivers for serial cards in any packages or would 
 these drivers be considered non-free?
 
 Thanks.
 
  
 -M

  
Videos that have everyone talking! Now also in HD! MSN.ca Video.
  
_
Hotmail  Messenger are available on your phone. Try now.
http://go.microsoft.com/?linkid=9724461

make.output
Description: Binary data

Debian Lenny + Grub2 + kernel message log capturing

[Mike Viau]

Hello,

I was hoping to get some feedback or tips on how to setup a PCI serial card 
(not onboard) for kernel message log capturing. I am using Debian Lenny x64 
with the grub2 bootloader.

This might sound like an easy question, but does the Linux kernel module have 
to be compiled with the running kernel in order to log messages at boot time? I 
mean obviously the driver is required to be loaded in Debian GNU/Linux when the 
serial/com device is used in conjunction
with /dev/ttyD[01].

I have found a website providing patches for the chip on the PCI serial card I 
am using at:
http://izto.org/mcs9865/

Does Debian not include drivers for serial cards in any packages or would these 
drivers be considered non-free?

Thanks.

 

-M


  
_
Videos that have everyone talking! Now also in HD!
http://go.microsoft.com/?linkid=9724465

RE: silverlight

[Mike Viau]

Wed, 7 Apr 2010 08:11:21 -0700 jerjoz.for...@gmail.com
 On Wed, Apr 7, 2010 at 7:47 AM, Robin Krahl ro...@rkrahl.de wrote:
  On 07.04.2010 16:26, steef wrote:
  somebody out there knows of an linux_equivalent for MS's siverlight??
 
  Moonlight [1] is a Open Source version of Silverlight, working on Linux.
 
 dont bother trying to use netflix with it!
 
 I have noticed it does not load up some silverlight video-casts from other 
 sites as well. You have been warned.  
 -- 
 To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
 with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
 Archive: 
 http://lists.debian.org/l2tf8d5d4f31004070811w1af0acefzbfde7722d1c91...@mail.gmail.com
 
  
_
Got a phone? Get Hotmail  Messenger for mobile!
http://go.microsoft.com/?linkid=9724464

How to list packages in various priorities or sections

[Mike Viau]

Hello,

I have used aptitude show $(package_name) to list the details of a given 
package. 

In the output of the vlan package for example one gets output like:

[snip]

Priority: extra
Section: misc

[/snip]

How might one determine all packages (installed or not) that fall under a 
particular Priority or Section ?

I was thinking something pseudo like aptitude show $(all packages) | grep 
(essential or required or important or standard or optional or extra)



 

-M

  
_
Videos that have everyone talking! Now also in HD!
http://go.microsoft.com/?linkid=9724465

RE: How to list packages in various priorities or sections

[Mike Viau]

Mon, 5 Apr 2010 17:47:36 -0400 tomh0...@gmail.com wrote:
 
 On Mon, Apr 5, 2010 at 5:28 PM, Mike Viau vi...@sheridanc.on.ca wrote:
  I have used aptitude show $(package_name) to list the details of a given
  package.
 
  In the output of the vlan package for example one gets output like:
 
  [snip]
 
  Priority: extra
  Section: misc
 
  [/snip]
 
  How might one determine all packages (installed or not) that fall under a
  particular Priority or Section ?
 
  I was thinking something pseudo like aptitude show $(all packages) | grep
  (essential or required or important or standard or optional or extra)
 
 aptitude search ~ssection
 aptitude search ~ppriority
 

Thanks for the tip. I noticed ~p works with all but the essential priority for 
some reason.

With your tip I was able to find this link:
http://algebraicthunk.net/~dburrows/projects/aptitude/doc/en/ch02s03s05.html#tableSearchTermQuickGuide

I noticed how terms might be ANDed together but I would appreicated a working 
example of this.

[snip]


  ?and(term1, term2)
term1 term2
  Select any package that matches both
  term1 and
  term2.

[/snip]

Both aptitude search ~pextra ~smisc and aptitude search ~pextra search 
~smisc resulted in a list of package which did not necessarily meet both the 
search patterns specified.


Table 2.1. Quick guide to search termsLong formShort formDescription
  ?=variable
 
  Select the package bound to
  variable; see the section called “Explicit search targets”.
?not(pattern)!pattern
  Select any package that does not match
  pattern.

  ?action(action)
~aaction
  Select packages that have been marked for the given
  action (e.g.,
  “install” or
  “upgrade”).

  ?all-versions(pattern)
 
  Select packages whose versions all match
  pattern.

  ?and(term1, term2)
term1 term2
  Select any package that matches both
  term1 and
  term2.
?any-version(pattern) 
  Select packages for which at least one version
  matches pattern.

  ?archive(archive)

  ~Aarchive

  Select packages from the given archive (such as
  “unstable”).
?automatic~M
  Select packages that were automatically installed.
?bind(variable, pattern)
  ?variable:term-name[(args)]

  Selects anything if
  variable matches
  pattern; see the section called “Explicit search targets”.
?broken~b
  Select packages that have a broken dependency.
?broken-depType~BdepType
  Select package that have a broken dependency of the
  given depType.
?broken-depType(pattern)~DB[depType:]pattern
  Select packages that have a broken dependency of the
  given depType matching
  pattern.
?broken-reverse-depType(pattern)~RBdepType:pattern
  Select packages that a package matching
  pattern declares a broken
  dependency of type depType.

  ?conflicts(pattern)
~Cpattern
  Select packages that conflict with a package
  matching pattern.
?config-files~c
  Select packages that were removed but not purged.
?depType(pattern)~D[depType:]pattern
  Match packages that declare a dependency of type
  depType on a package
  matching pattern.
?description(description)~ddescription
  Select packages whose description matches
  description.
?essential~E
  Select essential packages, those with
  Essential: yes in their control
  files.
?false~F
  Select no packages.
?for variable: pattern 
  Select packages that match
  pattern with
  variable bound to the
  package being matched; see the section called “Explicit 
search targets”.
?garbage~g
  Select packages that are not required by any manually
  installed package.
?installed~iSelect installed 
packages.?maintainer

RE: [SOLVED] How to list packages in various priorities or sections

[Mike Viau]

Mon, 5 Apr 2010 19:25:53 -0500 b...@iguanasuicide.net wrote:
 
 On Monday 05 April 2010 17:14:42 Mike Viau wrote:
  Both aptitude search ~pextra ~smisc and aptitude search ~pextra search
   ~smisc resulted in a list of package which did not necessarily meet both
   the search patterns specified.
 
 For short form, you can generally just smash things together to logical-AND 
 them.  (aptitude search '~pextra~smisc') should do what you want.

Yes thank you, that works much better :)


 -- 
 Boyd Stephen Smith Jr. ,= ,-_-. =.
 b...@iguanasuicide.net((_/)o o(\_))
 ICQ: 514984 YM/AIM: DaTwinkDaddy   `-'(. .)`-'
 http://iguanasuicide.net/  \_/
  
_
Hotmail  Messenger. Get them on your phone now.
http://go.microsoft.com/?linkid=9724463

[SOLVED] Working network connectivity, not working DNS resolutions

[Mike Viau]

 Mon, 29 Mar 2010 20:47:40 +1100 a...@samad.com.au wrote:
 On Mon, Mar 29, 2010 at 3:00 AM, Mike Viau vi...@sheridanc.on.ca wrote:
  Could there be an issue with MTU size?
 
 don't thing so
 
 [snip]
 
  My findings.
 
  # dig @10.254.2.254 google.com
 
  ;  DiG 9.4.3-P2  @10.254.2.254 google.com
  ; (1 server found)
  ;; global options:  printcmd
  ;; Got answer:
  ;; -HEADER- opcode: QUERY, status: NOERROR, id: 27942
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
 
  ;; QUESTION SECTION:
  ;google.com.IN  A
 
  ;; ANSWER SECTION:
  google.com. 55  IN  A   66.249.91.104
 
  ;; Query time: 4 msec
  ;; SERVER: 10.254.2.254#53(10.254.2.254)
  ;; WHEN: Fri Mar 26 01:02:53 2010
  ;; MSG SIZE  rcvd: 44
 [snip]
 
  So DNS does work on this box, as it forward DNS replies to other boxes on my
  local network.
 
  What should I do next? Any ideas?
 
 try the dig command from one of the boxes that can't get dns, follow the 
 packet with tcpdump
 
 all you have shown above is that your router can get dns
 
I do appreciate your assistance (everyone)! Looks like I found where the 
problem was. It was my /etc/network/interfaces file and how I was creating 
bridges on VLANs.

The configuration that works despite File exists errors during system boot 
was:


auto eth1.200
iface eth1.200 inet manual
auto br200
iface br200 inet static
 address 10.254.2.1
 netmask 255.255.255.0
 network 10.254.2.0
 broadcast 10.254.2.255
 gateway 10.254.2.254
 dns-nameservers 10.254.2.254
 dns-search site
 bridge-ports eth1.200


The configuration that does not works despite no errors during system boot was:


iface eth1.200 inet manual
auto br200
iface br200 inet static
 address 10.254.2.1
 network 10.254.2.0
 netmask 255.255.255.0
 broadcast 10.254.2.255
 gateway 10.254.2.254
 dns-nameservers 10.254.2.254
 dns-search site
 bridge-ports eth1.200


Any idea on how the working configuration could be modified to work and not 
leave File exists errors during system boot?


Thanks.



 -M

  
_
Check your Hotmail from your phone. 
http://go.microsoft.com/?linkid=9712957

RE: Working network connectivity, not working DNS resolutions

[Mike Viau]

Could there be an issue with MTU size?

Also has anyone witnessed a similar problem where a network is able to ping as 
well as lease an IP from a dchp server, but can not query the DNS service from 
the same server as the DHCP (no firewalling or ACLs in place) ?

 

-M





Fri, 26 Mar 2010 20:52:08 -0400 vi...@sheridanc.on.ca wrote:







My router (at 10.254.2.254) is running pfsense (a freebsd router distro)
 I found that I was able to run the dig and netstat commands from an SSH
 session.

My findings.

# dig @10.254.2.254 google.com

;
  DiG 9.4.3-P2  @10.254.2.254 google.com
;
 (1 server found)
;; global options:  printcmd
;; Got answer:
;;
 -HEADER- opcode: QUERY, status: NOERROR, id: 27942
;;
 flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;;
 QUESTION SECTION:
;google.com.IN  A

;;
 ANSWER SECTION:
google.com. 55  IN  A   
66.249.91.104

;; Query time: 4 msec
;; SERVER: 
10.254.2.254#53(10.254.2.254)
;; WHEN: Fri Mar 26 01:02:53 2010
;;
 MSG SIZE  rcvd: 44


# netstat -na
Active Internet 
connections (including servers)
Proto Recv-Q Send-Q  Local 
Address  Foreign Address(state)
tcp4   0 52 
10.254.2.254.2210.254.2.188.57059 ESTABLISHED
tcp6   
0  0 *.53   *.*LISTEN
tcp4  
 0  0 *.53   *.*LISTEN
tcp4  
 0  0 *.2189 *.*LISTEN
tcp4  
 0  0 *.80   *.*LISTEN
tcp4  
 0  0 127.0.0.1.8021 *.*LISTEN
tcp4  
 0  0 *.22   *.*LISTEN
tcp6  
 0  0 *.22   *.*LISTEN
udp4  
 0  0 *.67   *.*
udp6   0  0 
*.53   *.*
udp4   0  0 *.53  
 *.*
udp4   0  0 192.168.2.2.12176  209.139.209.82.123
udp4  
 0  0 192.168.2.2.21273  72.55.146.217.123
udp4   0  0
 192.168.2.2.60591  142.201.7.148.123
udp4   0  0 
10.254.2.254.123   *.*
udp4   0  0 10.254.2.254.35906
 *.*
udp4   0  0 *.1900 *.*
icm4   
0  0 *.**.*
Active UNIX domain sockets
Address 
 Type   Recv-Q Send-QInode Conn Refs  Nextref Addr
c59083f0
 stream  0  00000 
/tmp/php-fastcgi.socket-3
c5908690 stream  0  00 
c590873800
c5908738 stream  0  00 
c590869000
c5908c78 stream  0  0 
c5a84bdc000 /tmp/php-fastcgi.socket-3
c5908b28
 stream  0  0 c5b0b33c000 
/tmp/php-fastcgi.socket-2
c59089d8 stream  0  0 
c5b0bbdc000 /tmp/php-fastcgi.socket-1
c5908930
 stream  0  0 c5b0b000000 
/tmp/php-fastcgi.socket-0
c5909000 stream  0  0 
c5904ac8000 /var/run/devd.pipe
c5908dc8 
dgram   0  00 c59081500 c59091f8
c59080a8 
dgram   0  00 c5909d2000
c59091f8 
dgram   0  00 c59081500 c59087e0
c59087e0 
dgram   0  00 c59081500 c5909930
c5909930 
dgram   0  00 c59081500 c5909888
c5909888 
dgram   0  00 c59081500 c59099d8
c59099d8 
dgram   0  00 c59081500 c5909c78
c5909c78 
dgram   0  00 c590815000
c5908150 
dgram   0  0 c5a841140 c5908dc80 
/var/run/logpriv
c5909d20 dgram   0  0 c5a876780 
c59080a80 /var/run/log


So DNS does work on this box, 
as it forward DNS replies to other boxes on my local network.

What should I do next? Any ideas?

Thanks.


-M
  
Take your contacts everywhere.  Try Messenger for mobile
  
_
Take your contacts everywhere
http://go.microsoft.com/?linkid=9712959

RE: [UPDATE] Working network connectivity, not working DNS resolutions

[Mike Viau]

 Thu, 25 Mar 2010 19:00:51 -0400 tomh0...@gmail.com wrote:
  Why not add a dns-nameservers to iface br200?
 
  Updated my /etc/network/interfaces with:
  # INTERNAL LAN VLAN/BRIDGE
  iface eth1.200 inet manual
  auto br200
  iface br200 inet static
   dns-nameservers 10.254.2.254
   address 10.254.2.1
   netmask 255.255.255.0
   network 10.254.2.0
   broadcast 10.254.2.255
   gateway 10.254.2.254
   bridge-ports eth1.200
 
  But I still experience the same output including an unmodified
  /etc/resolv.conf
 
 The dns-nameservers... variable will only be recognized if you are
 running resolvconf; it is not a default /e/n/i option.
 
 

Yup you are right. I installed the resolvconf package from a deb file with dpkg.

r...@localhost:~# cat /etc/resolv.conf
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
nameserver 10.254.2.254


 -- 
 To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
 with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
 Archive: 
 http://lists.debian.org/6d4219cc1003251600v1ed8471do812d85594e416...@mail.gmail.com
 
  
My router (at 10.254.2.254) is running pfsense (a freebsd router distro)
 I found that I was able to run the dig and netstat commands from an SSH
 session.

My findings.

# dig @10.254.2.254 google.com

;
  DiG 9.4.3-P2  @10.254.2.254 google.com
;
 (1 server found)
;; global options:  printcmd
;; Got answer:
;;
 -HEADER- opcode: QUERY, status: NOERROR, id: 27942
;;
 flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;;
 QUESTION SECTION:
;google.com.IN  A

;;
 ANSWER SECTION:
google.com. 55  IN  A   
66.249.91.104

;; Query time: 4 msec
;; SERVER: 
10.254.2.254#53(10.254.2.254)
;; WHEN: Fri Mar 26 01:02:53 2010
;;
 MSG SIZE  rcvd: 44


# netstat -na
Active Internet 
connections (including servers)
Proto Recv-Q Send-Q  Local 
Address  Foreign Address(state)
tcp4   0 52 
10.254.2.254.2210.254.2.188.57059 ESTABLISHED
tcp6   
0  0 *.53   *.*LISTEN
tcp4  
 0  0 *.53   *.*LISTEN
tcp4  
 0  0 *.2189 *.*LISTEN
tcp4  
 0  0 *.80   *.*LISTEN
tcp4  
 0  0 127.0.0.1.8021 *.*LISTEN
tcp4  
 0  0 *.22   *.*LISTEN
tcp6  
 0  0 *.22   *.*LISTEN
udp4  
 0  0 *.67   *.*
udp6   0  0 
*.53   *.*
udp4   0  0 *.53  
 *.*
udp4   0  0 192.168.2.2.12176  209.139.209.82.123
udp4  
 0  0 192.168.2.2.21273  72.55.146.217.123
udp4   0  0
 192.168.2.2.60591  142.201.7.148.123
udp4   0  0 
10.254.2.254.123   *.*
udp4   0  0 10.254.2.254.35906
 *.*
udp4   0  0 *.1900 *.*
icm4   
0  0 *.**.*
Active UNIX domain sockets
Address 
 Type   Recv-Q Send-QInode Conn Refs  Nextref Addr
c59083f0
 stream  0  00000 
/tmp/php-fastcgi.socket-3
c5908690 stream  0  00 
c590873800
c5908738 stream  0  00 
c590869000
c5908c78 stream  0  0 
c5a84bdc000 /tmp/php-fastcgi.socket-3
c5908b28
 stream  0  0 c5b0b33c000 
/tmp/php-fastcgi.socket-2
c59089d8 stream  0  0 
c5b0bbdc000 /tmp/php-fastcgi.socket-1
c5908930
 stream  0  0 c5b0b000000 
/tmp/php-fastcgi.socket-0
c5909000 stream  0  0 
c5904ac8000 /var/run/devd.pipe
c5908dc8 
dgram   0  00 c59081500 c59091f8
c59080a8 
dgram   0  00 c5909d2000
c59091f8 
dgram   0  00 c59081500 c59087e0
c59087e0 
dgram   0  00 c59081500 c5909930
c5909930 
dgram   0  00 c59081500 c5909888
c5909888 
dgram   0  00 c59081500 c59099d8
c59099d8 
dgram   0  00 c59081500 c5909c78
c5909c78 
dgram   0  00 c590815000
c5908150 
dgram   0  0 c5a841140 c5908dc80 
/var/run/logpriv
c5909d20 dgram   0  0 c5a876780 
c59080a80 /var/run/log


So DNS does work on this box, 
as it forward DNS replies to other boxes on my local network.

What should I do next? Any ideas?

Thanks.


-M
  
_
Live connected with Messenger on your phone

Working network connectivity, not working DNS resolutions

[Mike Viau]

Hello debian-users,

I have run into an interesting issue with the DNS resolution on only one of my 
debian lenny systems on my network. 

I have confirmed that this system has working network connectivity but I would 
like to restore the ability to query DNS records from my local DNS server which 
is also in my case my network gateway. Additionally I can ssh into the system 
easily while connected to the same local network 10.254.2.0/24

The working (as in with other systems on my network) DNS and router is at 
10.254.2.254/24. The IP statically set for the debian system is 10.254.2.1/24

Some info from this AMD64 architecture system is below.

r...@localhost:~# cat /etc/debian_version 
5.0.4


r...@localhost:~# cat /etc/resolv.conf 
domain site
search site
nameserver 10.254.2.254


r...@localhost:~# route
Kernel IP routing table
Destination Gateway Genmask Flags Metric RefUse Iface
10.254.2.0  *   255.255.255.0   U 0  00 br200
default 10.254.2.2540.0.0.0 UG0  00 br200


Snippet from /etc/network/interfaces:

# LAN bridge
iface eth1.200 inet manual
auto br200
iface br200 inet static
 address 10.254.2.1
 network 10.254.2.0
 netmask 255.255.255.0
 broadcast 10.254.2.255
 gateway 10.254.2.254
 bridge-ports eth1.200


r...@localhost:~# ping 66.249.90.104  (a google IP beyond local router)
PING 66.249.90.104 (66.249.90.104) 56(84) bytes of data.
64 bytes from 66.249.90.104: icmp_seq=1 ttl=53 time=25.7 ms
64 bytes from 66.249.90.104: icmp_seq=2 ttl=53 time=24.3 ms
64 bytes from 66.249.90.104: icmp_seq=3 ttl=53 time=25.0 ms


r...@localhost:~# traceroute 66.249.90.104
traceroute to 66.249.90.104 (66.249.90.104), 30 hops max, 40 byte packets
 1  * * *
 2  * * *
 3  * * *
 4  * * *
 5  * * *
 6  * * *
 7  * * *
 8  * * *
 9  * * *
10  * * *
11  * * *
12  * * *
13  * * *
14  * * *
15  * * *
16  * * *
17  * * *
18  * * *
19  * * *
20  * * *
21  * * *
22  * * *
23  * * *
24  * * *
25  * * *
26  * * *
27  * * *
28  * * *
29  * * *
30  * * *


http://packages.debian.org/search?searchon=contentskeywords=resolv.confmode=filenamesuite=stablearch=amd64


Advice on how to troubleshoot further would be much appreciated, thanks.

 

-M
  
_
Live connected with Messenger on your phone
http://go.microsoft.com/?linkid=9712958