Browsing this Thread:
1 Anonymous Users
|
Re: Phase II
|
||||
|---|---|---|---|---|
|
Home away from home
 
|
1. Volume Manager - implement the basic volume manager resource, and its API.
2. fully manual partitioning possible 3. List out partitions already on the partition table so one can see where other OSs are installed and booting from those other bootable partitions from boot menu, as far as supported by GRUB. 4. The InstallAROS GUI sould have an "Advanced" option for the copying of extras with the packages listed so that users could individually enable/disable ones they wanted. 5. GUI Boot Menu Editor.
Posted on: 2007/4/1 14:52
|
|||
|
||||
|
Phase I
|
||||
|---|---|---|---|---|
|
Home away from home
|
1. User able to select HD.
2. Able to co-exist with other partitions. 3. Able to accept other file systems types as they are supported by AROS. 4. Autodetect Windows, and would set up GRUB to multiboot Windows and AROS. It wouldn't do this for Linux or other OSs, but it wouldn't overwrite their partitions of course (unless wiping the disk is requested by the user). 5. Selection of keyboard layout early in the installation. 6. Options to create either one partition, or separate System and Work partitions. Partition sizes can be typed in, or the user can ask to use all available space. 7. No fully manual partitioning needed. However, perhaps HDToolbox could be started from the installer to fill this role if it can be made reasonably reliable. 8. Fixed partition.library. Logical partitions sould be supported by the installer too.
Posted on: 2007/4/1 14:42
|
|||
|
||||
|
Re: Revised Installer bounty proposal
|
||||
|---|---|---|---|---|
|
Home away from home
|
@craid-hjb:
Yes, that's more or less what I was implying. I think the bounty needs to be split up or made simpler in order for some real progress to be made towards a better installer.
Posted on: 2007/3/7 17:14
|
|||
|
||||
|
Re: Revised Installer bounty proposal
|
||||
|---|---|---|---|---|
|
Just can't stay away
 
|
Quote:
As the FAT handler currently does not support writing data on media managed by FAT, it would become quite a lot of work to figure out what is working and what is not. I guess if you are installing multiboot environments, writing a minimal bootstrap on the primary FAT partition and starting AROS off from any AROS supported partition (FFS, SFS...) would sound perfect to the users' ears. We then only need a Windows FFS/SFS driver to access AROS data (I'm just joking  ).Manu
Posted on: 2007/3/7 13:53
|
|||
|
AROS
 Always believe in a better future!
|
||||
|
||||
|
Re: Revised Installer bounty proposal
|
||||
|---|---|---|---|---|
|
Home away from home
|
@Kalamatee & ncafferkey
In the beginning I was against dividing of this bounty, but right now I am beginning to be more and more skeptic. All the proposals brought up by you Kal are very judicious, but don?t you think it would make the bounty far more difficult as it?s needed right now.. in context of the possible opportunities within partition.library, partition recognition, HDToolbox, isn?t this task just getting to big for one person? What about dividing into following parts? Installer Part I Quote:
.. the second part would go more into the detail and could look like this: Installer Part II Quote:
I don?t know how far the new fat.handler could alleviate dualboot AROS+Windows (storing Kernel on fat partition?). Please give some feedback..
Posted on: 2007/3/7 10:07
|
|||
|
||||
|
Re: Revised Installer bounty proposal
|
||||
|---|---|---|---|---|
|
Home away from home
|
Why don?t you two agree on what should be done and cooperate to finish the bounty.
Posted on: 2007/3/7 7:30
|
|||
|
Daniel Olen......
Asus K8NE.d a64-3200+ Nvidia6600 |
||||
|
||||
|
Re: Revised Installer bounty proposal
|
||||
|---|---|---|---|---|
|
Home away from home
|
Or at the least, have an option that doesn't overwrite the users custom startup-sequeunce / user-startup if someone wants to reinstall over an existing installation.
Posted on: 2007/3/7 7:24
|
|||
|
||||
|
Re: Revised Installer bounty proposal
|
||||
|---|---|---|---|---|
|
Home away from home
|
Another thing I wanted to finish doing in the installer was to deal with "packages" completely seperate to the main "Extras" Copying.
I had planned to make InstallAROS Remove the paths defined in the packages env variable from the list to copy - and have them as seperate entities of it. The InstallAROS GUI would have an "Advanced" option for the copying of extras with the packages listed so that users could individually enable/disable ones they wanted - and have the default path available so they can install them all to custom locations. At the end of the copying the package env variables would be fixed (which currently doesnt happen) so everything should work after a reboot.
Posted on: 2007/3/7 7:07
|
|||
|
||||
|
Re: Revised Installer bounty proposal
|
||||
|---|---|---|---|---|
|
Home away from home
|
Quote:
Well theres a couple of pitfalls to how its done just now. A> Most of the tools use utility librarys list of boot devices to find out what drives are available which doesnt really work B> As u state your limited to ata.device without user intervention. This was first a problem when we moved from ide.device in the looong past to the ata.device we all know and love currently. If at some point we gain other drivers (for sata/scsi/fibre cards or usb drives etc) it would be preferable the tools automagically found the connected hardware. Atleast after much discussion on the subject on IRC this was made to feel like a neccessity.
Posted on: 2007/3/7 7:03
|
|||
|
||||
|
Re: Revised Installer bounty proposal
|
||||
|---|---|---|---|---|
|
Home away from home
|
Quote:
Yes, you're correct that manual intervention may be required in some circumstances. Remember that the reason I'm proposing to drop some of the bounty requirements is not because they're not useful, but to make the bounty completable in a reasonable time. So yes, when the revised bounty is completed, the installer won't do everything we'd like, but it will be a major improvement. Quote:
Yes, I could give the user the option to launch HDToolbox, but I won't make any promises about making HDToolbox 100% reliable. Quote:
This part of the installer would be unchanged: it would only work with ata.device. Again, I'm not saying it wouldn't be useful.
Posted on: 2007/3/6 17:31
|
|||
|
||||
You can view topic.
You cannot start a new topic.
You cannot reply to posts.
You cannot edit your posts.
You cannot delete your posts.
You cannot add new polls.
You cannot vote in polls.
You cannot attach files to posts.
You cannot post without approval.
You cannot use topic type.
You cannot use HTML syntax.
You cannot use signature.
You cannot create PDF files.
You cannot get print page.
