[9fans] bind error after today pull update - Plan9

This is a discussion on [9fans] bind error after today pull update - Plan9 ; Hi, Today, under qemu, I updated my stand-alone Plan 9 system with: /usr/glenda/bin/rc/pull /usr/glenda/bin/rc/pull -s /386/lib/libc.a /usr/glenda/bin/rc/pull -s /rc/bin/termrc without apparent problems. But right after fshalt -r, rio doesn't start anymore; I get: init: starting /bin/rc bind: #k: unknown device ...

+ Reply to Thread
Results 1 to 7 of 7

Thread: [9fans] bind error after today pull update

  1. [9fans] bind error after today pull update

    Hi,

    Today, under qemu, I updated my stand-alone Plan 9 system with:

    /usr/glenda/bin/rc/pull
    /usr/glenda/bin/rc/pull -s /386/lib/libc.a
    /usr/glenda/bin/rc/pull -s /rc/bin/termrc

    without apparent problems. But right after fshalt -r, rio
    doesn't start anymore; I get:

    init: starting /bin/rc
    bind: #k: unknown device in # filename
    rc: null list in concatenation
    init: rc exit status: rc 23: error

    init: starting /bin/rc
    % _

    Any ideas? Thank you very much, david.

  2. Re: [9fans] bind error after today pull update

    * David JEANNOT (djeannot24@gmail.com) wrote:
    > init: starting /bin/rc
    > bind: #k: unknown device in # filename


    This shouldn't be serious at all. The new diskparts script tries to bind the
    fs device, whis isn't compiled into the standard terminal kernel, into the
    namespace. I thought about making a patch to silence the bind, but it's
    probably a good idea to have the error messages if you are using the fs
    device.

    > rc: null list in concatenation
    > init: rc exit status: rc 23: error


    I'd like to make a wild guess here. Did you set up your network manually in
    your old termrc? What does `echo $sysname' say? `cat /dev/sysname' ?

    Martin


  3. Re: [9fans] bind error after today pull update

    > bind: #k: unknown device in # filename

    I don't see #k (fs(3)) appearing anywhere in /rc/bin/termrc, so I can
    only presume you have it in a local startup. Depending on whether you
    actually use it or not, you'll have to fix the startup script or
    compile a kernel that has '#k' in it. I presume the absence of '#k'
    is causing rc to stop.

    Of course, I am just as likely to be missing the wood for the trees.

    ++L


  4. Re: [9fans] bind error after today pull update

    On Sat, May 05, 2007 at 09:22:09PM +0200, Martin Neubauer wrote:
    > * David JEANNOT (djeannot24@gmail.com) wrote:
    > > rc: null list in concatenation
    > > init: rc exit status: rc 23: error

    >
    > I'd like to make a wild guess here. Did you set up your network
    > manually in your old termrc?


    Absolutely, I had:

    if(! test -e /net/ipifc/0/ctl)
    ip/ipconfig -g 10.0.2.2 ether /net/ether0 10.0.2.15 255.255.255.0 > /dev/null >[2=1]

    > What does `echo $sysname' say? `cat /dev/sysname' ?


    Nothing for both:

    % echo $sysname

    % cat /dev/sysname
    % _

    Thank you Martin, david.

  5. Re: [9fans] bind error after today pull update

    add ether= to your sys=yourmachine entry in your /lib/ndb/local
    or brute force it by putting sysname=mymachine in your plan9.ini/termrc

    On 5/5/07, David JEANNOT wrote:
    > On Sat, May 05, 2007 at 09:22:09PM +0200, Martin Neubauer wrote:
    > > * David JEANNOT (djeannot24@gmail.com) wrote:
    > > > rc: null list in concatenation
    > > > init: rc exit status: rc 23: error

    > >
    > > I'd like to make a wild guess here. Did you set up your network
    > > manually in your old termrc?

    >
    > Absolutely, I had:
    >
    > if(! test -e /net/ipifc/0/ctl)
    > ip/ipconfig -g 10.0.2.2 ether /net/ether0 10.0.2.15 255.255.255.0 > /dev/null >[2=1]
    >
    > > What does `echo $sysname' say? `cat /dev/sysname' ?

    >
    > Nothing for both:
    >
    > % echo $sysname
    >
    > % cat /dev/sysname
    > % _
    >
    > Thank you Martin, david.
    >



    --
    Federico G. Benavento

  6. Re: [9fans] bind error after today pull update

    On 5/5/07, David JEANNOT wrote:
    > On Sat, May 05, 2007 at 09:22:09PM +0200, Martin Neubauer wrote:
    > > * David JEANNOT (djeannot24@gmail.com) wrote:
    > > > rc: null list in concatenation
    > > > init: rc exit status: rc 23: error

    > >
    > > What does `echo $sysname' say? `cat /dev/sysname' ?

    >
    > Nothing for both:
    >
    > % echo $sysname
    >
    > % cat /dev/sysname
    > % _
    >
    > Thank you Martin, david.
    >


    Ok, I read "sorry: termrc-error" on plan9changes list and modified
    termrc accordingly.

    Thanks to all, david.

  7. Re: bind error after today pull update

    On May 5, 7:32 pm, djeanno...@gmail.com (David JEANNOT) wrote:
    > Hi,
    >
    > Today, under qemu, I updated my stand-alone Plan 9 system with:
    >
    > /usr/glenda/bin/rc/pull
    > /usr/glenda/bin/rc/pull -s /386/lib/libc.a
    > /usr/glenda/bin/rc/pull -s /rc/bin/termrc
    >
    > without apparent problems. But right after fshalt -r, rio
    > doesn't start anymore; I get:
    >
    > init: starting /bin/rc
    > bind: #k: unknown device in # filename
    > rc: null list in concatenation
    > init: rc exit status: rc 23: error
    >
    > init: starting /bin/rc
    > % _
    >
    > Any ideas? Thank you very much, david.


    Ok, I read "sorry: termrc-error" in the plan9changes list and updated
    termrc accordingly.

    Thanks to all, david.

+ Reply to Thread