devil-linux-develop Mailing List for Devil-Linux (Page 10)

Heiko Zuerker wrote:
> I added all the missing modules.

Thanks, I will remove it from my patches.

I aplied this version to my production routers/servers.
I have one problem, but about I write in separate thread.

Regards

-- 
Andrzej Odyniec

Andrzej,

I added all the missing modules.

Heiko

Quoting Andrzej Odyniec <an...@ma...>:

> Heiko Zuerker wrote:
>> I uploaded a new DL testing version to the FTP server.
>> The main change is the 3.0 Kernel.
>
> Thanks, Heiko.
>
> Todays compilation with Asterisk ended successfully.
> In build/prepare in build .config phase there is many new settings according
> to SND. I set it in the following manner:
>
>> echo CONFIG_SOUND_OSS_CORE_PRECLAIM=y >>config_linux
>> echo CONFIG_SND_PCM_OSS_PLUGINS=y >>config_linux
>> echo CONFIG_SND_HRTIMER=m >>config_linux
>> echo CONFIG_SND_DYNAMIC_MINORS=n >>config_linux
>> echo CONFIG_SND_SUPPORT_OLD_API=y >>config_linux
>> echo CONFIG_SND_VERBOSE_PROCFS=y >>config_linux
>> echo CONFIG_SND_DRIVERS=y >>config_linux
>> echo CONFIG_SND_PCSP=m >>config_linux
>> echo CONFIG_SND_ALOOP=m >>config_linux
>> echo CONFIG_SND_MTS64=m >>config_linux
>> echo CONFIG_SND_PORTMAN2X4=m >>config_linux
>> echo CONFIG_SND_AC97_POWER_SAVE=n >>config_linux
>> echo CONFIG_SND_ISA=y >>config_linux
>> echo CONFIG_SND_ADLIB=m >>config_linux
>> echo CONFIG_SND_AZT1605=m >>config_linux
>> echo CONFIG_SND_AZT2316=m >>config_linux
>> echo CONFIG_SND_SC6000=m >>config_linux
>> echo CONFIG_SND_JAZZ16=m >>config_linux
>> echo CONFIG_SND_MIRO=m >>config_linux
>> echo CONFIG_SND_MSND_PINNACLE=m >>config_linux
>> echo CONFIG_SND_MSND_CLASSIC=m >>config_linux
>> echo CONFIG_SND_PCI=y >>config_linux
>> echo CONFIG_SND_AD1889=m >>config_linux
>> echo CONFIG_SND_ALS300=m >>config_linux
>> echo CONFIG_SND_ASIHPI=m >>config_linux
>> echo CONFIG_SND_ATIIXP=m >>config_linux
>> echo CONFIG_SND_ATIIXP_MODEM=m >>config_linux
>> echo CONFIG_SND_AU8810=m >>config_linux
>> echo CONFIG_SND_AU8820=m >>config_linux
>> echo CONFIG_SND_AU8830=m >>config_linux
>> echo CONFIG_SND_AW2=m >>config_linux
>> echo CONFIG_SND_BT87X_OVERCLOCK=n >>config_linux
>> echo CONFIG_SND_CA0106=m >>config_linux
>> echo CONFIG_SND_OXYGEN=m >>config_linux
>> echo CONFIG_SND_CS5530=m >>config_linux
>> echo CONFIG_SND_CS5535AUDIO=m >>config_linux
>> echo CONFIG_SND_CTXFI=m >>config_linux
>> echo CONFIG_SND_DARLA20=m >>config_linux
>> echo CONFIG_SND_GINA20=m >>config_linux
>> echo CONFIG_SND_LAYLA20=m >>config_linux
>> echo CONFIG_SND_DARLA24=m >>config_linux
>> echo CONFIG_SND_GINA24=m >>config_linux
>> echo CONFIG_SND_LAYLA24=m >>config_linux
>> echo CONFIG_SND_MONA=m >>config_linux
>> echo CONFIG_SND_MIA=m >>config_linux
>> echo CONFIG_SND_ECHO3G=m >>config_linux
>> echo CONFIG_SND_INDIGO=m >>config_linux
>> echo CONFIG_SND_INDIGOIO=m >>config_linux
>> echo CONFIG_SND_INDIGODJ=m >>config_linux
>> echo CONFIG_SND_INDIGOIOX=m >>config_linux
>> echo CONFIG_SND_INDIGODJX=m >>config_linux
>> echo CONFIG_SND_EMU10K1X=m >>config_linux
>> echo CONFIG_SND_ES1968_INPUT=n >>config_linux
>> echo CONFIG_SND_HDA_INTEL=m >>config_linux
>> echo CONFIG_SND_HDSPM=m >>config_linux
>> echo CONFIG_SND_INTEL8X0M=m >>config_linux
>> echo CONFIG_SND_LOLA=m >>config_linux
>> echo CONFIG_SND_LX6464ES=m >>config_linux
>> echo CONFIG_SND_MAESTRO3_INPUT=n >>config_linux
>> echo CONFIG_SND_MIXART=m >>config_linux
>> echo CONFIG_SND_PCXHR=m >>config_linux
>> echo CONFIG_SND_RIPTIDE=m >>config_linux
>> echo CONFIG_SND_SIS7019=m >>config_linux
>> echo CONFIG_SND_VIA82XX_MODEM=m >>config_linux
>> echo CONFIG_SND_VIRTUOSO=m >>config_linux
>> echo CONFIG_SND_SPI=y >>config_linux
>> echo CONFIG_SND_USB=y >>config_linux
>> echo CONFIG_SND_USB_UA101=m >>config_linux
>> echo CONFIG_SND_USB_USX2Y=m >>config_linux
>> echo CONFIG_SND_USB_CAIAQ=m >>config_linux
>> echo CONFIG_SND_USB_US122L=m >>config_linux
>> echo CONFIG_SND_USB_6FIRE=m >>config_linux
>> echo CONFIG_SND_FIREWIRE=y >>config_linux
>> echo CONFIG_SND_FIREWIRE_SPEAKERS=m >>config_linux
>> echo CONFIG_SND_ISIGHT=m >>config_linux
>> echo CONFIG_SND_PCMCIA=y >>config_linux
>> echo CONFIG_SND_PDAUDIOCF=m >>config_linux
>> echo CONFIG_SND_SOC=m >>config_linux
>> echo CONFIG_HID_PRODIKEYS=m >>config_linux
>> echo CONFIG_SND_SEQ_HRTIMER_DEFAULT=y >>config_linux
>> echo CONFIG_SND_HDA_HWDEP=n >>config_linux
>> echo CONFIG_SND_HDA_INPUT_BEEP=n >>config_linux
>> echo CONFIG_SND_HDA_INPUT_JACK=n >>config_linux
>> echo CONFIG_SND_HDA_PATCH_LOADER=n >>config_linux
>> echo CONFIG_SND_HDA_CODEC_REALTEK=y >>config_linux
>> echo CONFIG_SND_HDA_CODEC_ANALOG=y >>config_linux
>> echo CONFIG_SND_HDA_CODEC_SIGMATEL=y >>config_linux
>> echo CONFIG_SND_HDA_CODEC_VIA=y >>config_linux
>> echo CONFIG_SND_HDA_CODEC_HDMI=y >>config_linux
>> echo CONFIG_SND_HDA_CODEC_CIRRUS=y >>config_linux
>> echo CONFIG_SND_HDA_CODEC_CONEXANT=y >>config_linux
>> echo CONFIG_SND_HDA_CODEC_CA0110=y >>config_linux
>> echo CONFIG_SND_HDA_CODEC_CMEDIA=y >>config_linux
>> echo CONFIG_SND_HDA_CODEC_SI3054=y >>config_linux
>> echo CONFIG_SND_HDA_GENERIC=y >>config_linux
>> echo CONFIG_SND_HDA_POWER_SAVE=n >>config_linux
>> echo CONFIG_SND_USB_CAIAQ_INPUT=n >>config_linux
>> echo CONFIG_SND_SOC_CACHE_LZO=n >>config_linux
>> echo CONFIG_SND_SOC_ALL_CODECS=m >>config_linux
>
> Next days I will try in testing environment. And will compile  
> without Asterisk
> with switched grsec on.
>
> Regards
>
> Andrzej Odyniec
>
> ------------------------------------------------------------------------------
> All of the data generated in your IT infrastructure is seriously valuable.
> Why? It contains a definitive record of application performance, security
> threats, fraudulent activity, and more. Splunk takes this data and makes
> sense of it. IT sense. And common sense.
> http://p.sf.net/sfu/splunk-d2dcopy2
> _______________________________________________
> Devil-linux-develop mailing list
> Dev...@li...
> https://lists.sourceforge.net/lists/listinfo/devil-linux-develop


