- Arch-general - lists.archlinux.org

[arch-general] Kernel Panic on x64 when writting to 1TB External USB disk
by Victor Silva 22 Feb '11

22 Feb '11

Hi folks i'm not 100% sure I'm posting on the right list so if im wrong please disregard and direct me to the appropriate list. :) Well I'm having a problem with USB devices causing kernel panic. I got an external 1 TB USB hard disk in NTFS format. When I tried to save some files (downloads from deluge) on it I get a kernel panic. Which files/logs can I provide to help you? The system simply hangs and all keyboard leads start to blink. I'm using Linux 2.6.37-ARCH #1 SMP PREEMPT Fri Feb 18 18:32:16 CET 2011 x86_64 AMD Athlon(tm) 64 X2 Dual Core Processor 5600+ AuthenticAMD GNU/Linux. It is the default arch linux kernel. If I write a small file and move to the folder things seem to be okay. Any ideas? Thanks for the great distro folks hope you can help me on this one.

4 3

[arch-general] Trinity Binaries - Unofficial Repo - Thank You Kainting Chen!
by David C. Rankin 21 Feb '11

21 Feb '11

All, Kaiting Chen has provided server space for Trinity binaries. Currently I have the i686 files uploaded and will upload x86_64 shortly (after my kids are done with toontown....) The url for the i686 repo is: http://www.kiwilight.com/~drankinatty/trinity/i686/ (Trinity packages are 2/19/2011 builds) The x86_64 repo will be the same url with x86_64. Trinity needs a clean environment currently (no kdemod3). If you have had a prior kdemod3 install, then delete: /var/tmp/kdecache-$USER/ksycoca /var/tmp/kdecache-$USER/ksycocastamp and move ~/.kde somewhere else. If you have kde4 installed, then expect akonadi/nepomuk and all the kde4 autostart files in /usr/share/autostart to run (Trinity devs are working on a way to ignore all the kde4 autostart files) To install trinity, just add the repo to /etc/pacman.conf: [trinity] Server = http://www.kiwilight.com/~drankinatty/trinity/i686/ Then just do 'pacman -Sy trinity-kdewebdev' and it will pull in the complete Trinity desktop (kdewebdev requires all trinity dependencies) I recommend installing it in either a clean Arch install, or just create a new Arch virtualbox VM and install it there. It is a darn good looking desktop. x86_64 packages by the morning :) See: https://wiki.archlinux.org/index.php/Trinity for current details :) -- David C. Rankin, J.D.,P.E.

2 5

Re: [arch-general] Howto - tell pacman -S (-U) to overwrite existing file in filesystem?
by David C. Rankin 21 Feb '11

21 Feb '11

On 02/20/2011 04:15 PM, Gaetan Bisson wrote: > [2011-02-20 15:32:14 -0600] David C. Rankin: >> The question is "Can I do something in the PKGBUILD to tell pacman >> - if the file is already there -> overwrite it?" > > Please. This mailing list is not for people to read you man pages. > > Next time, could you first spend five minutes to try and answer your > questions on your own? Here, it was as simple as searching for "pacman > overwrite" in Google, or looking for "overwrite" in pacman's man page. > > I am sure you understand this would benefit to everyone. > > For a more lengthy essay on the topic, see: > > http://www.catb.org/~esr/faqs/smart-questions.html#before > Thank you Gaetan and Sebastian, From your answers, I don't think you read my question before giving the the RTFM dismissal. I know how pacman -f works. I stated that in my original email. I'm not asking how to make pacman do it. I'm asking: <quote> The question is "Can I do something in the PKGBUILD to tell pacman - if the file is already there -> overwrite it?" </quote> The only information I found in man PKGBUILD on force was option(force) which relates to triggering an update even though the version number would not normally do so. I apologize if I missed it in the man page, but that is why I asked. -- David C. Rankin, J.D.,P.E.

6 6

[arch-general] Howto - tell pacman -S (-U) to overwrite existing file in filesystem?
by David C. Rankin 20 Feb '11

20 Feb '11

