[gentoo-user] Chrony-2.2 failing

Hello list, Chrony has been upgraded from 2.1.1 to 2.2 this week. The new version seems to run just fine on this amd64 box, but on my x86 Atom box it fails to start thus: # /etc/init.d/chronyd start * Starting chronyd ... * start-stop-daemon: caught an interrupt * start-stop-daemon:

Re: [gentoo-user] Bind stole my /

On Wed, Nov 18, 2015 at 9:00 PM, Jarry wrote: > On 10-Nov-15 14:22, Tom H wrote: >> On Tue, Nov 10, 2015 at 12:32 AM, Mike Gilbert wrote: >>> >>> Can you try replacing /etc/mtab with a symlink to /proc/self/mounts to >>> see if it makes any difference?

Re: [gentoo-user] Chrony-2.2 failing

On Thursday 19 November 2015 10:49:08 Peter Humphrey wrote: >Hello list, > [...] > >What's more, earlier versions had a decent man page and heavily commented >chronyd.conf, but now the chrony.conf man page has been cut to a bare >minimum and instead refers to a file chrony.txt "included in the

[gentoo-user] combining pdf files, different size

I'm trying to use "pdfjoin" to combine two different page size pdf files but it will not let me. Is it possible. I don't see any switches to ignore page size. -- Thelma

[gentoo-user] How to set up monospaced xterm fonts?

Lucidasanstypewriter-12 is still my favourite xterm font. A long time ago, it switched from ISO8859-1 to ISO10646. Fortunately, I had 2 machines, and salvaged the /usr/share/fonts directory from one, and still insert it in place of whatever portage gives me. I realize that it's an ugly hack,

Re: [gentoo-user] This is what I get for trying...

2015-11-19 9:17 GMT-06:00 Alan Grimes : > Naturally, the instructions on the gentoo wiki FAIL > > > > https://wiki.gentoo.org/wiki/Basic_guide_to_write_Gentoo_Ebuilds > > > atg@tortoise ~/archive $ ebuild seamonkey-2.35.ebuild clean merge >

[gentoo-user] OT bitcoind alternative

Hello all, Sorry for the off-topicness, I run bitcoind on a rather large VM with my original bitcoin qt wallet. It is working well, but bitcoin core is very resource hungry. I am looking for an alternative that I can run without a gui on the VM, that will also be able to read my wallet.dat Tried

Re: [gentoo-user] Re: Big problem: Seamonkey

Okay, since just dumping the legacy e-build into the portage tree would be too easy, it was prevented. How do I build an ebuild out-of-tree? =( I've kinda wanted to know how to do this for years but was too lazy to track down the information but these later versions of Seamonkey are so

[gentoo-user] This is what I get for trying...

Naturally, the instructions on the gentoo wiki FAIL https://wiki.gentoo.org/wiki/Basic_guide_to_write_Gentoo_Ebuilds atg@tortoise ~/archive $ ebuild seamonkey-2.35.ebuild clean merge Appending /home to PORTDIR_OVERLAY... !!! Repository 'x-home' is missing

Re: [gentoo-user] Big problem: Seamonkey

Alan Grimes wrote: > Hey, both Seamonkey 2.38 and 2.39 are unstable to the point of being > utterly unusable, I need to re-install 2.35 but it has already been > removed from Portage, HELP!! > > There are some mutterings on the upstream bugtracker about it being > related to how Cairo is being

Re: [gentoo-user] Re: Big problem: Seamonkey

Alan Grimes wrote: > Okay, since just dumping the legacy e-build into the portage tree would > be too easy, it was prevented. How do I build an ebuild out-of-tree? =( > create a portage overlay and put your ebuild in there, then mask seamonkey > 2.38 in package.mask: $ ll

Re: [gentoo-user] combining pdf files, different size

On Thu, 19 Nov 2015 19:17:47 -0700 the...@sys-concept.com wrote: > On 11/19/2015 06:39 PM, the...@sys-concept.com wrote: > > I'm trying to use "pdfjoin" to combine two different page size pdf files > > but it will not let me. Is it possible. > > > > I don't see any switches to ignore page size.

Re: [gentoo-user] combining pdf files, different size

On 11/19/2015 06:39 PM, the...@sys-concept.com wrote: > I'm trying to use "pdfjoin" to combine two different page size pdf files > but it will not let me. Is it possible. > > I don't see any switches to ignore page size. "pdfunite" works but I have to add/specify output file name. With

Re: [gentoo-user] Re: Big problem: Seamonkey

Todd Goodman wrote: > I believe using PORTDIR_OVERLAY is now deprecated and overlays are > configured in /etc/portage/repos.conf/* > > Check out: > > https://wiki.gentoo.org/wiki/Overlay/Local_overlay Good to know, I suppose the bit: root # repoman manifest is equivalent to: root #

Re: [gentoo-user] Re: Big problem: Seamonkey

* Raffaele BELARDI [151119 10:24]: > Alan Grimes wrote: > > Okay, since just dumping the legacy e-build into the portage tree would > > be too easy, it was prevented. How do I build an ebuild out-of-tree? =( > > > > create a portage overlay and put your ebuild in there,

Re: [gentoo-user] Re: Big problem: Seamonkey

* Raffaele BELARDI [151119 10:45]: > Todd Goodman wrote: > > I believe using PORTDIR_OVERLAY is now deprecated and overlays are > > configured in /etc/portage/repos.conf/* > > > > Check out: > > > > https://wiki.gentoo.org/wiki/Overlay/Local_overlay > > Good to know, I

Re: [gentoo-user] This is what I get for trying...

On Thu, Nov 19, 2015 at 10:17:03AM -0500, Alan Grimes wrote: > Naturally, the instructions on the gentoo wiki FAIL > > https://wiki.gentoo.org/wiki/Basic_guide_to_write_Gentoo_Ebuilds > > > atg@tortoise ~/archive $ ebuild seamonkey-2.35.ebuild clean merge >

[gentoo-user] https://wiki.gentoo.org/wiki/Traffic_shaping

Hi, does anyone know what happened to the 'Ingress Qdisc' kernel option mentioned on [1], and what the replacement would be? I'm trying to follow [2] to set up some simple traffic shaping with the intention to improve VOIP quality. [1]: https://wiki.gentoo.org/wiki/Traffic_shaping [2]:

Re: [gentoo-user] Chrony-2.2 failing

On Thu, Nov 19, 2015 at 12:49 PM, Peter Humphrey wrote: > Hello list, > > Chrony has been upgraded from 2.1.1 to 2.2 this week. The new version seems > to run just fine on this amd64 box, but on my x86 Atom box it fails to > start > thus: > > # /etc/init.d/chronyd start >

Re: [gentoo-user] Chrony-2.2 failing

On 19/11/2015 12:49, Peter Humphrey wrote: > Hello list, > > Chrony has been upgraded from 2.1.1 to 2.2 this week. The new version seems > to run just fine on this amd64 box, but on my x86 Atom box it fails to start > thus: > > # /etc/init.d/chronyd start > * Starting chronyd ... > *