Re: Thanks :)

Re: Thanks :)

[neilb]

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

Thanks!

[KeithG]

A big thanks to Grant and Marcel for tackling all these issues. I was
concerned that connman may go away, but this renewed effort gives me
hope that it'll keep going for a bit longer.

Keith

Re: Thanks!

[Grant Erickson]

On Nov 29, 2023, at 6:45 AM, KeithG <ys3al35l@gmail.com> wrote:
> A big thanks to Grant and Marcel for tackling all these issues. I was
> concerned that connman may go away, but this renewed effort gives me
> hope that it'll keep going for a bit longer.

Keith,

You’re welcome!

Best,

Grant

-- 
Principal
Nuovations

gerickson@nuovations.com
http://www.nuovations.com/

Re: Thanks!

[Marcus Folkesson]

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

I can only agree with Keith, thank you.

Best regards,
Marcus Folkesson

On Wed, Nov 29, 2023 at 08:59:47AM -0800, Grant Erickson wrote:
> On Nov 29, 2023, at 6:45 AM, KeithG <ys3al35l@gmail.com> wrote:
> > A big thanks to Grant and Marcel for tackling all these issues. I was
> > concerned that connman may go away, but this renewed effort gives me
> > hope that it'll keep going for a bit longer.
> 
> Keith,
> 
> You’re welcome!
> 
> Best,
> 
> Grant
> 
> -- 
> Principal
> Nuovations
> 
> gerickson@nuovations.com
> http://www.nuovations.com/
> 
> 

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

thanks!

[tungolcild]

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

As the submission period finished I wanted to thank everyone for their 
time, especially Julia and
Greg and Sasha (and everyone who helped!! As I am completing my MSc in 
Bioinformatics I wanted
to share this with everyone: http://www.pnas.org/content/107/20/9186

Fun! :) 

Good to luck to every Outreachy Applicant!

Best
ioannis

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

Thanks!

[Jan Evert van Grootheest]

Hello developers, testers and all those bug jugglers...

While pondering 2007 and 2008...

Many thanks for your work on Linux in 2007 from a simple Linux user. And 
I am looking forward to what 2008 will bring in .24 and on.

Have a blessed 2008.
Jan Evert

Thanks!

[Robert Brockway]

Hi guys.  I think the poor hard working developers get a lot more 
negative messages than positive (it's broken, there's a bug, etc) so I 
just wanted to send a positive message.

I've been a happy xfs user for many years and I've never had a problem 
with the filesystem.  Today I managed to powerdown a firewire drive with 
an XFS filesystem on it while it was mounted (oops).  Anyway there was FS 
corruption and after a vanilla xfs_repair failed I had to resort to 
xfs_repair -L.  The filesystem was fully repaired and is now fine.

Thanks a bunch to the xfs developers.

Cheers,

Rob

-- 
Robert Brockway B.Sc.        Phone:          +1-905-821-2327
Senior Technical Consultant  Urgent Support: +1-416-669-3073
OpenTrend Solutions Ltd      Email:          support@opentrend.net
                              Web:            www.opentrend.net

Thanks!!

[Dustin Lang]

Hi,

I finally upgraded to 2.6 last night, and I'm really enjoying it!  I have 
a PowerBook G4 1GHz (with NVidia graphics card).  CPU frequency scaling 
is working nicely for me.  The cpufreq driver reports:
> Registering PowerMac CPU frequency driver
> Low: 765 Mhz, High: 998 Mhz, Boot: 765 Mhz
Which makes me wonder if 2.4 was running at 765 the whole time.  Maybe 
because of this, 2.6 FEELS faster :)  Also, the backlight fine control is 
great!  I'll play with sleep/resume this weekend and report my status.

I just wanted to thank everyone who has worked on PPC Linux.  You've done 
great work!

Cheers,
dustin.

Re: Thanks!!

[Colin Leroy]

On 08 Apr 2005 at 10h04, Dustin Lang wrote:

Hi, 

> Which makes me wonder if 2.4 was running at 765 the whole time.
> Maybe because of this, 2.6 FEELS faster :)

2.6 feels faster on desktop for other reasons too, such as a faster
scheduler (at least it was the case when I switched to 2.6, maybe 2.4
got a faster one too).

>  Also, the backlight fine
> control is great!  I'll play with sleep/resume this weekend and
> report my status.

You mentioned you have an nVidia GPU, so I guess you won't have much
success - nVidia cards are badly supported as they're being very secret
about their hardware.

-- 
Colin

Re: Thanks!!

[Dan Malek]

On Apr 8, 2005, at 3:10 PM, Colin Leroy wrote:

> 2.6 feels faster on desktop for other reasons too, such as a faster
> scheduler (at least it was the case when I switched to 2.6, maybe 2.4
> got a faster one too).

A faster scheduler?  Now, that's one I've never heard :-)


	-- Dan

Re: Thanks!!

[Daniele Lacamera]

On Friday 08 April 2005 23:21, Dan Malek wrote:

> A faster scheduler?  Now, that's one I've never heard :-)
> 

