Re: [gentoo-user] gaim problem with Yahoo!

[Brandon Low]

scs.msg.yahoo.com and scs.yahoo.com have become disjoint networks
(afaics) I am able to connect with recent gaim versions to
scs.yahoo.com, the _old_ login scheme appears to be functioning on
scs.msg.yahoo.com and I'm not sure which one is the 'real' yahoo network
which yahoo messenger users will be connected to.

--Brandon

On Fri, 01/09/04 at 19:11:48 -0600, Andrew Gaffney wrote:
> Is anyone else getting an "Incorrect password" error when trying to connect 
> to Yahoo! using Gaim? Yes, I have changed the server to scs.msg.yahoo.com. 
> I have a friend using Slackware who says that Gaim is doing it to him, but 
> the Web Messenger works just fine. Gaim's website  says 
> nothing.
> 
> -- 
> Andrew Gaffney
> System Administrator
> Skyline Aeronautics, LLC.
> 776 North Bell Avenue
> Chesterfield, MO 63005
> 636-357-1548
> 
> 
> --
> [EMAIL PROTECTED] mailing list

--
[EMAIL PROTECTED] mailing list

Re: [gentoo-user] CoreUtils - Emerge Problem

[Brandon Low]

This is a me too, anyone else seen this, I took a quick peak at the
ebuild and didn't see any solution apparent...

--B