Guys, This is a curiosity really. I updated kdebase to create a trinity.desktop file in /etc/X11/sessions in the PKGBUILD package() function: # install desktop and update kdmrc and Xsession [[ -f trinity.desktop ]] && { mkdir -p ${pkgdir}/etc/X11/sessions cp trinity.desktop ${pkgdir}/etc/X11/sessions } <snip> Since I had already created trinity.desktop on my box (before it was part of the package), I get (correctly): Targets (1): trinity-kdebase-1221588-1 Total Download Size: 0.00 MB Total Installed Size: 86.71 MB Proceed with installation? [Y/n] checking package integrity... checking for file conflicts... trinity-kdebase: /etc/X11/sessions/trinity.desktop exists in filesystem IIRC this is exactly the way pacman is supposed to work because it has no knowledge of a prior trinity.desktop in the filesystem and won't overwrite it. The short answer is "dummy -- remove the file or use --force." I get that. The question is "Can I do something in the PKGBUILD to tell pacman - if the file is already there -> overwrite it?" The purpose for the question is make sure nobody else gets a conflict if they have followed a prior manual Trinity kdm install proceedure. -- David C. Rankin, J.D.,P.E.

3 2

[arch-general] [signoff] kernel26-2.6.37.1-1
by Tobias Powalowski 20 Feb '11

20 Feb '11

Hi guys, - bump to latest version greetings tpowa -- Tobias Powalowski Archlinux Developer & Package Maintainer (tpowa) http://www.archlinux.org tpowa(a)archlinux.org

3 2

[arch-general] makechrootpkg and multiple sources, a bug?
by Magnus Therning 20 Feb '11

20 Feb '11

I just tried building a package with more than one source file using makechrootpkg. It failed with this message: ==> ERROR: Integrity checks (md5) differ in size from the source array. After a bit of poking around in the makechrootpkg script I made the following change: --- makechrootpkg.orig 2011-02-20 09:22:30.130744179 +0000 +++ makechrootpkg 2011-02-20 09:22:44.494796349 +0000 @@ -173,7 +173,7 @@ for f in ${source[@]}; do basef=$(echo $f | sed 's|::.*||' | sed 's|^.*://.*/||g') if [ -f "$basef" ]; then - cp "$basef" "$copydir/srcdest/" + cp "$basef" "$copydir/build/" elif [ -f "$SRCDEST/$basef" ]; then cp "$SRCDEST/$basef" "$copydir/srcdest/" fi After this the package built just fine. I'm doubting myself in this though, because it seems like such an obvious bug, especially since the PKGBUILD is copied into $copydir/build/ just a few lines above this change. Also, should the copy in the elif-branch be changed too? /M -- Magnus Therning OpenPGP: 0xAB4DFBA4 email: magnus(a)therning.org jabber: magnus(a)therning.org twitter: magthe http://therning.org/magnus I invented the term Object-Oriented, and I can tell you I did not have C++ in mind. -- Alan Kay

3 9

[arch-general] who wants to write me a relatively simple webapp?
by Dieter Plaetinck 20 Feb '11

20 Feb '11

