Has anyone tried porting SMF to Linux? If not, then that isn't exactly portable either.
An interesting thought, but I do not believe that anyone has tried it because of it being CDDL instead of GPL. Those GPL advocates are pretty damn picky about what software you're allowed to use. Also the same reason we do not have launchd on Linux (which people also decried as anti-Unix, for the record).
The GPL people believe in freedom: Freedom to use what they tell you.
Forget systemd - KDE is a common desktop choice on AIX and FreeBSD. The fact that it is much more Unix friendly then GNOME is a talking point in and of itself.
Project: Port KSystemLog to use journald as a backend: With systemd it is actually possible to make a distro agnostic GUI log viewer that isn't just a "less" with windows decorations. I like using the CLI "journalctl", but a GUI, perhaps with some log watch support and real time panel notifications about "syslog level: Error" events and above would be nice.
For KDE, as long as they don't become dependent on systemd they should be okay to do that. One of the strengths of KDE over GNOME is cross platform support, and the devs have shied away to date from breaking compatibility with other UNIX systems. (That's my complaint with systemd anyway - it violates the Unix principle of being portable and compatible).
If they fix the power management bug and implement good error notifications (supporting journald wouldn't be a bad thing), that would be pretty awesome.
I'm looking at several machines that are near me right now - A Core 2 Quad, a Core 2 Duo (HP), a FX-8120, 2 third gen i5s and a first gen i7 (HP). Guess how many of them have serial or parallel ports? I just checked two more AMD boards that are sitting here as well (Sockets AM3 and AM3+) - no ports either.
I've always had much better luck with a fresh install of Linux then with Windows. Especially in situations where it may have been the only computer in the location (I know, not a problem any more). I can point to any number of Dell systems I've had in the past 10 years that worked with Linux (with the exception of some Broadcom cards that you needed NDISWrapper for) - my Precision M4500 is better supported under Linux then under Windows (actually is. Finding drivers for Windows 8.1 for it was a nightmare since Dell doesn't support it and there were issues with some of the Windows 7 drivers). I can point to plenty of Thinkpads and Toshiba Satellites that I have sitting around that I never had to muck with any settings to get to work in Linux either.
When I was in charge of managing UNIX servers, I don't recall ever having major issues with any of the AIX boxes (running AIX 7.1 and 6.1). However, the i-series box (IBM i 7.1 IIRC correctly) liked to lock out any user anything similar to the rights of QSECOFR on a regular basis, and I got plenty of use out of the 5250 emulation on the HMC.
I also had quite a few issues with one of my two HP-UX systems (HP-UX 11iv3 on Itanium, the HP-UX 11 on RISC I don't think anyone ever used).
I was complaining in the Fedora community when it first debuted (which was somewhere around Fedora 14 or 15). I also complained about GRUB 2, posted HOWTOs on keeping GRUB 1, and got laughed at for the thought that I wouldn't want systemd or GRUB2 (or GNOME 3, or a desktop that didn't always 'need' 3D accel, etc).
Last time I checked, SMF and upstart just replace init (Launchd is a bit larger in scope, and I don't think I have heard people complaining about it (now I need to see it changes how to use cron jobs on OS X...)) Nor are they written by someone who is fairly disliked within their own communities. Also, Apple and Sun have a lot more at stake for releasing something that works then Fedora does. Fedora has had plenty of releases that were pure crap over the years - they just shrug it off and move to the next one. Personally, I have fallen in love with the some of the old UNIX systems (my home servers are running IRIX at this point) and how simple things used to be to manage.
Those "few loud haters" translate to a whole bunch of system administrators and IT Managers/Directors who played a very large role in getting Linux to it's place in the datacenter today. We have plenty of options, outside of the systemd infested GNU/Linux world to choose from, so why would we want to bother with a system where the developers don't want us?
Interesting - I wonder why GNUTLS is a depedency (I'm building it from source on IRIX right now, no GNUTLS (currently built) on there). On the GPG website libksba is listed as optional, and npth is listed as 'you don't need it but probably want it'.
I'm all for replacing a lot of GNU software because of issues like that. Tying to build it manually ends up being a nightmare, because a lot of it depends on other GNU software they you may not want on there for various reasons.
Except if you put it in systemd, then it becomes confined to Linux.
Side note, GPG gets used across quite a few platforms (I see OS X, Windows, and VMS listed on the binaries page, and seems to be good on other Unix systems too), so it makes for a great utility for others to be able to use to verify whatever.
Slashdot Mirror
Well, if you are on Slashdot I assume you can google something.
Or that you can infer that they do Network Security from the summary or the title.
My grandmother did them one better....
> "Hello, I'm [her name] from Microsoft Support Service..."
GM: "Sorry, but I don't have a computer"
Has anyone tried porting SMF to Linux? If not, then that isn't exactly portable either.
An interesting thought, but I do not believe that anyone has tried it because of it being CDDL instead of GPL. Those GPL advocates are pretty damn picky about what software you're allowed to use. Also the same reason we do not have launchd on Linux (which people also decried as anti-Unix, for the record).
The GPL people believe in freedom: Freedom to use what they tell you.
Forget systemd - KDE is a common desktop choice on AIX and FreeBSD. The fact that it is much more Unix friendly then GNOME is a talking point in and of itself.
>
Project: Port KSystemLog to use journald as a backend: With systemd it is actually possible to make a distro agnostic GUI log viewer that isn't just a "less" with windows decorations. I like using the CLI "journalctl", but a GUI, perhaps with some log watch support and real time panel notifications about "syslog level: Error" events and above would be nice.
For KDE, as long as they don't become dependent on systemd they should be okay to do that. One of the strengths of KDE over GNOME is cross platform support, and the devs have shied away to date from breaking compatibility with other UNIX systems. (That's my complaint with systemd anyway - it violates the Unix principle of being portable and compatible).
If they fix the power management bug and implement good error notifications (supporting journald wouldn't be a bad thing), that would be pretty awesome.
Can't be - this is cross platform.
Well, Seeing stuff using Motif is getting rare, and not a whole lot uses TCL/TK or LessTif either...
With the exception of the GIMP, maybe they should have used Qt to begin with then. (I would expect the GIMP to use the GIMP Tool Kit, after all).
And quite a few times Spock was the one making the jokes too.
I'm looking at several machines that are near me right now - A Core 2 Quad, a Core 2 Duo (HP), a FX-8120, 2 third gen i5s and a first gen i7 (HP). Guess how many of them have serial or parallel ports? I just checked two more AMD boards that are sitting here as well (Sockets AM3 and AM3+) - no ports either.
A laptop that old probably lacks a CD Drive...and if it has one I'm pretty sure it can't boot to CDROM.
So...stream it from your desktop if you're at home?
So switch to Solaris and use a real UNIX?
I don't know, Slackware's installer always worked well for me :). The old Anaconda on Red Hat worked pretty well too.
I've not tried any BSD on a laptop. I have, however run Solaris/OpenSolaris on my laptops in the past, and that handled surprisingly well.
You're using Slackware?
Why don't you switch to a real UNIX, which uses sysvinit?
That's why I switched my home servers to IRIX...uses a real init system....
BSD init and SMF only replaced init. They didn't attempt to take over the rest of system configuration.
I've always had much better luck with a fresh install of Linux then with Windows. Especially in situations where it may have been the only computer in the location (I know, not a problem any more). I can point to any number of Dell systems I've had in the past 10 years that worked with Linux (with the exception of some Broadcom cards that you needed NDISWrapper for) - my Precision M4500 is better supported under Linux then under Windows (actually is. Finding drivers for Windows 8.1 for it was a nightmare since Dell doesn't support it and there were issues with some of the Windows 7 drivers). I can point to plenty of Thinkpads and Toshiba Satellites that I have sitting around that I never had to muck with any settings to get to work in Linux either.
Really? Because I see plenty of guides and plenty of people who will answer questions about getting XYZ to work with Fedora and Red Hat.
Sun and Ubuntu did replace init, but that's all their replacement did. It didn't creep into other areas and try to take over all of system management.
When I was in charge of managing UNIX servers, I don't recall ever having major issues with any of the AIX boxes (running AIX 7.1 and 6.1). However, the i-series box (IBM i 7.1 IIRC correctly) liked to lock out any user anything similar to the rights of QSECOFR on a regular basis, and I got plenty of use out of the 5250 emulation on the HMC.
I also had quite a few issues with one of my two HP-UX systems (HP-UX 11iv3 on Itanium, the HP-UX 11 on RISC I don't think anyone ever used).
I was complaining in the Fedora community when it first debuted (which was somewhere around Fedora 14 or 15). I also complained about GRUB 2, posted HOWTOs on keeping GRUB 1, and got laughed at for the thought that I wouldn't want systemd or GRUB2 (or GNOME 3, or a desktop that didn't always 'need' 3D accel, etc).
Last time I checked, SMF and upstart just replace init (Launchd is a bit larger in scope, and I don't think I have heard people complaining about it (now I need to see it changes how to use cron jobs on OS X...)) Nor are they written by someone who is fairly disliked within their own communities. Also, Apple and Sun have a lot more at stake for releasing something that works then Fedora does. Fedora has had plenty of releases that were pure crap over the years - they just shrug it off and move to the next one. Personally, I have fallen in love with the some of the old UNIX systems (my home servers are running IRIX at this point) and how simple things used to be to manage.
Those "few loud haters" translate to a whole bunch of system administrators and IT Managers/Directors who played a very large role in getting Linux to it's place in the datacenter today. We have plenty of options, outside of the systemd infested GNU/Linux world to choose from, so why would we want to bother with a system where the developers don't want us?
Interesting - I wonder why GNUTLS is a depedency (I'm building it from source on IRIX right now, no GNUTLS (currently built) on there). On the GPG website libksba is listed as optional, and npth is listed as 'you don't need it but probably want it'.
I'm all for replacing a lot of GNU software because of issues like that. Tying to build it manually ends up being a nightmare, because a lot of it depends on other GNU software they you may not want on there for various reasons.
Except if you put it in systemd, then it becomes confined to Linux. Side note, GPG gets used across quite a few platforms (I see OS X, Windows, and VMS listed on the binaries page, and seems to be good on other Unix systems too), so it makes for a great utility for others to be able to use to verify whatever.
Hey - you can even use Google's TF for your home SSH box.