Package: openbsd-inetd
Version: 0.20040915-1
Severity: normal
Tags: patch
On *BSD, AF_UNIX socket files permission bits are ignored, but
on linux they're not, and should be created with mode 0777 to
match *BSD behaviour. In order to do that, the included patch
(below) temporarily changes umask
subscribe
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Hi here.
I'm the author of this software, and am very glad there's
some interest in it... thank you for your support.
I prepared a 0.75 version of the package, as available
at http://www.corpit.ru/mjt/tinycdb/tinycdb_0.75.tar.gz --
as a native Debian package. Christian said it's not a
good
Lars Wirzenius wrote:
Package: rbldnsd
Version: 0.995
When testing rbldnsd with piuparts, I get the following error:
0m7.6s ERROR: Package purging left files on system:
/var/lib/rbldns
Lars, care to check whenever a bug has been already reported
before submitting a new one?
See:
Blah. It should Depends: on adduser (or is it Pre-Depends? adduser
is only used in postinst script.)
Also, the same postinst script references getent. While it's a part
of libc6, on which we already depends on, for other libc variations
it might not be the case. For example, libc6-udeb does
Santiago Vila wrote:
On Tue, 14 Nov 2006, Lucas Nussbaum wrote:
[]
Michael, this is just a missing dependency on adduser, which is needed
because adduser is not Essential: yes. Here is a patch:
Yup. I already replied to the original report a few minutes after I received
it. Should I add Cc:
Package: bsdtar
Version: 2.2.4-1
Severity: minor
bsdtar package is placed into wrong section - it's currently
in libs as libarchive, not in utils as it should be.
Apart from obvious but cosmetic issue, this leads to things
like deborphan listing it as orphaned and hence usual
dpkg -P
Package: glibc
Version: 2.7-5
Severity: important
Since 2.7, glibc changed behavour of fflush() wrt pending write in
the FILE* buffer. Before, the pending write data was cleared on
fflush(), now it's keept in the buffer.
As a result, we see some.. interesting stuff, like this:
$ echo foo
While trying to save space in Subject line, I created an
unclear bugreport.
The change in fflush() was with write error only.
Under normal conditions, fflush() writes pending data
just fine AND clears the write buffer. But in case
write(2) errors out, fflush() now does nothing, while
in pre-2.7
$subj.
debian/patches/any/submitted-fileops-and-signals.diff
in glibc package.
See #429021 for details.
The change was made for 2.6-1, at 07 Jul 2007.
/mjt
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Package: libpam-ssh
Version: 1.91.0-5
Severity: critical
A long time ago (circa 1998 or so) I looked at pam-ssh project and
noticied several problems with it. And since it's now in Debian,
the same problems applies to Debian too.
Here's one.
in pam_sm_authenticate() routine, pam_ssh saves
Justin Pryzby wrote:
On Thu, Mar 24, 2005 at 03:55:06PM +0300, Michael Tokarev wrote:
Package: libpam-ssh
Version: 1.91.0-5
Severity: critical
A long time ago (circa 1998 or so) I looked at pam-ssh project and
noticied several problems with it. And since it's now in Debian,
the same problems
A small followup with additional comments.
Justin Pryzby wrote:
[]
It seems that your request can be easily satisfied by using the
reentrant versions of these functions, like getpwnam_r. I'm including
a test file I've been playing with, which indicates that a patch, if
necessary, would be
zze-Beta Testeur LABROSSE A ext RD-CSRD-GRE wrote:
Hi,
I'd read your posts to the bug, and now I wonder what to do. I Add an
url to a patch[1] that seems to reduce number of call to getpwnam(), and
improve the behaviour of all the module. Please tell me if the patch fix
problems you're talking
Matthias Urlichs wrote:
I have a 7-disk raid6 array. Two of the disks have shut down due to a
flaky power supply. I rebooted the system. The degraded RAID didn't come
up.
$ mdadm -A /dev/md7 /dev/hd[bceijkl]1
mdadm: failed to add /dev/hdk1 to /dev/md7: Invalid argument
mdadm: failed to add
The last mdadm change -- 1.9.0-2.1 -- did NOT fix the bug,
but made the situation worse.
rcS.d/S04mdadm-raid is now the FIRST thing the system is
doing when booting. At that stage, /proc is not mounted
(it is mounted later), and in mdadm-raid bootscript, there's
the following code:
if [
Matthias Urlichs wrote:
Hi,
Michael Tokarev:
$ mdadm -A /dev/md7 /dev/hd[bceij]1
This worked.
Matthias, please provide your /etc/mdadm/mdadm.conf
entries for the array in question (/dev/md7). From
the description of your problem it seems it is due
to incorrect content of the array entry
Folks, can we close this bug now?
mdrun and AUTOSTART mess has been sorted out long ago
(the latter really means what it should mean now).
mdrun will not work with whole disks, and isn't supposed
to, and should go away completely.
There's a standard way to use either partitions or
whole disks with
Robert Edmonds wrote at Thu, 12 Jul 2007 18:59:23 -0400:
Package: moreutils
Version: 0.22
Severity: wishlist
Hi, Joey:
I currently have a single binary package called 'lckdo' -- I didn't
realize the upstream author (mjt) was a Debian developer when I packaged
it, however.
What do you
Ralf Hildebrandt wrote:
Package: libcdb-dev
Version: 0.76
Severity: normal
I tried to use pkg-config today and found that libcdb-dev does not
write /usr/lib/pkgconfig/libcdb.pc information (unlike libpcre3-dev
etc).
I wonder why people are using that stupid thing in the first place --
I'm - slowly - catching up with my inbox...
[EMAIL PROTECTED] wrote:
Hello, Thomas.
Michael Tokarev, the author of udns requested me to exclude udns from
Debian Etch, since he claims it is not stable API yet, and should not be
distributed in a system like Debian right now.
Well, it isn't
Neil Brown wrote:
[]
But joggling a usb stick (similar to your use case) would probably be OK
since
it would be hot-removed and then hot-added.
This still needs user-space interaction.
If the USB layer detects a removal and a re-insert, sdb may well come
back a something different (sdp?)
Henrique de Moraes Holschuh wrote:
On Sun, 10 Sep 2006, Marco d'Itri wrote:
[1] by setting FSCKTYPES=none in /etc/default/rcS and 0 in fstab
Yes, that would cripple it into not needing e2fsprogs, all right...
However, not doing any fsck at all is not the right solution. Removing the
fsck
Package: initscripts
Version: 2.86.ds1-38
Severity: normal
When either of RAMRUN or RAMLOCK are set to yes (supposed to
mount /var/run and /var/lock as tmpfs), AND /var is a separate
filesystem (a good thing to do really), mount of /var/run and/or
/var/lock fails, because mountkernfs.sh (which
Package: uucp
Version: 1.07-12
Severity: normal
When upgrading uucp package, the upgrade fails with the
following message:
Setting up uucp (1.07-12) ...
chown: cannot access `/etc/uucp/call': No such file or directory
dpkg: error processing uucp (--configure):
This is due to /etc/uucp/call
[EMAIL PROTECTED] removed from Cc list - don't submit replies
to bugreports as new bugs, ok? ;)]
Peter Palfrader wrote:
On Wed, 08 Jun 2005, Michael Tokarev wrote:
[]
In postinst script, we have:
if [ -n $version ] \
dpkg --compare-versions $version lt 1.07-10
Neil Brown wrote:
On Tuesday April 3, [EMAIL PROTECTED] wrote:
[]
After the power cycle the kernel boots, devices are discovered, among
which the ones holding raid. Then we try to find the device that holds
swap in case of resume and / in case of a normal boot.
Now comes a crucial point. The
Package: apache
Version: 1.3.33-6sarge1
Severity: grave
When upgrading apache (or dpkg-reconfiguring it), ServerName directive
is set to some value (defaults to `localhost'). Before upgrade the
configuration was perfectly valid, with ServerName taken from hostname
apache is running on. After
Tatsuya Kinoshita wrote:
I'm forwarding this bug report to the members of bug#299026, `ITP: tinycdb'.
[]
--- cdb_seek.c~ 2006-08-17 15:02:16.0 +0900
+++ cdb_seek.c 2006-08-17 15:02:43.0 +0900
@@ -75,7 +75,7 @@
/* read the key from file and compare with wanted
Bernhard R. Link agreed to sponsor tinycdb package, which I
prepared at http://www.corpit.ru/mjt/tinycdb/tinycdb_0.76pre2.tar.gz,
if no one steps in till the next Friday.
The tarball includes nss_cdb module still, but I plan to comment
it out for the final 0.76, just to reduce possible problems
tags 605800 + unreproducible
quit
03.12.2010 19:20, Gustavo Moreno wrote:
Package: KVM
Version: 1:0.12.5+dfsg-5
Severity: grave
After upgrading, any KVM virtual machine crashes when it try to start,
althought Qemu machines work fine. AQEMU gui doesn't crash.
I'm runnuing a amd64 kernel,
03.12.2010 23:08, Gustavo Moreno wrote:
Please, excuse my fault about lack of information and misclassification,
also for my mistakes with English. This is my first bug report! I marked
it as serious because I understood that would be a problem that could
affect a lot of users, making their
reassign 605800 linux-2.6 2.6.32-28
severity 605800 normal
merge 604956 605800
thanks
04.12.2010 00:01, Gustavo Moreno wrote:
I've already got a precompiled 64 bit kernel on this machine, namely.
linux-image-2.6.32-5-amd64 version:2.6.32-28
linux-headers-2.6.32-5-amd64
reassign 310440 busybox-udeb
thanks
the bug is about busybox-udeb: busybox and busybox-static
enables mktemp applet.
/mjt
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
reassign 316847 busybox-udeb
thanks
the bug is about busybox-udeb.
/mjt
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Package: dovecot-common
Version: 1:2.0.8-1~2.gbp45a01a
Severity: normal
Tags: experimental
(report against unreleased version)
When starting dovecot for the first time, it refuses to start
(and even doveadm complains) like this:
Starting IMAP/POP3 mail server: dovecotdoveconf: Fatal: Error in
Package: dovecot-common
Version: 1:2.0.8-1~2.gbp45a01a
Severity: normal
Tags: experimental
(report against unreleased package)
dovecot-common inctalls /etc/dovecot/conf.d/20-pop3.conf
and /etc/dovecot/conf.d/20-imap.conf which belong to
subpackages.
The result of this is that when only -common
Package: dovecot-common
Version: 1:2.0.8-1~2.gbp45a01a
Severity: normal
Tags: experimental
(report against unreleased package)
When starting a freshly-installed dovecot, it fails to start,
attempting to listen on each port twice:
Starting IMAP/POP3 mail server: dovecotError:
10.12.2010 18:06, Michael Tokarev пишет:
Package: dovecot-common
Version: 1:2.0.8-1~2.gbp45a01a
Severity: normal
Tags: experimental
(report against unreleased package)
When starting a freshly-installed dovecot, it fails to start,
attempting to listen on each port twice:
Starting
Package: roxterm
Version: 1.20.7-1
Severity: normal
With the new version, which changed window title by default
from %s to ROXterm: %s (so that all window names are now
different from what they were before), there's no way to
change the format in the configuration, but only per-window
(menu Edit
24.01.2011 19:44, Tony Houghton wrote:
With the new version, which changed window title by default
from %s to ROXterm: %s (so that all window names are now
different from what they were before), there's no way to
change the format in the configuration, but only per-window
(menu Edit - Window
26.01.2011 00:25, Moritz Muehlenhoff wrote:
Package: kvm
Severity: grave
Tags: security
Please see the following entry in the Red Hat bugzilla:
https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2011-0011
Yes, I've seen this even before CVE ID were assigned.
The impact is not entirely
On 26.01.2011 11:25, Julien Cristau wrote:
On Wed, Jan 26, 2011 at 08:56:06 +0300, Michael Tokarev wrote:
Second, this is an intended behavour. Emty vnc password
meant to be no authentication, not a lockdown. When you
start it without specifying a password it lets everyone
in.
Intended
Please excuse me for late reply - I missed your email initially somehow.
28.01.2011 00:59, Moritz Mühlenhoff wrote:
[]
Thanks for the verbose explanation. I've updated the Debian
Security Tracker.
While we're at it; could you please also look into
Package: etherboot-qemu
Version: 5.4.4-7
Severity: wishlist
The ROMs in etherboot-qemu package are built with the usual
boot from network or local pause which causes unnecessary
boot delays when booting virtual machines, where the choice
(where to boot from) is controlled in the qemu command
tags 612105 + unreproducible moreinfo
thanks
06.02.2011 02:09, Jonathan Nieder пишет:
Package: qemu-kvm
Version: 0.13.0+dfsg-2
Severity: important
Hi,
See [1] for the war story. When I boot the HURD without passing
-no-kvm-irqchip on the command line, the system usually will
print
06.02.2011 20:48, Jonathan Nieder wrote:
How about trying one of supported kernels first, instead
of (ab)using a development snapshot of the kernel?
Okay, will try. (Is testing kernels before they flow into
Debian really abuse?)
No, that's not what I mean. If it looked harsh to you,
Package: jabberd14
Version: 1.6.1.1-5+b1
Severity: normal
jabberd error reporting is nearly non-existing.
For example, access denied opening user profile
.xml file is silently ignored (returning
unauthorized to client without a way to
understand what's wrong, only strace on the
server helps).
: no reportbug configuration found. Proceeding in novice mode.
Detected character set: UTF-8
Please change your locale if this is incorrect.
Using 'Michael Tokarev m...@tls.msk.ru' as your from address.
Getting status for jabberd14...
[...]
(1-12/12) Is the bug you found listed above [y|N|b|m|r|q|s|f
tags 612775 + moreinfo
thanks
10.02.2011 18:34, Michal Suchanek wrote:
Package: qemu-kvm
Version: 0.12.5+dfsg-5
Severity: normal
Hello
gPXE does not work when loaded with Etherboot on an e1000 or virtio
card.
I'm not sure I understand this.
Since Etherboot is much older the error
tags 613413 + moreinfo unreproducible
thanks
14.02.2011 19:24, Xavier Martin wrote:
Package: qemu-kvm
Version: 0.12.5+dfsg-5
x@locahost:~$ kvm -m 1024 -cdrom x.iso -drive file=w.img,if=scsi,boot=on
-nographic -vnc :0
kvm: /tmp/buildd/qemu-kvm-0.12.5+dfsg/hw/lsi53c895a.c:596: lsi_reselect:
Adding some info about an oldish bugreport.
FWIW, but in 0.14 qemu-kvm (with seabios
version 0.6.1.2) I can't reproduce this
problem anymore, so it appears to be fixed.
So I'll close this bugreport by uploading
0.14 version.
Thanks!
/mjt
--
To UNSUBSCRIBE, email to
tags 607391 + moreinfo unreproducible
thanks
[Somehow I didn't see the bugreport - neither of the
messages reached me. Dunno why]
Richard Kettlewell wrote at Mon, 07 Feb 2011 22:12:18 +:
There is actually a file in /lib which can help achieve this. I used
these commands:
# cp
23.02.2011 23:10, Netvalue Support wrote:
I found /etc/udev/rules.d/65-kvm.rules on some of my systems, which I
had to remove. These started off as Etchnhalf and were previously
upgraded to Lenny; systems that started off as Lenny were fine. But to
muddy the waters a little, I've also had
Package: util-linux
Version: 2.17.2-9
Severity: normal
Tags: patch
unshare utility from util-linux segfaults when given an invalid
or incomplete (abbreviated) long option. This is because the
option array in sys-utils/unshare.c:main() is not NULL-terminated.
The attached patch fixes the issue,
Package: lxc
Version: 0.7.2-1
Severity: normal
Tags: upstream
when building lxc from source, it's impossible to re-build the
package after running ./debian/rules clean. This is because
config/Makefile.am has this:
distclean:
@$(RM) -f compile config.guess config.sub depcomp install-sh
16.12.2010 22:40, Yves-Alexis Perez wrote:
[]
There's no such thing as internal script. By default qemu - given
-net tap as above - _creates_ a network device, and runs the script
specified only _after_ the device is created. Here, you don't have
permission to _create_ a network device to
Package: squeeze
Version: 0.2.3-8
Severity: normal
Tags: squeeze
When trying to open any rar archive squeeze segfaults immediately
with a SIGSEGV error, and kernel reports just that:
[138304.063587] squeeze[7792]: segfault at 0 ip (null) sp ff92994c
error 14 in squeeze[8048000+23000]
19.12.2010 10:09, Yves-Alexis Perez wrote:
On dim., 2010-12-19 at 01:07 +0300, Michael Tokarev wrote:
When trying to open any rar archive squeeze segfaults immediately
with a SIGSEGV error, and kernel reports just that:
[138304.063587] squeeze[7792]: segfault at 0 ip (null) sp
Package: extlinux
Version: 2:4.02+dfsg-7
Severity: serious
Tags: squeeze
extlinux-update script quietly overwrites /etc/default/extlinux file
on each invocation. The file in question, according to the Policy,
is a configuration file, so the local changes made to this file should
be preserved. I
Package: extlinux
Version: 2:4.02+dfsg-7
Severity: important
Tags: squeeze
update-extlinux script modifies boot-related files in unsafe ways,
which is a good way to make system unbootable: it re-creates
several files in /boot/extlinux/ by zeroing the content at start
and adding information to
19.12.2010 14:31, Daniel Baumann wrote:
On 12/19/2010 12:25 PM, Michael Tokarev wrote:
extlinux-update script quietly overwrites /etc/default/extlinux file
on each invocation. The file in question, according to the Policy,
is a configuration file, so the local changes made to this file should
03.03.2011 00:31, Roland Dreier wrote:
Package: qemu-kvm
Version: 0.14.0+dfsg-1~tls
Severity: important
I'm running a 32-bit guest (Xubuntu 10.04 to be precise) on a
64-bit host with the command line:
kvm -drive file=xubuntu.img,if=virtio,format=qcow2,boot=on -net
nic,model=virtio
04.03.2011 23:57, Philippe Latu wrote:
I'm encountering initialization problems when using the '-vga vmware' option.
[]
All these VMs run fine without the '-vga vmware' option.
vmware isn't the best-tested virtual device out there, I'm afraid,
but it shouldn't be _that_ broken.
With 0.14,
07.03.2011 01:00, Pierre Bernhardt wrote:
Package: debian-installer
Severity: whishlist
Tags: d-i
Latest debian installer on Squeeze Iso disk debian-6.0.0-amd64-BD-1.iso used
to
install new computer.
At the level of creating md devices it is not possible to add an bitmap as I
can
do
tags 237351 + moreinfo
thanks
Replying to a several-years-old email.
11.03.2004 08:36, Joshua Kwan wrote:
Package: busybox-cvs
Severity: normal
Within the d-i initrd, ash loves to randomly quit while i'm typing a
command out. It is vastly annoying. I don't know what the cause is, but
I
07.07.2010 15:23, Taisuke Yamada wrote:
Package: busybox
Version: 1:1.15.3-1
Severity: wishlist
Because current debian build of busybox (and busybox-static) does not
include 'cttyhack' and 'setsid', it is impossible to use ^C and other
job control feature in initramfs shell.
-
16.01.2006 12:39, Colin Watson wrote:
Package: busybox-udeb
Version: 1:1.01-4
Severity: wishlist
Please enable CONFIG_GETOPT in config-udeb and config-udeb-linux. I need
this in order to merge Kickstart support; it's not feasible to do this
properly in shell without the help of getopt (I
10.03.2011 17:09, Otavio Salvador wrote:
On Thu, Mar 10, 2011 at 12:12, Colin Watson cjwat...@debian.org wrote:
On Thu, Mar 10, 2011 at 02:37:20PM +0300, Michael Tokarev wrote:
Isn't it sufficient to use getopts ash built-in?
No, getopts can't deal with long options, which Kickstart requires
Version: 1:1.17.3-8
10.02.2002 17:32, Vincent Beffara wrote:
Package: busybox-static
Version: 1:0.60.2-3.1
Severity: normal
I'm trying to build a boot CD using initrd and busybox as a shell. The
initrd contains :
[]
exec /sbin/init
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
severity 609231 wishlist
retitle 609231 filename parser in qemu chokes on colons
tags 609231 + upstream confirmed
thanks
07.01.2011 18:59, Michal Suchanek wrote:
Package: qemu-kvm
Version: 1:0.12.5+dfsg-5
Severity: normal
Apparently kvm cannot
convert the result into our native
unsigned long by truncating the most significant part if
necessary. This way, we will still have proper least
significant part, which is enough for comparison with
previous value of the same nature, and substraction gives
good result.
Signed-off-by: Michael
Christophe Benz wrote:
Experimental package kvm 88+dfsg-3 resolved the bug for me.
JFYI: kvm package is dead. It should be removed from
all the archives completely.
/mjt
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
Dmitry Torokhov wrote:
[]
This is exactly what happens, to me and to the original bug reporter --
we both are running 32bit userspace and 64bit kernel.
[]
Does the following patch fixes it for you guys?
No, Dmitry, it does not. It's buggy.
With this patch applied, the bits are all completely
Dmitry Torokhov wrote:
On Sun, Jan 10, 2010 at 02:01:08AM +0300, Michael Tokarev wrote:
Dmitry Torokhov wrote:
[]
This is exactly what happens, to me and to the original bug reporter --
we both are running 32bit userspace and 64bit kernel.
[]
Does the following patch fixes it for you guys
Stefano Zacchiroli wrote:
Dear maintainer,
I've prepared an NMU for qemu-kvm (versioned as 0.11.0+dfsg-1.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.
It's fixed in git on collab-maint for quite some time ago,
in `mjt-changes' branch, by
Martin Pitt wrote:
Michael Tokarev [2009-12-25 1:51 +0300]:
Not really :( We print in groups of longs so it is either 32 or 64 bits
worth of data per number.
Ok, I stand corrected. I verified the issue with 32bit kernel, and
there, hald works as expected, listing `synaptics' as x11_driver
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Never mind. I checked the Debian packages page, looked at the readme and
discovered my error. I had assumed that qemu-kvm added kvm to the qemu
package when in fact it replaces it, but also requires a different
command to start.
Can you elaborate
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Michael,
You states that your package embeds source code from
both qemu and kvm. This is wrong. Kvm *is* qemu, just
another variant of it, modifications to qemu to support
native CPU execution on CPUs with virtualization extensions.
The two
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Actually this action was useful and still may be.
The problem here is that there are other virtualization solutions
(virtualbox, vmware and others) who may use the same CPU support
as kvm uses. At least in the past, up to and including kernel
tags 528077 + moreinfo unreproducible
thanks
Bastian, is the problem you reports in #528077 is still
relevant for current qemu-kvm (0.11.0 and above)? I tried
using XEN in a kvm guest even before version 0.84 (against
which you filed the original bugreport), I think it was 0.81
(I might be
tags + moreinfo unreproducible
thanks
Marcus, can you please tell me what's your (host) graphics card
and host kernel version? I suspect the problem really is not
in kvm but in host video driver, but I might be completely wrong.
There are several points about this issue.
o in 0.88 and 0.11.0,
Adrian Irving-Beer wrote:
Package: qemu-kvm
Version: 0.11.1+dfsg-1
Severity: serious
Justification: Policy 3.5
In Debian bug #566028, I reported that the latest version of qemu-system
had an unstated dependency on libgssapi_krb5.so.2. It seems that
qemu-kvm now has the same dependency
Michael Tokarev wrote:
Michael Goetze wrote:
Package: qemu-kvm
Version: 0.11.1+dfsg-1
Severity: important
I'm trying to install virtual machines with FAI, and for this purpose
have installed a full FAI infrastructure (using dnsmasq) on my host
system, listening on br0. Currently I'm
Package: nsd
Version: 2.3.7-1.1
Severity: security
In /etc/init.d/nsd script there's a construct (repeated twice):
[ -n ${nsd_user} ] chown ${nsd_user}: ${dbfile}
where dbfile defaults to /var/lib/nsd/nsd.db, or in chroot, and
the parent directory of it (/var/lib/nsd) is owned by
Jan Christoph Nordholz wrote:
Hi Michael,
(the following holds for both autofs v4 and v5)
usually the daemon creates these directories on startup and removes
them on exit. If you do not want that to happen, it suffices to
mark the directory as u-w:
] r...@apocatequil:/etc# grep ^/misc
Jan Christoph Nordholz wrote:
Hi,
As I mentioned before, the ONLY way to stop it from
removing the top-level dir is to chattr+i it.
ah, autofs4 indeed removes the directory even without write permission
(v5 doesn't), I thought I'd checked that, too. But this behaviour has
been around for
Thadeu Lima de Souza Cascardo wrote:
Hello, folks.
Hello.
Thank you for bringing this issue up again.
While udns has no entered etch or lenny, we should reconsider that
situation in the case of squeeze. Some software in Debian depends or may
be improved while depending on udns.
tags 581355 + pending
thanks
Örjan Persson wrote:
Package: qemu-kvm
Version: 0.12.3+dfsg-4
Severity: important
Tags: squeeze sid
After upgrading kvm and using the version in lenny-backports, KVM fails
to start and giving a Cannot boot from non-existent NIC error.
I found this problem
Package: util-linux
Version: 2.16.2-0
Severity: wishlist
It's been over 12 years already since cfdisk is built against
libslang. It can be built either againt libncurses or libslang.
The interface it shows is basically the same.
Reasoning:
o libslang2 can be made optional, since the only
19.05.2010 12:52, Vladimir Kozhukalov wrote:
I've included sid repositories in my /etc/apt/sources.list
(debhttp://ftp.debian.org/debian sid main non-free contrib) and updated my
cache (aptitude update)? but there is no new package
qemu-kvm_0.12.4+dfsg-1, but only 0.12.3+dfsg-4 is the newest
20.05.2010 22:20, Matthew Ernisse wrote:
Package: qemu-kvm
Version: 0.12.4+dfsg-1
Severity: important
We originally noticed this problem on Ubuntu Lucid (lp:579596) but it appears
to also
effects the current version of qemu-kvm (which we have backported to lenny).
Upon booting a VM and
Package: qemu-kvm
Version: 0.12.4+dfsg-1
Severity: important
Tags: patch upstream pending
There's upstream patch for a data corruption that occurs
with 1Tb disk images and virtio-blk. Fix is available at
http://marc.info/?l=qemu-develm=127436114712437 .
/mjt
--
To UNSUBSCRIBE, email to
21.05.2010 16:01, Michael Tokarev пишет:
This is a guest issue, not kvm issue. See
http://marc.info/?l=qemu-develm=127439130431895
And indeed, I tried to set up winNT on two other
machines here, it fails the same way during boot,
with the same STOP: 0x0003 error (incorrect
multi-processor
21.05.2010 16:14, Michael Tokarev wrote:
21.05.2010 16:01, Michael Tokarev wrote:
This is a guest issue, not kvm issue. See
http://marc.info/?l=qemu-develm=127439130431895
And indeed, I tried to set up winNT on two other
machines here, it fails the same way during boot,
with the same STOP
21.05.2010 16:36, Harald Dunkel wrote:
On 05/12/10 12:41, Harald Dunkel wrote:
Hi folks,
I am trying to run Solaris 10u8 as a guest in kvm (kernel
2.6.33.2). Problem: The virtual network devices don't work
with this Solaris version.
Short update: Virtualbox 3.1.6 seems to be more reliable in
22.05.2010 10:29, Harald Dunkel wrote:
It took me some time to get back into Solaris, too. To change the
network driver:
After changing the kvm configuration you should boot Solaris at usual.
It will complain about some services not being run, and put you into
single user mode.
It does not
I opened a bugreport against upstream qemu, see
https://bugs.launchpad.net/qemu/+bug/584155
Apparently upstream is _very_ interested in this... :(
/mjt
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
tags 579751 + unreproducible
severity 579751 minor
thanks
22.05.2010 11:29, Michael Tokarev wrote:
22.05.2010 10:29, Harald Dunkel wrote:
[]
I left `ping -f $solaris-ip' process running for whole
night - it were still running in the morning without any
visible issues, at 100% CPU usage (2
06.05.2010 04:29, Gary Dale wrote:
When I use virt-manager to start the Windows XP virtual machine, the
screen saver works normally. However, I'm back having to use the kvm
command to launch it and the screen power saver issue is back.
Can you please try setting SDL_VIDEO_ALLOW_SCREENSAVER=1
1 - 100 of 2525 matches
Mail list logo
