Re: [arch-general] How to disable systemd-tmpfiles-clean.timer
> -Original Message- > From: arch-general [mailto:arch-general-boun...@archlinux.org] On Behalf > Of Lukas Jirkovsky > Sent: Thursday, May 08, 2014 3:54 AM > > Please don't start another systemd flamewar. And BTW, automatic /tmp > cleaning was there since the beginning. I agree to not start a flamewar but hopefully systemd devs do not consider their SW as perfect and are looking to improve it by taking into consideration the userbase complains about it. Maybe automatic /tmp cleaning was there since the beginning but it appears that it never worked on my systems until very recently after using ArchLinux for over 2 years. > -Original Message- > From: arch-general [mailto:arch-general-boun...@archlinux.org] On Behalf > Of Paul Gideon Dann > Sent: Thursday, May 08, 2014 5:26 AM > > On Thursday 08 May 2014 09:53:41 Lukas Jirkovsky wrote: > > On Thu, May 8, 2014 at 9:46 AM, Christos Nouskas > wrote: > > > On 8 May 2014 09:43, Olivier Langlois wrote: > > >> Since a recent update (I have first noticed a couple of weeks ago > > >> this new systemd enhancement), systemd started to automatically > > >> clean /tmp directory daily. This is not something that I like as I > > >> prefer to decide when to clean up and to manually perform the clean > up. > > The /tmp directory is intended for temporary files, after all. If you need > them > to stick around, I'd recommend using /var/tmp. But yeah, masking the unit > file should solve this for you, I think. I was forecasting that this comment would come when I wrote the original request. While I agree with what you say, I think that it is reasonable to let the user have the control over when it is cleaned. Without denaturing the /tmp folder, I'm using it to experiment patches on some packages or launch computation and store results into /tmp to return back at them the next morning. I have been a bit shocked to find out one morning that my files have been deleted by my system. IMHO, this goes against the rule of least surprise which is a pillar of the unix philosophy. I understand that for some sysadmins it might be convenient to have an automatic cleanup but IMHO they should explicitly set it up. I am not too sure that this is a good default behavior. That being said, I'll try to mask the service. Thank you very much for your replies. Greetings, Olivier Please ignore the confidentiality notice below. It is automatically added without my consent. CONFIDENTIALITY : This e-mail and any attachments are confidential and may be privileged. If you are not a named recipient, please notify the sender immediately and do not disclose the contents to another person, use it for any purpose or store or copy the information in any medium.
[arch-general] problem booting and using the installation media
Hi, I am trying to boot the installation media on a small embedded system already running linux. Everything boots fine until udev starts loading modules. Approximately when the install media reach the bash prompt, the display gets garbled. I suspect that this is when the graphic mode switch from text to graphic. I have been fooling around with the video and the vga kernel cmdline params but I haven't been able to find something that works. When booting the existing system and doing: cat /sys/devices/virtual/vtconsole/vtcon0 I have this: (S) VGA+ The graphic chipset on this system is: 00:02.0 VGA compatible controller [0300]: Intel Corporation System Controller Hub (SCH Poulsbo) Graphics Controller [8086:8108] (rev 07) Does someone have suggestions of things to try to use the installation media on this system? Thank you, Olivier CONFIDENTIALITY : This e-mail and any attachments are confidential and may be privileged. If you are not a named recipient, please notify the sender immediately and do not disclose the contents to another person, use it for any purpose or store or copy the information in any medium.
Re: [arch-general] Way too much kworkers
> -Original Message- > From: arch-general [mailto:arch-general-boun...@archlinux.org] On Behalf > Of Karol Blazewicz > > On Tue, Oct 1, 2013 at 9:16 PM, Dimitris Zervas wrote: > > Hello, > > > > I've googled a bit and saw that other people have this problem too, > > but without solution. > > What do these processes do? Slow down you computer, eat up RAM ...? > If I'm not mistaken, kworker is a kernel task used to defer work from interrupt handlers into a task context. There used to be 1 kworker per cpu but workqueue design has changed. You can learn by reading Documentation/workqueue.txt in the kernel documentation package. Usually, kworkers are used by device drivers, you could maybe check if downgrading your kernel helps and narrow down the issue to a particular release. CONFIDENTIALITY : This e-mail and any attachments are confidential and may be privileged. If you are not a named recipient, please notify the sender immediately and do not disclose the contents to another person, use it for any purpose or store or copy the information in any medium.
[arch-general] glibc 2.18-5 question
Hi, I just checked what was the motivation for this 5th release and I have found: http://hmarco.org/bugs/CVE-2013-4788.html where it says: The vulnerability is caused due to the non initialization to a random value (it is always zero) of the "pointer guard" by the glibc only when generating static compiled executables. Dynamic executables are not affected. Pointer guard is used to mangle the content of sensible pointers (longjmp, signal handlers, etc.), if the pointer guard value is zero (non-initialized) then it is not effective. So, out of curiosity, how big is the threat since I am under the impression that almost 100% if not 100% of Arch binaries uses libc.so Greetings, Olivier CONFIDENTIALITY : This e-mail and any attachments are confidential and may be privileged. If you are not a named recipient, please notify the sender immediately and do not disclose the contents to another person, use it for any purpose or store or copy the information in any medium.
Re: [arch-general] Apache PID File not readable
> On Sun, Jul 28, 2013 at 8:03 AM, Stefan Tatschner > wrote: > > I always get this message after restarting apache via systemctl: PID > > file /run/httpd/httpd.pid not readable (yet?) after start. > > What does cat /usr/lib/tmpfiles.d/apache.conf return? > > > =-Jameson Wow, this thread has just made me realized that there was a run directory in root dir. I have always though that pid files were supposed to go in /var/run by convention. I'm probably late in the news but can someone explain rationales behind that? I'm guessing that it is to avoid problems with /var being a mounted fs and make sure that pidfile dir is always there by putting it in the rootfs. but then, isn't it a bit awkward considering the recent change to deprecate /bin /lib and /sbin?? CONFIDENTIALITY : This e-mail and any attachments are confidential and may be privileged. If you are not a named recipient, please notify the sender immediately and do not disclose the contents to another person, use it for any purpose or store or copy the information in any medium.
Re: [arch-general] Broken sound with Linux 3.9.2 on Acer laptop
Hello BlissSam, > After upgrading to 3.9.2 kernel, the sound did not work. > However, the system CAN recognize my sound card, and my sound card > appeared in `alsamixer` Downgrading the kernel can solve the problem. > > > Providing more info: > > Acer Aspire laptop, with Intel i5 CPU, 2nd generation SandyBridge. > > `uname -a`: > > Linux brilliant-laptop 3.9.2-1-ARCH #1 SMP PREEMPT Sat May 11 20:31:08 > > CEST 2013 x86_64 GNU/Linux > > `lspci | grep Audio`: > > 00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset > > Family High Definition Audio Controller (rev 04) > lspci -nn | grep Audio could provide some info susceptible to help. snd_hda_intel apply treat differently hda intel hardware differently depending on device id. Explore a little bit files content under /proc/asound Such as: /proc/asound/cards /proc/asound/devices /proc/asound/pcm /proc/asound/card0/codec* Fallback to simple stuff such as speaker-test -c2 aplay somewavfile.wav aplay -l aplay -L I have found it useful and very interesting to do strace -e trace=open speaker-test -c2 That shows you all config files that alsa-lib opens. CONFIDENTIALITY : This e-mail and any attachments are confidential and may be privileged. If you are not a named recipient, please notify the sender immediately and do not disclose the contents to another person, use it for any purpose or store or copy the information in any medium.
Re: [arch-general] gcc: loop do not terminate
> void testing(void)
> {
> #define NR_STRUCT_A (4)
> struct B* ptr = malloc(sizeof(struct B) + NR_STRUCT_A*sizeof(struct
> A));
>
> ptr->numelem = NR_STRUCT_A;
> ptr->item= (struct A*)(ptr+1);
>
> ptr->item[0].a = 0;
> ptr->item[1].a = 1;
> ptr->item[2].a = 2;
> ptr->item[3].a = 3;
> ptr->item[4].a = 100; /* Wrong, violate memory accessing here! */
> #undef NR_STRUCT_A }
IMO, this is a viable alternative. The only disadvantage is that it is taking
an extra sizeof(struct A *) bytes of memory, if memory space is a concern.
CONFIDENTIALITY : This e-mail and any attachments are confidential and may be
privileged. If you are not a named recipient, please notify the sender
immediately and do not disclose the contents to another person, use it for any
purpose or store or copy the information in any medium.
Re: [arch-general] gcc: loop do not terminate
> > The only time the switch makes a difference is when the program is already > incorrect. I really doubt Arch is going to enable a flag slowing down all > programs to make invalid programs behave > *differently* (not necessary as they were intended to behave, just > *differently*). > > GCC is correctly noticing a situation that would result in undefined > behaviour, > and optimizing based on the assumption that it never happens. The solution > is to write valid code not relying on undefined behaviour - accessing beyond > the end of an array is undefined behaviour regardless of whether there's > more allocated memory. > > C99 has this feature as a flexible-length array member using `foo array[];` > and > that might be valid C++11 but I'm not sure and I don't feel like digging > through the standard. Using `foo array[0]` will also work because it's a GNU > extension, but keep in mind that you've left the land of standard C++. > > Compilers are going to get better and better at optimizing away code that's > not needed if the program is assumed to be correct. I recommend using > another language if you don't want to worry about incorrect code that seems > to work now breaking from future optimizations. I hear you. I, however, disagree when you qualify the old C trick pattern as incorrect. My A B toy structs are a simplification of what I have seen in the AMD ADL SDK and was causing the loop problem with: http://code.google.com/p/overdrive5/ What is debatable, IMO, is how widespread the usage of this particular pattern is. Personally, I am not using it but I knew it for having seen it in the past a couple of times. My expectations of compiler optimization is that they should be transparent and respect the intent of the program. This optimization switch must probably be doing a lot of good stuff but this particular manifestation is, IMO, a stunning reinterpretation of an explicit request to iterate n times. CONFIDENTIALITY : This e-mail and any attachments are confidential and may be privileged. If you are not a named recipient, please notify the sender immediately and do not disclose the contents to another person, use it for any purpose or store or copy the information in any medium.
[arch-general] gcc: loop do not terminate
I have just been hit by something:
lano1106@hpmini ~/dev/gcc-test $ g++ --version
g++ (GCC) 4.8.0 20130502 (prerelease)
Copyright (C) 2013 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
lano1106@hpmini ~/dev/gcc-test $ g++ -O2 -o test1 test1.cpp test1_init.cpp
lano1106@hpmini ~/dev/gcc-test $ ./test1
item 0
a: 1
lano1106@hpmini ~/dev/gcc-test $ g++ -O1 -o test1 test1.cpp test1_init.cpp
lano1106@hpmini ~/dev/gcc-test $ ./test1
item 0
a: 1
lano1106@hpmini ~/dev/gcc-test $ g++ -O0 -o test1 test1.cpp test1_init.cpp
lano1106@hpmini ~/dev/gcc-test $ ./test1
item 0
a: 1
item 1
a: 2
lano1106@hpmini ~/dev/gcc-test $ cat test1.h
struct A
{
int a;
int b;
int c;
};
struct B
{
int numelem;
/*
* Old C trick to define a dynamically sizable array just by allocating
* sizeof(B) + (numelem-1)*sizeof(A) memory.
*/
A item[1];
};
void initArr(B *p);
lano1106@hpmini ~/dev/gcc-test $ cat test1_init.cpp
#include "test1.h"
void initArr(B *p)
{
p->numelem = 2;
p->item[0].a = 1;
p->item[1].a = 2;
}
lano1106@hpmini ~/dev/gcc-test $ cat test1.cpp
/*
* Author: Olivier Langlois
*
* Purpose: Small test to highlight gcc optimization bug
*/
#include
#include
#include "test1.h"
/*
* Create a B array with the intent of only using the first item.
* The 19 other items sole purpose is to create a buffer large enough
* to accomodate A array needs.
*/
#define MAXBLEN 20
int main(int argc, char *argv[])
{
B arr[MAXBLEN];
memset(arr,0,sizeof(arr));
initArr(arr);
for( int i = 0; i < arr[0].numelem; ++i )
{
printf( "item %d\n"
" a: %d\n",
i,
arr[0].item[i].a);
}
return 0;
}
>From gcc website, this is not a bug:
Loops do not terminate
This is often caused by out-of-bound array accesses or by signed integer
overflow which both result in undefined behavior according to the ISO C
standard. For example
int
SATD (int* diff, int use_hadamard)
{
int k, satd = 0, m[16], dd, d[16];
...
for (dd=d[k=0]; k<16; dd=d[++k])
satd += (dd < 0 ? -dd : dd);
accesses d[16] before the loop is exited with the k<16 check. This causes
the compiler to optimize away the exit test because the new value of k must be
in the range [0, 15] according to ISO C.
GCC starting with version 4.8 has a new option
-fno-aggressive-loop-optimizations that may help here. If it does, then this is
a clear sign that your code is not conforming to ISO C and it is not a GCC bug.
I am surprised that I didn't hit the problem before but I am seriously
considering using '-fno-aggressive-loop-optimizations' in my own makepkg.conf.
I just want to test others feeling on this discovery to see if it wouldn't be a
good idea to make the switch standard in Arch...
CONFIDENTIALITY : This e-mail and any attachments are confidential and may be
privileged. If you are not a named recipient, please notify the sender
immediately and do not disclose the contents to another person, use it for any
purpose or store or copy the information in any medium.
Re: [arch-general] libxml2 out of date
>
> Anatol,
>
> Here is a source package building libxml2 2.9.1. It took less than 5 minutes
> to
> modify the official repo PKGBUILD and build the new version.
>
> I haven't tested all software depending on libxml2 but I have installed it
> myself and so far so good everything works perfectly for me.
Something stripped out the bin attachement. Here is a diff:
--- /var/abs/extra/libxml2/PKGBUILD 2013-05-03 18:05:54.0 -0400
+++ PKGBUILD2013-05-07 14:16:46.141882166 -0400
@@ -3,7 +3,7 @@
# Contributor: John Proctor
pkgname=libxml2
-pkgver=2.8.0
+pkgver=2.9.1
pkgrel=1
pkgdesc="XML parsing library, version 2"
arch=(i686 x86_64)
@@ -14,7 +14,7 @@ options=('!libtool')
url="http://www.xmlsoft.org/";
source=(ftp://ftp.xmlsoft.org/${pkgname}/${pkgname}-${pkgver}.tar.gz
http://www.w3.org/XML/Test/xmlts20080205.tar.gz)
-md5sums=('c62106f02ee00b6437f0fb9d370c1093'
+md5sums=('9c0cfef285d5c4a5c80d00904ddab380'
'b255be9a1c7f7021e52448e4ec8d7a0d')
build() {
CONFIDENTIALITY : This e-mail and any attachments are confidential and may be
privileged. If you are not a named recipient, please notify the sender
immediately and do not disclose the contents to another person, use it for any
purpose or store or copy the information in any medium.
Re: [arch-general] libxml2 out of date
> > > > I believe the next question is "Hussam, Jan is there anything we can > > do to make libxml2 upgrade happen?" > > Let me put this statement other way: I have some time that I would like to > contribute it back to Linux Arch. Trying to resolve libxml2 upgrade issues > seems a useful task. Could anyone provide me more information about > libxml upgrade problems? Jan, you are the maintainer should know it. If it > brakes apps then could you give me the list? > I'll try to look at it. Anatol, Here is a source package building libxml2 2.9.1. It took less than 5 minutes to modify the official repo PKGBUILD and build the new version. I haven't tested all software depending on libxml2 but I have installed it myself and so far so good everything works perfectly for me. CONFIDENTIALITY : This e-mail and any attachments are confidential and may be privileged. If you are not a named recipient, please notify the sender immediately and do not disclose the contents to another person, use it for any purpose or store or copy the information in any medium.
Re: [arch-general] HDMI Alsa sound problem from flashplayer 64 bit
> > I was unsure what was meant by trying to set up without KDE in the > > way? I > presumed that I could only run the chrome browser within a D.E. in order to > test the problem of flashplayer running a video with sound output? It was > not clear to me how to do that unless I had a different D.E. running (i.e. > not KDE) or window manager within which to test it? Presumably I can't test > from a text console, or can I? - apart from the command which works from a > Konsole terminal within KDE as I originally posted: Mike, I cannot think what would stop you from running a browser without any DE or WM. Just edit your ~/.xinitrc. Just add firefox to it. then startx It will run fullscreen with no title bar and the usual window frame. man xinit if you want to know a little bit the role of .xinitrc file in relation with the X server execution scope. CONFIDENTIALITY : This e-mail and any attachments are confidential and may be privileged. If you are not a named recipient, please notify the sender immediately and do not disclose the contents to another person, use it for any purpose or store or copy the information in any medium.
Re: [arch-general] Request help with wired network config after initial install and reboot
> > It seems that the ifconfig command is not available once rebooted into the > install and I don't know how to proceed. > > Can anyone give my any advice on how to get the network up on the newly > installed system? > Because it hard to get rid of a good old habit: lano1106@hpmini ~ $ pkgfile ifconfig core/net-tools CONFIDENTIALITY : This e-mail and any attachments are confidential and may be privileged. If you are not a named recipient, please notify the sender immediately and do not disclose the contents to another person, use it for any purpose or store or copy the information in any medium.
Re: [arch-general] Help with making a bootable usbkey from arch for ssd drive firmware update
> I did try using unetbootin to make a freedos usbkey using freedos from the > standard list in the available options within unetbootin but the key I > prepared > would not boot! I don't know if it is critical to put the partition table > into the > key in a particular way - but I tried using gparted and making a standard > msdos partition table followed by making a new partition which was fat32 > with boot and lba labels. I have seen some articles which have the old 63 > sector start point for the first partition on the usbkey - but again when I > tried > that the key would not get recognised by the arch system when I plugged it > in. > > So is there any magic incantation in formatting the usbkey in the first place > before putting writing the MBR and placing the syslinux boot files and image > files in the key? If using grub2 via grub-install on the key is there any > magic > incantation for that ? I guess if I can get freedos to boot on the key I may > be > closer to getting something going! (Or getting sysylinux to boot - either > would be a solution) > You remember me when I had to burn Windows7 dvd on a USB key because in the middle of the installation the setup program was suddenly complaining about a missing dvd player driver even if it got loaded fine from the dvd drive! I was in a hurry to find a magic incantation or a magical recipe from the internet to do just that for literally a whole night. Before that, the last time I had to create a bootable disk was back from DOS where everything was simply done with just format /b a: I failed and after a couple of hours of sleep. I decided to take some time to just read grub2 documentation. Just by stopping trying to take shortcuts and just read the grub documentation, I have been able to build my first bootable USB key! I suggest you to do the same. Just half an hour and bootloading won't have any secrets to you anymore. CONFIDENTIALITY : This e-mail and any attachments are confidential and may be privileged. If you are not a named recipient, please notify the sender immediately and do not disclose the contents to another person, use it for any purpose or store or copy the information in any medium.
Re: [arch-general] Udisks2: auto-mounts as read-only device/with wrong permissions
> [ 85.036758] FAT-fs (sdc1): error, fat_get_cluster: invalid cluster
> chain (i_pos 0)
> [ 85.036765] FAT-fs (sdc1): Filesystem has been set read-only
> \end{code}
> The last 2 lines are not present when mounting the device via console (s.
> above). The interesting thing is that they are also mounted as writable, when
> using Gnome in fallback mode.
>
Here is another interesting point concerning your observation in the difference
of mount behavior:
From
fs/fat/misc.c in kernel source code:
/*
* fat_fs_error reports a file system problem that might indicate fa data
* corruption/inconsistency. Depending on 'errors' mount option the
* panic() is called, or error message is printed FAT and nothing is done,
* or filesystem is remounted read-only (default behavior).
* In case the file system is remounted read-only, it can be made writable
* again by remounting it.
*/
CONFIDENTIALITY : This e-mail and any attachments are confidential and may be
privileged. If you are not a named recipient, please notify the sender
immediately and do not disclose the contents to another person, use it for any
purpose or store or copy the information in any medium.
Re: [arch-general] Udisks2: auto-mounts as read-only device/with wrong permissions
> [ 85.036758] FAT-fs (sdc1): error, fat_get_cluster: invalid cluster
> chain (i_pos 0)
> [ 85.036765] FAT-fs (sdc1): Filesystem has been set read-only
> \end{code}
> The last 2 lines are not present when mounting the device via console (s.
> above). The interesting thing is that they are also mounted as writable, when
> using Gnome in fallback mode.
>
Jakob,
Concerning the cluster chain problem, you can learn more about FAT at:
http://en.wikipedia.org/wiki/File_Allocation_Table
and possibly fix the error with:
pacman -S dosfstools
man dosfsck
Greetings,
Olivier
CONFIDENTIALITY : This e-mail and any attachments are confidential and may be
privileged. If you are not a named recipient, please notify the sender
immediately and do not disclose the contents to another person, use it for any
purpose or store or copy the information in any medium.
Re: [arch-general] UEFI experience - recommendations needed.
> -Original Message- > From: arch-general [mailto:arch-general-boun...@archlinux.org] On Behalf > Of Mike Cloaked > Sent: Saturday, January 05, 2013 3:24 PM > To: General Discussion about Arch Linux > Subject: [arch-general] UEFI experience - recommendations needed. > I would be interested to hear from anyone with this kind of experience > running arch - if it is useful the motherboard I am using is an Intel DQ77KB > (which I intend to update with the latest BIOS firmware) and with the Intel > i3- > 3220T CPU. > > Thanks for any replies (and useful links) > > -- > mike c Mike, My first experience with Arch Linux has been to install it on a UEFI system (Asus P9X79 WS MB). I have used grub-efi. At first, I was impressed with the fast boot time. However now that I have experience with several older BIOS based setup, I am now unsure by how much I can attribute the fast boot time to UEFI vs Arch slimness. To be honest, I had 0 problem with installation and UEFI usage. Beside installation, there is very few noticeable difference between BIOS and UEFI. I have insisted to use it just because I had a MB capable of UEFI. If you want to try UEFI, my advice is. Go for it, there is not much risk to do it but do not expect a big change. This won't shake your world! CONFIDENTIALITY : This e-mail and any attachments are confidential and may be privileged. If you are not a named recipient, please notify the sender immediately and do not disclose the contents to another person, use it for any purpose or store or copy the information in any medium.
Re: [arch-general] Nvidia Driver woes on Macbook 3,2
> > Daniel Bryan: > > > Here's what I've tried in EFI mode: > > > > - standard nouveau setup - X sort of starts up but there are weird > > artifacts, mouse doesn't work, and it freezes up pretty quickly. > > I had the same problem and found the following solution: > > - Install xf86-video-fbdev > This is very interesting. I was confronted with a similar problem with an old Nvidia card. I had weird visual artifacts with Nouveau and my card support has been dropped by the latest Nvidia driver. Their latest driver that supported it required Linux 2.6 I ended up installing xf86-video-vesa as suggested in the Beginner's installation guide. It works well except for a reduction of the maximum resolution to what was available prior to switching to Arch. (this Pc is coming from Linux 2.6 Ubuntu system) I could not find much info about xf86-video drivers by finding such pages like: http://cgit.freedesktop.org/xorg/driver/xf86-video-fbdev/ What is the difference between fbdev and vesa x driver? If my system is booting fine with the fb video driver for the vconsole, should I be better with the X fbdev video driver? CONFIDENTIALITY : This e-mail and any attachments are confidential and may be privileged. If you are not a named recipient, please notify the sender immediately and do not disclose the contents to another person, use it for any purpose or store or copy the information in any medium.
Re: [arch-general] rootfs remains in ro at boot on fresh install with new December ISO
Tom, As requested, here is my fstab file. As you'll see, there is nothing fancy in it. /dev/sda1 isn't mounted as it is just my 2MB grub partition. > > Since I didn't want a tmpfs mounted in /tmp, I did follow directives from > the Beginners guide: > > > > systemctl mask tmp.mount > > > > The result of that thing is: > > > > 1. rootfs is ro. > > > > 2. My disk partition for /tmp speficied in fstab isn't mounted. > > FWIW, if you have a /tmp entry in your fstab you don't need to mask > tmp.mount (the fstab takes precedence). The only time you need to maks > tmp.mount is if you don't want a partition mounted on /tmp at all. > Yep, I have discovered that as well during my experiments :-) CONFIDENTIALITY : This e-mail and any attachments are confidential and may be privileged. If you are not a named recipient, please notify the sender immediately and do not disclose the contents to another person, use it for any purpose or store or copy the information in any medium. fstab Description: fstab
Re: [arch-general] rootfs remains in ro at boot on fresh install with new December ISO
Dave, Tom, Thank you very much for your explanations. With your help, I have become a little bit less clueless about systemd and Arch initramfs system. by typing systemctl status /, the reported status was ok/mounted with some green on the output. Nothing special to report about that. I wish that I could provide the exact text but I still suck at cut & pasting without a mouse! However I have fixed my problem and I think that I have stumbled into a systemd bug. Since I didn't want a tmpfs mounted in /tmp, I did follow directives from the Beginners guide: systemctl mask tmp.mount The result of that thing is: 1. rootfs is ro. 2. My disk partition for /tmp speficied in fstab isn't mounted. If I undo the change with: systemctl unmask tmp.mount everything comes back all right as expected. Not sure if it does that systematically for any fstab setup or I have been unlucky to have an extraordinary and unique fstab setup (I don't think so). Maybe someone could try to repeat the problem. If it is, then we have found a systemd bug, if not, I can share my fstab with interested parties. Greetings, Olivier > > You'll want to actually provide your /etc/fstab as well as the output > of: > > systemctl status / > > Right after booting... > > > 5. Once logged, I have no problem doing "mount -o remount,rw /" > > 6. I have removed the ro kernel parameter option in grub.cfg (BTW, why is > this used at all? I'm a little bit ignorant about Linux booting good > practices). By > doing so rootfs still remains ro. > > 'ro' is the default if neither 'rw' nor 'ro' are specified. If you want your > root to > be mounted rw initially, you need to do 2 things: > > 1) explicitly add 'rw' to your kernel cmdline > 2) include the fsck hook in your initramfs > > Otherwise, it's left up to your /etc/fstab to ensure that it's remounted > properly. > > > I am suspecting either systemd or the content of the initramfs. Until now, > those are still black boxes to me. What should I look at to resolve my rootfs > ro problem? > > Strange suspicion... Without seeing it, I suspect your /etc/fstab is at fault, > simply because I've learned better than to trust anecdotal evidnce. > > d CONFIDENTIALITY : This e-mail and any attachments are confidential and may be privileged. If you are not a named recipient, please notify the sender immediately and do not disclose the contents to another person, use it for any purpose or store or copy the information in any medium.
[arch-general] rootfs remains in ro at boot on fresh install with new December ISO
Hi, I hope it is not caused by the shortcut that I have taken to update my usb install key from november iso to december iso as described in the other thread. The first symptom that I have observed is that dhcpcd isn't able to update /etc/resolv.conf I am going to provide as much relevant info so you can tell me what to look for 1. Installed from december iso on newly created GPT ext4 partitions 2. Bootloader GRUB2 3. Did a systemctl mask tmpfs as I am mounting a disk partition on /tmp from fstab 4. Double checked 2-3 times that all my mounts are rw in fstab 5. Once logged, I have no problem doing "mount -o remount,rw /" 6. I have removed the ro kernel parameter option in grub.cfg (BTW, why is this used at all? I'm a little bit ignorant about Linux booting good practices). By doing so rootfs still remains ro. I am suspecting either systemd or the content of the initramfs. Until now, those are still black boxes to me. What should I look at to resolve my rootfs ro problem? thank you very much! Olivier (A new Arch user and extremely happy to have found and tried your distribution!) CONFIDENTIALITY : This e-mail and any attachments are confidential and may be privileged. If you are not a named recipient, please notify the sender immediately and do not disclose the contents to another person, use it for any purpose or store or copy the information in any medium.
Re: [arch-general] [arch-announce] December: time for a new install medium
Hi Robbie, > > I know it's not really necessary, but I always like to have the most > up-to-date > Arch live on my toolbox USB stick. Is there a recommended way to update an > existing USB install medium (without overwriting other files?), or should I > just > follow the steps at [1], and update the syslinux configs each time? > > [1] > https://wiki.archlinux.org/index.php/USB_Installation_Media#Without_over > writing_the_USB_drive don't know if there is a recommended way but I did just that this weekend. 1. Mount iso and copy the arch,EFI and loader directory (it worked but maybe I should delete destinations directories first to avoid conflicts with old files not updated) 2. I have reexecuted extlinux install (possibly optionnal but I have played it safe) 3. You can skip the copy of the 440 bytes MBR bootstrap code. Updating files have no impact on it. 4. Modify 3 cfg files in /arch/boot/syslinux and /loader/entries to replace archisolabel with archisodevice That is all there is to do to update your usb key. CONFIDENTIALITY : This e-mail and any attachments are confidential and may be privileged. If you are not a named recipient, please notify the sender immediately and do not disclose the contents to another person, use it for any purpose or store or copy the information in any medium.
Re: [arch-general] Fail to run startx
> -Original Message- > From: arch-general [mailto:arch-general-boun...@archlinux.org] On Behalf > Of Lu, Boying > Sent: Monday, November 26, 2012 9:27 PM > To: arch-general@archlinux.org > Subject: [arch-general] Fail to run startx > > After installing the base system, I tried to configure X. But 'startx' failed > and I > found following error messages in the /var/log/Xorg.0.log: > > AIGLX error: vboxvideo does not export required DRI extension > AIGIX: reverting to software rendering > > Can anyone tell me how to fix this? > Here are a couple of suggestions: 1. When xstart returns: echo $? # Will give you return value of xinit. Might not be very enlightening if 0 or -1 but it could tell you if the process has been terminated by a signal 2. Before executing xstart, type the following commands: echo "/tmp/core.%e.%p" > /proc/sys/kernel/core_pattern ulimit -c unlimited If your X server core dumps a core dump will be created in your tmp directory. CONFIDENTIALITY : This e-mail and any attachments are confidential and may be privileged. If you are not a named recipient, please notify the sender immediately and do not disclose the contents to another person, use it for any purpose or store or copy the information in any medium.
