devil-linux-develop — developer discussions

Re: [Devil-linux-develop] etc.tar.bz2 upgrading ...

[Bruce S. <bw...@ar...>]

> >I've found one thing that is a pain, upgrading to a new version CD, 
> >plus also upgrading the configuration.
> ...
> Check if the file date is "Jan 1 1980", then it's an unmodified file.

I played it safe and compared each individual file.

> I would be very happy if you would get an update script working !

It seems to working on my system (not uploaded yet).

Basically it untars the old etc file and the new etc file into different
subdirectories, compares every file in old to new, gives you a list of
which file(s) changed and asks which file(s) you'd like to copy to the
new directory.  Then it tars up a new etc config file.

I really hated the thought of having to answer y/n for potentially
dozens of files to copy over to the new config (like the old kernel
"make config"), so I wrote it using "dialog", like the setup program.

This lets you scroll back & forth though the list of changed files and
check which file(s) to copy.  Plus if you press the HELP button on a
particular modified file, it does a "ls -l" on both old/new files, then
does a "diff -u" on them, and then does a "less" on both files.

The disadvantage is you need "dialog" installed on your desktop.  Do you
have a problem with that?  Most distro's come with dialog (at least
Redhat has come with it for quite a few releases), or the user can
always download and install the dialog package ...

 - BS

Re: [Devil-linux-develop] reworking build system

[Heiko Z. <hz...@pr...>]

On 10/13/2003 03:09:10 PM Friedrich Lobenstock wrote:
>Heiko Zuerker wrote:
>> I also removed the number from the .done files, since the number can=

>be
>> different.
>
>That's what I meant.

Oh..... ;-)
=

Re: [Devil-linux-develop] reworking build system

[Friedrich L. <fl...@fl...>]

Heiko Zuerker wrote:
> I also removed the number from the .done files, since the number can be
> different.

That's what I meant.

-- 
MfG / Regards
Friedrich Lobenstock
____________________________________________________________________
Friedrich Lobenstock                       Linux Services Lobenstock
URL: http://www.lsl.at/                         Email: fl...@fl...
____________________________________________________________________

Re: [Devil-linux-develop] reworking build system

[Heiko Z. <hz...@pr...>]

On 10/13/2003 02:33:32 PM Friedrich Lobenstock wrote:
>Heiko Zuerker wrote:
>> There's a new make command: "make prepare"
>> This  will order the build scripts according to the specified
>dependencies
>> and creates all the symlinks.
>> You need to do a "make prepare" when you added new scripts.
>> Prepare will also be automatically  invoked after a mrproper.
>>
>> The faciliities are specified in the file
>build/scripts/buildorder.conf .
>
>If insserv reordered the scripts then all .done files will become
>invalid because they have the number in them. Did you remove that
>part?

I re-worked this part, but the old .done files won't be recognized, but=
 the
principle is the same.
I also removed the number from the .done files, since the number can be=

different.

cya
  Heiko
=

Re: [Devil-linux-develop] reworking build system

[Friedrich L. <fl...@fl...>]

Heiko Zuerker wrote:
> There's a new make command: "make prepare"
> This  will order the build scripts according to the specified dependencies
> and creates all the symlinks.
> You need to do a "make prepare" when you added new scripts.
> Prepare will also be automatically  invoked after a mrproper.
> 
> The faciliities are specified in the file build/scripts/buildorder.conf .

If insserv reordered the scripts then all .done files will become
invalid because they have the number in them. Did you remove that
part?

-- 
MfG / Regards
Friedrich Lobenstock
____________________________________________________________________
Friedrich Lobenstock                       Linux Services Lobenstock
URL: http://www.lsl.at/                         Email: fl...@fl...
____________________________________________________________________

Re: [Devil-linux-develop] reworking build system

[Heiko Z. <hz...@pr...>]

On 10/12/2003 08:03:29 PM Heiko Zuerker wrote:
>Heiko Zuerker wrote:
>
>> Bruce Smith wrote:
>>
>>>> The major change is that you can define dependencies (i.e. which
>>>> libs are required for this package). It uses the insserv utility a=
nd
>>>> will be the same as our init system.
>>>>
>>>
>>>
>>> Sounds scary.  Give me a little notice before you check it in?
>>> (so I can run one last good compile, just in case ...  ;-)
>>>
>>>
>> The new build system seems to work. I have to do a few more compiles=

>> to make sure, but it looks like I can check it in later tonight.
>> So do you "cvs update -d -P" before I check my stuff in. ;-)
>
>Looks like our build system is a little bit too much for insserv. ;-)
>That means there will be some delays....

I found the problem, it was a small bug in insserv.

All the changes are checked in!
You need to do a "make mrproper unpack" first, since the new build syst=
em
will not recognize the old flags.

There's a new make command: "make prepare"
This  will order the build scripts according to the specified dependenc=
ies
and creates all the symlinks.
You need to do a "make prepare" when you added new scripts.
Prepare will also be automatically  invoked after a mrproper.

The faciliities are specified in the file build/scripts/buildorder.conf=
 .

cya
  Heiko
=

Re: [Devil-linux-develop] reworking build system

[Heiko Z. <he...@zu...>]

Heiko Zuerker wrote:

> Bruce Smith wrote:
>
>>> The major change is that you can define dependencies (i.e. which 
>>> libs are required for this package). It uses the insserv utility and 
>>> will be the same as our init system.
>>>   
>>
>>
>> Sounds scary.  Give me a little notice before you check it in?
>> (so I can run one last good compile, just in case ...  ;-)
>>  
>>
> The new build system seems to work. I have to do a few more compiles 
> to make sure, but it looks like I can check it in later tonight.
> So do you "cvs update -d -P" before I check my stuff in. ;-)

Looks like our build system is a little bit too much for insserv. ;-)
That means there will be some delays....

cya
  Heiko

[Devil-linux-develop] [ devil-linux-Bugs-822430 ] make DL LSB conform

[SourceForge.net <no...@so...>]

Bugs item #822430, was opened at 2003-10-12 18:29
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=410643&aid=822430&group_id=34096

Category: Build System
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Heiko Zuerker (smiley73)
Assigned to: Nobody/Anonymous (nobody)
Summary: make DL LSB conform

Initial Comment:
modify DL to get as much LSB conform as possible.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=410643&aid=822430&group_id=34096

Re: [Devil-linux-develop] attaching local HDD's ...

[Heiko Z. <he...@zu...>]

Bruce Smith wrote:

>>>Suppose I just want to run a simple command, like delete a file.
>>>There is no service to "start" or "stop", as the skeleton script reads.
>>>
>>>It's really handy just to have a script for miscellaneous commands.
>>>Call it "lazy" (or lacy :) if you want.  I've been called worse.  :-)
>>>      
>>>
>>for the archives... what file do you want to delete when booting a
>>devil-linux system? :)
>>    
>>
>
>Well ... that was only as example (from my Redhat system).  :-)
>
>One simple command I do want to run upon boot on my DL box is:
>
>  setterm -blank ......
>
>Another is:
>
>  noip -c /etc/noip.cfg
>
>Yeah, I know, "noip" a service and should have it's own script.
>But being in a hurry, I stuck them at the end of my firewall script.
>Me bad ...   :-)
>
Laaaaaazy assssss.....

>
>I suppose someone should create a real start/stop script for noip.
>Would that be considered a bug fix for 1.0, or a new 1.1 feature?
>  
>
new feature ;-)
I'm currently building RC-2

cya
  Heiko

Re: [Devil-linux-develop] attaching local HDD's ...

[Bruce S. <bw...@ar...>]