Hi, for Arch releng, we have recently started automatically building test builds (http://releng.archlinux.org/isos/) These images are built from the archiso and aif git repositories, and the current state of the repos. The idea is that people can test these images, and once in a while, I will promote a set of testbuilds and make them the officially supported media. Because everything evolves all the time, a lot of different things can cause regressions or new bugs, but at the same time it would be too much work to try to test all possible scenarios for each specific testbuild version. So I would like a web application that gives me "a pretty good idea" of the quality of current/recent images. I request someone other then me to make this app for me, I do not have the time. (I do have time for feedback or making adjustments to the codebase you provide) I'm not sure which is best, php or python, or whatever. I think both will be fine (Dan? Pierre?) Basically it would have 2 modes: 1) the "input" mode (after logging in with your wiki or forum account, not sure what's best here. Dan?): the user would select a version (maintain a cached list of the directories at http://releng.archlinux.org/isos/ the format will always be YYYY.MM.DD[suffix]) and select a list of options which are verified to be working fine. that is: (between braces are additional instructions for the user) = image arch = * dual, option i686 * dual, option x86_64 * i686 * x86_64 = image type = * core * net = image boot = * optical * usb * pxe = hardware type = * virtualbox * qemu * physical intel i686 * physical intel x86_64 * physical amd i686 * physical amd x86_64 = install type = * automatic install generic example * automatic install fancy example * automatic install custom config (specify in comments) * interactive install = source selection = * net install manual networking config (check that it works + rc.conf, resolv.conf, mirrorlist) * net install dhcp (check that it works + rc.conf) * core = clock = * left as is * reconfigured manually * reconfigured ntp = partitioning/filesystems = * autoprepare (check the installed system, incl fstab) * manual * from config file = fancy stuff (checklist, not selection) = * lvm2 * dm_crypt * softraid * nilfs2 * btrfs (check also fstab, menu.lst, initcpio.conf and crypttab if appropriate) = rollback tested = * yes * no = if rollback done, another partitioning/filesystems list and another "fancy stuff" list (same options as before) for after the rollback = = bootloader = * grub * syslinux * other/manual = result = * everything works fine * something failed (elaborate in comments) = comments = <textarea> Then, a second interface would need to represent the "current state of things.. (sort of)" that is, for every important thing (like, all image arches, image types, image boots, install types, source selections, clock, partitioning/filesystems, fancy stuff, rollback tested, grub/syslinux bootloader) it needs to show the last recent tests (or the last images for which it worked), along with which user tested it. (note: not all combinations of all variables, just any test with the given variable). if there was any failed test for a specific feature for an as recent (or more recent) image then the last successful one, there should be a warning about that. I'm not sure yet how exactly this page would look like, but basically I need to know all important features are tested with recent images, and that they all performed well. other factors (like hardware type, bootloader other/manual bootloader option) are not very important, they are more for reference. Thanks, Dieter

7 14

[arch-general] [signoff] kernel26-lts 2.6.32.29-2
by Tobias Powalowski 20 Feb '11

20 Feb '11

Latest LTS kernel is in testing, please signoff for both arches greetings tpowa -- Tobias Powalowski Archlinux Developer & Package Maintainer (tpowa) http://www.archlinux.org tpowa(a)archlinux.org

1 0

[arch-general] chrooting / LiveCD
by Jorge Almeida 19 Feb '11

19 Feb '11

I've been reading several pieces of documentation about making a custom LiveCD, in particular the documentation for Archiso. Makefiles and bash are not my strong suit, so I may have misunderstood something. Among other things, we need to create a directory, say "prov", and populate it with an arch system. I tried this: mkdir -p prov/var/lib/pacman pacman -r prov -Sy pacman -r prov -S base This seems to work, although it had a complain about the directory "sys". My question is: to populate a directory with a base system plus some assorted stuff, can we do it with pacman -r? Or is it necessary to chroot into prov? (And if so, don't we need to use pacman -r to have a functional chroot dir to begin with?) I would understand the need for chroot if we were to compile software (I read LFS stuff...), to ensure correct library linking. But we're talking about binary packages... I'm just trying to get the big (and small) picture... TIA Jorge Almeida

3 4

[arch-general] Quick & Dirty build script for Traditional Trinity PKGBUILDs
by David C. Rankin 19 Feb '11

19 Feb '11

Guys, I have added a simple Quick & Dirty build script that will build all of Trinity that has been ported to cmake using the new Traditional set of PKGBUILDs. https://wiki.archlinux.org/index.php/Trinity#Quick_.26_Dirty_Build_for_Trad… Just download the PKGBUILD tarballs and unzip them to a temporary directory, then set 3 path variables in the script, change to the build directory you set in the script and run it. It also provides a brief log in the build dir: Feb 18 21:54:42 building: trinity-tqtinterface resolving dependencies... looking for inter-conflicts... Targets (1): trinity-tqtinterface-1221148-1 Total Download Size: 0.00 MB Total Installed Size: 2.47 MB Proceed with installation? [Y/n] checking package integrity... checking for file conflicts... upgrading trinity-tqtinterface... `trinity-tqtinterface-1221148-1-x86_64.pkg.tar.xz' -> `/home/david/alc-home/arch/tpkg/x86_64/trinity-tqtinterface-1221148-1-x86_64.pkg.tar.xz' removed `trinity-tqtinterface-1221148-1-x86_64.pkg.tar.xz' Feb 18 21:57:25 building: trinity-arts <snip> Feb 18 22:02:56 building: trinity-kdelibs <snip> Feb 18 22:57:07 building: trinity-kdebase <snip> Feb 18 23:54:30 building: trinity-kdevelop <snip> It should build all the way through. All you have to do is hit Y to accept dependencies. See the wiki link above for details. -- David C. Rankin, J.D.,P.E.

1 1