Kai Krakow writes:
> Am Sat, 29 Apr 2017 14:39:13 +
> schrieb Alan Mackenzie :
>
>> For a start, I could barely read parts of it, which were displayed in
>> dark blue text on a black background. Setting
>> up /etc/portage/color.map is not the first thing a
Am Sun, 30 Apr 2017 00:56:40 -0500
schrieb R0b0t1 :
> On Sun, Apr 30, 2017 at 12:14 AM, Kai Krakow
> wrote:
> > Am Sat, 29 Apr 2017 14:39:13 +
> > schrieb Alan Mackenzie :
> >
> >> For a start, I could barely read parts of it, which were
On Sun, Apr 30, 2017 at 12:14 AM, Kai Krakow wrote:
> Am Sat, 29 Apr 2017 14:39:13 +
> schrieb Alan Mackenzie :
>
>> For a start, I could barely read parts of it, which were displayed in
>> dark blue text on a black background. Setting
>> up
Am Sat, 29 Apr 2017 20:53:50 -0700
schrieb Ian Zimmerman :
> On 2017-04-30 02:23, lee wrote:
>
> > > Do a --depclean and that will resolve itself.
> >
> > Last time I tried that, it wanted to remove the source of the kernel
> > I'm using, along with other things. It would
Am Sat, 29 Apr 2017 14:39:13 +
schrieb Alan Mackenzie :
> For a start, I could barely read parts of it, which were displayed in
> dark blue text on a black background. Setting
> up /etc/portage/color.map is not the first thing a new user should
> have to do to be able to read
On 2017-04-30 02:23, lee wrote:
> > Do a --depclean and that will resolve itself.
>
> Last time I tried that, it wanted to remove the source of the kernel
> I'm using, along with other things. It would have made sense if I had
> upgraded the kernel, too, but I didn't have the time to do that
6 matches
Mail list logo