- Arch-general - lists.archlinux.org

[arch-general] lm_sensors
by ponto 29 Aug '09

29 Aug '09

i've used sensors-detect and it gave me: Now follows a summary of the probes I have just done. Just press ENTER to continue: Driver `coretemp': * Chip `Intel Core family thermal sensor' (confidence: 9) Do you want to overwrite /etc/conf.d/lm_sensors? (YES/no): Copy prog/init/lm_sensors.init to /etc/rc.d/lm_sensors for initialization at boot time. You should now start the lm_sensors service to load the required kernel modules. and sensors started to give me: sensors coretemp-isa-0000 Adapter: ISA adapter Core 0: +56.0°C (high = +100.0°C, crit = +100.0°C) coretemp-isa-0001 Adapter: ISA adapter Core 1: +60.0°C (high = +100.0°C, crit = +100.0°C) acpitz-virtual-0 Adapter: Virtual device temp1: +60.0°C (crit = +94.0°C) was not suppose to give the fan's rpm's and so and so? oh, pwmconfig does outputs me this: pwmconfig # pwmconfig revision 5630 (2009-01-29) This program will search your sensors for pulse width modulation (pwm) controls, and test each one to see if it controls a fan on your motherboard. Note that many motherboards do not have pwm circuitry installed, even if your sensor chip supports pwm. We will attempt to briefly stop each fan using the pwm controls. The program will attempt to restore each fan to full speed after testing. However, it is ** very important ** that you physically verify that the fans have been to full speed after the program has completed. /usr/sbin/pwmconfig: There are no pwm-capable sensor modules installed as this have to do with the supose missing values on lm sensors?

1 0

[arch-general] "hardware clock" on a VPS
by Pierre Chapuis 28 Aug '09

28 Aug '09

Hi everybody, I was wondering if there's a means to specify, in rc.conf or somewhere else, that you never want to set your hardware clock. That's because, on Xen-based VPS, the hardware clock is handled on the hypervisor level, and /etc/cron.hourly/adjtime gives warnings such as: Cannot access the Hardware Clock via any known method. Use the --debug option to see the details of our search for an access method. An easy workaround is to delete this file but it will come back after each initscripts update. Does anybody know a solution to prevent that? -- catwell

2 2

[arch-general] 404 on 'view svn entries' in package details on archlinux.rog
by solsTiCe d'Hiver 28 Aug '09

28 Aug '09

hello, when you click on 'View svn entries' on quite a few package in details on archlinux.org, you end up on 404 page. is it a side effect of the massive package deletion reported some time ago ? is it another quirk or hiccup, or server migration ?

4 3

[arch-general] PKGBUILD for updated libldap
by ludovic coues 28 Aug '09

28 Aug '09

I've see that libldap is version 2.3.43 on arch, and the last release on there website is 2.4.17 . I attach the PKGBUILD with this mail.

2 1

[arch-general] server with an encrypted non-root disk
by Dieter Plaetinck 27 Aug '09

27 Aug '09

Hi, I have a little server at home which has an encrypted disk mounted at /home/media/1tbdisk I added it to crypttab and the decrypted dm device to fstab, but i have the following problems: 1) the keymap upon luksOpen is qwerty, even though i have my keymap set in rc.conf and added 'keymap' to hooks in rc.conf I ran `mkinitcpio -p kernel26` in the shell that the init(script) gave me when it tried to mount /dev/mapper/decrypted (after i mounted -o remount,ro /). Do i really have to run mkinitcpio again from the real system and reboot? (i can do it, but would like to know what might have gone wrong here) 2) even when i'm sure i'm typing correct pass (in qwerty) it doesn't unlock. i added dm_crypt to modules in rc.conf but no change. it asks the pass 3 times and then fstab tries to mount the nonexisting device and i get the shell If i comment out the entries in crypttab and fstab and unlock+mount myself after boot, it works fine. 3) even if for some reason one fails to unlock the volume, it would be nice that the boot process can continue. maybe there could also be a timeout: not unlocked within 60s, continue boot process. is this possible to do or would it make things too complicated? 4) suppose one can fix the stuff in the shell that you get from the fstab hook, is it possible to just resume boot instead of rebooting? 5) any other thoughts about this kind of setup? I know it's possible if you have IPMI to do serial over lan and type your password from anywhere around the globe during bootup. but i don't have ipmi, so if no-one can unlock the volume in x seconds, it can continue booting. Dieter

2 2

[arch-general] which package provides ifup & ifdown command ?
by Partha Chowdhury 27 Aug '09

27 Aug '09

i cannot find ifup and ifdown in any of the paths- not as a normal user nor as root user. only command i can use is ifconfig. so i was wondering which package provides these two binaries ?

9 9

[arch-general] arch-release
by richard terry 27 Aug '09

27 Aug '09

/etc/arch-release Anyone know what is meant to be in this file The guys on the gambas user list are writing some sort of script so users can identify details of their system in case of bugs etc, and i was asked if this file exists, which is does, but it is empty? ?any other unique arch identifiers.

13 20

[arch-general] introducing kernel26-lts
by Andreas Radke 27 Aug '09

27 Aug '09

Today I've added a 2nd kernel to our svn called "kernel26-lts". It should help to make you less caring about kernel updates. The intention is to 1) have a 2nd choice for the kernel pkg that suits better in certain situations and 2) it can be a fallback when a reboot after updating the core "kernel26" fails more detailed: 1) pkgdesc="The Linux Kernel and modules - stable longtime supported kernel package suitable for servers" The current longtime supported kernel version is 2.6.27.xx, right now we are at 2.6.27.31. The pkgdesc should clearly say what it should become in the future. Server systems won't be forced to take the risk to fail on the next boot after each kernel update. Modifications will be very small in the future within its lifecycle. The kernel configuration is based on the last .27.x config form our core pkg with small changes it has become in later versions + optimizations for server usage taken from here: http://www.serverwatch.com/tutorials/article.php/3715071/Ubuntu-Server--Ker… main changes are: 100Hz, no preempt, deadline I/O schedular. There will be no 3rd party modules. And no further patching. 2) a fallback kernel für almost everybody: a long requested feature. Everybody can install it along the core "kernel26" pkg and add lilo/grub entries for the "lts" kernel. Whenever an update of a future kernel26 will fail you won't be forced to boot with a rescue stick or cd. This should help a lot. attention: 2.6.27 kernel haven't had full ext4 support. I myself run a desktop with an ext4 / partition created with a later kernel version. the "lts" kernel is not capable to boot into this filesystem! But on real servers I guess everybody will wait a bit longer to use ext4. For the future it is planned to probably add Xen support to this or an outsplitted pkg. I will upload packages for both architectures to testing over the next days. Please discuss when you want see changes to the config file (x86_64 is done, i686 is not ready so far). -Andy

13 23

[arch-general] How to choose which grub entry boots next from the cli via ssh in Arch?
by David C. Rankin 26 Aug '09

26 Aug '09

Listmates, How do I choose which grub entry will boot the next time the machine is rebooted from the command line? In suse there is a package called 'grubonce' which you issue from the command line giving the grub entry you want to boot next. Example, if your menu.lst looks like: # (0) Arch Linux - The Ferarri of Distros title Arch Linux on SuperSFF root (hd0,7) kernel /boot/vmlinuz26 root=/dev/sda6 ro vga=0x317 initrd /boot/kernel26.img # (1) Arch Linux title Arch Linux Fallback root (hd0,7) kernel /boot/vmlinuz26 root=/dev/sda6 ro initrd /boot/kernel26-fallback.img # (2) Arch Linux LTS title Arch Linux LTS on SuperSFF root (hd0,7) kernel /boot/vmlinuz26-lts root=/dev/sda6 ro vga=0x31a initrd /boot/kernel26-lts.img I could issue: # grubonce 2 and Arch Linux LTS would be booted next. I thought the grubonce package was part of grub, but it isn't. Also, I don't need it for a local machine (obviously), but I need something I can use via ssh. What do we use here? -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com

4 8

[arch-general] Bug in latest vim - have to enter :q an additional time after split
by David C. Rankin 26 Aug '09

26 Aug '09

Listmates, There is a bug in the latest vim. Something prevents split windows from completely closing requiring an additional :q to exit. Take for example any two text files. I'll use /boot/grub/menu.lst and menu.lst.sav. To confirm the bug, do the following: cd /boot/grub vim menu.lst :split menu.lst.sav ## you now have both windows open with menu.lst.sav on top [1] :q (to exit menu.lst.sav, you get --No lines in buffer-- msg) [2] :q (to exit menu.lst, the syntax highlighting is killed but no exit??) [3] :q (finally, after 3rd quit, you actuall exit) Screenshots: [1] http://www.3111skyline.com/download/Archlinux/bugs/vim-1.jpeg [2] http://www.3111skyline.com/download/Archlinux/bugs/vim-2.jpeg [3] http://www.3111skyline.com/download/Archlinux/bugs/vim-3.jpeg Is this a bug I need to report or does it look like a configuration issue? -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com

2 6