[arch-dev-public] Test Isos with core repository
Hi here the changelog: i changed everything to fit to new core repository, 2 isos left ftp iso and core iso, the rest was setup/archboot changes to achieve this. - I cleaned up our documentation, to fit to those stuff please read it and tell me what is missing or wrong. - fixed the nasty /dev mount bug - fixed the /dev/ttyS0 errors if no serial port is installed in the system - fixed repositories in install environment to fit to both architectures - added pptpclient to install environment - added sdparm to install environment - added all free wireless drivers to install environment - added intel wireless drivers to install environment which will be activated by intel-wireless boot parameter - disabled arch_addons hook by default, it is triggered by arch-addons boot parameter - Ram usage increased to 160MB - added hosts.deny and hosts.allow to config dialog - added licenses to install environment - fixed km to not show broken chars after exit
you can download i686 Isos here: http://www.archlinux.org/~tpowa/rc-iso/686 you can download x86_64 Isos here: http://www.archlinux.org/~tpowa/rc-iso/x86_64
have fun in testing and report issues immediatly, thanks greetings tpowa
On 9/24/07, Tobias Powalowski t.powa@gmx.de wrote:
- Ram usage increased to 160MB
Wow, for an installer? This is getting a little hefty here, considering X isn't even loaded.
Perhaps we should look into this before it becomes a problem.
Tobias, I'm not sure where you keep archboot (it was on a different server), but could we move it to gerolde in /srv/projects?
If you don't have access, you could move the repo to your home dir and let me know, I will move it to /srv
Thanks, Aaron
Am Montag, 24. September 2007 schrieb Aaron Griffin:
On 9/24/07, Tobias Powalowski t.powa@gmx.de wrote:
- Ram usage increased to 160MB
Wow, for an installer? This is getting a little hefty here, considering X isn't even loaded.
Perhaps we should look into this before it becomes a problem.
Tobias, I'm not sure where you keep archboot (it was on a different server), but could we move it to gerolde in /srv/projects?
If you don't have access, you could move the repo to your home dir and let me know, I will move it to /srv
Thanks, Aaron
arch-dev-public mailing list arch-dev-public@archlinux.org http://archlinux.org/mailman/listinfo/arch-dev-public
Hi Aaron the problem is that the initrd size increased due to the wlan drivers. the size will not increase dramatically, only new drivers will be added in next isos. Ram usage is calculated like this: kernelsize+initrdsize+decompressed initrdsize it can be tested with the mem= boot parameter.
The binary part should be complete now. The initrd is not only a installer it's also a complete rescue system. Everything has up and downsides. In my opinion a system with less than 256mb ram is not really recommended and usable in 2007. greetings tpowa
On 9/24/07, Tobias Powalowski t.powa@gmx.de wrote:
Am Montag, 24. September 2007 schrieb Aaron Griffin:
On 9/24/07, Tobias Powalowski t.powa@gmx.de wrote:
- Ram usage increased to 160MB
Wow, for an installer? This is getting a little hefty here, considering X isn't even loaded.
Perhaps we should look into this before it becomes a problem.
Tobias, I'm not sure where you keep archboot (it was on a different server), but could we move it to gerolde in /srv/projects?
If you don't have access, you could move the repo to your home dir and let me know, I will move it to /srv
Thanks, Aaron
arch-dev-public mailing list arch-dev-public@archlinux.org http://archlinux.org/mailman/listinfo/arch-dev-public
Hi Aaron the problem is that the initrd size increased due to the wlan drivers. the size will not increase dramatically, only new drivers will be added in next isos. Ram usage is calculated like this: kernelsize+initrdsize+decompressed initrdsize it can be tested with the mem= boot parameter.
I understand all this, but I think there are better ways to do this. All modules do not need to be loaded directly into ram or be in the initrd. I actually have a proof-of-concept on phraktured.net of this.
This is why I'd like to get the archboot repo on gerolde, because I'm sure I could throw some tricks at it and make it use less RAM.
In my opinion a system with less than 256mb ram is not really recommended and usable in 2007.
That's true, but you're also thinking of a desktop/server machine. What if I wanted to install arch on my router? Even though it's probably a good guess that people have more than 160MB of RAM, that doesn't technically give us cause to be flippant about it - less RAM used means, most likely, faster too.
Let me know when you get archboot up on gerolde 8)
Am Montag, 24. September 2007 schrieb Aaron Griffin:
On 9/24/07, Tobias Powalowski t.powa@gmx.de wrote:
Am Montag, 24. September 2007 schrieb Aaron Griffin:
On 9/24/07, Tobias Powalowski t.powa@gmx.de wrote:
- Ram usage increased to 160MB
Wow, for an installer? This is getting a little hefty here, considering X isn't even loaded.
Perhaps we should look into this before it becomes a problem.
Tobias, I'm not sure where you keep archboot (it was on a different server), but could we move it to gerolde in /srv/projects?
If you don't have access, you could move the repo to your home dir and let me know, I will move it to /srv
Thanks, Aaron
arch-dev-public mailing list arch-dev-public@archlinux.org http://archlinux.org/mailman/listinfo/arch-dev-public
Hi Aaron the problem is that the initrd size increased due to the wlan drivers. the size will not increase dramatically, only new drivers will be added in next isos. Ram usage is calculated like this: kernelsize+initrdsize+decompressed initrdsize it can be tested with the mem= boot parameter.
I understand all this, but I think there are better ways to do this. All modules do not need to be loaded directly into ram or be in the initrd. I actually have a proof-of-concept on phraktured.net of this.
This is why I'd like to get the archboot repo on gerolde, because I'm sure I could throw some tricks at it and make it use less RAM.
In my opinion a system with less than 256mb ram is not really recommended and usable in 2007.
That's true, but you're also thinking of a desktop/server machine. What if I wanted to install arch on my router? Even though it's probably a good guess that people have more than 160MB of RAM, that doesn't technically give us cause to be flippant about it - less RAM used means, most likely, faster too.
Let me know when you get archboot up on gerolde 8)
arch-dev-public mailing list arch-dev-public@archlinux.org http://archlinux.org/mailman/listinfo/arch-dev-public
Hi the tarball is in cvs extra/system/archboot/ greetings tpowa
On 9/24/07, Tobias Powalowski t.powa@gmx.de wrote:
Hi the tarball is in cvs extra/system/archboot/
I'm talking more about this: http://bugs.archlinux.org/task/7789
I added you to the assignees.
* On Monday, September 24 2007, Aaron Griffin wrote:
On 9/24/07, Tobias Powalowski t.powa@gmx.de wrote:
In my opinion a system with less than 256mb ram is not really recommended and usable in 2007.
I think that statement is crap.
I run 1 machine on arch with a 400 mhz pentium 2 with 96 megs of ram as my irc and torrent box. That's right, 96 megs of ram. It works perfectly. I don't have X on it, obviously.
So you are saying I shouldn't be able to install arch on that box, just because you wouldn't use it?
// jeff
On 9/24/07, Tobias Powalowski t.powa@gmx.de wrote:
Am Montag, 24. September 2007 schrieb Aaron Griffin:
On 9/24/07, Tobias Powalowski t.powa@gmx.de wrote:
- Ram usage increased to 160MB
Wow, for an installer? This is getting a little hefty here, considering X isn't even loaded.
Perhaps we should look into this before it becomes a problem.
Tobias, I'm not sure where you keep archboot (it was on a different server), but could we move it to gerolde in /srv/projects?
If you don't have access, you could move the repo to your home dir and let me know, I will move it to /srv
Thanks, Aaron
arch-dev-public mailing list arch-dev-public@archlinux.org http://archlinux.org/mailman/listinfo/arch-dev-public
Hi Aaron the problem is that the initrd size increased due to the wlan drivers. the size will not increase dramatically, only new drivers will be added in next isos. Ram usage is calculated like this: kernelsize+initrdsize+decompressed initrdsize it can be tested with the mem= boot parameter.
The binary part should be complete now. The initrd is not only a installer it's also a complete rescue system. Everything has up and downsides. In my opinion a system with less than 256mb ram is not really recommended and usable in 2007. greetings tpowa -- Tobias Powalowski Archlinux Developer & Package Maintainer (tpowa) http://www.archlinux.org tpowa@archlinux.org
I personally have a server running with 312 MB of RAM, and obviously the 160 MB is not over this limit. However, I know that after boot and running all important server services, only 23 MB of ram is in use. It seems extreme to need 160 MB of RAM to boot, not to mention how long it takes.
A bigger concern is those who may want to run these ISOs in VMs. Needing this much RAM is going to really slow down the rest of my machine that is outside the VM, especially if it needs to start swapping.
-Dan
Hi updated iso names to new name scheme. have fun greetings tpowa
participants (4)
-
Aaron Griffin
-
Dan McGee
-
Jeff 'codemac' Mickey
-
Tobias Powalowski