Unix Question (really stupid question)
#1
Scooby Regular
Thread Starter
Join Date: May 2001
Location: Scotland
Posts: 4,580
Likes: 0
Received 0 Likes
on
0 Posts
A simple question ( if you know unix, personally I'm an NT bod )
We've got a Raptor install on Solaris, I've been told only to use vi to edit configs, host's etc and never to use the text editor as it "could screw things up"
Is this true???
John
We've got a Raptor install on Solaris, I've been told only to use vi to edit configs, host's etc and never to use the text editor as it "could screw things up"
Is this true???
John
#2
Never heard of it. Probably the purpetrator of the rumour was of the vi collective who thinks emacs is the work of the devil.
Learn and use vi anyhow, as its the one editor that is almost guaranteed to be on your system no matter what (unless you *really* like pain and want to learn edit). It's so straightforward! H=cursor left, K=cursor up...
Learn and use vi anyhow, as its the one editor that is almost guaranteed to be on your system no matter what (unless you *really* like pain and want to learn edit). It's so straightforward! H=cursor left, K=cursor up...
#3
Yes I'm afraid that's right.
Other editors such as emacs can treat carriage return and line feeds in a different way to which some programs expect and can therefore cause your system to **** up.
I remember writing a script that would rebuild 250Gb of logical disks in HVM in emacs, but because I had the wrong settings the script fell over and left me having to delete all the logical disks and manually go in and find the lines with the extra info in. It was ok, cus it was a DR test, but it still was annoying.
Vi is a major pain the *** to use, but it's also one of the few editors that work in single user mode(on standard UNIX systems).
I liked and used emacs whenever I could, but for system config stuff like fstab's etc then i'd use vi because of the above reasons
[This message has been edited by Neil Smalley (edited 08 June 2001).]
Other editors such as emacs can treat carriage return and line feeds in a different way to which some programs expect and can therefore cause your system to **** up.
I remember writing a script that would rebuild 250Gb of logical disks in HVM in emacs, but because I had the wrong settings the script fell over and left me having to delete all the logical disks and manually go in and find the lines with the extra info in. It was ok, cus it was a DR test, but it still was annoying.
Vi is a major pain the *** to use, but it's also one of the few editors that work in single user mode(on standard UNIX systems).
I liked and used emacs whenever I could, but for system config stuff like fstab's etc then i'd use vi because of the above reasons
[This message has been edited by Neil Smalley (edited 08 June 2001).]
#4
Scooby Regular
Join Date: Mar 2001
Location: Derbyshire
Posts: 4,496
Likes: 0
Received 0 Likes
on
0 Posts
Sometimes
I use vi all the time at work (in my leading edge technology company ) and we much prefer it over the standard notepad style editors.
Don't use emacs personally as I like vi
Only problem with vi is that it is not the most intuitive of editors, although it is one of the most powerful (if you can write gobble-de-gook commands )
The vuepad editor I've used (on HPUX) can put erroneous characters at the end of files (as mentioned). This caused us no end of grief when compiling source code as the compiler interprets it with some bizarre message
(Edit : misread original post...thought it was 'complaining' about vi!)
[This message has been edited by Hanslow (edited 08 June 2001).]
I use vi all the time at work (in my leading edge technology company ) and we much prefer it over the standard notepad style editors.
Don't use emacs personally as I like vi
Only problem with vi is that it is not the most intuitive of editors, although it is one of the most powerful (if you can write gobble-de-gook commands )
The vuepad editor I've used (on HPUX) can put erroneous characters at the end of files (as mentioned). This caused us no end of grief when compiling source code as the compiler interprets it with some bizarre message
(Edit : misread original post...thought it was 'complaining' about vi!)
[This message has been edited by Hanslow (edited 08 June 2001).]
#5
Scooby Regular
Thread Starter
Join Date: May 2001
Location: Scotland
Posts: 4,580
Likes: 0
Received 0 Likes
on
0 Posts
Thanks for the replies...i was wondering if it was the guy who put the firewall in just wanting to make things look so highly complex that we call him whenever we need to add a static route!!!
I'm gonna have to learn to use vi by the sounds what fun
Cheerz
I'm gonna have to learn to use vi by the sounds what fun
Cheerz
#7
After I learned vi, I wanted to master it. Eventually I encountered:
The Ultimate Guide to the VI and EX Text Editors by Hewlett-Packard Company, ISBN 0-8053-4460-8, HP part number 97005-90015, Benjamin/Cummings Publishing Company, Inc.
See Amazon US
The Ultimate Guide to the VI and EX Text Editors by Hewlett-Packard Company, ISBN 0-8053-4460-8, HP part number 97005-90015, Benjamin/Cummings Publishing Company, Inc.
See Amazon US
Trending Topics
#8
Scooby Regular
Join Date: Sep 2001
Location: Kingston ( Surrey, not Jamaica )
Posts: 4,670
Likes: 0
Received 0 Likes
on
0 Posts
There's no problem using a text editor under normal circumstances, as long as you know enough sed to strip out all the poxy ^M 's that get inserted.
Our developers took weeks to figure out they could turn off these control characters in ColdFusion Studio, and I'm still cleaning the mess up. The application works with them left in, but I'm a purist ......
:0,$s/[ctrl-v][ctrl-m]//g works for me
SteveM
Our developers took weeks to figure out they could turn off these control characters in ColdFusion Studio, and I'm still cleaning the mess up. The application works with them left in, but I'm a purist ......
:0,$s/[ctrl-v][ctrl-m]//g works for me
SteveM
#10
Scooby Regular
Join Date: Oct 2000
Location: Surrey, UK
Posts: 8,384
Likes: 0
Received 0 Likes
on
0 Posts
Raptor to firewalls are so secure, that if your not careful it stops you from remotely managing it.. a lesson some collegues of mine learned at my last place of work
And yes, vi the files (as loadsa people said above
And yes, vi the files (as loadsa people said above
Thread
Thread Starter
Forum
Replies
Last Post
Brzoza
Engine Management and ECU Remapping
1
02 October 2015 05:26 PM