Dear Kai,
well, then what is different and why can't that be upstreamed? And is there a
known case, where the driver provided by Debian doesn't work (if so, is there
a
bug filed)?
Perhaps you are right, given the time and the skills and the hardware
and the person skilled and motivated
Thanks, Julien.
I see you've made r8168-source package as well - nice.
I will introduce support for module-assistant if we agree on package inclusion.
I would second that as I have another problem with r8169 which doesn't
support support resuming from suspend/hibernate. I've been using r8168
inexperienced with git so I couldn't figure out how to
access your repository.
Is my Alioth account onlyjob-guest allowed to push?
Anyway you're the boss so I'm not going to do anything without you
permission (and instructions).
It appears to me that you might want to make a separate branch from my
it is to be a co-maintainer.
Please let me know of any procedures you believe we should agree on.
All the best,
Dmitry.
On 19 September 2011 20:45, Arno Töll deb...@toell.net wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Dmitry,
On 18.09.2011 16:25, onlyjob wrote:
When you mention
-
Hash: SHA1
On 18.09.2011 06:21, onlyjob wrote:
Recent package from http://mentors.debian.net works on 3.0.0-1-amd64
I am aware, you can see my package on [1]. Its pretty much complete but
I am not finished yet.
[1]
http://anonscm.debian.org/gitweb/?p=collab-maint/flashcache.git
MESSAGE-
Hash: SHA1
On 18.09.2011 14:03, onlyjob wrote:
No, I wasn't aware of yours...
I reckon we've been working independently
I just completed my own... There are definitely some similarities but
also differences in the way we did it.
I briefly looked at yours. It has some technical
Hi,
No so long ago flashcache's master branch was updated for
compatibility with Linux kernel 3.0
Recent package from http://mentors.debian.net works on 3.0.0-1-amd64
Regards,
Dmitry.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe.
Apparently it seems to be an SYSLINUX issue.
As explained in
PXE_FAQhttp://pxe.dev.aboveaverageurl.com/index.php/PXE_FAQ#I_used_PXELINUX_to_boot_memtest86.2B.bin.2C_but_all_it_does_it_print_.228000.22_over_and_over_again.21
:
I used PXELINUX to boot memtest86+.bin, but all it does it print 8000
Package: base-files
Version: 6.0squeeze1
Severity: wishlist
Tags: patch
AGPL-3 missing from /usr/share/common-licenses
AGPL-3
Description: Binary data
Hi,
As a matter of fact MEMTEST is a quite useful feature.
We ask to enable it not for what it cannot do, but for what it can.
For example ECC in hardware is not useless even though it doesn't
catch all possible errors.
As I demonstrate in
Package: perl-base
Version: 5.10.1-14
Severity: normal
There is a memory leak in 'use v5.8;' statement. (Version or notation not
important)
Can be reproduced using following command:
bash -c 'ulimit -v 7; perl -e eval q{use v5.8} while 1;'
Execution of this command terminates with 'Out
11 matches
Mail list logo