-- 

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

I added autoos=1 to CVS

-- 

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

> -----Original Message-----
> From: Andrzej Odyniec [mailto:an...@ma...]
> Sent: Thursday, October 06, 2011 1:28 PM
> To: dev...@li...
> Subject: Re: [Devil-linux-develop] new test version
> 
> Heiko Zuerker wrote:
> > I have a nightly build running with the CVS version and it's not
> > choking at webmin, that's why I'm reluctant to do the change.
> > There was a problem in one of the scripts which caused that, but I
> > know I fixed it. I just wish I'd remember what I did.
> >
> > Would you mind starting completely over?
> > I think the issue was somehow related to the new kernel.
> 
> Heiko,
> 
> I catched this issue three days ago, and since I'm hunting for the cause. I
> made about 10 builds on three machines. All are on first succesfully compiled
> DL with kernel 3.0.4 without grsecurity:
> -- old, bare metal, on the Asus P5B-VM DO, dedicated to
>     DL builds three years ago
> -- VM on i7-965/AsusP6WSpro and VMware 7 on W7
> -- VM on i7-2720QM/DellM6600 and VMware 8 on W7 Additionally I fschk'ed
> disks before this builds. Build environment was constructed completly from
> clean state every time. The only material not from Internet was source
> package repository, but checked every time by ./updatesrc.
> On this three environments was used exact copy of this same source
> packages.
> 
> On VMs webmin installs without stops. On bare metal Asus webmin install
> ask for OS. I don't know why? I haven't time to precise analyze webmin install
> scripts. So I changed autoos to =1 in webmin script and install dont stops.
> 
> That's all
> 
> Best Regards
> 
> --
> Andrzej Odyniec
> 
> <an...@ma...>
> Rada Nadzorcza Macrologic SA
> ul. Kłopotowskiego 22, 03-717 Warszawa
> tel. +48-222566332, kom. +48-601276572
> Skype: andrzej.odyniec
> Rejestr: Sąd Rejonowy dla m.st. Warszawy,
>           XIII Wydział Gospodarczy Krajowego
>           Rejestru Sądowego, numer 0000045462 Numer identyfikacji
> podatkowej: PL 5220002825 Kapitał zakładowy: 1888719 zł opłacony w całości
> 
> ------------------------------------------------------------------------------
> All the data continuously generated in your IT infrastructure contains a
> definitive record of customers, application performance, security threats,
> fraudulent activity and more. Splunk takes this data and makes sense of it.
> Business sense. IT sense. Common sense.
> http://p.sf.net/sfu/splunk-d2dcopy1
> _______________________________________________
> Devil-linux-develop mailing list
> Dev...@li...
> https://lists.sourceforge.net/lists/listinfo/devil-linux-develop

Heiko Zuerker wrote:
> I have a nightly build running with the CVS version and it's not  
> choking at webmin, that's why I'm reluctant to do the change.
> There was a problem in one of the scripts which caused that, but I  
> know I fixed it. I just wish I'd remember what I did.
> 
> Would you mind starting completely over?
> I think the issue was somehow related to the new kernel.

Heiko,

I catched this issue three days ago, and since I'm hunting for the cause. I 
made about 10 builds on three machines. All are on first succesfully compiled 
DL with kernel 3.0.4 without grsecurity:
-- old, bare metal, on the Asus P5B-VM DO, dedicated to
    DL builds three years ago
-- VM on i7-965/AsusP6WSpro and VMware 7 on W7
-- VM on i7-2720QM/DellM6600 and VMware 8 on W7
Additionally I fschk'ed disks before this builds. Build environment was 
constructed completly from clean state every time. The only material not from 
Internet was source package repository, but checked every time by ./updatesrc. 
On this three environments was used exact copy of this same source packages.

On VMs webmin installs without stops. On bare metal Asus webmin install ask 
for OS. I don't know why? I haven't time to precise analyze webmin install 
scripts. So I changed autoos to =1 in webmin script and install dont stops.

That's all

Best Regards

-- 
Andrzej Odyniec

<an...@ma...>
Rada Nadzorcza Macrologic SA
ul. Kłopotowskiego 22, 03-717 Warszawa
tel. +48-222566332, kom. +48-601276572
Skype: andrzej.odyniec
Rejestr: Sąd Rejonowy dla m.st. Warszawy,
          XIII Wydział Gospodarczy Krajowego
          Rejestru Sądowego, numer 0000045462
Numer identyfikacji podatkowej: PL 5220002825
Kapitał zakładowy: 1888719 zł opłacony w całości

Andrzej,

I have a nightly build running with the CVS version and it's not  
choking at webmin, that's why I'm reluctant to do the change.
There was a problem in one of the scripts which caused that, but I  
know I fixed it. I just wish I'd remember what I did.

Would you mind starting completely over?
I think the issue was somehow related to the new kernel.

Heiko

Quoting Andrzej Odyniec <an...@ma...>:

> Heiko Zuerker wrote:
>> What does this do?
>
> 1. I checked. I used LAST cvs. This time I was faster ;-)
>
> 2. webmin installation script calls oschooser script
>
>> $perl "$srcdir/oschooser.pl" "$srcdir/os_list.txt" $tempdir/$$.os $autoos
>
> with autoos as third parameter, but in oschooser is foloowing parameters
> description:
>
>> #!/usr/bin/perl
>> # oschooser.pl
>> # Read the list of operating systems and ask the user to choose
>> # an OS and version
>> # auto param: 0 = always ask user
>> #             1 = automatic, give up if fails
>> #             2 = automatic, ask user if fails
>> #             3 = automatic, ask user if fails and if a TTY
>
> so if autoos is set to 3, user can be asked sometime (when?) for os type
> selection. If autoos is set to 1, there should be no dialog at all  
> and no stops.
>
> Ofcourse, better is to be on os list in webmin, but this is the future.
>
> So I suggest change in install phase settings autoos=1 in script before
> calling setup.sh.
>
> Regards
>
> Andrzej Odyniec
>
> ------------------------------------------------------------------------------
> All the data continuously generated in your IT infrastructure contains a
> definitive record of customers, application performance, security
> threats, fraudulent activity and more. Splunk takes this data and makes
> sense of it. Business sense. IT sense. Common sense.
> http://p.sf.net/sfu/splunk-d2dcopy1
> _______________________________________________
> Devil-linux-develop mailing list
> Dev...@li...
> https://lists.sourceforge.net/lists/listinfo/devil-linux-develop


-- 

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

Heiko Zuerker wrote:
> What does this do?

1. I checked. I used LAST cvs. This time I was faster ;-)

2. webmin installation script calls oschooser script

> $perl "$srcdir/oschooser.pl" "$srcdir/os_list.txt" $tempdir/$$.os $autoos

with autoos as third parameter, but in oschooser is foloowing parameters 
description:

> #!/usr/bin/perl
> # oschooser.pl
> # Read the list of operating systems and ask the user to choose
> # an OS and version
> # auto param: 0 = always ask user
> #             1 = automatic, give up if fails
> #             2 = automatic, ask user if fails
> #             3 = automatic, ask user if fails and if a TTY

so if autoos is set to 3, user can be asked sometime (when?) for os type 
selection. If autoos is set to 1, there should be no dialog at all and no stops.

Ofcourse, better is to be on os list in webmin, but this is the future.

So I suggest change in install phase settings autoos=1 in script before 
calling setup.sh.

Regards

Andrzej Odyniec

What does this do?

-- 

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


> -----Original Message-----
> From: Andrzej Odyniec [mailto:an...@ma...]
> Sent: Thursday, October 06, 2011 8:13 AM
> To: dev...@li...
> Subject: Re: [Devil-linux-develop] new test version
> 
> > Build waits on dialog, when webmin is install'ed:
> 
> Probably better is to set in webmin script autoos=1 instead of autoos=3
> 
> Rgds
> 
> Andrzej Odyniec
> 
>
----------------------------------------------------------------------------
--
> All the data continuously generated in your IT infrastructure contains a
> definitive record of customers, application performance, security threats,
> fraudulent activity and more. Splunk takes this data and makes sense of
it.
> Business sense. IT sense. Common sense.
> http://p.sf.net/sfu/splunk-d2dcopy1
> _______________________________________________
> Devil-linux-develop mailing list
> Dev...@li...
> https://lists.sourceforge.net/lists/listinfo/devil-linux-develop

Heiko Zuerker wrote:

> Make sure you get the latest version from CVS, the fix is in there already.

Thanks. As usually, you are faster :-)

Regards

Andrzej Odyniec

> Build waits on dialog, when webmin is install'ed:

Probably better is to set in webmin script autoos=1 instead of autoos=3

Rgds

Andrzej Odyniec

Make sure you get the latest version from CVS, the fix is in there already.

-- 

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

> -----Original Message-----
> From: Andrzej Odyniec [mailto:an...@ma...]
> Sent: Thursday, October 06, 2011 7:33 AM
> To: dev...@li...
> Subject: Re: [Devil-linux-develop] new test version
> 
> Hi,
> 
> Build waits on dialog, when webmin is install'ed:
> 
> >
> **********************************************************
> ************
> > * For Webmin to work properly, it needs to know which operating system
> > type and version you are running. Please select your system type by
> > entering the number next to it from the list below
> >
---------------------------------------------------------------------------
> >   1) Pardus Linux           2) Sun Solaris            3) Lycoris
Desktop/LX
> >   4) Caldera OpenLinux eS   5) Caldera OpenLinux      6) Asianux Server
> [...]
> >  88) Cygwin                89) Sun Java Desktop Sys  90) Generic Linux
> >  91) Windows
> > ----------------------------------------------------------------------
> > -----
> > Operating system:
> 
> but only on one machine (exactly, on real machine)
> 
> On other two VMs answer is following:
> >
> **********************************************************
> ************
> > *
> > Failed to detect operating system
> > correcting config files
> > Can't open /etc/webmin/apache/*: No such file or directory.
> > Can't open /etc/webmin/cron/*: No such file or directory.
> [...]
> > Can't open /etc/webmin/dovecot/config: No such file or directory.
> > Can't open /etc/webmin/dovecot/config: No such file or directory.
> > rm: cannot remove `/etc/webmin/*cache': No such file or directory
> > `/etc/webmin' -> `/build/tmp/ETC/etc/webmin'
> > # Start Webmin?
> 
> and build go w/o waits.
> 
> On all build environments base system is new DL with kernel 3.0.4
> 
> I will search solution
> 
> Rgds
> 
> --
> Andrzej Odyniec
> 
>
----------------------------------------------------------------------------
--
> All the data continuously generated in your IT infrastructure contains a
> definitive record of customers, application performance, security threats,
> fraudulent activity and more. Splunk takes this data and makes sense of
it.
> Business sense. IT sense. Common sense.
> http://p.sf.net/sfu/splunk-d2dcopy1
> _______________________________________________
> Devil-linux-develop mailing list
> Dev...@li...
> https://lists.sourceforge.net/lists/listinfo/devil-linux-develop

Hi,

Build waits on dialog, when webmin is install'ed:

