Slashdot Mirror

The actual message is here. The politician mentioned in the story is this guy.

The politician, Salim Mehajer, is really something. Sort of an Australian Donald Trump. He runs people over with his super car, threatens people, violates election laws and then gets himself acquitted or wrist-slapped for all of it in court. The editor wanted to elaborate on details of this stuff in Salim Mehajer's Wikipedia page and the powers-that-be blocked him. Seems like the editor was trying to do the equivalent of investigative reporting, to the degree that it amounted to original research and detail excessive for a Wikipedia page.

Sarah seems rather talented, considering she (apparently) wrote and maintained the USB 3.0 code for Linux. And Matthew seems okay, having been awarded the 2013 FSF Free Software Award.

But the news here: A PNW Millennial and a Feminist do not agree with someone who is the architect of a giant, massively adopted project, and who has no time nor inclination to mentor people. It's going to be great in the next 5-10 years as the coddled Millennials meet the kind of international attitude where being overly polite is rude because it wastes time (German specifically, confirmed).

The Sarah Sharp thread shows her as a typical Social Justice Warrior who flies off the handle incomprehensibly. If she is a typical woman who saves everything up until it boils over (sorry for generalizing based on every woman I've ever met, minus two who do not fit the stereotype, but bear with me) then she may have a point that we just don't see in print. But we don't see it in print.

As for Matthew, This shows the reasoning behind Linus not adopting BSD style securelevels. Not that he refuses to listen - he clearly understands the limitations, and explained how he would accept an implementation of securelevels. In 1998.

And is it just a coincidence that he decided to fork after Sarah quit, and references that in his blog post? It doesn't matter, he's arguing a 17 year old point, and Linus has already said how he would accept the code.

For example, I would personally never be interested in using the BSD kind
of securelevels: by design the BSD securelevels would prevent me from
doing exactly the kinds of things I need to do (ie install a new kernel
and reboot, which is a very obvious security risk).
In short, to me the BSD securelevels are completely useless. Why should I
support them, when there is something that is a _superset_ of the BSD
behaviour, that I could actually find useful (ie I might well want to
limit some people from doing specific things).
Read my email again - I specifically said that if you want the bsd
behaviour you can get it with the per-process-bitmap approach. I don't
want to (I _cannot_) work in that kind of fascist setup, but it certainly
works well enough.

More:
http://www.tldp.org/LDP/LGNET/...

Matthew characterized is this way:

... having to deal with interminable arguments over the naming of an interface because Linus has an undying hatred of BSD securelevel, or having my name forever associated with the deepthroating of Microsoft because Linus couldn't be bothered asking questions about the reasoning behind a design before trashing it.

Is that anything like the same thing?

Sarah Sharp - Portland State University
BS, Computer Engineering
2002 â" 2007
Pacific Northwest Millennial

Matthew Garrett
http://geekfeminism.wikia.com/...
".. I'm very aware of how different my life might have been if Hanna hadn't gone to the trouble of ensuring that I knew not to be a dick. "

https://en.wikipedia.org/wiki/...
"In October 2014, Garrett stated on his blog that he would no longer contribute Linux kernel changes relating to Intel hardware, in response to Intel pulling their ads from Gamasutra over the Gamergate controversy."

Linus Benedict Torvalds
https://en.wikipedia.org/wiki/...
Linus Benedict Torvalds (born December 28, 1969) is a Finnish American
He later became the chief architect of the Linux kernel

At an online chat with Finlandâ(TM)s Aalto University, Linus explained:

"Iâ(TM)d like to be a nice person and curse les

If you wanted to compile the source code for Python 2.7 on Windows, you needed Microsoft VS2008 to do so. You couldn't use VS2010 or later. VS2008 is hard to come by and difficult to work with.

> Wikimedia spending has increased by 1,000 percent in the course of a few years.

That could be a problem.

> Jimmy Wales counters complaints by saying the Foundation are merely prudent in ensuring they always have a reserve equal to one year's spending

Yes, a one year reserve on the low end of normal. You don't want Wikipedia to disappear when something bad happens, and SHIT HAPPENS. It's a top 10 web site, meaning it's in the big leagues with Google, Microsoft etc., except it's nonprofit. They may have to deal with stuff like Google is dealing with in Europe - disputes with multiple governments on the other side. You don't want Wikipedia to go bankrupt when some government or some company somewhere doe something stupid that costs the foundation $5 million to deal with and repair the damage.

> nothing to do with generating and curating Wikipedia content, a task that is handled entirely by the unpaid volunteer base.'

False. A large chunk of the budget is developing software for "generating and curating Wikipedia content". It's disingenuous to claim that developing tools for generating and curating content "have nothing to do" with generating and curating content.

That's a fair point – I meant it in the sense of actually researching and writing the text that appears in Wikipedia. And I did say "most" of these budget increases had nothing to do with that. For example, they are not using money from donations to have medical experts check the thousands of medical articles in Wikipedia for accuracy: that to me would be active content curation. Those tasks are left to volunteers, or, in one or two cases like the Cancer Research UK initiative, people funded by others.

What I do think is reprehensible is raising the spectre of ads in the fundraising banners. By all means say that Wikipedia is ad-free and relies on donations – that's perfectly true – but don't imply that donations are needed to keep Wikipedia online and ad-free for another year, making everyone think that if not enough money comes in they'll have to pull the plug, or there will be ads by the end of next year. And that's a mainstream criticism within the Wikimedia movement. Just look at the Wikimedia mailing list discussion. The person speaking there is this guy, a veteran volunteer, GLAMWiki coordinator and former vice-president of Wikimedia Australia.

NSS? I'm no expert, but wonder why it's not used more. Force of habit? License differences? http://www.gossamer-threads.co...

No, MariaDB tested as fast or faster, or they wouldn't have made the move.

No, MariaDB tested as fast or faster, or they wouldn't have made the move.

some people seem to get plenty of good performance :

http://www.gossamer-threads.com/lists/modperl/modperl/104941

In my opinion, this is the interest of the new authorizedkeyscommand. A sample usage is available at http://www.sysadmin.org.au/index.php/2012/12/authorizedkeyscommand/

Nice! AuthorizedKeysCommand (introduced 2012/10/31) can do exactly what we need: Set up a script that (securely) logs key usage and e.g. deny any key that is older than 366 days (by first use or else filesystem timestamp) and hasn't been used in 90 days or for any user whose last login (regardless of which key) was over 60 days ago, with a list of exceptions (by key, not user).

That's still messier than something that can go right into the authorized_keys file as a parameter, but it would do the trick handily.

http://www.phoronix.com/scan.php?page=news_item&px=MTE1ODA

Maybe it's intentional, maybe it's not

It's probably intentional that Apple haven't gone out of their way to make sure that Linux Just Works(TM) on their machines. They probably don't care that much about Linux-on-Macs one way or the other; I doubt they'd go out of their way to make it work or to make it not work.

but it does seem to be a trend.

I'm not sure there's a long-term trend to make it harder. It might have gotten a bit easier after the switch to x86, with more use of standard rather than custom glue chips.

And, if you actually look at the intel-gfx thread pointed to by the Phoronix article, and follow that into the Linux kernel mailing list, it might just have been a bug or, at least, unnecessary (mis)feature that was subsequently fixed/removed.

The Phoronix article also linked to a blog post about a non-Apple laptop that needed a bit of help to boot Debian from a USB installation and didn't support all the hardware, so it's not as if "not entirely happy to run Linux" is an Apple-only problem.

In more detail...

Some of the suggestions from the Full Disclosure discussion and elsewhere:

• using mod_rewrite to forbid multiple ranges
• another rewrite
• another rewrite, "more efficient"
• using mod_headers to remove Range requests
• Snort filtering
• byterange_filter.c patch
• unsubscribe request from clueless Sudanese agricultural banker
• reference to RFC hints at better solution to come

In more detail...

Some of the suggestions from the Full Disclosure discussion and elsewhere:

• using mod_rewrite to forbid multiple ranges
• another rewrite
• another rewrite, "more efficient"
• using mod_headers to remove Range requests
• Snort filtering
• byterange_filter.c patch
• unsubscribe request from clueless Sudanese agricultural banker
• reference to RFC hints at better solution to come

In more detail...

Some of the suggestions from the Full Disclosure discussion and elsewhere:

• using mod_rewrite to forbid multiple ranges
• another rewrite
• another rewrite, "more efficient"
• using mod_headers to remove Range requests
• Snort filtering
• byterange_filter.c patch
• unsubscribe request from clueless Sudanese agricultural banker
• reference to RFC hints at better solution to come

http://www.gossamer-threads.com/lists/apache/dev/401638 -- someone has got a patch. Keep those fast moving script kittens at bay

It seems like almost everyone around here is heralding this is a horrible move. Does anyone actually have a suggestion for what Nokia should have done instead?

They should have stuck with Maemo. Seriously, it's rock fucking solid. I don't care what anyone says, it's a perfectly usable out of the box end user OS, and with the amount of effort they put into MeeGo, they could have very easily tuned and tweaked Maemo to make it into a combined Android/IOS killer.

I love my N900, but it's the only Nokia I've ever owned, and probably the last, after Nokia's clumsy shift to MeeGo (bad) and now WinMo7 (worse). And no, Android isn't open enough for me, not to mention that Android is far too insular. Why should Linux software have to be completely rewritten to work on a "Linux" phone? It doesn't. At most, the UI should need a makeover for the different V and C of the MVC, but not on Android.

According to Savvis invested in a new ipv6-capable network in 2006, to be finished in 2008. Savvis hosts sourceforge / slashdot (from the whois record). Yet, according to the nanog grapevine in 2010, Savvis is not yet able to offer IPv6 to customers. Time to put 'working ipv6' on the checklist for your new hosting?

Linux drivers would be desirable.

Phht, so done, see OpenNI.

There's even GPL code to turn Kinect hand gestures into LIRC controls using those drivers;
    MythTV-Users List
    OpenNI List

What a waste--way to fork a fork. You do realize that someone else already wrote /the/ complete MythTV replacement in only 1731 lines of Perl four years ago.

no one is going to pick your stupid theora code

http://www.neowin.net/news/google-investing-in-theora-for-mobile-devices
http://mozillalinks.org/wp/2008/07/native-ogg-vorbis-and-theora-support-added-for-firefox-31/
http://www.gossamer-threads.com/lists/wiki/wikitech/167167

Please provide sources to backup your statements. Thanks.

I noticed that as well. You can find the binary with OpenSSL on Apache's "archive" server, but I'm not going to download/install it until they fix what the problem is.

It looks like there was a problem with them and they were removed from their SVN repository:

http://www.gossamer-threads.com/lists/apache/cvs/381813

I am surprised the parent said he could do 1080i without VDPAU.

Playing MPEG-2 high-definition streams (whether from over-the-air or FireWire) is easy. To oversimplify, video playback involves 1) decoding the compressed video signal and 2) rendering, or displaying, it. As mentioned, my Pentium 4 was fast enough to decode MPEG-2 streams in 2005, and the Xv hardware-assisted renderer (usable from Linux via any Nvidia or Intel[1] video card/chipset made in the past many, many years) quite nicely displayed the video with the more-than-decent Bob 2X deinterlacer. The resulting 50-70% CPU usage I saw is perfectly adequate for a box that doesn't do anything else, and of course the usage would be less with a faster CPU. Before VDPAU, software decoding and Xv render is what the vast majority (I'd guess 95%) of MythTV users used for high-definition playback.

