Re: bad installation ?

2005-02-23 Thread Alexander Gottwald
On Wed, 23 Feb 2005, Banibrata Dutta wrote:

> I had installed Cygwin as "Administrator" for this machine, and I am
> able to successfully run X by doing cygwin terminal when I am logged
> in as "Administrator", but when I am logged in as "dutta" the above
> behaviour is what I see. Could someone please help ?

Make sure you have access rights to the folder where cygwin and XWin 
in particular is installed. Also check that there are no stale user mounts
and the global mounts are in place

$ mount
C:\cygwin\bin on /usr/bin type system (binmode)
C:\cygwin\lib on /usr/lib type system (binmode)
...


bye
ago
-- 
 [EMAIL PROTECTED] 
 http://www.gotti.org   ICQ: 126018723


RE: bad installation ?

2005-03-09 Thread Phil Betts
On Wednesday, February 23, 2005 6:23 PM, Banibrata Dutta wrote:
> Could anybody explain the following behaviour or Cygwin and "startx"
> in Cygwin...
> 
> 
> 
> Your group is currently "mkpasswd". This indicates that
> the /etc/passwd (and possibly /etc/group) files should be rebuilt.
> See the man pages for mkpasswd and mkgroup then, for example, run
> mkpasswd -l [-d] > /etc/passwd
> mkgroup  -l [-d] > /etc/group
> Note that the -d switch is necessary for domain users.

 

> Could someone please help ?

Did you actually *read* what you posted?

It tells you all you need to know.

**
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.

This footnote also confirms that this email message has been swept by
MIMEsweeper for the presence of computer viruses.

www.mimesweeper.com
**


RE: bad installation ?

2005-03-09 Thread Matthew Johnson
Well, Phil, I read what she posted, and I do NOT think
it tells "all Banibrata needs to know".

The big unanswered question that is probably still
bothering Banibrata is, "how on earth did the group
get to be 'mkpasswd' in the first place?" I very much
doubt that Banibrata set it to that. And I have never
seen that in Cygwin or Cygwin/X before. So it sounds
like some drastic error condition did this. And if it
did, who knows what _else_ is messed up in the
installation? THAT is what Banitrata needs to know; it
was NOT contained in the message.

Another thing Banibrata needs to know that was not
explained is which of the FOUR methods of rebuilding
the password file is appropriate for this condition.

Now it may very well be that the readers of the list
cannot answer this for Banibrata, since it varies from
case to case, and Banibrata simply has to knuckle-down
and read the man pages. But even if this is the case,
some guidelines for how to intepret the man pages
would be the right, helpful response.

To that end, I propose to Banibrata the following
questions:

1 - do you need remote access?
2 - what version of Windows are you running?
3 - do you have access to the Domain Controller?
4 - where do you have your home directory
(directories)?

The answers to these questions will tell you whether
or not you need the '-d' option, etc.

--- Phil Betts <[EMAIL PROTECTED]> wrote:
> On Wednesday, February 23, 2005 6:23 PM, Banibrata
> Dutta wrote:
> > Could anybody explain the following behaviour or
> Cygwin and "startx"
> > in Cygwin...
> > 
> > 
> > 
> > Your group is currently "mkpasswd". This indicates
> that
> > the /etc/passwd (and possibly /etc/group) files
> should be rebuilt.
> > See the man pages for mkpasswd and mkgroup then,
> for example, run
> > mkpasswd -l [-d] > /etc/passwd
> > mkgroup  -l [-d] > /etc/group
> > Note that the -d switch is necessary for domain
> users.
> 
>  
> 
> > Could someone please help ?
> 
> Did you actually *read* what you posted?
> 
> It tells you all you need to know.

[snip]





__ 
Celebrate Yahoo!'s 10th Birthday! 
Yahoo! Netrospective: 100 Moments of the Web 
http://birthday.yahoo.com/netrospective/


RE: bad installation ?

2005-03-10 Thread Morrison, John
As maintainer of the package which outputs that message I'm
always glad to hear of ways to improve it.  Can you suggest
a better message?

J.

