Re: SL on ARM
So...how well does SL run on them? You mean you haven't tried yet? Clint BowmanINTERNET: cl...@ecy.wa.gov Air Quality Modeler INTERNET: cl...@math.utah.edu Department of Ecology VOICE: (360) 407-6815 PO Box 47600FAX:(360) 407-7534 Olympia, WA 98504-7600 USPS: PO Box 47600, Olympia, WA 98504-7600 Parcels:300 Desmond Drive, Lacey, WA 98503-1274 On Thu, 28 Jun 2012, Alan Bartlett wrote: On 28 June 2012 22:31, Christopher Tooley wrote: Further update: I have a Raspberry Pi in my grubby little paws right now - so, yeah, definitely not vaporware ;) -Chris You're not the only one. I received mine today. :) Alan.
Re: SL on ARM
On 28 June 2012 22:31, Christopher Tooley wrote: > > Further update: > > I have a Raspberry Pi in my grubby little paws right now - so, yeah, > definitely not vaporware ;) > > -Chris You're not the only one. I received mine today. :) Alan.
Re: SL on ARM
On 2012-06-08, at 10:27 PM, Mark Rousell wrote: > On 26/03/2012 19:33, Konstantin Olchanski wrote: >> "no-one received", "online videos", "founders are demonstrating", "preorder >> now" and "available soon" is the definition of vaporware. >> >> One official vendor is: >> http://www.element14.com/community/groups/raspberry-pi >> read forum postings observe promised shipping dates in May-June. >> >> Bottom line is I cannot buy it, you cannot buy it. (For "buy" == it's in my >> hands. Not some promise to mail it to me later). >> >> K.O. > > Just to update this, the Raspberry Pi is real and is now shipping. You > can now buy it and receive it in your hands. > > It looks likely to spawn a new generation of ARM-based devices in the > same price range. I would have thought that such devices would be an > ideal target for SL. > > -- > MarkR > > PGP public key: http://www.signal100.com/markr/pgp > Key ID: C9C5C162 Further update: I have a Raspberry Pi in my grubby little paws right now - so, yeah, definitely not vaporware ;) -Chris
Return code 1 in Revisor
Hello, When I try to use the directions provided here[1] to build my custom SL, I'm getting this error: Building Installation Images: 0.0% Got an error from /usr/lib/revisor/scripts/RHEL6-buildinstall (return code 1) As a test I'm trying to create a very basic Image installing only @base with this command: revisor --cli --install-dvd --install-tree --model=sl6-x86_64 --kickstart=/home/lonely/kssl.ks I'm using: mock-1.1.21-1.el6.noarch revisor-cli-2.2-2.sl6.4.noarch revisor-gui-2.2-2.sl6.4.noarch revisor-2.2-2.sl6.4.noarch sl-revisor-configs-1-6.1.0.noarch On my new SL 6.2 with kernel-2.6.32-220.el6.x86_64 Any advices? [1] - https://www.scientificlinux.org/distributions/6x/build/sites -- Henrique "LonelySpooky" Junior http://about.me/henriquejunior
Re: For the RPMForge guys
On 28/06/12 05:52, jdow wrote: On 2012/06/27 13:58, S.Tindall wrote: On Wed, 2012-06-27 at 13:12 -0700, jdow wrote: On 2012/06/27 12:43, S.Tindall wrote: On Wed, 2012-06-27 at 12:31 -0700, jdow wrote: Latest clamav update main.cvd is an empty file. It apparently should not be empty. For two days now I've gotten this message: ERROR: Corrupted database file /var/clamav/main.cld: Broken or not a CVD file {^_^} Run freshclam and then restart clamd. Steve rerunning freshclam gives: ClamAV update process started at Wed Jun 27 13:11:13 2012 main.cvd is up to date (version: 54, sigs: 1044387, f-level: 60, builder: sven) daily.cld is up to date (version: 15092, sigs: 222617, f-level: 63, builder: ccordes) bytecode.cld is up to date (version: 185, sigs: 39, f-level: 63, builder: neo) WARNING: [LibClamAV] cli_cvdverify: Can't read CVD header ERROR: Corrupted database file /var/clamav/main.cld: Broken or not a CVD file Corrupted database file renamed to /var/clamav/main.cld.broken Trying again in 5 secs... ClamAV update process started at Wed Jun 27 13:11:19 2012 main.cvd is up to date (version: 54, sigs: 1044387, f-level: 60, builder: sven) daily.cld is up to date (version: 15092, sigs: 222617, f-level: 63, builder: ccordes) bytecode.cld is up to date (version: 185, sigs: 39, f-level: 63, builder: neo) It's broken, Jim! (Sorry Star Trek) {^_^} You "fixed" it with freshclam. As per the final section, main.cvd, daily.cld and bytecode.cld are now up to date. If /var/clamav/*broken bothers you, then delete it/them. # rm /var/clamav/*broken # ls /var/clamav/ bytecode.cld daily.cld main.cvd mirrors.dat At least on my EL6 systems, those satisfy clamd. # service clamd restart Stopping Clam AntiVirus Daemon: [ OK ] Starting Clam AntiVirus Daemon: [ OK ] Steve Then main.cld is a surplus file now? I didn't know that! {^_^} There seems to be two formats for the database files, .cld and .cvd. It doesn't seem to matter which you have, so just delete one or the other. IIRC having both causes some log file noise. On my system I have: $ ls /var/clamav/ bytecode.cld daily.cld main.cld mirrors.dat and after each update to clamav from rpmforge I manually remove the *.cvd files in stalled from clamav-db: rm /var/clamav/*.cvd and restart the clamd service. I guess the real questions here are why there are two formats, which is preferable and why, and can we get the packaged version to deliver only the preferred format. To date it's not bothered me enough to go looking for the answers to those questions so long as my workaround above seems to work :-) Anyway, this discussion would all be better placed on the rpmforge mailing lists rather than here as it's not an SL issue.