Return to the archive index

Re: installing a deb package on RH WAS:[ longrun utility error]

From: Francois Gurin <>
Date: Wed, 15 Jan 2003 13:44:04 -0500

i normally use alien to convert rpms to debs, shoudl work the other way around
as well..  search the diff for longrun.c.  debian diffs include all the 
changes to pristine source to fix bugs and also make it debianized, in one
bug patch.

one of the first changes is:
+#define __USE_FILE_OFFSET64 /* we should use 64 bit offset for pread/pwrite */

you can also try just the binary, i put my working one up on 

http://www.spic.net/u1/linux/dl/longrun
http://www.spic.net/u1/linux/dl/longrun.md5sum

it only has has dependencies on libc6 so should work off the bat
$ ldd /usr/bin/longrun 
        libc.so.6 => /lib/libc.so.6 (0x41014000)
        /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x41000000)

to the rest of the list: sorry about the subject line, i have procmail toss
in the wear-hard tag and often forget to remove it before sending out :p

--francois

On Wed, Jan 15, 2003 at 12:48:23PM -0500, Rick Jones wrote:
> I thought some actual code got changed but appearantly
> it is just in the makefile or am I just
> misunderstanding this....
> 
> http://ftp.debian.org/debian/pool/main/l/longrun/longrun_0.9-7.diff.gz
> 
> Rick
> 
>  --- Rick Jones <> wrote: > Ok I got
> the new code.. but it's a deb package.  How
> > do I get the deb package to a usable form on RH?
> > 
> >  --- Francois Gurin <> wrote: > 
> > > 
> > > i wouldn't spend more time with the kernel just
> > yet,
> > > cpuid 
> > > appears to be working.  try an strace of longrun
> > to
> > > see if 
> > > it sheds any light on the failure.  from the error
> > 
> > > cited 
> > > below, i'd venture longrun can't parse the input. 
> > > looking 
> > > at the debian changelog for longrun 0.9-7 shows:
> > >   * fix pread(),pwrite() offset problem, closes:
> > > #165781
> > > 
> > > this may have something to do with your problem. 
> > in
> > > fact, 
> > > checking out the bug report (below) shows the
> > exact
> > > same 
> > > error message.  i don't know if this fix is in the
> > > latest
> > > upstream version, but you can always grab the
> > debian
> > > package
> > > or just the diff and rebuild from there.  hope
> > this
> > > helps.
> > > 
> > >
> >
> http://bugs.debian.org/cgi-bin/bugreport.cgi?archive=no&bug=165781
> > > 
> > > --francois
> > > 
> > > 
> > > 
> > > On Tue, Jan 14, 2003 at 10:15:50PM -0500, Rick
> > Jones
> > > wrote:
> > > > I'm using RH8.0 kernel 2.4.18.. I gave read and
> > > write
> > > > permissions 666 to /dev/cpu/0/cpuid.  I can read
> > > > the string you mentioned from cpuid.  However, I
> > > am
> > > > still getting the error "longrun: error reading
> > > > /dev/cpu/0/cpuid: Invalid argument"
> > > > 
> > > > I've tried it with both kernels (msr/cpuid as
> > > static
> > > > or modules).  I'm rebuilding the static kernel
> > for
> > > > devfs.  I'll post more after I get it done and
> > > tested.
> > > > 
> > > > Any ideas feel free to reply..
> > > > 
> > > > Rick
> > > > 
> > > > 
> > > >  --- Francois Gurin <> wrote: > 
> > > > > what kernel version are you running?
> > > occasionally a
> > > > > build of 2.4.20 will
> > > > > compile but otherwise not actually init either
> > > cpuid
> > > > > or msr.  i've also 
> > > > > had an instance of longrun just refusing to
> > read
> > > the
> > > > > device.
> > > > > 
> > > > > a quick check is to cat cpuid.  be sure you
> > have
> > > > > read permision on the node
> > > > > and you should see somthing like GenuMx86ineTC
> > > with
> > > > > some garbage.  
> > > > > 
> > > > > if you don't get anything, try enabling devfs
> > &
> > > > > devfsd and try again.  
> > > > > 
> > > > > devfs will give an idea of what's going on. 
> > if
> > > > > neither cpuid or msr nodes
> > > > > appear, the kernel isn't loading them
> > properly. 
> > > if
> > > > > cpuid is blank, then 
> > > > > i don't know what to tell you.
> > > > > 
> > > > > if you do see the GenuMx86ineTC string, make
> > > sure
> > > > > you have read and write
> > > > > access to the nodes, as longrun needs to write
> > > to
> > > > > the devices.
> > > > > 
> > > > > this should hopefully give you an idea of
> > what's
> > > > > failing and where.
> > > > > 
> > > > > --francois
> > > > > 
> > > > > On Mon, Jan 13, 2003 at 10:49:13PM -0500, Rick
> > > Jones
> > > > > wrote:
> > > > > > I did some different things..  
> > > > > > 
> > > > > > I removed the msr and cpuid from /dev/cpu/0
> > > and
> > > > > tried
> > > > > > the kernel with the static msr and cpuid   -
> > > same
> > > > > > error msg.   I ran the MAKEDEV again and
> > tried
> > > it
> > > > > > again with the modular kernel - same error
> > > msg.
> > > > > > 
> > > > > > What do I need to do to read the info in
> > > > > > /dev/cpu/0/cpuid?  Or better trace the cpuid
> > > > > > communication in the static kernel..
> > > > > > 
> > > > > > Rick
> > > > > > 
> > > > > >  --- Rick Jones <> wrote:
> > >
> > > I
> > > > > just
> > > > > > rebuilt msr and cpuid in the kernel.  I had
> > > > > > > previously run the MAKEDEV script.  Do I
> > > need to
> > > > > do
> > > > > > > some clean up on the dev directories?
> > > > > > > 
> > > > > > > I'm using a Crusoe 5400  - I don't know if
> > > that
> > > > > > > effects the major number (in the script)
> > for
> > > the
> > > > > > > CPUID..
> > > > > > > 
> > > > > > > Rick
> > > > > > > 
> > > > > > > 
> > > > > > >  --- Doug <> wrote:
> > >
> > > > > Sounds
> > > > > > > like the device files are not created. I
> > > > > > > > believe
> > > > > > > > there is Makedev script that you need to
> > > run
> > > > > to
> > > > > > > > create
> > > > > > > > those. It should be in the longrun
> > > > > distribution.
> > > > > > > > What I
> > > > > > > > do is compile CPUID and MSR support
> > > statically
> > > > > > > into
> > > > > > > > the
> > > > > > > > kernels. It seems that when I do that I
> > > don't
> > > > > have
> > > > > > > > to
> > > > > > > > make those devices. Also, if you
> > included
> > > > > support
> > > > > > > > for
> > > > > > > > CPUID and MSR as loadable modules, you
> > may
> > > > > need to
> > > > > > > > load those (ie modprobe) before running
> > > > > longrun
> > > > > > > > util.
> > > > > > > > 
> > > > > > > >   -- Doug
> > > > > > > > 
> > > > > > > > 
> > > > > > > > At 10:59 AM 1/13/2003 -0500, you wrote:
> > > > > > > > >I finally got my kernel configured with
> > > msr
> > > > > and
> > > > > > > > cpuid.
> > > > > > > > >  I ran the MAKEFILE-MSR-CPUID.  When I
> > > type
> > > > > > > > ./longrun
> > > > > > > > >-l - I get the error "longrun:error
> > > reading
> > > > > > > > >/dev/cpu/0/cpuid: Invalid argument".
> > > > > > > > >
> > > > > > > > >Does anyone know what I need to do to
> > > solve
> > > > > this
> > 
> === message truncated === 
> 
> ______________________________________________________________________ 
> Post your free ad now! http://personals.yahoo.ca
> 
> --
> Subscription/unsubscription/info requests: send e-mail with subject of
> "subscribe", "unsubscribe", or "info" to 
> Wear-Hard Mailing List Archive (searchable): http://wearables.blu.org
> Please, *PLEASE* don't subscribe through a forward/expander/false domain

--
Subscription/unsubscription/info requests: send e-mail with subject of
"subscribe", "unsubscribe", or "info" to 
Wear-Hard Mailing List Archive (searchable): http://wearables.blu.org
Please, *PLEASE* don't subscribe through a forward/expander/false domain

+Previous Message in Thread | Next Message in Thread

From Wear-Hard Mailing list Archive (WH)
Maintained by R. Paul McCarty

Archive created with babymail