missing setup command line arguments in the FAQ.

classic Classic list List threaded Threaded
17 messages Options
Reply | Threaded
Open this post in threaded view
|

missing setup command line arguments in the FAQ.

Buchbinder, Barry (NIH/NIAID) [E]
The command line arguments listed in the FAQ
http://cygwin.com/faq/faq-nochunks.html#faq.setup.cli
are incomplete.  The following are missing.

 -O --only-site                         Ignore all sites except for -s
 -P --packages                          Specify packages to install
 -C --categories                        Specify entire categories to install
 -p --proxy                             HTTP/FTP proxy (host:port)
 -X --no-verify                         Don't verify setup.ini signatures
 -K --pubkey                            Path to extra public key file (gpg
                                        format)
 -S --sexpr-pubkey                      Extra public key in s-expr format
 -u --untrusted-keys                    Use untrusted keys from last-extrakeys
 -U --keep-untrusted-keys               Use untrusted keys and retain all

I apologize for the lack of a patch.

- Barry
  Disclaimer: Statements made herein are not made on behalf of NIAID.

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Reply | Threaded
Open this post in threaded view
|

Re: missing setup command line arguments in the FAQ.

Christopher Faylor-8
On Fri, Jan 15, 2010 at 12:32:12PM -0500, Buchbinder, Barry (NIH/NIAID) [E] wrote:

>The command line arguments listed in the FAQ
>http://cygwin.com/faq/faq-nochunks.html#faq.setup.cli
>are incomplete.  The following are missing.
>
> -O --only-site                         Ignore all sites except for -s
> -P --packages                          Specify packages to install
> -C --categories                        Specify entire categories to install
> -p --proxy                             HTTP/FTP proxy (host:port)
> -X --no-verify                         Don't verify setup.ini signatures
> -K --pubkey                            Path to extra public key file (gpg
>                                        format)
> -S --sexpr-pubkey                      Extra public key in s-expr format
> -u --untrusted-keys                    Use untrusted keys from last-extrakeys
> -U --keep-untrusted-keys               Use untrusted keys and retain all
>
>I apologize for the lack of a patch.

I've added these to the FAQ.  I haven't published the changes yet though.

Thanks.

cgf

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Reply | Threaded
Open this post in threaded view
|

Re: missing setup command line arguments in the FAQ.

Corinna Vinschen-2
On Jan 15 13:47, Christopher Faylor wrote:

> On Fri, Jan 15, 2010 at 12:32:12PM -0500, Buchbinder, Barry (NIH/NIAID) [E] wrote:
> >The command line arguments listed in the FAQ
> >http://cygwin.com/faq/faq-nochunks.html#faq.setup.cli
> >are incomplete.  The following are missing.
> >
> > -O --only-site                         Ignore all sites except for -s
> > -P --packages                          Specify packages to install
> > -C --categories                        Specify entire categories to install
> > -p --proxy                             HTTP/FTP proxy (host:port)
> > -X --no-verify                         Don't verify setup.ini signatures
> > -K --pubkey                            Path to extra public key file (gpg
> >                                        format)
> > -S --sexpr-pubkey                      Extra public key in s-expr format
> > -u --untrusted-keys                    Use untrusted keys from last-extrakeys
> > -U --keep-untrusted-keys               Use untrusted keys and retain all
> >
> >I apologize for the lack of a patch.
>
> I've added these to the FAQ.  I haven't published the changes yet though.

I've just published the latest FAQ changes.


Corinna

--
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Reply | Threaded
Open this post in threaded view
|

Re: missing setup command line arguments in the FAQ.

G.W. Haywood
In reply to this post by Buchbinder, Barry (NIH/NIAID) [E]
Hi there,

http://cygwin.com/cygwin-ug-net/setup-net.html#internet-setup

says

"Unfortunately setup.exe does not yet support unattended installs."

but

http://cygwin.com/faq/faq-nochunks.html#faq.setup.cli

seems to imply that it does, via the '-q' switch.

Which is correct?

