[gentoo-user] Building a new root for my Gentoo: Permission denied?

Hi, got a mysterious error message this morning (still building a new root...) One of the updates was gnutls: It ends with: ... checking for i686-pc-linux-gnu-pkg-config... /usr/bin/i686-pc-linux-gnu-pkg-config checking pkg-config is at least version 0.9.0...

Re: [gentoo-user] logrotate ... won't!

Peter Humphrey wrote: > On Sunday 12 Feb 2017 17:32:30 Mick wrote: > >> Thanks Alexander, it pays going back to basics ... for some reason my >> cronie service was not running. o_O >> >> I added it to default runlevel and hopefully it will do its magic from now >> on. > I'm glad I'm not the only

Re: [gentoo-user] Bad luck with new installation: Compilation issues (eudev)

Miroslav Rovis [17-02-12 14:03]: > On 170207-01:11+0100, meino.cra...@gmx.de wrote: > > Hi Alexander, > > > > it was documente in a bugreport by someone else. > > I did exactle the same. > Great, no everybody interested use the search engine, or maybe browse > all

Re: [gentoo-user] [OT] KDE config problem

On Sun, 12 Feb 2017 22:54:29 +, Peter Humphrey wrote: > Thanks Frank, but I just have a mini-script > > $ cat /usr/local/bin/gu > #!/bin/bash > grep -s --color=auto $1 $2 /usr/portage/profiles/use* > > The extra parameter is so's I can add a -w to grep. You could use $* instead of $1 $2,

Re: [gentoo-user] WARNING: Crucial MX300 drives SUUUUUCK!!!!

On Sun, Feb 12, 2017 at 5:40 PM, Alan Grimes wrote: > Dear god, I think I have come in contact with one of the suckiest things > in the universe! > > I mean first there are supermassive black holes... OK... Then there's > Crucial MX300 SSDs, and in a distant third there's

Re: [gentoo-user] WARNING: Crucial MX300 drives SUUUUUCK!!!!

On Sunday 12 Feb 2017 17:40:35 Alan Grimes wrote: > Dear god, I think I have come in contact with one of the suckiest things > in the universe! > > I mean first there are supermassive black holes... OK... Then there's > Crucial MX300 SSDs, and in a distant third there's Justin Beiber. > > I mean

Re: [gentoo-user] logrotate ... won't!

On Sunday 12 Feb 2017 17:32:30 Mick wrote: > Thanks Alexander, it pays going back to basics ... for some reason my > cronie service was not running. o_O > > I added it to default runlevel and hopefully it will do its magic from now > on. I'm glad I'm not the only one prone to this kind of

Re: [gentoo-user] [OT] KDE config problem

On Sunday 12 Feb 2017 23:08:41 Frank Steinmetzger wrote: > On Sat, Feb 11, 2017 at 10:21:36AM +, Peter Humphrey wrote: > > > Something which will help is if you clear out as much of your USE > > > flags in make.conf and package.use as you can, before you run emerge > > > -e. > > > > You may

Re: [gentoo-user] WARNING: Crucial MX300 drives SUUUUUCK!!!!

I have 3 of these class of device (if I recall) 3 Crucial SSDs where I have only had issues with the one install of the device, and I'm not really sure *why* that might be causing problems, but I suspect that a good part of why it "just won't work" is because of the UEFI system on that machine,

Re: [gentoo-user] [OT] KDE config problem

On Saturday 11 Feb 2017 10:21:36 I wrote: > On Friday 10 Feb 2017 10:15:10 Mick wrote: > > Peter, some years ago I also reverted from testing to stable arch, > > because I was spending more time fixing breakages than actually using > > the OS. From what I recall it took more than a month for

[gentoo-user] WARNING: Crucial MX300 drives SUUUUUCK!!!!

Dear god, I think I have come in contact with one of the suckiest things in the universe! I mean first there are supermassive black holes... OK... Then there's Crucial MX300 SSDs, and in a distant third there's Justin Beiber. I mean the absolute suckyness of MX300 SSDs defy human comprehension.

Re: [gentoo-user] Access device on 192.168.1.1 network

