Arch Linux Reviewed in Argentinian Magazine

Im happy to announce that after some work and evangelization, Arch Linux was reviewed in a local and quite popular Linux magazine here in Argentina. The magazine is called USERS Linux and its in Spanish. The review was followed by some questions they made me as admin of ww.archlinux.com.ar, if there is enough interest i will translate the article.
I collaborated on the article, so i cant say its "objective", its quite centred in the distribution and community, touching point by point the pluses and differences with others, we mention Arch64 and Archie as they had some good reasons to be on the article, the first being for those with 64bit procesors and want the best out of them, and the second for those who didnt want to risk to install Arch without trying it out first.
Congrats to Judd and all the developers, and i hope this gets us some more Spanish Talking users!
You can find a scan of each page here:
http://www.archlinux.com.ar/blog/2006/0 … ers-linux/
edit:
Changed the URL as the site changed hosting and I moved the whole system.

Hi,
im going to start translating the articles, but i will go slow unless there is a bit more interest, either way, sooner or later it will be translated.
brain0:
Yes, your are right, i missed that. I will write them so they can print an "errata" on the next issue, there is also a typo, they printed CRUZ instead of CRUX.
On the other hand, although it has been talked to death, no-one actually tried Arch on a K6-2, so we dont know for sure if it works or not. According to several posts here and some sites found via google, AMDs K6-2 are missing a couple of functions necesary to be fully i686 compliant. They are pretty common in this latitudes, so maybe someone gives it a shot and we will know for sure once and for all!

Similar Messages

New Arch Linux review

Arch Linux: The Simple, Flexible (and Fast!) Distro http://www.linux-mag.com/cache/7469/1.html.
Good review.

Reading it right now
Arch seems to get a lot of attention lately!
I still find linux-mag.com's articles more often then not boring... It seems like a 15 yo blog, not the high quality publication of before. But then, now its free
Edit: After 2 paragraph, they can't even link to the website: http://www.archlnux.org/ instead of http://www.archlinux.org/ ...
Edit: Still a nice article that talks about Arch general terms. It should give Arch more visibility!
Last edited by big_gie (2009-08-13 13:37:34)

My Arch Linux review

Hi,
If someone is interested in reading a review of Arch Linux, you can find one written by me here: http://nirski.pl/2010/02/arch-linux-keeps-it-simple/ . Please feel free to comment, criticism is welcome as it is my first review of an operating system. I am currently testing a free hosting so tell me if it works for you.
tarantoga

It's a nice article, but I want to comment on one quote you made, so there is no discouragement among new users.
tarantoga wrote:A small flaw – the repositories could be richer, package quantity is not as impressive as (for example) in Debian.
This is not a flaw. It's actually an advantage to the way Arch works. Probably 1/3 or more of packages you see in Debian are split packages such as the "*-devel" packages, which can be among the same variety of packages you would already have installed without them. In Arch, everything comes inside the package to simplify the installation/removal of packages with a more clear overhead on what's in the system. Rarely there is a need to split any, but they would all come as a dependency if needed. Every package you would ever want is in the repositories. If there is a package you cannot find, you are not limited as you already know. 99.8% of the time, they can be found in the AUR already setup with pre-made pkgbuilds and install scripts maintained by users, that can be downloaded and installed with an AUR helper (such as yaourt, packer, bauerbill, slurpy, etc.) or done manually with makepkg. If an upsupported package gains enough popular votes, it can move to the community repo maitained by a TU to make sure you get update the latest package updates possible without having to intervene with the AUR or the pkgbuilds. At the same time this would allow the Arch developers to focus more on the main repos, making sure you get the bleeding edge. When it comes to Arch, quality is always better than quantity.
Last edited by Acecero (2010-02-10 05:55:35)

Arch Linux review...help?

