Ashant Chalasani wrote:
Finally got the box to boot, with sshd.  I can connect on port 22, and
login prompt appears.  Very messy though, as this was possible only by
copying over /etc from host.

Can't figure out when I'm having to do all this, and why TinyBSD 0.9
doesn't work "out-of-the-make".  Or am I on a total tangent?  Jean?
Patrick?  Anybody there?


On Fri, Mar 28, 2008 at 12:34 PM, Ashant Chalasani <[EMAIL PROTECTED]> wrote:
Still no go on getting sshd to start.  A few things have gotten better though..

 Both /etc/rc and /etc/defaults/rc.conf were missing.  Copying these
 from host to tinybsd_ap helped.

 init right now looks like:

 --------------------------------------
 Timecounters tick every 1.000 msec
 Elan-mmcr driver: MMCR at 0xc5ad7000. PPS support.
 Elan-mmcr Soekris net45xx comBIOS ver. 1.23a 20040211 Copyright (C) 2000-2003
 ipfw2 initialized, divert enabled, rule-based forwarding disabled,
 default to accept, logging disabled
 ad0: 124MB <ZOOMCF 128MB CF040520> at ata0-master PIO4
 Trying to mount root from ufs:/dev/ad0a
 WARNING: /mnt was not properly dismounted
 Invalid time in clock: check and reset the date!
 Loading configuration files.
 WARNING: / was not properly dismounted
 mtree: line 6: unknown group wheel
 cp: /var/log/lastlog: No such file or directory
 chmod: /var/log/lastlog: No such file or directory
 cp: /var/log/wtmp: No such file or directory
 chmod: /var/log/wtmp: No such file or directory
 eval: cannot create /var/run/dmesg.boot: No such file or directory
 eval: cannot create /var/run/syslogd.sockets: No such file or directory
 Starting syslogd.
 syslogd: cannot open pid file: No such file or directory
 Mar 28 08:52:31  syslogd: cannot create /var/run/log: No such file or directory
 syslogd: child pid 83 exited with return code 1
 Flushed all rules.
 00100 allow ip from any to any via lo0
 00200 deny ip from any to 127.0.0.0/8
 00300 deny ip from 127.0.0.0/8 to any
 Firewall rules loaded.
 net.inet.ip.fw.enable: 1 -> 1
 lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
        inet 127.0.0.1 netmask 0xff000000
 Additional routing options:.
 Additional IP options:.
 Starting sshd.
 Missing privilege separation directory: /var/empty
 bridge0: Ethernet address: ca:03:78:21:3c:50
 bridge0
 ath0: promiscuous mode enabled
 sis0: promiscuous mode enabled
 Starting cron.
 cron: can't open or create /var/run/cron.pid: No such file or directory

 Fri M1sis0: Applying short cable fix (reg=f5)
 sis0: link state changed to UP
 -------------------------------------------------

 /var/log/ and /var/run/ directory contents are:

 [EMAIL PROTECTED] /var/log]# l
 total 4
 drwxr-xr-x  24 root  0  512 Mar 25 19:37 ..
 -rw-r--r--   1 root  0    0 Mar 27 14:00 lastlog
 -rw-r--r--   1 root  0    0 Mar 27 14:00 wtmp
 drwxr-xr-x   2 root  0  512 Mar 27 14:01 .

 [EMAIL PROTECTED] /var/run]# l
 total 20
 drwxr-xr-x   2 bind  53   512 Mar 25 17:02 named
 drwxrwx---   2 root  69   512 Mar 25 17:02 ppp
 drwxr-xr-x  24 root  0    512 Mar 25 19:37 ..
 -rw-r--r--   1 root  0      0 Mar 28 09:36 utmp
 -rw-r--r--   1 root  0      0 Mar 28 09:36 syslogd.sockets
 -rw-r--r--   1 root  0   8879 Mar 28 09:36 dmesg.boot
 -rw-r--r--   1 root  0      0 Mar 28 09:36 clean_var
 drwxr-xr-x   4 root  0    512 Mar 28 09:36 .
 -rw-------   1 root  0      4 Mar 28 09:36 cron.pid

 Can anyone see why the /var/log and /var/run errors are occuring
 inspite of files existing and writable?

 Thanks
 Ashant







 On Thu, Mar 27, 2008 at 2:01 PM, Ashant Chalasani <[EMAIL PROTECTED]> wrote:
 > The whole of /etc/rc.d/ directory is missing on TinyBSD 0.9.  Is this
 >  by design?  I'm hoping someone can throw light on it.
 >
 >  I copied the sshd script manually from my 7.0-REL host onto the flash
 >  image, as also a simple initialization script that I wrote for setting
 >  up the network.  But it looks like lot more startup scripts from
 >  /etc/rc.d/ are required to initialize the system.  I can ping the
 >  device on the network port, which means my network script ran.  But
 >  sshd on port 22 isn't available, so I guess /etc/rc.d/sshd failed.
 >
 >  I prefer to copy only the necessary scripts into my target's
 >  /etc/rc.d/ from the host, and not the whole directory.  There are 143
 >  scripts in rc.d.  Is there a minimal subset of scripts to setup the
 >  system, networking + basic services (dhclient, sshd etc)?
 >
 >  Thanks
 >  Ashant
 >
 >  --
 >  http://code.google.com/p/tinybsdap/
 >



 --
 http://code.google.com/p/tinybsdap/





I'm not subscribed on questions so i didn't read your mail before.

If you're using FreeBSD 7.0, you don't have to use TinyBSD 0.9, it's older. The newer TinyBSD is already in FreeBSD base at /usr/src/tools/tools/tinybsd.

BTW there are no problems reported to us, everthing is working fine. Try to read the TinyBSD documentation first at: http://www.tinybsd.org/tinybsd/Documentation

I hope it can help you.

--
Jean
_______________________________________________
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Reply via email to