From: Stefan Baur <X2Go-ML-1@baur-itcs.de>
To: cygwin@cygwin.com
Subject: Re: symbolic links on Paragon Linux File systems
Date: Mon, 17 Dec 2018 18:47:00 -0000 [thread overview]
Message-ID: <1d8d7c85-c88e-2404-db25-cc095f966247@baur-itcs.de> (raw)
In-Reply-To: <20181217165741.GB28727@calimero.vinschen.de>
[-- Attachment #1.1: Type: text/plain, Size: 1635 bytes --]
Am 17.12.18 um 17:57 schrieb Corinna Vinschen:
> As a sidenote, the OSS project Ext2Fsd handles symlinks transparently
> via standard Windows functions. With "CYGWIN=winsymlinks:native" you
> can generate real ext4 symlinks transparently. Even the good old Cygwin
> symlink works on Cygwin without programmatic intervention, albeit those
> won't be recognized as symlinks by Linux of course. Unfortunately
> Ext2Fsd didn't learn to handle ext4 with the 64bit FS option set yet.
> 64bit is default for quite some time.
Hmm, their website says:
> *Ext2Fsd 0.69 released !*
> November 2nd, 2017
>
> WARNINGS:
>
> Don't use Ext2Fsd 0.68 or earlier versions with latest Ubuntu or
> Debian systems. Ext2Fsd 0.68 cannot process EXT4 with 64-BIT mode
> enabled, then it could corrupt your data. Very sorry for this
> disaster issue, I'm working on an improvement.
>
> Features implemented and bugfix:
>
> 1, FIXME: superblock corruption of EXT4 volumes with 64BIT mode enabled
> 2, FIXME: possible corruption by race conditions in buffer-head reapering
> 3, FIXME: possible deadlock issues (when flushing) caused by BCB locks
> 4, FIXME: miscellaneous minor updates of Ext2Fsd code base
Sooo ... if the warning only applies for 0.68 and earlier versions,
while the current version is 0.69, as the headline says, I'd be tempted
to believe they fixed that issue.
-Stefan
--
BAUR-ITCS UG (haftungsbeschränkt)
Geschäftsführer: Stefan Baur
Eichenäckerweg 10, 89081 Ulm | Registergericht Ulm, HRB 724364
Fon/Fax 0731 40 34 66-36/-35 | USt-IdNr.: DE268653243
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2018-12-17 18:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1823593702.5343751.1545034298027.ref@mail.yahoo.com>
2018-12-17 8:11 ` Simon Liesenfeld via cygwin
2018-12-17 9:34 ` Corinna Vinschen
2018-12-17 9:41 ` Corinna Vinschen
2018-12-17 18:45 ` Corinna Vinschen
2018-12-17 18:47 ` Stefan Baur [this message]
2018-12-17 18:50 ` Stefan Baur
2018-12-17 19:22 ` Simon Liesenfeld via cygwin
2018-12-17 19:38 ` Corinna Vinschen
2018-12-17 20:50 ` Simon Liesenfeld via cygwin
2018-12-17 11:35 ` Andrey Repin
2018-12-17 12:04 ` Simon Liesenfeld via cygwin
2018-12-17 12:17 ` Corinna Vinschen
[not found] ` <1283756633.5566453.1545061591859@mail.yahoo.com>
2018-12-17 16:35 ` Simon Liesenfeld via cygwin
2018-12-17 16:57 ` Simon Liesenfeld via cygwin
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=1d8d7c85-c88e-2404-db25-cc095f966247@baur-itcs.de \
--to=x2go-ml-1@baur-itcs.de \
--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).