Search Results: "ag"

30 January 2008

Christian Perrier: DD resolution of the day

When filing an ITP, Thou shalt read Developer's Reference 6.2.2: A lot of Debian packages description really suck, indeed. Bubulle resolution of the day: read ITP and nag proponents about synopsis writing style. Other developers/maintainers resolution of the day: get back to your packages descriptions and think about them twice after reading DevRef 6.2.2 and 6.2.3.

Joerg Jaspert: Write Intent Bitmaps considered bad

Reading Russels post about Write Intent Bitmaps I thought “Well, lets try out if the performance impact is really only small”. Having done that I can only warn people and advice to not use them, at least not with internal bitmaps. The whole thing may be different if you have them on an own drive, but internal and as such on the raid device itself is really bad. So, having turned them on I just waited to see what happens with the machines under normal load. Not doing any stresstests, as they don’t show normal load situations anyway. And a little performance impact was expected. A little, not the thing that happened… I’m impressed, haven’t seen that much IO wait ever before. Even the old packages.debian.org code, which was really bad IO-wise (thanks to multiple greps per search), didn’t have such a bad impact. I mean - a Dual Core Athlon 3800, running a few Xen domains, usually without any noticable load, now having a load of 20 and more, while IO wait is at some 90% (as shown by top for both cores), constantly. (2 RAID1 devices). Or a Desktop System with a RAID5 (mad of 4 SATA discs), which normally unpacks a kernel tarball in some 10 seconds - now needs about 2 minutes to get it unpacked. Removing that tree now uses 5 minutes. No, bitmap internal is nothing one ever wants to use. One possibly might want to use that feature with a file for the bitmaps which is stored on a different device. That might actually make sense and wont hurt as much as internal does. I have one positive thing to say about them: Resyncing an array is indeed much much faster. But I go with longer resync times and slightly less performance during that time, the cost of having the bitmaps all the time massively impacts, a recovery of even a day doesn’t cost as much in total.

MJ Ray: Annual meetings, reports, and Social Source SW

The Phone Coop (agent link) will hold its workshop and annual meeting on Saturday. If anyone is going and wants to car-share from the N.Somerset/Bristol area, let me know (new comments form follows this post). I can't quite afford a 5h train trip instead of a 2h car trip, but I'd quite like to reduce the damage. Also, we've just finished and sent the official reports for TTLLP yesterday. We've also various projects which I want to get finished, including the IPC::Open3 for Koha. If I'm a bit hard to reach this week, this might be why. We are still returning calls in batches in our breaks, though, so please please please leave a voicemail. Social Source South West is next Tuesday in Bristol. I'll be there. Will you?

Russell Coker: My LCA Talk

