Menu
▾
▴
devil-linux-develop
|
From: Andrzej O. <an...@ma...> - 2014-11-10 17:29:15
|
Dear Heiko, Since my attempts with backport encountered some problems, especially in the context of grsec, I wanted to ask you about the plans for the transition to the 3.14 kernel line - whether and, if so, when are you planning to upgrade? Maybe my efforts are completely unnecessary? Ready-backports does not compile with kernel 3.2.63 patched grsec smoothly. The least problems give backports of 3.10 if only for iwlwifi wireless. If successful, also would require source code analysis. Meanwhile, the line is 3.14 has grsec from some time and seems is selected to be the successor to the kernel line 3.2. I suspect that only you Could upgrade D-L to the kernel line 3.14 --- unless it requires a change in the compiler, and probably changes in the build environment. That's why I thought to ask you about the plans. Best regards -- Andrzej Odyniec |
|
From: Heiko Z. <he...@zu...> - 2014-11-21 13:37:18
|
Andrzej, Sorry for the late answer. I have currently no plans to upgrade the Kernel. Being on the latest Kernel has historically caused us some grief with the kernel patches. That's why we're currently using the "stable long-term" kernel. I didn't realize that 3.14 is a new long-term kernel and I agree that we should try to switch to that. Anybody should be able to replace the Kernel. The initial fun is with the main kernel config, then the additional patches. We should also make a decision on which Kernel patches we actually want to keep in the distro. Some of the problematic ones might not even be used anymore by anybody. I'd say replace it and see what happens. ;-) Heiko Quoting Andrzej Odyniec <an...@ma...>: > Dear Heiko, > > Since my attempts with backport encountered some problems, especially in the > context of grsec, I wanted to ask you about the plans for the transition to > the 3.14 kernel line - whether and, if so, when are you planning to upgrade? > Maybe my efforts are completely unnecessary? > > Ready-backports does not compile with kernel 3.2.63 patched grsec smoothly. > The least problems give backports of 3.10 if only for iwlwifi wireless. If > successful, also would require source code analysis. > > Meanwhile, the line is 3.14 has grsec from some time and seems is selected to > be the successor to the kernel line 3.2. > > I suspect that only you Could upgrade D-L to the kernel line 3.14 --- unless > it requires a change in the compiler, and probably changes in the build > environment. > > That's why I thought to ask you about the plans. > > Best regards > > -- > Andrzej Odyniec > > ------------------------------------------------------------------------------ > _______________________________________________ > Devil-linux-develop mailing list > Dev...@li... > https://lists.sourceforge.net/lists/listinfo/devil-linux-develop -- Regards Heiko Zuerker |
|
From: Andrzej O. <an...@ma...> - 2014-12-03 17:25:56
|
Heiko, I started to try, although I had recently a lot of other activities. - We need to update aufs3, because the old is not compiling with 3.14 kernel - Keepalived, even this with git, do not want to compile with 3.14 so turned it off for now - Motion, including the one with svn, do not want to compile, so too turned it off for now too - Iptables must be raised to 1.4.21 - Unfortunately, gcc 4.4.5 is not sufficient because it does not support plug-ins, so as for now I raised gcc to 4.5.1; Of course I had to pick up a gcc-hardened; I took hardened patches from lfs; maybe I should raise gcc higher? - Kernel needs now to build bc, so I installed 1.06 In spite of this kernel build process stopped at aufs3; anything goes wrong and I have a little read about aufs; perhaps my manual controlled prepare for aufs3 did not properly. So kernel line upgrade is not so simple. But I do not resign Best regards Andrzej Odyniec --- Ta wiadomość została sprawdzona na obecność wirusów przez oprogramowanie antywirusowe Avast. http://www.avast.com |
|
From: Heiko Z. <he...@zu...> - 2014-12-03 18:44:31
|
Andrzej, That's the same trouble I usually have to go through when we upgrade the kernel. In regards to GCC, let's go to the highest possible that still compiles our sources. You'll find there will be some incompatibilities too. Hang in there! Heiko Quoting Andrzej Odyniec <an...@ma...>: > Heiko, > > I started to try, although I had recently a lot of other activities. > - We need to update aufs3, because the old is not compiling with 3.14 kernel > - Keepalived, even this with git, do not want to compile with 3.14 so turned > it off for now > - Motion, including the one with svn, do not want to compile, so too > turned it > off for now too > - Iptables must be raised to 1.4.21 > - Unfortunately, gcc 4.4.5 is not sufficient because it does not support > plug-ins, so as for now I raised gcc to 4.5.1; Of course I had to pick up a > gcc-hardened; I took hardened patches from lfs; maybe I should raise > gcc higher? > - Kernel needs now to build bc, so I installed 1.06 > > In spite of this kernel build process stopped at aufs3; anything goes wrong > and I have a little read about aufs; perhaps my manual controlled prepare for > aufs3 did not properly. > > So kernel line upgrade is not so simple. But I do not resign > > Best regards > > Andrzej Odyniec > > --- > Ta wiadomość została sprawdzona na obecność wirusów przez > oprogramowanie antywirusowe Avast. > http://www.avast.com > > > ------------------------------------------------------------------------------ > Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server > from Actuate! Instantly Supercharge Your Business Reports and Dashboards > with Interactivity, Sharing, Native Excel Exports, App Integration & more > Get technology previously reserved for billion-dollar corporations, FREE > http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk > _______________________________________________ > Devil-linux-develop mailing list > Dev...@li... > https://lists.sourceforge.net/lists/listinfo/devil-linux-develop -- Regards Heiko Zuerker |
|
From: Serge L. <ser...@gm...> - 2014-12-04 18:13:51
|
Hi Andrzej,
works for me, x86_64 only.
> GNU C Library (GNU libc) stable release version 2.19, by Roland McGrath et al.
...
> Compiled by GNU CC version 4.8.3.
> Compiled on a Linux 3.14.17 system on 2014-08-15.
aufs has the following structure:
root:/data/build/tmp/aufs# ls -1 ../aufs/
aufs-util
aufs3-standalone
scripts:
scripts/prepare
...
build )
...
if [ "$CONFIG_ETCFS" = "AUFS" ]; then
echo "Patching AUFS"
if [ ! -f $KERNELDIR/.done_aufs_patch ]; then
AUFSDIR=$(find_src_dir aufs)
patch -d $KERNELDIR -p1 -i
${AUFSDIR}/aufs3-standalone/aufs3-kbuild.patch || exit 1
patch -d $KERNELDIR -p1 -i
${AUFSDIR}/aufs3-standalone/aufs3-base.patch || exit 1
patch -d $KERNELDIR -p1 -i
${AUFSDIR}/aufs3-standalone/aufs3-mmap.patch || exit 1
patch -d $KERNELDIR -p1 -i
${AUFSDIR}/aufs3-standalone/aufs3-standalone.patch || exit 1
rm -f ${AUFSDIR}/aufs3-standalone/include/linux/Kbuild
rm -f ${AUFSDIR}/aufs3-standalone/include/uapi/linux/Kbuild
cp -dpvR ${AUFSDIR}/aufs3-standalone/{fs,Documentation,include}
$KERNELDIR/ || exit 1
touch $KERNELDIR/.done_aufs_patch
fi
set_kernel_option CONFIG_AUFS_FS m
set_kernel_option CONFIG_AUFS_HINOTIFY n
set_kernel_option CONFIG_AUFS_HNOTIFY y
set_kernel_option CONFIG_AUFS_BRANCH_MAX_127 y
set_kernel_option CONFIG_AUFS_BRANCH_MAX_511 n
set_kernel_option CONFIG_AUFS_BRANCH_MAX_1023 n
set_kernel_option CONFIG_AUFS_BRANCH_MAX_32767 n
set_kernel_option CONFIG_AUFS_SBILIST y
set_kernel_option CONFIG_AUFS_EXPORT n
set_kernel_option CONFIG_AUFS_BR_RAMFS n
set_kernel_option CONFIG_AUFS_SHWH n
set_kernel_option CONFIG_AUFS_RDU n
set_kernel_option CONFIG_AUFS_PROC_MAP n
set_kernel_option CONFIG_AUFS_SP_IATTR n
set_kernel_option CONFIG_AUFS_SHWH n
set_kernel_option CONFIG_AUFS_BR_RAMFS n
set_kernel_option CONFIG_AUFS_DEBUG n
set_kernel_option CONFIG_AUFS_HFSNOTIFY y
fi
and scripts/aufs :
build )
if [ "$CONFIG_ETCFS" = "AUFS" ]; then
#fix me
replace_str $KERNELDIR/include/uapi/linux/aufs_type.h
"__user" " "
cd aufs-util || exit 1
CPPFLAGS="-I $KERNELDIR/usr/include
-I../aufs2-standalone/include" make KDIR=$KERNELDIR all || exit 1
fi
;;
install )
if [ "$CONFIG_ETCFS" = "AUFS" ]; then
cp -dpvR aufs-util/aufs.5 $CDDIR/usr/share/man/man5/ || exit 1
cd aufs-util || exit 1
mkdir -p $TMPDIR/{sbin,usr/bin} || exit 1
mkdir -p $TMPDIR/etc/default || exit 1
make KDIR=$KERNELDIR DESTDIR=$TMPDIR install || exit 1
cp -dpvR $TMPDIR/etc/* $ETCDIR/etc/ || exit 1
rm -rf $TMPDIR/etc || exit 1
cp -dpvR $TMPDIR/* $CDDIR/ || exit 1
rm -rf $TMPDIR || exit 1
fi
;;
Thanks,
Serge
On 12/03/2014 09:25 AM, Andrzej Odyniec wrote:
> Heiko,
>
> I started to try, although I had recently a lot of other activities.
> - We need to update aufs3, because the old is not compiling with 3.14 kernel
> - Keepalived, even this with git, do not want to compile with 3.14 so turned
> it off for now
> - Motion, including the one with svn, do not want to compile, so too turned it
> off for now too
> - Iptables must be raised to 1.4.21
> - Unfortunately, gcc 4.4.5 is not sufficient because it does not support
> plug-ins, so as for now I raised gcc to 4.5.1; Of course I had to pick up a
> gcc-hardened; I took hardened patches from lfs; maybe I should raise gcc higher?
> - Kernel needs now to build bc, so I installed 1.06
>
> In spite of this kernel build process stopped at aufs3; anything goes wrong
> and I have a little read about aufs; perhaps my manual controlled prepare for
> aufs3 did not properly.
>
> So kernel line upgrade is not so simple. But I do not resign
>
> Best regards
>
> Andrzej Odyniec
>
> ---
> Ta wiadomość została sprawdzona na obecność wirusów przez oprogramowanie antywirusowe Avast.
> http://www.avast.com
>
>
> ------------------------------------------------------------------------------
> Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
> from Actuate! Instantly Supercharge Your Business Reports and Dashboards
> with Interactivity, Sharing, Native Excel Exports, App Integration & more
> Get technology previously reserved for billion-dollar corporations, FREE
> http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk
> _______________________________________________
> Devil-linux-develop mailing list
> Dev...@li...
> https://lists.sourceforge.net/lists/listinfo/devil-linux-develop
>
|
|
From: Andrzej O. <an...@ma...> - 2014-12-06 02:59:00
|
Dear Serge,
Thanks for scripts. I modified my. I try to make full automated DL-build with
new kernel. And after try with kernel alone I upgraded gcc sources and started
again full build. But now some packages before linux kernel are not compiling
probably because of loader. So now I upgraded binutils and try again. I think,
I will need many tries. But I don't resign.
Yours
Andrzej Odyniec
W dniu 2014-12-04 o 19:13, Serge Leschinsky pisze:
> Hi Andrzej,
>
> works for me, x86_64 only.
>
> > GNU C Library (GNU libc) stable release version 2.19, by Roland McGrath et al.
> ...
> > Compiled by GNU CC version 4.8.3.
> > Compiled on a Linux 3.14.17 system on 2014-08-15.
>
>
> aufs has the following structure:
>
> root:/data/build/tmp/aufs# ls -1 ../aufs/
> aufs-util
> aufs3-standalone
>
>
> scripts:
>
> scripts/prepare
> ...
> build )
> ...
> if [ "$CONFIG_ETCFS" = "AUFS" ]; then
> echo "Patching AUFS"
> if [ ! -f $KERNELDIR/.done_aufs_patch ]; then
> AUFSDIR=$(find_src_dir aufs)
> patch -d $KERNELDIR -p1 -i
> ${AUFSDIR}/aufs3-standalone/aufs3-kbuild.patch || exit 1
> patch -d $KERNELDIR -p1 -i
> ${AUFSDIR}/aufs3-standalone/aufs3-base.patch || exit 1
> patch -d $KERNELDIR -p1 -i
> ${AUFSDIR}/aufs3-standalone/aufs3-mmap.patch || exit 1
> patch -d $KERNELDIR -p1 -i
> ${AUFSDIR}/aufs3-standalone/aufs3-standalone.patch || exit 1
> rm -f ${AUFSDIR}/aufs3-standalone/include/linux/Kbuild
> rm -f ${AUFSDIR}/aufs3-standalone/include/uapi/linux/Kbuild
> cp -dpvR ${AUFSDIR}/aufs3-standalone/{fs,Documentation,include}
> $KERNELDIR/ || exit 1
> touch $KERNELDIR/.done_aufs_patch
> fi
>
> set_kernel_option CONFIG_AUFS_FS m
> set_kernel_option CONFIG_AUFS_HINOTIFY n
> set_kernel_option CONFIG_AUFS_HNOTIFY y
> set_kernel_option CONFIG_AUFS_BRANCH_MAX_127 y
> set_kernel_option CONFIG_AUFS_BRANCH_MAX_511 n
> set_kernel_option CONFIG_AUFS_BRANCH_MAX_1023 n
> set_kernel_option CONFIG_AUFS_BRANCH_MAX_32767 n
> set_kernel_option CONFIG_AUFS_SBILIST y
> set_kernel_option CONFIG_AUFS_EXPORT n
> set_kernel_option CONFIG_AUFS_BR_RAMFS n
> set_kernel_option CONFIG_AUFS_SHWH n
> set_kernel_option CONFIG_AUFS_RDU n
> set_kernel_option CONFIG_AUFS_PROC_MAP n
> set_kernel_option CONFIG_AUFS_SP_IATTR n
> set_kernel_option CONFIG_AUFS_SHWH n
> set_kernel_option CONFIG_AUFS_BR_RAMFS n
> set_kernel_option CONFIG_AUFS_DEBUG n
> set_kernel_option CONFIG_AUFS_HFSNOTIFY y
> fi
>
>
> and scripts/aufs :
>
> build )
> if [ "$CONFIG_ETCFS" = "AUFS" ]; then
> #fix me
> replace_str $KERNELDIR/include/uapi/linux/aufs_type.h
> "__user" ""
> cd aufs-util || exit 1
> CPPFLAGS="-I $KERNELDIR/usr/include
> -I../aufs2-standalone/include" make KDIR=$KERNELDIR all || exit 1
> fi
> ;;
>
> install )
> if [ "$CONFIG_ETCFS" = "AUFS" ]; then
> cp -dpvR aufs-util/aufs.5 $CDDIR/usr/share/man/man5/ || exit 1
> cd aufs-util || exit 1
> mkdir -p $TMPDIR/{sbin,usr/bin} || exit 1
> mkdir -p $TMPDIR/etc/default || exit 1
> make KDIR=$KERNELDIR DESTDIR=$TMPDIR install || exit 1
> cp -dpvR $TMPDIR/etc/* $ETCDIR/etc/ || exit 1
> rm -rf $TMPDIR/etc || exit 1
> cp -dpvR $TMPDIR/* $CDDIR/ || exit 1
> rm -rf $TMPDIR || exit 1
> fi
> ;;
>
> Thanks,
> Serge
--
Andrzej Odyniec
|
|
From: Heiko Z. <he...@zu...> - 2014-12-10 13:48:00
|
Andrzej,
I don't recall, but is it possible that I actually removed the
"--fatal-warnings" from the patch?
Can you compare with the original version from the LFS website?
I don't think it makes sense to modify every package. Actually the
right approach would be to find/create patches that will correct the
compiler warnings and replace the less secure code. But that's a lot
of work...
Heiko
Quoting Andrzej Odyniec <an...@ma...>:
> Dear All,
>
> After several attempts with different combinations, it appears that at the
> beginning I will build D-L with kernel 3.14 using gcc-4.5.3. And here I need
> your opinion please.
>
> Fpie-1 patch to 4.4.5 contains the default setting -no-fatal-warning and the
> same lfs patch to 4.5.3 no longer provides the default setting for this
> option(s). So compilation (linking) stops on tmpnam, mktemp or
> textrel warnings.
>
> What would you have suggested: Setting the option -no-fatal-warnings or
> --no-warn-shared-textrel in every script, which will crash gcc-4.5.3
> compilation patched using existing lfs patches or doing myself a patch to the
> default setting of these options, as it was with gcc-4.4.5?
>
> Regards
>
> Andrzej Odyniec
>
>
> Serge Leschinsky wrote:
>> Hi Andrzej,
>>
>> works for me, x86_64 only.
>>
>> > GNU C Library (GNU libc) stable release version 2.19, by Roland
>> McGrath et al.
>> ...
>> > Compiled by GNU CC version 4.8.3.
>> > Compiled on a Linux 3.14.17 system on 2014-08-15.
>>
>>
>> aufs has the following structure:
>>
>> root:/data/build/tmp/aufs# ls -1 ../aufs/
>> aufs-util
>> aufs3-standalone
>>
>>
>> scripts:
>>
>> scripts/prepare
>> ...
>> build )
>> ...
>> if [ "$CONFIG_ETCFS" = "AUFS" ]; then
>> echo "Patching AUFS"
>> if [ ! -f $KERNELDIR/.done_aufs_patch ]; then
>> AUFSDIR=$(find_src_dir aufs)
>> patch -d $KERNELDIR -p1 -i
>> ${AUFSDIR}/aufs3-standalone/aufs3-kbuild.patch || exit 1
>> patch -d $KERNELDIR -p1 -i
>> ${AUFSDIR}/aufs3-standalone/aufs3-base.patch || exit 1
>> patch -d $KERNELDIR -p1 -i
>> ${AUFSDIR}/aufs3-standalone/aufs3-mmap.patch || exit 1
>> patch -d $KERNELDIR -p1 -i
>> ${AUFSDIR}/aufs3-standalone/aufs3-standalone.patch || exit 1
>> rm -f ${AUFSDIR}/aufs3-standalone/include/linux/Kbuild
>> rm -f ${AUFSDIR}/aufs3-standalone/include/uapi/linux/Kbuild
>> cp -dpvR
>> ${AUFSDIR}/aufs3-standalone/{fs,Documentation,include}
>> $KERNELDIR/ || exit 1
>> touch $KERNELDIR/.done_aufs_patch
>> fi
>>
>> set_kernel_option CONFIG_AUFS_FS m
>> set_kernel_option CONFIG_AUFS_HINOTIFY n
>> set_kernel_option CONFIG_AUFS_HNOTIFY y
>> set_kernel_option CONFIG_AUFS_BRANCH_MAX_127 y
>> set_kernel_option CONFIG_AUFS_BRANCH_MAX_511 n
>> set_kernel_option CONFIG_AUFS_BRANCH_MAX_1023 n
>> set_kernel_option CONFIG_AUFS_BRANCH_MAX_32767 n
>> set_kernel_option CONFIG_AUFS_SBILIST y
>> set_kernel_option CONFIG_AUFS_EXPORT n
>> set_kernel_option CONFIG_AUFS_BR_RAMFS n
>> set_kernel_option CONFIG_AUFS_SHWH n
>> set_kernel_option CONFIG_AUFS_RDU n
>> set_kernel_option CONFIG_AUFS_PROC_MAP n
>> set_kernel_option CONFIG_AUFS_SP_IATTR n
>> set_kernel_option CONFIG_AUFS_SHWH n
>> set_kernel_option CONFIG_AUFS_BR_RAMFS n
>> set_kernel_option CONFIG_AUFS_DEBUG n
>> set_kernel_option CONFIG_AUFS_HFSNOTIFY y
>> fi
>>
>>
>> and scripts/aufs :
>>
>> build )
>> if [ "$CONFIG_ETCFS" = "AUFS" ]; then
>> #fix me
>> replace_str $KERNELDIR/include/uapi/linux/aufs_type.h
>> "__user" " "
>> cd aufs-util || exit 1
>> CPPFLAGS="-I $KERNELDIR/usr/include
>> -I../aufs2-standalone/include" make KDIR=$KERNELDIR all || exit 1
>> fi
>> ;;
>>
>> install )
>> if [ "$CONFIG_ETCFS" = "AUFS" ]; then
>> cp -dpvR aufs-util/aufs.5
>> $CDDIR/usr/share/man/man5/ || exit 1
>> cd aufs-util || exit 1
>> mkdir -p $TMPDIR/{sbin,usr/bin} || exit 1
>> mkdir -p $TMPDIR/etc/default || exit 1
>> make KDIR=$KERNELDIR DESTDIR=$TMPDIR install || exit 1
>> cp -dpvR $TMPDIR/etc/* $ETCDIR/etc/ || exit 1
>> rm -rf $TMPDIR/etc || exit 1
>> cp -dpvR $TMPDIR/* $CDDIR/ || exit 1
>> rm -rf $TMPDIR || exit 1
>> fi
>> ;;
>>
>> Thanks,
>> Serge
>>
>>
>> On 12/03/2014 09:25 AM, Andrzej Odyniec wrote:
>>
>>> Heiko,
>>>
>>> I started to try, although I had recently a lot of other activities.
>>> - We need to update aufs3, because the old is not compiling with
>>> 3.14 kernel
>>> - Keepalived, even this with git, do not want to compile with 3.14
>>> so turned
>>> it off for now
>>> - Motion, including the one with svn, do not want to compile, so
>>> too turned it
>>> off for now too
>>> - Iptables must be raised to 1.4.21
>>> - Unfortunately, gcc 4.4.5 is not sufficient because it does not support
>>> plug-ins, so as for now I raised gcc to 4.5.1; Of course I had to pick up a
>>> gcc-hardened; I took hardened patches from lfs; maybe I should
>>> raise gcc higher?
>>> - Kernel needs now to build bc, so I installed 1.06
>>>
>>> In spite of this kernel build process stopped at aufs3; anything goes wrong
>>> and I have a little read about aufs; perhaps my manual controlled
>>> prepare for
>>> aufs3 did not properly.
>>>
>>> So kernel line upgrade is not so simple. But I do not resign
>>>
>>> Best regards
>>>
>>> Andrzej Odyniec
>>>
>>> ---
>>> Ta wiadomość została sprawdzona na obecność wirusów przez
>>> oprogramowanie antywirusowe Avast.
>>> http://www.avast.com
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
>>> from Actuate! Instantly Supercharge Your Business Reports and Dashboards
>>> with Interactivity, Sharing, Native Excel Exports, App Integration & more
>>> Get technology previously reserved for billion-dollar corporations, FREE
>>> http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk
>>> _______________________________________________
>>> Devil-linux-develop mailing list
>>> Dev...@li...
>>> https://lists.sourceforge.net/lists/listinfo/devil-linux-develop
>>>
>>
>>
>>
>> ------------------------------------------------------------------------------
>> Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
>> from Actuate! Instantly Supercharge Your Business Reports and Dashboards
>> with Interactivity, Sharing, Native Excel Exports, App Integration & more
>> Get technology previously reserved for billion-dollar corporations, FREE
>> http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk
>> _______________________________________________
>> Devil-linux-develop mailing list
>> Dev...@li...
>> https://lists.sourceforge.net/lists/listinfo/devil-linux-develop
>
>
> --
> 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
>
> ---
> Ta wiadomość została sprawdzona na obecność wirusów przez
> oprogramowanie antywirusowe Avast.
> http://www.avast.com
>
>
> ------------------------------------------------------------------------------
> Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
> from Actuate! Instantly Supercharge Your Business Reports and Dashboards
> with Interactivity, Sharing, Native Excel Exports, App Integration & more
> Get technology previously reserved for billion-dollar corporations, FREE
> http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk
> _______________________________________________
> Devil-linux-develop mailing list
> Dev...@li...
> https://lists.sourceforge.net/lists/listinfo/devil-linux-develop
--
Regards
Heiko Zuerker
|
|
From: Heiko Z. <he...@zu...> - 2015-01-17 22:20:54
|
Andrzej,
Looks like our hand is going to be forced and we need to move to the
newer kernel.
Unfortunately AUFS doesn't work anymore with the latest 3.2 kernel and
it's not supported anymore for those versions....
Heiko
Quoting Heiko Zuerker <he...@zu...>:
> Sounds good.
>
> Heiko
>
> Quoting Andrzej Odyniec <an...@ma...>:
>
>> Heiko Zuerker wrote:
>>> Andrzej,
>>>
>>> I don't recall, but is it possible that I actually removed the
>>> "--fatal-warnings" from the patch?
>>> Can you compare with the original version from the LFS website?
>>
>> Heiko, you don't. This situation is in original lfs patches. I
>> think, this is
>> policy decision of Robert Connolly at lfs. In this same patch at 4.5.1 and
>> 4.5.3 he added intentionally in gcc.c line:
>> + %{!no-fatal-warnings:--fatal-warnings} "
>>
>> So this is current policy. And generally: proper decision.
>>
>>> I don't think it makes sense to modify every package. Actually the
>>> right approach would be to find/create patches that will correct the
>>> compiler warnings and replace the less secure code. But that's a lot
>>> of work...
>>
>> Yes, this is lot of work. Some packages can be upgraded to version without
>> this warnings. But i.e. gzip is not corrected from old times. So there is
>> needed patch in gcc or CC="gcc -no-fatal-warnings" in the script.
>>
>> For first time I will use modified myself pie patch at 4.5.3 for find other
>> problems. After I will try to do statistics about packages generating
>> warnings. And after I will report this. We will think, what is better.
>>
>> Regards
>>
>> --
>> Andrzej Odyniec
--
Regards
Heiko Zuerker
|
|
From: Andrzej O. <an...@ma...> - 2014-12-10 13:23:18
|
Dear All,
After several attempts with different combinations, it appears that at the
beginning I will build D-L with kernel 3.14 using gcc-4.5.3. And here I need
your opinion please.
Fpie-1 patch to 4.4.5 contains the default setting -no-fatal-warning and the
same lfs patch to 4.5.3 no longer provides the default setting for this
option(s). So compilation (linking) stops on tmpnam, mktemp or textrel warnings.
What would you have suggested: Setting the option -no-fatal-warnings or
--no-warn-shared-textrel in every script, which will crash gcc-4.5.3
compilation patched using existing lfs patches or doing myself a patch to the
default setting of these options, as it was with gcc-4.4.5?
Regards
Andrzej Odyniec
Serge Leschinsky wrote:
> Hi Andrzej,
>
> works for me, x86_64 only.
>
> > GNU C Library (GNU libc) stable release version 2.19, by Roland McGrath et al.
> ...
> > Compiled by GNU CC version 4.8.3.
> > Compiled on a Linux 3.14.17 system on 2014-08-15.
>
>
> aufs has the following structure:
>
> root:/data/build/tmp/aufs# ls -1 ../aufs/
> aufs-util
> aufs3-standalone
>
>
> scripts:
>
> scripts/prepare
> ...
> build )
> ...
> if [ "$CONFIG_ETCFS" = "AUFS" ]; then
> echo "Patching AUFS"
> if [ ! -f $KERNELDIR/.done_aufs_patch ]; then
> AUFSDIR=$(find_src_dir aufs)
> patch -d $KERNELDIR -p1 -i
> ${AUFSDIR}/aufs3-standalone/aufs3-kbuild.patch || exit 1
> patch -d $KERNELDIR -p1 -i
> ${AUFSDIR}/aufs3-standalone/aufs3-base.patch || exit 1
> patch -d $KERNELDIR -p1 -i
> ${AUFSDIR}/aufs3-standalone/aufs3-mmap.patch || exit 1
> patch -d $KERNELDIR -p1 -i
> ${AUFSDIR}/aufs3-standalone/aufs3-standalone.patch || exit 1
> rm -f ${AUFSDIR}/aufs3-standalone/include/linux/Kbuild
> rm -f ${AUFSDIR}/aufs3-standalone/include/uapi/linux/Kbuild
> cp -dpvR ${AUFSDIR}/aufs3-standalone/{fs,Documentation,include}
> $KERNELDIR/ || exit 1
> touch $KERNELDIR/.done_aufs_patch
> fi
>
> set_kernel_option CONFIG_AUFS_FS m
> set_kernel_option CONFIG_AUFS_HINOTIFY n
> set_kernel_option CONFIG_AUFS_HNOTIFY y
> set_kernel_option CONFIG_AUFS_BRANCH_MAX_127 y
> set_kernel_option CONFIG_AUFS_BRANCH_MAX_511 n
> set_kernel_option CONFIG_AUFS_BRANCH_MAX_1023 n
> set_kernel_option CONFIG_AUFS_BRANCH_MAX_32767 n
> set_kernel_option CONFIG_AUFS_SBILIST y
> set_kernel_option CONFIG_AUFS_EXPORT n
> set_kernel_option CONFIG_AUFS_BR_RAMFS n
> set_kernel_option CONFIG_AUFS_SHWH n
> set_kernel_option CONFIG_AUFS_RDU n
> set_kernel_option CONFIG_AUFS_PROC_MAP n
> set_kernel_option CONFIG_AUFS_SP_IATTR n
> set_kernel_option CONFIG_AUFS_SHWH n
> set_kernel_option CONFIG_AUFS_BR_RAMFS n
> set_kernel_option CONFIG_AUFS_DEBUG n
> set_kernel_option CONFIG_AUFS_HFSNOTIFY y
> fi
>
>
> and scripts/aufs :
>
> build )
> if [ "$CONFIG_ETCFS" = "AUFS" ]; then
> #fix me
> replace_str $KERNELDIR/include/uapi/linux/aufs_type.h
> "__user" " "
> cd aufs-util || exit 1
> CPPFLAGS="-I $KERNELDIR/usr/include
> -I../aufs2-standalone/include" make KDIR=$KERNELDIR all || exit 1
> fi
> ;;
>
> install )
> if [ "$CONFIG_ETCFS" = "AUFS" ]; then
> cp -dpvR aufs-util/aufs.5 $CDDIR/usr/share/man/man5/ || exit 1
> cd aufs-util || exit 1
> mkdir -p $TMPDIR/{sbin,usr/bin} || exit 1
> mkdir -p $TMPDIR/etc/default || exit 1
> make KDIR=$KERNELDIR DESTDIR=$TMPDIR install || exit 1
> cp -dpvR $TMPDIR/etc/* $ETCDIR/etc/ || exit 1
> rm -rf $TMPDIR/etc || exit 1
> cp -dpvR $TMPDIR/* $CDDIR/ || exit 1
> rm -rf $TMPDIR || exit 1
> fi
> ;;
>
> Thanks,
> Serge
>
>
> On 12/03/2014 09:25 AM, Andrzej Odyniec wrote:
>
>>Heiko,
>>
>>I started to try, although I had recently a lot of other activities.
>>- We need to update aufs3, because the old is not compiling with 3.14 kernel
>>- Keepalived, even this with git, do not want to compile with 3.14 so turned
>>it off for now
>>- Motion, including the one with svn, do not want to compile, so too turned it
>>off for now too
>>- Iptables must be raised to 1.4.21
>>- Unfortunately, gcc 4.4.5 is not sufficient because it does not support
>>plug-ins, so as for now I raised gcc to 4.5.1; Of course I had to pick up a
>>gcc-hardened; I took hardened patches from lfs; maybe I should raise gcc higher?
>>- Kernel needs now to build bc, so I installed 1.06
>>
>>In spite of this kernel build process stopped at aufs3; anything goes wrong
>>and I have a little read about aufs; perhaps my manual controlled prepare for
>>aufs3 did not properly.
>>
>>So kernel line upgrade is not so simple. But I do not resign
>>
>>Best regards
>>
>>Andrzej Odyniec
>>
>>---
>>Ta wiadomość została sprawdzona na obecność wirusów przez oprogramowanie antywirusowe Avast.
>>http://www.avast.com
>>
>>
>>------------------------------------------------------------------------------
>>Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
>>from Actuate! Instantly Supercharge Your Business Reports and Dashboards
>>with Interactivity, Sharing, Native Excel Exports, App Integration & more
>>Get technology previously reserved for billion-dollar corporations, FREE
>>http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk
>>_______________________________________________
>>Devil-linux-develop mailing list
>>Dev...@li...
>>https://lists.sourceforge.net/lists/listinfo/devil-linux-develop
>>
>
>
>
> ------------------------------------------------------------------------------
> Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
> from Actuate! Instantly Supercharge Your Business Reports and Dashboards
> with Interactivity, Sharing, Native Excel Exports, App Integration & more
> Get technology previously reserved for billion-dollar corporations, FREE
> http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk
> _______________________________________________
> Devil-linux-develop mailing list
> Dev...@li...
> https://lists.sourceforge.net/lists/listinfo/devil-linux-develop
--
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
---
Ta wiadomość została sprawdzona na obecność wirusów przez oprogramowanie antywirusowe Avast.
http://www.avast.com
|
|
From: Andrzej O. <an...@ma...> - 2014-12-10 15:02:01
|
Heiko Zuerker wrote:
> Andrzej,
>
> I don't recall, but is it possible that I actually removed the
> "--fatal-warnings" from the patch?
> Can you compare with the original version from the LFS website?
Heiko, you don't. This situation is in original lfs patches. I think, this is
policy decision of Robert Connolly at lfs. In this same patch at 4.5.1 and
4.5.3 he added intentionally in gcc.c line:
+ %{!no-fatal-warnings:--fatal-warnings} "
So this is current policy. And generally: proper decision.
> I don't think it makes sense to modify every package. Actually the
> right approach would be to find/create patches that will correct the
> compiler warnings and replace the less secure code. But that's a lot
> of work...
Yes, this is lot of work. Some packages can be upgraded to version without
this warnings. But i.e. gzip is not corrected from old times. So there is
needed patch in gcc or CC="gcc -no-fatal-warnings" in the script.
For first time I will use modified myself pie patch at 4.5.3 for find other
problems. After I will try to do statistics about packages generating
warnings. And after I will report this. We will think, what is better.
Regards
--
Andrzej Odyniec
---
Ta wiadomość została sprawdzona na obecność wirusów przez oprogramowanie antywirusowe Avast.
http://www.avast.com
|
|
From: Heiko Z. <he...@zu...> - 2014-12-10 15:26:50
|
Sounds good.
Heiko
Quoting Andrzej Odyniec <an...@ma...>:
> Heiko Zuerker wrote:
>> Andrzej,
>>
>> I don't recall, but is it possible that I actually removed the
>> "--fatal-warnings" from the patch?
>> Can you compare with the original version from the LFS website?
>
> Heiko, you don't. This situation is in original lfs patches. I think, this is
> policy decision of Robert Connolly at lfs. In this same patch at 4.5.1 and
> 4.5.3 he added intentionally in gcc.c line:
> + %{!no-fatal-warnings:--fatal-warnings} "
>
> So this is current policy. And generally: proper decision.
>
>> I don't think it makes sense to modify every package. Actually the
>> right approach would be to find/create patches that will correct the
>> compiler warnings and replace the less secure code. But that's a lot
>> of work...
>
> Yes, this is lot of work. Some packages can be upgraded to version without
> this warnings. But i.e. gzip is not corrected from old times. So there is
> needed patch in gcc or CC="gcc -no-fatal-warnings" in the script.
>
> For first time I will use modified myself pie patch at 4.5.3 for find other
> problems. After I will try to do statistics about packages generating
> warnings. And after I will report this. We will think, what is better.
>
> Regards
>
> --
> Andrzej Odyniec
>
> ---
> Ta wiadomość została sprawdzona na obecność wirusów przez
> oprogramowanie antywirusowe Avast.
> http://www.avast.com
>
>
> ------------------------------------------------------------------------------
> Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
> from Actuate! Instantly Supercharge Your Business Reports and Dashboards
> with Interactivity, Sharing, Native Excel Exports, App Integration & more
> Get technology previously reserved for billion-dollar corporations, FREE
> http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk
> _______________________________________________
> Devil-linux-develop mailing list
> Dev...@li...
> https://lists.sourceforge.net/lists/listinfo/devil-linux-develop
--
Regards
Heiko Zuerker
|
|
From: Andrzej O. <an...@ma...> - 2015-01-19 19:50:31
|
Heiko Zuerker wrote:
> Andrzej,
>
> Looks like our hand is going to be forced and we need to move to the
> newer kernel.
>
> Unfortunately AUFS doesn't work anymore with the latest 3.2 kernel and
> it's not supported anymore for those versions....
Heiko,
But AUFS is in colission with grsec in three files. Because of this I can't
compile kernel with grsec. This stopped me temporarily. But I think about
source analysis. In recent months I've been busy at work and in the family.
Some grandchildren grow up and the other is born. Already 14 :) So I planned
to read collisional sources for about two weeks. Mayby you will be faster?
Near all rest was compiling using gcc 4.5.3 patched for fpie-1 and nonfatal
warning. All I did is:
%{nonow:-z lazy;:-z now} }}\
%{!no-fatal-warnings:--fatal-warnings} "
instead
%{nonow:-z lazy;:-z now} }}"
in fpie-1 patch.
But as I said -- grsec kernel is not compiling because of colision with aufs.
Andrzej
---
Ta wiadomość została sprawdzona na obecność wirusów przez oprogramowanie antywirusowe Avast.
http://www.avast.com
|
|
From: Heiko Z. <he...@zu...> - 2015-01-20 14:18:27
|
Andrzej,
I'm not sure how much time I'll have myself. Family is the priority
(and work of course), no question about that. But Devil-Linux should
come right behind that! ;-)
Looks like the aufs mmap patch is supposed to solve the issue with the
3.2 kernel, but this one collides with grsecurity. Is it the same
issue for the kernel you've been working on?
My plan was to see if I can modify the 3.2 mmap patch to work
grsecurity. That should be the quickest. Switching to a new Kernel
takes a lot of testing, that's why I don't want to rush that one.
Heiko
Quoting Andrzej Odyniec <an...@ma...>:
> Heiko Zuerker wrote:
>> Andrzej,
>>
>> Looks like our hand is going to be forced and we need to move to the
>> newer kernel.
>>
>> Unfortunately AUFS doesn't work anymore with the latest 3.2 kernel and
>> it's not supported anymore for those versions....
>
> Heiko,
>
> But AUFS is in colission with grsec in three files. Because of this I can't
> compile kernel with grsec. This stopped me temporarily. But I think about
> source analysis. In recent months I've been busy at work and in the family.
> Some grandchildren grow up and the other is born. Already 14 :) So I planned
> to read collisional sources for about two weeks. Mayby you will be faster?
>
> Near all rest was compiling using gcc 4.5.3 patched for fpie-1 and nonfatal
> warning. All I did is:
>
> %{nonow:-z lazy;:-z now} }}\
> %{!no-fatal-warnings:--fatal-warnings} "
>
> instead
>
> %{nonow:-z lazy;:-z now} }}"
>
> in fpie-1 patch.
>
> But as I said -- grsec kernel is not compiling because of colision with aufs.
>
> Andrzej
>
> ---
> Ta wiadomość została sprawdzona na obecność wirusów przez
> oprogramowanie antywirusowe Avast.
> http://www.avast.com
>
>
> ------------------------------------------------------------------------------
> New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
> GigeNET is offering a free month of service with a new server in Ashburn.
> Choose from 2 high performing configs, both with 100TB of bandwidth.
> Higher redundancy.Lower latency.Increased capacity.Completely compliant.
> http://p.sf.net/sfu/gigenet
> _______________________________________________
> Devil-linux-develop mailing list
> Dev...@li...
> https://lists.sourceforge.net/lists/listinfo/devil-linux-develop
--
Regards
Heiko Zuerker
|
|
From: Heiko Z. <he...@zu...> - 2015-01-22 02:54:54
|
Hey,
I changed a few things around in the build system, to help make our
life easier. (Not checked-in yet)
The grsecurity patch is now applied via the prepare script (like most
of the other kernel patches) and AUFS is applied right afterwards.
I was also able to modify the aufs-mmap patch for 3.2, to work with
grsecurity.
My compile is running, we'll see if it will finish. Hopefully I'll
have some time this weekend to test it...
Heiko
Quoting Heiko Zuerker <he...@zu...>:
> Andrzej,
>
> I'm not sure how much time I'll have myself. Family is the priority
> (and work of course), no question about that. But Devil-Linux should
> come right behind that! ;-)
>
> Looks like the aufs mmap patch is supposed to solve the issue with the
> 3.2 kernel, but this one collides with grsecurity. Is it the same
> issue for the kernel you've been working on?
> My plan was to see if I can modify the 3.2 mmap patch to work
> grsecurity. That should be the quickest. Switching to a new Kernel
> takes a lot of testing, that's why I don't want to rush that one.
>
> Heiko
>
> Quoting Andrzej Odyniec <an...@ma...>:
>
>> Heiko Zuerker wrote:
>>> Andrzej,
>>>
>>> Looks like our hand is going to be forced and we need to move to the
>>> newer kernel.
>>>
>>> Unfortunately AUFS doesn't work anymore with the latest 3.2 kernel and
>>> it's not supported anymore for those versions....
>>
>> Heiko,
>>
>> But AUFS is in colission with grsec in three files. Because of this I can't
>> compile kernel with grsec. This stopped me temporarily. But I think about
>> source analysis. In recent months I've been busy at work and in the family.
>> Some grandchildren grow up and the other is born. Already 14 :) So I planned
>> to read collisional sources for about two weeks. Mayby you will be faster?
>>
>> Near all rest was compiling using gcc 4.5.3 patched for fpie-1 and nonfatal
>> warning. All I did is:
>>
>> %{nonow:-z lazy;:-z now} }}\
>> %{!no-fatal-warnings:--fatal-warnings} "
>>
>> instead
>>
>> %{nonow:-z lazy;:-z now} }}"
>>
>> in fpie-1 patch.
>>
>> But as I said -- grsec kernel is not compiling because of colision
>> with aufs.
>>
>> Andrzej
>>
>> ---
>> Ta wiadomość została sprawdzona na obecność wirusów przez
>> oprogramowanie antywirusowe Avast.
>> http://www.avast.com
>>
>>
>> ------------------------------------------------------------------------------
>> New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
>> GigeNET is offering a free month of service with a new server in Ashburn.
>> Choose from 2 high performing configs, both with 100TB of bandwidth.
>> Higher redundancy.Lower latency.Increased capacity.Completely compliant.
>> http://p.sf.net/sfu/gigenet
>> _______________________________________________
>> Devil-linux-develop mailing list
>> Dev...@li...
>> https://lists.sourceforge.net/lists/listinfo/devil-linux-develop
>
>
>
> --
>
> Regards
> Heiko Zuerker
>
> ------------------------------------------------------------------------------
> New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
> GigeNET is offering a free month of service with a new server in Ashburn.
> Choose from 2 high performing configs, both with 100TB of bandwidth.
> Higher redundancy.Lower latency.Increased capacity.Completely compliant.
> http://p.sf.net/sfu/gigenet
> _______________________________________________
> Devil-linux-develop mailing list
> Dev...@li...
> https://lists.sourceforge.net/lists/listinfo/devil-linux-develop
--
Regards
Heiko Zuerker
|
|
From: Heiko Z. <he...@zu...> - 2015-08-15 13:07:33
|
Andrzej,
Could you please tarball the work you have done with the newer kernel,
so I can continue working on it?
I just saw that grsecurity will drop support for the 3.2 kernel series
by the end of the year. This means we'll have to upgrade to 3.14,
which is the latest long-term kernel version grsecurity supports.
Heiko
Quoting Heiko Zuerker <he...@zu...>:
> Hey,
>
> I changed a few things around in the build system, to help make our
> life easier. (Not checked-in yet)
> The grsecurity patch is now applied via the prepare script (like most
> of the other kernel patches) and AUFS is applied right afterwards.
> I was also able to modify the aufs-mmap patch for 3.2, to work with
> grsecurity.
> My compile is running, we'll see if it will finish. Hopefully I'll
> have some time this weekend to test it...
>
> Heiko
>
> Quoting Heiko Zuerker <he...@zu...>:
>
>> Andrzej,
>>
>> I'm not sure how much time I'll have myself. Family is the priority
>> (and work of course), no question about that. But Devil-Linux should
>> come right behind that! ;-)
>>
>> Looks like the aufs mmap patch is supposed to solve the issue with the
>> 3.2 kernel, but this one collides with grsecurity. Is it the same
>> issue for the kernel you've been working on?
>> My plan was to see if I can modify the 3.2 mmap patch to work
>> grsecurity. That should be the quickest. Switching to a new Kernel
>> takes a lot of testing, that's why I don't want to rush that one.
>>
>> Heiko
>>
>> Quoting Andrzej Odyniec <an...@ma...>:
>>
>>> Heiko Zuerker wrote:
>>>> Andrzej,
>>>>
>>>> Looks like our hand is going to be forced and we need to move to the
>>>> newer kernel.
>>>>
>>>> Unfortunately AUFS doesn't work anymore with the latest 3.2 kernel and
>>>> it's not supported anymore for those versions....
>>>
>>> Heiko,
>>>
>>> But AUFS is in colission with grsec in three files. Because of this I can't
>>> compile kernel with grsec. This stopped me temporarily. But I think about
>>> source analysis. In recent months I've been busy at work and in the family.
>>> Some grandchildren grow up and the other is born. Already 14 :) So
>>> I planned
>>> to read collisional sources for about two weeks. Mayby you will be faster?
>>>
>>> Near all rest was compiling using gcc 4.5.3 patched for fpie-1 and nonfatal
>>> warning. All I did is:
>>>
>>> %{nonow:-z lazy;:-z now} }}\
>>> %{!no-fatal-warnings:--fatal-warnings} "
>>>
>>> instead
>>>
>>> %{nonow:-z lazy;:-z now} }}"
>>>
>>> in fpie-1 patch.
>>>
>>> But as I said -- grsec kernel is not compiling because of colision
>>> with aufs.
>>>
>>> Andrzej
>>>
>>> ---
>>> Ta wiadomość została sprawdzona na obecność wirusów przez
>>> oprogramowanie antywirusowe Avast.
>>> http://www.avast.com
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
>>> GigeNET is offering a free month of service with a new server in Ashburn.
>>> Choose from 2 high performing configs, both with 100TB of bandwidth.
>>> Higher redundancy.Lower latency.Increased capacity.Completely compliant.
>>> http://p.sf.net/sfu/gigenet
>>> _______________________________________________
>>> Devil-linux-develop mailing list
>>> Dev...@li...
>>> https://lists.sourceforge.net/lists/listinfo/devil-linux-develop
>>
>>
>>
>> --
>>
>> Regards
>> Heiko Zuerker
>>
>> ------------------------------------------------------------------------------
>> New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
>> GigeNET is offering a free month of service with a new server in Ashburn.
>> Choose from 2 high performing configs, both with 100TB of bandwidth.
>> Higher redundancy.Lower latency.Increased capacity.Completely compliant.
>> http://p.sf.net/sfu/gigenet
>> _______________________________________________
>> Devil-linux-develop mailing list
>> Dev...@li...
>> https://lists.sourceforge.net/lists/listinfo/devil-linux-develop
>
>
>
> --
>
> Regards
> Heiko Zuerker
>
> ------------------------------------------------------------------------------
> New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
> GigeNET is offering a free month of service with a new server in Ashburn.
> Choose from 2 high performing configs, both with 100TB of bandwidth.
> Higher redundancy.Lower latency.Increased capacity.Completely compliant.
> http://p.sf.net/sfu/gigenet
> _______________________________________________
> Devil-linux-develop mailing list
> Dev...@li...
> https://lists.sourceforge.net/lists/listinfo/devil-linux-develop
--
Regards
Heiko Zuerker
|
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X