September 2005 - Arch-projects - lists.archlinux.org

[arch-projects] _nus
by eliott 30 Sep '05

30 Sep '05

I have a project I am currently working on, called _nus. http://e.cactuswax.net/index.php/projects/_nus/ _nus is an attempt at a remote server update manager for ArchLinux. Think of it like...the redhat-network, if you are familiar with that. My hope is that people would be able to use it to monitor a large collection of servers, to see which ones are out of date, and to schedule things like adding/removing/updating packages. _nus has two components: A web aggregator, and a monitor daemon. The monitor daemon runs on each of the servers being...monitored. Both are written in ruby (with the rails framework for the web aggregator). I have the monitor daemon code (_nus:Client) mostly framed out. I just need to add the actual 'work' code to it. I am currently working on the web aggregator (_nus:Server) portion. Maveric has been providing me some good feedback, and he said he will provide some testing when I get something usable out. Hopefully this tool will be useful to someone out there. ;) -- Bender: It was horrible! A nightmare! Fry: What happened? Bender: I dreamt I was in a place of 0's and 1's and all of a sudden... I saw a two *whimper* Fry: It's ok Bender, don't worry. There's no such thing as 2's. -------------------------- There are only 10 types of people in the world; those who understand binary and those who don't.

1 0

[arch-projects] Change ArchWM-base to ArchWD?
by Rasatmakananda 29 Sep '05

29 Sep '05

Hi, In the project ArchWM-base, an effort of developing a 'perfect' Window Manager for Arch Linux, something fundamental is missing. I thought the current base (ver. 0.4.9.3) does the job but I don't think it will do, though, the base (not including Pacwm toolkit but the WM side) is good. Here lets consider its 'perfect'. But I still consider something is missing. Users will not be depended what ArchWM-base will offer but can contribute their own modules and features, but still something is missing. The configure for end users became easy by incorporating a runcom system similar to Arch (rc.conf and rc.sysinit), and the coding of all fvwm system files were change to simple format, but still something is missing. It is what you make it, but still something is missing. The missing part is caused by making ArchWM-base into a package and the users will wait for upgrades. It has same affect as the general Linux distributions making the end users depended what's offered. Arch Linux break that tradition by not having fixed releases but a continues upgrade. Also provided a means (ABS) of include users' own packages. The ArchWM-base use the same idea, allowing user contributions, but currently has "fixed" releases. Instead of making an ArchWM-base as an individual package, why not an ArchWD (distro). A "distro" running within Arch. Not only getting rid of the rigid concept of WM (managing windows what is actually quite limited) but creating a new style of "WM" same as Arch did as a distro. The ArchWD still manages the windows but aims to distribute WM and DE related packages (modules and scripts). Not only Fvwm based packages but also others. The style of upgrading the ArchWD system files and user contributed packages, will be same as pacman. The current name "pacwm" toolkit (confusing name) will be changed to "pactk" (package toolkit). To upgrade ArchWD and all installed user packages, simply run in terminal: pactk -Syu Sounds good? Or something is still missing? Wiki: http://user-contributions.org/wikis/userwiki/index.php/ArchWM-base Forum: http://bbs.archlinux.org/viewtopic.php?t=15368 Why Fvwm and not PekWM: http://bbs.archlinux.org/viewtopic.php?t=15222 Markku (rasat)

2 2

[arch-projects] AMD 64 Port
by Jeffrey Zellman 19 Sep '05

19 Sep '05

Hi, I would like to get involved with porting Arch Linux to AMD64. Does anyone have any information on the project? thanks, Jeff -- Peter Griffin: Brian, there's a message in my Alpha Bits. It says "OOOOOO". Brian Griffin: Peter, those are Cheerios.

2 1