> -Original Message-
> From: Matthew Johnson 
> 
> Well, Phil, I read what she posted, and I do NOT think
> it tells "all Banibrata needs to know".
> 
> The big unanswered question that is probably still
> bothering Banibrata is, "how on earth did the group
> get to be 'mkpasswd' in the first place?" I very much
> doubt that Banibrata set it to that. And I have never
> seen that in Cygwin or Cygwin/X before. So it sounds
> like some drastic error condition did this. And if it
> did, who knows what _else_ is messed up in the
> installation? THAT is what Banitrata needs to know; it
> was NOT contained in the message.
> 
> Another thing Banibrata needs to know that was not
> explained is which of the FOUR methods of rebuilding
> the password file is appropriate for this condition.
> 
> Now it may very well be that the readers of the list
> cannot answer this for Banibrata, since it varies from
> case to case, and Banibrata simply has to knuckle-down
> and read the man pages. But even if this is the case,
> some guidelines for how to intepret the man pages
> would be the right, helpful response.
> 
> To that end, I propose to Banibrata the following
> questions:
> 
> 1 - do you need remote access?
> 2 - what version of Windows are you running?
> 3 - do you have access to the Domain Controller?
> 4 - where do you have your home directory
> (directories)?
> 
> The answers to these questions will tell you whether
> or not you need the '-d' option, etc.
> 
> --- Phil Betts <[EMAIL PROTECTED]> wrote:
> > On Wednesday, February 23, 2005 6:23 PM, Banibrata
> > Dutta wrote:
> > > Could anybody explain the following behaviour or
> > Cygwin and "startx"
> > > in Cygwin...
> > > 
> > > 
> > > 
> > > Your group is currently "mkpasswd". This indicates
> > that
> > > the /etc/passwd (and possibly /etc/group) files
> > should be rebuilt.
> > > See the man pages for mkpasswd and mkgroup then,
> > for example, run
> > > mkpasswd -l [-d] > /etc/passwd
> > > mkgroup  -l [-d] > /etc/group
> > > Note that the -d switch is necessary for domain
> > users.
> > 
> >  
> > 
> > > Could someone please help ?
> > 
> > Did you actually *read* what you posted?
> > 
> > It tells you all you need to know.


This e-mail has come from Experian International: winner of the UK's National 
Business of the Year Award 2003.

==
Information in this e-mail and any attachments are confidential, and may 
not be copied or used by anyone other than the addressee, nor disclosed 
to any third party without our permission. There is no intention to 
create any legally binding contract or other binding commitment through 
the use of this electronic communication unless it is issued in accordance 
with the Experian Limited standard terms and conditions of purchase or 
other express written agreement between Experian Limited and the recipient 
Experian Limited (registration number 653331) Registered office: 
Talbot House, Talbot Street, Nottingham NG80 1TH

Although Experian has taken reasonable steps to ensure that this communication 
and any attachments are free from computer virus, you are advised to take 
your own steps to ensure that they are actually virus free.



RE: bad installation ?

2005-03-10 Thread Matthew Johnson
Hi, John-

Since I myself have no idea why it is outputting that
message, no I cannot suggest a better message. And I
notice that when I did a fresh installation of cygwin
and cygwin/x on a brand new system yesterday, now I am
getting that message too. Do _you_ have any idea why
fresh installations did not used to output this
message, but now they do? Is it a new message, or did
something change in cygwin or cygwin/x, such that the
group now gets initialized to 'mkpasswd' (and did not
get so initialized before)?

--- "Morrison, John" <[EMAIL PROTECTED]>
wrote:

> As maintainer of the package which outputs that
> message I'm
> always glad to hear of ways to improve it.  Can you
> suggest
> a better message?
> 
> J.
> 
> > -Original Message-
> > From: Matthew Johnson 
> > 
> > Well, Phil, I read what she posted,
> > and I do NOT think
> > it tells "all Banibrata needs to know".
> > 
> > The big unanswered question that is probably still
> > bothering Banibrata is, "how on earth did the
> >group get to be 'mkpasswd' in the first place?"
> > I very much doubt that Banibrata set it to that.

And now I can add, I _know_ I did not set it to that,
yet now I get the message too, when starting up the
bash shell.

