On a personal level, I have had multiple corrupt HFS+ filesystems, one of which was unrecoverable.
The problem with HFS+ isn't so much HFS+ as it is the ancient code that is still used to fsck it. Back in the day, Norton Utilities for Mac had a good disk repair, and the current good repair utility is DiskWarrior, but fsck_hfs apparently still uses the same basic code that dates back to the '90s.
but will it support upper/lower case?
HFS+ has supported case-sensitive mode for years, but you do have to make the choice when the partition is first formatted, and it's not recommended for the boot partition, just in case some random program fails with it.
Until a few weeks ago, I had been using a Blue & White G3 for an internet server (HTTP, DNS, SMTP, IMAP, as well as NAT/DHCP). They date back to the turn of the century. But after moving it to a different city and a differently configured LAN, netinfo started getting confused and locking up the system for anything beyond simple UI activities, sometimes hours after boot, sometimes minutes.
It was so slow that its load average shot way up and noticeably bogged down the NAT performance when one of those "hail mary" SSH abuse bots slammed it with dozens of attempts per second. (Because of course you should keep trying a bunch of different SSH passwords for root on an OS X system, one of them is sure to be right!)
It had been so long since I had last updated its configuration that I had to migrate to Apache 2 and mod_perl 2, and recompile new versions of all the services because I was moving to an Intel mac mini. 2010-2012 era Macs are still quite relevant, partly because Intel CPUs haven't gotten significantly better since then, and they can actually be upgraded years later, unlike newer models.
the team made a few key decisions regarding connectivity requirements
Not having bought an XBone (or any system since the original Wii), I was stunned one day a year or two ago when someone was trying to set up an apparently brand new out of the box XBone for the video gaming room at a convention. It actually required an internet connection and a large download before it would do anything at all! Unfortunately, the wiffy was very crappy in that room and it never did get set up.
This is the same disconnect from reality behind the "helpful" unsolicited download of six and a half gigabytes of the Windows 10 "upgrade", with no regard to bandwidth cost or even free disk space, and the later forced updates to it. (My two Windows machines still run 7, with updates turned off since I can no longer trust Microsoft at all.)
I take it you don't read Hackaday regularly. They use "they" even when the gender of the person in question is known or otherwise obvious from the link to what the article is talking about.
Google calls them "fiberhoods", and the slow progress very likely indicates difficulty in getting access to utility poles. (at least at a price that Google is willing to pay) And if your neighborhood has buried wires? Tough luck for you, I'm sure.
Many years ago, TWC ran an underground wire in my NW Austin neighborhood with a 2-inch hammer mole, and dug a hole in 1/4 of the backyards along the block (every other house on one side) to access the pipe. Imagine having to do this a block at a time, taking a day or two per block. Of course there was still space left in TWC's little pipe, but I'm sure they wouldn't sell it cheap.
I moved from far NW Austin (near 183/620) back to NE San Antonio. I will likely get Google fiber not much later, and ATT fiber sooner than I would have in Austin.
I worked *FOR* Cisco in the early 2Ks (as a Software Eng, but not on IOS) and I recall them being very slow to put SSH into their firmware, long after the problem of plaintext passwords was well known. I don't think they even had it by 2005. So maybe *a* decade at most, but not decade*s* plural.
Thank you. It's good to see the ol' "your anti-spam technique is a fail" form. Christ, I bet you can go back 11 or 12 years and see this exact same story on Slashdot.
It was already old on Usenet before it reached Slashdot.
"Support" apparently means that you can use your Windows install disk to keep the CPU from falling off the table. Assuming you can actually find an install disk, of course.
Would someone tell me how this happened? We were the fucking vanguard of shaving in this country. The K7 was the CPU to own. Then the other guy came out with a three-core CPU. Were we scared? Hell, no. Because we hit back with a little thing called the Athlon. That's three cores and an aloe strip. For moisture. But you know what happened next? Shut up, I'm telling you what happened—the bastards went to four cores. Now we're standing around with our cocks in our hands, selling three cores and a GPU. Moisture or no, suddenly we're the chumps. Well, fuck it. We're going to five cores.
Sure, we could go to four cores next, like the competition. That seems like the logical thing to do. After all, three worked out pretty well, and four is the next number after three. So let's play it safe. Let's make a thicker aloe strip and call it the AthlonSuperTurbo. Why innovate when we can follow? Oh, I know why: Because we're a business, that's why!
Basically, it is heavily slanted towards Eastern European phonemes, particularly in terms of using consonants that do not exist in many languages. But it has plenty of other weirdnesses too.
Have you tried using Discord? One group I was involved with moved to it from IRC.
Discord starts with badly contrasting colors for body text*, then adds tons of sidebar panes that you can't hide whether nor not you care about them. So the window takes up most of my screen (shrinking the window only shrinks the chat area), when I used to could follow the chat on IRC on the side of a wide-screen monitor and still have room for web browsing.
Yep, definitely a millennial UI. Please save us from this crap, Gen-Z!
* The stupid old Web 2.0 85/85 meme: 85% size, 85% gray, but they use a 15% gray background too! It also defaults to white-on-black, but at least the only other theme is black-on-white. I hate white-on-black, because I prefer to just turn down my display backlight when the room is dark. I hate it enough that I even made custom CSS for Hackaday.
Also, requiring you to call someone to manually unlock your account, instead of time-outs like an hour or even a few minutes. But yeah, requiring passwords so complicated that they are hard to remember and easy to mistype, combined with low lockout thresholds, that's just stupid.
In Austin, there is a Radio Shack across the street from a Fry's. Yes, seriously. A few years ago when they closed a few stores (about two years before the bankruptcy), the two RS locations near where I lived were both closed, and that one was kept open.
Now that I am moving back to San Antonio, I'm going to miss the 15-minute drive to Fry's. They were planning to open a store here right before they had bad financial troubles that made it hard enough for them just to stay in business. It's the largest city in Texas with no Fry's. There are other places I can go, but none of them have all the computer parts and electronic parts under the same roof. And the nearest RS I know of is halfway across town from me.
The problem with ANI is depends on the originating entity being trustworthy. This is likely not the case with budget VoIP services. You could add some kind of digital certificate thingy to validate the initial entry into telephone routing, but what would you do with a blob of crypto on its own? Many caller ID devices use simple 2x16 LCD displays, if even that much.
I've also received malformed numbers (like four or five digits, or just "1"), and name ID with no number. It is impossible for me to block those numbers with my telco's blocking (which limits me to 20 numbers anyhow) because I can't enter a malformed number.
I'm really surprised yet that they don't just generate a random number in the callee's area code for every call. Probably because it would require the manufacturer of their equipment to support that, or to actually understand open-source VoiP software beyond a "google SO for patches" level.
Slashdot Mirror
On a personal level, I have had multiple corrupt HFS+ filesystems, one of which was unrecoverable.
The problem with HFS+ isn't so much HFS+ as it is the ancient code that is still used to fsck it. Back in the day, Norton Utilities for Mac had a good disk repair, and the current good repair utility is DiskWarrior, but fsck_hfs apparently still uses the same basic code that dates back to the '90s.
but will it support upper/lower case?
HFS+ has supported case-sensitive mode for years, but you do have to make the choice when the partition is first formatted, and it's not recommended for the boot partition, just in case some random program fails with it.
Until a few weeks ago, I had been using a Blue & White G3 for an internet server (HTTP, DNS, SMTP, IMAP, as well as NAT/DHCP). They date back to the turn of the century. But after moving it to a different city and a differently configured LAN, netinfo started getting confused and locking up the system for anything beyond simple UI activities, sometimes hours after boot, sometimes minutes.
It was so slow that its load average shot way up and noticeably bogged down the NAT performance when one of those "hail mary" SSH abuse bots slammed it with dozens of attempts per second. (Because of course you should keep trying a bunch of different SSH passwords for root on an OS X system, one of them is sure to be right!)
It had been so long since I had last updated its configuration that I had to migrate to Apache 2 and mod_perl 2, and recompile new versions of all the services because I was moving to an Intel mac mini. 2010-2012 era Macs are still quite relevant, partly because Intel CPUs haven't gotten significantly better since then, and they can actually be upgraded years later, unlike newer models.
From TFS:
the team made a few key decisions regarding connectivity requirements
Not having bought an XBone (or any system since the original Wii), I was stunned one day a year or two ago when someone was trying to set up an apparently brand new out of the box XBone for the video gaming room at a convention. It actually required an internet connection and a large download before it would do anything at all! Unfortunately, the wiffy was very crappy in that room and it never did get set up.
This is the same disconnect from reality behind the "helpful" unsolicited download of six and a half gigabytes of the Windows 10 "upgrade", with no regard to bandwidth cost or even free disk space, and the later forced updates to it. (My two Windows machines still run 7, with updates turned off since I can no longer trust Microsoft at all.)
I take it you don't read Hackaday regularly. They use "they" even when the gender of the person in question is known or otherwise obvious from the link to what the article is talking about.
The Europans built a wall in 2061,why can't the Plutonians?
Just wait until you see all the Sailor Moon sequels this can start!
Was it a high-fiber shit?
Google calls them "fiberhoods", and the slow progress very likely indicates difficulty in getting access to utility poles. (at least at a price that Google is willing to pay) And if your neighborhood has buried wires? Tough luck for you, I'm sure.
Many years ago, TWC ran an underground wire in my NW Austin neighborhood with a 2-inch hammer mole, and dug a hole in 1/4 of the backyards along the block (every other house on one side) to access the pipe. Imagine having to do this a block at a time, taking a day or two per block. Of course there was still space left in TWC's little pipe, but I'm sure they wouldn't sell it cheap.
I moved from far NW Austin (near 183/620) back to NE San Antonio. I will likely get Google fiber not much later, and ATT fiber sooner than I would have in Austin.
I worked *FOR* Cisco in the early 2Ks (as a Software Eng, but not on IOS) and I recall them being very slow to put SSH into their firmware, long after the problem of plaintext passwords was well known. I don't think they even had it by 2005. So maybe *a* decade at most, but not decade*s* plural.
Thank you. It's good to see the ol' "your anti-spam technique is a fail" form. Christ, I bet you can go back 11 or 12 years and see this exact same story on Slashdot.
It was already old on Usenet before it reached Slashdot.
"Support" apparently means that you can use your Windows install disk to keep the CPU from falling off the table. Assuming you can actually find an install disk, of course.
I thought it was a Linux web forum until I read TFS.
Would someone tell me how this happened? We were the fucking vanguard of shaving in this country. The K7 was the CPU to own. Then the other guy came out with a three-core CPU. Were we scared? Hell, no. Because we hit back with a little thing called the Athlon. That's three cores and an aloe strip. For moisture. But you know what happened next? Shut up, I'm telling you what happened—the bastards went to four cores. Now we're standing around with our cocks in our hands, selling three cores and a GPU. Moisture or no, suddenly we're the chumps. Well, fuck it. We're going to five cores.
Sure, we could go to four cores next, like the competition. That seems like the logical thing to do. After all, three worked out pretty well, and four is the next number after three. So let's play it safe. Let's make a thicker aloe strip and call it the AthlonSuperTurbo. Why innovate when we can follow? Oh, I know why: Because we're a business, that's why!
Please tell us how this will work with a landline phone.
I have some contacts that dodge software limitations by doing the thing they need to do in the particular app that supports it.
For example, Excel. All we need to do is get Excel to support instant messaging. And of course e-mail. Got to keep up with emacs, ya know!
It is horrible, just like PHP. No, wait, sometimes it makes PHP look sane.
Where Esperanto got it wrong
Learn NOT to speak Esperanto
Basically, it is heavily slanted towards Eastern European phonemes, particularly in terms of using consonants that do not exist in many languages. But it has plenty of other weirdnesses too.
Have you tried using Discord? One group I was involved with moved to it from IRC.
Discord starts with badly contrasting colors for body text*, then adds tons of sidebar panes that you can't hide whether nor not you care about them. So the window takes up most of my screen (shrinking the window only shrinks the chat area), when I used to could follow the chat on IRC on the side of a wide-screen monitor and still have room for web browsing.
Yep, definitely a millennial UI. Please save us from this crap, Gen-Z!
* The stupid old Web 2.0 85/85 meme: 85% size, 85% gray, but they use a 15% gray background too! It also defaults to white-on-black, but at least the only other theme is black-on-white. I hate white-on-black, because I prefer to just turn down my display backlight when the room is dark. I hate it enough that I even made custom CSS for Hackaday.
Also, requiring you to call someone to manually unlock your account, instead of time-outs like an hour or even a few minutes. But yeah, requiring passwords so complicated that they are hard to remember and easy to mistype, combined with low lockout thresholds, that's just stupid.
In Austin, there is a Radio Shack across the street from a Fry's. Yes, seriously. A few years ago when they closed a few stores (about two years before the bankruptcy), the two RS locations near where I lived were both closed, and that one was kept open.
Now that I am moving back to San Antonio, I'm going to miss the 15-minute drive to Fry's. They were planning to open a store here right before they had bad financial troubles that made it hard enough for them just to stay in business. It's the largest city in Texas with no Fry's. There are other places I can go, but none of them have all the computer parts and electronic parts under the same roof. And the nearest RS I know of is halfway across town from me.
I used to enjoy misreading a previous version of their logo as "Radio Shock".
Where are you going to put your porn if the HD is already full?
The problem with ANI is depends on the originating entity being trustworthy. This is likely not the case with budget VoIP services. You could add some kind of digital certificate thingy to validate the initial entry into telephone routing, but what would you do with a blob of crypto on its own? Many caller ID devices use simple 2x16 LCD displays, if even that much.
"Hi, I'm from the IRS. See my number? I'm legit!"
That was so last year. Now it's "blah blah blah blah can you still hear me?" [wait for YES] [save YES recording for nefarious purposes]
I've also received malformed numbers (like four or five digits, or just "1"), and name ID with no number. It is impossible for me to block those numbers with my telco's blocking (which limits me to 20 numbers anyhow) because I can't enter a malformed number.
I'm really surprised yet that they don't just generate a random number in the callee's area code for every call. Probably because it would require the manufacturer of their equipment to support that, or to actually understand open-source VoiP software beyond a "google SO for patches" level.