The problem is most people would would rather fly.
Unless....
How (in my oppionion, not talking subway/commuter) to make the train system in the US compete with the airlines.
Trains have to run every 2 two 3 hours.
There should be reletivly long distances between stops (Event throught trains can be faster than cars, too many stops on a route make them slower)
Most Importantly, all trains should be car trains. This is one place the airlines can not compete.
So basically, I should be able to get to a place (or close to a place) with my car, in the same amount of time it would take to drive or a little shorter. Plus the price would be similar to the cost of driving.
Kind of, but the track itself wouldn't lower, the car would. I was thinking a bus like vehicle that would lower all the way to the ground, and you could walk on without steps.
Here is a novel idea. Rapid transit trains suspended from their tracks instead of on them.
Why would that be cool. Well give the train the ability to lower to the ground (a jack like mechanism I'm guessing). Run the tracks over roads in the city.
So it basicly works like the bus system, but only lowers in the bus stop. This would avoid traffic jams and street lights.
The tracks might be on the ugly side. They might look a lot like roller coaster tracks. Power lines would have to be run over them, and street lights might have to be adjusted.
Also the tracks would have to be pretty far from the ground so that tall truck could go under the train cars.
Videolan is realy cool! Expecialy if you want to stream video across your lan. The only problem is it doesn't really do much as far as managing the content for you.
MythTV on the other hand has nice menus for browsing the movie collection and a lot of nice features including remote control support (for instance the one that comes with a haupag 350).
MythTV is something your wife, parents, or kids could use with very little difficulty, as long as the setup is already done.
Head down to a mall and set up a user interface test. Call the mall first and ask if they will donate an area to the activity. Take machines down and set up tables.
Ask passers by to take a survey. Give them a task to complete. After they try it, have them fill out a survey about the experience. Collect the surveys on a website so open source developers can access the info.
Unless my next car has a CVT. The Toyota Prius is actualy looking pretty goot at this point.
Why are Ford and GM so far behind? They don't have CVT's. They are just talking about Hybrids, I'm not holding my breath. Toyota and Honda have had Hybrid's and CVT transmisions for years now.
I'm thinking that in the future a lot of our energy will be grown.
Farmers with large biomass generators, biobatteries, methane tanks will grow energy crops or raise animals. Woody crops for things like biomass generators, carrot or potatoe like vegatables for biobatteries. Animal waste will be used for methane.
Maybe small consumer versions will be available to help dispose of lawn waste. Extra energy could be sold back to the grid.
Another nice outcome would be less need to subsidize farms, because of high demand for energy. The electric companies would be more a distibuter, and less a producer.
I believe we all have the ultimate solor collectors in our yards already. The grass in the other foilage.
I've seen articles about bio-batteries that use bacteria to break down organic matter, and make electricity.
I'm guessing in about ten years there will be a product that takes yard clippings, and leaves, and other foilage, and produces energy. Fertilizer will be a biproduct.
In the future we would grow our energy supply. We already use fossil fules. They were grown millions of years ago.
Most end users don't understand drive maps anyway. An NFS server and a bunch of Linux boxes with home mounted remote is a lot easier to manage.
No more "Well you should of saved your important files on the network drive!".
What a Corporate Linux desktop needs is a file sharing utility built into the file manager that is easy for end users to use.
User A right clicks on folder, and shares it. Folder in now called shared work area. Address book pops up and prompts users to select other users that are allowed to access files. Other users receive email with invitation to work area.
Users have a shared work area manager that list other shares they have access to + manage them like bookmarks. Shares are listed by the user in charge, and name. Machine is not important. Storage capacity is determined by quota's + resides on same drive as owners home directory
Good ldap support is important for all this to work correctly
Maybe what would be nice would be a resolution independent toolkit. Maybe QT or GTK could be modified for this. All widget sizes would be specified in distance units such as Centimeters or inches (Programers Choice). No mater what your res was all programs would pop up at their normal size. Then add the ability to do tranformations to the coordinate system on the fly.
Some nice features could then be added to the desktop. For instance. Miniturizing programs (Mini caculators, text editors, any program) that can still be interacted with, and doesn't require extra programming. A slider could be added to the window manager to scale the app.
This would probably require hardware acceleration like OS X. But instead of just using it for eye candy, make it usefull.
I wonder how much energy return they would get if they used a fuel cell instead of a heat engine. Would the efficeincy offset the extra cost of the fuel cell?
Also a smaller version of this would be nice for yard waste. I could just think of my yard as a solar energy collector. No need to waste money on fertilizer.
Maybe my use of the word thin client is incorrect, or confusing (Maybe skinny:). This install option would use minimal disk space. So I could use an old 10M drive if I had to. Basically an easy way to turn a stack of old machines (with good harddrives) into usefull machines
The install would allow me to pick a primary server. It should also give me the option of using a remote font server.
I understand why LTSP would be desireable for a number of people, and it would be nice if it was included with Redhat. The only problem is where I work, I'm not in the department that controls the dhcp server and the server is windows 2000.
I'm assuming a lot of people are in the same boat I'm in.
I sometimes set up machines with minimal installs to use as an X server, but a minimal install with redhat is hard to accomplish.
Thanks
Adam
Here is a quick list of features I'm wishing for 8.1.
1. A default ldap server setup that works. Modify all relevent system tools with the option of updating the ldap database instead of config files.
2. A decent hard drive management utility. Try to default to an all lvm system when possible, but allow for old style
3. New install type: X windows thin client.
4. Better printing. 8.0's printing subsystem seems to be a little flakey
I wonder how much unused energy I rake off my yard every fall and send to the city compost pile.
What I need is a back yard composter/fertilizer dispenser/generator that I can throw leaves, grass (actually I mulch these now), kitched scaps (sugar cubes, carrots, etc).
I sell the extra energy back to the power grid, and spread the fertilizer on my yard.
No wait, this would make to much ecological/economic sense, I must be some kind of hippie, tree hugger, freak.
Now What they need is a camera small enough to fit in your Iris. Get rid of that extra radio equipment since the chip can connect directly to the camera. Ad some cool night vision and Infared capabilities, maybe zoom. Then make it comparably priced as laser treatment. Only then I will get surgery for my myopia.
Here is an Idea for easier security management through ACL's.
Add a file system capability mask. This would be similar to the Group and Other file permissions, but would block those permissions.
For instance droping the "rw" capability from the "other" and "group" masks would cause this proccess, and all it's children to be denied access to files that it doesn't own (services should not be run as root of course), but still access files owned by it's user or files/directories explicitly given access vi ACL's. This way a user could grant access to everyone for his/her directory, but system process couldn't be coerced into reading that directory, or any directory. An admin would have to explicitly grant access for a system service. The whole/bin and/usr file systems would automaticly be traversable, but directory listings,file reads, and file writes would be impossible for such a proccess.
Is there any project doing this? Is this even a good idea?
Why stop at Gnome and KDE.
Why can't we make the theme engine work for java, tk, fltk, Motif(Choose any free implementation), Athena, Xaw, Etc. Providing a unified look, although not always a unified feel for all the applications.
I get the feeling that KDE theming is more advanced so should be used as the
starting point for the theming engine. I believe KDE themes are based on replacable theme engines(libraries) instead of images sets, different drawing libraries allow a large number of color combinations to be choosen, and be applied to almost any theme. Correct me if I am wrong on this points
There should be a choice of C or C++ (Maybe even Java) theme libraries. This will make both C and C++ programmers happy.
This way we can have a consistent look without being forced to use the same languages, or libraries. After having a unified theme, further integration such as file dialogs, drag and drop, file system abstraction can be open to discussion.
Why stop at Gnome and KDE.
Why can't we make the theme engine work for java, tk, fltk, Motif(Choose any free implementation), Athena, Xaw, Etc. Providing a unified look, although not always a unified feel for all the applicationns.
I get the feeling that KDE theming is more advanced so should be used as the starting point for the theming engine. I believe KDE themes are based on replacable theme engines(libraries) instead of images sets, different drawing libraries allow a large number of color combinations to be choosen, and be applied to almost any theme. Correct me if I am wrong on this points
There should be a choice of C or C++ (Maybe even Java) theme libraries. This will make both C and C++ programmers happy.
This way we can have a consistent look without being forced to use the same languages, or libraries. After having a unified theme, further integration such as file dialogs, drag and drop, file system abstraction can be open to discussion.
Slashdot Mirror
The problem is most people would would rather fly.
Unless....
How (in my oppionion, not talking subway/commuter) to make the train system in the US compete with the airlines.
Trains have to run every 2 two 3 hours.
There should be reletivly long distances between stops (Event throught trains can be faster than cars, too many stops on a route make them slower)
Most Importantly, all trains should be car trains. This is one place the airlines can not compete.
So basically, I should be able to get to a place (or close to a place) with my car, in the same amount of time it would take to drive or a little shorter. Plus the price would be similar to the cost of driving.
If more laws are enacted like this, maybe we should demand a law where anybody holding a public office should be required to give a dna sample.
His comments may be inflamitory, but in the long run, the comments will be good for Gnome.
Nothing like some harsh criticism about something you worked hard on to make you work even harder.
You have to have thick skin to be an open source developer. I don't know how they do it sometimes.
Kind of, but the track itself wouldn't lower, the car would. I was thinking a bus like vehicle that would lower all the way to the ground, and you could walk on without steps.
Here is a novel idea. Rapid transit trains suspended from their tracks instead of on them.
Why would that be cool. Well give the train the ability to lower to the ground (a jack like mechanism I'm guessing). Run the tracks over roads in the city.
So it basicly works like the bus system, but only lowers in the bus stop. This would avoid traffic jams and street lights.
The tracks might be on the ugly side. They might look a lot like roller coaster tracks. Power lines would have to be run over them, and street lights might have to be adjusted.
Also the tracks would have to be pretty far from the ground so that tall truck could go under the train cars.
Just thought it was an interesting idea.
Videolan is realy cool! Expecialy if you want to stream video across your lan. The only problem is it doesn't really do much as far as managing the content for you.
MythTV on the other hand has nice menus for browsing the movie collection and a lot of nice features including remote control support (for instance the one that comes with a haupag 350).
MythTV is something your wife, parents, or kids could use with very little difficulty, as long as the setup is already done.
Here is an idea for your local LUG.
Nothing to do on a weekend?
Head down to a mall and set up a user interface test. Call the mall first and ask if they will donate an area to the activity. Take machines down and set up tables.
Ask passers by to take a survey. Give them a task to complete. After they try it, have them fill out a survey about the experience. Collect the surveys on a website so open source developers can access the info.
Sound like a good idea?
I'm no physicist, but I was wondering, couldn't these mini electro-mechanical devices be a more efficient way to make electricity from heat.
If I remember correctly heat is manifest as molecular motion, or radiation.
So couldnt a small enough array of MEM's make electricity out of this molecular motion while cooling at the same time?
I'm thinking if this is the case, it could result in a lot of nice applications in the future.
For instance super fuel efficent electric generators, Freezers/ air conditioning that generates electricity, etc
Although this sounds like it would break some law of physics.
Are you saying I'm redundant, I repeat myself, I say things over and over?
I guess I didn't search the internet long enough to find the Saturn. How long has it had a CVT?
Unless my next car has a CVT. The Toyota Prius is actualy looking pretty goot at this point.
Why are Ford and GM so far behind? They don't have CVT's. They are just talking about Hybrids, I'm not holding my breath.
Toyota and Honda have had Hybrid's and CVT transmisions for years now.
I'm thinking that in the future a lot of our energy will be grown.
Farmers with large biomass generators, biobatteries, methane tanks will grow energy crops or raise animals. Woody crops for things like biomass generators, carrot or potatoe like vegatables for biobatteries. Animal waste will be used for methane.
Maybe small consumer versions will be available to help dispose of lawn waste. Extra energy could be sold back to the grid.
Another nice outcome would be less need to subsidize farms, because of high demand for energy. The electric companies would be more a distibuter, and less a producer.
I believe we all have the ultimate solor collectors in our yards already. The grass in the other foilage.
I've seen articles about bio-batteries that use bacteria to break down organic matter, and make electricity.
I'm guessing in about ten years there will be a product that takes yard clippings, and leaves, and other foilage, and produces energy. Fertilizer will be a biproduct.
In the future we would grow our energy supply. We already use fossil fules. They were grown millions of years ago.
Most end users don't understand drive maps anyway. An NFS server and a bunch of Linux boxes with home mounted remote is a lot easier to manage.
No more "Well you should of saved your important files on the network drive!".
What a Corporate Linux desktop needs is a file sharing utility built into the file manager that is easy for end users to use.
User A right clicks on folder, and shares it. Folder in now called shared work area. Address book pops up and prompts users to select other users that are allowed to access files. Other users receive email with invitation to work area.
Users have a shared work area manager that list other shares they have access to + manage them like bookmarks. Shares are listed by the user in charge, and name. Machine is not important. Storage capacity is determined by quota's + resides on same drive as owners home directory
Good ldap support is important for all this to work correctly
Maybe what would be nice would be a resolution independent toolkit. Maybe QT or GTK could be modified for this. All widget sizes would be specified in distance units such as Centimeters or inches (Programers Choice). No mater what your res was all programs would pop up at their normal size. Then add the ability to do tranformations to the coordinate system on the fly.
Some nice features could then be added to the desktop. For instance. Miniturizing programs (Mini caculators, text editors, any program) that can still be interacted with, and doesn't require extra programming. A slider could be added to the window manager to scale the app.
This would probably require hardware acceleration like OS X. But instead of just using it for eye candy, make it usefull.
This is funny. I noticed if you search for oracle the third result if very similar.
No they are not biased at all!!
I wonder how much energy return they would get if they used a fuel cell instead of a heat engine. Would the efficeincy offset the extra cost of the fuel cell?
Also a smaller version of this would be nice for yard waste. I could just think of my yard as a solar energy collector. No need to waste money on fertilizer.
After 4 years, does anybody know if there is/was a lawsuit invoking the DMCA against sombody who is actually pirating content?
The install would allow me to pick a primary server. It should also give me the option of using a remote font server.
I understand why LTSP would be desireable for a number of people, and it would be nice if it was included with Redhat. The only problem is where I work, I'm not in the department that controls the dhcp server and the server is windows 2000. I'm assuming a lot of people are in the same boat I'm in.
I sometimes set up machines with minimal installs to use as an X server, but a minimal install with redhat is hard to accomplish.
Thanks Adam
Here is a quick list of features I'm wishing for 8.1.
1. A default ldap server setup that works. Modify all relevent system tools with the option of updating the ldap database instead of config files.
2. A decent hard drive management utility. Try to default to an all lvm system when possible, but allow for old style
3. New install type: X windows thin client.
4. Better printing. 8.0's printing subsystem seems to be a little flakey
What I need is a back yard composter/fertilizer dispenser/generator that I can throw leaves, grass (actually I mulch these now), kitched scaps (sugar cubes, carrots, etc).
I sell the extra energy back to the power grid, and spread the fertilizer on my yard.
No wait, this would make to much ecological/economic sense, I must be some kind of hippie, tree hugger, freak.
Now What they need is a camera small enough to fit in your Iris. Get rid of that extra radio equipment since the chip can connect directly to the camera. Ad some cool night vision and Infared capabilities, maybe zoom. Then make it comparably priced as laser treatment. Only then I will get surgery for my myopia.
Here is an Idea for easier security management through ACL's.
/bin and /usr file systems would automaticly be traversable, but directory listings,file reads, and file writes would be impossible for such a proccess.
Add a file system capability mask. This would be similar to the Group and Other file permissions, but would block those permissions.
For instance droping the "rw" capability from the "other" and "group" masks would cause this proccess, and all it's children to be denied access to files that it doesn't own (services should not be run as root of course), but still access files owned by it's user or files/directories explicitly given access vi ACL's. This way a user could grant access to everyone for his/her directory, but system process couldn't be coerced into reading that directory, or any directory. An admin would have to explicitly grant access for a system service. The whole
Is there any project doing this? Is this even a good idea?
Why stop at Gnome and KDE. Why can't we make the theme engine work for java, tk, fltk, Motif(Choose any free implementation), Athena, Xaw, Etc. Providing a unified look, although not always a unified feel for all the applications.
I get the feeling that KDE theming is more advanced so should be used as the starting point for the theming engine. I believe KDE themes are based on replacable theme engines(libraries) instead of images sets, different drawing libraries allow a large number of color combinations to be choosen, and be applied to almost any theme. Correct me if I am wrong on this points
There should be a choice of C or C++ (Maybe even Java) theme libraries. This will make both C and C++ programmers happy.
This way we can have a consistent look without being forced to use the same languages, or libraries. After having a unified theme, further integration such as file dialogs, drag and drop, file system abstraction can be open to discussion.
OK, I'm not sure exactly how I Managed to attach this to the setti at home post, I will cut and past it into the correct story, I hope Sorry.
Why stop at Gnome and KDE.
Why can't we make the theme engine work for java, tk, fltk, Motif(Choose any free implementation), Athena, Xaw, Etc. Providing a unified look, although not always a unified feel for all the applicationns.
I get the feeling that KDE theming is more advanced so should be used as the starting point for the theming engine. I believe KDE themes are based on replacable theme engines(libraries) instead of images sets, different drawing libraries allow a large number of color combinations to be choosen, and be applied to almost any theme. Correct me if I am wrong on this points
There should be a choice of C or C++ (Maybe even Java) theme libraries. This will make both C and C++ programmers happy.
This way we can have a consistent look without being forced to use the same languages, or libraries. After having a unified theme, further integration such as file dialogs, drag and drop, file system abstraction can be open to discussion.