Or possibly some attempt at stopping arbitrarily many of their customers setups from breaking... If you've got enough poorly configured machines, it might be easier to ensure that the servers they are looking for remain available, rather than trying to fix _all_ of them immediately... Especially if they're mission-critical systems...
I'll experiment with using DVCS on a project soon and will see if the shortcomings are less significant than I am making out.
One possibility, if you want a low-time-cost way to try a DVCS, is to try SVK on an existing svn server.
To make it easy, I've copied and paraphrased the quickstart I was given for the first time I was introduced to SVK...
I'll assume you've downloaded and installed SVN and SVK.
First step is mirroring: user@host$ svk mirror svn://repository/url//mirror/project Committed revision 209.
Sync the whole SVN repository locally: user@host$ svk sync//mirror/project Syncing svn://repository/url Retrieving log information from 1 to 4 Committed revision 210 from revision 1. Committed revision 211 from revision 2. Committed revision 212 from revision 3. Committed revision 213 from revision 4.
Has the mirror happened? user@host$ svk mirror --list Path Source//mirror/project svn://repository/url
Now, I find the naming of the 'mirror' strangely counter-intuitive. The mirror doesn't get modified by your changes until the server gets modified. It is truly a mirror, which is why I say it's 'strangely' counter intuitive.
The implication of this is that whether or not you make a local branch affects how you commit. To simplify the thinking, I'll ask a question. Take the option appropriate to the answer you give. The question is - when you commit changes, would you (a) like to commit directly back to the mirror, or (b) to commit to a local repository, and only later back to a mirror?
If you prefer to work in mode (a), you can do:
user@host$ svk co//mirror/project Syncing//mirror/project(/mirror/project) in/home/user/code/project to 213. A project/documents A project/documents/StoryOverview.doc A project/documents/StoryChapters.html
And edit the files... Type 'svk ci' to commit your changes. Your changes will affect the mirror immediately, and therefore the *server* at svn://repository/url immediately.
If you have a preference for (b), you should:
user@host$ svk copy//mirror/project//local/project Waiting for editor... Committed revision 216.
user@host$ svk co//local/project Syncing//local/project(/local/project) in/home/user/code/project to 216. A project/documents A project/documents/StoryOverview.doc A project/documents/StoryChapters.html
Now, when you type 'svk ci' commits are made only to the *local* repository. To push them back to the main repository (on the server) you need to type 'svk push'. To freshen your local copy with changes from the server, type 'svk pull'.
Notes: option (a) corresponds to using SVK as a CVCS frontend to SVN, while option (b) corresponds to using it as a DVCS frontend instead, so it's easy to switch between behaviours.
This quickstart misses the need to run svk sync occasionally, but it should get you up and running, anyway...
meanwhile, if you're using SVN on Unix/Linux boxes, you might want to check out svk. All the advantages of a DVCS, but with the central repo being a (possibly pre-existing) standard svn server.
(I put the disclaimer about unix boxes in because the last time I had a colleague on a Mac running SVK, there were some minor issues around binary files and line ending munging... I don't know if they are resolved already or not...)
At first you say it'd be difficult to get enough dirt to make the keys stick under normal use, and then the very next sentence you said the keys started sticking after a few months. Are you using them in a factory or in the desert or something? What is so abnormal about your environment that it makes the keys stick? Hmm... When I read that, it sounded to me like he's saying "it's difficult to get dirt in there, and yet the keys still stick, so the cause is probably something else".
Decimal floats are a wasteful misunderstanding of what you're working with. Interesting... How do you propose to calculate division of decimals without the use of decimal floats?
I think the long-term solution is to add a flag to DNS, indicating that mail from a specific domain will allways come from a set of servers on specific emails and all others (e.g. relayed) should be silently dropped. It sounds like you're describing SPF. From the SPF Intro:
Even more precisely, SPFv1 allows the owner of a domain to specify their mail sending policy, e.g. which mail servers they use to send mail from their domain.... If, e.g., the message comes from an unknown server, it can be considered a fake.
Sounds like Brad Templeton's How to fix DNS idea. The idea has been around for a long time; other than economic blockading from the current financial stakeholders, I don't know why is hasn't had more consideration...
I don't see anything missing from Evolution that Outlook was able to do, the last time I used that. Fair point - it has been a while since I looked at Evolution, and Kontact similarly can do the meeting-request stuff these days.
What do office drones want that Evolution doesn't do? The missing link so far has been hosting and updating server-based calendars, the MS Exchange part of the job not the Outlook part. Even Evolution's documentation says that "the Free/Busy feature only works with Microsoft Exchange servers..." CalDAV and other attempts at a protocol have been made, but nothing has emerged as a stand out...
Also, like yourself, I haven't been following this very closely recently - there may be an answer now, that just doesn't stand out very well in Aptitude...
(Actually, just remembering: the other one I've been asked about is shared addressbooks; LDAP works, but is almost completely uneditable by the end user, who is usually the secretary given a pile of business cards to enter...)
The key point is that for a single roadwarrior, most things can be made to work... But for a larger office, _sharing_ info (calendars, addressbooks, delegated email, etc) can be an issue.
The office drones I know just want to browse the web and send e-mails & IMs... One thing you missed, and office drones have regularly mentioned to me: calendaring, and specifically calendar sharing. If there's one thing drones like, it's knowing when they can schedule meetings. There are some attempts at calendaring on Linux, but I haven't noticed a cleanly working solution yet, although some of the pieces appear to finally be in place...
Umm, from that site's data, Russia's share has _fallen_ over the last 26 years; from a high of almost 5% to today's 2.69%.... And USA has been flat at around 21% the entire time; China grew from 3% to 14%, India from 3% to 6%... And France, Spain and Italy have taken minor falls from 4-ish percent to 3-ish percent over that time... How does that equate to "getting more evenly distributed"?
It's designed for kids and people who have never used a computer before. Umm, because I build computers for people who have never used computers before? Because a simple, easy-to-use UI would be useful for kiosk-type applications? Because I want a nongeek-friendly interface for the box hooked up to my TV?
Just because you can only see one use for a particular application, doesn't mean that that's all it's good for.
For what it's worth, it appears to be great as a blogging tool; Alex seems to like the way it works for the blogging functions, but the forum functions are what are generally found to be "quirky"...
If you're using vim, you can save yourself three keystrokes: Vjjjjjjjy p And if you're grabbing the whole document, you can further shorten this to: Gygg p
The Thinkpads have been pretty good about this, I remember from back when I had a T21... But I've currently had access to Acer, HP and Asus laptops, and for all of them the Fn-VolumeKeys do nothing in firmware... Actually, from poking around on my Asus, it appears that they don't even send keyboard events, they send ACPI button-press events!
Fortunately for me, my Asus comes with a hardware potentiometer/mute function, but the Acers and HP machines I've seen don't have that, and you can't do volume control until after the OS is up. On the Acers, the mute is actually not activated until after boot (in Windows, at least), so if you have the volume above minimum, mute, then power off, the startup sounds are played before the muting is applied...
It's deeper than the operating system, it goes right to the core of the system. The best explanation I've seen of it is from Ross Anderson's Trusted Computing FAQ.
TC provides a computing platform on which you can't tamper with the application software, and where these applications can communicate securely with their authors and with each other. The original motivation was digital rights management (DRM): Disney will be able to sell you DVDs that will decrypt and run on a TC platform, but which you won't be able to copy. The music industry will be able to sell you music downloads that you won't be able to swap. They will be able to sell you CDs that you'll only be able to play three times, or only on your birthday. All sorts of new marketing possibilities will open up.
TC will also make it much harder for you to run unlicensed software. In the first version of TC, pirate software could be detected and deleted remotely. Since then, Microsoft has sometimes denied that it intended TC to do this, but at WEIS 2003 a senior Microsoft manager refused to deny that fighting piracy was a goal: `Helping people to run stolen software just isn't our aim in life', he said. The mechanisms now proposed are more subtle, though. TC will protect application software registration mechanisms, so that unlicensed software will be locked out of the new ecology. Furthermore, TC apps will work better with other TC apps, so people will get less value from old non-TC apps (including pirate apps). Also, some TC apps may reject data from old apps whose serial numbers have been blacklisted. If Microsoft believes that your copy of Office is a pirate copy, and your local government moves to TC, then the documents you file with them may be unreadable. TC will also make it easier for people to rent software rather than buy it; and if you stop paying the rent, then not only does the software stop working but so may the files it created. So if you stop paying for upgrades to Media Player, you may lose access to all the songs you bought using it.
For years, Bill Gates has dreamed of finding a way to make the Chinese pay for software: TC looks like being the answer to his prayer.
There are many other possibilities. Governments will be able to arrange things so that all Word documents created on civil servants' PCs are `born classified' and can't be leaked electronically to journalists. Auction sites might insist that you use trusted proxy software for bidding, so that you can't bid tactically at the auction. Cheating at computer games could be made more difficult.
There are some gotchas too. For example, TC can support remote censorship. In its simplest form, applications may be designed to delete pirated music under remote control. For example, if a protected song is extracted from a hacked TC platform and made available on the web as an MP3 file, then TC-compliant media player software may detect it using a watermark, report it, and be instructed remotely to delete it (as well as all other material that came through that platform). This business model, called traitor tracing, has been researched extensively by Microsoft (and others). In general, digital objects created using TC systems remain under the control of their creators, rather than under the control of the person who owns the machine on which they happen to be stored (as at present). So someone who wri
Slashdot Mirror
Umm, the "customers" in question might not have been on the same AS?
And, for that matter, if Bill Manning authorized the use of the address space, then it's not even an attack!
Exactly!
Or possibly some attempt at stopping arbitrarily many of their customers setups from breaking... If you've got enough poorly configured machines, it might be easier to ensure that the servers they are looking for remain available, rather than trying to fix _all_ of them immediately... Especially if they're mission-critical systems...
One possibility, if you want a low-time-cost way to try a DVCS, is to try SVK on an existing svn server.
To make it easy, I've copied and paraphrased the quickstart I was given for the first time I was introduced to SVK...
Notes: option (a) corresponds to using SVK as a CVCS frontend to SVN, while option (b) corresponds to using it as a DVCS frontend instead, so it's easy to switch between behaviours.
This quickstart misses the need to run svk sync occasionally, but it should get you up and running, anyway...
Doesn't SVK start to fill that role?
meanwhile, if you're using SVN on Unix/Linux boxes, you might want to check out svk. All the advantages of a DVCS, but with the central repo being a (possibly pre-existing) standard svn server.
(I put the disclaimer about unix boxes in because the last time I had a colleague on a Mac running SVK, there were some minor issues around binary files and line ending munging... I don't know if they are resolved already or not...)
The apparent paradox is due to the expectations of your random variables being infinity... See http://www.ms.unimelb.edu.au/~moshe/twoenvelopeparadox/
Sounds like Brad Templeton's How to fix DNS idea. The idea has been around for a long time; other than economic blockading from the current financial stakeholders, I don't know why is hasn't had more consideration...
The rest of the essays in that collection are at http://www.templetons.com/brad/dns/
Also, like yourself, I haven't been following this very closely recently - there may be an answer now, that just doesn't stand out very well in Aptitude...
(Actually, just remembering: the other one I've been asked about is shared addressbooks; LDAP works, but is almost completely uneditable by the end user, who is usually the secretary given a pile of business cards to enter...)
The key point is that for a single roadwarrior, most things can be made to work... But for a larger office, _sharing_ info (calendars, addressbooks, delegated email, etc) can be an issue.
It makes one feel old to read that and wonder: What ever happened to LinkExchange?
Umm, from that site's data, Russia's share has _fallen_ over the last 26 years; from a high of almost 5% to today's 2.69%.... And USA has been flat at around 21% the entire time; China grew from 3% to 14%, India from 3% to 6%... And France, Spain and Italy have taken minor falls from 4-ish percent to 3-ish percent over that time... How does that equate to "getting more evenly distributed"?
boster suggested above that it was A Deepness in the Sky ...
It's designed for kids and people who have never used a computer before. Umm, because I build computers for people who have never used computers before? Because a simple, easy-to-use UI would be useful for kiosk-type applications? Because I want a nongeek-friendly interface for the box hooked up to my TV?
Just because you can only see one use for a particular application, doesn't mean that that's all it's good for.
It's nice to see you're a fan of Brians's "Common Errors in English", but Paul specifically asks that you link to the main page, rather than the errors page...
I've heard of Community Server, as it also powers The Daily WTF.
...
Unfortunately, the readers of the site are generally of the opinion that "The real WTF is this forum software" because "the forum software sucks"
For what it's worth, it appears to be great as a blogging tool; Alex seems to like the way it works for the blogging functions, but the forum functions are what are generally found to be "quirky"...
If you're using vim, you can save yourself three keystrokes:
Vjjjjjjjy p
And if you're grabbing the whole document, you can further shorten this to:
Gygg p
I do believe that's the Peter Principle, although I could see Dilbert espousing it...
The Thinkpads have been pretty good about this, I remember from back when I had a T21... But I've currently had access to Acer, HP and Asus laptops, and for all of them the Fn-VolumeKeys do nothing in firmware... Actually, from poking around on my Asus, it appears that they don't even send keyboard events, they send ACPI button-press events!
Fortunately for me, my Asus comes with a hardware potentiometer/mute function, but the Acers and HP machines I've seen don't have that, and you can't do volume control until after the OS is up. On the Acers, the mute is actually not activated until after boot (in Windows, at least), so if you have the volume above minimum, mute, then power off, the startup sounds are played before the muting is applied...
Other comments from Richard Stallman's Can you trust your computer and the EFF's paper Trusted Computing: Promise and Risk
Another good summary is this Benjamin Stephen and Lutz Vogel's video Misconceptions
From Anderson's FAQ: