14 Jun
2013
14 Jun
'13
4:14 p.m.
On Wed, Jun 12, 2013 at 05:09:54PM -0600, ben wrote:
[...]
Umm... How do you write Unix software if you are
running windows?
I pick the first off this list based on what the client and/or their
bureaucracy permits me to do:
1) Ignore the client-provided Windows box and do everything on my own Mac
laptop.
2) Wipe said Windows box and install a real operating system.
3) Check my bank balance and/or the job market to decide whether I am in a
position to fire a client that's being silly.
4) Install virtualisation software and boot up a real operating system.
5) Install PuTTY and ssh to a real computer.
6) Install Cygwin and/or other development tools, and hope I don't accidentally
write something non-portable.
7) Give up, because it is impossible to write software now that the client has
vetoed all possible means, so just tread water until my finances and/or the
job market improves then fire the client.
Ben.
PS I keep forgetting that the concept of 'a single user UNIX' was never
a selling point so the PC world never got a UNIX like product for the
86's/286's to replace DOS. OS/9 (6809) did come close but a bit to late
for unix like product.
BeOS was sort of a single user Unix: it was sufficiently POSIXy for me to fire
up a shell prompt and feel at home, although it did not support multiple users
at all.
These days, MacOS X is commonly used as a single-user workstation, even though
it *does* support multiple users.