[openbeosstorage] Re: ISO9660/cdrom progress
- From: Tyler Dauwalder <tyler@xxxxxxxxxxxxx>
- To: openbeosstorage@xxxxxxxxxxxxx
- Date: Mon, 17 Feb 2003 02:14:40 -0800
On 2003-02-17 at 00:21:13 [-0800], Axel D=F6rfler wrote:
> Tyler Dauwalder <tyler@xxxxxxxxxxxxx> wrote:
> > > What
> > > about the chronological order of the volumes on disk -- is it
> > > implied
> > > (by the order of appearance) or explicit (time stamp)=3D3F
> > Not sure. Possibly both.
>=20
> No, I don't think it's that - I dunno if anyone knows Nero, but there
> you can actually choose the session to use in a nice tree.
> So you could do things like:
> 1. session
> 2. session based on 1. session
> 3. session based on 2. session
> 4. session based on 2. session
>=20
> Then you should (IMO) give the users the choice between session 3 & 4,
> since they are the latest sessions in their set.
Yes, I agree. 3 and 4 should be the sessions presented by default.
> > This is, afaik, not defined. Windows always presents the last=20
> > session
> > on the CD, regardless of whether it is part of a set (even if there
> > are
> > previous sessions that are *not* part of any set). R5 presents
> > everything. I would like to see us present the last session of each
> > set
> > on the CD by default (treating independent sessions as one-volume
> > sets), and offer the option of choosing or switching to earlier
> > sessions for multi-volume sets.
>=20
> Something like this, yes - I think it would be enough flag the main
> sessions on the disk, so that Tracker only shows those. Optionally, it
> should be able to show all sessions on the disk, though (not
> necessarily the correct tree, that would be overkill).
I don't know; I for one would be thoroughly impressed by an OS that=20
charted out the proper inheritance tree for a complex multi-session=20
disc. I think it would at least be nice to know the proper ordering=20
that leads up to each leaf session, but once we know that, I doubt it's=20
much more (if any) work to know the whole tree.=20
For Tracker then, we could maybe have something along the lines of a=20
"session chooser" item in pop up menus for volumes existing on=20
multi-session media that opens up a window showing the session=20
inheritance tree, allowing you to mount and unmount sessions at will. I=20
think that sort of interface would make CD backups a lot more useful=20
(providing an easily accessible, almost CVS-like backup history).
> > I will email you the specs, as I forget where I got them from
> > originally. :-) If you feel like playing with the volume descriptors
> > on
> > an iso CD, the iso9660 add-on loops through all the descriptors on a
> > volume, and can easily be made to print out more information about/
> > from
> > each it encounters.
>=20
> Me too!
Done. :-)
-Tyler
- Follow-Ups:
- [openbeosstorage] Re: ISO9660/cdrom progress
- From: Axel =?iso-8859-1?q?D=F6rfler
- References:
- [openbeosstorage] Re: ISO9660/cdrom progress
- From: Axel =?iso-8859-1?q?D=F6rfler
Other related posts:
- » [openbeosstorage] Re: ISO9660/cdrom progress
- » [openbeosstorage] Re: ISO9660/cdrom progress
- » [openbeosstorage] Re: ISO9660/cdrom progress
- » [openbeosstorage] Re: ISO9660/cdrom progress
- » [openbeosstorage] Re: ISO9660/cdrom progress
- » [openbeosstorage] Re: ISO9660/cdrom progress
- » [openbeosstorage] Re: ISO9660/cdrom progress
- » [openbeosstorage] Re: ISO9660/cdrom progress
- » [openbeosstorage] Re: ISO9660/cdrom progress
- » [openbeosstorage] Re: ISO9660/cdrom progress
- » [openbeosstorage] Re: ISO9660/cdrom progress
- » [openbeosstorage] Re: ISO9660/cdrom progress
- » [openbeosstorage] Re: ISO9660/cdrom progress
- » [openbeosstorage] Re: ISO9660/cdrom progress
- » [openbeosstorage] Re: ISO9660/cdrom progress
- » [openbeosstorage] Re: ISO9660/cdrom progress
- » [openbeosstorage] Re: ISO9660/cdrom progress
- » [openbeosstorage] Re: ISO9660/cdrom progress
- » [openbeosstorage] Re: ISO9660/cdrom progress
- » [openbeosstorage] Re: ISO9660/cdrom progress
- » [openbeosstorage] Re: ISO9660/cdrom progress
- » [openbeosstorage] Re: ISO9660/cdrom progress
- » [openbeosstorage] Re: ISO9660/cdrom progress
- » [openbeosstorage] Re: ISO9660/cdrom progress
- » [openbeosstorage] Re: ISO9660/cdrom progress
- » [openbeosstorage] Re: ISO9660/cdrom progress
- » [openbeosstorage] Re: ISO9660/cdrom progress
- » [openbeosstorage] Re: ISO9660/cdrom progress
- » [openbeosstorage] Re: ISO9660/cdrom progress
- » [openbeosstorage] Re: ISO9660/cdrom progress
- » [openbeosstorage] Re: ISO9660/cdrom progress
- » [openbeosstorage] Re: ISO9660/cdrom progress
- » [openbeosstorage] Re: ISO9660/cdrom progress
- » [openbeosstorage] ISO9660/cdrom progress
- » [openbeosstorage] Re: ISO9660/cdrom progress
- » [openbeosstorage] Re: ISO9660/cdrom progress
- » [openbeosstorage] Re: ISO9660/cdrom progress
- » [openbeosstorage] Re: ISO9660/cdrom progress
- » [openbeosstorage] Re: ISO9660/cdrom progress
- [openbeosstorage] Re: ISO9660/cdrom progress
- From: Axel =?iso-8859-1?q?D=F6rfler
- [openbeosstorage] Re: ISO9660/cdrom progress
- From: Axel =?iso-8859-1?q?D=F6rfler