--

73,
Ged.

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Reply | Threaded
Open this post in threaded view
|

Re: missing setup command line arguments in the FAQ.

Christopher Faylor-8
On Sat, Jan 16, 2010 at 09:17:24AM +0000, G.W. Haywood wrote:

>Hi there,
>
>http://cygwin.com/cygwin-ug-net/setup-net.html#internet-setup
>
>says
>
>"Unfortunately setup.exe does not yet support unattended installs."
>
>but
>
>http://cygwin.com/faq/faq-nochunks.html#faq.setup.cli
>
>seems to imply that it does, via the '-q' switch.
>
>Which is correct?

If only there was some way to tell...

cgf

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Reply | Threaded
Open this post in threaded view
|

Re: missing setup command line arguments in the FAQ.

G.W. Haywood
In reply to this post by Buchbinder, Barry (NIH/NIAID) [E]
Hi there,

On Sun, 17 Jan 2010 Christopher Faylor wrote:

> On Sat, Jan 16, 2010 at 09:17:24AM +0000, G.W. Haywood wrote:
>
> > Which is correct?
>
> If only there was some way to tell...

I think you should seek professional help.

--

73,
Ged.

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Reply | Threaded
Open this post in threaded view
|

Re: missing setup command line arguments in the FAQ.

Dave Korn-6
G.W. Haywood wrote:

> Hi there,
>
> On Sun, 17 Jan 2010 Christopher Faylor wrote:
>
>> On Sat, Jan 16, 2010 at 09:17:24AM +0000, G.W. Haywood wrote:
>>
>>> Which is correct?
>> If only there was some way to tell...
>
> I think you should seek professional help.

  Nurse!  The screens!

> --
>
> 73,
> Ged.

  Now I'm confused.  Is that your high-score, your shoe size, or your age?

    cheers,
      DaveK


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Reply | Threaded
Open this post in threaded view
|

Re: missing setup command line arguments in the FAQ.

Dave Korn-6
Dave Korn wrote:

> G.W. Haywood wrote:
>> Hi there,
>>
>> On Sun, 17 Jan 2010 Christopher Faylor wrote:
>>
>>> On Sat, Jan 16, 2010 at 09:17:24AM +0000, G.W. Haywood wrote:
>>>
>>>> Which is correct?
>>> If only there was some way to tell...
>> I think you should seek professional help.
>
>   Nurse!  The screens!

  BTW, if you run "setup.exe --help", it will (depending on OS version) either
display the usage instructions to the screen, or dump them to a setup.log file
in the directory where you run it.  (As indeed it points out at the start of
that FAQ entry you linked to.  Which was why cgf was hinting that you already
had everything you needed to tell...)

    cheers,
      DaveK


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Reply | Threaded
Open this post in threaded view
|

Re: missing setup command line arguments in the FAQ.

Christopher Faylor-8
In reply to this post by G.W. Haywood
On Sun, Jan 17, 2010 at 08:15:36AM +0000, G.W. Haywood wrote:
>On Sun, 17 Jan 2010 Christopher Faylor wrote:
>>On Sat, Jan 16, 2010 at 09:17:24AM +0000, G.W.  Haywood wrote:
>>>Which is correct?
>>
>>If only there was some way to tell...
>
>I think you should seek professional help.

Wow!  Zing!

cgf

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Reply | Threaded
Open this post in threaded view
|

Re: missing setup command line arguments in the FAQ.

Christopher Faylor-8
In reply to this post by Dave Korn-6
On Sun, Jan 17, 2010 at 10:32:43AM +0000, Dave Korn wrote:

>Dave Korn wrote:
>>G.W.  Haywood wrote:
>>>On Sun, 17 Jan 2010 Christopher Faylor wrote:
>>>>On Sat, Jan 16, 2010 at 09:17:24AM +0000, G.W.  Haywood wrote:
>>>>>Which is correct?
>>>>If only there was some way to tell...
>>>I think you should seek professional help.
>>
>>Nurse! The screens!
>
>BTW, if you run "setup.exe --help", it will (depending on OS version)
>either display the usage instructions to the screen, or dump them to a
>setup.log file in the directory where you run it.  (As indeed it points
>out at the start of that FAQ entry you linked to.  Which was why cgf
>was hinting that you already had everything you needed to tell...)