> ***********************************************************************
> For Webmin to work properly, it needs to know which operating system
> type and version you are running. Please select your system type by
> entering the number next to it from the list below
> ---------------------------------------------------------------------------
>   1) Pardus Linux           2) Sun Solaris            3) Lycoris Desktop/LX
>   4) Caldera OpenLinux eS   5) Caldera OpenLinux      6) Asianux Server
[...]
>  88) Cygwin                89) Sun Java Desktop Sys  90) Generic Linux
>  91) Windows
> ---------------------------------------------------------------------------
> Operating system:

but only on one machine (exactly, on real machine)

On other two VMs answer is following:
> ***********************************************************************
> Failed to detect operating system
> correcting config files
> Can't open /etc/webmin/apache/*: No such file or directory.
> Can't open /etc/webmin/cron/*: No such file or directory.
[...]
> Can't open /etc/webmin/dovecot/config: No such file or directory.
> Can't open /etc/webmin/dovecot/config: No such file or directory.
> rm: cannot remove `/etc/webmin/*cache': No such file or directory
> `/etc/webmin' -> `/build/tmp/ETC/etc/webmin'
> # Start Webmin?

and build go w/o waits.

On all build environments base system is new DL with kernel 3.0.4

I will search solution

Rgds

-- 
Andrzej Odyniec

Heiko Zuerker wrote:
> I uploaded a new DL testing version to the FTP server.
> The main change is the 3.0 Kernel.

Thanks, Heiko.

Todays compilation with Asterisk ended successfully.
In build/prepare in build .config phase there is many new settings according 
to SND. I set it in the following manner:

> echo CONFIG_SOUND_OSS_CORE_PRECLAIM=y >>config_linux
> echo CONFIG_SND_PCM_OSS_PLUGINS=y >>config_linux
> echo CONFIG_SND_HRTIMER=m >>config_linux
> echo CONFIG_SND_DYNAMIC_MINORS=n >>config_linux
> echo CONFIG_SND_SUPPORT_OLD_API=y >>config_linux
> echo CONFIG_SND_VERBOSE_PROCFS=y >>config_linux
> echo CONFIG_SND_DRIVERS=y >>config_linux
> echo CONFIG_SND_PCSP=m >>config_linux
> echo CONFIG_SND_ALOOP=m >>config_linux
> echo CONFIG_SND_MTS64=m >>config_linux
> echo CONFIG_SND_PORTMAN2X4=m >>config_linux
> echo CONFIG_SND_AC97_POWER_SAVE=n >>config_linux
> echo CONFIG_SND_ISA=y >>config_linux
> echo CONFIG_SND_ADLIB=m >>config_linux
> echo CONFIG_SND_AZT1605=m >>config_linux
> echo CONFIG_SND_AZT2316=m >>config_linux
> echo CONFIG_SND_SC6000=m >>config_linux
> echo CONFIG_SND_JAZZ16=m >>config_linux
> echo CONFIG_SND_MIRO=m >>config_linux
> echo CONFIG_SND_MSND_PINNACLE=m >>config_linux
> echo CONFIG_SND_MSND_CLASSIC=m >>config_linux
> echo CONFIG_SND_PCI=y >>config_linux
> echo CONFIG_SND_AD1889=m >>config_linux
> echo CONFIG_SND_ALS300=m >>config_linux
> echo CONFIG_SND_ASIHPI=m >>config_linux
> echo CONFIG_SND_ATIIXP=m >>config_linux
> echo CONFIG_SND_ATIIXP_MODEM=m >>config_linux
> echo CONFIG_SND_AU8810=m >>config_linux
> echo CONFIG_SND_AU8820=m >>config_linux
> echo CONFIG_SND_AU8830=m >>config_linux
> echo CONFIG_SND_AW2=m >>config_linux
> echo CONFIG_SND_BT87X_OVERCLOCK=n >>config_linux
> echo CONFIG_SND_CA0106=m >>config_linux
> echo CONFIG_SND_OXYGEN=m >>config_linux
> echo CONFIG_SND_CS5530=m >>config_linux
> echo CONFIG_SND_CS5535AUDIO=m >>config_linux
> echo CONFIG_SND_CTXFI=m >>config_linux
> echo CONFIG_SND_DARLA20=m >>config_linux
> echo CONFIG_SND_GINA20=m >>config_linux
> echo CONFIG_SND_LAYLA20=m >>config_linux
> echo CONFIG_SND_DARLA24=m >>config_linux
> echo CONFIG_SND_GINA24=m >>config_linux
> echo CONFIG_SND_LAYLA24=m >>config_linux
> echo CONFIG_SND_MONA=m >>config_linux
> echo CONFIG_SND_MIA=m >>config_linux
> echo CONFIG_SND_ECHO3G=m >>config_linux
> echo CONFIG_SND_INDIGO=m >>config_linux
> echo CONFIG_SND_INDIGOIO=m >>config_linux
> echo CONFIG_SND_INDIGODJ=m >>config_linux
> echo CONFIG_SND_INDIGOIOX=m >>config_linux
> echo CONFIG_SND_INDIGODJX=m >>config_linux
> echo CONFIG_SND_EMU10K1X=m >>config_linux
> echo CONFIG_SND_ES1968_INPUT=n >>config_linux
> echo CONFIG_SND_HDA_INTEL=m >>config_linux
> echo CONFIG_SND_HDSPM=m >>config_linux
> echo CONFIG_SND_INTEL8X0M=m >>config_linux
> echo CONFIG_SND_LOLA=m >>config_linux
> echo CONFIG_SND_LX6464ES=m >>config_linux
> echo CONFIG_SND_MAESTRO3_INPUT=n >>config_linux
> echo CONFIG_SND_MIXART=m >>config_linux
> echo CONFIG_SND_PCXHR=m >>config_linux
> echo CONFIG_SND_RIPTIDE=m >>config_linux
> echo CONFIG_SND_SIS7019=m >>config_linux
> echo CONFIG_SND_VIA82XX_MODEM=m >>config_linux
> echo CONFIG_SND_VIRTUOSO=m >>config_linux
> echo CONFIG_SND_SPI=y >>config_linux
> echo CONFIG_SND_USB=y >>config_linux
> echo CONFIG_SND_USB_UA101=m >>config_linux
> echo CONFIG_SND_USB_USX2Y=m >>config_linux
> echo CONFIG_SND_USB_CAIAQ=m >>config_linux
> echo CONFIG_SND_USB_US122L=m >>config_linux
> echo CONFIG_SND_USB_6FIRE=m >>config_linux
> echo CONFIG_SND_FIREWIRE=y >>config_linux
> echo CONFIG_SND_FIREWIRE_SPEAKERS=m >>config_linux
> echo CONFIG_SND_ISIGHT=m >>config_linux
> echo CONFIG_SND_PCMCIA=y >>config_linux
> echo CONFIG_SND_PDAUDIOCF=m >>config_linux
> echo CONFIG_SND_SOC=m >>config_linux
> echo CONFIG_HID_PRODIKEYS=m >>config_linux
> echo CONFIG_SND_SEQ_HRTIMER_DEFAULT=y >>config_linux
> echo CONFIG_SND_HDA_HWDEP=n >>config_linux
> echo CONFIG_SND_HDA_INPUT_BEEP=n >>config_linux
> echo CONFIG_SND_HDA_INPUT_JACK=n >>config_linux
> echo CONFIG_SND_HDA_PATCH_LOADER=n >>config_linux
> echo CONFIG_SND_HDA_CODEC_REALTEK=y >>config_linux
> echo CONFIG_SND_HDA_CODEC_ANALOG=y >>config_linux
> echo CONFIG_SND_HDA_CODEC_SIGMATEL=y >>config_linux
> echo CONFIG_SND_HDA_CODEC_VIA=y >>config_linux
> echo CONFIG_SND_HDA_CODEC_HDMI=y >>config_linux
> echo CONFIG_SND_HDA_CODEC_CIRRUS=y >>config_linux
> echo CONFIG_SND_HDA_CODEC_CONEXANT=y >>config_linux
> echo CONFIG_SND_HDA_CODEC_CA0110=y >>config_linux
> echo CONFIG_SND_HDA_CODEC_CMEDIA=y >>config_linux
> echo CONFIG_SND_HDA_CODEC_SI3054=y >>config_linux
> echo CONFIG_SND_HDA_GENERIC=y >>config_linux
> echo CONFIG_SND_HDA_POWER_SAVE=n >>config_linux
> echo CONFIG_SND_USB_CAIAQ_INPUT=n >>config_linux
> echo CONFIG_SND_SOC_CACHE_LZO=n >>config_linux
> echo CONFIG_SND_SOC_ALL_CODECS=m >>config_linux

Next days I will try in testing environment. And will compile without Asterisk 
with switched grsec on.

Regards

Andrzej Odyniec

Hello,

I uploaded a new DL testing version to the FTP server.
The main change is the 3.0 Kernel.

Please let report any issues.

-- 

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

DONE

-- 

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

> -----Original Message-----
> From: Andrzej Odyniec [mailto:an...@ma...]
> Sent: Friday, September 02, 2011 1:52 PM
> To: dev...@li...
> Subject: Re: [Devil-linux-develop] DL memcached compiling problem
> 
> Heiko,
> 
> I wrote:
> > but... new dar has in /usr/share unusually long name, so now
> > bootcd.iso isn't built... only squashfs.
> 
> In default config DL builds bootcd.iso correctly. But if there is long
file name in
> tree, mkisofs stops with message:
> 
> > Creating the CD iso image, /build/tmp/bootcd.iso...
> > Warning: creating filesystem that does not conform to ISO-9660.
> > Warning: using transparent compression. This is a nonstandard Rock Ridge
> >          extension. The resulting filesystem can only be transparently
> >          read on Linux. On other operating systems you need to call
> >          mkzftree by hand to decompress the files.
> > mkisofs: Error:
> >
> ./usr/share/dar/html/classlibdar_1_1crit__in__place__data__more__recen
> > t__or__equal__to-members.html and
> >
> ./usr/share/dar/html/classlibdar_1_1crit__in__place__data__more__recen
> > t__or__equal__to.html have the same Joliet name
> > mkisofs: Joliet file names differ after 65 chars
> > mkisofs: Try to use the option -joliet-long
> > mkisofs: Joliet tree sort failed.
> 
> This happened for me, because asterisk needs doxygen and I appended
> doxygen to compilation. This doxygen was detected by dar and used, so in
> /usr/share/dar doxygen created documentation in files with unusually long
> filenames.
> 
> Appending suggested -joliet-long option to mkisofs call solves problem.
> Maybe tomorrow this will touch the standard DL compilation?
> 
> Best Regards
> 
> Andrzej Odyniec
> 
>
----------------------------------------------------------------------------
--
> Special Offer -- Download ArcSight Logger for FREE!
> Finally, a world-class log management solution at an even better
price-free!
> And you'll get a free "Love Thy Logs" t-shirt when you download Logger.
> Secure your free ArcSight Logger TODAY!
> http://p.sf.net/sfu/arcsisghtdev2dev
> _______________________________________________
> Devil-linux-develop mailing list
> Dev...@li...
> https://lists.sourceforge.net/lists/listinfo/devil-linux-develop

All,

 

I uploaded the current CVS version of DL into the testing directory.

ftp://ftp.devil-linux.org/pub/devel/testing/

 

-- 

 

Regards

   Heiko Zuerker

    <http://www.devil-linux.org> http://www.devil-linux.org

 

Heiko,

I wrote:
> but... new dar has in /usr/share unusually long name, so now bootcd.iso isn't 
> built... only squashfs.

In default config DL builds bootcd.iso correctly. But if there is long file 
name in tree, mkisofs stops with message:

> Creating the CD iso image, /build/tmp/bootcd.iso...
> Warning: creating filesystem that does not conform to ISO-9660.
> Warning: using transparent compression. This is a nonstandard Rock Ridge
>          extension. The resulting filesystem can only be transparently
>          read on Linux. On other operating systems you need to call
>          mkzftree by hand to decompress the files.
> mkisofs: Error: ./usr/share/dar/html/classlibdar_1_1crit__in__place__data__more__recent__or__equal__to-members.html and ./usr/share/dar/html/classlibdar_1_1crit__in__place__data__more__recent__or__equal__to.html have the same Joliet name
> mkisofs: Joliet file names differ after 65 chars
> mkisofs: Try to use the option -joliet-long
> mkisofs: Joliet tree sort failed.

This happened for me, because asterisk needs doxygen and I appended doxygen to 
compilation. This doxygen was detected by dar and used, so in /usr/share/dar 
doxygen created documentation in files with unusually long filenames.

Appending suggested -joliet-long option to mkisofs call solves problem.
Maybe tomorrow this will touch the standard DL compilation?

Best Regards

Andrzej Odyniec

I wrote:
> but... new dar has in /usr/share unusually long name, so now bootcd.iso isn't 
> built... only squashfs.

Sorry for the alarm; with default configuration there is no above effect. 
Only, when I compile DL with asterisk, so I must check process again. I will 
report results.

Regards

Andrzej Odyniec

Heiko Zuerker wrote:
> I uploaded the latest memcached version and a couple of other changes  
> to the FTP server.
> The compile should now work.

Thanks Heiko,

but... new dar has in /usr/share unusually long name, so now bootcd.iso isn't 
built... only squashfs.

Regards

Andrzej Odyniec

I uploaded the latest memcached version and a couple of other changes  
to the FTP server.
The compile should now work.

Heiko

Quoting Heiko Zuerker <he...@zu...>:

> Hi,
>
> I can reproduce the memcached compile problem.
> I'm currently working on updating all the software versions and the
> new memcached seems to compile fine.
>
> It'll be a few days until I'm done with this, then I'll upload the new
> sources.
>
> --
>
> Regards
>    Heiko Zuerker
>    http://www.devil-linux.org
>
>
>
> ------------------------------------------------------------------------------
> EMC VNX: the world's simplest storage, starting under $10K
> The only unified storage solution that offers unified management
> Up to 160% more powerful than alternatives and 25% more efficient.
> Guaranteed. http://p.sf.net/sfu/emc-vnx-dev2dev
> _______________________________________________
> Devil-linux-develop mailing list
> Dev...@li...
> https://lists.sourceforge.net/lists/listinfo/devil-linux-develop


-- 

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

Hi,

I can reproduce the memcached compile problem.
I'm currently working on updating all the software versions and the  
new memcached seems to compile fine.

It'll be a few days until I'm done with this, then I'll upload the new  
sources.

-- 

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

Hi Heiko,

> Are you using the default configuration?

Yes. After encountering problem I always try with fresh environment and default configuration
without mods.

The only, I not tried, is downloading all sources again. I get sources from my side copy and after
I'm doing ./update_src, but I tried with separately downloaded memcached again. And side copies of
sources are used two on two separate machines.

> I kicked off a fresh compile, to see if I can reproduce the issue.

I reproduced issue every time and on two separate machines. This memcached version assume IOV_MAX
as 1024 only if system has defined __FreeBSD__ or __APPLE__, else IOV_MAX should be defined. But
it seems that the symbol IOV_MAX in relation to the version of June/July has been stolen from
place, where memcached searched it or some tricky defs are inactive now. Maybe this is because one
of upgraded packages? So I borrowed definition from /usr/include/bits/stdio_lim.h where it is
present.

Sorry that I did not comparation analysis betwen versions from June/July and current, but I'm on
vacation and from my village I have very slow Internet access - I'm controlling compiling machines
via SSH only.

Best regards

Andrzej Odyniec

Hi,

Sorry for the late response, I was out on vacation.
Are you using the default configuration?
I kicked off a fresh compile, to see if I can reproduce the issue.

-- 

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


> -----Original Message-----
> From: Andrzej Odyniec [mailto:an...@ma...]
> Sent: Wednesday, August 17, 2011 8:38 PM
> To: dev...@li...
> Subject: [Devil-linux-develop] DL memcached compiling problem
> 
> Dears,
> 
> Build stops in memcached.
> 
> Exactly IOV_MAX in not defined. Probably this definition was moved from
> limits.h to bits/stdio_lim.h but in memcached.c is limits.h included
> 
> Change of header file name in #include solved problem
> 
> There are waits for new kernel symbols (two or three) in prepare too.
> 
> Tested especially on fresh build environment.
> My base system is as usually last myself built DL (w/o grsec etc).
> 
> Regards
> 
> Andrzej Odyniec
> 
>
----------------------------------------------------------------------------
--
> Get a FREE DOWNLOAD! and learn more about uberSVN rich system, user
> administration capabilities and model configuration. Take the hassle out
of
> deploying and managing Subversion and the tools developers use with it.
> http://p.sf.net/sfu/wandisco-d2d-2
> _______________________________________________
> Devil-linux-develop mailing list
> Dev...@li...
> https://lists.sourceforge.net/lists/listinfo/devil-linux-develop

Dears,

Build stops in memcached.

Exactly IOV_MAX in not defined. Probably this definition was moved from 
limits.h to bits/stdio_lim.h but in memcached.c is limits.h included

Change of header file name in #include solved problem

There are waits for new kernel symbols (two or three) in prepare too.

Tested especially on fresh build environment.
My base system is as usually last myself built DL (w/o grsec etc).

Regards

Andrzej Odyniec

Heiko,

Thank you!

Serge

