ArchThis Forum is for the discussion of Arch Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I haven't had this much fun installing a system since Slackware in the 90s, boot floppies over 14.4 modem, and 486 pc. Every distro comes with so much automagic and eye-candy these days I always want to rip it apart, strip it to bare metal, but with Arch I'm taking baby steps learning about brand-new-generation Linux from the bottom up. It's come a long way in the 10 years since I installed Mandrake10 on my trusty old laptop in 2005.
I acquired a Dell OptiPlex 755 about 3 years old that is in desperate need of a new OS. Someone already had the sense to nuke the Fisher-Price(tm) OS that it came with. It still has the sticker on the top that declares Proof of License and Certificate of Authority, along with a mystical 25 digit number that will solve all your problems, maybe cure your asthma too. My box has been blessed by the Big G himself, or at least one of His angelic minions. Woo hoo
Anyhoo, I like the assembly of hardware that is now reborn under the constellation of Linux. I think it'll live a good service life and keep me educated and entertained for a few years, hey, maybe a decade, like it's older brother who's retiring to remote-login-land print-server. Basically nap in the corner until the Samsung-ML1660 packs it in.
Over the past few weeks I've gone through about 10 different distros. All of them have been unsatisfactory to me in some way or another. Mostly useless cruft and over-complicating basic things. I won't mention any names of the worst offenders (cough-selinux-cough...) but I'd like to give a shout-out to the clever peeps at ArchLinux HQ that put this together.
Someone already had the sense to nuke the Fisher-Price(tm) OS that it came with. It still has the sticker on the top that declares Proof of License and Certificate of Authority, along with a mystical 25 digit number that will solve all your problems, maybe cure your asthma too. My box has been blessed by the Big G himself, or at least one of His angelic minions. Woo hoo
thanks for this. it didn't make my day, but it surely spiced up this linuxquestions session .
keep'em coming!
I'm still getting my head around udev/systemd. My last systems were all devfsd/sysvinit. Without the ability to hack around as root in runlevel3, rebooting constantly and watching dmesg/journalctl, I'd still be mystified by it all. The thing reboots in 30 seconds, from reboot to login. Sweet.
Once everything is working to my satisfaction, making it look pretty with XWindows is no big deal. The only thing I need X for is web browser and office suite, maybe some fun stuff like dosbox.
At first I was cursing systemd, until I got to know it a bit better. "WHERE'S MY !@#$% LOGFILES!!!" heh heh. It's pretty clever, I have to say. Udev is weird. I'm still working on that one, but I've only been at it a few days.
Come back and tell us this after you have to roll back a few packages after a pacman -Syu
I stray but I always come back to Arch because it's more flexible but I dunno about the best thing since sliced bread
Yeah. I'm getting to see some of Arch's annoyances. But still, just the option of near-complete customization is such a relief after so many auto-magic installs that are never what I want.
Re pacman -Syu: I'm not sure I'd even try that. Everywhere I go I see complaints about stuff not working after the auto-magic is done it's thing.
I've been installing packages individually as I need them, and even then I get fails. For example, when I went to install archlinux none of the repos had screen-4.2.1-3, which was required. I don't need screen, so I told it to ignore. But what if this happens during -Syu? Also ffmpeg package downloaded everything BUT ffmpeg. Nobody has ffmpeg-1:2.6.3-3-i686. Ergo, the package fails.
This is annoying. I can get source and compile it (ffmpeg is a pain to compile, but I've done it before). Where do I get this particular package to satisfy package deps if the repos don't even have it?
Re pacman -Syu: I'm not sure I'd even try that. Everywhere I go I see complaints about stuff not working after the auto-magic is done it's thing.
Arch is like a bike -- it's only stable when it's rolling.
You should use `pacman -Syu` regularly.
If there are any problems with updated packages (and there *will* be at some point) then they will be much easier to troubleshoot and track down if the list of upgraded packages is relatively short, ie, if you have kept the gap between updates small.
Nobody has ffmpeg-1:2.6.3-3-i686. Ergo, the package fails.
what?
i have it:
Code:
$ uname -m
i686
$ pacman -Ss ffmpeg
extra/ffmpeg 1:2.6.3-1 [installed]
Complete and free Internet live audio and video
broadcasting solution
(actually i have a slightly older version because i haven't made a "pacman -Syu" on this sytem for a while)
if you can't install it it's probably a consequence of keeping your system only partially up-to-date.
if you posted this on archlinux forums, you would pretty soon get a moderator response: "Partial updates are not supported."
Yeah. That's about the only way to support a given distro. There's the basic Linux support, then distro support, then individual package support. 3 competely different things, from completely different places.
Frankly, I think it's kinda magic that I can just type a simple command and it goes out and fetches the freshest software available for my system. I'm used to digging through CDs and archives looking for a reasonable match for whatever I need. Then the compiling process, fetching all the libs and utilities and stuff. In the end it's nice, but the process can be frustrating.
There's a few things I insist on compiling myself, but for most stuff it's best when it just works.
i've been a slacker for years, decided to give arch a try in a virtual machine. got it working with xfce. Decided to move it over to my main desktop and had it up and running with X in about 40 minutes max.
i've been a slacker for years, decided to give arch a try in a virtual machine. got it working with xfce. Decided to move it over to my main desktop and had it up and running with X in about 40 minutes max.
It been 2 weeks since I made the original post, and I'm still happily banging away at Arch.
I'm on my 4th install: 1st one I borked trying to understand this new-fangled systemd stuff. 2nd one I borked messing with udev. 3rd one got borked installing grub to flash drive and it rudely stomped partition table on sda1. Bad doggy. (That incident had nothing to do with Arch). This one is pretty much borked hacking at security, so next install will likely be in a day or 2.
Let's see what I can break next...
Addenda: There are some very interesting things about the system (that may or may not have much to do with Arch itself) that seem worth mentioning:
I like the new filesystem heirarchy, all libs in one place, all the bins pointing to the same thing. Nice. Never did make much sense the old way. Artifacts of small hard drives.
The package handling system kicks ass. It's cool to see the growth of package handling since rpm came out. Then deb. Then broadband and repos. I like tarballs with metadata you can ignore if you like, but they install like rpms otherwise. Very clever, and simple.
I'm still on the fence with systemd. I like sysvinit for it's essential simplicity. Systemd tries to do too much I think. Do one thing and do it well. It's a good motto for programming, and Linux in general. I'm not so keen on all the binaries in /lib/systemd. They should be perl scripts.
Udev is cool but config seems over-complicated. I have permissions problems in /dev constantly. Udev seems to like changing permissions on things when it's bored. Maybe it's something else changing permissions. Could be pam, that's what I'm banging on now. Does somebody have a link to a GOOD tutorial on udev? Or is there some tidbit I've overlooked?
Excellent. This Arch n00b thanks you for the good links.
I might just play with OpenRC. Maybe bork my system again See, I have this little problem: Arch just sorta works, and then I have nothing to fix, so I get bored and start poking around...
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.