Actually, I was suggesting that one could just *try it*.  Obviously the
documentation must be untrustworthy since it was contradictory.  There
was one section which provided a command-line option for unattended
installation and another which implied that there was no option.

The supposition was, apparently, that spurious descriptions of
nonexistent options must have crept into the documentation so the only
real way to figure out what works is to actually run the program.

cgf

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Reply | Threaded
Open this post in threaded view
|

Re: missing setup command line arguments in the FAQ.

G.W. Haywood
In reply to this post by Buchbinder, Barry (NIH/NIAID) [E]
Hello again,

On Mon, 18 Jan 2010 several of us wrote:

> > 73,
> > Ged.
>
> Now I'm confused.  Is that your high-score, your shoe size, or your age?

It's a relic from the days of morse code; just over my weight, and
half my IQ; and uncomfortably close to my age.

> BTW, if you run "setup.exe --help", it will (depending on OS
> version) either display the usage instructions to the screen, or
> dump them to a setup.log file in the directory where you run it.

That's not correct (*):

laptop:~$ >>> ./setup.exe
-bash: ./setup.exe: cannot execute binary file

> ... cgf was hinting that you already had everything you needed ...

One of his premises was false.

> Actually, I was suggesting that one could just *try it*.
> ...
> The supposition was, apparently, that spurious descriptions of
> nonexistent options must have crept into the documentation so the
> only real way to figure out what works is to actually run the program.

Interesting - the thought that spurious descriptions of nonexistent
options could creep into the documentation.  Is that something that
happens a lot?  It never crossed my mind.  Although it _did_ cross my
mind that the unattended install option didn't work right (e.g. hosed
installation at a customer's site just before they do the payroll run,
invoices going missing, you know, the kinds of things we worry about).
It also crossed my mind that the not-working-right part somehow might
not have made it to the docs in place of the it-can't-be-done part...

Mr. Faylor, please accept my apologies.  I really shouldn't prey on
the fallibilities of other people.  Heaven knows I have enough of my
own.  I knew when writing my question that I was probably going to be
treated to one of your, er, no-brainers, and my response to that was
calculated to make you look foolish:

Yes, one could just *try it*, if he had a Windows machine on which to
try it.  But I don't own any Windows boxes, which is why I was reduced
to asking a question on this list.  Now wouldn't it have been easier,
and wouldn't it have wasted a lot less bandwidth, if you'd politely
answered the question instead of trying to hump me?

I've been reading the cygwin list for quite a while.  I can say for
most other lists that it's a pleasant experience, for one or two that
it's neither pleasant nor unpleasant, but for only one that it's almost
always an unpleasant experience.  That one is the cygwin users list.

When it's an unpleasant experience I'll usually just unsubscribe, but
in the case of the cygwin list the urge to become more familiar with
the subject outweighs the unpleasantness, and until now I've simply
put up with it.

One individual is directly responsible for the unpleasantness.

I wasn't joking about the professional help.  There's clearly some
deep seated need there to dominate people.  Unfortunately it won't
work with everyone.

(*) Sorry again, Dave, but it's not you I'm getting at. :)

--

73,
Ged.

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Reply | Threaded
Open this post in threaded view
|

Re: missing setup command line arguments in the FAQ.

Dave Korn-6
G.W. Haywood wrote:

>> BTW, if you run "setup.exe --help", it will (depending on OS
>> version) either display the usage instructions to the screen, or
>> dump them to a setup.log file in the directory where you run it.
>
> That's not correct (*):
>
> laptop:~$ >>> ./setup.exe
> -bash: ./setup.exe: cannot execute binary file

  Well strictly it is, since I said what would happen if you ran it, and not
