Re: Facing the End ;-)

> "Ingo Weinhold" <bonefish-CFLBMwTPW48UNGrzBIF7/[email protected]> wrote:
> [...]
> > > It would be nice if the GUI app (or any other resizer app) could 
> > > just 
> > > continue where it stopped before the crash. Some kind of a 
> > > journaled 
> > > partition resizing.
> > Do I understand you correctly, that you want to be able to resize 
> > the 
> > boot partition while being mounted, abort the process the hard way 
> > using the power switch and still expect the OS to boot like a charm
> > =3F 
> > That's definitely something users of other OSs would be damn 
> > impressed 
> > by. ;-)
> 
> And that's not even my primary concern ;-))
> I don't think that partition resizing is done very often, but I think 
> we have to provide a mechanism to make them safe against any crashes.
> And when we've done that (and support defragmentation [and API to 
> move 
> files around]), doing the "online" version of it should be easy (yet 
> very nice ;).

I'll just trust you on that. ;-)

> [...]
> > > We should have a unified way to detect disk changes - I think 
> > > BeOS 
> > > already has this, but I am too lazy now to look it up.
> > I just found the B=5FGET=5FMEDIA=5FSTATUS ioctl(), if you mean 
> > that. It is 
> > alright for a polling solution for removable media.
> 
> Well, AFAIK polling is the only way. All other notify mechanisms 
> aren't 
> reliable. We could have a kernel daemon that checks for media 
> changes, 
> and unmount devices if needed.

Yep.

> That way, we wouldn't have to care (almost) anywhere else in the 
> kernel, and still provide notifications for higher levels.
> The daemon would iterate over all mounted devices (using next=
> 5Fdev()) 
> and asks them if they had any media changes. Perhaps we can even have 
> a 
> more optimized internal API for that purpose.

It should not only iterate over mounted devices. All devices are of 
interest. E.g. if you insert a CD, there should be a notification, so 
that the Tracker can decide whether or not to mount it.

CU, Ingo