Re: [gentoo-user] Layman errors. Google ain't helping.

2011-09-04 Thread Andrea Conti
>> No such file or directory: '/var/lib/layman/make.config'
^^
> -rw-r--r-- 1 root root 64 Sep  3 22:49 /var/lib/layman/make.conf
  
That's either a typo or the source of the problem :)

andrea





Re: [gentoo-user] systemd

2011-09-04 Thread Peter Humphrey
On Sunday 04 September 2011 01:44:31 I wrote:
> On Sunday 04 September 2011 01:19:51 Alan McKinnon wrote:
> > It doesn't support KMail folders directly (Claws doesn't do traditional
> > MailDir, it's native format is MH) but you can find import scripts
> > here:
> > 
> > http://www.claws-mail.org/tools.php?section=downloads
> > 
> > There are kmail-specific scripts listed
> 
> Good stuff! Thanks Alan.

Except that, when I ran the converter script and restarted Claws, the folder 
structure had been duplicated but they were all empty. I have another head-
scratching opportunity...

-- 
Rgds
Peter   Linux Counter 5290, 1994-04-23



[gentoo-user] BadRAM patch

2011-09-04 Thread William Kenworthy
Do any of the gentoo kernels have the badram patch? - just found a 2G
stick with one stuck bit :(

Googling for this shows activity up to 2.6.28 - then nothing.  Did it
get included in the kernel?

Otherwise its roll my own ...

BillK






Re: [gentoo-user] Re: Typewriter sound

2011-09-04 Thread Alex Schuster
Grant Edwards writes:

> On 2011-08-31, Paul Hartman  wrote:
>> On Wed, Aug 31, 2011 at 12:46 PM, Grant Edwards
>>  wrote:
 b) old school pc-speaker in your computer
[...]
>> I think it just made the generic "beep" (or a beep short enough and
>> low enough in tone to sound similar to a click)
> 
> I checked, and I do have the old standard PC-speaker connected to the
> motherboard, and "xset c" still does nothing.

Does the speaker actually work? Is the pcspkr module loaded?

Wonko



Re: [gentoo-user] /etc/modules, 2.6, and 3.0

2011-09-04 Thread Michael Orlitzky
On 09/03/2011 02:25 PM, fe...@crowfix.com wrote:
> Upgrading /etc/modules, I notice it has 2_6 for all its examples;
> should this be changed to 3_0 if running a 3.0 kernel?  I am going to
> expand it with both, for the time being, but all the gentoo.org docs
> still show 2_6, and it made me think, always a confusing misstep.
> 

You can also drop the version number entirely, e.g.,

  modules="${modules} powernow-k8"
  module_powernow_k8_args=""

  modules="${modules} r8169"
  module_r8169_args=""

  ...



Re: [gentoo-user] Layman errors. Google ain't helping.

2011-09-04 Thread Dale

cov...@ccs.covici.com wrote:

Dale  wrote:


I'm working on the install for my friend still.  Since KDE4 wants to
stay in bed, I thought I would try KDE3 from the overlay.  I read not
long ago that it is still somewhat kicking.  So I installed layman and
added the overlay.  I then added this line to make.conf:

source /var/lib/layman/make.conf

When I add that, I get errors like this:

!!! Parse error in '/etc/make.conf': source command failed: [Errno 2]
No such file or directory: '/var/lib/layman/make.config'
!!! Parse error in '/etc/make.conf': source command failed: [Errno 2]
No such file or directory: '/var/lib/layman/make.config'

fireball / # eix-update
Reading Portage settings ..
failed to source '/var/lib/layman/make.config'
Building database (/var/cache/eix) ..
[0] "gentoo" /usr/portage/ (cache: metadata-flat)

I have googled and followed some Gentoo docs and this error just keeps
popping up.  What am I doing wrong?

Keep in mind I am doing a 32 bit install on a 64 bit machine.  I am
following the guide that was linked to earlier.

Ideas?

I think you have run into the fact that you only put that source line
after you have added your first overlay -- is this the case?



I did do it afterwards because when I read the guide, it said to do it 
afterwards.  If you do it earlier portage will complain.  It appears 
that has changed.  What do I do to fix this mess?


Dale

:-)  :-)



Re: [gentoo-user] Layman errors. Google ain't helping.

2011-09-04 Thread Dale

Andrea Conti wrote:

No such file or directory: '/var/lib/layman/make.config'

 ^^

-rw-r--r-- 1 root root 64 Sep  3 22:49 /var/lib/layman/make.conf

   
That's either a typo or the source of the problem :)