> > Suppose I just want to run a simple command, like delete a file.
> > There is no service to "start" or "stop", as the skeleton script reads.
> > 
> > It's really handy just to have a script for miscellaneous commands.
> > Call it "lazy" (or lacy :) if you want.  I've been called worse.  :-)
> 
> for the archives... what file do you want to delete when booting a
> devil-linux system? :)

Well ... that was only as example (from my Redhat system).  :-)

One simple command I do want to run upon boot on my DL box is:

  setterm -blank ......

Another is:

  noip -c /etc/noip.cfg

Yeah, I know, "noip" a service and should have it's own script.
But being in a hurry, I stuck them at the end of my firewall script.
Me bad ...   :-)

I suppose someone should create a real start/stop script for noip.
Would that be considered a bug fix for 1.0, or a new 1.1 feature?

 - BS

Re: [Devil-linux-develop] attaching local HDD's ...

[Diego T. <dt...@co...>]

On Fri, Oct 10, 2003 at 03:16:55PM -0400, Bruce Smith wrote:

> Suppose I just want to run a simple command, like delete a file.
> There is no service to "start" or "stop", as the skeleton script reads.
> 
> It's really handy just to have a script for miscellaneous commands.
> Call it "lazy" (or lacy :) if you want.  I've been called worse.  :-)

for the archives... what file do you want to delete when booting a devil-linux system? :)

-- 
-- gnupg keyfingerprint -- 48AF 5BF9 8F54 2966 64CC  2327 7CD0 DD91 B09D 5799
-- Use of a keyboard or mouse may be linked to serious injuries or disorders.  
Diego Torres - dt...@co... - Madrid / España

Re: [Devil-linux-develop] reworking build system

[Bruce S. <bw...@ar...>]

> >>The major change is that you can define dependencies (i.e. which libs 
> >>are required for this package). It uses the insserv utility and will be 
> >>the same as our init system.
> >
> >Sounds scary.  Give me a little notice before you check it in?
> >(so I can run one last good compile, just in case ...  ;-)
> >
> The new build system seems to work. 

Cool!

> I have to do a few more compiles to make sure, 

Try the ISO and make sure it runs too.  :-)

> but it looks like I can check it in later tonight.
> So do you "cvs update -d -P" before I check my stuff in. ;-)

Got it, thanks!  :-)

 - BS

Re: [Devil-linux-develop] reworking build system

[Heiko Z. <he...@zu...>]

Bruce Smith wrote:

>>The major change is that you can define dependencies (i.e. which libs 
>>are required for this package). It uses the insserv utility and will be 
>>the same as our init system.
>>    
>>
>
>Sounds scary.  Give me a little notice before you check it in?
>(so I can run one last good compile, just in case ...  ;-)
>  
>
The new build system seems to work. I have to do a few more compiles to 
make sure, but it looks like I can check it in later tonight.
So do you "cvs update -d -P" before I check my stuff in. ;-)

cya
  Heiko

Re: [Devil-linux-develop] reworking build system

[Heiko Z. <he...@zu...>]

Bruce Smith wrote:

>>The major change is that you can define dependencies (i.e. which libs 
>>are required for this package). It uses the insserv utility and will be 
>>the same as our init system.
>>    
>>
>
>Sounds scary.  Give me a little notice before you check it in?
>(so I can run one last good compile, just in case ...  ;-)
>  
>
It's probably a bit strange in the beginning, but you will soon love the 
benefits.

I have to continue cleaning now, I have people coming over tonight.

cya
  Heiko

Re: [Devil-linux-develop] Making changes to 1.0?

[Heiko Z. <he...@zu...>]

Bruce Smith wrote:

>...
>All makes sense, kind of what I figured, thanks!
>
>  
>
>>You *do not* want to run compiles inside the same lfssystem for 1.0 
>>*and* 1.1. Keep it separated !
>>    
>>
>
>That brings up another question I think I know the answer to, too.  :-)
>
>We are using the same lfssystem for 1.0 & 1.1, right?  
>(lfssystem-cvs-20030127-i486-stripped.tar.bz2)
>  
>
Yes we do, for now at least.

