[EROS-Arch] Installers
Robert Wittams
robert.wittams@ic.ac.uk
23 Mar 2001 00:22:43 +0000
> However, would install programs/scripts on EROS get away with doing
> less? Might the installers have to do *more*, just to get around the OS
> doing less? IE, it might need to make a 'filesystem' for itself (ftp
> server?),
That would be a very normal thing for an app to do. Make a private
namespace.
> cook a partition for database use
I think this is somehting that would be done in making the profile.
Ie giving it a key to a raw device.
Anyway this is Evil(TM). We have persistence!
> handle interrupts in
> strange devices,
Erm ? Confusion. Installer - not device driver.
Or do you mean detecting as yet unutilised devices?
This could be done, but by a different service.
It could use the package manager to install drivers, I suppose.
... I just don't know what is desired/expected/possible
> for the installer programs, mainly because I am unfamiliar with them.
>
> I think you may be right; however, as you said, this isn't Unix. Be
> careful assuming the enumerated list carries over from one OS to
> another.
Weird things aren't going to come out of nowhere.
Programs can only require the stuff that actually exists.
All the things that you need to mess around with on unix are gone,
and I can't see that anything that requires messing around has been
introduced.
Bye
Rob