Menu
▾
▴
devil-linux-develop — developer discussions
You can subscribe to this list here.
| 2001 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(55) |
Oct
(44) |
Nov
(156) |
Dec
(123) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2002 |
Jan
(130) |
Feb
(156) |
Mar
(162) |
Apr
(171) |
May
(97) |
Jun
(127) |
Jul
(58) |
Aug
(81) |
Sep
(86) |
Oct
(45) |
Nov
(41) |
Dec
(84) |
| 2003 |
Jan
(71) |
Feb
(87) |
Mar
(133) |
Apr
(152) |
May
(151) |
Jun
(232) |
Jul
(320) |
Aug
(237) |
Sep
(271) |
Oct
(536) |
Nov
(301) |
Dec
(393) |
| 2004 |
Jan
(393) |
Feb
(184) |
Mar
(314) |
Apr
(225) |
May
(139) |
Jun
(77) |
Jul
(87) |
Aug
(75) |
Sep
(139) |
Oct
(50) |
Nov
(8) |
Dec
(28) |
| 2005 |
Jan
(66) |
Feb
(63) |
Mar
(14) |
Apr
(14) |
May
(8) |
Jun
(23) |
Jul
(21) |
Aug
(6) |
Sep
(29) |
Oct
(55) |
Nov
(38) |
Dec
(8) |
| 2006 |
Jan
(5) |
Feb
(10) |
Mar
(1) |
Apr
(15) |
May
(32) |
Jun
(44) |
Jul
(11) |
Aug
(8) |
Sep
(9) |
Oct
(14) |
Nov
(4) |
Dec
(3) |
| 2007 |
Jan
(3) |
Feb
(3) |
Mar
(2) |
Apr
|
May
|
Jun
|
Jul
(35) |
Aug
(49) |
Sep
(8) |
Oct
(42) |
Nov
(44) |
Dec
(7) |
| 2008 |
Jan
(2) |
Feb
(7) |
Mar
(8) |
Apr
(80) |
May
(74) |
Jun
(29) |
Jul
(5) |
Aug
(7) |
Sep
(6) |
Oct
(1) |
Nov
|
Dec
|
| 2009 |
Jan
(8) |
Feb
(19) |
Mar
(3) |
Apr
(24) |
May
(22) |
Jun
(23) |
Jul
(8) |
Aug
(23) |
Sep
(8) |
Oct
(27) |
Nov
(52) |
Dec
(27) |
| 2010 |
Jan
(36) |
Feb
(29) |
Mar
(17) |
Apr
(28) |
May
(21) |
Jun
(4) |
Jul
|
Aug
(28) |
Sep
(18) |
Oct
(6) |
Nov
(34) |
Dec
(16) |
| 2011 |
Jan
(18) |
Feb
(12) |
Mar
|
Apr
|
May
(9) |
Jun
(1) |
Jul
(5) |
Aug
(5) |
Sep
(7) |
Oct
(16) |
Nov
(26) |
Dec
(17) |
| 2012 |
Jan
(6) |
Feb
(34) |
Mar
(52) |
Apr
(10) |
May
(3) |
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
(4) |
Nov
(1) |
Dec
(4) |
| 2013 |
Jan
(5) |
Feb
|
Mar
|
Apr
(5) |
May
(4) |
Jun
|
Jul
|
Aug
(14) |
Sep
|
Oct
|
Nov
|
Dec
|
| 2014 |
Jan
|
Feb
(2) |
Mar
(5) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(3) |
Dec
(11) |
| 2015 |
Jan
(5) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(1) |
Sep
(1) |
Oct
(1) |
Nov
|
Dec
|
| 2016 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(2) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2017 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2018 |
Jan
(2) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Heiko Z. <he...@zu...> - 2013-05-04 13:31:29
|
A, Updated in CVS. Best Regards Heiko Zuerker -----Original Message----- From: Arnaud Gomes-do-Vale [mailto:Arn...@ir...] Sent: Tuesday, April 30, 2013 4:18 AM To: dev...@li... Subject: [Devil-linux-develop] [PATCH] Quagga 0.99.22 Hello, Another patch for upgrading Quagga to 0.99.22; we have hit a nasty bug in ospf6d from 0.99.20 which seems to have been fixed in 0.99.21. The source file is from <http://download.savannah.gnu.org/releases/quagga/quagga-0.99.22.tar.gz>. -- A |
|
From: Heiko Z. <he...@zu...> - 2013-05-04 13:24:58
|
Hello Arnaud, Before I add it, just a couple of questions: How's bird different from quagga? What's the benefit with having both in DL? Best Regards Heiko Zuerker -----Original Message----- From: Arnaud Gomes-do-Vale [mailto:Arn...@ir...] Sent: Tuesday, April 30, 2013 3:35 AM To: dev...@li... Subject: [Devil-linux-develop] [PATCH] BIRD routing daemon Hello, I have added support for the BIRD Internet Routing Daemon <http://bird.network.cz/> to DL. The patch is attached; the source tarball can be downloaded from <ftp://bird.network.cz/pub/bird/bird-1.3.9.tar.gz>. -- A |
|
From: Arnaud Gomes-do-V. <Arn...@ir...> - 2013-04-30 09:18:08
|
Hello, Another patch for upgrading Quagga to 0.99.22; we have hit a nasty bug in ospf6d from 0.99.20 which seems to have been fixed in 0.99.21. The source file is from <http://download.savannah.gnu.org/releases/quagga/quagga-0.99.22.tar.gz>. -- A |
|
From: Arnaud Gomes-do-V. <Arn...@ir...> - 2013-04-30 08:35:29
|
Hello, I have added support for the BIRD Internet Routing Daemon <http://bird.network.cz/> to DL. The patch is attached; the source tarball can be downloaded from <ftp://bird.network.cz/pub/bird/bird-1.3.9.tar.gz>. -- A |
|
From: Heiko Z. <he...@zu...> - 2013-04-25 12:19:47
|
Oliver, We haven't been doing any changes lately. Maybe something went wrong with your build? I'd start completely over with a "mrproper", just to make sure everything is okay. Heiko Quoting Serge Leschinsky <ser...@gm...>: > Hi Oliver, > > as far as I can see, the system image was not properly mounted so switch_root > fails. I'm a bit confused by "Permission denied" message - I'm not sure I > understand why you got it. I'd suggest unpacking initrd (because the problem > hides there) and double check init and other scripts for permissions etc. > > Sincerely, > Serge > > On 04/24/2013 06:01 AM, Oliver Niesner wrote: >> Hi, there! >> >> I have a problem with the recent CVS and booting. >> The make prepare build install iso commands went fine, but when i try >> too boot from the iso the kernel get panic. >> Has anyone an idea what went wrong and what i can do to prevent this? >> >> screenshot: >> >> http://centos.servebbs.org/pic/devil_panic.png >> >> Thx in advance, >> >> Oliver >> >> ------------------------------------------------------------------------------ >> Try New Relic Now & We'll Send You this Cool Shirt >> New Relic is the only SaaS-based application performance monitoring service >> that delivers powerful full stack analytics. Optimize and monitor your >> browser, app, & servers with just a few lines of code. Try New Relic >> and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_apr >> _______________________________________________ >> Devil-linux-develop mailing list >> Dev...@li... >> https://lists.sourceforge.net/lists/listinfo/devil-linux-develop >> > > > ------------------------------------------------------------------------------ > Try New Relic Now & We'll Send You this Cool Shirt > New Relic is the only SaaS-based application performance monitoring service > that delivers powerful full stack analytics. Optimize and monitor your > browser, app, & servers with just a few lines of code. Try New Relic > and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_apr > _______________________________________________ > Devil-linux-develop mailing list > Dev...@li... > https://lists.sourceforge.net/lists/listinfo/devil-linux-develop -- Regards Heiko Zuerker http://www.devil-linux.org |
|
From: Serge L. <ser...@gm...> - 2013-04-24 17:27:19
|
Hi Oliver, as far as I can see, the system image was not properly mounted so switch_root fails. I'm a bit confused by "Permission denied" message - I'm not sure I understand why you got it. I'd suggest unpacking initrd (because the problem hides there) and double check init and other scripts for permissions etc. Sincerely, Serge On 04/24/2013 06:01 AM, Oliver Niesner wrote: > Hi, there! > > I have a problem with the recent CVS and booting. > The make prepare build install iso commands went fine, but when i try > too boot from the iso the kernel get panic. > Has anyone an idea what went wrong and what i can do to prevent this? > > screenshot: > > http://centos.servebbs.org/pic/devil_panic.png > > Thx in advance, > > Oliver > > ------------------------------------------------------------------------------ > Try New Relic Now & We'll Send You this Cool Shirt > New Relic is the only SaaS-based application performance monitoring service > that delivers powerful full stack analytics. Optimize and monitor your > browser, app, & servers with just a few lines of code. Try New Relic > and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_apr > _______________________________________________ > Devil-linux-develop mailing list > Dev...@li... > https://lists.sourceforge.net/lists/listinfo/devil-linux-develop > |
|
From: Oliver N. <oli...@gm...> - 2013-04-24 13:01:47
|
Hi, there!
I have a problem with the recent CVS and booting.
The make prepare build install iso commands went fine, but when i try
too boot from the iso the kernel get panic.
Has anyone an idea what went wrong and what i can do to prevent this?
screenshot:
http://centos.servebbs.org/pic/devil_panic.png
Thx in advance,
Oliver
|
|
From: Heiko Z. <he...@zu...> - 2013-01-19 22:05:41
|
Philippe, I added the change to CVS, it will be included in any future builds. Best Regards Heiko Zuerker -----Original Message----- From: Philippe Weill [mailto:phi...@la...] Sent: Friday, January 18, 2013 10:35 AM To: dev...@li... Subject: [Devil-linux-develop] request for quagga multipath option hello everybody thanks for all your work since so many years I'm working on a new version of our firewall and we need to have quagga with multipath option active ( equal path routing ) I think this is something that could be enable by default on devil this is just a compile time option --enable-multipath=64 ( package in rhel6,debian and mageia have this option by default ) Thanks in advance -- Weill Philippe - Administrateur Systeme et Reseaux CNRS/UPMC/IPSL LATMOS (UMR 8190) Tour 45/46 3e Etage B302 - 4 Place Jussieu - 75252 Paris Cedex 05 - FRANCE Email:phi...@la... | tel:+33 0144274759 Fax:+33 0144273776 ---------------------------------------------------------------------------- -- Master HTML5, CSS3, ASP.NET, MVC, AJAX, Knockout.js, Web API and much more. Get web development skills now with LearnDevNow - 350+ hours of step-by-step video tutorials by Microsoft MVPs and experts. SALE $99.99 this month only -- learn more at: http://p.sf.net/sfu/learnmore_122812 _______________________________________________ Devil-linux-develop mailing list Dev...@li... https://lists.sourceforge.net/lists/listinfo/devil-linux-develop |
|
From: Philippe W. <phi...@la...> - 2013-01-18 17:26:45
|
hello everybody thanks for all your work since so many years I'm working on a new version of our firewall and we need to have quagga with multipath option active ( equal path routing ) I think this is something that could be enable by default on devil this is just a compile time option --enable-multipath=64 ( package in rhel6,debian and mageia have this option by default ) Thanks in advance -- Weill Philippe - Administrateur Systeme et Reseaux CNRS/UPMC/IPSL LATMOS (UMR 8190) Tour 45/46 3e Etage B302 - 4 Place Jussieu - 75252 Paris Cedex 05 - FRANCE Email:phi...@la... | tel:+33 0144274759 Fax:+33 0144273776 |
|
From: Andrzej O. <an...@ma...> - 2013-01-10 13:27:45
|
Dear Serge, > grub2 is a part of this system, so EFI boot should not be a problem. > The only issue with submitting all this stuff back in DL source control > is backward compatibility which I cannot guarantee ( with reasonable > time contribution). I know that EFI boot is possible not only via Syslinux, but also grub2efi. However, one of the most important features is the ability to load the same DL system from a different drives or partitions using one of the multiple copies of the configuration. Free choice of boot partition is allowed in Syslinux using chain module (without changes in BIOS/EFI setup settings). This is especially valuable on routers operating in a remote location, which are experiencing a malfunction of hard drive or flash memory. In addition, only Syslinux gives you the ability to indicate the number of I/O port of serial console (eg, 16550A), which allows remote access to the full boot process through Intel AMT. These are the reasons why I tried to fight with Syslinux EFI. Boot the system by the BIOS or EFI Compatibility Support Module solves the problem, as long as the producers did not decide to follow an interesting target market for motherboards with EFI without CSM. And on this occasion I tried to explore Syslinyx EFI. The second problem is the security issues (eg security hole gets procedure), which was finally cut by the C11 and what is implemented in glibc 2.16. I thought that after over a year of C11, most packages will be revised and so I tried once with gcc 4.7.2 and glibc 2.16. However, from a certain point, as you noticed, almost every package need to patch in sources or in a build script. When I came to the keepalive packet, I lost motivation for this Sisyphean labor and I decided to put off my work for a few months. Also because incorporated now a lot of patches will oblige us to remove them, when authors will have his packages adapted to the new environment. The Syslinux authors motivate us to gcc 4.7 glibc 2.16. But on the other hand - Syslinux EFI does not fully work yet - there are problems with the modules c32, and they are the most valuable. This is yet another reason to wait. I think the move to EFI without CSM has not in danger us at least a year. The scope of last update work in DL indicates that Heiko thinks the same. > at this moment I have 2 working build environments ( the current is gcc > 4.6.3/glibc 2.15, the former is gcc 4.5.2/glibc 2.12) which I will be > happy to share. > > The both toolchains are well-tested and stable, however they are not a > truly DL, because it was necessary to add a lot of patches to scripts > and sources. I'm curious, what benefits arise from the transition to gcc 4.6.3 glibc 2.15 - because it is still in front of the standard C11. Maybe your work is near compatible with 4.7/2.16? Best regards in New Year Andrzej Odyniec |
|
From: Serge L. <ser...@gm...> - 2013-01-09 23:39:56
|
Andrzej, at this moment I have 2 working build environments ( the current is gcc 4.6.3/glibc 2.15, the former is gcc 4.5.2/glibc 2.12) which I will be happy to share. The both toolchains are well-tested and stable, however they are not a truly DL, because it was necessary to add a lot of patches to scripts and sources. grub2 is a part of this system, so EFI boot should not be a problem. The only issue with submitting all this stuff back in DL source control is backward compatibility which I cannot guarantee ( with reasonable time contribution). Serge On 01/09/2013 07:25 AM, Andrzej Odyniec wrote: > Dear Heiko, > > I mentioned that I'll try to boot using EFI. > > It seems that for the EFI boot (at least using Syslinux) we must wait a bit. > > Although I was able to load the kernel using syslinux compiled on Arch Linux, > but there are no way to compile git syslinux with efi on DL build environment. > > Syslinux maintainers are from Intel. They use newest versions of compiler and > glibc. > > I tried to do an update of DL to gcc 4.7.2 and glibc 2.16, but there are a lot > dependencies and patches. I came to keepalive and gave up. C11 changes are > included in the gcc 4.7 and glibc 2.16 but in many applications have not yet. > > It seems that the authors of the packages or maintainers must patch sources. > And it probably will take about six months or longer. > > I think you have a similar view. > > Best Regards and Happy New Year. > > Andrzej Odyniec > > ------------------------------------------------------------------------------ > Master Java SE, Java EE, Eclipse, Spring, Hibernate, JavaScript, jQuery > and much more. Keep your Java skills current with LearnJavaNow - > 200+ hours of step-by-step video tutorials by Java experts. > SALE $49.99 this month only -- learn more at: > http://p.sf.net/sfu/learnmore_122612 > _______________________________________________ > Devil-linux-develop mailing list > Dev...@li... > https://lists.sourceforge.net/lists/listinfo/devil-linux-develop > |
|
From: Andrzej O. <an...@ma...> - 2013-01-09 15:25:29
|
Dear Heiko, I mentioned that I'll try to boot using EFI. It seems that for the EFI boot (at least using Syslinux) we must wait a bit. Although I was able to load the kernel using syslinux compiled on Arch Linux, but there are no way to compile git syslinux with efi on DL build environment. Syslinux maintainers are from Intel. They use newest versions of compiler and glibc. I tried to do an update of DL to gcc 4.7.2 and glibc 2.16, but there are a lot dependencies and patches. I came to keepalive and gave up. C11 changes are included in the gcc 4.7 and glibc 2.16 but in many applications have not yet. It seems that the authors of the packages or maintainers must patch sources. And it probably will take about six months or longer. I think you have a similar view. Best Regards and Happy New Year. Andrzej Odyniec |
|
From: Heiko Z. <he...@zu...> - 2012-12-31 13:35:27
|
Hello DL Community! Devil-Linux 1.6.3 brings lots of software updates, in addition to support for being a file and backup server for Apple computers. Please see the change log for details. Best Regards Heiko Zuerker http://www.devil-linux.org |
|
From: Andrzej O. <an...@ma...> - 2012-12-17 13:28:55
|
Heiko Zuerker wrote: > Your scripts have been added to CVS, but I did not do anything with > install-on-usb yet. Dear Heiko, Thanks for that. I do not think, that changes in install-on-usb are urgent. I mainly signaled the possibility of a booting from large disk. But the goal is certainly full support of (U)EFI Boot and this will require major changes in install-on-usb. Now UEFI motherboards are manufactured more and more, and compatibility modules has some limitations. I'm trying to do it, but in GRUB EFI boot is quite complicated but Syslinux EFI is still in alpha testing (version 6.00pre3). I think that if someone need to do BIOS boot from a GPT partition now, he/she is an expert and the changes in script install-on-usb for this person will be not problematic. It is only to write another MBR. When I load the DL with UEFI without compliance module, I will let to know. Best regards -- Andrzej Odyniec |
|
From: Heiko Z. <he...@zu...> - 2012-12-15 16:02:13
|
Andrzej,
This has been added to CVS. Thanks for you submission!
Best Regards
Heiko Zuerker
-----Original Message-----
From: Andrzej Odyniec [mailto:an...@ma...]
Sent: Monday, November 12, 2012 8:11 AM
To: dev...@li...
Subject: [Devil-linux-develop] init.d/network script and dhcpd client
Dear Heiko,
There are totally not urgent fixes to the script init.d/network, but worth
consideration with the next edition.
Tere are two problems with network starting script, occuring in rare cases.
First. The problem manifests itself when two or more interfaces has set
DHCP=yes (which is quite rare for routers). network script starts dhcpcd
client for each interface separately, but each involves a separate pid file
with name of the device as the name suffix. To specify the name of pid file
killproc function is ready but loadproc is not and therefore loadproc check
the presence of common pid file. Therefore, the second instance of dhcpcd
client does not start.
Fix requires modification of loadproc function (in functions) by adding the
option of the form "-p name.pid" like in killproc and (in network script
itself) callings to startup and stopping of dhcpcd client.
Second. The problem is when closing labeled interfaces, such as eth0:1,
eth0:2 etc -- labeled interfaces are not closing correctly. The interface
definition files in the /etc/sysconfig/nic are elaborated in sequence of
"ls" command.
Labeled interface files are adding IP address to the main interface when
opening and taken away at closing. When stopping interfaces, reverse list
order is needed for closing labelled interfaces before main and, therefore,
we need use the command "ls -1 -r". This change is needed only in script
network.
Patches are included
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
|
|
From: Heiko Z. <he...@zu...> - 2012-12-15 16:01:48
|
Andrzej, Your scripts have been added to CVS, but I did not do anything with install-on-usb yet. Thanks for the submission! Best Regards Heiko Zuerker -----Original Message----- From: Andrzej Odyniec [mailto:an...@ma...] Sent: Thursday, October 25, 2012 1:57 PM To: dev...@li... Subject: Re: [Devil-linux-develop] Disks larger than 2TB Heiko Zuerker wrote: > I like this and will add it to my todo list. > Unfortunately I'm extremely busy lately and it may take a while for me > to work on this. This is natural. And my idea isn't urgent in any sense. I tried to compile GPT fdisk without icu library (which is relatively large). Attached script I altered with changing Makefile using awk according to authors instructions. All utilities are working near correct, but about one issue I send message to the author. I don't know exactly, for what Rod is using unicode ICU libraries. The only place for text is comment name on GPT partitions, but for DL, I think, this is absolutely unneeded. So maybe better is cancel the ICU to the time when it will be necessary to do something else. As for now, I'm booting (on BIOS machine) from GPT partitioned disk (using Syslinux) and on this huge disk I have several partitions. Journalists threatened for some time that all machines will soon UEFI. ;-) Best regards -- Andrzej Odyniec |
|
From: Andrzej O. <an...@ma...> - 2012-11-12 14:11:24
|
Dear Heiko,
There are totally not urgent fixes to the script init.d/network, but worth
consideration with the next edition.
Tere are two problems with network starting script, occuring in rare cases.
First. The problem manifests itself when two or more interfaces has set
DHCP=yes (which is quite rare for routers). network script starts dhcpcd
client for each interface separately, but each involves a separate pid file
with name of the device as the name suffix. To specify the name of pid file
killproc function is ready but loadproc is not and therefore loadproc check
the presence of common pid file. Therefore, the second instance of dhcpcd
client does not start.
Fix requires modification of loadproc function (in functions) by adding the
option of the form "-p name.pid" like in killproc and (in network script
itself) callings to startup and stopping of dhcpcd client.
Second. The problem is when closing labeled interfaces, such as eth0:1, eth0:2
etc -- labeled interfaces are not closing correctly. The interface definition
files in the /etc/sysconfig/nic are elaborated in sequence of "ls" command.
Labeled interface files are adding IP address to the main interface when
opening and taken away at closing. When stopping interfaces, reverse list
order is needed for closing labelled interfaces before main and, therefore, we
need use the command "ls -1 -r". This change is needed only in script network.
Patches are included
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
|
|
From: Andrzej O. <an...@ma...> - 2012-10-25 18:57:41
|
Heiko Zuerker wrote: > I like this and will add it to my todo list. > Unfortunately I'm extremely busy lately and it may take a while for me > to work on this. This is natural. And my idea isn't urgent in any sense. I tried to compile GPT fdisk without icu library (which is relatively large). Attached script I altered with changing Makefile using awk according to authors instructions. All utilities are working near correct, but about one issue I send message to the author. I don't know exactly, for what Rod is using unicode ICU libraries. The only place for text is comment name on GPT partitions, but for DL, I think, this is absolutely unneeded. So maybe better is cancel the ICU to the time when it will be necessary to do something else. As for now, I'm booting (on BIOS machine) from GPT partitioned disk (using Syslinux) and on this huge disk I have several partitions. Journalists threatened for some time that all machines will soon UEFI. ;-) Best regards -- Andrzej Odyniec |
|
From: Heiko Z. <he...@zu...> - 2012-10-23 18:55:46
|
Andrzej, I like this and will add it to my todo list. Unfortunately I'm extremely busy lately and it may take a while for me to work on this. Heiko Quoting Andrzej Odyniec <an...@ma...>: > Dear Heiko, > > Drives larger than 2TB is a reality. I bought 4TB drive in a store. > > But although the Devil Linux is wonderfully suited to be the file server, > still can not cope with such drives. > > The solution is quite simple, and I propose to use them in the near future. > > 1. The structure of the partition table in the BIOS model can not deal with > larger disks as 2^32 LBA it is 2TB, so we should use UEFI GPT partitioning. > > But for the effective operation of such tables kernel should be compiled with > the setting: CONFIG_EFI_PARTITION=y, otherwise kernel will do not recognise > such partitions properly and the startup scripts will not cope for example in > finding on such partitions configuration files. > > 2. Although support for GPT partition somewhat ensures parted, but a great > addition to the package seems to be a GPT fdisk. > > (http://downloads.sourceforge.net/project/gptfdisk/gptfdisk/0.8.5/gptfdisk-0.8.5.tar.gz) > > > This package depends on ncurses but if we do not modify its Makefile (I did > not), to support unicode is needed ICU libraries package. > > (http://download.icu-project.org/files/icu4c/49.1.2/icu4c-49_1_2-src.tgz) > > I attach my scripts and configurations for these packages. > > 3. If we set the legacy_boot flag on GPT partition with Devil-Linux boot, we > can boot DL on BIOS computer from 3TB drive (tested by me). This can be > valuable when we run Samba on huge drive and don't want to charge the system > with additional USB stick. But for this our syslinux build script should be > modified to grant access to another mbr code, named gptmbr.bin and > install-on-usb script should test partition table using for example, the > following test: > > [ "`parted -m -s $DEVICE print|grep "^$DEVICE"|awk > 'BEGIN{FS=":"}{print $6}'`" > == "gpt" ] > > and selecting appropriate mbr.bin or gptmbr.bin to put into MBR. > > Best regards > > -- > Andrzej Odyniec > > > ------------------------------------------------------------------------------ > Everyone hates slow websites. So do we. > Make your web apps faster with AppDynamics > Download AppDynamics Lite for free today: > http://p.sf.net/sfu/appdyn_sfd2d_oct > _______________________________________________ > Devil-linux-develop mailing list > Dev...@li... > https://lists.sourceforge.net/lists/listinfo/devil-linux-develop -- Regards Heiko Zuerker http://www.devil-linux.org |
|
From: Andrzej O. <an...@ma...> - 2012-10-23 16:53:54
|
I wrote:
> I attach my scripts and configurations for these packages.
So there are this scripts.
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
|
|
From: Andrzej O. <an...@ma...> - 2012-10-23 16:42:47
|
Dear Heiko, Drives larger than 2TB is a reality. I bought 4TB drive in a store. But although the Devil Linux is wonderfully suited to be the file server, still can not cope with such drives. The solution is quite simple, and I propose to use them in the near future. 1. The structure of the partition table in the BIOS model can not deal with larger disks as 2^32 LBA it is 2TB, so we should use UEFI GPT partitioning. But for the effective operation of such tables kernel should be compiled with the setting: CONFIG_EFI_PARTITION=y, otherwise kernel will do not recognise such partitions properly and the startup scripts will not cope for example in finding on such partitions configuration files. 2. Although support for GPT partition somewhat ensures parted, but a great addition to the package seems to be a GPT fdisk. (http://downloads.sourceforge.net/project/gptfdisk/gptfdisk/0.8.5/gptfdisk-0.8.5.tar.gz) This package depends on ncurses but if we do not modify its Makefile (I did not), to support unicode is needed ICU libraries package. (http://download.icu-project.org/files/icu4c/49.1.2/icu4c-49_1_2-src.tgz) I attach my scripts and configurations for these packages. 3. If we set the legacy_boot flag on GPT partition with Devil-Linux boot, we can boot DL on BIOS computer from 3TB drive (tested by me). This can be valuable when we run Samba on huge drive and don't want to charge the system with additional USB stick. But for this our syslinux build script should be modified to grant access to another mbr code, named gptmbr.bin and install-on-usb script should test partition table using for example, the following test: [ "`parted -m -s $DEVICE print|grep "^$DEVICE"|awk 'BEGIN{FS=":"}{print $6}'`" == "gpt" ] and selecting appropriate mbr.bin or gptmbr.bin to put into MBR. Best regards -- Andrzej Odyniec |
|
From: Heiko Z. <he...@zu...> - 2012-08-18 13:23:24
|
Hello DL Community! Devil-Linux 1.6.2 brings many security related software updates. Upgrading is strongly advised. Please read the change log for details. Best Regards Heiko Zuerker http://www.devil-linux.org |
|
From: Heiko Z. <he...@zu...> - 2012-05-10 12:28:49
|
Hello DL Community!
Devil-Linux 1.6.1 brings many security related software updates. Upgrading
is strongly advised.
Please read the change log for details.
--
Regards
Heiko Zuerker
<http://www.devil-linux.org> http://www.devil-linux.org
|
|
From: Serge L. <ser...@gm...> - 2012-05-04 19:30:26
|
Hi Heiko, yes, I thought there is no harm in it because microcode module should be loaded specially, udev doesn't load it. Serge On 05/01/2012 10:30 AM, Heiko Zuerker wrote: > Serge, > > Did you want to add this to the standard configuration? > > Regards > Heiko > > Quoting Serge Leschinsky<sma...@us...>: > >> Update of /cvsroot/devil-linux/build/scripts >> In directory vz-cvs-3.sog:/tmp/cvs-serv32338/scripts >> >> Added Files: >> microcode >> Log Message: >> >> - added CPU microcode update >> >> >> --- NEW FILE: microcode --- >> #!/bin/bash >> # $Source: /cvsroot/devil-linux/build/scripts/microcode,v $ >> # $Revision: 1.1 $ >> # $Date: 2012/04/23 05:45:45 $ >> # http://www.devil-linux.org >> >> # you need the next line, otherwise script won't be executed !!! >> # DL-build-system v3 >> >> # get the directoryname of the script >> MYDIR=${0%/*} >> >> # source functions and config >> source $MYDIR/settings >> >> case $1 in >> build ) >> gcc -Wall -o intel-microcode2ucode intel-microcode2ucode.c || exit 1 >> mkdir firmware&& pushd firmware> /dev/null || exit 1 >> for i in $SRCDIR/microcode/*; do >> tar vfxj $i || exit 1 >> done >> ../intel-microcode2ucode microcode.dat || exit 1 >> popd> /dev/null >> ;; >> >> install ) >> rm -rf $TMPDIR || exit 1 >> >> mkdir -p $TMPDIR/lib/firmware/{amd-ucode,intel-ucode}&& chmod 755 >> $TMPDIR/lib/firmware/*-ucode || exit 1 >> cp -a firmware/amd-ucode*/microcode_amd.bin >> $TMPDIR/lib/firmware/amd-ucode/ || exit 1 >> cp -a firmware/amd-ucode*/microcode_amd_fam15h.bin >> $TMPDIR/lib/firmware/amd-ucode/ || exit 1 >> cp -a firmware/intel-ucode/* $TMPDIR/lib/firmware/intel-ucode/ || exit 1 >> mkdir -p $TMPDIR/lib/udev/rules.d&& cp microcode.rules >> $TMPDIR/lib/udev/rules.d/89-microcode.rules || exit 1 >> copy_files $TMPDIR/lib $CDDIR/ || exit 1 >> >> rm -rf $TMPDIR || exit 1 >> ;; >> >> * ) >> echo "ERROR ($0)" >> echo "please add parameter so I know what to do" >> exit 1 >> ;; >> esac >> >> >> ------------------------------------------------------------------------------ >> For Developers, A Lot Can Happen In A Second. >> Boundary is the first to Know...and Tell You. >> Monitor Your Applications in Ultra-Fine Resolution. Try it FREE! >> http://p.sf.net/sfu/Boundary-d2dvs2 >> _______________________________________________ >> Devil-linux-commit mailing list >> Dev...@li... >> https://lists.sourceforge.net/lists/listinfo/devil-linux-commit > |
|
From: Heiko Z. <he...@zu...> - 2012-05-01 17:30:34
|
Serge, Did you want to add this to the standard configuration? Regards Heiko Quoting Serge Leschinsky <sma...@us...>: > Update of /cvsroot/devil-linux/build/scripts > In directory vz-cvs-3.sog:/tmp/cvs-serv32338/scripts > > Added Files: > microcode > Log Message: > > - added CPU microcode update > > > --- NEW FILE: microcode --- > #!/bin/bash > # $Source: /cvsroot/devil-linux/build/scripts/microcode,v $ > # $Revision: 1.1 $ > # $Date: 2012/04/23 05:45:45 $ > # http://www.devil-linux.org > > # you need the next line, otherwise script won't be executed !!! > # DL-build-system v3 > > # get the directoryname of the script > MYDIR=${0%/*} > > # source functions and config > source $MYDIR/settings > > case $1 in > build ) > gcc -Wall -o intel-microcode2ucode intel-microcode2ucode.c || exit 1 > mkdir firmware && pushd firmware > /dev/null || exit 1 > for i in $SRCDIR/microcode/*; do > tar vfxj $i || exit 1 > done > ../intel-microcode2ucode microcode.dat || exit 1 > popd > /dev/null > ;; > > install ) > rm -rf $TMPDIR || exit 1 > > mkdir -p $TMPDIR/lib/firmware/{amd-ucode,intel-ucode} && chmod 755 > $TMPDIR/lib/firmware/*-ucode || exit 1 > cp -a firmware/amd-ucode*/microcode_amd.bin > $TMPDIR/lib/firmware/amd-ucode/ || exit 1 > cp -a firmware/amd-ucode*/microcode_amd_fam15h.bin > $TMPDIR/lib/firmware/amd-ucode/ || exit 1 > cp -a firmware/intel-ucode/* $TMPDIR/lib/firmware/intel-ucode/ || exit 1 > mkdir -p $TMPDIR/lib/udev/rules.d && cp microcode.rules > $TMPDIR/lib/udev/rules.d/89-microcode.rules || exit 1 > copy_files $TMPDIR/lib $CDDIR/ || exit 1 > > rm -rf $TMPDIR || exit 1 > ;; > > * ) > echo "ERROR ($0)" > echo "please add parameter so I know what to do" > exit 1 > ;; > esac > > > ------------------------------------------------------------------------------ > For Developers, A Lot Can Happen In A Second. > Boundary is the first to Know...and Tell You. > Monitor Your Applications in Ultra-Fine Resolution. Try it FREE! > http://p.sf.net/sfu/Boundary-d2dvs2 > _______________________________________________ > Devil-linux-commit mailing list > Dev...@li... > https://lists.sourceforge.net/lists/listinfo/devil-linux-commit -- Regards Heiko Zuerker http://www.devil-linux.org |
35 messages has been excluded from this view by a project administrator.