Until there's no real reason to change this, I won't. It's just too much 
work.
I'll probably introduce something new, once the new build system is 
working.
The idea is to provide a small statically compiled LFS system (as 
described in the book) and the rest is done via our build system.

cya
  Heiko

Re: [Devil-linux-develop] reworking build system

[Bruce S. <bw...@ar...>]

> I'm currently reworking the build system. 

Cool.

> The major change is that you can define dependencies (i.e. which libs 
> are required for this package). It uses the insserv utility and will be 
> the same as our init system.

Sounds scary.  Give me a little notice before you check it in?
(so I can run one last good compile, just in case ...  ;-)

 - BS

Re: [Devil-linux-develop] Making changes to 1.0?

[Bruce S. <bw...@ar...>]

...
All makes sense, kind of what I figured, thanks!

> You *do not* want to run compiles inside the same lfssystem for 1.0 
> *and* 1.1. Keep it separated !

That brings up another question I think I know the answer to, too.  :-)

We are using the same lfssystem for 1.0 & 1.1, right?  
(lfssystem-cvs-20030127-i486-stripped.tar.bz2)

 - BS

Re: [Devil-linux-develop] Making changes to 1.0?

[Heiko Z. <he...@zu...>]

Bruce Smith wrote:

>I should probably update the firewall script in 1.0 and 1.1 as someone
>suggested.  Since I've never worked with multiple branches, let me make
>sure I know what I'm doing so I don't screw something up.
>
>I haven't done anything since the new 1.1 branch, so my hard drive now
>contains all the 1.1 files, correct?  (it better! :)
>
>To modify a file in 1.0, I need to check it all out from CVS, correct?
>Do I need to re-download everything, or is there any to short-cut this
>by copying over my 1.1 directory to somewhere else?
>
>If I commit something in 1.0, does the change automatically go to 1.1,
>or do I have to manually commit it in 1.1 too?
>
>Anything else I should know ... ?  :-)
>  
>
Go into some other directory (i.e. /lfssystem/data2 ) and do a
cvs_sf co -r rel-1-0-patches build

This will check out the 1.0 branch. Whatever CVS command you execute in 
there, will be in the 1.0 branch.
You have to change the file in both 1.0 and 1.1, we don't use any 
merging features (I don't trust them).

In you case you don't need to download any sources or compile it, since 
it's "just" the firewall script.
But when you have to do it, just copy over the src directory and run a 
./update_src to make sure the differences are taken care off.

You *do not* want to run compiles inside the same lfssystem for 1.0 
*and* 1.1. Keep it separated !

cya
  Heiko

Re: [Devil-linux-develop] Making changes to 1.0?

[Friedrich L. <fl...@fl...>]

Bruce Smith wrote:
> I should probably update the firewall script in 1.0 and 1.1 as someone
> suggested.  Since I've never worked with multiple branches, let me make
> sure I know what I'm doing so I don't screw something up.
> 
> I haven't done anything since the new 1.1 branch, so my hard drive now
> contains all the 1.1 files, correct?  (it better! :)
> 
> To modify a file in 1.0, I need to check it all out from CVS, correct?
> Do I need to re-download everything, or is there any to short-cut this
> by copying over my 1.1 directory to somewhere else?
> 
> If I commit something in 1.0, does the change automatically go to 1.1,
> or do I have to manually commit it in 1.1 too?
> 
> Anything else I should know ... ?  :-)

I think you have to:
  * remove the unchanged script in question
  * check it out with the tag of the 1.1 branch
  * make modifications
  * check them in
  * merge the branch of your script with the main branch

See also http://www.cvshome.org/docs/manual/cvs-1.11.7/cvs_5.html
especially http://www.cvshome.org/docs/manual/cvs-1.11.7/cvs_5.html#SEC62

