Re: [gentoo-user] How to handle "50 files in ... need updating."?

2003-11-07 Thread Juha-Mikko Ahonen
On pe, 2003-11-07 at 13:17, Karl-Heinz Zimmer wrote:
> Hi all,
> 
> after a world update now I got more than 50 config files needing
> updating and I am wondering if there might be a BETTER way of doing
> this - better than the usual manually diffing of each single file
> to see if I can take the old one or the new one or must merge with
> the new one...

Run etc-update as root. It will automatically scan the updated
configuration files and does the diffing for you. Most of your changed
config files are probably translations and such, which you can safely
update (replace original).

Note: If etc-update crashes on some config file (happened to me), just
rerun etc-update and continue with the next file. The crashed file
should work when there're no other config files left. And you can
allways manually update them.



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


Re: [gentoo-user] stupid newbie question on where network interfaces are defined

2003-11-07 Thread Juha-Mikko Ahonen
On pe, 2003-11-07 at 09:09, Chad Leigh -- Shire.Net LLC wrote:
> Ok, I have not seen where the network interfaces are defined.
> 
> On debian it is in /etc/network/interfaces
> on FreeBSD it is in /etc/rc.conf
> 
> What about gentoo?

/etc/conf.d/net



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


Re: [gentoo-user] emerge system prob

2003-10-28 Thread Juha-Mikko Ahonen
On ti, 2003-10-28 at 13:28, James Ferguson wrote:
> Hi, I'm trying to install on a new 1.4GHz Duron, one of the new 133FSB
> cpu's.
>  
> I'm Installing from stage 1 as I always do, (first time on this
> particular machine though)  but now when I get to emerge system i get
> the following error during configure of modutils 2.4.25:
>  
> checking whether the C compiler (gcc -mcpu=athlon -03 -pipe -yet_exec
> ) works
>  no
> configure: error: installation or configuration problem: C compiler
> cannot create executables.
>  
> I used mcpu=athlon to bootstrap.
>  
> at first I was using -mcpu=athon-xp  and when i got the error i
> thought mabey i was aiming to high so I started again from
> bootstrap using -mcpu=athlon.
>  
> can anyone shed a little light on this problem for me

I use -march=i686 for my Duron. It works fine enough. You can always use
i386 as a safe option.

Duron is a low-end processor, lacking the many neat features Athlon
processors have. Thus binaries utilising the features specific to Athlon
processors won't work with Durons. AFAIK there's no arch target for
Duron. You'll have to choose from one of the older Intel architectures:
386 and 686.



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


Re: [gentoo-user] XFree won't merge

2003-10-15 Thread Juha-Mikko Ahonen
On to, 2003-10-16 at 06:01, Brett I.Holcomb wrote:
> I'm doing an upgrade to XFree after an emerge synch.  It goes for a long time 
> then gives this error:
> 
> !!! copy 
> /var/tmp/portage/xfree-4.3.0-43/image/usr/X11R6/man/man3/xXdbeGetVisualInfo.3x.gz 
> -> /usr/X11R6/man/man3/XdbeGetVisualInfo.3x.gz failed.
> 
> !!! [Errno 22] Invalid argument
> 
> What argument  Is the ebuild porked - I sure didn't give it any argument.

I had one package (not XFree) with similarly bizarre error message:
permission denied. This message went away after I did a deep update of
world. So I suggest you try
emerge -uD system
Or if it doesn't solve the situation
emerge -uD world

It's likely that the XFree 4.3.0 ebuild uses some Portage feature which
is not available, or which works differently, in your version of
Portage.


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


Re: [gentoo-user] modules vs. compiled in

2003-10-03 Thread Juha-Mikko Ahonen
On pe, 2003-10-03 at 15:02, gabriel wrote:
> what if you disabled "loadable module support" in the kernel?

Wont help you as it is possible to insert code directly into the kernel
via /dev/kmem. Making the kernel memory read-only is an option for
combatting malicious kernel module injection. This can be done IIRC with
grsecurity patches.





signature.asc
Description: This is a digitally signed message part
This message has been 'sanitized'.  This means that potentially
dangerous content has been rewritten or removed.  The following
log describes which actions were taken.

Sanitizer (start="1065184022"):
  Forcing message to be multipart/mixed, to facilitate logging.
  Writer (pos="862"):
Part (pos="1031"):
  Part (pos="191"):
