Yes, DOSEMU usually works better, but AFAIK it only works on i386 and Linux (and maybe some BSDs). The OP said somewhere else in the thread it didn't work for him.
Re:Anything would be faster...
on
Bochs 2.0 Released
·
· Score: 4, Interesting
If you just want to play old DOS games, try DOSBox. It's specifically designed for this goal, and cheats in various ways to make it fast (for example, the BIOS and DOS are built-in instead of emulated). The main problem with it is the lack of 386 Protected Mode support.
It doesn't work on most of the architectures supported by Debian (does it even work on anything but i386?)
It is geared toward CD installs, its support for network installs is just not good enough.
It's too much work to make a installer. The Debian people hope to have a installable version of testing available at all times, but that's just too much work with PGI.
You could probably use the DOS or Linux version of
F-Prot. It doesn't need to write anything, and it has some nice command-line options for automated scanning etc.
With a little effort, you can even fit the DOS version on a single floppy. You'll need to store it compressed, and uncompress it to a ramdisk when booting.
Huh? 127.0.0.1 is your own system. If you're running a webserver, the runtime will get a 404 error. Otherwise it will immediately get a "can't connect" error. It won't ever need to time out.
But the real bear is the compilation error messages, which can be pages long, and ultimately completely unreadable.
Simply write a quick Perl script that "pretty-prints" the error messages. You want to remove the optional template arguments about custom memory management etc. Also, replace basic_sting with string. It'll work wonders.
Oh, and also, never look at more than the first error message. Fix it, and the rest will magically disappear:)
Vim is not a shell or an Operating System. You will not be able to run a
shell inside Vim or use it to control a debugger.
This should work the
other way around: Use Vim as a component from a shell or in an IDE.
A satirical way to say this: "Unlike Emacs, Vim does not attempt to include
everything but the kitchen sink, but some people say that you can clean one
with it.;-)"
Vim is designed to be embedded in other applications. An example of this is the integration with Sun Visual Workshop, support for which is included in the official version.
If this was an internal server, how did the RIAA ever discovered its existance? I doubt the sysadmins were stupid enough to make the system visible from the Internet. And even if they were, they would have noticed the bandwidth usage:)
If my computer where taken by anyone I would want it to contain no information whatsoever, preferably having the people who took it have no access to the box what-so-ever. encrypted fs, encrypted bios, requiring one of those nice USB keychains to use as key to turn the thing on, why aren't there features like that in most bioses?
BIOS protection is mostly useless. Nobody will try to actually boot your computer. They'll just take the hard disk, make a copy on some read-only media (read-only, so they can "proof" they didn't change any data), and give back the computer.
Encrypted file systems are a nice idea, and you can get a patch for Linux here. Unfortunately, they can't go in the official kernel, because the encryption laws in many countries. Also, I don't know of any distribution that supports this out of the box.
Autodestruction scripts are easy. Just install a procmail recipe that watches for a certain subject and then executes "cat/dev/urandom >/dev/hda". Pretty effective. An alternative is a CGI script (make sure Google doesn't index it:).
And those keychains are pretty handy to store your PGP private key on (and a lot more reliable than diskettes!)
According to this diagram of Unix history, the first version of OSF/1 (later True64) was based on a mix of SVR4, 4.2BSD en Mach 2.6. (isn't this true of just about any Unix?)
"With this article we'd like to ask all Debian developers and experienced users out there for feedback on an idea we've had."
I wonder why they haven't posted anything on the Debian mailing lists...
The Debian people are by the way already working on a better installer. Woody will be the last release that uses the current one. This new installer will use aptitude instead of dselect for example.
Also, Linux User only plans for i386 support. Check this page. Debian supports many architectures, and the installer should work on all of them. Also, remember that Debian is being ported to non-Linux kernels. The Hurd is coming along nicely, and will probably released in Woody+1, and people are starting on a port to NetBSD. Again, the installer should support these kernels.
Slashdot Mirror
If I recall correctly, Google changed its page rank formula in one simple way: It severely downrated any site that linked to SearchKing.
No, what they did was more general, everything that resembled a link farm was ranked down. For example, many blogs were also hit by the change.
The Debian Policy manual is the reason behind apt-get's magic.
Err, you seem to be talking about a completely different program.
Yes, DOSEMU usually works better, but AFAIK it only works on i386 and Linux (and maybe some BSDs). The OP said somewhere else in the thread it didn't work for him.
It's an implementation of the Win32 API.
If you just want to play old DOS games, try DOSBox. It's specifically designed for this goal, and cheats in various ways to make it fast (for example, the BIOS and DOS are built-in instead of emulated). The main problem with it is the lack of 386 Protected Mode support.
Not to mention that most viruses hide their modifications when active.
You could probably use the DOS or Linux version of F-Prot. It doesn't need to write anything, and it has some nice command-line options for automated scanning etc.
With a little effort, you can even fit the DOS version on a single floppy. You'll need to store it compressed, and uncompress it to a ramdisk when booting.
Be wary of modern hard drives---some of them may use a write cache internally (from what I have heard, anyway).
You can disable this with hdparm -W 0 /dev/hd*. Other hdparm parameters may also be interesting.
You just have to modify your program to save a bitmap of each frame to a file. That can't be that much of work.
Which GTK theme is that?
Huh? 127.0.0.1 is your own system. If you're running a webserver, the runtime will get a 404 error. Otherwise it will immediately get a "can't connect" error. It won't ever need to time out.
Simply write a quick Perl script that "pretty-prints" the error messages. You want to remove the optional template arguments about custom memory management etc. Also, replace basic_sting with string. It'll work wonders.
Oh, and also, never look at more than the first error message. Fix it, and the rest will magically disappear :)
SGI's reference is excellent. It covers the entire STL standard (the few SGI-specific extensions are clearly marked), and is very well written.
You'd better reread Vim's design goals. From the documentation:
Vim is designed to be embedded in other applications. An example of this is the integration with Sun Visual Workshop, support for which is included in the official version.There's a similar project for GNOME, called Gnome-vim (screenshot). AFAIK, it is only useable with Evolution.
Josh Cogliati is working on a reimplementation in Python called L.A.M.B. -- Land Access Mechanized Bot. There's still a lot of work to do, tough.
If this was an internal server, how did the RIAA ever discovered its existance? I doubt the sysadmins were stupid enough to make the system visible from the Internet. And even if they were, they would have noticed the bandwidth usage :)
BIOS protection is mostly useless. Nobody will try to actually boot your computer. They'll just take the hard disk, make a copy on some read-only media (read-only, so they can "proof" they didn't change any data), and give back the computer.
Encrypted file systems are a nice idea, and you can get a patch for Linux here. Unfortunately, they can't go in the official kernel, because the encryption laws in many countries. Also, I don't know of any distribution that supports this out of the box.
Autodestruction scripts are easy. Just install a procmail recipe that watches for a certain subject and then executes "cat /dev/urandom > /dev/hda". Pretty effective. An alternative is a CGI script (make sure Google doesn't index it :).
And those keychains are pretty handy to store your PGP private key on (and a lot more reliable than diskettes!)
According to this diagram of Unix history, the first version of OSF/1 (later True64) was based on a mix of SVR4, 4.2BSD en Mach 2.6. (isn't this true of just about any Unix?)
Don't convert your old MP3's (you'll only lose sound quality), but use Ogg for your new music.
I wonder why they haven't posted anything on the Debian mailing lists...
The Debian people are by the way already working on a better installer. Woody will be the last release that uses the current one. This new installer will use aptitude instead of dselect for example.
Also, Linux User only plans for i386 support. Check this page. Debian supports many architectures, and the installer should work on all of them. Also, remember that Debian is being ported to non-Linux kernels. The Hurd is coming along nicely, and will probably released in Woody+1, and people are starting on a port to NetBSD. Again, the installer should support these kernels.
as I use a Unix based mail client, I cannot block addresses.
On Unix, filtering mail is normally done by Procmail, not by your mail client. See this excellent tutorial.