Jeff Lasman <[email protected]> wrote:

> I could certainly do the job, but I also fear that Michael won't want to 
> pay my hourly rate.  

I have already worked out an arrangement with another member of this
list whose hourly rate is perfectly reasonable and OK with me.  Let's
see how it works out.

In the meantime I would really prefer for this thread to die.

> I believe from reading Michael's original post and reply that what he's 
> looking for is someone he can trust to follow his philosophy so he 
> doesn't have to get involved in the moment-by-moment decisions.  I 
> could be wrong.

No, you have fit the nail right on the head.

Note to the person with whom I've made the arrangement (assuming he is
reading the list): Jeff has expressed it better than I could.

In another message:

> I believe that anyone of us who's spent more than a few minutes speaking 
> with Michael knows he could certainly run Slackware on his own if he 
> wanted to do so.

I already do, but mostly either without X11 (like on my overflow server*)
or with a very minimal X11 setup (like on the laptop which I bring with
me to SRCLE meetings).  I have done X11 setups under Slackware before,
but oftentimes I end up with a display that looks wrong in a way that
suggests something being not right with the info I've entered about the
video card or about the monitor.  I certainly could spend oodles of time
and extra work to figure it all out and fix it, but I would rather
outsource it if I can.  Life is very short, my time is very expensive,
and I would rather outsource those things that I can outsource so that
I can work on those things that only I can do.

* "overflow server" is my term for a Slackware Linux box (pee sea HW
unfortunately) that runs a few programs I need which would be far too
difficult (i.e., not worthy of my super-expensive time) to port to run
under 4.3BSD-Quasijarus on the VAX.  Hence there are a few tasks which
"overflow" from UNIX to Linux in my workflow.  My normal setup is that
my primary login session resides on the VAX and that's where I run
everything, but for the overflow tasks I have scripts/programs that rsh
to the overflow server behind the scenes feeding the input and output
through pipes.  This way all work is stored on the VAX and to the user
it looks and feels like everything is running on the VAX; the rsh job
submissions to the overflow server are normally invisible to the user.

MS

Reply via email to