Last year at LCA Crispin Cowan suggested to me that I make a joint offer of a combined tutorial on SE Linux and AppArmor as a way of publicly comparing the two technologies. I ended up not accepting the challenge, among other things I had a long-term project going in production in early December that needed some ongoing support. Crispin’s plan B was to just give a lecture about AppArmor. Recently Crispin joined Microsoft [1] and John Johansen of Suse was going to give the talk in his place. The LCA people made a minor mistake by having the conference web site give the description of the tutorial option [2] (which I don’t believe was ever going to happen as I had not accepted the offer), but it’s easy to understand the webmaster copying the wrong description when the one person makes two offers (which I believe is not a common practice). So this morning I and about 150 other people were waiting in the main lecture theatre and no-one from Suse turned up. Being fairly audacious when the announcement was made that the event was officially cancelled I stood up and asked if anyone would like an impromptu talk about SE Linux instead. The audience received that idea quite well. My talk wasn’t as good as I had hoped, not having had a proper breakfast or any caffeinated drinks reduced my mental stack space. So I could talk well on one topic but when questions diverted me to a side topic I found it difficult to remember the previous point I was making. Fortunately when giving an impromptu talk with no notes or presentation materials the audience expectations for a consistent plan of the talk seem reasonably low. ;) I started by talking about my SE Linux Play Machines. Some of that material had been covered in previous talks at other conferences (such as at a previous SE Linux Symposium), but some things (such as my use of Xen) I had not previously covered, but none of it had been mentioned in a talk in Australia for a while. Having given an hour-long talk about SE linux yesterday to an audience with many of the same members I wanted to start by talking about something that they hadn’t heard before, and I was also wearing a Play Machine T-shirt (with the root password printed on it) [4]. After I finished talking about my Play Machines and started covering some of the same material as yesterday about a quarter of the audience left (which was fair enough). I then spoke about general SE Linux issues, largely in response to questions. I covered the differences between the policies (including the history of policy development), the JFFS2 XATTR development (and how SE Linux couldn’t be used on an iPaQ without it), issues of disk space usage for XATTRs for SE Linux labelling on various filesystems and how it drives the use of context mount options, poly-instantiated directories (including some discussion on how the actual storage location for such directories can be on a different filesystem and how this could be convenient when using encrypted filesystems), how Apache/PHP work in a SE Linux environment, and a lot more. I couldn’t resist mentioning to the audience the irony that I had declined a challenge for a joint presentation and then got a sole presenter spot (and a large audience) due to the Suse guy not showing up. For future situations I plan to load lecture notes from all my common talks on my iPaQ. Then next time I have such a speaking opportunity I can give a better prepared talk. Update: It turned out that the LCA people had been informed that the Suse talk was cancelled and had made a mistake, see this link for details.

Sylvain Le Gall: OCamlMeeting in Paris -- Debian summary

