LQ Job Marketplace [Archive]NOTE: The new LQ Job Marketplace can be found here.
The LQ Job Marketplace allows you to post available jobs for Linux, Open Source and programming related positions. There is a fee associated with each thread. Please read the guidelines before posting.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
That may have been it's start, but the current Suse releases are clones of RHEL with Novell's proprietary apps tossed in.
and since the FSF's LSB project made rpm the "standard" package manager, every distro has to support rpm at least if they want to be standards compliant. It doesn't matter that rpm is the least capable package manager it is the required format for LSB compliancy.
[ this along with a few other boneheaded decisions is why lsb is not a respected base standard. base standard should stop at the minimal software required to be running linux and installing more software, so the package list for LFS is as far as the LSB should go. ]
Folks -- please keep in mind that threads in the LQ Job Marketplace are not general discussion topics -- they are real, paying jobs being offered to interested Linux users. As such, posting a question about the job opening itself is OK, but comments that are not specifically related to the job being offered are better suited to one of the other technical forums.
1. Do you have a go-live checklist? If so, please attach.
2. What were the factors that had the largest impact on schedule and budget of the migration?
3. What are the biggest risks in such a migration?
I understand that everything is vetted in this forum but the above still doesn't sound quite right. I've never heard of an employer asking for any of this type of documentation. Generally a resume and a list of reference is all that they want. Aside from that it seems it would be preferable to ask the reference how the migration went rather than the potential employee.
This assessment will take place over the next week and will require 2-5 hours of your time. You may telecommute.
According to this and at the time of this particular reply, the "assessment" will likely have been already completed and there will have been less of a need to glean further (free) migration support info from LQ towards this paid position.
Why switch from Suse to RH?
both are "Enterprise Linux" and switching to a newer version of Suse is a far easier Migration, as well as being the same cost or less, for the distro.
[ ignoring the simple fact that Suse is based on RHEL ]
By staying with Suse to be running on the 2.6 kernel it is more an upgrade of the software than a major change, and the current live systems should be able to literally be upgraded with no alteration of configuration.
once the client is using the newst versions of the software, then it's a far simpler task to change distros, if they desire it.
~ crawling back into my hole to continue cross compiling linux from scratch on new multicore 64 bit system my current migration undertaking ~
Other more current positions specifically from this Keystone Strategy Inc
What you are really asking for, Keystone, is a consultation. But the problem is, that is not what you are currently attempting to buy.
What you are saying is, "I want someone to tell my client what they should do, if they decide to do it. And I'm going to pay between 2*$150 and 5*$150 for that. Anybody interested?" And the answer is, I think, a smart and resounding "No!" Which, I think, has taken you by surprise. But it shouldn't.
What you are seeking to buy is an expert opinion. A truly qualified expert is going to carefully interview you and/or your client to assess your needs, is then going to do careful research to prepare a thorough analysis of your various business options, and is going to deliver you a comprehensive and well-reasoned report ... and he or she will assign some additional time to review and to explain those findings to you.
This takes time, and the genuine expert is going to charge you for that time. It will be "time very well spent" to obtain such opinions from not just one but several experts.
It is very clear from your description that you and/or your client are not entirely certain what the issues at hand are, hence you are both in "a discovery phase." So, you're hedging your bets and reinforcing your right to say "so long and thanks for all the fish" and then just walk away. That sounds very sensible, but is such a strategy going to give you what you both want most ... confidence? No, it won't. It will give you neither confidence nor any basis for ever having it.
A truly qualified expert will look at your request and instantly know that there is a much bigger iceberg beneath that surface, and that you most-likely do not know that it is even there. (Warning bells are ringing at this time.) Why, exactly, have you|the-client decided to switch from SUSE to Red Hat? (And who, exactly, is driving that decision? Are you, "who will write the check" (but only if someone writes the expected check to you, otherwise "you shall surely stiff me"), firmly in control of the situation .. or are you not? The expert can only guess, but with years of experience to guide him or her.
If the expert does not dismiss you as "too risky," the expert will want to zero-in on the underlying reasons for what you have presented ... to ascertain whether "shifting from SUSE to Red Hat" will fulfill that underlying business reason or not.
"What a qualified expert's opinion will buy you" is "a position of strength" from which to properly deal with your client's expectations .. even if your client (and even if you) do not know what those things are.
Last edited by sundialsvcs; 09-04-2007 at 07:54 PM.
From the sounds of it they're an NHS hospital (Wales / UK) - they won't have any money then. They probably had to close a ward to pay the outside recruitment agency.
I'd be interested to know too, why change from that OS to the other. At the end of the day with migrations - they're not really any different to installations. You need to know what hardware you'd be installing anything onto, what data they want who to get access to and where that data is currently, and who's all allowed to get access to what parts of the network, from where. It might be an idea to make up one of those personal checklists that's asked for - something modular.
Anyway I know this is old, it just interested me, the discussion that was generated.