andrea



That's what the guide has:

# If you have>=app-portage/layman-1.3.0
# source "/var/lib/layman/make.conf"

I'm using 1.4 but that is also what the message said after I emerge it.  I 
actually copied it from there.

Ideas?

Dale

:-)  :-)





[gentoo-user] del.uged want to start on net.eth1, only eth0 is there

2011-09-04 Thread Lars Madson
Hi,

After upgrading world, I might have gone a bit fast on the last conf files
that I update with etc-update.
Now that I restart deluged, the init script brings up eth1 but I only have
eth0 correctly setup.
It should use eth0. In rc-update list I see net.eth1, no net.eth0, if it can
help.

My question is when this net.eth1 is called so that I could fix this wrong
routing?

thx
Laurent


Re: [gentoo-user] BadRAM patch

2011-09-04 Thread William Kenworthy
Looks like you use a "memmap=1M$157M" (in my case) argument when booting
these days.  

BillK


On Sun, 2011-09-04 at 20:38 +0800, William Kenworthy wrote:
> Do any of the gentoo kernels have the badram patch? - just found a 2G
> stick with one stuck bit :(
> 
> Googling for this shows activity up to 2.6.28 - then nothing.  Did it
> get included in the kernel?
> 
> Otherwise its roll my own ...
> 
> BillK
> 
> 
> 
> 





Re: [gentoo-user] del.uged want to start on net.eth1, only eth0 is there

2011-09-04 Thread Dale

Lars Madson wrote:

Hi,

After upgrading world, I might have gone a bit fast on the last conf 
files that I update with etc-update.
Now that I restart deluged, the init script brings up eth1 but I only 
have eth0 correctly setup.
It should use eth0. In rc-update list I see net.eth1, no net.eth0, if 
it can help.


My question is when this net.eth1 is called so that I could fix this 
wrong routing?


thx
Laurent


If I understand this correctly, it sounds like udev has created a new 
nic for some reason.  Your file should be here and look something like this:


root@fireball / # cat /etc/udev/rules.d/70-persistent-net.rules
# This file was automatically generated by the /lib64/udev/write_net_rules
# program, run by the persistent-net-generator.rules rules file.
#
# You can modify it, as long as you keep each rule on a single
# line, and change only the value of the NAME= key.

# PCI device 0x10ec:0x8168 (r8169)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", 
ATTR{address}=="1c:6f:65:4c:91:c7", ATTR{dev_id}=="0x0", 
ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"

root@fireball / #

If you only have one nic but have two lines there, I would just delete 
the whole file and reboot.  When you do and udev comes back up, it will 
create a new file and it resets its naming and such which should get you 
back to net.eth0 again.


I think you can kill udev and restart it if you don't want to reboot for 
some reason.


Again, this is if I understand the problem correctly.  If this makes 
sense, I may on track.  If not, I may be missing something and you may 
want to wait on someone else to chime in.


Dale

:-)  :-)



Re: [gentoo-user] Layman errors. Google ain't helping.

2011-09-04 Thread James Broadhead
make.config != make.conf

:)



Re: [gentoo-user] Layman errors. Google ain't helping.

2011-09-04 Thread Dale

James Broadhead wrote:

make.config != make.conf

:)





Oh yea !!!  Much better.  I knew it had to be something stupid that only 
I would do.  I copied that from somewhere tho.  I need to find out where 
so I can report it.  I get this now:


fireball / # eix-update
Reading Portage settings ..
Building database (/var/cache/eix) ..
[0] "gentoo" /usr/portage/ (cache: metadata-flat)
 Reading category 155|155 (100%) Finished
[1] "kde-sunset" /var/lib/layman/kde-sunset (cache: 
parse|ebuild*#metadata-flat#assign)

 Reading category  17|155 ( 10%): app-misc .. *


THANKS MUCH 

Dale

:-)  :-)



Re: [gentoo-user] del.uged want to start on net.eth1, only eth0 is there

2011-09-04 Thread Lars Madson
hm there's only one line in my /etc/udev/rules.d/70-persistent-net.rules:

# This file was automatically generated by the /lib64/udev/write_net_rules
# program run by the persistent-net-generator.rules rules file.
#
# You can modify it, as long as you keep each rule on a single line.

# PCI device 0x10ec:0x8168 (r8169)
SUBSYSTEM=="net", DRIVERS=="?*", ATTR{address}=="00:1c:c0:5a:81:dc",
KERNEL=="eth*", NAME="eth0"