If interested take a look here :
http://josh.trancesoftware.com/linux/


-- 
Daniele Lacamera
root at danielinux.net

Re: Thanks!!

[Colin Leroy]

On 08 Apr 2005 at 17h04, Dan Malek wrote:

Hi, 

> 
> On Apr 8, 2005, at 3:10 PM, Colin Leroy wrote:
> 
> > 2.6 feels faster on desktop for other reasons too, such as a faster
> > scheduler (at least it was the case when I switched to 2.6, maybe
> > 2.4 got a faster one too).
> 
> A faster scheduler?  Now, that's one I've never heard :-)

See http://kerneltrap.org/node/342 and
http://www.hpl.hp.com/research/linux/kernel/o1.php if you want more
infos.


-- 
Colin

Thanks :)

[David Greaves]

I got this yesterday

#################
This is an automatically generated mail message from mdadm
running on cu.dgreaves.com

A Fail event had been detected on md device /dev/md0.
#################

Looking at it tonight:
Oct 22 18:09:44 cu kernel: Current sdd: sense key Medium Error
Oct 22 18:09:44 cu kernel: Additional sense: Unrecovered read error - auto realloca
te failed
Oct 22 18:09:44 cu kernel: end_request: I/O error, dev sdd, sector 196988598
Oct 22 18:09:45 cu kernel: scsi3: ERROR on channel 0, id 0, lun 0, CDB: Read (10) 0
0 0b bd ce b7 00 00 01 00
Oct 22 18:09:45 cu kernel: Current sdd: sense key Medium Error
Oct 22 18:09:45 cu kernel: Additional sense: Unrecovered read error - auto realloca
te failed
Oct 22 18:09:45 cu kernel: end_request: I/O error, dev sdd, sector 196988599


The Maxtor Maxline+II 250Gb SATA drive (mfg date: feb 2004) is now out and I'm starting the RMA procedure.

No data lost (yet) so we can still watch TV - thanks everyone (especially Neil)

David

Re: Thanks :)

[Robin Bowes]

David Greaves wrote:
> I got this yesterday
> 
> #################
> This is an automatically generated mail message from mdadm
> running on cu.dgreaves.com
> 
> A Fail event had been detected on md device /dev/md0.
> #################

David,

How have you set things up to achieve this?

R.
-- 
http://robinbowes.com

Re: Thanks :)

[Steven Ihde]

On Fri, 22 Oct 2004 21:17:16 +0100, Robin Bowes wrote:
> David Greaves wrote:
> >I got this yesterday
> >
> >#################
> >This is an automatically generated mail message from mdadm
> >running on cu.dgreaves.com
> >
> >A Fail event had been detected on md device /dev/md0.
> >#################
> 
> David,
> 
> How have you set things up to achieve this?

See the section on Monitor mode (-F option) in the mdadm man page.
Debian's mdadm package, for example, sets it up so mdadm -F gets run
automatically at boot time to monitor your arrays.

-Steve

Re: Thanks :)

[Robin Bowes]

Steven Ihde wrote:
> On Fri, 22 Oct 2004 21:17:16 +0100, Robin Bowes wrote:
> 
>>David Greaves wrote:
>>
>>>I got this yesterday
>>>
>>>#################
>>>This is an automatically generated mail message from mdadm
>>>running on cu.dgreaves.com
>>>
>>>A Fail event had been detected on md device /dev/md0.
>>>#################
>>
>>David,
>>
>>How have you set things up to achieve this?
> 
> 
> See the section on Monitor mode (-F option) in the mdadm man page.
> Debian's mdadm package, for example, sets it up so mdadm -F gets run
> automatically at boot time to monitor your arrays.


Sorry, I wasn't clear enough in my question...

I am aware of mdadms' monitor mode; in fact, I'm sure it used to run 
when I first started using mdadm (on Fedora Core 2 installed from rpm 
built myself from src rpm).

I seem to remember that this was disabled at some stage but can't 
remember the detail - possibly something to do with preventing the array 
from shutting down cleanly because mdadm -F was open on it.

I am hoping that someone can suggest how best to run mdadm -F on Fedora 
Core 2. Perhaps it could be as simple as creating a script in 
/etc/init.d/ which would terminate before the array is shutdown?

R.
-- 
http://robinbowes.com

Thanks!!!

[Philipp Vollmer]

Hello to all developers,

thank you for your help. I finally managed to build this application.
I am only 14 years old but have been programming for 4 years ( 2 years in 
C(++) ) but I never saw so many tutorials with so many errors than in the
ALSA project.
Finally I found them all with your help and I hope I can program with the
ALSA library successfully.

With best regards

Philipp Vollmer

PS ( to Tim Goetze ):
The codeline in the example was completely wrong.
The argument had to be the adress of a pointer (!!!) but the other
arguments had the wrong type. Viva Polymorphism!!!
Thank you although.

_______________________________________________________________

Don't miss the 2002 Sprint PCS Application Developer's Conference
August 25-28 in Las Vegas - http://devcon.sprintpcs.com/adp/index.cfm?source=osdntextlink