Actually, you're wrong to assume that NX is just giving you a picture of a desktop like VNC is. Yes, you can use it like VNC in that you can have a big window containing a desktop (you can also use it in the much more traditional seamless mode). But, whereas VNC is a rather dumb protocol to pass through pixels and mouse/keyboard events (and this does help it be portable between X, Windows, and Mac OS), NX is more of a wrapper around the X protocol itself, reducing redundant messages, compressing bitmaps as needed, and sending text as actual text to be rendered client-side (this last one alone makes it a HUGE advantage if you ever have to work from a shitty Internet connection; your icons might look like a garbled JPEG mess, but the text is crystal-clear; VNC requires either having everything clear but dog-slow, or compressed like crazy and fast, but rendering text unreadable too often).
Your information seems out of date. One issue with the sound, was that neither 64-bit Windows Vista or either version of Windows 7 contains AC97 drivers by default. This has since been mitigated with the addition of the emulated Intel HD Audio card (and selected by default on Windows Vista/7 guests at creation time, so you have to go out of your way to make sound not work). Ethernet is handled by emulating one of two AMD cards or three Intel cards, which guests support what also varies, and VirtualBox is smart enough to pick the appropriate one at VM creation time (assuming you aren't lying about the guest OS type, of course;)). Shared directories and USB devices, yes they were a pain in the VirtualBox 1.x days, but they have both become quite a breeze (even shared folders from a command-line only Linux guest is as simple as "mount -t vboxsf ShareName/mnt").
Disclaimer: I use Linux as a host operating system and don't have much experience with VirtualBox on other hosts, be it Windows, Mac OS, or Solaris. If it's still troublesome on one of the others, all I can say is "Oh well" and hope the situation improves for you.
I have to agree that forking GNOME 2 isn't quite as appealing as it might first sound. GNOME 3's fallback mode already works excellently (I use it!), and work really ought to be focused on refining that instead.
1. Somehow, Richard Stallman hasn't claimed that OpenBSD is also "the Gnu System".
Probably because it's not GNU, what a shocker. Even though it might sound pedantic of him to keep repeating it, he emphasizes the name GNU/Linux precisely because Linux filled in the kernel void where HURD failed to deliver. On GNU/Linux, you're using the GNU system, just not with the kernel they wanted (for better or worse). This is the same reason that Debian 6.0 and later have an install disc for GNU/kFreeBSD; it's GNU with the kernel of FreeBSD.
OpenBSD (and FreeBSD) are not based on GNU; you can install GNU separately (typically with all their filenames prefixed with the letter g), but it's still not GNU.
Except all of the following are true now:
1. Flash is natively x86 64-bit
2. Flash is accelerated, smooth fullscreen on Intel GPUs.
2. Flash is accelerated, smooth fullscreen on NVIDIA GPUs.
2. Flash is accelerated, smooth fullscreen on AMD GPUs.
WebKit seems to be becoming that rather quickly. Chromium/Chrome seems to be the only except that refuses to use a system-wide libwebkit and instead uses its own.
Indeed, his ranting on Java in particular is somewhat silly given this; it's been fully Unicode safe since the very beginning. If you can type the glyphs directly and don't want to bother with codepoints, then fine, you just do it, assuming you have an editor that is UTF-8 safe, but well, almost all are.
Sure, pretty everyone with IPv6 has huge swaths of address space. Take for example, a 6to4 address of 2002:1234:4567::/48. You've got 1,208,925,819,614,629,174,706,176 addresses to use for your one IPv4 connection, all machines directly accessible over IPv6. That's just for a single IPv4 link; the IPv6 address space is *huge*, shortage is not going to happen any time soon.
What's wrong with FAT? Pretty much everything from space inefficiency to lack of permissions to filename restrictions to reliability issues, especially after unclean shutdowns.
Also GRUB's core.img already only supports one filesystem -- whichever one is/boot (which can be FAT, GRUB can do that as well), filesystem modules for other types if necessary are loaded directly from said/boot partition.
Slashdot Mirror
Actually, you're wrong to assume that NX is just giving you a picture of a desktop like VNC is. Yes, you can use it like VNC in that you can have a big window containing a desktop (you can also use it in the much more traditional seamless mode). But, whereas VNC is a rather dumb protocol to pass through pixels and mouse/keyboard events (and this does help it be portable between X, Windows, and Mac OS), NX is more of a wrapper around the X protocol itself, reducing redundant messages, compressing bitmaps as needed, and sending text as actual text to be rendered client-side (this last one alone makes it a HUGE advantage if you ever have to work from a shitty Internet connection; your icons might look like a garbled JPEG mess, but the text is crystal-clear; VNC requires either having everything clear but dog-slow, or compressed like crazy and fast, but rendering text unreadable too often).
Your information seems out of date. One issue with the sound, was that neither 64-bit Windows Vista or either version of Windows 7 contains AC97 drivers by default. This has since been mitigated with the addition of the emulated Intel HD Audio card (and selected by default on Windows Vista/7 guests at creation time, so you have to go out of your way to make sound not work). Ethernet is handled by emulating one of two AMD cards or three Intel cards, which guests support what also varies, and VirtualBox is smart enough to pick the appropriate one at VM creation time (assuming you aren't lying about the guest OS type, of course ;)). Shared directories and USB devices, yes they were a pain in the VirtualBox 1.x days, but they have both become quite a breeze (even shared folders from a command-line only Linux guest is as simple as "mount -t vboxsf ShareName /mnt").
Disclaimer: I use Linux as a host operating system and don't have much experience with VirtualBox on other hosts, be it Windows, Mac OS, or Solaris. If it's still troublesome on one of the others, all I can say is "Oh well" and hope the situation improves for you.
I have to agree that forking GNOME 2 isn't quite as appealing as it might first sound. GNOME 3's fallback mode already works excellently (I use it!), and work really ought to be focused on refining that instead.
1. Somehow, Richard Stallman hasn't claimed that OpenBSD is also "the Gnu System".
Probably because it's not GNU, what a shocker. Even though it might sound pedantic of him to keep repeating it, he emphasizes the name GNU/Linux precisely because Linux filled in the kernel void where HURD failed to deliver. On GNU/Linux, you're using the GNU system, just not with the kernel they wanted (for better or worse). This is the same reason that Debian 6.0 and later have an install disc for GNU/kFreeBSD; it's GNU with the kernel of FreeBSD.
OpenBSD (and FreeBSD) are not based on GNU; you can install GNU separately (typically with all their filenames prefixed with the letter g), but it's still not GNU.
Buy three and suddenly you have more RAM than an iMac.
Still only for 32-bit Windows, making CoLinux useless for me.
Since version 1.7, Cygwin is able to make multiple files that differ only in letter casing. You need to make sure the filesystem is enabled for case-sensitivity though (this is also the case with SUA). See http://cygwin.com/cygwin-ug-net/using-specialnames.html#pathnames-casesensitive
He did address them, see the part "Dropbox + encryption". I personally employ GPG on all sensitive data that goes into Dropbox, and it works fine.
I think the other word in the term describes it well enough: "Download"
in the same way that Mac OS X didn't freeze the API at 10.0's state, no.
I've already been doing this, at least for web browsing tasks, with Firefox Sync. It's really the killer feature I think Firefox has over anyone else.
I happily use Iceweasel 5.0 for Debian Squeeze: http://mozilla.debian.net/
OK That's what I get for posting soon after I wake up :P
Except all of the following are true now: 1. Flash is natively x86 64-bit 2. Flash is accelerated, smooth fullscreen on Intel GPUs. 2. Flash is accelerated, smooth fullscreen on NVIDIA GPUs. 2. Flash is accelerated, smooth fullscreen on AMD GPUs.
WebKit seems to be becoming that rather quickly. Chromium/Chrome seems to be the only except that refuses to use a system-wide libwebkit and instead uses its own.
There's a release about every three months, which gives four releases per year. I would say about 4-5 years old. http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=de46c33745f5e2ad594c72f2cf5f490861b16ce1 Oh hey, it's four years old after all.
PayPal also controls your money. There's not much difference.
Indeed, his ranting on Java in particular is somewhat silly given this; it's been fully Unicode safe since the very beginning. If you can type the glyphs directly and don't want to bother with codepoints, then fine, you just do it, assuming you have an editor that is UTF-8 safe, but well, almost all are.
My 1.5TB /home volume on ext4 takes about 50 seconds to fsck. Even faster than "minutes" :p
Sure, pretty everyone with IPv6 has huge swaths of address space. Take for example, a 6to4 address of 2002:1234:4567::/48. You've got 1,208,925,819,614,629,174,706,176 addresses to use for your one IPv4 connection, all machines directly accessible over IPv6. That's just for a single IPv4 link; the IPv6 address space is *huge*, shortage is not going to happen any time soon.
What's wrong with FAT? Pretty much everything from space inefficiency to lack of permissions to filename restrictions to reliability issues, especially after unclean shutdowns.
Also GRUB's core.img already only supports one filesystem -- whichever one is /boot (which can be FAT, GRUB can do that as well), filesystem modules for other types if necessary are loaded directly from said /boot partition.
LVM is the solution to that -- though it's only on Linux and NetBSD so far and Windows has little chance of ever getting native support.
Obviously no software that is legally free is available on Windows as well, right? How much did you pay for Firefox again?
It seems too obvious that this should be done by default, exactly for TFA's reason.
Probably more due to the fact that ext2 cannot go that far out in time without rolling over to 1901 a few times.