Slashdot Mirror

Frequent screwups? Penny Arcade are dependable as clockwork. Well, not quite, but they are very consistent, and every comic IS a comic. You should read Megatokyo sometime. The whole archive is at least 10% filler. And since the author quit his job to do MT full-time, I find that disgusting.

As for this pot thing... well, a long time ago, I ran a web comic of my own on Keenspace. It was only stickmen, but it did update seven days a week. For a thousand straight days. Not kidding.

So, good luck guys, we'll see you all in four or five years' time when somebody actually claims this...

Based on http://www.ubuntu.com/wiki/HoaryPMResults, a decently large number of machines will do ACPI suspend to RAM now. You probably want vbetool to restore video state after resume.

Here

There's an easier way. See this page for a utility that disables the check without requiring BIOS modification.

Matthew Garrett

In case you're looking for the Journal the orignal paper by Adam Chalcraft and Michael Greene, see
http://www.srcf.ucam.org/archim/eureka/backissues. html#53

therefore 0.0000..0001 is equal to zero, yet greater than zero..

I don't know if you were flaming the OP or just joining in with deliberately bad math, but that conclusion of yours is fundamentally wrong

Small wikis do tend to work better than large ones. For example, I recently set up a MathWiki for the maths students at my university. It's still suffering growth pains (and no-one ever posts during the holidays...), but shows every sign of being a very useful resource.

I'm in a university society called the Assassins' Guild, which is a cross between roleplay and live-action Quake Deathmatch. The game we play involves hunting down other people playing the same game until only one is standing, and is cooler than it sounds (hey, we have girls playing!). The thing that's interesting with respect to this discussion is the excellent testing ground this gives for new technologies vis-a-vis the tracking of indivisuals.

Number one on the list is, surprisingly, static IP addresses on home-user machines. If you know your target's IP address, it is trivial in many cases to check whether he/she is in his/her room, and secondary information like lecture times (and hence the target's course) can be inferred.

On a more sophisticated level, it is possible to examine the movement patterns of a target by the public workstations he/she uses (they have to be regulars on the #assassins IRC channel for this to apply), although this is more easily maskable using screen/irssi off a unix server. The holy grail would be to scan the mobile phone command frequency band - one would only need to know one's target's phone number to triangulate his/her position. I don't know of anyone who's done this, but I'll be attempting it myself over the holidays.

RFID tags present an issue at a similar level, albeit with far greater possibilities for abuse due to their small size. If I were to have access to a reader (of the sort that, if this technology were to become widespread, would be available with no hardware hackery required), I would wait til the target were dumb enough to leave something outside his/her door and drop a suitably crafted tag in it. This would enable me to trail and ambush the target fairly easily when they didn't have any means of defense to hand.

This would be a slightly overworked solution for the purposes of the guild (albeit an excellent way of dealing with one of the more skilled assassins) but would come into its own in the hands of an actual stalker. Imagine someone you can't flee, can't hide from. Imagine what could happen if this technology were abused.

Imagine tags in designer clothes. An excellent way for criminals to know that yes, that coat is genuinely worth a hell of a lot. Imagine tags in young children. Do you really want paedophiles to know exactly when kids have run away from mummy's care? Imagine tags in students. Your grades are fine but you skipped too many lectures - you're out. Imagine tags in employees. Now your fundamentalist boss knows about your trip to the sex toys shop a block over from the office.

Imagine tags in you. Imagine anyone who wanted to being able to track your motions. How secure does that make you feel?

... dont't forget AskJesus! http://www.srcf.ucam.org/~dcf21/test/jesus.cgi

Your assumption here is that no-one will want to use this info unless you're doing something bad, right? That's kinda wrong. Think stalkers, think terrorists ("lets see how many casualties we can acheive by monitoring who goes into that building"), think the petty-minded official who you annoyed once and now he's out to make your life hell.

Even as far as breaking the law goes... to quote Terry Pratchett, probably the only way to avoid breaking a law is to spend all your time locked in a dark cellar with your hands on the table in front of you. And even then you'd probably be guilty of loitering.

I'm in a society called the Assassins' Guild, which plays games based around a kind of controlled, mutually-consensual stalking. It is truly horrifying how easy it is to track any given person down. This is why I value privacy - the games we play are harmless, but there are more than enough crazies out there who are perfectly willing to use this information maliciously. And any system that relies on respecting thy neighbour is, in my opinion, in deep trouble.

Online LOGO Interpreter

Here

enjoy!

http://www.chris-j.co.uk/forum

Wind-Up Entertainment is a member of a certain association. I think the acronym stands for Recording Industry something or other of America or someting :)

