From: Richard Adams <pa3gcu@zeelandnet.nl>
To: Suriya Narayanan M S <mssnlayam@cs.annauniv.edu>,
Paul Furness <paul.furness@vil.ite.mee.com>
Cc: GNU/Linux Newbie <linux-newbie@vger.kernel.org>
Subject: Re: CD writing in ext2 filesystem
Date: Thu, 25 Apr 2002 18:34:46 +0000 [thread overview]
Message-ID: <02042518344606.04696@unix.pa3gcu> (raw)
In-Reply-To: <200204250727.51401.mssnlayam@cs.annauniv.edu>
On Thursday 25 April 2002 17:00, Suriya Narayanan M S wrote:
> On Wednesday 24 April 2002 15:15, Paul Furness wrote:
> > Is there a particular reason why you were trying to put an ext2 fiole
> > system on the CD rather than an ISO9660 one?
>
> Yes. One would like to have all the filesystems to be of the same
> type. It would be easier to handle and there would be no
> inconsistencies. It (the one you use regularly) is the best filesystem
> to backup data.
>
> But the main advantage (of using ext2) is that you get a
> filesystem which is the same as your native system. Permissions,
> ownership, symlinks, pipes, device files..... (all the great features
> of ext2) get taken care of. Most of the above would
> not be possible with iso9660. The Rockridge extensions handle them
> well. However it too has a problem with the maximum depth
> of a directory tree.
UUM, excuse me for only thinking, but, if one creates a tarball and then
burns it to a cd, one then has the same, or am i missing something here.?????
How do you think a linux distribution comes on a cdrom.????
Its iso9660 of course, but when its copied onto a H/D it has permissions of
its piers.
I do not see your point of view here, if i am missing something please tell
me, i am at a loss as to what in the world it could be.
>
> If you do not need your CD to be accessed on other OSs
> then ext2 is the best bet.
>
> Bye,
> Suriya Narayanan M S
--
Regards Richard
pa3gcu@zeelandnet.nl
http://people.zeelandnet.nl/pa3gcu/
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
next prev parent reply other threads:[~2002-04-25 18:34 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-23 17:48 CD writing in ext2 filesystem Suriya Narayanan M S
2002-04-23 18:47 ` Pierre Rousselet
2002-04-23 20:43 ` Staci
2002-04-24 9:45 ` Paul Furness
2002-04-24 14:50 ` Richard Adams
2002-04-25 17:00 ` Suriya Narayanan M S
2002-04-25 18:34 ` Richard Adams [this message]
2002-04-25 18:49 ` Pierre Rousselet
2002-04-25 19:20 ` Richard Adams
2002-04-25 19:12 ` Steven Smith
2002-04-25 19:29 ` Richard Adams
-- strict thread matches above, loose matches on Subject: below --
2002-04-25 1:24 Suriya Narayanan M S
2002-04-25 15:52 ` Richard Adams
2002-04-21 16:51 Suriya Narayanan M S
2002-04-21 19:59 ` Pierre Rousselet
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=02042518344606.04696@unix.pa3gcu \
--to=pa3gcu@zeelandnet.nl \
--cc=linux-newbie@vger.kernel.org \
--cc=mssnlayam@cs.annauniv.edu \
--cc=paul.furness@vil.ite.mee.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.