Re: [gentoo-user] Gentoo net0 - auto resetting - very impressed

2015-09-16 Thread Alan McKinnon
On 17/09/2015 08:45, Stroller wrote:
> 
> On Wed, 16 September 2015, at 7:22 am, Alan McKinnon 
>  wrote:
> 
>> Their latest printers do not make that same
>> stupid mistake; mine is a recent colour laser and the cheapest in the
>> range. Doesn't even have a display or keyboard so it creates it's own
>> ad-hoc wifi connection so you can connect and configure in a browser.
>> Once it's on your real network, it all JustWorks(tm) and understands
>> postscript, PCL, SPL and ipp.
> 
> What model is this, please?


C410W

It's a simple basic home colour laser printer


-- 
Alan McKinnon
alan.mckin...@gmail.com




Re: [gentoo-user] Re: new machine : case + power

2015-09-16 Thread Dale
Alan McKinnon wrote:
> On 17/09/2015 05:38, james wrote:
>>>   150914 Mobo : Gigabyte GA-970A-UD3P 970+SB950 DDR3 2000  :  119.99
   2x PCI-Express x16 GLAN 6xSATA 6.0 Gb/s 4xUSB 3.0 14xUSB 2.0
>> I have (3) of the Ggiabyte 990A-UD3P mobos:: I love mine
>>
>> Very extensive wiring needs, plus you have to match the video card 
>> power needs to the power supply. None of my older PS would fit the bill.
>> Also, there has been a quiet revolution in power supply. The efficiency
>> of the switching circuits will save you more money in the long run
>> and those electronics will deliver the cleanest power to your other 
>> electronics. PS have ratings so look at the efficiency and oversizing a bit
>> from calculated loads is never a bad idea. 
>
> +1
>
> Don't be tempted to cut corners on the PSU. It's the one component in a
> computer that can "wear out" so to speak, and aged PSUs are responsible
> for more issues than anything else (except maybe dodgy RAM with a few
> dud cells).
>
> PSUs are not expensive and there's lots of other things one can save
> cash on. I firmly believe cutting corners with PSUs is like saving money
> by not replacing oil filters - you save some cash now, and cause
> yourself enormous expense later
>


It's the one thing that is common to everything else.  Most good power
supplies have protection but let's say that 12 VDC rail went to 16
volts.  It would turn a perfectly working puter into a nice door stop,
pretty quick.  It would likely burn out every component in the rig that
uses the 12 volt line, which a lot of stuff does. 

Yea, skimping and getting a el cheapo power supply is a bad idea. 

Dale

:-)  :-) 



Re: [gentoo-user] Gentoo net0 - auto resetting - very impressed

2015-09-16 Thread Stroller

On Wed, 16 September 2015, at 7:22 am, Alan McKinnon  
wrote:

> Their latest printers do not make that same
> stupid mistake; mine is a recent colour laser and the cheapest in the
> range. Doesn't even have a display or keyboard so it creates it's own
> ad-hoc wifi connection so you can connect and configure in a browser.
> Once it's on your real network, it all JustWorks(tm) and understands
> postscript, PCL, SPL and ipp.

What model is this, please?

Stroller.




Re: [gentoo-user] Re: new machine : case + power

2015-09-16 Thread Alan McKinnon
On 17/09/2015 05:38, james wrote:
>>   150914 Mobo : Gigabyte GA-970A-UD3P 970+SB950 DDR3 2000  :  119.99
>> >   2x PCI-Express x16 GLAN 6xSATA 6.0 Gb/s 4xUSB 3.0 14xUSB 2.0
> I have (3) of the Ggiabyte 990A-UD3P mobos:: I love mine
> 
> Very extensive wiring needs, plus you have to match the video card 
> power needs to the power supply. None of my older PS would fit the bill.
> Also, there has been a quiet revolution in power supply. The efficiency
> of the switching circuits will save you more money in the long run
> and those electronics will deliver the cleanest power to your other 
> electronics. PS have ratings so look at the efficiency and oversizing a bit
> from calculated loads is never a bad idea. 


+1

Don't be tempted to cut corners on the PSU. It's the one component in a
computer that can "wear out" so to speak, and aged PSUs are responsible
for more issues than anything else (except maybe dodgy RAM with a few
dud cells).

PSUs are not expensive and there's lots of other things one can save
cash on. I firmly believe cutting corners with PSUs is like saving money
by not replacing oil filters - you save some cash now, and cause
yourself enormous expense later

-- 
Alan McKinnon
alan.mckin...@gmail.com




Re: [gentoo-user] Quick check on net-print/hplip-3.14.10

2015-09-16 Thread Mick
On Thursday 17 Sep 2015 02:11:44 waben...@gmail.com wrote:
> Mick  wrote:
> > Hi All,
> > 
> > I just noticed that the driver for my old printer no longer shows up
> > in cups, on one of my PCs.  Comparison with other PCs shows that this
> > one does *not* have the hpijs USE set.
> > 
> > Could someone who also does not have hpijs set in their hplip tell me
> > if the HP DeskJet 930C selection is missing, when they load up the
> > GUI via https://127.0.0.1:631 and then try to modify a printer?
> > 
> > Until this week there wasn't a problem with this PC so I am not sure
> > what changed ...
> > 
> > I've set it up with DeskJet 932c for now without USE=hpijs and it
> > seems to work, so I am in two minds if I need hpijs or if I need to
> > use the 930c driver anyway.
> 
> I don't have USE flag hpijs set for hplip (3.14.10) and when I modify
> my printer, there are two lines for HP DeskJet 930C shown up:
> 
> HP Deskjet 930C Foomatic/cdj550 (en)
> HP Deskjet 930c, hpcups 3.14.10 (en)
> 
> My USE flags for hplip are:
> 
> X doc hpcups libnotify qt4 scanner snmp -fax -hpijs -kde -libusb0 -minimal
> -parport -policykit -static-ppds
> 
> --
> Regards
> wabe

Thank you wabe.  This is just how I recalled this should be and confirms my 
suspicions that hpijs is not needed.  I am at a loss as to why 930c suddenly 
disappeared from the list of available drivers.  I am also at the latest 
stable hplip-3.14.10.

Could this be btrfs playing up and messing up cups?  O_o

-- 
Regards,
Mick


signature.asc
Description: This is a digitally signed message part.


Re: [gentoo-user] Re: Quick check on net-print/hplip-3.14.10

2015-09-16 Thread Mick
On Thursday 17 Sep 2015 01:45:14 walt wrote:
> On Wed, 16 Sep 2015 22:22:32 +0100
> 
> Mick  wrote:
> > Hi All,
> > 
> > I just noticed that the driver for my old printer no longer shows up
> > in cups, on one of my PCs.  Comparison with other PCs shows that this
> > one does *not* have the hpijs USE set.
> > 
> > Could someone who also does not have hpijs set in their hplip tell me
> > if the HP DeskJet 930C selection is missing, when they load up the
> > GUI via https://127.0.0.1:631 and then try to modify a printer?
> > 
> > Until this week there wasn't a problem with this PC so I am not sure
> > what changed ...
> > 
> > I've set it up with DeskJet 932c for now without USE=hpijs and it
> > seems to work, so I am in two minds if I need hpijs or if I need to
> > use the 930c driver anyway.
> 
> Sometime in the past few days hpijs came to my attention in a way that
> escapes me at the moment, but I remember being puzzled by it.  What is
> also puzzling is that hpijs doesn't show up here in the output of eix:
> 
> Installed versions:  2.0.4^t(06:49:33 AM 08/28/2015)(X acl dbus java
> pam python ssl systemd threads -debug -kerberos -lprng-compat -selinux
> -static-libs -usb -xinetd -zeroconf ABI_MIPS="-n32 -n64 -o32"
> ABI_PPC="-32 -64" ABI_S390="-32 -64" ABI_X86="32 64 -x32"
> ELIBC="-FreeBSD" LINGUAS="-ca -cs -de -es -fr -it -ja -pt_BR -ru"
> PYTHON_TARGETS="python2_7") Homepage:http://www.cups.org/
> Description: The Common Unix Printing System
> 
> When I run ufed, though, I do see an hpijs useflag described, because
> it's listed in /usr/portage/profiles/use.local.desc (dated today).
> Here is a good use for the new git-based portage tree (which I'm not
> using yet, BTW):
> 
> https://gitweb.gentoo.org/repo/gentoo.git/
> 
> I just spent 10 minutes searching through the commits related to cups
> and I can't find anything about hpijs, but I know there's something
> strange going on with that useflag.