I am a member of a university organisation called the Assassins Guild, the basic premise being that, on the basis of the most limited possible information, we hunt down and "kill" other guild members with weapons such as cap guns and cardboard swords. As such, I have some personal experience of the use of Google in stalking. I can tell you that, in a university composed presumably of some of the most net-savvy people around, I have only found a photo once. Occasionally I have found a usenet posting or slashdot account. Old schools are common, but the folk at my uni are often those who are mentioned in school newsletters. The average web presence of the average user is approximately nil. In a range of cases, someone may become more prominent (either by accident or design - Darl McBride for example), but on the whole there is very little you can gather from Google. Occasionally it's enough to kill your target, but don't count on bank details.

For the convenience of lynx/links users, here is an ascii art of him.

The next feature is going to be ascii art

Does this guy look familar?

Well, look at this guy

http://www.srcf.ucam.org/~dmo25/OpticalComputing/

just throwing out a link.

Mike Bond has made a temporary webpage The paper on the attack (UCAM-CL-TR-560) is also duplicated.

These URLs are just temporary until the webserver is back up so could disappear at any time.

Mike Bond has made a temporary webpage The paper on the attack (UCAM-CL-TR-560) is also duplicated.

These URLs are just temporary until the webserver is back up so could disappear at any time.

Fuck you cunt.
http://hal.trinhall.cam.ac.uk/~nrs27

Try making your cunt signature a link. I hate that shit. Fucking cunt.

Your site is fag gay.

Neil you are a fag.

Your PGP key isnt there because you cant get it to work with Outlook.

Your house looks like a pigsty shithole typical of fat people who get no sex.

Helen Butler looks like she has chunky brown vaginal discharges. You and your friends look like fags.

You have broken links, prick.

W3C validator found errors in your shit site.
Genrally you make me sick

