Arch Linux Question

[raymac46]

First of all, how often is it advisable to update Arch Linux? When I have done an update of my VBox install, I sometimes get a weird boot screen where the timer counts down from 5 to 1, then counts down from 5 to 1, then counts down from 5 to 1 ...ad nauseum. The only solution is to nuke the VBox and restore an older version that usually runs OK. After that I don't think it's advisable to update at all.

When Arch works after an update I always back it up right away. The last update I did I believe changed the kernel so that may have something to do with it. Or maybe there's a Syslinux problem.

[abarbarian]

At least once a week. You need to do a reboot after a kernel update.

[raymac46]

I reboot after every update and that's when I typically run into this problem.

[raymac46]

Well it worked this time. I had forgotten to install the Linux headers, so I did that, updated again and then rebooted VBox and the Arch Linux guest. Everything worked and so I backed it up. I'll wait till next week to update again.

[securitybreach]

I update 4-5 times a day and only reboot after a kernel update. BTW I run the Testing branch and it is still very stable.

[saturnian]

I update 4-5 times a day and only reboot after a kernel update. BTW I run the Testing branch and it is still very stable.

 

Wow, that's a lot.

 

I don't know what's "advisable," but I try to update at least once a week. Twice a week if I can get around to it.

 

Hey, I wasn't even aware of Arch's Testing branch! Or, maybe I ignored (or forgot about) the testing repos: https://wiki.archlinux.org/index.php/Official_Repositories

[saturnian]

and only reboot after a kernel update

 

What about after a systemd update? I don't know if it's necessary to reboot then; so, since I'm not sure, I reboot.

[securitybreach]

Well I do not think you need to reboot for systemd update but you can simply reload systemd and all the daemons with this command (scans for new and/or changed units):

 

# systemctl daemon-reload

[saturnian]

Wow. Thanks, securitybreach! I'll add that to my notes.

[securitybreach]

Not a problem, glad to help

[saturnian]

I just want to thank the folks here (securitybreach and abarbarian, specifically) who helped me out when I was getting a feel for things with Bridge Linux and ArchBang. From what I understand, I would have been banned from the Arch forums for even mentioning that I was using those Arch derivatives. Well, I still have the ArchBang and Bridge installations running fine... I just don't think that I would have gone on and installed Arch without trying those two first, or without info that was provided here in response to some of my questions. I understand that those distros "are not Arch" and all that, but I thought it was best for me to take this approach, and I really appreciate that you folks didn't skewer me for not starting out with "the real thing." That's all.

[abarbarian]

what I helped someone. Blimey I'm going to faint with the shock of it

 

You might be interested in these Arch derivatives.

 

http://antergos.com/

 

This MATE is quite neat the live usb I tried flew along,

 

http://mate-desktop.org/blog/2014-01-30-mate-desktop-live-cd/

 

http://www.reddit.com/r/linux/comments/1wigga/the_mate_desktop_live_cd/

 

So no skewering here. Well I do do the odd kebab.

 

As to unfriendly Arch forums. Well they are Arch forums so they are entitled to be upset if someone is so pig ignorant as to start talking about other distros and using up precious expensive bandwith. If folks want to talk about their distro then do so on their own sites or on some open site.

It ain't exactly a new idea. You try standing at the Kop end at Anfield and shout out "Man united are great and see what reaction you get

[securitybreach]

Well you would of not been banned from the Arch forums but you would of probably been flamed for asking though...

[saturnian]

From https://wiki.archlin...orum_Etiquette:

 

Respect Other Distributions and Operating Systems

 

Maligning other GNU/Linux distributions, operating systems, or users thereof is prohibited. The entire Arch team is happy to volunteer their time and energy to provide you with the Arch Linux distribution, documentation and forums. Kindly show respect toward the volunteers, users and communities of other distributions and operating systems as well. Views, experiences and opinions are always welcome, but unproductive slander is not.

 

 

Arch Linux Distribution Support ONLY

 

Arch-based distributions often use different packages, package versions, repositories, and make custom system configurations surreptitiously, constituting support for such projects quite impossible on the Arch forums. Community technical support shall only be provided for the Arch Linux distribution and the Arch User Repository. Threads concerning issues with, and requesting support for, derivate distributions, or operating systems other than Arch Linux are strictly prohibited and will be closed.

 

 

I think that's fair enough.

 

I don't care much for what's been called "distro tribalism" or the "our team only" way of thinking at some distro's forums; as someone who uses (and has used) several different distros, it's much more pleasant to participate at some of the oher distros' forums where discussion of a different distro isn't a big deal. I've probably been spoiled by, for example, the Mepis forums, where I could happen to mention an issue I'm having with, say, openSUSE, and someone familiar with that distro might be nice enough to take the time to try to point me in the right direction. But I completely understand that things can't be like that at every distro's forums.

[raymac46]

I think most of the stability issues I've had are due to me running Arch in VirtualBox - which isn't the most stable way to use any distro, frankly. At least not compared to an actual install. Debian Jessie has also given me some static in VirtualBox.

One further question - is it advisable or even mandatory to install the kernel headers as part of the Arch installation process? I did not do that originally.

[abarbarian]

I think most of the stability issues I've had are due to me running Arch in VirtualBox - which isn't the most stable way to use any distro, frankly. At least not compared to an actual install. Debian Jessie has also given me some static in VirtualBox.

One further question - is it advisable or even mandatory to install the kernel headers as part of the Arch installation process? I did not do that originally.

 

