LWN.net Logo

Quotes of the week

I don't think the situation is in fact deteriorating. We're shipping decent releases, growing our user base, within and without the kernel developer community, and still have plenty of major feature areas to work on. We have not seen regressive LKML obstructions, though admittedly that is a low standard when it comes to serving the community.
-- SystemTap maintainer Frank Eigler

If my corporate overlords told me I had to use my Exchange "messaging" account for external email communication, they would get a quite clear 'no' in response. My response may also contain suggestions that they use certain other objects for purposes for which they were not designed.

Seriously, just use an external email account and ignore the broken corporate policy. 'Policy' is just a euphemism for not having to think for yourself.

-- David Woodhouse
(Log in to post comments)

Quotes of the week

Posted Aug 12, 2010 10:19 UTC (Thu) by Tet (subscriber, #5433) [Link]

I have to say, I get frustrated at the systemtap situation. It's an incredibly useful tool. Sure, maybe it's an approach that the kernel maintainers don't like. But it seems like they raise an objection to something, and the systemtap maintainers change things around to make them happier. And then it still doesn't appease them. I'm a strong advocate of not mainlining anything unless it has a good, clean design. After all, it needs to be supportable. But it does seem like the maintainers are going out of their way to ensure that systemtap fails, without suggesting alternatives that would provide similar functionality.

Quotes of the week

Posted Aug 12, 2010 15:12 UTC (Thu) by jackb (subscriber, #41909) [Link]

Just run an SSH server that listens to port 443 on your home computer and you'll never need to worry about not getting work done because Websense is blocking something you need to access.

Quotes of the week

Posted Aug 12, 2010 19:13 UTC (Thu) by dtlin (✭ supporter ✭, #36537) [Link]

This actually didn't work at one of my previous workplaces, because the firewall would say "that ssh traffic doesn't look like SSL" and drop the connection.

I ended up

  • patching my Apache for #29744
  • setting up mod_proxy behind mod_ssl (and requiring authentication), allowing CONNECT to port 22
  • configuring ssh to proxy its traffic through proxytunnel

Luckily I now work someplace with more enlightened network operations.

Copyright © 2010, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds