devil-linux-discuss — General Mailing List for all discussions

Re: [Devil-Linux-discuss] Feature request

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

Quoting Her...@sp...:

>
> Hi List
>
> I'm glad to hear that DL 1.4 is making progress! Lately, I have tested RC2
> and in my environment, it runs stable. I run it from a write protected CF
> card in a nexcom NSA appliance. The config file is loaded from a USB stick.
>
> I'm using the feature with the signed config file and it works grat for me,
> as long as the signature is valid. Here I'd like to have the following
> functionality:
> If the signature of the config file is not valid, the system should ask if
> it should continue to load it (as it does already). If this question times
> out or is not confirmed, the system should load a backup config file if the
> signature of the backup config file is valid.
>
> Doing this, we have a fallback configuration, in case the main
> configuration is not valid for some reason, and the system can still be
> operated from remote and the problem with the main configuration can be
> fixed.
>
> What do you think about this?

Not a bad idea.
We need a naming standard for the backup file.
The backup file would be created manually because of the signature, correct?


-- 

Regards
   Heiko Zuerker
   http://www.devil-linux.org


----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.

[Devil-Linux-discuss] Feature request

[<Her...@sp...>]

Hi List

I'm glad to hear that DL 1.4 is making progress! Lately, I have tested RC2
and in my environment, it runs stable. I run it from a write protected CF
card in a nexcom NSA appliance. The config file is loaded from a USB stick.

I'm using the feature with the signed config file and it works grat for me,
as long as the signature is valid. Here I'd like to have the following
functionality:
If the signature of the config file is not valid, the system should ask if
it should continue to load it (as it does already). If this question times
out or is not confirmed, the system should load a backup config file if the
signature of the backup config file is valid.

Doing this, we have a fallback configuration, in case the main
configuration is not valid for some reason, and the system can still be
operated from remote and the problem with the main configuration can be
fixed.

What do you think about this?

Regards,

Herbert

[Devil-Linux-discuss] Devil-Linux 1.4RC3 released

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

Hello DL Community

the third Release Candidate of Devil-Linux 1.4 is available for
download.

All known bugs of RC2 have been resolved, in addition to many software
updates.

Please report any problems on our mailing list or add them to the bug
tracker.

Regards
  Heiko Zuerker
  http://www.devil-linux.org

Re: [Devil-Linux-discuss] adding binaries to initial boot process

[Serge L. <fi...@in...>]

John,

I'm not sure you should copy binaries from 'big" system to initrd, because the
majority of ordinary files are dynamically linked and you will need to copy all
libs as well or rebuild tools in order to get statically linked binaries.

In initrd we use busybox - please check if busybox has mkfs.ext2 and sfdisk in
the list of supported applets.

Sincerely,
Serge


On 03/03/2010 06:48 PM, John Dailey wrote:
> Further information....I'm still having problems executing these
> commands.  I successfully have the files available during the iso boot,
> but they won't execute.
> 
> What I keep ending up with is this:
> 
> /init: line 348: /sbin/mkfs.ext2: not found
> 
> But if I include commands before the mkfs.ext2 like "which mkfs.ext2" it
> prints out /sbin/mkfs.ext2.  And if I do a "ls -l /sbin" I see my files
> there with the execute bit set on.
> 
> Both mkfs.ext2 and sfdisk give this same error, yet both appear to be
> available from the output from the "ls -l /sbin" command
> 
> All this is done from the linuxrc file, not from later scripts.
> 
> I'm sure I'm missing something important here.
> 
> -John
> 
> On Wed, Mar 3, 2010 at 6:37 PM, John Dailey <jd...@cp...
> <mailto:jd...@cp...>> wrote:
> 
>     OK, I may be answering my own question here -- hopefully someone can
>     stop me if I'm going down the wrong track.
> 
>     Browsing through the code, it looks like the initrdtree is built
>     piecemeal by the install make target of all the various packages.
>      So I altered the scripts ~/scripts/e2fsprogs and
>     ~/scripts/util-linux and did a manual cp to $INITRDDIR at the end of
>     the install block.
> 
>     I'm hoping this is a sensible way of doing this.
> 
>     -John
> 
> 
>     On Wed, Mar 3, 2010 at 4:04 PM, John Dailey <jd...@cp...
>     <mailto:jd...@cp...>> wrote:
> 
>         Hello,  I'm practicing customizing devil-linux, and am not quite
>         sure how to continue:
> 
>         I'm wanting to alter the boot-up procedure to auto format a
>         local hard drive in a certain way automatically during boot,
>         then use one of the partitions as the configuration store.  I've
>         found how to edit ~/config/etc/initrd/linuxrc, and clear the
>         build flag at ~/tmp/FLAGS/install/create-etc.  I'm successfully
>         rebuilding the iso file, and my changes are reflected during the
>         new boot.
> 
>         The problem is that during the boot process, I don't have access
>         to two utilities I need: sfdisk, and mkfs.ext2.  
> 
>         What is the 'correct' way to get those binaries to find their
>         way into a place accessible during boot.  Am I wanting to see
>         them show up in ~/tmp/ISO/initrdtree/bin?  Where do I make a
>         change to have them show up there?
> 
>         Also, if anyone thinks I'm going to run into some dependency
>         problems with those binaries, other suggestions are welcome.
> 
>         Thank you for any help you can provide.
> 
>         -John Dailey
> 
> 
> 
> 
> 
> ------------------------------------------------------------------------------
> Download Intel&#174; Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> 
> 
> 
> _______________________________________________
> Devil-linux-discuss mailing list
> Dev...@li...
> https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss

Re: [Devil-Linux-discuss] adding binaries to initial boot process

[John D. <jd...@cp...>]

Further information....I'm still having problems executing these commands.
 I successfully have the files available during the iso boot, but they won't
execute.

What I keep ending up with is this:

/init: line 348: /sbin/mkfs.ext2: not found

But if I include commands before the mkfs.ext2 like "which mkfs.ext2" it
prints out /sbin/mkfs.ext2.  And if I do a "ls -l /sbin" I see my files
there with the execute bit set on.

Both mkfs.ext2 and sfdisk give this same error, yet both appear to be
available from the output from the "ls -l /sbin" command

All this is done from the linuxrc file, not from later scripts.

I'm sure I'm missing something important here.

-John

On Wed, Mar 3, 2010 at 6:37 PM, John Dailey <jd...@cp...> wrote:

> OK, I may be answering my own question here -- hopefully someone can stop
> me if I'm going down the wrong track.
>
> Browsing through the code, it looks like the initrdtree is built piecemeal
> by the install make target of all the various packages.  So I altered the
> scripts ~/scripts/e2fsprogs and ~/scripts/util-linux and did a manual cp to
> $INITRDDIR at the end of the install block.
>
> I'm hoping this is a sensible way of doing this.
>
> -John
>
>
> On Wed, Mar 3, 2010 at 4:04 PM, John Dailey <jd...@cp...> wrote:
>
>> Hello,  I'm practicing customizing devil-linux, and am not quite sure how
>> to continue:
>>
>> I'm wanting to alter the boot-up procedure to auto format a local hard
>> drive in a certain way automatically during boot, then use one of the
>> partitions as the configuration store.  I've found how to edit
>> ~/config/etc/initrd/linuxrc, and clear the build flag at
>> ~/tmp/FLAGS/install/create-etc.  I'm successfully rebuilding the iso file,
>> and my changes are reflected during the new boot.
>>
>> The problem is that during the boot process, I don't have access to two
>> utilities I need: sfdisk, and mkfs.ext2.
>>
>> What is the 'correct' way to get those binaries to find their way into a
>> place accessible during boot.  Am I wanting to see them show up in
>> ~/tmp/ISO/initrdtree/bin?  Where do I make a change to have them show up
>> there?
>>
>> Also, if anyone thinks I'm going to run into some dependency problems with
>> those binaries, other suggestions are welcome.
>>
>> Thank you for any help you can provide.
>>
>> -John Dailey
>>
>
>

Re: [Devil-Linux-discuss] adding binaries to initial boot process

[John D. <jd...@cp...>]

OK, I may be answering my own question here -- hopefully someone can stop me
if I'm going down the wrong track.

Browsing through the code, it looks like the initrdtree is built piecemeal
by the install make target of all the various packages.  So I altered the
scripts ~/scripts/e2fsprogs and ~/scripts/util-linux and did a manual cp to
$INITRDDIR at the end of the install block.

I'm hoping this is a sensible way of doing this.

-John

On Wed, Mar 3, 2010 at 4:04 PM, John Dailey <jd...@cp...> wrote:

> Hello,  I'm practicing customizing devil-linux, and am not quite sure how
> to continue:
>
> I'm wanting to alter the boot-up procedure to auto format a local hard
> drive in a certain way automatically during boot, then use one of the
> partitions as the configuration store.  I've found how to edit
> ~/config/etc/initrd/linuxrc, and clear the build flag at
> ~/tmp/FLAGS/install/create-etc.  I'm successfully rebuilding the iso file,
> and my changes are reflected during the new boot.
>
> The problem is that during the boot process, I don't have access to two
> utilities I need: sfdisk, and mkfs.ext2.
>
> What is the 'correct' way to get those binaries to find their way into a
> place accessible during boot.  Am I wanting to see them show up in
> ~/tmp/ISO/initrdtree/bin?  Where do I make a change to have them show up
> there?
>
> Also, if anyone thinks I'm going to run into some dependency problems with
> those binaries, other suggestions are welcome.
>
> Thank you for any help you can provide.
>
> -John Dailey
>

[Devil-Linux-discuss] adding binaries to initial boot process

[John D. <jd...@cp...>]

Hello,  I'm practicing customizing devil-linux, and am not quite sure how to
continue:

I'm wanting to alter the boot-up procedure to auto format a local hard drive
in a certain way automatically during boot, then use one of the partitions
as the configuration store.  I've found how to edit
~/config/etc/initrd/linuxrc, and clear the build flag at
~/tmp/FLAGS/install/create-etc.  I'm successfully rebuilding the iso file,
and my changes are reflected during the new boot.