http://unix.stackexchange.com/questions/63228/what-package-could-linux-headers-3-7-5-1-arch-mean

 

You can find the answer here.

[raymac46]

Did the inquiry and did not see anything obvious. It might have to do with the vboxvideo or other modules though - specific VirtualBox stuff.

I still have a sneaking suspicion my problem is an occasional glitch with Syslinux.

[abarbarian]

is it advisable or even mandatory to install the kernel headers as part of the Arch installation process?

 

My link answered your Q.

 

 

The linux-headers package in many Linux distributions generally contain the C header files (files with the .h extension) for the Linux kernel. These files generally define constants and functions that can be used by other programs and drivers.

You generally need the kernel header files in order to compile and install 3rd party drivers for the kernel.

 

From the Wiki,

 

https://wiki.archlinux.org/index.php/Installing_Arch_Linux_in_VMware

 

 

Installing the official VMware tools

 

Install the ifconfig(1) program for the installer to work properly from net-tools.

Install Linux kernel headers (linux-headers) for the installer to work properly:

 

[raymac46]

VmWare is slightly different from VirtualBox but probably the principles are the same. Anyway I've got linux-headers installed now so I'll see if that fixes things.

Edited April 3, 2014 by raymac46

[raymac46]

Still having some issues with restarting Arch in VBox after an update so I've nuked everything and started over:

• I've used grub this time as a bootloader rather than Syslinux.
  
• I've only installed the Xfce desktop.
  
• I've not yet installed a graphical display manager. I'll log in and start X manually for a while.
  

 

I'll see if this improves matters.

[securitybreach]

It has been mentioned but perhaps the virtualbox wiki entry could provide some assistance:

https://wiki.archlinux.org/index.php/VirtualBox#Installation_steps_for_Arch_Linux_guests

[raymac46]

Oh, it certainly did help. That's the advice you need to get X working after you install it. I think the real things I found out so far:

• Keep it simple and don't bother with a graphics display manager. Just log on in the console and startx.
  
• It is a lot easier the second time you install Arch. You actually learn something the first time.
  
• If there's one distro where you want to RTFM it is Arch. Documentation is amazing.
  
• Take it slow and make sure what you've done is working OK before you move on. You can install 10 window managers at once, but that doesn't mean you should.
  
• Xfce is as usual a great choice for a DE. It isn't minimalist but it is less complicated than say, Cinnamon or Gnome Shell.
  

[ichase]

ray, my hats off too you for doing things "your way", we all have our own comfort zone and if we sway from that, I think we often loose the "fun" aspect that comes with learning linux. I wrote this blog on LinuxQuestions.org back in 2010 that kinda sums up my look at linux and how and what made me go in the direction I did. Linuxville

 

I like threads like this one because you often times learn more than what you knew before you started reading. For example:

# systemctl daemon-reload

New to me, but now I have a new alias

 

I know we have more guest that read BATL then post and I am sure so many that have never posted have probably learned a ton of things from just being here reading. If you are a guest and you like what you read; Create a login and join us. I happen to think there is no better place on the web to feel comfortable asking questions and giving your advice then Bruno's All Things Linux.

[securitybreach]

I completely agree and it's nice to see you back around these parts Ian

[raymac46]

This has always been a great place to hang out and learn. Although we've had some certifiable gurus here (and still do) there's always been an atmosphere of friendliness and helpfulness here that you rarely find anywhere else in Linux forums. We all know why, and who developed this atmosphere. His presence still directs the way we operate.

Although the only place I feel like a guru is in VirtualBox, I feel I see the big picture in a lot of hardware/software issues so I believe I can contribute as well as learn. This site has great forums on Windows, hardware and security as well.

Edited April 6, 2014 by raymac46

[ichase]

Although the only place I feel like a guru is in VirtualBox, I feel I see the big picture in a lot of hardware/software issues so I believe I can contribute as well as learn.

Well from someone who religiously runs VirtualBox, I now know who to ask when I have problems. And besides taking snapshots weekly of my VM's, I often find myself running into problems "after" I run virtualbox guest additions. So, instead of re-imagining from my snapshots, I know who I am going to ask.

 

Case in point, I have about 7 active VM's. All work great except for Arch. It works, but for some reason it's the only VM I have that will not pull the sound from the host? This should be it's own thread, but "sound" is not something I absolutely require. I mainly just run Arch in VM on my work laptop with a Win7 host. But sound does not work with the Arch host either. Hmmmmmm. Like I said, not a big enough deal to create an individual post.

 

Ok, ray....I'm going to put you to the test on ANOTHER question I DO have in regards to VBox and I AM going to create an seperate post for it. Got your thinking cap on.

[raymac46]

Tried an answer in the other thread but again you need to back up before trying it.

As far as sound goes in Arch/VBox you need to install alsa-utils on the guest and then run alsamixer and unmute the playback.

 

Look at about the 5 minute point of the video.

[raymac46]

Another crash after a recent update. The fault lies with the pcre upgrade which is some sort of Perl library I think. I get libpcre.so.1 file too short errors and then X won't start.

I can't upgrade because the system will crash.

Have you folks who run Arch natively seen this before? What can be done?

[securitybreach]

I have never seen this but if you could post the exact error, I may be able to help you. BTW I have 6 arch machines here and I have not gotten any errors on them lately. So this issue is not widespread.

 

Still running it in VirtualBox?

[raymac46]

Yes still running in Vbox. I'll have to upgrade again and break my system to get the exact error. Hold on. I'll be back.