It is a flag for hplip rather than cups.
-- 
Regards,
Mick


signature.asc
Description: This is a digitally signed message part.


Re: [gentoo-user] Quick check on net-print/hplip-3.14.10

2015-09-16 Thread Mick
On Wednesday 16 Sep 2015 23:43:51 Dale wrote:
> Mick wrote:
> > Hi All,
> > 
> > I just noticed that the driver for my old printer no longer shows up in
> > cups, on one of my PCs.  Comparison with other PCs shows that this one
> > does *not* have the hpijs USE set.
> > 
> > Could someone who also does not have hpijs set in their hplip tell me if
> > the HP DeskJet 930C selection is missing, when they load up the GUI via
> > https://127.0.0.1:631 and then try to modify a printer?
> > 
> > Until this week there wasn't a problem with this PC so I am not sure what
> > changed ...
> > 
> > I've set it up with DeskJet 932c for now without USE=hpijs and it seems
> > to work, so I am in two minds if I need hpijs or if I need to use the
> > 930c driver anyway.
> 
> I was going to try and test this.  I try to help when ever I can.  Thing
> is, the way CUPS works here, you have to have the printer connected to
> set it up.  I can't find a option to set up a printer that is not
> connected during the set up process.  Maybe I am missing something.  o_O
> 
> Maybe someone else who has that printer can test it.  We hope.
> 
> Dale
> 
> :-)  :-)

Thank you Dale,

You don't have to complete the setup of the printer.  Just select Modify 
printer and 'try' to change its driver from the dropdown selection.  You don't 
need to actually change it - just look in there if DeskJet 930c is listed.  
Assuming of course that your hplip was compiled with USE="-hpijs".

My 930C is a USB printer, but I have a little ethernet to USB printer server 
that I access it through.  This is a monodirectional lpd server, so all the 
hplip GUI to report printer status is not working.  It doesn't bother me as 
printing is a rare occasion and all users know what to do if it runs out of 
ink.

