Azure Jane Lunatic (Azz) 🌺 (![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png)
azurelunatic) wrote2003-09-02 10:42 am
azurelunatic) wrote2003-09-02 10:42 am
Morning
Went to lab, and spent the better part of two hours staring at the guts of a firewall. Propz to me: I'm becoming more proficient at the command-line thing. More propz to me: I made sure that we could get online beforehand. This took some doing. We finally had to call over the Lab Guy (well, in this case, the "petite female" version of guy), who looked at it and told us to do what we'd been doing after verifying that all our information was in order... and it worked.
I showed Sam2 the relevant koan.
I then proceeded to type in the rules for the firewall, line by line, until Sandstrom came over and commented that it would be an awful lot easier if we were putting them in a file, so we could run them later at will. He recommended vi, and told me that actually, the way I was doing it was the way he'd do it, testing first before putting into a file...
Scary and evil things happened, at least from the viewpoint of the Sams; man and -h saw me at least limping through putting stuff into vi, which later proved to be in a way that was... well... not really good, since it wouldn't save to the file I thought it was saving to, was beyond the expertise of the lab guy, and finally required Sandstrom's intervention.
And we never did finish the firewall.
I showed Sam2 the relevant koan.
I then proceeded to type in the rules for the firewall, line by line, until Sandstrom came over and commented that it would be an awful lot easier if we were putting them in a file, so we could run them later at will. He recommended vi, and told me that actually, the way I was doing it was the way he'd do it, testing first before putting into a file...
Scary and evil things happened, at least from the viewpoint of the Sams; man and -h saw me at least limping through putting stuff into vi, which later proved to be in a way that was... well... not really good, since it wouldn't save to the file I thought it was saving to, was beyond the expertise of the lab guy, and finally required Sandstrom's intervention.
And we never did finish the firewall.
no subject
Actually, that's not true. Particle physics isn't that hard.
Next time, try 'pico', or 'nano' (one of those should work - two names for the same program). It's much nicer to use, and tells you at the bottom of the screen the most important keystrokes for controlling it.
It's not as powerful as vi or EMACS, of course, but when you'd rather just get stuff than than learn a new horribly complicated text editor...
no subject
I think Sandstrom overestimates me, because I can be scarily competent without knowing jack.
Of course, this may be a mark of a baby hacker...
no subject
I am an emacs-evangelist. Not to the degree that some people are vivangelists, though.
emacs doesn't have modes so you can't accidentally start typing when you are in the wrong mode and only realise after a few seconds that you've just deleted everything.
On the other hand shift-delete in emacs opens random info files at you which is very doomful when you are typing at 90 wpm!!
for most non code purposes I would say to just use pico.
no subject
no subject
vi, i've always had trouble with.
Pico is great for basics.
I use EMACS once I start needing the bigger stuff.
Its just a matter of having a handy Control cheat sheet.
no subject