Slashdot Mirror


User: groggy-P

groggy-P's activity in the archive.

Stories
0
Comments
18
First seen
Last seen
Profile
(view on slashdot.org)

Comments · 18

  1. Re:Interesting, I'm glad someone has done this... on Build Your Own BSD Beer Brewing Control System · · Score: 1

    That link is a double 404.

    But the answer is probably "because it won't do the job well enough". For details read the web page again, and particularly the first attempt, which looks like what I think you're talking about.

    Greg

  2. Re:Alternative ideas for this system... on Build Your Own BSD Beer Brewing Control System · · Score: 1

    Strange. I just had a shower using a thermostatic valve that I bought for $50 and which was a screw-in replacement for a standard DIN mixing valve. Looks like you've been ripped off.

    Greg

  3. Re:Time to remove on Build Your Own BSD Beer Brewing Control System · · Score: 1
    An update:

    Date: Sun, 16 Jan 2005 08:55:52 +1030
    From: Greg 'groggy' Lehey
    To: abuse@optonline.net
    Subject: Attempted breakin from your network

    I have just blocked 68.194.48.0/24 from our network following a series
    of attempts to break in to brewer.lemis.com:
    07:48:21.890190 < 68.194.48.16.49458 > 192.109.197.147.35846: S 1756009650:1756009650(0) win 1024
    07:48:21.961893 < 68.194.48.16.49459 > 192.109.197.147.27225: S 1756075187:1756075187(0) win 3072
    07:48:22.204138 < 68.194.48.16.49459 > 192.109.197.147.30331: S 1756075187:1756075187(0) win 3072
    07:48:22.208404 < 68.194.48.16.49460 > 192.109.197.147.59035: S 1756140724:1756140724(0) win 4096
    07:48:22.220790 < 68.194.48.16.49457 > 192.109.197.147.61826: S 1755944113:1755944113(0) win 3072

    08:49:29.940607 sm200d < ool-44c23010.dyn.optonline.net.49459 > brewer.lemis.com.16637: S 1756075187:1756075187(0) win
    +4096
    08:49:29.940692 sm200d < ool-44c23010.dyn.optonline.net.49459 > brewer.lemis.com.6813: S 1756075187:1756075187(0) win
    +3072
    08:49:29.940775 sm200d < ool-44c23010.dyn.optonline.net.49459 > brewer.lemis.com.38262: S 1756075187:1756075187(0) win
    +3072
    08:49:29.940955 sm200d < ool-44c23010.dyn.optonline.net.49456 > brewer.lemis.com.35376: S 1755878576:1755878576(0) win
    +1024
    In total, there were several thousand such attempts. The appear to
    follow a legitimate query on port 4135:
    Jan 16 07:48:09 brewer tempcontrol: Query rom ool-44c23010.dyn.optonline.net (68.194.48.16)
    I assume that this is a result of a recent slashdot posting about the
    temperature control hardware on this machine ("telnet brewer.lemis.com
    4135"). Please take appropriate action.

    Greg Lehey
  4. Re:Summer? on Build Your Own BSD Beer Brewing Control System · · Score: 1

    That's right, mate, maintain the image. We don't have to tell them that summer in Melbourne is three days after Australia day.

    Greg

  5. Re:No math skills on Build Your Own BSD Beer Brewing Control System · · Score: 1

    What do I say? Are you having difficulties with your browser?

    What I've drunk is there for all to see: http://www.lemis.com/grog/brewing/today.

    Greg

  6. Re:When all you have is a hammer... on Build Your Own BSD Beer Brewing Control System · · Score: 1

    Yes, that's what I did. The price is slightly higher than you quote, but only marginally:
    the temperature sensors cost about $10 (US) each. And you still need the relays, of
    course.

    What difference in complexity do you see?

    Greg

  7. Re:Interesting, I'm glad someone has done this... on Build Your Own BSD Beer Brewing Control System · · Score: 1
    There are a number of components of the system:
    1. The hardware. The sensors I'm using are rated up to 85, which isn't enough for what
      you want. You could use thermocouples, though.
    2. The software. I'm still experimenting with that, but I'd expect that you could easily
      modify it to your requirements. Contact me if you have any problems.
    BTW, the software version out there works, but it's a little out of date. I'm still
    working on fine tuning, and my next project is to run multiple fridges (anybody got a
    spare fridge for sale?). Watch the web page: I'll be releasing something soon.

    Greg
  8. Re:Time to remove on Build Your Own BSD Beer Brewing Control System · · Score: 1

    The funny thing is, even now there aren't very many hits on the port,
    only about one a minute. But of course I'm monitoring the situation :-)

    Jan 15 13:16:48 brewer tempcontrol: Query from pcp0010467984pcs.brghtn01.mi.comcast.net (68.43.71.178)
    Jan 15 13:17:01 brewer tempcontrol: Query from wantadilla.lemis.com (192.109.197.135)
    Jan 15 13:18:16 brewer tempcontrol: Query from 186-222.35-65.tampabay.rr.com (65.35.222.186)
    Jan 15 13:18:21 brewer tempcontrol: Query from h000c41483a1f.ne.client2.attbi.com (65.96.182.214)
    Jan 15 13:18:34 brewer tempcontrol: Query from host81-152-215-192.range81-152.btcentralplus.com (81.152.215.192)

    Oh, I didn't say that I might publish your address, did I?

    Greg

  9. Re:Alternative ideas for this system... on Build Your Own BSD Beer Brewing Control System · · Score: 2, Insightful

    Shower temperature regulation is one of the things I've been thinking
    of for decades. It requires much faster responses than beer brewing,
    and to do it right you need to understand the differential pressures
    of the hot and cold water. It's a lot simpler to buy a thermostatic
    valve.

    Greg

  10. Re:About Debian's FreeBSD based system. on Interview With The FreeBSD Core Team · · Score: 1
    Is it a joint project by FreeBSD and Debian teams?

    I don't think so. I don't know of any FreeBSD developer involved in this port. I've known about it for some time, and I've never understood what merit there would be in tearing apart a system and putting a new userland on its kernel. The close relationship between userland and kernel is one of the advantages of FreeBSD (and also of NetBSD and OpenBSD).

  11. Re:What? No legal threats? on Interview With The FreeBSD Core Team · · Score: 1
    You've missed a couple of things here:
    1. SCO is suing IBM, not Linux. There's not much point suing a group of people who have no money.
    2. The BSDs have had their war, remember? The resulting FUD was the main reason that Linux got so much better known than BSD.
  12. dillon leaves the FreeBSD project on FreeBSD Core Developer Thrown Out · · Score: 5, Informative
    The information you have is from the open FreeBSD-chat mailing list. The thread was started by people in the project who are not on the closed developers@FreeBSD-org mailing list, and some of the statements are wide of the mark:
    • Matt Dillon was never a "core developer". The FreeBSD project doesn't use that term, but it looks like a reference to the core team. Matt has never been a member of the core team.
    • Matt has done some very good work over the years. His contribution to FreeBSD release 4 was invaluable, but it would be wrong to suggest that he single-handedly made the difference. Commit statistics on the orginal list show that he has not been very active over the last 12 months.
    • I was not aware of his involvement with Linux VM. Nothing we have done will change this, though.
    • The FreeBSD core team has informed the development community in detail about the reasons for Matt's removal. We don't think it's appropriate, nor fair to Matt, to wash dirty linen in public.
    • Matt has very little influence on the future of the FreeBSD kernel. That work which he has done over the last two years or so was mainly maintenance.
    It's always sad to have to make these decisions. It's even more difficult to defend them when our hands are tied behind our backs.
  13. Re:Similar to the Net/OpenBSD split on FreeBSD Core Developer Thrown Out · · Score: 3, Insightful

    Yes, we considered this too. It's not clear that
    dillon will, in fact, leave the project for good: nothing in this matter requires that. But it's certainly good to note that the BSD world is better for OpenBSD, not worse. Maybe dillonBSD would be another good one.

  14. Re:Matt Dillon? on FreeBSD Core Developer Thrown Out · · Score: 1

    We already have Terry Lambert on the project.

  15. Re:Linux Jewellery on Australian Open Source Awards · · Score: 1

    Silicon Breeze is a one man show run by Patryk Zadarnowski. Patryk is a true philanthropist; he's not rich, but he donates a lot of his income to various free software projects. For example, 15% of the income from the daemon statues goes to a BSD project, and he donated the speakers' gifts (Tux and Daemon statues, depending on your taste) for the AUUG annual conference. I don't think it's appropriate to lump him with the get-rich-quick crowd.

    Greg Lehey
    President, AUUG Inc.

  16. Re:Where their other canidates? on Australian Open Source Awards · · Score: 1

    Well, if you follow the links, specifically the award home page, you'll see that there were a total of thirteen candidates up for election. These were not all the candidates. The nominations committee had quite a job of limiting them, including some who were very deserving. I don't see any difficulty in finding enough candidates for the next three or four years; after that, I hope that new people will have sprung up to keep up the level of competition.

    Greg Lehey
    President, AUUG Inc.

  17. Re:NetBSD core team wins a golden Tux award on Australian Open Source Awards · · Score: 1

    We discussed this issue, and decided that the spirit of free software was inclusive, not divisive. Tux is just as much of a symbol for free software as the Berkeley daemon, and I'm sure that Luke would not have objected if he had received the award with a Tux.

    That wouldn't have happened, though. Despite our agreement, Patryk came prepared: he had a daemon statue which he would have stuck on the pedestal had one of the BSD people won an award.

    Greg Lehey
    President, AUUG Inc.

  18. Interrupt threads (was: Moderate that back) on FreeBSD SMP Plans · · Score: 1
    It's possible that only a small amount of information has trickled through to /., but I can't be bothered to check. Interrupt threads are a natural consequence of removing spl protection: instead, we need to be able to block interrupt execution, which requires a minimal context.

    We're still working on the implementation details, but we're planning to have up-to-date information available on Jason Evans' SMP web page at http://people.freebsd.org/~jasone/smp/. If you're interested in participating actively, join the FreeBSD-smp mailing list.

    Greg