[prev in list] [next in list] [prev in thread] [next in thread] 

List:       busybox
Subject:    Re: [BusyBox] Problem with syslogd
From:       Stewart Brodie <stewart () metahusky ! net>
Date:       2003-11-20 20:19:52
[Download RAW message or body]

Jason <jason@jasonandjessi.com> wrote:

> OK, I know this is a stretch, but it's all I can think of because other
> then this one difference, it looks like what I got working.  Change the
> /dev/log link from ../var/run/syslog.socket  to /var/run/syslog.socket. So
> give it the full path not relative to anything and see ,what happens.

My symlink works either way in my system and always has done.  I'm not the
one who had the problem with opening /dev/log ... that was somebody else.  I
was just suggesting the symlink as an alternative to mounting the root
filesystem read-write.


-- 
Stewart Brodie
_______________________________________________
busybox mailing list
busybox@mail.busybox.net
http://codepoet.org/mailman/listinfo/busybox
[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic