[gentoo-amd64] no sound in firefox java

[gentoo-amd64] no sound in firefox java

[Daiajo Tibdixious]

If I use firefox-bin (32 bit) or firefox (64 bit) on youtube, I get
sound no problems.
If I run mplayer I get sound also.
If I use firefox-bin with a java applet that plays sound, I get no sound at all.
I can't load this applet in firefox, which is why I still use
firefox-bin for it.

Googling "no sound in firefox java" gives lots of hits, mainly from
people with the same problem.
1 solution was to "modprobe snd-pcm-oss" which did not help. I.m
fairly sure this is redundant with base layout 2.

I upgraded the kernel twice, from linux-2.6.36-gentoo-r5 where I
initially had the problem,
to linux-2.6.36-gentoo-r8 and now on linux-2.6.38-gentoo-r6 paying
careful attention to all the sound related configuration options. This
had no effect.

I've run out of things to try, so I'm asking the list.

I previously had a problem where the first firefox session would get
sound, but no subsequent application, including firefox would have
sound, in other words the first invocation of firefox would lock the
sound. I could live with that, this current problem is far more
annoying.

Re: [gentoo-amd64] no sound in firefox java

[Lie Ryan]

[-- Attachment #1: Type: text/plain, Size: 1293 bytes --]

> I previously had a problem where the first firefox session
> would get sound,

OSS or ALSA?
On 18/06/2011 10:03 AM, "Daiajo Tibdixious" <daiajo@gmail.com> wrote:
> If I use firefox-bin (32 bit) or firefox (64 bit) on youtube, I get
> sound no problems.
> If I run mplayer I get sound also.
> If I use firefox-bin with a java applet that plays sound, I get no sound
at all.
> I can't load this applet in firefox, which is why I still use
> firefox-bin for it.
>
> Googling "no sound in firefox java" gives lots of hits, mainly from
> people with the same problem.
> 1 solution was to "modprobe snd-pcm-oss" which did not help. I.m
> fairly sure this is redundant with base layout 2.
>
> I upgraded the kernel twice, from linux-2.6.36-gentoo-r5 where I
> initially had the problem,
> to linux-2.6.36-gentoo-r8 and now on linux-2.6.38-gentoo-r6 paying
> careful attention to all the sound related configuration options. This
> had no effect.
>
> I've run out of things to try, so I'm asking the list.
>
> I previously had a problem where the first firefox session would get
> sound, but no subsequent application, including firefox would have
> sound, in other words the first invocation of firefox would lock the
> sound. I could live with that, this current problem is far more
> annoying.
>

[-- Attachment #2: Type: text/html, Size: 1635 bytes --]

Re: [gentoo-amd64] no sound in firefox java

[Barry Schwartz]

Daiajo Tibdixious <daiajo@gmail.com> skribis:
> If I use firefox-bin (32 bit) or firefox (64 bit) on youtube, I get
> sound no problems.
> If I run mplayer I get sound also.
> If I use firefox-bin with a java applet that plays sound, I get no sound at all.
> I can't load this applet in firefox, which is why I still use
> firefox-bin for it.

I would set up pulseaudio (if it isn't set up already) and then worry
if I still had trouble with sound.

Re: [gentoo-amd64] no sound in firefox java

[Daiajo Tibdixious]

Lie Ryan  <lie.1296@gmail.com>
> OSS or ALSA?

Using ALSA by default, although I suspect java or firefox is using OSS
hence playing around the the OSS emulation.

I meant to include this
# lspci | grep Audio
00:14.2 Audio device: ATI Technologies Inc SBx00 Azalia (Intel HDA)
01:00.1 Audio device: ATI Technologies Inc HD48x0 audio

I've tried selecting both devices in alsaconf. Same symtoms for both.

On 6/18/11, Barry Schwartz <chemoelectric@chemoelectric.org> wrote:
> I would set up pulseaudio (if it isn't set up already) and then worry
> if I still had trouble with sound.

I installed pulseaudio, added the pulseaudio use flag, and rebuild
with --newuse.
I went thru <http://pulseaudio.org/wiki/PerfectSetup> logged out & in from kde,
and got no sound at all.
Rebooted and still no sound, in any application.

If I mplayer -ao pulse, it opens the sound okay, but no sound is audible
if I mplayer -ao alsa it can't find the library, I think thats because
of the rebuild
with pulseaudio use flag.
There is no /dev/dsp device (which is the oss compatibility device).

pavucontrol runs, but doesn't see any sound devices.

<http://en.gentoo-wiki.com/wiki/PulseAudio>
suggests doing a "fuser /dev/snd/*" and kill off any process listed.
I have nothing listed here. Before rebooting there were a few KDE
things, eg. knotify
This also suggests killing the daemon and doing "pulseaudio -vvvv"
which gave:
          :
D: cli-command.c: Checking for existance of
'/usr/lib64/pulse-0.9.22/modules/module-esound-protocol-unix.so':
success
E: socket-server.c: bind(): Address already in use
E: module.c: Failed to load  module "module-esound-protocol-unix"
(argument: ""): initialization failed.
E: main.c: Module load failed.
E: main.c: Failed to initialize daemon.
          :
The problem is I now have 3 pulseaudio daemons, which keep starting,
stopping, restarting,
so the PIDs keep changing. I'm about to reboot again to get rid of them.

[gentoo-amd64] Re: no sound in firefox java

[Duncan]

Daiajo Tibdixious posted on Sun, 19 Jun 2011 13:48:23 +1000 as excerpted:

> I installed pulseaudio, added the pulseaudio use flag, and rebuild with
> --newuse.
> I went thru <http://pulseaudio.org/wiki/PerfectSetup> logged out & in
> from kde,
> and got no sound at all.
> Rebooted and still no sound, in any application.
> 
> If I mplayer -ao pulse, it opens the sound okay, but no sound is audible
> if I mplayer -ao alsa it can't find the library, I think thats because
> of the rebuild with pulseaudio use flag.
> There is no /dev/dsp device (which is the oss compatibility device).

I believe Barry and I disagree on pulse.  It's yet another layer between 
the apps and the hardware that can break, and I don't need it, so from my 
perspective I'm better off without it.

As such I know little about it.  However, I *DO* know one of the frequent 
issues with alsa is that it starts with everything muted by default.  You 
have to unmute and set the volumes to something reasonable, then if you 
want it to keep that instead of coming up muted at each boot, you must 
setup something to set it back to the saved settings.  (The GUI desktops 
normally handle it pretty much automatically, so they're "something", or 
setup alsactl to run and set the saved settings at boot, for console-
users.  I believe Gentoo's alsa initscript does that if you put it in a 
runlevel.)

A lot of folks don't know that and think their audio is broken, even tho 
it's simply muted by default.

I've no idea if pulse is similar, tho it would make sense, given you 
don't want something blaring unexpectedly so mute-by-default is a very 
good policy, but if it is, have you checked that it's not simply muted?

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman

Re: [gentoo-amd64] Re: no sound in firefox java

[Daiajo Tibdixious]

On 6/19/11, Duncan <1i5t5.duncan@cox.net> wrote:
> Daiajo Tibdixious posted on Sun, 19 Jun 2011 13:48:23 +1000 as excerpted:
>
>> I installed pulseaudio, added the pulseaudio use flag, and rebuild with
>> --newuse.
>> I went thru <http://pulseaudio.org/wiki/PerfectSetup> logged out & in
>> from kde,
>> and got no sound at all.
>> Rebooted and still no sound, in any application.
>>
>> If I mplayer -ao pulse, it opens the sound okay, but no sound is audible
>> if I mplayer -ao alsa it can't find the library, I think thats because
>> of the rebuild with pulseaudio use flag.
>> There is no /dev/dsp device (which is the oss compatibility device).
>
> I believe Barry and I disagree on pulse.  It's yet another layer between
> the apps and the hardware that can break, and I don't need it, so from my
> perspective I'm better off without it.

> I've no idea if pulse is similar, tho it would make sense, given you
> don't want something blaring unexpectedly so mute-by-default is a very
> good policy, but if it is, have you checked that it's not simply muted?

Yeah, checking mute/volume is part of the debugging process.
At the moment I only have 1 master volume, not the whole rack of
volumes in AlSA's mixer, but its not muted nor too low to hear.
I think my problem is that my sound card is not defined to pulse,
can't find out what to do about it.

pulse did seem like a solution to my initial problem.
Anyway, I'm hoping solving this problem will help me with my original problem
(sound in all but firefox java applet).

[gentoo-amd64] Unsubscribe

[Tim A]

unsubscribe

Re: [gentoo-amd64] Unsubscribe

[Dale]

Tim A wrote:
> unsubscribe
>
>    

NO !!  This is the roach motel.  You can check out but you can never 
leave.  OK.  Maybe this once.  Try this:

gentoo-amd64+unsubscribe@lists.gentoo.org

Don't forget to confirm after you blanky to send that.

Dale

:-)  :-)

Re: [gentoo-amd64] Unsubscribe

[Joost Roeleveld]

On Wednesday 22 June 2011 07:21:51 Dale wrote:
> Tim A wrote:
> > unsubscribe
> 
> NO !!  This is the roach motel.

Not Hotel California? :)

> You can check out but you can never
> leave.  OK.  Maybe this once.  Try this:
> 
> gentoo-amd64+unsubscribe@lists.gentoo.org
> 
> Don't forget to confirm after you blanky to send that.
> 
> Dale
> 
> :-)  :-)

Re: [gentoo-amd64] Unsubscribe

[Dale]

Joost Roeleveld wrote:
> On Wednesday 22 June 2011 07:21:51 Dale wrote:
>    
>> Tim A wrote:
>>      
>>> unsubscribe
>>>        
>> NO !!  This is the roach motel.
>>      
> Not Hotel California? :)
>
>    

That's another possibility.  I just like the roach motel.

Dale

:-)  :-)

Re: [gentoo-amd64] Unsubscribe

[felix]

On Thu, Jun 23, 2011 at 05:44:37AM -0500, Dale wrote:
> Joost Roeleveld wrote:
> > On Wednesday 22 June 2011 07:21:51 Dale wrote:
> >    
> >> Tim A wrote:
> >>      
> >>> unsubscribe
> >>>        
> >> NO !!  This is the roach motel.
> >>      
> > Not Hotel California? :)
> >
> >    
> 
> That's another possibility.  I just like the roach motel.
> 
> Dale
> 
> :-)  :-)

I see it's been too long.  But my instructions are from an older kit
and may be antiquated.  I would appreciate receiving any fresher
versions by return mail.

Here's how to unsubscribe:

First, ask your Internet Provider to mail you an Unsubscribing Kit.
Then follow these directions.

The kit will most likely be the standard no-fault type. Depending on
requirements, System A and/or System B can be used. When operating
System A, depress lever and a plastic dalkron unsubscriber will be
dispensed through the slot immediately underneath. When you have
fastened the adhesive lip, attach connection marked by the large "X"
outlet hose. Twist the silver-coloured ring one inch below the
connection point until you feel it lock.

The kit is now ready for use. The Cin-Eliminator is activated by the
small switch on the lip.  When securing, twist the ring back to its
initial condition, so that the two orange lines meet.  Disconnect.
Place the dalkron unsubscriber in the vacuum receptacle to the rear.
Activate by pressing the blue button.

The controls for System B are located on the opposite side. The red
release switch places the Cin-Eliminator into position; it can be
adjusted manually up or down by pressing the blue manual release
button. The opening is self-adjusting. To secure after use, press the
green button, which simultaneously activates the evaporator and
returns the Cin-Eliminator to its storage position.

You may log off if the green exit light is on over the evaporator.  If
the red light is illuminated, one of the Cin-Eliminator requirements
has not been properly implemented. Press the "List Guy" call button on
the right of the evaporator. He will secure all facilities from his
control panel.

To use the Auto-Unsub, first undress and place all your clothes in the
clothes rack. Put on the velcro slippers located in the cabinet
immediately below. Enter the shower, taking the entire kit with
you. On the control panel to your upper right upon entering you will
see a "Shower seal" button. Press to activate. A green light will then
be illuminated immediately below. On the intensity knob, select the
desired setting. Now depress the Auto-Unsub activation lever. Bathe
normally.

The Auto-Unsub will automatically go off after three minutes unless
you activate the "Manual off" override switch by flipping it up. When
you are ready to leave, press the blue "Shower seal" release
button. The door will open and you may leave. Please remove the velcro
slippers and place them in their container.

If you prefer the ultrasonic log-off mode, press the indicated blue
button. When the twin panels open, pull forward by rings A & B. The
knob to the left, just below the blue light, has three settings, low,
medium or high. For normal use, the medium setting is suggested.

After these settings have been made, you can activate the device by
switching to the "ON" position the clearly marked red switch. If
during the unsubscribing operation you wish to change the settings,
place the "manual off" override switch in the "OFF" position. You may
now make the change and repeat the cycle. When the green exit light
goes on, you may log off and have lunch. Please close the door behind
you.


-- 
            ... _._. ._ ._. . _._. ._. ___ .__ ._. . .__. ._ .. ._.
     Felix Finch: scarecrow repairman & rocket surgeon / felix@crowfix.com
  GPG = E987 4493 C860 246C 3B1E  6477 7838 76E9 182E 8151 ITAR license #4933
I've found a solution to Fermat's Last Theorem but I see I've run out of room o

[gentoo-amd64] unsubscribe

[redspot]

unsubscribe

On Wed, Mar 21, 2012 at 5:03 AM,  <gentoo-amd64+help@lists.gentoo.org> wrote:
> Topics (messages 13110 through 13125):
>
> [gentoo-amd64] Kernel-3.3.0 and Nvidia-drivers
>      13110 - Frank Peters <frank.peters@comcast.net>
>
> [gentoo-amd64] Kernel-3.3.0 and Nvidia-drivers
>      13111 - Mark Knecht <markknecht@gmail.com>
>
> [gentoo-amd64] Kernel-3.3.0 and Nvidia-drivers
>      13112 - Frank Peters <frank.peters@comcast.net>
>
> [gentoo-amd64] Kernel-3.3.0 and Nvidia-drivers
>      13113 - Cheng Renquan <crquan@gmail.com>
>
> [gentoo-amd64] Kernel-3.3.0 and Nvidia-drivers
>      13114 - Mark Knecht <markknecht@gmail.com>
>
> [gentoo-amd64] Kernel-3.3.0 and Nvidia-drivers
>      13115 - Mark Knecht <markknecht@gmail.com>
>
> [gentoo-amd64] Kernel-3.3.0 and Nvidia-drivers
>      13116 - Frank Peters <frank.peters@comcast.net>
>
> [gentoo-amd64] Kernel-3.3.0 and Nvidia-drivers
>      13117 - Mark Knecht <markknecht@gmail.com>
>
> [gentoo-amd64] Kernel-3.3.0 and Nvidia-drivers
>      13118 - Paul Hartman <paul.hartman+gentoo@gmail.com>
>
> [gentoo-amd64] Kernel-3.3.0 and Nvidia-drivers
>      13119 - Barry Schwartz <chemoelectric@chemoelectric.org>
>
> [gentoo-amd64] Kernel-3.3.0 and Nvidia-drivers
>      13120 - Mark Knecht <markknecht@gmail.com>
>
> [gentoo-amd64] Kernel-3.3.0 and Nvidia-drivers
>      13121 - Barry Schwartz <chemoelectric@chemoelectric.org>
>
> [gentoo-amd64] Kernel-3.3.0 and Nvidia-drivers
>      13122 - Frank Peters <frank.peters@comcast.net>
>
> [gentoo-amd64] Kernel-3.3.0 and Nvidia-drivers
>      13123 - Barry Schwartz <chemoelectric@chemoelectric.org>
>
> [gentoo-amd64] Re: Kernel-3.3.0 and Nvidia-drivers
>      13124 - Duncan <1i5t5.duncan@cox.net>
>      13125 - Duncan <1i5t5.duncan@cox.net>
>
>
>
> Linux-3.3.0 is released and, as is my usual habit, I downloaded and compiled
> the plain vanilla source.
>
> After rebooting to the command console, and before starting X, I needed
> to re-install the nvidia-driver module for the new kernel.  Doing
> "emerge nvidia-drivers" gave me the following error (the entire build log
> is attached):
>
>>>> Source prepared.
>>>> Configuring source in /tmp/portage-acc/tmp/portage/x11-drivers/nvidia-drivers-295.20-r1/work ...
>>>> Source configured.
>>>> Compiling source in /tmp/portage-acc/tmp/portage/x11-drivers/nvidia-drivers-295.20-r1/work ...
> Preparing nvidia module
> make -j9 HOSTCC=x86_64-pc-linux-gnu-gcc CROSS_COMPILE=x86_64-pc-linux-gnu- 'LDFLAGS=-m elf_x86_64' IGNORE_CC_MISMATCH=yes V=1 SYSSRC=/usr/src/linux SYSOUT=/lib/modules/3.3.0/build CC=x86_64-pc-linux-gnu-gcc clean module
>
> *** Unable to determine the target kernel version. ***
>
> make: *** [select_makefile] Error 1
> emake failed
> ERROR: x11-drivers/nvidia-drivers-295.20-r1 failed (compile phase):
>  Unable to emake HOSTCC=x86_64-pc-linux-gnu-gcc CROSS_COMPILE=x86_64-pc-linux-gnu- LDFLAGS=-m elf_x86_64  IGNORE_CC_MISMATCH=yes V=1 SYSSRC=/usr/src/linux             SYSOUT=/lib/modules/3.3.0/build CC=x86_64-pc-linux-gnu-gcc clean module
>
> Call stack:
>    ebuild.sh, line   85:  Called src_compile
>  environment, line 3711:  Called linux-mod_src_compile
>  environment, line 2668:  Called die
> The specific snippet of code:
>              eval "emake HOSTCC=\"$(tc-getBUILD_CC)\"
>
>
> The first part of the build log (see attached file) indicates that the
> kernel source was correctly found (at /usr/src/linux), but for some
> reason the make process fails.
>
> Could this be due to some changes in the kernel-3.3.0 tree?
>
> Frank Peters
>
>
> On Mon, Mar 19, 2012 at 9:12 AM, Frank Peters <frank.peters@comcast.net> wrote:
>> Linux-3.3.0 is released and, as is my usual habit, I downloaded and compiled
>> the plain vanilla source.
>>
> <SNIP>
>> The first part of the build log (see attached file) indicates that the
>> kernel source was correctly found (at /usr/src/linux), but for some
>> reason the make process fails.
>>
>> Could this be due to some changes in the kernel-3.3.0 tree?
>>
>> Frank Peters
>>
>
> Possibly this from Google will help?
>
> Good luck & post back,
> Mark
>
> On Mon, 19 Mar 2012 09:35:34 -0700
> Mark Knecht <markknecht@gmail.com> wrote:
>
>>
>> Possibly this from Google will help?
>>
>
> Did you intend to include a link?  If so, it must have gotten
> lost somewhere.
>
> Frank Peters
>
>
> I have switched to nouveau driver, for over 1 year,
> using with gnome3 interface, no performance issue, and quite stable,
>
> enjoying every mainline kernel 3.0, 3.1, 3.2, 3.3, no building issue
>
>
> I think it's time for everyone to give up nvidia-drivers, the blob of binary
>
> On Mon, Mar 19, 2012 at 9:12 AM, Frank Peters <frank.peters@comcast.net> wrote:
>> Linux-3.3.0 is released and, as is my usual habit, I downloaded and compiled
>> the plain vanilla source.
>>
>> After rebooting to the command console, and before starting X, I needed
>> to re-install the nvidia-driver module for the new kernel.  Doing
>> "emerge nvidia-drivers" gave me the following error (the entire build log
>> is attached):
>>
>>>>> Source prepared.
>>>>> Configuring source in /tmp/portage-acc/tmp/portage/x11-drivers/nvidia-drivers-295.20-r1/work ...
>>>>> Source configured.
>>>>> Compiling source in /tmp/portage-acc/tmp/portage/x11-drivers/nvidia-drivers-295.20-r1/work ...
>> Preparing nvidia module
>> make -j9 HOSTCC=x86_64-pc-linux-gnu-gcc CROSS_COMPILE=x86_64-pc-linux-gnu- 'LDFLAGS=-m elf_x86_64' IGNORE_CC_MISMATCH=yes V=1 SYSSRC=/usr/src/linux SYSOUT=/lib/modules/3.3.0/build CC=x86_64-pc-linux-gnu-gcc clean module
>>
>> *** Unable to determine the target kernel version. ***
>
> On Mon, Mar 19, 2012 at 12:05 PM, Frank Peters <frank.peters@comcast.net> wrote:
>> On Mon, 19 Mar 2012 09:35:34 -0700
>> Mark Knecht <markknecht@gmail.com> wrote:
>>
>>>
>>> Possibly this from Google will help?
>>>
>>
>> Did you intend to include a link?  If so, it must have gotten
>> lost somewhere.
>>
>> Frank Peters
>>
>>
>
> Gadzooks, yes I did. Sorry!
>
> http://weltall.heliohost.org/wordpress/2012/01/20/linux-kernel-3-3-rc1-and-nvidia-drivers/
>
> To be clear, I have no idea if it will solve your exact problem. It
> didn't for all.
>
> My experience with nvidia is pretty good if you give them a couple of
> days, but very spotty on the first or second day a new kernel minor
> rev is released. Nominally I use this page:
>
> http://www.nvidia.com/Download/indexsg.aspx?lang=en-us
>
> and then search out my specific card to determine what _exact_ driver
> they want me to run. It almost always requires i run ~amd64.
>
> HTH,
> Mark
>
> On Mon, Mar 19, 2012 at 12:14 PM, Cheng Renquan <crquan@gmail.com> wrote:
>> I have switched to nouveau driver, for over 1 year,
>> using with gnome3 interface, no performance issue, and quite stable,
>>
>> enjoying every mainline kernel 3.0, 3.1, 3.2, 3.3, no building issue
>>
>>
>> I think it's time for everyone to give up nvidia-drivers, the blob of binary
>>
>
> And how would one use CUDA if we gave up nvidia-drivers? Does nouveau
> support all the CUDA stuff?
>
> Cheers,
> Mark
>
> On Mon, 19 Mar 2012 09:35:34 -0700
> Mark Knecht <markknecht@gmail.com> wrote:
>
>>
>> Possibly this from Google will help?
>>
>
> OK, I think I've found the URL that you may have intended:
>
> http://weltall.heliohost.org/wordpress/2012/01/20/linux-kernel-3-3-rc1-and-nvidia-drivers/
>
> I followed the second fix that is described and now the nvidia-drivers
> emerge and work nicely with linux kernel-3.3.
>
> Thanks for the hint.
>
> There are changes to the kernel-3.3 tree that will have to addressed
> by the gentoo nvidia-drivers or other users will hit this problem
> as well.
>
> Frank Peters
>
>
> On Mon, Mar 19, 2012 at 12:30 PM, Frank Peters <frank.peters@comcast.net> wrote:
>> On Mon, 19 Mar 2012 09:35:34 -0700
>> Mark Knecht <markknecht@gmail.com> wrote:
>>
>>>
>>> Possibly this from Google will help?
>>>
>>
>> OK, I think I've found the URL that you may have intended:
>>
>> http://weltall.heliohost.org/wordpress/2012/01/20/linux-kernel-3-3-rc1-and-nvidia-drivers/
>>
>> I followed the second fix that is described and now the nvidia-drivers
>> emerge and work nicely with linux kernel-3.3.
>>
>> Thanks for the hint.
>>
>> There are changes to the kernel-3.3 tree that will have to addressed
>> by the gentoo nvidia-drivers or other users will hit this problem
>> as well.
>>
>> Frank Peters
>>
>>
>
> Glad you found it. That is the link I just sent along and good to know
> it helped a bit.
>
> As I said, on kernel revision number changes I ALWAYS wait a minimum
> of 3-5 days before trying to upgrade. nvidia always seems to need at
> least a few days to catch up with a new release, or that's been my
> experience in the past anyway.
>
> Cheers,
> Mark
>
> On Mon, Mar 19, 2012 at 3:08 PM, Mark Knecht <markknecht@gmail.com> wrote:
>>
>> As I said, on kernel revision number changes I ALWAYS wait a minimum
>> of 3-5 days before trying to upgrade. nvidia always seems to need at
>> least a few days to catch up with a new release, or that's been my
>> experience in the past anyway.
>
> Same here, nvidia-drivers and vmware-modules are why I usually wait
> until the .1 release on a new kernel series. :)
>
> Mark Knecht <markknecht@gmail.com> skribis:
>> And how would one use CUDA if we gave up nvidia-drivers? Does nouveau
>> support all the CUDA stuff?
>
> I think they may have reverse engineered CUDA, but whether it is
> implemented I don’t know, and I wouldn’t want to be the one to test
> it, either. :)
>
> I’m donating processor time with boinc and that’s good enough reason
> to use the binary driver if it gives me more processor to donate.
>
> (Waiting before installing anything new is painful, I know, because
> with Gentoo you always feel like you want it to be doing something, or
> at least that’s my experience. :) )
>
> On Mon, Mar 19, 2012 at 2:28 PM, Barry Schwartz
> <chemoelectric@chemoelectric.org> wrote:
>> Mark Knecht <markknecht@gmail.com> skribis:
>>> And how would one use CUDA if we gave up nvidia-drivers? Does nouveau
>>> support all the CUDA stuff?
>>
>> I think they may have reverse engineered CUDA, but whether it is
>> implemented I don’t know, and I wouldn’t want to be the one to test
>> it, either. :)
>>
>> I’m donating processor time with boinc and that’s good enough reason
>> to use the binary driver if it gives me more processor to donate.
>>
>> (Waiting before installing anything new is painful, I know, because
>> with Gentoo you always feel like you want it to be doing something, or
>> at least that’s my experience. :) )
>>
>
> I have no problem with you or anyone else running nouveau. None at all.
>
> I do have a problem with someone saying 'it's time for everyone to
> give up nvidia-drivers' without demonstrating they know the full
> impact of what they are suggesting. Had Cheng Renquan suggest 'Maybe
> people who don't need anything other than basic X capabilities should
> consider running nouveau' I wouldn't have even chimed in.
>
> And thanks for running boinc. It's good of you and good for you.
>
> Cheers,
> Mark
>
> Mark Knecht <markknecht@gmail.com> skribis:
>> I do have a problem with someone saying 'it's time for everyone to
>> give up nvidia-drivers' without demonstrating they know the full
>> impact of what they are suggesting. Had Cheng Renquan suggest 'Maybe
>> people who don't need anything other than basic X capabilities should
>> consider running nouveau' I wouldn't have even chimed in.
>
> Sage Notebook (sage-on-gentoo overlay) can use CUDA as well. I think
> you don't have to worry that nvidia-drivers would go away; in the
> worst case it would end up in a good overlay. That's unlikely IMO, and
> would mostly likely be if there were an established alternative
> implementation of CUDA.
>
> On Mon, 19 Mar 2012 14:40:34 -0700
> Mark Knecht <markknecht@gmail.com> wrote:
>
>>
>> I have no problem with you or anyone else running nouveau. None at all.
>>
>> I do have a problem with someone saying 'it's time for everyone to
>> give up nvidia-drivers' without demonstrating they know the full
>> impact of what they are suggesting. Had Cheng Renquan suggest 'Maybe
>> people who don't need anything other than basic X capabilities should
>> consider running nouveau' I wouldn't have even chimed in.
>>
>
> I think the main complaint is that the Nvidia drivers are closed
> binary blobs while Nouveau is an attempt to create an entirely
> open source driver.  The spirit of free software demands that we
> support these open initiatives.
>
> Actually, until recently, I was very happy using the legacy open
> source xorg nvidia driver known simply as as "nv."  It is still
> available in Gentoo as x11-drivers/xf86-video-nv.
>
> Since I do not do gaming or other intensive graphic activities,
> I could get by nicely with just nv.  However, the nv driver does
> not seem to support the latest hardware too well.  On one of
> my machines I have a card based on Nvidia GeForce 210.  Although
> the nv driver works with this card, it does not enable the Xv
> extension and consequently the graphic response is poor.
>
> On older cards nv does work quite well for ordinary purposes.
>
> Frank Peters
>
>
> Frank Peters <frank.peters@comcast.net> skribis:
>> I think the main complaint is that the Nvidia drivers are closed
>> binary blobs while Nouveau is an attempt to create an entirely
>> open source driver.
>
> Unfortunately the nvidia drivers are needed not only for graphics but
> also to use the GPU for scientific calculations, including for
> donating processor time to medical research, for instance.
>
>
> Frank Peters posted on Tue, 20 Mar 2012 00:03:06 -0400 as excerpted:
>
>> Actually, until recently, I was very happy using the legacy open source
>> xorg nvidia driver known simply as as "nv."  It is still available in
>> Gentoo as x11-drivers/xf86-video-nv.
>>
>> Since I do not do gaming or other intensive graphic activities, I could
>> get by nicely with just nv.  However, the nv driver does not seem to
>> support the latest hardware too well.
>
> FWIW, the old nv driver is legacy, now, and won't be supporting new
> hardware.  AFAIK older hardware should be switching as well, for support
> with current software, as nv won't be updated for that any longer, either.
>
> The same thing happened to it as happened to nvidia's proprietary network
> driver some years ago; pretty much everyone involved, including the
> distros that used to ship nv and nvidia itself, seems to have recognized
> that the reverse-engineered work is now better than nvidia's basic
> freedomware stub driver, nv, and nouveau has officially taken its place.
>
> --
> Duncan - List replies preferred.   No HTML msgs.
> "Every nonfree program has a lord, a master --
> and if you use the program, he is your master."  Richard Stallman
>
>
> Barry Schwartz posted on Tue, 20 Mar 2012 01:20:13 -0500 as excerpted:
>
>> Unfortunately the nvidia drivers are needed not only for graphics but
>> also to use the GPU for scientific calculations, including for donating
>> processor time to medical research, for instance.
>
> My donation ends where their disrespect for human freedom begins.  (Over
> a decade ago, back on MS, I used to run distributed.net.  However, they
> don't have a freedomware client, or at least didn't back then, and while
> I understand the reasons why -- someone cheating and saying they did the
> work when they didn't, just to get the stats -- that didn't change the
> fact that I wasn't going to run servantware.  But as they say, YMMV.)
>
> --
> Duncan - List replies preferred.   No HTML msgs.
> "Every nonfree program has a lord, a master --
> and if you use the program, he is your master."  Richard Stallman
>
>

Re: [gentoo-amd64] unsubscribe

[Dale]

redspot wrote:
> unsubscribe
> 


Nope.  It ain't going to happen.  Sorry.  This is Hotel California so
you can't leave.  OK.  Stop laughing.  This may help:

Send email to gentoo-amd64+unsubscribe@lists.gentoo.org and then wait.
You should get a confirmation that you want to leave us poor lonesome
folks all alone.  If you really want to leave us here all alone, just
hit reply, don't change anything and hit send.  You will get one more
confirmation email.  After that, we will just all sit here alone without
you.

I hope you think about the Hotel California song all day long.  LOL

Dale

:-)  :-)


-- 
I am only responsible for what I said ... Not for what you understood or
how you interpreted my words!

Miss the compile output?  Hint:
EMERGE_DEFAULT_OPTS="--quiet-build=n"

Re: [gentoo-amd64] unsubscribe

[Alex Alexander]

[-- Attachment #1: Type: text/plain, Size: 974 bytes --]

On Mar 22, 2012 7:57 PM, "Dale" <rdalek1967@gmail.com> wrote:
>
> redspot wrote:
> > unsubscribe
> >
>
>
> Nope.  It ain't going to happen.  Sorry.  This is Hotel California so
> you can't leave.  OK.  Stop laughing.  This may help:
>
> Send email to gentoo-amd64+unsubscribe@lists.gentoo.org and then wait.
> You should get a confirmation that you want to leave us poor lonesome
> folks all alone.  If you really want to leave us here all alone, just
> hit reply, don't change anything and hit send.  You will get one more
> confirmation email.  After that, we will just all sit here alone without
> you.
>
> I hope you think about the Hotel California song all day long.  LOL
>
> Dale
>
> :-)  :-)
>
>
> --
> I am only responsible for what I said ... Not for what you understood or
> how you interpreted my words!
>
> Miss the compile output?  Hint:
> EMERGE_DEFAULT_OPTS="--quiet-build=n"
>

for some bizarre reason I lost The Game because of your email :p

Alex | wired

[-- Attachment #2: Type: text/html, Size: 1387 bytes --]

Re: [gentoo-amd64] unsubscribe

[Dale]

Alex Alexander wrote:
> On Mar 22, 2012 7:57 PM, "Dale" <rdalek1967@gmail.com
> <mailto:rdalek1967@gmail.com>> wrote:
>>
>> redspot wrote:
>> > unsubscribe
>> >
>>
>>
>> Nope.  It ain't going to happen.  Sorry.  This is Hotel California so
>> you can't leave.  OK.  Stop laughing.  This may help:
>>
>> Send email to gentoo-amd64+unsubscribe@lists.gentoo.org
> <mailto:gentoo-amd64%2Bunsubscribe@lists.gentoo.org> and then wait.
>> You should get a confirmation that you want to leave us poor lonesome
>> folks all alone.  If you really want to leave us here all alone, just
>> hit reply, don't change anything and hit send.  You will get one more
>> confirmation email.  After that, we will just all sit here alone without
>> you.
>>
>> I hope you think about the Hotel California song all day long.  LOL
>>
>> Dale
>>
>> :-)  :-)
>>
>>
>> --
>> I am only responsible for what I said ... Not for what you understood or
>> how you interpreted my words!
>>
>> Miss the compile output?  Hint:
>> EMERGE_DEFAULT_OPTS="--quiet-build=n"
>>
> 
> for some bizarre reason I lost The Game because of your email :p
> 
> Alex | wired
> 


Was you laughing or singing the song to yourself?

I try not to be mean about it.  Most mailing lists don't work like
Gentoos so people just need a little nudge.  ;-)

Dale

:-)  :-)

-- 
I am only responsible for what I said ... Not for what you understood or
how you interpreted my words!

Miss the compile output?  Hint:
EMERGE_DEFAULT_OPTS="--quiet-build=n"

Re: [gentoo-amd64] unsubscribe

[Zhu Sha Zang]

No, you can't.

Not this way, try something like sending a e-mail to:

gentoo-amd64+unsubscribe@lists.gentoo.org


Good Luck

On 22-03-2012 13:42, redspot wrote:
> unsubscribe
>
> On Wed, Mar 21, 2012 at 5:03 AM,<gentoo-amd64+help@lists.gentoo.org>  wrote:
>    
>> Topics (messages 13110 through 13125):
>>
>> [gentoo-amd64] Kernel-3.3.0 and Nvidia-drivers
>>       13110 - Frank Peters<frank.peters@comcast.net>
>>
>> [gentoo-amd64] Kernel-3.3.0 and Nvidia-drivers
>>       13111 - Mark Knecht<markknecht@gmail.com>
>>
>> [gentoo-amd64] Kernel-3.3.0 and Nvidia-drivers
>>       13112 - Frank Peters<frank.peters@comcast.net>
>>
>> [gentoo-amd64] Kernel-3.3.0 and Nvidia-drivers
>>       13113 - Cheng Renquan<crquan@gmail.com>
>>
>> [gentoo-amd64] Kernel-3.3.0 and Nvidia-drivers
>>       13114 - Mark Knecht<markknecht@gmail.com>
>>
>> [gentoo-amd64] Kernel-3.3.0 and Nvidia-drivers
>>       13115 - Mark Knecht<markknecht@gmail.com>
>>
>> [gentoo-amd64] Kernel-3.3.0 and Nvidia-drivers
>>       13116 - Frank Peters<frank.peters@comcast.net>
>>
>> [gentoo-amd64] Kernel-3.3.0 and Nvidia-drivers
>>       13117 - Mark Knecht<markknecht@gmail.com>
>>
>> [gentoo-amd64] Kernel-3.3.0 and Nvidia-drivers
>>       13118 - Paul Hartman<paul.hartman+gentoo@gmail.com>
>>
>> [gentoo-amd64] Kernel-3.3.0 and Nvidia-drivers
>>       13119 - Barry Schwartz<chemoelectric@chemoelectric.org>
>>
>> [gentoo-amd64] Kernel-3.3.0 and Nvidia-drivers
>>       13120 - Mark Knecht<markknecht@gmail.com>
>>
>> [gentoo-amd64] Kernel-3.3.0 and Nvidia-drivers
>>       13121 - Barry Schwartz<chemoelectric@chemoelectric.org>
>>
>> [gentoo-amd64] Kernel-3.3.0 and Nvidia-drivers
>>       13122 - Frank Peters<frank.peters@comcast.net>
>>
>> [gentoo-amd64] Kernel-3.3.0 and Nvidia-drivers
>>       13123 - Barry Schwartz<chemoelectric@chemoelectric.org>
>>
>> [gentoo-amd64] Re: Kernel-3.3.0 and Nvidia-drivers
>>       13124 - Duncan<1i5t5.duncan@cox.net>
>>       13125 - Duncan<1i5t5.duncan@cox.net>
>>
>>
>>
>> Linux-3.3.0 is released and, as is my usual habit, I downloaded and compiled
>> the plain vanilla source.
>>
>> After rebooting to the command console, and before starting X, I needed
>> to re-install the nvidia-driver module for the new kernel.  Doing
>> "emerge nvidia-drivers" gave me the following error (the entire build log
>> is attached):
>>
>>      
>>>>> Source prepared.
>>>>> Configuring source in /tmp/portage-acc/tmp/portage/x11-drivers/nvidia-drivers-295.20-r1/work ...
>>>>> Source configured.
>>>>> Compiling source in /tmp/portage-acc/tmp/portage/x11-drivers/nvidia-drivers-295.20-r1/work ...
>>>>>            
>> Preparing nvidia module
>> make -j9 HOSTCC=x86_64-pc-linux-gnu-gcc CROSS_COMPILE=x86_64-pc-linux-gnu- 'LDFLAGS=-m elf_x86_64' IGNORE_CC_MISMATCH=yes V=1 SYSSRC=/usr/src/linux SYSOUT=/lib/modules/3.3.0/build CC=x86_64-pc-linux-gnu-gcc clean module
>>
>> *** Unable to determine the target kernel version. ***
>>
>> make: *** [select_makefile] Error 1
>> emake failed
>> ERROR: x11-drivers/nvidia-drivers-295.20-r1 failed (compile phase):
>>   Unable to emake HOSTCC=x86_64-pc-linux-gnu-gcc CROSS_COMPILE=x86_64-pc-linux-gnu- LDFLAGS=-m elf_x86_64  IGNORE_CC_MISMATCH=yes V=1 SYSSRC=/usr/src/linux             SYSOUT=/lib/modules/3.3.0/build CC=x86_64-pc-linux-gnu-gcc clean module
>>
>> Call stack:
>>     ebuild.sh, line   85:  Called src_compile
>>   environment, line 3711:  Called linux-mod_src_compile
>>   environment, line 2668:  Called die
>> The specific snippet of code:
>>               eval "emake HOSTCC=\"$(tc-getBUILD_CC)\"
>>
>>
>> The first part of the build log (see attached file) indicates that the
>> kernel source was correctly found (at /usr/src/linux), but for some
>> reason the make process fails.
>>
>> Could this be due to some changes in the kernel-3.3.0 tree?
>>
>> Frank Peters
>>
>>
>> On Mon, Mar 19, 2012 at 9:12 AM, Frank Peters<frank.peters@comcast.net>  wrote:
>>      
>>> Linux-3.3.0 is released and, as is my usual habit, I downloaded and compiled
>>> the plain vanilla source.
>>>
>>>        
>> <SNIP>
>>      
>>> The first part of the build log (see attached file) indicates that the
>>> kernel source was correctly found (at /usr/src/linux), but for some
>>> reason the make process fails.
>>>
>>> Could this be due to some changes in the kernel-3.3.0 tree?
>>>
>>> Frank Peters
>>>
>>>        
>> Possibly this from Google will help?
>>
>> Good luck&  post back,
>> Mark
>>
>> On Mon, 19 Mar 2012 09:35:34 -0700
>> Mark Knecht<markknecht@gmail.com>  wrote:
>>
>>      
>>> Possibly this from Google will help?
>>>
>>>        
>> Did you intend to include a link?  If so, it must have gotten
>> lost somewhere.
>>
>> Frank Peters
>>
>>
>> I have switched to nouveau driver, for over 1 year,
>> using with gnome3 interface, no performance issue, and quite stable,
>>
>> enjoying every mainline kernel 3.0, 3.1, 3.2, 3.3, no building issue
>>
>>
>> I think it's time for everyone to give up nvidia-drivers, the blob of binary
>>
>> On Mon, Mar 19, 2012 at 9:12 AM, Frank Peters<frank.peters@comcast.net>  wrote:
>>      
>>> Linux-3.3.0 is released and, as is my usual habit, I downloaded and compiled
>>> the plain vanilla source.
>>>
>>> After rebooting to the command console, and before starting X, I needed
>>> to re-install the nvidia-driver module for the new kernel.  Doing
>>> "emerge nvidia-drivers" gave me the following error (the entire build log
>>> is attached):
>>>
>>>        
>>>>>> Source prepared.
>>>>>> Configuring source in /tmp/portage-acc/tmp/portage/x11-drivers/nvidia-drivers-295.20-r1/work ...
>>>>>> Source configured.
>>>>>> Compiling source in /tmp/portage-acc/tmp/portage/x11-drivers/nvidia-drivers-295.20-r1/work ...
>>>>>>              
>>> Preparing nvidia module
>>> make -j9 HOSTCC=x86_64-pc-linux-gnu-gcc CROSS_COMPILE=x86_64-pc-linux-gnu- 'LDFLAGS=-m elf_x86_64' IGNORE_CC_MISMATCH=yes V=1 SYSSRC=/usr/src/linux SYSOUT=/lib/modules/3.3.0/build CC=x86_64-pc-linux-gnu-gcc clean module
>>>
>>> *** Unable to determine the target kernel version. ***
>>>        
>> On Mon, Mar 19, 2012 at 12:05 PM, Frank Peters<frank.peters@comcast.net>  wrote:
>>      
>>> On Mon, 19 Mar 2012 09:35:34 -0700
>>> Mark Knecht<markknecht@gmail.com>  wrote:
>>>
>>>        
>>>> Possibly this from Google will help?
>>>>
>>>>          
>>> Did you intend to include a link?  If so, it must have gotten
>>> lost somewhere.
>>>
>>> Frank Peters
>>>
>>>
>>>        
>> Gadzooks, yes I did. Sorry!
>>
>> http://weltall.heliohost.org/wordpress/2012/01/20/linux-kernel-3-3-rc1-and-nvidia-drivers/
>>
>> To be clear, I have no idea if it will solve your exact problem. It
>> didn't for all.
>>
>> My experience with nvidia is pretty good if you give them a couple of
>> days, but very spotty on the first or second day a new kernel minor
>> rev is released. Nominally I use this page:
>>
>> http://www.nvidia.com/Download/indexsg.aspx?lang=en-us
>>
>> and then search out my specific card to determine what _exact_ driver
>> they want me to run. It almost always requires i run ~amd64.
>>
>> HTH,
>> Mark
>>
>> On Mon, Mar 19, 2012 at 12:14 PM, Cheng Renquan<crquan@gmail.com>  wrote:
>>      
>>> I have switched to nouveau driver, for over 1 year,
>>> using with gnome3 interface, no performance issue, and quite stable,
>>>
>>> enjoying every mainline kernel 3.0, 3.1, 3.2, 3.3, no building issue
>>>
>>>
>>> I think it's time for everyone to give up nvidia-drivers, the blob of binary
>>>
>>>        
>> And how would one use CUDA if we gave up nvidia-drivers? Does nouveau
>> support all the CUDA stuff?
>>
>> Cheers,
>> Mark
>>
>> On Mon, 19 Mar 2012 09:35:34 -0700
>> Mark Knecht<markknecht@gmail.com>  wrote:
>>
>>      
>>> Possibly this from Google will help?
>>>
>>>        
>> OK, I think I've found the URL that you may have intended:
>>
>> http://weltall.heliohost.org/wordpress/2012/01/20/linux-kernel-3-3-rc1-and-nvidia-drivers/
>>
>> I followed the second fix that is described and now the nvidia-drivers
>> emerge and work nicely with linux kernel-3.3.
>>
>> Thanks for the hint.
>>
>> There are changes to the kernel-3.3 tree that will have to addressed
>> by the gentoo nvidia-drivers or other users will hit this problem
>> as well.
>>
>> Frank Peters
>>
>>
>> On Mon, Mar 19, 2012 at 12:30 PM, Frank Peters<frank.peters@comcast.net>  wrote:
>>      
>>> On Mon, 19 Mar 2012 09:35:34 -0700
>>> Mark Knecht<markknecht@gmail.com>  wrote:
>>>
>>>        
>>>> Possibly this from Google will help?
>>>>
>>>>          
>>> OK, I think I've found the URL that you may have intended:
>>>
>>> http://weltall.heliohost.org/wordpress/2012/01/20/linux-kernel-3-3-rc1-and-nvidia-drivers/
>>>
>>> I followed the second fix that is described and now the nvidia-drivers
>>> emerge and work nicely with linux kernel-3.3.
>>>
>>> Thanks for the hint.
>>>
>>> There are changes to the kernel-3.3 tree that will have to addressed
>>> by the gentoo nvidia-drivers or other users will hit this problem
>>> as well.
>>>
>>> Frank Peters
>>>
>>>
>>>        
>> Glad you found it. That is the link I just sent along and good to know
>> it helped a bit.
>>
>> As I said, on kernel revision number changes I ALWAYS wait a minimum
>> of 3-5 days before trying to upgrade. nvidia always seems to need at
>> least a few days to catch up with a new release, or that's been my
>> experience in the past anyway.
>>
>> Cheers,
>> Mark
>>
>> On Mon, Mar 19, 2012 at 3:08 PM, Mark Knecht<markknecht@gmail.com>  wrote:
>>      
>>> As I said, on kernel revision number changes I ALWAYS wait a minimum
>>> of 3-5 days before trying to upgrade. nvidia always seems to need at
>>> least a few days to catch up with a new release, or that's been my
>>> experience in the past anyway.
>>>        
>> Same here, nvidia-drivers and vmware-modules are why I usually wait
>> until the .1 release on a new kernel series. :)
>>
>> Mark Knecht<markknecht@gmail.com>  skribis:
>>      
>>> And how would one use CUDA if we gave up nvidia-drivers? Does nouveau
>>> support all the CUDA stuff?
>>>        
>> I think they may have reverse engineered CUDA, but whether it is
>> implemented I don’t know, and I wouldn’t want to be the one to test
>> it, either. :)
>>
>> I’m donating processor time with boinc and that’s good enough reason
>> to use the binary driver if it gives me more processor to donate.
>>
>> (Waiting before installing anything new is painful, I know, because
>> with Gentoo you always feel like you want it to be doing something, or
>> at least that’s my experience. :) )
>>
>> On Mon, Mar 19, 2012 at 2:28 PM, Barry Schwartz
>> <chemoelectric@chemoelectric.org>  wrote:
>>      
>>> Mark Knecht<markknecht@gmail.com>  skribis:
>>>        
>>>> And how would one use CUDA if we gave up nvidia-drivers? Does nouveau
>>>> support all the CUDA stuff?
>>>>          
>>> I think they may have reverse engineered CUDA, but whether it is
>>> implemented I don’t know, and I wouldn’t want to be the one to test
>>> it, either. :)
>>>
>>> I’m donating processor time with boinc and that’s good enough reason
>>> to use the binary driver if it gives me more processor to donate.
>>>
>>> (Waiting before installing anything new is painful, I know, because
>>> with Gentoo you always feel like you want it to be doing something, or
>>> at least that’s my experience. :) )
>>>
>>>        
>> I have no problem with you or anyone else running nouveau. None at all.
>>
>> I do have a problem with someone saying 'it's time for everyone to
>> give up nvidia-drivers' without demonstrating they know the full
>> impact of what they are suggesting. Had Cheng Renquan suggest 'Maybe
>> people who don't need anything other than basic X capabilities should
>> consider running nouveau' I wouldn't have even chimed in.
>>
>> And thanks for running boinc. It's good of you and good for you.
>>
>> Cheers,
>> Mark
>>
>> Mark Knecht<markknecht@gmail.com>  skribis:
>>      
>>> I do have a problem with someone saying 'it's time for everyone to
>>> give up nvidia-drivers' without demonstrating they know the full
>>> impact of what they are suggesting. Had Cheng Renquan suggest 'Maybe
>>> people who don't need anything other than basic X capabilities should
>>> consider running nouveau' I wouldn't have even chimed in.
>>>        
>> Sage Notebook (sage-on-gentoo overlay) can use CUDA as well. I think
>> you don't have to worry that nvidia-drivers would go away; in the
>> worst case it would end up in a good overlay. That's unlikely IMO, and
>> would mostly likely be if there were an established alternative
>> implementation of CUDA.
>>
>> On Mon, 19 Mar 2012 14:40:34 -0700
>> Mark Knecht<markknecht@gmail.com>  wrote:
>>
>>      
>>> I have no problem with you or anyone else running nouveau. None at all.
>>>
>>> I do have a problem with someone saying 'it's time for everyone to
>>> give up nvidia-drivers' without demonstrating they know the full
>>> impact of what they are suggesting. Had Cheng Renquan suggest 'Maybe
>>> people who don't need anything other than basic X capabilities should
>>> consider running nouveau' I wouldn't have even chimed in.
>>>
>>>        
>> I think the main complaint is that the Nvidia drivers are closed
>> binary blobs while Nouveau is an attempt to create an entirely
>> open source driver.  The spirit of free software demands that we
>> support these open initiatives.
>>
>> Actually, until recently, I was very happy using the legacy open
>> source xorg nvidia driver known simply as as "nv."  It is still
>> available in Gentoo as x11-drivers/xf86-video-nv.
>>
>> Since I do not do gaming or other intensive graphic activities,
>> I could get by nicely with just nv.  However, the nv driver does
>> not seem to support the latest hardware too well.  On one of
>> my machines I have a card based on Nvidia GeForce 210.  Although
>> the nv driver works with this card, it does not enable the Xv
>> extension and consequently the graphic response is poor.
>>
>> On older cards nv does work quite well for ordinary purposes.
>>
>> Frank Peters
>>
>>
>> Frank Peters<frank.peters@comcast.net>  skribis:
>>      
>>> I think the main complaint is that the Nvidia drivers are closed
>>> binary blobs while Nouveau is an attempt to create an entirely
>>> open source driver.
>>>        
>> Unfortunately the nvidia drivers are needed not only for graphics but
>> also to use the GPU for scientific calculations, including for
>> donating processor time to medical research, for instance.
>>
>>
>> Frank Peters posted on Tue, 20 Mar 2012 00:03:06 -0400 as excerpted:
>>
>>      
>>> Actually, until recently, I was very happy using the legacy open source
>>> xorg nvidia driver known simply as as "nv."  It is still available in
>>> Gentoo as x11-drivers/xf86-video-nv.
>>>
>>> Since I do not do gaming or other intensive graphic activities, I could
>>> get by nicely with just nv.  However, the nv driver does not seem to
>>> support the latest hardware too well.
>>>        
>> FWIW, the old nv driver is legacy, now, and won't be supporting new
>> hardware.  AFAIK older hardware should be switching as well, for support
>> with current software, as nv won't be updated for that any longer, either.
>>
>> The same thing happened to it as happened to nvidia's proprietary network
>> driver some years ago; pretty much everyone involved, including the
>> distros that used to ship nv and nvidia itself, seems to have recognized
>> that the reverse-engineered work is now better than nvidia's basic
>> freedomware stub driver, nv, and nouveau has officially taken its place.
>>
>> --
>> Duncan - List replies preferred.   No HTML msgs.
>> "Every nonfree program has a lord, a master --
>> and if you use the program, he is your master."  Richard Stallman
>>
>>
>> Barry Schwartz posted on Tue, 20 Mar 2012 01:20:13 -0500 as excerpted:
>>
>>      
>>> Unfortunately the nvidia drivers are needed not only for graphics but
>>> also to use the GPU for scientific calculations, including for donating
>>> processor time to medical research, for instance.
>>>        
>> My donation ends where their disrespect for human freedom begins.  (Over
>> a decade ago, back on MS, I used to run distributed.net.  However, they
>> don't have a freedomware client, or at least didn't back then, and while
>> I understand the reasons why -- someone cheating and saying they did the
>> work when they didn't, just to get the stats -- that didn't change the
>> fact that I wasn't going to run servantware.  But as they say, YMMV.)
>>
>> --
>> Duncan - List replies preferred.   No HTML msgs.
>> "Every nonfree program has a lord, a master --
>> and if you use the program, he is your master."  Richard Stallman
>>
>>
>>      
>
>    

[gentoo-amd64] Unsubscribe

[Otávio Cipriani]

[-- Attachment #1: Type: text/plain, Size: 1151 bytes --]

Em 16/02/2012 04:36, "Nikos Chantziaras" <realnc@arcor.de> escreveu:

> On 16/02/12 02:06, Frank Peters wrote:
>
>> After updating nvidia-drivers from 290.10 to 295.20-r1, I cannot start X
>> and the log files contain this message:
>>
>> (EE) NVIDIA(0): Failed to initialize the NVIDIA kernel module. Please see
>> the
>> [  3482.609] (EE) NVIDIA(0):     system's kernel log for additional error
>> messages and
>> [  3482.609] (EE) NVIDIA(0):     consult the NVIDIA README for details.
>> [  3482.609] (EE) NVIDIA(0):  *** Aborting ***
>> [  3482.609]
>>
>> NVRM: API mismatch: the client has the version 295.20, but
>> NVRM: this kernel module has the version 290.10.
>>
>> What could be the problem?  I've seen no other reports of
>> this issue.
>>
>
> The above error means that the kernel module that is currently loaded is
> the old one while the X driver is the new one.  In other words, you only
> tried to restart X instead of rebooting the machine or terminating X, doing
> "modprobe -r nvidia" and then restarting X.
>
> Contrary to other posts, you do NOT need to rebuild your kernel.  You only
> need to load the new kernel module.
>
>
>

[-- Attachment #2: Type: text/html, Size: 1549 bytes --]

Re: [gentoo-amd64] Unsubscribe

[Dale]

To put it simply, NOPE.  You can't leave.  This is Hotel California.

gentoo-amd64+unsubscribe@lists.gentoo.org

If you follow the steps, we may let you leave.  Send to that address,
reply to the conformation.

Hope you have a sense of humour.  lol

Dale

:-)  :-)


-- 
I am only responsible for what I said ... Not for what you understood or
how you interpreted my words!

Miss the compile output?  Hint:
EMERGE_DEFAULT_OPTS="--quiet-build=n"

Re: [gentoo-amd64] Unsubscribe

[Otávio Cipriani]

[-- Attachment #1: Type: text/plain, Size: 562 bytes --]

Thank you Dale. :-D
Em 16/02/2012 08:54, "Dale" <rdalek1967@gmail.com> escreveu:

> To put it simply, NOPE.  You can't leave.  This is Hotel California.
>
> gentoo-amd64+unsubscribe@lists.gentoo.org
>
> If you follow the steps, we may let you leave.  Send to that address,
> reply to the conformation.
>
> Hope you have a sense of humour.  lol
>
> Dale
>
> :-)  :-)
>
>
> --
> I am only responsible for what I said ... Not for what you understood or
> how you interpreted my words!
>
> Miss the compile output?  Hint:
> EMERGE_DEFAULT_OPTS="--quiet-build=n"
>
>

[-- Attachment #2: Type: text/html, Size: 948 bytes --]

Re: [gentoo-amd64] Unsubscribe

[Benny Pedersen]

Den 2012-02-16 11:52, Dale skrev:
> To put it simply, NOPE.  You can't leave.  This is Hotel California.
> Hope you have a sense of humour.  lol

you need funtoo to have that ?

Re: [gentoo-amd64] Unsubscribe

[Dale]

Benny Pedersen wrote:
> Den 2012-02-16 11:52, Dale skrev:
>> To put it simply, NOPE.  You can't leave.  This is Hotel California.
>> Hope you have a sense of humour.  lol
> 
> you need funtoo to have that ?
> 
> 

LOL

Dale

:-)  :-)

-- 
I am only responsible for what I said ... Not for what you understood or
how you interpreted my words!

Miss the compile output?  Hint:
EMERGE_DEFAULT_OPTS="--quiet-build=n"

[gentoo-amd64] Possible Math Problem - Request For Verification

[Frank Peters]

[-- Attachment #1: Type: text/plain, Size: 3781 bytes --]

Hello,

Believe it or not, at the very beginning, Linux/GNU had some math problems.
In particular, it would do somewhat poorly on various floating point tests
that are available on-line.  Because I do mathematical work on my machine,
I used to regularly evaluate my software using these tests.

However, for the past several years Linux/GNU has gotten nearly perfect
scores on these same tests and it seemed that glibc and/or gcc had finally
gotten the math code right.  As a result of this, I stopped my regular
evaluations of the software.

Just recently I decided to run these tests again.  I expected to see the
same nearly perfect scores but, to my surprise, a failure occurred in the
area of complex number operations.  This may not be a very serious failure,
but it was not present during prior tests and thus it should not be present
now.

Possibly a fault has crept in somewhere either in glibc or gcc.  Because
I had stopped my regular testing I can't relate the failure to any specific
version change of either package.

I need to request a verification from any Gentoo users.  All that needs to
be done is run a straightforward software test.

The software is called UCBTEST and is described at http://www.netlib.org/fp/

The source code, however, is ancient Unix (1995) code and must be patched.
I have created a patched tarball that can run on recent Linux.  This file
is attached as ucbtest.tar.bz2

If one is accustomed to modern GUI software, this code is a mess, but it is
rather straightforward to implement.  Here are the steps:

1) Create a directory somewhere, e.g. /tmp/fp-test

2) Unpack the tarball into this directory.

3) Change into the /tmp/fp-test directory

4) Modify the ucbREADME/linux.sh file as follows:

Line 10 -- specify a full path for the results directory -- all test results
will be stored here -- e.g. /tmp/fp-test-results

Line 11 -- specify the full path to the Unix time program -- ucbtest won't run
without time -- for Gentoo just "emerge time" and the path will be "/usr/bin/time"

Line 17 -- specify the full path to the test directory -- same as in step #1

Line 36 -- enter your CFLAGS here

That's it as far as configuration.  Now, from the top directory of the source
just execute: 

ucbREADME/linux.sh

The code will take several minutes to compile, execute, and complete.  While
the test is running it will spit out its progress to stdout.  Upon completion
a brief summary is given:

UCBFAIL indicates problems!
/tmp/fp-test-results/ccos_DP.output: ucbtest UCBFAIL in COS(X) at line 444 for generic 
/tmp/fp-test-results/clib_DP.output: ucbtest UCBFAIL in cabsd at line 701 for double 
/tmp/fp-test-results/clib_DP.output: ucbtest UCBFAIL in powd at line 701 for double 
/tmp/fp-test-results/clib_DP.output:UCBFAIL clib_DP.output , 25 out of 25 tests completed
/tmp/fp-test-results/csin_DP.output: ucbtest UCBFAIL in SIN(X) at line 444 for generic 

only 11 out of 14 show UCBPASS!


There are expected failures in the trigonometric tests since trigonometric
performance is not specified in IEEE754/854.  The failure in powd (double power
function) is also expected.  But everything else should have passed.

In my case, the new failure occurs in the cabsd test, which is the absolute
value for complex numbers.  I have never seen this error previously and
it may possibly indicate some problem with either glibc or gcc. 

The results directory is also a mess (someone should really clean this code up).
In the results directory (see step #4) all detailed test results are contained
in the *.output files.

Anyway, if anyone wants to try this test, the steps have been outlined.
In spite of the messiness, the procedure is really quite simple, and the
ucbtest is a very good test of floating point performance.

Frank Peters


[-- Attachment #2: ucbtest.tar.bz2 --]
[-- Type: application/x-bzip2, Size: 520301 bytes --]

Re: [gentoo-amd64] Possible Math Problem - Request For Verification

[Volker Armin Hemmann]

Believe it or not, this tarball is straight from hell.

1. do not tar-bomb. Pack directories not files.
2. the permissions are a nightmare.
3. I accidentally unpacked in /tmp and your tarball tried to set UTIME and the 
permissions of the parent directory. WTF?
4. have you checked that the errors you are seeing are really errors?
Just remember that stupidity about 80bit/64bit/128bit floats all around.
5. http://gcc.gnu.org/wiki/FloatingPointMath

without additional settings gcc 4.5.2:

UCBFAIL indicates problems!
/tmp/usbtest/catan_DP.output:UCBFAIL catan_DP.output.tmp 127
/tmp/usbtest/ccos_DP.output:UCBFAIL ccos_DP.output.tmp 127
/tmp/usbtest/cdiv_DP.output:UCBFAIL cdiv_DP.output
/tmp/usbtest/cexp_DP.output:UCBFAIL cexp_DP.output.tmp 127
/tmp/usbtest/cexpm1_DP.output:UCBFAIL cexpm1_DP.output.tmp 127
/tmp/usbtest/cfindpi_DP.output:UCBFAIL cfindpi_DP.output
/tmp/usbtest/clib_DP.output: ucbtest UCBFAIL in cabsd at line 701 for double 
/tmp/usbtest/clib_DP.output: ucbtest UCBFAIL in powd at line 701 for double 
/tmp/usbtest/clib_DP.output:UCBFAIL clib_DP.output , 25 out of 25 tests 
completed
/tmp/usbtest/clog1p_DP.output:UCBFAIL clog1p_DP.output.tmp 127
/tmp/usbtest/clog_DP.output:UCBFAIL clog_DP.output.tmp 127
/tmp/usbtest/cmul_DP.output:UCBFAIL cmul_DP.output
/tmp/usbtest/cpar_DP.output:UCBFAIL cpar_DP.output
/tmp/usbtest/cpi_DP.output:UCBFAIL cpi_DP.output
/tmp/usbtest/csin_DP.output:UCBFAIL csin_DP.output.tmp 127
/tmp/usbtest/csqr_DP.output:UCBFAIL csqr_DP.output






-- 
#163933

Re: [gentoo-amd64] Possible Math Problem - Request For Verification

[Volker Armin Hemmann]

On Sunday 26 June 2011 13:30:41 you wrote:
> Believe it or not, this tarball is straight from hell.
> 
> 1. do not tar-bomb. Pack directories not files.
> 2. the permissions are a nightmare.
> 3. I accidentally unpacked in /tmp and your tarball tried to set UTIME and
> the permissions of the parent directory. WTF?
> 4. have you checked that the errors you are seeing are really errors?
> Just remember that stupidity about 80bit/64bit/128bit floats all around.
> 5. http://gcc.gnu.org/wiki/FloatingPointMath
> 
> without additional settings gcc 4.5.2:
> 
> UCBFAIL indicates problems!
> /tmp/usbtest/catan_DP.output:UCBFAIL catan_DP.output.tmp 127
> /tmp/usbtest/ccos_DP.output:UCBFAIL ccos_DP.output.tmp 127
> /tmp/usbtest/cdiv_DP.output:UCBFAIL cdiv_DP.output
> /tmp/usbtest/cexp_DP.output:UCBFAIL cexp_DP.output.tmp 127
> /tmp/usbtest/cexpm1_DP.output:UCBFAIL cexpm1_DP.output.tmp 127
> /tmp/usbtest/cfindpi_DP.output:UCBFAIL cfindpi_DP.output
> /tmp/usbtest/clib_DP.output: ucbtest UCBFAIL in cabsd at line 701 for double
> /tmp/usbtest/clib_DP.output: ucbtest UCBFAIL in powd at line 701 for double
> /tmp/usbtest/clib_DP.output:UCBFAIL clib_DP.output , 25 out of 25 tests
> completed
> /tmp/usbtest/clog1p_DP.output:UCBFAIL clog1p_DP.output.tmp 127
> /tmp/usbtest/clog_DP.output:UCBFAIL clog_DP.output.tmp 127
> /tmp/usbtest/cmul_DP.output:UCBFAIL cmul_DP.output
> /tmp/usbtest/cpar_DP.output:UCBFAIL cpar_DP.output
> /tmp/usbtest/cpi_DP.output:UCBFAIL cpi_DP.output
> /tmp/usbtest/csin_DP.output:UCBFAIL csin_DP.output.tmp 127
> /tmp/usbtest/csqr_DP.output:UCBFAIL csqr_DP.output

ignore those results, were without time.

with time and additional -frounding-math -fsignaling-nans -fno-builtin"

UCBFAIL indicates problems!
/tmp/usbtest/ccos_DP.output: ucbtest UCBFAIL in COS(X) at line 444 for generic 
/tmp/usbtest/clib_DP.output: ucbtest UCBFAIL in cabsd at line 701 for double 
/tmp/usbtest/clib_DP.output: ucbtest UCBFAIL in powd at line 701 for double 
/tmp/usbtest/clib_DP.output:UCBFAIL clib_DP.output , 25 out of 25 tests 
completed
/tmp/usbtest/csin_DP.output: ucbtest UCBFAIL in SIN(X) at line 444 for generic 

only 11 out of 14 show UCBPASS!


-- 
#163933

[gentoo-amd64] unsubscribe

[Piotr Hosowicz]

unsubscribe

Re: [gentoo-amd64] unsubscribe

[Dale]

Piotr Hosowicz wrote:
> unsubscribe
>
>

NO !!!  You can't leave.  :-P

List-Unsubscribe:<mailto:gentoo-amd64+unsubscribe@lists.gentoo.org>

That may help tho.  Just do like you did when you checked in.  We MAY let you check out.  lol

Dale

:-)  :-)

Re: [gentoo-amd64] unsubscribe

[Lie Ryan]

[-- Attachment #1: Type: text/plain, Size: 466 bytes --]

2011/6/27 Dale <rdalek1967@gmail.com>

> Piotr Hosowicz wrote:
>
>> unsubscribe
>>
>>
>>
> NO !!!  You can't leave.  :-P
>
> List-Unsubscribe:<mailto:gento**o-amd64+unsubscribe@lists.**gentoo.org<gentoo-amd64%2Bunsubscribe@lists.gentoo.org>
> >
>
> That may help tho.  Just do like you did when you checked in.  We MAY let
> you check out.  lol
>
>
Anyone noticed that this list have a higher than normal tendency to bully
those who tried to unsubscribe and failed?

[-- Attachment #2: Type: text/html, Size: 919 bytes --]

Re: [gentoo-amd64] unsubscribe

[Volker Armin Hemmann]

On Monday 27 June 2011 03:26:59 Lie Ryan wrote:
> 2011/6/27 Dale <rdalek1967@gmail.com>
> 
> > Piotr Hosowicz wrote:
> >> unsubscribe
> > 
> > NO !!!  You can't leave.  :-P
> > 
> > List-Unsubscribe:<mailto:gento**o-amd64+unsubscribe@lists.**gentoo.org<g
> > entoo-amd64%2Bunsubscribe@lists.gentoo.org>
> > 
> > 
> > That may help tho.  Just do like you did when you checked in.  We MAY
> > let
> > you check out.  lol
> 
> Anyone noticed that this list have a higher than normal tendency to bully
> those who tried to unsubscribe and failed?

bully? No, make fun of people failing to follow basic instructions? Maybe. But 
not more than gentoo-user...

-- 
#163933

Re: [gentoo-amd64] unsubscribe

[Dale]

Volker Armin Hemmann wrote:
> On Monday 27 June 2011 03:26:59 Lie Ryan wrote:
>    
>> 2011/6/27 Dale<rdalek1967@gmail.com>
>>
>>      
>>> Piotr Hosowicz wrote:
>>>        
>>>> unsubscribe
>>>>          
>>> NO !!!  You can't leave.  :-P
>>>
>>> List-Unsubscribe:<mailto:gento**o-amd64+unsubscribe@lists.**gentoo.org<g
>>> entoo-amd64%2Bunsubscribe@lists.gentoo.org>
>>>
>>>
>>> That may help tho.  Just do like you did when you checked in.  We MAY
>>> let
>>> you check out.  lol
>>>        
>> Anyone noticed that this list have a higher than normal tendency to bully
>> those who tried to unsubscribe and failed?
>>      
> bully? No, make fun of people failing to follow basic instructions? Maybe. But
> not more than gentoo-user...
>
>    
I admit, it annoys me but I know that a LOT of mailing lists tell a 
person to unsubscribe the way they are trying to do here.  Thing is, it 
doesn't work here.  So, I just try to be funny then provide the needed 
info to help the person check out.   At least they leave laughing, 
hopefully.

At least I didn't post the one with the long instructions that involve 
contacting their ISP.  ;-)  It is funny tho, if you bother to read it.

Dale

:-)  :-)

Re: [gentoo-amd64] unsubscribe

[Dale]

[-- Attachment #1: Type: text/plain, Size: 609 bytes --]

Lie Ryan wrote:
> 2011/6/27 Dale <rdalek1967@gmail.com <mailto:rdalek1967@gmail.com>>
>
>     Piotr Hosowicz wrote:
>
>         unsubscribe
>
>
>
>     NO !!!  You can't leave.  :-P
>
>     List-Unsubscribe:<mailto:gentoo-amd64+unsubscribe@lists.gentoo.org
>     <mailto:gentoo-amd64%2Bunsubscribe@lists.gentoo.org>>
>
>     That may help tho.  Just do like you did when you checked in.  We
>     MAY let you check out.  lol
>
>
> Anyone noticed that this list have a higher than normal tendency to 
> bully those who tried to unsubscribe and failed?
>

Who is bullying?  I certainly haven't.

Dale

:-)  :-)

[-- Attachment #2: Type: text/html, Size: 1520 bytes --]

[gentoo-amd64] tcptraceroute have buffer overflow in ipv6

[Benny Pedersen]

tcptraceroute ipv6.google.com 80

shows me a nice buffer overflow, i like to camture it into a log file but
lost on how :/

tryed:
tcptraceroute ipv6.google.com 80 | less

and press s from less to save it, still no file content to save :(

Re: [gentoo-amd64] tcptraceroute have buffer overflow in ipv6

[Benny Pedersen]

> To capture both, redirect STDOUT first, then set STDERR to match:
> tcptraceroute ipv6.google.com 80 > /path/to/log/file 2>&1

i end with 2 empty files

would have being usefull if -d have turned stderr over to stdout for debug

what more can i try now ?

Re: [gentoo-amd64] tcptraceroute have buffer overflow in ipv6

[Frank Peters]

On Thu, 14 Apr 2011 06:18:09 +0200
Benny Pedersen <me@junc.org> wrote:

> 
> i end with 2 empty files
> 
> would have being usefull if -d have turned stderr over to stdout for debug
> 
> what more can i try now ?
> 

If console redirection is not working, a possible work around is to use
the script command.  This will capture everything that is sent to the
console, either via the keyboard or STDOUT/STDERR.

script /path/to/output/file

command 1
command 2
 ...
exit

See the man page for script.

Frank Peters

[gentoo-amd64] unsubscribe

[Guy Harrison]

Re: [gentoo-amd64] unsubscribe

[Dale]

Guy Harrison wrote:

Nope.  It ain't happening.  lol

List-Post:<mailto:gentoo-amd64@lists.gentoo.org>
List-Help:<mailto:gentoo-amd64+help@lists.gentoo.org>
List-Unsubscribe:<mailto:gentoo-amd64+unsubscribe@lists.gentoo.org>
List-Subscribe:<mailto:gentoo-amd64+subscribe@lists.gentoo.org>

That may help tho.

Dale

:-)  :-)

Re: [gentoo-amd64] unsubscribe

[Guy Harrison]

On Monday 02 May 2011 21:19:18 Dale wrote:
> Guy Harrison wrote:
>
> Nope.  It ain't happening.  lol
>
> List-Post:<mailto:gentoo-amd64@lists.gentoo.org>
> List-Help:<mailto:gentoo-amd64+help@lists.gentoo.org>
> List-Unsubscribe:<mailto:gentoo-amd64+unsubscribe@lists.gentoo.org>
> List-Subscribe:<mailto:gentoo-amd64+subscribe@lists.gentoo.org>
>
> That may help tho.
>
> Dale
>
> :-)  :-)

Cheers Dale, you're a star! :-))

[gentoo-amd64] unsubscribe

[redspot]

On Mon, Jan 17, 2011 at 10:02 PM,  <gentoo-amd64+help@lists.gentoo.org> wrote:
> Topics (messages 12890 through 12890):
>
> [gentoo-amd64] horde h3 php 5.3 success ?
>      12890 - Benny Pedersen <me@junc.org>
>
>
>
> here it fails :(
>
> but i can get roundcube up just fine, php 5.3.5 does have a bug with
> libphp.so is not installed in correct dir, i symlinked it to get it back
>
> others running horde h3 ?
>
>
>
>

Re: [gentoo-amd64] unsubscribe

[Dale]

Not so fast there slick.

> To unsubscribe from a list, send an empty email to:
>
> listname+unsubscribe@lists.gentoo.org

http://www.gentoo.org/main/en/lists.xml

May have more success with that.  Replace the needed sections of course.

Dale

:-)  :-)

[gentoo-amd64] unsubscribe

[Michele Schiavo]

Re: [gentoo-amd64] unsubscribe

[Alex Alexander]

On 13 Oct 2010, at 20:05, Michele Schiavo <micheleschi@gmail.com> wrote:

> 
> 

Sorry, once you've subscribed, you're stuck with us for life ;)

Seriously though, you should follow the instructions here: http://www.gentoo.org/main/en/lists.xml

Alex | wired | sent from my i4

Re: [gentoo-amd64] unsubscribe

[Thanasis]

 send mail to

gentoo-amd64+unsubscribe@lists.gentoo.org

Re: [gentoo-amd64] unsubscribe

[Daniel de Oliveira]

[-- Attachment #1: Type: text/plain, Size: 425 bytes --]

I have the same problem, I've tried to unsubscribe (to subscribe in another
mail) and nothing happens.

2010/10/13 Thanasis <thanasis@asyr.hopto.org>

>  send mail to
>
> gentoo-amd64+unsubscribe@lists.gentoo.org<gentoo-amd64%2Bunsubscribe@lists.gentoo.org>
>
>


-- 
Daniel de Oliveira
----
Network and System Analyst
Security Specialist
IBM RISC Specialist
IBM Storage Specialist
Linux/Unix Specialist
Linux User #: 405334

[-- Attachment #2: Type: text/html, Size: 750 bytes --]

Re: [gentoo-amd64] unsubscribe

[Alex Alexander]

[-- Attachment #1: Type: text/plain, Size: 618 bytes --]

On 22 Oct 2010, at 20:26, Daniel de Oliveira <akulatraxas@gmail.com> wrote:

> I have the same problem, I've tried to unsubscribe (to subscribe in another mail) and nothing happens.
> 
> 2010/10/13 Thanasis <thanasis@asyr.hopto.org>
>  send mail to
> 
> gentoo-amd64+unsubscribe@lists.gentoo.org
> 
> 
> 
> 
> -- 
> Daniel de Oliveira
> ----
> Network and System Analyst
> Security Specialist
> IBM RISC Specialist
> IBM Storage Specialist
> Linux/Unix Specialist 
> Linux User #: 405334

Check your spam folder, the unsubscribe confirmation is probably there :)

Alex | wired | sent from my i4

[-- Attachment #2: Type: text/html, Size: 1693 bytes --]

Re: [gentoo-amd64] unsubscribe

[Drake Donahue]

On Fri, 2010-10-22 at 15:26 -0200, Daniel de Oliveira wrote:
> I have the same problem, I've tried to unsubscribe (to subscribe in
> another mail) and nothing happens.
> 
> 2010/10/13 Thanasis <thanasis@asyr.hopto.org>
>          send mail to
>         
>         gentoo-amd64+unsubscribe@lists.gentoo.org
>         
> 
> 
> 
> -- 
> Daniel de Oliveira
> ----
> Network and System Analyst
> Security Specialist
> IBM RISC Specialist
> IBM Storage Specialist
> Linux/Unix Specialist 
> Linux User #: 405334

Read the direct6ions at: http://www.gentoo.org/main/en/lists.xml which
say:

To unsubscribe from a list, send an empty email to:

listname+unsubscribe@lists.gentoo.org

Re: [gentoo-amd64] unsubscribe

[Daniel de Oliveira]

[-- Attachment #1: Type: text/plain, Size: 1200 bytes --]

Nope, not in spam folder and I make all the things. Ive already do
unsubscribe on this mail and a new subscribe to other 5 lists, only this one
have this problem.

On Fri, Oct 22, 2010 at 17:28, Drake Donahue <donahue95@comcast.net> wrote:

> On Fri, 2010-10-22 at 15:26 -0200, Daniel de Oliveira wrote:
> > I have the same problem, I've tried to unsubscribe (to subscribe in
> > another mail) and nothing happens.
> >
> > 2010/10/13 Thanasis <thanasis@asyr.hopto.org>
> >          send mail to
> >
> >         gentoo-amd64+unsubscribe@lists.gentoo.org<gentoo-amd64%2Bunsubscribe@lists.gentoo.org>
> >
> >
> >
> >
> > --
> > Daniel de Oliveira
> > ----
> > Network and System Analyst
> > Security Specialist
> > IBM RISC Specialist
> > IBM Storage Specialist
> > Linux/Unix Specialist
> > Linux User #: 405334
>
> Read the direct6ions at: http://www.gentoo.org/main/en/lists.xml which
> say:
>
> To unsubscribe from a list, send an empty email to:
>
> listname+unsubscribe@lists.gentoo.org<listname%2Bunsubscribe@lists.gentoo.org>
>
>
>


-- 
Daniel de Oliveira
----
Network and System Analyst
Security Specialist
IBM RISC Specialist
IBM Storage Specialist
Linux/Unix Specialist
Linux User #: 405334

[-- Attachment #2: Type: text/html, Size: 1849 bytes --]

Re: [gentoo-amd64] unsubscribe

[Juan Fco. Giordana]

I also have issues with my gmail account and gentoo e-mail servers:

http://www.google.com/support/forum/p/gmail/thread?tid=079890087213d489&hl=en

Feel free to contribute to that post so they may check the issue.

On 10/22/2010 05:26 PM, Daniel de Oliveira wrote:
> Nope, not in spam folder and I make all the things. Ive already do
> unsubscribe on this mail and a new subscribe to other 5 lists, only this
> one have this problem.

[gentoo-amd64] unsubscribe

[Rafał]

[-- Attachment #1: Type: text/html, Size: 16 bytes --]

[gentoo-amd64] unsubscribe

[Осипов Станислав]

unsubscribe

Re: [gentoo-amd64] unsubscribe

[Xi Shen]

you should email to unsubscribe-gentoo-amd64@lists.gentoo.org :)


On Mon, Jan 11, 2010 at 6:26 AM, Осипов Станислав <demofly@mail.ru> wrote:
>
> unsubscribe
>
>



--
Best Regards,
David Shen

http://twitter.com/davidshen84/
http://meme.yahoo.com/davidshen84/

[gentoo-amd64] unsubscribe

[Donald Anderson]

unsubscribe

[gentoo-amd64] unsubscribe

[Donald Anderson]

unsubscribe

Re: [gentoo-amd64] unsubscribe

[Eduardo Schoedler]

RTFM !!!!

http://www.gentoo.org/main/en/lists.xml

To unsubscribe from a list, send an EMPTY EMAIL to:
listname+unsubscribe@lists.gentoo.org



----- Original Message ----- 
From: "Donald Anderson" <dwa@bristowhill.com>
Sent: Friday, July 24, 2009 3:58 PM
Subject: [gentoo-amd64] unsubscribe


> unsubscribe

[gentoo-amd64] unsubscribe

[igor]

unsubscribe

Re: [gentoo-amd64] unsubscribe

[Denis Solaro]

play him off, keyboard cat 

On Sat, 2009-07-11 at 10:31 +0300, igor@satelittv.md wrote:
> unsubscribe
> 
> 
-- 
Denis Solaro <dsolaro@coffeehaus.com>

[gentoo-amd64] unsubscribe

[l0rd4gu1 .]

[-- Attachment #1: Type: text/plain, Size: 206 bytes --]

-- 
Ing. Raúl Alvarez Aguileta
Red de Control Corporativo
(52)55 1473-8581

Victorious warriors win first and then go to war, while defeated warriors go
to war first and then seek to win. -- Sun-Tzu

[-- Attachment #2: Type: text/html, Size: 241 bytes --]

Re: [gentoo-amd64] unsubscribe

[Bob Sanders]

l0rd4gu1 ., mused, then expounded:
> -- 
> Ing. Raúl Alvarez Aguileta
> Red de Control Corporativo
> (52)55 1473-8581
> 
> Victorious warriors win first and then go to war, while defeated warriors go
> to war first and then seek to win. -- Sun-Tzu

To be a victorious warrior, one must study all the information.  Such as
that found in the email headers:

List-Unsubscribe: <mailto:gentoo-amd64+unsubscribe@lists.gentoo.org>

And one must use the correct syntax so the list doesn't get spammed with
unsubscribe messages.

Bob
-- 
-  

Re: [gentoo-amd64] unsubscribe

[Homer Parker]

On Thu, 2009-06-18 at 11:00 -0700, Bob Sanders wrote:
> And one must use the correct syntax so the list doesn't get spammed with
> unsubscribe messages.

	What happened to the unsubscribe kit to help people with? ;)

-- 
Homer Parker <hparker@gentoo.org>

Re: [gentoo-amd64] unsubscribe

[Peter Humphrey]

On Saturday 20 June 2009 03:48:32 Homer Parker wrote:

> 	What happened to the unsubscribe kit to help people with? ;)

Something nasty, I hope.

-- 
Rgds
Peter

Re: [gentoo-amd64] unsubscribe

[felix]

On Sat, Jun 20, 2009 at 10:18:51AM +0100, Peter Humphrey wrote:
> On Saturday 20 June 2009 03:48:32 Homer Parker wrote:
> 
> > 	What happened to the unsubscribe kit to help people with? ;)
> 
> Something nasty, I hope.

One should be careful what one wishes for ...

Here's how to unsubscribe:

First, ask your Internet Provider to mail you an Unsubscribing Kit.
Then follow these directions.

The kit will most likely be the standard no-fault type. Depending on
requirements, System A and/or System B can be used. When operating
System A, depress lever and a plastic dalkron unsubscriber will be
dispensed through the slot immediately underneath. When you have
fastened the adhesive lip, attach connection marked by the large "X"
outlet hose. Twist the silver-coloured ring one inch below the
connection point until you feel it lock.

The kit is now ready for use. The Cin-Eliminator is activated by the
small switch on the lip.  When securing, twist the ring back to its
initial condition, so that the two orange lines meet.  Disconnect.
Place the dalkron unsubscriber in the vacuum receptacle to the rear.
Activate by pressing the blue button.

The controls for System B are located on the opposite side. The red
release switch places the Cin-Eliminator into position; it can be
adjusted manually up or down by pressing the blue manual release
button. The opening is self-adjusting. To secure after use, press the
green button, which simultaneously activates the evaporator and
returns the Cin-Eliminator to its storage position.

You may log off if the green exit light is on over the evaporator.  If
the red light is illuminated, one of the Cin-Eliminator requirements
has not been properly implemented. Press the "List Guy" call button on
the right of the evaporator. He will secure all facilities from his
control panel.

To use the Auto-Unsub, first undress and place all your clothes in the
clothes rack. Put on the velcro slippers located in the cabinet
immediately below. Enter the shower, taking the entire kit with
you. On the control panel to your upper right upon entering you will
see a "Shower seal" button. Press to activate. A green light will then
be illuminated immediately below. On the intensity knob, select the
desired setting. Now depress the Auto-Unsub activation lever. Bathe
normally.

The Auto-Unsub will automatically go off after three minutes unless
you activate the "Manual off" override switch by flipping it up. When
you are ready to leave, press the blue "Shower seal" release
button. The door will open and you may leave. Please remove the velcro
slippers and place them in their container.

If you prefer the ultrasonic log-off mode, press the indicated blue
button. When the twin panels open, pull forward by rings A & B. The
knob to the left, just below the blue light, has three settings, low,
medium or high. For normal use, the medium setting is suggested.

After these settings have been made, you can activate the device by
switching to the "ON" position the clearly marked red switch. If
during the unsubscribing operation you wish to change the settings,
place the "manual off" override switch in the "OFF" position. You may
now make the change and repeat the cycle. When the green exit light
goes on, you may log off and have lunch. Please close the door behind
you.


-- 
            ... _._. ._ ._. . _._. ._. ___ .__ ._. . .__. ._ .. ._.
     Felix Finch: scarecrow repairman & rocket surgeon / felix@crowfix.com
  GPG = E987 4493 C860 246C 3B1E  6477 7838 76E9 182E 8151 ITAR license #4933
I've found a solution to Fermat's Last Theorem but I see I've run out of room o

[gentoo-amd64] unsubscribe

[redspot]

[-- Attachment #1: Type: text/plain, Size: 1 bytes --]



[-- Attachment #2: Type: text/html, Size: 5 bytes --]

[gentoo-amd64] unsubscribe

[Mateusz Mierzwinski]

unsubscribe

[gentoo-amd64] unsubscribe

[Eirik Rude]

[-- Attachment #1: Type: text/plain, Size: 1 bytes --]



[-- Attachment #2: Type: text/html, Size: 5 bytes --]

[gentoo-amd64] unsubscribe

[Adam Mooz]

[-- Attachment #1: Type: text/plain, Size: 13 bytes --]

unsubscribe


[-- Attachment #2: Type: text/html, Size: 1631 bytes --]

Re: [gentoo-amd64] unsubscribe

[Paul Hartman]

On Thu, Nov 6, 2008 at 2:36 PM, Adam Mooz <adam.mooz@gmail.com> wrote:
> unsubscribe

You're doing it wrong. Send e-mail to
gentoo-amd64+unsubscribe@lists.gentoo.org instead.

[gentoo-amd64] unsubscribe

[redspot]

On Wed, Nov 5, 2008 at 7:00 PM,  <gentoo-amd64+help@lists.gentoo.org> wrote:
> Topics (messages 10055 through 10074):
>
> [gentoo-amd64] mplayerplug-in update bombs
>      10055 - "Mark Haney" <mhaney@ercbroadband.org>
>
> [gentoo-amd64] mplayerplug-in update bombs
>      10056 - Beso <givemesugarr@gmail.com>
>
> [gentoo-amd64] Re: Fwd: [install] emerge gentoo-sources fails
>      10057 - "Martin Herrman" <martin@herrman.nl>
>
> [gentoo-amd64] Still unable to unmask KDE4.1.2
>      10058 - "Mark Haney" <mhaney@ercbroadband.org>
>
> [gentoo-amd64] Re: Fwd: [install] emerge gentoo-sources fails
>      10059 - Michael Moore <mikem.unet@gmail.com>
>
> [gentoo-amd64] Still unable to unmask KDE4.1.2
>      10060 - Richard Freeman <rich0@gentoo.org>
>
> [gentoo-amd64] Still unable to unmask KDE4.1.2
>      10061 - Barry Schwartz <chemoelectric@chemoelectric.org>
>
> [gentoo-amd64] Still unable to unmask KDE4.1.2
>      10062 - "Mark Haney" <mhaney@ercbroadband.org>
>
> [gentoo-amd64] Still unable to unmask KDE4.1.2
>      10063 - "Mark Haney" <mhaney@ercbroadband.org>
>
> [gentoo-amd64] Still unable to unmask KDE4.1.2
>      10064 - "Mark Haney" <mhaney@ercbroadband.org>
>
> [gentoo-amd64] Still unable to unmask KDE4.1.2 -- Solved
>      10065 - "Mark Haney" <mhaney@ercbroadband.org>
>
> [gentoo-amd64] KDE 4.1.2 issues
>      10066 - "Mark Haney" <mhaney@ercbroadband.org>
>
> [gentoo-amd64] KDE 4.1.2 issues - updated
>      10067 - "Mark Haney" <mhaney@ercbroadband.org>
>
> [gentoo-amd64] KDE 4.1.2 issues - updated
>      10068 - Beso <givemesugarr@gmail.com>
>
> [gentoo-amd64] KDE 4.1.2 issues - updated
>      10069 - "Till Schwalbe (Gentoo)" <gentoo@cumulum.de>
>
> [gentoo-amd64] KDE 4.1.2 issues - updated
>      10070 - "Mark Haney" <mhaney@ercbroadband.org>
>
> [gentoo-amd64] KDE 4.1.2 issues - updated
>      10071 - "Mark Haney" <mhaney@ercbroadband.org>
>
> [gentoo-amd64] KDE 4.1.2 issues - updated
>      10072 - Beso <givemesugarr@gmail.com>
>
> [gentoo-amd64] Re: KDE 4.1.2 issues - updated
>      10073 - Duncan <1i5t5.duncan@cox.net>
>
> [gentoo-amd64] KDE 4.1.2 issues - updated -- SOLVED
>      10074 - "Mark Haney" <mhaney@ercbroadband.org>
>
>
>
> I just tried to update mplayerplug-in and this is what I get:
>
> configure: Determining mozilla/firefox packages to build against
> checking for MOZPLUG... no
> configure: WARNING: firefox-plugin not found
> checking for MOZPLUG... no
> configure: WARNING: seamonkey-plugin not found
> checking for MOZPLUG... no
> configure: WARNING: xulrunner-plugin not found
> checking for MOZPLUG... no
> configure: WARNING: iceape-plugin not found
> configure: error: Unable to find mozilla or firefox development files
>
>
>
> I've never seen that with previous builds, so I'm not sure how to proceed.  Any ideas?
>
>
> --
> Frustra laborant quotquot se calculationibus fatigant pro inventione quadraturae circuli
>
> Mark Haney
> Sr. Systems Administrator
> ERC Broadband
> (828) 350-2415
>
> Call (866) ERC-7110 for after hours support
>
> 2008/10/31 Mark Haney <mhaney@ercbroadband.org>:
>> I just tried to update mplayerplug-in and this is what I get:
>>
>> configure: Determining mozilla/firefox packages to build against
>> checking for MOZPLUG... no
>> configure: WARNING: firefox-plugin not found
>> checking for MOZPLUG... no
>> configure: WARNING: seamonkey-plugin not found
>> checking for MOZPLUG... no
>> configure: WARNING: xulrunner-plugin not found
>> checking for MOZPLUG... no
>> configure: WARNING: iceape-plugin not found
>> configure: error: Unable to find mozilla or firefox development files
>>
>>
>>
>> I've never seen that with previous builds, so I'm not sure how to proceed.
>>  Any ideas?
>>
>>
>
>
> install mozilla-firefox and not only mozilla-firefox-bin. then you
> should have both working on a multilib profile. the latest
> mplayerplug-in versions have a multilib profile set by default and
> build for both firefoxes. also you'll need both mplayer-bin and
> mplayer installed.
>
> --
> dott. ing. beso
>
> Hi Michael and Duncan,
>
> you two had send me a reply some time ago, but I didn't had the time
> to reply. Well, here it is :-)
>
> In the mean time my desktop is 'fully' functional, at least I can do
> my usual stuff on it.
>
> Of course I have had some issues that needed to be solved:
> - forgot to include USB HID support in my kernel :-)
> - network-adapter driver is broken is current gentoo sources, so I had
> to take kernel.org's 2.6.27.4
> - radeon driver didn't recognise video-chip (yeah, had to unmask
> radeonhd driver..)
> - wireless card required firmware in /lib/firmware
> - ... lots I already forgot..
> But it could all be solved within minutes or in some cases within a
> small couple of hours!
>
> That takes me to the issues I have experienced with FreeBSD: although
> it looks like a very well-documented (and centralised!) system, I had
> problems understanding e.g. the ports way of installing software. I
> had lot's of errors, which I couldn't solve. I think that Gentoo's
> user-base is much larger, which makes it easier to find solutions and
> bug-reports online. But also the messages shown at e.g. the output of
> emerge help a lot. In FreeBSD I also had trouble to do a full system
> upgrade: what are the command's you should use in what sequence? I had
> that information avaialble for gentoo in minutes.
> Maybe I do not have an objective view, because I know Linux quite well
> and FreeBSD is totally new to me.
>
> Best regards,
>
> Martin
>
> On Tue, Oct 21, 2008 at 4:14 AM, Michael Moore <mikem.unet@gmail.com> wrote:
>> On 19:37 Mon 20 Oct     , Martin Herrman wrote:
>>> I have used slackware, redhat, mandrake and debian before (in that
>>> order) and about 2 years ago switched to Ubuntu because it was so easy
>>> to use. But it's also bloated (it is even hard to compile your own
>>> kernel) and that's why I started to use Gentoo 2 months ago on my
>>> notebook. I liked it (compared to FreeBSD: that ports system is
>>> documented so badly..)!
>>
>> Surprised to hear that, because quite a lot of people (including yours
>> truly) find FreeBSD and Gentoo to be couple of the most well documented
>> systems.
>>
>> So, what was the exact problem you had with the ports documentation?
>>
>> --
>>
>> Regards,
>> Michael Moore <mikem.unet(at)gmail.com>
>> About *NIX: If its not fun, why do it?
>>
>>
>
> Well, after 2 weeks of fumbling and fidgeting, I still am unable to unmask KDE4.1.2.  I really do not know now where to go from this point. Here's what I"ve done.
>
> I've removed all KDE4.0.X packages.
>
> I've keyworded the KDE:4 packages (per the documentation) and I still do not see any KDE4.1.2 packages listed in emerge -upD world.
>
> I thought, at one time that I needed to also unmask the KDE4.1.2 files since I"m not running ~amd64, but that didn't change anything.
>
> I'm at a complete loss for where to go now.
>
> --
> Frustra laborant quotquot se calculationibus fatigant pro inventione quadraturae circuli
>
> Mark Haney
> Sr. Systems Administrator
> ERC Broadband
> (828) 350-2415
>
> Call (866) ERC-7110 for after hours support
>
> On 19:51 Sun 02 Nov     , Martin Herrman wrote:
>> That takes me to the issues I have experienced with FreeBSD: although
>> it looks like a very well-documented (and centralised!) system, I had
>> problems understanding e.g. the ports way of installing software. I
>> had lot's of errors, which I couldn't solve. I think that Gentoo's
>> user-base is much larger, which makes it easier to find solutions and
>> bug-reports online. But also the messages shown at e.g. the output of
>> emerge help a lot. In FreeBSD I also had trouble to do a full system
>> upgrade: what are the command's you should use in what sequence? I had
>> that information avaialble for gentoo in minutes.
>> Maybe I do not have an objective view, because I know Linux quite well
>> and FreeBSD is totally new to me.
>>
>> Best regards,
>>
>> Martin
>>
> Hi Martin,
>
> In a nutshell you could say that Gentoo Linux has a highly refined
> implementation of the methods of FreeBSD (though at the core they
> are two totally different systems- technically & philosophically).
> It includes an excellent package manager and a lot of well polished
> tools (eselect et al.) which make system administration less of a
> chore and infact a highly easy job (contrary to popular belief).
> This is one of the reasons i love Gentoo Linux -- it provides the
> power without putting you into too much of an inconvenience. But
> that doesn't take anything away from FreeBSD, which has managed to
> still follow the KISS Principle and keep things fairly well integrated.
>
> As regards the emerge output, you would realise that the make output of
> the ports system isn't different. And as for the update just read the
> docs. You would find out that a world update in FreeBSD is quite similar
> to others, provided if you get the knowhow about userland and system.
>
> But, anyways both are quite different systems so, please don't view
> anyone with any kind of prejudice. I am not trying to profess any particular
> system but, you should only criticise something once you are fairly well versed
> with it.
>
> --
>
> Michael Moore <mikem.unet(at)gmail.com>
> About *NIX: If its not fun, why do it?
>
> Mark Haney wrote:
>>
>> Well, after 2 weeks of fumbling and fidgeting, I still am unable to unmask KDE4.1.2.  I really do not know now where to go from this point. Here's what I"ve done.
>>
>> I've removed all KDE4.0.X packages.
>>
>> I've keyworded the KDE:4 packages (per the documentation) and I still do not see any KDE4.1.2 packages listed in emerge -upD world.
>>
>> I thought, at one time that I needed to also unmask the KDE4.1.2 files since I"m not running ~amd64, but that didn't change anything.
>>
>> I'm at a complete loss for where to go now.
>>
>
> Are you using a package manager that supports EAPI 2?  I suspect that this is only supported by portage v2.2 or newer versions of paludis - and the unstable kde ebuilds use EAPI 2 so they would be masked by older versions of either package manager.
>
> Mark Haney <mhaney@ercbroadband.org> skribis:
>> I've keyworded the KDE:4 packages (per the documentation) and I still do
>> not see any KDE4.1.2 packages listed in emerge -upD world.
>
> I haven't looked at the docs lately, or followed this conversation,
> but :4 was changed to :4.1
>
>
> Richard Freeman wrote:
>
>>
>> Are you using a package manager that supports EAPI 2?  I suspect that this is only supported by portage v2.2 or newer versions of paludis - and the unstable kde ebuilds use EAPI 2 so they would be masked by older versions of either package manager.
>>
>
> I was under the impression, especially based on the documentation, that the latest version of portage and associated tools supported that.  I'm using portage 2.1.4.5 and based on what I've read, this should be fine.
>
>
>
> --
> Frustra laborant quotquot se calculationibus fatigant pro inventione quadraturae circuli
>
> Mark Haney
> Sr. Systems Administrator
> ERC Broadband
> (828) 350-2415
>
> Call (866) ERC-7110 for after hours support
>
> Barry Schwartz wrote:
>>
>> Mark Haney <mhaney@ercbroadband.org> skribis:
>>>
>>> I've keyworded the KDE:4 packages (per the documentation) and I still do not see any KDE4.1.2 packages listed in emerge -upD world.
>>
>> I haven't looked at the docs lately, or followed this conversation,
>> but :4 was changed to :4.1
>>
>>
>
> That may be true, but in the documentation, there's no mention of what to unmask.  There's mention of what to keyword, but not unmask.  I've tried everything I can think of to unmask the files, and nothing has worked.
>
>
>
> --
> Frustra laborant quotquot se calculationibus fatigant pro inventione quadraturae circuli
>
> Mark Haney
> Sr. Systems Administrator
> ERC Broadband
> (828) 350-2415
>
> Call (866) ERC-7110 for after hours support
>
> Mark Haney wrote:
>>
>> Richard Freeman wrote:
>>
>
>>
>> I was under the impression, especially based on the documentation, that the latest version of portage and associated tools supported that.  I'm using portage 2.1.4.5 and based on what I've read, this should be fine.
>>
>>
>>
>
> You know, that might actually be my problem, somehow portage got downgraded here to 2.1.4.5 instead of 2.2.0_rc11 that I KNOW was on their before.
>
> So, I'm throwing 2.2.0_rc13 on here and we'll see how it goes from there.
>
>
>
> --
> Frustra laborant quotquot se calculationibus fatigant pro inventione quadraturae circuli
>
> Mark Haney
> Sr. Systems Administrator
> ERC Broadband
> (828) 350-2415
>
> Call (866) ERC-7110 for after hours support
>
> Mark Haney wrote:
>>
>> You know, that might actually be my problem, somehow portage got downgraded here to 2.1.4.5 instead of 2.2.0_rc11 that I KNOW was on their before.
>>
>> So, I'm throwing 2.2.0_rc13 on here and we'll see how it goes from there.
>>
>>
>>
>
>
> Yep, that did it. I can't believe I didn't catch that earlier. I was /certain/ portage was the right version.  Oh well.
>
> Thanks for all the help.
>
>
> --
> Frustra laborant quotquot se calculationibus fatigant pro inventione quadraturae circuli
>
> Mark Haney
> Sr. Systems Administrator
> ERC Broadband
> (828) 350-2415
>
> Call (866) ERC-7110 for after hours support
>
> Well, I've got kdebase installed (and I must say the new sets are awesome. I love it.) but I'm stumped on a problem.
>
> Instead of the KDE4.1 greeter, I'm getting the generic X Windows greeter login screen. I've checked /etc/conf.d/xdm and it says 'DISPLAYMANAGER=kde-4.1', and I've changed /etc/rc.conf to be kde-4.1, but still I get the X login.
>
> What am I missing?
>
>
>
> --
> Frustra laborant quotquot se calculationibus fatigant pro inventione quadraturae circuli
>
> Mark Haney
> Sr. Systems Administrator
> ERC Broadband
> (828) 350-2415
>
> Call (866) ERC-7110 for after hours support
>
> Well, I've got kdebase installed (and I must say the new sets are
> awesome. I love it.) but I'm stumped on a problem.
>
> Instead of the KDE4.1 greeter, I'm getting the generic X Windows greeter
> login screen. I've checked /etc/conf.d/xdm and it says
> 'DISPLAYMANAGER=kde-4.1', and I've changed /etc/rc.conf to be kde-4.1,
> but still I get the X login.
>
> What am I missing?
>
>
> One other thing, when I logged back in to KDE4, I lost all my desktop settings.  Is this supposed to happen?  I've set /etc/make.conf for 'kdeprefix' so I thought I would keep most of my desktop customizations.  They weren't real complex changes, just setting up a quick link on the task bar for Konsole and such.
>
>
>
>
> --
> Frustra laborant quotquot se calculationibus fatigant pro inventione
> quadraturae circuli
>
> Mark Haney
> Sr. Systems Administrator
> ERC Broadband
> (828) 350-2415
>
> Call (866) ERC-7110 for after hours support
>
>
> 2008/11/4 Mark Haney <mhaney@ercbroadband.org>:
>> Well, I've got kdebase installed (and I must say the new sets are
>> awesome. I love it.) but I'm stumped on a problem.
>>
>> Instead of the KDE4.1 greeter, I'm getting the generic X Windows greeter
>> login screen. I've checked /etc/conf.d/xdm and it says
>> 'DISPLAYMANAGER=kde-4.1', and I've changed /etc/rc.conf to be kde-4.1,
>> but still I get the X login.
>>
>> What am I missing?
>>
>>
>> One other thing, when I logged back in to KDE4, I lost all my desktop
>> settings.  Is this supposed to happen?  I've set /etc/make.conf for
>> 'kdeprefix' so I thought I would keep most of my desktop customizations.
>>  They weren't real complex changes, just setting up a quick link on the task
>> bar for Konsole and such.
>>
> usually that stuff isn't necessary. the kdebase-startkde package
> installs the right scripts. so that you don't need kde-4.1 as
> displaymanager. try using just kdm or kde instead of kde-4.1. also
> having a look inside the qlist kdebase-startkde files might be of help
> on how to set right the displaymanager.
>
> --
> dott. ing. beso
>
> Hi Mark,
>
> Am Dienstag, 4. November 2008 14:16:25 schrieb Mark Haney:
>> Well, I've got kdebase installed (and I must say the new sets are
>> awesome. I love it.) but I'm stumped on a problem.
>>
>> Instead of the KDE4.1 greeter, I'm getting the generic X Windows greeter
>> login screen. I've checked /etc/conf.d/xdm and it says
>> 'DISPLAYMANAGER=kde-4.1', and I've changed /etc/rc.conf to be kde-4.1,
>> but still I get the X login.
>>
>> What am I missing?
>
> A few days ago I had the same problem. Then I changed the entries in both
> rc.conf and conf.d/xdm to "kdm" without any extension, and now it works.
>
> Maybe the "4.1" is only functional if one sets the kdeprefix useflag.
>
> HTH.
>
> Have a nice day.
> Till
>
> Till Schwalbe (Gentoo) wrote:
>>
>> Hi Mark,
>>
>> Am Dienstag, 4. November 2008 14:16:25 schrieb Mark Haney:
>>>
>>> Well, I've got kdebase installed (and I must say the new sets are
>>> awesome. I love it.) but I'm stumped on a problem.
>>>
>>> Instead of the KDE4.1 greeter, I'm getting the generic X Windows greeter
>>> login screen. I've checked /etc/conf.d/xdm and it says
>>> 'DISPLAYMANAGER=kde-4.1', and I've changed /etc/rc.conf to be kde-4.1,
>>> but still I get the X login.
>>>
>>> What am I missing?
>>
>> A few days ago I had the same problem. Then I changed the entries in both rc.conf and conf.d/xdm to "kdm" without any extension, and now it works.
>>
>> Maybe the "4.1" is only functional if one sets the kdeprefix useflag.
>>
>> HTH.
>>
>> Have a nice day.
>> Till
>>
>
> Well, maybe, but I can say it doesn't work in this case, as I use the kdeprefix flag.
>
>
>
> --
> Frustra laborant quotquot se calculationibus fatigant pro inventione quadraturae circuli
>
> Mark Haney
> Sr. Systems Administrator
> ERC Broadband
> (828) 350-2415
>
> Call (866) ERC-7110 for after hours support
>
> Beso wrote:
>
>>>
>> usually that stuff isn't necessary. the kdebase-startkde package
>> installs the right scripts. so that you don't need kde-4.1 as
>> displaymanager. try using just kdm or kde instead of kde-4.1. also
>> having a look inside the qlist kdebase-startkde files might be of help
>> on how to set right the displaymanager.
>>
>
> Well, I took a look with qlist and this is what's in there:
>
> octavian kdebase-startkde-4.1.2-r1 # qlist kdebase-startkde
> /usr/kde/3.5/bin/startkde
> /usr/kde/3.5/env/agent-startup.sh
> /usr/kde/3.5/env/xdg.sh
> /usr/kde/3.5/shutdown/agent-shutdown.sh
> /usr/share/xsessions/kde-3.5.desktop
> /etc/X11/Sessions/kde-3.5
> /usr/share/doc/kde/kdebase-startkde-4.1.2-r1/README.bz2
> /usr/share/xsessions/KDE-4.desktop
> /usr/bin/startkde
> /usr/bin/safestartkde
> /etc/kde/startup/agent-startup.sh
> /etc/kde/startup/xdg.sh
> /etc/kde/shutdown/agent-shutdown.sh
> /etc/X11/Sessions/kde-4.1
>
>
> So, based on this, I don't see a KDM listed, but I do see a kde-4.1 in /etc/X11/Sessions/
>
> Still not sure where this leaves me though.
>
>
> --
> Frustra laborant quotquot se calculationibus fatigant pro inventione quadraturae circuli
>
> Mark Haney
> Sr. Systems Administrator
> ERC Broadband
> (828) 350-2415
>
> Call (866) ERC-7110 for after hours support
>
> 2008/11/4 Mark Haney <mhaney@ercbroadband.org>:
>> Beso wrote:
>>
>>>>
>>> usually that stuff isn't necessary. the kdebase-startkde package
>>> installs the right scripts. so that you don't need kde-4.1 as
>>> displaymanager. try using just kdm or kde instead of kde-4.1. also
>>> having a look inside the qlist kdebase-startkde files might be of help
>>> on how to set right the displaymanager.
>>>
>>
>> Well, I took a look with qlist and this is what's in there:
>>
>> octavian kdebase-startkde-4.1.2-r1 # qlist kdebase-startkde
>> /usr/kde/3.5/bin/startkde
>> /usr/kde/3.5/env/agent-startup.sh
>> /usr/kde/3.5/env/xdg.sh
>> /usr/kde/3.5/shutdown/agent-shutdown.sh
>> /usr/share/xsessions/kde-3.5.desktop
>> /etc/X11/Sessions/kde-3.5
>> /usr/share/doc/kde/kdebase-startkde-4.1.2-r1/README.bz2
>> /usr/share/xsessions/KDE-4.desktop
>> /usr/bin/startkde
>> /usr/bin/safestartkde
>> /etc/kde/startup/agent-startup.sh
>> /etc/kde/startup/xdg.sh
>> /etc/kde/shutdown/agent-shutdown.sh
>> /etc/X11/Sessions/kde-4.1
>>
>>
>> So, based on this, I don't see a KDM listed, but I do see a kde-4.1 in
>> /etc/X11/Sessions/
>>
>> Still not sure where this leaves me though.
>>
>>
>> --
>> Frustra laborant quotquot se calculationibus fatigant pro inventione
>> quadraturae circuli
>>
>> Mark Haney
>> Sr. Systems Administrator
>> ERC Broadband
>> (828) 350-2415
>>
>> Call (866) ERC-7110 for after hours support
>>
>>
>
> as displaymanager i have just 4.0 (i should correct it to the newer
> one but it seems that for me it automatically detects changes).
> usually this shouldn't be necessary as the new /etc/init.d/xdm file
> should already point to the right location (i have different voices
> for kde3.5 kde4 and gnome that go and see the kdm in the {MY_KDE}
> directory under /usr/kde/. so if you have a look at that the
> DISPLAYMANAGER should point just to the right dir. if you have
> /usr/kde/4.1 point it to 4.1. also you should remember to install the
> kdebase-startkde-4.1.2 package or you won't be able to select that
> session.
>
> --
> dott. ing. beso
>
> Beso <givemesugarr@gmail.com> posted
> d257c3560811041417h16cfc3bby1eed7cb0e4b002ef@mail.gmail.com, excerpted
> below, on  Tue, 04 Nov 2008 22:17:09 +0000:
>
>>> So, based on this, I don't see a KDM listed, but I do see a kde-4.1 in
>>> /etc/X11/Sessions/
>
> FWIW, I don't use a *dm at all.  I boot to a virtual terminal in text
> mode, login there, and start X/KDE from there.  The /etc/X11/Sessions/*
> entries are for doing that.  You set and export XSESSION=<name>, where
> <name> is the name of one of those files, run startx, and it should do
> just that (start X), with the appropriate environment based on whichever
> one you set/exported, logged in as the user you ran startx as.  Note that
> formerly the XSESSION variable was set system-wide in some rc file, IDR
> which but something like /etc/conf.d/rc or some such, but at least with
> baselayout-2 and openrc, that's no longer the case.  Individual logins
> could always overrule it; now they set it, period, in their bashrc or
> individual scripts they create or whatever.
>
> Of course the KDE X11/Sessions files don't do much, only call startkde
> (of the appropriate version) at the appropriate time as X starts.  It's
> the startkde scripts that do the real work.
>
> But since I've customized the locations of a number of files, due to
> running /tmp on tmpfs and /var/tmp as a symlink pointed at it, plus
> customized the menu and etc for both kde3 and kde4, I have customized KDE
> start scripts as well.  These set various critical variables to point
> stuff at my customized locations, do a few more symlinks beyond what
> startkde does to keep the kde3 and kde4 user configs from stepping on
> each other, etc.
>
> But the point is, no dm is necessary.  KDE (or other environments as
> merged) can be started from the console login, provided (1) XSESSION is
> set correctly, and (2) the appropriate start scripts, for kde, the
> startkde package, is merged.  I have both the 3.5.10-r4 and 4.1.2-r1
> versions of kdebase-startkde merged, and can start either one from my
> virtual terminal login.
>
>> as displaymanager i have just 4.0 (i should correct it to the newer one
>> but it seems that for me it automatically detects changes). usually this
>> shouldn't be necessary as the new /etc/init.d/xdm file should already
>> point to the right location (i have different voices for kde3.5 kde4 and
>> gnome that go and see the kdm in the {MY_KDE} directory under /usr/kde/.
>> so if you have a look at that the DISPLAYMANAGER should point just to
>> the right dir. if you have /usr/kde/4.1 point it to 4.1. also you should
>> remember to install the kdebase-startkde-4.1.2 package or you won't be
>> able to select that session.
>
> Now, if you are running a display manager, with a graphical login, then
> the above applies.  However, it's not necessary, and I long ago (2003-
> ish, Mandrake 8.x) quit doing so, after Mandrake broke their DM login in
> whatever cooker version I was running at the time.  IIRC I had already
> been running KDE from text mode part of the time (having decided before
> that that I preferred KDE to GNOME or whatever), but after that, I got in
> the habit of doing it all the time, and I've never used whatever *DM at
> all on Gentoo, and haven't even had one merged since Gentoo/KDE started
> the split packages thing.  I just prefer logging in in text mode, I
> guess, and running X/KDE like I would any other application, from there.
>
> --
> Duncan - List replies preferred.   No HTML msgs.
> "Every nonfree program has a lord, a master --
> and if you use the program, he is your master."  Richard Stallman
>
>
> Beso wrote:
>
>>
>> as displaymanager i have just 4.0 (i should correct it to the newer
>> one but it seems that for me it automatically detects changes).
>> usually this shouldn't be necessary as the new /etc/init.d/xdm file
>> should already point to the right location (i have different voices
>> for kde3.5 kde4 and gnome that go and see the kdm in the {MY_KDE}
>> directory under /usr/kde/. so if you have a look at that the
>> DISPLAYMANAGER should point just to the right dir. if you have
>> /usr/kde/4.1 point it to 4.1. also you should remember to install the
>> kdebase-startkde-4.1.2 package or you won't be able to select that
>> session.
>>
>
> Interesatingly enough the fix was rather simple.  In /etc/conf.d/xdm, I changed 'kde-4.1' to 'kdm' and voila, problem solved.
>
>
> --
> Frustra laborant quotquot se calculationibus fatigant pro inventione quadraturae circuli
>
> Mark Haney
> Sr. Systems Administrator
> ERC Broadband
> (828) 350-2415
>
> Call (866) ERC-7110 for after hours support
>
>

Re: [gentoo-amd64] unsubscribe

[Qian Qiao]

Jesus. If you think sending a message to the list with "unsubscribe"
as the subject line can unsubscribe you, at least send an empty
message...

More to the point, have you ever heard of reading message headers? The
header clearly states: List-Unsubscribe:
<mailto:gentoo-amd64+unsubscribe@lists.gentoo.org>

[gentoo-amd64] unsubscribe

[Vladimir Strycek]

*unsubscribe*

[gentoo-amd64] unsubscribe

[Daniele Salatti]

Re: [gentoo-amd64] unsubscribe

[Mark Haney]

Daniele Salatti wrote:

You know you tried this once and it didn't work.  So do you really 
believe trying it again will work?

(Couldn't help myself, some people need to read the directions.)



-- 
Libenter homines id quod volunt credunt -- Caius Julius Caesar


Mark Haney
Sr. Systems Administrator
ERC Broadband
(828) 350-2415

Call (866) ERC-7110 for after hours support

Re: [gentoo-amd64] unsubscribe

[felix]

On Fri, Aug 22, 2008 at 03:24:41PM +0200, Daniele Salatti wrote:
> 

Well, cat's got your tongue, I see, so I will step boldy into the
void.

Here's how to unsubscribe:

First, ask your Internet Provider to mail you an Unsubscribing Kit.
Then follow these directions.

The kit will most likely be the standard no-fault type. Depending on
requirements, System A and/or System B can be used. When operating
System A, depress lever and a plastic dalkron unsubscriber will be
dispensed through the slot immediately underneath. When you have
fastened the adhesive lip, attach connection marked by the large "X"
outlet hose. Twist the silver-coloured ring one inch below the
connection point until you feel it lock.

The kit is now ready for use. The Cin-Eliminator is activated by the
small switch on the lip.  When securing, twist the ring back to its
initial condition, so that the two orange lines meet.  Disconnect.
Place the dalkron unsubscriber in the vacuum receptacle to the rear.
Activate by pressing the blue button.

The controls for System B are located on the opposite side. The red
release switch places the Cin-Eliminator into position; it can be
adjusted manually up or down by pressing the blue manual release
button. The opening is self-adjusting. To secure after use, press the
green button, which simultaneously activates the evaporator and
returns the Cin-Eliminator to its storage position.

You may log off if the green exit light is on over the evaporator.  If
the red light is illuminated, one of the Cin-Eliminator requirements
has not been properly implemented. Press the "List Guy" call button on
the right of the evaporator. He will secure all facilities from his
control panel.

To use the Auto-Unsub, first undress and place all your clothes in the
clothes rack. Put on the velcro slippers located in the cabinet
immediately below. Enter the shower, taking the entire kit with
you. On the control panel to your upper right upon entering you will
see a "Shower seal" button. Press to activate. A green light will then
be illuminated immediately below. On the intensity knob, select the
desired setting. Now depress the Auto-Unsub activation lever. Bathe
normally.

The Auto-Unsub will automatically go off after three minutes unless
you activate the "Manual off" override switch by flipping it up. When
you are ready to leave, press the blue "Shower seal" release
button. The door will open and you may leave. Please remove the velcro
slippers and place them in their container.

If you prefer the ultrasonic log-off mode, press the indicated blue
button. When the twin panels open, pull forward by rings A & B. The
knob to the left, just below the blue light, has three settings, low,
medium or high. For normal use, the medium setting is suggested.

After these settings have been made, you can activate the device by
switching to the "ON" position the clearly marked red switch. If
during the unsubscribing operation you wish to change the settings,
place the "manual off" override switch in the "OFF" position. You may
now make the change and repeat the cycle. When the green exit light
goes on, you may log off and have lunch. Please close the door behind
you.


-- 
            ... _._. ._ ._. . _._. ._. ___ .__ ._. . .__. ._ .. ._.
     Felix Finch: scarecrow repairman & rocket surgeon / felix@crowfix.com
  GPG = E987 4493 C860 246C 3B1E  6477 7838 76E9 182E 8151 ITAR license #4933
I've found a solution to Fermat's Last Theorem but I see I've run out of room o

Re: [gentoo-amd64] unsubscribe

[Daniele Salatti]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Why don't you find a job? :)

felix@crowfix.com wrote:
> On Fri, Aug 22, 2008 at 03:24:41PM +0200, Daniele Salatti wrote:
> 
> Well, cat's got your tongue, I see, so I will step boldy into the
> void.
> 
> Here's how to unsubscribe:
> 
> First, ask your Internet Provider to mail you an Unsubscribing Kit.
> Then follow these directions.
> 
> The kit will most likely be the standard no-fault type. Depending on
> requirements, System A and/or System B can be used. When operating
> System A, depress lever and a plastic dalkron unsubscriber will be
> dispensed through the slot immediately underneath. When you have
> fastened the adhesive lip, attach connection marked by the large "X"
> outlet hose. Twist the silver-coloured ring one inch below the
> connection point until you feel it lock.
> 
> The kit is now ready for use. The Cin-Eliminator is activated by the
> small switch on the lip.  When securing, twist the ring back to its
> initial condition, so that the two orange lines meet.  Disconnect.
> Place the dalkron unsubscriber in the vacuum receptacle to the rear.
> Activate by pressing the blue button.
> 
> The controls for System B are located on the opposite side. The red
> release switch places the Cin-Eliminator into position; it can be
> adjusted manually up or down by pressing the blue manual release
> button. The opening is self-adjusting. To secure after use, press the
> green button, which simultaneously activates the evaporator and
> returns the Cin-Eliminator to its storage position.
> 
> You may log off if the green exit light is on over the evaporator.  If
> the red light is illuminated, one of the Cin-Eliminator requirements
> has not been properly implemented. Press the "List Guy" call button on
> the right of the evaporator. He will secure all facilities from his
> control panel.
> 
> To use the Auto-Unsub, first undress and place all your clothes in the
> clothes rack. Put on the velcro slippers located in the cabinet
> immediately below. Enter the shower, taking the entire kit with
> you. On the control panel to your upper right upon entering you will
> see a "Shower seal" button. Press to activate. A green light will then
> be illuminated immediately below. On the intensity knob, select the
> desired setting. Now depress the Auto-Unsub activation lever. Bathe
> normally.
> 
> The Auto-Unsub will automatically go off after three minutes unless
> you activate the "Manual off" override switch by flipping it up. When
> you are ready to leave, press the blue "Shower seal" release
> button. The door will open and you may leave. Please remove the velcro
> slippers and place them in their container.
> 
> If you prefer the ultrasonic log-off mode, press the indicated blue
> button. When the twin panels open, pull forward by rings A & B. The
> knob to the left, just below the blue light, has three settings, low,
> medium or high. For normal use, the medium setting is suggested.
> 
> After these settings have been made, you can activate the device by
> switching to the "ON" position the clearly marked red switch. If
> during the unsubscribing operation you wish to change the settings,
> place the "manual off" override switch in the "OFF" position. You may
> now make the change and repeat the cycle. When the green exit light
> goes on, you may log off and have lunch. Please close the door behind
> you.
> 
> 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFIrsr7oJaqqUDStNkRAh46AKCFQTJlK94VcGkxRXRJM+TDYoqi7ACgmzrs
GzZbFOjCGLmJh5uqb6yMytE=
=WBkZ
-----END PGP SIGNATURE-----

Re: [gentoo-amd64] unsubscribe

[Volker Armin Hemmann]

On Freitag, 22. August 2008, Daniele Salatti wrote:
> Why don't you find a job? :)

why don't you read and follow the unsubscribe instructions? They are in every 
header you got from this mailing list.

Also: don't toppost

and finally: his posting is the standard answer for people who send a wrong 
unsubscribe email.

[gentoo-amd64] unsubscribe

[Daniele Salatti]

unsubscribe

[gentoo-amd64] unsubscribe

[Andreas Radke]

Re: [gentoo-amd64] unsubscribe

[Qian Qiao]

On Sun, Aug 3, 2008 at 11:11 AM, Andreas Radke <a.radke@arcor.de> wrote:
>
>

Must... not... post... the... unsubscription... kit...

So... hard... to... resist...

-- 
There are 3 kinds of people in the world: those who can count, and
those who can't.
Calvin Trillin  - "Health food makes me sick."

Re: [gentoo-amd64] unsubscribe

[Michael Beasley]

[-- Attachment #1: Type: text/plain, Size: 268 bytes --]

On 16:51 Sun 03 Aug     , Qian Qiao wrote:
> On Sun, Aug 3, 2008 at 11:11 AM, Andreas Radke <a.radke@arcor.de> wrote:
> >
> >
> 
> Must... not... post... the... unsubscription... kit...
> 
> So... hard... to... resist...
> 
The force is strong with this one

[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]

[gentoo-amd64] unsubscribe

[Daniele Salatti]

[-- Attachment #1: Type: text/plain, Size: 204 bytes --]

-- 
Daniele Salatti
http://www.salatti.net

<a href="http://feeds.feedburner.com/~r/salattinet-en/~6/2"><img src="
http://feeds.feedburner.com/salattinet-en.2.gif" alt="Salatti.NET"
style="border:0"></a>

[-- Attachment #2: Type: text/html, Size: 456 bytes --]

[gentoo-amd64] Obligatory FF3 question.

[Mark Haney]

So, how's it working?  Anyone emerged it yet?

-- 
Libenter homines id quod volunt credunt -- Caius Julius Caesar


Mark Haney
Sr. Systems Administrator
ERC Broadband
(828) 350-2415

Call (866) ERC-7110 for after hours support
-- 
gentoo-amd64@lists.gentoo.org mailing list

Re: [gentoo-amd64] Obligatory FF3 question.

[M. Edward (Ed) Borasky]

Mark Haney wrote:
> So, how's it working?  Anyone emerged it yet?
> 
The binary is working ... the mirrors are hosed on the source version, 
though. They have the binary version and the checksums don't match.
-- 
gentoo-amd64@lists.gentoo.org mailing list

Re: [gentoo-amd64] Obligatory FF3 question.

[Mark Haney]

M. Edward (Ed) Borasky wrote:
> Mark Haney wrote:
>> So, how's it working?  Anyone emerged it yet?
>>
> The binary is working ... the mirrors are hosed on the source version, 
> though. They have the binary version and the checksums don't match.

I was able to get good source.  It built and it absolutely hauls the 
proverbial ass.


-- 
Libenter homines id quod volunt credunt -- Caius Julius Caesar


Mark Haney
Sr. Systems Administrator
ERC Broadband
(828) 350-2415

Call (866) ERC-7110 for after hours support
-- 
gentoo-amd64@lists.gentoo.org mailing list

Re: [gentoo-amd64] Obligatory FF3 question.

[Beso]

[-- Attachment #1: Type: text/plain, Size: 585 bytes --]

2008/6/18 Mark Haney <mhaney@ercbroadband.org>:

> M. Edward (Ed) Borasky wrote:
>
>> Mark Haney wrote:
>>
>>> So, how's it working?  Anyone emerged it yet?
>>>
>>>  The binary is working ... the mirrors are hosed on the source version,
>> though. They have the binary version and the checksums don't match.
>>
>
> I was able to get good source.  It built and it absolutely hauls the
> proverbial ass.
>

have you tried it with the new gnash plugin and the new icedtea (the free
openjdk java plugin that seems to be compatible at 90% with java6 ) on amd64
arch?



-- 
dott. ing. beso

[-- Attachment #2: Type: text/html, Size: 1208 bytes --]

Re: [gentoo-amd64] Obligatory FF3 question.

[Mark Haney]

Beso wrote:
> 2008/6/18 Mark Haney <mhaney@ercbroadband.org>:
> 
>> M. Edward (Ed) Borasky wrote:
>>
>>> Mark Haney wrote:
>>>
>>>> So, how's it working?  Anyone emerged it yet?
>>>>
>>>>  The binary is working ... the mirrors are hosed on the source version,
>>> though. They have the binary version and the checksums don't match.
>>>
>> I was able to get good source.  It built and it absolutely hauls the
>> proverbial ass.
>>
> 
> have you tried it with the new gnash plugin and the new icedtea (the free
> openjdk java plugin that seems to be compatible at 90% with java6 ) on amd64
> arch?
> 
> 
> 

No I haven't.  How is it?



-- 
Libenter homines id quod volunt credunt -- Caius Julius Caesar


Mark Haney
Sr. Systems Administrator
ERC Broadband
(828) 350-2415

Call (866) ERC-7110 for after hours support
-- 
gentoo-amd64@lists.gentoo.org mailing list

Re: [gentoo-amd64] Obligatory FF3 question.

[Beso]

[-- Attachment #1: Type: text/plain, Size: 1535 bytes --]

2008/6/18 Mark Haney <mhaney@ercbroadband.org>:

> Beso wrote:
>
>> 2008/6/18 Mark Haney <mhaney@ercbroadband.org>:
>>
>>  M. Edward (Ed) Borasky wrote:
>>>
>>>  Mark Haney wrote:
>>>>
>>>>  So, how's it working?  Anyone emerged it yet?
>>>>>
>>>>>  The binary is working ... the mirrors are hosed on the source version,
>>>>>
>>>> though. They have the binary version and the checksums don't match.
>>>>
>>>>  I was able to get good source.  It built and it absolutely hauls the
>>> proverbial ass.
>>>
>>>
>> have you tried it with the new gnash plugin and the new icedtea (the free
>> openjdk java plugin that seems to be compatible at 90% with java6 ) on
>> amd64
>> arch?
>>
>>
>>
>>
> No I haven't.  How is it?
>
>
well, icedtea, from the latest news in my possession has merged with openjdk
ad java plugin and it supports nearly 90% of java around (this means that
there's no need for a 32bit wrapper for java with firefox).
gnash is now fully compatible with flash v7 and has about 50% of flash 8 and
9 serie. now with the opening of the flash format specifications gnash
should progress much faster than it was before. for example i've read that
with firefox 2 with gnash and java youtube (usually a quite bad site for
flash players and which has also some java code included, for my knowledge)
is playing well (more than 85% of videos work well and the remnants just
need to use the gnash controls to work).
but as i've said, i haven't tried it yet so i don't know if these assertions
are reallly true.


-- 
dott. ing. beso

[-- Attachment #2: Type: text/html, Size: 2598 bytes --]

Re: [gentoo-amd64] Obligatory FF3 question.

[Mark Haney]

Beso wrote:
> 2008/6/18 Mark Haney <mhaney@ercbroadband.org>:
> 
>> Beso wrote:
>>
>>> 2008/6/18 Mark Haney <mhaney@ercbroadband.org>:
>>>
>>>  M. Edward (Ed) Borasky wrote:
>>>>  Mark Haney wrote:
>>>>>  So, how's it working?  Anyone emerged it yet?
>>>>>>  The binary is working ... the mirrors are hosed on the source version,
>>>>>>
>>>>> though. They have the binary version and the checksums don't match.
>>>>>
>>>>>  I was able to get good source.  It built and it absolutely hauls the
>>>> proverbial ass.
>>>>
>>>>
>>> have you tried it with the new gnash plugin and the new icedtea (the free
>>> openjdk java plugin that seems to be compatible at 90% with java6 ) on
>>> amd64
>>> arch?
>>>
>>>
>>>
>>>
>> No I haven't.  How is it?
>>
>>
> well, icedtea, from the latest news in my possession has merged with openjdk
> ad java plugin and it supports nearly 90% of java around (this means that
> there's no need for a 32bit wrapper for java with firefox).
> gnash is now fully compatible with flash v7 and has about 50% of flash 8 and
> 9 serie. now with the opening of the flash format specifications gnash
> should progress much faster than it was before. for example i've read that
> with firefox 2 with gnash and java youtube (usually a quite bad site for
> flash players and which has also some java code included, for my knowledge)
> is playing well (more than 85% of videos work well and the remnants just
> need to use the gnash controls to work).
> but as i've said, i haven't tried it yet so i don't know if these assertions
> are reallly true.
> 
> 


Well, I was going to try icedtea just to see how it worked, and I wanted 
to not have to spend a lot of time installing/configuring. There's a 
HOWTO page for icedtea, but the libre_java_overlay mentioned isn't there 
now.  Is there another way to automate the install?


-- 
Libenter homines id quod volunt credunt -- Caius Julius Caesar


Mark Haney
Sr. Systems Administrator
ERC Broadband
(828) 350-2415

Call (866) ERC-7110 for after hours support
-- 
gentoo-amd64@lists.gentoo.org mailing list

Re: [gentoo-amd64] Obligatory FF3 question.

[anorexicsumo]

On 6/19/08, Mark Haney <mhaney@ercbroadband.org> wrote:
> Well, I was going to try icedtea just to see how it worked, and I wanted to
> not have to spend a lot of time installing/configuring. There's a HOWTO page
> for icedtea, but the libre_java_overlay mentioned isn't there now.  Is there
> another way to automate the install?
>

icedtea is in java-overlay now.  I haven't had a chance to test it
yet, but icedtea-6.1.2 builds for me.

Does anyone know why cups is pulled as well?

-- 
aim: cyst23
email: anorexicsumo@gmail.com

"We can categorically state that we have not released man-eating
badgers into the area."  - UK military spokesman Major Mike Shearer
-- 
gentoo-amd64@lists.gentoo.org mailing list

[gentoo-amd64] UNSUBSCRIBE

[Nicolas Merline]

UNSUBSCRIBE

Yes, let the instructions begin.

[gentoo-amd64] unsubscribe

[Matthias Zirnstein]

-- 
gentoo-amd64@gentoo.org mailing list

[gentoo-amd64] unsubscribe

[Tim Ames]

unsubscribe

-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] unsubscribe

[Qian Qiao]

On Nov 11, 2007 7:12 PM, Tim Ames <lls@bigsurdigital.org> wrote:
> unsubscribe

Must... resist... the... temptation... to... post... the...
unsubscribe... kit...

This... is... killing... me...
-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] unsubscribe

[felix]

On Sun, Nov 11, 2007 at 07:43:22PM +0000, Qian Qiao wrote:
> On Nov 11, 2007 7:12 PM, Tim Ames <lls@bigsurdigital.org> wrote:
> > unsubscribe
> 
> Must... resist... the... temptation... to... post... the...
> unsubscribe... kit...
> 
> This... is... killing... me...

OK, I'll take pity on both of you.

Here's how to unsubscribe:

First, ask your Internet Provider to mail you an Unsubscribing Kit.
Then follow these directions.

The kit will most likely be the standard no-fault type. Depending on
requirements, System A and/or System B can be used. When operating
System A, depress lever and a plastic dalkron unsubscriber will be
dispensed through the slot immediately underneath. When you have
fastened the adhesive lip, attach connection marked by the large "X"
outlet hose. Twist the silver-coloured ring one inch below the
connection point until you feel it lock.

The kit is now ready for use. The Cin-Eliminator is activated by the
small switch on the lip.  When securing, twist the ring back to its
initial condition, so that the two orange lines meet.  Disconnect.
Place the dalkron unsubscriber in the vacuum receptacle to the rear.
Activate by pressing the blue button.

The controls for System B are located on the opposite side. The red
release switch places the Cin-Eliminator into position; it can be
adjusted manually up or down by pressing the blue manual release
button. The opening is self-adjusting. To secure after use, press the
green button, which simultaneously activates the evaporator and
returns the Cin-Eliminator to its storage position.

You may log off if the green exit light is on over the evaporator.  If
the red light is illuminated, one of the Cin-Eliminator requirements
has not been properly implemented. Press the "List Guy" call button on
the right of the evaporator. He will secure all facilities from his
control panel.

To use the Auto-Unsub, first undress and place all your clothes in the
clothes rack. Put on the velcro slippers located in the cabinet
immediately below. Enter the shower, taking the entire kit with
you. On the control panel to your upper right upon entering you will
see a "Shower seal" button. Press to activate. A green light will then
be illuminated immediately below. On the intensity knob, select the
desired setting. Now depress the Auto-Unsub activation lever. Bathe
normally.

The Auto-Unsub will automatically go off after three minutes unless
you activate the "Manual off" override switch by flipping it up. When
you are ready to leave, press the blue "Shower seal" release
button. The door will open and you may leave. Please remove the velcro
slippers and place them in their container.

If you prefer the ultrasonic log-off mode, press the indicated blue
button. When the twin panels open, pull forward by rings A & B. The
knob to the left, just below the blue light, has three settings, low,
medium or high. For normal use, the medium setting is suggested.

After these settings have been made, you can activate the device by
switching to the "ON" position the clearly marked red switch. If
during the unsubscribing operation you wish to change the settings,
place the "manual off" override switch in the "OFF" position. You may
now make the change and repeat the cycle. When the green exit light
goes on, you may log off and have lunch. Please close the door behind
you.


-- 
            ... _._. ._ ._. . _._. ._. ___ .__ ._. . .__. ._ .. ._.
     Felix Finch: scarecrow repairman & rocket surgeon / felix@crowfix.com
  GPG = E987 4493 C860 246C 3B1E  6477 7838 76E9 182E 8151 ITAR license #4933
I've found a solution to Fermat's Last Theorem but I see I've run out of room o
-- 
gentoo-amd64@gentoo.org mailing list

[gentoo-amd64] emerge --sync failed

[Paul Stear]

Hi all,
I'm sorry if this has been covered but I have had trouble with my mail.
I use the command eix-sync && emerge -auvtDN world && prelink -aqR to 
update my system. However, since Friday I am getting the following 
output:-
* Removing old portage-cache in /var/cache/edb/dep ...               {ok ]
 * Running emerge --sync ...
 * Problems running time emerge --sync                             [ !! ]
 * emerge --sync failed

Has anybody any ideas as to what is causing this and how to solve it?
Thanks
Paul
-- 
This message has been sent using kmail with gentoo linux
-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] emerge --sync failed

[Kenneth Prugh]

[-- Attachment #1: Type: text/plain, Size: 772 bytes --]

On Sat, 27 Oct 2007 14:43:03 +0100
Paul Stear <gentoo@appjaws.plus.com> wrote:

> Hi all,
> I'm sorry if this has been covered but I have had trouble with my
> mail. I use the command eix-sync && emerge -auvtDN world && prelink
> -aqR to update my system. However, since Friday I am getting the
> following output:-
> * Removing old portage-cache in /var/cache/edb/dep ...
> {ok ]
>  * Running emerge --sync ...
>  * Problems running time emerge --sync
> [ !! ]
>  * emerge --sync failed
> 
> Has anybody any ideas as to what is causing this and how to solve it?
> Thanks
> Paul

Not sure, but does `emerge --sync` actually work? That would probably
give a more detailed error than eix does.

-- 
Kenneth Prugh - Ken69267
Gentoo AMD64 Arch Tester

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-amd64] emerge --sync failed

[Paul Stear]

On Saturday 27 October 2007, Kenneth Prugh wrote:
> On Sat, 27 Oct 2007 14:43:03 +0100
>
> Paul Stear <gentoo@appjaws.plus.com> wrote:
> > Hi all,
> > I'm sorry if this has been covered but I have had trouble with my
> > mail. I use the command eix-sync && emerge -auvtDN world && prelink
> > -aqR to update my system. However, since Friday I am getting the
> > following output:-
> > * Removing old portage-cache in /var/cache/edb/dep ...
> > {ok ]
> >  * Running emerge --sync ...
> >  * Problems running time emerge --sync
> > [ !! ]
> >  * emerge --sync failed
> >
> > Has anybody any ideas as to what is causing this and how to solve it?
> > Thanks
> > Paul
>
> Not sure, but does `emerge --sync` actually work? That would probably
> give a more detailed error than eix does.

Hi, this is the error for emerge --sync:-
>>> Starting retry 2 of 3 with rsync://64.127.121.98/gentoo-portage
>>> Checking server timestamp ...
timed out
rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at rsync.c(244) 
[receiver=2.6.9]
>>> Retrying...


>>> Starting retry 3 of 3 with rsync://140.211.166.165/gentoo-portage
>>> Checking server timestamp ...
timed out
rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at rsync.c(244) 
[receiver=2.6.9]

So it appears a time out problem. What should I do now?
Thanks
Paul
-- 
This message has been sent using kmail with gentoo linux
-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] emerge --sync failed

[Beso]

[-- Attachment #1: Type: text/plain, Size: 2363 bytes --]

probably the rsync has changed ip. try one of this servers:
sync = rsync://rsync.gentoo.org/gentoo-portage
#sync = rsync://rsync3.it.gentoo.org/gentoo-sources
#sync = http://www.die.unipd.it/pub/Linux/distributions/gentoo-sources/
#sync = http://mirror.ing.unibo.it/gentoo/
the first is the official one, the others should be mirrors. a full list of
rsync mirrors can be found somewhere on the gentoo site. just search for it.
the problem with your method is that you don't pass through a dns server
asking directly for an ip address and this could not work anymore when the
site you're trying has changed ip. you'd have to get again the ip. if you
want to use the ip address try searching the name with a ping or traceroute
or in some dns site like in the opendns cache site.

2007/10/27, Paul Stear <gentoo@appjaws.plus.com>:
>
> On Saturday 27 October 2007, Kenneth Prugh wrote:
> > On Sat, 27 Oct 2007 14:43:03 +0100
> >
> > Paul Stear <gentoo@appjaws.plus.com> wrote:
> > > Hi all,
> > > I'm sorry if this has been covered but I have had trouble with my
> > > mail. I use the command eix-sync && emerge -auvtDN world && prelink
> > > -aqR to update my system. However, since Friday I am getting the
> > > following output:-
> > > * Removing old portage-cache in /var/cache/edb/dep ...
> > > {ok ]
> > >  * Running emerge --sync ...
> > >  * Problems running time emerge --sync
> > > [ !! ]
> > >  * emerge --sync failed
> > >
> > > Has anybody any ideas as to what is causing this and how to solve it?
> > > Thanks
> > > Paul
> >
> > Not sure, but does `emerge --sync` actually work? That would probably
> > give a more detailed error than eix does.
>
> Hi, this is the error for emerge --sync:-
> >>> Starting retry 2 of 3 with rsync://64.127.121.98/gentoo-portage
> >>> Checking server timestamp ...
> timed out
> rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at rsync.c(244)
> [receiver=2.6.9]
> >>> Retrying...
>
>
> >>> Starting retry 3 of 3 with rsync://140.211.166.165/gentoo-portage
> >>> Checking server timestamp ...
> timed out
> rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at rsync.c(244)
> [receiver=2.6.9]
>
> So it appears a time out problem. What should I do now?
> Thanks
> Paul
> --
> This message has been sent using kmail with gentoo linux
> --
> gentoo-amd64@gentoo.org mailing list
>
>


-- 
dott. ing. beso

[-- Attachment #2: Type: text/html, Size: 3141 bytes --]

[gentoo-amd64] unsubscribe

[Kevin Carpenter]

unsubscribe

Re: [gentoo-amd64] unsubscribe

[Volker Armin Hemmann]

On Monday 13 December 2010 13:52:03 Kevin Carpenter wrote:
> unsubscribe

nice try Kev ;)

Re: [gentoo-amd64] unsubscribe

[Dale]

Kevin Carpenter wrote:
> unsubscribe
>
>
http://www.gentoo.org/main/en/lists.xml

Dale

:-)  :-)

[gentoo-amd64] unsubscribe

[Fraser Thomson]

-- 
gentoo-amd64@gentoo.org mailing list

[gentoo-amd64] unsubscribe

[Matthias Zirnstein]

unsubscribe
-- 
gentoo-amd64@gentoo.org mailing list

[gentoo-amd64] UNSUBSCRIBE

[NiQoZ]

-- 
NiQoZ

*************************************
**                                 **
*         ^  NiQoZ WeB  ^           *
*                                   *
*     HISTORIQUES, TUTORIELS et     *
*      DOCUMENTATIONS pour les      *
*  administrateurs et utilisateurs  *
*        de la distribution         *
*         GENTOO GNU/Linux          *
*                                   *
*  Cliquez http://www.niqozweb.net  *
**                                 **
*************************************


-- 
NiQoZ

*************************************
**                                 **
*         ^  NiQoZ WeB  ^           *
*                                   *
*     HISTORIQUES, TUTORIELS et     *
*      DOCUMENTATIONS pour les      *
*  administrateurs et utilisateurs  *
*        de la distribution         *
*         GENTOO GNU/Linux          *
*                                   *
*  Cliquez http://www.niqozweb.net  *
**                                 **
*************************************


-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] UNSUBSCRIBE

[Mark Haney]

NiQoZ wrote:
>
>
>   
Doesn't ANYONE read the unsubscribe options anymore?


-- 
Mark Haney
Sr. Systems Administrator	
ERC Broadband


-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] UNSUBSCRIBE

[me]

Did they ever? 

- Mac


On Monday 21 May 2007 10:09 am, Mark Haney wrote:
> NiQoZ wrote:
>
>
>
> Doesn't ANYONE read the unsubscribe options anymore?
>
>
> --
> Mark Haney
> Sr. Systems Administrator
> ERC Broadband
-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] UNSUBSCRIBE

[Dustin J. Mitchell]

I missed my cue this time, sorry.

The instructions *are* fairly long -- maybe we should build an
eunsubscribe tool, or add a wiki page to explain how to read the
documentation?

---

Here's how to unsubscribe:

First, ask your Internet Provider to mail you an Unsubscribing Kit.
Then follow these directions.

The kit will most likely be the standard no-fault type. Depending on
requirements, System A and/or System B can be used. When operating
System A, depress lever and a plastic dalkron unsubscriber will be
dispensed through the slot immediately underneath. When you have
fastened the adhesive lip, attach connection marked by the large "X"
outlet hose. Twist the silver-coloured ring one inch below the
connection point until you feel it lock.

The kit is now ready for use. The Cin-Eliminator is activated by the
small switch on the lip.  When securing, twist the ring back to its
initial condition, so that the two orange lines meet.  Disconnect.
Place the dalkron unsubscriber in the vacuum receptacle to the rear.
Activate by pressing the blue button.

The controls for System B are located on the opposite side. The red
release switch places the Cin-Eliminator into position; it can be
adjusted manually up or down by pressing the blue manual release
button. The opening is self-adjusting. To secure after use, press the
green button, which simultaneously activates the evaporator and
returns the Cin-Eliminator to its storage position.

You may log off if the green exit light is on over the evaporator.  If
the red light is illuminated, one of the Cin-Eliminator requirements
has not been properly implemented. Press the "List Guy" call button on
the right of the evaporator. He will secure all facilities from his
control panel.

To use the Auto-Unsub, first undress and place all your clothes in the
clothes rack. Put on the velcro slippers located in the cabinet
immediately below. Enter the shower, taking the entire kit with
you. On the control panel to your upper right upon entering you will
see a "Shower seal" button. Press to activate. A green light will then
be illuminated immediately below. On the intensity knob, select the
desired setting. Now depress the Auto-Unsub activation lever. Bathe
normally.

The Auto-Unsub will automatically go off after three minutes unless
you activate the "Manual off" override switch by flipping it up. When
you are ready to leave, press the blue "Shower seal" release
button. The door will open and you may leave. Please remove the velcro
slippers and place them in their container.

If you prefer the ultrasonic log-off mode, press the indicated blue
button. When the twin panels open, pull forward by rings A & B. The
knob to the left, just below the blue light, has three settings, low,
medium or high. For normal use, the medium setting is suggested.

After these settings have been made, you can activate the device by
switching to the "ON" position the clearly marked red switch. If
during the unsubscribing operation you wish to change the settings,
place the "manual off" override switch in the "OFF" position. You may
now make the change and repeat the cycle. When the green exit light
goes on, you may log off and have lunch. Please close the door behind
you.

---

Dustin

On Mon, May 21, 2007 at 08:39:35PM -0400, me wrote:
> Did they ever? 
> 
> - Mac
> 
> 
> On Monday 21 May 2007 10:09 am, Mark Haney wrote:
> > NiQoZ wrote:
> >
> >
> >
> > Doesn't ANYONE read the unsubscribe options anymore?
> >
> >
> > --
> > Mark Haney
> > Sr. Systems Administrator
> > ERC Broadband
> -- 
> gentoo-amd64@gentoo.org mailing list
> 
> 
-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] UNSUBSCRIBE

[Isidore Ducasse]

[-- Attachment #1: Type: text/plain, Size: 375 bytes --]

2007/5/22, Dustin J. Mitchell <dustin@v.igoro.us>:
>
> I missed my cue this time, sorry.
>
> The instructions *are* fairly long -- maybe we should build an
> eunsubscribe tool, or add a wiki page to explain how to read the
> documentation?



The "eunsubscribe" tool idea seems funny _ quite gentooish. The wiki
documentation howto isn't a bad idea in my opinion, seriously.

[-- Attachment #2: Type: text/html, Size: 659 bytes --]

[gentoo-amd64] unsubscribe

[Axel Groetsch]

-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] unsubscribe

[dustin]

Here's how to unsubscribe:

First, ask your Internet Provider to mail you an Unsubscribing Kit.
Then follow these directions.

The kit will most likely be the standard no-fault type. Depending on
requirements, System A and/or System B can be used. When operating
System A, depress lever and a plastic dalkron unsubscriber will be
dispensed through the slot immediately underneath. When you have
fastened the adhesive lip, attach connection marked by the large "X"
outlet hose. Twist the silver-coloured ring one inch below the
connection point until you feel it lock.

The kit is now ready for use. The Cin-Eliminator is activated by the
small switch on the lip.  When securing, twist the ring back to its
initial condition, so that the two orange lines meet.  Disconnect.
Place the dalkron unsubscriber in the vacuum receptacle to the rear.
Activate by pressing the blue button.

The controls for System B are located on the opposite side. The red
release switch places the Cin-Eliminator into position; it can be
adjusted manually up or down by pressing the blue manual release
button. The opening is self-adjusting. To secure after use, press the
green button, which simultaneously activates the evaporator and
returns the Cin-Eliminator to its storage position.

You may log off if the green exit light is on over the evaporator.  If
the red light is illuminated, one of the Cin-Eliminator requirements
has not been properly implemented. Press the "List Guy" call button on
the right of the evaporator. He will secure all facilities from his
control panel.

To use the Auto-Unsub, first undress and place all your clothes in the
clothes rack. Put on the velcro slippers located in the cabinet
immediately below. Enter the shower, taking the entire kit with
you. On the control panel to your upper right upon entering you will
see a "Shower seal" button. Press to activate. A green light will then
be illuminated immediately below. On the intensity knob, select the
desired setting. Now depress the Auto-Unsub activation lever. Bathe
normally.

The Auto-Unsub will automatically go off after three minutes unless
you activate the "Manual off" override switch by flipping it up. When
you are ready to leave, press the blue "Shower seal" release
button. The door will open and you may leave. Please remove the velcro
slippers and place them in their container.

If you prefer the ultrasonic log-off mode, press the indicated blue
button. When the twin panels open, pull forward by rings A & B. The
knob to the left, just below the blue light, has three settings, low,
medium or high. For normal use, the medium setting is suggested.

After these settings have been made, you can activate the device by
switching to the "ON" position the clearly marked red switch. If
during the unsubscribing operation you wish to change the settings,
place the "manual off" override switch in the "OFF" position. You may
now make the change and repeat the cycle. When the green exit light
goes on, you may log off and have lunch. Please close the door behind
you.
-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] unsubscribe

[felix]

On Mon, May 14, 2007 at 11:05:15AM -0500, dustin@v.igoro.us wrote:
> Here's how to unsubscribe:

Better send it twice, once for each unsub request.  He'll need to get
two separate kits and heaven knows, you wouldn't want him using
instructions from another kit!

-- 
            ... _._. ._ ._. . _._. ._. ___ .__ ._. . .__. ._ .. ._.
     Felix Finch: scarecrow repairman & rocket surgeon / felix@crowfix.com
  GPG = E987 4493 C860 246C 3B1E  6477 7838 76E9 182E 8151 ITAR license #4933
I've found a solution to Fermat's Last Theorem but I see I've run out of room o
-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] unsubscribe

[dustin]

On Mon, May 14, 2007 at 09:44:35AM -0700, felix@crowfix.com wrote:
> On Mon, May 14, 2007 at 11:05:15AM -0500, dustin@v.igoro.us wrote:
> > Here's how to unsubscribe:
> 
> Better send it twice, once for each unsub request.  He'll need to get
> two separate kits and heaven knows, you wouldn't want him using
> instructions from another kit!

I sent him an extra one without copying the list.  At least *I* have som
netiquette.. ;)

Dustin
-- 
gentoo-amd64@gentoo.org mailing list

[gentoo-amd64] unsubscribe

[Axel Groetsch]

-- 
gentoo-amd64@gentoo.org mailing list

[gentoo-amd64] Tracking down dependencies - x11-proto/printproto x11-apps/xdpyinfo

[Daiajo Tibdixious]

I don't have a printer, and never expect to have one, so I try to
remove any print related packages,
and I'm currently targetting x11-proto/printproto.

This package is conditional on the "xprint" USE flag in
x11-base/xorg-server which is OFF in emerge --info.

I recenly installed 64 bit firefox (thought I'd give it another go,
not working so hot that that's another rant) which includes
www-client/mozilla-launcher which has a hard dependency on
x11-apps/xdpyinfo.

x11-apps/xdpyinfo has a hard dependency on x11-proto/printproto
despite the code being conditional on xprint via the config
HAVE_X11_EXTENSIONS_PRINT_H, which will always be
true since the ebuild pulls it in.

Now I think there is a bug in the x11-apps/xdpyinfo ebuild. I changed
xdpyinfo-1.0.1.ebuild
34c34
<       xprint? ( x11-proto/printproto )"
---
>       x11-proto/printproto"
# ebuild xdpyinfo-1.0.1.ebuild digest

and tested it
# xdpyinfo > ~/tmp/xdpyinfo-before
# emerge -aC x11-proto/printproto
# emerge -a1 x11-apps/xdpyinfo
# xdpyinfo > ~/tmp/xdpyinfo-after
# diff ~/tmp/xdpyinfo-before ~/tmp/xdpyinfo-after
54d53
<   print screen:    no

The compile was clean, the baseline/regression test (rudimentary) worked well.

So my question is: is this enough to submit as a bug/feature request?
I ask because I've submitted quite a few bugs and gotten unpolite
responses on occassion, left out obvious information, and generally
looked like the dumb user I'm tring not to be.
-- 
gentoo-amd64@gentoo.org mailing list

[gentoo-amd64] unsubscribe

[GizVee]

unsubscribe

-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] unsubscribe

[dustin]

Here's how to unsubscribe:

First, ask your Internet Provider to mail you an Unsubscribing Kit.
Then follow these directions.

The kit will most likely be the standard no-fault type. Depending on
requirements, System A and/or System B can be used. When operating
System A, depress lever and a plastic dalkron unsubscriber will be
dispensed through the slot immediately underneath. When you have
fastened the adhesive lip, attach connection marked by the large "X"
outlet hose. Twist the silver-coloured ring one inch below the
connection point until you feel it lock.

The kit is now ready for use. The Cin-Eliminator is activated by the
small switch on the lip.  When securing, twist the ring back to its
initial condition, so that the two orange lines meet.  Disconnect.
Place the dalkron unsubscriber in the vacuum receptacle to the rear.
Activate by pressing the blue button.

The controls for System B are located on the opposite side. The red
release switch places the Cin-Eliminator into position; it can be
adjusted manually up or down by pressing the blue manual release button.
The opening is self-adjusting. To secure after use, press the green
button, which simultaneously activates the evaporator and returns the
Cin-Eliminator to its storage position.

You may log off if the green exit light is on over the evaporator.  If
the red light is illuminated, one of the Cin-Eliminator requirements has
not been properly implemented. Press the "List Guy" call button on the
right of the evaporator. He will secure all facilities from his control
panel.

To use the Auto-Unsub, first undress and place all your clothes in the
clothes rack. Put on the velcro slippers located in the cabinet
immediately below. Enter the shower, taking the entire kit with you. On
the control panel to your upper right upon entering you will see a
"Shower seal" button. Press to activate. A green light will then be
illuminated immediately below. On the intensity knob, select the desired
setting. Now depress the Auto-Unsub activation lever. Bathe normally.

The Auto-Unsub will automatically go off after three minutes unless you
activate the "Manual off" override switch by flipping it up. When you
are ready to leave, press the blue "Shower seal" release button. The
door will open and you may leave. Please remove the velcro slippers and
place them in their container.

If you prefer the ultrasonic log-off mode, press the indicated blue
button. When the twin panels open, pull forward by rings A & B. The knob
to the left, just below the blue light, has three settings, low, medium
or high. For normal use, the medium setting is suggested.

After these settings have been made, you can activate the device by
switching to the "ON" position the clearly marked red switch. If during
the unsubscribing operation you wish to change the settings, place the
"manual off" override switch in the "OFF" position. You may now make the
change and repeat the cycle. When the green exit light goes on, you may
log off and have lunch. Please close the door behind you.
-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] unsubscribe

[Thomas Rösner]

dustin@v.igoro.us schrieb:
> Here's how to unsubscribe:
>   
[...]

It's getting funnier every single time.

Regards,
    Thomas
-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] unsubscribe

[Ryan Sims]

On 4/2/07, Thomas Rösner <Thomas.Roesner@digital-trauma.de> wrote:
> dustin@v.igoro.us schrieb:
> > Here's how to unsubscribe:
> >
> [...]
>
> It's getting funnier every single time.
>
> Regards,
>     Thomas

Maybe we should set up a rotation so we all get a turn at being snarky. ;)

-- 
Ryan W Sims
--
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] unsubscribe

[Guillermo A. Amaral]

[-- Attachment #1: Type: text/plain, Size: 533 bytes --]

On Monday 02 April 2007, dustin@v.igoro.us wrote:
> Here's how to unsubscribe:
>
> First, ask your Internet Provider to mail you an Unsubscribing Kit.
> Then follow these directions.
>
> [snip]
>

Bloody hell... so that's what got mailed to me by mistake...	
 
-- 
Guillermo A. Amaral, CSE
# Free & Open Source Advocate
& nick: guillermoamaral
@ blog: http://blog.guillermoamaral.com/
@ site: http://www.guillermoamaral.com/
$  irc: guillermoamaral@freenode
%  gpg: http://downloads.guillermoamaral.com/public.asc

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

[gentoo-amd64] unsubscribe

[Axel Grötsch]

unsubscribe
-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] unsubscribe

[Erik]

absolutely not.


On 1/11/07, Axel Grötsch <ml@omd26.de> wrote:
>
> unsubscribe
> --
> gentoo-amd64@gentoo.org mailing list
>
>


-- 
Erik

-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] unsubscribe

[Jean.Borsenberger]

[-- Attachment #1: Type: TEXT/PLAIN, Size: 577 bytes --]

 	Yes it seems realy impossible to unsubscribe, none of the methods
works (mail to list+..., mail to postmaster@, mail to abuse@).
 	The only way seems to destroy the list. Think of it.

Jean Borsenberger
tel: +33 (0)1 45 07 74 69
Observatoire de Paris Meudon
5 place Jules Janssen
92195 Meudon France

On Fri, 12 Jan 2007, Erik wrote:

> absolutely not.
>
>
> On 1/11/07, Axel Grötsch <ml@omd26.de> wrote:
>> 
>> unsubscribe
>> --
>> gentoo-amd64@gentoo.org mailing list
>> 
>> 
>
>
> -- 
> Erik
>
> -- 
> gentoo-amd64@gentoo.org mailing list
>
>

RE: [gentoo-amd64] unsubscribe

[David Pyke]

Have you tried setting fire to your computer?  That should stop you from
getting the mail. 

-----Original Message-----
From: Jean Borsenberger [mailto:jborsen@siolinh.obspm.fr] On Behalf Of
Jean.Borsenberger@obspm.fr
Sent: Friday, January 12, 2007 3:59 PM
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] unsubscribe

 	Yes it seems realy impossible to unsubscribe, none of the methods
works (mail to list+..., mail to postmaster@, mail to abuse@).
 	The only way seems to destroy the list. Think of it.

Jean Borsenberger
tel: +33 (0)1 45 07 74 69
Observatoire de Paris Meudon
5 place Jules Janssen
92195 Meudon France

On Fri, 12 Jan 2007, Erik wrote:

> absolutely not.
>
>
> On 1/11/07, Axel Grötsch <ml@omd26.de> wrote:
>> 
>> unsubscribe
>> --
>> gentoo-amd64@gentoo.org mailing list
>> 
>> 
>
>
> --
> Erik
>
> --
> gentoo-amd64@gentoo.org mailing list
>
>


-- 
gentoo-amd64@gentoo.org mailing list

RE: [gentoo-amd64] unsubscribe

[Jean.Borsenberger]

[-- Attachment #1: Type: TEXT/PLAIN, Size: 1287 bytes --]

 	installing gentoo-64 and upgrading it is sufficient to put it 
down, no use to set fire.

Jean Borsenberger
tel: +33 (0)1 45 07 74 69
Observatoire de Paris Meudon
5 place Jules Janssen
92195 Meudon France

On Fri, 12 Jan 2007, David Pyke wrote:

> Have you tried setting fire to your computer?  That should stop you from
> getting the mail.
>
> -----Original Message-----
> From: Jean Borsenberger [mailto:jborsen@siolinh.obspm.fr] On Behalf Of
> Jean.Borsenberger@obspm.fr
> Sent: Friday, January 12, 2007 3:59 PM
> To: gentoo-amd64@lists.gentoo.org
> Subject: Re: [gentoo-amd64] unsubscribe
>
> 	Yes it seems realy impossible to unsubscribe, none of the methods
> works (mail to list+..., mail to postmaster@, mail to abuse@).
> 	The only way seems to destroy the list. Think of it.
>
> Jean Borsenberger
> tel: +33 (0)1 45 07 74 69
> Observatoire de Paris Meudon
> 5 place Jules Janssen
> 92195 Meudon France
>
> On Fri, 12 Jan 2007, Erik wrote:
>
>> absolutely not.
>>
>>
>> On 1/11/07, Axel Grötsch <ml@omd26.de> wrote:
>>>
>>> unsubscribe
>>> --
>>> gentoo-amd64@gentoo.org mailing list
>>>
>>>
>>
>>
>> --
>> Erik
>>
>> --
>> gentoo-amd64@gentoo.org mailing list
>>
>>
>
>
> -- 
> gentoo-amd64@gentoo.org mailing list
>
>

Re: [gentoo-amd64] unsubscribe

[Simon Stelling]

Jean.Borsenberger@obspm.fr wrote:
>     installing gentoo-64 and upgrading it is sufficient to put it down, 
> no use to set fire.

I love black humor. Jokes aside, reading documentation usually saves a 
lot of nerves, both when upgrading and unsubscribing.

http://www.gentoo.org/main/en/lists.xml

-- 
Kind Regards,

Simon Stelling
Gentoo/AMD64 Developer
-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] unsubscribe

[felix]

On Fri, Jan 12, 2007 at 11:40:04PM +0200, Simon Stelling wrote:
> Jean.Borsenberger@obspm.fr wrote:
> >    installing gentoo-64 and upgrading it is sufficient to put it down, 
> >no use to set fire.
> 
> I love black humor. Jokes aside, reading documentation usually saves a 
> lot of nerves, both when upgrading and unsubscribing.

Ah, documentation you want, is it?

Here's how to unsubscribe:

First, ask your Internet Provider to mail you an Unsubscribing Kit.
Then follow these directions.

The kit will most likely be the standard no-fault type. Depending on
requirements, System A and/or System B can be used. When operating
System A, depress lever and a plastic dalkron unsubscriber will be
dispensed through the slot immediately underneath. When you have
fastened the adhesive lip, attach connection marked by the large "X"
outlet hose. Twist the silver-coloured ring one inch below the
connection point until you feel it lock.

The kit is now ready for use. The Cin-Eliminator is activated by the
small switch on the lip.  When securing, twist the ring back to its
initial condition, so that the two orange lines meet.  Disconnect.
Place the dalkron unsubscriber in the vacuum receptacle to the rear.
Activate by pressing the blue button.

The controls for System B are located on the opposite side. The red
release switch places the Cin-Eliminator into position; it can be
adjusted manually up or down by pressing the blue manual release
button. The opening is self-adjusting. To secure after use, press the
green button, which simultaneously activates the evaporator and
returns the Cin-Eliminator to its storage position.

You may log off if the green exit light is on over the evaporator.  If
the red light is illuminated, one of the Cin-Eliminator requirements
has not been properly implemented. Press the "List Guy" call button on
the right of the evaporator. He will secure all facilities from his
control panel.

To use the Auto-Unsub, first undress and place all your clothes in the
clothes rack. Put on the velcro slippers located in the cabinet
immediately below. Enter the shower, taking the entire kit with
you. On the control panel to your upper right upon entering you will
see a "Shower seal" button. Press to activate. A green light will then
be illuminated immediately below. On the intensity knob, select the
desired setting. Now depress the Auto-Unsub activation lever. Bathe
normally.

The Auto-Unsub will automatically go off after three minutes unless
you activate the "Manual off" override switch by flipping it up. When
you are ready to leave, press the blue "Shower seal" release
button. The door will open and you may leave. Please remove the velcro
slippers and place them in their container.

If you prefer the ultrasonic log-off mode, press the indicated blue
button. When the twin panels open, pull forward by rings A & B. The
knob to the left, just below the blue light, has three settings, low,
medium or high. For normal use, the medium setting is suggested.

After these settings have been made, you can activate the device by
switching to the "ON" position the clearly marked red switch. If
during the unsubscribing operation you wish to change the settings,
place the "manual off" override switch in the "OFF" position. You may
now make the change and repeat the cycle. When the green exit light
goes on, you may log off and have lunch. Please close the door behind
you.


-- 
            ... _._. ._ ._. . _._. ._. ___ .__ ._. . .__. ._ .. ._.
     Felix Finch: scarecrow repairman & rocket surgeon / felix@crowfix.com
  GPG = E987 4493 C860 246C 3B1E  6477 7838 76E9 182E 8151 ITAR license #4933
I've found a solution to Fermat's Last Theorem but I see I've run out of room o
-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] unsubscribe

[Nicolas Merline]

[-- Attachment #1: Type: text/plain, Size: 4028 bytes --]

roflmao. So the i write the check to I.C. Weiner right?

On 1/13/07, felix@crowfix.com <felix@crowfix.com> wrote:
>
> On Fri, Jan 12, 2007 at 11:40:04PM +0200, Simon Stelling wrote:
> > Jean.Borsenberger@obspm.fr wrote:
> > >    installing gentoo-64 and upgrading it is sufficient to put it down,
> > >no use to set fire.
> >
> > I love black humor. Jokes aside, reading documentation usually saves a
> > lot of nerves, both when upgrading and unsubscribing.
>
> Ah, documentation you want, is it?
>
> Here's how to unsubscribe:
>
> First, ask your Internet Provider to mail you an Unsubscribing Kit.
> Then follow these directions.
>
> The kit will most likely be the standard no-fault type. Depending on
> requirements, System A and/or System B can be used. When operating
> System A, depress lever and a plastic dalkron unsubscriber will be
> dispensed through the slot immediately underneath. When you have
> fastened the adhesive lip, attach connection marked by the large "X"
> outlet hose. Twist the silver-coloured ring one inch below the
> connection point until you feel it lock.
>
> The kit is now ready for use. The Cin-Eliminator is activated by the
> small switch on the lip.  When securing, twist the ring back to its
> initial condition, so that the two orange lines meet.  Disconnect.
> Place the dalkron unsubscriber in the vacuum receptacle to the rear.
> Activate by pressing the blue button.
>
> The controls for System B are located on the opposite side. The red
> release switch places the Cin-Eliminator into position; it can be
> adjusted manually up or down by pressing the blue manual release
> button. The opening is self-adjusting. To secure after use, press the
> green button, which simultaneously activates the evaporator and
> returns the Cin-Eliminator to its storage position.
>
> You may log off if the green exit light is on over the evaporator.  If
> the red light is illuminated, one of the Cin-Eliminator requirements
> has not been properly implemented. Press the "List Guy" call button on
> the right of the evaporator. He will secure all facilities from his
> control panel.
>
> To use the Auto-Unsub, first undress and place all your clothes in the
> clothes rack. Put on the velcro slippers located in the cabinet
> immediately below. Enter the shower, taking the entire kit with
> you. On the control panel to your upper right upon entering you will
> see a "Shower seal" button. Press to activate. A green light will then
> be illuminated immediately below. On the intensity knob, select the
> desired setting. Now depress the Auto-Unsub activation lever. Bathe
> normally.
>
> The Auto-Unsub will automatically go off after three minutes unless
> you activate the "Manual off" override switch by flipping it up. When
> you are ready to leave, press the blue "Shower seal" release
> button. The door will open and you may leave. Please remove the velcro
> slippers and place them in their container.
>
> If you prefer the ultrasonic log-off mode, press the indicated blue
> button. When the twin panels open, pull forward by rings A & B. The
> knob to the left, just below the blue light, has three settings, low,
> medium or high. For normal use, the medium setting is suggested.
>
> After these settings have been made, you can activate the device by
> switching to the "ON" position the clearly marked red switch. If
> during the unsubscribing operation you wish to change the settings,
> place the "manual off" override switch in the "OFF" position. You may
> now make the change and repeat the cycle. When the green exit light
> goes on, you may log off and have lunch. Please close the door behind
> you.
>
>
> --
>             ... _._. ._ ._. . _._. ._. ___ .__ ._. . .__. ._ .. ._.
>      Felix Finch: scarecrow repairman & rocket surgeon / felix@crowfix.com
>   GPG = E987 4493 C860 246C 3B1E  6477 7838 76E9 182E 8151 ITAR license
> #4933
> I've found a solution to Fermat's Last Theorem but I see I've run out of
> room o
> --
> gentoo-amd64@gentoo.org mailing list
>
>

[-- Attachment #2: Type: text/html, Size: 4854 bytes --]

[gentoo-amd64] unsubscribe

[Jüri-Kaur Schultz]

unsubscribe
-- 
gentoo-amd64@gentoo.org mailing list

__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] unsubscribe

[Daniel Iliev]

Jüri-Kaur Schultz wrote:
> unsubscribe
>   

Send a mail to gentoo-amd64+help@gentoo.org to find out how to do this.

-- 
Best regards,
Daniel


-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] unsubscribe

[Simon Stelling]

Jüri-Kaur Schultz wrote:
> unsubscribe

No.

-- 
Kind Regards,

Simon Stelling
Gentoo/AMD64 Developer
-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] unsubscribe

[felix]

On Wed, Dec 27, 2006 at 10:46:25PM -0800, J?ri-Kaur Schultz wrote:
> unsubscribe

Here's how to unsubscribe:

First, ask your Internet Provider to mail you an Unsubscribing Kit.
Then follow these directions.

The kit will most likely be the standard no-fault type. Depending on
requirements, System A and/or System B can be used. When operating
System A, depress lever and a plastic dalkron unsubscriber will be
dispensed through the slot immediately underneath. When you have
fastened the adhesive lip, attach connection marked by the large "X"
outlet hose. Twist the silver-coloured ring one inch below the
connection point until you feel it lock.

The kit is now ready for use. The Cin-Eliminator is activated by the
small switch on the lip.  When securing, twist the ring back to its
initial condition, so that the two orange lines meet.  Disconnect.
Place the dalkron unsubscriber in the vacuum receptacle to the rear.
Activate by pressing the blue button.

The controls for System B are located on the opposite side. The red
release switch places the Cin-Eliminator into position; it can be
adjusted manually up or down by pressing the blue manual release
button. The opening is self-adjusting. To secure after use, press the
green button, which simultaneously activates the evaporator and
returns the Cin-Eliminator to its storage position.

You may log off if the green exit light is on over the evaporator.  If
the red light is illuminated, one of the Cin-Eliminator requirements
has not been properly implemented. Press the "List Guy" call button on
the right of the evaporator. He will secure all facilities from his
control panel.

To use the Auto-Unsub, first undress and place all your clothes in the
clothes rack. Put on the velcro slippers located in the cabinet
immediately below. Enter the shower, taking the entire kit with
you. On the control panel to your upper right upon entering you will
see a "Shower seal" button. Press to activate. A green light will then
be illuminated immediately below. On the intensity knob, select the
desired setting. Now depress the Auto-Unsub activation lever. Bathe
normally.

The Auto-Unsub will automatically go off after three minutes unless
you activate the "Manual off" override switch by flipping it up. When
you are ready to leave, press the blue "Shower seal" release
button. The door will open and you may leave. Please remove the velcro
slippers and place them in their container.

If you prefer the ultrasonic log-off mode, press the indicated blue
button. When the twin panels open, pull forward by rings A & B. The
knob to the left, just below the blue light, has three settings, low,
medium or high. For normal use, the medium setting is suggested.

After these settings have been made, you can activate the device by
switching to the "ON" position the clearly marked red switch. If
during the unsubscribing operation you wish to change the settings,
place the "manual off" override switch in the "OFF" position. You may
now make the change and repeat the cycle. When the green exit light
goes on, you may log off and have lunch. Please close the door behind
you.


-- 
            ... _._. ._ ._. . _._. ._. ___ .__ ._. . .__. ._ .. ._.
     Felix Finch: scarecrow repairman & rocket surgeon / felix@crowfix.com
  GPG = E987 4493 C860 246C 3B1E  6477 7838 76E9 182E 8151 ITAR license #4933
I've found a solution to Fermat's Last Theorem but I see I've run out of room o
-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] unsubscribe

[Michel Merinoff]

Jüri-Kaur Schultz wrote:
> unsubscribe
>   
#include subscribe.h;
unsubscribe ('gentoo-amd64@lists.gentoo.org') or die();
Send instant messages to your online friends http://uk.messenger.yahoo.com 
-- 
gentoo-amd64@gentoo.org mailing list

[gentoo-amd64] unsubscribe

[Ryan A. Rice]

unsubscribe
-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] unsubscribe

[Harry Holt]

[-- Attachment #1: Type: text/plain, Size: 568 bytes --]

It looks like you are trying to add to your subscriptions.  I can
automatically subscribe you to all the lists I have access to.  If this is
what you want, do nothing!  I will add you to all 13,467 subscriptions
within a few hours!

If that is not what you want, please respond back with your name, address,
phone number, and credit card information.  We will check your credit
balance and response within a few weeks.

Thanks!


On 12/28/06, Ryan A. Rice <rrice@ihydra.com> wrote:
>
> unsubscribe
> --
> gentoo-amd64@gentoo.org mailing list
>
>


-- 
Harry Holt, PMP

[-- Attachment #2: Type: text/html, Size: 944 bytes --]

RE: [gentoo-amd64] unsubscribe

[Mike Bonar]

<thick French accent>Be gone!  Or we shall taunt you a third time!</thick French accent>

;-)



-----Original Message-----
From: Michel Merinoff [mailto:mike_merinov@yahoo.co.uk]
Sent: Thursday, December 28, 2006 10:43 AM
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] unsubscribe


Jüri-Kaur Schultz wrote:
> unsubscribe
>   
#include subscribe.h;
unsubscribe ('gentoo-amd64@lists.gentoo.org') or die();
Send instant messages to your online friends http://uk.messenger.yahoo.com 
-- 
gentoo-amd64@gentoo.org mailing list

-- 
No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.5.432 / Virus Database: 268.15.29/607 - Release Date: 12/28/2006 12:31 PM
 

-- 
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.5.432 / Virus Database: 268.15.29/607 - Release Date: 12/28/2006 12:31 PM
 


-- 
gentoo-amd64@gentoo.org mailing list

[gentoo-amd64] unsubscribe

[Alex Alpisa]

unsubscribe
-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] unsubscribe

[Simon Stelling]

Alex Alpisa wrote:
> unsubscribe

I wish you a merry christmas, too.

-- 
Kind Regards,

Simon Stelling
Gentoo/AMD64 Developer
-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] Error emerge-ing ffmpeg-0.4.9-_p20062006

[Thomas Rösner]

Ronan Klyne wrote:
> Somehow my googling did not turn up that bug page, thanks for pointing
> it out...

Google doesn't like bugzilla (and, to a lesser degree, the forums). So 
if you try to find out if someone else is hit by a problem, try bugzilla 
search (with ALL as first word when using the quick search), google, 
forums (that's the order I search them).

Regards,
    T.
-- 
gentoo-amd64@gentoo.org mailing list

[gentoo-amd64] unsubscribe

[roberts]

unsubscribe

-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] unsubscribe

[Daniel Iliev]

roberts wrote:
> unsubscribe
>
>   

I will not!

;-)))

-- 
Best regards,
Daniel


-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] unsubscribe

[Joaquim Quinteiro Uchoa]

How To UnSubscribe

    First, send me $29.95 + 6.95 shipping for an Unsubscribing Kit.
When you receive it, follow these directions.

    The basic kit will be the standard no-fault type. Depending on
your specific requirements, System A and/or System B can be used. When
operating System A, depress yellow lever and a plastic dalkron
unsubscriber will be dispensed through the slot immediately
underneath. When you have fastened the adhesive lip, attach connection
marked by the large "X" on the outlet hose. Twist the silver-coloured
ring one inch below the connection point until you feel it lock into
position.

    The kit is now ready for use. The Cin-Eliminator is activated by
the small switch on the lip. When securing, twist the ring back to its
initial condition, so that the two orange lines meet. Disconnect.
Place the dalkron unsubscriber in the vacuum receptacle to the rear.
Activate by pressing the blue button.

    The controls for System B are located on the opposite side. The
red release switch swings the Cin-Eliminator into position; it can be
adjusted manually up or down by pressing the blue manual release
button. The opening is self-adjusting. To secure after use, press the
green button, which simultaneously activates the evaporator and
returns the Cin-Eliminator to its neutral position.

    You may log off if the green exit light is on over the evaporator.
If the red light is illuminated, one of the Cin-Eliminator
requirements has not been properly implemented. Press the "List Guy"
call button, located to the right of the evaporator. He will secure
all facilities from his control panel.

    To use the Auto-Unsub, first undress and place your clothes in the
clothes rack. Put on the Velcro slippers located in the cabinet
immediately below. Enter the shower, taking the entire kit with you.
On the control panel to your upper right upon entering you will see a
"Shower seal" button. Press to activate. A green light will then be
illuminated immediately beneath the button. On the intensity knob,
select the desired setting. Now depress the Auto-Unsub activation
lever and bathe normally.

    The Auto-Unsub will automatically turn off after three minutes
unless you activate the "Manual off" override switch by flipping it
up. When you are ready to leave, press the blue "Shower seal release"
button. The door will open and you may leave. Please remove the Velcro
slippers and place them in the receptacle provided.

    If you prefer the ultrasonic log-off mode, press the indicated
orange button. When the twin panels open, pull forward by rings A & B.
The knob to the left, just below the blue light, has three settings,
low, medium or high. For normal use, the medium setting is suggested.

    After these settings have been made, you can activate the device
by switching to the "ON" position the clearly marked red switch. If
during the unsubscribing operation, you wish to change the settings,
turn the "manual off" override switch to the "OFF" position. You may
now make the change and repeat the cycle. When the green exit light
goes on, you may log off and have lunch. Please close the door behind
you to avoid discharging the Cin-Eliminator during periods of nonuse.

2006/12/8, roberts <listes@ocean.lv>:
> unsubscribe
>
> --
> gentoo-amd64@gentoo.org mailing list
>
>


-- 
[]s
Joaquim
------------------------------------------
  (o_    Joaquim Quinteiro Uchoa
 //\        Consultor Linux e EaD
 U_/_    Linux User # 100534
------------------------------------------
-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] unsubscribe

[Marek Wróbel]

Joaquim Quinteiro Uchoa wrote:
> How To UnSubscribe
> 
>    First, send me $29.95 + 6.95 shipping for an Unsubscribing Kit.
> When you receive it, follow these directions.
>
> [SNIP]

I had been waiting for it :)

Regards,
Marek Wróbel
-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] unsubscribe

[Vladimir G. Ivanovic]

Marek Wróbel wrote:
> Joaquim Quinteiro Uchoa wrote:
>> How To UnSubscribe
>>
>>    First, send me $29.95 + 6.95 shipping for an Unsubscribing Kit.
>> When you receive it, follow these directions.
>>
>> [SNIP]
> 
> I had been waiting for it :)
> 
> Regards,
> Marek Wróbel

Me too. I lost the original instructions and so I've been compelled to 
read all those messages to gentoo-amd64. (When will those people get a 
life? ;-)

Thanks.

--- Vladimir

P.S. I heard there was a $10 mail-in rebate (one per household) , but 
I've spent hours looking for it on the Web, without ever finding it. 
Any leads would be appreciated.
-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] unsubscribe

[Peter Weller]

Time for me to unsubscribe ^_-
-- 
gentoo-amd64@gentoo.org mailing list

[gentoo-amd64] unsubscribe

[Jean.Borsenberger]

-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] unsubscribe

[Simon Stelling]

Here's how to unsubscribe:

First, ask your Internet Provider to mail you an Unsubscribing Kit.
Then follow these directions.

The kit will most likely be the standard no-fault type. Depending on
requirements, System A and/or System B can be used. When operating
System A, depress lever and a plastic dalkron unsubscriber will be
dispensed through the slot immediately underneath. When you have
fastened the adhesive lip, attach connection marked by the large "X"
outlet hose. Twist the silver-coloured ring one inch below the
connection point until you feel it lock.

The kit is now ready for use. The Cin-Eliminator is activated by the
small switch on the lip.  When securing, twist the ring back to its
initial condition, so that the two orange lines meet.  Disconnect.
Place the dalkron unsubscriber in the vacuum receptacle to the rear.
Activate by pressing the blue button.

The controls for System B are located on the opposite side. The red
release switch places the Cin-Eliminator into position; it can be
adjusted manually up or down by pressing the blue manual release
button. The opening is self-adjusting. To secure after use, press the
green button, which simultaneously activates the evaporator and
returns the Cin-Eliminator to its storage position.

You may log off if the green exit light is on over the evaporator.  If
the red light is illuminated, one of the Cin-Eliminator requirements
has not been properly implemented. Press the "List Guy" call button on
the right of the evaporator. He will secure all facilities from his
control panel.

To use the Auto-Unsub, first undress and place all your clothes in the
clothes rack. Put on the velcro slippers located in the cabinet
immediately below. Enter the shower, taking the entire kit with
you. On the control panel to your upper right upon entering you will
see a "Shower seal" button. Press to activate. A green light will then
be illuminated immediately below. On the intensity knob, select the
desired setting. Now depress the Auto-Unsub activation lever. Bathe
normally.

The Auto-Unsub will automatically go off after three minutes unless
you activate the "Manual off" override switch by flipping it up. When
you are ready to leave, press the blue "Shower seal" release
button. The door will open and you may leave. Please remove the velcro
slippers and place them in their container.

If you prefer the ultrasonic log-off mode, press the indicated blue
button. When the twin panels open, pull forward by rings A & B. The
knob to the left, just below the blue light, has three settings, low,
medium or high. For normal use, the medium setting is suggested.

After these settings have been made, you can activate the device by
switching to the "ON" position the clearly marked red switch. If
during the unsubscribing operation you wish to change the settings,
place the "manual off" override switch in the "OFF" position. You may
now make the change and repeat the cycle. When the green exit light
goes on, you may log off and have lunch. Please close the door behind
you.

-- 
Kind Regards,

Simon Stelling
Gentoo/AMD64 Developer
-- 
Kind Regards,

Simon Stelling
Gentoo/AMD64 developer
-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] unsubscribe

[Rob Lesslie]

Ahh... waiting for that.
-- 
Rob Lesslie
-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] unsubscribe

[Daniel Iliev]

Jean.Borsenberger@obspm.fr wrote:
>
DON'T!

-- 
Best regards,
Daniel


-- 
gentoo-amd64@gentoo.org mailing list

[gentoo-amd64] unsubscribe

[Michal Žeravík]

unsubscribe
-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] unsubscribe

[Simon Stelling]

All your base are belong to us.

-- 
Kind Regards,

Simon Stelling
Gentoo/AMD64 Developer
-- 
gentoo-amd64@gentoo.org mailing list

[gentoo-amd64] unsubscribe

[Mike Do]

-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] unsubscribe

[Simon Stelling]

Here's how to unsubscribe:

First, ask your Internet Provider to mail you an Unsubscribing Kit.
Then follow these directions.

The kit will most likely be the standard no-fault type. Depending on
requirements, System A and/or System B can be used. When operating
System A, depress lever and a plastic dalkron unsubscriber will be
dispensed through the slot immediately underneath. When you have
fastened the adhesive lip, attach connection marked by the large "X"
outlet hose. Twist the silver-coloured ring one inch below the
connection point until you feel it lock.

The kit is now ready for use. The Cin-Eliminator is activated by the
small switch on the lip.  When securing, twist the ring back to its
initial condition, so that the two orange lines meet.  Disconnect.
Place the dalkron unsubscriber in the vacuum receptacle to the rear.
Activate by pressing the blue button.

The controls for System B are located on the opposite side. The red
release switch places the Cin-Eliminator into position; it can be
adjusted manually up or down by pressing the blue manual release
button. The opening is self-adjusting. To secure after use, press the
green button, which simultaneously activates the evaporator and
returns the Cin-Eliminator to its storage position.

You may log off if the green exit light is on over the evaporator.  If
the red light is illuminated, one of the Cin-Eliminator requirements
has not been properly implemented. Press the "List Guy" call button on
the right of the evaporator. He will secure all facilities from his
control panel.

To use the Auto-Unsub, first undress and place all your clothes in the
clothes rack. Put on the velcro slippers located in the cabinet
immediately below. Enter the shower, taking the entire kit with
you. On the control panel to your upper right upon entering you will
see a "Shower seal" button. Press to activate. A green light will then
be illuminated immediately below. On the intensity knob, select the
desired setting. Now depress the Auto-Unsub activation lever. Bathe
normally.

The Auto-Unsub will automatically go off after three minutes unless
you activate the "Manual off" override switch by flipping it up. When
you are ready to leave, press the blue "Shower seal" release
button. The door will open and you may leave. Please remove the velcro
slippers and place them in their container.

If you prefer the ultrasonic log-off mode, press the indicated blue
button. When the twin panels open, pull forward by rings A & B. The
knob to the left, just below the blue light, has three settings, low,
medium or high. For normal use, the medium setting is suggested.

After these settings have been made, you can activate the device by
switching to the "ON" position the clearly marked red switch. If
during the unsubscribing operation you wish to change the settings,
place the "manual off" override switch in the "OFF" position. You may
now make the change and repeat the cycle. When the green exit light
goes on, you may log off and have lunch. Please close the door behind
you.

-- 
Kind Regards,

Simon Stelling
Gentoo/AMD64 Developer
-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] unsubscribe

[Peter Humphrey]

On Thursday 25 May 2006 22:45, Simon Stelling wrote:

[blah blah blah etc]

Don't you ever get tired of that childish game?

-- 
Rgds
Peter.
-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] unsubscribe

[Nuitari]

> On Thursday 25 May 2006 22:45, Simon Stelling wrote:
>
> [blah blah blah etc]
>
> Don't you ever get tired of that childish game?

I laugh everytime.
-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] unsubscribe

[Chris Traylor]

[-- Attachment #1: Type: text/plain, Size: 470 bytes --]

On Thu, 2006-05-25 at 18:54 -0400, Nuitari wrote:

> > On Thursday 25 May 2006 22:45, Simon Stelling wrote:
> >
> > [blah blah blah etc]
> >
> > Don't you ever get tired of that childish game?
> 
> I laugh everytime.


Not only do I laugh everytime, but I actually look forward to the reply
when I see an errant request.

Chris

--
Sometimes I wonder whether the world is being run by smart people who
are putting us on or by imbeciles who really mean it. -- Mark Twain

[-- Attachment #2: Type: text/html, Size: 1030 bytes --]

Re: [gentoo-amd64] unsubscribe

[Mike Arthur]

On Friday 26 May 2006 01:20, Chris Traylor wrote:
> Not only do I laugh everytime, but I actually look forward to the reply
> when I see an errant request.
>
> Chris
I am exactly the same!

-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] unsubscribe

[Hemmann, Volker Armin]

On Friday 26 May 2006 00:48, Peter Humphrey wrote:
> On Thursday 25 May 2006 22:45, Simon Stelling wrote:
>
> [blah blah blah etc]
>
> Don't you ever get tired of that childish game?

I don't

but I do get tired of all that 'unsubscribe' and 'please unsubscribe me!!!' 
and 'don't you ever get tired' mails ... *eg*
-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] unsubscribe

[Benny Pedersen]

> Here's how to unsubscribe:

Mailing List: Post to List | Reply to List | Help | Unsubscribe | Subscribe

i see them on all maillisng lists that follow some rfc for this, if i want to undo some bad things i just
press a link in squirrel, yes its hard to do that on notmail.com :-)

good to see gentoo developpers have humor where availble :-))



-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] unsubscribe

[Richard Fish]

On 5/25/06, Simon Stelling <blubb@gentoo.org> wrote:
> Here's how to unsubscribe:

Simon,

Any chance you could stick this in your dev space, and just post a
link to it in the future?

-Richard

-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] unsubscribe

[Simon Stelling]

Richard Fish wrote:
> Any chance you could stick this in your dev space, and just post a
> link to it in the future?

Well, yes, of course I could, but then it wouldn't be fun anymore, would it?

-- 
Kind Regards,

Simon Stelling
Gentoo/AMD64 Developer
-- 
gentoo-amd64@gentoo.org mailing list

[gentoo-amd64] unsubscribe

[Seth Jennings]

-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] unsubscribe

[Kyle Lutze]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Seth Jennings wrote:
> 

must resist!.. ugh,
must resist the urge to post the unsubscribe kit information!
sooo hard...

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2-ecc0.1.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFESEn9VFIipMnXxfYRAtWUAJ0YRfF/JIa/2hBOfGQ7i9xysdAWeQCeIWom
5RuXDwewu6cHkNUhvkZcjuc=
=QtNG
-----END PGP SIGNATURE-----
-- 
gentoo-amd64@gentoo.org mailing list

[gentoo-amd64] unsubscribe

[Charles Read]

-- 
gentoo-amd64@gentoo.org mailing list

[gentoo-amd64] unsubscribe

[Casey Bralla]

On Sunday 05 February 2006 13:01, gentoo-amd64+help@gentoo.org wrote:
> Topics (messages 3220 throught 3269):
>
> [gentoo-amd64] Re: Re: Re: XOrg 6.9
>       3220 - Bernhard Breinbauer <infopipe@gmx.net>
>
> [gentoo-amd64] Wow! KDE 3.5.1 & Xorg 7.0 w/ Composite
>       3221 - Bernhard Breinbauer <infopipe@gmx.net>
>
> [gentoo-amd64] Re: Fritz! WLAN Usb stick
>       3222 - Duncan <1i5t5.duncan@cox.net>
>
> [gentoo-amd64] Re: Re: Re: Re: XOrg 6.9
>       3223 - Duncan <1i5t5.duncan@cox.net>
>
> [gentoo-amd64] Re: Fritz! WLAN Usb stick
>       3224 - Nuitari <nuitari@melchior.nuitari.net>
>
> [gentoo-amd64] Wow! KDE 3.5.1 & Xorg 7.0 w/ Composite
>       3225 - Bernhard Breinbauer <infopipe@gmx.net>
>
> [gentoo-amd64] Re: Re: Wow! KDE 3.5.1 & Xorg 7.0 w/ Composite
>       3226 - Duncan <1i5t5.duncan@cox.net>
>       3245 - Duncan <1i5t5.duncan@cox.net>
>
> [gentoo-amd64] Re: Re: Wow! KDE 3.5.1 & Xorg 7.0 w/ Composite
>       3227 - John Myers <electronerd@electronerdia.net>
>
> [gentoo-amd64] Re: Re: Re: Re: XOrg 6.9
>       3228 - Bernhard Breinbauer <infopipe@gmx.net>
>
> [gentoo-amd64] Re: Wow! KDE 3.5.1 & Xorg 7.0 w/ Composite
>       3229 - ??? <michalz@olomouc.com>
>       3234 - Duncan <1i5t5.duncan@cox.net>
>       3235 - Harm Geerts <harmgeerts@home.nl>
>       3236 - Harm Geerts <harmgeerts@home.nl>
>
> [gentoo-amd64] fwbuilder taking ages to compile
>       3230 - Gavin Seddon <gavin.m.seddon@manchester.ac.uk>
>
> [gentoo-amd64] Re: fwbuilder taking ages to compile[fixed]
>       3231 - Gavin Seddon <gavin.m.seddon@manchester.ac.uk>
>
> [gentoo-amd64] Fritz! WLAN Usb stick
>       3232 - B Vance <bvance@storm.ca>
>
> [gentoo-amd64] Wow! KDE 3.5.1 & Xorg 7.0 w/ Composite
>       3233 - jj <tenties@gmx.de>
>
> [gentoo-amd64] Re: Wow! KDE 3.5.1 & Xorg 7.0 w/ Composite
>       3237 - Brett Johnson <brett@blzj.com>
>
> [gentoo-amd64] Re: Wow! KDE 3.5.1 & Xorg 7.0 w/ Composite
>       3238 - Mike Owen <kyphros@gmail.com>
>
> [gentoo-amd64] Re: Wow! KDE 3.5.1 & Xorg 7.0 w/ Composite
>       3239 - William Tetrault <xcourse97@charter.net>
>
> [gentoo-amd64] Wow! KDE 3.5.1 & Xorg 7.0 w/ Composite
>       3240 - Bernhard Breinbauer <infopipe@gmx.net>
>
> [gentoo-amd64] rosegarden
>       3242 - Piotr Pruszczak <p.pruszczak@pro.onet.pl>
>
> [gentoo-amd64] rosegarden
>       3243 - ??? <michalz@olomouc.com>
>
> [gentoo-amd64] rosegarden
>       3244 - Maik <maik@maik.kicks-ass.org>
>
> [gentoo-amd64] Re: Re: Wow! KDE 3.5.1 & Xorg 7.0 w/ Composite
>       3246 - Taka John Brunkhorst <antiwmac@gmail.com>
>
> [gentoo-amd64] Broken network
>       3247 - "gigli@swipnet.se" <gigli@swipnet.se>
>
> [gentoo-amd64] Broken network
>       3248 - Steve Herber <herber@thing.com>
>
> [gentoo-amd64] Fritz! WLAN Usb stick
>       3249 - Luigi Pinna <mailing-gentoo@sailorferris.com>
>
> [gentoo-amd64] emerging x86 Sun-JDK in my amd64
>       3250 - Felipe Ribeiro <felipernb@gmail.com>
>
> [gentoo-amd64] emerging x86 Sun-JDK in my amd64
>       3251 - "Hemmann, Volker Armin" <volker.armin.hemmann@tu-clausthal.de>
>
> [gentoo-amd64] emerging x86 Sun-JDK in my amd64
>       3252 - Karol Krizka <kkrizka@gmail.com>
>
> [gentoo-amd64] emerging x86 Sun-JDK in my amd64
>       3253 - "Hemmann, Volker Armin" <volker.armin.hemmann@tu-clausthal.de>
>
> [gentoo-amd64] emerging x86 Sun-JDK in my amd64
>       3254 - Felipe Ribeiro <felipernb@gmail.com>
>
> [gentoo-amd64] emerging x86 Sun-JDK in my amd64
>       3255 - Felipe Ribeiro <felipernb@gmail.com>
>
> [gentoo-amd64] emerging x86 Sun-JDK in my amd64
>       3256 - "Hemmann, Volker Armin" <volker.armin.hemmann@tu-clausthal.de>
>
> [gentoo-amd64] libGL can't be found...
>       3257 - Hamish Marson <hamish@travellingkiwi.com>
>
> [gentoo-amd64] Broken network
>       3258 - "gigli@swipnet.se" <gigli@swipnet.se>
>
> [gentoo-amd64] Fritz! WLAN Usb stick
>       3259 - Lorenzo Milesi <lorenzo.milesi@gmail.com>
>
> [gentoo-amd64] network problem - at a loss
>       3260 - Thierry de Coulon <tcoulon@decoulon.ch>
>
> [gentoo-amd64] emerging x86 Sun-JDK in my amd64
>       3261 - Jan Meier <jan@codejunky.org>
>
> [gentoo-amd64] network problem - solved (?!)
>       3262 - Thierry de Coulon <tcoulon@decoulon.ch>
>
> [gentoo-amd64] libGL can't be found...
>       3263 - "Hemmann, Volker Armin" <volker.armin.hemmann@tu-clausthal.de>
>
> [gentoo-amd64] Re: network problem - at a loss
>       3264 - Duncan <1i5t5.duncan@cox.net>
>
> [gentoo-amd64] Re: network problem - at a loss
>       3265 - Thierry de Coulon <tcoulon@decoulon.ch>
>
> [gentoo-amd64] Broken network
>       3266 - Richard Fish <bigfish@asmallpond.org>
>
> [gentoo-amd64] AMD Athlon 64 and AMD Athlon 64 FX
>       3267 - "P.V.Anthony" <pvantony@singnet.com.sg>
>
> [gentoo-amd64] AMD Athlon 64 and AMD Athlon 64 FX
>       3268 - Barry Walsh <bwalsh@indigo.ie>
>
> [gentoo-amd64] AMD Athlon 64 and AMD Athlon 64 FX
>       3269 - "P.V.Anthony" <pvantony@singnet.com.sg>

-- 

Casey Bralla
Chief Nerd in Residence
The NerdWorld Organisation

IM: VorlonNerdWorld
Skype: NerdWorld
http://www.NerdWorld.org
-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] unsubscribe

[Craig Webster]

On 5 Feb 2006, at 18:47, Casey Bralla wrote:
> [an unsubscribe request judging by the subject of the email]

Please check any of the list emails -- they all include list  
instructions in their headers:

List-Post: <mailto:gentoo-amd64@lists.gentoo.org>
List-Help: <mailto:gentoo-amd64+help@gentoo.org>
List-Unsubscribe: <mailto:gentoo-amd64+unsubscribe@gentoo.org>
List-Subscribe: <mailto:gentoo-amd64+subscribe@gentoo.org>
List-Id: Gentoo Linux mail <gentoo-amd64.gentoo.org>

Email the unsubscribe address to unsubscribe.

Yours,
Craig
--
Craig Webster | t: +44 (0)131 516 8595 | e: craig@xeriom.net
Xeriom.NET    | f: +44 (0)131 661 0689 | w: http://xeriom.net


-- 
gentoo-amd64@gentoo.org mailing list

[gentoo-amd64] unsubscribe

[Iain McKee]

[-- Attachment #1: Type: text/plain, Size: 23 bytes --]

Please unsubscribe me

[-- Attachment #2: Type: text/html, Size: 27 bytes --]

Re: [gentoo-amd64] unsubscribe

[Simon Stelling]

Iain McKee wrote:
> Please unsubscribe me

please do that yourself and have a look at the mail header of your message:

List-Unsubscribe: <mailto:gentoo-amd64+unsubscribe@gentoo.org>

-- 
Simon Stelling
Gentoo/AMD64 Operational Co-Lead
blubb@gentoo.org
-- 
gentoo-amd64@gentoo.org mailing list

[gentoo-amd64] unsubscribe

[Brandon M. Heimbigner]

unsubscribe
-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] unsubscribe

[Jonathan Schaeffer]

Hey Felix, won't you post again your howto unsubscribe ?

2005/9/20, Brandon M. Heimbigner <bassmutant@tuffmail.com>:
> unsubscribe
> --
> gentoo-amd64@gentoo.org mailing list
> 
>

-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] unsubscribe

[felix]

On Tue, Sep 20, 2005 at 11:11:51AM +0200, Jonathan Schaeffer wrote:
> Hey Felix, won't you post again your howto unsubscribe ?

Arrrrr :-)

-- 
            ... _._. ._ ._. . _._. ._. ___ .__ ._. . .__. ._ .. ._.
     Felix Finch: scarecrow repairman & rocket surgeon / felix@crowfix.com
  GPG = E987 4493 C860 246C 3B1E  6477 7838 76E9 182E 8151 ITAR license #4933
I've found a solution to Fermat's Last Theorem but I see I've run out of room o
-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] unsubscribe

[felix]

On Mon, Sep 19, 2005 at 05:58:32PM -0700, Brandon M. Heimbigner wrote:
> unsubscribe

Here's how to unsubscribe:

First, ask your Internet Provider to mail you an Unsubscribing Kit.
Then follow these directions.

The kit will most likely be the standard no-fault type. Depending on
requirements, System A and/or System B can be used. When operating
System A, depress lever and a plastic dalkron unsubscriber will be
dispensed through the slot immediately underneath. When you have
fastened the adhesive lip, attach connection marked by the large "X"
outlet hose. Twist the silver-coloured ring one inch below the
connection point until you feel it lock.

The kit is now ready for use. The Cin-Eliminator is activated by the
small switch on the lip.  When securing, twist the ring back to its
initial condition, so that the two orange lines meet.  Disconnect.
Place the dalkron unsubscriber in the vacuum receptacle to the rear.
Activate by pressing the blue button.

The controls for System B are located on the opposite side. The red
release switch places the Cin-Eliminator into position; it can be
adjusted manually up or down by pressing the blue manual release
button. The opening is self-adjusting. To secure after use, press the
green button, which simultaneously activates the evaporator and
returns the Cin-Eliminator to its storage position.

You may log off if the green exit light is on over the evaporator.  If
the red light is illuminated, one of the Cin-Eliminator requirements
has not been properly implemented. Press the "List Guy" call button on
the right of the evaporator. He will secure all facilities from his
control panel.

To use the Auto-Unsub, first undress and place all your clothes in the
clothes rack. Put on the velcro slippers located in the cabinet
immediately below. Enter the shower, taking the entire kit with
you. On the control panel to your upper right upon entering you will
see a "Shower seal" button. Press to activate. A green light will then
be illuminated immediately below. On the intensity knob, select the
desired setting. Now depress the Auto-Unsub activation lever. Bathe
normally.

The Auto-Unsub will automatically go off after three minutes unless
you activate the "Manual off" override switch by flipping it up. When
you are ready to leave, press the blue "Shower seal" release
button. The door will open and you may leave. Please remove the velcro
slippers and place them in their container.

If you prefer the ultrasonic log-off mode, press the indicated blue
button. When the twin panels open, pull forward by rings A & B. The
knob to the left, just below the blue light, has three settings, low,
medium or high. For normal use, the medium setting is suggested.

After these settings have been made, you can activate the device by
switching to the "ON" position the clearly marked red switch. If
during the unsubscribing operation you wish to change the settings,
place the "manual off" override switch in the "OFF" position. You may
now make the change and repeat the cycle. When the green exit light
goes on, you may log off and have lunch. Please close the door behind
you.


-- 
            ... _._. ._ ._. . _._. ._. ___ .__ ._. . .__. ._ .. ._.
     Felix Finch: scarecrow repairman & rocket surgeon / felix@crowfix.com
  GPG = E987 4493 C860 246C 3B1E  6477 7838 76E9 182E 8151 ITAR license #4933
I've found a solution to Fermat's Last Theorem but I see I've run out of room o
-- 
gentoo-amd64@gentoo.org mailing list

[gentoo-amd64] unsubscribe

[Thierry Girardin]

[-- Attachment #1: Type: text/plain, Size: 1 bytes --]



[-- Attachment #2: Type: text/html, Size: 233 bytes --]

[gentoo-amd64] unsubscribe

[dan farrell]

-- 
gentoo-amd64@gentoo.org mailing list

[gentoo-amd64] unsubscribe

[dan farrell]

-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] unsubscribe

[Camilo Aguilar]

[-- Attachment #1.1: Type: text/plain, Size: 179 bytes --]

please, for unsubscribe send mail to gentoo-amd64+unsubscribe@gentoo.org

On Sat, 2005-08-27 at 22:30 -0500, dan farrell wrote:

> 
> 


Camilo Aguilar 
Director de Proyectos





[-- Attachment #1.2: Type: text/html, Size: 662 bytes --]

[-- Attachment #2: image001.gif --]
[-- Type: image/gif, Size: 3459 bytes --]