Bug#1008766: Segmentation fault using fs=4096m

[Wakko Warner]

Package: wodim
Version: 9:1.1.11-3.2
Severity: normal

I'm running on a machine with 128GB memory and I want to use a large FIFO due
to running 6 simutanious burns from the same drive.

Here's the command that doesn't work:
wodim dev=/dev/sr6 fs=4096m speed=16 tsize=2298496s -v large.iso debug=10

NOTE: I added debug=10 to see where it bombs.

Using strace, this is what I see:
35596 write(1, "Blocks total: 2298496 Blocks current: 2298496 Blocks remaining: 
0\n", 66) = 66
35596 getuid()  = 
35596 write(2, "bufsize: 65536 buffers: 65536 hdrsize 1572864\n", 46) = 46
35596 write(2, "bufsize: 65536 buffers: 65512 hdrsize 1572288\n", 46) = 46
35596 write(1, "Using 65512 buffers of 64512 bytes.\n", 36) = 36
35596 --- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_ACCERR, 
si_addr=0x7f84a10d6000} ---
35596 +++ killed by SIGSEGV +++

I found the line "Using 65512 buffers of 64512 bytes.\n" in
wodim/fifo.c:init_faio around line 467 (This is without applying debian's
patches)

I assume it has to seg somewhere between that and the fork() about 20 lines
down.

If I use fs=1024m or fs=1536m, it works w/o issues.

If I use fs=2048m, I get this:
wodim: No write mode specified.
wodim: Assuming -tao mode.
wodim: Future versions of wodim may have different drive dependent defaults.
TOC Type: 1 = CD-ROM
wodim: Cannot allocate memory. Cannot get mmap for -2147479552 Bytes on 
/dev/zero.

If I use fs=3072m, I get this:
wodim: No write mode specified.
wodim: Assuming -tao mode.
wodim: Future versions of wodim may have different drive dependent defaults.
TOC Type: 1 = CD-ROM
wodim: Cannot allocate memory. Cannot get mmap for -1073737728 Bytes on 
/dev/zero.

I'm assuming that there is a 32-bit integer involved in this.  I found in
wodim/fifo.c:mkshare that the parameter "size" is type int.  Global "bufsize"
is type long.  Looking at mmap man page, the size parameter is type size_t.
It's possible I'm wrong on this, it's been a long time since I've programmed
in C. 

-- System Information:
Debian Release: 10.0
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)



-- no debconf information

Bug#962310: chmod 0700 warning messages appears to be incorrect

[Wakko Warner]

David Kalnischkies wrote:
> On Fri, Jun 05, 2020 at 09:15:56PM -0400, Wakko Warner wrote:
> > I noticed, due to the way I have apt setup, that it complains about chmoding
> > some files.  I was looking in the source for a way to bypass this message
> > and noticed that 0700 is hard coded in the warning.
> 
> Can you describe your setup some more so that we can perhaps make apt
> deal with that setup better? It is a bit on the backburner ATM, but
> isolating the methods more from the system and each other is always on
> the TODO list and that tends to involve more directories with more
> permissions and stuff.

I keep a mirror of debian in /debian.  I usually only get dists/sid
(amd64/i386 and source only), zz-dists and pool (again, amd64/i386/source).

In apt/, I have amd64, amd64+i386 and i386.

Under those, I have 2 apt config snippets to use the local mirror (one keeps
cache on local system, other keeps it centralized).  I have a sources.list
that points to this location.  Then I have cache and lists.  These are the
same as /var/cache/apt and /var/lib/apt/lists.

After my mirror finishes, the following is ran:
unset clean
for dir in apt/*;do
 [ "$dir" = "apt/*" ] && break
 [ -e "$dir/00mirror" ] || continue
 rm -f "$dir/cache/pkgcache.bin" "$dir/cache/srcpkgcache.bin"
 apt-get ${clean+-o} $clean -o Debug::NoLocking=yes -c "$dir/00mirror" update
 clean="APT::Get::List-Cleanup=no"
done

This is not ran as root, the reason for NoLocking.  Currently, my server's
apt version is quite old and I have been reluctant to upgrade it due to this
setup and the fact that apt-file changed.  apt currenlty 1.0.7 and apt-file
2.5.1 on the server.  Clients with 2.1.6 works just fine but not apt-file

00mirror is for trusted clients (Normally part of my network) and have full
write access to the mirror.  The other part of this is to keep the .bin files
off the local machine.  This file also describes my directory layout too.
I'm only using sid for this setup.  00mirror (for my amd64+i386) contains:
Apt::Architecture "amd64";
Apt::Architectures {"amd64"; "i386";};
Dir "/debian/"
{
 State "apt/amd64+i386/"
 {
  Lists "lists/";
  extended_states "/var/lib/apt/extended_states";
  status "/var/lib/dpkg/status";
 };
 Cache "apt/amd64+i386/cache/"
 {
  Archives "/var/cache/apt/archives/";
  srcpkgcache "srcpkgcache.bin";
  pkgcache "pkgcache.bin";
 };
 Etc "/etc/apt/"
 {
  SourceList "/debian/apt/amd64+i386/sources.list";
 };
 Log "/var/log/apt";
};

The amd64 only and i386 only have that specific arch on line 1, they do not
have the 2nd line and the paths are changed respectively.

00mirror-localcache is the same, just replacing the Cache section with
Cache "/var/cache/apt/";
It's used on clients where the mirror is read only.

For the client side, all that has to be done is
1) create /debian
2) mount via nfs
3) link either 00mirror or 00mirror-localcache to /etc/apt/apt.conf.d

apt-get update is never ran on client side, it's always up to date.  I
noticed that if packagecache.bin is out of date, an apt-get install will fix
it.  I also know that the .bin files are not the same between apt versions,
however I never install packages on 2 different machines concurrently (For
the ones that use 00mirror)

> > In apt-pkg/acquire.cc:SetupAPTPartialDirectory() on lines 112 and 119 is
> > where I noticed the message.  The chown in the if statement shows it using a
> > variable named mode.  The warning message should reflect the mode it was
> > trying to set.
> 
> Indeed, thanks for reporting!
> 
> I will see how to change that string (and the one assuming root-group to
> be root even through we have a compile-time variable for that) without
> creating busywork for our translations.

Y/W.  I received another email that stated this was fixed in git already.

-- 
 Microsoft has beaten Volkswagen's world record.  Volkswagen only created 22
 million bugs.

Bug#962310: chmod 0700 warning messages appears to be incorrect

[Wakko Warner]

Package: apt
Version: 2.1.6
Severity: minor

I noticed, due to the way I have apt setup, that it complains about chmoding
some files.  I was looking in the source for a way to bypass this message
and noticed that 0700 is hard coded in the warning.

In apt-pkg/acquire.cc:SetupAPTPartialDirectory() on lines 112 and 119 is
where I noticed the message.  The chown in the if statement shows it using a
variable named mode.  The warning message should reflect the mode it was
trying to set.

Bug#932008: stat-disk.so: undefined symbol: minor

[Wakko Warner]

Package: procmeter3
Version: 3.6-2
Severity: important
Tags: patch

I get this error when launching procmeter3
ProcMeter: Cannot open the module '/usr/lib/ProcMeter3/modules/stat-disk.so' : 
/usr/lib/ProcMeter3/modules/stat-disk.so: undefined symbol: minor

3.6-1.1 didn't have this problem.

When compiling only stat-disk, I see errors for major() and minor().

The following fixed the issue for me:

--- stat-disk.c.orig2019-07-13 14:21:23.591434156 -0400
+++ stat-disk.c 2019-07-13 14:18:28.762860695 -0400
@@ -25,6 +25,7 @@
 #include 
 
 #include 
+#include 
 
 #include "procmeter.h"
 

I didn't recompile all of procmeter, just this one object.

Bug#881011: Add support for -q (quiet) and -o -

[Wakko Warner]

Package: p0f
Version: 3.09b
Severity: wishlist
Tags: patch

I like the output of the log file, but I don't like the normal output as it's
too long.  This patch was against 3.06b but should apply to 3.09b.

Option -q causes the output to be mostly quiet.  There is some output.
Option -o has been enhanced to allow - as the name to indicate stdout.

I wrote this for myself and documentation was not important so the changes
weren't documented anywhere, thus also not in the patch.

If there is interest, I can add the documentation.
--- p0f.c	2012-09-30 00:44:27.0 -0400
+++ /home/wakko/p0f-3.06b/p0f.c	2012-11-05 19:35:20.028244647 -0500
@@ -1,5 +1,6 @@
 /*
-   p0f - main entry point and all the pcap / unix socket innards
+   p0f - main
+entry point and all the pcap / unix socket innards
-
 
Copyright (C) 2012 by Michal Zalewski 
@@ -93,6 +94,8 @@
 u8 daemon_mode; /* Running in daemon mode?*/
 
 static u8 set_promisc;  /* Use promiscuous mode?  */
+
+static u8 set_quiet;/* Don't output anything.  Use -o to log */
  
 static pcap_t *pt;  /* PCAP capture thingy*/
 
@@ -217,7 +220,10 @@
 static void open_log(void) {
 
   struct stat st;
-  s32 log_fd;
+  s32 log_fd = -1;
+
+  if (log_file && log_file[0] == '-' && log_file[1] == 0)
+goto lf_open;
 
   log_fd = open((char*)log_file, O_WRONLY | O_APPEND | O_NOFOLLOW | O_LARGEFILE);
 
@@ -241,11 +247,21 @@
   if (flock(log_fd, LOCK_EX | LOCK_NB))
 FATAL("'%s' is being used by another process.", log_file);
 
-  lf = fdopen(log_fd, "a");
-
-  if (!lf) FATAL("fdopen() on '%s' failed.", log_file);
-
-  SAYF("[+] Log file '%s' opened for writing.\n", log_file);
+lf_open:
+  lf = (log_fd == -1) ?
+	fdopen(1, "w") :
+	fdopen(log_fd, "a");
+
+  if (!lf)
+  	FATAL("fdopen() on '%s' failed.",
+  	(int)log_fd == -1 ? 
+  	"stdout" :
+  	(char *)log_file);
+
+  if (log_fd == -1)
+SAYF("[+] Log file using stdout for writing.\n");
+  else
+SAYF("[+] Log file '%s' opened for writing.\n", log_file);
 
 }
 
@@ -311,7 +327,7 @@
 
   if (obs_fields) FATAL("Premature end of observation.");
 
-  if (!daemon_mode) {
+  if (!daemon_mode && !set_quiet) {
 
 SAYF(".-[ %s/%u -> ", addr_to_str(f->client->addr, f->client->ip_ver),
  f->cli_port);
@@ -353,7 +369,7 @@
 
   if (!obs_fields) FATAL("Unexpected observation field ('%s').", key);
 
-  if (!daemon_mode)
+  if (!daemon_mode && !set_quiet)
 SAYF("| %-8s = %s\n", key, value ? value : (u8*)"???");
 
   if (log_file) LOGF("|%s=%s", key, value ? value : (u8*)"???");
@@ -362,7 +378,7 @@
 
   if (!obs_fields) {
 
-if (!daemon_mode) SAYF("|\n`\n\n");
+if (!daemon_mode && !set_quiet) SAYF("|\n`\n\n");
 
 if (log_file) LOGF("\n");
 
@@ -1022,7 +1038,7 @@
   if (getuid() != geteuid())
 FATAL("Please don't make me setuid. See README for more.\n");
 
-  while ((r = getopt(argc, argv, "+LS:df:i:m:o:pr:s:t:u:")) != -1) switch (r) {
+  while ((r = getopt(argc, argv, "+LS:df:i:m:o:pr:qs:t:u:")) != -1) switch (r) {
 
 case 'L':
 
@@ -1104,6 +1120,10 @@
   set_promisc = 1;
   break;
 
+case 'q':
+  set_quiet = 1;
+  break;
+
 case 'r':
 
   if (read_file)
@@ -1168,6 +1188,13 @@
   if (!api_sock && api_max_conn != API_MAX_CONN)
 FATAL("Option -S makes sense only with -s.");
 
+  if (set_quiet) {
+if (daemon_mode)
+  FATAL("Daemon mode is already quiet");
+if (!log_file)
+  FATAL("Quiet requires a log file");
+  }
+
   if (daemon_mode) {
 
 if (read_file)

Bug#816871: Segfault in battery.so

[Wakko Warner]

Package: procmeter3
Version: 3.6-1
Severity: important

Procmeter segfaults every time.  Strace shows it trying to open
/sys/class/power_supply which doesn't exist on my system.  Removing
battery.so causes procmeter to work.  Procmeter 3.5d-1 works.

Here's the strace:
open("/usr/lib/ProcMeter3/modules/battery.so", O_RDONLY|O_CLOEXEC) = 5
read(5, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0@\22\0\0\0\0\0\0"..., 
832) = 832
fstat(5, {st_mode=S_IFREG|0644, st_size=18280, ...}) = 0
mmap(NULL, 2113640, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 5, 0) = 
0x7f1390b55000
mprotect(0x7f1390b58000, 2097152, PROT_NONE) = 0
mmap(0x7f1390d58000, 8192, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 5, 0x3000) = 0x7f1390d58000
close(5)= 0
mprotect(0x7f1390d58000, 4096, PROT_READ) = 0
openat(AT_FDCWD, "/sys/class/power_supply", 
O_RDONLY|O_NONBLOCK|O_DIRECTORY|O_CLOEXEC) = -1 ENOENT (No such file or 
directory)
--- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_MAPERR, si_addr=0} ---
+++ killed by SIGSEGV +++
zsh: segmentation fault  strace procmeter3

GDB:
(gdb) run
Starting program: /usr/bin/procmeter3 

Program received signal SIGSEGV, Segmentation fault.
0x76874b40 in dirfd () from /lib/x86_64-linux-gnu/libc.so.6
(gdb) bt
#0  0x76874b40 in dirfd () from /lib/x86_64-linux-gnu/libc.so.6
#1  0x745377b4 in Initialise ()
   from /usr/lib/ProcMeter3/modules/battery.so
#2  0xf67f in LoadModule ()
#3  0xfc00 in LoadAllModules ()
#4  0x8bc8 in main ()
(gdb) 


Please note the following information was when 3.5d-1 was installed.
-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.4.4 (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/bash
Init: sysvinit (via /sbin/init)

Versions of packages procmeter3 depends on:
ii  libatk1.0-0 2.18.0-1
ii  libc6   2.21-9
ii  libcairo2   1.14.6-1
ii  libfontconfig1  2.11.0-6.3
ii  libfreetype62.6.1-0.1
ii  libgdk-pixbuf2.0-0  2.32.3-1.2
ii  libglib2.0-02.46.2-3
ii  libgtk2.0-0 2.24.29-1
ii  libice6 2:1.0.9-1+b1
ii  libpango1.0-0   1.38.1-1
ii  libsensors4 1:3.4.0-2
ii  libsm6  2:1.2.2-1+b1
ii  libx11-62:1.6.3-1
ii  libxaw7 2:1.0.13-1
ii  libxext62:1.3.3-1
ii  libxmu6 2:1.1.2-2
ii  libxt6  1:1.1.5-1

procmeter3 recommends no packages.

procmeter3 suggests no packages.

-- no debconf information

Bug#724230: rwhod spams syslog

[Wakko Warner]

Package: rwhod
Version: 0.17-13
Severity: minor

The change in rwhod from -12 to -13 causes it to log to the syslog every 3
minutes.

I diffed -12 and -13 and noticed that it calls configure(sk) in the main loop
and that it forgets previous neighbors; interfaces may have changed.
I'm using rwhod with -i eth0 to limit to my internal network.

I also noticed 2013-09-22 15:13:23 ani rwhod[28401]: specified interface eth0
more than once was listed.  Downgrading to -12 fixes the problem for me.

Maybe make this a switch?

-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 3.5.0 (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/bash

Versions of packages rwhod depends on:
ii  adduser   3.113+nmu3
ii  libc6 2.17-92+b1
ii  lsb-base  4.1+Debian12
ii  passwd1:4.1.4.2+svn3283-3

rwhod recommends no packages.

rwhod suggests no packages.

-- Configuration Files:
/etc/cron.monthly/rwhod [Errno 2] No such file or directory: 
u'/etc/cron.monthly/rwhod'
/etc/default/rwhod changed [not included]

-- no debconf information


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

Bug#710201: [Packaging] Bug#710201: Bug#710201: Bug#710201: Bug#710201: Ability to turn off fields in graph

[Wakko Warner]

Stig Sandbeck Mathisen wrote:
 Wakko Warner wa...@animx.eu.org writes:
 
  Thanks, however I sent another patch that replaced the previous patch.
  The latest one was complete with all the changes including the html.
 
 You sent two patches, named munin-2.1.diff, and munin-2.1.1.diff. I took
 the 2.1.1 patch, assuming the number is a version number of the patch,
 and that a higher version number is better. Were my assumtions correct?

Sorry for the confusion.  I placed the version of munin in the name of the
patch.  The first time, I left off the revision of the 2.1.x, second time I
didn't.  Just didn't remember about which way I did it before.  Could have
been the excitement of completing it =)

 As seen on the URI I sent,
 http://munin-monitoring.org/changeset/d2e28ce6f65cb43b95cd98632864e2ed6fde963b/munin-dev/,
 the munin-2.1.1.diff contains changes in the following source files:
 
 *  _bin/munin-cgi-graph.in (4 diffs)
 * lib/Munin/Master/GraphOld.pm (17 diffs)
 * lib/Munin/Master/HTMLConfig.pm (3 diffs)
 * static/dynazoom.html (5 diffs)
 * static/dynazoom.js
 * static/querystring.js (1 diff) 
 
 Just to avoid further confusion, and to be explicit, is this
 (munin-2.1.1.diff) the patch you want us to use?

This is the correct one.

-- 
 Microsoft has beaten Volkswagen's world record.  Volkswagen only created 22
 million bugs.


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

Bug#710201: [Packaging] Bug#710201: Bug#710201: Bug#710201: Bug#710201: Ability to turn off fields in graph

[Wakko Warner]

Stig Sandbeck Mathisen wrote:
 Wakko Warner wa...@animx.eu.org writes:
 
  Just to avoid further confusion, and to be explicit, is this
  (munin-2.1.1.diff) the patch you want us to use?
 
  This is the correct one.
 
 Excellent, thanks. :)

You're welcome.  It bugged me that much!  =)

FYI: I tested with IE7 today and it does not work.  IE8 does work.  I
personally feel that if someone is still using IE7, they would need to
install something better like firefox (iceweasel) or chrome (chromium). 
This has been tested on the following browsers and works to my satisfaction:
Firefox 0.9.x (Yes, it's old! =)
Iceweasel 3.6.13, 17, and 21
Chromium 26
IE8 and up.  (Works better with IE9 and 10 compared to 8)

IE7 won't show load the image.  I assume it's a problem with the javascript
DOM.  But like I said earlier, I'm not that good with javascript.

-- 
 Microsoft has beaten Volkswagen's world record.  Volkswagen only created 22
 million bugs.


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

Bug#710201: [Packaging] Bug#710201: Bug#710201: Bug#710201: Ability to turn off fields in graph

[Wakko Warner]

Stig Sandbeck Mathisen wrote:
 Wakko Warner wa...@animx.eu.org writes:
 
  Holger Levsen wrote:
  Also, please reply to the bug and attach the code you currently have 
  (and/or 
  provide the link to a git repo which has it :)
 
  Sorry, no git. I'm working on a test vm with a live install.
 
  This patch is ONLY for the munin perl code. I will have changed
  dynazoom.html so much that attaching it will be smaller.
 
 Thanks for the contribution. :)
 
 I've cleaned up the filename and whitespace issues in the patch, and
 imported it into a git branch called bts/710201-better-cgi-graphing in
 the upstream munin-dev repo.
 
 The commit is visible at
 http://munin-monitoring.org/changeset/d2e28ce6f65cb43b95cd98632864e2ed6fde963b/munin-dev/

Thanks, however I sent another patch that replaced the previous patch.  The
latest one was complete with all the changes  including the html.

-- 
 Microsoft has beaten Volkswagen's world record.  Volkswagen only created 22
 million bugs.


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

Bug#710201: [PATCH] Bug#710201: Ability to turn off fields in graph

[Wakko Warner]

I've played with this enough.  I've added more features than this wishlist.

Here's the broad idea of what's changed.
1) 3 clicks to zoom has been replaced with drag'n'drop style selecting.
2) Ability to turn off fields (exception, cannot turn all fields off).
The graph total is not considered a field, but is able to be turned
off as well.  Fields turned off will not be shown in the graph
legend.
3) When a field is listed in the graph legend and has been unchecked, a gray
out bar is shown over the field in the legend.
4) As a convenience, the field line in the graph legend is clickable.
5) Original dynazoom.html did not work with IE8.  This version works to an
extent with IE8 with 1 known bug.  If the paged is scrolled to the
horizontally, the zoom selection will be wrong.
6) Added a second submit button just below the graph for convenience.
7) Limit low/high also will accept 'none' and will let rrdtool pick it's own
limits.  Could possibly change this to 'auto' instead.
8) Added ability to force area draw type to line.
9) Added ability to disable stacking.  I found these 2 items to be useful
when looking at the memory graph.

