From: BGINFO4X <bginfo4x@kztsoftware.com>
To: cygwin@cygwin.com
Subject: Re: MSYS mode (continue)
Date: Tue, 09 Jul 2013 10:57:00 -0000 [thread overview]
Message-ID: <CAO2ddnapuJd1du2H5MNyLx6KAh6HviSaoz3173BfYhx+XUJUMA@mail.gmail.com> (raw)
In-Reply-To: <20130704163612.GA4729@ednor.casa.cgf.cx>
Hello,
Regarding to the fstab format, I don't know if it is supported, but it
would be nice to support Environment Variables.
For example, Instead of:
C:/Users /desktop
Use:
%USERPROFILE% /desktop
It is only a suggestion/example.
Regards.
##############
>>> >> >> >> {
>>> >> >> >> - char sysname[20];
>>> >> >> >> + char sysname[21];
>>> >> >> >
>>> >> >> > We can't do that. struct utsname is a publically facing structure.
>>> >> >> > If you change the size, you're breaking compatibility with existing
>>> >> >> > applications.
>>> >> >> >
>>> >> >> > You should better drop some character from the string you want to enter
>>> >> >> > here.
>>> >> >> >
>>> >> >>
>>> >> >> I can't drop any symbol from "MINGW32" word :)
>>> >> >
>>> >> > That's not 20 chars long.
>>> >> >
>>> >> Yes. But not only this need to be in 20 symbols. On cygwin 20 symbols is:
>>> >>
>>> >> CYGWIN_NT-6.1-WOW64\0
>>> >>
>>> >> But
>>> >>
>>> >> MINGW32_NT-6.1-WOW64\0
>>> >>
>>> >> is 21 symbol.
>>> >
>>> > Then drop the dash between "NT" and "6.1". Or let's drop the WOW64
>>> > since it's redundant anyway, given the content of "machine".
>>> >
>>>
>>> Let's drop it!
>>
>>I'm ok with that, but I think we should drop the "32" from MINGW in
>>the first place.
>>
>>Does anybody rely on the "WOW64" in uname -s output? I just checked
>>the scripts in /bin in my installation and none of it seems to check
>>for that info.
>>
>>And then again, it *is* redundant, given the uname -m output...
>
> Can we back up a moment and discuss whether, regardless of string
> length, this is the right approach? This isn't what I'd envisioned
> when I said "hooks".
>
> Also can we please discuss this in the cygwin-developers and
> cygwin-patches mailing lists? That's what they are for.
>
> --
> 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
>
--
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
next prev parent reply other threads:[~2013-07-09 10:39 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-03 16:03 Alexey Pavlov
2013-07-03 18:15 ` Christopher Faylor
2013-07-03 18:25 ` Alexey Pavlov
2013-07-03 19:50 ` Corinna Vinschen
2013-07-03 21:03 ` Charles Wilson
2013-07-03 21:57 ` Christopher Faylor
2013-07-03 22:39 ` Charles Wilson
2013-07-04 2:33 ` Alexey Pavlov
2013-07-04 8:58 ` Corinna Vinschen
2013-07-04 9:07 ` Alexey Pavlov
2013-07-04 9:09 ` Alexey Pavlov
2013-07-04 9:17 ` Corinna Vinschen
2013-07-04 9:37 ` Alexey Pavlov
2013-07-04 10:11 ` Corinna Vinschen
2013-07-04 10:23 ` Alexey Pavlov
2013-07-04 10:34 ` Kai Tietz
2013-07-04 10:47 ` Corinna Vinschen
2013-07-04 10:54 ` Alexey Pavlov
2013-07-04 14:43 ` Charles Wilson
2013-07-04 10:37 ` Corinna Vinschen
2013-07-04 10:45 ` Alexey Pavlov
2013-07-04 12:16 ` Corinna Vinschen
2013-07-04 14:47 ` Charles Wilson
2013-07-04 16:36 ` Christopher Faylor
2013-07-09 10:57 ` BGINFO4X [this message]
2013-07-09 18:15 ` Buchbinder, Barry (NIH/NIAID) [E]
2013-07-04 9:13 ` Corinna Vinschen
2013-07-04 8:39 ` Corinna Vinschen
2013-07-04 14:49 ` Charles Wilson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAO2ddnapuJd1du2H5MNyLx6KAh6HviSaoz3173BfYhx+XUJUMA@mail.gmail.com \
--to=bginfo4x@kztsoftware.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).