Brian May writes:
> I have a patched 1.6.10-2 for sid and jessie, amd64 and i386 at
> https://linuxpenguins.xyz/debian/pool/main/s/schroot/
>
> Haven't had a chance to test it extensively yet, but so far seems to
> work.
Still getting unexpected mount errors; don't have
to test it extensively yet, but so far seems to
work.
--
Brian May
mounts-private.patch is for, it seems to
patch files not in schroot but has references to schroot files.
Do I need the 2nd patch or is the 1st one sufficient?
--
Brian May
l info about processes that
> } use the device is found by lsof(8) or fuser(1).)
Sounds very much like the reason behind #794828, which has been a
constant problem for me.
Are there any workarounds for Jessie?
--
Brian May
Package: src:linux
Version: 3.14.12-1~bpo70+1
Severity: important
With the following nvidia card:
NVIDIA GPU GeForce GTX 660 (GK106) at PCI:1:0:0 (GPU-0)
If I boot 3.12, 3.13. or 3.14 from Debian backports, *and* XWindows is
disabled or otherwise doesn't start, I don't get a working text console
On Sun, Jan 03, 2010 at 11:26:34AM +0100, Bastian Blank wrote:
> On Sun, Jan 03, 2010 at 04:55:27PM +1100, Brian May wrote:
> > On Sun, Jan 03, 2010 at 01:21:55AM +, Ben Hutchings wrote:
> > > I believe we will have Xen hypervisor and Linux dom0 packages, but they
> >
tualisation
extensions.
Like I said previously, I think dropping Xen support is a mistake because KVM
requires QEMU and QEMU seems to have a reputation of being insecure.
--
Brian May
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe
Moritz Muehlenhoff wrote:
Does this error still occur with more recent kernel versions?
I can't remember. The computer has Ubuntu on it now, so the results may
not be relevant anyway...
Feel free to close this bug report if you want.
Brian May
--
To UNSUBSCRIBE, email to d
, F-Secure, that prevents Windows from releasing oplocks
properly. After turning off the firewall, the oplocks get released and
there is no problem. Possibly related to the timing of wpkg being
invoked before system logons too.
So probably "not a bug" as opposed to "fixed in newer v
Package: linux-image-2.6.18-6-686
Version: 2.6.18.dfsg.1-18etch5
Severity: important
Hello,
[I just sent this as an email to [EMAIL PROTECTED], however as it
involves the kernel in Debian/Etch, I felt it wise to submit here too. Upstream
may not be happy with supporting the older kernel version..
http://bugs.debian.org/395971
http://bugs.debian.org/397372
I believe this might be the problem:
snoopy:/swap# diff -u /boot/config-2.6.17-2-xen-686
/boot/config-2.6.18-1-xen-686 | grep POLICE
-CONFIG_NET_CLS_POLICE=y
+# CONFIG_NET_ACT_POLICE is not set
--
Brian May <[EMAIL PROTEC
>>>>> "Brian" == Brian May <[EMAIL PROTECTED]> writes:
Brian> I believe this is related to the following configuration option:
Brian> snoopy:~# less /boot/config-2.6.18-1-xen-686 | grep
CONFIG_XEN_DISABLE_SERIAL
Brian> CONFIG_XEN_DISABLE_SERIA
ld do exactly the same thing as
CONFIG_XEN_DISABLE_SERIAL (but correct me if I am mistaken).
As it is, it would appear that I need to recompile the kernel to get
serial support working.
Thanks.
--
Brian May <[EMAIL PROTECTED]>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a
On Wed, Nov 02, 2005 at 10:38:15AM +1100, Brian May wrote:
> I apologize if this bug is unrelated. I think it might be...
s/I think it might be.../It looks related to me.../
sorry for any confusion.
--
Brian May <[EMAIL PROTECTED]>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with
naled filesystem can get into such a big
mess. Hence I suspect the curruption might be happening at the block
device layer, and unrelated to filesystem.
I do not yet know if I can reproduce this on demand.
I am not running knfs or any other NFS server (contrary to log
messages).
--
Brian May <[EMAIL P
am at lca2005 this week, so don't have access to the
machine (it is turned off) in order to retest it.
--
Brian May <[EMAIL PROTECTED]>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
how the kernel works, but it strikes me as odd
that you would want to make decisions on kernel modules based on what
kernels are installed.
--
Brian May <[EMAIL PROTECTED]>
17 matches
Mail list logo