On Wed, 07/30/03 at 13:41:52 -0400, Elliott, Andrew wrote:
> Anyone have any idea what is causing this?  (~x86)
> 
> 
> Making all in wc
> make[3]: Entering directory
> `/var/tmp/portage/coreutils-5.0-r1/work/coreutils-5.0/tests/wc'
> make[3]: Nothing to be done for `all'.
> make[3]: Leaving directory
> `/var/tmp/portage/coreutils-5.0-r1/work/coreutils-5.0/tests/wc'
> make[3]: Entering directory
> `/var/tmp/portage/coreutils-5.0-r1/work/coreutils-5.0/tests'
> make[3]: Nothing to be done for `all-am'.
> make[3]: Leaving directory
> `/var/tmp/portage/coreutils-5.0-r1/work/coreutils-5.0/tests'
> make[2]: Leaving directory
> `/var/tmp/portage/coreutils-5.0-r1/work/coreutils-5.0/tests'
> make[2]: Entering directory
> `/var/tmp/portage/coreutils-5.0-r1/work/coreutils-5.0'
> make[2]: Nothing to be done for `all-am'.
> make[2]: Leaving directory
> `/var/tmp/portage/coreutils-5.0-r1/work/coreutils-5.0'
> make[1]: Leaving directory
> `/var/tmp/portage/coreutils-5.0-r1/work/coreutils-5.0'
> --- ACCESS VIOLATION SUMMARY
> ---
> LOG FILE = "/tmp/sandbox-coreutils-5.0-r1-10346.log"
> 
> unlink:   
> /portage/coreutils-5.0-r1/work/coreutils-5.0/confdir3/confdir3/confdir3/
> confdir3/confdir3/confdir3/confdir3/confdir3/confdir3/confdir3/confdir3/
> confdir3/confdir3/confdir3/confdir3/confdir3/confdir3/confdir3/confdir3/
> confdir3/confdir3/confdir3/confdir3/confdir3/confdir3/confdir3/confdir3/
> confdir3/confdir3/confdir3/confdir3/confdir3/confdir3/confdir3/confdir3/
> confdir3/confdir3/confdir3/confdir3/confdir3/confdir3/confdir3/confdir3/
> confdir3/confdir3/confdir3/confdir3/confdir3/confdir3/confdir3/confdir3/
> confdir3/confdir3/confdir3/confdir3/confdir3/confdir3/confdir3/confdir3/
> confdir3/confdir3/confdir3/confdir3/confdir3/confdir3/confdir3/confdir3/
> confdir3/confdir3/confdir3/confdir3/confdir3/confdir3/confdir3/confdir3/
> confdir3/confdir3/confdir3/confdir3/confdir3/confdir3/confdir3/confdir3/
> confdir3/confdir3/confdir3/confdir3/confdir3/confdir3/confdir3/confdir3/
> confdir3/confdir3/confdir3/confdir3/confdir3/confdir3/confdir3/confdir3/
> confdir3/confdir3/confdir3/confdir3/confdir3/confdir3/confdir3/confdir3/
> confdir3/confdir3/confdir3/confdir3/confdir3/confdir3/confdir3/confdir3/
> confdir3/confdir3/confdir3/confdir3/confdir3/confdir3/confdir3/confdir3/
> confdir3/confdir3/confdir3/confdir3/confdir3/confdir3/confdir3/confdir3/
> confdir3/confdir3/confdir3/confdir3/confdir3/confdir3/confdir3/confdir3/
> confdir3/confdir3/confdir3/confdir3/confdir3/confdir3/confdir3/confdir3/
> confdir3/confdir3/confdir3/confdir3/confdir3/confdir3/confdir3/confdir3/
> confdir3/confdir3/confdir3/confdir3/confdir3/confdir3/confdir3/confdir3/
> confdir3/confdir3/confdir3/confdir3/confdir3/confdir3/confdir3/confdir3/
> confdir3/confdir3/confdir3/confdir3/confdir3/confdir3/confdir3/confdir3/
> confdir3/confdir3/confdir3/confdir3/confdir3/confdir3/confdir3/confdir3/
> confdir3/confdir3/confdir3/confdir3/confdir3/confdir3/confdir3/confdir3/
> confdir3/confdir3/confdir3/confdir3/confdir3/confdir3/confdir3/confdir3/
> confdir3/confdir3/confdir3/confdir3/confdir3/confdir3/confdir3/confdir3/
> confdir3/confdir3/confdir3/confdir3/confdir3/confdir3/confdir3/confdir3/
> confdir3/confdir3/confdir3/confdir3/confdir3/confdir3/confdir3/confdir3/
> confdir3/confdir3/confdir3/confdir3/confdir3/confdir3/confdir3/confdir3/
> confdir3/confdir3/confdir3/confdir3/confdir3/confdir3/confdir3/confdir3/
> confdir3/confdir3/confdir3/confdir3/confdir3/confdir3/confdir3/confdir3/
> confdir3/confdir3/confdir3/confdir3/confdir3/confdir3/confdir3/confdir3/
> confdir3/confdir3/confdir3/confdir3/confdir3/confdir3/confdir3/confdir3/
> confdir3/confdir3/confdir3/confdir3/confdir3/confdir3/confdir3/confdir3/
> confdir3/confdir3/confdir3/confdir3/confdir3/confdir3/confdir3/confdir3/
> confdir3/confdir3/confdir3/confdir3/confdir3/confdir3/confdir3/confdir3/
> confdir3/confdir3/confdir3/confdir3/confdir3/confdir3/confdir3/confdir3/
> confdir3/confdir3/confdir3/confdir3/confdir3/confdir3/confdir3/confdir3/
> confdir3/confdir3/confdir3/confdir3/confdir3/confdir3/confdir3/confdir3/
> confdir3/confdir3/confdir3/confdir3/confdir3/confdir3/confdir3/confdir3/
> confdir3/confdir3/confdir3/confdir3/confdir3/confdir3/confdir3/confdir3/
> confdir3/confdir3/confdir3/confdir3/confdir3/confdir3/confdir3/confdir3/
> confdir3/confdir3/confdir3/confdir3/confdir3/confdir3/confdir3/confdir3/
> confdir3/confdir3/confdir3/confdir3/confdir3/confdir3/confdir3/confdir3/
> confdir3/confdir3/confdir3/confdir3/confdir3/confdir3/confdir3/confdir3/
> confdir3/confdir3/confdir3/confdir3/confdir3/confdir3/confdir3/confdir3/
> confdir3/confdir3/confdir3/confdir3/confdir3/confdir3/confdir3/confdir3/
> confdir3/confdir3/confdir3/confdir3/confdir3/confdir3/confdir3/confdir3/
> confdir3/confdir3/confdir3/confdir3/confdir3/confdir

Re: [gentoo-user] Kernel Re-Compilation Question

[Brandon Low]

Unfortunately, I'm not sure about this, as I have never used kernel module autoloading 
:-\ good luck! :)

(My understanding is that this means that MANY module needs can be automatically 
detected and loaded and unlaoded as needed in this manner, but I'm not real clear on 
it)

--Brandon

On Thu, 03/06/03 at 14:12:53 -0800, Doug Gorley wrote:
> Thanks; one more question before I go experiment.  If I've got
> 
> CONFIG_KMOD=y
> 
> in my .config file after configuring my kernel, how do I take advantage of
> it?  Documentation/kmod.txt says to use the following command to set the
> path to modprobe:
> 
> echo "/sbin/modprobe" > /proc/sys/kernel/modprobe
> 
> and the following crontab entry to remove unused modules.
> 
> 0-59/5 * * * * /sbin/rmmod -a
> 
> If I do this, do I still need to list my modules in /etc/modules.autoload,
> or will kmod handle everything correctly?
> 
> > Yeah, quite correct... been a while since I did two different .configs
> > same source that I wanted to use.. :)
> >
> > --B
> >
> > On Thu, 03/06/03 at 13:38:34 -0800, Doug Gorley wrote:
> >> Thanks for your reply.
> >>
> >> So, not only is this OK, but it's a good idea if I want to experiment
> >> with different kernels from the same source, yes?  Otherwise, if I
> >> compiled two kernels from the vanilla-sources, wouldn't the modules
> >> from the second clobber those from the first?
> >>
> >> > The kernel 'knows' it's name, and all packages that install kernel
> >> modules also look at the same version that the kernel in
> >> /usr/src/linux knows (/usr/src/linux/include/version.h (or something
> >> of the sort)), so changing the name and recompiling works just fine
> >> and dandy.
> >> >
> >> > --Brandon
> >> >
> >> > On Thu, 03/06/03 at 13:16:43 -0800, Doug Gorley wrote:
> >> >> Good afternoon (PST) list,
> >> >>
> >> >> I'm trying to get a little more comfortable with kernel
> >> configuration, and have just compiled a 2.4.20 kernel from the
> >> vanilla-sources that uses modules wherever possible.  Following the
> >> Kernel HOWTO at http://www.tldp.org/, I changed my Makefile to read
> >> >>
> >> >> EXTRAVERSION = -Carnage_2003-03-06
> >> >>
> >> >> Now, what I've noticed is that in /lib/modules, I now have separate
> >> directories called 2.4.20 and 2.4.20-Carnage_2003-03-06.  Will the
> >> new kernel automatically know that it's modules are in the
> >> directory bearing it's name, or do I now have to somehow tell my
> >> kernel where to look?
> >> >>
> >> >> Thanks,
> >> >>
> >> >> --
> >> >> Doug Gorley | [EMAIL PROTECTED]
> >> >>
> >> >>
> >> >>
> >> >>
> >> >> --
> >> >> [EMAIL PROTECTED] mailing list
> >> >
> >> > --
> >> > [EMAIL PROTECTED] mailing list
> >>
> >>
> >> --
> >> Doug Gorley | [EMAIL PROTECTED]
> >>
> >>
> >
> > --
> > [EMAIL PROTECTED] mailing list
> 
> 
> -- 
> Doug Gorley | [EMAIL PROTECTED]
> 
> 

--
[EMAIL PROTECTED] mailing list

Re: [gentoo-user] etc-update

[Brandon Low]

Check bugs.gentoo.org for more information on the new dispatch-conf script, post any 
etc-update type feature requests there, as dispatch conf is currently slated to 
replace etc-update pending matching etc-update's feature set.  Since dispatch-conf is 
written in python, it has much more flexibility looking forward in terms of being able 
to integrate into portage, and to have various UIs integrated.  

--Brandon

On Thu, 03/06/03 at 11:57:05 -0500, Jason Giangrande wrote:
> Is there a way to use etc-update to update all config files at once, 
> either merge or replace?  The manpage didn't have anything and doing 
> them one at a time is a huge pain.
> 
> Thanks,
> -- 
> -Jason Giangrande
>  giangrande.org - http://www.giangrande.org 
>  Dog's I View - http://www.dogsiview.com 
> 
> 
> --
> [EMAIL PROTECTED] mailing list

--
[EMAIL PROTECTED] mailing list

Re: [gentoo-user] Kernel Re-Compilation Question

[Brandon Low]

Yeah, quite correct... been a while since I did two different .configs same source 
that I wanted to use.. :)

--B

On Thu, 03/06/03 at 13:38:34 -0800, Doug Gorley wrote:
> Thanks for your reply.
> 
> So, not only is this OK, but it's a good idea if I want to experiment with
> different kernels from the same source, yes?  Otherwise, if I compiled two
> kernels from the vanilla-sources, wouldn't the modules from the second
> clobber those from the first?
> 
> > The kernel 'knows' it's name, and all packages that install kernel
> > modules also look at the same version that the kernel in /usr/src/linux
> > knows (/usr/src/linux/include/version.h (or something of the sort)), so
> > changing the name and recompiling works just fine and dandy.
> >
> > --Brandon
> >
> > On Thu, 03/06/03 at 13:16:43 -0800, Doug Gorley wrote:
> >> Good afternoon (PST) list,
> >>
> >> I'm trying to get a little more comfortable with kernel configuration,
> >> and have just compiled a 2.4.20 kernel from the vanilla-sources that
> >> uses modules wherever possible.  Following the Kernel HOWTO at
> >> http://www.tldp.org/, I changed my Makefile to read
> >>
> >> EXTRAVERSION = -Carnage_2003-03-06
> >>
> >> Now, what I've noticed is that in /lib/modules, I now have separate
> >> directories called 2.4.20 and 2.4.20-Carnage_2003-03-06.  Will the new
> >> kernel automatically know that it's modules are in the directory
> >> bearing it's name, or do I now have to somehow tell my kernel where to
> >> look?
> >>
> >> Thanks,
> >>
> >> --
> >> Doug Gorley | [EMAIL PROTECTED]
> >>
> >>
> >>
> >>
> >> --
> >> [EMAIL PROTECTED] mailing list
> >
> > --
> > [EMAIL PROTECTED] mailing list
> 
> 
> -- 
> Doug Gorley | [EMAIL PROTECTED]
> 
> 

--
[EMAIL PROTECTED] mailing list

Re: [gentoo-user] Kernel Re-Compilation Question

[Brandon Low]

The kernel 'knows' it's name, and all packages that install kernel modules also look 
at the same version that the kernel in /usr/src/linux knows 
(/usr/src/linux/include/version.h (or something of the sort)), so changing the name 
and recompiling works just fine and dandy.

--Brandon

On Thu, 03/06/03 at 13:16:43 -0800, Doug Gorley wrote:
> Good afternoon (PST) list,
> 
> I'm trying to get a little more comfortable with kernel configuration, and
> have just compiled a 2.4.20 kernel from the vanilla-sources that uses
> modules wherever possible.  Following the Kernel HOWTO at
> http://www.tldp.org/, I changed my Makefile to read
> 
> EXTRAVERSION = -Carnage_2003-03-06
> 
> Now, what I've noticed is that in /lib/modules, I now have separate
> directories called 2.4.20 and 2.4.20-Carnage_2003-03-06.  Will the new
> kernel automatically know that it's modules are in the directory bearing
> it's name, or do I now have to somehow tell my kernel where to look?
> 
> Thanks,
> 
> -- 
> Doug Gorley | [EMAIL PROTECTED]
> 
> 
> 
> 
> --
> [EMAIL PROTECTED] mailing list

--
[EMAIL PROTECTED] mailing list

Re: [gentoo-user] XFS not enabled, is that on purpose? JFS users beware of XFS.

[Brandon Low]

It is just letting you know that the kernle you have merged does not have XFS support, 
if you need it then you would want to remerge it with 'USE="xfs"', otherwise don't 
worry about it.

--Brandon

On Fri, 02/28/03 at 10:55:02 -0500, gabriel wrote:
> 
> i just emerged the new kernel sources and go this after a successful emerge:
> 
>   * XFS not enabled, is that on purpose?  JFS users beware of XFS.
> 
> i use ext3 for most of my partitions (ext2 for /boot)  why did this 
> message come up?  what is xfs?  is it better than ext3?  i didn't set 
> anything in make.conf to make xfs not go did i?  here's my use flags:
> 
> USE="-3dnow -apm -arts -avi -encode gd -gnome -gpm -gtk innodb -kde maildir 
> -mikmod -motif -mpeg mysql -opengl -oss perl -qt -qtmt -quicktime -readline 
> samba tiff -truetype -X -xmms -xv"
> 
> as you can see, this is a web/file server, so i didn't need most of the stuff 
> i have in my desktop
> 
> 
> -- 
> we are linked, ta'lon, our fate is like an image caught in a mirror.
> if we deny the other, we deny ourselves...
> and we will cease to exist
>   - g'kar, babylon 5 "point of no return"
> 
> 
> --
> [EMAIL PROTECTED] mailing list

--
[EMAIL PROTECTED] mailing list

Re: [gentoo-user] lm_sensors-2.7.0 and i2c-2.7.0

[Brandon Low]

Hmm... I have a bug open on this, the lm_sensors ebuild should accept any of the more 
recent kernel-sources released by us OR i2c-2.7.0 as a dependency, not sure why it 
isn't.  As for it not building, I'm not at all sure, but once I resolve the deps maybe 
I can look at it.

--Brandon

On Thu, 02/27/03 at 23:31:24 -0800, Matt Tucker wrote:
> -- Joe Stone <[EMAIL PROTECTED]> spake thusly:
> 
> > today I made an emerge sync
> > then a emerge -up world with the following result:
> > 
> > These are the packages that I would merge, in order:
> > 
> > Calculating world dependencies /
> > !!! all ebuilds that could satisfy ">=sys-apps/i2c-2.7.0" have been
> > masked. !!!(dependency required by "sys-apps/lm_sensors-2.7.0"
> > [ebuild])
> 
> For the record, I'm running ACCEPT_KEYWORDS=~x86, and I have 2.7.0 of
> both of these installed fine.
> 
> 
> > okay, I installed i2c-2.7.0 manually, because I had always troubles
> > with  sensors and I hoped the problems could vanish.
> > 
> > So I made emerge i2c-2.7.0.ebuild
> > ...snip
>  Source unpacked.
> > Makefile:188: kernel/i2c-core.d: No such file or directory
> > Makefile:188: kernel/i2c-dev.d: No such file or directory
> > Makefile:188: kernel/i2c-algo-bit.d: No such file or directory
> > Makefile:188: kernel/i2c-elv.d: No such file or directory
> > Makefile:188: kernel/i2c-velleman.d: No such file or directory
> > Makefile:188: kernel/i2c-algo-pcf.d: No such file or directory
> > Makefile:188: kernel/i2c-elektor.d: No such file or directory
> > Makefile:188: kernel/i2c-proc.d: No such file or directory
> > Makefile:188: kernel/i2c-pport.d: No such file or directory
> > Makefile:188: kernel/i2c-pcf-epp.d: No such file or directory
> > ...snip
> 
> This is not an issue at all. It's just saying that the dependencies
> files don't exist, but it immediately makes them so no worries. It's
> standard behavior for this build. Same goes for lm_sensors.
> 
> 
> 
> > kernel/busses/i2c-amd8111.c:25:2: #error Your i2c is too old -
> > i2c-2.7.0 or  greater required!
> > kernel/busses/i2c-amd8111.c: In function `amd8111_access':
> > kernel/busses/i2c-amd8111.c:238: `I2C_CLIENT_PEC' undeclared (first
> > use in  this function)
> > kernel/busses/i2c-amd8111.c:238: (Each undeclared identifier is
> > reported only  once
> > ...snipp...
> > make: *** [kernel/busses/i2c-amd8111.o] Error 1
> > make: *** Waiting for unfinished jobs
> 
> The error at line 25 occurs if I2C_HW_SMBUS_AMD8111 is undeclared,
> which happens in linux/i2c-id.h, which gets included by linux/i2c.h.
> 
> Perhaps you haven't enabled I2C in the kernel?
> 
> 
> --
> [EMAIL PROTECTED] mailing list

--
[EMAIL PROTECTED] mailing list

Re: [gentoo-user] etc-update make.globals

[Brandon Low]

Really the only time you'll see make.globals appear is when you've downgraded portage 
as you just have.  It is quite alrigth in this case to keep the new or the old 
make.globals, either one will be quite acceptable.  I tend to keep the one from the 
portage I'm downgrading from in this situation, hwoever if make.globals change may be 
the very reasonf or needing to downgrade then that is not the best choice.

--Brandon

On Sat, 02/22/03 at 21:57:40 -0500, Carl Hudkins wrote:
Content-Description: signed data
> On Saturday 22 February 2003 21:42, el lodger wrote:
> 
> > As you can see most of the changes are minor. FEATURES is
> > commented in my make.conf. I just use the system defaults.
> > RSYNC_TIMEOUT can be simply commented as well. That leaves only the
> > header line to change.Should
> > I replace the original make.globals with the new one or just edit
> > make.conf and
> > forget about the header?
> 
>   I'd say just allow it to be replaced with the "new" file, since it's only 
> going back to what it was before the upgrade to 2.0.47-r2.  I make no 
> changes to make.globals, and have a few minor mods to make.conf.
> 
> -- 
> // Carl Hudkins :: ICQ 5723399 :: PGP 50238D9E
> //
> // "I do not take a single newspaper, nor read one a month;
> //  and I feel myself infinitely the happier for it."
> //   --Thomas Jefferson



--
[EMAIL PROTECTED] mailing list

Re: [gentoo-user] Kernel recommendations

[Brandon Low]

use the latest XFS-sources it has the proper support for Nforce2 afaik.

--B

On Sun, 02/16/03 at 15:53:47 -0500, Ernie Schroder wrote:
> Hi All,
>   By the end of the week, I'll have my shiny new motherboard and Athlon 
> XP2100+ The board is a Leadtek K7NCR18D-pro using the nForce2 chipset. 
> I'll be using pretty much standard hardware, CD-ROM, CD-RW nVidia 
> GeForce-4 512 megs PC2700 DDR...
>   I was wondering if anyone has experience with this setup and if they 
> have any words of wisdom regarding USE variables and kernel config. 
> Heck, if I can learn by your mistakes I can cut down on my own. Any 
> horror stories, OOOPS, or handy hints would be appreciated.
> -- 
> Regards, Ernie
> 100% Microsoft and Intel free
> 
> --
> [EMAIL PROTECTED] mailing list

--
[EMAIL PROTECTED] mailing list

Re: [gentoo-user] ck-sources

[Brandon Low]

Of late, there aren't any 'options' except low latency and preempt in Con's stuff... 
but know that he is hard at work making your desktop faster.  Check out -ck3 recently 
added to portage.

--Brandon

On Mon, 02/10/03 at 16:11:53 -0500, Seth Rothberg wrote:
> In the interest of speeding up my desktop I want to try  the Con Kolivas 
> kernel patches but when I emerged ck-sources-r2 and ran xconfig I couldn't 
> find any new latency options, at least not in the Processor type and features 
> section. Did these get put somewhere else? Do I need to download other 
> patches and apply them myself?
> 
> Thanks,
> 
> Seth
> 
> --
> [EMAIL PROTECTED] mailing list

--
[EMAIL PROTECTED] mailing list