From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: Home directory was not created
Date: Tue, 2 Mar 2021 11:56:53 -0700 [thread overview]
Message-ID: <4125b749-86de-ae02-43d9-16ff5a8565cd@SystematicSw.ab.ca> (raw)
In-Reply-To: <24934718098a4d26a65b68ef62f3b46e@BELBRU-EXMP101.eeas.europa.eu>
On 2021-03-02 01:08, KAVALAGIOS Panagiotis (EEAS-EXT) wrote:
> -----Original Message-----
> From: KAVALAGIOS Panagiotis (EEAS-EXT)
> Sent: 02 March 2021 08:15
> To: cygwin@cygwin.com
> Subject: RE: Home directory was not created
>
>> -----Original Message-----
>> From: On Behalf Of Brian Inglis
>> Sent: 01 March 2021 18:38
>>
>> On 2021-03-01 08:33, KAVALAGIOS Panagiotis (EEAS-EXT) wrote:
>>> Something went wrong to my Cygwin installation update (update is
>>> performed by removing everything and installing again the new
>>> version). The home directory of my user was not created, when you
>>> run
>> Cygwin for the first time.
>>> When I start Cygwin it defaults to the evil C:\Windows\System32!?!?
>>> -bash-4.4$ pwd
>>> /cygdrive/c/WINDOWS/System32
>>> -bash-4.4$ cd
>>> -bash: cd: /home/kavalpa: No such file or directory -bash-4.4$ How
>>> this can be fixed in proper way, without causing any permission issues.
>>
>> By figuring out what went wrong during setup.
>> Please respond attaching /var/log/setup.log.full and terminal or
>> console log if possible.
>>
>> Otherwise just run setup-x86/_64 [-g] to upgrade without wiping
>> everything to avoid such problems.
>
> The log is attached. I couldn't see any error except for the libgpg-error0 package that matches the "error" search term :)
>
> The home directory is created afterwards anyway at the first Cygwin execution, if it does not exist. Are you sure it is an installation error? I would rather avoid re-installing and fix the issue by creating the conditions and force Cygwin to create the home directory.
> [Hi Brian, I apologise for this personal e-mail. I have tried to send it twice to the list to no avail. It's not HTML and it does not appear to list's mail archive either. I have no idea what is going wrong.]
> zip 358KB > 256KB too big I think
All postinstall steps failed because of BLODA or installation path:
2021/02/09 17:48:06 running: C:\Program Files\Cygwin\bin\dash.exe
"/etc/postinstall/0p_000_autorebase.dash"
0 [main] dash (2296) shared_info::initialize: size of shared memory
region changed from 49080 to 40888
2021/02/09 17:48:20 abnormal exit: exit code=-1073741819
...
Installing under Program\ Files causes issues because of space in path names and
BLODA-like AV protections on those paths.
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in binary units and prefixes, physical quantities in SI.]
next prev parent reply other threads:[~2021-03-02 18:56 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-01 15:33 KAVALAGIOS Panagiotis (EEAS-EXT)
2021-03-01 17:37 ` Brian Inglis
[not found] ` <24934718098a4d26a65b68ef62f3b46e@BELBRU-EXMP101.eeas.europa.eu>
2021-03-02 18:56 ` Brian Inglis [this message]
2021-03-03 11:22 ` KAVALAGIOS Panagiotis (EEAS-EXT)
2021-03-03 11:55 ` Andrey Repin
2021-03-03 12:59 ` KAVALAGIOS Panagiotis (EEAS-EXT)
2021-03-03 11:57 ` Thomas Wolff
2021-03-03 12:43 ` KAVALAGIOS Panagiotis (EEAS-EXT)
2021-03-03 12:58 ` Thomas Wolff
2021-03-03 13:07 ` KAVALAGIOS Panagiotis (EEAS-EXT)
2021-03-03 17:07 ` Brian Inglis
2021-03-05 21:22 ` Kraja, Aldi
2021-03-05 21:52 ` remove my email aldi@wustl.edu from the cygwin@cygwin.com email list Kraja, Aldi
2021-03-06 1:38 ` Help on Unsubscribing Brian Inglis
2021-03-05 10:17 ` Home directory was not created KAVALAGIOS Panagiotis (EEAS-EXT)
2021-03-05 18:50 ` Brian Inglis
2021-03-02 17:27 ` Adam Dinwoodie
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=4125b749-86de-ae02-43d9-16ff5a8565cd@SystematicSw.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--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).