SanitizeFile (filename="unnamed.txt", mimetype="text/plain"):
  Match (names="unnamed.txt", rule="9"):
Enforced policy: accept

  Part (pos="690"):
SanitizeFile (filename="signature.asc", mimetype="application/pgp-signature"):
  Match (names="signature.asc", rule="15"):
ScanFile (file="/var/quarantine/att-signature.asc-3f7d6b16.KJ"):
  Scan succeeded, file is clean.

Enforced policy: accept


Anomy 0.0.0 : Sanitizer.pm
Sanitizer version 1.63 (Debian GNU/Linux)

--
[EMAIL PROTECTED] mailing list

Re: [gentoo-user] Kbd and mouse hang

2003-09-29 Thread Juha-Mikko Ahonen
On ma, 2003-09-29 at 17:05, Andreas Vinsander wrote:
> I am using PS/2 kbd and mouse, should I still expect USB hub to be the 
> reason?

Some VIA chipsets have problems if both USB hubs are enabled. This is
what happened to my brother -- he had his Windows hanging every now and
then until I told him to disable one of the USB hubs, which took care of
the problem.

Your problem may not be related to USB however, but if you're not using
USB anyways, it's safer to turn them off. It'll release some resources
for other processes.

> On the machine that is working, I have the same GPU, but the integrated 
> ethernet unit is a VIA rhine instead of a realtek.
> Right now I feel like a big questionmark... :-(

If you have APIC/IO-APIC enabled on the kernel, remove it. Either boot
with noapic or remove APIC support entirely from the kernel. APIC causes
some problems with at least on some VIA and SiS chipsets on uniprocessor
systems (and some AMD multiprocessor systems). To determine if it might
be APIC-related problem. Type dmesg on the command promt and see if
there's a "spurious interrupt" message anywhere. It won't appear
allways, but if it does, it's an APIC problem.

Hardware problems are hard to determine if there's no indication on what
might cause the problem. To be on the safer side, you could start off by
installing the latest 2.4 kernel, and hope it's a driver issue.


signature.asc
Description: This is a digitally signed message part
This message has been 'sanitized'.  This means that potentially
dangerous content has been rewritten or removed.  The following
log describes which actions were taken.

Sanitizer (start="1064901106"):
  Forcing message to be multipart/mixed, to facilitate logging.
  Writer (pos="856"):
Part (pos="1026"):
  Part (pos="191"):
SanitizeFile (filename="unnamed.txt", mimetype="text/plain"):
  Match (names="unnamed.txt", rule="9"):
Enforced policy: accept

  Part (pos="1742"):
SanitizeFile (filename="signature.asc", mimetype="application/pgp-signature"):
  Match (names="signature.asc", rule="15"):
ScanFile (file="/var/quarantine/att-signature.asc-3f7919f2.PG"):
  Scan succeeded, file is clean.

Enforced policy: accept


Anomy 0.0.0 : Sanitizer.pm
Sanitizer version 1.63 (Debian GNU/Linux)

--
[EMAIL PROTECTED] mailing list

Re: [gentoo-user] Kbd and mouse hang

2003-09-29 Thread Juha-Mikko Ahonen
On ma, 2003-09-29 at 15:52, Andreas Vinsander wrote:
> Some more information.
> 
> In addition to moving the mouse fast I can make the mouse hang by 
> switching (ctrl + alt + ) to and from X.
> 
> The MB includes video and sound controllers (cheap thing).
> 
> I have a similar machine running (not the same MB, though) flawlessly, 
> that's why I suspect something kernel related.

Try disabling one or both of your USB hubs from BIOS and see if it
still hangs. Some integrated GPUs have problem working with Linux.
You could update your kernel to the latest 2.4 release if you're
not already running one.


signature.asc
Description: This is a digitally signed message part
This message has been 'sanitized'.  This means that potentially
dangerous content has been rewritten or removed.  The following
log describes which actions were taken.

Sanitizer (start="1064842489"):
  Forcing message to be multipart/mixed, to facilitate logging.
  Writer (pos="781"):
Part (pos="950"):
  Part (pos="191"):
SanitizeFile (filename="unnamed.txt", mimetype="text/plain"):
  Match (names="unnamed.txt", rule="9"):
Enforced policy: accept

  Part (pos="978"):
SanitizeFile (filename="signature.asc", mimetype="application/pgp-signature"):
  Match (names="signature.asc", rule="15"):
ScanFile (file="/var/quarantine/att-signature.asc-3f7834f9.S9"):
  Scan succeeded, file is clean.

Enforced policy: accept


Anomy 0.0.0 : Sanitizer.pm
Sanitizer version 1.63 (Debian GNU/Linux)

--
[EMAIL PROTECTED] mailing list

Re: [gentoo-user] System crash

2003-09-29 Thread Juha-Mikko Ahonen
On ma, 2003-09-29 at 14:59, [EMAIL PROTECTED] wrote:
> On Mon, Sep 29, 2003 at 12:33:54PM +0100, Rick [Kitty5] wrote:
> > One easy way to rule out over-heating, install povray and leave it rendering
> > something overnight (at a command prompt, not in X), its still up in the
> > morning (btw, doesn't have to be pov, anything that pegs the cpu at 100%
> > for hours on end will do - but with pov you get a pretty picture at the end
> > of it)
> 
> Seems like a lot of work... if you just want to peg your CPU for a heat
> test, this infinite perl loop will do the job nicely:
> 
>   perl -e 'for (;;) {}'

Not quite so, as it will not utilize anything save jumps. Jumps won't
generate much heat in any CPU, altough ps will show 100% CPU usage. If
you really want to test for heat, install GIMPS Mersenne client from
www.mersenne.org (no Gentoo package available). You can set the client
for system benchmarking only, if you're not interested in joining the
prime searching project.

Note that some errors, like memory errors, can take a long time to be
noticed. Leave the client running for at least a week to see if your
memory is OK. GIMPS can detect memory errors which are unnoticed by
memtest86 binary.



signature.asc
Description: This is a digitally signed message part
This message has been 'sanitized'.  This means that potentially
dangerous content has been rewritten or removed.  The following
log describes which actions were taken.

Sanitizer (start="1064837531"):
  Forcing message to be multipart/mixed, to facilitate logging.
  Writer (pos="903"):
Part (pos="1072"):
  Part (pos="191"):
SanitizeFile (filename="unnamed.txt", mimetype="text/plain"):
  Match (names="unnamed.txt", rule="9"):
Enforced policy: accept

  Part (pos="1577"):
SanitizeFile (filename="signature.asc", mimetype="application/pgp-signature"):
  Match (names="signature.asc", rule="15"):
ScanFile (file="/var/quarantine/att-signature.asc-3f78219b.RI"):
  Scan succeeded, file is clean.

Enforced policy: accept


Anomy 0.0.0 : Sanitizer.pm
Sanitizer version 1.63 (Debian GNU/Linux)

--
[EMAIL PROTECTED] mailing list

Re: [gentoo-user] Disabling from X

2003-09-25 Thread Juha-Mikko Ahonen
On pe, 2003-09-26 at 09:22, Craig Main wrote:
> Hi all,
> 
> Is there a way to diable the above to stop people getting to a console?

You could remove the gettys from your /etc/inittab file. If you have
sshd running, you'll still be able to log in remotely to maintain the
boxes.

> I am busy setting up some boxes to be used in an internet cafe and am
> trying to secure them and only allow certain apps to be run. (maybe
> there is a "kiosk" distro that I don't know about?

If the users can't obtain a shell from console, xterm, gnome-terminal,
konsole or the like, then you could easily limit users' access to only
the programs you've installed to kde/gnome/wm.

Keep in mind though that you will need to strip the Run command from
the WM menus, or the user could execute shell commands.


signature.asc
Description: This is a digitally signed message part
This message has been 'sanitized'.  This means that potentially
dangerous content has been rewritten or removed.  The following
log describes which actions were taken.

Sanitizer (start="1064559471"):
  Forcing message to be multipart/mixed, to facilitate logging.
  Writer (pos="800"):
Part (pos="970"):
  Part (pos="191"):
SanitizeFile (filename="unnamed.txt", mimetype="text/plain"):
  Match (names="unnamed.txt", rule="9"):
Enforced policy: accept

  Part (pos="1141"):
SanitizeFile (filename="signature.asc", mimetype="application/pgp-signature"):
  Match (names="signature.asc", rule="15"):
ScanFile (file="/var/quarantine/att-signature.asc-3f73e36f.UL"):
  Scan succeeded, file is clean.

Enforced policy: accept


Anomy 0.0.0 : Sanitizer.pm
Sanitizer version 1.63 (Debian GNU/Linux)

--
[EMAIL PROTECTED] mailing list