Unofficial Arch Linux Newsletter for February, 2009

I don't want to step on anyones toes (sorry Kensai and pressh if I did), but I had a few things to say to the community, and some people were getting impatient, so here's a little unofficial Arch Linux Newsletter for February. Looking forward to the next official one!
If anyone wants to comment (constructive criticism, rants, hate mail, whatever) feel free to post.
Last edited by Ghost1227 (2009-02-04 09:31:39)

Dusty wrote:
pressh wrote:As I want to change a few things in the newsletter and Eduardo maybe too,
Did this make anybody else giggle? I want to change a few things with Eduardo myself... :-D
ah crap
[edit]
of course I meant to say that I want to change some things in both the newsletter and Eduardo
[edit2]
btw. Dusty, if you have any input on this in any way it is much appreciated. just let me know.
Last edited by pressh (2009-02-04 13:58:35)

Similar Messages

Arch Linux Newsletter for July 01, 2008, Discussion.

http://archlinux.org/static/newsletters … ul-07.html
Here we are going to discuss any questions, suggestions or random talk about the newsletter for June 04, 2008. Feel free to contribute with ideas and suggestions.
As always thanks for your support,
In the name of the Arch Linux Newsletter Team
Eduardo "kensai" Romero

Misfit138 wrote:
kensai wrote:
Dusty wrote:apparently people are more loyal to the Arch brand than the tux brand. :-D
Those people have not seen an angry penguin charging at them.
I most certainly am. Philosophically, I resent using the penguin kernel.
It's just that Arch is so damn good, it has spoiled me for anything else.
-->Same Here<--
The linux kernel can drive me crazy sometimes...
Hmmm, do you want to start ArchBSD Misfit? That is, FreeBSD + Pacman goodness + updated rc.conf?
I shouldn't have suggested that, I don't have the time to be a dev for anything right now.

Arch Linux Newsletter for June 04, 2008 Discussion

http://archlinux.org/static/newsletters … un-02.html
Here we are going to discuss any questions, suggestions or random talk about the newsletter for June 04, 2008. Feel free to contribute with ideas and suggestions.
As always thanks for your support,
In the name of the Arch Linux Newsletter Team
Eduardo "kensai" Romero

kensai wrote:
[vEX] wrote:I also think it should have been made clear that Tremuluos is only available for i686 and you need to enable the Community repository (I think it's enabled by default now, but I bet some people have it disabled).
Ok fixed everything but the interview, since I don't like correcting people in interviews, he is from Germany so English might not be his first language, still I always like Interviews to be left untouched.
Oh, and check it out now, I updated the Tremulous article with your note. ;)
Yeah, I feel the same way about the interview, it's just that previously in some interviews small typos have had [sic] next to them to point out the editor being aware of them.
weseven wrote:
Update: [vEX] from the forums pointed out: "it should have been made clear that Tremuluos is only available for i686 and you need to enable the Community repository (I think it's enabled by default now, but I bet some people have it disabled)."
false.
trem is for x86_64 too. the backport client you linked is only for i686, but if you search a bit on google, you can find svn client versions for 64 too.
playing trem on an arch64 laptop :)
Oh, I didn't spend much time searching for it, I just checked what's available in the Arch repositories, so in one way I'm still correct. It'd be nice to see a package (be it in Extra/Community or AUR) for us 64-bit users.
Last edited by [vEX] (2008-06-05 12:07:03)

Arch Linux Newsletter December 2009?