On 07/06/2011 08:16 AM, Heiko Zuerker wrote:
> The file is uploading and will be available 30 minutes after I sent
> this email.
>
> ftp://ftp.devil-linux.org/pub/devel/sources/lfssystem-for-DL-1.5/
>
> Heiko
>
> Quoting Heiko Zuerker<he...@zu...>:
>
>> Completely forgot, there's a new lfssystem for DL 1.5.
>> I'll upload it to the FTP server.
>>
>> Heiko
>>
>> Quoting Heiko Zuerker<he...@zu...>:
>>
>>> Hey,
>>>
>>> Below are some commands from the buildroot mailinglist, which I used
>>> initially to figure out how this git thing works.
>>> If you didn't use git before then I'm sure there will be questions, so
>>> feel free to ask.
>>>
>>> This is the URL you'll need to use:
>>> ssh://username@devil-linux.git.sourceforge.net/gitroot/devil-linux/devil-linux
>>> of course replace username with your SF username.
>>>
>>> Here's some additional documentation:
>>> http://sourceforge.net/scm/?type=git&group_id=34096
>>>
>>> You find the DL specific stuff under target/devil-linux.
>>> There's also a default DL config under config/ which will compile a
>>> working x86_64 version.
>>>
>>> There are quite a few buildroot specific things if you want to add new
>>> scripts. A lot of information can be found here:
>>> http://buildroot.uclibc.org/
>>> I usually send any non-DL specific changes to buildroot, so they can
>>> incorporate it. They're quite picky about what goes in and the quality
>>> of the script (the 2nd one being a good thing).
>>>
>>> Heiko
>>>
>>> ----- Forwarded message from Thomas Petazzoni
>>> <tho...@fr...>  -----
>>>      Date: Sun, 5 Dec 2010 09:17:24 +0100
>>>      From: Thomas Petazzoni<tho...@fr...>
>>> Subject: [Buildroot] How to contribute to Buildroot with Git
>>>        To: bui...@bu...
>>>
>>> On Sat, 4 Dec 2010 16:09:00 -0800 (PST)
>>> Justin Mark<oi...@ya...>  wrote:
>>>
>>>> I can build libgee with buildroot in my workspace, how should I
>>>> submit the patch for review? post the patch here or directly do it
>>>> from git? Can someone give me some details since I don't know much
>>>> about git?
>>>
>>> The best is to use Git. Here is a simplified version of the Git workflow
>>> that I use to work with Buildroot:
>>>
>>>    1) Clone (to be done only once)
>>>
>>>       git clone git://git.busybox.net/buildroot
>>>
>>>    2) Configure Git (to be done only once)
>>>
>>>       Then tell git who you are :
>>>
>>>       git config --global user.name "Firstname Lastname"
>>>       git config --global user.email fir...@so...
>>>
>>>       And tell git how to send emails :
>>>
>>>       git config --global sendemail.smtpserver mysmtpserver
>>>
>>>       And to avoid chained reply :
>>>
>>>       git config --global sendemail.chainreplyto false
>>>
>>>    3) Create a branch to work on your topic (to be done for every
>>>       separate topic you'd like to work with)
>>>
>>>       git checkout -b mytopic
>>>
>>>       Note that this also switches immediatly to the new 'mytopic'
>>>       branch. You can run 'git branch' at any time to know on which
>>>       branch you are.
>>>
>>>    4) Make some modifications, for one particuler subtopic (like adding
>>>       the vala compiler)
>>>
>>>    5) Commit those modifications
>>>
>>>       git commit -s -a
>>>
>>>       And enter an appropriate commit log.
>>>
>>>       If you created new files, add them with "git add".
>>>
>>>       Then go back to step 4 for the other changes you want to do, or
>>>       proceed to step 6 if you're done with your changes.
>>>
>>>    6) Review your changes
>>>
>>>       git log -p master..
>>>
>>>    7) Prepare patches for your changes
>>>
>>>       git format-patch HEAD
>>>
>>>       This will generate a set of 000X-*.patch files in the Buildroot
>>>       directory
>>>
>>>    8) Send your patches to the list
>>>
>>>       git send-email --to bui...@uc... --compose *.patch
>>>
>>> And you're done.
>>>
>>> If while reviewing your commits you find that you need to merge some of
>>> them (because you did some mistakes that you fixed later and you don't
>>> want the world to know about your mistakes), then you have to use the
>>> rebasing feature of git:
>>>
>>>       git rebase -i master
>>>
>>> Git will open up a text editor with the list of your commits. You can
>>> edit this file to change the order of the commits, or to change the
>>> action taken on a particular commit (see the file itself for
>>> documentation on those actions). A typical thing is :
>>>
>>>       pick SOMEGITHASH package: add foobar
>>>       pick SOMEGITHASH package: add barfoo
>>>       pick SOMEGITHASH I did something wrong in add foobar, merge me
>>>
>>> So obviously you want the last commit to be merged into the first one,
>>> so that nobody knows you did some mistakes during your development. So,
>>> turn those three lines into the following ones:
>>>
>>>       pick SOMEGITHASH package: add foobar
>>>       fixup SOMEGITHASH I did something wrong in add foobar, merge me
>>>       pick SOMEGITHASH package: add barfoo
>>>
>>> And exit the text editor. Git will reorganize your commits, and you'll
>>> end up with just two commits.
>>>
>>> Don't hesitate to ask questions if you have issues,
>>>
>>> Thomas
>>> --
>>> Thomas Petazzoni, Free Electrons
>>> Kernel, drivers, real-time and embedded Linux
>>> development, consulting, training and support.
>>> http://free-electrons.com
>>> _______________________________________________
>>> buildroot mailing list
>>> bui...@bu...
>>> http://lists.busybox.net/mailman/listinfo/buildroot
>>>
>>> ----- End forwarded message -----
>>>
>>> --
>>>
>>> Regards
>>>     Heiko Zuerker
>>>     http://www.devil-linux.org
>>>
>>> Quoting Serge Leschinsky<ser...@gm...>:
>>>
>>>> Hi,
>>>>
>>>> It looks like I missed instruction/howto for DL git repo. I don't post the
>>>> changes very often of course, but anyway -  I wouldn?t like to
>>>> bother Heiko with
>>>> tracking and resubmitting those changes. If you know where I can find the
>>>> manual, please let me know.
>>>>
>>>>
>>>> Thanks,
>>>> Serge
>>>>
>>>> ------------------------------------------------------------------------------
>>>> All of the data generated in your IT infrastructure is seriously valuable.
>>>> Why? It contains a definitive record of application performance, security
>>>> threats, fraudulent activity, and more. Splunk takes this data and makes
>>>> sense of it. IT sense. And common sense.
>>>> http://p.sf.net/sfu/splunk-d2d-c2
>>>> _______________________________________________
>>>> Devil-linux-develop mailing list
>>>> Dev...@li...
>>>> https://lists.sourceforge.net/lists/listinfo/devil-linux-develop
>>>
>>>
>>> --
>>>
>>> Regards
>>>     Heiko Zuerker
>>>     http://www.devil-linux.org
>>>
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> All of the data generated in your IT infrastructure is seriously valuable.
>>> Why? It contains a definitive record of application performance, security
>>> threats, fraudulent activity, and more. Splunk takes this data and makes
>>> sense of it. IT sense. And common sense.
>>> http://p.sf.net/sfu/splunk-d2d-c2
>>> _______________________________________________
>>> Devil-linux-develop mailing list
>>> Dev...@li...
>>> https://lists.sourceforge.net/lists/listinfo/devil-linux-develop
>>
>>
>> --
>>
>> Regards
>>     Heiko Zuerker
>>     http://www.devil-linux.org
>>
>>
>>
>> ------------------------------------------------------------------------------
>> All of the data generated in your IT infrastructure is seriously valuable.
>> Why? It contains a definitive record of application performance, security
>> threats, fraudulent activity, and more. Splunk takes this data and makes
>> sense of it. IT sense. And common sense.
>> http://p.sf.net/sfu/splunk-d2d-c2
>> _______________________________________________
>> Devil-linux-develop mailing list
>> Dev...@li...
>> https://lists.sourceforge.net/lists/listinfo/devil-linux-develop
>
>

The file is uploading and will be available 30 minutes after I sent   
this email.

ftp://ftp.devil-linux.org/pub/devel/sources/lfssystem-for-DL-1.5/

Heiko

Quoting Heiko Zuerker <he...@zu...>:

