Talk:Contributors program archive: Difference between revisions

From OLPC
Jump to navigation Jump to search
No edit summary
(moved loose comments to the end)
Line 1: Line 1:

== Please add reference to Development Wiki ==

Perhaps you could say something like this:

If your interest is primarily on doing some systems level or applications level coding, then join one of the projects on our [http://dev.laptop.org/wiki Hosting Wiki].

== photos ==

You might want to add a link to this photo gallery. It shows how one developer set it up inside an old 286 case. There appear to be two boards in the photos but one is a photo explaining all the interface connectors.

http://daemons.gr/gallery/v/100laptop/

== Hosting Wiki moved - please fix ==

The hosting wiki has moved to another machine. Please fix the link on the main page. I fixed it above. sakai

LAPTOP.ORG PEOPLE, please fix hosting link!!!

:done [[User:Walter|Walter]] 14:16, 7 July 2006 (EDT)


== Hardware Developers' Program ==
Are there any intellectual property restrictions to a private firm beginning production of these machines? Are the details of the [[Hardware specification]] available in machine-readable format?

I would like to start a [[Production Commons]] to begin independent development of this hardware (including modified versions) as soon as possible. Are the design specifications Free as in Freedom so that we may proceed? [[User:Ownut|Ownut]]

== BIOS section should be revised for LinuxBIOS ==

This page should contain a link to [[Upgrading_to_LinuxBIOS]] rather than saying that people shouldn't mess with their BIOSes.

== SELinux ==

SELinux vs 0-day attacks is uninteresting. Attacks which would normally succeed will still succeed under SELinux control, with limited privileges; some possibilities:

* Burn CPU until power goes out (but it dies as well)
* Kill other user processes (i.e. the Web browser being used to take a test)
* Infect the user's account (i.e. if we break in through Firefox or something) and start on every log-in
* Destroy user data
* Constantly write to flash, until it starts to suffer infant mortality (several weeks/months of this maybe, but still bad; plus we're killing power)

Deploying other enhancements like stronger address randomization and stack smash protection will help this in general. Ptmalloc (in glibc) is hardened against heap corruption and double-free() already.

What you can use SELinux for is ''execmem,execmod,execheap,execstack'' protections to control memory execution; but this won't work entirely without an NX bit. Port the emulation from Exec Shield (weak, stack only--usually, sometimes no protection) or PaX (Strong, fine-grained per-page, but more CPU intensive and likely to be a pain due to the very few TLB entries); or run full PaX and possibly GrSecurity.

== Background ==

s/Machine are also being allocated/Machines are also being allocated/

== Goals ==

s/and most easily done/and is most easily done/

== More Talk ==

Please link to the [[USB ethernet adaptors]] page in the paragraph where USB ethernet adaptors are mentioned. -- [[User:probono|probono]]
Please link to the [[USB ethernet adaptors]] page in the paragraph where USB ethernet adaptors are mentioned. -- [[User:probono|probono]]


Line 74: Line 129:


----
----

== Please add reference to Development Wiki ==

Perhaps you could say something like this:

If your interest is primarily on doing some systems level or applications level coding, then join one of the projects on our [http://dev.laptop.org/wiki Hosting Wiki].

== photos ==

You might want to add a link to this photo gallery. It shows how one developer set it up inside an old 286 case. There appear to be two boards in the photos but one is a photo explaining all the interface connectors.

http://daemons.gr/gallery/v/100laptop/

== Hosting Wiki moved - please fix ==

The hosting wiki has moved to another machine. Please fix the link on the main page. I fixed it above. sakai

LAPTOP.ORG PEOPLE, please fix hosting link!!!

:done [[User:Walter|Walter]] 14:16, 7 July 2006 (EDT)


== Hardware Developers' Program ==
Are there any intellectual property restrictions to a private firm beginning production of these machines? Are the details of the [[Hardware specification]] available in machine-readable format?

I would like to start a [[Production Commons]] to begin independent development of this hardware (including modified versions) as soon as possible. Are the design specifications Free as in Freedom so that we may proceed? [[User:Ownut|Ownut]]

== BIOS section should be revised for LinuxBIOS ==

This page should contain a link to [[Upgrading_to_LinuxBIOS]] rather than saying that people shouldn't mess with their BIOSes.

== SELinux ==

SELinux vs 0-day attacks is uninteresting. Attacks which would normally succeed will still succeed under SELinux control, with limited privileges; some possibilities:

* Burn CPU until power goes out (but it dies as well)
* Kill other user processes (i.e. the Web browser being used to take a test)
* Infect the user's account (i.e. if we break in through Firefox or something) and start on every log-in
* Destroy user data
* Constantly write to flash, until it starts to suffer infant mortality (several weeks/months of this maybe, but still bad; plus we're killing power)

Deploying other enhancements like stronger address randomization and stack smash protection will help this in general. Ptmalloc (in glibc) is hardened against heap corruption and double-free() already.

What you can use SELinux for is ''execmem,execmod,execheap,execstack'' protections to control memory execution; but this won't work entirely without an NX bit. Port the emulation from Exec Shield (weak, stack only--usually, sometimes no protection) or PaX (Strong, fine-grained per-page, but more CPU intensive and likely to be a pain due to the very few TLB entries); or run full PaX and possibly GrSecurity.

== Background ==

s/Machine are also being allocated/Machines are also being allocated/

== Goals ==

s/and most easily done/and is most easily done/

Revision as of 12:22, 28 January 2007

Please add reference to Development Wiki

Perhaps you could say something like this:

If your interest is primarily on doing some systems level or applications level coding, then join one of the projects on our Hosting Wiki.

photos

You might want to add a link to this photo gallery. It shows how one developer set it up inside an old 286 case. There appear to be two boards in the photos but one is a photo explaining all the interface connectors.

http://daemons.gr/gallery/v/100laptop/

Hosting Wiki moved - please fix

The hosting wiki has moved to another machine. Please fix the link on the main page. I fixed it above. sakai

LAPTOP.ORG PEOPLE, please fix hosting link!!!

done Walter 14:16, 7 July 2006 (EDT)


Hardware Developers' Program

Are there any intellectual property restrictions to a private firm beginning production of these machines? Are the details of the Hardware specification available in machine-readable format?

I would like to start a Production Commons to begin independent development of this hardware (including modified versions) as soon as possible. Are the design specifications Free as in Freedom so that we may proceed? Ownut

BIOS section should be revised for LinuxBIOS

This page should contain a link to Upgrading_to_LinuxBIOS rather than saying that people shouldn't mess with their BIOSes.

SELinux

SELinux vs 0-day attacks is uninteresting. Attacks which would normally succeed will still succeed under SELinux control, with limited privileges; some possibilities:

  • Burn CPU until power goes out (but it dies as well)
  • Kill other user processes (i.e. the Web browser being used to take a test)
  • Infect the user's account (i.e. if we break in through Firefox or something) and start on every log-in
  • Destroy user data
  • Constantly write to flash, until it starts to suffer infant mortality (several weeks/months of this maybe, but still bad; plus we're killing power)

Deploying other enhancements like stronger address randomization and stack smash protection will help this in general. Ptmalloc (in glibc) is hardened against heap corruption and double-free() already.

What you can use SELinux for is execmem,execmod,execheap,execstack protections to control memory execution; but this won't work entirely without an NX bit. Port the emulation from Exec Shield (weak, stack only--usually, sometimes no protection) or PaX (Strong, fine-grained per-page, but more CPU intensive and likely to be a pain due to the very few TLB entries); or run full PaX and possibly GrSecurity.

Background

s/Machine are also being allocated/Machines are also being allocated/

Goals

s/and most easily done/and is most easily done/

More Talk

Please link to the USB ethernet adaptors page in the paragraph where USB ethernet adaptors are mentioned. -- probono


Regarding the serial cable, please do `s/DB9/DE9/`, and also state whether the connector is Male or Female. A DB9 (D-shell, size B, 9 pins) would be the size of a Parellel port... as opposed to DE9 (D-shell, size E, 9 pins) which is the size of a VGA connector (aka DE15). Sladen 09:33, 31 May 2006 (EDT)

done Walter 17:10, 13 June 2006 (EDT)

I wondered what FOSS means and went to http://www.yahoo.com and looked it up.

It means Free and Open Source Software.

http://en.wikipedia.org/wiki/FOSS


I found the reference to OOM killer obscure. It seems to refer to "Out of Memory Killer," but I don't know what will make it less naive, more sophisticated for OLPC needs.

Details at:

http://linux-mm.org/OOM_Killer http://kerneltrap.org/node/142

Fbkintanar 00:20, 13 June 2006 (EDT)

Right now, the heuristic used by the kernel to choose what to shoot has no information provided by user space: it makes some guesses. Something much better is clearly possible. - jg

I'd say the better thing is to set vm.overcommit_memory=0 and be done with it. - Slamb 12:17, 5 August 2006 (EDT)

"IPv6 support, and service discovery, which are very important to us." I am interested in helping with IPv6, even if just testing for now. Any suggestions where to get started? Specifically, is there any ongoing effort to address service discovery? Is there any interest in instrumenting the stack for systems management? Please point me to an appropriate place, if this is off topic.

Fbkintanar 00:20, 13 June 2006 (EDT)

I think both Marcelo and our SOC student have interest in the stack area.

We're using the Avahi library to do mdns/zeroconf stuff. You can test it on IPv6, and there are missing pieces to connect it with dns for higher scaling. Get in touch with blizzard. -jg


The distribution of the boards with serial numbers on them resonated with an art project which is on the internet.

http://www.autonomousorange.com/EN/index.html


In the Background section is the following.

..., which is aimed at individual FOSS developers or research organizations.

Yet in the How to apply section is the following.

3. Employer

Could you please consider rewording this to say

3. Employer (if any)

or to

3. Employer (if this application is related to any employment you may have)

as at present it does provide the possible interpretation that an applicant must have an employer and that the employer is involved in the application.

I feel that this is important as otherwise the project could come by custom and practice to have a "not representing an organization" discrimination ambience.

fixed. Thanks.