For those of you who didn't see my email on the Arch General mailing list, here's the situation with the Arch Linux Newsletter/Arch Linux Magazine. As many of you know, Kensai recently moved and got married and I recently moved and have been trying to find a job. My situation led to me having difficulty finding the time to dedicate to the Newsletter/Magazine that I have in the past. Combined with Kensai's absence (and as such, our inability to post anything even if we had a completed issue), this caused the lack of our great publication for the last few months. Thankfully, the situation has been rectified and we are now preparing for our next issue. Unfortunately, this solution has come at a cost. Our fearless leader has decided to step down from his position in order to dedicate more time to his new-found family and I can't say I blame him. As such, we wish Kensai the best and hope that once his life calms down him start contributing again, even if in just a small way.
After much deliberation (alright, so maybe I'm exaggerating a little bit), the Arch Linux development team has graciously decided that they want to keep me on as editor of our official publication. As such, I am preparing for the release of our next issue! I would like to see us make a comeback to where we left off and then some. I want to see more community contributions and writers, and I want to get the Schwag report back. I want more sections and special features and I even have a few surprises in store for you all down the road a bit.
This improvement is going to be a big project and I can't do it alone. If any of you, our loyal readers, are willing to contribute please step up and say so. Leave a message here, join me in #archlinux-magazine on freenode, or send me an email at [email protected]. You don't have to have a mass media background or immense technical knowledge, I can find a way for anyone to contribute. Help us make the new Arch Linux Newsletter/Arch Linux Magazine the best one yet!

kensai wrote:Is so hard to say good bye, guys thanks for all the support you have given me all this time, without this wonderful community I would have never done all I did. I hope one day I will come back, when things get more stable, cause you know, when starting something new the start is a mess most of the time until things settle down.
Don't think of it as a "good bye", but as a "See you soon". I'll bet you'll be back once you're settled in (which may or may not happen faster than you expect). Either way, best of luck for now and the future, and don't sweat the small things, chances are time will fix most of the small messes.
and to ghost: Do you have a rough estimate of when we might be getting started on the newsletter and such?

ArchLinux Newsletter for February 22

Greetings, and welcome to the ArchLinux weekly newsletter for the week ending February 22, 2004.
Front Page News:
NEW KERNELS ABOUND
Hi all,
First off, a huge thank-you to everyone that has donated over the last couple of days. We now have enough of a start to pay setup fees and the first couple months on a new server. You guys rock.
Now, an update regarding the new kernels... We're planning on using 2.6.3 as the default kernel for Widget's release, so I've renamed the 2.4 kernel packages for more consistency. We now have four kernel packages:
* kernel24
* kernel24-scsi
* kernel26
* kernel26-scsi
As you know, the kernel26 packages write their bzImages as /boot/vmlinuz26 so that they can coexist with a 2.4 kernel. I've left the kernel 2.4 bzImage as /boot/vmlinuz for now, to avoid breaking too many users' boxes. But keep in mind that I may rename them to /boot/vmlinuz24 sometime in the future. Watch out!
Another effect of the package renames is that the setup script had to be updated. This means that you will have to re-download the root.img disk image to do an ftp-based install. The old one will look for the 'kernel' package, which no longer exists.
http://archlinux.org/news.php#48
FUN WITH BANDWIDTH COSTS
As most of you know, the recent review on OSNews has brought a large influx of users to us. While we're overjoyed to have so many new users, the bandwidth costs associated with all these new --sysupgrade'ers is going to cost me a lot of money that I don't really have.
To curb the trend, I've had to cap transfer speeds on ftp.archlinux.org. They now sit at 20 K/s with a max of 30 users at a time.
So, long story short, I have a couple of favors to ask:
1. If you can volunteer to be a mirror, please contact me.
2. Please download this perl script, which will use the "netselect" program to re-sort the server lists in pacman.conf, lowest ping times first. You can run it like so:
# ./sortmirrors.pl </etc/pacman.conf >pacman.conf.new
Make sure pacman.conf.new looks okay, then move it into place:
# mv pacman.conf.new /etc/pacman.conf
3. If you can spare a few bucks for a bandwidth-hungry distribution, please donate. We're looking to get another server, but the donations just aren't there yet.
Thanks a lot everyone. We'll keep on making it if you keep on running it.
Editor's Note: The perl script now comes with the new version of pacman, and the download cap has been lifted.
http://archlinux.org/news.php#47
This Week on the Forum:
Rasat made a request that we try to clean up the forums to make it easier to read. One idea was to put [RMx] for remove, [MVx] for move or [FXx] for fixed / resolved, in our topic titles. Read about it here: http://bbs.archlinux.org/viewtopic.php?t=2773
Neocephas wrote a CUPS HOW-TO for Arch. It's still being worked on, so go help out over here: http://bbs.archlinux.org/viewtopic.php?t=2757
This Week on the Mailing List:
After the announcement by Judd about the bandwidth troubles, people raised some ideas for saving bandwidth. One was randomizing mirrors automatically via pacman. Another was to take the Full 0.5 ISO off of the main ftp site, because it's out of date anyway. Neither of these have been implemented yet, but discussion is still ongoing. Read the threads at:
http://www.archlinux.org/pipermail/arch … 00844.html
http://www.archlinux.org/pipermail/arch … 00853.html
The idea was brought up again about multiple flavors of kernels. DanG also asked if multiple 2.4 or 2.6 kernel packages could "live together". The answer was no. A 2.4 and 2.6 kernel can co-exist though. Judd stated that there were no plans for different flavors of kernels (like "failsafe") and instead people should be building their own. Read the thread at: http://www.archlinux.org/pipermail/arch … 00872.html
What's happening with the TUR mailing list:
We're currently looking to assimilate a couple more Trusted Users to run their own repository and help test packages from /incoming. The system now requires sponsorship. So if you have submitted a lot of packages to /incoming that have made their way into the repositories, the TUs will be willing to sponsor you. If you are interested, join and mail the TUR Mailing list: https://lists.berlios.de/mailman/listinfo/tur-users
This Week in Dev Land (by Jason Chu):
Manolis Tzanidakis (zen_guerilla) left the development team. He has decided to work on his own personal distro and won't have time for both. We wish him well.
Tobias Kieslich (neri) and Damir Perisa (dp) have joined the dev team. They've started adopting packages and are still learning how everything works. They are a welcome addition to the dev team.
We now have a new package server. All the regular traffic goes to the original server but ftp.archlinux.org is now on a different one. This one has a higher limit on bandwidth but if you use a mirror please continue doing so.
We are debating if/how to add f77 and gcj compilers to gcc. The best suggestion is to have seperate packages that depend on gcc but gcc is a scary package so it's still being researched.
The gcc question brought up another: should we implement multiple packages per PKGBUILD file? It was agreed that a single package per PKGBUILD is much simpler and more like the arch way. At the same time, we still have some issues to work through because of this simple method.
There are new disk images on ftp.archlinux.org. They're more modular and have support for keymaps, xfs/jfs support, and raid/lvm. The setup scripts don't support all of these new features but the advanced user will be able to use them. There will also be an expert install script to support these features.
Xfree86 licensing is still being researched. An interesting link was found: http://www.xfree86.org/legal/licenses.html
An 0.6-base-BETA1 was released. It's available on the archlinux ftp server. Feel free to test it.
An Archlinux goal/philosophy/social contract document was mentioned. Judd said he was thinking about this already and we will probably start one soon.
A number of packages were found to be missing urls and md5sums. Namcap will detect this and spit out an error. If anyone finds PKGBUILDs with these missing, they can submit a bug report for that package.
Package Highlights:
Updated init scripts were released this week. They provide a more cleaned up boot process.
reiserfsprogs 3.6.13 was released this week. This fixes a bug that can prevent a ReiserFS partition from booting. Read about it here: http://bbs.archlinux.org/viewtopic.php?t=2614
GCC, Coreutils, the kernel and some other core packages were updated this week. These types of upgrades can be risky sometimes, so be sure to submit any problems you have to the Bug Tracker.
Pacman 2.7.4 was released this week. Changes are:
- fixed a bug in conflict handling, where installing a conflicting package would fail even if the new package "provided" it
- if pacman sees a newer version of itself during an upgrade, it will ask to install itself first, then be re-run to upgrade the other packages.
- You can now use the --info option with --sync to display an uninstalled package's dependency info.
- Added a sane umask before db writes
- buffer overflow fix (bug #442)
FAQ of The Week:
Well, it's the same as last week and the week before. Unfortunately, we're still receiving the same questions. If you are having an issue, please review the past Arch Newsletters because your questions are probably answered.
Bugs Opened this Week:
k3b-0.11.4-1 does not work: broken permissions
autologin feature of kdm and gdm does not work
IP Forwarding in iptables pkg
missing dependency for kdegraphics: fribidi, lcms
Mozilla 1.6 package has broken permissions
makewhatis creates /usr/local/man/whatis via crond
kpilot missing from KDEPIM
Bugs Closed this Week:
Program additions for 0.6 installer
kernel upgrades should remind users to run lilo.
Add nano to base
Choose other server in ftp install
Option to use non us keymaps in installer
Add jfs and xfs support
incorrect url in download list
groff-1.19 now available from German mirror
Please add the graphics mode to the links package!
New Vim 6.2 supports GTK2 but in arch it's still GTK1
InitScripts outdated Copyright
util-linux: missing
PARPORT_1284 support in Kernel
N_HDLC support in Kernel
Joystick support in kernel
Please update mozilla-thunderbird
Reiserfsprogs 3.6.12 can't mount partitions read only
Links (graphics mode)
pacman -Syu behaviour
PATCH: Fix buffer overflow in Pacman
pacman: set umask before writing db entries
libgnomeui needs depends on gnome-common
Nautilus crashes immediately
gqmpeg fails to build
gdesklets missing dependencies
transcode fails to build
mp32ogg fails to build
mjpegtools fails to build
mplayer-plugin fails to build
transcode pkg needs to be updated.
missing dep in transcode pkg. again
avifile dies with failure to build codecs
flashplugin be updated to reflect firebird's new name change
small firefox changes
gtk2 deps screwed up between package and db
gtk2 won't build
New and Updated Packages:
k3b 0.11.5-1
barcode 0.98-1
glabels 1.93.3-1
avidemux 2.0.20-2
lcab 1.0b10-1
hd2u 0.9.0-1
maxima 5.9.0-1
kobodeluxe 0.4pre8-1
pth 2.0.0-1
kile 1.6.1-1
atitvout 0.4-1
kdevelop 3.0.1-2
kdevelop-devel 3.1.0.snap040221-1
fbi 1.30-1
pipemeter 0.9.1-1
zile 1.7b3-1
gqview 1.4.0-1
ringtonetools 2.19-1
dbp 0.5.7-1
dcraw 1.170-1
scite 1.59-1
device-mapper 1.00.07-2
coreutils 5.2.0-1
lzop 1.01-3
gtick 0.3.0-2
ogle 0.9.2-3
rar 3.3.0-1
ascii 3.6-1
whois 4.6.9-1
rasmol 2.7.2.1-1
stellarium 0.5.2-1
xfsprogs 2.5.6-1
xmame-sdl 0.78.1-1
lesstif 0.93.94-1
kaffeine 0.4.1-1
alsa-driver 1.0.2-2
xpdf 3.00-1
initscripts 0.6-6
cssed pre0.1.4-1
gdsl 1.0-2
glut 3.7-2
rsync 2.6.0-2
vim 6.2-2
links 2.1pre14-2
gvim 6.2-2
kernel24 2.4.25-1
kernel24-scsi 2.4.25-1
uml_utilities 20040114-1
words 1.0-2
user-mode-linux 2.4.24-1
kernel26-scsi 2.6.3-1
kernel26 2.6.3-1
reiserfsprogs 3.6.13-1
pacman 2.7.4-1
bzflag 1.10.4.20040125-1
galeon 1.3.13-1
toppler 1.0.6-1
gcc 3.3.3-1
wine 20040213-1
mozilla-firefox 0.8-2
less 382-1
iptables 1.2.9-4
flashplugin 6.0r79-8
cdrdao 1.1.8-1
bash-completion 20040214-1
zope 2.7.0-1
liquidwar 5.6.2-1
pcmcia-cs 3.2.7-1
fortune-mod-buffy 1-1
pango 1.2.5-4
gtk2 2.2.4-3
Packages in Staging:
To gain access to this repository and the TURs, visit http://tur.berlios.de
filelight 0.6.4-1
j 0.20.2-s1
inkscape 0.37-s1
abcm2ps 3.7.3-1
potracegui 0.3-s1
amule 1.2.4-1
conglomerate 0.7.12-s1
bogofilter 0.17.0-s1
fftw3 3.0.1-1
gp 0.26-1
fox 1.0.50-s1
ion-devel 20030814-1
libcapsinetwork 0.2.5-s1
labplot 1.2.2-1
hwd 1.6-2
libchipcard 0.9.1-1
libksba 0.4.7-1
liblrdf 0.3.1-1
libofx 0.6.4-1
gtk-smooth-engine 0.5.6-s1
cups-pdf 1.4.1-s1
mage 6.30.030607-1
mpck 0.04-1
pixieplus 0.5.4-1
potrace 1.2-1
prekin 6.30.030607-1
tla 1.1-2
lwm 1.2.0-1
tse3 0.2.7-1
windowlab 1.21-s1
universalkopete 0.1-1
xv 3.10a-1
smclone 0.55-1
kbarcode 1.6.1-s1
bs 2.6-1
mp3burn 0.3.1-1
shaaft 0.5.0-1
monopd 0.9.0-s1
giftui 0.3.1-1
gurlchecker 0.6.4-s1
mono 0.30.1-1
ttf-cheapskate 0.1-2
libxml++ 1.0.0-1
chromium 0.9.12-1
passepartout 0.4-1
gnome-cups-manager 0.17-1
libgnomecups 0.1.6-1
gweled 0.4-s1
logjam 4.2.4-2
xpenguins_themes 1.0-1
libmath++ 0.0.3-1
texmacs 1.0.3.3-s1
gtkatlantic 0.3.2-1
ms-sys 1.1.1-1
rox-system 1.9.0-s1
smb4k 0.3.1-1
ksambaplugin 0.5b2-1
materm 0.1-1
seahorse 0.7.3-2
parse-yapp 1.05-1
libavc1394 0.4.1-1
xml-dom 1.43-1
xml-regexp 0.03-1
xml-xql 0.68-1
prizm 0.2-s1
liferea 0.4.6b-1
panorama-tools 2.6bml12-s1
sylpheed-gtk2 0.9.8a-s1
amarok 0.8.3-s1
mlview 0.6.2-1
gossip 0.7.1-s1
loudmouth 0.15.1-s1
gtodo 0.13.5-s1
gnome-alsamixer 0.9.6-s1
scribus-devel 1.1.5-s1
source-highlight 1.8-s1
xtermset 0.5.1-s1
cdw 0.2.2-s1
gnotime 2.1.7-s1
xfce4-fsguard-plugin 0.2.0-s1
xfce4-xmms-plugin 0.1.1-s1
gksu 1.0.3-s1
pychecker 0.8.13-s1
gtkglext 1.0.5-s1
gtkglextmm 1.0.1-s1
pygtkglext 1.0.1-s1
spe 0.4.2c-s1
gmencoder 0.1.0-s1
scribus-docs 1.0.1-s1
ArchStats Update:
To participate, visit http://archstats.coding-zone.com
Number of registered systems: 135
Date first system was registered: 20031017 [22:24:30]
Most recent update occurred: 20040222 [16:30:46]
Longest recorded uptime: 166 days, 22 hours, 51 minutes, 56 seconds.
Average uptime: 8 days, 2 hours, 14 minutes, 33 seconds.
Lowest kernel version: 2.4.21
Highest kernel version: 2.6.3-mm2
Least packages installed on a system: 44
Average installed packages: 255
Most packages installed on a system: 563
That's it for this week, stay tuned for more exciting news.
-- Jason Chu and Ben Mazer

Keep up the good work!

About the future of Arch Linux Newsletter.

Hi,
As you may have noticed, I have taken the job to make the Arch Linux weekly newsletter a possibility again. I the time I've been doing them, we speak of about 3 weeks, I have enjoyed writing them and have received very positive comments from the community that reads them. I would like to thank all of you personally for the support, you are the community and yours are the newsletter. But, as you all may have noticed the newsletter has been in an unchanged format for quite a long time. I mean, I just added the Humor section thats all, I know there is an email address to which you can all write your suggestions to, but I find people communicate and express themselves better on the forums.
So what I will ask of you, dear readers, suggestions of sections I should add/remove/edit, I will appreciate your constructive criticism in general. Express your thoughts in this thread to help me make a better more quality newsletter.
In other news, the newsletter won't be weekly no more, as Jason Chu and I have talked about, is easier to maintain a 2 time a month newsletter than 4 times a month, also the Arch Linux Developers/Community doesn't make that much noise as the other major distributions, we tend to be a bit quieter. The bright side is, the newsletter will be written with more time at hand, more stuff to write about, and will contribute to a better quality overall.
What has been suggested so far and I will work out on the next issue of the newsletter?
* Change the Bugs stats to not reflect the overall percentage but the actual bugs opened and closed that week.
As Roman Kyrylych points out: "They show a summary of status field "Progress" in open reports, but in 99% this field goes straight from 0% to 100%, so the overall number is always very low and doesn't really show anything".
So I wait for your suggestions as well.;)

Hi again,
I ask for your opinion again on the subject of the stats section in the newsletter, Do you find this an important part that should stay there?
I mean, this is going to be the most tedious, time-taking and in my opinion useless section I will have to write for the newsletter. I do want to bring a high quality newsletter but I feel this part doesn't contribute to the quality of the newsletter at all, Why?
* Newsletters that include this section are mostly from distributions that has point releases and not rolling releases.
* The number will always increase with minimum decrease because as a rolling release system Arch Linux is every package keep being updated everyday to newer versions, opening and closing more bugs by itself.
* People might not be interested in how many bugs are and how many are closed every week, since this numbers aren't even provided on the bug system itself.
Please give this a consideration and tell me your opinions.

Arch Linux newsletter: Featuring an interview with Judd Vinet.

Is time again for another interview, this one will feature in the newsletter scheduled for release on December 3, 2007. This time, the interview will be, with the creator and former leader of the Arch Linux Operating System, Judd Vinet. Following the style of the interview with Aaron Griffin, the ones asking the questions will be the community. Please, read below for the guidelines.
Guidelines: (Please, follow them)
* You may post as many questions as you want, just try to put them all in a single post.
* You may post humor questions, but please, try to include serious questions as well.
* This thread needs to be kept clean, so don't go Off-Topic, or Dusty will have no mercy on us. (Maybe a Taco will make him reconsider)
* apeiro can ask Judd Vinet any questions he feels he would like to hear answered.
* phrakture is not banned from asking neither.
* If you bought Judd Vinet's leather pants, you can't ask for your money back.
Now, on with the questions.
Thanks
Eduardo "kensai" Romero

I know is hard to make good questions to Judd Vinet, even harder when the community didn't had the same level of interaction they had with Aaron Griffin. As he were more accessible to the users. Judd Vinet is not to blame for this, he just didn't had enough time. So, this post is to ask you guys, to keep posting questions, think hard of any good questions the media would like to ask Judd Vinet because of his retirement as a leader of the Arch Linux OS.
If not enough questions are asked by the end of this week, I'll have to proceed with another interview and postpone Judd Vinet's interview for the next scheduled newsletter after that, December 17, 2007. So please, cooperation is needed, this is going to be the first interview after his retirement as the leader of Arch. Thanks.

Arch Linux skin for xmms/bmp/audacious

This is a simple skin for xmms/bmp/audacious with an Arch Linux look (based on a skin for Debian).
You can get it from here. Untar it in the Skins subdir (for audacious this is ~/.local/share/audacious/Skins/).
F

Thanks
Just paste the .tar.gz to ~/.xmms/Skins
No root-permission needed
(show hidden files!:))

Is Arch Linux right for me?

Arch seems like a pretty awesome distro, and I think I would like it a lot. But is it right for me?
I was first introduced to Linux and Unix-based systems last summer when I took a course at my local community college. Since then, I have installed Ubuntu on my HP laptop. In the past months, I have learned and taught myself a lot about the way linux works: downloading and installing software, Unix command line prompt, etc.
Ubuntu is a fantastic distro for linux beginners, but I feel like I'm ready to take the next step and I'm always itching to see a little more of what goes on behind the scenes. I read a guide on Arch over at LifeHacker and skimmed the "Getting Started" guide on Arch Wiki and I generally understood everything that was going on; nothing seemed way over my head. So I think I could handle Arch. What do you guys think?
If you think I should take Arch for a spin, is it practical to install it as my main OS on my main machine? Should I dual-boot it next to Ubuntu or similar? I am planning on building a PC this summer and am currently debating over which OS to use; Arch is a main candidate. My main uses for this computer will be surfing the net, listening to music (integration with my iPod would be great), a little video editing, some casual gaming, and general programming/tinkering with my computer.
I know y'all probably get a lot of these but I appreciate your feedback.

Check out the Beginner's Guide and The Arch Way in the wiki. It's important to note that what really distinguishes Arch from most other distros is that it isn't a distro in the most common sense of the term. Ubuntu, Fedora, SuSE, Sabayon, Mandriva, PCLOS, etc. have graphical installers that pre-configure everything for you; the choices are made for you, and you'll have to work around anything you don't find to your liking. You can easily add and remove programs, but always limited by what they've provided: packages that are patched in order to work in the way they've deemed appropriate, and an init system that's opaque to users (remember the fuss over certain graphics drivers not rendering Plymouth splashes correctly? I've never had that issue in Arch). Arch, on the other hand, is essentially a set of tools--the Arch Installation Framework, a couple init scripts, about six config files (give or take), repos, the ABS tree, the kernel and a package manager--that allow a user to craft their own operating system to their liking. A couple of the things I just mentioned are even optional as it is; at least three of those config files have never been touched by me, as I don't need them. Combine this sense of freedom and control with the DIY philosophy (which I find empowering as well, but hell--I enjoy research, learning and problem solving) and the close-knit community, and you've got my favorite distro. Ultimately, it's the choices of the developers that make a distro what it is; the software--at least in principle--rarely changes. In the case of Arch, most everything comes straight from upstream, goes in the testing repo briefly, then ends up in the standard repo, only altered if deemed necessary for security or basic functionality.
I left Ubuntu after switching to KDE and finding Kubuntu not to my liking; I also found that many of the "conveniences" of Ubuntu (and the 9-12 other distros I tried afterward) just got in the way. For example, why use the Ubuntu USB Startup Disk Creator or Unetbootin when "dd" is faster and easier? How much frustration could I have avoided installing the Catalyst driver in Ubuntu or SuSE if I'd done so manually (with a number of console commands I can count on one hand) rather than mess around with a GUI, thus knowing exactly what I did wrong? To me, it just seems better to start with what I absolutely need and build up piecemeal, rather than add a bunch of crap I don't need/want/even know is there in the first place and hide it all behind extra GUI's, then try and pick it apart. Ultimately, you make Arch what you want it to be. No one can tell you if it's right for you, or if you should install it (there are rare cases where folks here would flat-out say "No," but yours doesn't seem to be one of 'em ). Check out those wiki articles I mentioned; if it seems like something that interests you, give it a whirl!

New Arch Linux Logo for HP?

Hi i released 3D Arch Logos and the reaction was... that 2 peoples asked me to this:
Brutal !!! fresh
by code933k on: 05/03/2007, 15:16
code933k code933k
Home
It is amazing the effect that you've achieved with arch's logo. I was thinking some days ago if it would be possible to change the unpolished perspective of the official logo at arch's home page.
I wonder if you hadn't proposed this well proportioned, clear, and good angled image as the new official logo.
Arch is one of the best distros so you deserve double grats.
I hope to see more of your artwork soon. I drink to make other people interesting.
goood fresh
by spookykid on: 05/04/2007, 3:24
spookykid spookykid
Home
i agree you defenetely should post it in arch forums and see where it goes from there. would you mind posting the source? (original files)spookykidisthinking!
Here the thread:
http://gnome-look.org/usermanager/searc … n=contents
Here the logo:
http://www.2blabla.ch/stuff/Linux/Wallp … -color.png
Question: have the Arch Logo Designer intrest for my 3D logo?

root_tux_linux wrote:
I created that pic with cinema 4D on wine...
and now i change to blender or alias maya 7.0 ^^
Btw. Im a noobie in 3D world ^^
Well, I'm in a similiar situation atm. I used cinema4D a few years ago but stopped mainly because of my switch to linux.
I didn't want to use c4d under wine (and was unable to start it with recent wine version anyway..) and was kind of scared by blenders UI.
After reading a few tutorials my fear is gone and I start to enjoy using blender
Try it out! You'll like it...

Arch Linux Support for Atmel ATmega168

I'm thinking about buying this ATmega168: http://www.amazon.com/NerdKits-USB-Micr … B001I08PK8
I'm wondering if the avrdude, binutils-avr, and gcc-avr packages (http://www.archlinux.org/packages/?q=avr) will work with it... Does anyone know?
Last edited by tony5429 (2011-11-24 02:06:40)

not only yes. but heck yes. I use D.) All of the above on every AVR micro I have (including the ATmega168). sparkfun.com has a really good tutorial for getting started. I suggest it. (it is a windows tutorial, but the exact same software works the same on any PC.) One benefit of this tutorial is that it provides a fantastic skeleton makefile for all of your future AVR programming needs.
oh yeah, and AVRFreaks.com is another really good resource. I do quite a bit of work with AVR micro's. so if you ever have any specific questions feel free to PM me.

Archmobile: Arch Linux for ARM Devices

Hello,
I want to introduce our Operating System for ARM Devices, that's running on the OpenMoko NeoFreerunner, but we want to support more Devices.
We from http://archmobile.org port Arch Linux on ARM, and we want to give you the simple Freedom which has Arch Linux x86 for ARM.
We can already SSH on our Freerunners, and we nearly have X working. One of the Devs already uses our OS as Daily-Phone with QT Extended.
If you want to know more about us, or you want to try out our System visit us at http://archmobile.org !
The first Snapshot is already at http://naeg.archmobile.org/snapshots/ available. This Snapshot works on the Freerunner and you can SSH into your phone and play a lil bit with our OS Also you can install the System with our Installation Script we provide, to get a really up-to-date System and not configured.
It would be great if other people with other ARM Devices would contact us on IRC(on freenode #arch-arm) and we will try to support your ARM Device too. New Developer are always welcome
I think it would be awesome if we get some support from the official Arch Linux. An Entry in the list of Arch Related Projects would be great.
Feel free to talk about that.
Greetings, naeg - alias rott_at

Thanks for your tips to make the wiki better. I will edit the pages to avoid any confusion you've had. Although I won't do all the changes (e.g. remove $ and #). But I will then make a note which should clarify it.
markc wrote:
Some errors I encountered...
# touch /_Archlinux_ARM
/bin/touch: setting times of `_Archlinux_ARM': Invalid argument
This issue is known with a x86_64 host. I don't know where it originates from as i686 host is fine. Use this binary instead: http://stanny.homelinux.org/touch [1]. This is my home FTP. Thus it might not be available 24/7.
markc wrote:checking dependency style of gcc... /bin/touch: setting times of `sub/conftst1.h': Invalid argument
Should be fixed using the touch binary I provided.
markc wrote:bsdtar: Failed to set default locale
Unsupported ioctl: cmd=0xffffffff80046601
bsdtar: Couldn't list extended attributes: Function not implemented
The error in the first line might be solved by configuring your locales correctly. The error below is issued by qemu.
While this is annoying it doesn't appear to cause any harm. Just ignore it. You'll find other ioctls not being supported by qemu and we expect them to be fixed along with qemu's development.
edit:
[1] I moved it to a permanent location: http://archmobile.org/~harlekin/touch
Last edited by harlekin (2009-07-30 22:16:59)

Arch Linux for Google Compute Engine

Hi Arch users,
I’ve created a tool that can create an Arch Linux image for Google Compute Engine. It has the compute-image-packages software preinstalled so basic GCE integration works.
I’m working to improve the boot times and shrink the image since it’s a bit larger than I’d like it to be. You can follow the instructions below to boot a virtual machine running Arch.
The source code is hosted on Github: https://github.com/GoogleCloudPlatform/ … ge-builder, pull requests welcome!
I've already built one today and has been made public on Cloud Storage at gs://jeremyje/arch-stable/arch-v20140906.tar.gz
Instructions to boot a VM with the image:
1. Create a project or pick an existing one. Turn on Compute Engine.
https://console.developers.google.com/
Click "Create project"
Enter a project name and project id.
Go to Compute > Compute Engine
If necessary, enable billing.
2. Add the Arch Image to your Project
Go to Compute > Compute Engine > Images
Click "New image"
Name: arch-v20140906
Description: Arch Linux built on 2014-09-06
Source Type: Cloud Storage object
Cloud Storage Object Path: gs://jeremyje/arch-stable/arch-v20140906.tar.gz
3. Create an Arch Linux instance.
Go to https://console.developers.google.com/
Select your project.
Compute > Compute Engine > VM instances > Add Instance
Select a zone, machine type, and select the “arch-v20140906” image.
You can SSH into the VM by clicking on the SSH button after you create it.
If you like command line here's the equivalent.
Google Cloud SDK: https://developers.google.com/cloud/sdk/
# Install Python2
pacman -S python2
# Install Cloud SDK
export CLOUDSDK_PYTHON=/usr/bin/python2
curl https://sdk.cloud.google.com | bash
echo “export CLOUDSDK_PYTHON=/usr/bin/python2” >> ~/.bashrc
source ~/.bashrc
# Login, create a project
gcloud auth login
# Add the image to your project.
gcloud compute images create archlinux gs://jeremyje/arch-stable/arch-v20140906.tar.gz --description “Arch Linux built on 2014-09-06”
# Create the instance booting Arch
gcloud compute instances create archvm --zone us-central1-a --machine-type f1-micro --image arch-v20140906
Lastly, there’s no official support for these images but if you find a problem please file a bug or submit a fix on Github.

Hi! Do you have any update of your Arch image?
Thank you

First alternative skin for the Neuf Box 4 : Arch Linux skin !

Since the last firmware version of the Neuf Box 4, it is now possible to customize its web interface with skins.
As I've not seen any skin yet, I decided to make my own, base on the design of archlinux.org.
The result is here : Arch Linux skin for the NB4
with details on how to use it.
Tell me what you think

Would you be willing to post a larger image? That one is so tiny that it is hard to see. It seems like a great project, and from what I can see, it looks good.
When I first read the description, "integrated access device" sounded like some corporate/marketing drivel. But, it seems like a great device: "DSL modem that supports ADSL, ADSL2+, and fiber connections. It also integrates a a WiFi access point and three-port Ethernet switch, an RJ-11 phone jack with analog-to-IP phone network adapter, a print server for USB printers (two host ports are provided), a USB device port for USB networking with a PC, and a special Ethernet port for connection to an available TV decoder box."
Wow.

Arch linux diagnostic

Hi, I am new to Archlinux, but I have already used Ubuntu and Debian.
I am starting to have problems with my configuration but have some things working correctly, while others dont.
My question is, how I can diagnose Arch Linux?
For example, when I boot Archlinux, there is some message of a loaded module failing. I don't know how to read it since it appears so fast, is not a log where the text that appears where you boot can be written?
My other question is diagnostic about package, I dont know how to diagnose whick packages are complete and which need dependencies.
And for last, I would ask for advice about general diagnosing since it is the way I can learn by myself better.

In a default installation, your diagnostic tools are the numerous logs under /var/log, which you can take a peek with tail, or any other application that handles text streams; cat, vim, etc. Familiarize yourself with dmesg, tail and syslog by looking at their respective man pages.
man dmesg
This would should you the manual page for dmesg.
What you're asking for is non-specific to Arch. There are other, more sophisticated way of looking at logs, but they all depend on what I've pointed out so far. Be it GUI or a syslog-ng replacement, you're looking at the same output.
Other ways of diagnosing your system (specific to modules and devices) is through /proc. lspci and lsdev are some of the tools that facilitate interfacing with /proc.
Last edited by gog (2009-10-15 02:12:24)

Unofficial Arch Linux Newsletter for February, 2009

Similar Messages

Maybe you are looking for