Decoding high-definition h.264 video (such as produced by the Hauppauge HD-PVR, which shipped in May 2008) is much more difficult. My Pentium 4 was able to just barely play 720p 6Mbps h.264 recordings, but no more; people on mythtv-users were reporting in mid-2008 that a the fastest Core 2 Duo boxes were just barely adequate to play 13Mbps (the best quality, more or less indistinguishable from the original) HD-PVR recordings, and sometimes were overstretched even then. In other words, MythTV users were beginning to create recordings they could not play back!

VDPAU has the video card handle everything. The card itself, not the CPU, decodes both MPEG-2 and h.264 streams and renders the resulting video using excellent deinterlacers. Given the dilemma that the HD-PVR created, VDPAU could not have arrived later (late 2008/early 2009) than it did.

[1] There's still no adequate Xv support using ATi, from what I understand. I don't know whether current ATi Linux drivers have finally solved this; most sensible people on mythtv-users just throw up their hands and buy a $30 Nvidia card.

I've been using a Pentium 4 3.0GHz-powered box as a MythTV frontend/backend for more than four years. It often records four high-definition over-the-air or FireWire MPEG-2 streams while playing back another.

For the first three years I used an Nvidia video card with Xv output to play the recordings at very good quality with 50-70% CPU usage. A year ago I moved to VDPAU, which gives me even better playback with under 5% CPU usage, and will do the same with h.264 recordings (generated by the Hauppauge HD-PVR, for example). Thanks to VDPAU, there's every possibility I'll be able to use the Pentium 4 box for another four years.