Printing was all working fine on this PC until a couple of days ago, so I 
wonder if I removed something in /etc/portage/* to cause this ...
-- 
Regards,
Mick


signature.asc
Description: This is a digitally signed message part.


Re: [gentoo-user] Re: portage directory ownerships?

2015-09-16 Thread Mick
On Wednesday 16 Sep 2015 15:51:55 Neil Bothwick wrote:
> On Wed, 16 Sep 2015 16:19:40 +0200, Alan McKinnon wrote:
> > > PORTDIR_OVERLAY="/usr/local/portage" ==>
> > > PORTDIR_OVERLAY="/var/lib/layman"
> > 
> > No. DoItRite as above. That PORTDIR_OVERLAY crap never did work right -
> > all overlays were essentially considered equal and it would be pot luck
> > where your next ebuild comes from
> 
> It was according to the order of the overlays in PORTDIR_OVERLAY, for
> ebuilds with equal versions.

This may help:

https://wiki.gentoo.org/wiki/Project:Portage/Sync

I have not yet changed my layman config to use 
/etc/portage/repos.conf/layman.conf but will be looking into installing 
laymanator and doing the necessary when I get a minute.

-- 
Regards,
Mick


signature.asc
Description: This is a digitally signed message part.


[gentoo-user] Re: new machine : case + power

2015-09-16 Thread Nikos Chantziaras

On 17/09/15 06:04, Philip Webb wrote:

My previous machines' (2000/3/7/12) cases all contained a PSU,
but it seems I now have to buy case/PSU separately, so my next question is
whether I can safely use the case + power supply from the 2007 machine


This should be fine, as long as the PSU has SATA power connectors. If 
not, you will need molex to SATA adapters.


The PSU does not need to provide a PCI-e power connector, since the Asus 
GT610 does not take external power. It's powered exclusively by the bus.


However, note that PSUs tend to go bad after years of operation. An 8 
years old PSU might start losing power or voltage stability. If you see 
random machine resets or hangups, it's usually because the PSU is dying.


With that GPU, you don't need more than 400W. And the amps on the 12V 
rail are also not important, as that only comes into play with 
higher-end GPUs. Other features can still be important though, like 
protection against surges and such (think lightning strikes that can 
potentially damage your PC, or some PSU malfunction that could do the same.)





[gentoo-user] Re: [solved] app-office/libreoffice-5.0.1.2

2015-09-16 Thread Nikos Chantziaras

On 15/09/15 12:21, Stefan G. Weichinger wrote:

On 15.09.2015 08:49, Stefan G. Weichinger wrote:


I will retry a build and show you parts of the log.


Something in my merging history seems to have solved it now.
Merged OK today, sorry for the noise.


I'd run a complete memtest just in case. Last time libreoffice failed to 
build for me, and the failure was at a different point in the build 
process, it turned out a memory module had developed an error.





[gentoo-user] Re: new machine : case + power

2015-09-16 Thread james
Philip Webb  ca.inter.net> writes:


>   150914 CPU : AMD X8 FX8370E 8-core 4,3 GHz 16 MB 32 nm 95 W 

 I have 3) FX8350. Outstanding performance for the cost. Love them all.



>   150914 Mobo : Gigabyte GA-970A-UD3P 970+SB950 DDR3 2000  :  119.99
>   2x PCI-Express x16 GLAN 6xSATA 6.0 Gb/s 4xUSB 3.0 14xUSB 2.0

I have (3) of the Ggiabyte 990A-UD3P mobos:: I love mine

Very extensive wiring needs, plus you have to match the video card 
power needs to the power supply. None of my older PS would fit the bill.
Also, there has been a quiet revolution in power supply. The efficiency
of the switching circuits will save you more money in the long run
and those electronics will deliver the cleanest power to your other 
electronics. PS have ratings so look at the efficiency and oversizing a bit
from calculated loads is never a bad idea. 
I would recommend to 'not go cheap' on the PS. Becuase
4+ GHz can create some very localized heats, I put a 'water cooler'
on the chip that has hoses running to a radiaor bolted on the the main rear
fan of the Case. A wise investment at 4.3GHz. Air cooled CPUs are suspect
at those frequencies, particular if you like to compile  lots of code
or stress the all the cores at the same time.




>   150914 Memory : Kingston HyperX Fury 8 GB DDR3 1866 MHz CL10 :   68.99

I always max ram in lieu of SSD. I know you have a budget but max
ram is the single biggest item on performance and most things are 
memory constrained on processing, ymmv.

Every thing else look for bargains. Newegg is a great place to vett prices.

Make sure your case has a big and quite fan to draw air across the HD. Most
new cases do. In all you buy, check the dB (sound level) especially if
you want a quite rig to sit near you. Make sure the UPS you have is 
adequate and tested. Put a large light on the UPS. Yank the power cord
of the UPS to the wall and you should not see a flicker nor deeming
of the light of the bulb; thats a good UPS. UPS protects ALL your
electronics, but never printers as their power draw surges can easily
fry a smaller UPS.

hth,
James






Re: [gentoo-user] new machine : case + power

2015-09-16 Thread Dale
Philip Webb wrote:
> Thanks for the  2  replies to my previous query (hijacked by overclockers).
>
> I have bought (prices in CAD) :
>
>   150914 CPU : AMD X8 FX8370E 8-core 4,3 GHz 16 MB 32 nm 95 W  :  259.00
>  Direct replacement : 3 yr :   38.85
>   150914 Mobo : Gigabyte GA-970A-UD3P 970+SB950 DDR3 2000  :  119.99
>   2x PCI-Express x16 GLAN 6xSATA 6.0 Gb/s 4xUSB 3.0 14xUSB 2.0
>   150914 Memory : Kingston HyperX Fury 8 GB DDR3 1866 MHz CL10 :   68.99
>   150914 Graphix : Asus GT610 810 MHz clock 1200 MHz memory:   74.99
>   150914 SSD : Kingston SSDNow V300 240 GB SATA RW 450 MB/s:  109.99
>   150914 HDD : Seagate Desktop SATA3 1 TB 64 MB 6 GB/s :   57.99
>  Ont recycle fee   :0.75
>   150914 DVD : Samsung SH-224FB 24x SATA 1,5 MB:   21.99
>  Ont recycle fee   :0.75
>
>   subtotal :  753.29
>tax :   97.93
>  total :  851.22
>
> Prices have gone up since 2012, mainly due to a drop in CAD.
> My previous machines' (2000/3/7/12) cases all contained a PSU,
> but it seems I now have to buy case/PSU separately, so my next question is
> whether I can safely use the case + power supply from the 2007 machine,
> an in-house Canada Computers creation with a  500 W  PSU ,
> which served well for  5 yr .  The front USBs mb more limited,
> but might there be differences in the PSU outlet cabling ?
>


I use this list as a guide on power supplies, linky below.  These are
tested and graded as to the quality of the power supply.  Nothing is
perfect but short of buying all the equipment and power supplies then
testing them yourself, this is as close as it gets. 

http://www.overclockers.com/forums/showthread.php/589708-Recommended-PSU-s-True-Tested
 


The first post is really all you need to look at.  As they test them,
they update that first post.  At least you may can tell what brand does
better than others. 

Hope that helps. 

Dale

:-)  :-) 



[gentoo-user] new machine : case + power

2015-09-16 Thread Philip Webb
Thanks for the  2  replies to my previous query (hijacked by overclockers).

I have bought (prices in CAD) :

  150914 CPU : AMD X8 FX8370E 8-core 4,3 GHz 16 MB 32 nm 95 W  :  259.00
 Direct replacement : 3 yr :   38.85
  150914 Mobo : Gigabyte GA-970A-UD3P 970+SB950 DDR3 2000  :  119.99
  2x PCI-Express x16 GLAN 6xSATA 6.0 Gb/s 4xUSB 3.0 14xUSB 2.0
  150914 Memory : Kingston HyperX Fury 8 GB DDR3 1866 MHz CL10 :   68.99
  150914 Graphix : Asus GT610 810 MHz clock 1200 MHz memory:   74.99
  150914 SSD : Kingston SSDNow V300 240 GB SATA RW 450 MB/s:  109.99
  150914 HDD : Seagate Desktop SATA3 1 TB 64 MB 6 GB/s :   57.99
 Ont recycle fee   :0.75
  150914 DVD : Samsung SH-224FB 24x SATA 1,5 MB:   21.99
 Ont recycle fee   :0.75

  subtotal :  753.29
   tax :   97.93
 total :  851.22

Prices have gone up since 2012, mainly due to a drop in CAD.
My previous machines' (2000/3/7/12) cases all contained a PSU,
but it seems I now have to buy case/PSU separately, so my next question is
whether I can safely use the case + power supply from the 2007 machine,
an in-house Canada Computers creation with a  500 W  PSU ,
which served well for  5 yr .  The front USBs mb more limited,
but might there be differences in the PSU outlet cabling ?

-- 
,,
SUPPORT ___//___,   Philip Webb
ELECTRIC   /] [] [] [] [] []|   Cities Centre, University of Toronto
TRANSIT`-O--O---'   purslowatchassdotutorontodotca




Re: [gentoo-user] Quick check on net-print/hplip-3.14.10

2015-09-16 Thread wabenbau
Mick  wrote:

> Hi All,
> 
> I just noticed that the driver for my old printer no longer shows up
> in cups, on one of my PCs.  Comparison with other PCs shows that this
> one does *not* have the hpijs USE set.
> 
> Could someone who also does not have hpijs set in their hplip tell me
> if the HP DeskJet 930C selection is missing, when they load up the
> GUI via https://127.0.0.1:631 and then try to modify a printer?
> 
> Until this week there wasn't a problem with this PC so I am not sure
> what changed ...
> 
> I've set it up with DeskJet 932c for now without USE=hpijs and it
> seems to work, so I am in two minds if I need hpijs or if I need to
> use the 930c driver anyway.

I don't have USE flag hpijs set for hplip (3.14.10) and when I modify 
my printer, there are two lines for HP DeskJet 930C shown up:

HP Deskjet 930C Foomatic/cdj550 (en)
HP Deskjet 930c, hpcups 3.14.10 (en)

My USE flags for hplip are:

X doc hpcups libnotify qt4 scanner snmp -fax -hpijs -kde -libusb0 -minimal 
-parport -policykit -static-ppds

--
Regards
wabe



[gentoo-user] Re: Quick check on net-print/hplip-3.14.10

2015-09-16 Thread walt
On Wed, 16 Sep 2015 22:22:32 +0100
Mick  wrote:

> Hi All,
> 
> I just noticed that the driver for my old printer no longer shows up
> in cups, on one of my PCs.  Comparison with other PCs shows that this
> one does *not* have the hpijs USE set.
> 
> Could someone who also does not have hpijs set in their hplip tell me
> if the HP DeskJet 930C selection is missing, when they load up the
> GUI via https://127.0.0.1:631 and then try to modify a printer?
> 
> Until this week there wasn't a problem with this PC so I am not sure
> what changed ...
> 
> I've set it up with DeskJet 932c for now without USE=hpijs and it
> seems to work, so I am in two minds if I need hpijs or if I need to
> use the 930c driver anyway.

Sometime in the past few days hpijs came to my attention in a way that
escapes me at the moment, but I remember being puzzled by it.  What is
also puzzling is that hpijs doesn't show up here in the output of eix:

Installed versions:  2.0.4^t(06:49:33 AM 08/28/2015)(X acl dbus java
pam python ssl systemd threads -debug -kerberos -lprng-compat -selinux
-static-libs -usb -xinetd -zeroconf ABI_MIPS="-n32 -n64 -o32"
ABI_PPC="-32 -64" ABI_S390="-32 -64" ABI_X86="32 64 -x32"
ELIBC="-FreeBSD" LINGUAS="-ca -cs -de -es -fr -it -ja -pt_BR -ru"
PYTHON_TARGETS="python2_7") Homepage:http://www.cups.org/
Description: The Common Unix Printing System

When I run ufed, though, I do see an hpijs useflag described, because
it's listed in /usr/portage/profiles/use.local.desc (dated today).
Here is a good use for the new git-based portage tree (which I'm not
using yet, BTW):

https://gitweb.gentoo.org/repo/gentoo.git/

I just spent 10 minutes searching through the commits related to cups
and I can't find anything about hpijs, but I know there's something
strange going on with that useflag.





Re: [gentoo-user] Quick check on net-print/hplip-3.14.10

2015-09-16 Thread Dale
Mick wrote:
> Hi All,
>
> I just noticed that the driver for my old printer no longer shows up in cups, 
> on one of my PCs.  Comparison with other PCs shows that this one does *not* 
> have the hpijs USE set.
>
> Could someone who also does not have hpijs set in their hplip tell me if the 
> HP DeskJet 930C selection is missing, when they load up the GUI via 
> https://127.0.0.1:631 and then try to modify a printer?
>
> Until this week there wasn't a problem with this PC so I am not sure what 
> changed ...
>
> I've set it up with DeskJet 932c for now without USE=hpijs and it seems to 
> work, so I am in two minds if I need hpijs or if I need to use the 930c 
> driver 
> anyway.


I was going to try and test this.  I try to help when ever I can.  Thing
is, the way CUPS works here, you have to have the printer connected to
set it up.  I can't find a option to set up a printer that is not
connected during the set up process.  Maybe I am missing something.  o_O 

Maybe someone else who has that printer can test it.  We hope.

Dale

:-)  :-) 



[gentoo-user] Quick check on net-print/hplip-3.14.10

2015-09-16 Thread Mick
Hi All,

I just noticed that the driver for my old printer no longer shows up in cups, 
on one of my PCs.  Comparison with other PCs shows that this one does *not* 
have the hpijs USE set.

Could someone who also does not have hpijs set in their hplip tell me if the 
HP DeskJet 930C selection is missing, when they load up the GUI via 
https://127.0.0.1:631 and then try to modify a printer?

Until this week there wasn't a problem with this PC so I am not sure what 
changed ...

I've set it up with DeskJet 932c for now without USE=hpijs and it seems to 
work, so I am in two minds if I need hpijs or if I need to use the 930c driver 
anyway.
-- 
Regards,
Mick


signature.asc
Description: This is a digitally signed message part.


Re: [gentoo-user] Syslog-ng "Failed to seek to the Cursor"

2015-09-16 Thread Rich Freeman
On Wed, Sep 16, 2015 at 3:57 PM, Alan McKinnon  wrote:
> On 16/09/2015 21:42, Rich Freeman wrote:
>> On Wed, Sep 16, 2015 at 12:55 PM, Alan McKinnon  
>> wrote:
>>>
>>> It has something to do with systemd's log thingy.
>>>
>>> The error only appears in one place in the syslog-ng source,
>>> in modules/systemd-journal/journal-reader.c:
>>>
>>> static inline gboolean
>>> __seek_to_saved_state(JournalReader *self)
>>> {
>>>   JournalReaderState *state =
>>> persist_state_map_entry(self->persist_state, self->persist_handle);
>>>   gint rc = journald_seek_cursor(self->journal, state->cursor);
>>>   persist_state_unmap_entry(self->persist_state, self->persist_handle);
>>>   if (rc != 0)
>>> {
>>>   msg_warning("Failed to seek to the cursor",
>>>   evt_tag_str("cursor", state->cursor),
>>>   evt_tag_errno("error", errno),
>>>   NULL);
>>>   return __seek_to_head(self);
>>> }
>>>   journald_next(self->journal);
>>>   return TRUE;
>>> }
>>>
>>
>> The other posts are getting at the solution - disable journal support
>> if you're not actually using systemd.
>>
>> However, does syslog-ng actually READ logs?  My understanding is that
>> journal cursors are used to read logs, not to write them, and I
>> associate syslog-ng more with writing logs.
>>
>> The concept is that when you query the journal every record gets
>> returned with a cursor, which is just a guid of some sort.  Then you
>> can run a later query and pass the last cursor you saw back and just
>> get a list of new records since the last one you read.  The use case
>> is for log monitors and such so that they can periodically poll the
>> log without having to read the entire thing from the beginning each
>> time.
>>
>
>
> Digging up ancient memory from other people's posts long ago:
>
> Doesn't syslog-ng read systemd's log from early userspace startup
> (before syslog-ng starts) and write those entries to syslog-ng?
>

Ah, that makes sense.  This isn't about recording syslog data in the
journal.  This is about recording journal data in syslog, for which
using cursors would be a completely obvious design.

-- 
Rich



Re: [gentoo-user] Syslog-ng "Failed to seek to the Cursor"

2015-09-16 Thread Alan McKinnon
On 16/09/2015 21:42, Rich Freeman wrote:
> On Wed, Sep 16, 2015 at 12:55 PM, Alan McKinnon  
> wrote:
>>
>> It has something to do with systemd's log thingy.
>>
>> The error only appears in one place in the syslog-ng source,
>> in modules/systemd-journal/journal-reader.c:
>>
>> static inline gboolean
>> __seek_to_saved_state(JournalReader *self)
>> {
>>   JournalReaderState *state =
>> persist_state_map_entry(self->persist_state, self->persist_handle);
>>   gint rc = journald_seek_cursor(self->journal, state->cursor);
>>   persist_state_unmap_entry(self->persist_state, self->persist_handle);
>>   if (rc != 0)
>> {
>>   msg_warning("Failed to seek to the cursor",
>>   evt_tag_str("cursor", state->cursor),
>>   evt_tag_errno("error", errno),
>>   NULL);
>>   return __seek_to_head(self);
>> }
>>   journald_next(self->journal);
>>   return TRUE;
>> }
>>
> 
> The other posts are getting at the solution - disable journal support
> if you're not actually using systemd.
> 
> However, does syslog-ng actually READ logs?  My understanding is that
> journal cursors are used to read logs, not to write them, and I
> associate syslog-ng more with writing logs.
> 
> The concept is that when you query the journal every record gets
> returned with a cursor, which is just a guid of some sort.  Then you
> can run a later query and pass the last cursor you saw back and just
> get a list of new records since the last one you read.  The use case
> is for log monitors and such so that they can periodically poll the
> log without having to read the entire thing from the beginning each
> time.
> 


Digging up ancient memory from other people's posts long ago:

Doesn't syslog-ng read systemd's log from early userspace startup
(before syslog-ng starts) and write those entries to syslog-ng?

-- 
Alan McKinnon
alan.mckin...@gmail.com




Re: [gentoo-user] Syslog-ng "Failed to seek to the Cursor"

2015-09-16 Thread Rich Freeman
On Wed, Sep 16, 2015 at 12:55 PM, Alan McKinnon  wrote:
>
> It has something to do with systemd's log thingy.
>
> The error only appears in one place in the syslog-ng source,
> in modules/systemd-journal/journal-reader.c:
>
> static inline gboolean
> __seek_to_saved_state(JournalReader *self)
> {
>   JournalReaderState *state =
> persist_state_map_entry(self->persist_state, self->persist_handle);
>   gint rc = journald_seek_cursor(self->journal, state->cursor);
>   persist_state_unmap_entry(self->persist_state, self->persist_handle);
>   if (rc != 0)
> {
>   msg_warning("Failed to seek to the cursor",
>   evt_tag_str("cursor", state->cursor),
>   evt_tag_errno("error", errno),
>   NULL);
>   return __seek_to_head(self);
> }
>   journald_next(self->journal);
>   return TRUE;
> }
>

The other posts are getting at the solution - disable journal support
if you're not actually using systemd.

However, does syslog-ng actually READ logs?  My understanding is that
journal cursors are used to read logs, not to write them, and I
associate syslog-ng more with writing logs.

The concept is that when you query the journal every record gets
returned with a cursor, which is just a guid of some sort.  Then you
can run a later query and pass the last cursor you saw back and just
get a list of new records since the last one you read.  The use case
is for log monitors and such so that they can periodically poll the
log without having to read the entire thing from the beginning each
time.

-- 
Rich



Re: [gentoo-user] Syslog-ng "Failed to seek to the Cursor"

2015-09-16 Thread Fernando Rodriguez
On Wednesday, September 16, 2015 3:05:55 PM Fernando Rodriguez wrote:
> On Wednesday, September 16, 2015 8:52:21 PM Helmut Jarausch wrote:
> > On 09/16/2015 06:55:00 PM, Alan McKinnon wrote:
> > > On 16/09/2015 17:57, Helmut Jarausch wrote:
> > > > I have syslog-ng-3.7.1 installed here.
> > > > Syslog-ng fails to start with the message:
> > > > Failed to seek to the Cursor cursor='', error='Success (0)'
> > > >
> > > > Does anybody know what's happening?
> > > >
> > > > Many thanks for a hint,
> > > > Helmut
> > > >
> > > >
> > > 
> > > 
> > > It has something to do with systemd's log thingy.
> > > 
> > > The error only appears in one place in the syslog-ng source,
> > > in modules/systemd-journal/journal-reader.c:
> > > 
> > > static inline gboolean
> > > __seek_to_saved_state(JournalReader *self)
> > > {
> > >   JournalReaderState *state =
> > > persist_state_map_entry(self->persist_state, self->persist_handle);
> > >   gint rc = journald_seek_cursor(self->journal, state->cursor);
> > >   persist_state_unmap_entry(self->persist_state,
> > > self->persist_handle);
> > >   if (rc != 0)
> > > {
> > >   msg_warning("Failed to seek to the cursor",
> > >   evt_tag_str("cursor", state->cursor),
> > >   evt_tag_errno("error", errno),
> > >   NULL);
> > >   return __seek_to_head(self);
> > > }
> > >   journald_next(self->journal);
> > >   return TRUE;
> > > }
> > > 
> > > 
> > > First step would appear to be to check systemd's built-in log thingy
> > > 
> > 
> > Thanks Alan,
> > 
> > but how to do that. I have systemd installed here but I haven't ever used 
it 
> since I'm using openrc.
> > So, what can I do?
> > 
> > Thanks,
> > Helmut
> > 
> > 
> 
> Look for file named syslog-ng.persist somewhere in /var and delete it, then 
try 
> restarting syslog-ng.
> 
> I also recommend you start playing with journalctl. I hated it for a while 
but 
> mostly because I didn't knew how to use it. Now I love it and got rid of 
> syslog-ng.

Ops, I missed the part about not using systemd. If deleting that file doesn't 
fix it check if you have the systemd use flag enabled for syslog-ng and disable 
it. Are you using a systemd profile?

-- 
Fernando Rodriguez



Re: [gentoo-user] Syslog-ng "Failed to seek to the Cursor"

2015-09-16 Thread Fernando Rodriguez
On Wednesday, September 16, 2015 8:52:21 PM Helmut Jarausch wrote:
> On 09/16/2015 06:55:00 PM, Alan McKinnon wrote:
> > On 16/09/2015 17:57, Helmut Jarausch wrote:
> > > I have syslog-ng-3.7.1 installed here.
> > > Syslog-ng fails to start with the message:
> > > Failed to seek to the Cursor cursor='', error='Success (0)'
> > >
> > > Does anybody know what's happening?
> > >
> > > Many thanks for a hint,
> > > Helmut
> > >
> > >
> > 
> > 
> > It has something to do with systemd's log thingy.
> > 
> > The error only appears in one place in the syslog-ng source,
> > in modules/systemd-journal/journal-reader.c:
> > 
> > static inline gboolean
> > __seek_to_saved_state(JournalReader *self)
> > {
> >   JournalReaderState *state =
> > persist_state_map_entry(self->persist_state, self->persist_handle);
> >   gint rc = journald_seek_cursor(self->journal, state->cursor);
> >   persist_state_unmap_entry(self->persist_state,
> > self->persist_handle);
> >   if (rc != 0)
> > {
> >   msg_warning("Failed to seek to the cursor",
> >   evt_tag_str("cursor", state->cursor),
> >   evt_tag_errno("error", errno),
> >   NULL);
> >   return __seek_to_head(self);
> > }
> >   journald_next(self->journal);
> >   return TRUE;
> > }
> > 
> > 
> > First step would appear to be to check systemd's built-in log thingy
> > 
> 
> Thanks Alan,
> 
> but how to do that. I have systemd installed here but I haven't ever used it 
since I'm using openrc.
> So, what can I do?
> 
> Thanks,
> Helmut
> 
> 

Look for file named syslog-ng.persist somewhere in /var and delete it, then try 
restarting syslog-ng.

I also recommend you start playing with journalctl. I hated it for a while but 
mostly because I didn't knew how to use it. Now I love it and got rid of 
syslog-ng.

-- 
Fernando Rodriguez



Re: [gentoo-user] Syslog-ng "Failed to seek to the Cursor"

2015-09-16 Thread Alan McKinnon
On 16/09/2015 20:52, Helmut Jarausch wrote:
> On 09/16/2015 06:55:00 PM, Alan McKinnon wrote:
>> On 16/09/2015 17:57, Helmut Jarausch wrote:
>>> I have syslog-ng-3.7.1 installed here.
>>> Syslog-ng fails to start with the message:
>>> Failed to seek to the Cursor cursor='', error='Success (0)'
>>>
>>> Does anybody know what's happening?
>>>
>>> Many thanks for a hint,
>>> Helmut
>>>
>>>
>>
>>
>> It has something to do with systemd's log thingy.
>>
>> The error only appears in one place in the syslog-ng source,
>> in modules/systemd-journal/journal-reader.c:
>>
>> static inline gboolean
>> __seek_to_saved_state(JournalReader *self)
>> {
>>   JournalReaderState *state =
>> persist_state_map_entry(self->persist_state, self->persist_handle);
>>   gint rc = journald_seek_cursor(self->journal, state->cursor);
>>   persist_state_unmap_entry(self->persist_state,
>> self->persist_handle);
>>   if (rc != 0)
>> {
>>   msg_warning("Failed to seek to the cursor",
>>   evt_tag_str("cursor", state->cursor),
>>   evt_tag_errno("error", errno),
>>   NULL);
>>   return __seek_to_head(self);
>> }
>>   journald_next(self->journal);
>>   return TRUE;
>> }
>>
>>
>> First step would appear to be to check systemd's built-in log thingy
>>
> 
> Thanks Alan,
> 
> but how to do that. I have systemd installed here but I haven't ever used it 
> since I'm using openrc.
> So, what can I do?

Well you are one better than me.
I _don't_ have systemd installed here but I haven't ever used it since
I'm using openrc :-)

I haven't seen Canek for a few days, hopefully he'll drop by and help
you out - he's usually the one with the most useful systemd answers

-- 
Alan McKinnon
alan.mckin...@gmail.com




Re: [gentoo-user] Syslog-ng "Failed to seek to the Cursor"

2015-09-16 Thread Helmut Jarausch
On 09/16/2015 06:55:00 PM, Alan McKinnon wrote:
> On 16/09/2015 17:57, Helmut Jarausch wrote:
> > I have syslog-ng-3.7.1 installed here.
> > Syslog-ng fails to start with the message:
> > Failed to seek to the Cursor cursor='', error='Success (0)'
> >
> > Does anybody know what's happening?
> >
> > Many thanks for a hint,
> > Helmut
> >
> >
> 
> 
> It has something to do with systemd's log thingy.
> 
> The error only appears in one place in the syslog-ng source,
> in modules/systemd-journal/journal-reader.c:
> 
> static inline gboolean
> __seek_to_saved_state(JournalReader *self)
> {
>   JournalReaderState *state =
> persist_state_map_entry(self->persist_state, self->persist_handle);
>   gint rc = journald_seek_cursor(self->journal, state->cursor);
>   persist_state_unmap_entry(self->persist_state,
> self->persist_handle);
>   if (rc != 0)
> {
>   msg_warning("Failed to seek to the cursor",
>   evt_tag_str("cursor", state->cursor),
>   evt_tag_errno("error", errno),
>   NULL);
>   return __seek_to_head(self);
> }
>   journald_next(self->journal);
>   return TRUE;
> }
> 
> 
> First step would appear to be to check systemd's built-in log thingy
> 

Thanks Alan,

but how to do that. I have systemd installed here but I haven't ever used it 
since I'm using openrc.
So, what can I do?

Thanks,
Helmut




Re: [gentoo-user] Syslog-ng "Failed to seek to the Cursor"

2015-09-16 Thread Alan McKinnon
On 16/09/2015 17:57, Helmut Jarausch wrote:
> I have syslog-ng-3.7.1 installed here.
> Syslog-ng fails to start with the message:
> Failed to seek to the Cursor cursor='', error='Success (0)'
> 
> Does anybody know what's happening?
> 
> Many thanks for a hint,
> Helmut
> 
> 


It has something to do with systemd's log thingy.

The error only appears in one place in the syslog-ng source,
in modules/systemd-journal/journal-reader.c:

static inline gboolean
__seek_to_saved_state(JournalReader *self)
{
  JournalReaderState *state =
persist_state_map_entry(self->persist_state, self->persist_handle);
  gint rc = journald_seek_cursor(self->journal, state->cursor);
  persist_state_unmap_entry(self->persist_state, self->persist_handle);
  if (rc != 0)
{
  msg_warning("Failed to seek to the cursor",
  evt_tag_str("cursor", state->cursor),
  evt_tag_errno("error", errno),
  NULL);
  return __seek_to_head(self);
}
  journald_next(self->journal);
  return TRUE;
}


First step would appear to be to check systemd's built-in log thingy


-- 
Alan McKinnon
alan.mckin...@gmail.com




Re: [gentoo-user] emaint -C logs

2015-09-16 Thread covici
Neil Bothwick  wrote:

> On Wed, 16 Sep 2015 12:07:55 -0400, cov...@ccs.covici.com wrote:
> 
> > What is emaint -- I don't see it in the tree.
> 
> That's because it's part of portage, an essential part now as syncing
> won't work without it so you already have it installed.

OK, thanks.


-- 
Your life is like a penny.  You're going to lose it.  The question is:
How do
you spend it?

 John Covici
 cov...@ccs.covici.com



Re: [gentoo-user] emaint -C logs

2015-09-16 Thread Neil Bothwick
On Wed, 16 Sep 2015 12:07:55 -0400, cov...@ccs.covici.com wrote:

> What is emaint -- I don't see it in the tree.

That's because it's part of portage, an essential part now as syncing
won't work without it so you already have it installed.


-- 
Neil Bothwick

Procedure: (n.) a method of performing a program sub-task in an
inefficient way by extensively using the stack instead of a GOTO.


pgpS2I9SsUN7e.pgp
Description: OpenPGP digital signature


Re: [gentoo-user] emaint -C logs

2015-09-16 Thread covici
Peter Humphrey  wrote:

> Hello list,
> 
> I've been playing with emaint and on one box I got an error message:
> 
> # emaint -C logs
> 
> PORT_LOGDIR_CLEAN command returned None
> See the make.conf(5) man page for PORT_LOGDIR_CLEAN usage instructions.
> 
> This is needlessly complex. In fact all I needed was for PORT_LOGDIR to be 
> defined in make.conf.
> 
> Just thought I'd mention it in case anyone else was similarly afflicted.

What is emaint -- I don't see it in the tree.

-- 
Your life is like a penny.  You're going to lose it.  The question is:
How do
you spend it?

 John Covici
 cov...@ccs.covici.com



[gentoo-user] Syslog-ng "Failed to seek to the Cursor"

2015-09-16 Thread Helmut Jarausch
I have syslog-ng-3.7.1 installed here.
Syslog-ng fails to start with the message:
Failed to seek to the Cursor cursor='', error='Success (0)'

Does anybody know what's happening?

Many thanks for a hint,
Helmut




Re: [gentoo-user] Re: portage directory ownerships?

2015-09-16 Thread Neil Bothwick
On Wed, 16 Sep 2015 16:19:40 +0200, Alan McKinnon wrote:

> > PORTDIR_OVERLAY="/usr/local/portage" ==>
> > PORTDIR_OVERLAY="/var/lib/layman"  
> 
> No. DoItRite as above. That PORTDIR_OVERLAY crap never did work right -
> all overlays were essentially considered equal and it would be pot luck
> where your next ebuild comes from

It was according to the order of the overlays in PORTDIR_OVERLAY, for
ebuilds with equal versions.


-- 
Neil Bothwick

I get enough exercise just pushing my luck.


pgpyWtHzSZSl6.pgp
Description: OpenPGP digital signature


[gentoo-user] Re: Can't paste from selection in gtk-3 apps

2015-09-16 Thread Grant Edwards
On 2015-09-16, J. Roeleveld  wrote:
> On Tuesday, September 15, 2015 06:57:36 PM Grant Edwards wrote:
>> On 2015-09-15, Grant Edwards  wrote:
>> > In most X11 apps I can select some text and then paste it somewhere
>> > else with a middle-click, or dump it to stdout with the command 'xclip
>> > -o'.  That doesn't work for highligted text in gtk-3 apps (meld,
>> > evince, audacious, etc.).  After selecting text in a gtk-3 app, if I
>> > middle-click in a terminal window it does nothing and 'xclip -o' just
>> > hangs.  Selecting text elsewhere will deselect the text in the gtk-3
>> > app, so gtk-3 isn't _completely_ ignoring X11 clipboards/buffers.
>> > 
>> > Any ideas why gtk-3 copy/paste is broken and how to fix it?
>> 
>> Ah, it turns out it's only a problem if you have multiple screens: you
>> can only paste a gtk-3 selection if the destination is on the same X11
>> screen as the source.  I'm pretty sure this is a known problem, but
>> I'm having trouble finding it again in the Gnome bugtracker...
>
> Must be related to gtk-3 then.
>
> I use 2 screens extensively and never experienced any issues like you 
> describe.

And you can select/paste from one screen to another where the source
is a gtk-3 app?

I should clarify that I mean "screen" in the strict X11 usage.  Using
Xinerama or the like to spread a single desktop across multiple
monitors is still a single screen setup.  I'm trying to select text on
DISPLAY=:0.0 and paste it on DISPLAY=:0.1

> Am surprised it would respond differently between GTK-3 and non-GTK-3
> apps.

I'm not.  When somebody selects something, you've got to make onr or
more Xlib function calls to grab control of the selection, and if
you're naive and think that the screen where your program is running
is the only one, then you only make the call to grab control of the
selection for that screen. Apparently the gtk-3 developers never
thought about the possibility that there are mutliple screens in an
X11 session.

> I don't configure anything special for multiple screens in the past
> few years.

Are you really using multiple screens?  Or a single screen spread
across mutliple monitors?  If you start an xterm on every monitor and
do "echo $DISPLAY" in each one, do you get different results or are
they all the same?

-- 
Grant Edwards   grant.b.edwardsYow! Gibble, Gobble, we
  at   ACCEPT YOU ...
  gmail.com




Re: [gentoo-user] Re: portage directory ownerships?

2015-09-16 Thread Alan McKinnon
On 16/09/2015 15:46, james wrote:
> Neil Bothwick  digimed.co.uk> writes:
> 
> 
> 
>>> Here, all of /etc/portage is root:root
>>> The tree and all overlays are portage:portage
> 
>> Just to add some confusion to the mix
> 
> 
> 
> Good example and it got me thinking
> 
>> So some are portage:portage, some are root:root - all use /var/portage
>> for $PORTDIR so that's not an issue. One of the portage:portage ones is
>> the one that syncs with the mirrors and acts as an rsync host for the
>> others, this may or may not be significant.
> 
> I might swith to /var/portage on a new install. Whats the pedantic 
> reasons for for it? On an SSD for speed ? tmpdir? I'm curious, so tell me 
> more.

Nothing to do with tmpdir stuff.

/usr has always been something that must mountable read-only and still
work should the user want it that way.
/var is where data goes that can change. The tree is a database, it can
change, and does every time you sync.

The tree was in /usr/portage for years for NO OTHER REASON than that's
where FreeBSD put it (portage is based off/inspired by FreeBSD ports).
That works on FreeBSD nicely but strictly according to Linux conventions
and FHS should have been in /var all along.

You can put the tree any place you like, just modify PORTDIR to suit
plus a few other bits (eg profile symlink in /etc/portage). The switch
to /var is only a change to the hard-coded default


> 
> 
> 1. So 'the tree' (/usr/portage/) is portage:portage  OK.
> 
> 2. and /etc/portages is root:root  except for distfiles (root:portage) OK.
> 
> 3. and /var/lib/layman  and subdirs are  root:root  ???
> Note, these are the overlays I use but do not hack on.

That's fine. If you only --sync as root it all works out

> 
> 
> 4. and /usr/local/portage isjames:james
> this where I hack on codes that are mostly other overlays that
> need enhancements or raw codes I am processing into ebuilds.
> 
> 5. /usr/local/experimental is  james:james   
> where I working on codes that can compile
> install or be removed without the baggage of portage/ebuilds. It
> will be for embedded and cluster/cloud/vm movements of binaries
> to attach directly to the 4.x kernel, dynamically.
> I'm working on a new build semantic with DAGs, Tup, ninja and CheckInstall
> 
> 
> So I can ignore (5) in make.conf. But I'm now getting ebuilds installed
> in /usr/local/portage, I think because of this line in my make.conf::
> 
> PORTDIR_OVERLAY="source /etc/portage/repos.conf/layman.conf"
> PORTDIR_OVERLAY="/usr/local/portage"

No man, rip that shit out. Delete both lines and replace with entries in
/etc/portage/repos.conf/

There was a news item on 2 Feb that gives full details.
Then emerge layman with use="sync-plugin-portage"

And btw, your second line overrides and replaces the first.

> For goals of 1-5 what are improvements (any and all suggestions) on
> make.conf I should make?  I need to ensure that overlays that I do
> not modify stay separate for the ebuild I modify. In fact some packages
> are in both 3 and 4.  I use git to seed category 4 so what caveates
> do I use to ensure that git only seeds categroy 4 packages (ebuilds)once
> and does not contaminant my 'old school; vim' hackery.

Edit only inside the overlay you want to change. If you have another
overlay that is essentially read-only (or you don't change), and you do
edit it, well then you just changed it and the computer will follow your
lead :-)

so vi then git add/commit/push the stuff you edit.

Or maybe I don't grok what you mean here

> 
> 
> I think this is the only change I need::
> PORTDIR_OVERLAY="/usr/local/portage" ==>
> PORTDIR_OVERLAY="/var/lib/layman"

No. DoItRite as above. That PORTDIR_OVERLAY crap never did work right -
all overlays were essentially considered equal and it would be pot luck
where your next ebuild comes from


> Or does layman and git (syncs) know where to place things. I do use
> 'git clone' to seed category 4 packages-->ebuilds and will
> eventually be use more of git's features to push out updates.

layman doesn't know anything other than what's in it's config. There's
no magic. If you tell it a repo in mastered at place X, and you make
changes to X, layman will sync those changes.

Don't use 'git clone' for this. A clone is your first checkout. Rather
push the stuff you edit and pull updates from there with layman

> 
> I just gotta get this straight, consistent and keep things seperate
> in my mind, because being an old fart, reading lots of codes, sometimes
> I forget the origins of hacks. (yea yea document the code you old hack)



-- 
Alan McKinnon
alan.mckin...@gmail.com




[gentoo-user] Re: portage directory ownerships?

2015-09-16 Thread james
Neil Bothwick  digimed.co.uk> writes:



> > Here, all of /etc/portage is root:root
> > The tree and all overlays are portage:portage

> Just to add some confusion to the mix



Good example and it got me thinking

> So some are portage:portage, some are root:root - all use /var/portage
> for $PORTDIR so that's not an issue. One of the portage:portage ones is
> the one that syncs with the mirrors and acts as an rsync host for the
> others, this may or may not be significant.

I might swith to /var/portage on a new install. Whats the pedantic 
reasons for for it? On an SSD for speed ? tmpdir? I'm curious, so tell me more.


1. So 'the tree' (/usr/portage/) is portage:portage  OK.

2. and /etc/portages is root:root  except for distfiles (root:portage) OK.

3. and /var/lib/layman  and subdirs are  root:root  ???
Note, these are the overlays I use but do not hack on.


4. and /usr/local/portage isjames:james
this where I hack on codes that are mostly other overlays that
need enhancements or raw codes I am processing into ebuilds.

5. /usr/local/experimental is  james:james   
where I working on codes that can compile
install or be removed without the baggage of portage/ebuilds. It
will be for embedded and cluster/cloud/vm movements of binaries
to attach directly to the 4.x kernel, dynamically.
I'm working on a new build semantic with DAGs, Tup, ninja and CheckInstall


So I can ignore (5) in make.conf. But I'm now getting ebuilds installed
in /usr/local/portage, I think because of this line in my make.conf::

PORTDIR_OVERLAY="source /etc/portage/repos.conf/layman.conf"
PORTDIR_OVERLAY="/usr/local/portage"

For goals of 1-5 what are improvements (any and all suggestions) on
make.conf I should make?  I need to ensure that overlays that I do
not modify stay separate for the ebuild I modify. In fact some packages
are in both 3 and 4.  I use git to seed category 4 so what caveates
do I use to ensure that git only seeds categroy 4 packages (ebuilds)once
and does not contaminant my 'old school; vim' hackery.


I think this is the only change I need::
PORTDIR_OVERLAY="/usr/local/portage" ==>
PORTDIR_OVERLAY="/var/lib/layman"

Or does layman and git (syncs) know where to place things. I do use
'git clone' to seed category 4 packages-->ebuilds and will
eventually be use more of git's features to push out updates.

I just gotta get this straight, consistent and keep things seperate
in my mind, because being an old fart, reading lots of codes, sometimes
I forget the origins of hacks. (yea yea document the code you old hack)

All suggestions welcome.
TIA,
James







Re: [gentoo-user] Re: Can't paste from selection in gtk-3 apps

2015-09-16 Thread J. Roeleveld
On Tuesday, September 15, 2015 06:57:36 PM Grant Edwards wrote:
> On 2015-09-15, Grant Edwards  wrote:
> > In most X11 apps I can select some text and then paste it somewhere
> > else with a middle-click, or dump it to stdout with the command 'xclip
> > -o'.  That doesn't work for highligted text in gtk-3 apps (meld,
> > evince, audacious, etc.).  After selecting text in a gtk-3 app, if I
> > middle-click in a terminal window it does nothing and 'xclip -o' just
> > hangs.  Selecting text elsewhere will deselect the text in the gtk-3
> > app, so gtk-3 isn't _completely_ ignoring X11 clipboards/buffers.
> > 
> > Any ideas why gtk-3 copy/paste is broken and how to fix it?
> 
> Ah, it turns out it's only a problem if you have multiple screens: you
> can only paste a gtk-3 selection if the destination is on the same X11
> screen as the source.  I'm pretty sure this is a known problem, but
> I'm having trouble finding it again in the Gnome bugtracker...

Must be related to gtk-3 then.
I use 2 screens extensively and never experienced any issues like you 
describe.

Am surprised it would respond differently between GTK-3 and non-GTK-3 apps.

I don't configure anything special for multiple screens in the past few years.

--
Joost



[gentoo-user] emaint -C logs

2015-09-16 Thread Peter Humphrey
Hello list,

I've been playing with emaint and on one box I got an error message:

# emaint -C logs

PORT_LOGDIR_CLEAN command returned None
See the make.conf(5) man page for PORT_LOGDIR_CLEAN usage instructions.

This is needlessly complex. In fact all I needed was for PORT_LOGDIR to be 
defined in make.conf.

Just thought I'd mention it in case anyone else was similarly afflicted.

-- 
Rgds
Peter




Re: [gentoo-user] portage directory ownerships?

2015-09-16 Thread Neil Bothwick
On Tue, 15 Sep 2015 22:25:15 +0200, Alan McKinnon wrote:

> > That got me thinking. Everywhere that portage operates or owns
> > things, should the ownership not be portage.portage
> > and what would the typical permissions be?  
> 
> Here, all of /etc/portage is root:root
> The tree and all overlays are portage:portage

Just to add some confusion to the mix

root@fenchurch: drwxr-xr-x 1 root root 3378 Aug 25 08:43 /var/portage
root@hactar: drwxr-xr-x 1 root root 3378 Aug 25 07:55 /var/portage
root@vroomfondel: drwxr-xr-x 168 root root 4096 Aug 25 08:03 /var/portage
root@slartibartfast: drwxr-xr-x 1 portage portage 3378 Aug 25 08:05 /var/portage
root@lunkwill: drwxr-xr-x 168 portage portage 4096 Aug 25 07:35 /var/portage
root@quordlepleen: drwxr-xr-x 1 root root 3378 Aug 25 08:04 /var/portage

So some are portage:portage, some are root:root - all use /var/portage
for $PORTDIR so that's not an issue. One of the portage:portage ones is
the one that syncs with the mirrors and acts as an rsync host for the
others, this may or may not be significant.

Downloading a portage snapshot shows it all to be owned by
portage:portage, so I guess that's as close as we are going to get to a
definitive answer.


-- 
Neil Bothwick

If at first you don't succeed, you'll get a lot of free advice from
folks who didn't succeed either.


pgpUGIRCpxZVl.pgp
Description: OpenPGP digital signature


Re: [gentoo-user] portage directory ownerships?

2015-09-16 Thread Fernando Rodriguez
On Wednesday, September 16, 2015 8:01:56 AM Alan McKinnon wrote:
> On 16/09/2015 00:36, Fernando Rodriguez wrote:
> > On Tuesday, September 15, 2015 10:25:15 PM Alan McKinnon wrote:
> >> On 15/09/2015 22:09, james wrote:
> >>> Hello,
> >>>
> >>> So looking at /etc/portage/repos.conf, it seems root.root owns these
> >>> files; shouldn't it be portage.portage? and /usr/portage
> >>>
> >>> That got me thinking. Everywhere that portage operates or owns
> >>> things, should the ownership not be portage.portage
> >>> and what would the typical permissions be?
> >>
> >> Here, all of /etc/portage is root:root
> >> The tree and all overlays are portage:portage
> >>
> >> You can make a local overlay owned by user you want, stuff you hack away
> >> at yourself should probably be james:james or james:users
> >>
> >> Typically, permissions in /etc/portage are the usual 755 for dirs and
> >> 644 for files
> >>
> >> I set overlays and the tree to be 2775 for dirs and 664 for files
> >>
> >>>
> >>> Is there a master list I can look at? Surely root not own all
> >>> these dirs, like /usr/portage/* ? My /usr/portage is root.root
> >>> and 755 on permissions, is that right?
> >>
> >> Permissions should be what YOU need them to be on your computer. There's
> >> a default, it's what portage makes them when you install stuff
> >>
> >>>
> >>> If so, why?
> >>
> >> Only root should change the master config files in /etc, just like in
> >> all other apps
> >> IIRC emerge can drop privs to a user account, if that user is portage
> >> then portage must own the files
> > 
> > It is true that portage drops privileges to the portage account (unless 
the 
> > ebuild has RESTRICT="userpriv" or I think FEATURES="-userpriv" on 
make.conf) 
> > but it doesn't need to write to the portage tree except to the distfiles 
> > directory so I don't know of any reason to have everything owned by 
> > portage:portage if the perms are 755/644.
> 
> portage also syncs the tree. For that it needs write perms.
> 
> > 
> > Mine is owned by root:root because it got borked one time after a sync so 
I 
> > deleted it and copied from another box manually. The only problem I ever 
had 
> > is that a fetch failed, and I just chowned the distfiles dir to 
portage:portage 
> > to fix it. Only recently it was pointed to me on this list that it was 
supposed 
> > to be portage:portage. I never changed it back to portage:portage but I 
made a 
> > mental note not to forget about it in case of trouble, that way I'll learn 
why 
> > that's the default if/when something breaks :) Besides it offers some 
(limited) 
> > protection against an ebuild accidentally writing to your portage tree.
> > 
> >>>
> >>> In my /usr/local/portage and it's subdirs where I hack on many 
> >>> ebuild, portage.portage owns everything.?
> >>
> >> Make your life easy, chaown that stuff to james
> > 
> > I personally prefer root:root because I think it is more secure. If you 
let 
> > somebody use your account even for a minute s/he could modify an ebuild 
> > without a password to install whatever s/he wants next time you run an 
update.
> 
> I'll argue that it's less secure. Giving someone else a gap to modify
> your ebuilds when you accidentally leave the computer unlocked is a rare
> event whereas you modifying your own ebuilds like james does is a common
> event.
> 
> If an overlay is root:root then he has to be root every time he works on
> it. If he then commits that rare blunder of leaving the computer
> unlocked, Murphy says he'll do it with a root shell open.

I also have the habit of never opening root shells unless absolutely necessary 
(which is next to never) and when I do I'm very conscious about it so that 
won't be a problem for me. I do a lot of ebuild hacking and that does mean I 
type my password a lot but you get used to it.

> While it is entirely possible to have a rogue colleague install a dodgy
> ebuild, that attacker would have to know exactly what to install where
> and would have to have the ebuild on hand to slip it in during the very
> few minutes available. To my eye that's a very small window of
> opportunity and needs a perfect storm to pull it off = vanishingly small
> risk

If that was my mission I just pick something that I know you run at startup 
like udev (I may pick something more trivial if possible to minimize the 
chance of you noticing). I'd bump the version and have the ebuild install my 
evil program along with it and add a few liner patch to fork() and execve() my 
program or just make my program a patch to the main prog. Then I'll put it on 
a webserver along with a script that does to work for me. Now I just need to 
run a single command to download and execute the script. 

So granted, it takes planning, and maybe some social engineering or other 
methods to get details about your system but once I get the chance it'll take 
only a few seconds and next time you update I'd have root access.

-- 
Fernando Rodriguez