[snip]




__ 
Do you Yahoo!? 
Yahoo! Small Business - Try our new resources site!
http://smallbusiness.yahoo.com/resources/ 


RE: bad installation ?

2005-03-10 Thread John Morrison (Cygwin)
Hi Matthew,

Although the message is from base-files the reason is
due to installation.  In my experience this only
occurs when installing for a domain user although
others have reported other reasons for it.

For me, the message occurs because the base-passwd
(which I also maintain) doesn't and (for a number of
reasons, see archives) can't add domain users.

The outcome is, for this user, is that you get added
to a special group.  In an effort to stop or at least
slow ;) the number of emails to the list when stuff
didn't work because their user/group wasn't setup
correctly some detection code was added to base-files
along with some instruction as to what to do.


Basically adding your user (using the domain flag if
appropriate) to the passwd and group files which is
what the message attempts to help the user to do.  It
appears (judging from the number of times this
question isn't now appearing on the lists) to have
worked for most people, but I'm always looking for
perfection ;)

Hope this helps explain things,

J.

On Thu, March 10, 2005 7:22 pm, Matthew Johnson said:
> Hi, John-
>
> Since I myself have no idea why it is outputting that
> message, no I cannot suggest a better message. And I
> notice that when I did a fresh installation of cygwin
> and cygwin/x on a brand new system yesterday, now I am
> getting that message too. Do _you_ have any idea why
> fresh installations did not used to output this
> message, but now they do? Is it a new message, or did
> something change in cygwin or cygwin/x, such that the
> group now gets initialized to 'mkpasswd' (and did not
> get so initialized before)?
>
> --- "Morrison, John" <[EMAIL PROTECTED]>
> wrote:
>
>> As maintainer of the package which outputs that
>> message I'm
>> always glad to hear of ways to improve it.  Can you
>> suggest
>> a better message?
>>
>> J.
>>
>> > -Original Message-
>> > From: Matthew Johnson
>> >
>> > Well, Phil, I read what she posted,
>> > and I do NOT think
>> > it tells "all Banibrata needs to know".
>> >
>> > The big unanswered question that is probably still
>> > bothering Banibrata is, "how on earth did the
>> >group get to be 'mkpasswd' in the first place?"
>> > I very much doubt that Banibrata set it to that.
>
> And now I can add, I _know_ I did not set it to that,
> yet now I get the message too, when starting up the
> bash shell.
>
> [snip]
>
>
>
>
> __
> Do you Yahoo!?
> Yahoo! Small Business - Try our new resources site!
> http://smallbusiness.yahoo.com/resources/
>
>




RE: bad installation ?

2005-03-10 Thread Matthew Johnson

--- "John Morrison (Cygwin)" <[EMAIL PROTECTED]>
wrote:

> Hi Matthew,
> 
> Although the message is from base-files the reason
> is due to installation.

OK...

> In my experience this only
> occurs when installing for a domain user although
> others have reported other reasons for it.

'Domain'? What kind of 'domain' are you talking about
here? And why should a user have to rebuild the entire
passwd and group files just because they are a domain
user? This sounds wrong: if it is right, more
explanation is necessary.

> For me, the message occurs because the base-passwd
> (which I also maintain) doesn't and (for a number of
> reasons, see archives) can't add domain users.

What 'base-passwd'? And can you be a little more
specific than "see archives"? I did a search with
"cygwin base-passwd domain user" and I still have a
sinking feeling when I see what links come up.

> The outcome is, for this user, is that you get added
> to a special group.  In an effort to stop or at
> least
> slow ;) the number of emails to the list when stuff
> didn't work because their user/group wasn't setup
> correctly some detection code was added to
> base-files
> along with some instruction as to what to do.
 
Right. And when I follow those instructions, it
_still_ does not work: it does not allow me to remake
the group, so I still get the message. So I am quite
surprised that you say this message has reduced the
number of emails to the list.

Besides: the user should not have to know enough about
domains and passwords to know why you have assumed
that domain user stay domain users. And why are you so
worried about the "problems there" when domain users
are added (or did you mean not added) to passwd/group
files?
 
