Re: [osol-discuss] SUNWscpu ? Am I old fashioned and confused ?

2006-04-24 Thread Joerg Schilling
Dennis Clarke [EMAIL PROTECTED] wrote: So I can not see a reason why a person needs vipw to edit the /etc/passwd file and good old vi ( mine is /usr/xpg4/bin/vi ) will do the job nicely and safely. The correct way may be simply to use usermod(1M) and not ever edit /etc/passwd directly. If

[osol-discuss] SUNWscpu ? Am I old fashioned and confused ?

2006-04-11 Thread Dennis Clarke
This is an important question to me. I have been using UNIX in some flavour and on various systems since about 1984 and am more than able to throw my oversized ego over the wall in the hopes of education and instruction. I have recently run into a situation where I am unclear on what to do. I

Re: [osol-discuss] SUNWscpu ? Am I old fashioned and confused ?

2006-04-11 Thread James Carlson
Dennis Clarke writes: SunOS/BSD Compatibility Package Commands vipw(1B) ^^^ That's a key phrase there. It doesn't say museum artifact, but it could. SYNOPSIS /usr/ucb/vipw [...] This system is a Solaris Neveda build 35 system complete with

Re: [osol-discuss] SUNWscpu ? Am I old fashioned and confused ?

2006-04-11 Thread Darren J Moffat
Dennis Clarke wrote: I recently adopted a style of doing things that may be Linux like and thus a bad thing in the strict UNIX world. I began to put my root user in a home directory of /root along with all of the dot files that get created for PSARC 2003/039 Alternate home directory for root

Re: [osol-discuss] SUNWscpu ? Am I old fashioned and confused ?

2006-04-11 Thread James Dickens
On 4/11/06, Dennis Clarke [EMAIL PROTECTED] wrote: [snip] Do we need vipw to safely edit the /etc/passwd file ? YES!!! absolutely, people make mistakes, and no one wants to go down to the datacenter or even the basement, and boot the system with an emergency disk or install disk to fix

Re: [osol-discuss] SUNWscpu ? Am I old fashioned and confused ?

2006-04-11 Thread Dennis Clarke
Dennis Clarke wrote: I recently adopted a style of doing things that may be Linux like and thus a bad thing in the strict UNIX world. I began to put my root user in a home directory of /root along with all of the dot files that get created for PSARC 2003/039 Alternate home directory for

Re: [osol-discuss] SUNWscpu ? Am I old fashioned and confused ?

2006-04-11 Thread Gavin Maltby
On 04/11/06 15:25, James Dickens wrote: On 4/11/06, Dennis Clarke [EMAIL PROTECTED] wrote: [snip] Do we need vipw to safely edit the /etc/passwd file ? YES!!! absolutely, people make mistakes, and no one wants to go down to the datacenter or even the basement, and boot the system with an

Re: [osol-discuss] SUNWscpu ? Am I old fashioned and confused ?

2006-04-11 Thread Dennis Clarke
On 4/11/06, Dennis Clarke [EMAIL PROTECTED] wrote: [snip] Do we need vipw to safely edit the /etc/passwd file ? YES!!! absolutely, people make mistakes, and no one wants to go down to the datacenter or even the basement, and boot the system with an emergency disk or install disk to

Re: [osol-discuss] SUNWscpu ? Am I old fashioned and confused ?

2006-04-11 Thread Darren J Moffat
Dennis Clarke wrote: It says State : Closed, fixed and thus must be in a patch somewhere for Solaris 10 GA ? Or strictly solaris_nevada(snv_36) ? Probably a patch on the way. Don't know if it is being backported or not. Closed, fixed doesn't imply that there is a backported fix. --

Re: [osol-discuss] SUNWscpu ? Am I old fashioned and confused ?

2006-04-11 Thread Dennis Clarke
On 04/11/06 15:25, James Dickens wrote: On 4/11/06, Dennis Clarke [EMAIL PROTECTED] wrote: [snip] Do we need vipw to safely edit the /etc/passwd file ? YES!!! absolutely, people make mistakes, and no one wants to go down to the datacenter or even the basement, and boot the system with

Re: [osol-discuss] SUNWscpu ? Am I old fashioned and confused ?

2006-04-11 Thread Dennis Clarke
Dennis Clarke wrote: It says State : Closed, fixed and thus must be in a patch somewhere for Solaris 10 GA ? Or strictly solaris_nevada(snv_36) ? Probably a patch on the way. Don't know if it is being backported or not. Closed, fixed doesn't imply that there is a backported fix. Ah