From: "Nicolás Ortega Froysa" <nortega@themusicinnoise.net>
To: libreplanet-discuss@libreplanet.org
Subject: Re: Dropbox vs. Linux
Date: Mon, 13 Aug 2018 10:38:22 +0200 [thread overview]
Message-ID: <20180813083822.GA1179@athena.localdomain> (raw)
In-Reply-To: <1347238804.172808.1534117575793@connect.xfinity.com>
[-- Attachment #1.1: Type: text/plain, Size: 1947 bytes --]
On Sun, Aug 12, 2018 at 07:46:15PM -0400, Arthur Torrey wrote:
> I will say that I am a bit perplexed by the description of what DropBox is supposedly doing. My understanding has always been that all the file handling was done by the O/S (Gnu/Linux or other) in a transparent manner - you (a program) requests read/write on a file and the O/S handles it through the file system driver such that it always looks the same to the requester... If so, how how would DropBox even know what file system you were using, let alone care???
When I heard the news I too was a bit confused. Generally, Dropbox
shouldn't need to support anything. The only interfaces that I believe
Dropbox would have to deal with are those involving file
editing/creation/deletion, which do not change since based on filesystem
because (as you mention) the kernel takes care of that. When I write a
program in C, even if I want to do something ultra specific and
therefore use some of the `sys/' header files, it would still be
universal to every supported Linux filesystem. What is the most
perplexing is that they're not using it as an excuse to drop Linux
entirely (which would actually just mean it's a business decision and
they needed a cheap excuse), but rather they plan to continue support
for ext4, but 'not' anything else. It was pointed out to me that,
perhaps, they are not getting enough GNU/Linux users that are paying for
premium packages, and therefore it may have been a business decision to
attempt to reduce the number of GNU/Linux users.
I would actually be curious to see if, despite what Dropbox says
officially, the software still continued to function on all other Linux
filesystems.
--
Nicolás Ortega Froysa
https://themusicinnoise.net/
http://uk7ewohr7xpjuaca.onion/
Public PGP Key:
https://themusicinnoise.net/nortega@themusicinnoise.net_pub.asc
http://uk7ewohr7xpjuaca.onion/nortega@themusicinnoise.net_pub.asc
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 183 bytes --]
_______________________________________________
libreplanet-discuss mailing list
libreplanet-discuss@libreplanet.org
https://lists.libreplanet.org/mailman/listinfo/libreplanet-discuss
next prev parent reply other threads:[~2018-08-13 8:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-12 23:46 Dropbox vs. Linux Arthur Torrey
2018-08-13 8:38 ` Nicolás Ortega Froysa [this message]
2018-08-13 9:55 ` Carsten Lange
2018-08-13 19:20 ` Zygo Blaxell
2018-08-15 17:35 ` Caleb Herbert
2018-08-15 17:42 ` Nicolás Ortega Froysa
2018-08-16 1:20 ` bill-auger
2018-08-16 10:38 ` Andrea Trentini
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
List information: https://lists.gnu.org/mailman/listinfo/libreplanet-discuss
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180813083822.GA1179@athena.localdomain \
--to=nortega@themusicinnoise.net \
--cc=libreplanet-discuss@libreplanet.org \
/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).