Brian responded:
Sorry about all of the silly questions, though not so silly to me, since
I don't set up cygwin everyday and have only done it once, quite a while
ago. THerefore I have forgotten most of what I did to set it up in the
first place.
Probably because you had no mount table.
But
Vidiot wrote:
Probably because you had no mount table.
But that shouldn't be anywhere near the C:\WINDOWS directory. Permissions
like before?
The mount table is not stored in a file, it's a set of keys in the
registry.
(Which makes sense, because the whole point of a mount table is to
I GOT IT WORKING!
The clues that got me thinking were the login problems with cron-config
and the manual timer setup problems with TSReader. Both complained about
not being able to complete, because of login problems.
So, I set up the system in classic login mode and sure enough, I couldn't
Vidiot wrote:
I GOT IT WORKING!
The clues that got me thinking were the login problems with cron-config
and the manual timer setup problems with TSReader. Both complained about
not being able to complete, because of login problems.
So, I set up the system in classic login mode and sure
Larry responded:
Both 'cron' and 'ssh' have config scripts that handle installing and
starting the service for you, if you let them. They are documented in
their README files in '/usr/share/doc/Cygwin'. 'cygrunsrv --help' gives
you an overview of the command and it's available options.
That is
On 25 June 2007 19:02, Vidiot wrote:
Larry responded:
Both 'cron' and 'ssh' have config scripts that handle installing and
starting the service for you, if you let them. They are documented in
their README files in '/usr/share/doc/Cygwin'. 'cygrunsrv --help' gives
you an overview of the
I just thought of something else.
Why not have the setup program have a section where it asks if the user wants
to start services like cron and ssh, where there would be the selection box
and at the bottom of the GUI it would tell the user to reference the readme
files in the doc directory as
Vidiot wrote:
I just thought of something else.
Why not have the setup program have a section where it asks if the user wants
to start services like cron and ssh, where there would be the selection box
and at the bottom of the GUI it would tell the user to reference the readme
files in the doc
Larry:
You may be surprised to find out that these ideas are not new. What's been
missing in the past has been patches that do something like what you suggest
in a compelling way. If you're interested, you may be able to remedy that.
I'm happy to read that the idea isn't new.
As much as I'd
DaveK responded:
No, it's a really bad idea.
Interesting.
Your suggestion amounts to People might look in the wrong place for the
documentation, so put all the documentation in every single place they might
look.
Yes and no. As I pointed out, the on line web page says that the user
doc,
On Mon, 25 Jun 2007, Vidiot wrote:
Larry responded:
Both 'cron' and 'ssh' have config scripts that handle installing and
starting the service for you, if you let them. They are documented in
their README files in '/usr/share/doc/Cygwin'. 'cygrunsrv --help' gives
you an overview of the
Igor posted:
What do you mean, nothing? What about this:
http://cygwin.com/faq/faq.resources.html#faq.resources.documentation?
As I indicated in a previous posting, I text searched the large FAQ for
cron and came up with nothing.
Your reference has the following:
There is a comprehensive
Vidiot wrote:
Larry:
You may be surprised to find out that these ideas are not new. What's been
missing in the past has been patches that do something like what you suggest
in a compelling way. If you're interested, you may be able to remedy that.
I'm happy to read that the idea isn't new.
Larry responded:
The 'setup.exe' code is in a challenged state which can make adding
features challenging. Perhaps you'd like to provide a Sun installer
and then port it to Cygwin. ;-)
Now we are just being funny. :-) I said that I could use the Sun package
facility for doing installs and
Vidiot wrote:
I had to replace the mobo because, well, simple, the other one died :-(
I had to reload WinXP-SP2 because the mobo drivers that were there didn't
simply cause an error and abort, they caused (or at least the one that did this)
the boot process to fail and caused a reboot. So,
Larry Hall responded:
'setup.exe' will only remove files when uninstalling or upgrading. It won't
remove configuration files that have been modified. Also, if the user
files in question were not installed by Cygwin, they will not be touched.
Thanks.
Also, where was/is the crontab file
On 6/24/07, Vidiot wrote:
Larry Hall responded:
'setup.exe' will only remove files when uninstalling or upgrading. It won't
remove configuration files that have been modified. Also, if the user
files in question were not installed by Cygwin, they will not be touched.
Thanks.
Also, where
OK, now I am completely confused.
After bringing up the system, I tried running the cygwin batch file and it
complained about not being able to find the zsh program (I run Z-shell).
So, I figured that I needed to reinstall cygwin. Hence the question I
previously posted.
Well, I ran the
Jason reponded:
Is this Windows XP Professional or Home? You may be using Simple File
Sharing (http://support.microsoft.com/kb/304040) which dumbs down the
security permission rules quite a bit.
Pro
Turn it off if you can and you will have a 'Security' tab on the
properties when you
Vidiot wrote:
After bringing up the system, I tried running the cygwin batch file and it
complained about not being able to find the zsh program (I run Z-shell).
Probably because you had no mount table.
So, I figured that I needed to reinstall cygwin. Hence the question I
previously
Vidiot wrote:
Jason reponded:
The reason you need to update your permissions is because Windows ties
permissions to a unique SSID for each user. When you reinstall, even
if you set up the same user names, the SSIDs associated with them are
different.
Ah, a hidden thing I never have had to
I had to replace the mobo because, well, simple, the other one died :-(
I had to reload WinXP-SP2 because the mobo drivers that were there didn't
simply cause an error and abort, they caused (or at least the one that did this)
the boot process to fail and caused a reboot. So, XP-SP2 was
22 matches
Mail list logo