On January 26th 2008, the OCaml community has its first meeting in Europe. There was 5 different talks, including one from me. The meeting was pretty constructive and i think some great things should come out of it. In this post, i will focus on the Debian maintainer point of view. The meeting was organized by me, with the help of Garbriel Kerneis and Vincent Balat. I wish to thank Mme Turgis from ENST/ParisTech who has made possible all this to happen. Introduction: I announce the creation of OCamlCore, a SS2L. It will provide commercial support for OCaml and related products. It will also provide community with some resources (including a GForge, a planet, some SCM repository...) For now, i will open administration to Debian people who wish to help (for root rights) and from the whole community for other task (gforge and general administration). For now, i will choose alone who can administrate and who cannot... This is not a very open position, but this server is also for my company. Xavier Leroy give us a nice talk that has let us see some future direction: But above all, Xavier talked about the fact that there is a lack of manpower at INRIA and invited the community to build tools and other things (including a CPAN like distribution) to make the language more widespread. He also stated that a lot of things will stay in place in the name of backward compatibility. OCsigen Vincent Balat has given us a nice talk about OCsigen, a new framework for programming web application. This program is already in Debian and it is at the root of Debian discussion about moving .cm[ao] into libxxx-ocaml package. This new framework allows to program web application using continuation, which should ease a lot of aspect. It also features static type checking, including static verification of the generated HTML pages. GODI I was impressed to see G. Stolpmann coming to the meeting. Unfortunately, i cannot follow the whole talk, since i have some phone call to make, in order to book the restaurant. From what i have seen, it seems that GODI is growing, in term of manpower. They have some issues with OCaml 3.10, because of camlp4 and some packages. At the end of the conference, he was pushing for a more general use of GODIVA. In particular, it requires to have a very uniform way of building software. It should be the foundation of a build standard for OCaml software. In my humble opinion, i don't agree on this point. Basically, its proposal was based on configure/make all, which is too C style way of doing. It is not bad, but just exclude ocamlbuild enabled software. ocamlbuild Nicolas Pouillard has made an introduction on how to use ocamlbuild. I have discovered how it was working, since i didn't have time to work on this topic. It seems a good thing. I hope to be able to try it at some point. The conclusion was about modifying ocamlbuild to allow the use of multiple plugins. For now, the plugin is a separate file which is compiled first and then loaded, as a special case. Nicolas is looking for a full OCaml way to handle this for multiple plugins. OCaml in Debian I have spoken about different aspect of Debian packaging. After a short introduction and some history about OCaml in Debian, I come to some conclusions/problems: Talking with Xavier give me some additional informations: At the end of the presentation, there were some questions. I discover that many people are ignoring the ABI problem with OCaml and its libraries. They seem to discover that it requires regular rebuild of our packages. I also have a discussion about the fact that Debian binary distribution doesn't fit developers need. It seems that developers prefer to have the source of libraries they compile and also the most recent release. But at the same time, people avoid using GODI, which also have the problem of needing to wait for a particular library to be released... After some discussion, I point that some companies prefer to live in a frozen world, which Debian stable can provide. Living in a frozen world helps company developers to have the same environment from the beginning to the end of a project - which can last years. It also help to avoid build environment de-synchronization between company developers. There was also a question about interaction between installed OCaml package and GODI software. I cannot answer it, expect with a "patches are welcome". OCaml on a JVM using OCaml-Java Xavier Clerc explained us how he has achieved running a full OCaml environment on a JVM. This work was pretty impressive, because he was able to compile OCaml top level and provide it as an applet. This is something amazing (and working). He stated also that this should allow to do some binding with java graphical user interface from OCaml. I was pretty busy with a phone call (to a restaurant for the dinner), so i don't have attend the whole conference. Anyway, the project is promising, but it needs to recompile every library using its compiler. I think this is not suited for Debian for now. Workshop The workshop was shorter than it should have been. This is due to accumulated time shift during the day. However, it was pretty interesting, because everybody can talked almost freely. The initial discussion was about the "Unicode situation". This was a question about Unicode in Unison, but there is no real solution about it. For reader information, unison has problem with filename containing UTF-8 char. In particular when syncing two directories which are on two file system with a different encoding on each. Even if the file can be represented on the two file systems, the comparison (between UTF-8 and ISO8859-15) fails. This is because the comparison is a byte to byte comparison. We discuss further the idea of OSR (OCaml standard recommendation) which was briefly discussed in the morning. I think David Teller (who have also done a great part of the IRC retranscription) was very keen on this idea. I invited Nicolas Pouillard to discuss the three following subjects. About camlp4 documentation, Nicolas told people about the he set up. About ocamlfind and ocamlbuild, he went back to the multiple plugin problems. About ocamlbuild and GODI, Gerd, Nicolas and Xavier tried to build a list of what metadata can be shared. This includes list of files to be installed (PLIST in GODI). Concerning the "feedback from the Gallium", Xavier explains that he has done this in the morning (which is true). I think that Xavier implicitly agreed on the fact that if this kind of event happens again, he can do another talk about future of OCaml. Concerning Summer of Code, I just remind that people can write description of Google Summer of Code project in the cocan wiki. Another one remind about Jane St Capital summer of code. Points concerning common interfaces raise the discussion about OSR. The organization of next year events doesn't raise particular interest. I think people would be interested to have one next year, if something comes out of this meeting.

29 January 2008

Adam Rosi-Kessel: Security and Privacy