-- 
MfG / Regards
Friedrich Lobenstock
____________________________________________________________________
Friedrich Lobenstock                       Linux Services Lobenstock
URL: http://www.lsl.at/                         Email: fl...@fl...
____________________________________________________________________

Re: [Devil-linux-develop] etc.tar.bz2 upgrading ...

[Heiko Z. <he...@zu...>]

Bruce Smith wrote:

>I've found one thing that is a pain, upgrading to a new version CD, 
>plus also upgrading the configuration.
>
>If you don't upgrade the config, you are potentially missing new updates
>in scripts in the /etc/init.d directory and other places.
>
>If you DO upgrade your config, it's a pain copying over all your
>customized configuration files (or recreating them).
>
>I've been thinking of writing a script to ease this pain.  It can
>compare your old config to a new config, and ask you one file at a time
>if it should be upgraded or not.  Then create a updated etc.tar.bz2.
>
>Thoughts?
>  
>
Check if the file date is "Jan 1 1980", then it's an unmodified file.

I would be very happy if you would get an update script working !

cya
  Heiko

Re: [Devil-linux-develop] Re: [Devil-Linux-discuss] Hard Disk Installation

[Heiko Z. <he...@zu...>]

Bruce Smith wrote:

>>I was just checking the linuxrc script, either I'm still not awake (very 
>>much possible).,,
>>I didn't find the part were you load the etc.tar.bz2 from the CD ROM
>>    
>>
>
>On my system, like number 176 says:
>
>  echo "Using custom configuration on CDROM."
>
>See the surrounding lines.  (after you wake up ;)
>  
>
Oh there it is... ;-)
I guess know I'm (almost) awake.

cya
  Heiko

[Devil-linux-develop] Making changes to 1.0?

[Bruce S. <bw...@ar...>]

I should probably update the firewall script in 1.0 and 1.1 as someone
suggested.  Since I've never worked with multiple branches, let me make
sure I know what I'm doing so I don't screw something up.

I haven't done anything since the new 1.1 branch, so my hard drive now
contains all the 1.1 files, correct?  (it better! :)

To modify a file in 1.0, I need to check it all out from CVS, correct?
Do I need to re-download everything, or is there any to short-cut this
by copying over my 1.1 directory to somewhere else?

If I commit something in 1.0, does the change automatically go to 1.1,
or do I have to manually commit it in 1.1 too?

Anything else I should know ... ?  :-)

 - BS

[Devil-linux-develop] etc.tar.bz2 upgrading ...

[Bruce S. <bw...@ar...>]

I've found one thing that is a pain, upgrading to a new version CD, 
plus also upgrading the configuration.

If you don't upgrade the config, you are potentially missing new updates
in scripts in the /etc/init.d directory and other places.

If you DO upgrade your config, it's a pain copying over all your
customized configuration files (or recreating them).

I've been thinking of writing a script to ease this pain.  It can
compare your old config to a new config, and ask you one file at a time
if it should be upgraded or not.  Then create a updated etc.tar.bz2.

Thoughts?

 - BS

Re: [Devil-linux-develop] Re: [Devil-Linux-discuss] Hard Disk Installation

[Bruce S. <bw...@ar...>]

> > I was just checking the linuxrc script, either I'm still not awake (very 
> > much possible).,,
> > I didn't find the part were you load the etc.tar.bz2 from the CD ROM
> 
> On my system, like number 176 says:

Or "line" number 176 ...  (guess I should wake up too :)

>   echo "Using custom configuration on CDROM."
> 
> See the surrounding lines.  (after you wake up ;)

 - BS

Re: [Devil-linux-develop] Re: [Devil-Linux-discuss] Hard Disk Installation

[Bruce S. <bw...@ar...>]

> I was just checking the linuxrc script, either I'm still not awake (very 
> much possible).,,
> I didn't find the part were you load the etc.tar.bz2 from the CD ROM

On my system, like number 176 says:

  echo "Using custom configuration on CDROM."

See the surrounding lines.  (after you wake up ;)

 - BS