what would happen if you _didn't_ run it (for whatever reason that might
happen to be)!

> Yes, one could just *try it*, if he had a Windows machine on which to
> try it.

*koff* Prepare to be shocked, amazed, awed and astounded!

> [davek@ubique ~]$ uname -a
> Linux ubique.localdomain 2.6.27.21-170.2.56.fc10.i686 #1 SMP Mon Mar 23 23:37:54 EDT 2009 i686 athlon i386 GNU/Linux
> [davek@ubique ~]$ wget http://cygwin.com/setup.exe
> --2010-01-18 13:20:58--  http://cygwin.com/setup.exe
> Resolving cygwin.com... 209.132.180.131
> Connecting to cygwin.com|209.132.180.131|:80... connected.
> HTTP request sent, awaiting response... 200 OK
> Length: 624128 (610K) [application/octet-stream]
> Saving to: `setup.exe'
>
> 100%[====================================================================================>] 624,128     28.6K/s   in 16s    
>
> 2010-01-18 13:21:15 (37.3 KB/s) - `setup.exe' saved [624128/624128]
>
> [davek@ubique ~]$ chmod a+x setup.exe
> [davek@ubique ~]$ wine ./setup.exe --help
> fixme:msvcrt:MSVCRT_setlocale :Codepage only locale not implemented
> Starting cygwin install, version 2.677
> io_stream_cygfile: fopen(/etc/setup/setup.rc) failed 2 No such file or directory
> io_stream_cygfile: fopen(/etc/setup/last-cache) failed 2 No such file or directory
> io_stream_cygfile: fopen(/etc/setup/last-action) failed 2 No such file or directory
> io_stream_cygfile: fopen(/etc/setup/net-method) failed 2 No such file or directory
> io_stream_cygfile: fopen(/etc/setup/net-proxy-host) failed 2 No such file or directory
> io_stream_cygfile: fopen(/etc/setup/net-proxy-port) failed 2 No such file or directory
> io_stream_cygfile: fopen(/etc/setup/last-mirror) failed 2 No such file or directory
> io_stream_cygfile: fopen(/etc/setup/extrakeys) failed 2 No such file or directory
> io_stream_cygfile: fopen(/etc/setup/chooser_window_settings) failed 2 No such file or directory
> Current Directory: Z:\home\davek
>
> Command Line Options:
>  -D --download                          Download from internet
>  -L --local-install                     Install from local directory
>  -s --site                              Download site
>  -O --only-site                         Ignore all sites except for -s
>  -R --root                              Root installation directory
>  -P --packages                          Specify packages to install
>  -C --categories                        Specify entire categories to install
>  -p --proxy                             HTTP/FTP proxy (host:port)
>  -q --quiet-mode                        Unattended setup mode
>  -h --help                              print help
>  -l --local-package-dir                 Local package directory
>  -r --no-replaceonreboot                Disable replacing in-use files on next
>                                         reboot.
>  -X --no-verify                         Don't verify setup.ini signatures
>  -n --no-shortcuts                      Disable creation of desktop and start
>                                         menu shortcuts
>  -N --no-startmenu                      Disable creation of start menu shortcut
>  -d --no-desktop                        Disable creation of desktop shortcut
>  -K --pubkey                            Path to extra public key file (gpg
>                                         format)
>  -S --sexpr-pubkey                      Extra public key in s-expr format
>  -u --untrusted-keys                    Use untrusted keys from last-extrakeys
>  -U --keep-untrusted-keys               Use untrusted keys and retain all
>  -A --disable-buggy-antivirus           Disable known or suspected buggy anti
>                                         virus software packages during
>                                         execution.
> Ending cygwin install
> AddAccessAllowedAce(, owner) failed: 1337
> AddAccessAllowedAce(, group) failed: 1337
> AddAccessAllowedAce(, everyone) failed: 1337
> AddAccessAllowedAce(, owner) failed: 1337
> AddAccessAllowedAce(, group) failed: 1337
> AddAccessAllowedAce(, everyone) failed: 1337
> [davek@ubique ~]$

  :-)

    cheers,
      DaveK


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Reply | Threaded
Open this post in threaded view
|

