The porn industry has admitted that amateur home videos are giving the industry
a run for their money http://tobiasmeyer.gmxhome.de/lol.html
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
on media is for.
Chuck Zmudzinski
to
update old device drivers so they are compatible with the
modern version? Does the Xen virtual keyboard need to be
managed by udev? Is there a simple way to disable incompatible
devices so udev ignores them?
Chuck Zmudzinski
On 8/24/2021 1:12 PM, Ben Hutchings wrote:
On Tue, 2021-08-24 at 10:56 -0400, Chuck Zmudzinski wrote:
On 5/24/2021 3:30 AM, Michael Biebl wrote:
Hi Phillip
Am 24.05.2021 um 06:19 schrieb Cyril Brulebois:
trigger to cold plug all devices. Both scripts are set -e. The Xen
Virtual Keyboard
I could be wrong about that.
I read the discussion Philip had with the Xen developers and they
seemed to want to keep the Xen keyboard driver as it is.
Chuck
On 8/25/2021 12:45 PM, Chuck Zmudzinski wrote:
On 8/24/2021 7:12 PM, Ben Hutchings wrote:
On Tue, Aug 24, 2021 at 03:27:19PM -0400, Phillip Susi wrote:
Ben Hutchings writes:
I think a proper fix would be one of:
a. If the Xen virtual keyboard driver is advertising capabilities it
��ï
ailed. The build was checking symbols when
it failed.
This will take a little while because it takes over an hour to build the
kernel on my system.
Chuck
On 8/25/2021 4:16 PM, Phillip Susi wrote:
Chuck Zmudzinski writes:
If it doesn't work, I am also willing to try approach a by patching
the Linux kernel xen-kbdfront driver by removing the for loops that
advertise those 654 keys. I tend to agree with Philip that this is
totally unnecessary
in many years, and I never built a Debian
kernel before.
All the best,
Chuck
On 8/26/2021 8:01 AM, Chuck Zmudzinski wrote:
On 8/24/2021 7:12 PM, Ben Hutchings wrote:
The current limit on the environment of a uevent appears to be 2 KB
(UEVENT_BUFFER_SIZE defined in ).� That seems like it
*might* be easier to change, so long as user-space doesn't have a
similar
een tested to apparently fix this bug and
the bug has been elevated to important and tagged patch and upstream,
AFAICT there is no action yet upstream or anywhere else after more than
three weeks. Is this patch dead as a possible fix for this bug?
Best wishes,
Chuck
nstall
Bullseye in a Xen HVM domain to the workarounds that have been
identified for this problem that has not yet been fixed?
Regards,
Chuck Zmudzinski
On 8/26/2021 7:18 PM, Debian Bug Tracking System wrote:
Processing commands for cont...@bugs.debian.org:
severity 983357 important
Bug
On 2/9/2022 3:43 PM, Paul Gevers wrote:
Hi,
Subject: 983357: Why is it not mentioned in bullseye release notes /
installation guide?
For at least the release notes, because nobody asked the editors to
include it.
On 09-02-2022 21:04, Chuck Zmudzinski wrote:
However, this is a well-known
On 2/10/2022 3:27 AM, Paul Gevers wrote:
Hi Chuck,
On 10-02-2022 01:34, Chuck Zmudzinski wrote:
The problem as I see it is that the debian installer team is already
aware of the problem and has been aware of it for over six months
because #983357 is marked as affecting d-i. So I do not
On 2/10/22 3:27 AM, Paul Gevers wrote:
On 10-02-2022 01:34, Chuck Zmudzinski wrote:
Do I need to file another bug in addition to #983357 to get this
problem listed on the bullseye (and also RC versions) d-i errata pages?
This is the most establish process, so yes, I suggest you just go
to use the standard debian config for the
latest kernel, or does the installer have some special requirements?
Thanks for any help,
Chuck
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
On Fri, 2012-11-02 at 11:09 +0100, Cyril Brulebois wrote:
> chuck adams (31/10/2012):
> > Problem occurred on reboot into debian wheezy in that login
> > display screen is a mess. Unusable, unreadable and just plain
> > ugly. I can take a digital photo if that wou
command
Any suggestions on the options to the boot? Is
'grub' overriding the options?
thanks,
chuck
--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: htt
I booted a live-CD version of ubuntu 12.10 (sorry)
and mounted the debian partition /dev/sda1
Went to
/etc/inittab
and changed
id:2:initdefault
to
id:1:initdefault
and rebooted. System brought up the mangled screen
instead of an ASCII display.
This get us any further?
chuck
--
To
not do) that was effective (or
ineffective)?
Installation of the three packages using apt-get fixed the problem.
* What was the outcome of this action?
Fixed and working as advertised.
* What outcome did you expect instead?
thanks in advance,
chuck
-- Package-specific info:
Boot
functional.
chuck
-- Package-specific info:
Boot method:
Image version:
Date:
Machine:
Partitions:
Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it
Initial boot: [ ]
Detect network card:[ ]
Configure network: [ ]
D
stems and the exact
files that were configured differently. So many bugs and so
little time.
thanks and I hope this helps,
chuck adams
--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.or
at sgi at one time.
Now spending my time writing books and the current one is
on debian.
FYI
chuck
P.S. I am about to redo the inst using eth0 and see that
the daily-build netinst #3 for today gives the same results
as before. I don't mind doing all the experiments needed
to resolve
23 matches
Mail list logo