2011/9/4 Dale 

> Lars Madson wrote:
>
>> Hi,
>>
>> After upgrading world, I might have gone a bit fast on the last conf files
>> that I update with etc-update.
>> Now that I restart deluged, the init script brings up eth1 but I only have
>> eth0 correctly setup.
>> It should use eth0. In rc-update list I see net.eth1, no net.eth0, if it
>> can help.
>>
>> My question is when this net.eth1 is called so that I could fix this wrong
>> routing?
>>
>> thx
>> Laurent
>>
>
> If I understand this correctly, it sounds like udev has created a new nic
> for some reason.  Your file should be here and look something like this:
>
> root@fireball / # cat /etc/udev/rules.d/70-**persistent-net.rules
> # This file was automatically generated by the /lib64/udev/write_net_rules
> # program, run by the persistent-net-generator.rules rules file.
> #
> # You can modify it, as long as you keep each rule on a single
> # line, and change only the value of the NAME= key.
>
> # PCI device 0x10ec:0x8168 (r8169)
> SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",
> ATTR{address}=="1c:6f:65:4c:**91:c7", ATTR{dev_id}=="0x0",
> ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"
> root@fireball / #
>
> If you only have one nic but have two lines there, I would just delete the
> whole file and reboot.  When you do and udev comes back up, it will create a
> new file and it resets its naming and such which should get you back to
> net.eth0 again.
>
> I think you can kill udev and restart it if you don't want to reboot for
> some reason.
>
> Again, this is if I understand the problem correctly.  If this makes sense,
> I may on track.  If not, I may be missing something and you may want to wait
> on someone else to chime in.
>
> Dale
>
> :-)  :-)
>
>


Re: [gentoo-user] del.uged want to start on net.eth1, only eth0 is there

2011-09-04 Thread Dale

Lars Madson wrote:

hm there's only one line in my /etc/udev/rules.d/70-persistent-net.rules:

# This file was automatically generated by the /lib64/udev/write_net_rules
# program run by the persistent-net-generator.rules rules file.
#
# You can modify it, as long as you keep each rule on a single line.

# PCI device 0x10ec:0x8168 (r8169)
SUBSYSTEM=="net", DRIVERS=="?*", ATTR{address}=="00:1c:c0:5a:81:dc", KERNEL=="eth*", 
NAME="eth0"



Must be something else then.  My new nickname is stumped.  lol  At least 
we know what it is not tho.


Dale

:-)  :-)


Re: [gentoo-user] del.uged want to start on net.eth1, only eth0 is there

2011-09-04 Thread Mark Knecht
On Sun, Sep 4, 2011 at 6:27 AM, Lars Madson  wrote:
> Hi,
> After upgrading world, I might have gone a bit fast on the last conf files
> that I update with etc-update.
> Now that I restart deluged, the init script brings up eth1 but I only have
> eth0 correctly setup.
> It should use eth0. In rc-update list I see net.eth1, no net.eth0, if it can
> help.
> My question is when this net.eth1 is called so that I could fix this wrong
> routing?
> thx
> Laurent

Check /etc/init.d to ensure you have links for both eth0 and eth1.
Then check both /etc/conf.d/net &
/etc/udev/rules.d/70-persistent-net.rules to ensure you have both
interfaces set up as you want them, double checking each interface's
MAC address using ifconfig against any values listed in
70-persistent-net.rules, if any.

HTH,
Mark



[gentoo-user] Re: del.uged want to start on net.eth1, only eth0 is there

2011-09-04 Thread walt
On 09/04/2011 06:27 AM, Lars Madson wrote:
> Hi,
> 
> After upgrading world, I might have gone a bit fast on the last conf files 
> that I update with etc-update.
> Now that I restart deluged, the init script brings up eth1 but I only have 
> eth0 correctly setup.
> It should use eth0. In rc-update list I see net.eth1, no net.eth0, if it can 
> help.
> 
> My question is when this net.eth1 is called so that I could fix this wrong 
> routing?

If you are using only one ethernet adapter then you should remove
/etc/init.d/net.eth1.

If eth1 seems to exist somewhere but it really shouldn't exist, then
you should delete /etc/udev/rules.d/70-persistent-net.rules and reboot.
That should get rid of eth1.

If you really have two ethernet adapters then my answer is probably wrong.




Re: [gentoo-user] Help needed:jpeg_resync_to_restart() and zathura pdf reader

2011-09-04 Thread Ignas Anikevicius
Hello,