The problem is that during the boot process, I don't have access to two
utilities I need: sfdisk, and mkfs.ext2.

What is the 'correct' way to get those binaries to find their way into a
place accessible during boot.  Am I wanting to see them show up in
~/tmp/ISO/initrdtree/bin?  Where do I make a change to have them show up
there?

Also, if anyone thinks I'm going to run into some dependency problems with
those binaries, other suggestions are welcome.

Thank you for any help you can provide.

-John Dailey

Re: [Devil-Linux-discuss] Snort and IPTables

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

I'm sure there's some documentation on this out there somewhere.... ;-)

You can always add a feature request in our bug tracker or send in a patch.

Heiko

Quoting Bradlee Landis <bra...@gm...>: 

> But snort doesn't do permanent block, does it? It would just block the packets that are detected as vulnerabilities from what I thought.
>
> Anyways, I would think they would be included to at least provide a choice. Now, if there is an article showing that this is really a bad idea, I could justify the reasoning a little better, but a lot of these programs exist and I have not seen such documentation.
>
>
> Thanks,
> Brad Landis
>
> On Tue, Mar 2, 2010 at 6:43 PM, Heiko Zuerker <he...@zu...> wrote:
>
>
> > Brad, 
> >
> > Neither of those tools are included in DL. 
> >
> > Here?s the reason behind not including these tools: 
> >
> > Having snort automatically block a suspected intruder, makes you very vulnerable to a DOS attack. 
> >
> > Imagine an attacker who spoofs the source IP of the attack to be i.e. your DNS providers IPs or the IP of the next hop?. 
> >
> > Heiko 
> >
> > FROM: Bradlee Landis [mailto:bra...@gm...] 
> > SENT: Tuesday, March 02, 2010 1:25 PM
> > TO: dev...@li...
> > SUBJECT: [Devil-Linux-discuss] Snort and IPTables  
> >
> > I noticed that snort is installed on DL, but I can't seem to find a way to connect it to a firewall rule. I'm on 1.4RC1.
> >
> > Something like fwsnort - http://www.cipherdyne.org/fwsnort/ , or snort-inline (http://snort-inline.sourceforge.net/). Are either of these, or an alternative program installed that I am just missing, or is snort not installed for that purpose on DL?
> >
> > Thanks,
> > Brad Landis 
> >
> >
> > ------------------------------------------------------------------------------
> > Download Intel&#174; Parallel Studio Eval
> > Try the new software tools for yourself. Speed compiling, find bugs
> > proactively, and fine-tune applications for parallel performance.
> > See why Intel Parallel Studio got high marks during beta.
> > http://p.sf.net/sfu/intel-sw-dev
> > _______________________________________________
> > Devil-linux-discuss mailing list
> > Dev...@li...
> > https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss

-- 

Regards
  Heiko Zuerker
http://www.devil-linux.org

----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.

Re: [Devil-Linux-discuss] Snort and IPTables

[Bradlee L. <bra...@gm...>]

But snort doesn't do permanent block, does it? It would just block the
packets that are detected as vulnerabilities from what I thought.

Anyways, I would think they would be included to at least provide a choice.
Now, if there is an article showing that this is really a bad idea, I could
justify the reasoning a little better, but a lot of these programs exist and
I have not seen such documentation.


Thanks,
Brad Landis


On Tue, Mar 2, 2010 at 6:43 PM, Heiko Zuerker <he...@zu...> wrote:

>  Brad,
>
>
>
> Neither of those tools are included in DL.
>
>
>
> Here’s the reason behind not including these tools:
>
> Having snort automatically block a suspected intruder, makes you very
> vulnerable to a DOS attack.
>
> Imagine an attacker who spoofs the source IP of the attack to be i.e. your
> DNS providers IPs or the IP of the next hop….
>
>
>
> Heiko
>
>
>
> *From:* Bradlee Landis [mailto:bra...@gm...]
> *Sent:* Tuesday, March 02, 2010 1:25 PM
> *To:* dev...@li...
> *Subject:* [Devil-Linux-discuss] Snort and IPTables
>
>
>
> I noticed that snort is installed on DL, but I can't seem to find a way to
> connect it to a firewall rule. I'm on 1.4RC1.
>
> Something like fwsnort - http://www.cipherdyne.org/fwsnort/ , or
> snort-inline (http://snort-inline.sourceforge.net/). Are either of these,
> or an alternative program installed that I am just missing, or is snort not
> installed for that purpose on DL?
>
> Thanks,
> Brad Landis
>
>
>
>
> ------------------------------------------------------------------------------
> Download Intel&#174; Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> _______________________________________________
> Devil-linux-discuss mailing list
> Dev...@li...
> https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss
>
>

Re: [Devil-Linux-discuss] Snort and IPTables

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

Brad,

 

Neither of those tools are included in DL.

 

Here's the reason behind not including these tools:

Having snort automatically block a suspected intruder, makes you very
vulnerable to a DOS attack.

Imagine an attacker who spoofs the source IP of the attack to be i.e.
your DNS providers IPs or the IP of the next hop..

 

Heiko

 

From: Bradlee Landis [mailto:bra...@gm...] 
Sent: Tuesday, March 02, 2010 1:25 PM
To: dev...@li...
Subject: [Devil-Linux-discuss] Snort and IPTables

 

I noticed that snort is installed on DL, but I can't seem to find a way
to connect it to a firewall rule. I'm on 1.4RC1.

Something like fwsnort - http://www.cipherdyne.org/fwsnort/ , or
snort-inline (http://snort-inline.sourceforge.net/). Are either of
these, or an alternative program installed that I am just missing, or is
snort not installed for that purpose on DL?

Thanks,
Brad Landis

 

[Devil-Linux-discuss] Snort and IPTables

[Bradlee L. <bra...@gm...>]

I noticed that snort is installed on DL, but I can't seem to find a way to
connect it to a firewall rule. I'm on 1.4RC1.

Something like fwsnort - http://www.cipherdyne.org/fwsnort/ , or
snort-inline (http://snort-inline.sourceforge.net/). Are either of these, or
an alternative program installed that I am just missing, or is snort not
installed for that purpose on DL?

Thanks,
Brad Landis

Re: [Devil-Linux-discuss] Support non PAE cpu's

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

Quoting Frank Weis <Fra...@ct...>:

> Heiko Zuerker wrote:
>> Quoting Frank Weis <Fra...@ct...>:
>>
>>> Heiko Zuerker wrote:
>>>> Quoting Frank Weis <Fra...@ct...>:
>>>>
>>>>>>>>> You're compiling DL yourself, right? If yes, then use the  
>>>>>>>>> i586 version.
>>>>>>>>> If not, I just screwed up my build machine and it may be a few days
>>>>>>>>> before I can provide you a new compile.
>>>>> Hmm, either I am really stupid, or something is badly wrong, or a
>>>>> combination thereof, but I can't seem to build DL....
>>>>>
>>>>> so if you could provide a 586 build with all other options set to
>>>>> default, I'd be seriously grateful...
>>>> Where is it failing?
>>>> Can you attach the logs?
>>>>
>>> One build later:
>>>
>>> minicom still fails on 'install'
>>>
>>> install: minicom                                  log:
>>> /build/tmp/LOGS/install/minicom
>>> make: *** [minicom] Error 1
>>
>> This is weird, for some reason it is recompiling your minicom in the
>> install phase. It's not supposed to do that. In the build phase, we
>> actually make sure it includes the iconv library.
>>
>> Remove the file tmp/FLAGS/build/minicom and do a "make all" again.
>>
> Yep,
>
> after doing a first complete build with minicom disabled, I re-enabled
> it. I had to delete the source completely and re-extract it, delete the
> build flag, and then it compiled, installed correctly....

Aaahhh, that explains it.
Now I can stop worrying.... ;-)

-- 

Regards
   Heiko Zuerker
   http://www.devil-linux.org


----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.

Re: [Devil-Linux-discuss] Support non PAE cpu's

[Frank W. <Fra...@ct...>]

Heiko Zuerker wrote:
> Quoting Frank Weis <Fra...@ct...>:
> 
>> Heiko Zuerker wrote:
>>> Quoting Frank Weis <Fra...@ct...>:
>>>
>>>>>>>> You're compiling DL yourself, right? If yes, then use the i586 version.
>>>>>>>> If not, I just screwed up my build machine and it may be a few days
>>>>>>>> before I can provide you a new compile.
>>>> Hmm, either I am really stupid, or something is badly wrong, or a
>>>> combination thereof, but I can't seem to build DL....
>>>>
>>>> so if you could provide a 586 build with all other options set to
>>>> default, I'd be seriously grateful...
>>> Where is it failing?
>>> Can you attach the logs?
>>>
>> One build later:
>>
>> minicom still fails on 'install'
>>
>> install: minicom                                  log:
>> /build/tmp/LOGS/install/minicom
>> make: *** [minicom] Error 1
> 
> This is weird, for some reason it is recompiling your minicom in the  
> install phase. It's not supposed to do that. In the build phase, we  
> actually make sure it includes the iconv library.
> 
> Remove the file tmp/FLAGS/build/minicom and do a "make all" again.
> 
Yep,

after doing a first complete build with minicom disabled, I re-enabled
it. I had to delete the source completely and re-extract it, delete the
build flag, and then it compiled, installed correctly....

Thanks,
Frank

-- 
_______________________________________________
 Centre de Technologie de l'Education
 29 avenue John F. Kennedy
 L-1855 Luxembourg-Kirchberg
 email: Fra...@ct...
 tél.: +352 247-85973
 fax: +352 333797
_______________________________________________

Re: [Devil-Linux-discuss] Support non PAE cpu's

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

Quoting Frank Weis <Fra...@ct...>:

> Heiko Zuerker wrote:
>> Quoting Frank Weis <Fra...@ct...>:
>>
>>>>>>> You're compiling DL yourself, right? If yes, then use the i586 version.
>>>>>>> If not, I just screwed up my build machine and it may be a few days
>>>>>>> before I can provide you a new compile.
>>>
>>> Hmm, either I am really stupid, or something is badly wrong, or a
>>> combination thereof, but I can't seem to build DL....
>>>
>>> so if you could provide a 586 build with all other options set to
>>> default, I'd be seriously grateful...
>>
>> Where is it failing?
>> Can you attach the logs?
>>
> One build later:
>
> minicom still fails on 'install'
>
> install: minicom                                  log:
> /build/tmp/LOGS/install/minicom
> make: *** [minicom] Error 1

This is weird, for some reason it is recompiling your minicom in the  
install phase. It's not supposed to do that. In the build phase, we  
actually make sure it includes the iconv library.

Remove the file tmp/FLAGS/build/minicom and do a "make all" again.

-- 

Regards
   Heiko Zuerker
   http://www.devil-linux.org


----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.

Re: [Devil-Linux-discuss] Support non PAE cpu's

[Frank W. <Fra...@ct...>]

Heiko Zuerker wrote:
> Quoting Frank Weis <Fra...@ct...>:
> 
>>>>>> You're compiling DL yourself, right? If yes, then use the i586 version.
>>>>>> If not, I just screwed up my build machine and it may be a few days
>>>>>> before I can provide you a new compile.
>>
>> Hmm, either I am really stupid, or something is badly wrong, or a
>> combination thereof, but I can't seem to build DL....
>>
>> so if you could provide a 586 build with all other options set to
>> default, I'd be seriously grateful...
> 
> Where is it failing?
> Can you attach the logs?
> 
One build later:

minicom still fails on 'install'

install: minicom                                  log:
/build/tmp/LOGS/install/minicom
make: *** [minicom] Error 1



make[1]: Entering directory `/build/tmp/minicom-2.4/src'
gcc -DHAVE_CONFIG_H -I. -I..  -I../lib -DCONFDIR=\"/etc\"
-DLOCALEDIR=\"/usr/share/locale\"  -mtune=i586 -march=i586 -Wall -W
-mtune=i586 -march=i586 -MT minicom.o -MD -MP -MF .deps/minicom.Tpo -c
-o minicom.o minicom.c
mv -f .deps/minicom.Tpo .deps/minicom.Po
gcc -mtune=i586 -march=i586 -Wall -W -mtune=i586 -march=i586   -o
minicom minicom.o vt100.o config.o help.o updown.o util.o dial.o
window.o wkeys.o ipc.o windiv.o sysdep1.o sysdep1_s.o sysdep2.o rwconf.o
main.o file.o getsdir.o wildmat.o common.o ../lib/libport.a -lncurses
minicom.o: In function `do_iconv':
minicom.c:(.text+0x5d0): undefined reference to `libiconv'
minicom.c:(.text+0x618): undefined reference to `libiconv'
minicom.o: In function `.L201':
minicom.c:(.text+0x17cc): undefined reference to `libiconv_open'
minicom.o: In function `.L346':
minicom.c:(.text+0x3479): undefined reference to `libiconv_close'
collect2: ld returned 1 exit status
make[1]: *** [minicom] Error 1
make[1]: Leaving directory `/build/tmp/minicom-2.4/src'
make: *** [install-recursive] Error 1


-- 
_______________________________________________
 Centre de Technologie de l'Education
 29 avenue John F. Kennedy
 L-1855 Luxembourg-Kirchberg
 email: Fra...@ct...
 tél.: +352 247-85973
 fax: +352 333797
_______________________________________________

Re: [Devil-Linux-discuss] Problem With MySQL

[Moray M. <mmc...@ox...>]

Chris, /home will not be mounted to a hard drive unless you set up a hard drive partition as detailed at

http://www.devil-linux.org/documentation/1.3.x/ch01s05.html

I would recommend as well as /home and /var/log setting up the logical volume data (mapped to /var/data) for mysql, and having your mysql data at /var/data/mysql. In fact you might want to check that's not where it starts out anyway (I'm writing this on the move, so can't check)

Yours,
Moray
------------------
Moray McConnachie
Director of IT,
Oxford Analytica


-----Original Message-----
From: Dominic Raferd <dl...@ed...>
Date: Fri, 26 Feb 2010 04:33:44 
To: <dev...@li...>
Subject: Re: [Devil-Linux-discuss] Problem With MySQL

hmm, yes I think so. First find your current [or previous, if you 
already made the change in setup and restarted mysqld] mysql database 
(i.e. directory) location, and make a note of it:

/etc/init.d/mysqld stop

Now make the change in setup, when this is done (and saved), and 
assuming that the previous mysql database location was /var:

mv /var/mysql /home

If you had already previously restarted mysqld after changing setup, 
then the above line may throw an error, if you really want to recover 
the pre-existing database I think mv -f should overwrite the newer /home 
database.

Lastly do:

/etc/init.d/mysqld start

Dominic

On 25/02/2010 22:26, Chris Grove wrote:
> Thanks for that Dominic.
> Just one question though, will I need to recreate the database after adding
> the command??
> Thanks, Chris.
>
> --------------------------------------------------
> From: "Dominic Raferd"<dl...@ed...>
> Sent: Thursday, February 25, 2010 6:35 PM
> To:<dev...@li...>
> Subject: Re: [Devil-Linux-discuss] Problem With MySQL
>
>> Hi Chris
>>
>> Run setup, choose Other / MySQL, put in settings like:
>>
>> --user=mysql --pid-file=/var/run/mysql.pid --datadir=/home/mysql
>>
>> as you see, this specifies a datadir which is in /home, which is (for
>> me, and probably for you) a permanent (hard disk) location.
>>
>> Do:
>>
>> save-config -q
>> /etc/init.d/mysqld restart
>>
>> Dominic
>>
>> On 25/02/2010 17:28, Chris Grove wrote:
>>> Hi guys. I've got a bit of a noob problem here. I've got my DL server
>>> running just nice, I've managed to get postfix and dovecot to play nice
>>> too
>>> and work. The problem is, when the system restarts the MySQL database
>>> disappears and I have to set it all up again. Is there any way of moving
>>> the
>>> database so it gets backed up by the save-config command?? Either that or
>>> is
>>> there any way of writing a script to recreate the db after a reboot?
>>> Thanks, Chris.
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> Download Intel&#174; Parallel Studio Eval
>>> Try the new software tools for yourself. Speed compiling, find bugs
>>> proactively, and fine-tune applications for parallel performance.
>>> See why Intel Parallel Studio got high marks during beta.
>>> http://p.sf.net/sfu/intel-sw-dev
>>>_______________________________________________
>>> Devil-linux-discuss mailing list
>>> Dev...@li...
>>> https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss
>>
>> ------------------------------------------------------------------------------
>> Download Intel&#174; Parallel Studio Eval
>> Try the new software tools for yourself. Speed compiling, find bugs
>> proactively, and fine-tune applications for parallel performance.
>> See why Intel Parallel Studio got high marks during beta.
>> http://p.sf.net/sfu/intel-sw-dev
>>_______________________________________________
>> Devil-linux-discuss mailing list
>> Dev...@li...
>> https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss
>
>
>
>>
>> No virus found in this incoming message.
>> Checked by AVG - www.avg.com
>> Version: 9.0.733 / Virus Database: 271.1.1/2709 - Release Date: 02/25/10
>> 07:34:00
>>
>
> ------------------------------------------------------------------------------
> Download Intel&#174; Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
>_______________________________________________
> Devil-linux-discuss mailing list
> Dev...@li...
> https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss

------------------------------------------------------------------------------
Download Intel&#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Devil-linux-discuss mailing list
Dev...@li...
https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss

Re: [Devil-Linux-discuss] Problem With MySQL

[Dominic R. <dl...@ed...>]

hmm, yes I think so. First find your current [or previous, if you 
already made the change in setup and restarted mysqld] mysql database 
(i.e. directory) location, and make a note of it:

/etc/init.d/mysqld stop

Now make the change in setup, when this is done (and saved), and 
assuming that the previous mysql database location was /var:

mv /var/mysql /home

If you had already previously restarted mysqld after changing setup, 
then the above line may throw an error, if you really want to recover 
the pre-existing database I think mv -f should overwrite the newer /home 
database.

Lastly do:

/etc/init.d/mysqld start

Dominic

On 25/02/2010 22:26, Chris Grove wrote:
> Thanks for that Dominic.
> Just one question though, will I need to recreate the database after adding
> the command??
> Thanks, Chris.
>
> --------------------------------------------------
> From: "Dominic Raferd"<dl...@ed...>
> Sent: Thursday, February 25, 2010 6:35 PM
> To:<dev...@li...>
> Subject: Re: [Devil-Linux-discuss] Problem With MySQL
>
>> Hi Chris
>>
>> Run setup, choose Other / MySQL, put in settings like:
>>
>> --user=mysql --pid-file=/var/run/mysql.pid --datadir=/home/mysql
>>
>> as you see, this specifies a datadir which is in /home, which is (for
>> me, and probably for you) a permanent (hard disk) location.
>>
>> Do:
>>
>> save-config -q
>> /etc/init.d/mysqld restart
>>
>> Dominic
>>
>> On 25/02/2010 17:28, Chris Grove wrote:
>>> Hi guys. I've got a bit of a noob problem here. I've got my DL server
>>> running just nice, I've managed to get postfix and dovecot to play nice
>>> too
>>> and work. The problem is, when the system restarts the MySQL database
>>> disappears and I have to set it all up again. Is there any way of moving
>>> the
>>> database so it gets backed up by the save-config command?? Either that or
>>> is
>>> there any way of writing a script to recreate the db after a reboot?
>>> Thanks, Chris.
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> Download Intel&#174; Parallel Studio Eval
>>> Try the new software tools for yourself. Speed compiling, find bugs
>>> proactively, and fine-tune applications for parallel performance.
>>> See why Intel Parallel Studio got high marks during beta.
>>> http://p.sf.net/sfu/intel-sw-dev
>>> _______________________________________________
>>> Devil-linux-discuss mailing list
>>> Dev...@li...
>>> https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss
>>
>> ------------------------------------------------------------------------------
>> Download Intel&#174; Parallel Studio Eval
>> Try the new software tools for yourself. Speed compiling, find bugs
>> proactively, and fine-tune applications for parallel performance.
>> See why Intel Parallel Studio got high marks during beta.
>> http://p.sf.net/sfu/intel-sw-dev
>> _______________________________________________
>> Devil-linux-discuss mailing list
>> Dev...@li...
>> https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss
>
>
>
>>
>> No virus found in this incoming message.
>> Checked by AVG - www.avg.com
>> Version: 9.0.733 / Virus Database: 271.1.1/2709 - Release Date: 02/25/10
>> 07:34:00
>>
>
> ------------------------------------------------------------------------------
> Download Intel&#174; Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> _______________________________________________
> Devil-linux-discuss mailing list
> Dev...@li...
> https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss

Re: [Devil-Linux-discuss] Problem With MySQL

[Chris G. <dl...@ki...>]

Thanks for that Dominic.
Just one question though, will I need to recreate the database after adding 
the command??
Thanks, Chris.

--------------------------------------------------
From: "Dominic Raferd" <dl...@ed...>
Sent: Thursday, February 25, 2010 6:35 PM
To: <dev...@li...>
Subject: Re: [Devil-Linux-discuss] Problem With MySQL

> Hi Chris
>
> Run setup, choose Other / MySQL, put in settings like:
>
> --user=mysql --pid-file=/var/run/mysql.pid --datadir=/home/mysql
>
> as you see, this specifies a datadir which is in /home, which is (for
> me, and probably for you) a permanent (hard disk) location.
>
> Do:
>
> save-config -q
> /etc/init.d/mysqld restart
>
> Dominic
>
> On 25/02/2010 17:28, Chris Grove wrote:
>> Hi guys. I've got a bit of a noob problem here. I've got my DL server
>> running just nice, I've managed to get postfix and dovecot to play nice 
>> too
>> and work. The problem is, when the system restarts the MySQL database
>> disappears and I have to set it all up again. Is there any way of moving 
>> the
>> database so it gets backed up by the save-config command?? Either that or 
>> is
>> there any way of writing a script to recreate the db after a reboot?
>> Thanks, Chris.
>>
>>
>> ------------------------------------------------------------------------------
>> Download Intel&#174; Parallel Studio Eval
>> Try the new software tools for yourself. Speed compiling, find bugs
>> proactively, and fine-tune applications for parallel performance.
>> See why Intel Parallel Studio got high marks during beta.
>> http://p.sf.net/sfu/intel-sw-dev
>> _______________________________________________
>> Devil-linux-discuss mailing list
>> Dev...@li...
>> https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss
>
> ------------------------------------------------------------------------------
> Download Intel&#174; Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> _______________________________________________
> Devil-linux-discuss mailing list
> Dev...@li...
> https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss



>
> No virus found in this incoming message.
> Checked by AVG - www.avg.com
> Version: 9.0.733 / Virus Database: 271.1.1/2709 - Release Date: 02/25/10 
> 07:34:00
> 

Re: [Devil-Linux-discuss] Problem With MySQL

[Dominic R. <dl...@ed...>]

Hi Chris

Run setup, choose Other / MySQL, put in settings like:

--user=mysql --pid-file=/var/run/mysql.pid --datadir=/home/mysql

as you see, this specifies a datadir which is in /home, which is (for 
me, and probably for you) a permanent (hard disk) location.

Do:

save-config -q
/etc/init.d/mysqld restart

Dominic

On 25/02/2010 17:28, Chris Grove wrote:
> Hi guys. I've got a bit of a noob problem here. I've got my DL server
> running just nice, I've managed to get postfix and dovecot to play nice too
> and work. The problem is, when the system restarts the MySQL database
> disappears and I have to set it all up again. Is there any way of moving the
> database so it gets backed up by the save-config command?? Either that or is
> there any way of writing a script to recreate the db after a reboot?
> Thanks, Chris.
>
>
> ------------------------------------------------------------------------------
> Download Intel® Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> _______________________________________________
> Devil-linux-discuss mailing list
> Dev...@li...
> https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss

Re: [Devil-Linux-discuss] Problem With MySQL

[Moray M. <mmc...@ox...>]

The most common way would be to run mysql on a regular HD. See the DL docs for instruction on how to do this - essentially DL intelligently uses certain pre-determined named volume groups.

You would have to develop your own backup strategy.

The problem with using the DB as is and just moving it to somewhere that it gets saved with save-config (which you could doubtless do using symlinks) is that the DB is being stored in a ram disk - as the DB grows this is likely to become unfeasible. 

Yours,
Moray
------Original Message------
From: Chris Grove
To: dev...@li...
ReplyTo: dev...@li...
Subject: [Devil-Linux-discuss] Problem With MySQL
Sent: 25 Feb 2010 17:28

Hi guys. I've got a bit of a noob problem here. I've got my DL server 
running just nice, I've managed to get postfix and dovecot to play nice too 
and work. The problem is, when the system restarts the MySQL database 
disappears and I have to set it all up again. Is there any way of moving the 
database so it gets backed up by the save-config command?? Either that or is 
there any way of writing a script to recreate the db after a reboot?
Thanks, Chris. 


------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Devil-linux-discuss mailing list
Dev...@li...
https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss



------------------
Moray McConnachie
Director of IT,
Oxford Analytica

[Devil-Linux-discuss] Problem With MySQL

[Chris G. <dl...@ki...>]

Hi guys. I've got a bit of a noob problem here. I've got my DL server 
running just nice, I've managed to get postfix and dovecot to play nice too 
and work. The problem is, when the system restarts the MySQL database 
disappears and I have to set it all up again. Is there any way of moving the 
database so it gets backed up by the save-config command?? Either that or is 
there any way of writing a script to recreate the db after a reboot?
Thanks, Chris. 

Re: [Devil-Linux-discuss] Support non PAE cpu's

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

Quoting Frank Weis <Fra...@ct...>:

> Heiko Zuerker wrote:
>> Quoting Frank Weis <Fra...@ct...>:
>>
>>>>>>> You're compiling DL yourself, right? If yes, then use the i586 version.
>>>>>>> If not, I just screwed up my build machine and it may be a few days
>>>>>>> before I can provide you a new compile.
>>>
>>> Hmm, either I am really stupid, or something is badly wrong, or a
>>> combination thereof, but I can't seem to build DL....
>>>
>>> so if you could provide a 586 build with all other options set to
>>> default, I'd be seriously grateful...
>>
>> Where is it failing?
>> Can you attach the logs?
>>
> It is 'seemingly' random.... This morning, it had failed on building
> minicom. I 'make menuconfig'ed and disabled minicom and it built OK.
>
> Fine I thought, maybe someone works on minicom, so I did ./update_src
> followed. The subsequent build failed on installing openssl....
>
> Combined with the fact that the build sometimes 'hangs' because a
> process is asking for input (grsec did this), I'm going slowly nuts.
>
> I just rm'd the entire lfsystem and started from scratch with everything
> set to 586 in the build options.
>
> I'll be in touch with logs as soon as I have news...

I unfortunately destroyed my build machine earlier this week and had  
to rebuild it. I 'upgraded' to the latest OpenSUSE and now face  
similar problems you do.
Wondering if they added some new security features, do you see  
anything in the sys log or dmesg?


-- 

Regards
   Heiko Zuerker
   http://www.devil-linux.org


----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.

Re: [Devil-Linux-discuss] Support non PAE cpu's

[Frank W. <Fra...@ct...>]

Heiko Zuerker wrote:
> Quoting Frank Weis <Fra...@ct...>:
> 
>>>>>> You're compiling DL yourself, right? If yes, then use the i586 version.
>>>>>> If not, I just screwed up my build machine and it may be a few days
>>>>>> before I can provide you a new compile.
>>
>> Hmm, either I am really stupid, or something is badly wrong, or a
>> combination thereof, but I can't seem to build DL....
>>
>> so if you could provide a 586 build with all other options set to
>> default, I'd be seriously grateful...
> 
> Where is it failing?
> Can you attach the logs?
> 
It is 'seemingly' random.... This morning, it had failed on building
minicom. I 'make menuconfig'ed and disabled minicom and it built OK.

Fine I thought, maybe someone works on minicom, so I did ./update_src
followed. The subsequent build failed on installing openssl....

Combined with the fact that the build sometimes 'hangs' because a
process is asking for input (grsec did this), I'm going slowly nuts.

I just rm'd the entire lfsystem and started from scratch with everything
set to 586 in the build options.

I'll be in touch with logs as soon as I have news...

Thanks

Frank

-- 
_______________________________________________
 Centre de Technologie de l'Education
 29 avenue John F. Kennedy
 L-1855 Luxembourg-Kirchberg
 email: Fra...@ct...
 tél.: +352 247-85973
 fax: +352 333797
_______________________________________________

Re: [Devil-Linux-discuss] Support non PAE cpu's

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

Quoting Frank Weis <Fra...@ct...>:

>
>>>>> You're compiling DL yourself, right? If yes, then use the i586 version.
>>>>> If not, I just screwed up my build machine and it may be a few days
>>>>> before I can provide you a new compile.
>
>
> Hmm, either I am really stupid, or something is badly wrong, or a
> combination thereof, but I can't seem to build DL....
>
> so if you could provide a 586 build with all other options set to
> default, I'd be seriously grateful...

Where is it failing?
Can you attach the logs?

-- 

Regards
   Heiko Zuerker
   http://www.devil-linux.org


----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.

Re: [Devil-Linux-discuss] Support non PAE cpu's

[Frank W. <Fra...@ct...>]

>>>> You're compiling DL yourself, right? If yes, then use the i586 version.
>>>> If not, I just screwed up my build machine and it may be a few days
>>>> before I can provide you a new compile.


Hmm, either I am really stupid, or something is badly wrong, or a
combination thereof, but I can't seem to build DL....

so if you could provide a 586 build with all other options set to
default, I'd be seriously grateful...

Thanks,

Frank


-- 
_______________________________________________
 Centre de Technologie de l'Education
 29 avenue John F. Kennedy
 L-1855 Luxembourg-Kirchberg
 email: Fra...@ct...
 tél.: +352 247-85973
 fax: +352 333797
_______________________________________________