In article ,
David Wright wrote:
> On Mon 16 Oct 2023 at 16:05:48 (-0700), Bill Brelsford wrote:
>> The latest version of procps (2:4.0.4-2) depends on libsystemd0, so
>> upgrading 2:4.0.3-1 to it causes libsystemd0 to be installed. But
>> on my sysvinit system it confl
The latest version of procps (2:4.0.4-2) depends on libsystemd0, so
upgrading 2:4.0.3-1 to it causes libsystemd0 to be installed. But
on my sysvinit system it conflicts with libelogind0:
libelogind0 : Conflicts: libsystemd0 but 254.5-1 is to be installed
Should I let libsystemd0 replace libelo
On Sat Aug 31 2019 at 03:40 PM +0200, Stefan Krusche wrote:
> Am Freitag, 30. August 2019 schrieb Bill Brelsford:
> > My 64-bit buster installation was created using its installer, with
> > / and /home partitions in an encrypted logical volume (sda3_crypt).
> > On shutdown, i
they hung indefinitely.
Anyone else seeing this? Any suggestions or workarounds (other
than systemd)? Thanks..
--
Bill Brelsford
wbr...@k2di.net
On Wed Sep 12 2018 at 10:10 PM +0200, Sven Joachim wrote:
> On 2018-09-11 19:05 -0700, Bill Brelsford wrote:
>
> > I recently upgraded the sid installation on an i386 machine. With
> > udev upgraded to 239-8, many devices are no longer detected during
> > boot, e.g.
ting a bug report. Anyone else? Any other ideas?
Thanks..
--
Bill Brelsford
wbr...@k2di.net
On Fri Oct 13 2017 at 01:20 AM +0200, deloptes wrote:
> Bill Brelsford wrote:
>
> > This doesn't explain why I got the EBDA message in the first place,
> > but all is working now..
>
> once again the question: why not use grub?
Lilo has always met my needs well,
On Mon Oct 09 2017 at 12:50 AM +0200, Bill Brelsford wrote:
> After the stretch 9.2 kernel upgrade to 4.9.0-4, lilo gives, at
> boot, "EBDA is big; kernel setup stack overlaps LILO second stage"
> and freezes.
Problem solved. This is a dual-boot system, with the Win 10
bootloa
e i686 with
similar configuration, except that the failing one installs the
boot loader in a partition rather than in the MBR.
Suggestions?
--
Bill Brelsford
wbr...@k2di.net
On Wed Aug 19 2015 at 11:40 AM +0200, Darac Marjal wrote:
> On Tue, Aug 18, 2015 at 09:32:24AM -0700, Bill Brelsford wrote:
> > Recent security updates on jessie (i486) have failed:
> >
> > # aptitude update
> > ...
> > # aptitude -DPR safe-upgrade
>
Recent security updates on jessie (i486) have failed:
# aptitude update
...
# aptitude -DPR safe-upgrade
The following packages will be upgraded:
libgdk-pixbuf2.0-0 libgdk-pixbuf2.0-common
...
Reading changelogs... Done
(Reading database ... 72512 files and dir
ounds?
Thanks.. Bill
--
Bill Brelsford
wbr...@k2di.net
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/e1xt4mg-0006pd-hw...@k2di.net
not being called.
Bug? Or do I have something configured wrong?
--
Bill Brelsford
w...@k2di.net
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/e1ungbr-0003sp-md@k2di.net
Since upgrading to kernel 2.6.38, I've been experiencing freezes
in X. After startup, things are normal for a matter of minutes;
then most keypresses and mouseclicks have no effect until focus
is moved to another window, at which time the screen "catches up."
Once it starts it continues until X is
Another problem after recent X updates in sid: switching back to
the X virtual terminal (e.g. via alt-F7) results in the contents of
the cut/paste buffer being pasted into the active X window.
Anyone else see this behavior? A bug in xserver-xorg (1:7.3+2)?
--
Bill Brelsford
[EMAIL PROTECTED
On Tue Sep 11 2007 at 10:37 PM -0700, Bill Brelsford wrote:
> After a recent update to sid, incoming rlogin and rsh connections
> ignore /etc/hosts.equiv (and ~/.rhosts) and ask for a password or
> fail with "permission denied". The rsh-server (and -client)
> packages were n
0.99.7.1-4. I'm not sure one of them is
the culprit (and see no new bugs filed for them), but pam is
involved in the authentication process.
Is this a known problem? Anyone else experiencing it?
--
Bill Brelsford
[EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
wi
FDC 0 is a post-1991 82077
I can, however, mount and use the floppy. There is no problem
under sarge (e2fsck 1.37). And, with no floppy in the drive,
e2fsck correctly complains "No such device..".
Suggestions?
--
Bill Brelsford
[EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [
18 matches
Mail list logo
