On September 20, 2002 02:26 pm, Rama at freevsd lists wrote:

wel i am having an issue with RedHat 7.3
when i create a virtual server .. and i try to bevs .. i get the following 
error.

bevs: relocation error: /lib/libnss_files.so.2: symbol _nss_files_parse_pwent, 
version GLIBC_2.0 not defined in file libc.so.6 with link time reference

Anyway have an idea how i can work around this?


Mike

> Hi all,
>
>       I've just subscribed to the mailing lists and have been looking at the
> archives for information about running Freevsd + Redhat 7.3 but couldn't
> find anything. I've also checked the FAQ and Ben Kennish (I guess)
> states he managed to have Freevsd + Redhat 7.2 running by issuing the
> development tree for Freevsd 1.4.10 (from CVS).
>
>       I wonder how complicated it is to have that stuff running. I have no
> prior experience on working or implementing software from it's
> development tree and I also have my doubts about how stable it might
> work.
>
>       Does anybody know if a new version for Freevsd will be released soon in
> order to set up Freevsd within a Redhat 7.3 or at least 7.2 ?
>       Anyway does anybody know where to get information on how to do such
> implementation with the available release (or even devel) ?
>
> I will be glad to receive any kind of help.
>
> Thanks in advance,
> Rama
>
>
>
>
> ------------------------- The freeVSD Support List
> -------------------------- Subscribe:  
> mailto:[EMAIL PROTECTED]?body=subscribe%20freevsd-support Unsubscribe:
> mailto:[EMAIL PROTECTED]?body=unsubscribe%20freevsd-support Archives:  
>  http://freevsd.org/support/mail-archives/freevsd-support
> ---------------------------------------------------------------------------
>--

------------------------- The freeVSD Support List --------------------------
Subscribe:   mailto:[EMAIL PROTECTED]?body=subscribe%20freevsd-support
Unsubscribe: mailto:[EMAIL PROTECTED]?body=unsubscribe%20freevsd-support
Archives:    http://freevsd.org/support/mail-archives/freevsd-support
-----------------------------------------------------------------------------

Reply via email to