RE: [leaf-devel] LEAF configuration process/frontend

2003-07-19 Thread Erich Titl
Mohan you may want to have a look at the rload stuff if did lately. It uses the exixting lrp.conf file for the purpose of loading packages over the net. This runs long after linuxrc has finished and does not require hacks in the existing system. http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/l

RE: [leaf-devel] LEAF configuration process/frontend

2003-07-19 Thread S Mohan
I've had many reactions to this. I tried what I had in mind and was successful. I wanted to maintain backward compatibility too. Thus the file to load packages can be edited using lrcfg and we can have multiple lines in the file to declare the packages. The scheme I implemented was as follows: 1.

RE: [leaf-devel] LEAF configuration process/frontend

2003-07-17 Thread Erich Titl
Mohan At 19:04 18.07.2003, S Mohan wrote: I was looking at making configuration easy. That was the reason to suggest editing lrpkg.cfg from the LEAF system menu and the backup process saving this file. However, to make sure root, etc and other mandatory packages are not removed by mistake causing

RE: [leaf-devel] LEAF configuration process/frontend

2003-07-17 Thread S Mohan
y, July 17, 2003 8:15 PM To: [EMAIL PROTECTED]; Erich Titl Subject: Re: [leaf-devel] LEAF configuration process/frontend Hallo Erich this is always the problem in answering different people at once ;) I agree LRP=content can be put in a different file now allready. If LRP= is empty or not is not im

Re: [leaf-devel] LEAF configuration process/frontend

2003-07-17 Thread eric wolzak
the bering Crew -Ursprüngliche Nachricht- Von: Erich Titl <[EMAIL PROTECTED]> An: [EMAIL PROTECTED] <[EMAIL PROTECTED]> Datum: Donnerstag, 17. Juli 2003 16:32 Betreff: Re: [leaf-devel] LEAF configuration process/frontend Eric At 15:27 17.07.2003 +0200, eric wolzak wrote: >Hello Mo

Re: [leaf-devel] LEAF configuration process/frontend

2003-07-17 Thread Erich Titl
Eric At 15:27 17.07.2003 +0200, eric wolzak wrote: Hello Mohan, Erich, Charles and other The "early package " system can be changed ofcourse, but don't forget that the syslinux.cfg brings more information than just what packages to load. It defines the boot and Package load medium. System size a

Re: [leaf-devel] LEAF configuration process/frontend

2003-07-17 Thread eric wolzak
package loading is necessary ( for example something like apt-get ) my 2 Euro cent ;) Eric Wolzak member of the Bering Crew. -Ursprüngliche Nachricht- Von: S Mohan <[EMAIL PROTECTED]> An: [EMAIL PROTECTED] <[EMAIL PROTECTED]> Datum: Mittwoch, 16. Juli 2003 04:30 Betreff: [leaf-

Re: [leaf-devel] LEAF configuration process/frontend

2003-07-16 Thread Erich Titl
Hi At 06:49 16.07.2003 -0500, Charles Steinkuehler wrote: Erich Titl wrote: Mohan At 07:50 17.07.2003 +0530, S Mohan wrote: I was going thro' the LEAF documentation and in many places, syslinux.cfg needs to be edited. I've a suggestion to make this more user friendly. Can we not convert this proc

Re: [leaf-devel] LEAF configuration process/frontend

2003-07-16 Thread Charles Steinkuehler
Erich Titl wrote: Mohan At 07:50 17.07.2003 +0530, S Mohan wrote: I was going thro' the LEAF documentation and in many places, syslinux.cfg needs to be edited. I've a suggestion to make this more user friendly. Can we not convert this process and integrate it into the configuration menu under sys

Re: [leaf-devel] LEAF configuration process/frontend

2003-07-15 Thread Erich Titl
Mohan At 07:50 17.07.2003 +0530, S Mohan wrote: I was going thro' the LEAF documentation and in many places, syslinux.cfg needs to be edited. I've a suggestion to make this more user friendly. Can we not convert this process and integrate it into the configuration menu under system -option 2. We

[leaf-devel] LEAF configuration process/frontend

2003-07-15 Thread S Mohan
I was going thro' the LEAF documentation and in many places, syslinux.cfg needs to be edited. I've a suggestion to make this more user friendly. Can we not convert this process and integrate it into the configuration menu under system -option 2. We can adopt the lrpkg.cfg file to be edited as the