On Wed, 10 Jul 2019 09:49:43 +1000, Adam Carter wrote:
> > Same here, it's been reported on b.g.o and dropping the two patches
> > linked to there into /etc/portage/patches/sys-apps/systemd-242-r4/ and
> > re-emerging systemd fixed it.
> >
>
> Thanks Neil - that fixed both boxes.
>
> For
On Wed, Jul 10, 2019 at 3:56 AM Neil Bothwick wrote:
> Same here, it's been reported on b.g.o and dropping the two patches
> linked to there into /etc/portage/patches/sys-apps/systemd-242-r4/ and
> re-emerging systemd fixed it.
>
Thanks Neil - that fixed both boxes.
For anyone that wants to
> I've just tried upgrading mariadb again while watching it, and got similar
> results. I did notice that an error notice came up about being unable to
> store
> a message received via POP3, which is my main incoming source. I can't
> quote
> exactly because the notice disappeared too soon.
>
>
On Fri, Jul 5, 2019 at 10:14 AM Vladimir Romanov wrote:
>
> Fdisk can not work with drives larger than 2TB. Your drive may be slightly
> (10 mb) larger than that, so the result. For such disks you need not Fdisk,
> but GPT programs.
Correction: modern fdisk provided by util-linux supports
On 09/07/19 02:34, Adam Carter wrote:
> lsdrv looks like lsblk, it's just that it handles afaik pretty much
> everything - starts with the disk, then lists any partitions, any lvm's,
> any raids, etc etc.
>
>
> What does lsdrv have that lsblk is missing?
Looking at "man lsblk",
On Tuesday, 9 July 2019 19:45:25 BST Wols Lists wrote:
> On 09/07/19 11:38, Peter Humphrey wrote:
> >> Eventually I noticed that mariadb had been upgraded, so I masked the
> >> latest
> >>
> >> > version and reverted to the older one. Lo! and Behold! Kmail sprang
> >> > back
> >> > into life.
> >
On 2019-07-09, Ian Zimmerman wrote:
> On 2019-07-05 14:25, Grant Edwards wrote:
>
>> -grub.cfg--
>> timeout=10
>> root=hd0,1
>>
>> menuentry 'vmlinuz-4.19.52-gentoo' {
>> linux /boot/vmlinuz-4.19.52-gentoo root=/dev/sda1
>> }
>>
>>
On 09/07/19 11:38, Peter Humphrey wrote:
>> Eventually I noticed that mariadb had been upgraded, so I masked the latest
>> > version and reverted to the older one. Lo! and Behold! Kmail sprang back
>> > into life.
> Today's update included dev-db/mysql-connector-c-6.1.11-r1 to -r2, so I tried
>
Hi all,
This all happens on an up to date openrc machine with the profile
default/linux/amd64/17.0/desktop/plasma
I've added a few hooks to the emerge process via the bashrc that is in
/etc/portage. One of the things I do upon emerge failure is kill vlc,
which would have been playing a
On Tue, 9 Jul 2019 11:19:22 +1000, Adam Carter wrote:
> Happened on 2/2 systems tested. You can bring the interface up manually
> if you're at the console.
>
> Error looks like
> systemd-networkd[252]: enp5s0: Could not bring up interface: Invalid
> argument
>
> Looks like its fixed in git
>
On 2019-07-05 14:25, Grant Edwards wrote:
> -grub.cfg--
> timeout=10
> root=hd0,1
>
> menuentry 'vmlinuz-4.19.52-gentoo' {
> linux /boot/vmlinuz-4.19.52-gentoo root=/dev/sda1
> }
>
> menuentry 'vmlinuz-4.14.83-gentoo' {
> linux
Howdy,
I finished a recent update which included a lot of QT packages. I did
my usual logout and log back in procedure and my second display, what I
use to watch TV with, was not working. At first I thought it might be
the splitter box but after connecting directly and it still not working,
I
On Saturday, 22 June 2019 10:07:46 BST Peter Humphrey wrote:
> Hello lists,
>
> Yesterday's routine update took mariadb from 10.3.16 to 10.4.6. When I came
> to look at my emails today, kmail couldn't do anything. To start with, it
> was stuck in an endless, looping attempt to display the current
13 matches
Mail list logo
