Re: Basic question

[John Summerfield]

Leslie Turriff wrote:

BTW, If you'd like to use an editor other than vi, the visudo man page
describes the editor and env_editor variables.


In Debian, the default editor is nano. As soon as I see it, I remember to
sudo apt-get remove nano




--

Cheers
John

-- spambait
1...@coco.merseine.nu  z1...@coco.merseine.nu
-- Advice
http://webfoot.com/advice/email.top.php
http://www.catb.org/~esr/faqs/smart-questions.html
http://support.microsoft.com/kb/555375

You cannot reply off-list:-)

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

X2 advantages (was Re: Basic question)

[Leslie Turriff]

As a former user of CMS' Xedit, what I like about X2 is the ability to use
Xeditish command line commands, and to easily make both block and line
selections without having to take my hands off the keyboard to use the mouse.

Configuration is a bit problematic in Linux, but the Windows version looks
pretty good. :-(

Leslie

On Wednesday 31 December 2008, Smith, Ann (ISD, IT) wrote:
> I actually still use THE editor on SLES10 (The Hessling Editor). I've
> never tried X2.
> I'm still upset that Mansfield software won't be supporting KEDIT for
> Windows any more.
> I will check out X2.
[ snip ]

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

Re: Basic question

[Wayne Henley]

I recommend visudo.

~ Wayne





From: "Smith, Ann (ISD, IT)" 
To: LINUX-390@VM.MARIST.EDU
Sent: Wednesday, December 31, 2008 12:28:11 PM
Subject: Basic question

I need to update sudoers and don't know proper procedure.
Figured I'd ask before I mess it up. I did at least create a backup of
/etc/sudoers

This communication, including attachments, is for the exclusive use of 
addressee and may contain proprietary, confidential and/or privileged 
information.  If you are not the intended recipient, any use, copying, 
disclosure, dissemination or distribution is strictly prohibited.  If you are 
not the intended recipient, please notify the sender immediately by return 
e-mail, delete this communication and destroy all copies.


--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

Re: Basic question

[Adam Thornton]

On Dec 31, 2008, at 11:28 AM, Smith, Ann (ISD, IT) wrote:


I need to update sudoers and don't know proper procedure.
Figured I'd ask before I mess it up. I did at least create a backup of
/etc/sudoers


visudo, usually.

Set your EDITOR environment variable (or VISUAL) to the editor you
prefer.

Adam

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

Re: Basic question

[Douglas Wooster]

There's also a version of THE for Windows.  It's up to 3.3 beta 3 on
http://sourceforge.net/projects/hessling-editor/ .  That said, X2 looks a
lot more usable now than it did the last time I looked at it.

Douglas
Hooray for command lines!



From:
"Smith, Ann (ISD, IT)" 
To:
LINUX-390@VM.MARIST.EDU
Date:
12/31/2008 02:27 PM
Subject:
Re: [LINUX-390] Basic question



I actually still use THE editor on SLES10 (The Hessling Editor). I've
never tried X2.
I'm still upset that Mansfield software won't be supporting KEDIT for
Windows any more.
I will check out X2.

In this case I used VISUDO just because the customer insisted they still
did not have sudo.
In the end he was just having a bad day and forgot to type 'sudo' before
the command.
The sudoers file was actually okay.



-Original Message-
From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of
Leslie Turriff
Sent: Wednesday, December 31, 2008 1:14 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Basic question

BTW, If you'd like to use an editor other than vi, the visudo man page
describes the editor and env_editor variables.  (My preferred editor is
the
X2 Programmer's Editor by Blair W. Thompson
<http://www.tangbu.com/x2main.shtml>)

>From the visudo man page:
editor

A colon (':') separated list of editors allowed to be used with visudo.
visudo will choose the editor that matches the user's EDITOR environment
variable if possible, or the first editor in the list that exists and is
executable.  The default is the path to vi on your system.

env_editor

If set, visudo will use the value of the EDITOR or VISUAL environment
variables before falling back on the default editor list.  Note that
this may create a security hole as it allows the user to run any
arbitrary command as root without logging.  A safer alternative is to
place a colon-separated list of editors in the editor variable.  visudo
will then only use the EDI TOR or VISUAL if they match a value specified
in editor.  This flag is on by default.

Leslie Turriff

On Wednesday 31 December 2008, Smith, Ann (ISD, IT) wrote:
> I need to update sudoers and don't know proper procedure.
> Figured I'd ask before I mess it up. I did at least create a backup of

> /etc/sudoers

--
For LINUX-390 subscribe / signoff / archive access instructions, send
email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
visit http://www.marist.edu/htbin/wlvindex?LINUX-390

This communication, including attachments, is for the exclusive use of
addressee and may contain proprietary, confidential and/or privileged
information.  If you are not the intended recipient, any use, copying,
disclosure, dissemination or distribution is strictly prohibited.  If you
are not the intended recipient, please notify the sender immediately by
return e-mail, delete this communication and destroy all copies.


--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
visit
http://www.marist.edu/htbin/wlvindex?LINUX-390



--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

Re: Basic question

[Smith, Ann (ISD, IT)]

I actually still use THE editor on SLES10 (The Hessling Editor). I've
never tried X2.
I'm still upset that Mansfield software won't be supporting KEDIT for
Windows any more.
I will check out X2.

In this case I used VISUDO just because the customer insisted they still
did not have sudo.
In the end he was just having a bad day and forgot to type 'sudo' before
the command.
The sudoers file was actually okay.

   

-Original Message-
From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of
Leslie Turriff
Sent: Wednesday, December 31, 2008 1:14 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Basic question

BTW, If you'd like to use an editor other than vi, the visudo man page
describes the editor and env_editor variables.  (My preferred editor is
the
X2 Programmer's Editor by Blair W. Thompson
<http://www.tangbu.com/x2main.shtml>)

>From the visudo man page:
editor

A colon (':') separated list of editors allowed to be used with visudo.
visudo will choose the editor that matches the user's EDITOR environment
variable if possible, or the first editor in the list that exists and is
executable.  The default is the path to vi on your system.

env_editor

If set, visudo will use the value of the EDITOR or VISUAL environment
variables before falling back on the default editor list.  Note that
this may create a security hole as it allows the user to run any
arbitrary command as root without logging.  A safer alternative is to
place a colon-separated list of editors in the editor variable.  visudo
will then only use the EDI TOR or VISUAL if they match a value specified
in editor.  This flag is on by default.

Leslie Turriff

On Wednesday 31 December 2008, Smith, Ann (ISD, IT) wrote:
> I need to update sudoers and don't know proper procedure.
> Figured I'd ask before I mess it up. I did at least create a backup of

> /etc/sudoers

--
For LINUX-390 subscribe / signoff / archive access instructions, send
email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
visit http://www.marist.edu/htbin/wlvindex?LINUX-390

This communication, including attachments, is for the exclusive use of 
addressee and may contain proprietary, confidential and/or privileged 
information.  If you are not the intended recipient, any use, copying, 
disclosure, dissemination or distribution is strictly prohibited.  If you are 
not the intended recipient, please notify the sender immediately by return 
e-mail, delete this communication and destroy all copies.


--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

Re: Basic question

[Leslie Turriff]

BTW, If you'd like to use an editor other than vi, the visudo man page 
describes the editor and env_editor variables.  (My preferred editor is the 
X2 Programmer's Editor by Blair W. Thompson 
)

From the visudo man page:
editor

A colon (':') separated list of editors allowed to be used with visudo.
visudo will choose the editor that matches the user's EDITOR environment
variable if possible, or the first editor in the list that exists and is
executable.  The default is the path to vi on your system.

env_editor

If set, visudo will use the value of the EDITOR or VISUAL environment 
variables before falling back on the default editor list.  Note that this may
create a security hole as it allows the user to run any arbitrary command
as root without logging.  A safer alternative is to place a colon-separated
list of editors in the editor variable.  visudo will then only use the EDI TOR 
or VISUAL if they match a value specified in editor.  This flag is on
by default.

Leslie Turriff

On Wednesday 31 December 2008, Smith, Ann (ISD, IT) wrote:
> I need to update sudoers and don't know proper procedure.
> Figured I'd ask before I mess it up. I did at least create a backup of
> /etc/sudoers

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

Re: Basic question

[Mark Post]

>>> On 12/31/2008 at  1:00 PM, "Smith, Ann (ISD, IT)" 
>>> 
wrote: 
> I will try visudo then.
> I take it the changes take effect immediately? No other commands needed?

Correct.  Every time the sudo command is issued, it reads the contents of 
/etc/sudoers.


Mark Post

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

Re: Basic question

[Smith, Ann (ISD, IT)]

I will try visudo then.
I take it the changes take effect immediately? No other commands needed?


-Original Message-
From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of
Mark Post
Sent: Wednesday, December 31, 2008 12:48 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Basic question

>>> On 12/31/2008 at 12:28 PM, "Smith, Ann (ISD, IT)" 
>>> 
wrote: 
> I need to update sudoers and don't know proper procedure.
> Figured I'd ask before I mess it up. I did at least create a backup of

> /etc/sudoers

The only safe way is to use visudo.  It syntax checks the file before
rewriting it, and gives you a chance to fix any problems.


Mark Post

--
For LINUX-390 subscribe / signoff / archive access instructions, send
email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
visit http://www.marist.edu/htbin/wlvindex?LINUX-390

This communication, including attachments, is for the exclusive use of 
addressee and may contain proprietary, confidential and/or privileged 
information.  If you are not the intended recipient, any use, copying, 
disclosure, dissemination or distribution is strictly prohibited.  If you are 
not the intended recipient, please notify the sender immediately by return 
e-mail, delete this communication and destroy all copies.


--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

Re: Basic question

[Mark Post]

>>> On 12/31/2008 at 12:28 PM, "Smith, Ann (ISD, IT)" 
>>> 
wrote: 
> I need to update sudoers and don't know proper procedure.
> Figured I'd ask before I mess it up. I did at least create a backup of
> /etc/sudoers

The only safe way is to use visudo.  It syntax checks the file before rewriting 
it, and gives you a chance to fix any problems.


Mark Post

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

Re: Basic question

[Rob van der Heij]

On Wed, Dec 31, 2008 at 6:28 PM, Smith, Ann (ISD, IT)
 wrote:
> I need to update sudoers and don't know proper procedure.
> Figured I'd ask before I mess it up. I did at least create a backup of
> /etc/sudoers

visudo is a wrapper that invokes vi to edit the file and then
validates it before replacing the old one. I have always found this
overkill. But I guess when sudo is all you have to change things back,
then it may be worth to prevent locking yourself out. I don't know how
thorough the check is.

Rob

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

Basic question

[Smith, Ann (ISD, IT)]

I need to update sudoers and don't know proper procedure.
Figured I'd ask before I mess it up. I did at least create a backup of
/etc/sudoers

This communication, including attachments, is for the exclusive use of 
addressee and may contain proprietary, confidential and/or privileged 
information.  If you are not the intended recipient, any use, copying, 
disclosure, dissemination or distribution is strictly prohibited.  If you are 
not the intended recipient, please notify the sender immediately by return 
e-mail, delete this communication and destroy all copies.


--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

Re: Help with basic question Linux/390

[[EMAIL PROTECTED]]

AGREE !! I tried MANY MANY Windows FTP clients and they all gave me
headaches, just put up a linux FTP server and IT WILL WORK FINE.
Ken Dreger
Cornerstone Systems INC.




At 12:28 PM 6/15/2002 +0200, you wrote:
>hi,
>
>I had the same problem using FTP-Install (I ran Bison FTP-Server on Windows
>NT). I could not find out wether it was a bug in the install-script when
>using (Windows) FTP-server - it just did not work correctly. I decided to
>use my Linux-Labtop and did a reinstall using NFS-Method and completed the
>installation without any problems. Conclusion: Do not!!! use Windows, you
>may run  into problems.
>Regards
>
>
> Original Message -
>From: "Carlos A. Bodra" <[EMAIL PROTECTED]>
>To: <[EMAIL PROTECTED]>
>Sent: Saturday, June 15, 2002 6:23 AM
>Subject: Help with basic question Linux/390
>
>
> > Hi,
> >
> > I4m new to Linux world so some stupid questions could arise!
> >
> > 1 - I downloaded Suse 7.0 - 2.4.7 Kernel Level.- CD1 and CD2
> > 2 - IPLed from VM/ESA RDR as described in manuals.
> > 3 - As IPL completed, I run INSMOD DASD DASD=200-201
> > 4 - 200 was choose as swap device - no problem.
> > 5 - 201 was choose as "/"
> > 6 - 202 was choose as "/USR"
> > 7 - Create and mounting filesystems msg arises OK.
> > 8 - Install from scratch
> > 9 - Install method is FTP
> > 10 - I filled in ftp server information screen and hit F5 (check)
> > receive Settings OK
> > 11 - Now press F10 and process start. - Now I receive a note: No kernel
> > images found on server.
> > 12 - The process continues but I never receive Selecting software
> > configuration screen .
> > 13 - From item 11 I receive a pop-up window with options Load
> > Configuration, Save Configuration, Change/Create etc..
> > 14 - I selected Start Installation and all runs (about 52 packages) well.
> > 15 - Receive Installation Complete msg
> > 16 - Now main problem: I never receive a pop-up window with Select a
>Kernel.
> >
> > So, if YaST is an automated process why I can4t get it correct? I
> > already read and read again
> > all IBM redbooks and Suse doc about installing under VM and can4t find
> > where is my mistake.
> > Anyone get something similar? Anyone can explain me why I can4t see all
> > correct windows?
> > All FTP of CD1/CD2 from Suse ftp site ended ok, so it4s complete.
> >
> > Thanks in advance for any tip or ideiaabout.
> >
> > --
> > Carlos Alberto Bodra
> > VM/VSE System Consultant and Linux/390 rookie!
> > Sao Paulo - Brazil
> >

Re: Help with basic question Linux/390

[Ferguson, Neale]

What are you using as your FTP server? If it's Windows then it can't read
all the files on the CD which includes the kernel. Try using a Linux box to
serve the files.

> -Original Message-
> 11 - Now press F10 and process start. - Now I receive a note:
> No kernel
> images found on server.

Re: Help with basic question Linux/390

[Joachim Schmidt]

hi,

I had the same problem using FTP-Install (I ran Bison FTP-Server on Windows
NT). I could not find out wether it was a bug in the install-script when
using (Windows) FTP-server - it just did not work correctly. I decided to
use my Linux-Labtop and did a reinstall using NFS-Method and completed the
installation without any problems. Conclusion: Do not!!! use Windows, you
may run  into problems.
Regards


 Original Message -
From: "Carlos A. Bodra" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Saturday, June 15, 2002 6:23 AM
Subject: Help with basic question Linux/390


> Hi,
>
> I4m new to Linux world so some stupid questions could arise!
>
> 1 - I downloaded Suse 7.0 - 2.4.7 Kernel Level.- CD1 and CD2
> 2 - IPLed from VM/ESA RDR as described in manuals.
> 3 - As IPL completed, I run INSMOD DASD DASD=200-201
> 4 - 200 was choose as swap device - no problem.
> 5 - 201 was choose as "/"
> 6 - 202 was choose as "/USR"
> 7 - Create and mounting filesystems msg arises OK.
> 8 - Install from scratch
> 9 - Install method is FTP
> 10 - I filled in ftp server information screen and hit F5 (check)
> receive Settings OK
> 11 - Now press F10 and process start. - Now I receive a note: No kernel
> images found on server.
> 12 - The process continues but I never receive Selecting software
> configuration screen .
> 13 - From item 11 I receive a pop-up window with options Load
> Configuration, Save Configuration, Change/Create etc..
> 14 - I selected Start Installation and all runs (about 52 packages) well.
> 15 - Receive Installation Complete msg
> 16 - Now main problem: I never receive a pop-up window with Select a
Kernel.
>
> So, if YaST is an automated process why I can4t get it correct? I
> already read and read again
> all IBM redbooks and Suse doc about installing under VM and can4t find
> where is my mistake.
> Anyone get something similar? Anyone can explain me why I can4t see all
> correct windows?
> All FTP of CD1/CD2 from Suse ftp site ended ok, so it4s complete.
>
> Thanks in advance for any tip or ideiaabout.
>
> --
> Carlos Alberto Bodra
> VM/VSE System Consultant and Linux/390 rookie!
> Sao Paulo - Brazil
>

Help with basic question Linux/390

[Carlos A. Bodra]

Hi,

I4m new to Linux world so some stupid questions could arise!

1 - I downloaded Suse 7.0 - 2.4.7 Kernel Level.- CD1 and CD2
2 - IPLed from VM/ESA RDR as described in manuals.
3 - As IPL completed, I run INSMOD DASD DASD=200-201
4 - 200 was choose as swap device - no problem.
5 - 201 was choose as "/"
6 - 202 was choose as "/USR"
7 - Create and mounting filesystems msg arises OK.
8 - Install from scratch
9 - Install method is FTP
10 - I filled in ftp server information screen and hit F5 (check)
receive Settings OK
11 - Now press F10 and process start. - Now I receive a note: No kernel
images found on server.
12 - The process continues but I never receive Selecting software
configuration screen .
13 - From item 11 I receive a pop-up window with options Load
Configuration, Save Configuration, Change/Create etc..
14 - I selected Start Installation and all runs (about 52 packages) well.
15 - Receive Installation Complete msg
16 - Now main problem: I never receive a pop-up window with Select a Kernel.

So, if YaST is an automated process why I can4t get it correct? I
already read and read again
all IBM redbooks and Suse doc about installing under VM and can4t find
where is my mistake.
Anyone get something similar? Anyone can explain me why I can4t see all
correct windows?
All FTP of CD1/CD2 from Suse ftp site ended ok, so it4s complete.

Thanks in advance for any tip or ideiaabout.

--
Carlos Alberto Bodra
VM/VSE System Consultant and Linux/390 rookie!
Sao Paulo - Brazil