The config file format shouldn't need to be modified. Obviously they're already machine-readable! The problem is that people write myopic GUI config tools. They should be using something like augeas.
Augeas is a configuration editing tool. It parses configuration files in their native formats and transforms them into a tree. Configuration changes are made by manipulating this tree and saving it back into native config files.
Augeas is: An API provided by a C library A command line tool to manipulate configuration from the shell (and shell scripts) Language bindings to do the same from your favorite scripting language Canonical tree representations of common configuration files A domain-specific language to describe configuration file formats
Augeas goals: Manipulate configuration files safely, safer than the ad-hoc techniques generally used with grep, sed, awk and similar mechanisms in scripting languages Provide a local configuration API for Linux Make it easy to integrate new config files into the Augeas tree
IANAL, but the GPL does not affect your rights as the user of a piece of software. It affects your rights as a distributor of that software or derivatives of it.
The ASUS RT-N16, Linksys WRT610N, and Netgear WNR3500L look promising. They're all supported by dd-wrt and in theory could work with openwrt. The Asus is some nice hardware for $90.
Interesting, because according to the reviews on that newegg page those are a revision of the WGR614 that don't work with dd-wrt, openwrt, etc. IF your experience is different I'd love to find out details.
Since I worked on the presentation with Sean for the days he was here in SF, let me give you my view and sean's view. That way we won't get into some version of the telephone game.
I won't go over 1& 2 but I'll cover #3 since rasters perception has a bit of color added to it. Only a tiny bit and he's entitled to that color commentary, I'll just add what Sean and I, as authors of the presentation, had as our message.
Our biggest challenge was to make a choice about how to spend the balance of 2009.
There were two paths: A: Fulfill our promises on FreeRunner and launch GTA03 B: Fulfill our promises on FreeRunner and launch project B.
We will talk more about project B in the coming months, but these salient facts should be able to guide any budding executives out there.
1. GTA03 was in constant flux as a design. 2. GTA03 schedule was consequently always slipping. 3. The resources required for GTA03 are 3X those required for Project B. 4. We don't have 3X.
So, we picked plan B.
Now comes the question, what about GTA03? how do we get there? And when? and what is it?
Well my basic argument was and is this:
First we attend to the issues that still remain with the GTA02. That's why the VP of marketing ( of all people) is working on the buzz fix problem. Second we complete project B. When we've done that, then we get to eat dessert. Essentially, I made the same argument I heard so many times on this list: "How do expect us to buy a GTA03 when you've yet to deliver on all the promise of FreeRunner?" And I took the arguments I heard from disty seriously, "how do you expect us to buy FR, when GTA03 is right around the corner?" And I accepted the arguments I heard from Engineers I respect who questioned the viability of the GTA03 in the market place. All of those arguments said "put a bullet in its brain pan!"
So, what about GTA03? As it was defined, it is dead. So how do we get to a new GTA03? Two requirements: continue to improve GTA02; deliver on project B. What is GTA03 and when do we get there? There are a number of independent efforts out there that are pitching me ideas for GTA03. I talked to sean a bit about this and I'd like to try to open up more of the design process and the marketing process to the community. Perhaps on a separate list. Some of these discussions have already started.
What can you do to help? 1. Move GTA02 code upstream. 2. Stay Involved. 3. Continue work on applications 4. Buy a FreeRunner. 5. Get involved in GTA03 discussions
No, that's now how it works. You provide only your username, not your password, to the individual websites. The entire process is explained in the wikipedia article.
I'm seconding Snake Wrangling for Kids. I'm really impressed by the amount of care the author has put into it. The text has already been updated for Python 3 (the Python 2 version is still available). There are separate editions for Windows, OS X, and linux so that the screenshots will match the system the reader is using.
Can you leave your phone turned on for 24 hours without charging it? I'd love to get an Openmoko running the Qtopia or Android stack if they have working power management.
Now that AMD isn't competitive, Intel is taking their time to roll out new technology. It may be mid-2009 before desktop i7 parts show up. According to Ars Technica:
"AMD will instead launch Shanghai in all server brackets simultaneously, from one-socket to four-socket. Intel, in contrast, plans to ramp Nehalem rather leisurely. Dual-socket Nehalem (Gainestown) will launch sometime in the first quarter of 2009, with Beckton (octal core) arriving in the first half of next year... Current predictions suggest we won't see a wide desktop presence for Nehalem until the second or third quarter of 2009"
I'll have to check this out. A similar program that hasn't gotten much attention is Elisa. There are packages for Windows and many linux distributions.
Comcast and Level 3 communications (who happens to host Netflix) had a peering agreement, which Level 3 violated.
That description of the Comcast and Level 3 dispute is too simplified. You might find two articles informative.
The config file format shouldn't need to be modified. Obviously they're already machine-readable! The problem is that people write myopic GUI config tools. They should be using something like augeas.
Augeas is a configuration editing tool. It parses configuration files in their native formats and transforms them into a tree. Configuration changes are made by manipulating this tree and saving it back into native config files.
Augeas is:
An API provided by a C library
A command line tool to manipulate configuration from the shell (and shell scripts)
Language bindings to do the same from your favorite scripting language
Canonical tree representations of common configuration files
A domain-specific language to describe configuration file formats
Augeas goals:
Manipulate configuration files safely, safer than the ad-hoc techniques generally used with grep, sed, awk and similar mechanisms in scripting languages
Provide a local configuration API for Linux
Make it easy to integrate new config files into the Augeas tree
IANAL, but the GPL does not affect your rights as the user of a piece of software. It affects your rights as a distributor of that software or derivatives of it.
The ASUS RT-N16, Linksys WRT610N, and Netgear WNR3500L look promising. They're all supported by dd-wrt and in theory could work with openwrt. The Asus is some nice hardware for $90.
Which came first, GPL or CDDL? Sun knew what they were doing when they choose the license for the opensolaris kernel.
'mount -t nfs -o intr' and 'umount -l' should solve your problems.
Yeah, why can't there be one way to do it like on Windows.
$ lsb_release -c
Codename: ibex
It sounds like you'd be interested in at Perl/Linux, a linux distribution where ALL programs are written in perl.
Interesting, because according to the reviews on that newegg page those are a revision of the WGR614 that don't work with dd-wrt, openwrt, etc. IF your experience is different I'd love to find out details.
There's a lot of alternatives in between pure python and pure C or fortran that can be speedy to write and run.
Do you mean Ubuntu 8.04? 9.04 includes openssh 5.1
Reposting from http://lists.openmoko.org/pipermail/community/2009-April/044915.html
Sean's speech at ESC about making a 3G device:
Since I worked on the presentation with Sean for the days he was here in
SF, let me give you my view and sean's view. That way we won't get into
some version of the telephone game.
Sean discussed three things at OpenExpo.
1. Our successes.
2. Our mistakes.
3. Our challenges
I won't go over 1& 2 but I'll cover #3 since rasters perception has
a bit of color added to it. Only a tiny bit and he's entitled
to that color commentary, I'll just add what Sean and I, as authors
of the presentation, had as our message.
Our biggest challenge was to make a choice about how to spend the
balance of 2009.
There were two paths:
A: Fulfill our promises on FreeRunner and launch GTA03
B: Fulfill our promises on FreeRunner and launch project B.
We will talk more about project B in the coming months, but these
salient facts should be able to guide any budding executives out there.
1. GTA03 was in constant flux as a design.
2. GTA03 schedule was consequently always slipping.
3. The resources required for GTA03 are 3X those required for Project B.
4. We don't have 3X.
So, we picked plan B.
Now comes the question, what about GTA03? how do we get there? And when?
and what is it?
Well my basic argument was and is this:
First we attend to the issues that still remain with the GTA02. That's
why the VP of marketing ( of all people) is working on the buzz fix
problem. Second we complete project B. When we've done that, then we
get to eat dessert. Essentially, I made the same argument I heard so
many times on this list: "How do expect us to buy a GTA03 when you've
yet to deliver on all the promise of FreeRunner?" And I took the
arguments I heard from disty seriously, "how do you expect us to buy FR,
when GTA03 is right around the corner?" And I accepted the arguments I
heard from Engineers I respect who questioned the viability of the GTA03
in the market place. All of those arguments said "put a bullet in its
brain pan!"
So, what about GTA03? As it was defined, it is dead. So how do we
get to a new GTA03? Two requirements: continue to improve GTA02; deliver
on project B. What is GTA03 and when do we get there? There are a number
of independent efforts out there that are pitching me ideas for GTA03.
I talked to sean a bit about this and I'd like to try to open up more
of the design process and the marketing process to the community.
Perhaps on a separate list. Some of these discussions have already started.
What can you do to help?
1. Move GTA02 code upstream.
2. Stay Involved.
3. Continue work on applications
4. Buy a FreeRunner.
5. Get involved in GTA03 discussions
$ lsb_release -d /usr/sbin/cupsd
Description: Ubuntu 8.10
$ ps -ef | grep cupsd
root 6860 1 0 Feb08 ? 00:00:00
One place is the Schoolforge mailing list.
Unless I'm mistaken, the systems you linked to are based on the Via's Eden, not their new Nano processors.
If someone hands her a Microsoft Word document, she double-clicks it and it opens in OpenOffice.org.
Sure, there haven't been any video problem on Windows recently.
How many of these problem are solved by going to System->Preferences->Appearance->Visual Effects and choosing None?
Shake. Con Colivas defrag. ext4 will ship with a defrag tool.
No, that's now how it works. You provide only your username, not your password, to the individual websites. The entire process is explained in the wikipedia article.
I'm seconding Snake Wrangling for Kids. I'm really impressed by the amount of care the author has put into it. The text has already been updated for Python 3 (the Python 2 version is still available). There are separate editions for Windows, OS X, and linux so that the screenshots will match the system the reader is using.
Can you leave your phone turned on for 24 hours without charging it? I'd love to get an Openmoko running the Qtopia or Android stack if they have working power management.
Now that AMD isn't competitive, Intel is taking their time to roll out new technology. It may be mid-2009 before desktop i7 parts show up. According to Ars Technica: "AMD will instead launch Shanghai in all server brackets simultaneously, from one-socket to four-socket. Intel, in contrast, plans to ramp Nehalem rather leisurely. Dual-socket Nehalem (Gainestown) will launch sometime in the first quarter of 2009, with Beckton (octal core) arriving in the first half of next year... Current predictions suggest we won't see a wide desktop presence for Nehalem until the second or third quarter of 2009"
I'll have to check this out. A similar program that hasn't gotten much attention is Elisa. There are packages for Windows and many linux distributions.