From: <ea...@gm...> - 2007-08-18 21:57:12
|
Joe, is the frmPartSelect form supposed to show the filesystems of existing partitions (by parsing parted as well, for example), or is the "Filesystems" column there only for the user to specify what filesystem is to be used for formatting the selected partition (with reiserfs being the default choice)? |
From: <ea...@gm...> - 2007-09-04 23:29:05
|
Well, here is just an update on the installer's "progress": for about nearl= y 2 weeks I've been trying to use Gambas to call functions in libparted directly for access to a partition's filesystem name and to the free/unused space available. Parsing parted's (libparted's frontend) output on the command line is very slow, so thats basically set aside. It would be really cool to implement libparted's functions in the installer= , but so far I haven't been able to declare the functions in a way that they can be used in Gambas. Here is the thread that has been going on in the gambas-usel mailing list about this issue: http://www.nabble.com/Calling-library-functions-in-Gambas2-tf4295859.html Right now the most appealing approach other than direct use of libparted is the df command. So thats what I'll be using so that work on the installer can continue. But I'm posting this so that if anyone has any idea on how to declare the libparted functions in a usable manner in Gambas, then that can be implemented instead of parsing df... Cheers, Eug=E9ne |
From: Jose J. R. <jo...@gm...> - 2007-09-05 00:58:14
|
On 9/4/07, Eug=E9ne Suter <ea...@gm...> wrote: > Well, here is just an update on the installer's "progress": for about nea= rly > 2 weeks I've been trying to use Gambas to call functions in libparted > directly for access to a partition's filesystem name and to the free/unus= ed > space available. > I've been following that thread and even had a quick look at the libparted manual, but it's too damned obscure for a simple quick look... What I propose is that we concentrate first on installing to a full drive and to empty space. An old teacher of mine taught me as a kid that you should always answer the easier questions on a test first, to put them behind you... :) I believe a first version of the installer would be functional enough with a simple note that you should use a liveCD if you need to resize partitions. Let's get something working first, then build from there. Regards, Joe1962 |
From: <ea...@gm...> - 2007-09-05 01:09:56
|
On 05/09/07, Jose J. Rodriguez <jo...@gm...> wrote: > I've been following that thread and even had a quick look at the > libparted manual, but it's too damned obscure for a simple quick > look... What I propose is that we concentrate first on installing to a > full drive and to empty space. An old teacher of mine taught me as a > kid that you should always answer the easier questions on a test > first, to put them behind you... :) Indeed, I just hate being defeated by a computer... :\ I believe a first version of the installer would be functional enough > with a simple note that you should use a liveCD if you need to resize > partitions. Let's get something working first, then build from there. > > Regards, > Joe1962 Meanwhile, uelsk8s has brought a couple of useful commands to my attention, probedisk and disktype (actually probepart as well, but its a script that uses probedisk and disktype). At least from a first look, it seems like probedisk and disktype combined can give all the info that fdisk + parted could. So it looks like its possible after all :) Cheers, Eug=E9ne |
From: Jose J. R. <jo...@gm...> - 2007-09-05 01:18:05
|
On 9/4/07, Eug=E9ne Suter <ea...@gm...> wrote: > On 05/09/07, Jose J. Rodriguez <jo...@gm...> wrote: > > I've been following that thread and even had a quick look at the > > libparted manual, but it's too damned obscure for a simple quick > > look... What I propose is that we concentrate first on installing to a > > full drive and to empty space. An old teacher of mine taught me as a > > kid that you should always answer the easier questions on a test > > first, to put them behind you... :) > > Indeed, I just hate being defeated by a computer... :\ > I always had this unwritten TODO item, which I discussed with Uel at one point, to use libparted and build-in our own dedicated partitioner with only the stuff needed for an installer. However, I figured we should not reinvent the wheel till we actually had a working installer. After that, the sky's the limit... ;) > > > I believe a first version of the installer would be functional enough > > with a simple note that you should use a liveCD if you need to resize > > partitions. Let's get something working first, then build from there. > > > > Regards, > > Joe1962 > > Meanwhile, uelsk8s has brought a couple of useful commands to my attentio= n, > probedisk and disktype (actually probepart as well, but its a script that > uses probedisk and disktype). > At least from a first look, it seems like probedisk and disktype combined > can give all the info that fdisk + parted could. So it looks like its > possible after all :) > Dang, I put a lot of work into that international-ready fdisk parser... :( It probably works at least for all languages that use our number characters, since I tested a lot of them, some of which I couldn't even read what I was doing, lol. Regards, Joe1962 |
From: <ea...@gm...> - 2007-09-05 01:39:45
|
On 05/09/07, Jose J. Rodriguez <jo...@gm...> wrote: > Dang, I put a lot of work into that international-ready fdisk > parser... :( It probably works at least for all languages that use > our number characters, since I tested a lot of them, some of which I > couldn't even read what I was doing, lol. > > Regards, > Joe1962 Well I haven't actually removed anything so far, and probably wont work on it until the end of the week ("real-life" taking over). It would be a shame= , its the neatest code in the installer :) Anyway, it does look like disktype can be processed at the same time as the fdisk output (and in the same sub) so it doesn't necessarily have to be removed ;). One of my objectives was to get all the data necessary processe= d at once, not in bit-and pieces like the current getFileSystems() sub does..= . Eug=E9ne |
From: <ea...@gm...> - 2007-09-10 00:35:56
|
Today I've been working on some of the filesystem identification and updating the frmPartSelect class to display filesystem information I've encountered a problem though: if I create a non-linux filesystem where a linux filesystem used to be, fdisk does not update this information until the computer is rebooted. So frmPartSelect will display something like this: | Filesystem | | Linux - NTFS | when it should display | HPFS/NTFS - NTFS | I'm guessing that after a user has used GParted of cfdisk from the installer's embedder we will have to force them to reboot so that fdisk can refresh its data, instead sending them right along to the frmPartSelect form to setup mountpoints/filesystem :( Is there any way to force fdisk to update its information without rebooting? It would probably be a lot better to let the user proceed right away after setting up partitions than having to reboot. |
From: uel a. <ue...@gm...> - 2007-09-10 01:02:23
|
I would say if they create a non-linuxfilesystem then force a reboot. the current installer ask you to reboot after fdisk how often would you create a non-linux filesystem in linux anyway? ---------- Forwarded message ---------- From: Eug=E9ne Suter <ea...@gm...> Date: Sep 9, 2007 6:35 PM Subject: Re: [Vectorlinux-devel] The installer To: Vector Linux developer's list < vec...@li...= > Today I've been working on some of the filesystem identification and updating the frmPartSelect class to display filesystem information I've encountered a problem though: if I create a non-linux filesystem where a linux filesystem used to be, fdisk does not update this information until the computer is rebooted. So frmPartSelect will display something like this= : | Filesystem | | Linux - NTFS | when it should display | HPFS/NTFS - NTFS | I'm guessing that after a user has used GParted of cfdisk from the installer's embedder we will have to force them to reboot so that fdisk can refresh its data, instead sending them right along to the frmPartSelect for= m to setup mountpoints/filesystem :( Is there any way to force fdisk to update its information without rebooting= ? It would probably be a lot better to let the user proceed right away after setting up partitions than having to reboot. ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Vectorlinux-devel mailing list Vec...@li... https://lists.sourceforge.net/lists/listinfo/vectorlinux-devel |
From: <ea...@gm...> - 2007-09-10 08:12:21
|
On 10/09/2007, uel archuletta <ue...@gm...> wrote: > how often would you create a non-linux filesystem in linux anyway? Well, while using GParted, the user may create any partition he/she wants, maybe a FAT partiton that will later be used as a shared drive?... Anyway, force a reboot it is then. |
From: <ea...@gm...> - 2007-09-12 01:55:57
|
Hi again, I have a question I probably should have asked a lot earlier.... So far I've been working on getting filesystem types and free spaces assuming that the "Free Space" installation option is for using the free space on a selected partition...is it (eg: user selects a big windows partition with plenty of space on it, the installer will resize that partition automatically to make space)? Or was it supposed to be something else, like unpartitioned disk space? Even if what I was doing is "wrong" I guess its not worth scrapping this fa= r along... :( Eug=E9ne |
From: Jose J. R. <jo...@gm...> - 2007-09-12 02:37:30
|
On 9/11/07, Eug=E9ne Suter <ea...@gm...> wrote: > Hi again, > > I have a question I probably should have asked a lot earlier.... > So far I've been working on getting filesystem types and free spaces > assuming that the "Free Space" installation option is for using the free > space on a selected partition...is it (eg: user selects a big windows > partition with plenty of space on it, the installer will resize that > partition automatically to make space)? Nope. That's an advanced installer function, I figured we could leave that as a manual pass of gparted for now. > Or was it supposed to be something else, like unpartitioned disk space? That's exactly it. As I was saying the other day, prioritizing full disk and empty (unpartitioned) space is the easier way to go to actually get a working installer in smaller time frame. Then we add the frills. > Even if what I was doing is "wrong" I guess its not worth scrapping this = far > along... :( > Of course not, we'll need it later on anyway. Regards, Joe1962 |