Menu
▾
▴
vectorlinux-devel — Vector Linux developer's list
You can subscribe to this list here.
| 2006 |
Jan
|
Feb
|
Mar
(40) |
Apr
(76) |
May
(31) |
Jun
(39) |
Jul
(44) |
Aug
(87) |
Sep
(32) |
Oct
(23) |
Nov
(36) |
Dec
(10) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2007 |
Jan
(3) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(2) |
Aug
(49) |
Sep
(14) |
Oct
|
Nov
|
Dec
(1) |
| 2008 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(63) |
Aug
(95) |
Sep
(39) |
Oct
(61) |
Nov
(75) |
Dec
(118) |
| 2009 |
Jan
(25) |
Feb
(37) |
Mar
(20) |
Apr
(15) |
May
(14) |
Jun
(48) |
Jul
(82) |
Aug
(160) |
Sep
(94) |
Oct
(55) |
Nov
(59) |
Dec
(4) |
| 2010 |
Jan
(5) |
Feb
(17) |
Mar
(6) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(3) |
Oct
|
Nov
|
Dec
|
| 2011 |
Jan
(2) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2012 |
Jan
|
Feb
|
Mar
(1) |
Apr
(2) |
May
|
Jun
|
Jul
|
Aug
|
Sep
(2) |
Oct
|
Nov
(1) |
Dec
|
| 2013 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2016 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(1) |
|
From: M0E L. <m0...@gm...> - 2007-08-15 00:34:52
|
So then, you do need to know the ammount of free space left on the device so you can then resize which ever partition is the largest and steal space to make your Linux friendly partition. This involves * an analysis of the drive to determine what partitions are present. * If in Wind OS, most likely one hughe partition for the system and mayne a backup / restore partition * Maybe analyze the size of each partition to determine which one is the largest and also to get a correct label for your new partitons (/dev/hdxx) On 8/14/07, uel archuletta <ue...@gm...> wrote: > Sorry I didnt think about wanting to resize. > i dont have any ext3 partitions but I do get this error with ext2 > root:# parted /dev/hdb print 5 > Error: File system was not cleanly unmounted! You should run e2fsck. > Modifying > an unclean file system could cause severe corruption. > Ignore/Cancel? i > > Minor: 5 > Flags: > File System: ext2 > Size: 10.5GB (4.20%) > Minimum size: 9001MB (3.60%) > Maximum size: 250GB (100%) > > and it seems the version of parted i have doesnt support ntfs > root:# parted /dev/hda print 1 > No Implementation: Support for opening ntfs file systems is not implement= ed > yet. > but works well with fat32 > root:# parted /dev/hdb print 1 > > Minor: 1 > Flags: boot, lba > File System: fat32 > Size: 105GB (41.9%) > Minimum size: 97.5GB (39.0%) > Maximum size: 250GB (100%) > > uel > > On 8/14/07, Eug=E9ne Suter <ea...@gm...> wrote: > > > > Seems that parted can be used for this after all (according to the post= in > the gparted forum): > > > > > > > > > Lets say the partition you want to check is a fat32 partition on > /dev/hda1. > > > > > > >parted /dev/hda1 > > > > > > bla bla bla > > > > > > >print 1 > > > > > > Minor: 1 > > > Flags: > > > File System: fat32 > > > Size: 10.0GB (100%) > > > Minimum size: 8369MB (83.7%) <------- RIGHT HERE > > > Maximum size: 10.0GB (100%) > > > > > > 100% - 83.7% =3D 16.3% free > > > > > > That's how GParted does it. Hope this helps. > > > > > > Patrick Verner > > > www.partedmagic.com > > > > > > > > Problem is, this only works for me on non ext* filesystems. > > Running parted against one of my ext3 backup partitions gives this erro= r: > > > > > > > > > root:# parted /dev/hda print 5 > > > Error: File system has an incompatible feature enabled. > > > > Anyone else get this problem on ext3 partitions as well? > > > > > > > ------------------------------------------------------------------------- > > This SF.net email is sponsored by: Splunk Inc. > > Still grepping through log files to find problems? Stop. > > Now Search log events and configuration files using AJAX and a browser. > > Download your FREE copy of Splunk now >> http://get.splunk.com/ > > _______________________________________________ > > Vectorlinux-devel mailing list > > Vec...@li... > > > https://lists.sourceforge.net/lists/listinfo/vectorlinux-devel > > > > > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > Vectorlinux-devel mailing list > Vec...@li... > https://lists.sourceforge.net/lists/listinfo/vectorlinux-devel > > |
|
From: uel a. <ue...@gm...> - 2007-08-14 23:18:50
|
Sorry I didnt think about wanting to resize. i dont have any ext3 partitions but I do get this error with ext2 root:# parted /dev/hdb print 5 Error: File system was not cleanly unmounted! You should run e2fsck. Modifying an unclean file system could cause severe corruption. Ignore/Cancel? i Minor: 5 Flags: File System: ext2 Size: 10.5GB (4.20%) Minimum size: 9001MB (3.60%) Maximum size: 250GB (100%) and it seems the version of parted i have doesnt support ntfs root:# parted /dev/hda print 1 No Implementation: Support for opening ntfs file systems is not implemented yet. but works well with fat32 root:# parted /dev/hdb print 1 Minor: 1 Flags: boot, lba File System: fat32 Size: 105GB (41.9%) Minimum size: 97.5GB (39.0%) Maximum size: 250GB (100%) uel On 8/14/07, Eug=E9ne Suter <ea...@gm...> wrote: > > Seems that parted can be used for this after all (according to the post i= n > the gparted forum): > > > Lets say the partition you want to check is a fat32 partition on > > /dev/hda1. > > > > >parted /dev/hda1 > > > > bla bla bla > > > > >print 1 > > > > Minor: 1 > > Flags: > > File System: fat32 > > Size: 10.0GB (100%) > > Minimum size: 8369MB (83.7%) <------- RIGHT HERE > > Maximum size: 10.0GB (100%) > > > > 100% - 83.7% =3D 16.3% free > > > > That's how GParted does it. Hope this helps. > > > > Patrick Verner > > www.partedmagic.com > > > > Problem is, this only works for me on non ext* filesystems. > Running parted against one of my ext3 backup partitions gives this error: > > > root:# parted /dev/hda print 5 > > Error: File system has an incompatible feature enabled. > > > Anyone else get this problem on ext3 partitions as well? > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > Vectorlinux-devel mailing list > Vec...@li... > https://lists.sourceforge.net/lists/listinfo/vectorlinux-devel > > |
|
From: <ea...@gm...> - 2007-08-14 23:01:38
|
Seems that parted can be used for this after all (according to the post in the gparted forum): Lets say the partition you want to check is a fat32 partition on /dev/hda1. > > >parted /dev/hda1 > > bla bla bla > > >print 1 > > Minor: 1 > Flags: > File System: fat32 > Size: 10.0GB (100%) > Minimum size: 8369MB (83.7%) <------- RIGHT HERE > Maximum size: 10.0GB (100%) > > 100% - 83.7% = 16.3% free > > That's how GParted does it. Hope this helps. > > Patrick Verner > www.partedmagic.com Problem is, this only works for me on non ext* filesystems. Running parted against one of my ext3 backup partitions gives this error: root:# parted /dev/hda print 5 > Error: File system has an incompatible feature enabled. Anyone else get this problem on ext3 partitions as well? |
|
From: <ea...@gm...> - 2007-08-14 21:34:22
|
Parted allows resizing of ntfs and fat partitions as well, so the idea is to allow the user to chose *any* partition he/she wishes to "steal" space from, even windows partitions. On 14/08/07, M0E Lnx <m0...@gm...> wrote: > > Does this assume the available "free space" is on a linux > friendly-formatted partition? or does this require resizing a hughe > vfat or ntfs and creating the necessary ext* partitions? > |
|
From: M0E L. <m0...@gm...> - 2007-08-14 21:06:56
|
Does this assume the available "free space" is on a linux friendly-formatted partition? or does this require resizing a hughe vfat or ntfs and creating the necessary ext* partitions? On 8/14/07, Eug=E9ne Suter <ea...@gm...> wrote: > Well, for the automatic partitioning mode, the entire drive is erased and > new partition sizes are calculated and compared to the amount of space th= at > the packages will occupy. > > But for the free-space mode (in which only free space from an existing > partition is used), it is not going to make any modifications to the driv= e > at all until it is sure that the packages will fit in that unused > space...thats why its important to know how much unused space that select= ed > partition has. > > Using the df method is my last resort...its *really* messy (especially if > the user has many partitions). > > > > On 14/08/07, M0E Lnx < m0...@gm...> wrote: > > Well, if this is for the "auto-partition" mode, then I think we > > definitely need to know how much space we got to play with ;) > > > > That way, the installer can allocate the necessary space for the > > necessary partitions. > > > > On 8/14/07, uel archuletta < ue...@gm...> wrote: > > > you shouldnt need to know the unused space on a partition only the > partition > > > size. since we should format the partitions, shouldnt we? > > > > > > Uel > > > > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > Vectorlinux-devel mailing list > Vec...@li... > https://lists.sourceforge.net/lists/listinfo/vectorlinux-devel > > |
|
From: <ea...@gm...> - 2007-08-14 20:58:43
|
Well, for the automatic partitioning mode, the entire drive is erased and new partition sizes are calculated and compared to the amount of space that the packages will occupy. But for the free-space mode (in which only free space from an existing partition is used), it is not going to make any modifications to the drive at all until it is sure that the packages will fit in that unused space...thats why its important to know how much unused space that selected partition has. Using the df method is my last resort...its *really* messy (especially if the user has many partitions). On 14/08/07, M0E Lnx <m0...@gm...> wrote: > > Well, if this is for the "auto-partition" mode, then I think we > definitely need to know how much space we got to play with ;) > > That way, the installer can allocate the necessary space for the > necessary partitions. > > On 8/14/07, uel archuletta <ue...@gm...> wrote: > > you shouldnt need to know the unused space on a partition only the > partition > > size. since we should format the partitions, shouldnt we? > > > > Uel > > |
|
From: M0E L. <m0...@gm...> - 2007-08-14 20:40:28
|
Well, if this is for the "auto-partition" mode, then I think we definitely need to know how much space we got to play with ;) That way, the installer can allocate the necessary space for the necessary partitions. On 8/14/07, uel archuletta <ue...@gm...> wrote: > you shouldnt need to know the unused space on a partition only the partit= ion > size. since we should format the partitions, shouldnt we? > > Uel > > On 8/14/07, Eug=E9ne Suter <ea...@gm...> wrote: > > > > Well, a little update on whats happening with the drive partitioning: > > I'm trying to get the installer to check for available space before > installing anything (since this was one of the flaws that the text instal= ler > has: it will crash and burn if space runs out). > > > > This is easy enough to accomplish for the full-auto partitioning mode, > since the installer creates the partitions, it knows how much space there= is > available. > > But for the "free-space mode" its a different story: the unused space > values have to be obtained some other way, and from reading parted's > documentation and asking on the #parted channel, libparted does not provi= de > any way to know the amount of unused space on an *unmounted* partition. > > > > One possible way would be to mount ALL the partitions found and parse d= f, > but thats a somewhat messy approach. > > The best would be to get the amount of unused space when the partitions > are still unmounted (so these values can be displayed to the user before > selecting a partition). > > > > I've opened a thread on the GParted forum about this > (http://gparted-forum.surf4.info/viewtopic.php?id=3D862 ), > since they have obviously found a way to do this. > > Any ideas on solving this problem some other way? > > > > Cheers, > > > > Eug=E9ne > > > > > ------------------------------------------------------------------------- > > This SF.net email is sponsored by: Splunk Inc. > > Still grepping through log files to find problems? Stop. > > Now Search log events and configuration files using AJAX and a browser. > > Download your FREE copy of Splunk now >> http://get.splunk.com/ > > _______________________________________________ > > Vectorlinux-devel mailing list > > Vec...@li... > > > https://lists.sourceforge.net/lists/listinfo/vectorlinux-devel > > > > > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > Vectorlinux-devel mailing list > Vec...@li... > https://lists.sourceforge.net/lists/listinfo/vectorlinux-devel > > |
|
From: uel a. <ue...@gm...> - 2007-08-14 20:29:42
|
you shouldnt need to know the unused space on a partition only the partitio= n size. since we should format the partitions, shouldnt we? Uel On 8/14/07, Eug=E9ne Suter <ea...@gm...> wrote: > > Well, a little update on whats happening with the drive partitioning: > I'm trying to get the installer to check for available space before > installing anything (since this was one of the flaws that the text instal= ler > has: it will crash and burn if space runs out). > > This is easy enough to accomplish for the full-auto partitioning mode, > since the installer creates the partitions, it knows how much space there= is > available. > But for the "free-space mode" its a different story: the unused space > values have to be obtained some other way, and from reading parted's > documentation and asking on the #parted channel, libparted does not provi= de > any way to know the amount of unused space on an *unmounted* partition. > > One possible way would be to mount ALL the partitions found and parse df, > but thats a somewhat messy approach. > The best would be to get the amount of unused space when the partitions > are still unmounted (so these values can be displayed to the user before > selecting a partition). > > I've opened a thread on the GParted forum about this ( > http://gparted-forum.surf4.info/viewtopic.php?id=3D862), since they have > obviously found a way to do this. > Any ideas on solving this problem some other way? > > Cheers, > > Eug=E9ne > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > Vectorlinux-devel mailing list > Vec...@li... > https://lists.sourceforge.net/lists/listinfo/vectorlinux-devel > > |
|
From: M0E L. <m0...@gm...> - 2007-08-14 20:28:44
|
I would say mount the go the messy way... * Mount the partitions * Get your values * un-mount the partitions * move on... On 8/14/07, Eug=E9ne Suter <ea...@gm...> wrote: > Well, a little update on whats happening with the drive partitioning: > I'm trying to get the installer to check for available space before > installing anything (since this was one of the flaws that the text instal= ler > has: it will crash and burn if space runs out). > > This is easy enough to accomplish for the full-auto partitioning mode, si= nce > the installer creates the partitions, it knows how much space there is > available. > But for the "free-space mode" its a different story: the unused space val= ues > have to be obtained some other way, and from reading parted's documentati= on > and asking on the #parted channel, libparted does not provide any way to > know the amount of unused space on an *unmounted* partition. > > One possible way would be to mount ALL the partitions found and parse df, > but thats a somewhat messy approach. > The best would be to get the amount of unused space when the partitions a= re > still unmounted (so these values can be displayed to the user before > selecting a partition). > > I've opened a thread on the GParted forum about this > (http://gparted-forum.surf4.info/viewtopic.php?id=3D862), > since they have obviously found a way to do this. > Any ideas on solving this problem some other way? > > Cheers, > > Eug=E9ne > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > Vectorlinux-devel mailing list > Vec...@li... > https://lists.sourceforge.net/lists/listinfo/vectorlinux-devel > > |
|
From: <ea...@gm...> - 2007-08-14 20:09:11
|
Well, a little update on whats happening with the drive partitioning: I'm trying to get the installer to check for available space before installing anything (since this was one of the flaws that the text installe= r has: it will crash and burn if space runs out). This is easy enough to accomplish for the full-auto partitioning mode, sinc= e the installer creates the partitions, it knows how much space there is available. But for the "free-space mode" its a different story: the unused space value= s have to be obtained some other way, and from reading parted's documentation and asking on the #parted channel, libparted does not provide any way to know the amount of unused space on an *unmounted* partition. One possible way would be to mount ALL the partitions found and parse df, but thats a somewhat messy approach. The best would be to get the amount of unused space when the partitions are still unmounted (so these values can be displayed to the user before selecting a partition). I've opened a thread on the GParted forum about this ( http://gparted-forum.surf4.info/viewtopic.php?id=3D862), since they have obviously found a way to do this. Any ideas on solving this problem some other way? Cheers, Eug=E9ne |
|
From: <cod...@go...> - 2007-08-13 20:17:55
|
Author: M0E.lnx
Date: Mon Aug 13 13:17:02 2007
New Revision: 21
Added:
trunk/frmChooseFB.class
trunk/frmChooseFB.form
Modified:
trunk/.lang/.pot
trunk/.project
trunk/Functions.module
trunk/Global.class
trunk/frmChooseMBR.class
Log:
The boot manager installer can now detect the MBR's on several devices (if available) it can find the root partition on the Linux Install, it can also find the kernel And offers to choose a boot mode (bootsplash and fb modes) and Stores the information to the Global class. This information will be used to write lilo.conf
Modified: trunk/.lang/.pot
==============================================================================
--- trunk/.lang/.pot (original)
+++ trunk/.lang/.pot Mon Aug 13 13:17:02 2007
@@ -22,7 +22,8 @@
msgid "OK"
msgstr ""
-#: InputBox.class:212 frmDriveSelect.class:133 frmPartSelect.class:379
+#: InputBox.class:212 frmChooseFB.class:91 frmDriveSelect.class:133
+#: frmPartSelect.class:379
msgid "Cancel"
msgstr ""
@@ -67,15 +68,71 @@
msgid "Advanced"
msgstr ""
-#: frmChooseMBR.class:46
+#: frmChooseFB.class:76
+msgid "Please Select Boot Mode:"
+msgstr ""
+
+#: frmChooseFB.class:81
+msgid "Standard [ The standard Linux Console ]"
+msgstr ""
+
+#: frmChooseFB.class:81
+msgid "Bootsplash - high [ 1024x768 image ]"
+msgstr ""
+
+#: frmChooseFB.class:81
+msgid "Bootsplash - med [ 800x600 image ]"
+msgstr ""
+
+#: frmChooseFB.class:81
+msgid "Bootsplash - low [ 640x480 image ]"
+msgstr ""
+
+#: frmChooseFB.class:81
+msgid "640 x 480 @ 256"
+msgstr ""
+
+#: frmChooseFB.class:81
+msgid "800 x 600 @ 256"
+msgstr ""
+
+#: frmChooseFB.class:81
+msgid "1024 x 768 @ 256"
+msgstr ""
+
+#: frmChooseFB.class:81
+msgid "640 x 480 @ 32k"
+msgstr ""
+
+#: frmChooseFB.class:81
+msgid "800 x 600 @ 32k"
+msgstr ""
+
+#: frmChooseFB.class:81
+msgid "1024 x 768 @ 32k"
+msgstr ""
+
+#: frmChooseFB.class:81
+msgid "640 x 480 @ 64k"
+msgstr ""
+
+#: frmChooseFB.class:81
+msgid "800 x 600 @ 64k"
+msgstr ""
+
+#: frmChooseFB.class:81
+msgid "1024 x 768 @ 64k"
+msgstr ""
+
+#: frmChooseFB.class:86 frmChooseMBR.class:47
msgid "Next >"
msgstr ""
-#: frmChooseMBR.class:51
+#: frmChooseMBR.class:52
msgid "< Back"
msgstr ""
-#: frmChooseMBR.class:56
+#: frmChooseMBR.class:57
msgid "Please select the drive you want your boot manager installed to:"
msgstr ""
Modified: trunk/.project
==============================================================================
--- trunk/.project (original)
+++ trunk/.project Mon Aug 13 13:17:02 2007
@@ -2,7 +2,7 @@
Title=VL-gui-installer
Startup=Main
Icon=vl_logo_icon2.png
-Version=0.0.193
+Version=0.0.197
Library=gb.qt
Library=gb.qt.ext
TabSize=3
Modified: trunk/Functions.module
==============================================================================
--- trunk/Functions.module (original)
+++ trunk/Functions.module Mon Aug 13 13:17:02 2007
@@ -343,7 +343,8 @@
IF NOT sRoot_Part OR sRoot_Part <> "" THEN
SHELL "mount | awk '{if ($3 == \"/\") {print $1}}'" TO sRoot_Part
END IF
- message.Info("I've identified your root partition as " & gb.newline & sRoot_Part)
+ 'message.Info("I've identified your root partition as " & gb.newline & sRoot_Part)
+ Global.RootPart = sRoot_Part ' Store the location of the root partition to the global module
END IF
' Figure out where the kernel is
IF Exist(Boot_DIR & "/vmlinuz") THEN
@@ -354,7 +355,8 @@
Message.Info("I can't find a kernel !!! ")
END IF
IF sKernel_Loc OR sKernel_Loc <> "" THEN
- message.Info("I've located the kernel in " & gb.NewLine & sKernel_Loc)
+ 'message.Info("I've located the kernel in " & gb.NewLine & sKernel_Loc)
+ Global.KernelLoc = sKernel_Loc ' Store the location of the kernel to the global module
END IF
END
Modified: trunk/Global.class
==============================================================================
--- trunk/Global.class (original)
+++ trunk/Global.class Mon Aug 13 13:17:02 2007
@@ -65,8 +65,11 @@
'temp stuff 2 check out:
STATIC PUBLIC installDrive AS String
-' MBR Selection (When more than one is available)
-STATIC PUBLIC MBRSel AS String
+' Boot Manager variables
+STATIC PUBLIC MBRSel AS String ' MBR to use in case there is more than 1
+STATIC PUBLIC RootPart AS String ' Root Partition
+STATIC PUBLIC KernelLoc AS String ' Kernel location in root partition
+STATIC PUBLIC CONSOLENUM AS String ' The boot fb console #
Added: trunk/frmChooseFB.class
==============================================================================
--- (empty file)
+++ trunk/frmChooseFB.class Mon Aug 13 13:17:02 2007
@@ -0,0 +1,59 @@
+' Gambas class file
+
+
+PUBLIC SUB btNext_Click()
+DIM sel AS String
+sel = Trim(fblist.text)
+
+IF InStr(sel, "Standard") THEN
+global.CONSOLENUM = "normal"
+ELSE IF InStr(sel, "Bootsplash - high") THEN
+global.CONSOLENUM = "791"
+' Need to add more code to take care of the splash
+'SPLASH = "plash=silent"
+'RAMDISK="/boot/initrd"
+ELSE IF InStr(sel, "Bootsplash - med") THEN
+Global.CONSOLENUM = "788"
+'SPLASH = "splash=silent"
+'RAMDISK = "/boot/initrd"
+ELSE IF InStr(sel, "Bootsplash - low") THEN
+Global.CONSOLENUM = "785"
+'SPLASH="splash=silent"
+'RAMDISK="/boot/initrd"
+ELSE IF InStr(sel, "640 x 480 @ 256") THEN
+Global.CONSOLENUM = "769"
+ELSE IF InStr(sel, "800 x 600 @ 256") THEN
+Global.CONSOLENUM = "771"
+ELSE IF InStr(sel, "1024 x 768 @ 256") THEN
+Global.CONSOLENUM = "773"
+ELSE IF InStr(sel, "640 x 480 @ 32k") THEN
+Global.CONSOLENUM = "784"
+ELSE IF InStr(sel, "800 x 600 @ 32k") THEN
+Global.CONSOLENUM = "787"
+ELSE IF InStr(sel, "1024 x 768 @ 32k") THEN
+Global.CONSOLENUM = "790"
+ELSE IF InStr(sel, "640 x 480 @ 64k") THEN
+Global.CONSOLENUM = "785"
+ELSE IF InStr(sel, "800 x 600 @ 64k") THEN
+Global.CONSOLENUM = "788"
+ELSE IF InStr(sel, "1024 x 768 @ 64k") THEN
+Global.CONSOLENUM = "791"
+ELSE
+message.Error("Please select from the list!")
+END IF
+'message.Info(Trim(fblist.text))
+'message.Info(Global.CONSOLENUM)
+Message.Info("Found your root partition : " & global.RootPart & gb.newline &
+"Found your kernel in : " & global.KernelLoc & gb.newline &
+"Video mode to use for boot: " & global.CONSOLENUM & gb.NewLine &
+"Installing Boot manager to : " & global.MBRSel)
+ME.Close
+
+
+END
+
+PUBLIC SUB btCancel_Click()
+
+ME.close
+
+END
Added: trunk/frmChooseFB.form
==============================================================================
--- (empty file)
+++ trunk/frmChooseFB.form Mon Aug 13 13:17:02 2007
@@ -0,0 +1,22 @@
+# Gambas Form File 2.0
+
+{ Form Form
+ MoveScaled(0,0,64,50)
+ Text = ("")
+ { lbSelfbinfo TextLabel
+ MoveScaled(1,1,62,6)
+ Text = ("Please Select Boot Mode:")
+ }
+ { FBList ListBox
+ MoveScaled(2,10,62,34)
+ List = [("Standard [ The standard Linux Console ]"), ("Bootsplash - high [ 1024x768 image ]"), ("Bootsplash - med [ 800x600 image ]"), ("Bootsplash - low [ 640x480 image ]"), ("640 x 480 @ 256"), ("800 x 600 @ 256"), ("1024 x 768 @ 256"), ("640 x 480 @ 32k"), ("800 x 600 @ 32k"), ("1024 x 768 @ 32k"), ("640 x 480 @ 64k"), ("800 x 600 @ 64k"), ("1024 x 768 @ 64k")]
+ }
+ { btNext Button
+ MoveScaled(54,46,8,3)
+ Text = ("Next >")
+ }
+ { btCancel Button
+ MoveScaled(45,46,8,3)
+ Text = ("Cancel")
+ }
+}
Modified: trunk/frmChooseMBR.class
==============================================================================
--- trunk/frmChooseMBR.class (original)
+++ trunk/frmChooseMBR.class Mon Aug 13 13:17:02 2007
@@ -4,7 +4,8 @@
PUBLIC SUB btNext_Click()
global.MBRSel = Trim(MBRList.text)
-Message.Info(global.MBRSel) ' Just a sanity check to make sure the right value is parsed
+'Message.Info(global.MBRSel) ' Just a sanity check to make sure the right value is parsed
+frmChooseFB.show
ME.Close
' May need to add more code here... to tell it where to go next
|
|
From: <cod...@go...> - 2007-08-13 15:37:09
|
Author: M0E.lnx
Date: Mon Aug 13 08:35:59 2007
New Revision: 20
Modified:
trunk/.lang/.pot
trunk/.lang/frmTools.pot
trunk/.project
trunk/Functions.module
trunk/frmChooseMBR.form
trunk/frmTools.class
Log:
The Boot manager setup now detects the different drives and can find the kernel, as well as the root partitions.
It will show a list of available disks. So far only gathers information but this information will be useful when writing the actual config file for the boot manager
Modified: trunk/.lang/.pot
==============================================================================
--- trunk/.lang/.pot (original)
+++ trunk/.lang/.pot Mon Aug 13 08:35:59 2007
@@ -67,19 +67,16 @@
msgid "Advanced"
msgstr ""
-#: frmChooseMBR.class:45
+#: frmChooseMBR.class:46
msgid "Next >"
msgstr ""
-#: frmChooseMBR.class:50
+#: frmChooseMBR.class:51
msgid "< Back"
msgstr ""
-#: frmChooseMBR.class:55
-msgid ""
-"You chose to install the boot manager to your MBR, but you have\n"
-"multiple disks. Please select the disk you would like to install the "
-"bootmanager in to."
+#: frmChooseMBR.class:56
+msgid "Please select the drive you want your boot manager installed to:"
msgstr ""
#: frmConfig.class:116
@@ -384,7 +381,7 @@
msgid "No partitioning"
msgstr ""
-#: frmTools.class:115
+#: frmTools.class:116
msgid ""
"<center><h3><b>Vector Linux repair tools:</b></h3></center>\n"
"\n"
@@ -409,43 +406,43 @@
"</ul>\n"
msgstr ""
-#: frmTools.class:126
+#: frmTools.class:127
msgid "VL Tools"
msgstr ""
-#: frmTools.class:141
+#: frmTools.class:142
msgid "Distro repair"
msgstr ""
-#: frmTools.class:148
+#: frmTools.class:149
msgid "Restore packages"
msgstr ""
-#: frmTools.class:156
+#: frmTools.class:157
msgid "Repair LILO"
msgstr ""
-#: frmTools.class:163
+#: frmTools.class:164
msgid "Backup / restore"
msgstr ""
-#: frmTools.class:170
+#: frmTools.class:171
msgid "Backup /home"
msgstr ""
-#: frmTools.class:178
+#: frmTools.class:179
msgid "Restore /home"
msgstr ""
-#: frmTools.class:185
+#: frmTools.class:186
msgid "Miscellaneous"
msgstr ""
-#: frmTools.class:192
+#: frmTools.class:193
msgid "Tool 5"
msgstr ""
-#: frmTools.class:200
+#: frmTools.class:201
msgid "(Make FHS tree)"
msgstr ""
Modified: trunk/.lang/frmTools.pot
==============================================================================
--- trunk/.lang/frmTools.pot (original)
+++ trunk/.lang/frmTools.pot Mon Aug 13 08:35:59 2007
@@ -14,47 +14,47 @@
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
-#: frmTools.class:115
+#: frmTools.class:116
msgid "<center><h3><b>Vector Linux repair tools:</b></h3></center>\n\n<b><u>Distro repair tools:</u></b>\n<ul>\n<li><b>Repair LILO:</b> Repair <b>Linux Loader</b> boot manager of an existing Vector Linux installation.</li>\n<li><b>Restore packages:</b> Restore original packages from the install CD, to fix a broken upgrade.</li>\n</ul>\n<b><u>Backup / restore tools:</u></b>\n<ul>\n<li><b>Backup /home:</b> Backup your /home directory for safekeeping.</li>\n<li><b>Restore /home:</b> Restore your /home directory from a previous backup. <font color=\"#FF0000\">WARNING: The existing /home directory will be OVERWRITTEN during restore. You have been WARNED.</font></li>\n</ul>\n<b><u>Miscellaneous tools:</u></b> \n<ul>\n<li><b>Tool 5:</b> Tool number 5 to fix something or other.</li>\n<li><b>Tool 6:</b> Tool number 6 to fix something or other.</li>\n</ul>\n"
msgstr ""
-#: frmTools.class:126
+#: frmTools.class:127
msgid "VL Tools"
msgstr ""
-#: frmTools.class:141
+#: frmTools.class:142
msgid "Distro repair"
msgstr ""
-#: frmTools.class:148
+#: frmTools.class:149
msgid "Restore packages"
msgstr ""
-#: frmTools.class:156
+#: frmTools.class:157
msgid "Repair LILO"
msgstr ""
-#: frmTools.class:163
+#: frmTools.class:164
msgid "Backup / restore"
msgstr ""
-#: frmTools.class:170
+#: frmTools.class:171
msgid "Backup /home"
msgstr ""
-#: frmTools.class:178
+#: frmTools.class:179
msgid "Restore /home"
msgstr ""
-#: frmTools.class:185
+#: frmTools.class:186
msgid "Miscellaneous"
msgstr ""
-#: frmTools.class:192
+#: frmTools.class:193
msgid "Tool 5"
msgstr ""
-#: frmTools.class:200
+#: frmTools.class:201
msgid "(Make FHS tree)"
msgstr ""
Modified: trunk/.project
==============================================================================
--- trunk/.project (original)
+++ trunk/.project Mon Aug 13 08:35:59 2007
@@ -2,7 +2,7 @@
Title=VL-gui-installer
Startup=Main
Icon=vl_logo_icon2.png
-Version=0.0.178
+Version=0.0.193
Library=gb.qt
Library=gb.qt.ext
TabSize=3
Modified: trunk/Functions.module
==============================================================================
--- trunk/Functions.module (original)
+++ trunk/Functions.module Mon Aug 13 08:35:59 2007
@@ -324,72 +324,77 @@
END
-' PUBLIC SUB BootMngrSet()
-' ' This must determine:
-' ' * Where the root partition is
-' ' * Where the kernel is installed
-' ' * where to install lilo (from global.enumLILOMODE ?? )
-' ' * Which OS's to display in the boot menu (From user input)
-' ' * To use bootsplash or to use framebuffer
-' ' We'll use message.info to display the values for now, we can move those values somewhere else, or dome something more useful with them later
-' DIM sRoot_Part AS String
-' DIM sKernel_Loc AS String
-' DIM ROOT_DIR AS String = "/"
-' DIM Boot_DIR AS String = Root_DIR & "boot"
-' ' Locate the root Partition
-' IF global.enumLILOMODE = 0 THEN
-' locate_mbr()
-' SHELL "cat /etc/fstab | awk '{if ($2 == \"/\") {print $1}}'" TO sRoot_Part
-' IF NOT sRoot_Part OR sRoot_Part <> "" THEN
-' SHELL "mount | awk '{if ($3 == \"/\") {print $1}}'" TO sRoot_Part
-' END IF
-' message.Info("I've identified your root partition as " & gb.newline & sRoot_Part)
-' END IF
-' ' Figure out where the kernel is
-' IF Exist(Boot_DIR & "/vmlinuz") THEN
-' sKernel_Loc = Boot_DIR & "/vmlinuz"
-' ELSE IF Exist(ROOT_DIR & "/vmlinuz") THEN
-' sKernel_Loc = Root_DIR & "/vmlinuz"
-' ELSE
-' Message.Info("I can't find a kernel !!! ")
-' END IF
-' IF sKernel_Loc OR sKernel_Loc <> "" THEN
-' message.Info("I've located the kernel in " & gb.NewLine & sKernel_Loc)
-' END IF
-'
-' END
+PUBLIC SUB BootMngrSet()
+' This must determine:
+' * Where the root partition is
+' * Where the kernel is installed
+' * where to install lilo (from global.enumLILOMODE ?? )
+' * Which OS's to display in the boot menu (From user input)
+' * To use bootsplash or to use framebuffer
+' We'll use message.info to display the values for now, we can move those values somewhere else, or dome something more useful with them later
+ DIM sRoot_Part AS String
+ DIM sKernel_Loc AS String
+ DIM ROOT_DIR AS String = "/"
+ DIM Boot_DIR AS String = Root_DIR & "boot"
+ ' Locate the root Partition
+ IF global.enumLILOMODE = 0 THEN
+ locate_mbr()
+ SHELL "cat /etc/fstab | awk '{if ($2 == \"/\") {print $1}}'" TO sRoot_Part
+ IF NOT sRoot_Part OR sRoot_Part <> "" THEN
+ SHELL "mount | awk '{if ($3 == \"/\") {print $1}}'" TO sRoot_Part
+ END IF
+ message.Info("I've identified your root partition as " & gb.newline & sRoot_Part)
+ END IF
+' Figure out where the kernel is
+ IF Exist(Boot_DIR & "/vmlinuz") THEN
+ sKernel_Loc = Boot_DIR & "/vmlinuz"
+ ELSE IF Exist(ROOT_DIR & "/vmlinuz") THEN
+ sKernel_Loc = Root_DIR & "/vmlinuz"
+ ELSE
+ Message.Info("I can't find a kernel !!! ")
+ END IF
+ IF sKernel_Loc OR sKernel_Loc <> "" THEN
+ message.Info("I've located the kernel in " & gb.NewLine & sKernel_Loc)
+ END IF
+
+END
+
+PUBLIC SUB locate_mbr()
+
+ ' If the user chooses to install bootmanager to MBR
+ ' This routine will analyze whether there are more than 1 MBR available
+ ' and which one to use if true, else, use the one available automatically
+ 'SHELL "/sbin/vliloconf"
+
+DIM disks AS String ' list of the mbrs as string
+DIM MBRs AS String[] ' split the many MBR's
+DIM MBR AS String ' Hold a temporary MBR
+DIM MBRTotal AS Integer ' Total MBRS
+DIM MBRIndex AS Integer ' Current MBR (index)
+DIM UseMBR AS String ' MBR to use.... A better place for this is probabbly somewhere in Global
+DIM findcmd AS String = "fdisk -l | grep Disk | cut -d \" \" -f 2 | cut -c 1-8"
'
-' PUBLIC SUB locate_mbr()
-'
-' ' If the user chooses to install bootmanager to MBR
-' ' This routine will analyze whether there are more than 1 MBR available
-' ' and which one to use if true, else, use the one available automatically
-' SHELL "/sbin/vliloconf"
-'
-' ' DIM disks AS String ' list of the mbrs as string
-' ' DIM MBRs AS String[] ' split the many MBR's
-' ' DIM MBR AS String ' Hold a temporary MBR
-' ' DIM MBRTotal AS Integer ' Total MBRS
-' ' DIM MBRIndex AS Integer ' Current MBR (index)
-' ' DIM UseMBR AS String ' MBR to use.... A better place for this is probabbly somewhere in Global
-' '
-' ' SHELL "fdisk -l | grep Disk | cut -d " & " " & "-f 2 | cut -c 1-8" TO disks
-' ' MBRs = Split(disks, " ") ' Maybe use a blank space (ie " " ) instead ??
-' ' MbrTotal = MBRs.Count
-' ' IF MBRTotal = 0 THEN ' This should never happen.
-' ' message.Info(disks)
-' ' message.Error("Cannot find an MBR on this box... You must be on some kind of alien box... ;) ")
-' ' ELSE IF MBRTotal = 1 ' Located only one MBR
-' ' UseMBR = disks ' Obviously, use the one available MBR
-' ' Message.Info("The boot manager will be installed to: " & disks)
-' ' ELSE IF MBRTotal >= 2 THEN ' We found several MBR's here... Your box is loaded with drives out the whazoo!
-' ' FOR MBRIndex = 0 TO MBRs.count - 1
-' ' MBR = MBRs[MBRIndex]
-' ' frmChooseMBR.MbrList.Add(MBR) ' populate the list in the form
-' ' frmChooseMBR.Show ' This form will shoot out a value to Global
-' ' NEXT
-' ' END IF
-'
-'END
+'SHELL "fdisk -l | grep Disk | cut -d " " - f 2 | cut -c 1-8" TO disks
+SHELL findcmd TO disks
+'message.Info(disks)
+MBRs = Split(disks, " ") ' Maybe use a blank space (ie " " ) instead ??
+MbrTotal = MBRs.Count
+IF MBRTotal = 0 THEN ' This should never happen.
+'message.Info(disks)
+ message.Error("Cannot find an MBR on this box... You must be on some kind of alien box... ;) ")
+'ELSE IF MBRTotal = 1 ' Located only one MBR
+' UseMBR = disks ' Obviously, use the one available MBR
+' Message.Info("The boot manager will be installed to: " & disks)
+'ELSE IF MBRTotal >= 2 THEN ' We found several MBR's here... Your box is loaded with drives out the whazoo!
+ELSE
+'message.Info(disks)
+FOR MBRIndex = 0 TO MBRs.count - 1
+ MBR = MBRs[MBRIndex]
+ frmChooseMBR.MbrList.Add(MBR) ' populate the list in the form
+ frmChooseMBR.Show ' This form will shoot out a value to Global
+NEXT
+END IF
+
+END
Modified: trunk/frmChooseMBR.form
==============================================================================
--- trunk/frmChooseMBR.form (original)
+++ trunk/frmChooseMBR.form Mon Aug 13 08:35:59 2007
@@ -5,7 +5,8 @@
Font = Font["Luxi Mono"]
Text = ("")
{ MbrList ListBox
- MoveScaled(1,14,62,23)
+ MoveScaled(1,10,62,27)
+ Font = Font["Luxi Mono"]
}
{ btNext Button
MoveScaled(53,38,9,3)
@@ -16,7 +17,7 @@
Text = ("< Back")
}
{ lbWarn TextLabel
- MoveScaled(1,1,62,12)
- Text = ("You chose to install the boot manager to your MBR, but you have\nmultiple disks. Please select the disk you would like to install the bootmanager in to.")
+ MoveScaled(1,1,62,8)
+ Text = ("Please select the drive you want your boot manager installed to:")
}
}
Modified: trunk/frmTools.class
==============================================================================
--- trunk/frmTools.class (original)
+++ trunk/frmTools.class Mon Aug 13 08:35:59 2007
@@ -24,10 +24,9 @@
END
PUBLIC SUB btnBMRepair_Click() ' Repair LILO:
-'frmMain.btnChoice_Click
-'frmMain.btnConfigure_click ' Display the Boot Manager selection window
+frmMain.btnChoice_Click
+frmMain.btnConfigure_click ' Display the Boot Manager selection window
' Save us some time and use the existing code via Xdialog ???
-SHELL "/sbin/vliloconf"
' Might need to just make it appear in the right place
|
|
From: Jose J. R. <jo...@gm...> - 2007-08-11 03:59:27
|
On 8/10/07, M0E Lnx <m0...@gm...> wrote: > Unless there was a way to somehow embed this into the form like the > gparted window. * cough* Joe1962 *cough* > I'll try and check that out next week (after an important new customer demo we'll be doing). Or you can easily figure out how I did it for cfdisk and gparted in the installer code... ;) Regards, Joe1962 |
|
From: M0E L. <m0...@gm...> - 2007-08-11 00:40:21
|
I agree... And that would also give it a consistant look.. I'll see what I can do to write a gambas based equivalent... all it takes to fire up the existing tool is a line of code anyway ;) On 8/10/07, Jose J. Rodriguez <jo...@gm...> wrote: > On 8/10/07, Eug=E9ne Suter <ea...@gm...> wrote: > > That would be indeed a time saver...however, maybe the installer code s= hould > > be as much "pure" gambas as possible. > > I support the pure Gambas ideal as far as possible. > > > But I don't want to trample on your idea either! > > Maybe vliloconf can be used initially until the installer can actually > > install something, at which point more attention can be dedicated to ge= tting > > everything "Gambas'ized" ;) > > This is pretty much what I was going to reply to M0E's post, but you > got ahead of me. Let's use what we have for a first "draft", then work > from there. > > Regards, > Joe1962 > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > Vectorlinux-devel mailing list > Vec...@li... > https://lists.sourceforge.net/lists/listinfo/vectorlinux-devel > |
|
From: Jose J. R. <jo...@gm...> - 2007-08-10 22:34:08
|
On 8/10/07, Eug=E9ne Suter <ea...@gm...> wrote: > That would be indeed a time saver...however, maybe the installer code sho= uld > be as much "pure" gambas as possible. I support the pure Gambas ideal as far as possible. > But I don't want to trample on your idea either! > Maybe vliloconf can be used initially until the installer can actually > install something, at which point more attention can be dedicated to gett= ing > everything "Gambas'ized" ;) This is pretty much what I was going to reply to M0E's post, but you got ahead of me. Let's use what we have for a first "draft", then work from there. Regards, Joe1962 |
|
From: <ea...@gm...> - 2007-08-10 21:05:57
|
That would be indeed a time saver...however, maybe the installer code shoul= d be as much "pure" gambas as possible. But I don't want to trample on your idea either! Maybe vliloconf can be used initially until the installer can actually install something, at which point more attention can be dedicated to gettin= g everything "Gambas'ized" ;) Eug=E9ne |
|
From: M0E L. <m0...@gm...> - 2007-08-10 20:56:25
|
I decided to go back and try a different approach to the boot manager setup process. This time using the existing tools already in the system. We have vliloconf which pretty much already does everything we need it to do.. * Lets the user chose between LILO or GRUB * Sets up the bootsplash, append, Os's and all that other good stuff.. * Uses Xdialog when available. To make this work, we would need to call it straight from frmTools, and rename the "Repair LILO" button to something like "Setup Boot Manager" or something... This also means that we would not need to show the frmConfig window. The only downside I see to this is that it will not be themed like the rest of the installer... Unless there was a way to somehow embed this into the form like the gparted window. * cough* Joe1962 *cough* Other than that, I think this could be a good approach, it works for sure, and it would save us the time it would take to write the whole thing over... But again, I'd like to get input... What does every1 think ?? On 8/9/07, M0E Lnx <m0...@gm...> wrote: > After speaking to uel on IRC, I think I got enough info to start it... > Let's see how this goes... > > Looks like we'll have 2 options here > > The current installer can do Xdialog... > Now, I'm not sure which would be best, to call the current script and > let it do it's xdialog thing, or to re-master the entire thing in > gambas.. > > I'm open for suggestions. > > On 8/9/07, Jose J. Rodriguez <jo...@gm...> wrote: > > On 8/9/07, M0E Lnx <m0...@gm...> wrote: > > > I am not familiar with the code to the existing text-mode installer, > > > and being the n00b that I am in gambas, I'm trying to work on the > > > tools -> Repair Lilo option on the installer. > > > > > > > Good starting point... :) > > > > > > > > I'd like to know what this needs to do. > > > Will we offer options for both, LILO and GRUB? or just LILO? > > > If we offer both, maybe change the button the read somethng like > > > "Setup boot manager" and then make the user choose between lilo or > > > grub. > > > > > > > Agreed, there was no grub support on VL back when we started this... ;) > > > > > > > > After the user makes the selection... > > > How is the the configuration going to be done? > > > Are the shell commands like "lilo" and "grubconfig" available on the > > > temporary system ? > > > is there a plan already in place for the algorithm??? > > > > > > Please fill me in here. > > > > > > > No idea, this was just part of the wishlist... :( > > > > Regards, > > Joe1962 > > > > ------------------------------------------------------------------------- > > This SF.net email is sponsored by: Splunk Inc. > > Still grepping through log files to find problems? Stop. > > Now Search log events and configuration files using AJAX and a browser. > > Download your FREE copy of Splunk now >> http://get.splunk.com/ > > _______________________________________________ > > Vectorlinux-devel mailing list > > Vec...@li... > > https://lists.sourceforge.net/lists/listinfo/vectorlinux-devel > > > |
|
From: <cod...@go...> - 2007-08-10 20:46:58
|
Author: M0E.lnx
Date: Fri Aug 10 13:46:09 2007
New Revision: 19
Added:
trunk/frmChooseMBR.class
trunk/frmChooseMBR.form
Modified:
trunk/.lang/.pot
trunk/.lang/frmTools.pot
trunk/.project
trunk/Functions.module
trunk/Global.class
trunk/frmTools.class
Log:
Modified the previous code on the boot manager setup. Now, it calls the existing script that uses Xdialog to setup the boot manager. It allows the user to choose, and to setup whatever the choice is... I think it saves us a lot of time and effort.
Modified: trunk/.lang/.pot
==============================================================================
--- trunk/.lang/.pot (original)
+++ trunk/.lang/.pot Fri Aug 10 13:46:09 2007
@@ -67,6 +67,21 @@
msgid "Advanced"
msgstr ""
+#: frmChooseMBR.class:45
+msgid "Next >"
+msgstr ""
+
+#: frmChooseMBR.class:50
+msgid "< Back"
+msgstr ""
+
+#: frmChooseMBR.class:55
+msgid ""
+"You chose to install the boot manager to your MBR, but you have\n"
+"multiple disks. Please select the disk you would like to install the "
+"bootmanager in to."
+msgstr ""
+
#: frmConfig.class:116
msgid ""
"<center><h3><b>Configuration:</b></h3></center>\n"
@@ -369,7 +384,7 @@
msgid "No partitioning"
msgstr ""
-#: frmTools.class:113
+#: frmTools.class:115
msgid ""
"<center><h3><b>Vector Linux repair tools:</b></h3></center>\n"
"\n"
@@ -394,43 +409,43 @@
"</ul>\n"
msgstr ""
-#: frmTools.class:124
+#: frmTools.class:126
msgid "VL Tools"
msgstr ""
-#: frmTools.class:139
+#: frmTools.class:141
msgid "Distro repair"
msgstr ""
-#: frmTools.class:146
+#: frmTools.class:148
msgid "Restore packages"
msgstr ""
-#: frmTools.class:154
+#: frmTools.class:156
msgid "Repair LILO"
msgstr ""
-#: frmTools.class:161
+#: frmTools.class:163
msgid "Backup / restore"
msgstr ""
-#: frmTools.class:168
+#: frmTools.class:170
msgid "Backup /home"
msgstr ""
-#: frmTools.class:176
+#: frmTools.class:178
msgid "Restore /home"
msgstr ""
-#: frmTools.class:183
+#: frmTools.class:185
msgid "Miscellaneous"
msgstr ""
-#: frmTools.class:190
+#: frmTools.class:192
msgid "Tool 5"
msgstr ""
-#: frmTools.class:198
+#: frmTools.class:200
msgid "(Make FHS tree)"
msgstr ""
Modified: trunk/.lang/frmTools.pot
==============================================================================
--- trunk/.lang/frmTools.pot (original)
+++ trunk/.lang/frmTools.pot Fri Aug 10 13:46:09 2007
@@ -14,47 +14,47 @@
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
-#: frmTools.class:113
+#: frmTools.class:115
msgid "<center><h3><b>Vector Linux repair tools:</b></h3></center>\n\n<b><u>Distro repair tools:</u></b>\n<ul>\n<li><b>Repair LILO:</b> Repair <b>Linux Loader</b> boot manager of an existing Vector Linux installation.</li>\n<li><b>Restore packages:</b> Restore original packages from the install CD, to fix a broken upgrade.</li>\n</ul>\n<b><u>Backup / restore tools:</u></b>\n<ul>\n<li><b>Backup /home:</b> Backup your /home directory for safekeeping.</li>\n<li><b>Restore /home:</b> Restore your /home directory from a previous backup. <font color=\"#FF0000\">WARNING: The existing /home directory will be OVERWRITTEN during restore. You have been WARNED.</font></li>\n</ul>\n<b><u>Miscellaneous tools:</u></b> \n<ul>\n<li><b>Tool 5:</b> Tool number 5 to fix something or other.</li>\n<li><b>Tool 6:</b> Tool number 6 to fix something or other.</li>\n</ul>\n"
msgstr ""
-#: frmTools.class:124
+#: frmTools.class:126
msgid "VL Tools"
msgstr ""
-#: frmTools.class:139
+#: frmTools.class:141
msgid "Distro repair"
msgstr ""
-#: frmTools.class:146
+#: frmTools.class:148
msgid "Restore packages"
msgstr ""
-#: frmTools.class:154
+#: frmTools.class:156
msgid "Repair LILO"
msgstr ""
-#: frmTools.class:161
+#: frmTools.class:163
msgid "Backup / restore"
msgstr ""
-#: frmTools.class:168
+#: frmTools.class:170
msgid "Backup /home"
msgstr ""
-#: frmTools.class:176
+#: frmTools.class:178
msgid "Restore /home"
msgstr ""
-#: frmTools.class:183
+#: frmTools.class:185
msgid "Miscellaneous"
msgstr ""
-#: frmTools.class:190
+#: frmTools.class:192
msgid "Tool 5"
msgstr ""
-#: frmTools.class:198
+#: frmTools.class:200
msgid "(Make FHS tree)"
msgstr ""
Modified: trunk/.project
==============================================================================
--- trunk/.project (original)
+++ trunk/.project Fri Aug 10 13:46:09 2007
@@ -2,7 +2,7 @@
Title=VL-gui-installer
Startup=Main
Icon=vl_logo_icon2.png
-Version=0.0.171
+Version=0.0.178
Library=gb.qt
Library=gb.qt.ext
TabSize=3
Modified: trunk/Functions.module
==============================================================================
--- trunk/Functions.module (original)
+++ trunk/Functions.module Fri Aug 10 13:46:09 2007
@@ -324,37 +324,72 @@
END
-PUBLIC SUB BootMngrSet()
-' This must determine:
-' * Where the root partition is
-' * Where the kernel is installed
-' * where to install lilo (from global.enumLILOMODE ?? )
-' * Which OS's to display in the boot menu (From user input)
-' * To use bootsplash or to use framebuffer
-' We'll use message.info to display the values for now, we can move those values somewhere else, or dome something more useful with them later
- DIM sRoot_Part AS String
- DIM sKernel_Loc AS String
- DIM ROOT_DIR AS String = "/"
- DIM Boot_DIR AS String = Root_DIR & "boot"
- ' Locate the root Partition
- IF global.enumLILOMODE = 0 THEN
- SHELL "cat /etc/fstab | awk '{if ($2 == \"/\") {print $1}}'" TO sRoot_Part
- IF NOT sRoot_Part OR sRoot_Part <> "" THEN
- SHELL "mount | awk '{if ($3 == \"/\") {print $1}}'" TO sRoot_Part
- END IF
- message.Info("I've identified your root partition as " & gb.newline & sRoot_Part)
- END IF
-' Figure out where the kernel is
- IF Exist(Boot_DIR & "/vmlinuz") THEN
- sKernel_Loc = Boot_DIR & "/vmlinuz"
- ELSE IF Exist(ROOT_DIR & "/vmlinuz") THEN
- sKernel_Loc = Root_DIR & "/vmlinuz"
- ELSE
- Message.Info("I can't find a kernel !!! ")
- END IF
- IF sKernel_Loc OR sKernel_Loc <> "" THEN
- message.Info("I've located the kernel in " & gb.NewLine & sKernel_Loc)
- END IF
-
-END
+' PUBLIC SUB BootMngrSet()
+' ' This must determine:
+' ' * Where the root partition is
+' ' * Where the kernel is installed
+' ' * where to install lilo (from global.enumLILOMODE ?? )
+' ' * Which OS's to display in the boot menu (From user input)
+' ' * To use bootsplash or to use framebuffer
+' ' We'll use message.info to display the values for now, we can move those values somewhere else, or dome something more useful with them later
+' DIM sRoot_Part AS String
+' DIM sKernel_Loc AS String
+' DIM ROOT_DIR AS String = "/"
+' DIM Boot_DIR AS String = Root_DIR & "boot"
+' ' Locate the root Partition
+' IF global.enumLILOMODE = 0 THEN
+' locate_mbr()
+' SHELL "cat /etc/fstab | awk '{if ($2 == \"/\") {print $1}}'" TO sRoot_Part
+' IF NOT sRoot_Part OR sRoot_Part <> "" THEN
+' SHELL "mount | awk '{if ($3 == \"/\") {print $1}}'" TO sRoot_Part
+' END IF
+' message.Info("I've identified your root partition as " & gb.newline & sRoot_Part)
+' END IF
+' ' Figure out where the kernel is
+' IF Exist(Boot_DIR & "/vmlinuz") THEN
+' sKernel_Loc = Boot_DIR & "/vmlinuz"
+' ELSE IF Exist(ROOT_DIR & "/vmlinuz") THEN
+' sKernel_Loc = Root_DIR & "/vmlinuz"
+' ELSE
+' Message.Info("I can't find a kernel !!! ")
+' END IF
+' IF sKernel_Loc OR sKernel_Loc <> "" THEN
+' message.Info("I've located the kernel in " & gb.NewLine & sKernel_Loc)
+' END IF
+'
+' END
+'
+' PUBLIC SUB locate_mbr()
+'
+' ' If the user chooses to install bootmanager to MBR
+' ' This routine will analyze whether there are more than 1 MBR available
+' ' and which one to use if true, else, use the one available automatically
+' SHELL "/sbin/vliloconf"
+'
+' ' DIM disks AS String ' list of the mbrs as string
+' ' DIM MBRs AS String[] ' split the many MBR's
+' ' DIM MBR AS String ' Hold a temporary MBR
+' ' DIM MBRTotal AS Integer ' Total MBRS
+' ' DIM MBRIndex AS Integer ' Current MBR (index)
+' ' DIM UseMBR AS String ' MBR to use.... A better place for this is probabbly somewhere in Global
+' '
+' ' SHELL "fdisk -l | grep Disk | cut -d " & " " & "-f 2 | cut -c 1-8" TO disks
+' ' MBRs = Split(disks, " ") ' Maybe use a blank space (ie " " ) instead ??
+' ' MbrTotal = MBRs.Count
+' ' IF MBRTotal = 0 THEN ' This should never happen.
+' ' message.Info(disks)
+' ' message.Error("Cannot find an MBR on this box... You must be on some kind of alien box... ;) ")
+' ' ELSE IF MBRTotal = 1 ' Located only one MBR
+' ' UseMBR = disks ' Obviously, use the one available MBR
+' ' Message.Info("The boot manager will be installed to: " & disks)
+' ' ELSE IF MBRTotal >= 2 THEN ' We found several MBR's here... Your box is loaded with drives out the whazoo!
+' ' FOR MBRIndex = 0 TO MBRs.count - 1
+' ' MBR = MBRs[MBRIndex]
+' ' frmChooseMBR.MbrList.Add(MBR) ' populate the list in the form
+' ' frmChooseMBR.Show ' This form will shoot out a value to Global
+' ' NEXT
+' ' END IF
+'
+'END
+
Modified: trunk/Global.class
==============================================================================
--- trunk/Global.class (original)
+++ trunk/Global.class Fri Aug 10 13:46:09 2007
@@ -65,5 +65,8 @@
'temp stuff 2 check out:
STATIC PUBLIC installDrive AS String
+' MBR Selection (When more than one is available)
+STATIC PUBLIC MBRSel AS String
+
Added: trunk/frmChooseMBR.class
==============================================================================
--- (empty file)
+++ trunk/frmChooseMBR.class Fri Aug 10 13:46:09 2007
@@ -0,0 +1,23 @@
+' Gambas class file
+
+
+PUBLIC SUB btNext_Click()
+
+global.MBRSel = Trim(MBRList.text)
+Message.Info(global.MBRSel) ' Just a sanity check to make sure the right value is parsed
+ME.Close
+' May need to add more code here... to tell it where to go next
+
+END
+
+PUBLIC SUB btBack_Click()
+
+ME.Close
+
+END
+
+PUBLIC SUB Form_Open()
+
+ME.title = "Choose MBR"
+
+END
Added: trunk/frmChooseMBR.form
==============================================================================
--- (empty file)
+++ trunk/frmChooseMBR.form Fri Aug 10 13:46:09 2007
@@ -0,0 +1,22 @@
+# Gambas Form File 2.0
+
+{ Form Form
+ MoveScaled(0,0,64,43)
+ Font = Font["Luxi Mono"]
+ Text = ("")
+ { MbrList ListBox
+ MoveScaled(1,14,62,23)
+ }
+ { btNext Button
+ MoveScaled(53,38,9,3)
+ Text = ("Next >")
+ }
+ { btBack Button
+ MoveScaled(44,38,8,3)
+ Text = ("< Back")
+ }
+ { lbWarn TextLabel
+ MoveScaled(1,1,62,12)
+ Text = ("You chose to install the boot manager to your MBR, but you have\nmultiple disks. Please select the disk you would like to install the bootmanager in to.")
+ }
+}
Modified: trunk/frmTools.class
==============================================================================
--- trunk/frmTools.class (original)
+++ trunk/frmTools.class Fri Aug 10 13:46:09 2007
@@ -25,7 +25,11 @@
PUBLIC SUB btnBMRepair_Click() ' Repair LILO:
'frmMain.btnChoice_Click
-frmMain.btnConfigure_click ' Display the Boot Manager selection window
+'frmMain.btnConfigure_click ' Display the Boot Manager selection window
+' Save us some time and use the existing code via Xdialog ???
+SHELL "/sbin/vliloconf"
+' Might need to just make it appear in the right place
+
END
|
|
From: <cod...@go...> - 2007-08-10 14:16:05
|
Author: M0E.lnx
Date: Fri Aug 10 07:15:39 2007
New Revision: 18
Modified:
trunk/.lang/.pot
trunk/.lang/frmConfig.pot
trunk/.project
trunk/Functions.module
trunk/frmConfig.class
Log:
First lines of the boot manager setup
Modified: trunk/.lang/.pot
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D
--- trunk/.lang/.pot (original)
+++ trunk/.lang/.pot Fri Aug 10 07:15:39 2007
@@ -67,7 +67,7 @@
msgid "Advanced"
msgstr ""
=20
-#: frmConfig.class:114
+#: frmConfig.class:116
msgid ""
"<center><h3><b>Configuration:</b></h3></center>\n"
"\n"
@@ -101,39 +101,39 @@
"</ul>\n"
msgstr ""
=20
-#: frmConfig.class:125
+#: frmConfig.class:127
msgid "Additional configuration"
msgstr ""
=20
-#: frmConfig.class:140
+#: frmConfig.class:142
msgid "Boot manager"
msgstr ""
=20
-#: frmConfig.class:147
+#: frmConfig.class:149
msgid "Master Boot Record"
msgstr ""
=20
-#: frmConfig.class:155
+#: frmConfig.class:157
msgid "VL Boot Sector"
msgstr ""
=20
-#: frmConfig.class:163
+#: frmConfig.class:165
msgid "Floppy diskette"
msgstr ""
=20
-#: frmConfig.class:171
+#: frmConfig.class:173
msgid "Do not install"
msgstr ""
=20
-#: frmConfig.class:178
+#: frmConfig.class:180
msgid "Other configuration"
msgstr ""
=20
-#: frmConfig.class:185
+#: frmConfig.class:187
msgid "Config 1"
msgstr ""
=20
-#: frmConfig.class:193
+#: frmConfig.class:195
msgid "Config 2"
msgstr ""
=20
Modified: trunk/.lang/frmConfig.pot
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D
--- trunk/.lang/frmConfig.pot (original)
+++ trunk/.lang/frmConfig.pot Fri Aug 10 07:15:39 2007
@@ -14,43 +14,43 @@
"Content-Type: text/plain; charset=3DUTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
=20
-#: frmConfig.class:114
+#: frmConfig.class:116
msgid "<center><h3><b>Configuration:</b></h3></center>\n\n<b><u>Linux Loade=
r boot manager setup:</u></b>\n<ul>\n<li><b>Master Boot Record:</b> Install =
Linux Loader boot manager to the master Boot Record of the bootable hard dis=
k. This is the simplest method and the default action for most common operat=
ing systems.</li>\n<li><b>VL Boot sector:</b> Install Linux Loader boot mana=
ger to the Boot Sector of the Vector Linux install partition. This will requ=
ire the following extra steps:\n<ul>\n<li>make the Vector Linux partition bo=
otable using a partition manager.</li>\n<li>add an option to your default bo=
ot manager to boot to LiLo in this partition.</li>\n</ul>\n</li>\n<li><b>Flo=
ppy diskette:</b> Install Linux Loader boot manager to a floopy diskette in =
/dev/fd0 (drive A:). You can then boot to the Vector Linux install by simply=
booting the diskette.</li>\n<li><b>Do not install:</b> Do not install Linux=
Loader. Select this if you use another boot manager and know how to set up =
an option to boot the Vector Linux install from it.</li>\n</ul>\n\n<b><u>Oth=
er configuration:</u></b>\n<ul>\n<li><b>Config 1:</b> Other configuration se=
lection 1.</li>\n<li><b>Config 2:</b> Other configuration selection 2.</li>\=
n</ul>\n"
msgstr ""
=20
-#: frmConfig.class:125
+#: frmConfig.class:127
msgid "Additional configuration"
msgstr ""
=20
-#: frmConfig.class:140
+#: frmConfig.class:142
msgid "Boot manager"
msgstr ""
=20
-#: frmConfig.class:147
+#: frmConfig.class:149
msgid "Master Boot Record"
msgstr ""
=20
-#: frmConfig.class:155
+#: frmConfig.class:157
msgid "VL Boot Sector"
msgstr ""
=20
-#: frmConfig.class:163
+#: frmConfig.class:165
msgid "Floppy diskette"
msgstr ""
=20
-#: frmConfig.class:171
+#: frmConfig.class:173
msgid "Do not install"
msgstr ""
=20
-#: frmConfig.class:178
+#: frmConfig.class:180
msgid "Other configuration"
msgstr ""
=20
-#: frmConfig.class:185
+#: frmConfig.class:187
msgid "Config 1"
msgstr ""
=20
-#: frmConfig.class:193
+#: frmConfig.class:195
msgid "Config 2"
msgstr ""
=20
Modified: trunk/.project
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D
--- trunk/.project (original)
+++ trunk/.project Fri Aug 10 07:15:39 2007
@@ -2,9 +2,10 @@
Title=3DVL-gui-installer
Startup=3DMain
Icon=3Dvl_logo_icon2.png
-Version=3D0.0.166
+Version=3D0.0.171
Library=3Dgb.qt
Library=3Dgb.qt.ext
TabSize=3D3
Translate=3D1
ControlPublic=3D1
+ExecPath=3D/home/moe/Desktop/vl-installer.gambas
Modified: trunk/Functions.module
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D
--- trunk/Functions.module (original)
+++ trunk/Functions.module Fri Aug 10 07:15:39 2007
@@ -323,3 +323,38 @@
ENDIF =20
=20
END
+
+PUBLIC SUB BootMngrSet()
+' This must determine:
+' * Where the root partition is
+' * Where the kernel is installed
+' * where to install lilo (from global.enumLILOMODE ?? )
+' * Which OS's to display in the boot menu (From user input)
+' * To use bootsplash or to use framebuffer
+' We'll use message.info to display the values for now, we can move those v=
alues somewhere else, or dome something more useful with them later
+ DIM sRoot_Part AS String
+ DIM sKernel_Loc AS String
+ DIM ROOT_DIR AS String =3D "/"
+ DIM Boot_DIR AS String =3D Root_DIR & "boot"
+ ' Locate the root Partition
+ IF global.enumLILOMODE =3D 0 THEN=20
+ SHELL "cat /etc/fstab | awk '{if ($2 =3D=3D \"/\") {print $1}}'" TO sRoot=
_Part
+ IF NOT sRoot_Part OR sRoot_Part <> "" THEN=20
+ SHELL "mount | awk '{if ($3 =3D=3D \"/\") {print $1}}'" TO sRoot_Part
+ END IF
+ message.Info("I've identified your root partition as " & gb.newline &=
sRoot_Part)
+ END IF
+' Figure out where the kernel is
+ IF Exist(Boot_DIR & "/vmlinuz") THEN=20
+ sKernel_Loc =3D Boot_DIR & "/vmlinuz"
+ ELSE IF Exist(ROOT_DIR & "/vmlinuz") THEN=20
+ sKernel_Loc =3D Root_DIR & "/vmlinuz"
+ ELSE=20
+ Message.Info("I can't find a kernel !!! ")
+ END IF
+ IF sKernel_Loc OR sKernel_Loc <> "" THEN=20
+ message.Info("I've located the kernel in " & gb.NewLine & sKernel_Loc)
+ END IF
+ =20
+END
+
Modified: trunk/frmConfig.class
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D
--- trunk/frmConfig.class (original)
+++ trunk/frmConfig.class Fri Aug 10 07:15:39 2007
@@ -25,18 +25,20 @@
PUBLIC SUB btnMBR_Click() 'Master Boot Record:
=20
Global.enumLILOMODE =3D 0
+Functions.BootMngrSet
=20
END
=20
PUBLIC SUB btnBootSec_Click() 'VL Boot Sector:
=20
Global.enumLILOMODE =3D 1
-
+Functions.BootMngrSet
END
=20
PUBLIC SUB btnFloppy_Click() 'Floppy diskette:
=20
Global.enumLILOMODE =3D 2
+functions.BootMngrSet
=20
END
=20
|
|
From: <cod...@go...> - 2007-08-09 22:43:41
|
Author: easuter
Date: Thu Aug 9 15:42:31 2007
New Revision: 17
Modified:
trunk/.lang/.pot
trunk/.lang/frmChoice.pot
trunk/Functions.module
trunk/Main.module
trunk/frmChoice.class
Log:
- Functions.AutoRootSize now accepts a partition mode as an argument,
in order to calculate the root partition size for that mode
(auto and freespace modes, though the free-space mode still needs work)
- Functions.EnoughSpace() created to compare the theoretical root
partition size with the space the packages will ocupy (returns a boolean
value).
Modified: trunk/.lang/.pot
==============================================================================
--- trunk/.lang/.pot (original)
+++ trunk/.lang/.pot Thu Aug 9 15:42:31 2007
@@ -26,7 +26,7 @@
msgid "Cancel"
msgstr ""
-#: frmChoice.class:95
+#: frmChoice.class:94
msgid ""
"<center><h3><b>You have 3 choices:</b></h3></center>\n"
"\n"
@@ -47,23 +47,23 @@
"</ul>\n"
msgstr ""
-#: frmChoice.class:106
+#: frmChoice.class:105
msgid "Choose install type"
msgstr ""
-#: frmChoice.class:121
+#: frmChoice.class:120
msgid "Install types"
msgstr ""
-#: frmChoice.class:126
+#: frmChoice.class:125
msgid "Full-automatic"
msgstr ""
-#: frmChoice.class:132
+#: frmChoice.class:131
msgid "Semi-automatic"
msgstr ""
-#: frmChoice.class:138
+#: frmChoice.class:137
msgid "Advanced"
msgstr ""
Modified: trunk/.lang/frmChoice.pot
==============================================================================
--- trunk/.lang/frmChoice.pot (original)
+++ trunk/.lang/frmChoice.pot Thu Aug 9 15:42:31 2007
@@ -14,27 +14,27 @@
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
-#: frmChoice.class:95
+#: frmChoice.class:94
msgid "<center><h3><b>You have 3 choices:</b></h3></center>\n\n<ul>\n<li><b><u>Full-automatic install:</u></b> Our easiest install yet; choose this option if you want to use your entire hard disk for VL. Your system will be automatically set up, partitions and all. <font color=\"#FF0000\">WARNING: this option will DELETE everything on your hard disk, or offer a choice if there are multiple disks.</font> There will of course be a confirmation dialog in case you selected this option by mistake.</li>\n<li><b><u>Semi-automatic install:</u></b> With this option, you manually partition your drives with gparted, but the rest of the setup will be pretty automatic.</li>\n<li><b><u>Advanced install:</u></b> For the technically savvy user that must do everything by hand. You can control most aspects of the install. However, there will be assisted options available all the way through, so this is a very flexible install.</li>\n</ul>\n"
msgstr ""
-#: frmChoice.class:106
+#: frmChoice.class:105
msgid "Choose install type"
msgstr ""
-#: frmChoice.class:121
+#: frmChoice.class:120
msgid "Install types"
msgstr ""
-#: frmChoice.class:126
+#: frmChoice.class:125
msgid "Full-automatic"
msgstr ""
-#: frmChoice.class:132
+#: frmChoice.class:131
msgid "Semi-automatic"
msgstr ""
-#: frmChoice.class:138
+#: frmChoice.class:137
msgid "Advanced"
msgstr ""
Modified: trunk/Functions.module
==============================================================================
--- trunk/Functions.module (original)
+++ trunk/Functions.module Thu Aug 9 15:42:31 2007
@@ -222,8 +222,8 @@
RETURN sysmem * 2.5
ELSE IF sysmem < 268435456 AND sysmem > 134217728 THEN
RETURN sysmem * 2
-ELSE
- RETURN 536870912 'Don't return swap partition sizes above 512MB
+ELSE 'Don't return swap partition sizes above 512MB
+ RETURN 536870912
ENDIF
END
@@ -271,26 +271,55 @@
END
-PUBLIC FUNCTION AutoRootSize() AS Long
-'Calculate the size of the theoretical root partition
+PUBLIC FUNCTION AutoRootSize(partmode AS Integer) AS Long
+'Calculate the size of the theoretical root partition, for the automatic or free-space partitioning modes
DIM iRootSize AS Long
DIM iTotalSize AS Long
DIM sTemp AS String
-Utils.GetSysMemory
-iTotalSize = 0
-
-IF Global.SimulationMode = TRUE THEN
- sTemp = "38000000"
-ELSE
- SHELL "fdisk -s " & Global.installDrive TO sTemp
+IF Global.enumPARTMODE = 0 THEN 'Use entire drive
+ IF Global.SimulationMode = TRUE THEN
+ sTemp = "3800000"
+ ELSE 'Get real value from fdisk
+ SHELL "fdisk -s " & Global.installDrive TO sTemp
+ ENDIF
+
+ iTotalSize = CLng(Val(Trim$(sTemp))) * 1024 'Convert to long integer and turn value into bytes
+ iRootSize = iTotalSize - CalcSwap(Global.SysMemory)
+
+ELSE IF Global.enumPARTMODE = 1 'Use only free space
+ IF Global.SimulationMode = TRUE THEN
+ sTemp = "3800000"
+ ELSE
+ 'Do whatever needs to be done to get free space values from available partitions
+ ENDIF
+ELSE
+ Message.Error("Unacceptable partition mode (" & Global.enumPARTMODE & ") for AutoRootSize function.")
ENDIF
-iTotalSize = Val(sTemp)
-iTotalSize = iTotalSize * 1024 'Convert to bytes
-
-'Return the size to be used for the root partition, in bytes, with a "safety margin" of 150MB
-iRootSize = iTotalSize - CalcSwap(Global.SysMemory) - 157286400
RETURN iRootSize
+END
+
+PUBLIC FUNCTION EnoughSpace() AS Boolean
+'Check whether the space destined to the package installation is enough (with a 150MB "safety" margin)
+DIM iAvailableSpace AS Long
+
+IF Global.enumPARTMODE = 0 THEN
+ iAvailableSpace = AutoRootSize - CalcSwap(Global.SysMemory) - 157286400
+ IF iAvailableSpace > CalcPaksSize("all") THEN
+ RETURN TRUE
+ ELSE
+ RETURN FALSE
+ ENDIF
+'Do the same for other partition modes
+ELSE IF Global.enumPARTMODE = 1 THEN
+ELSE IF Global.enumPARTMODE = 2 THEN
+ELSE IF Global.enumPARTMODE = 3 THEN
+ELSE IF Global.enumPARTMODE = 4 THEN
+ELSE IF Global.enumPARTMODE = 5 THEN
+ELSE
+ Message.Error("Invalid partition mode: " & Global.enumPARTMODE)
+ENDIF
+
END
Modified: trunk/Main.module
==============================================================================
--- trunk/Main.module (original)
+++ trunk/Main.module Thu Aug 9 15:42:31 2007
@@ -16,6 +16,9 @@
Global.SimulationMode = FALSE
ENDIF
+'Get some basic system info processed:
+Utils.GetSysMemory
+
' Initially no buttons being executed:
Global.flagBUTTExec = FALSE
Modified: trunk/frmChoice.class
==============================================================================
--- trunk/frmChoice.class (original)
+++ trunk/frmChoice.class Thu Aug 9 15:42:31 2007
@@ -25,6 +25,9 @@
PUBLIC SUB btnFullAuto_Click() ' Full-automatic.
Global.enumINSTMODE = 0 ' Full-automatic install mode.
+Global.enumPARTMODE = 0 'Full-automatic partitioning
+Global.enumPACKS = 0 'All packages selected
+Global.enumLILOMODE = 0 'Install lilo to MBR
Utils.DrivePartInfo
IF Global.DiskInfo.Count >= 1 THEN frmDriveSelect.ShowModal
@@ -32,10 +35,6 @@
frmMain.btnChoice.Enabled = FALSE ' Disable Choices.
frmMain.btnGo.Enabled = TRUE ' Enable Go for it!.
frmMain.btnGo_Click ' Advance to Go for it!.
-
-'Debug
-Utils.GetSysMemory
-frmGo.TextLabel1.Text = "Swap: " & Functions.AutoUnits(Functions.CalcSwap(Global.SysMemory)) & " Root: " & Functions.AutoUnits(Functions.AutoRootSize()) & " Packages will ocupy: " & Functions.AutoUnits(Functions.CalcPaksSize("all"))
END
|
|
From: M0E L. <m0...@gm...> - 2007-08-09 20:51:22
|
After speaking to uel on IRC, I think I got enough info to start it... Let's see how this goes... Looks like we'll have 2 options here The current installer can do Xdialog... Now, I'm not sure which would be best, to call the current script and let it do it's xdialog thing, or to re-master the entire thing in gambas.. I'm open for suggestions. On 8/9/07, Jose J. Rodriguez <jo...@gm...> wrote: > On 8/9/07, M0E Lnx <m0...@gm...> wrote: > > I am not familiar with the code to the existing text-mode installer, > > and being the n00b that I am in gambas, I'm trying to work on the > > tools -> Repair Lilo option on the installer. > > > > Good starting point... :) > > > > > I'd like to know what this needs to do. > > Will we offer options for both, LILO and GRUB? or just LILO? > > If we offer both, maybe change the button the read somethng like > > "Setup boot manager" and then make the user choose between lilo or > > grub. > > > > Agreed, there was no grub support on VL back when we started this... ;) > > > > > After the user makes the selection... > > How is the the configuration going to be done? > > Are the shell commands like "lilo" and "grubconfig" available on the > > temporary system ? > > is there a plan already in place for the algorithm??? > > > > Please fill me in here. > > > > No idea, this was just part of the wishlist... :( > > Regards, > Joe1962 > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > Vectorlinux-devel mailing list > Vec...@li... > https://lists.sourceforge.net/lists/listinfo/vectorlinux-devel > |
|
From: Jose J. R. <jo...@gm...> - 2007-08-09 20:23:54
|
On 8/9/07, M0E Lnx <m0...@gm...> wrote: > I am not familiar with the code to the existing text-mode installer, > and being the n00b that I am in gambas, I'm trying to work on the > tools -> Repair Lilo option on the installer. > Good starting point... :) > > I'd like to know what this needs to do. > Will we offer options for both, LILO and GRUB? or just LILO? > If we offer both, maybe change the button the read somethng like > "Setup boot manager" and then make the user choose between lilo or > grub. > Agreed, there was no grub support on VL back when we started this... ;) > > After the user makes the selection... > How is the the configuration going to be done? > Are the shell commands like "lilo" and "grubconfig" available on the > temporary system ? > is there a plan already in place for the algorithm??? > > Please fill me in here. > No idea, this was just part of the wishlist... :( Regards, Joe1962 |
|
From: <cod...@go...> - 2007-08-09 19:32:20
|
Author: M0E.lnx Date: Thu Aug 9 12:30:48 2007 New Revision: 16 Modified: trunk/.lang/#project.pot trunk/.lang/Functions.pot trunk/.lang/Global.pot trunk/.lang/InputBox.pot trunk/.lang/Main.pot trunk/.lang/Utils.pot trunk/.lang/cDiskInfo.pot trunk/.lang/cPartInfo.pot trunk/.lang/cPartInstall.pot trunk/.lang/frmChoice.pot trunk/.lang/frmConfig.pot trunk/.lang/frmDriveSelect.pot trunk/.lang/frmGO.pot trunk/.lang/frmMain.pot trunk/.lang/frmPackages.pot trunk/.lang/frmPartSelect.pot trunk/.lang/frmPartitioner.pot trunk/.lang/frmPartitions.pot trunk/.lang/frmTools.pot trunk/.lang/frmWelcome.pot trunk/frmTools.class Log: Attempting to implement the Boot Manager setup Modified: trunk/.lang/#project.pot ============================================================================== --- trunk/.lang/#project.pot (original) +++ trunk/.lang/#project.pot Thu Aug 9 12:30:48 2007 @@ -1,4 +1,4 @@ -# /home/joe1962/develop/2-cvs/vl-gui-installer/.project +# /home/moe/projects/vl-installer/.project # Generated by Gambas compiler # FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. Modified: trunk/.lang/Functions.pot ============================================================================== --- trunk/.lang/Functions.pot (original) +++ trunk/.lang/Functions.pot Thu Aug 9 12:30:48 2007 @@ -1,4 +1,4 @@ -# /home/easuter/vinstall-ng/Functions.module +# /home/moe/projects/vl-installer/Functions.module # Generated by Gambas compiler # FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. Modified: trunk/.lang/Global.pot ============================================================================== --- trunk/.lang/Global.pot (original) +++ trunk/.lang/Global.pot Thu Aug 9 12:30:48 2007 @@ -1,4 +1,4 @@ -# /home/easuter/vinstall-ng/Global.class +# /home/moe/projects/vl-installer/Global.class # Generated by Gambas compiler # FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. Modified: trunk/.lang/InputBox.pot ============================================================================== --- trunk/.lang/InputBox.pot (original) +++ trunk/.lang/InputBox.pot Thu Aug 9 12:30:48 2007 @@ -1,4 +1,4 @@ -# /home/easuter/vinstall-ng/InputBox.class +# /home/moe/projects/vl-installer/InputBox.class # Generated by Gambas compiler # FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. Modified: trunk/.lang/Main.pot ============================================================================== --- trunk/.lang/Main.pot (original) +++ trunk/.lang/Main.pot Thu Aug 9 12:30:48 2007 @@ -1,4 +1,4 @@ -# /home/easuter/vinstall-ng/Main.module +# /home/moe/projects/vl-installer/Main.module # Generated by Gambas compiler # FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. Modified: trunk/.lang/Utils.pot ============================================================================== --- trunk/.lang/Utils.pot (original) +++ trunk/.lang/Utils.pot Thu Aug 9 12:30:48 2007 @@ -1,4 +1,4 @@ -# /home/easuter/vinstall-ng/Utils.module +# /home/moe/projects/vl-installer/Utils.module # Generated by Gambas compiler # FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. Modified: trunk/.lang/cDiskInfo.pot ============================================================================== --- trunk/.lang/cDiskInfo.pot (original) +++ trunk/.lang/cDiskInfo.pot Thu Aug 9 12:30:48 2007 @@ -1,4 +1,4 @@ -# /home/easuter/vinstall-ng/cDiskInfo.class +# /home/moe/projects/vl-installer/cDiskInfo.class # Generated by Gambas compiler # FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. Modified: trunk/.lang/cPartInfo.pot ============================================================================== --- trunk/.lang/cPartInfo.pot (original) +++ trunk/.lang/cPartInfo.pot Thu Aug 9 12:30:48 2007 @@ -1,4 +1,4 @@ -# /home/easuter/vinstall-ng/cPartInfo.class +# /home/moe/projects/vl-installer/cPartInfo.class # Generated by Gambas compiler # FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. Modified: trunk/.lang/cPartInstall.pot ============================================================================== --- trunk/.lang/cPartInstall.pot (original) +++ trunk/.lang/cPartInstall.pot Thu Aug 9 12:30:48 2007 @@ -1,4 +1,4 @@ -# /home/easuter/vinstall-ng/cPartInstall.class +# /home/moe/projects/vl-installer/cPartInstall.class # Generated by Gambas compiler # FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. Modified: trunk/.lang/frmChoice.pot ============================================================================== --- trunk/.lang/frmChoice.pot (original) +++ trunk/.lang/frmChoice.pot Thu Aug 9 12:30:48 2007 @@ -1,4 +1,4 @@ -# /home/easuter/vinstall-ng/frmChoice.class +# /home/moe/projects/vl-installer/frmChoice.class # Generated by Gambas compiler # FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. Modified: trunk/.lang/frmConfig.pot ============================================================================== --- trunk/.lang/frmConfig.pot (original) +++ trunk/.lang/frmConfig.pot Thu Aug 9 12:30:48 2007 @@ -1,4 +1,4 @@ -# /home/easuter/vinstall-ng/frmConfig.class +# /home/moe/projects/vl-installer/frmConfig.class # Generated by Gambas compiler # FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. Modified: trunk/.lang/frmDriveSelect.pot ============================================================================== --- trunk/.lang/frmDriveSelect.pot (original) +++ trunk/.lang/frmDriveSelect.pot Thu Aug 9 12:30:48 2007 @@ -1,4 +1,4 @@ -# /home/easuter/vinstall-ng/frmDriveSelect.class +# /home/moe/projects/vl-installer/frmDriveSelect.class # Generated by Gambas compiler # FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. Modified: trunk/.lang/frmGO.pot ============================================================================== --- trunk/.lang/frmGO.pot (original) +++ trunk/.lang/frmGO.pot Thu Aug 9 12:30:48 2007 @@ -1,4 +1,4 @@ -# /home/easuter/vinstall-ng/frmGO.class +# /home/moe/projects/vl-installer/frmGO.class # Generated by Gambas compiler # FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. Modified: trunk/.lang/frmMain.pot ============================================================================== --- trunk/.lang/frmMain.pot (original) +++ trunk/.lang/frmMain.pot Thu Aug 9 12:30:48 2007 @@ -1,4 +1,4 @@ -# /home/easuter/vinstall-ng/frmMain.class +# /home/moe/projects/vl-installer/frmMain.class # Generated by Gambas compiler # FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. Modified: trunk/.lang/frmPackages.pot ============================================================================== --- trunk/.lang/frmPackages.pot (original) +++ trunk/.lang/frmPackages.pot Thu Aug 9 12:30:48 2007 @@ -1,4 +1,4 @@ -# /home/easuter/vinstall-ng/frmPackages.class +# /home/moe/projects/vl-installer/frmPackages.class # Generated by Gambas compiler # FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. Modified: trunk/.lang/frmPartSelect.pot ============================================================================== --- trunk/.lang/frmPartSelect.pot (original) +++ trunk/.lang/frmPartSelect.pot Thu Aug 9 12:30:48 2007 @@ -1,4 +1,4 @@ -# /home/easuter/vinstall-ng/frmPartSelect.class +# /home/moe/projects/vl-installer/frmPartSelect.class # Generated by Gambas compiler # FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. Modified: trunk/.lang/frmPartitioner.pot ============================================================================== --- trunk/.lang/frmPartitioner.pot (original) +++ trunk/.lang/frmPartitioner.pot Thu Aug 9 12:30:48 2007 @@ -1,4 +1,4 @@ -# /home/easuter/vinstall-ng/frmPartitioner.class +# /home/moe/projects/vl-installer/frmPartitioner.class # Generated by Gambas compiler # FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. Modified: trunk/.lang/frmPartitions.pot ============================================================================== --- trunk/.lang/frmPartitions.pot (original) +++ trunk/.lang/frmPartitions.pot Thu Aug 9 12:30:48 2007 @@ -1,4 +1,4 @@ -# /home/easuter/vinstall-ng/frmPartitions.class +# /home/moe/projects/vl-installer/frmPartitions.class # Generated by Gambas compiler # FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. Modified: trunk/.lang/frmTools.pot ============================================================================== --- trunk/.lang/frmTools.pot (original) +++ trunk/.lang/frmTools.pot Thu Aug 9 12:30:48 2007 @@ -1,4 +1,4 @@ -# /home/easuter/vinstall-ng/frmTools.class +# /home/moe/projects/vl-installer/frmTools.class # Generated by Gambas compiler # FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. Modified: trunk/.lang/frmWelcome.pot ============================================================================== --- trunk/.lang/frmWelcome.pot (original) +++ trunk/.lang/frmWelcome.pot Thu Aug 9 12:30:48 2007 @@ -1,4 +1,4 @@ -# /home/easuter/vinstall-ng/frmWelcome.class +# /home/moe/projects/vl-installer/frmWelcome.class # Generated by Gambas compiler # FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. Modified: trunk/frmTools.class ============================================================================== --- trunk/frmTools.class (original) +++ trunk/frmTools.class Thu Aug 9 12:30:48 2007 @@ -24,8 +24,8 @@ END PUBLIC SUB btnBMRepair_Click() ' Repair LILO: - - +'frmMain.btnChoice_Click +frmMain.btnConfigure_click ' Display the Boot Manager selection window END |
|
From: M0E L. <m0...@gm...> - 2007-08-09 19:28:54
|
I am not familiar with the code to the existing text-mode installer, and being the n00b that I am in gambas, I'm trying to work on the tools -> Repair Lilo option on the installer. I'd like to know what this needs to do. Will we offer options for both, LILO and GRUB? or just LILO? If we offer both, maybe change the button the read somethng like "Setup boot manager" and then make the user choose between lilo or grub. After the user makes the selection... How is the the configuration going to be done? Are the shell commands like "lilo" and "grubconfig" available on the temporary system ? is there a plan already in place for the algorithm??? Please fill me in here. |
|
From: M0E L. <m0...@gm...> - 2007-08-09 18:09:25
|
The issue tracking is a good feature in deed ;) I'm still lost in the code though... haven't done anything really.. just trying to catch up and understand it. On 8/8/07, Jose J. Rodriguez <jo...@gm...> wrote: > As you have probably figured out by now, I configured the vinstall-ng > Google Code Project to use this mailing list for email notifications > of subversion commits and also for issue tracker changes. > > The Project Members uelsk8s, M0E.lnx and easuter have been "upgraded" > to Project Owners... :) > > I suggest we put the project wiki and issue tracker to good use. You > can see a small example of use at http://code.google.com/p/vcpufreq/. > > We had some older notes regarding installer algorithms, etc at: > http://wikihost.org/wikis/vecdev/programm/gebo.prg?name=start > > For example: > http://wikihost.org/wikis/vecdev/wiki/driveselect > http://wikihost.org/wikis/vecdev/wiki/autopartition > > Keep up the good work! > > Regards, > Joe1962 > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > Vectorlinux-devel mailing list > Vec...@li... > https://lists.sourceforge.net/lists/listinfo/vectorlinux-devel > |
14 messages has been excluded from this view by a project administrator.