JFFS2 is designed for unmanaged NAND flash, not flash cards with built-in controllers that emulate IDE drives. Therefore you can't use it on SD cards, CF cards, or anything that has a built-in memory controller.

See this Maemo development thread: http://www.gossamer-threads.com/lists/maemo/developers/36921

Did you check the [mythtv-users] mailing list? I though I've seen lots of discussion on that issue there.

http://www.gossamer-threads.com/lists/mythtv/users/

Speaking of fine-grained locking, how much of the BKL is left in Linux? I know they've been getting rid of it for a long time, and it's mostly gone. But I thought there were a few paths that used the BKL, and ioctl was one. For instance...

On May 15, 2008, the BKL was returned to non-preemptible. http://kerneltrap.org/BKL

On Oct 10, 2009, the BKL was removed from soundcore_open. http://groups.google.com/group/linux.kernel/browse_thread/thread/d4d323a4781f1c05

On Oct 15, 2009, the BKL was removed from the realtime clock on the 68000 arch. http://www.gossamer-threads.com/lists/linux/kernel/1142631?page=last

In 2008 there were 1300+ uses of BKL, and it looks as if they've been chipping away. Any idea what's left?

exFAT sounds promising, but real question - is it protected by patents? Currently, AFAIK there is proof of concept Linux kernel implemenetation that can read exFAT: http://www.phoronix.com/scan.php?page=news_item&px=NzAzMg Patches: http://www.gossamer-threads.com/lists/linux/kernel/1026144