It’s probably impossible to get too much of Bruce Schneier, although I honestly wouldn’t mind if he stopped Friday Squid Blogging. His latest Wired.com article on the false dichotomy between security and privacy is an excellent counterpoint to a recent Lawrence Wright profile in the New Yorker on Director of National Intelligence Mike McConnell. The Lawrence Wright article was surprisingly uncritical, considering the New Yorker’s usual zealous approach. Check out, for example, his description of the “Clipper” chip:
In the nineties, new encryption software that could protect telephone conversations, faxes, and e-mails from unwarranted monitoring was coming on the market, but the programs could also block entirely legal efforts to eavesdrop on criminals or potential terrorists. Under McConnell s direction, the N.S.A. developed a sophisticated device, the Clipper Chip, with a superior ability to encrypt any electronic transmission; it also allowed law-enforcement officials, given the proper authority, to decipher and eavesdrop on the encrypted communications of others. Privacy advocates criticized the device, though, and the Clipper was abandoned by 1996. They convinced the folks on the Hill that they couldn t trust the government to do what it said it was going to do, Richard Wilhelm, who was in charge of information warfare under McConnell, says.
(emphasis added). Compare, for example, EPIC’s Clipper Chip information page. Schneier, by contrast, sees right through the core:
We’ve been told we have to trade off security and privacy so often — in debates on security versus privacy, writing contests, polls, reasoned essays and political rhetoric — that most of us don’t even question the fundamental dichotomy. But it’s a false one. Security and privacy are not opposite ends of a seesaw; you don’t have to accept less of one to get more of the other. Think of a door lock, a burglar alarm and a tall fence. Think of guns, anti-counterfeiting measures on currency and that dumb liquid ban at airports. Security affects privacy only when it’s based on identity, and there are limitations to that sort of approach. Since 9/11, approximately three things have potentially improved airline security: reinforcing the cockpit doors, passengers realizing they have to fight back and — possibly — sky marshals. Everything else — all the security measures that affect privacy — is just security theater and a waste of effort. By the same token, many of the anti-privacy “security” measures we’re seeing — national ID cards, warrantless eavesdropping, massive data mining and so on — do little to improve, and in some cases harm, security. And government claims of their success are either wrong, or against fake threats. The debate isn’t security versus privacy. It’s liberty versus control.
Read the whole essay. And send it to your mother, as well. Technorati Tags: , ,

John Goerzen: Why Are We So Afraid of Socialized Medicine?

I've been thinking about this for awhile, so time to put down some thoughts.

First, what is socialized medicine? If we listen to the politicians that label health care as "socialized", it seems to be "anything that is paid for by taxes and delivered free or cheaply to citizens." Putting aside the question of whether that meets the academic definition of socialism for the moment, let's look at things in the United States that are already socialized:



That's right. We trust the government with our children all day long for 13 years. For free!

Yet this is a country in which hospitals dump the homeless in the gutter for being unable to pay their bills. Even insured Americans find claims turned down for arbitrary reasons. People are afraid to change jobs for fear of losing health insurance.

Why is it bad to have the government pay for health care?

Here in the United States, our health care system is far from best in the world. It's not even top 10. Or 20. Our system encourages minimizing health care, and doesn't encourage preventative care.

I'd suggest that, in a democracy, it's best to have the government pay for health care. That's because, in a democracy, we are in control of the bureaucrats. If we wish to exercise common sense and pound into their heads that paying for preventative care makes good long-term sense, then we can do so at the ballot box.

So why the scare tactics about government being involved in health care?

Perhaps our real problem is that we have let government get out of our control? Perhaps we are too frightened of change to vote. Perhaps we've given up on a responsive government. Perhaps we think that the insurance companies and drug companies will never let us have a good health care system.

Yes, the lobbyists have a lot of power. But we have the power to remove it, and it's high time we used it.

The audacity of Obama to have hope. To say that we can do better. When Hillary Clinton falls in line with the Republicans and accuses him of having "false hope", effectively saying that we can't do any better, then is she -- or any Republicans -- really a candidate of change? I think that all these accusations from conservatives and Hillary that Obama has "false hope" has finally convinced me that he's the one to vote for. If everyone else claims that his ideas are too good, that his dreams too big, then I like him.

Oh, and you could substitute "college education" for "socialized medicine" everywhere in this article and get equally valid arguments.

Christine Spang: Real Life Accessibility

