Probably realistic, we seem to be reaching another nice convergence of stability points. Things just tend to build and work without much of a fight nowadays;-)
This is a very sticky situation to be in, because you are damned either way. When the old PIX gets overrun they aren't going to care that you warned them beforehand (keep all memos, meeting minutes, emails), they are gonna come after you because you failed to protect their network.
If the folks you work with aren't savvy enough to understand the risks, you have a hard sell. Best you can do is try to protect them in spite of themselves. Personally I'd grab a spare box, slap OpenBSD or a minimal linux distro on it, set it up as a firewall (std or bridging) then do a stealth deployment out of hours putting it between the PIX and the rest of the network.
You may get some grief about it, but it is gonna be a lot less grief than having your network compromised
As for the laptops etc, they are out of your hands if there is no buy-in from management. Not much you can do...
I'll just go and hide in a hole and smash my teeth up with a hammer to get at those damn transmitters they keep putting in my mouth, damnit... always listenening to every word I say...
Wha! was that a black helicopter going overhead?
/me wraps himself in tinfoil
Re:Yes, Debian supports multiple gcc versions.
on
The Future of NetBSD
·
· Score: 1
So can anyone else if gcc is built and installed to the same prefix using --enable-version-specific-runtime-libs and specifying a suffix during configure.
This also applies to any cross-compilers you have.
Switch versions with the -V switch, switch arches with -b
First I'll preface this with the fact that I am a linux zealout.
I'm afraid that the great thing in NetBSD - which is multiple platforms support - will soon be irrelevant, since linux already supports all the currently-used architectures.
For the well trodden path (ix86, ppc, ultrasparc) you are correct, linux works well.
However, once you leave those for say
mac-m68k - broken ADB, broken serial console - you have a nice brick, and the maintainer is asleep at the wheel and has been so since 2.2 kernel
sun4m - hypersparc broken, SMP supersparc broken, but at least this may be fixed sometime
On the glibc side look at all the arches disappearing into non-core maintenance in the glibc-ports tree
NetBSD is there to keep the old stuff running where everyone else on the planet tends to leave them to die.
I have to wholeheartedly agree with your approach.
I personally have reached the point where I may check my email accounts maybe once a week if I am lucky.
If folks need me they have a few options.
* For conversations, telephone, IM, IRC. There is no way in hell I am wasting my time on an endless email conversation when it will only take me 30 seconds to tell you in person.
* For tasks, lodge a trouble ticket in the queue or assign the bug to me (I'll see it when I refresh)
* You want a meeting? Put it in my calender.
* You want to spam the company with meaningless corporate crap, put it up on the website so I can ignore it there instead.
Due to the above policy my productivity has at least doubled, and everything of importance is done in a timely manner. Email is a millstone around the neck of the modern worker, utterly abused for tasks it was never meant for.
Heh, we refer to it as Bloatus Croaks.
If I had a dollar for every flame I have gotten for using Notes (be it due to notes eating the in reply to header fscking up the threading, totally screwing up the formatting (when I say text only I MEAN text only)...) I would be a rich rich man.
/me waves away the crack smoke coming from Tom Yagers pipe
Sure, just what the datacentre wants, ANOTHER bloody OS/Arch/Vendor to add to the support list.
The only thing I see happening, especially in traditional Sun environments, is the trend of
replacing arbitrary linux distros on x86 boxen (usually webservers) or entry level sparc servers with solaris 10 x86 on amd64.
When you have to maintain 100+ boxen you generally want to standardise on both OS and architecture, and if you cant standardise on architecture, you at least standardise on OS.
With Solaris or Linux this is possible on arbitrary x86 platforms or ultrasparc systems.
Unless apple allows folks to boot MacOS on arbitrary x86 systems or in VM's, only the deluded could possibly believe it will replace ANYTHING in the datacentre
Slashdot Mirror
Most likely it is there to keep their current fanclub happy in an attempt to try to stop the developer bleed off to JSP/PHP/etc.
Probably realistic, we seem to be reaching another nice convergence of stability points. Things just tend to build and work without much of a fight nowadays;-)
This is a very sticky situation to be in, because you are damned either way. When the old PIX gets overrun they aren't going to care that you warned them beforehand (keep all memos, meeting minutes, emails), they are gonna come after you because you failed to protect their network.
If the folks you work with aren't savvy enough to understand the risks, you have a hard sell. Best you can do is try to protect them in spite of themselves. Personally I'd grab a spare box, slap OpenBSD or a minimal linux distro on it, set it up as a firewall (std or bridging) then do a stealth deployment out of hours putting it between the PIX and the rest of the network.
You may get some grief about it, but it is gonna be a lot less grief than having your network compromised
As for the laptops etc, they are out of your hands if there is no buy-in from management. Not much you can do...
Maybe someone should start selling off the titles for ontario's land titles departments or of their local members of parliament.
Pretty sure you'd find their response to these actions would change rather quickly methinks.
I'll just go and hide in a hole and smash my teeth up with a hammer to get at those damn transmitters they keep putting in my mouth, damnit... always listenening to every word I say...
/me wraps himself in tinfoil
Wha! was that a black helicopter going overhead?
So can anyone else if gcc is built and installed to the same prefix using --enable-version-specific-runtime-libs and specifying a suffix during configure.
This also applies to any cross-compilers you have.
Switch versions with the -V switch, switch arches with -b
For the well trodden path (ix86, ppc, ultrasparc) you are correct, linux works well.
However, once you leave those for say
On the glibc side look at all the arches disappearing into non-core maintenance in the glibc-ports tree
NetBSD is there to keep the old stuff running where everyone else on the planet tends to leave them to die.
I have to wholeheartedly agree with your approach.
I personally have reached the point where I may check my email accounts maybe once a week if I am lucky.
If folks need me they have a few options.
* For conversations, telephone, IM, IRC. There is no way in hell I am wasting my time on an endless email conversation when it will only take me 30 seconds to tell you in person.
* For tasks, lodge a trouble ticket in the queue or assign the bug to me (I'll see it when I refresh)
* You want a meeting? Put it in my calender.
* You want to spam the company with meaningless corporate crap, put it up on the website so I can ignore it there instead.
Due to the above policy my productivity has at least doubled, and everything of importance is done in a timely manner. Email is a millstone around the neck of the modern worker, utterly abused for tasks it was never meant for.
Heh, we refer to it as Bloatus Croaks. If I had a dollar for every flame I have gotten for using Notes (be it due to notes eating the in reply to header fscking up the threading, totally screwing up the formatting (when I say text only I MEAN text only)...) I would be a rich rich man.
/me waves away the crack smoke coming from Tom Yagers pipe
Sure, just what the datacentre wants, ANOTHER bloody OS/Arch/Vendor to add to the support list.
The only thing I see happening, especially in traditional Sun environments, is the trend of replacing arbitrary linux distros on x86 boxen (usually webservers) or entry level sparc servers with solaris 10 x86 on amd64.
When you have to maintain 100+ boxen you generally want to standardise on both OS and architecture, and if you cant standardise on architecture, you at least standardise on OS.
With Solaris or Linux this is possible on arbitrary x86 platforms or ultrasparc systems.
Unless apple allows folks to boot MacOS on arbitrary x86 systems or in VM's, only the deluded could possibly believe it will replace ANYTHING in the datacentre