search for: thyrsus

IMAP logins via fetchmail are failing on my mailserver root at grelber:/home/esr# tail -f /var/log/mail.err Nov 24 16:56:48 grelber dovecot: IMAP(cathy): mail_location not set and autodetection failed: Mail storage autodetection failed with home=/home/cathy Nov 24 16:56:48 grelber dovecot: IMAP(cathy): Fatal: Namespace initialization failed Nov 24 16:57:39 grelber dovecot: IMAP(cathy):

This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to mime@docserver.cac.washington.edu for more info. --1918950298-1868141776-898362261=:6767 Content-Type: TEXT/PLAIN; charset=US-ASCII Something to think about for CRAN's future. best, -tony --1918950298-1868141776-898362261=:6767

...ttelstaedt <tedm at mittelstaedt.us>: > On 7/26/2014 12:18 PM, Arnaud Quette wrote: > >> Hi Eric, >> >> sorry for the lag, summer time... >> >> I'm first seconding Charles comments >> >> 2014-07-09 12:31 GMT+02:00 Eric S. Raymond <esr at thyrsus.com >> <mailto:esr at thyrsus.com>>: >> >> >> I think the time for me to get involved in NUT documentation has come >> again. >> >> >> welcome back >> >> Late last week I had to buy a UPS under time pressure. The Eato...

I just bought a pair of Belkin USB UPSes -- F6C1200-UNV and F6C550-AVR -- and installed the latest version of nut under Ubuntu 7.04. I'm using the F6C1200-UNV. My system does see the device; dmesg says [ 82.718428] usb 2-2: new low speed USB device using ohci_hcd and address 2 [ 82.941189] usb 2-2: configuration #1 chosen from 1 choice [ 83.036825] usbcore: registered new driver

I just bought a pair of Belkin USB UPSes -- F6C1200-UNV and F6C550-AVR -- and installed the latest version of nut under Ubuntu 7.04. I'm using the F6C1200-UNV. My system does see the device; dmesg says [ 82.718428] usb 2-2: new low speed USB device using ohci_hcd and address 2 [ 82.941189] usb 2-2: configuration #1 chosen from 1 choice [ 83.036825] usbcore: registered new driver

Is someone on the core teams going to take responsibility for reviewing and (if approproate) merging this? -- <a href="http://www.catb.org/~esr/">Eric S. Raymond</a>

Hi Eric, sorry for the lag, summer time... I'm first seconding Charles comments 2014-07-09 12:31 GMT+02:00 Eric S. Raymond <esr at thyrsus.com>: > I think the time for me to get involved in NUT documentation has come > again. > welcome back > Late last week I had to buy a UPS under time pressure. The Eaton unit > that thus project gifted me with in 2006(?) died during a severe > thunderstorm watch, so it was...

I think the time for me to get involved in NUT documentation has come again. Late last week I had to buy a UPS under time pressure. The Eaton unit that thus project gifted me with in 2006(?) died during a severe thunderstorm watch, so it was off to MicroCenter to get a replacement pronto. I wound up buying an APC BN700MC. It was what they had in the performance range I needed. The removable

On Jul 9, 2014, at 6:31 AM, Eric S. Raymond <esr at thyrsus.com> wrote: > What I'd like to do is this: confer in real-time, perhaps via IRC, > with someone who knows this process. Ask about every step (thought > processes and diagnostics). *Write them down* and turn this into a > document on how to qualify and support a new device. H...

3a. What part of the documentation needs the most immediate attention? 3b. Will anyone come after me with an axe if I move the entire corpus to ASCIIDOC markup? http://www.methods.co.nz/asciidoc/ 3c. Why isn't the content of the website a branch in the repo? Can we fix things so it is? Hint: If the website becomes a repo branch, I'll reorganize and rewrite that for clarity, too. --

I've spent the better part of two working days reading the NUT code and documentation and thinking about typical modern use cases for the software. I'm now questioning whether I want to get any further involved with this project, because it seems to me that the codebase is a huge and complicated pile of machinery mainly aimed at solving problems that no longer matter. I could be wrong

This is taking longer than I expected, because there is all kinds of cvs2svn-generated ugliness in your back history that tends to crash my tools. Your repo makes a great test case. (Yes, I know, that's like having someone say "Your dog is fantastically ugly!") Current state of things is that I have scrapped my precious approach, which was to put the Subversion tools in a Python

Arnaud, my UPS arrived yesterday; thanks for your generosity. I'm using it to power the computer I'm typing on. This moves NUT up a few places on my priority list. In our last email exchange, I believe we agreed on a couple of major points. I want to confirm these before I start modifying the documentation heavily. 1. asciidoc is a good master format for the in-tree documentation. 2.

2. Recommendations? My use case is pretty typical. I have one Linux machine I want to protect, automated shutown is desirable, blackouts longer than a hour are very rare at my location (the last one I can remember was in 1993), brownouts are very rare and mild, but summer thunderstorms are common and can be severe. I'm a good match for your typical consmer-grade UPS. 2a. In 2009, what do

My UPS died two nights ago. From the symptoms, including the fact that the event took the motherboard of my main machine with it and the unreasonable amount of heat the UPS was generating immediately after, I believe this was a genuine fried-brains failure of the control electronics, not a mere battery death. The old UPS (a Belkin FVC1200) has been packed off to a recycler, and the motherboard

Scenario 1: Package-centric Have the .deb package for NUT install a single-user/single-UPS configuration, with the .deb asking for the UPS type and dispatching on that to set up ups.conf for the correct driver. Package installation could even create a nut user and group, so there wouldn't even be a security compromise. I don't know how to do the equivalent with RPM, because RPM

[was: Asking hard questions about the NUT architecture] Hy Eric, 2007/5/31, Eric S. Raymond <esr at thyrsus.com>: > Arnaud Quette <aquette.dev at gmail.com>: > > doc definitely! > > As mentioned earlier, I've tried several times to start a full > > rewrite, using docbook, to produce a friendly and complete html doc. > > But the facts are that the doc writers have g...

(Copied to Dave Hart at the NTP project, who's interested in the code's progress for non-NUTty reasons. Dave, the background is that I'm doing a trial conversion of the Network UPS Tools repo.) First, repostreamer per se is dead. As it evolved it kept pulling in more bits of code from reposurgeon until I said "screw it!" and merged the repostreamer logic in as a reposurgeon

Recently, I've been working on tools for doing high-quality conversions of project histories from centralized version-control systems like Subversion to modern decentralized systems like git and hg. To see what I mean by "high quality", take a look at my DVCS migration guide: <http://www.catb.org/esr/dvcs-migration-guide.html>. A really good conversion should, for example,

On 7/9/2014 6:51 AM, Charles Lepple wrote: > On Jul 9, 2014, at 6:31 AM, Eric S. Raymond<esr at thyrsus.com> wrote: > >> What I'd like to do is this: confer in real-time, perhaps via IRC, >> with someone who knows this process. Ask about every step >> (thought processes and diagnostics). *Write them down* and turn >> this into a document on how to qualify and supp...