Various security mailing lists received several postings today about BART card exploits. ezrider.bart.gov is probably either overloaded or intentionally offline. It looks like it's hosted in the Dallas area while Twitter is near DC.

KDE did already do the 2nd (what you list as correct), and most developers assumed that this was sufficient to keep the files in a consistent state, due to rename() being atomic. The problem is the sync issue you mention afterwards: the failure mode being encountered was that the rename() executed instantly to clobber the old file, while the new file still contained no data on disk. If the machine crashed in the window between the rename() and the sync, you have neither the old nor the new file.

The main thing being discussed with KDE (and others) is how to fix this. Adding a sync() after every config update totally destroys performance, if you might update hundreds of small config files semi-frequently. See, for example, this discussion among Python folks for pros/cons of various options.

Let me refer you to what Paul Vixie has to say on the subject. Quoting from the NANOG list a couple of months ago http://www.gossamer-threads.com/lists/nanog/users/109650#109650

the human, as a species in the animal kingdom, is known to be the kind of animal who fouls its own nest and overruns its habitat. the idea of a tipping point, whether it be for CO2 in the atmosphere or polar ice shelves or explosively deaggregated IPv4 routing tables, does not occur in the minds of individual decision makers. instead it's left to us "chicken little" types, and the only way the individual decision makers ever make their decisions on the basis of tipping points is if some kind of "governance" makes them do so.
--
Paul Vixie

It's a bit depressing how nobody takes the security implications of the internet seriously, and acts surprised when they're reminded of them.