> Completely forgot, there's a new lfssystem for DL 1.5.
> I'll upload it to the FTP server.
>
> Heiko
>
> Quoting Heiko Zuerker <he...@zu...>:
>
>> Hey,
>>
>> Below are some commands from the buildroot mailinglist, which I used
>> initially to figure out how this git thing works.
>> If you didn't use git before then I'm sure there will be questions, so
>> feel free to ask.
>>
>> This is the URL you'll need to use:
>> ssh://username@devil-linux.git.sourceforge.net/gitroot/devil-linux/devil-linux
>> of course replace username with your SF username.
>>
>> Here's some additional documentation:
>> http://sourceforge.net/scm/?type=git&group_id=34096
>>
>> You find the DL specific stuff under target/devil-linux.
>> There's also a default DL config under config/ which will compile a
>> working x86_64 version.
>>
>> There are quite a few buildroot specific things if you want to add new
>> scripts. A lot of information can be found here:
>> http://buildroot.uclibc.org/
>> I usually send any non-DL specific changes to buildroot, so they can
>> incorporate it. They're quite picky about what goes in and the quality
>> of the script (the 2nd one being a good thing).
>>
>> Heiko
>>
>> ----- Forwarded message from Thomas Petazzoni
>> <tho...@fr...> -----
>>     Date: Sun, 5 Dec 2010 09:17:24 +0100
>>     From: Thomas Petazzoni <tho...@fr...>
>> Subject: [Buildroot] How to contribute to Buildroot with Git
>>       To: bui...@bu...
>>
>> On Sat, 4 Dec 2010 16:09:00 -0800 (PST)
>> Justin Mark <oi...@ya...> wrote:
>>
>>> I can build libgee with buildroot in my workspace, how should I
>>> submit the patch for review? post the patch here or directly do it
>>> from git? Can someone give me some details since I don't know much
>>> about git?
>>
>> The best is to use Git. Here is a simplified version of the Git workflow
>> that I use to work with Buildroot:
>>
>>   1) Clone (to be done only once)
>>
>>      git clone git://git.busybox.net/buildroot
>>
>>   2) Configure Git (to be done only once)
>>
>>      Then tell git who you are :
>>
>>      git config --global user.name "Firstname Lastname"
>>      git config --global user.email fir...@so...
>>
>>      And tell git how to send emails :
>>
>>      git config --global sendemail.smtpserver mysmtpserver
>>
>>      And to avoid chained reply :
>>
>>      git config --global sendemail.chainreplyto false
>>
>>   3) Create a branch to work on your topic (to be done for every
>>      separate topic you'd like to work with)
>>
>>      git checkout -b mytopic
>>
>>      Note that this also switches immediatly to the new 'mytopic'
>>      branch. You can run 'git branch' at any time to know on which
>>      branch you are.
>>
>>   4) Make some modifications, for one particuler subtopic (like adding
>>      the vala compiler)
>>
>>   5) Commit those modifications
>>
>>      git commit -s -a
>>
>>      And enter an appropriate commit log.
>>
>>      If you created new files, add them with "git add".
>>
>>      Then go back to step 4 for the other changes you want to do, or
>>      proceed to step 6 if you're done with your changes.
>>
>>   6) Review your changes
>>
>>      git log -p master..
>>
>>   7) Prepare patches for your changes
>>
>>      git format-patch HEAD
>>
>>      This will generate a set of 000X-*.patch files in the Buildroot
>>      directory
>>
>>   8) Send your patches to the list
>>
>>      git send-email --to bui...@uc... --compose *.patch
>>
>> And you're done.
>>
>> If while reviewing your commits you find that you need to merge some of
>> them (because you did some mistakes that you fixed later and you don't
>> want the world to know about your mistakes), then you have to use the
>> rebasing feature of git:
>>
>>      git rebase -i master
>>
>> Git will open up a text editor with the list of your commits. You can
>> edit this file to change the order of the commits, or to change the
>> action taken on a particular commit (see the file itself for
>> documentation on those actions). A typical thing is :
>>
>>      pick SOMEGITHASH package: add foobar
>>      pick SOMEGITHASH package: add barfoo
>>      pick SOMEGITHASH I did something wrong in add foobar, merge me
>>
>> So obviously you want the last commit to be merged into the first one,
>> so that nobody knows you did some mistakes during your development. So,
>> turn those three lines into the following ones:
>>
>>      pick SOMEGITHASH package: add foobar
>>      fixup SOMEGITHASH I did something wrong in add foobar, merge me
>>      pick SOMEGITHASH package: add barfoo
>>
>> And exit the text editor. Git will reorganize your commits, and you'll
>> end up with just two commits.
>>
>> Don't hesitate to ask questions if you have issues,
>>
>> Thomas
>> --
>> Thomas Petazzoni, Free Electrons
>> Kernel, drivers, real-time and embedded Linux
>> development, consulting, training and support.
>> http://free-electrons.com
>> _______________________________________________
>> buildroot mailing list
>> bui...@bu...
>> http://lists.busybox.net/mailman/listinfo/buildroot
>>
>> ----- End forwarded message -----
>>
>> --
>>
>> Regards
>>    Heiko Zuerker
>>    http://www.devil-linux.org
>>
>> Quoting Serge Leschinsky <ser...@gm...>:
>>
>>> Hi,
>>>
>>> It looks like I missed instruction/howto for DL git repo. I don't post the
>>> changes very often of course, but anyway -  I wouldn?t like to
>>> bother Heiko with
>>> tracking and resubmitting those changes. If you know where I can find the
>>> manual, please let me know.
>>>
>>>
>>> Thanks,
>>> Serge
>>>
>>> ------------------------------------------------------------------------------
>>> All of the data generated in your IT infrastructure is seriously valuable.
>>> Why? It contains a definitive record of application performance, security
>>> threats, fraudulent activity, and more. Splunk takes this data and makes
>>> sense of it. IT sense. And common sense.
>>> http://p.sf.net/sfu/splunk-d2d-c2
>>> _______________________________________________
>>> Devil-linux-develop mailing list
>>> Dev...@li...
>>> https://lists.sourceforge.net/lists/listinfo/devil-linux-develop
>>
>>
>> --
>>
>> Regards
>>    Heiko Zuerker
>>    http://www.devil-linux.org
>>
>>
>>
>> ------------------------------------------------------------------------------
>> All of the data generated in your IT infrastructure is seriously valuable.
>> Why? It contains a definitive record of application performance, security
>> threats, fraudulent activity, and more. Splunk takes this data and makes
>> sense of it. IT sense. And common sense.
>> http://p.sf.net/sfu/splunk-d2d-c2
>> _______________________________________________
>> Devil-linux-develop mailing list
>> Dev...@li...
>> https://lists.sourceforge.net/lists/listinfo/devil-linux-develop
>
>
> --
>
> Regards
>    Heiko Zuerker
>    http://www.devil-linux.org
>
>
>
> ------------------------------------------------------------------------------
> All of the data generated in your IT infrastructure is seriously valuable.
> Why? It contains a definitive record of application performance, security
> threats, fraudulent activity, and more. Splunk takes this data and makes
> sense of it. IT sense. And common sense.
> http://p.sf.net/sfu/splunk-d2d-c2
> _______________________________________________
> Devil-linux-develop mailing list
> Dev...@li...
> https://lists.sourceforge.net/lists/listinfo/devil-linux-develop


-- 

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