> Basically adding your user (using the domain flag if
> appropriate) to the passwd and group files which is
> what the message attempts to help the user to do. 

This sentence is missing a main verb. Besides: I tried
this both with and without the -d flag and make group
failed both ways.

> It
> appears (judging from the number of times this
> question isn't now appearing on the lists) to have
> worked for most people, but I'm always looking for
> perfection ;)

As I said, it surprises me that this would reduce the
number, since it failed so quickly for me. But I
always knew I was different;)


> Hope this helps explain things,

Partially, yes. But I am still mystified why both
"mkgroup -l > /etc/passwd" and "mkgroup -l -d >
/etc/passwd" fail. The error code from the latter is
"Cannot get PDC, code = 2453".

[snip]

BTW: maybe _you_ never log on locally when running on
a network domain, but I often do. So I find the
restriction irritating. And I see from perusing the
list that I am not the first to find it so. More
important, in some benighted companies, users do not
have Administrator privileges on their own Win95
workstations. They can only log on with their domain
user name. Won't they want to be able to log on
locally even more often (under Cygwin)?



---
Matthew Johnson
[EMAIL PROTECTED]



__ 
Do you Yahoo!? 
Yahoo! Small Business - Try our new resources site!
http://smallbusiness.yahoo.com/resources/ 


RE: bad installation ?

2005-03-11 Thread Owen Rees
--On 10 March 2005 20:14 + John Morrison (Cygwin) wrote:
Basically adding your user (using the domain flag if
appropriate) to the passwd and group files which is
what the message attempts to help the user to do.  It
appears (judging from the number of times this
question isn't now appearing on the lists) to have
worked for most people, but I'm always looking for
perfection ;)
Hope this helps explain things,
My system is not in the same domain as my login id, and I suspect that may 
make a difference. One of the problems with saying "if appropriate" is that 
it assumes that the reader knows when it is appropriate, but if they did, 
they would probably not need to ask the question.

Searching the mail archives turned up this in 
:

There is an off chance that 'mkpasswd -u yourself -d thedomain'
might work, where thedomain is the global corporate domain.
Sustituting "domain part from the domain\user I can use to log in" for 
"global corporate domain" (they are not the same thing in my case) I got a 
result that included the (number of) the group "Domain Users", the group in 
which Windows utilities seems to create files for me. Unfortunately the 
result offered a different home directory from the one I have been using 
with my current setup, but a careful edit to /etc/passwd seems to have 
changed things for the better.

As for neither fixing the problem before, not posting about it, I was 
getting stupid results from 'ls -l' for the group, but apart from that 
nothing seemed to be broken. It did not seem worth a lot of effort trying 
to tidy up a loose end that did not seem to be making any real difference.

I did try the things that the message about mkgroup_l_d seemed to be 
suggesting, but they did not make any difference. In reading the man page 
for mkpasswd I did not realise that "current domain" apparently does not 
mean the domain in which my login id is defined.

--
Owen Rees <[EMAIL PROTECTED]>
Hewlett Packard Laboratories, Bristol, UK
tel: +44 117 312 9439 fax: +44 117 312 8924



Re: bad installation ?

2005-03-11 Thread Christopher Faylor
On Fri, Mar 11, 2005 at 01:28:05PM +, Owen Rees wrote:
>--On 10 March 2005 20:14 + John Morrison (Cygwin) wrote:
>>Basically adding your user (using the domain flag if appropriate) to
>>the passwd and group files which is what the message attempts to help
>>the user to do.  It appears (judging from the number of times this
>>question isn't now appearing on the lists) to have worked for most
>>people, but I'm always looking for perfection ;)
>>
>>Hope this helps explain things,
>
>My system is not in the same domain as my login id, and I suspect that
>may make a difference.  One of the problems with saying "if
>appropriate" is that it assumes that the reader knows when it is
>appropriate, but if they did, they would probably not need to ask the
>question.
>
>Searching the mail archives turned up this in
>:

As the above link suggests, this discussion is off topic for
cygwin-xfree.  Please move it to the main list.  You'll have a lot more
people to pick on than John Morrison in the main list.

I'm blocking this subject from further discussion here.

cgf