Email is not secure. Using SSL for your POP/SMTP/IMAP connections secures your login to the server, but the mail itself is still transmitted in the clear. And people act surprised when you tell them that people can and likely do scan their email?

Then again, given that our financial institutions actively train their users to ignore security indicators (a very exploitable situation), we shouldn't be surprised at that sort of nonsense.

I noticed the following in the article:

It got worse. Most Internet commerce transactions are encrypted. The encryption is provided by companies like VeriSign. Online vendors visit the VeriSign site and buy the encryption; customers can then be confident that their transactions are secure.

But not anymore. Kaminsky's exploit would allow an attacker to redirect VeriSign's Web traffic to an exact functioning replica of the VeriSign site.

I was going to write about how clearly the built-in CA certs in the user's browser would throw up a flag and note that the cert wasn't actually signed by the folks at Verisign or whatever... but then I realized that, hey, given the abysmal state of security compliance, it's probable that nobody would even notice.

And an article on cache poisoning that doesn't even mention that Dan Bernstein had foreseen and fixed the lack of source-port randomization while pointing out that it's still only a stopgap seven years earlier is an article that should have been edited a bit more thoroughly. Kaminsky made the attack much more dangerous, but the possibility should never have existed in the first place.

In a more ideal world, we'd all exchange encrypted and signed email and access any site that involved a login using valid SSL certificates and secure-only cookies. But we're not there.

I don't use 5.1, just Dolby Pro-logic....yep, a 1080p TV matched with a stereo using 1980's audio technology :) So, sorry....no specific advice there.

However, is it safe to assume that you've asked such a question on the mythtv users mailing list (and if it was a long time ago, have you asked again recently). Seems like a problem somebody would have solved at some point. Here's a thread that might be relevant:
http://www.gossamer-threads.com/lists/mythtv/users/253940?search_string=transcode%20AC3%205.1;#253940

You're confusing products a bit. The two pieces of Myth that handle non-tv media, MythMusic and MythDVD. These are both plug-ins to Myth and while they do tend to ship with most Myth setups, they are not part of the core MythTV product. I agree with you that they both suck - The UIs and overall management of media are just terrible - But don't poo-poo MythTV because of them. In essence it's like saying Firefox sucks because your Yahoo toolbar has a bad interface.

XBMC is awesome but it's not a replacement for MythTV. It has no mechanism for recording tv shows or hooking to any type of tuner card. What it excels at is, as you said, media management. I modified my MythTV menu to include XBMC, so when I want to watch my DVD ISOs on a Windows box I launch it from the MythTV interface. A quick blurb on how I did it is here.

FWIW, you can add MythTV as a video source in XBMC using the mythtv:// prefix. You can then view recordings as well as live tv, although it was buggy the last time I tried it.

This release is anything but "pointless chrome." They are moving from QT3 to QT4, which will enable a lot of things (not the least of which being IDE support). Relevant thread here.

The model would be that XBMC would run on an Xbox, and it would connect to Myth over the network just like another frontend.

Incidentally, from what I can tell, XBMC now has a basic, native MythTV client built in. It can be used to watch and delete recordings, and watch and record live TV. However, it has no EPG support, no commercials skip, etc. See here:

http://www.gossamer-threads.com/lists/mythtv/users/326091

Looks like an interesting option.

Now explain why we would want to help them.

