This server was down for a chunk of today; my house’s electric service (porcelain fuses from the 1920s) was pulled out and replaced. There will be another outage in the next few days as RG&E resets the exterior wiring.
Category: About This Site
Due to a DNS change, shiningsilence.com was down for a while last night. Sorry about the lack of news!
Speaking of outages, this system will be down during the day on Monday, the 11th, because of an electrical system upgrade.
The street where shiningsilence.com is hosted (my house) has been having electrical outages over the course of today; they’re lasting longer than my UPS can handle, so access may be intermittent if the power goes out again.
I have a semi-functional electrical system and a partial network up, so regular newsposts should resume. Sorry about the extended hiatus – it wasn’t supposed to take this long!
I’m all moved, or at least I have all my possessions boxed up in one house. I’ve got a partial network going, so I will attempt to get caught up on all the DragonFly news that happened recently, though it will take a few days.
I have additional electrical work that needs to be done in my house, so shiningsilence.com may have the occasional outage in the next week or two – I don’t anticipate it being for more than a few hours at a time, however.
Things have been quiet on the mailing lists for DragonFly, and I’m in the process of moving house, so news on this page may be intermittent for a week or two…
A semi-milestone: This is news item 1001. That works out to an average of 2 posts per day over the last 18 months.
shiningsilence.com was down for a good chunk of yesterday; a construction worker tripped a fuse in my house, and my UPS only kept going for so long… It’s obviously better now.
If you can read this, it means shiningsilence.com has now moved from FreeBSD 4.10-STABLE on a dual P2/333, to a single 1.8G AMD64 running on DragonFly stable.
shiningsilence.com is moving to newer hardware, which means a change in IP and probably a short adjustment time as DNS updates come through. So, this site and mail will be unavailable for a little while, perhaps as soon as tonight.
The system hosting this page, shiningsilence.com, won’t be going down this weekend after all. The new system’s motherboard has a broken IDE controller, so an RMA is going to have to happen first. Darnit!
shiningsilence.com, where the DragonFly BSD Log is hosted, is having a hardware upgrade this weekend, which means some downtime. Please be patient.
We had a short outage tonight because of a full partition – fixed now.
Up and running again – shiningsilence.com is now running through my home connection on a home machine. Neither of those are terribly high-powered, but that’s OK. I’ll attempt to get a more beefy machine in the coming months, and a better connection may be available within the year.
In the several hours this afternoon when I was rebuilding this Log, comment spam filtering was turned off – some 400-500 spams came rolling in. Wow.
Almost have this working again – I slightly mangled the restoration of entries here, so it’ll be a bit.
I’m moving my hosted locations around; this site may not be available temporarily dring the next few days as DNS updates.
I’ve been changing jobs; I’ll do my best to catch up on news.
Spam was being placed in the comments for various entries on this page at the rate of 1 every 10 minutes or so; I’ve changed the setup to block most of it. If you post a comment and it doesn’t appear immediately, it may be waiting for approval.
This log page passed 20,000 views for May. It’ll be interesting to see the bump after the 1.0 release happens…
If you have a login to BSDNews (and you should – it’s free), you can customize your BSDNews page layout to include the news feed from this very site, listed as “DragonFly BSD”! Thanks to Wes Peters and Chris Coleman for setting that up.
300 posts so far in about 8 months – yay me! I think it’s time to stop counting.
News reporting from me has been slow for the past few days and will still be slow; my house has an ice dam built up and my kitchen and basement are flooding every time the sun comes out. Argh!
I’m using Movable Type for this page; I’ve updated it to version 2.661. This should have little visible effect for readers.
This is the 200th post here – neat! I’m averaging just under 1.5 posts per day, which is good: healthy posting, healthy project.
I haven’t had any posts for the past day or so because there’s not been a lot of activity on the mailing lists, and I’m working up an ‘end-of-year’ report similar to the FreeBSD Status Reports. No link yet, cause it’s not done.
I’ve corrected my how-to-install writeup, based on what several people said in dragonfly.kernel. Several steps are now removed, but it still has the same flavor.
We had some power outages/surges here because of a windstorm, and my UPS didn’t handle it well, along with other local network equipment. So, I’ll be slow with news posts until I get my internal network in better working order.
On a suggestion from Hiten Pandya, I’m going to try to note specific code commits that happen in the dragonfly.commit newsgroup. I’ve not been tracking them too carefully until now.
Apparently this server is colocated somewhere Hurricane Isabel touched down in the US – it was offline for some hours, but seems OK now.
No posts here September 5-7th, as I’ll be out.
I’ve always thought that one of the problems for the various BSD programs is that there’s a lot of good information that can only be found by digging through the various mailing lists. Nobody in their right mind wants to have to sort through the last 3 months of firstname.lastname@example.org just for a 5-second answer. So, blog software used to provide a ‘newsfeed’ may be useful.
I’m not a clever enough programmer to contribute code to DragonFly BSD, but I do read the main newsgroups for it. The DragonFly BSD project is small enough that a rolling readout of events may work. So, I’ve got this blog here to do just that. You too can watch me fumble technical terms!
My first goal is to read up and post. This layout just doesn’t work without an article history, or at least more long-winded articles.