Re: missing setup command line arguments in the FAQ.

Christopher Faylor-8
In reply to this post by G.W. Haywood
On Mon, Jan 18, 2010 at 12:18:13PM +0000, G.W. Haywood wrote:
>I wasn't joking about the professional help.  There's clearly some
>deep seated need there to dominate people.  Unfortunately it won't
>work with everyone.

Please question my sanity in the cygwin-talk mailing list.  While it
may be entertaining, it isn't really on-topic here.

cgf

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Reply | Threaded
Open this post in threaded view
|

Re: missing setup command line arguments in the FAQ.

Christopher Faylor-8
In reply to this post by Dave Korn-6
On Mon, Jan 18, 2010 at 01:23:27PM +0000, Dave Korn wrote:
>G.W. Haywood wrote:
>> Yes, one could just *try it*, if he had a Windows machine on which to
>> try it.
>
>*koff* Prepare to be shocked, amazed, awed and astounded!

This thread was started because Barry Buchbinder noticed a discrepancy
between the online documentation and what was available from setup.exe.
I guess I should have been clearer in my response.

I updated the documentation on the web page directly from setup.exe
--help output.  So, knowing that, it should be no surprise that the web
page and the help output coincide.

I also removed the line about unattended installation.

cgf

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Reply | Threaded
Open this post in threaded view
|

Re: missing setup command line arguments in the FAQ.

G.W. Haywood
In reply to this post by Buchbinder, Barry (NIH/NIAID) [E]
Hello again,

On Mon, 18 Jan 2010 we variously wrote:

> > That's not correct (*):
>
> Well strictly it is, since I said what would happen if you ran it, and not
> what would happen if you _didn't_ run it (for whatever reason that might
> happen to be)!

Damn.  Aced.  15-love.

> [davek@ubique ~]$ wine ./setup.exe --help
> ...

Out!  This falls into the category of documented but not working.  15 all.

> ... I guess I should have been clearer in my response.
> ... no surprise that the web page and the help output coincide.

Quite so.

> I also removed the line about unattended installation.

Thank you.

--

73,
Ged.

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Reply | Threaded
Open this post in threaded view
|

Re: missing setup command line arguments in the FAQ.

Brolin Empey-3
In reply to this post by Dave Korn-6
I found this message in my hosted Gmail (Google Apps) account’s Spam
folder.  I wonder why Gmail thought it was spam?  Because it contained
the URL of a(n) (Windows) executable file?

Dave Korn wrote:
> G.W. Haywood wrote:
>
>>> BTW, if you run "setup.exe --help", it will (depending on OS
>>> version) either display the usage instructions to the screen,

I assume you mean it will print the usage instructions to stdout or
stderr, which are not necessarily connected to a terminal?

> or
>>> dump them to a setup.log file in the directory where you run it.
>>
>> That's not correct (*):
>>
>> laptop:~$>>>  ./setup.exe
>> -bash: ./setup.exe: cannot execute binary file
>
>    Well strictly it is, since I said what would happen if you ran it, and not
> what would happen if you _didn't_ run it (for whatever reason that might
> happen to be)!

Because G.W. Haywood is not running it on Windows (nor ReactOS) nor with
Wine?

>
>> Yes, one could just *try it*, if he had a Windows machine on which to
>> try it.

Not all Cygwin users are male.  Please use “he or she” or, if you agree
with singular usage of traditionally plural pronouns, “they” instead of
“he”.

>
> *koff*

Don’t you mean *COFF* (as opposed to ELF)? ;)

> Prepare to be shocked, amazed, awed and astounded!
>
>> [davek@ubique ~]$ uname -a

bash?  Shouldn’t you use *ksh? ;)

>> Linux ubique.localdomain 2.6.27.21-170.2.56.fc10.i686 #1 SMP Mon Mar 23 23:37:54 EDT 2009 i686 athlon i386 GNU/Linux
>> [davek@ubique ~]$ wget http://cygwin.com/setup.exe
>> --2010-01-18 13:20:58--  http://cygwin.com/setup.exe
>> Resolving cygwin.com... 209.132.180.131
>> Connecting to cygwin.com|209.132.180.131|:80... connected.
>> HTTP request sent, awaiting response... 200 OK
>> Length: 624128 (610K) [application/octet-stream]

Is that a (bit)stream of eighth notes in the key of C? ;)

>> Saving to: `setup.exe'
>>
>> 100%[====================================================================================>] 624,128     28.6K/s   in 16s
>>
>> 2010-01-18 13:21:15 (37.3 KB/s) - `setup.exe' saved [624128/624128]
>>
>> [davek@ubique ~]$ chmod a+x setup.exe
>> [davek@ubique ~]$ wine ./setup.exe --help

Are you using Wine with the builtin xor native libraries?  Note:  the
xor operator is to prevent a “Yes” answer since this question requires a
string, not a boolean, as an answer. :)

>> fixme:msvcrt:MSVCRT_setlocale :Codepage only locale not implemented
>> Starting cygwin install, version 2.677
>> io_stream_cygfile: fopen(/etc/setup/setup.rc) failed 2 No such file or directory
>> io_stream_cygfile: fopen(/etc/setup/last-cache) failed 2 No such file or directory
>> io_stream_cygfile: fopen(/etc/setup/last-action) failed 2 No such file or directory
>> io_stream_cygfile: fopen(/etc/setup/net-method) failed 2 No such file or directory
>> io_stream_cygfile: fopen(/etc/setup/net-proxy-host) failed 2 No such file or directory
>> io_stream_cygfile: fopen(/etc/setup/net-proxy-port) failed 2 No such file or directory
>> io_stream_cygfile: fopen(/etc/setup/last-mirror) failed 2 No such file or directory
>> io_stream_cygfile: fopen(/etc/setup/extrakeys) failed 2 No such file or directory
>> io_stream_cygfile: fopen(/etc/setup/chooser_window_settings) failed 2 No such file or directory
>> Current Directory: Z:\home\davek
>>
>> Command Line Options:

<snip>

>> Ending cygwin install
>> AddAccessAllowedAce(, owner) failed: 1337
>> AddAccessAllowedAce(, group) failed: 1337
>> AddAccessAllowedAce(, everyone) failed: 1337
>> AddAccessAllowedAce(, owner) failed: 1337
>> AddAccessAllowedAce(, group) failed: 1337
>> AddAccessAllowedAce(, everyone) failed: 1337

Does this mean you are too 1337 to be allowed access? ;)

>> [davek@ubique ~]$
>
>    :-)
>
>      cheers,
>        DaveK

Did you know old Apple keyboards, such as the Apple Extended Keyboard II
from 1989, have the bumps on D and K instead of F and J? :)  I used to
have one of those keyboards in my 68k Mac collection.  I wish I had kept
the keyboard because it would be cool if I could use it on a PC with an
ADB→USB converter.  I liked that keyboard’s feel:  it had mechanical key
switches instead of rubber membrane/dome switches.  The Caps Lock key
stayed down when Caps Lock was on, like Shift Lock on a typewriter (and
a C64?).  I forgot if it had the Lock LEDs on the keys themselves or in
a group elsewhere on the keyboard.


--
Sometimes I forget how to do small talk: <http://xkcd.com/222/>

“If you have to ask why, you’re not a member of the intended audience.”
— Bob Zimbinski, <http://webpages.mr.net/bobz/ttyquake/>

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Reply | Threaded
Open this post in threaded view
|

Re: missing setup command line arguments in the FAQ.

Christopher Faylor-8
On Fri, Jan 22, 2010 at 03:07:10PM -0800, Brolin Empey wrote:
>[deleted]

Please.  There was little in this message that was on-topic for the
cygwin mailing list.  Please use the cygwin-talk mailing list if you
really want to pursue this further.

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple