>ok boot disk bsd Boot device:(Can't read an inode table)
Couldn't load /etc/silo.conf No config file loaded, you can boot just from this command line Type [prompth;]part/path_to_image [parameters] on the prompt E.g. /iommu/sbus/espdma/esp/sd@3,0;4/vmlinux root=/dev/sda4 or 2/vmlinux.live (to load vmlinux.live from 2nd partition of boot disk
Your imagename 'bsd' and arguments '' have either wrong syntax, or describe a label which is not present in silo.conf Type 'help' at the boot: prompt if you need it and then try again. boot: な感じですがどーすれば起動するんでしょう？ みなさんは普通に入れ終わったあと普通に起動するものなのでしょうか？
004: SECURITY FIX: May 22, 2002 Under certain conditions, on systems using YP with netgroups in the password database, it is possible that sshd(8) does ACL checks for the requested user name but uses the password database entry of a different user for authentication. This means that denied users might authenticate successfully while permitted users could be locked out.
005: SECURITY FIX: June 19, 2002 A buffer overflow can occur during the interpretation of chunked encoding in the http daemon, leading to possible remote crash.
006: SECURITY FIX: June 24, 2002 An (as yet) undisclosed bug exists in OpenSSH which a patch is not forthcoming for yet -- no patch exists yet! However, upgrading to OpenSSH 3.3 with the UsePrivilegeSeparation option enabled will block this problem. All users are advised to update immediately, and keep an eye out for a upcoming OpenSSH 3.4 release on Monday containing a real fix.