I'm working on putting together a review of AL .4 for possible web publication on any site that'll take it. But, as you may have noticed, I'm a bit of a newbie.
I'm planning on touching on the following things:
Arch's goals
Arch's install
ABS, package optimisations and pacman (maintaining an Arch system)
Running X in Arch
Then strengths, weaknesses
And a sort of verdict (ie, what Arch is best suited for, overall quality)
Now, my question for those here at the bbs: what have I left out or what do I need to touch on that I may overlook? Feel free to mention subjects that may be containted within the above headings, because I may not be grasping all the aspects of Arch's awesomeness.
The going may be a bit slow on my review, but I hope to draw a bit more attention Arch's way!

beniro wrote:I think it's gonna go up on Distrowatch, because they seem to be booming right now. I'm not totally decided on that site yet.
What I am noticing with Distrowatch, its only holding the first paragraph with a link to the full article (review) wherever you put it up. I suggest you contact Distrowatch once you decide.
Lets hope your review will help Arch Linux to rise higher on Distrowatch list. Maybe not competing Yoper, which became # 1 within two months, but to same level (or above) as CRUX Linux .
http://www.distrowatch.com/

Arch Linux Review

Here's another review for anyone that might be interested:
http://www.linux-magazine.com/issue/64/ … Review.pdf

tomk wrote:Yeah - the author (jondkent) posted here before and after publication. There are a couple of threads about it already.
Oops... you are right tomk, it has been posted before. I thought it was a new review since the mazine is showing as March 2006 but it appears to be the same review as posted before.
Can a mod please lock this thread?
Thanks!
oz

Please suggest non-English articles for Arch Linux Press Review

Good day,
If you know of any non-English language articles or reviews about Arch Linux, please contribute them to the Arch Linux Press Review wikipage. The page is found here:
http://wiki.archlinux.org/index.php/Arc … ess_Review
Feel free to edit the page directly, or post article suggestions in the thread of this topic.
Please feel free to make any corrections needed to the non-English article section of the webpage.
Translating and posting this message to other language based forums is appreciated.
Thank you,
Luke Seubert

Don't double post....
Replies go here: http://bbs.archlinux.org/viewtopic.php? … 09#p556409

Looking for addition articles for the Arch Linux Press Review wikipage

Good day all,
I recently updated the Arch Linux Press Review wikipage, found here:
http://wiki.archlinux.org/index.php/Arc … ess_Review
If you know of any additional reviews or articles about Arch Linux, please edit the wiki page or post the info as a reply.
Any contributions for non-English language articles, or corrections in that area, would be especially appreciated.
Thank you,
Luke Seubert

tlaloc wrote:
We have a collection of German reports over here:
http://wiki.archlinux.de/title/Arch_in_den_Medien
Thanks tlaloc! I transferred that list of articles over to the Arch Press Review wikipage under the German Language section, and included a link back to the German original. I also fixed a tiny spelling error in the German page. I also doublechecked all the links to make sure they are live. As the French would day, "J'encule les moustiques"
tlaloc wrote:
No damage done - just go on.
We are all behind you (eight miles behind you, so if you get in trouble ....)
But that's fine by me, just go on.
So nice to know you have my back tlaloc
Last edited by lseubert (2009-05-22 14:35:31)

Arch Linux Magazine, February 2010

