I love all the uneducated comments about "it can't work because... electricity."
There are very large/heavy/fast electric vehicles already. With a vehicle this large and one-off, you could do some pretty cool stuff:
two (or more?) redundant electric motors for front vs rear drive
inductive charging (just park next to a transformer somewhere... haha)
regenerative breaking for increased range in urban areas
extreme high efficiency solar cells for maintaining charge/powering internal devices
gas/diesel backup power plant
Also, with advances in materials, it's possible that armor isn't nearly as heavy for *better* protection.
The real limiting factor will be finding all of the components made exclusively in the US.
... is not always straight forward. This is especially so if you are running in a NAT environment and want to deploy IPv6 and do host resolution correctly. Internally, you want to resolve a host as:
Since this node makes connections to the world, we need to resolve it's address for some services to work:
test1.example.com 2001:DB8::a
Before IPv6 was enabled on this network, this node would be resolved via a generic NAT IP address.
Now you have an asymmetry in how access to/from test1.example.com occurs which means it can work for some people (internal hosts, IPv6 enabled remote hosts) but not for others (IPv4-only sites.) In general, asymmetry in your security with two different paths to the same host means you are less secure. Unfortunately, IPv6 is more than IPv4:IPv4:IPv4:IPv4 and requires some thought and expertise that many shops just don't have.
What about other disruptive technologies extrapolated into the future? With self-driving vehicles, there will be less of a chance that people own their own vehicle and just tap on their smart phone (or whatever they have at that point) for the next available car to pick them up and drop them off where they are going. There should be a law of some kind about future predictions that are of the form "if everything stays the same as today except this one thing then..." which states that the prediction is invalid.
sensitive data shouldn't be written unencrypted to disk in the first place.
Init doesn't make sure programs always run, it makes sure things are run once and never cares about it again. SMF makes sure that things always run.
Solaris 10/11 has a completely rewritten network stack because the old one was getting sorely long in the tooth. As time went on, developers realized that networking has gotten far more complex in enterprise environments than an interface like ifconfig can cope with. As such, there is still an ifconfig but there are many other tools for configuring the network as well.
I stopped using any kind of Solaris once they killed off the OpenSolaris community. I was an unofficial Nexenta developer and very keen on some features (and not so much on other bugs) but overall, the changes made in Solaris/OpenSolaris were done thoughtfully and carefully. At least until Oracle took over. At that point I have no clue except that their NFS appliances are kinda buggy and we are forced to upgrade constantly.
Yes, however, if this person was fired and brought this issue up to management above before going to his lawyers then it's quite possible there is a culture built around it. If that's the case then Oracle isn't quite as shiny as their PR department tries to make them out to be... which I guess is news?
I get extremely disgusted when people confuse discuss and disgust. One is an emotion. One is what women always do. One is an emotion you can see on women's faces when they look towards a slashdot user.
but we need to go further. How cool would it be to have an XMPP based initiation protocol instead of a LAMP stack? Place your jabber server credentials of choice into two devices and then have some form of pairing over XMPP. Initiate a direct connection if possible but use XMPP as a fallback. Extra points for communicating over SSL via generated public-private key pairs per device with a graphical fingerprint for pairing the two devices together.
Slashdot Mirror
I'm sure we will use this technology wisely.
will also never be practical because the filament always burns up. Edison will never make it work.
That's exempt under the politician^H{,,,,,,,,,} narrow law-enforcement clause.
I love all the uneducated comments about "it can't work because ... electricity."
There are very large/heavy/fast electric vehicles already. With a vehicle this large and one-off, you could do some pretty cool stuff:
two (or more?) redundant electric motors for front vs rear drive ... haha)
inductive charging (just park next to a transformer somewhere
regenerative breaking for increased range in urban areas
extreme high efficiency solar cells for maintaining charge/powering internal devices
gas/diesel backup power plant
Also, with advances in materials, it's possible that armor isn't nearly as heavy for *better* protection.
The real limiting factor will be finding all of the components made exclusively in the US.
... is not always straight forward. This is especially so if you are running in a NAT environment and want to deploy IPv6 and do host resolution correctly. Internally, you want to resolve a host as:
test1.example.com 192.168.0.10
test1.example.com 2001:DB8::a
Since this node makes connections to the world, we need to resolve it's address for some services to work:
test1.example.com 2001:DB8::a
Before IPv6 was enabled on this network, this node would be resolved via a generic NAT IP address.
Now you have an asymmetry in how access to/from test1.example.com occurs which means it can work for some people (internal hosts, IPv6 enabled remote hosts) but not for others (IPv4-only sites.) In general, asymmetry in your security with two different paths to the same host means you are less secure. Unfortunately, IPv6 is more than IPv4:IPv4:IPv4:IPv4 and requires some thought and expertise that many shops just don't have.
If anyone thinks you're working at a glacial speed, you are now 4x as fast as you were in the 1990's. Now THAT is progress!
... because my massive vernacular forbids me from uttering, "first post."
... become Amish.
Hmm, how do you backup the crypto keys?
What about other disruptive technologies extrapolated into the future? With self-driving vehicles, there will be less of a chance that people own their own vehicle and just tap on their smart phone (or whatever they have at that point) for the next available car to pick them up and drop them off where they are going. There should be a law of some kind about future predictions that are of the form "if everything stays the same as today except this one thing then ..." which states that the prediction is invalid.
You're doing it wrong ... http://xkcd.com/463/
sensitive data shouldn't be written unencrypted to disk in the first place.
Init doesn't make sure programs always run, it makes sure things are run once and never cares about it again. SMF makes sure that things always run.
Solaris 10/11 has a completely rewritten network stack because the old one was getting sorely long in the tooth. As time went on, developers realized that networking has gotten far more complex in enterprise environments than an interface like ifconfig can cope with. As such, there is still an ifconfig but there are many other tools for configuring the network as well.
I stopped using any kind of Solaris once they killed off the OpenSolaris community. I was an unofficial Nexenta developer and very keen on some features (and not so much on other bugs) but overall, the changes made in Solaris/OpenSolaris were done thoughtfully and carefully. At least until Oracle took over. At that point I have no clue except that their NFS appliances are kinda buggy and we are forced to upgrade constantly.
Yes, however, if this person was fired and brought this issue up to management above before going to his lawyers then it's quite possible there is a culture built around it. If that's the case then Oracle isn't quite as shiny as their PR department tries to make them out to be... which I guess is news?
It's regular overreach for our needed bureaucracy.
Talk about trivial pursuits ... after all, this *is* Slashdot.
Time to get that self-driving car to market!
R...
B......
T..
L....
I get extremely disgusted when people confuse discuss and disgust. One is an emotion. One is what women always do. One is an emotion you can see on women's faces when they look towards a slashdot user.
That's three you discussing swine!
... white people are racist
how dare you say white people are racist!
https://git-annex.branchable.com/assistant/
Wow, that's pretty cool. It even supports storing an encrypted copy on a remote server as well as storage on common cloud platforms.
but we need to go further. How cool would it be to have an XMPP based initiation protocol instead of a LAMP stack? Place your jabber server credentials of choice into two devices and then have some form of pairing over XMPP. Initiate a direct connection if possible but use XMPP as a fallback. Extra points for communicating over SSL via generated public-private key pairs per device with a graphical fingerprint for pairing the two devices together.