> PS/2 mouse/keyboard ports used to require > separate expansion cards.
Really? I don't think I've EVER seen a motherboard without onboard keyboard. PS/2 Mice... Maybe... but the cards would have appeared *after* the PS/2 put 'em on the motherboard.
More correctly -- C code can be cross platform, if you care to make it so.
The problem is programmers who don't.
When I write code which I intend to be portable, I usually use the man pages from at least one other OS as my reference for the system libraries, if it's outside of the POSIX realm. Well, that's how I used to. A little more than 2 years ago I switched all new projects to APR and haven't looked back. Damn stuff even runs on Windows without tweaking.
Of course, I also use fairly strict typing (lots of typedefs, enums, consts) and throw several compiler warning flags to let me know when I'm being dumb. Like comparing signed and unsigned, promoting pointers to greater alignmnent, etc. But 7 years of hacking mostly-SPARC has got me pretty good at that -- they're a lot pickier than Intel boxes. The only thing that gets me now and then are endian issues -- but those aren't language specific, anyhow.
The system libraries, on the other hand.. well, that has nothing to do with the language. If you want cross-platform code, use cross-platform libraries.
If you can stick to using only functions in K&R and the POSIX Programmer's Reference Guide, you will find that your code (if written properly) will run damn near anywhere.
If you want a little more functionality (as much as you need, really) without GUI, adding the Apache Runtime Library will get you there -- portably. Especially under unices and workalikes.
Why on earth are people always so insistent on doing raw-level dupes of disks?
First of all, it means backing up a 40GB with 2 GB of data may actually take 40GB of bandwidth.
Second of all, it means the disk geometries have to be compatible.
Then, I have to wonder if there will be any wackiness with things like journals if you're only restoring a data drive and the kernel versions are different...
I have been using ufsdump / ufsrestore on UNIX for...decades!. It works great, and its trivial to pump over ssh:
# ufsdump 0f -/dev/rdsk/c0t0d0s0 | ssh user@machine 'cd/newdisk && ufsrestore 0f -'.. it even supports incremental dumps (see: "dump level"), which is the main reason to use it over tar (tar can to incremental with find . -newer X | tar -cf filename -T -, but it won't handle deletes).
So -- WHY are you people so keen on bit-level dumps? Forensics? That doesn't seem to be what the folks above are commenting on.
Is it just that open source UNIX derivative and clones don't have dump/restore utilities?
I'd like to know if the OP has ever lusted after products made by the following companies:
- Ford (German division supplied trucks and tracked vehicles to the Nazis)
- Chrysler (Daimler Benz made poison gas vans)
- GM (Opel made trucks for Hitler)
- BMW (Nazi Motorcycles and tanks)
- Volkswagen (Buzz Bombs, Jeeps)
- Porsche (see above)
- BASF (Formerly IG Farben, made fuel for the nazis)
- Bayer (ditto)
- Siemens (bomber aircraft engines for Hitler)
- Mitsubishi (Japanese Zero)
- Matsushita/Panasonic (electronic components for RADAR etc for the emperor)
- Hitachi (air plane engines, aircraft carriers)
- Kawasaki (fighter planes and ships for for Hirohito)
- Toshiba (Tokyo Electric worked on nukes)
Oh, the list goes on. It seems nothing is safe from the touch of a once-enemy..
Plug and play wasn't thought up by MS Marketing, it was from their Japanese HW research lab. Only, the engineer describing it was trying to say "Plug and Pray".
> And the ending to Voyager was insipid and unmemorable. I don't even > remember what happened to tell you the truth (whereas I can tell you all the > plot-holes in the final episode of TNG).
I can't believe you forgot something so predictable.
It was classic Trek: A whole show (or series, in this cas) was wrapped in five minutes.
It was classic Voyager: The writers said "Fuck it!" and pulled out the time travel deus ex machina. Again.
Hmm, I should look to see who wrote that episode... and compare it to who wrote the premise for Enterprise..
WTF, have you ever watched the show? Jesus Christ, she's from a completely different fucking planet! BETAZED! It's why she's a goddamned EMPATH! HELLO! She's not from Greece! She's NOT EVEN HUMAN!
Chakoty was of native South or Central American descent. I don't think they ever made this clear. But, he was Americanized (through away all his traditional values in his youth).
Are you sure Kim was Chinese? He sure looks Chinese, but I don't remember them saying for sure. He doesn't look Korean, for sure.
Oh, and Picard was clearly a French impostor. If his english accent isn't enough to give that away, his french one was.
> hoping RIAA customs control doesnt hear when it starts playing Bob Dylan out of your ass..
Just make sure the first few tracks on your playlist are country music; that shouldn't draw any undue attention. After all, *any* asshole can play country music.
> If you're talking about losing focus in the window manager sense, > it's not possible under linux without some very specific hacks:
I can't help but wonder if something *extremely* similar to this couldn't be accomplished by allocating X memory via mmap() and letting the kernel know what's going on via madvise(). This wouldn't actually be an enormous amount of work -- a bit of dinking at the dynamic linker (LD_PRELOAD?) and some mechanism to do the madvise call (signal from the window manager?)
The original poster is essentially describing tagging the page dirty bits, which I'm guessing is probably what happens with MADV_DONTNEED.
Of course, these suggestions come from a guy with a Solaris background, I don't know anything about Linux system internals.
Slashdot Mirror
> PS/2 mouse/keyboard ports used to require
> separate expansion cards.
Really? I don't think I've EVER seen a motherboard without onboard keyboard. PS/2 Mice... Maybe... but the cards would have appeared *after* the PS/2 put 'em on the motherboard.
More correctly -- C code can be cross platform, if you care to make it so.
The problem is programmers who don't.
When I write code which I intend to be portable, I usually use the man pages from at least one other OS as my reference for the system libraries, if it's outside of the POSIX realm. Well, that's how I used to. A little more than 2 years ago I switched all new projects to APR and haven't looked back. Damn stuff even runs on Windows without tweaking.
Of course, I also use fairly strict typing (lots of typedefs, enums, consts) and throw several compiler warning flags to let me know when I'm being dumb. Like comparing signed and unsigned, promoting pointers to greater alignmnent, etc. But 7 years of hacking mostly-SPARC has got me pretty good at that -- they're a lot pickier than Intel boxes. The only thing that gets me now and then are endian issues -- but those aren't language specific, anyhow.
C *is* cross-platform.
The system libraries, on the other hand.. well, that has nothing to do with the language. If you want cross-platform code, use cross-platform libraries.
If you can stick to using only functions in K&R and the POSIX Programmer's Reference Guide, you will find that your code (if written properly) will run damn near anywhere.
If you want a little more functionality (as much as you need, really) without GUI, adding the Apache Runtime Library will get you there -- portably. Especially under unices and workalikes.
C++ -- I'm not qualified to comment on that.
And after it passes the Sun spec, we can fix it to be useful (since we have the source) with a simple header change:
..that should eliminate half of the code, decreasing binary size and actually performing. ;)
#define sleep(a) while(0)
Now there was a guy who always knew where his towel was.
So long, and thanks for all the books.
> It found emails I wrote six years ago that I
> forgot I received.
Interesting.
Do you still send yourself emails?
Why on earth are people always so insistent on doing raw-level dupes of disks?
...decades!. It works great, and its trivial to pump over ssh:
/dev/rdsk/c0t0d0s0 | (cd /newdisk && ufsrestore f -)
/dev/rdsk/c0t0d0s0 | ssh user@machine 'cd /newdisk && ufsrestore 0f -' .. it even supports incremental dumps (see: "dump level"), which is the main reason to use it over tar (tar can to incremental with find . -newer X | tar -cf filename -T -, but it won't handle deletes).
First of all, it means backing up a 40GB with 2 GB of data may actually take 40GB of bandwidth.
Second of all, it means the disk geometries have to be compatible.
Then, I have to wonder if there will be any wackiness with things like journals if you're only restoring a data drive and the kernel versions are different...
I have been using ufsdump / ufsrestore on UNIX for
# ssh user@machine ufsdump 0f -
or
# ufsdump 0f -
So -- WHY are you people so keen on bit-level dumps? Forensics? That doesn't seem to be what the folks above are commenting on.
Is it just that open source UNIX derivative and clones don't have dump/restore utilities?
I'd like to know if the OP has ever lusted after products made by the following companies:
- Ford (German division supplied trucks and tracked vehicles to the Nazis)
- Chrysler (Daimler Benz made poison gas vans)
- GM (Opel made trucks for Hitler)
- BMW (Nazi Motorcycles and tanks)
- Volkswagen (Buzz Bombs, Jeeps)
- Porsche (see above)
- BASF (Formerly IG Farben, made fuel for the nazis)
- Bayer (ditto)
- Siemens (bomber aircraft engines for Hitler)
- Mitsubishi (Japanese Zero)
- Matsushita/Panasonic (electronic components for RADAR etc for the emperor)
- Hitachi (air plane engines, aircraft carriers)
- Kawasaki (fighter planes and ships for for Hirohito)
- Toshiba (Tokyo Electric worked on nukes)
Oh, the list goes on. It seems nothing is safe from the touch of a once-enemy..
> there is really nobody to blame but the masses..
No... we can blame the Neilsen Families. I say we round 'em up and lynch 'em.
> Why would a computer with a 64 bit processor be more secure, exactly? I don't get it.
You can make every other bit a one, which will have the effect of keeping the other bits in line, behind bars, etc.
Plug and play wasn't thought up by MS Marketing, it was from their Japanese HW research lab. Only, the engineer describing it was trying to say "Plug and Pray".
He's wrong, anyhow. The default is only -C when the output device isatty().
> And the ending to Voyager was insipid and unmemorable. I don't even
> remember what happened to tell you the truth (whereas I can tell you all the
> plot-holes in the final episode of TNG).
I can't believe you forgot something so predictable.
It was classic Trek: A whole show (or series, in this cas) was wrapped in five minutes.
It was classic Voyager: The writers said "Fuck it!" and pulled out the time travel deus ex machina. Again.
Hmm, I should look to see who wrote that episode... and compare it to who wrote the premise for Enterprise..
WTF, have you ever watched the show? Jesus Christ, she's from a completely different fucking planet! BETAZED! It's why she's a goddamned EMPATH! HELLO! She's not from Greece! She's NOT EVEN HUMAN!
Chakoty was of native South or Central American descent. I don't think they ever made this clear. But, he was Americanized (through away all his traditional values in his youth).
Are you sure Kim was Chinese? He sure looks Chinese, but I don't remember them saying for sure. He doesn't look Korean, for sure.
Oh, and Picard was clearly a French impostor. If his english accent isn't enough to give that away, his french one was.
Um, no. The Slashdot editor's could not POSSIBLY have the intellect of a child and an excellent memory.
If they did, they would be able to remember not to post dupes from six months ago, let alone six hours ago.
I can assure you.. I am very classified.
> If you want your line straight, hold down Shift while you do the above.
Shit, and all these years I've been using a damned ruler on my mouse pad!
How much you wanna bet you bumped the restore key, causing an NMI and eventual EOI which restored a stuck interrupt handler?
Why, version 3.2, of course -- to match the version of HTML they are almost confirming to.
> hoping RIAA customs control doesnt hear when it starts playing Bob Dylan out of your ass..
Just make sure the first few tracks on your playlist are country music; that shouldn't draw any undue attention. After all, *any* asshole can play country music.
http://www.cfrc.ca/programs.asp
> If you're talking about losing focus in the window manager sense,
> it's not possible under linux without some very specific hacks:
I can't help but wonder if something *extremely* similar to this couldn't be accomplished by allocating X memory via mmap() and letting the kernel know what's going on via madvise(). This wouldn't actually be an enormous amount of work -- a bit of dinking at the dynamic linker (LD_PRELOAD?) and some mechanism to do the madvise call (signal from the window manager?)
The original poster is essentially describing tagging the page dirty bits, which I'm guessing is probably what happens with MADV_DONTNEED.
Of course, these suggestions come from a guy with a Solaris background, I don't know anything about Linux system internals.
> Let slashdot throw the first stone in this battle
Slashdot should consider becoming compliant with *some* standard before it starts picking on non-compliant 3rd parties.
> If you're dreaming of making eight bucks an hour, you should either
;)
> consider asking for a raise, or changing careers.
The dollar sign, in 80's-esque 6502ish syntax, clearly indicates that I'm talking about hexadecimal numbers, not binary
> it might not work on, say, Solaris.
It will if you install SMCcoreutils.
Otherwise, man strptime(3C), mktime(3C). Good back to at least 2.5.1.