Line 9, column 42: . . ^Error: unknown entity "apos" . .
Line 11, column 13: . . ^Error: there is no attribute "ALINK" for this element (in this HTML version) . .
Line 20, column 3: . You can find my PGP key here (when I put it . . ^Error: text is not allowed here; try wrapping the text in a more descriptive container . .
Line 20, column 35: . . find my PGP key here (when I put it . . ^Error: element "A" not allowed here; possible cause is an in
Line element containing a block-level element . .
Line 20, column 35: . . GP key here (when I put it up). . ^Error: text is not allowed here; try wrapping the text in a more descriptive container . .
Line 27, column 0: . The gallery contains a large selecti . . ^Error: text is not allowed here; try wrapping the text in a more descriptive container . .
Line 27, column 31: . . The gallery contains a lar . . ^Error: there is no attribute "TARGET" for this element (in this HTML version) . .
Line 27, column 33: . . The gallery contains a lar . . ^Error: element "A" not allowed here; possible cause is an in
Line element containing a block-level element . .
Line 27, column 35: . . ="./gallery" target="">gallery contains a large selectio . . ^Error: text is not allowed here; try wrapping the text in a more descriptive container . .
Line 27, column 50: . . stuff. Also see the second gallery, . . ^Error: element "A" not allowed here; possible cause is an in
Line element containing a block-level element . .
Line 27, column 50: . . second gallery, which contains stu . . ^Error: text is not allowed here; try wrapping the text in a more descriptive container . .
Line 33, column 30: . . mouse.v - a example for c . . ^Error: element "A" not allowed here; possible cause is an in
Line element containing a block-level element . .
Line 33, column 35: . . ef="mouse.v" target="">mouse.v - a example for compsci t . . ^Error: text is not allowed here; try wrapping the text in a more descriptive container . .
Line 34, column 18: . that went wrong
. ^Error: element "BR" not allowed here; possible cause is an in
Line element containing a block-level element . .
Line 35, column 35: . . a href="./java/java.html" target="">Java - collection of . . ^Error: element "A" not allowed here; possible cause is an in
Line element containing a block-level element . .
Line 35, column 35: . . java/java.html" target="">Java - collection of java bits . . ^Error: text is not allowed here; try wrapping the text in a more descriptive container . .
Line 36, column 13: . and pieces
. ^Error: element "BR" not allowed here; possible cause is an in
Line element containing a block-level element . .
Line 37, column 27: . . old - the site that used to . . ^Error: element "A" not allowed here; possible cause is an in
Line element containing a block-level element . .
Line 37, column 35: . . old - the site that used to b . . ^Error: text is not allowed here; try wrapping the text in a more descriptive container . .
Line 37, column 50: . . ull example of MS Word applying itself to html)
. ^Error: element "BR" not allowed here; possible cause is an in
Line element containing a block-level element . .
Line 38, column 34: . . Work - A selection of . . ^Error: element "A" not allowed here; possible cause is an in
Line element containing a block-level element . .
Line 38, column 35: . . ="./work" target="_blank">Work - A selection of bits of . . ^Error: text is not allowed here; try wrapping the text in a more descriptive container . .
Line 38, column 50: . . ct areas, using an abbreviation for the course.
. ^Error: element "BR" not allowed here; possible cause is an in
Line element containing a block-level element . .
Line 41, column 30: . Slashdot
. ^Error: element "A" not allowed here; possible cause is an in
Line element containing a block-level element . .
Line 41, column 48: . Slashdot
. ^Error: element "BR" not allowed here; possible cause is an in
Line element containing a block-level element . .
Line 42, column 39: . The Register
. ^Error: element "A" not allowed here; possible cause is an in
Line element containing a block-level element . .
Line 42, column 60: . The Register
. ^Error: element "BR" not allowed here; possible cause is an in
Line element containing a block-level element . .
Line 43, column 37: . The Inquirer
. ^Error: element "A" not allowed here; possible cause is an in
Line element containing a block-level element . .
Line 43, column 58: . The Inquirer
. ^Error: element "BR" not allowed here; possible cause is an in
Line element containing a block-level element . .
Line 44, column 36: . BBC News
. ^Error: element "A" not allowed here; possible cause is an in
Line element containing a block-level element . .
Line 44, column 53: . BBC News
. ^Error: element "BR" not allowed here; possible cause is an in
Line element containing a block-level element . .
Line 45, column 35: . . ttp://www.srcf.ucam.org/assassins/"> The Cambridge Assasins . . ^Error: element "A" not allowed here; possible cause is an in
Line element containing a block-level element . .
Line 45, column 50: . . g/assassins/"> The Cambridge Assasins Guild
. ^Error: element "BR" not allowed here; possible cause is an in
Line element containing a block-level element . .
Line 46, column 35: . . http://www.aaib.dtlr.gov.uk/index/"> AAIB (Air Accidents Inv . . ^Error: element "A" not allowed here; possible cause is an in
Line element containing a block-level element . .
Line 47, column 14: . Branch)
. ^Error: element "BR" not allowed here; possible cause is an in
Line element containing a block-level element . .
Line 51, column 18: . Peter
. ^Error: element "A" not allowed here; possible cause is an in
Line element containing a block-level element . .
Line 51, column 33: . Peter
. ^Error: element "BR" not allowed here; possible cause is an in
Line element containing a block-level element . .
Line 52, column 42: . Chris
. ^Error: element "A" not allowed here; possible cause is an in
Line element containing a block-level element . .
Line 52, column 56: . Chris
. ^Error: element "BR" not allowed here; possible cause is an in
Line element containing a block-level element . .
Line 53, column 43: . John
. ^Error: element "A" not allowed here; possible cause is an in
Line element containing a block-level element . .
Line 53, column 56: . John
. ^Error: element "BR" not allowed here; possible cause is an in
Line element containing a block-level element . .
Line 54, column 43: . Joe
. ^Error: element "A" not allowed here; possible cause is an in
Line element containing a block-level element . .
Line 54, column 56: . Joe
. ^Error: element "BR" not allowed here; possible cause is an in
Line element containing a block-level element . .
Line 55, column 43: . Matt
. ^Error: element "A" not allowed here; possible cause is an in
Line element containing a block-level element . .
Line 55, column 56: . Matt
. ^Error: element "BR" not allowed here; possible cause is an in
Line element containing a block-level element . .
Line 56, column 43: . Stu
. ^Error: element "A" not allowed here; possible cause is an in
Line element containing a block-level element . .
Line 56, column 54: . Stu
. ^Error: element "BR" not allowed here; possible cause is an in
Line element containing a block-level element . .
Line 57, column 42: . Dr. Simon Moore
. ^Error: element "A" not allowed here; possible cause is an in
Line element containing a block-level element . .
Line 57, column 66: . Dr. Simon Moore
. ^Error: element "BR" not allowed here; possible cause is an in
Line element containing a block-level element . .
Line 61, column 0: . A small set of instructions / scripts to get sound working in GnomeICU . ^Error: text is not allowed here; try wrapping the text in a more descriptive container . .
Line 62, column 9: . Small(Small( . ^Error: end tag for element "A" which is not open; try removing the end tag or check for improper nesting of elements . .
Line 65, column 3: .
. ^Error: element "BR" not allowed here; possible cause is an in
Line element containing a block-level element . .
Line 67, column 0: . Copyright 2001 N. Smith (nrs27@nospam.cam.ac.uk) Last modified 10th . ^Error: text is not allowed here; try wrapping the text in a more descriptive container . . .

Fuck you cunt.
http://hal.trinhall.cam.ac.uk/~nrs27

Try making your cunt signature a link. I hate that shit. Fucking cunt.

Your site is fag gay.

Neil you are a fag.

Your PGP key isnt there because you cant get it to work with Outlook.

Your house looks like a pigsty shithole typical of fat people who get no sex.

Helen Butler looks like she has chunky brown vaginal discharges. You and your friends look like fags.

You have broken links, prick.

W3C validator found errors in your shit site.
Genrally you make me sick

Line 9, column 42: . . ^Error: unknown entity "apos" . .
Line 11, column 13: . . ^Error: there is no attribute "ALINK" for this element (in this HTML version) . .
Line 20, column 3: . You can find my PGP key here (when I put it . . ^Error: text is not allowed here; try wrapping the text in a more descriptive container . .
Line 20, column 35: . . find my PGP key here (when I put it . . ^Error: element "A" not allowed here; possible cause is an in
Line element containing a block-level element . .
Line 20, column 35: . . GP key here (when I put it up). . ^Error: text is not allowed here; try wrapping the text in a more descriptive container . .
Line 27, column 0: . The gallery contains a large selecti . . ^Error: text is not allowed here; try wrapping the text in a more descriptive container . .
Line 27, column 31: . . The gallery contains a lar . . ^Error: there is no attribute "TARGET" for this element (in this HTML version) . .
Line 27, column 33: . . The gallery contains a lar . . ^Error: element "A" not allowed here; possible cause is an in
Line element containing a block-level element . .
Line 27, column 35: . . ="./gallery" target="">gallery contains a large selectio . . ^Error: text is not allowed here; try wrapping the text in a more descriptive container . .
Line 27, column 50: . . stuff. Also see the second gallery, . . ^Error: element "A" not allowed here; possible cause is an in
Line element containing a block-level element . .
Line 27, column 50: . . second gallery, which contains stu . . ^Error: text is not allowed here; try wrapping the text in a more descriptive container . .
Line 33, column 30: . . mouse.v - a example for c . . ^Error: element "A" not allowed here; possible cause is an in
Line element containing a block-level element . .
Line 33, column 35: . . ef="mouse.v" target="">mouse.v - a example for compsci t . . ^Error: text is not allowed here; try wrapping the text in a more descriptive container . .
Line 34, column 18: . that went wrong
. ^Error: element "BR" not allowed here; possible cause is an in
Line element containing a block-level element . .
Line 35, column 35: . . a href="./java/java.html" target="">Java - collection of . . ^Error: element "A" not allowed here; possible cause is an in
Line element containing a block-level element . .
Line 35, column 35: . . java/java.html" target="">Java - collection of java bits . . ^Error: text is not allowed here; try wrapping the text in a more descriptive container . .
Line 36, column 13: . and pieces
. ^Error: element "BR" not allowed here; possible cause is an in
Line element containing a block-level element . .
Line 37, column 27: . . old - the site that used to . . ^Error: element "A" not allowed here; possible cause is an in
Line element containing a block-level element . .
Line 37, column 35: . . old - the site that used to b . . ^Error: text is not allowed here; try wrapping the text in a more descriptive container . .
Line 37, column 50: . . ull example of MS Word applying itself to html)
. ^Error: element "BR" not allowed here; possible cause is an in
Line element containing a block-level element . .
Line 38, column 34: . . Work - A selection of . . ^Error: element "A" not allowed here; possible cause is an in
Line element containing a block-level element . .
Line 38, column 35: . . ="./work" target="_blank">Work - A selection of bits of . . ^Error: text is not allowed here; try wrapping the text in a more descriptive container . .
Line 38, column 50: . . ct areas, using an abbreviation for the course.
. ^Error: element "BR" not allowed here; possible cause is an in
Line element containing a block-level element . .
Line 41, column 30: . Slashdot
. ^Error: element "A" not allowed here; possible cause is an in
Line element containing a block-level element . .
Line 41, column 48: . Slashdot
. ^Error: element "BR" not allowed here; possible cause is an in
Line element containing a block-level element . .
Line 42, column 39: . The Register
. ^Error: element "A" not allowed here; possible cause is an in
Line element containing a block-level element . .
Line 42, column 60: . The Register
. ^Error: element "BR" not allowed here; possible cause is an in
Line element containing a block-level element . .
Line 43, column 37: . The Inquirer
. ^Error: element "A" not allowed here; possible cause is an in
Line element containing a block-level element . .
Line 43, column 58: . The Inquirer
. ^Error: element "BR" not allowed here; possible cause is an in
Line element containing a block-level element . .
Line 44, column 36: . BBC News
. ^Error: element "A" not allowed here; possible cause is an in
Line element containing a block-level element . .
Line 44, column 53: . BBC News
. ^Error: element "BR" not allowed here; possible cause is an in
Line element containing a block-level element . .
Line 45, column 35: . . ttp://www.srcf.ucam.org/assassins/"> The Cambridge Assasins . . ^Error: element "A" not allowed here; possible cause is an in
Line element containing a block-level element . .
Line 45, column 50: . . g/assassins/"> The Cambridge Assasins Guild
. ^Error: element "BR" not allowed here; possible cause is an in
Line element containing a block-level element . .
Line 46, column 35: . . http://www.aaib.dtlr.gov.uk/index/"> AAIB (Air Accidents Inv . . ^Error: element "A" not allowed here; possible cause is an in
Line element containing a block-level element . .
Line 47, column 14: . Branch)
. ^Error: element "BR" not allowed here; possible cause is an in
Line element containing a block-level element . .
Line 51, column 18: . Peter
. ^Error: element "A" not allowed here; possible cause is an in
Line element containing a block-level element . .
Line 51, column 33: . Peter
. ^Error: element "BR" not allowed here; possible cause is an in
Line element containing a block-level element . .
Line 52, column 42: . Chris
. ^Error: element "A" not allowed here; possible cause is an in
Line element containing a block-level element . .
Line 52, column 56: . Chris
. ^Error: element "BR" not allowed here; possible cause is an in
Line element containing a block-level element . .
Line 53, column 43: . John
. ^Error: element "A" not allowed here; possible cause is an in
Line element containing a block-level element . .
Line 53, column 56: . John
. ^Error: element "BR" not allowed here; possible cause is an in
Line element containing a block-level element . .
Line 54, column 43: . Joe
. ^Error: element "A" not allowed here; possible cause is an in
Line element containing a block-level element . .
Line 54, column 56: . Joe
. ^Error: element "BR" not allowed here; possible cause is an in
Line element containing a block-level element . .
Line 55, column 43: . Matt
. ^Error: element "A" not allowed here; possible cause is an in
Line element containing a block-level element . .
Line 55, column 56: . Matt
. ^Error: element "BR" not allowed here; possible cause is an in
Line element containing a block-level element . .
Line 56, column 43: . Stu
. ^Error: element "A" not allowed here; possible cause is an in
Line element containing a block-level element . .
Line 56, column 54: . Stu
. ^Error: element "BR" not allowed here; possible cause is an in
Line element containing a block-level element . .
Line 57, column 42: . Dr. Simon Moore
. ^Error: element "A" not allowed here; possible cause is an in
Line element containing a block-level element . .
Line 57, column 66: . Dr. Simon Moore
. ^Error: element "BR" not allowed here; possible cause is an in
Line element containing a block-level element . .
Line 61, column 0: . A small set of instructions / scripts to get sound working in GnomeICU . ^Error: text is not allowed here; try wrapping the text in a more descriptive container . .
Line 62, column 9: . Small(Small( . ^Error: end tag for element "A" which is not open; try removing the end tag or check for improper nesting of elements . .
Line 65, column 3: .
. ^Error: element "BR" not allowed here; possible cause is an in
Line element containing a block-level element . .
Line 67, column 0: . Copyright 2001 N. Smith (nrs27@nospam.cam.ac.uk) Last modified 10th . ^Error: text is not allowed here; try wrapping the text in a more descriptive container . . .

If the X-server was written using OpenGL textures, they could be mapped onto any mesh and hence the Genie effect would be fairly easy to implement.

A screenie shows the DVD playback working (using the xine engine) but it will have a KDE wrapper. It works but is a bit rough :)

I also hate the xine GUI and I work on the xine project but the emphasis at the moment is increasing stability, flexability and quality of playback (oh and ironing out those pesky DVD-menu bugs).

A screenie shows the DVD playback working (using the xine engine) but it will have a KDE wrapper. It works but is a bit rough :)

I also hate the xine GUI and I work on the xine project but the emphasis at the moment is increasing stability, flexability and quality of playback (oh and ironing out those pesky DVD-menu bugs).

The Cambridge Assassins' Guild have had to learn to live with one of these owned by a player who owns a shop in the centre of town. It's nowhere near as impressive as some of the larger rubber pellet guns available because you can't draw and shoot at speed!

nope, its not, I've seen one myself. It sees active use in the Cambridge University Assassins Guild.

Cue the ucam.chat New Four Yorkshiremen sketch. Binary? We used to dream o' binary!

Well, I've got an Intel Outside.

Seriously though, do we really need a cheesy slogan for AMD processors? People who choose AMD over Intel have more sensible reasons. IMHO even when AMD wasn't a serious competitor, I found the 'intel inside' logo as repulsive as *cringes* 'Designed for Windows 95'.

--

Disclaimer/shameless plug: I've recently compiled a semi-technical paper on some of the theory behind quantum computing, as a project in our undergraduate physics course.

--

More because I'm bored than because I actually believe anyone will follow the link, read my magnificent comic - Pete the Carnivorous Plant.

I thank you.

Nah, on second thoughts, sluggy is much better. Go there.

CloudWarrior .o. "I may be in the gutter but I look to the stars"

College used to have a cluster of Suns, but they gradually became unmaintained and were removed after they were all hacked. As a result, we ended up with a bunch of Windows machines and no UNIX provision. What we ended up doing was designing a net-booting Linux system that required no access to the local hard drive (documentation here) and just used that until the COs finally gave up and made it official. At around the same time, people finally gave up with the university's policy regarding undergraduate access to UNIX systems (ie, the only general provision would be access to the mail server running a heavily limited shell designed for the express purpose of reading email and carrying out various mail-related tasks) and set up a university-wide service with some support from the student union. The SRCF was the result. Of course, both these could probably have gone very differently if the authorities had taken a different view of things (the SRCF was set up after consultation with the university computing service, and our Linux system happened to coincide with a time when the college COs were too busy fighting with each other to give a damn what we did), but even so if you're unhappy with the computing facilities available to you it is worth attempting to do something about it.

Probably much too late for this to get noticed now, but...

Is there an archive of ZX81 software anywhere, possibly in WAV or MP3 format?

The best by far is ftp://ftp.void.jump.org/pub/sinclair/ zx8 1/, part of World of Spectrum. These are generally RAM images, rather than tape images.

Other places worth going are the comp.sys.sinclair newsgroup, and its FAQ (although this is more ZX Spectrum biased. And maintained by me :-)).

Phil

1. partition (if you put the Hurd and Linux on the same partition, things will get messed, because the Hurd does a lot of cool stuff with inodes to make changes persistent)
2. get dpkg and a bunch of .debs
3. "cross-install" the .debs onto the Hurd partition (there is a shell script for this)
4. make a GRUB bootdisk (BTW GRUB is by far the coolest x86 bootloader I've ever seen)

I suppose a CD would be nice (it would save quite a bit of download time if you're on dial-up), but, quite frankly, I don't think anyone would buy it :D