* Merkey explaining to Guy why it's OK for him to be in a separate reality because his astrologer said so:
http://en.wikipedia.org/w/index.php?title=User_talk:JzG&diff=prev&oldid=138290116
* Merkey the Mormon messiah:
http://en.wikipedia.org/w/index.php?title=User_talk:JzG&diff=prev&oldid=135869262
* The remarkable cosmic events surrounding Merkey's birth:
http://en.wikipedia.org/w/index.php?title=User_talk:JzG&diff=prev&oldid=138290116
* Merkey's "Right to Edit":
http://messages.finance.yahoo.com/Business_%26_Finance/Investments/Stocks_(A_to_Z)/Stocks_S/threadview?bn=2942&tid=423118&mid=423118
* Merkey's lawsuit against the internet:
http://www.theinquirer.net/images/articles/utah.pdf
* Merkey's peyote offer:
http://groups.google.com/group/mlist.linux.kernel/msg/c29b254c15fc5059
* Merkey disavowing his peyote offer YEARS after it was made:
http://www.ussg.iu.edu/hypermail/linux/kernel/0507.0/0230.html
* Merkey revealing that his Linux kernel buyout offer was part of his native american politicking:
http://www.gossamer-threads.com/lists/linux/kernel/501519
* Merkey's arthritis cure, developed at Timpanogas:
http://www.uwsg.indiana.edu/hypermail/linux/kernel/0108.1/0587.html
* .. which is also a law firm!:
http://www.ussg.iu.edu/hypermail/linux/kernel/0010.0/0955.html
* Merkey vouching for SCO's case:
http://www.ussg.iu.edu/hypermail/linux/kernel/0410.2/2674.html
* Merkey's "Mormon masters" letter showing his hatred:
http://scofacts.org/Novell-TRG-1998-01-30-letter.pdf
* Merkey's _gold_ mine:
http://groups.google.com/group/alt.cyberpunk/browse_thread/thread/3ca32f485a1ea07e/244b0f713989de6b?lnk=st
* Merkey's double-Y chromosome giving him a third brain and the powers of Einstein and Nostradamus:
http://www.ussg.iu.edu/hypermail/linux/kernel/0009.0/1206.html
* MANOS: The fantastic operating system noone ever saw.
http://www.vnunet.com/vnunet/news/2113408/open-source-netware-compatible-unveiled
* Gadugi: More fantastic software noone ever saw:
http://www.ussg.iu.edu/hypermail/linux/kernel/0410.2/2723.html
* Novell threatens to destroy Merkey's family:
http://lwn.net/2001/0704/a/nwfs.php3
* Merkey gets his ass handed to him by Andre, who not too subtly hints that his NWFS code may be stolen:
http://www.uwsg.iu.edu/hypermail/linux/kernel/0111.2/0450.html
* Merkey's the Toad dealer:

I've had a MythTV setup at home for more than two years now, and have posted several times about it. Here's my quick take on the major changes for 0.21:

* Support for multiple recording directories.
* Support for recording multiple streams over DVB.
* New deinterlacers (and an OpenGL-based video renderer, but that's still disabled by default, as I understand it).

That's it. There are hundreds of other changes and fixes, great and small, but for most people these are the changes that'll mean the most. Despite the 18 months since 0.20's release (a way too-long interval, I'd argue), this is a testament to just how good 0.20 was feature- and stabilitywise.

Even bigger news than 0.21 is the forthcoming $299 Hauppauge HD-PVR, the first consumer-grade high-definition video encoder (and with promised Linux support, no less). Within a couple of months, anyone—not just those lucky enough to have unencrypted FireWire ports—will be able to record in real time full 720p or 1080i video and Dolby 5.1 audio from their high-definition cable boxes into h.264 format and play it back on their MythTV boxes. Be aware, however, that the h.264 recordings will for many likely require faster hardware than what they're using for their MythTV frontends.

I've had a MythTV setup at home for more than two years now, and have posted several times about it. Here's my quick take on the major changes for 0.21:

* Support for multiple recording directories.
* Support for recording multiple streams over DVB.
* New deinterlacers (and an OpenGL-based video renderer, but that's still disabled by default, as I understand it).

That's it. There are hundreds of other changes and fixes, great and small, but for most people these are the changes that'll mean the most. Despite the 18 months since 0.20's release (a way too-long interval, I'd argue), this is a testament to just how good 0.20 was feature- and stabilitywise.

Even bigger news than 0.21 is the forthcoming $299 Hauppauge HD-PVR, the first consumer-grade high-definition video encoder (and with promised Linux support, no less). Within a couple of months, anyone—not just those lucky enough to have unencrypted FireWire ports—will be able to record in real time full 720p or 1080i video and Dolby 5.1 audio from their high-definition cable boxes into h.264 format and play it back on their MythTV boxes. Be aware, however, that the h.264 recordings will for many likely require faster hardware than what they're using for their MythTV frontends.

the exploit worked on my gentoo i686 install. i had to change the exploit somewhat to get it to compile, but the result was the same, root access.

after patching my kernel using this patch and re-compiling my kernel, everything is OK. just like many others have related.

I remember seeing a recent thread on lkml about that.

The av-vendor side was that they just want to hook their scanner so that it goes before a file is allowed to be opened and other file operations. They also want to scan contents being written and be able to deny the write.

The kernel side was that a full implementation in the kernel is very difficult because you can't do that for mmap, and that if the intention is protecting Windows boxes they could just do it in userspace (patch Samba to scan files, say).

My impression is that AV vendors would love to have an on-demand scanner in Linux, whether such a thing is actually needed or not. If it's made, expect them all to start pushing protection of Linux systems, even if it's completely unnecessary.

holy crap.
forgot the link

http://www.gossamer-threads.com/lists/engine?do=post_view_printable;post=19711;list=maemo

Approximately 2 weeks ago, we discovered that TimeWarner/Road Runner/AOL was redirecting traffic from irc.ablenet.org port 6667 to their own dummy install of ircd along with commands to connecting users to ".remove" in the event that the connection was a bot. If the end user were to attempt to speak or issue a command, that user was banned from the 'dummy' network.

At about the same time, we noticed that verizon was restricting access to the IPs all together, apparently using some form of port restriction as the DNS still resolved on their name servers correctly. I have documented this informally, with screenshots, on my weblog, found at http://anthony.blogs.ablenet.org/ .

As of today, it now appears that Cox is also redirecting traffic apparently in an effort to disable botnets.