Patch is attached.  It should apply cleanly to munin 2.0 (untested), but this
was done against 2.1.1.  I don't believe there was enough changes in 2.1.2 to
make a difference.
diff -ruN /root/munin/usr/lib/munin/cgi/munin-cgi-graph ./munin-cgi-graph
--- /root/munin/usr/lib/munin/cgi/munin-cgi-graph   2013-05-27 
15:52:30.0 -0400
+++ ./munin-cgi-graph   2013-06-29 12:08:40.166711000 -0400
@@ -102,6 +102,7 @@
 my $path = $ENV{PATH_INFO} || ;
 
 DEBUG Request path is $path;
+DEBUG Request query is $ENV{QUERY_STRING};
 
 # The full URL looks like this:
 # Case 1:
@@ -342,6 +343,8 @@
 my $scale   = shift;
 my $fileext = shift;
 my $params  = shift;
+my $filename_base;
+my $filename;
 
 # XXX - hack to fix cgitmpdir default 
 $config-{cgitmpdir} ||= $Munin::Common::Defaults::MUNIN_CGITMPDIR;
@@ -350,7 +353,17 @@
 $params = $params ? ?$params : ;
 $params =~ tr/\//_/; # / are forbidden in a filename
 $params = $1 if $params =~ m/(.*)/; # XXX - QD untaint
-return $cgi_tmp_dir/$domain/$name/$service-$scale.$fileext . $params;
+$filename_base = $cgi_tmp_dir/$domain/$name/$service-$scale.$fileext;
+$filename = $filename_base . $params;
+
+# Due to the ability to graph specific fields, the filename can now be way
+# too long.  Exploit -f to see if the name is too long.
+if (! -f $filename  $!{ENAMETOOLONG})
+{
+$filename = $filename_base . Digest::MD5::md5_hex($params);
+}
+DEBUG [DEBUG] Using $filename as image name;
+return $filename;
 }
 
 sub has_offending_chars {
@@ -480,6 +493,19 @@
 push @params, --debug
   if (CGI::param(debug));
 
+# Limit fields
+push @params, map {('--field' = $_)} CGI::param(field);
+
+# Graph total
+push @params, --nototal if CGI::param(nototal);
+
+# Force draw to line1
+push @params, --force-line if CGI::param(force_line);
+
+# Disable stacking
+push @params, --nostack if CGI::param(nostack);
+
+DEBUG graph_main(\ . join(', ', @params) . \);;
 graph_main(\@params);
 
 return $filename;
diff -ruN /root/munin/usr/share/perl5/Munin/Master/GraphOld.pm ./GraphOld.pm
--- /root/munin/usr/share/perl5/Munin/Master/GraphOld.pm2013-05-27 
15:51:16.0 -0400
+++ ./GraphOld.pm   2013-06-29 12:14:23.694711000 -0400
@@ -94,6 +94,9 @@
 my $skip_locking   = 0;
 my $skip_stats = 0;
 my $stdout = 0;
+my $nototal= 0;
+my $nostack= 0;
+my $force_line = 0;
 my $force_run_as_root = 0;
 my $conffile   = $Munin::Common::Defaults::MUNIN_CONFDIR . /munin.conf;
 my $libdir = $Munin::Common::Defaults::MUNIN_LIBDIR;
@@ -162,6 +165,7 @@
 # Limit graphing to certain hosts and/or services
 my @limit_hosts= ();
 my @limit_services = ();
+my @limit_fields = ();
 my $only_fqn = '';
 
 my $watermark = Munin  . $Munin::Common::Defaults::MUNIN_VERSION;
@@ -183,6 +187,7 @@
 
 my @init_limit_hosts = @limit_hosts;
 my @init_limit_services = @limit_services;
+my @init_limit_fields = @limit_fields;
 
 sub process_pinpoint {
 my ($pinpoint, $arg_name, $arg_value) = @_; 
@@ -225,6 +230,7 @@
 %draw = %init_draw;
 @limit_hosts = @init_limit_hosts;
 @limit_services = @init_limit_services;
+@limit_fields = @init_limit_fields;
 
 $pinpoint   = undef;
 my $pinpointopt= undef;
@@ -240,6 +246,9 @@
 $skip_locking   = 0;
 $skip_stats = 0;
 $stdout = 0;
+$nototal= 0;
+$nostack= 0;
+$force_line = 0;
 
 $size_x= undef;
 $size_y = undef;
@@ -265,9 +274,13 @@
 lazy! = \$force_lazy,
 host=s= \@limit_hosts,
 service=s = \@limit_services,
+   

Bug#710201: [Packaging] Bug#710201: Bug#710201: Ability to turn off fields in graph

[Wakko Warner]

Holger Levsen wrote:
 Also, please reply to the bug and attach the code you currently have (and/or 
 provide the link to a git repo which has it :)

Sorry, no git.  I'm working on a test vm with a live install.

This patch is ONLY for the munin perl code.  I will have changed
dynazoom.html so much that attaching it will be smaller.

The patch attached does the following:
GraphOld.pm:
1) Adds --nototal
2) Adds --fields
3) Adds skipping fields in process_service
4) BUG with stacked fields and skipping the first non stacked fields
5) Keeps field color the same
6) Causes the total virtual field to be skipped based on --nototal
HTMLConfig.pm:
7) Adds URL::Escape
8) Add generating a list of fields with labels
9) Adds the generated field list to the dynazoom urls as pairs of
field=field:label and uses URL::Escape to encode it
10) Adds hastotal=1 to the dynazoom urls
munin-cgi-graph:
11) Add debug with QUERY_STRING.  (My debugging, may remove)
12) Adds filename too long checking.  Urls generated by dynazoom.html can
now be too long.  If this happens, the params is MD5 encoded
13) Adds --field foreach field= CGI Parameter
14) Adds --nototal if nototal CGI parameter is ... I don't remember if it
was a test for existence or a test for a true value.  Possibly true
value.

Another feature I've changed in dynazoom is the click 'n' drag to select an
area to zoom into.  The original 3 clicks was annoying.  At this point, it
works, but I took dynazoom.html fresh after fixing the original bugs.

diff -ruN /usr/lib/munin/cgi/munin-cgi-graph-orig 
/usr/lib/munin/cgi/munin-cgi-graph
--- /usr/lib/munin/cgi/munin-cgi-graph-orig 2013-05-27 15:52:30.0 
-0400
+++ /usr/lib/munin/cgi/munin-cgi-graph  2013-06-09 20:23:15.418711000 -0400
@@ -102,6 +102,7 @@
 my $path = $ENV{PATH_INFO} || ;
 
 DEBUG Request path is $path;
+DEBUG Request query is $ENV{QUERY_STRING};
 
 # The full URL looks like this:
 # Case 1:
@@ -342,6 +343,8 @@
 my $scale   = shift;
 my $fileext = shift;
 my $params  = shift;
+my $filename_base;
+my $filename;
 
 # XXX - hack to fix cgitmpdir default 
 $config-{cgitmpdir} ||= $Munin::Common::Defaults::MUNIN_CGITMPDIR;
@@ -350,7 +353,17 @@
 $params = $params ? ?$params : ;
 $params =~ tr/\//_/; # / are forbidden in a filename
 $params = $1 if $params =~ m/(.*)/; # XXX - QD untaint