Another month, another issue!
As promised, we are slowly working back towards releasing the monthly copy of Arch Linux Magazine on the first. This month I was only a few short hours off from my target time. On the flip side, this month we have a few new features (and one noticeably missing, sorry... it'll be back next month). Hopefully we'll be able to keep doing the new features and, over time, build ALM up to what I know it can be.
My sincerest thanks to those of you who continue to contribute, and for those of you who are interested in contributing in the future (or translating), we now have a wiki page designed specifically for you! As for those who are waiting for sources for translation, I haven't forgotten you and will be sending you the link in the morning... it's long past my bedtime.
And so, without further ado...
http://www.archlinux.org/static/magazine

Dieter@be wrote:whose desktop is it? maybe mention it in the article. and frankly i don't see the point of the desktop item but maybe that's just me.
If you're referring to the Desk Shot, it's my desk. The PDF has my name, but the text version doesn't seem to.
As for why...I always find it interesting to see what kind of environment people work in, simply because it can often make me feel better about mine Besides that, probably isn't much else to say for/against it. Similar to the Desk Shot thread on the forums, not too many people posted in it, but there were a few who were interested in it.

(Arch) Linux Myths

I have recently noticed that online forums and Linux user communities in particular are prone to developing what I'd like to call "technology myths".
Most of the problems and solutions given on forums are anecdotal in nature. Problems are rarely sourced to the actual code and suggestions are often casual or incomplete which is of course natural for this kind of communication. However, as certain solutions are being repeated without clear feedback, some notions take deeper roots in the collective consciousness thus becoming myths. Let me illustrate with an example.
How often have you seen people posting glxgears results? How often have you seen people replying "glxgears is not a benchmark"? Could you actually explain why it's not suitable to be one? The explanation is out there.
Another example could be the myth that exporting INTEL_BATCH=1 increases performance on Intel integrated GPUs. I have seen this in circulation for a long time, despite the fact that the actual code that could be triggered by this environment variable has been removed a long time ago.
As Arch Linux is rolling-release and a lot of code is being replaced rather rapidly, old and tried solutions are likely to become obsolete fast. I'd like to ask the Community to share their examples of other widely circulated myths and help keep an updated and sourced list of them (https://wiki.archlinux.org/index.php/Myths) so others will not waste their time trying solutions which are sure to fail.

In my experience, outdated wiki pages tend to propagate this stuff, along with blog entries. The trouble with blog entries is that they're often fire-and-forget, which means that solutions that might have been necessary a while ago are now unsuitable or unnecessary.
Wiki pages have no such excuse, being more fluid than blogs posts. This is particularly prevalent on the Arch Wiki, as Arch is a distribution with a small number but a large variety of (mostly) technically-experienced users who will often go to great lengths to increase performance or to accomodate for Rube Goldberg machine-like hardware or network setups. Thus, there are a lot of hacks on obscure pages (not, say, the Beginner's Guide or the major pages).
What we need is a major overhaul and review of many of the shorter and more obscure wiki pages, such as any of the ones under Request:Correction and Request:Expansion. I've "rescued" a few pages from this purgatory, but many pages have sat there for months or years and I do not have the experience or knowledge to improve them. I think that we could gain a great deal from more community awareness about improving the wiki and trying to encourage people to edit more. Rather than the same editors working on more mainstream pages and ignoring or barely touching the more arcane ones, it might be preferable to have people with little editing experience but more technical experience to take a look at some of the pages, capitalizing on the cumulative knowledge of our userbase a bit more.
Just a thought.

Arch Linux Handbook 2.0

Hey all,
I'd like to announce the freshly minted Arch Linux Handbook 2.0, available from the estore here:
https://www.createspace.com/3482247
It should be showing up in Amazon stores within a few weeks, and you'll be able to order it from your favourite brick and mortar store after a month or two.
Nearly 400 copies of the first handbook were sold. This one is more up to date with a fancy cover, more pages, and prettier interior. The Arch Linux Handbook is simply a print edition of the Beginners' Guide, which has seen a few hundred revisions since the first edition went to print. So it was time for an update, and here it is!
I would like to extend a huge thank you to both Jules Pitsker (Misfit) and Branko Vukelic (foxbunny). Jules is the motivating force and primary maintainer behind the online Beginners' Guide. His tireless and thankless contributions have turned it into the exceptionally well-written and comprehensive document that it is. Branko is the best designer I know, both for print and web based materials. He did a terrific job on this handbook cover.

Thank you Dusty. I appreciate your handbook, it played a role in converting me to ArchLinux.
It was important to me to see that there is printed documentation for any linux distro I use.
ArchLinux passed the test because of you.
I bought a copy of your first edition and reviewed it on Amazon. As soon as the second edition
shows up on Amazon I'll buy a copy and give it another review. I'm sure that I'll be able to say
that it is greatly enhanced and everyone should certainly own a copy.
Every Archer **should** own a copy
In fact I have my copy [rummages through closet] right HERE and I did get it out recently when I
repartitioned my SSD and did a re-install with Arch-only. It's __handy__

[SOLVED] Arch Linux won't boot

Hi,
I was bad and didn't update my packages often enough, and now my arch installation on a desktop won't boot.
I've booted off of a usb arch install, mounted all of the appropriate harddrive partitions, and used arch-chroot to switch to the offending hard drive.
The /boot/syslinux/syslinux.cfg is such:
# Config file for Syslinux -
# /boot/syslinux/syslinux.cfg
# Comboot modules:
# * menu.c32 - provides a text menu
# * vesamenu.c32 - provides a graphical menu
# * chain.c32 - chainload MBRs, partition boot sectors, Windows bootloa
ders
# * hdt.c32 - hardware detection tool
# * reboot.c32 - reboots the system
# * poweroff.com - shutdown the system
# To Use: Copy the respective files from /usr/lib/syslinux to /boot/sysli
nux.
# If /usr and /boot are on the same file system, symlink the files instea
d
# of copying them.
# If you do not use a menu, a 'boot:' prompt will be shown and the system
# will boot automatically after 5 seconds.
# Please review the wiki: https://wiki.archlinux.org/index.php/Syslinux
# The wiki provides further configuration examples
DEFAULT arch
PROMPT 0 # Set to 1 if you always want to display the boot: prompt
TIMEOUT 50
# You can create syslinux keymaps with the keytab-lilo tool
#KBDMAP de.ktl
# Menu Configuration
# Either menu.c32 or vesamenu32.c32 must be copied to /boot/syslinux
UI menu.c32
#UI vesamenu.c32
# Refer to http://syslinux.zytor.com/wiki/index.php/Doc/menu
MENU TITLE Arch Linux
#MENU BACKGROUND splash.png
MENU COLOR border 30;44 #40ffffff #a0000000 std
MENU COLOR title 1;36;44 #9033ccff #a0000000 std
MENU COLOR sel 7;37;40 #e0ffffff #20ffffff all
MENU COLOR unsel 37;44 #50ffffff #a0000000 std
MENU COLOR help 37;40 #c0ffffff #a0000000 std
MENU COLOR timeout_msg 37;40 #80ffffff #00000000 std
MENU COLOR timeout 1;37;40 #c0ffffff #00000000 std
MENU COLOR msg07 37;40 #90ffffff #a0000000 std
MENU COLOR tabmsg 31;40 #30ffffff #00000000 std
# boot sections follow
# TIP: If you want a 1024x768 framebuffer, add "vga=773" to your kernel l
ine.
LABEL arch
MENU LABEL Arch Linux
LINUX ../vmlinuz-linux
APPEND root=/dev/md0 ro
INITRD ../initramfs-linux.img
LABEL archfallback
MENU LABEL Arch Linux Fallback
LINUX ../vmlinuz-linux
APPEND root=/dev/md0 ro
INITRD ../initramfs-linux-fallback.img
#LABEL windows
# MENU LABEL Windows
# COM32 chain.c32
# APPEND hd0 1
LABEL hdt
MENU LABEL HDT (Hardware Detection Tool)
COM32 hdt.c32
LABEL reboot
MENU LABEL Reboot
COM32 reboot.c32
LABEL off
MENU LABEL Power Off
COMBOOT poweroff.com
and /etc/mdadm.conf is:
ARRAY /dev/md0 UUID=3830049a:44459d91:3ad800a8:e77f102f
ARRAY /dev/md1 UUID=a69afb27:1266d0c2:0c8966db:14500cdb
ARRAY /dev/md2 UUID=20b0675c:2fcca1a5:0882d652:06324bf6
ARRAY /dev/md3 UUID=3f0343cb:ff7342c9:fe8e73d4:ba6d61b3
ARRAY /dev/md4 UUID=287c6b6d:8cbd733c:c6e9d285:a2b14814
ARRAY /dev/md5 UUID=ccd0d21c:8103251b:2c9a32d1:bc6dcc78
and it looks to me like this agrees with blkid:
sh-4.3# blkid
/dev/sda1: UUID="3830049a-4445-9d91-3ad8-00a8e77f102f" UUID_SUB="932acc3b-f7ba-d443-cf76-9d59b663c651" LABEL="archiso:0" TYPE="linux_raid_member" PARTLABEL="Linux RAID" PARTUUID="9574bd41-8133-4c6a-b5b4-981002a41867"
/dev/sda2: UUID="a69afb27-1266-d0c2-0c89-66db14500cdb" UUID_SUB="e3de7e2c-8153-0c53-ac5d-ffc678deb269" LABEL="archiso:1" TYPE="linux_raid_member" PARTLABEL="Linux RAID" PARTUUID="fc78d66d-53a4-4c99-a29c-b881d19c1e8d"
/dev/sda3: UUID="20b0675c-2fcc-a1a5-0882-d65206324bf6" UUID_SUB="36f53577-cd9b-0c4e-4223-58123a6b2426" LABEL="archiso:2" TYPE="linux_raid_member" PARTLABEL="Linux RAID" PARTUUID="b7187772-bf01-4517-99a1-d2aa209aa35b"
/dev/sda4: UUID="3f0343cb-ff73-42c9-fe8e-73d4ba6d61b3" UUID_SUB="e583cdb9-f523-b4ea-01bb-609779ca3efe" LABEL="archiso:3" TYPE="linux_raid_member" PARTLABEL="Linux RAID" PARTUUID="df9fddd2-762b-4eb3-860c-ef79f545fa77"
/dev/sda5: UUID="287c6b6d-8cbd-733c-c6e9-d285a2b14814" UUID_SUB="ec1c493a-97f0-48e2-1659-068c25b7aa55" LABEL="archiso:4" TYPE="linux_raid_member" PARTLABEL="Linux RAID" PARTUUID="ba388b64-8f6b-4053-a695-14560832735e"
/dev/sda6: UUID="ccd0d21c-8103-251b-2c9a-32d1bc6dcc78" UUID_SUB="9b53306f-941d-8048-5780-533ada837e11" LABEL="archiso:5" TYPE="linux_raid_member" PARTLABEL="Microsoft basic data" PARTUUID="6325add3-aa39-4fa2-995c-aacf7165097c"
/dev/sdb1: UUID="3830049a-4445-9d91-3ad8-00a8e77f102f" UUID_SUB="ec3420f6-d21a-5e69-94f8-d81f277079ec" LABEL="archiso:0" TYPE="linux_raid_member" PARTLABEL="Linux RAID" PARTUUID="9574bd41-8133-4c6a-b5b4-981002a41867"
/dev/sdb2: UUID="a69afb27-1266-d0c2-0c89-66db14500cdb" UUID_SUB="4b1e7230-ffec-0985-1ac7-a69aec27eec2" LABEL="archiso:1" TYPE="linux_raid_member" PARTLABEL="Linux RAID" PARTUUID="fc78d66d-53a4-4c99-a29c-b881d19c1e8d"
/dev/sdb3: UUID="20b0675c-2fcc-a1a5-0882-d65206324bf6" UUID_SUB="4d1721b6-d87f-00b6-4bd9-45712592b033" LABEL="archiso:2" TYPE="linux_raid_member" PARTLABEL="Linux RAID" PARTUUID="b7187772-bf01-4517-99a1-d2aa209aa35b"
/dev/sdb4: UUID="3f0343cb-ff73-42c9-fe8e-73d4ba6d61b3" UUID_SUB="085a16ce-1a7c-d79e-eb92-fed6b1b70365" LABEL="archiso:3" TYPE="linux_raid_member" PARTLABEL="Linux RAID" PARTUUID="df9fddd2-762b-4eb3-860c-ef79f545fa77"
/dev/sdb5: UUID="287c6b6d-8cbd-733c-c6e9-d285a2b14814" UUID_SUB="10857018-548a-9311-178e-7d2b06e25942" LABEL="archiso:4" TYPE="linux_raid_member" PARTLABEL="Linux RAID" PARTUUID="ba388b64-8f6b-4053-a695-14560832735e"
/dev/sdb6: UUID="ccd0d21c-8103-251b-2c9a-32d1bc6dcc78" UUID_SUB="d577ff9e-a687-f335-7062-f2f629886a58" LABEL="archiso:5" TYPE="linux_raid_member" PARTLABEL="Microsoft basic data" PARTUUID="6325add3-aa39-4fa2-995c-aacf7165097c"
/dev/sdc1: LABEL="/dev/sdc1" UUID="de2a5dc6-4b22-466f-819a-86dda839c7e6" TYPE="ext4" PARTUUID="c3072e18-01"
/dev/sdc2: LABEL="/dev/sdc2" UUID="2909b560-e9b9-48cf-a194-7b7c9c38d312" TYPE="ext4" PARTUUID="c3072e18-02"
/dev/md127: UUID="3f9ddf01-4f7c-4633-844d-82a1781170a5" TYPE="ext4"
/dev/md126: UUID="7105ac32-610b-4d4b-935b-675edc71ff32" TYPE="ext4"
/dev/md125: UUID="90cc6dbe-2d0f-422b-8653-965f103b8e8d" TYPE="ext4"
/dev/md124: UUID="5fd8960f-6017-49c8-bc7e-c972aa0e2f31" TYPE="ext4"
/dev/md123: UUID="7B9075B74838729A" TYPE="ntfs"
/dev/md122: UUID="96468ceb-857b-467e-b9c7-2a37e13fde6f" TYPE="ext4"
and lsblk is:
sh-4.3# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 931.5G 0 disk
|-sda1 8:1 0 1G 0 part
| `-md126 9:126 0 1024M 0 raid1 /boot
|-sda2 8:2 0 24G 0 part
| `-md122 9:122 0 24G 0 raid1 /
|-sda3 8:3 0 15G 0 part
| `-md127 9:127 0 15G 0 raid1 /var
|-sda4 8:4 0 100G 0 part
| `-md125 9:125 0 100G 0 raid1 /home/j3doucet
|-sda5 8:5 0 100G 0 part
| `-md124 9:124 0 100G 0 raid1 /home/c2hollow
`-sda6 8:6 0 691.5G 0 part
`-md123 9:123 0 691.4G 0 raid1 /media
sdb 8:16 0 931.5G 0 disk
|-sdb1 8:17 0 1G 0 part
| `-md126 9:126 0 1024M 0 raid1 /boot
|-sdb2 8:18 0 24G 0 part
| `-md122 9:122 0 24G 0 raid1 /
|-sdb3 8:19 0 15G 0 part
| `-md127 9:127 0 15G 0 raid1 /var
|-sdb4 8:20 0 100G 0 part
| `-md125 9:125 0 100G 0 raid1 /home/j3doucet
|-sdb5 8:21 0 100G 0 part
| `-md124 9:124 0 100G 0 raid1 /home/c2hollow
`-sdb6 8:22 0 691.5G 0 part
`-md123 9:123 0 691.4G 0 raid1 /media
sdc 8:32 1 58.9G 0 disk
|-sdc1 8:33 1 19.5G 0 part /etc/resolv.conf
`-sdc2 8:34 1 39.4G 0 part
sr0 11:0 1 1024M 0 rom
Everything looks fine to me, /dev/sda1 is /boot, which has the same UUID as what mdadm has for /dev/md0, which is what syslinux.cfg has been told to boot off of. I'm not sure what to do from here.
Last edited by c2hollow (2015-01-02 00:43:56)

It's long that Arch uses rw argument on kernel command line.
You should correct your syslinux.cfg as follow.
LABEL arch
MENU LABEL Arch Linux
LINUX ../vmlinuz-linux
APPEND root=LABEL="archiso:1" rw ## <<< Here's the diff
INITRD ../initramfs-linux.img
This isn't for the fallback menu entry, you just analyze the differences and do same there.
I'm not familiar with syslinux, I just suppose you may try to test these options on-the-fly, before write them permanently. So when the syslinux menu will appear at boot time, please find the way to enter in edit mode and apply the correction. That will stay for the time you boot once. But it will ensure if it'll be good enough and do the writing later once you've booted.

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?

The Big Arch Linux Interview

The Big Arch Linux Interview
http://www.osnews.com/story/10142/The_B … _Interview
from 2005 ........ I had to dig this one out. It has a nice pic of Judd
Actually stumbled upon it searching for something else..... was an interesting read, thought I'd share it with those that hadn't read it yet.

kensai wrote:Yeah, this was back when Eugenia liked Arch Linux and Linux in general, now she don't. OSnews used to be a fair web site, but now, news about operating system hardly make it to the front page.
Now it primarily exists for Eugenia to get free hardware for "reviews" or for use as a digital video soapbox. That's when it's not reposting slashdot a day later

[Fake News] Arch Linux to change its release cycle

Today the Arch Linux community proclaimed that Arch Linux will change its release cycle and version numbering, as this was requested by billions of corporate goonies, Freemasons and Illuminati throughout the universe.
Releases will henceforth be scheduled in intervals deemed posh by the GNU/Linux community at the particular moment. The version numbering will be based on year the a new release is being published. Arch Linux "2016" will be released in early 2006. All following releases will have an offset of at least 10 years to underline how much more pure dead brilliant Arch Linux is compared to Mandrake.
To achieve a smooth transition, an transitional release will be made at once, named "Useless Marketing Edition". The Arch Linux FTP server will be configured allow one download of the iso image only. This will also be an experiment to find out how the community will be able to spread such a limited edition.
An Arch Linux user who wishes to remain nameless said in an exclusive interview with the almighty incinerator: "This is a great opportunity for Arch Linux, the new release numbering will confuse and divert computer illiterate lusers from installing our beloved Arch Linux, freeing us from answering stupid support requests. Now we can finally start to work towards our ultimate goal: To become the only GNU/Linux community being as elitist as OpenBSD's."

Ach guys, you don't get it :-(
The version numbering scheme was supposed to mock the fact Mandrake plans to release their "2006" version in 2005. That reminds of old times, when (computer) magazines were trying to beat each other releasing the most up-to-date issue to the market. The whole affair became absolutely silly, there were magazines that had the "April" issue hitting the shelves at the end of January. These "issue number wars" occur every now and then.
The funny scenario I can imagine is that other (GNU/Linux) vendors could jump onto that train and "predating" their releases further and further.
The rest is just various mockery about lusers and other things found in the Mandrake's press release. And of course the arrogantly elitist OpenBSD community always deserves getting their arses whipped ;-)

The grumpy editor's Arch Linux experience

Jonathan Corbet from lwn.net did a review on Arch Linux.
It is now available for free <https://lwn.net/Articles/638069/>.

ANOKNUSA wrote:
satanselbow wrote:Not an unreasonable article - somewhat let down by the moronic, flag waving nature of some of the comment{er}s.
I'd rather someone avoid something entirely because it requires actual thought, than have them actively demand someone else do all the thinking for them while trying to reap the reward. People who stay away from Arch because it requires more than a mouse click are dodged bullets.
Its weird how anyone using Linux (even Ubuntu) would be adverse to thought and tinkering. Even with Ubuntu, there will be cases of googleing, reading the Arch Wiki, and copy/pasteing Terminal commands to fix problems. The only difference is that Arch requires more tinkering (and an involved install process), but as a result users become more conforable with tinkering their systems. Also being able to scrutinize what packages are installed.
Unless someone merely uses Ubuntu for web browsing, they should have to tinker once in a while too. So they shouldent hate on other distros for having to do it more .
Last edited by bromanbro (2015-04-10 05:09:15)

Arch Linux Reviewed in Argentinian Magazine

Similar Messages

Maybe you are looking for