I live in a cooperative living group, and during the fall semester a person who we’d invited to live with us who is a dwarf and relies on a scooter for most of his transportation decided he’d like to move in. Unfortunately, while he can get out of his scooter and come inside by himself, we had no stepless entrances such that he could bring his scooter inside to protect it from the angry Cambridge winter. Mmm, frozen batteries. So, we’re a coop and we maintain the house ourselves—so we decided to build one, of course. A ramp up to the back porch! Nevermind the fact that we need to sink four-foot foundation holes in the ground in January. We got started right away at the beginning of IAP, while people were still trickling back into town from all over the country. First we surveyed out where the posts should be sunk: Then it was time for excavating the holes where concrete would eventually be poured. This involved a power auger of DOOM: It’s advertised as a 2-man tool. Two 200-pound construction workers, that is. We had to put four people on it plus one person with a shovel clearing dirt to make it manageable, and even then it was a pain. There’s a delicate rhythm you have to get into to avoid getting the bit stuck—DOWN. UP. CLEAR. And inevitably there are rocks and roots that have to be dealt with. We lucked out with a fairly warm weekend to do the digging on, but on the first day we still had to deal with a couple inches of frozen ground: There was also some fun stuff involving having to clear away our (frozen) mulch containers and use a concrete cutter on a weird old concrete pathway that used to run through the same area: Next we mixed and poured concrete: And placed hardware in the concrete to hold the posts: Framing: Eventually it became functional, woo: And done! (except for metal handrail): This all took place over the course of about three weeks. And now our scooter-bound housemate can bring his wheels inside! The house still isn’t totally accessible to wheelchairs/scooters, but at least the first floor is. It really brings me pride to see things like this go from start to finish here. We can do it! This guy who is moving in has really influenced my life—he’s really good at making people feel comfortable talking to him, and for me it’s gone from “wow this is awkward, I have no idea what to say” to “talking to a person with different physical abilities and characteristics seems normal”. And that’s made me a better person.

Matthew Garrett

This article is kind of interesting - it's a claim from a conservation group that using PCs to perform climate modelling is preferable to leaving them idle. The figures they provide are based on this brouchure from Tufts University, which provides an average power consumption per computer of 120 Watts and CO2 production of 1500 pounds per year. That gives a figure of 12.5 pounds of CO2 per Watt year.

The brouchure also contains the obviously false claim that an idle computer draws approximately the same amount of power as an active one. Anyone who's ever actually used a computer will have noticed that they get hotter when they're under load, and the baby thermodynamics would be crying if that energy didn't come from somewhere. The difference between idle and full load can be up to 100 Watts, though that includes extra draw from the graphics card. Something like the Climate Prediction application aren't likely to push the hardware that hard, but you're still looking at at least 20 Watts difference between idle and loaded on any reasonably modern computer. Using the Tufts figures and assuming that this results in an extra 16 hours of load per computer, that's somewhere around 170 extra pounds of CO2 per computer running the application per year - or, using the Tufts figure for the quantity of CO2 absorbed per tree, around 15 extra trees worth of required CO2 sequestration.

Distributed computing isn't a free resource. Each machine running one of these clients overnight is using something like 130 Watts more than a machine that's suspended instead. Deciding whether that's worth it is going to depend on your beliefs about how useful climate modelling is going to be in avoiding climate change. I'm leaning towards it being more of a political issue than a scientific one at this point, so my recommendation is to turn the things off.

(And please don't talk to me about the amount of energy wasted on demonstrating that cryptography can be broken when you've got enough processors to throw at it. The level to which anyone should be surprised at this result can be expressed in very few words)

Michal Čihař: Gammu stable version 1.18.0

Good news everyone, first stable Gammu release in this year is out. Since 1.17.92 only few small fixes in SMS decoding and AT engine did happen, but there is quite big list of changes compared to 1.17.0: You can download from usual place: http://cihar.com/gammu/.

Michal Čihař: My first Drupal module

As I use Drupal for Czech phpMyAdmin pages, it was only a matter of time till I will have (or want) to add some functionality. My first Drupal module is quite trivial, but anyway I already got positive feedback on it just after committing to Drupal CVS :-). Today I finished little cleanup which my initial version required and I decided to make a first release out of it. And what I'm still talking about? It's a module for adding measuring code for various web auditing systems used in Czechia. I didn't wanted to hack this somehow into templates and module which will provide block with those looks as best solution to me. You can get it on Drupal pages.

Neil Williams: QuickList 0.9.1 and beyond