On 04/09/11 01:29, Michael Orlitzky wrote:
> RDEPEND=">=app-text/mupdf-0.8"

Oh sorry, I have forgotten to tell that I am using the girara branch,
which uses plugins and depends only on girara libs, it should be
fixed to have that, but I did not bother to do it previously as I had
all the dependencies tracked by hand.

I have EGIT_BRANCH="girara" in '/etc/portage/env/app-text/zathura'.

>
> And have you tried using libjpeg instead of the -turbo version?
>
This is were I was wondering as well, but did not have chance to check
it. Also, Arch guys are using the turbo version and I was thinking
that it should not be an issue, but I will try and see whether it also
does not work with non turbo version.

Cheers,
Ignas


Re: [gentoo-user] who needs Java ?

2011-09-04 Thread Philip Webb
110817 Philip Webb wrote:
> 110815 Florian Philipp most helpfully wrote:
>>   
>> http://wiki.services.openoffice.org/w/index.php?title=Java_and_OpenOffice.org&oldid=15
> I deleted 'java' from the  make.conf  USE list
> & recompiled Libreoffice (latest testing) + Cups +  2  deps for KDE3.
> Printing is ok from LO & Vim (via the Printdialog extension);
> LO help calls up a WWW page, which doesn't help,
> but I've downloaded  2  PDFs with the help for Writer + Calc,
> which sb better than the rather clumsy version included inside OO ;
> the  2  KDE3 apps continue to start (Kmahjongg Kworldclock).
> Emerge throws out a dire warning re compiling LO without Java,
> but doesn't say exactly what the dire results wb.

I have submitted bug # 381823 to suggest a more appropriate warning
from the LO ebuild.

I have unmerged all the Java pkgs & removed the 'gcj' USE flag.
Gcc 4.5.3-r3 now compiles much more quickly (Core 2 Duo,  2 GB  memory) :
  (1st time) by Gcc 4.4.5 with 'gcj' it took  40 min ;
  (2nd time) by Gcc 4.5.3-r3 without 'gcj' it took 24 min .
Doing a regular weekly system update yesterday, I had the feeling
that it was quicker with Gcc 4.5.3 , but have no actual figures.

The only remaining small puzzle was 'emerge -Dup world' (testing version),
which wanted to remerge Pdftk 1.44 using Gcc with 'gcj' enabled,
but 'emerge -pv pdftk' offered to go ahead without any such changes.
Pdftk is useful, but not so useful as to force me to re-install Java:
I haven't tested whether it still works.

HTH others

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




[gentoo-user] problem with dump

2011-09-04 Thread Allan Gottlieb
I noticed that the last two (daily) dumps have been bad (too short,
unreadable by restore).

I tried to remerge app-arch/dump both 0.4.44-r1 (which I had before)
and o.4.44.  Both failed in the compile phase (details below).
This seem a little frightening to me.  Can someone tell me what has
happened

thanks,
allan

system is ~amd64.  The filesystem is ext3

x86_64-pc-linux-gnu-gcc -c -D_BSD_SOURCE -D_USE_BSD_SIGNAL  -march=native -O2 
-pipe -ggdb  -pipe  -I.. -I../compat/include -I/usr/include/ext2fs 
-I/usr/include/et   -I../dump -DRDUMP -DRRESTORE -DLINUX_FORK_BUG -DHAVE_LZO 
-D_PATH_DUMPDATES=\"/etc/dumpdates\" -D_DUMP_VERSION=\"0.4b44\" traverse.c 
-o traverse.o
x86_64-pc-linux-gnu-gcc -c -D_BSD_SOURCE -D_USE_BSD_SIGNAL  -march=native -O2 
-pipe -ggdb  -pipe  -I.. -I../compat/include -I/usr/include/ext2fs 
-I/usr/include/et   -I../dump -DRDUMP -DRRESTORE -DLINUX_FORK_BUG -DHAVE_LZO 
-D_PATH_DUMPDATES=\"/etc/dumpdates\" -D_DUMP_VERSION=\"0.4b44\" unctime.c 
-o unctime.o
sed -e "s|__DUMPDATES__|/etc/dumpdates|g" \
-e "s|__DATE__|June 10, 2011|g" \
-e "s|__VERSION__|0.4b44|g" dump.8.in > dump.8
traverse.c: In function ‘dumpino’:
traverse.c:1000:49: error: ‘struct struct_ext2_filsys’ has no member named 
‘fragsize’
traverse.c:1001:58: error: ‘struct struct_ext2_filsys’ has no member named 
‘fragsize’
traverse.c:1002:24: error: ‘struct struct_ext2_filsys’ has no member named 
‘fragsize’
traverse.c:1002:24: error: ‘struct struct_ext2_filsys’ has no member named 
‘fragsize’
traverse.c: In function ‘blksout’:
traverse.c:1277:9: error: ‘struct struct_ext2_filsys’ has no member named 
‘fragsize’
make[1]: *** [traverse.o] Error 1



