[opensuse-project] openSUSE @ Google Summer of Code 2007
Hi everyone, [sorry for cross-posting.] We just submitted our Google Summer of Code application for being a mentoring org in this years program. Therefore we are now looking for your project proposals and ideas, that could be turned into potential Summer of Code projects. Please share your thoughts with us on the mailing lists and/or add them to http://en.opensuse.org/Summer_of_Code_2007 Thanks, Christoph -- Christoph Thiel, Tech. Project Management, Research & Development SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-project+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, Christoph Thiel wrote:
We just submitted our Google Summer of Code application for being a mentoring org in this years program. Therefore we are now looking for your project proposals and ideas, that could be turned into potential Summer of Code projects.
Please share your thoughts with us on the mailing lists and/or add them to http://en.opensuse.org/Summer_of_Code_2007
Great, thanks! In relation to last year's project to create a GTK-based UI for YaST2, I now added a proposal to add a web Frontend to YaST2 by using the Wt C++ widget library: http://witty.sf.net/ I think it would be very cool to be able to remotely use YaST using a regular web browser. Thanks! Bye, LenZ - -- - ------------------------------------------------------------------ Lenz Grimmer <lenz@grimmer.com> -o) [ICQ: 160767607 | Jabber: LenZGr@jabber.org] /\\ http://www.lenzg.org/ V_V -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFF9TDgSVDhKrJykfIRAk0gAJ9DGpFX8Os1gLrSHhnIIeE4LqUNBACbBVQK lSdKp/2Ux0z25vTXI+9rsew= =KWKm -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-project+help@opensuse.org
Lenz Grimmer wrote:
I think it would be very cool to be able to remotely use YaST using a regular web browser. Thanks!
very good idea :-) jdd
-- http://www.dodin.net Lucien Dodin, inventeur http://lucien.dodin.net/index.shtml --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-project+help@opensuse.org
On Saturday 10 March 2007 17:10:32 Christoph Thiel wrote:
Hi everyone,
[sorry for cross-posting.]
We just submitted our Google Summer of Code application for being a mentoring org in this years program. Therefore we are now looking for your project proposals and ideas, that could be turned into potential Summer of Code projects.
For any of those who don't know, openSUSE was rejected as a SoC project this year. It's the only major distribution to not have been accepted this year, and I find it both very curious and a little ridiculous. Of course my suspicions, like most others' out there, is that this is because of the MS-Novell deal. I emailed gsoc@google.com and got this response: ------------------------- Hello Francis, Thanks for your email. I am very curious who told you that openSUSE was rejected because of the Microsoft deal. We are simply changing the mix of linux distros this year. That's it. There is no need to look for a conspiracy theory here. Best, Leslie Hawthorn Open Source Program Office Google Inc. ---------------------- Funnily enough, I can't really see how they 'mixed up' the linux distros this year. All the distros from last year seem to be on there; am I missing one of them? Regards, -- Francis Giannaros Website: http://francis.giannaros.org IRC: apokryphos on irc.freenode.net --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-project+help@opensuse.org
On Fri, Mar 16, 2007 at 10:15:32AM +0000, Francis Giannaros wrote:
On Saturday 10 March 2007 17:10:32 Christoph Thiel wrote:
Hi everyone,
[sorry for cross-posting.]
We just submitted our Google Summer of Code application for being a mentoring org in this years program. Therefore we are now looking for your project proposals and ideas, that could be turned into potential Summer of Code projects.
For any of those who don't know, openSUSE was rejected as a SoC project this year. It's the only major distribution to not have been accepted this year, and I find it both very curious and a little ridiculous. Of course my suspicions, like most others' out there, is that this is because of the MS-Novell deal.
AFAIK ~ 2/3 of the applying organizations were rejected :( We are talking to Google to figure out the details. Best, Christoph -- Christoph Thiel, Tech. Project Management, Research & Development SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-project+help@opensuse.org
At 04:10 AM 11/03/2007, Christoph Thiel wrote:
Hi everyone,
[sorry for cross-posting.]
We just submitted our Google Summer of Code application for being a mentoring org in this years program. Therefore we are now looking for your project proposals and ideas, that could be turned into potential Summer of Code projects.
Please share your thoughts with us on the mailing lists and/or add them to http://en.opensuse.org/Summer_of_Code_2007
Thanks, Christoph -- Christoph Thiel, Tech. Project Management, Research & Development SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) ---------------------------------------------------------------------
?what about something in the startup script that allows for the ability to lock out individual blocks of ram that are known faulty from use. I don't know how many old, but linux serviceable, notebooks that i've had to tell the owners nothing can be done with because a block of the ram on the motherboard ram has failed. They are of course out of warrenty and parts are either too expensive or non obtainable. scsijon -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.5.446 / Virus Database: 268.18.11/723 - Release Date: 15/03/2007 11:27 AM --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-project+help@opensuse.org
On Friday 16 March 2007 22:57, scsijon wrote:
...
?what about something in the startup script that allows for the ability to lock out individual blocks of ram that are known faulty from use.
I don't know how many old, but linux serviceable, notebooks that i've had to tell the owners nothing can be done with because a block of the ram on the motherboard ram has failed. They are of course out of warrenty and parts are either too expensive or non obtainable.
I know it's already moot w.r.t. the SoC, but I have encountered situations where I've wanted this very feature.
scsijon
Randall Schulz --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-project+help@opensuse.org
Hello, on Samstag, 17. März 2007, scsijon wrote:
?what about something in the startup script that allows for the ability to lock out individual blocks of ram that are known faulty from use.
I don't know how many old, but linux serviceable, notebooks that i've had to tell the owners nothing can be done with because a block of the ram on the motherboard ram has failed. They are of course out of warrenty and parts are either too expensive or non obtainable.
Just google for "badram" - there's a kernel patch available. Or, if only the upper blocks of RAM are broken, use the mem=... boot parameter. However, I don't know if it is a good idea to work with broken RAM - it might break more sooner or later and cause broken data. If things go bad, you won't even notice it and end up with lots of broken files on your harddisk. Not really funny... So the question is: how much are your data worth? (My answer: usually much more than new RAM would cost!) Regards, Christian Boltz PS: random sig ;-) - translation: There's always a backup of important data. The reverse is also valid: data that is not backed up isn't important. -- Von wichtigen Daten gibt es immer ein Backup. Der Umkehrschluß ist ebenfalls zulässig: Daten, von denen es kein Backup gibt, sind nicht wichtig. [Andreas Feile in suse-linux] --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-project+help@opensuse.org
Christian Boltz wrote:
(My answer: usually much more than new RAM would cost!)
basic laptop ram is not removable jdd -- http://www.dodin.net Lucien Dodin, inventeur http://lucien.dodin.net/index.shtml --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-project+help@opensuse.org
At 01:59 AM 18/03/2007, Christian Boltz wrote:
Hello,
on Samstag, 17. März 2007, scsijon wrote:
?what about something in the startup script that allows for the ability to lock out individual blocks of ram that are known faulty from use.
I don't know how many old, but linux serviceable, notebooks that i've had to tell the owners nothing can be done with because a block of the ram on the motherboard ram has failed. They are of course out of warrenty and parts are either too expensive or non obtainable.
Just google for "badram" - there's a kernel patch available. Or, if only the upper blocks of RAM are broken, use the mem=... boot parameter.
However, I don't know if it is a good idea to work with broken RAM - it might break more sooner or later and cause broken data. If things go bad, you won't even notice it and end up with lots of broken files on your harddisk. Not really funny...
So the question is: how much are your data worth? (My answer: usually much more than new RAM would cost!)
as I said basic ram in most notebooks is not removable. just pulled a p3 notebook I have on shelf with this problem to quote as an example: has 256meg on motherboard (fixed non-removable) with 128meg additional in socket. problem is the faulty ram is a 16byte block in the second 64k of the fixed ram. it's got a "soft" error, which means that sometimes it's ok other times it's not. other than this one problem there is nothing wrong with the notebook. I will have a search and read for the patch, but this may byte back as i've never patched a kernal before. Is there a quick guide anywhere? scsijon
Regards,
Christian Boltz
PS: random sig ;-) - translation: There's always a backup of important data. The reverse is also valid: data that is not backed up isn't important. -- Von wichtigen Daten gibt es immer ein Backup. Der Umkehrschluß ist ebenfalls zulässig: Daten, von denen es kein Backup gibt, sind nicht wichtig. [Andreas Feile in suse-linux] --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-project+help@opensuse.org
-- No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.5.446 / Virus Database: 268.18.12/724 - Release Date: 16/03/2007 12:12 PM
-- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.5.446 / Virus Database: 268.18.12/724 - Release Date: 16/03/2007 12:12 PM --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-project+help@opensuse.org
participants (7)
-
Christian Boltz -
Christoph Thiel -
Francis Giannaros -
jdd sur free -
Lenz Grimmer -
Randall R Schulz -
scsijon