RedHat has never been interested in selling a desktop solution
Sure they have. Go back to the Red Hat Linux days, the desktop was the main reason why they got into the business to begin with. It failed miserably though and that's when they switched to the enterprise market.
(just to contradict me, I believe that recently they have a workstation version comming up).
There have been desktop version of RHEL going back to the first version. They actually have two of them, Desktop and Workstation where Workstation is intended for software development while Desktop is meant for regular desktops.
Ubuntu is first and foremost concentrating on the Desktop experience.
If there's something Ubuntu is missing it's focus. They are doing desktop, mobile, tablet and server. Ubuntu Server is extremely popular in the server market, I would guess that's probably their biggest user base.
Steam supports Ubuntu, not Fedora. Ubuntu is what is closest to Windows and Mac as for support. It had wifi connection via GUI two years before Fedora got it.
And if you do not like Unity, you can try Gubuntu. It should look familliar to Fedora as it runs Gnome 3.
Canonical only supports packages which are in main, and most of the alternatives to Unity including Gnome is in universe. You may and often will miss out on important security updates if you use them. I see tons of people install Ubuntu's LTS releases thinking that they can install just about any package and it will be supported for five years, but in reality only a small subset of packages are supported that long and the majority are not supported at all.
You should read the release notes for any RHEL minor release. They do all kind of crazy stuff in their enterprise kernel. The entire KVM virtual machine layer for example, that came in with RHEL 5.2, a minor update that you got automatically. They also break stuff occasionally, but I've not had that happen very often.
You know there are reasons why Jessie is still in testing and has not been released yet? If you want something that works you should use the stable version, which is currently Wheezy.
A developer fixes a bug, and writes a comment on github.
Technically he was @-mentioned (or whatever it's called nowdays), got a notification from the GitHub thread in his email and responded to it from his email. He did not write a comment on GitHub. GitHub took his reply and posted it automatically.
Actually he/she is right. OS X does support running 64 bit binaries on a 32-bit kernel. OS X didn't even have a 64 bit kernel until 10.6 and it wasn't until 10.7 when OS X started to boot into the 64 bit kernel by default, but you could still run 64 bit programs just fine back to 10.2 just as long as you had a 64 bit CPU.
That was exactly his point: you can hire another company to continue the maintenance.
I guess you missed his/her point as well. With Windows you got free updates up until July this year. With Linux you would have had to finance that yourself. Installing Linux in 2003 and paying someone to make updates for you would most likely not have been cheaper.
With Windows, there is no such option even if you were ready to throw cash on the table.
Yep, absolutely. You're screwed once MS stops their support. In their defense though, it is quite good that they provided updates for 12 years.
Naming a book "Storage Essentials" and then not talking about ZFS was a mistake. If you're going to be building any type of NAS, you're going to want to use ZFS for it's scalability, reliability and stability. While you might get away with UFS for a couple of terabytes, you're going to have a bad time of it when you've got 40TB worth of storage space to manage.
Essentials means "the essentials," not "everything you should know about X."
After quickly looking through the table of contents, I don't think there's actually enough room in the book to even introduce ZFS. What should he have taken out? Smart? RAID? Encryption? I would argue that all that is way more "essentials" than ZFS. ZFS deserves its own book.
...and apparently no one got the joke, since Macintoshes don't have internal blu-ray drives or software to play blu-ray discs...
I have not tested myself, I'm not interested in blu-ray. But I believe that you can get it to work on a Mac with VLC.
Re:Might have done that, but OSX is Unix, runs FOS
on
Why Run Linux On Macs?
·
· Score: 1
The bash shell is exactly the same
Actually it is not. Due to political reasons the latest OS X release still ships with an eight year old version of Bash. Sure it's still fine for most users, but you're missing out on eight years of new features.
send them to grep in the right order and use a proper regex with lookarounds. And before you complain about difficulty, it isn't harder to learn that then to learn other commands.
Actually, it is much easier to use the --since and --until flags with journalctl.
I don't know if someone has built a journal viewer for Windows. Nothing would stop that. However, the benefits of using a journal format that preserves meta data is much more useful on a daily basis than the potential downsides when occasionally trying to read the on-disk format from Windows.
Please see the above posts mentioning that even gimp depends on systemd already.
No it doesn't. It depends on dbus which some distros build so that it depends on libsystemd. That's a client-side library for interacting with systemd, if it is installed an running. It is not the init system and it does not even depend on it.
On Debian, gimp, a graphical editing tool, has an indirect systemd dependency!
Gimp depends on dbus, and Debian build dbus so that it depends on libsystemd. Libsystemd is a client-side library for interacting with systemd, if it's installed and running. It's not an init system. It doesn't even depend on it.
Slashdot Mirror
RedHat has never been interested in selling a desktop solution
Sure they have. Go back to the Red Hat Linux days, the desktop was the main reason why they got into the business to begin with. It failed miserably though and that's when they switched to the enterprise market.
(just to contradict me, I believe that recently they have a workstation version comming up).
There have been desktop version of RHEL going back to the first version. They actually have two of them, Desktop and Workstation where Workstation is intended for software development while Desktop is meant for regular desktops.
Ubuntu is first and foremost concentrating on the Desktop experience.
If there's something Ubuntu is missing it's focus. They are doing desktop, mobile, tablet and server. Ubuntu Server is extremely popular in the server market, I would guess that's probably their biggest user base.
Steam supports Ubuntu, not Fedora. Ubuntu is what is closest to Windows and Mac as for support. It had wifi connection via GUI two years before Fedora got it.
And if you do not like Unity, you can try Gubuntu. It should look familliar to Fedora as it runs Gnome 3.
Canonical only supports packages which are in main, and most of the alternatives to Unity including Gnome is in universe. You may and often will miss out on important security updates if you use them. I see tons of people install Ubuntu's LTS releases thinking that they can install just about any package and it will be supported for five years, but in reality only a small subset of packages are supported that long and the majority are not supported at all.
You should read the release notes for any RHEL minor release. They do all kind of crazy stuff in their enterprise kernel. The entire KVM virtual machine layer for example, that came in with RHEL 5.2, a minor update that you got automatically. They also break stuff occasionally, but I've not had that happen very often.
You know there are reasons why Jessie is still in testing and has not been released yet? If you want something that works you should use the stable version, which is currently Wheezy.
A developer fixes a bug, and writes a comment on github.
Technically he was @-mentioned (or whatever it's called nowdays), got a notification from the GitHub thread in his email and responded to it from his email. He did not write a comment on GitHub. GitHub took his reply and posted it automatically.
They have outsourced parts of their business to companies in China, but that does not make them a Chinese company.
The solution is not that Apple should take iMessage to every platform out there, but that we start using open protocols instead like XMPP.
Actually he/she is right. OS X does support running 64 bit binaries on a 32-bit kernel. OS X didn't even have a 64 bit kernel until 10.6 and it wasn't until 10.7 when OS X started to boot into the 64 bit kernel by default, but you could still run 64 bit programs just fine back to 10.2 just as long as you had a 64 bit CPU.
That was exactly his point: you can hire another company to continue the maintenance.
I guess you missed his/her point as well. With Windows you got free updates up until July this year. With Linux you would have had to finance that yourself. Installing Linux in 2003 and paying someone to make updates for you would most likely not have been cheaper.
With Windows, there is no such option even if you were ready to throw cash on the table.
Yep, absolutely. You're screwed once MS stops their support. In their defense though, it is quite good that they provided updates for 12 years.
20 pages are barely enough to even introduce ZFS. Another 200 page book is more reasonable.
Yep, that's why the Roslyn compiler is so interesting.
Yes. And the problem is that VB is MS only. It is a vendor lock in. What about stuents that have a Mac or Linux at home? He chains them to MS.
On Debian 7:
$ uname
Linux
$ vbnc
Visual Basic.Net Compiler version 0.0.0.5943
Copyright (C) 2004-2010 Rolf Bjarne Kvinge. All rights reserved.
Error : VBNC2011: No files to compile! Cannot do anything!
Compilation took 00:00:00.2141430
https://packages.debian.org/je...
Also, the new Microsoft .NET compiler (Roslyn) is open source.
VB.NET is certainly not C# with a different syntax. They both compile to IL and run on the CLR, and they have similar features but they are different.
Naming a book "Storage Essentials" and then not talking about ZFS was a mistake. If you're going to be building any type of NAS, you're going to want to use ZFS for it's scalability, reliability and stability. While you might get away with UFS for a couple of terabytes, you're going to have a bad time of it when you've got 40TB worth of storage space to manage.
Essentials means "the essentials," not "everything you should know about X."
After quickly looking through the table of contents, I don't think there's actually enough room in the book to even introduce ZFS. What should he have taken out? Smart? RAID? Encryption? I would argue that all that is way more "essentials" than ZFS. ZFS deserves its own book.
...and apparently no one got the joke, since Macintoshes don't have internal blu-ray drives or software to play blu-ray discs...
I have not tested myself, I'm not interested in blu-ray. But I believe that you can get it to work on a Mac with VLC.
The bash shell is exactly the same
Actually it is not. Due to political reasons the latest OS X release still ships with an eight year old version of Bash. Sure it's still fine for most users, but you're missing out on eight years of new features.
The iMac is not a laptop.
OS X uses bits and pieces from FreeBSD, but it's not FreeBSD. Not even close.
It makes a lot of sense if you want to edit 4K video at 1:1 resolution and still have space left for palettes and windows.
send them to grep in the right order and use a proper regex with lookarounds. And before you complain about difficulty, it isn't harder to learn that then to learn other commands.
Actually, it is much easier to use the --since and --until flags with journalctl.
I don't know if someone has built a journal viewer for Windows. Nothing would stop that. However, the benefits of using a journal format that preserves meta data is much more useful on a daily basis than the potential downsides when occasionally trying to read the on-disk format from Windows.
How do you make grep give you everything that happened between two arbitrary timestamps and take log rotation into consideration?
journalctl | grep foo
Now that was hard wasn't it?
Ohh, and isn't "Macintosh HD" the default name? Ouch!
Please see the above posts mentioning that even gimp depends on systemd already.
No it doesn't. It depends on dbus which some distros build so that it depends on libsystemd. That's a client-side library for interacting with systemd, if it is installed an running. It is not the init system and it does not even depend on it.
On Debian, gimp, a graphical editing tool, has an indirect systemd dependency!
Gimp depends on dbus, and Debian build dbus so that it depends on libsystemd.
Libsystemd is a client-side library for interacting with systemd, if it's installed and running.
It's not an init system. It doesn't even depend on it.