Re: [gentoo-user] problem with dump

2011-09-04 Thread Alex Schuster
Allan Gottlieb writes:

> I noticed that the last two (daily) dumps have been bad (too short,
> unreadable by restore).
> 
> I tried to remerge app-arch/dump both 0.4.44-r1 (which I had before)
> and o.4.44.  Both failed in the compile phase (details below).
> This seem a little frightening to me.  Can someone tell me what has
> happened

When I try to install it, I get the same problem. I guess somethings in
one of the header files it delivers has been changed in the recent
update of ext2fsprogs-libs from 1.41.14 to 1.42_pre0702. That was two
days ago, so might this be the reason for dump failing in the first place?

You could try to downgrade ext2fsprogs-libs, but don't unmerge it first,
I think this will break all sorts of things.

Someone should report a bug... if noone volunteers, I'll do this myself
some time tomorrow.

Wonko



Re: [gentoo-user] problem with dump

2011-09-04 Thread Allan Gottlieb
On Sun, Sep 04 2011, Alex Schuster wrote:

> Allan Gottlieb writes:
>
>> I noticed that the last two (daily) dumps have been bad (too short,
>> unreadable by restore).
>> 
>> I tried to remerge app-arch/dump both 0.4.44-r1 (which I had before)
>> and o.4.44.  Both failed in the compile phase (details below).
>> This seem a little frightening to me.  Can someone tell me what has
>> happened
>
> When I try to install it, I get the same problem. I guess somethings in
> one of the header files it delivers has been changed in the recent
> update of ext2fsprogs-libs from 1.41.14 to 1.42_pre0702. That was two
> days ago, so might this be the reason for dump failing in the first place?
>
> You could try to downgrade ext2fsprogs-libs, but don't unmerge it first,
> I think this will break all sorts of things.
>
> Someone should report a bug... if noone volunteers, I'll do this myself
> some time tomorrow.
>
>   Wonko

Thanks I just submitted 381835.  I wasn't sure of the etiquette do did
not mention your name in regards to ext2fsprogs-libs.

I feel much relieved after reading your (extremely prompt) reply.
Thank you.

allan



Re: [gentoo-user] OpenLDAP works only at localhost, not from outside

2011-09-04 Thread Johannes Geiss
On Fri, 02 Sep 2011 08:50:46 +0200
Joost Roeleveld  wrote:

> What do you mean with, "outside"?

I meant from another place via the Internet through my router to my
computer.


> [...]

> Hope this helps.

Yes, your suggestions helped. Thank you very much. Though it doesn't
solve the problem. Now I know I did everything right at my
LDAP-server, but the problem is my router (Speedport W 503V Typ C).
It's blocking some (not all) of the communication. I forwarded all
ports to my computer (ie. it's in the DMZ), but LDAP is not working
correctly. 

Bye
Johannes
-- 

--//--
 // PGP at https://pegasos.dnsalias.org/~jgeiss/pgpkey.txt
 \\ //Johannes R. GeissPandora, Zaurus, Pegasos, Amiga and C64
--\X/-


signature.asc
Description: PGP signature


[gentoo-user] What do new keywords mean?

2011-09-04 Thread Walter Dnes
  Whilst spelunking through ebuild files I notice that in addition to
the usual ~amd64 and ~x86 keywords, I also see ~amd64-linux and
~x86-linux.  What is the significance of this?

-- 
Walter Dnes 



Re: [gentoo-user] What do new keywords mean?

2011-09-04 Thread JD Horelick
On 5 September 2011 02:24, Walter Dnes  wrote:
>  Whilst spelunking through ebuild files I notice that in addition to
> the usual ~amd64 and ~x86 keywords, I also see ~amd64-linux and
> ~x86-linux.  What is the significance of this?
>
> --
> Walter Dnes 
>
>

As far as I am aware, Gentoo now supports something called prefix
installations where you can use portage on top of (at least some of)
the BSD's and Solaris and some old-school Unixes and other operating
systems that aren't linux, the ~x86-linux keywords are to just signify
that it's only being stabilised for linux, not any of the other
operating systems. I could be wrong though.