1. I tried in vain some time ago to push a working extensable pluggable cpu
scheduler framework (based on wli's work) for the linux kernel. It was
perma-vetoed by Linus and Ingo (and Nick also said he didn't like it) as
being absolutely the wrong approach and that we should never do that. Oddly
enough the linux-kernel-mailing list was -dead- at the time and the
discussion did not make it to the mailing list. Every time I've tried to
forward it to the mailing list the spam filter decided to drop it so most
people have not even seen this original veto-forever discussion.

2. Since then I've been thinking/working on a cpu scheduler design that takes
away all the guesswork out of scheduling and gives very predictable, as fair
as possible, cpu distribution and latency while preserving as solid
interactivity as possible within those confines. For weeks now, Ingo has said
that the interactivity regressions were showstoppers and we should address
them, never mind the fact that the so-called regressions were purely "it
slows down linearly with load" which to me is perfectly desirable behaviour.
While this was not perma-vetoed, I predicted pretty accurately your intent
was to veto it based on this. ...

http://www.gossamer-threads.com/lists/linux/kernel /755787#755787

I'm not a kernel developer but happened to be reading the mailing lists when the "CFS" originally hit the scene a few months ago.

Basically Ingo Molnar, the author of CFS, who is also the maintainer of the scheduler in the kernel, opposed the inclusion of the competing SD scheduler from Con Kolivas for years. Then he claimed that he was just suddenly inspired to whip up a new scheduler that addresses the exact same problems. He then did so in "62 hours".

If you start at this point and read the next 20 or so messages it gives a pretty clear flavor of how things went down. ( the 62 hour comment is in there too).
http://www.gossamer-threads.com/lists/linux/kernel /755787#755787

you'll note that Ingo's defense is to use smileys and to tell some guy that he's a BSD developer and therefore doesn't understand Linux and should therefore butt out. (I also enjoyed the comment about how having pluggable schedulers is not desirable because it would confuse people. Not like there's already io schedulers, for example. )

After 10 years of working with developers in corporate land, to me it reads like a clear power-play followed by some significant chest thumping. On technical merit the scheduler sounds fine, but on process it was clearly crap and resulted in an obviously skilled and motivated contributor being driven from the world of kernel development.
(some have already posted this link: http://bhhdoa.org.au/pipermail/ck/2007-June/007893 .html )

i'll just post AC since i don't really want this to come back and haunt me in the future (yet i still feel compelled to say something on the topic)

1) forwarding sucks. Why? I don't know.

On the contrary, forwarding is Very Very useful. I have somewhere around a dozen different accounts on email servers that I don't control that forward to a couple accounts that I DO control. With so many accounts, fetchmail isn't viable (especially with "expiring" passwords to deal with) and some forwarding accounts don't even allow logins fr various reasons.

The SPF "solution" is SRS (Sender Rewriting Scheme).

Unfortunately, SRS ALSO sucks. Instead of a huge long post here, I'll just refer to this post, but the gist of it is that SRS creates a fundamental gaping hole in the utility of SPF.

SRS isn't even supported on most of the servers that I have forwarding accounts on anyway, so it's a non-"solution" from the start.

http://www.gossamer-threads.com/lists/mythtv/users /275533#275533
And it isn't just MythTV that uses the guide data provided...

I wanna see someone port MythTV's codecs to the PS3's Cell DSPs so I can use it as my PVR direct to my HDMI TV and 7.1 surround.

Rigt before going to spec out a nice bunch of PC components on NewEgg and build a good box, I always pass by the Myth TV Users Mailing List to make sure that I get the most relevant and updated hardware necessary, and instead end up reading a sampling of the horror stories they go through, taking a few minutes to savor the different tortures one can be subjected to (video out of sync with audio, artifacts on certain channels, MySQL database corruption, NuvExport screws up, X breaks dependencies, and all the rest) and decide to wait another few weeks, certainly the new upcoming release will be much more reliable and user-friendly? And by the way, what happened to all of the things that were done during last year's Google's 'Summer Of Code' for Myth TV ? All the great features and enhancements that were worked on?

So I keep waiting, hoping that the next time I check the mailing list, their version of Matt Groening's Life In Hell have died down a bit....

Even though I am definitely doing a fair amount of Sys Admin duties on various distros, this is different, the killer part is what will happen when something screws up while I'm not around, and my wife gets mad because something didn't work, (provided I can even teach her to deal with all of these menus, options and the whole 'watching Live TV through Myth' syndrome) or my kid decides that he knows better and starts trying to hack the box himself in frustration....?

Surely the TiVo is an attractive box for the wife and kids, but with technology changing as rapidly as it has been, it is questionable whether to invest in such a product today, unless we were hard-core TV addicts, and could justify the cost as it would immediately be recouped.

Funnily enough, the most expedient thing I've ended up doing has been to identify the things I want to watch, and as a previous poster pointed out, just BitTorrent the shows in HD without commercials the next day, no matter where in the world I may be. (...and yes, it is sweet to download things at 10 Megs speed while in certain countries like Japan or Norway!!...LOL!)

Net result: I hardly EVER watch any TV whatsoever, and the few shows I care about can be watched on my laptop.

Well, I wish I had more time to tinker.... and still, major kudos to Jarod Wilson for having created this amazing open-source wonder. But as others have pointed out, for either of these two options, it's really going to all be about being able to have Myth TV interact with the CableCard slot, at least in major urban centers where cable companies rule the roost, and antenna reception is unwatchable!! The killer is that companies like Time Warner Cable are offering their own PVR deals, so they will make sure to lock anyone else out of the convenience until forced to do so by the FCC... Or that someone learns to hack the Firewire outputs of some of those new set-top decoders. Then you potentially still have HDCP to contend with. Oh, brother!! Brave new world !!

Z.

Sheesh, windows users are so damn unimaginative.

Simply do VNC over an SSH tunnel. I seriously doubt that you have to worry about port 22 being blocked, and all of your packets will be encrypted.

and yes, you can do this in windows with putty (windows ssh package) and vncviewer.exe.

Look here for a step by step how do to this

I could go back and find out, but I hesitate to raise the issue for the possibility of being labeled a "troll" and being blocked again, even out of spite—and as I'm sure you know, this is a real risk when asking for help on Wikipedia. If you want vigilante admins blocking good-faith contributors out of process, there's no shortage of those on the block log or in this discussion.