> > --- > arp -a > > ? (192.168.0.100) at on net0 > DD-WRT (10.0.0.1) at 90:e6:ba:2e:ec:5c [ether] on net0 > ? (192.168.1.100) at 00:09:45:41:73:d1 [ether] on net0 > This shows that the IP is correct and communication may be possible. > When I boot and try WAN port the device gets

Re: [gentoo-user] [OT] KDE config problem

On Sat, Feb 11, 2017 at 10:21:36AM +, Peter Humphrey wrote: > > Something which will help is if you clear out as much of your USE flags in > > make.conf and package.use as you can, before you run emerge -e. > You may have it there. Goodness knows how long they'd been there, being > copied

Re: [gentoo-user] Access device on 192.168.1.1 network

On Sunday 12 Feb 2017 10:59:38 the...@sys-concept.com wrote: > On 02/12/2017 04:26 AM, Adam Carter wrote: > > On Sun, Feb 12, 2017 at 7:07 PM, > > > > wrote: > > On 02/12/2017 01:01 AM, the...@sys-concept.com > > > >

Re: [gentoo-user] Access device on 192.168.1.1 network

On 02/12/2017 04:26 AM, Adam Carter wrote: > On Sun, Feb 12, 2017 at 7:07 PM, > wrote: > > On 02/12/2017 01:01 AM, the...@sys-concept.com > wrote: > > My local network is 10.0.0.1 - > > >

Re: [gentoo-user] logrotate ... won't!

On Sunday 12 Feb 2017 19:11:23 Alexander Kapshuk wrote: > On Sun, Feb 12, 2017 at 6:57 PM, Mick wrote: > > I am perplexed why box of mine will not logrotate system logs, which have > > now grown into gigs. kern.log, syslog, messages, etc. are eating up > > space

Re: [gentoo-user] logrotate ... won't!

On Sun, Feb 12, 2017 at 6:57 PM, Mick wrote: > I am perplexed why box of mine will not logrotate system logs, which have now > grown into gigs. kern.log, syslog, messages, etc. are eating up space > unconstrained, to the point where the partition run out of it. > >

[gentoo-user] logrotate ... won't!

I am perplexed why box of mine will not logrotate system logs, which have now grown into gigs. kern.log, syslog, messages, etc. are eating up space unconstrained, to the point where the partition run out of it. Trying to run /etc/cron.daily/logrotate from a terminal does not show anything in

Re: [gentoo-user] Access device on 192.168.1.1 network

On Sun, Feb 12, 2017 at 01:01:01AM -0700, the...@sys-concept.com wrote: > My local network is 10.0.0.1 - > > I have an external device that is pre-set from factory to 192.168.1.100 and I > need to access to it via browser to change its network setting. > So I do: > ifconfig net0:1 192.168.1.1

Re: [gentoo-user] Access device on 192.168.1.1 network

On Sun, Feb 12, 2017 at 7:07 PM, wrote: > On 02/12/2017 01:01 AM, the...@sys-concept.com wrote: > > My local network is 10.0.0.1 - > > > > I have an external device that is pre-set from factory to 192.168.1.100 > and I need to access to it via browser to change its

Re: [gentoo-user] Access device on 192.168.1.1 network

On Sunday 12 Feb 2017 01:07:09 the...@sys-concept.com wrote: > On 02/12/2017 01:01 AM, the...@sys-concept.com wrote: > > My local network is 10.0.0.1 - > > > > I have an external device that is pre-set from factory to 192.168.1.100 > > and I need to access to it via browser to change its network

Re: [gentoo-user] Access device on 192.168.1.1 network

On 02/12/2017 01:01 AM, the...@sys-concept.com wrote: > My local network is 10.0.0.1 - > > I have an external device that is pre-set from factory to 192.168.1.100 and I > need to access to it via browser to change its network setting. > So I do: > ifconfig net0:1 192.168.1.1 up > > nmap -sn

[gentoo-user] Access device on 192.168.1.1 network

My local network is 10.0.0.1 - I have an external device that is pre-set from factory to 192.168.1.100 and I need to access to it via browser to change its network setting. So I do: ifconfig net0:1 192.168.1.1 up nmap -sn 192.168.1.1/24 Starting Nmap 6.47 ( http://nmap.org ) at 2017-02-12