-return $cgi_tmp_dir/$domain/$name/$service-$scale.$fileext . $params;
+$filename_base = $cgi_tmp_dir/$domain/$name/$service-$scale.$fileext;
+$filename = $filename_base . $params;
+
+# Due to the ability to graph specific fields, the filename can now be way
+# too long.  Exploit -f to see if the name is too long.
+if (! -f $filename  $!{ENAMETOOLONG})
+{
+$filename = $filename_base . Digest::MD5::md5_hex($params);
+}
+DEBUG [DEBUG] Using $filename as image name;
+return $filename;
 }
 
 sub has_offending_chars {
@@ -480,6 +493,12 @@
 push @params, --debug
   if (CGI::param(debug));
 
+# Limit fields
+push @params, map {('--field' = $_)} CGI::param(field);
+
+# Graph total
+push @params, --nototal if CGI::param(nototal);
+DEBUG graph_main(\ . join(', ', @params) . \);;
 graph_main(\@params);
 
 return $filename;
diff -ruN /usr/share/perl5/Munin/Master/GraphOld-old.pm 
/usr/share/perl5/Munin/Master/GraphOld.pm
--- /usr/share/perl5/Munin/Master/GraphOld-orig.pm  2013-05-27 
15:51:16.0 -0400
+++ /usr/share/perl5/Munin/Master/GraphOld.pm   2013-06-03 13:06:25.054711000 
-0400
@@ -94,6 +94,7 @@
 my $skip_locking   = 0;
 my $skip_stats = 0;
 my $stdout = 0;
+my $nototal= 0;
 my $force_run_as_root = 0;
 my $conffile   = $Munin::Common::Defaults::MUNIN_CONFDIR . /munin.conf;
 my $libdir = $Munin::Common::Defaults::MUNIN_LIBDIR;
@@ -162,6 +163,7 @@
 # Limit graphing to certain hosts and/or services
 my @limit_hosts= ();
 my @limit_services = ();
+my @limit_fields = ();
 my $only_fqn = '';
 
 my $watermark = Munin  . $Munin::Common::Defaults::MUNIN_VERSION;
@@ -183,6 +185,7 @@
 
 my @init_limit_hosts = @limit_hosts;
 my @init_limit_services = @limit_services;
+my @init_limit_fields = @limit_fields;
 
 sub process_pinpoint {
 my ($pinpoint, $arg_name, $arg_value) = @_; 
@@ -225,6 +228,7 @@
 %draw = %init_draw;
 @limit_hosts = @init_limit_hosts;
 @limit_services = @init_limit_services;
+@limit_fields = @init_limit_fields;
 
 $pinpoint   = undef;
 my $pinpointopt= undef;
@@ -240,6 +244,7 @@
 $skip_locking   = 0;
 $skip_stats = 0;
 $stdout = 0;
+$nototal= 0;
 
 $size_x= undef;
 $size_y = undef;
@@ -265,9 +270,11 @@
 lazy! = \$force_lazy,
 host=s= \@limit_hosts,
 service=s = \@limit_services,
+field=s   = \@limit_fields,
 only-fqn=s 

Bug#710201: [Packaging] Bug#710201: Ability to turn off fields in graph

[Wakko Warner]

Holger Levsen wrote:
 thanks for the bug report. I've tagged it upstream and notified them.

I don't know if anyone has started to work on this, but I've got something
working for me.  It's not ready to be released yet.  It has a few minor
problems that needs to be worked out.

An addition to this specific wishlist, I added the ability to not graph the
totals.

I'll attach a patch when I'm ready.

I should mention that I'm using version 2.1.1-1 for my testing.  It should
apply to 2.0 as well when I'm finished.


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

Bug#710201: Ability to turn off fields in graph

[Wakko Warner]

Package: munin
Severity: wishlist

I've been toying with munin v2 and I like the dynazoom.
Some plugins will output many fields (IE: df with many mounted filesystems)
and sometimes the graph can be difficult to read.

I think it would be nice to be able to have this ability.  My thoughts would
be to extend dynazoom to allow for this.  I'm pretty sure that this would
also entail a change to the GraphOld.pm.


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

Bug#700762: System fails to shutdown due to iscsid being terminated.

[Wakko Warner]

Ritesh Raj Sarraf wrote:
 Hello Wakko
 
 On Sun, Feb 17, 2013 at 8:13 AM, Wakko Warner wa...@animx.eu.org wrote:
  I have a test system that boots over iSCSI.  If iscsid is killed and the
  kernel decides to sync the scsi caches, the iSCSI connection fails.
 
 How is iscsid being killed here?
 
 I still can't see whey the connection would fail.

I tested it on one of my systems and it works.  iscsid is killed during
shutdown by sendsigs.  I don't know why either, but once iscsid is dead, the
kernel will sync the scsi cache and then the iscsi driver cannot connect
anymore.

  I change the init script to drop a link to the PID file for iscsid to the
  /run/sendsigs.omit.d and it shuts down properly now.
 
  I've attached the patch, it's only adds 2 lines.
 
 
 I looked but have no clue at what it does.

It places a link to the pid file so that send sigs will not kill it.

-- 
 Microsoft has beaten Volkswagen's world record.  Volkswagen only created 22
 million bugs.


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

Bug#700762: System fails to shutdown due to iscsid being terminated.

[Wakko Warner]

Package: open-iscsi
Version: 2.0.872-2
Severity: normal
Tags: patch

I have a test system that boots over iSCSI.  If iscsid is killed and the
kernel decides to sync the scsi caches, the iSCSI connection fails.

I change the init script to drop a link to the PID file for iscsid to the
/run/sendsigs.omit.d and it shuts down properly now.

I've attached the patch, it's only adds 2 lines.

-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 3.3.0
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages open-iscsi depends on:
ii  libc6 2.13-20Embedded GNU C Library: Shared lib
ii  udev  172-1  /dev/ and hotplug management daemo

open-iscsi recommends no packages.

-- no debconf information
--- a/open-iscsi	2011-09-14 05:18:39.0 -0400
+++ b/open-iscsi	2013-02-16 21:39:20.0 -0500
@@ -14,6 +15,7 @@
 PIDFILE=/var/run/iscsid.pid
 NAMEFILE=/etc/iscsi/initiatorname.iscsi
 CONFIGFILE=/etc/iscsi/iscsid.conf
+OMITDIR=/run/sendsigs.omit.d
 
 [ -x $DAEMON ] || exit 0
 
@@ -97,6 +99,7 @@
 	modprobe -q iscsi_tcp 2/dev/null || :
 	modprobe -q ib_iser 2/dev/null || :
 	start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON
+	ln -s $PIDFILE $OMITDIR
 	RETVAL=$?
 	log_end_msg $RETVAL
 

Bug#698077: Syntax highlighting for shell scripts broken with left bit shift

[Wakko Warner]

Package: joe
Version: 3.7-2.3
Severity: minor

When writing a script I found that use of  causes problems with bash's
( ) notation.  Ex:

Run joe similar to this:
$ joe test.sh

Type in these 3 lines:
#!/bin/bash
(x = 1  2)
if [

The 3rd line is incomplete, however, the if [ is not colored correctly.
By adding a space between the , the coloring becomes correct.

Joe 3.3 did not have this problem.  Have not tested on any versions between
3.3 and 3.7

I have joe 3.5-1, 3.5-1.1 and 3.5-2 incase I need to test with those versions.

I modified my sh.jsf on line 42 from
*   inc buffer noeat
to
*   idle

Which fixes the problem for me.  I know this is not the proper solution but
I unfortunately don't understand the highlighting syntax.

-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 3.5.0 (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/bash

Versions of packages joe depends on:
ii  libc6 2.13-37Embedded GNU C Library: Shared lib
ii  libncurses5   5.9-10 shared libraries for terminal hand
ii  libtinfo5 5.9-10 shared low-level terminfo library 

joe recommends no packages.

-- no debconf information


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

Bug#677654: fsdev is not supported

[Wakko Warner]

Package: qemu-system
Version: 1.1.0+dfsg-1
Severity: normal

I upgraded to this version and noticed that fsdev was no longer supported.
Downgrading to 1.0.1+dfsg-1 works.

Is fsdev no longer supported?



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

Bug#674919: Fails to start with -fsdev

[Wakko Warner]

Michael Tokarev wrote:
 On 29.05.2012 07:56, Wakko Warner wrote:
 []
  (process:14897): GLib-CRITICAL **: g_thread_pool_new: assertion 
  `g_thread_supported ()' failed
  worker thread initialization failed
 []
  You know what, forget all of the above.  My libglib version is 2.28.6-1.  I
  extracted the library from libglib2.0-0_2.32.3-1_amd64.deb and ran:
  LD_LIBRARY_PATH=/junk/kvm/glib/lib/x86_64-linux-gnu 
  /junk/kvm/qemu-kvm-1.0-11-debian/usr/bin/kvm -fsdev 
  local,security_model=mapped,id=fsdev-fs0,path=/var -device 
  virtio-9p-pci,id=fs0,fsdev=fsdev-fs0,mount_tag=kernel,bus=pci.0,addr=0x3 -M 
  pc-0.14 -nodefaults -vga std
  and it works fine.
  
  The fix for this bug might be to just depend on a newer version of
  libglib2.0-0.  I upgraded this package on my system and qemu-kvm and
  everything is happy.
 
 Thank you Wakko, thank you very much for finding this.  Trying
 different glib version is something I'd do at the very end if
 I had to debug this problem, so it is very unlikely I'd found
 it even if I really tried... ;)  And note I'd start with squeeze
 version (see below) and that'd failed to reproduce the issue too :)

I'm using SID actually.  After the compiles worked (I did 3.  One I reverted
the pci fix that went into -10, then the other 2 were no changes, just
different gcc versions)  I figured since both worked and the error thrown
was a glib error, I figured I'd try a newer glib.

 Now, it is actually interesting.  libglib2.0-0 version in squeeze
 is 2.24.2-1, and that version actually _works_.  I don't have
 2.28.6-1 version around (I know about snapshot.d.o).  It is even
 more interesting that the problem only manifests itself when
 using this -fsdev option.

I keep the old packages that are removed from debian (2.7tb worth of source,
amd64 and i386) incase something like this happens.  If you would like, I
can provide you with the version of glib that doesn't work.

It is interesting.  Most of my VMs use fsdev for the modules.  That way, I
have 1 copy of the modules, kernel, etc for all the VMs I have.  I found
that this was the cause because I have 2 test VMs that are net booting and
don't use fsdev.  The fsdev ones failed, the netboot started.

 When qemu-kvm is compiled against current version of libglib2,
 the dependency placed for the package is = 2.24.0 (this is
 a manual dependency from soversions file in libglib package).
 That file becomes out of date quite often, for many and especially
 complex packages, since it is difficult to watch for the symbol
 or behavour changes carefully.

I can understand that.

 The difference between -9 and -11 packages regarding glib is that
 -9 were compiled against older libglib package (pre-2.32), while
 when I compiled -11, some 2.32.x version were current.  So this
 sort of proves this theory, which becomes a mismatch between
 more recent libglib headers or library and older runtme library
 (which is all about that soversions file).

Makes sense.

 Hmm.
 
 I'll try to take a look at all this when I've some spare time
 (as I already mentioned I'm quite busy currently).  But at least,
 can we downgrade the severity of the bug now, please? :)

I know how the busy thing goes.  I see no reason not to downgrade that.

 And thank you very much, once again, for the great work you
 did by finding the real cause, really, much apprecated!

You're welcome.  The only pain was trying to install the -dev packages for
the libraries I had installed.

-- 
 Microsoft has beaten Volkswagen's world record.  Volkswagen only created 22
 million bugs.



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

Bug#674919: Fails to start with -fsdev

[Wakko Warner]

Package: qemu-kvm
Version: 1.0+dfsg-11
Severity: important

I'm using libvirt 0.9.9-3+b2 to start VMs with kvm.  I just upgraded qemu-kvm.
I am no longer able to start VMs where I have defined a file system device. 
My previous version was 1.0+dfsg-9 

This is what I see:
# LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin 
HOME=/root USER=root LOGNAME=root /usr/bin/kvm -S -M pc-0.14 -cpu core2duo 
-enable-kvm -m 512 -smp 1,sockets=1,cores=1,threads=1 -name iscsiinit -uuid 
128a255b-23db-a249-53ad-4226bc2f129e -nographic -nodefconfig -nodefaults 
-chardev 
socket,id=charmonitor,path=/var/lib/libvirt/qemu/iscsiinit.monitor,server,nowait
 -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-shutdown 
-drive file=/vm/iscsiinit.qcow2,if=none,id=drive-virtio-disk0,format=qcow2 
-device 
virtio-blk-pci,bus=pci.0,addr=0x5,drive=drive-virtio-disk0,id=virtio-disk0 
-fsdev local,security_model=mapped,id=fsdev-fs0,path=/var/local/kvm/kernel 
-device 
virtio-9p-pci,id=fs0,fsdev=fsdev-fs0,mount_tag=kernel,bus=pci.0,addr=0x3 
-chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 
-usb -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x7
char device redirected to /dev/pts/5

(process:14897): GLib-CRITICAL **: g_thread_pool_new: assertion 
`g_thread_supported ()' failed
worker thread initialization failed
#

Removing the 
-device virtio-9p-pci,id=fs0,fsdev=fsdev-fs0,mount_tag=kernel,bus=pci.0,addr=0x3
I get this:

# LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin 
HOME=/root USER=root LOGNAME=root /usr/bin/kvm -S -M pc-0.14 -cpu core2duo 
-enable-kvm -m 512 -smp 1,sockets=1,cores=1,threads=1 -name iscsiinit -uuid 
128a255b-23db-a249-53ad-4226bc2f129e -nographic -nodefconfig -nodefaults 
-chardev 
socket,id=charmonitor,path=/var/lib/libvirt/qemu/iscsiinit.monitor,server,nowait
 -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-shutdown 
-drive file=/vm/iscsiinit.qcow2,if=none,id=drive-virtio-disk0,format=qcow2 
-device 
virtio-blk-pci,bus=pci.0,addr=0x5,drive=drive-virtio-disk0,id=virtio-disk0 
-fsdev local,security_model=mapped,id=fsdev-fs0,path=/var/local/kvm/kernel 
-chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 
-usb -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x7 
char device redirected to /dev/pts/14
^Cqemu: terminating on signal 2
#

I cancelled the command after a few seconds.  The one above died immediately.

Downgrading to -9 works fine.

-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.9 (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash

Versions of packages qemu-kvm depends on:
ii  adduser 3.112+nmu2   add and remove users and groups
ii  ipxe1.0.0+git-2.149b50-1 PXE boot firmware
ii  libaio1 0.3.109-1Linux kernel AIO access library - 
ii  libasound2  1.0.24.1-4   shared library for ALSA applicatio
ii  libbluetooth3   4.93-3   Library to use the BlueZ Linux Blu
ii  libbrlapi0.54.2-7braille display access via BRLTTY 
ii  libc6   2.13-10  Embedded GNU C Library: Shared lib
ii  libcurl3-gnutls 7.21.6-1 Multi-protocol file transfer libra
ii  libglib2.0-02.28.6-1 The GLib library of C routines
ii  libgnutls26 2.12.19-1GNU TLS library - runtime library
ii  libiscsi1   1.0.1-1  iSCSI client shared library
ii  libjpeg88c-2 Independent JPEG Group's JPEG runt
ii  libncurses5 5.9-1shared libraries for terminal hand
ii  libpng12-0  1.2.46-3 PNG library - runtime
ii  libpulse0   1.0-2PulseAudio client libraries
ii  librados2   0.43-1   RADOS distributed object store cli
ii  librbd1 0.43-1   RADOS block device client library
ii  libsasl2-2  2.1.25.dfsg1-2   Cyrus SASL - authentication abstra
ii  libsdl1.2debian 1.2.14-6.4   Simple DirectMedia Layer
ii  libspice-server10.10.1-2 Implements the server side of the 
ii  libtinfo5   5.9-2shared low-level terminfo library 
ii  libuuid12.19.1-5 Universally Unique ID library
ii  libvdeplug2 2.2.3-3+b1   Virtual Distributed Ethernet - Plu
ii  libx11-62:1.4.3-2X11 client-side library
ii  python  2.6.6-14 interactive high-level object-orie
ii  qemu-keymaps0.14.0+dfsg-5.1  QEMU keyboard maps
ii  qemu-utils  0.14.0+dfsg-5.1  QEMU utilities
ii  seabios 1.6.3-2  Legacy BIOS implementation
ii  

Bug#674919: Fails to start with -fsdev

[Wakko Warner]

Michael Tokarev wrote:
 tags 674919 + moreinfo unreproducible
 thanks
 
 On 28.05.2012 20:00, Wakko Warner wrote:
  Package: qemu-kvm
  Version: 1.0+dfsg-11
  Severity: important
  
  I'm using libvirt 0.9.9-3+b2 to start VMs with kvm.  I just upgraded 
  qemu-kvm.
  I am no longer able to start VMs where I have defined a file system device. 
  My previous version was 1.0+dfsg-9 
  
  This is what I see:
  # LC_ALL=C 
  PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin 
  HOME=/root USER=root LOGNAME=root /usr/bin/kvm -S -M pc-0.14 -cpu core2duo 
  -enable-kvm -m 512 -smp 1,sockets=1,cores=1,threads=1 -name iscsiinit -uuid 
  128a255b-23db-a249-53ad-4226bc2f129e -nographic -nodefconfig -nodefaults 
  -chardev 
  socket,id=charmonitor,path=/var/lib/libvirt/qemu/iscsiinit.monitor,server,nowait
   -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc 
  -no-shutdown -drive 
  file=/vm/iscsiinit.qcow2,if=none,id=drive-virtio-disk0,format=qcow2 -device 
  virtio-blk-pci,bus=pci.0,addr=0x5,drive=drive-virtio-disk0,id=virtio-disk0 
  -fsdev local,security_model=mapped,id=fsdev-fs0,path=/var/local/kvm/kernel 
  -device 
  virtio-9p-pci,id=fs0,fsdev=fsdev-fs0,mount_tag=kernel,bus=pci.0,addr=0x3 
  -chardev pty,id=charserial0 -device 
  isa-serial,chardev=charserial0,id=serial0 -usb -device 
  virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x7
  char device redirected to /dev/pts/5
  
  (process:14897): GLib-CRITICAL **: g_thread_pool_new: assertion 
  `g_thread_supported ()' failed
  worker thread initialization failed
  #
  
  Removing the 
  -device 
  virtio-9p-pci,id=fs0,fsdev=fsdev-fs0,mount_tag=kernel,bus=pci.0,addr=0x3
  I get this:
 [works]
 
 I can't reproduce this.  It works here with 1.0+dfsg-11 just fine:
 
 $ kvm -fsdev local,security_model=mapped,id=fsdev-fs0,path=/var -device 
 virtio-9p-pci,id=fs0,fsdev=fsdev-fs0,mount_tag=kernel,bus=pci.0,addr=0x3 -M 
 pc-0.14 -nodefaults -vga std
 
 What I'm doing wrong?
 
 Maybe there are some other options which interfere,
 but I've no time right now to experiment further.

I really do not know.  libvirt provided the parameters in the above.  I only
removed the networking parts to run it from the command line.  Try using all
of the options that was in the one I had.

-- 
 Microsoft has beaten Volkswagen's world record.  Volkswagen only created 22
 million bugs.



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

Bug#674919: Fails to start with -fsdev

[Wakko Warner]

I found the real problem.  Read the bottom where I said forget all that.
Everything above that was things that I had tried.

Michael Tokarev wrote:
 tags 674919 + moreinfo unreproducible
 thanks
 
 On 28.05.2012 20:00, Wakko Warner wrote:
  Package: qemu-kvm
  Version: 1.0+dfsg-11
  Severity: important
  
  I'm using libvirt 0.9.9-3+b2 to start VMs with kvm.  I just upgraded 
  qemu-kvm.
  I am no longer able to start VMs where I have defined a file system device. 
  My previous version was 1.0+dfsg-9 
  
  This is what I see:
  # LC_ALL=C 
  PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin 
  HOME=/root USER=root LOGNAME=root /usr/bin/kvm -S -M pc-0.14 -cpu core2duo 
  -enable-kvm -m 512 -smp 1,sockets=1,cores=1,threads=1 -name iscsiinit -uuid 
  128a255b-23db-a249-53ad-4226bc2f129e -nographic -nodefconfig -nodefaults 
  -chardev 
  socket,id=charmonitor,path=/var/lib/libvirt/qemu/iscsiinit.monitor,server,nowait
   -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc 
  -no-shutdown -drive 
  file=/vm/iscsiinit.qcow2,if=none,id=drive-virtio-disk0,format=qcow2 -device 
  virtio-blk-pci,bus=pci.0,addr=0x5,drive=drive-virtio-disk0,id=virtio-disk0 
  -fsdev local,security_model=mapped,id=fsdev-fs0,path=/var/local/kvm/kernel 
  -device 
  virtio-9p-pci,id=fs0,fsdev=fsdev-fs0,mount_tag=kernel,bus=pci.0,addr=0x3 
  -chardev pty,id=charserial0 -device 
  isa-serial,chardev=charserial0,id=serial0 -usb -device 
  virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x7
  char device redirected to /dev/pts/5
  
  (process:14897): GLib-CRITICAL **: g_thread_pool_new: assertion 
  `g_thread_supported ()' failed
  worker thread initialization failed
  #
  
  Removing the 
  -device 
  virtio-9p-pci,id=fs0,fsdev=fsdev-fs0,mount_tag=kernel,bus=pci.0,addr=0x3
  I get this:
 [works]
 
 I can't reproduce this.  It works here with 1.0+dfsg-11 just fine:
 
 $ kvm -fsdev local,security_model=mapped,id=fsdev-fs0,path=/var -device 
 virtio-9p-pci,id=fs0,fsdev=fsdev-fs0,mount_tag=kernel,bus=pci.0,addr=0x3 -M 
 pc-0.14 -nodefaults -vga std
 
 What I'm doing wrong?
 
 Maybe there are some other options which interfere,
 but I've no time right now to experiment further.

I took the source and compiled it.  I used
build/x86_64-softmmu/qemu-system-x86_64 from the 1.0+dfsg-11 source package
after it was compiled.  I made NO changes to anything.  I issued
debian/rules build to compile and stripped the binary mentioned above.

I could not reproduce this error with the one I compiled.  I extracted the
kvm binary from the 1.0+dfsg-11 amd64 package to a temporary location.  It
still gives me the same error.

It may be possible that I have an older library or something is different on
my system.

One difference I found is that I'm using gcc 4.6.1-8.  The kvm binary from
the -dbg package contains
GCC: (Debian 4.6.3-3) 4.6.3
GCC: (Debian 4.4.6-14) 4.4.6

Not sure which it was compiled with.  I cleaned and recompiled it with
gcc-4.4.6-6.  Still not able to reproduce.

I could not find the 1.0+dfsg-10 amd64 package (I did find the i386 package)
to check with that version.

One more test I did.  I ran your exact command line (only changing the path
to kvm)

# /junk/kvm/qemu-kvm-1.0-11-debian/usr/bin/kvm -fsdev 
local,security_model=mapped,id=fsdev-fs0,path=/var -device 
virtio-9p-pci,id=fs0,fsdev=fsdev-fs0,mount_tag=kernel,bus=pci.0,addr=0x3 -M 
pc-0.14 -nodefaults -vga std

(process:22949): GLib-CRITICAL **: g_thread_pool_new: assertion 
`g_thread_supported ()' failed
worker thread initialization failed
#

You know what, forget all of the above.  My libglib version is 2.28.6-1.  I
extracted the library from libglib2.0-0_2.32.3-1_amd64.deb and ran:
LD_LIBRARY_PATH=/junk/kvm/glib/lib/x86_64-linux-gnu 
/junk/kvm/qemu-kvm-1.0-11-debian/usr/bin/kvm -fsdev 
local,security_model=mapped,id=fsdev-fs0,path=/var -device 
virtio-9p-pci,id=fs0,fsdev=fsdev-fs0,mount_tag=kernel,bus=pci.0,addr=0x3 -M 
pc-0.14 -nodefaults -vga std
and it works fine.

The fix for this bug might be to just depend on a newer version of
libglib2.0-0.  I upgraded this package on my system and qemu-kvm and
everything is happy.

-- 
 Microsoft has beaten Volkswagen's world record.  Volkswagen only created 22
 million bugs.



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

Bug#644675: 1 sector difference between extX and reiserfs

[Wakko Warner]

Package: genisoimage
Version: 9:1.1.11-2
Severity: minor

I have volumes of deleted files archived to dvd.  I did a test between 2 of
my systems.  The first command is ran against my file set on an ext4
filesystem.  The second command is ran against my file set on a reiserfs on
an nfs mounted server.  That server is using reiserfs for it's volume.
Before one thinks this is an NFS problem, I did the test from the NFS server
and the results are the same and using the same version.  I saw this same
thing years ago when mkisofs was the around and I may have reported the same
bug back then.  It was never fixed from what I can tell.

/debian/isovol# genisoimage -r -print-size -no-pad -quiet vol877
2297889
/debian/isovol# genisoimage -r -print-size -no-pad -quiet 
/vegeta/debian/isovol/vol877
2297888
/debian/isovol# 

-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.39 (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash

Versions of packages genisoimage depends on:
ii  libbz2-1.0  1.0.5-6  high-quality block-sorting file co
ii  libc6   2.13-10  Embedded GNU C Library: Shared lib
ii  libmagic1   5.04-5+b1File type determination library us
ii  zlib1g  1:1.2.3.4.dfsg-3 compression library - runtime

genisoimage recommends no packages.

Versions of packages genisoimage suggests:
ii  wodim 9:1.1.11-1 command line CD/DVD writing tool

-- no debconf information



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

Bug#641820: Spams log with user not found

[Wakko Warner]

Arthur de Jong wrote:
 tags 641820 + pending
 thanks
 
 On Fri, 2011-09-16 at 09:47 -0400, Wakko Warner wrote:
  It would be nice if nslcd would not log warnings like this and other
  messages which would be reported by another service.
 
 Sorry for not responding sooner. It is probably best to reduce the
 loglevel of the user not found messages to debug so they won't show up
 by default.

In my logs, all auth.* logs go to 1 place and auth.debug doesn't go anywhere
else.

 I think it's a good idea to keep the authentication failed messages even
 though they the PAM stack also logs some information because it will
 generally include more (possibly useful) details.

This is why the patch I did has to use a switch to turn it off.  I agree
that some people may not want to turn those off so it's not default.  I've
been running my patched version on the 2 effected systems with no adverse
problems.

 Thanks for your patch.

NP.



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

Bug#643928: Add USB bridge to known IDs

[Wakko Warner]

Package: smartmontools
Version: 5.41+svn3365-1
Severity: wishlist

I have an external USB hard disk.  smartctl shows this:

# smartctl -l selftest usb device
smartctl 5.41 2011-06-09 r3365 [i686-linux-2.6.30] (local build)
Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net

/dev/mobile: Unknown USB bridge [0x0c0b:0xb001 (0x1110)]
Smartctl: please specify device type with the -d option.

Use smartctl -h to get a usage summary

#

This works fine with usbcypress.

# smartctl -d usbcypress usb device
smartctl 5.41 2011-06-09 r3365 [i686-linux-2.6.30] (local build)
Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net

=== START OF READ SMART DATA SECTION ===
SMART Self-test log structure revision number 1
Num  Test_DescriptionStatus  Remaining  LifeTime(hours)  
LBA_of_first_error
# 1  Extended offlineCompleted: read failure   00% 42097 
29152294
# 2  Extended offlineAborted by host   60% 42096 -
# 3  Extended captiveInterrupted (host reset)  90% 42096 -
# 4  Extended captiveInterrupted (host reset)  90% 42094 -
# 5  Short offline   Completed without error   00% 42094 -

#



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

Bug#641820: [PATCH] Spams log with user not found

[Wakko Warner]

Here is the patch that will add a --nowarn option to nslcd.  This is not
default so it would not break existing installations.

- BEGIN -
diff -ru nss-pam-ldapd-0.8.4/nslcd/nslcd.c nss-pam-ldapd-0.8.4.1/nslcd/nslcd.c
--- nss-pam-ldapd-0.8.4/nslcd/nslcd.c   2011-04-18 17:29:09.0 -0400
+++ nss-pam-ldapd-0.8.4.1/nslcd/nslcd.c 2011-09-16 20:18:43.0 -0400
@@ -79,6 +79,9 @@
 /* the exit flag to indicate that a signal was received */
 static volatile int nslcd_exitsignal=0;
 
+/* useless warnings flag (defined in pam.c) */
+extern int useless_warnings;
+
 /* the server socket used for communication */
 static int nslcd_serversocket=-1;
 
@@ -120,6 +123,7 @@
   fprintf(fp,  -d, --debugdon't fork and print debugging to 
stderr\n);
   fprintf(fp,  --help display this help and exit\n);
   fprintf(fp,  --version  output version information and exit\n);
+  fprintf(fp,  --nowarn   disable useless warnings\n);
   fprintf(fp,\n
  Report bugs to %s.\n,PACKAGE_BUGREPORT);
 }
@@ -131,9 +135,10 @@
   { debug,   no_argument,   NULL, 'd' },
   { help,no_argument,   NULL, 'h' },
   { version, no_argument,   NULL, 'V' },
+  { nowarn,  no_argument,   NULL, 'W' },
   { NULL, 0, NULL, 0 }
 };
-#define NSLCD_OPTIONSTRING cdhV
+#define NSLCD_OPTIONSTRING cdhVW
 
 /* parse command line options and save settings in struct  */
 static void parse_cmdline(int argc,char *argv[])
@@ -156,6 +161,9 @@
 case 'V': /* --version  output version information and exit */
   display_version(stdout);
   exit(EXIT_SUCCESS);
+case 'W': /* --nowarn   disable useless warnings */
+  useless_warnings=0;
+  break;
 case ':': /* missing required parameter */
 case '?': /* unknown option character or extraneous parameter */
 default:
diff -ru nss-pam-ldapd-0.8.4/nslcd/pam.c nss-pam-ldapd-0.8.4.1/nslcd/pam.c
--- nss-pam-ldapd-0.8.4/nslcd/pam.c 2011-06-10 04:49:11.0 -0400
+++ nss-pam-ldapd-0.8.4.1/nslcd/pam.c   2011-09-16 20:18:31.0 -0400
@@ -39,6 +39,16 @@
 #include common/dict.h
 #include common/expr.h
 
+/* useless warnings flag
+ * this disables the following warnings when set to 0
+ *
+ * lookup of user failed
+ * user: not found
+ *
+ * defined here because the test_* don't link with nslcd.o
+ */
+int useless_warnings=1;
+
 /* set up a connection and try to bind with the specified DN and password,
returns an LDAP result code */
 static int try_bind(const char *userdn,const char *password)
@@ -62,7 +72,8 @@
   {
 if (rc==LDAP_SUCCESS)
   rc=LDAP_LOCAL_ERROR;
-log_log(LOG_WARNING,lookup of %s failed: %s,userdn,ldap_err2string(rc));
+if (useless_warnings)
+  log_log(LOG_WARNING,lookup of %s failed: 
%s,userdn,ldap_err2string(rc));
   }
   else
   {
@@ -71,7 +82,8 @@
 {
   if (rc==LDAP_SUCCESS)
 rc=LDAP_NO_RESULTS_RETURNED;
-  log_log(LOG_WARNING,lookup of %s failed: 
%s,userdn,ldap_err2string(rc));
+  if (useless_warnings)
+log_log(LOG_WARNING,lookup of %s failed: 
%s,userdn,ldap_err2string(rc));
 }
   }
   /* close the session */
@@ -100,7 +112,8 @@
   {
 if (rc==LDAP_SUCCESS)
   rc=LDAP_NO_SUCH_OBJECT;
-log_log(LOG_WARNING,\%s\: user not found: 
%s,username,ldap_err2string(rc));
+if (useless_warnings)
+  log_log(LOG_WARNING,\%s\: user not found: 
%s,username,ldap_err2string(rc));
 *rcp=rc;
   }
   return entry;
- END -



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

Bug#641820: Spams log with user not found

[Wakko Warner]

Package: nslcd
Version: 0.8.4
Severity: wishlist

I'm continually see messages like the following:
2011-09-16 06:25:02 vegeta nslcd[29120]: [dd36d7] authz=nobody nobody: 
user not found: No such object
2011-09-16 09:40:02 ani nslcd[20514]: [21915c] authz=munin munin: user 
not found: No such object

In this case, this happens every 5 minutes.  I am not sure if this is caused
by the nss side or the pam side.  I do have minimum_uid=0 in the pam
configuration.  I do this because I want my root password to be taken from
ldap.  Hoever, nobody is  the default uid of 1000.

It would be nice if nslcd would not log warnings like this and other
messages which would be reported by another service (IE failed password as
in this log:
2011-09-15 22:19:30 vegeta nslcd[29120]: [068dd7] authc=user lookup of 
uid=user,ou=users,dc=x,dc=x failed: Invalid credentials
)

A possible solution would be to add a switch to disable these types of
warnings.  I could provide a patch when I get time to make the
modifications.

-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.30 (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/bash

Versions of packages nslcd depends on:
ii  adduser3.100 Add and remove users and groups
ii  debconf [debconf-2.0]  1.5.41Debian configuration management sy
ii  libc6  2.13-10   Embedded GNU C Library: Shared lib
ii  libgssapi-krb5-2   1.9+dfsg-1+b1 MIT Kerberos runtime libraries - k
ii  libldap-2.4-2  2.4.25-3  OpenLDAP libraries

Versions of packages nslcd recommends:
ii  host  2331-9 utility for querying DNS servers
ii  ldap-utils2.2.26-5   OpenLDAP utilities
ii  libnss-ldapd [libnss-ldap]0.8.4  NSS module for using LDAP as a nam
ii  libpam-ldapd [libpam-ldap]0.8.4  PAM module for using LDAP as an au
pn  nscd  none (no description available)

-- debconf information excluded



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

Bug#641165: fails to configure if it cannot start slapd

[Wakko Warner]

Package: slapd
Version: 2.4.25-3
Severity: normal

I install slapd and answered no to the initial configuration and the package
failes to configure with the following:

  Omitting slapd configuration as requested.
No configuration file was found for slapd at /etc/ldap/slapd.conf. (warning).
invoke-rc.d: initscript slapd, action start failed.
dpkg: error processing slapd (--configure):
 subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
 slapd

-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.33
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages slapd depends on:
ii  adduser   3.99   Add and remove users and groups
ii  coreutils 5.97-5.2   The GNU core utilities
ii  debconf [debconf-2.0] 1.5.19 Debian configuration management sy
ii  libc6 2.13-20Embedded GNU C Library: Shared lib
ii  libdb4.8  4.8.30-9   Berkeley v4.8 Database Libraries [
ii  libdb5.1  5.1.25-11  Berkeley v5.1 Database Libraries [
ii  libgcrypt11   1.4.6-5LGPL Crypto library - runtime libr
ii  libgnutls26   2.12.10-1  GNU TLS library - runtime library
ii  libldap-2.4-2 2.4.25-3   OpenLDAP libraries
ii  libltdl7  2.4-4  A system independent dlopen wrappe
ii  libperl5.12   5.12.4-4   shared Perl library
ii  libsasl2-22.1.22.dfsg1-8 Authentication abstraction library
ii  libslp1   1.0.11-7   OpenSLP libraries
ii  libwrap0  7.6.q-16   Wietse Venema's TCP wrappers libra
ii  lsb-base  3.2-20 Linux Standard Base 3.2 init scrip
ii  multiarch-support 2.13-20Transitional package to ensure mul
ii  perl [libmime-base64-perl 5.12.4-4   Larry Wall's Practical Extraction 
ii  psmisc21.5-1 Utilities that use the proc filesy
ii  unixodbc  2.2.14p2-3 Basic ODBC tools

Versions of packages slapd recommends:
pn  libsasl2-modules  none (no description available)

-- debconf information:
  shared/organization:
  slapd/upgrade_slapcat_failure:
  slapd/backend: HDB
  slapd/allow_ldap_v2: false
* slapd/no_configuration: true
  slapd/move_old_database: true
  slapd/dump_database_destdir: /var/backups/slapd-VERSION
  slapd/domain:
  slapd/password_mismatch:
  slapd/invalid_config: true
  slapd/dump_database: when needed
  slapd/purge_database: false



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

Bug#640360: output information like it would appear in a zone file.

[Wakko Warner]

Package: bind9-host
Version: 1:9.7.3.dfsg-1+b1
Severity: wishlist

It would be nice if the host program could output information the way it would
be in the zone file.

IE:
# host example.com
example.com A   1.2.3.4
#

instead of
# host example.com
example.com has address 1.2.3.4
#

the option -v can do it, but has so much extra stuff it's harder to read.



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

Bug#639506: Use of uninitialized value when issuing ls

[Wakko Warner]

Package: shelldap
Version: 0.4-3
Severity: minor

Shows warnings when issuing ls

# shelldap --server ldapi:/// --binddn cn=admin,cn=config --basedn cn=config
Bind password: 
Would you like to cache your connection information? [Y/n]: n
~  ls
Use of uninitialized value in string eq at /usr/bin/shelldap line 1470, STDIN 
line 2.
cn=module{0}
Use of uninitialized value in string eq at /usr/bin/shelldap line 1470, STDIN 
line 2.
cn=schema
Use of uninitialized value in string eq at /usr/bin/shelldap line 1470, STDIN 
line 2.
olcBackend={0}hdb
Use of uninitialized value in string eq at /usr/bin/shelldap line 1470, STDIN 
line 2.
olcDatabase={-1}frontend
Use of uninitialized value in string eq at /usr/bin/shelldap line 1470, STDIN 
line 2.
olcDatabase={0}config
Use of uninitialized value in string eq at /usr/bin/shelldap line 1470, STDIN 
line 2.
olcDatabase={1}hdb
~ 
#



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

Bug#634117: Fails when console is not a virtual terminal

[Wakko Warner]

Package: uswsusp
Version: 1.0+20110509-1
Severity: wishlist

I have a VM running with no vga under KVM.  The only local terminal is the
serial console.  When trying to use s2disk, I see:
s2disk: No local tty. Remember to specify local console after the remote. 
Reason: Invalid argument

It would be nice if s2disk would work w/o needing a local console

strace shows this:

stat(/dev/snapshot, {st_mode=S_IFCHR|0600, st_rdev=makedev(10, 231), ...}) = 0
open(/dev/snapshot, O_RDONLY) = 4
ioctl(4, SNAPSHOT_SET_SWAP_AREA, 0x7fff45212de0) = 0
open(/dev/console, O_RDONLY)  = 5
ioctl(5, KDGKBTYPE, 0x7fff45212b5f) = -1 EINVAL (Invalid argument)
close(5)= 0
write(2, s2disk: No local tty. Remember t..., 99s2disk: No local tty. 
Remember to specify local console after the remote. Reason: Invalid argument
) = 99
close(4)= 0
close(3)= 0
chdir(/)  = 0
umount(/proc/7119, 0) = 0
munmap(0x7fd1b578e000, 425984)  = 0
exit_group(22)  = ?

-- System Information:
Removed, reportbug is not installed on system with problem.  I believe that
this information is irrelevent to the wishlist.



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

Bug#633368: ssh hostbased authentication fails when ECDSA keys are available

[Wakko Warner]

Package: openssh-client
Version: 1:5.8p1-4
Severity: normal

If I have hostbased authentication enabled and attempt to ssh to another
system, hostbased authentication always fails and falls back to password
authentication.

If I remove /etc/ssh/ssh_host_ecdsa_key* and try again, everything works.

I found this bug report from Feb 2011:
http://lists.mindrot.org/pipermail/openssh-bugs/2011-February/010105.html

Apparently, this is fixed in 5.9 which debian does not appear to have yet.

-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.39 (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash

Versions of packages openssh-client depends on:
ii  adduser  3.112+nmu2  add and remove users and groups
ii  debconf [debconf-2.0 1.5.39  Debian configuration management sy
ii  dpkg 1.16.0.3Debian package management system
ii  libc62.13-4  Embedded GNU C Library: Shared lib
ii  libedit2 2.11-20080614-2 BSD editline and history libraries
ii  libgssapi-krb5-2 1.9.1+dfsg-1+b1 MIT Kerberos runtime libraries - k
ii  libselinux1  2.0.98-1+b1 SELinux runtime shared libraries
ii  libssl1.0.0  1.0.0d-2SSL shared libraries
ii  passwd   1:4.1.4.2+svn3283-3 change and administer password and
ii  zlib1g   1:1.2.3.4.dfsg-3compression library - runtime

Versions of packages openssh-client recommends:
ii  openssh-blacklist 0.4.1  list of default blacklisted OpenSS
ii  xauth 1:1.0.5-1  X authentication utility

-- Configuration Files:
/etc/ssh/ssh_config changed [not included]

-- no debconf information



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

Bug#631869: SEGV with bad fstab

[Wakko Warner]

Package: mount
Version: 2.19.1-2
Severity: normal

I had this in fstab:
/dev/vda/   ext4defaults 1 1
sys /syssysfs

And mount crashes when the system boots.  The command that was ran (when I
issued sh -x /etc/init.d/mountall.sh start) is
mount -a -t nonfs,nfs4,smbfs,cifs,ncp,ncpfs,coda,ocfs2,gfs,gfs2 -O no_netdev

I understand that the fstab was my mistake, however mount shouldn't have
segfaulted.

-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.39 (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash

Versions of packages mount depends on:
ii  libblkid12.17.2-9.1  block device id library
ii  libc62.13-4  Embedded GNU C Library: Shared lib
ii  libmount12.19.1-2block device id library
ii  libselinux1  2.0.98-1+b1 SELinux runtime shared libraries
ii  libsepol12.0.42-1SELinux library for manipulating b

mount recommends no packages.

Versions of packages mount suggests:
ii  nfs-common1:1.2.3-3  NFS support files common to client

-- no debconf information



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

Bug#576009: multigraph plugins don't show up when using telnet

[Wakko Warner]

Package: munin-node
Version: 1.4.4-1
Severity: minor

This shows the bug:

# telnet localhost 4949
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
# munin node at roshi
cap multigraph
cap multigraph
list switch
snmp_switch_uptime
quit
Connection closed by foreign host.
# nc localhost 4949
# munin node at roshi
cap multigraph
list switch
cap multigraph
snmp_switch_uptime snmp_switch_if_multi
quit
# 

Doing fetch/config on a multigraph plugin when using telnet works after
issueing cap multigraph.

-- System Information:
Debian Release: 3.1
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.33
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages munin-node depends on:
ii  adduser 3.99 Add and remove users and groups
ii  gawk1:3.1.5.dfsg-4.1 GNU awk, a pattern scanning and pr
ii  libnet-server-perl  0.94-1   An extensible, general perl server
ii  lsb-base3.2-20   Linux Standard Base 3.2 init scrip
ii  munin-common1.4.4-1  network-wide graphing framework (c
ii  perl5.10.0-19Larry Wall's Practical Extraction 
ii  procps  1:3.2.7-6/proc file system utilities

Versions of packages munin-node recommends:
ii  libnet-snmp-perl  5.2.0-1Script SNMP connections

-- no debconf information



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

Bug#575180: uptime: Don't scale.

[Wakko Warner]

Package: munin-node
Version: 1.4.3-2
Severity: wishlist
Tags: patch

Systems with uptimes over 1000 show up as 1.0k or larger.  This makes it
difficult to view the actual uptime.  I have such a system.  The fix is
to add 1 line according to the following diff.

--- uptime  2010-03-01 12:48:54.0 -0500
+++ uptime  2010-03-01 12:48:54.0 -0500
@@ -37,6 +37,7 @@
 
echo 'graph_title Uptime'
echo 'graph_args --base 1000 -l 0 '
+   echo 'graph_scale no'
echo 'graph_vlabel uptime in days'
echo 'graph_category system'
echo 'uptime.label uptime'

This was a cut'n'paste diff, hopefully it will work.

-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.30 (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/bash

Versions of packages munin-node depends on:
ii  adduser3.100 Add and remove users and groups
ii  gawk   1:3.1.4-2.0.1 GNU awk, a pattern scanning and pr
ii  libnet-server-perl 0.94-1An extensible, general perl server
ii  lsb-base   3.2-20Linux Standard Base 3.2 init scrip
ii  munin-common   1.4.3-2   network-wide graphing framework (c
ii  perl   5.10.1-9  Larry Wall's Practical Extraction 
ii  procps 1:3.2.7-3 /proc file system utilities

Versions of packages munin-node recommends:
ii  libnet-snmp-perl  5.2.0-1Script SNMP connections

-- no debconf information



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

Bug#569491: mail_eximstats graph connections and disconnections

[Wakko Warner]

Tom Feiner wrote:
 Thanks for the bug report. As this is a munin issue rather than a debian
 issue, this should be handled upstream. I've forwarded this bug to the
 upstream bug tracker.
 
 If you get a chance to write the patch, please include it there, so it can be
 incorporated in a future munin release.

I've been looking into this in my spare time.  I don't believe it would be a
good idea to incorporate this into exim_mailstats.  I have found 10 things
that exim writes that could be monitored.  These items would clutter the
current graph and IMO make it unreadable.

I took exim_mailstats as a base and made exim_connections.  The down side of
this is that it parses the exim log 2 times (that is, if one uses both
plugins).  An exim_log_multi would be better suited for this task.

This is the code that gathers the data.  I'm not aware of any other
connection/disconnection reasons than these.

/ refused: too many connections from that IP address$/ and $toomany++, next;
/ connection count / and $connections++, next;
/ no (?:host name|IP address) found for / and $nordns++, next;
/ lost(?: |$)/ and $lost++, next;
/ command timeout / and $timeout++, next;
/ \(message abandoned\) / and $abandon++, next;
/ closed after SIG[A-Z]{1,10}$/ and $signal++, next;
/ unexpected disconnection / and $unexpected++, next;
if (/ closed by /)
{
 / DROP in ACL$/ and $dropacl++, next;
 / QUIT$/ and $quit++, next;
}

I should point out that with some spam software, the toomany will jump pretty
high and could make the other information unreadable on the graph.  On one
server, I see toomany max at almost 70 where as all the others only top 5.

-- 
 Lab tests show that use of micro$oft causes cancer in lab animals
 Got Gas???



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

Bug#569621: exim_mailstats doesn't count Completed properly

[Wakko Warner]

Package: munin
Version: 1.4.3-2
Severity: normal
Tags: patch

# grep  Completed  /var/log/exim4/mainlog|wc -l
0
# grep  Completed$ /var/log/exim4/mainlog|wc -l
4835
# 

This patch changes the line that counts the completed lines.

-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.30 (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/bash

Versions of packages munin depends on:
ii  adduser   3.100  Add and remove users and groups
ii  cron  3.0pl1-87  management of regular background p
pn  libdigest-md5-perlnone (no description available)
ii  libhtml-template-perl 2.9-1  HTML::Template : A module for usin
ii  liblog-log4perl-perl  1.26-1 A Perl port of the widely popular 
ii  librrds-perl  1.3.8-1Time-series data storage and displ
pn  libstorable-perl  none (no description available)
ii  munin-common  1.4.3-2network-wide graphing framework (c
ii  perl [libtime-hires-perl] 5.10.1-9   Larry Wall's Practical Extraction 
ii  perl-modules  5.10.1-9   Core Perl modules
ii  rrdtool   1.2.27-1   Time-series data storage and displ
ii  ttf-dejavu2.30-2 Metapackage to pull in ttf-dejavu-

Versions of packages munin recommends:
pn  libdate-manip-perlnone (no description available)
ii  munin-node1.4.3-2network-wide graphing framework (n

-- no debconf information
--- exim_mailstats.orig 2010-02-11 17:44:11.0 -0500
+++ exim_mailstats  2010-02-12 16:34:36.0 -0500
@@ -117,7 +117,7 @@
 if (/ = /) {
 $received++;
 }
-elsif (/ Completed /) {
+elsif (/ Completed$/) {
 $completed++;
 }
 elsif (/ rejected /) {

Bug#569491: mail_eximstats graph connections and disconnections

[Wakko Warner]

Package: munin-node
Version: 1.4.3-2
Severity: wishlist

It would be nice if mail_eximstats could also output the number of connects
and disconnects (also seperated by how, ie QUIT, lost, DROP in ACL, etc.)

I may post a patch for this when I get a chance.



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

Bug#569496: mail_eximstats fails if there is no current state

[Wakko Warner]

Package: munin-node
Version: 1.4.3-2
Severity: normal

It may be easier to demonstrate:

# munin-run mail_eximstats
received.value U
completed.value U
rejected.value U
# cat /var/lib/munin/plugin-state/exim_mailstats-
%MUNIN-STATE1.0
2351803
U
U
U
# 
wait for mail to come in
# munin-run mail_eximstats
received.value AA
completed.value U
rejected.value U
# cat /var/lib/munin/plugin-state/exim_mailstats-
%MUNIN-STATE1.0
2355576
AA
U
U
#

Would it be better to do this?
=== BEGIN ===
--- exim_mailstats.orig 2010-02-11 17:44:11.0 -0500
+++ exim_mailstats  2010-02-11 17:44:26.0 -0500
@@ -218,7 +218,7 @@
 # file up to now, but remember how large it is now, and next
 # time read from there.
 $pos = (stat $logfile)[7];  # File size
-$received = $completed = $rejected = 'U';
+$received = $completed = $rejected = '0';
 }
 else {
 $pos = parseEximfile($logfile, $pos);
=== END ===

Or even change U to 0 in parseEximfile?

-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.30 (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/bash

Versions of packages munin-node depends on:
ii  adduser3.100 Add and remove users and groups
ii  gawk   1:3.1.4-2.0.1 GNU awk, a pattern scanning and pr
ii  libnet-server-perl 0.94-1An extensible, general perl server
ii  lsb-base   3.2-20Linux Standard Base 3.2 init scrip
ii  munin-common   1.4.3-2   network-wide graphing framework (c
ii  perl   5.10.1-9  Larry Wall's Practical Extraction 
ii  procps 1:3.2.7-3 /proc file system utilities

Versions of packages munin-node recommends:
ii  libnet-snmp-perl  5.2.0-1Script SNMP connections

-- no debconf information



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

Bug#568938: Some statements in munin.conf no longer work.

[Wakko Warner]

Package: munin
Version: 1.4.3-2
Severity: normal

I upgraded munin from 1.2.5-2.  I had this in my config:
[narf]
address narf
use_node_name yes
if_ppp0.up.max 15000
if_ppp0.down.max 15000

This causes the ppp0 graph to not jump every time the connection is reset.
1.2.5-2's /var/lib/munin/datafile looks like this:
# grep narf.*ppp.*max /archive/ani-20100101/var/lib/munin/datafile
narf;narf:if_ppp0.up.max 15000
narf;narf:if_ppp0.down.max 15000
# 

In 1.4.3-2:
# grep narf.*ppp.*max /var/lib/munin/datafile
narf;narf:if_ppp0.down.max U
narf;narf:if_ppp0.up.max U
# 

-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.30 (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/bash

Versions of packages munin depends on:
ii  adduser   3.100  Add and remove users and groups
ii  cron  3.0pl1-87  management of regular background p
ii  libhtml-template-perl 2.9-1  HTML::Template : A module for usin
ii  liblog-log4perl-perl  1.26-1 A Perl port of the widely popular 
ii  librrds-perl  1.3.8-1Time-series data storage and displ
ii  munin-common  1.4.3-2network-wide graphing framework (c
ii  perl [libtime-hires-perl] 5.10.1-9   Larry Wall's Practical Extraction 
ii  perl-modules  5.10.1-9   Core Perl modules
ii  rrdtool   1.2.27-1   Time-series data storage and displ
ii  ttf-dejavu2.30-2 Metapackage to pull in ttf-dejavu-

Versions of packages munin recommends:
ii  munin-node1.2.5-1network-wide graphing framework (n

-- no debconf information



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

Bug#564597: blkid doesn't identify partitions

[Wakko Warner]

Package: util-linux
Version: 2.16.2-0
Severity: normal

This may belong to libblkid1 instead.

# blkid /dev/sda
/dev/sda: UUID=923098ea-b196-41f1-af4f-a21628bcd144 TYPE=ext2 
# blkid /dev/sda1
/dev/sda1: UUID=21c66652-1ce3-483a-8269-e44022f447e9 TYPE=ext3 
# blkid /dev/sda2
/dev/sda2: UUID=6b8b4567-327b-23c6-643c-986966334873 TYPE=linux_raid_member 
# blkid /dev/sdm 
# blkid /dev/sdm1
/dev/sdm1: LABEL= UUID=4268-5265 TYPE=vfat 
# blkid /dev/sdn 
/dev/sdn: UUID=0c1c2edf-4c3f-4d3c-b2c0-93440806d237 TYPE=ext2 
# blkid /dev/sdn1
/dev/sdn1: UUID=0c1c2edf-4c3f-4d3c-b2c0-93440806d237 TYPE=ext2 
# 

All of these have ms-dos style partition tables.  The TYPE is correct for all
partitions.  sdn is special.  sdn is ext2 and msdos as well as sdn1.  The
partition table was there to satisfy grub legacy and sdn1 starts at sect 0.
sdm shows nothing.

Nothing in the man pages state that the tool is limited to filesystems, LVM,
and raid.

-- System Information:
Debian Release: 3.1
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.27.5
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages util-linux depends on:
ii  dpkg   1.14.22   Debian package management system
ii  initscripts2.86.ds1-61   Scripts for initializing and shutt
ii  install-info   4.13a.dfsg.1-5Manage installed documentation in 
ii  libblkid1  2.16.2-0  block device id library
ii  libc6  2.9-18GNU C Library: Shared libraries
ii  libncurses55.6+20080203-1Shared libraries for terminal hand
ii  libselinux12.0.82-1  SELinux shared libraries
ii  libuuid1   2.16.2-0  Universally Unique ID library
ii  lsb-base   3.2-20Linux Standard Base 3.2 init scrip
ii  tzdata 2007k-1   time zone and daylight-saving time
ii  zlib1g 1:1.2.3.3.dfsg-12 compression library - runtime

util-linux recommends no packages.

-- no debconf information



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

Bug#524134: Compressed database files.

[Wakko Warner]

Package: mlocate
Version: 0.21.1-2
Severity: wishlist

Since mlocate writes a new database file each time it updates, it would be
nice if there was a compression option.

I would agree that most systems won't have a large database; however I am
testing the feasability on an archive filesystem with a large amount of
files.

For the curioush ere's an ls -l of the database files while updatedb is
running:
-rw-r--r-- 1 root root 1179729353 Apr 14 21:36 /archive/archive.db
-rw--- 1 root root  948277248 Apr 14 22:06 /archive/archive.db.Mg7tBQ

That's about 55 million files.

-- System Information:
Debian Release: 3.1
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.27.5
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages mlocate depends on:
ii  adduser   3.99   Add and remove users and groups
ii  libc6 2.7-5  GNU C Library: Shared libraries

mlocate recommends no packages.

-- no debconf information



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

Bug#475078: easy workaround: needs manual configuration

[Wakko Warner]

Holger Levsen wrote:
 tags 475078 +upstream
 thanks
 
 Hi Wakko,
 
 Unfortunatly at the moment you have to configure the lower the default speed 
 of this interface manually, which can easily be done in munin.conf:
 
 Something like this should work: (untested!)
 
 [localhost]
 address 127.0.0.1
 use_node_name yes
 if_ppp0.graph_args --base 100 -Y
 
 I agree that it would be nice if the plugin would determine the interface 
 speed itself.

I already corrected the problem, but in a different way.  I just set the max
speed I ever expected the device to show.

-- 
 Lab tests show that use of micro$oft causes cancer in lab animals
 Got Gas???



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

Bug#507102: Option to call action script on startup if no link.

[Wakko Warner]

Package: ifplugd
Version: 0.28-14
Severity: wishlist

I configured my system to use a wired/wireless combination.  Basically if my
wired has link, it UPs that interface and downs the wireless interface and
vice versa if no link.  Unfortunately, ifplugd does not call the script on
initial run if there's no link.



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#504678: add -r to make resulting devices read/only

[Wakko Warner]

Package: kpartx
Version: 0.4.8-13
Severity: wishlist
Tags: patch

I'd like to have the ability to create targets in which are read-only to
keep from accidentally modifying the newly created device.  In some cases,
mounting with -o ro still modifies the device (in the case of ext3
filesystems).  I created a small patch that will do this.  I have tested it
only to the point that using -a with or without -r produces the desired
effects.

-- System Information:
Debian Release: 3.1
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.24.5
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages kpartx depends on:
ii  dmsetup  2:1.02.27-4 The Linux Kernel Device Mapper use
ii  libc62.7-5   GNU C Library: Shared libraries
ii  libdevmapper1.02.1   2:1.02.27-4 The Linux Kernel Device Mapper use

kpartx recommends no packages.

-- no debconf information
diff -ruN multipath-tools-0.4.8-orig/kpartx/devmapper.c multipath-tools-0.4.8/kpartx/devmapper.c
--- multipath-tools-0.4.8-orig/kpartx/devmapper.c	2007-08-02 17:05:37.0 -0400
+++ multipath-tools-0.4.8/kpartx/devmapper.c	2008-11-05 21:32:51.0 -0500
@@ -72,7 +72,7 @@
 
 extern int
 dm_addmap (int task, const char *name, const char *target,
-	   const char *params, unsigned long size, const char *uuid, int part) {
+	   const char *params, unsigned long size, int ro, const char *uuid, int part) {
 	int r = 0;
 	struct dm_task *dmt;
 	char *prefixed_uuid;
@@ -86,6 +86,9 @@
 	if (!dm_task_add_target (dmt, 0, size, target, params))
 		goto addout;
 
+	if (ro  !dm_task_set_ro (dmt))
+		goto addout;
+
 	if (task == DM_DEVICE_CREATE  uuid) {
 		prefixed_uuid = malloc(MAX_PREFIX_LEN + strlen(uuid) + 1);
 		if (!prefixed_uuid) {
diff -ruN multipath-tools-0.4.8-orig/kpartx/devmapper.h multipath-tools-0.4.8/kpartx/devmapper.h
--- multipath-tools-0.4.8-orig/kpartx/devmapper.h	2007-08-02 17:05:37.0 -0400
+++ multipath-tools-0.4.8/kpartx/devmapper.h	2008-11-05 21:36:05.0 -0500
@@ -1,7 +1,7 @@
 int dm_prereq (char *, int, int, int);
 int dm_simplecmd (int, const char *);
 int dm_addmap (int, const char *, const char *, const char *, unsigned long,
-	   char *, int);
+	   int, char *, int);
 int dm_map_present (char *);
 char * dm_mapname(int major, int minor);
 dev_t dm_get_first_dep(char *devname);
diff -ruN multipath-tools-0.4.8-orig/kpartx/kpartx.c multipath-tools-0.4.8/kpartx/kpartx.c
--- multipath-tools-0.4.8-orig/kpartx/kpartx.c	2007-08-02 17:05:37.0 -0400
+++ multipath-tools-0.4.8/kpartx/kpartx.c	2008-11-05 21:38:59.0 -0500
@@ -82,7 +82,7 @@
 	addpts(sun, read_sun_pt);
 }
 
-static char short_opts[] = ladgvnp:t:;
+static char short_opts[] = rladgvnp:t:;
 
 /* Used in gpt.c */
 int force_gpt=0;
@@ -91,6 +91,7 @@
 usage(void) {
 	printf(usage : kpartx [-a|-d|-l] [-v] wholedisk\n);
 	printf(\t-a add partition devmappings\n);
+	printf(\t-r devmappings will be readonly\n);
 	printf(\t-d del partition devmappings\n);
 	printf(\t-l list partitions devmappings that would be added by -a\n);
 	printf(\t-p set device name-partition number delimiter\n);
@@ -183,7 +184,7 @@
 
 int
 main(int argc, char **argv){
-	int fd, i, j, m, n, op, off, arg, c, d;
+	int fd, i, j, m, n, op, off, arg, c, d, ro=0;
 	struct slice all;
 	struct pt *ptp;
 	enum action what = LIST;
@@ -230,6 +231,9 @@
 	}
 
 	while ((arg = getopt(argc, argv, short_opts)) != EOF) switch(arg) {
+		case 'r':
+			ro=1;
+			break;
 		case 'g':
 			force_gpt=1;
 			break;
@@ -458,7 +462,7 @@
 	DM_DEVICE_RELOAD : DM_DEVICE_CREATE);
 
 dm_addmap(op, partname, DM_TARGET, params,
-	  slices[j].size, uuid, j+1);
+	  slices[j].size, ro, uuid, j+1);
 
 if (op == DM_DEVICE_RELOAD)
 	dm_simplecmd(DM_DEVICE_RESUME,
@@ -514,7 +518,7 @@
 	  DM_DEVICE_RELOAD : DM_DEVICE_CREATE);
 
 	dm_addmap(op, partname, DM_TARGET, params,
-		  slices[j].size, uuid, j+1);
+		  slices[j].size, ro, uuid, j+1);
 
 	if (op == DM_DEVICE_RELOAD)
 		dm_simplecmd(DM_DEVICE_RESUME,

Bug#481117: openvpn: Please depend on openssl = 0.9.8g-9

[Wakko Warner]

Please do not do this.  There's really no reason to have openssl installed
when installing openvpn for every install.  Would it not be better for
libssl0.9.8 to conflict with older versions?

-- 
 Lab tests show that use of micro$oft causes cancer in lab animals
 Got Gas???



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#483601: aboot: Unable to boot kernels = 2.6.23

[Wakko Warner]

Steve Langasek wrote:
 On Fri, May 30, 2008 at 06:48:56PM -0400, Wakko Warner wrote:
  Steve Langasek wrote:
   On Fri, May 30, 2008 at 06:58:12AM -0400, Wakko Warner wrote:
  It also happened with linux-image-2.6.24-1-alpha-generic_2.6.24-7_alpha.deb
  (26701190 May 10 16:47 MD5:66a24de6495e9fbc601077a1846a6aa2)
  Was this cross compiled too?
 
 No.  If it's happening for you with the kernel in the archive, then you
 don't have the right aboot boot block installed to your disk at all; the
 current sid version of aboot *does* correctly handle the ELF header on this
 kernel.
 
 Do you also have the current version of aboot-base installed (or, did you
 have it installed at the time you ran swriteboot)?  That's the binary
 package that contains the boot block.

I don't understand it but for some reason, it's now working (with 2 program
headers)  I just built another kernel (2.6.25 gave me some problems with the
tulip card) and I didn't have a problem booting it.

-- 
 Lab tests show that use of micro$oft causes cancer in lab animals
 Got Gas???



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#480842: rwhod segfaults upon startup when specifying interface to use

[Wakko Warner]

I'm willing to bet the following change is causing the problems.  Shouldn't
there be a : after i in the getopt()?

--- netkit-rwho-0.17-8/rwhod/rwhod.c2008-05-31 22:10:27.0 -0400
+++ netkit-rwho-0.17-10/rwhod/rwhod.c   2008-05-31 22:09:14.0 -0400
@@ -192,7 +192,7 @@
exit(1);
}
 
-   while ((opt = getopt(argc, argv, bpai:fu:)) != EOF) {
+   while ((opt = getopt(argc, argv, bpaih?:fu:)) != EOF) {
switch (opt) {
  case 'b':
  use_broadcast = 1;

-- 
 Lab tests show that use of micro$oft causes cancer in lab animals
 Got Gas???



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#483601: aboot: Unable to boot kernels = 2.6.23

[Wakko Warner]

Steve Langasek wrote:
 On Thu, May 29, 2008 at 04:11:29PM -0400, [EMAIL PROTECTED] wrote:
  Package: aboot
  Version: 1.0~pre20040408-2
  Severity: important
 
  I built a kernel for my alpha and noticed it wouldn't boot (It was
  cross-compiled, but I doubt that makes a difference)
 
  Using readelf -h, my kernel has 2 program headers.  Aboot will not boot
  these files.
 
  I also have linux-image-2.6.24-1-alpha-generic_2.6.24-7_alpha.deb installed
  on my alpha.  This kernel also does not boot.
 
  There was apparently a change between kernel v2.6.22 and v2.6.23 in the
  vmlinux.lds.S that specifies 2 program headers.  I modified my ld script to
  specify 1 header.  The system did boot with this modification.
 
  Either aboot needs to cope with this or the kernel should be fixed.
 
 What needs to happen is that you need to install the boot block from aboot
 1.0~pre20040408-2 to your hard drive.  You appear to have upgraded from
 etch, and bootloader packages don't automatically install new boot blocks
 when they're upgraded.

This was a fresh install of sid.  I ran swriteboot after I installed this
version of aboot.

-- 
 Lab tests show that use of micro$oft causes cancer in lab animals
 Got Gas???



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#483601: aboot: Unable to boot kernels = 2.6.23

[Wakko Warner]

Steve Langasek wrote:
 On Fri, May 30, 2008 at 06:58:12AM -0400, Wakko Warner wrote:
  Steve Langasek wrote:
I built a kernel for my alpha and noticed it wouldn't boot (It was
cross-compiled, but I doubt that makes a difference)
 
Using readelf -h, my kernel has 2 program headers.  Aboot will not boot
these files.
 
I also have linux-image-2.6.24-1-alpha-generic_2.6.24-7_alpha.deb 
installed
on my alpha.  This kernel also does not boot.
 
There was apparently a change between kernel v2.6.22 and v2.6.23 in the
vmlinux.lds.S that specifies 2 program headers.  I modified my ld 
script to
specify 1 header.  The system did boot with this modification.
 
Either aboot needs to cope with this or the kernel should be fixed.
 
   What needs to happen is that you need to install the boot block from aboot
   1.0~pre20040408-2 to your hard drive.  You appear to have upgraded from
   etch, and bootloader packages don't automatically install new boot blocks
   when they're upgraded.
 
  This was a fresh install of sid.  I ran swriteboot after I installed this
  version of aboot.
 
 Ok, then it appears this is a problem specific to your cross-compiled
 kernel, since this version of aboot works just fine with the 2.6.24 kernels
 in the archive.  Downgrading the severity, thanks.

It also happened with linux-image-2.6.24-1-alpha-generic_2.6.24-7_alpha.deb
(26701190 May 10 16:47 MD5:66a24de6495e9fbc601077a1846a6aa2)
Was this cross compiled too?

-- 
 Lab tests show that use of micro$oft causes cancer in lab animals
 Got Gas???



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#483601: aboot: Unable to boot kernels = 2.6.23

[Wakko Warner]

Steve Langasek wrote:
 On Fri, May 30, 2008 at 06:48:56PM -0400, Wakko Warner wrote:
  Steve Langasek wrote:
   On Fri, May 30, 2008 at 06:58:12AM -0400, Wakko Warner wrote:
Steve Langasek wrote:
 What needs to happen is that you need to install the boot block from 
 aboot
 1.0~pre20040408-2 to your hard drive.  You appear to have upgraded 
 from
 etch, and bootloader packages don't automatically install new boot 
 blocks
 when they're upgraded.
 
This was a fresh install of sid.  I ran swriteboot after I installed 
this
version of aboot.
 
   Ok, then it appears this is a problem specific to your cross-compiled
   kernel, since this version of aboot works just fine with the 2.6.24 
   kernels
   in the archive.  Downgrading the severity, thanks.
 
  It also happened with linux-image-2.6.24-1-alpha-generic_2.6.24-7_alpha.deb
  (26701190 May 10 16:47 MD5:66a24de6495e9fbc601077a1846a6aa2)
  Was this cross compiled too?
 
 No.  If it's happening for you with the kernel in the archive, then you
 don't have the right aboot boot block installed to your disk at all; the
 current sid version of aboot *does* correctly handle the ELF header on this
 kernel.
 
 Do you also have the current version of aboot-base installed (or, did you
 have it installed at the time you ran swriteboot)?  That's the binary
 package that contains the boot block.

The disk never had an OS on it (it was a data disk, plus it was completely
reinitialized before I started).  I booted the machine from the cd and used
my sid mirror (it's probably a week out of date now) to install the
packages.  Aboot was not part of that install and I installed it with
apt-get install aboot.  It also installed aboot-base.

This is what was installed:
[EMAIL PROTECTED]:/root] dpkg -l aboot\*|cat
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Cfg-files/Unpacked/Failed-cfg/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad)
||/ Name Version  
Description
+++---
ii  aboot1.0~pre20040408-2
Linux bootloader for the SRM console
ii  aboot-base   1.0~pre20040408-2
base files required for bootable media on Li
un  aboot-cross  none   
(no description available)
[EMAIL PROTECTED]:/root] 

After that, i did swriteboot -f3 /dev/rd/c0d0

When I attempted to boot the debian kernel, it gave me (at the srm console):
aboot: Can't load kernel. Multiple BSS segments

The version did match the version I installed.  As I said, there was no loader
installed to the disk when I started (not even a disk label)

-- 
 Lab tests show that use of micro$oft causes cancer in lab animals
 Got Gas???



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#463769: Fails on files (ie disk images)

[Wakko Warner]

martin f krafft wrote:
 also sprach Wakko Warner [EMAIL PROTECTED] [2008.04.11.2318 +0200]:
  Querying is the only thing I was after.  The patch I made makes querying
  work.
 
 Wakko, is this querying-specific, and does the patch have no other
 effects?

I don't think it's query specific due to the way mdadm was written.

What it does is this:
in Query.c:Query:
2 places where an open is performed, I added O_LARGEFILE to the flags. 
Without this, obviously, files larger than 2gb will not open.

in mdadm.h:
I added a define for _FILE_OFFSET_BITS 64
It's been a while, I don't remember exactly why, but I think that caused
O_LARGEFILE to be included from one of the system libraries.

in util.c:dev_open:
I add O_LARGEFILE to the flags which is used later in an open statement.

in util.c:get_dev_size:
I add an fstat to get the size of the file if it is a regular file.  That
function only used ioctls to get the size.

Those modifications allowed querying with -E work on regular files. 

 Neil, can we integrate this upstream? The patch makes mdadm -E/D
 work on files, not only block devices.

This does not work with -D.  -D requires an active MD device to query.

-- 
 Lab tests show that use of micro$oft causes cancer in lab animals
 Got Gas???



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#463769: Fails on files (ie disk images)

[Wakko Warner]

martin f krafft wrote:
 also sprach Wakko Warner [EMAIL PROTECTED] [2008.04.11.1802 +0200]:
  That wasn't the point.  The point was I wasn't able to examine
  the file. There's absolutely no reason that one has to attach it
  to a loopback device just to examine the md superblock.
 
 md is multi-device. A file is not a device.

Agreed

  Of course, mdadm
 could work on files,

Yes.  But only in query mode.  I would not expect to actually use the file
as a device w/o loopback.

 it could also implicitly gunzip them and do

Definately not.  AFAIK, there's no way to fetch a specific uncompressed
offset with a .gz file

 character translation and all the like.

Again, definately not.

 But it doesn't, and it
 won't.

Querying is the only thing I was after.  The patch I made makes querying
work.

 Now, at least this is my interpretation. I CC'd upstream and if he
 disagrees, I'll take it all back. Neil, the bug report is at
 http://bugs.debian.org/463769.

The reason I did this was to make sure that this file contains an MD
superblock and that I named the file correctly (IE has sdX in the name)

-- 
 Lab tests show that use of micro$oft causes cancer in lab animals
 Got Gas???



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#475078: Plugin: if_ usage on ppp interface when interface goes down and back up

[Wakko Warner]

Package: munin-node
Version: 1.2.5-1
Severity: minor

I noticed in my graphs that my ppp0 (56k Dialup) shows 14mb/sec average
(probably depends on how much traffic has been seen when it actually goes
down) each time the interface goes down and comes back up.  Considering that
this interface cannot actually do this, it makes the graph completely useless.
I don't have a clue what the best way to handle this is.

I would assume that when the interface goes down and comes back up, the
transfer size resets and it assumes that an overflow has occured.  If it
were possible to detect, it probably would be better to assume it hasn't
overflowed if the link was just reset.  I'm not sure how to check that
though.

-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.24.3 (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/bash

Versions of packages munin-node depends on:
ii  adduser   3.100  Add and remove users and groups
ii  libnet-server-perl0.94-1 An extensible, general perl server
ii  lsb-base  3.1-24 Linux Standard Base 3.1 init scrip
ii  perl  5.8.8-7Larry Wall's Practical Extraction 
ii  procps1:3.2.7-3  /proc file system utilities

Versions of packages munin-node recommends:
ii  libnet-snmp-perl  5.2.0-1Script SNMP connections

-- no debconf information



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#463769: Fails on files (ie disk images)

[Wakko Warner]

Package: mdadm
Version: 2.6.4-1
Severity: minor
Tags: patch

I made an image of 2 disks that are part of a 2 disk raid0.  These images are
320gb in size.  I tried to use mdadm -E to give me some information about
them which resulted in:
# mdadm -E /junk/nail.md0-part1of2.img
mdadm: cannot open /junk/nail.md0-part1of2.img: File too large
# 

I modified the source to use O_LARGEFILE in open which gave me an error
stating that the device was not recognised.  mdadm does not stat files to
obtain the size, it only uses ioctl's.  The patch adds O_LARGEFILE and tests
to see if the device is a file and uses that information instead.

This worked for me, but I only modified for -Q and -E.  I did not attempt to
assemble the array.

-- System Information:
Debian Release: 3.1
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.23
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages mdadm depends on:
ii  debconf   1.5.19 Debian configuration management sy
ii  libc6 2.7-5  GNU C Library: Shared libraries
ii  lsb-base  3.1-22 Linux Standard Base 3.1 init scrip
ii  makedev   2.3.1-75   Creates device files in /dev

Versions of packages mdadm recommends:
ii  exim4-daemon-custom [mail-tra 10:4.63-10 custom exim MTA (v4) daemon with l
ii  module-init-tools 3.2.2-3tools for managing Linux kernel mo

-- debconf information excluded
diff -ru mdadm-2.6.4-orig/Query.c mdadm-2.6.4/Query.c
--- mdadm-2.6.4-orig/Query.c	2007-10-18 23:59:52.0 -0400
+++ mdadm-2.6.4/Query.c	2008-02-02 20:33:30.0 -0500
@@ -37,7 +37,7 @@
 	 * whether it is an md device and whether it has 
 	 * a superblock
 	 */
-	int fd = open(dev, O_RDONLY, 0);
+	int fd = open(dev, O_RDONLY | O_LARGEFILE, 0);
 	int vers;
 	int ioctlerr;
 	int superror, superrno;
@@ -101,7 +101,7 @@
 			mddev = get_md_name(info.array.md_minor);
 			disc.number = info.disk.number;
 			activity = undetected;
-			if (mddev  (fd = open(mddev, O_RDONLY))=0) {
+			if (mddev  (fd = open(mddev, O_RDONLY | O_LARGEFILE))=0) {
 if (md_get_version(fd) = 9000 	
 ioctl(fd, GET_ARRAY_INFO, array)= 0) {
 	if (ioctl(fd, GET_DISK_INFO, disc) = 0 
diff -ru mdadm-2.6.4-orig/mdadm.h mdadm-2.6.4/mdadm.h
--- mdadm-2.6.4-orig/mdadm.h	2007-10-18 23:59:53.0 -0400
+++ mdadm-2.6.4/mdadm.h	2008-02-02 21:08:30.0 -0500
@@ -28,6 +28,7 @@
  */
 
 #define	_GNU_SOURCE
+#define _FILE_OFFSET_BITS 64
 #include	unistd.h
 #if !defined(__dietlibc__)  !defined(__KLIBC__)
 extern __off64_t lseek64 __P ((int __fd, __off64_t __offset, int __whence));
diff -ru mdadm-2.6.4-orig/util.c mdadm-2.6.4/util.c
--- mdadm-2.6.4-orig/util.c	2007-10-18 23:59:53.0 -0400
+++ mdadm-2.6.4/util.c	2008-02-02 21:10:29.0 -0500
@@ -711,6 +711,7 @@
 
 	if (!dev) return -1;
 
+	flags |= O_LARGEFILE;
 	major = strtoul(dev, e, 0);
 	if (e  dev  *e == ':'  e[1] 
 	(minor = strtoul(e+1, e, 0)) = 0 
@@ -792,6 +793,13 @@
 int get_dev_size(int fd, char *dname, unsigned long long *sizep)
 {
 	unsigned long long ldsize;
+	struct stat st;
+
+	if (fstat(fd, st) != -1  S_ISREG(st.st_mode))
+	{
+	 ldsize = (unsigned long long)st.st_size;
+	}
+	else
 #ifdef BLKGETSIZE64
 	if (ioctl(fd, BLKGETSIZE64, ldsize) != 0)
 #endif

Bug#448438: Displays inf rpm on my system

[Wakko Warner]

Package: xengine
Version: 1.11-11
Severity: normal

My system is a 2x dual core xeon 3.2ghz with an ati firegl v5100.  xengine
reports inf rpm.  I assume it is ran so fast it cannot calculate.

-- System Information:
Debian Release: 3.1
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.23
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages xengine depends on:
ii  libc6 2.6.1-5GNU C Library: Shared libraries
ii  libice6   1:1.0.1-2  X11 Inter-Client Exchange library
ii  libsm61:1.0.1-3  X11 Session Management library
ii  libx11-6  2:1.0.3-3  X11 client-side library
ii  libxaw7   1:1.0.2-4  X11 Athena Widget library
ii  libxext6  1:1.0.1-2  X11 miscellaneous extension librar
ii  libxmu6   1:1.0.2-2  X11 miscellaneous utility library
ii  libxt61:1.0.2-2  X11 toolkit intrinsics library

xengine recommends no packages.

-- no debconf information



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#446621: Cannot find sources.list on a non-standard setup

[Wakko Warner]

Package: apt-file
Version: 2.0.8.2
Severity: important

When invoking apt-file, I see this:

# apt-file search md5sum
E: Can't open /debian//etc/apt//debian/apt/sources.list: No such file or 
directory
# 

My /etc/apt/sources.list is not used at all on my system and infact, it does
not attempt to read it (that's good actually).  However, it doesn't get the
path correct as seen above.

strace -eopen shows the following (libraries were removed):
open(/etc/apt/apt-file.conf, O_RDONLY|O_LARGEFILE) = 5
open(/etc/apt/apt.conf.d/, O_RDONLY|O_NONBLOCK|O_LARGEFILE|O_DIRECTORY) = 5
open(/etc/apt/apt.conf.d/00mirror, O_RDONLY|O_LARGEFILE) = 5
open(/etc/apt/apt.conf.d/00noauth, O_RDONLY|O_LARGEFILE) = 5
open(/etc/apt/apt.conf.d/01autoremove, O_RDONLY|O_LARGEFILE) = 5
open(/etc/apt/apt.conf.d/70debconf, O_RDONLY|O_LARGEFILE) = 5
open(/etc/apt/apt.conf.d/show_upgraded, O_RDONLY|O_LARGEFILE) = 5
open(/debian//etc/apt//debian/apt/sources.list, O_RDONLY|O_LARGEFILE) = -1 
ENOENT (No such file or directory)
E: Can't open /debian//etc/apt//debian/apt/sources.list: No such file or 
directory

The contents of the 00noauth, 01autoremove, 70debconf, and show_upgraded are
not relevent, however, 00mirror is:
Dir /debian/
{
 State apt/
 {
  Lists lists/;
 };
 Cache apt/cache/
 {
  Archives /var/cache/apt/archives/;
  srcpkgcache srcpkgcache.bin;
  pkgcache pkgcache.bin;
 };
 Etc /etc/apt/
 {
  SourceList /debian/apt/sources.list;
 };
};

This has never failed me for apt-get and apt-cache, but apt-file barfs at it.
All my systems NFS mount /debian (except for the server of course, and I
never have to use apt-get update !!!)

-- System Information:
Debian Release: 3.1
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.20-pae
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages apt-file depends on:
ii  gzip  1.3.5-9The GNU compression utility
ii  libapt-pkg-perl   0.1.21+b1  Perl interface to libapt-pkg
ii  libconfig-file-perl   1.4-2  Parses simple configuration files
ii  perl  5.8.8-7Larry Wall's Practical Extraction 
ii  wget  1.10.2-3   retrieves files from the web

apt-file recommends no packages.

-- no debconf information



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#399654: Monitor flickers

[Wakko Warner]

Brice Goglin wrote:
 Hi Wakko,
 
 This bug apparently got some new attention upstream recently. Did you
 try the new upstream release candidates that have been in experimental
 recently (xserver-xorg-video-ati 1:6.6.192-1 currently) in case it helps?

I tried one of them a few weeks ago, didn't help in this case.

-- 
 Lab tests show that use of micro$oft causes cancer in lab animals
 Got Gas???


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#399654: Monitor flickers

[Wakko Warner]

Brice Goglin wrote:
 This bug apparently got some new attention upstream recently. Did you
 try the new upstream release candidates that have been in experimental
 recently (xserver-xorg-video-ati 1:6.6.192-1 currently) in case it helps?

Ignore my last post, I didn't notice the subject line.  For me, it has been
long since fixed by setting the Horizonal frequency to 50hz (whatever the
lowest pixel clock was for each mode line).  It also was a problem with
hardware.  I had a radeon 9200 dual head with vga and dvi connectors.  The
problem only happened on the DVI.  I replaced the card with a FireGL X1 dual
DVI and I no longer have this problem.  When I change the card, I did not
change *ANY* configurations to the xorg.conf.  It just worked and better I
might add!

-- 
 Lab tests show that use of micro$oft causes cancer in lab animals
 Got Gas???


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#415543: Bug#393190: X fails to start on a PowerMac beige G3 when PCI NIC installed

[Wakko Warner]

Brice Goglin wrote:
 Wakko Warner wrote:
  At one point, I installed XFree86 that was still laying in pool.  It didn't
  have a problem.  I think older copies of Xorg worked (7.x) but I'm not
  quite sure.
 
  IIRC, if I just use the onboard nic, it did work.

 
 Somebody just reported the same issue with an explanation of the problem.
 Have a look at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=426433
 I forwarded the bug upstream, let's hope it will be taken care of.

More fuel to the fire:
[EMAIL PROTECTED]:/tmp] X
_XSERVTransSocketOpenCOTSServer: Unable to open socket for inet6
_XSERVTransOpen: transport open failed for inet6/narf-mac:0
_XSERVTransMakeAllCOTSServerListeners: failed to open listener for inet6

X Window System Version 1.3.0
Release Date: 19 April 2007
X Protocol Version 11, Revision 0, Release 1.3
Build Operating System: Linux Debian
Current Operating System: Linux narf-mac 2.6.17 #4 Tue Sep 19 20:32:37 EDT 2006 
ppc
Build Date: 04 June 2007
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Module Loader present
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: /var/log/Xorg.0.log, Time: Thu Jun  7 21:06:55 2007
(==) Using config file: /etc/X11/xorg.conf
(II) Module already built-in
(II) Module already built-in
(WW) INVALID IO ALLOCATION b: 0xfe001000 e: 0xfe0010ff correcting
(EE) end of block range 0xfdff  begin 0xfe00
(EE) ATI(0): Unable to register the following bus resources:
[0] 0   0   0xfe000400 - 0xfe0004ff (0x100) IS[B]
(EE) Screen(s) found, but none have a usable configuration.

Fatal server error:
no screens found
[EMAIL PROTECTED]:/tmp] lspci -vs 0e
:00:0e.0 Ethernet controller: 3Com Corporation 3c905C-TX/TX-M [Tornado] 
(rev 78)
Subsystem: 3Com Corporation 3C905C-TX Fast Etherlink for PC Management 
NIC
Flags: bus master, medium devsel, latency 32, IRQ 24
I/O ports at fe000400 [size=128]
Memory at 8180 (32-bit, non-prefetchable) [size=128]
Expansion ROM at 8182 [disabled] [size=128K]
Capabilities: [dc] Power Management version 2

[EMAIL PROTECTED]:/tmp] lspci -vs 12
:00:12.0 VGA compatible controller: ATI Technologies Inc 3D Rage I/II 215GT 
[Mach64 GT] (rev 9a) (prog-if 00 [VGA])
Flags: bus master, stepping, medium devsel, latency 32, IRQ 22
Memory at 8200 (32-bit, non-prefetchable) [size=16M]
I/O ports at fe001000 [size=256]
Memory at 8000 (32-bit, non-prefetchable) [size=4K]

[EMAIL PROTECTED]:/tmp] 

As stated, this only happens with an ethernet controller installed (the chip
apparently doesn't matter).
ii  xserver-xorg-video-ati 6.6.191-1  X.Org X server -- ATI display driver

Any other versions available that I can try (w/o compiling it myself)?

-- 
 Lab tests show that use of micro$oft causes cancer in lab animals
 Got Gas???


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#415543: Bug#393190: X fails to start on a PowerMac beige G3 when PCI NIC installed

[Wakko Warner]

Brice Goglin wrote:
 I don't know what is going on with Powermac beige G3, but it looks like
 several people actualy have conflicts between Xorg and the network on
 this kind of machine. I am merging the relevant bugs.
 
 I am trying to get some help for either upstream Xorg people or PowerPC
 guys since I am not even sure whether it's a hardware of software
 (kernel? Xorg only?) related problem. If anybody has a clue, please let
 me know.

At one point, I installed XFree86 that was still laying in pool.  It didn't
have a problem.  I think older copies of Xorg worked (7.x) but I'm not
quite sure.

IIRC, if I just use the onboard nic, it did work.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#426333: Fails to convert libc6-dev-ppc64_2.5-9_powerpc.deb due to symlink problem

[Wakko Warner]

Package: dpkg-cross
Version: 1.37
Severity: normal

Apparently, dpkg-cross chokes on symlinks pointing to .

[EMAIL PROTECTED]:/o/cross] dpkg-cross -a powerpc -b 
libc6-dev-ppc64_2.5-9_powerpc.deb
dpkg-cross: failed to create symlink 
/tmp/dpkg-cross.AB7fefKl/dst/usr/powerpc-linux-gnu/include/powerpc64-linux-gnu 
- : No such file or directory
dpkg-cross: conversion of libc6-dev-ppc64_2.5-9_powerpc.deb failed.
[EMAIL PROTECTED]:/o/cross] 

[EMAIL PROTECTED]:/o/cross] dpkg -x libc6-dev-ppc64_2.5-9_powerpc.deb x   
[EMAIL PROTECTED]:/o/cross] ls -l x/usr/include 
total 0
drwxr-xr-x 2 wakko users 80 May 23 14:33 gnu/
lrwxrwxrwx 1 wakko users  1 May 27 21:13 powerpc64-linux-gnu - ./
[EMAIL PROTECTED]:/o/cross] 

-- System Information:
Debian Release: 3.1
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.20-pae
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages dpkg-cross depends on:
ii  binutils   2.17cvs20070426-3 The GNU assembler, linker and bina
ii  debconf1.4.39Debian configuration management sy
ii  dpkg-dev   1.14.3package building tools for Debian
ii  file   4.20-5Determines file type using magic

dpkg-cross recommends no packages.

-- debconf information excluded


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#426333: This fix worked for me.

[Wakko Warner]

dpkg-cross:606
change if ($lv =~ /^[^\/]/) {
to if ($lv ne . and $lv =~ /^[^\/]/) {

I do not know if this is correct or not, but with out it, the link points to
/usr/include/.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#415543: xorg: xserver crashes on beige G3 PowerMac

[Wakko Warner]

Brice Goglin wrote:
 Could somebody have a look at bug #415543? Rob has a strange problem on
 his PowerMac. Basically, Xorg and network cannot work at the same time.
 I suspect a hardware or kernel problem, but I am not familiar enough
 with powerpc to debug further. Help would be appreciated.

I had a problem like this.  If I installed a nic (3com, tulip, or amd
pcnet32), X wouldn't work.  I forgot the details now.

  Hi, first of all thanks for your reply. My /proc/interrupts looks as 
  follows:
 
CPU0
   18:583   PMAC-PIC  Edge  MESH
   20:  0   PMAC-PIC  Edge  PMac
   21:  0   PMAC-PIC  Edge  PMac Output
   22:  0   PMAC-PIC  Edge  PMac Input
   23:217   PMAC-PIC  Level eth0
   25:  0   PMAC-PIC  Edge  SWIM3
   27:   1559   PMAC-PIC  Edge  ide0
   29:   5078   PMAC-PIC  Edge  ADB
  BAD:  0
   
  eth0 doesn't appear to share the interrupt with anything else. I really 
  can't tell which one my graphic card is supposed to be. The network card's 
  number is 23 which explains the Disabling IRQ#23 message when I get 
  thrown out of the network. On a hunch I moved the ethernet card to another 
  pci slot but that had the same result.
 
  The sordid debian installation story for my power mac is as follows. I had 
  both xfree86 and network working together with sarge, the 2.6.8  kernel and 
  bootx (the bootloader). With bootx you boot into os9 and then from there 
  boot into linux. I then completely erased os9 and sarge and installed sarge 
  and then etch using quik. Quik (also a bootloader) allows you to boot 
  directly into linux. Because I couldn't get xfree86 or xorg working at all 
  with quik (similar problem with screen freezing), I installed etch with os9 
  and bootx.
 
  Beats me if I broke something along the way...
 
  Anyways, thanks for your help up till now. At least I know now what 
  interrupts and IRQs are. As always, more help is appreciated.
 
  yours, rob homsi

 
 
 -- 
 To UNSUBSCRIBE, email to [EMAIL PROTECTED]
 with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
 
-- 
 Lab tests show that use of micro$oft causes cancer in lab animals
 Got Gas???


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#417858: Strange time differential in the log (via syslogd)

[Wakko Warner]

Paul Slootman wrote:
 On Wed 04 Apr 2007, Wakko Warner wrote:
 
  Package: rsync
  Version: 2.6.9-3
  Severity: normal
  
  I have one system that does an update of another via rsync when one machine
  is running rsync as a daemon (IE, rsh/ssh not being used as the transport)
  
  The log shows this:
  Apr  4 20:32:05 vegeta rsyncd[31217]: connect from nail
  Apr  4 20:32:05 vegeta rsyncd[31217]: rsync on debian/pool/ from nail
  Apr  5 00:32:05 vegeta rsyncd[31217]: building file list 
  Apr  5 00:34:44 vegeta rsyncd[31217]: sent 363012298 bytes  received 17763
  bytes  total size 92369457939 
  
  Apparently those last 2 lines are in UTC time instead of EDT time.  No, it
 
 It's a known problem upstream, and it seems to be related with how glibc
 handles its timezone data. If my assumptions are correct, you have this
 rsync module configured to do a chroot. After the chroot, rsync (or
 rather, glibc) can't find the timezone data, and falls back to UTC.

I just checked, it is doing a chroot.  I don't think it really matters since
this isn't internet accessible.

 Rsync already does its best to initialize the timezone data before the
 chroot, but apparently glibc wants continued access to the timezone
 data. On most systems the rsync approach works, only on linux the log
 timestamps are wrong when rsync chroots.
 
 If it's a real problem, then to workaround you need to copy the
 necessary timezone files to the chroot, although in practice that is
 probably not workable :(

-- 
 Lab tests show that use of micro$oft causes cancer in lab animals
 Got Gas???


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#417858: Strange time differential in the log (via syslogd)

[Wakko Warner]

Package: rsync
Version: 2.6.9-3
Severity: normal

I have one system that does an update of another via rsync when one machine
is running rsync as a daemon (IE, rsh/ssh not being used as the transport)

The log shows this:
Apr  4 20:32:05 vegeta rsyncd[31217]: connect from nail
Apr  4 20:32:05 vegeta rsyncd[31217]: rsync on debian/pool/ from nail
Apr  5 00:32:05 vegeta rsyncd[31217]: building file list 
Apr  5 00:34:44 vegeta rsyncd[31217]: sent 363012298 bytes  received 17763
bytes  total size 92369457939 

Apparently those last 2 lines are in UTC time instead of EDT time.  No, it
didn't take 4 hours.  The following line in the log file is:
Apr  4 20:34:48 vegeta in.rshd[31219]: connect from nail

(FYI: that log line was due to an rsync using rsh as the transport)

I'm not sure if this is really a bug in rsync, syslogd, or some
configuration mistake.  If it makes any difference, the machine has
tzdata 2007d-1 installed.  Everything else appears to log the correct time.

-- System Information:
Debian Release: 3.1
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.20
Locale: LANG=C, LC_CTYPE=C

Versions of packages rsync depends on:
ii  libacl1  2.2.23-1Access control list shared library
ii  libc62.3.6.ds1-9 GNU C Library: Shared libraries
ii  libpopt0 1.10-3  lib for parsing cmdline parameters
ii  lsb-base 3.1-22  Linux Standard Base 3.1 init scrip

-- no debconf information


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#399654: Monitor flickers

[Wakko Warner]

Michel D?nzer wrote:
 tags 399654 upstream
 forwarded 399654 https://bugs.freedesktop.org/show_bug.cgi?id=2859
 kthxbye
 
 On Mon, 2006-11-20 at 22:50 -0500, Wakko Warner wrote: 
  
  I have an ATI Radeon 9200 with DVI and VGA outputs.  Connected to the DVI, I
  have a Samsung SyncMaster 204T.
  
  When xterms scroll rapidly I notice flickering.  In a browser, sometimes
  changing tabs causes it to blank out noticably (duration say .5 seconds).
  Running gears from xscreensaver-gl with -delay 0 causes the monitor to blank
  entirely.  Moving some windows around (depends on content) will cause
  flickers or jitters.
 
 See the upstream bug report referenced above.

Thanks.

  Here's my device section from /etc/X11/xorg.conf
  Section Device
  Identifier  Generic Video Card
  Driver  radeon
  Option  AGPMode 6
  Option  DisplayPriority BIOS
  EndSection
 
 If
 
   Option  DisplayPriority HIGH
 
 doesn't help, a reduced blanking mode might.

What do I do to set a reduced blanking mode?  I'll try the HIGH sometime
this week.

-- 
 Lab tests show that use of micro$oft causes cancer in lab animals
 Got Gas???


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#399654: Monitor flickers

[Wakko Warner]

Michel D?nzer wrote:
  Here's my device section from /etc/X11/xorg.conf
  Section Device
  Identifier  Generic Video Card
  Driver  radeon
  Option  AGPMode 6
  Option  DisplayPriority BIOS
  EndSection
 
 If
 
   Option  DisplayPriority HIGH

Tried it, doesn't work.  Same thing

 doesn't help, a reduced blanking mode might.

I do not know how to do this.  I set several mode lines, X ignores all lines
I try and uses it's own.

-- 
 Lab tests show that use of micro$oft causes cancer in lab animals
 Got Gas???


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#389496: Workaround: Asks for password when starting

[Wakko Warner]

Christian Hammers wrote:
 On 2006-10-26 Wakko Warner wrote:
  /etc/pam.d/quagga:
  authrequiredpam_permit.so
  
  This causes quagga not to ask for a password as it uses pam authentication
  methods.  I do not see a security risk because:
  1) Only quagga user or quaggavty group has access to the sockets
  2) Any admin who compiles their own vtysh w/o asking for a password will do
  the exact same thing.
  
  There is really no reason that I can see to authenticate the calling user.
 
 This is currently true but I expect the other daemons to start using PAM in
 the future, too and having a pam_permit laying around probably isn't the best
 idea then.

Maybe not, but that was the workaround I found.  I didn't look at rootok
though.  I tested vtysh as a normal user which was unable to connect to the
daemons running.

 I'm preparing an upload with pam_rootok.so in the
 default /etc/pam.d/quagga. This is enough for the init script to work.

This is still a workaround IMO.

 Sadly vtysh does not give a sane error message.
 
 What do you think?

Personally, I think the authentication should be completely removed from
vtysh.  It has already been proven to be a useless authentication method. 
As stated, anyone could compile their own vtysh to bypass this (or just
place the permit in the pam config).  Unless someone chowns the sockets that
the daemons use, only quagga user and root user can connect.

Do what you feel is best.

-- 
 Lab tests show that use of micro$oft causes cancer in lab animals
 Got Gas???


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#389496: Workaround: Asks for password when starting

[Wakko Warner]

/etc/pam.d/quagga:
authrequiredpam_permit.so

This causes quagga not to ask for a password as it uses pam authentication
methods.  I do not see a security risk because:
1) Only quagga user or quaggavty group has access to the sockets
2) Any admin who compiles their own vtysh w/o asking for a password will do
the exact same thing.

There is really no reason that I can see to authenticate the calling user.

-- 
 Lab tests show that use of micro$oft causes cancer in lab animals
 Got Gas???


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#392296: Asks for password when starting

[Wakko Warner]

Package: quagga
Version: 0.99.5-2
Severity: important

I have a Quagga.conf that is non-empty.

issueing /etc/init.d/quagga start shows:
# /etc/init.d/quagga start
Loading capability module if not yet done.
Starting Quagga daemons (prio:10): zebra ospfd.
Password: 
# 

sh -x shows that the command causing this is vtysh -b

I have used quagga on other systems before (0.99.4) which does not exibit
this behaviour.

strace -eopen vtysh shows:
open(/etc/ld.so.cache, O_RDONLY)  = 3
open(/usr/lib/libzebra.so.0, O_RDONLY) = 3
open(/lib/libcap.so.1, O_RDONLY)  = 3
open(/lib/libreadline.so.5, O_RDONLY) = 3
open(/lib/tls/libm.so.6, O_RDONLY)= 3
open(/lib/tls/libcrypt.so.1, O_RDONLY) = 3
open(/lib/libpam.so.0, O_RDONLY)  = 3
open(/lib/libpam_misc.so.0, O_RDONLY) = 3
open(/lib/tls/libc.so.6, O_RDONLY)= 3
open(/lib/libncurses.so.5, O_RDONLY)  = 3
open(/lib/tls/libdl.so.2, O_RDONLY)   = 3
open(/etc/mtab, O_RDONLY) = 3
open(/proc/meminfo, O_RDONLY) = 3
open(/etc/quagga/vtysh.conf, O_RDONLY) = -1 ENOENT (No such file or directory)
open(/etc/nsswitch.conf, O_RDONLY)= 3
open(/etc/ld.so.cache, O_RDONLY)  = 3
open(/lib/libnss_ldap.so.2, O_RDONLY) = 3
open(/usr/lib/libldap_r.so.2, O_RDONLY) = 3
open(/usr/lib/liblber.so.2, O_RDONLY) = 3
open(/lib/tls/libnsl.so.1, O_RDONLY)  = 3
open(/lib/tls/libresolv.so.2, O_RDONLY) = 3
open(/usr/lib/libsasl2.so.2, O_RDONLY) = 3
open(/usr/lib/libgnutls.so.11, O_RDONLY) = 3
open(/lib/tls/libpthread.so.0, O_RDONLY) = 3
open(/usr/lib/libtasn1.so.2, O_RDONLY) = 3
open(/usr/lib/libgcrypt.so.11, O_RDONLY) = 3
open(/usr/lib/libgpg-error.so.0, O_RDONLY) = 3
open(/usr/lib/libz.so.1, O_RDONLY)= 3
open(/etc/libnss-ldap.conf, O_RDONLY) = 3
open(/etc/resolv.conf, O_RDONLY)  = 3
open(/etc/ld.so.cache, O_RDONLY)  = 3
open(/lib/tls/libnss_files.so.2, O_RDONLY) = 3
open(/etc/host.conf, O_RDONLY)= 3
open(/etc/hosts, O_RDONLY)= 3
open(/etc/ldap/ldap.conf, O_RDONLY|O_LARGEFILE) = 3
open(/root/ldaprc, O_RDONLY|O_LARGEFILE) = -1 ENOENT (No such file or 
directory)
open(/root/.ldaprc, O_RDONLY|O_LARGEFILE) = -1 ENOENT (No such file or 
directory)
open(ldaprc, O_RDONLY|O_LARGEFILE)= -1 ENOENT (No such file or directory)
open(/usr/lib/sasl2, O_RDONLY|O_NONBLOCK|O_LARGEFILE|O_DIRECTORY) = 3
open(/usr/lib/sasl2/libsasldb.la, O_RDONLY) = 6
open(/usr/lib/sasl2/libsasldb.so.2, O_RDONLY) = 6
open(/etc/ld.so.cache, O_RDONLY)  = 6
open(/usr/lib/libdb-4.2.so, O_RDONLY) = 6
open(/usr/lib/sasl2/libsasldb.la, O_RDONLY) = 6
open(/etc/hosts, O_RDONLY)= 3
open(/etc/hosts, O_RDONLY)= 3
open(/etc/pam.d/quagga, O_RDONLY) = -1 ENOENT (No such file or directory)
open(/etc/pam.d/other, O_RDONLY)  = 6
open(/etc/pam.d/common-auth, O_RDONLY) = 10
open(/lib/security/pam_ldap.so, O_RDONLY) = 11
open(/lib/security/pam_unix.so, O_RDONLY) = 11
open(/etc/pam.d/common-account, O_RDONLY) = 10
open(/etc/pam.d/common-password, O_RDONLY) = 10
open(/etc/pam.d/common-session, O_RDONLY) = 10
open(/etc/pam_ldap.conf, O_RDONLY)= 6
open(/etc/ldap.secret, O_RDONLY)  = 6
Password: 
open(/etc/hosts, O_RDONLY)= 6
open(/etc/hosts, O_RDONLY)= 6
open(/etc/localtime, O_RDONLY)= 10
open(/etc/shadow, O_RDONLY)   = 11
Password: 
open(/etc/shadow, O_RDONLY)   = 11
open(/etc/quagga/Quagga.conf, O_RDONLY) = 12
#

NOTE: I typed the password incorrectly the first time in the trace above.
My system uses LDAP for all user information which is why ldap libraries are
pulled in.

-- System Information:
Debian Release: 3.1
Architecture: i386 (i686)
Kernel: Linux 2.6.14
Locale: LANG=C, LC_CTYPE=C

Versions of packages quagga depends on:
ii  adduser   3.59   Add and remove users and groups
ii  debconf [debconf-2.0] 1.4.39 Debian configuration management sy
ii  iproute   20041019-3 Professional tools to control the 
ii  libc6 2.3.6-7GNU C Library: Shared libraries
ii  libcap1   1:1.10-12  support for getting/setting POSIX.
ii  libpam0g  0.76-13Pluggable Authentication Modules l
ii  libreadline5  5.1-5  GNU readline and history libraries
ii  logrotate 3.7-2  Log rotation utility

-- debconf information excluded


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#283350: joe segfaults reproducable Could be the default config

[Wakko Warner]

Josip Rodin wrote:
 On Sun, Jun 04, 2006 at 08:11:21PM -0400, Wakko Warner wrote:
This is just additional information.

[EMAIL PROTECTED]:/home/wakko] dpkg -l joe
ii  joe3.1-0.2user friendly full screen text editor

I have my own .joerc and I did not know about the syntax highlighting
until recently.  I copied all the relevent parts from the debian joerc 
for
highlighting (just the files I use) into my .joerc and I noticed that 
joe
DOES NOT segfault on me.  If I use the debian joerc file, it does
segfault.

I tested the different debian rc files for joe.
jmacsrc segfaults
joerc   segfaults
jpicorc works fine
jstarrc segfaults
rjoerc  works fine

If I find anything else out, I'll report back.
   
   What's your locale? Can you try with joe 3.3?
  
  I have no idea what my locale is.  C Maybe.
 
 Type locale and paste over the output :)

LANG=
LC_CTYPE=POSIX
LC_NUMERIC=POSIX
LC_TIME=POSIX
LC_COLLATE=POSIX
LC_MONETARY=POSIX
LC_MESSAGES=POSIX
LC_PAPER=POSIX
LC_NAME=POSIX
LC_ADDRESS=POSIX
LC_TELEPHONE=POSIX
LC_MEASUREMENT=POSIX
LC_IDENTIFICATION=POSIX
LC_ALL=


-- 
 Lab tests show that use of micro$oft causes cancer in lab animals
 Got Gas???


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#283350: joe segfaults reproducable Could be the default config

[Wakko Warner]

This is just additional information.

[EMAIL PROTECTED]:/home/wakko] dpkg -l joe
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed
|/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err:uppercase=bad)
||/ Name   VersionDescription
+++-==-==-
ii  joe3.1-0.2user friendly full screen text editor
[EMAIL PROTECTED]:/home/wakko] 

I have my own .joerc and I did not know about the syntax highlighting until
recently.  I copied all the relevent parts from the debian joerc for
highlighting (just the files I use) into my .joerc and I noticed that joe
DOES NOT segfault on me.  If I use the debian joerc file, it does segfault.

I tested the different debian rc files for joe.
jmacsrc segfaults
joerc   segfaults
jpicorc works fine
jstarrc segfaults
rjoerc  works fine

If I find anything else out, I'll report back.

-- 
 Lab tests show that use of micro$oft causes cancer in lab animals
 Got Gas???


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#338186: apt: Installing new package that conflicts with installed causes install of unwanted packages

[Wakko Warner]

Package: apt
Version: 0.6.41
Severity: important

I'm trying to install package xserver-xorg which xserver-xfree86 is currently
installed.  When I do this, it wants to install some packages that
xserver-xorg recommends.  It wants to install discover1 discover1-data
libdiscover1 which I do not want on any of my systems.  I have noticed this
on every machine I upgrade to xorg if xfree is installed.  If I remove
xserver-xfree86 first, it will not install these packages.

I'm installing the xorg from SID, however, I'm not sure if APT is from sid or
sarge.  I saw it with apt 0.5.xx (unsure on xx)

Here's an example of what I mean:
# apt-get -o Debug::pkgProblemResolver=true install xserver-xorg
Reading Package Lists... Done
Building Dependency Tree... Done
Starting
Starting 2
Investigating xserver-xorg
Package xserver-xorg has broken dep on discover1
  Considering discover1 0 as a solution to xserver-xorg 
  Re-Instated discover1-data
  Re-Instated libdiscover1
  Re-Instated discover1
Package xserver-xorg has broken dep on xserver-xfree86
  Considering xserver-xfree86 0 as a solution to xserver-xorg 
  Added xserver-xfree86 to the remove list
  Fixing xserver-xorg via remove of xserver-xfree86
Investigating x11-common
Package x11-common has broken dep on x-window-system
  Considering x-window-system 0 as a solution to x11-common 31
  Holding Back x11-common rather than change x-window-system
Investigating xserver-common
Package xserver-common has broken dep on x11-common
  Considering x11-common 31 as a solution to xserver-common 3
  Holding Back xserver-common rather than change x11-common
Investigating xserver-xorg
Package xserver-xorg has broken dep on xserver-common
  Considering xserver-common 3 as a solution to xserver-xorg 
  Re-Instated xfree86-common
  Re-Instated x11-common
  Re-Instated xserver-common
Done
The following extra packages will be installed:
  discover1 discover1-data libdiscover1 libgcc1 x11-common xfree86-common
  xserver-common
Suggested packages:
  x-window-system-core x-window-system xfonts-scalable configlet-frontends
  libglide2
Recommended packages:
  discover mdetect xresprobe laptop-detect
The following packages will be REMOVED:
  xserver-xfree86
The following NEW packages will be installed:
  discover1 discover1-data libdiscover1 x11-common xserver-xorg
The following packages will be upgraded:
  libgcc1 xfree86-common xserver-common
3 upgraded, 5 newly installed, 1 to remove and 249 not upgraded.
Need to get 0B/7627kB of archives.
After unpacking 1864kB of additional disk space will be used.
Do you want to continue? [Y/n] n
# 

Currently installed xserver-xfree86 is 4.3.0.dfsg.1-10

-- Package-specific info:

-- System Information:
Debian Release: 3.1
Architecture: i386 (i686)
Kernel: Linux 2.6.12
Locale: LANG=C, LC_CTYPE=C

Versions of packages apt depends on:
ii  libc6 2.3.5-6GNU C Library: Shared libraries an
ii  libgcc1   1:4.0.2-2  GCC support library
ii  libstdc++64.0.2-2The GNU Standard C++ Library v3

-- no debconf information


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#317793: cdrecord: Fails to burn 2 cds at once if lower numbered burner is in use.

[Wakko Warner]

Joerg Schilling wrote:
 The problem is caused by braindead modifications applied by Debian to
 cdrtools. Please do not blaim me for bugs that are not in the official
 cdrtools source.
 
 
 An unmodified cdrtools (run as root as documented in the man page)
 does not have this problem.

1) I sent this to debian's bug tracking.  What was done with it after that
   is not my fault.  I found a bug, and explained it.
2) The dev=x,y,z part is braindead.  As I have noticed, it searches /dev/sgX
   to find x,y,z.  Specifying /dev/sr0 or /dev/hdc is much cleaner,
   especially when one has USB devices and plugs/unplugs.  I have always had
   to run -scanbus every single time something on my USB bus changes to use
   my USB burner again.  I have /dev/myburner automatically linked to the
   proper burner device node.  No I will not modify for dev=x,y,z as it
   would have been much easier to figure it out from the device itself and
   cdrecord is the ONLY application that uses this that I use.

Asides from the dev= stuff, cdrecord, when it works, works great.

I looked through the patch.  The only thing I can see is the fact they added
retrying.  The fact that cdrecord (modified or not) searches /dev/sg0
... /dev/sgX to find the specified device is what's brain dead.  If this
were not the case, debian's patch would not have made a difference.  I wish
you would come out of your shell and work with people instead of against
people.  I use linux.  I like linux.  I have no reason to change.  Others
might use windows, freebsd, solaris, or whatever.  Trying to fit the same
device naming scheme with all operating systems is broken by design. 
Portable software has to realize this and work with whatever it was designed
to work with.  However if you're not in agreeance with that, why are there
so many scsi-xxx.c files in libscg?

-- 
 Lab tests show that use of micro$oft causes cancer in lab animals


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#317793: cdrecord: Fails to burn 2 cds at once if lower numbered burner is in use.

[Wakko Warner]

Steve McIntyre wrote:
 On Mon, Jul 11, 2005 at 10:39:05AM -0400, Wakko Warner wrote:
 Package: cdrecord
 Version: 4:2.01+01a01-4
 Severity: normal
 
 # cdrecord dev=28,0,0 -tao -v someimage.iso
 Cdrecord-Clone 2.01.01a01 (i686-pc-linux-gnu) Copyright (C) 1995-2004 Joerg 
 Schilling
 NOTE: this version of cdrecord is an inofficial (modified) release of 
 cdrecord
   and thus may have bugs that are not present in the original version.
   Please send bug reports and support requests to [EMAIL PROTECTED].
   The original author should not be bothered with problems of this 
  version.
 
 cdrecord: Warning: Running on Linux-2.6.12
 cdrecord: There are unsettled issues with Linux-2.5 and newer.
 cdrecord: If you have unexpected problems, please try Linux-2.4 or Solaris.
 TOC Type: 1 = CD-ROM
 scsidev: '28,0,0'
 scsibus: 28 target: 0 lun: 0
 Error trying to open /dev/sg0 exclusively (Device or resource busy)... 
 retrying in 1 second.
 Error trying to open /dev/sg0 exclusively (Device or resource busy)... 
 retrying in 1 second.
 Error trying to open /dev/sg0 exclusively (Device or resource busy)... 
 retrying in 1 second.
 ^C here
 
 I have 2 burners in the above machine.  one is scsi 0:0:0:0 (true scsi), the
 other is scsi 28:0:0:0 (usb).  I received teh above error because I was
 burning a cd on the first burner.  CDrecord shouldn't error out here since
 it's using the wrong device anyway.  (the 2nd one happens to be sg7)
 
 Ah... The first burn will have opened the first burner
 exclusively. The second burn will be walking through all the device
 entries trying to convert Joerg's braindead B,T,L syntax into a real
 device to open. Does this work fine if you use dev=devname instead?

Yes, I would agree that the 0,0,0 is braindead.  So it works for solaris,
whatever, it isn't really portable.  dev=devname does not work.  2.6.12
doesn't like it and it hangs the bus for a few minutes.

I would say it would be best to in his braindead library to ignore devices
it can't open and fail if it can't match the device.

-- 
 Lab tests show that use of micro$oft causes cancer in lab animals


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#318430: Console switching broken

[Wakko Warner]

[EMAIL PROTECTED] wrote:
 Package: xserver-xorg
 Version: 6.8.2.dfsg.1-2
 
 Hi, 
 I just moved from XFree86 to the new Xorg server package. 
 Hardware is 
 
 :01:00.0 VGA compatible controller: Matrox Graphics, Inc. MGA G200
 AGP (rev 03)
 
 driver is mga.
 
 Basically, it works well, but when changing to text-console
 (Ctrl-Alt-F1) the screen is full of garbage. 

Same here, except it gave me a blue border and the text was missing (I have
colored prompts and stuff so I saw some colored blocks)

My card:
:01:00.0 VGA compatible controller: Matrox Graphics, Inc. MGA G400 AGP
(rev 04)

Maybe this is a matrox driver problem?

I have ATI rage, ATI radeon, and a Trident CyberBlade I can try Xorg on.

-- 
 Lab tests show that use of micro$oft causes cancer in lab animals


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#317793: cdrecord: Fails to burn 2 cds at once if lower numbered burner is in use.

[Wakko Warner]

Package: cdrecord
Version: 4:2.01+01a01-4
Severity: normal

# cdrecord dev=28,0,0 -tao -v someimage.iso
Cdrecord-Clone 2.01.01a01 (i686-pc-linux-gnu) Copyright (C) 1995-2004 Joerg 
Schilling
NOTE: this version of cdrecord is an inofficial (modified) release of cdrecord
  and thus may have bugs that are not present in the original version.
  Please send bug reports and support requests to [EMAIL PROTECTED].
  The original author should not be bothered with problems of this version.

cdrecord: Warning: Running on Linux-2.6.12
cdrecord: There are unsettled issues with Linux-2.5 and newer.
cdrecord: If you have unexpected problems, please try Linux-2.4 or Solaris.
TOC Type: 1 = CD-ROM
scsidev: '28,0,0'
scsibus: 28 target: 0 lun: 0
Error trying to open /dev/sg0 exclusively (Device or resource busy)... retrying 
in 1 second.
Error trying to open /dev/sg0 exclusively (Device or resource busy)... retrying 
in 1 second.
Error trying to open /dev/sg0 exclusively (Device or resource busy)... retrying 
in 1 second.
^C here

I have 2 burners in the above machine.  one is scsi 0:0:0:0 (true scsi), the
other is scsi 28:0:0:0 (usb).  I received teh above error because I was
burning a cd on the first burner.  CDrecord shouldn't error out here since
it's using the wrong device anyway.  (the 2nd one happens to be sg7)

-- System Information
Debian Release: 3.1
Kernel Version: Linux ani 2.6.12 #4 SMP Sun Jul 3 15:54:15 EDT 2005 i686 
GNU/Linux

Versions of the packages cdrecord depends on:
ii  debconf1.4.49 Debian configuration management system
ii  libc6  2.3.2.ds1-22   GNU C Library: Shared libraries and Timezone
ii  libcap11.10-14support for getting/setting POSIX.1e capabil
ii  makedev2.3.1-78   creates device files in /dev


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#316873: xine-ui: Unable to play any file that begins with a space

[Wakko Warner]

Package: xine-ui
Version: 0.99.3-1
Severity: normal

I do not know why the original bug was closed as this is a real problem.
Following shows the bug quite clearly, please do not close until it is really
resolved.

# strace xine -f \ Ratt\ -\ Back\ For\ More\ \(I\).mpg|grep Ratt
execve(/usr/bin/xine, [xine, -f,  Ratt - Back For More (I).mpg], [/* 24 
vars */]) = 0
stat64(Ratt - Back For More (I).mpg, 0xbfc66b50) = -1 ENOENT (No such file or 
directory)
stat64(Ratt - Back For More (I).sub, 0xbfc65a20) = -1 ENOENT (No such file or 
directory)
stat64(Ratt - Back For More (I).srt, 0xbfc65a20) = -1 ENOENT (No such file or 
directory)
stat64(Ratt - Back For More (I).asc, 0xbfc65a20) = -1 ENOENT (No such file or 
directory)
stat64(Ratt - Back For More (I).smi, 0xbfc65a20) = -1 ENOENT (No such file or 
directory)
stat64(Ratt - Back For More (I).ssa, 0xbfc65a20) = -1 ENOENT (No such file or 
directory)
open(Ratt - Back For More (I).mpg, O_RDONLY|O_LARGEFILE) = -1 ENOENT (No such 
file or directory)
open(Ratt - Back For More (I).mpg, O_RDONLY|O_LARGEFILE) = -1 ENOENT (No such 
file or directory)
C-c here
# 

As you can see from the execve, there is clearly a space before the name.
however, you can also clearly see that it has stripped the space when doing
a stat64 and when doing the open which the file does not exist.

-- System Information
Debian Release: 3.1
Kernel Version: Linux ani 2.6.12 #4 SMP Sun Jul 3 15:54:15 EDT 2005 i686 
GNU/Linux

Versions of the packages xine-ui depends on:
ii  libc6  2.3.2.ds1-22   GNU C Library: Shared libraries and Timezone
ii  libcurl3   7.12.2-2   Multi-protocol file transfer library, now wi
ii  libfreetype6   2.1.7-1FreeType 2 font engine, shared library files
ii  libice64.3.0.dfsg.1-8 Inter-Client Exchange library
ii  libidn11   0.5.13-1.0 GNU libidn library, implementation of IETF I
ii  libncurses55.4-4  Shared libraries for terminal handling
ii  libpng12-0 1.2.8rel-1 PNG library - runtime
ii  libreadline5   5.0-10 GNU readline and history libraries, run-time
ii  libsm6 4.3.0.dfsg.1-8 X Window System Session Management library
ii  libssl0.9.70.9.7e-2   SSL shared libraries
ii  libx11-6   4.3.0.dfsg.1-8 X Window System protocol client library
ii  libxext6   4.3.0.dfsg.1-8 X Window System miscellaneous extension libr
ii  libxine1   1.0.1-1the xine video/media player library, binary 
ii  libxtst6   4.3.0.dfsg.1-8 X Window System event recording and testing 
ii  libxv1 4.3.0.dfsg.1-5 X Window System video extension library
ii  xlibs  4.3.0.dfsg.1-8 X Window System client libraries metapackage
ii  zlib1g 1.2.2-4compression library - runtime


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#316305: xine-ui: Unable to play any file that begins with a space

[Wakko Warner]

Package: xine-ui
Version: 0.99.3-1
Severity: normal

I have a file or 2 that the first character is a space.  xine complains about 
unable to open file.  If I rename the file so that the first character is not
a space, it works fine (including spaces elsewhere in the name)

-- System Information
Debian Release: 3.1
Kernel Version: Linux ani 2.6.12 #3 SMP Sat Jun 18 18:26:18 EDT 2005 i686 
GNU/Linux

Versions of the packages xine-ui depends on:
ii  libc6  2.3.2.ds1-22   GNU C Library: Shared libraries and Timezone
ii  libcurl3   7.12.2-2   Multi-protocol file transfer library, now wi
ii  libfreetype6   2.1.7-1FreeType 2 font engine, shared library files
ii  libice64.3.0.dfsg.1-8 Inter-Client Exchange library
ii  libidn11   0.5.13-1.0 GNU libidn library, implementation of IETF I
ii  libncurses55.4-4  Shared libraries for terminal handling
ii  libpng12-0 1.2.8rel-1 PNG library - runtime
ii  libreadline5   5.0-10 GNU readline and history libraries, run-time
ii  libsm6 4.3.0.dfsg.1-8 X Window System Session Management library
ii  libssl0.9.70.9.7e-2   SSL shared libraries
ii  libx11-6   4.3.0.dfsg.1-8 X Window System protocol client library
ii  libxext6   4.3.0.dfsg.1-8 X Window System miscellaneous extension libr
ii  libxine1   1.0.1-1the xine video/media player library, binary 
ii  libxtst6   4.3.0.dfsg.1-8 X Window System event recording and testing 
ii  libxv1 4.3.0.dfsg.1-5 X Window System video extension library
ii  xlibs  4.3.0.dfsg.1-8 X Window System client libraries metapackage
ii  zlib1g 1.2.2-4compression library - runtime


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#299072: grub: Grub cannot read ext2/3 on whole disk

[Wakko Warner]

Package: grub
Version: 0.95+cvs20040624-15
Severity: normal

# mkreiserfs -f /dev/sdb
snip

# grub --device-map=dev
grub root (hd0)
 Filesystem type is reiserfs, using whole disk
 
grub 

# mke2fs /dev/sdb
snip

# grub --device-map=dev
grub root (hd0)
 Filesystem type unknown, using whole disk
 
grub 

# mount /dev/sdb /mnt
# df /mnt
Filesystem   1K-blocks  Used Available Use% Mounted on
/dev/sdb   961717220   9128628   1% /mnt
# umount /dev/sdb
# mke2fs -j /dev/sdb
snip

# grub --device-map=dev
grub root (hd0)
 Filesystem type unknown, using whole disk

grub 
 


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#291419: findutils: Unable to use find to locate files that have dates in the future

[Wakko Warner]

Package: findutils
Version: 4.1.20-4
Severity: wishlist

I have a system that has a bad clock and files get dates way off in the
future.  Unfortunately, I'm unable to locate these files using find.

-- System Information
Debian Release: 3.1
Kernel Version: Linux ani 2.6.10 #2 SMP Thu Jan 6 18:35:37 EST 2005 i686 
GNU/Linux

Versions of the packages findutils depends on:
ii  libc6  2.3.2.ds1-20   GNU C Library: Shared libraries and Timezone


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#291419: findutils: Unable to use find to locate files that have dates in the future

[Wakko Warner]

Andreas Metzler wrote:
 On 2005-01-20 Wakko Warner [EMAIL PROTECTED] wrote:
  Package: findutils
  Version: 4.1.20-4
  Severity: wishlist
 
  I have a system that has a bad clock and files get dates way off in the
  future.  Unfortunately, I'm unable to locate these files using find.
 
 How about this?
 $ touch --date=tomorrow tomorrow ; touch now ; touch --date=yesterday 
 yesterday
 $ find -mmin +0 -or -printf File generated in future: %p%n
 File generated in future: ./tomorrow

I didn't think about +0, however, it's not quite obvious though.  Actually,
I was hoping for a way to see if a file was way off in the future  Like say
in 2007 or so.

It's not a big deal which is why it's wishlist.  I have often wanted a way
to specify seconds as well.  Like before/after $date.

-- 
 Lab tests show that use of micro$oft causes cancer in lab animals


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#291419: findutils: Unable to use find to locate files that have dates in the future

[Wakko Warner]

Andreas Metzler wrote:
 On 2005-01-20 Wakko Warner [EMAIL PROTECTED] wrote:
  I didn't think about +0, however, it's not quite obvious though.
  Actually, I was hoping for a way to see if a file was way off in the
  future  Like say in 2007 or so.
 
 I wouldn't know how to do that.

Without touching a file to a date and using -cnewer, there's not.  Quite
annoying IMO.

  It's not a big deal which is why it's wishlist.
 
 I'll forward it, seems to be a valid request. The most interesting
 problem is probably how to specify this on the commandline, as the
 obvious candidate -mtime -x is already taken.

-fromdate x or -today x ??  =)

  I have often wanted a way to specify seconds as well.
 
 Wishlist request #2. ;-) I assume you want something like in FreeBSD
 (check the description of -atime in
 http://www.freebsd.org/cgi/man.cgi?query=find).

YES!

  Like before/after $date.
 
 Wishlist request#3. -newerXY with Y=t, as in
 http://www.freebsd.org/cgi/man.cgi?query=find.

YES!

heheh, trying to get me to switch to bsd?  =)

-- 
 Lab tests show that use of micro$oft causes cancer in lab animals


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]