It could be that the drive is connected to a PATA or SATA controller for which a driver wasn't installed, which would explain why Windows couldn't see the drive at all. That should be evident from the BIOS bootup screens. I have an ASUS desktop motherboard which needs a hard to find Windows driver to make its PATA controller work, and that's what that PC's optical drives are attached to.
The Linux part postdates POSIX, but not the GNU part. Remember who came up with the name POSIX? Richard Stallman. Several of us who worked for the Free Software Foundation in the late 80s/early 90s contributed changes to the POSIX drafts while we were working on implementing them in the existing GNU libc and shell and utilities.
Same here. For several years, incandescents and CFLs in my front porch light would die almost every time there was a big storm, several times a year. Maybe thermal stress. I replaced the fixture, but the problem continued. Finally bought a 60W-equivalent LED several months ago and it's still fine after several storms. It's the one place I've found an LED is definitely worth it.
And, for a lot of consumer routers, you'd have to configure IPv6 by editing text files from the command line, because they don't have the 8MB of memory that's apparently needed to run any of those alternate firmwares with IPV6 support and a GUI for it. I spent hours searching for a firmware for my Buffalo 4MB router that would support IPV6 with a GUI. None exists. I'm running Tomato on it now, and it works great, but there is no IPv6 support. I refuse to risk my sanity to configuring IPV6 manually.
I just inquired about SonicWall also. IPv6 is only supported in a special build of their firmware that is about a year out of date in other features, and you have to request specially from them. I suspect that by the end of this year they'll have rolled it into their mainstream releases, but there's no published timeline. Their press release from last summer boasting IPv6 certification is misleading, in my view.
Trouble is, most consumer routers made before this year don't have enough memory (8MB) to run any of those alternate firmwares with IPV6 support and a GUI for it. At best, you could get IPV6 support but you would have to configure it by editing text files from the command line. I spent hours searching for a firmware for my Buffalo 4MB router that would support IPV6 with a GUI. None exists. I'm running Tomato on it now, and it works great, but there is no IPv6 support. I refuse to risk my sanity to configuring IPV6 manually.
It's true, pretty much. We developed configure scripts and ways to generate them in the days of 28.8kbps modems and they had to work on Unix System III and Xenix and HP-UX. We couldn't assume anything like Perl or Python was available. Linux distros were only just appearing, and there were no package management systems. Windows was still a 16-bit DOS shell. It was a different world. I'm amazed this stuff has endured as long as it has with so few changes. By the time Automake was written, several years after Autoconf, we at least felt we could assume the presence of Perl.
Want to know why it's called "Autoconf", which I think is a bit ugly of a name? I wanted to call it "Autoconfig", but when you add a version number and ".tgz" to that, you exceed the 14-character file name limit of some of the Unix variants it had to be downloaded and installed on!
You can show a movie full-screen using QuickTime Player (without Pro) by clicking on a short AppleScript.
Type these 3 lines into/Applications/AppleScript/Script Editor.
tell application "QuickTime Player" present movie 1 end tell
Then Save As, choose File Format Application, and give it a name something like "Present Current QT Movie.app". Then open a movie in QT Player and double-click on that app you just made to show it full-screen.
Or you can drag & drop a movie onto an application made from the below AppleScript, name it something like "Present Named QT Movie.app". Then QT Player doesn't need to be opened first.
on open fileName tell application "QuickTime Player" open fileName present movie 1 end tell end open
Lack of speed? Not all electric cars. Have you ever ridden in an EV1? It pressed me to the seat with its acceleration, something like 0-60 in 7 seconds.
Sphera is another commercial system, along the lines of Ensim, I believe. I've been at presentations for both, though I've used neither (rolled my own, starting 6 1/2 years ago before there were any other choices available).
I'd like to know why FreeBSD (I use 4.2-STABLE) ships with PAM but with no PAM support in OpenSSH or any of the 3 versions of Kerberos, and with only minimal PAM support in the core login, ftpd, and rshd (no support for sessions or account management). It was a nasty surprise when I installed and configured a PAM module that restricts logins using account management, and none of the login mechanisms used it!
Solaris and Linux have done a much better integration job in this area. I'm wondering why FreeBSD pretends to support PAM and ships with it when it doesn't really use it. It seems dangerous to mislead sysadmins into thinking they have secured their system when the security mechanisms are actually ignored.
Slashdot Mirror
It could be that the drive is connected to a PATA or SATA controller for which a driver wasn't installed, which would explain why Windows couldn't see the drive at all. That should be evident from the BIOS bootup screens. I have an ASUS desktop motherboard which needs a hard to find Windows driver to make its PATA controller work, and that's what that PC's optical drives are attached to.
The Linux part postdates POSIX, but not the GNU part. Remember who came up with the name POSIX? Richard Stallman.
Several of us who worked for the Free Software Foundation in the late 80s/early 90s contributed changes to the POSIX drafts while we were working on implementing them in the existing GNU libc and shell and utilities.
Same here. For several years, incandescents and CFLs in my front porch light would die almost every time there was a big storm, several times a year. Maybe thermal stress. I replaced the fixture, but the problem continued. Finally bought a 60W-equivalent LED several months ago and it's still fine after several storms. It's the one place I've found an LED is definitely worth it.
And, for a lot of consumer routers, you'd have to configure IPv6 by editing text files from the command line, because they don't have the 8MB of memory that's apparently needed to run any of those alternate firmwares with IPV6 support and a GUI for it. I spent hours searching for a firmware for my Buffalo 4MB router that would support IPV6 with a GUI. None exists. I'm running Tomato on it now, and it works great, but there is no IPv6 support. I refuse to risk my sanity to configuring IPV6 manually.
I just inquired about SonicWall also. IPv6 is only supported in a special build of their firmware that is about a year out of date in other features, and you have to request specially from them. I suspect that by the end of this year they'll have rolled it into their mainstream releases, but there's no published timeline. Their press release from last summer boasting IPv6 certification is misleading, in my view.
Trouble is, most consumer routers made before this year don't have enough memory (8MB) to run any of those alternate firmwares with IPV6 support and a GUI for it. At best, you could get IPV6 support but you would have to configure it by editing text files from the command line. I spent hours searching for a firmware for my Buffalo 4MB router that would support IPV6 with a GUI. None exists. I'm running Tomato on it now, and it works great, but there is no IPv6 support. I refuse to risk my sanity to configuring IPV6 manually.
It's true, pretty much. We developed configure scripts and ways to generate them in the days of 28.8kbps modems and they had to work on Unix System III and Xenix and HP-UX. We couldn't assume anything like Perl or Python was available. Linux distros were only just appearing, and there were no package management systems. Windows was still a 16-bit DOS shell. It was a different world. I'm amazed this stuff has endured as long as it has with so few changes. By the time Automake was written, several years after Autoconf, we at least felt we could assume the presence of Perl.
Want to know why it's called "Autoconf", which I think is a bit ugly of a name? I wanted to call it "Autoconfig", but when you add a version number and ".tgz" to that, you exceed the 14-character file name limit of some of the Unix variants it had to be downloaded and installed on!
Dave MacKenzie
Autoconf's main developer
You can show a movie full-screen using QuickTime Player (without Pro) by clicking on a short AppleScript.
/Applications/AppleScript/Script Editor.
Type these 3 lines into
tell application "QuickTime Player"
present movie 1
end tell
Then Save As, choose File Format Application, and give it a name something like "Present Current QT Movie.app".
Then open a movie in QT Player and double-click on that app you just made to show it full-screen.
Or you can drag & drop a movie onto an application made from the below AppleScript, name it something like "Present Named QT Movie.app". Then QT Player doesn't need to be opened first.
on open fileName
tell application "QuickTime Player"
open fileName
present movie 1
end tell
end open
Lack of speed? Not all electric cars. Have you ever ridden in an EV1? It pressed me to the seat with its acceleration, something like 0-60 in 7 seconds.
That would be Gamma World.
(But I don't remember who created it or TS.)
Sphera is another commercial system, along the lines of Ensim, I believe. I've been at presentations for both, though I've used neither (rolled my own, starting 6 1/2 years ago before there were any other choices available).
I'd like to know why FreeBSD (I use 4.2-STABLE) ships with PAM but with no PAM support in OpenSSH or any of the 3 versions of Kerberos, and with only minimal PAM support in the core login, ftpd, and rshd (no support for sessions or account management). It was a nasty surprise when I installed and configured a PAM module that restricts logins using account management, and none of the login mechanisms used it!
Solaris and Linux have done a much better integration job in this area. I'm wondering why FreeBSD pretends to support PAM and ships with it when it doesn't really use it. It seems dangerous to mislead sysadmins into thinking they have secured their system when the security mechanisms are actually ignored.