Main changes here are including the translations provided by Debian - thanks to all those who submitted po files.
No new functionality in this release - more an incremental improvement in the underlying codebase.
Future plans for QuickList
The 0.9.x series will continue the theme of incremental improvements, but once libqof2 is released, quicklist will begin to use QOF objects that are created dynamically from QuickList data as well as using QOF features like 64bit time and a choice of backends. I expect this to bring with it a SQL-query interface that would allow QuickList to provide a more usable report interface, finally replacing the missing functionality from the old QuickList. The QOF support will be implemented as a "read-only" mode, certainly initially, so that QuickList could read any QOF data source then produce SQL-based reports in HTML on the data. Eventually, this "read-only" mode should be able to handle "integral" data sources like the apt cache or other well-established sources where a suitable C API exists. This would allow any QuickList user to load the apt-cache, select data in any control field of any package using SQL syntax (via a GUI or via direct text entry), format a report in HTML and export that report to a file.
The QOF support would allow the code to support these data sources to be packaged as Glib modules (similar to libqofexpensesobjects0) to keep dependencies under control.
With this kind of support in place, I could finally be ready to release quicklist 1.0.0 sometime after Lenny. :-)
If anyone is interested in any of these ideas, feel free to help with QuickList development.
http://quicklist.sourceforge.net/
Query Object Framework (QOF).

Julian Andres Klode: Improved aufs support in Ubuntu, Debian


pre-compiled aufs modules for Ubuntu Hardy will be available soon. Today, the linux-ubuntu-modules git has seen the commit which adds the aufs module for generic and server kernels on the i386 and amd64 architectures. But this is not the only thing. 5 patches from the aufs source have been commited to Ubuntu Hardy’s kernel repo.
  1. Export __lookup_hash: and is needed for NFS
  2. Export put_filp: This patch exports put_filp and is needed for NFS.
  3. Export do_splice_from and do_splice_to:
  4. Export security_inode_permission(), also used by UnionFS, where it is currently disabled
  5. Export deny_write_access():
The aufs source package will see an update in Debian soon, which will be sync’ed into Ubuntu Hardy. This update uses the same code as the aufs code in linux-ubuntu-modules. This new code has improved XFS support, improved TMPFS support, improved support for lhash and put_filp patches. It’s also the first revision to support kernel 2.6.24. In the next days, we may see first disks using aufs. I’ll provide patches for the software tomorrow. If nothing goes wrong, Ubuntu Hardy disks may use aufs instead of UnionFS, which may still be provided as a fallback.

Filip Van Raemdonck: Why globals suck

To the people looking for a way of converting from metres per seconds to metres per days: multiply your value by 86400 (60 for seconds in a minute, times 60 for minutes in an hour, times 24 for hours in a day).

One of the disadvantages of using dynamic web pages, is that you might end up serving pages (depending on how the application works) that basically say: "I can't find what you're looking for". Over the last hour I've kept half an eye onto the webserver logs for this weblog, and noticed that the Google crawler tried to index pages which simply aren't there, like for example an archive view for the year 2083. But the underlying PHP script happily returns a HTTP 200 status, with the message that filters don't match anything. Hardly useful.
I also ran trough a large part of the site, checking if any page could refer to such 2083 archive, but haven't found any links to it. Which leaves me wonder why Google came to it.

On faulty pages; for the last couple of days I've also been updating the script code to some extent, and through the log following of the server logs I noticed that some links were broken (and did not return 200 but 404 instead, or, in case of the comment code, made it impossible to post anything at all). Largely due to modification of a global in some code path, which variable was used later to build up these broken links.
I think I've covered all faulty links; but if I oversaw any please let me know, I can be reached by email at mechanix on rack66.net.

Neil Williams: QOF 0.7.4 release

Finally making the last release of libqof1 before the imminent transition to libqof2. v0.7.4 includes a new pkg-config file that will become the default for libqof2 and later releases - qof.pc. In 0.7.4, this is installed alongside qof-1.pc to make it easier for packages to transition to the new file and to libqof2. (The transition itself simply consists of removing all the deprecated code in 0.7.4 in a single operation - use --disable-deprecated-qof to ./configure to see the effect.)
Once uploaded, I'll make releases of pilot-qof and gpe-expenses using the new pkg-config --libs qof call in ./configure (and a minimum requirement for QOF v0.7.4). GnoTime also needs to make this change (other changes for libqof2 have already been made - thanks Linas.)
There's plenty of time before libqof2 - I want to get the GDA backend operational before making the first libqof2 release. It's coming along but still experimental - this is why I have not asked for translation updates for 0.7.4, the strings that have changed are related to GDA which is not enabled by default in 0.7.4 and the strings will change again before libqof2 (QOF v0.8.0). I'll make a call for updates in good time before the 0.8.0 release. Depending on other tasks, this should be possible before Debian Lenny is released but if time is short, I'll wait until after Lenny.

Benjamin Mako Hill: Chama o Bombeiro!

In Brazilian Portuguese, "bombeiro" is the word for both a fireman and a plumber. If someone asks you to call a "bombeiro," their statement is usually unambiguous due to context. Usually. /copyrighteous/images/chama_o_bombeiro.png Both SVG source and t-shirts are available at cost.

Russell Coker: Change of Rules for the Blogging Contest

Due to the lack of entries so far I am amending the rules. It is no longer required that an entry be on the blog of the person who submitted it. Being on any blog that is aggregated by the conference Planet will do. This is known as a “guest post“. All it requires is that you email the post content to a blogger who you trust and they post it crediting you as the author. Guest posts are fairly common among serious bloggers, a google search will surely give more information.

Filip Van Raemdonck: Task scheduler annoyances

Apparently, the task scheduler in all Windows NT-derived versions up to (and including) Windows Server 2003 cannot run jobs under the "NT Authority\Network Service" security principal; "NT Authority\System" is the only so-called well-know security principal that can be used with it. Support for running tasks as "Network Service" or "Local Service" was only added in Task Scheduler 2.0, which is the version that ships with Vista and will be also included in Windows Server 2008.

Side note: I wonder why the link above, being a command reference for an administrative tool, is on the MSDN and not on the Technet site.

Practical implication is that without being able to use the "Network Service" principal, a distinct network account (domain account or server account) is required for any job that needs to access any network resource. This also means keeping track of another account and password — and taking care of controlling and auditing it's access; whereas the "Network Service" principal cannot normally be used for interactive sessions.

Annoyingly, the task scheduler UI also does not tell you that you can't if you try, but rather gives the un-helpful message "Access is denied. You do not have permission to perform the requested operation".
The same message is also shown when, for a regular account, the password entered does not match the actual account password. (This happened to me because the keyboard layout on a remote desktop session turned out to be not what I thought it was)
Anyone know if the error reporting has improved anything in the new task scheduler?

Romain Francoise: Shared links for 2008-01-29

Filip Van Raemdonck: Task scheduler annoyances

Apparently, the task scheduler in all Windows NT-derived versions up to (and including) Windows Server 2003 cannot run jobs under the "NT Authority\Network Service" security principal; "NT Authority\System" is the only so-called well-know security principal that can be used with it. Support for running tasks as "Network Service" or "Local Service" was only added in Task Scheduler 2.0, which is the version that ships with Vista and will be also included in Windows Server 2008.

Side note: I wonder why the link above, being a command reference for an administrative tool, is on the MSDN and not on the Technet site.

Practical implication is that without being able to use the "Network Service" principal, a distinct network account (domain account or server account) is required for any job that needs to access any network resource. This also means keeping track of another account and password — and taking care of controlling and auditing it's access; whereas the "Network Service" principal cannot normally be used for interactive sessions.

Annoyingly, the task scheduler UI also does not tell you that you can't if you try, but rather gives the un-helpful message "Access is denied. You do not have permission to perform the requested operation".
The same message is also shown when, for a regular account, the password entered does not match the actual account password. (This happened to me because the keyboard layout on a remote desktop session turned out to be not what I thought it was)
Anyone know if the error reporting has improved anything in the new task scheduler?

Next.

Previous.