Re: Installer & HAMMER only
Jeremy C. Reed wrote: On Wed, 28 Jan 2009, FloW wrote: cd /dev && /bin/echo ad0s4a || /bin/sh MAKEDEV ad0s4a Shouldn't this be rather cd /dev && /bin/echo ad0s4a && /bin/sh MAKEDEV ad0s4a Neither of those make sense to me as that echo will always return 0. If this is to check existence why not use test (or ls)? Unless it really does a cd /dev/ && /bin/echo ad0s4a* and depends on the shell to complain when expanding... but a test(1) would be even better... cheers simon -- <3 the future +++ RENT this banner advert +++ ASCII Ribbon /"\ rock the past +++ space for low €€€ NOW!1 +++ Campaign \ / Party Enjoy Relax | http://dragonflybsd.org Against HTML \ Dude 2c 2 the max ! http://golden-apple.biz Mail + News / \
Re: Installer & HAMMER only
On Wed, 28 Jan 2009, FloW wrote: > cd /dev && /bin/echo ad0s4a || /bin/sh MAKEDEV ad0s4a > > Shouldn't this be rather > > cd /dev && /bin/echo ad0s4a && /bin/sh MAKEDEV ad0s4a Neither of those make sense to me as that echo will always return 0. If this is to check existence why not use test (or ls)?
Re: Installer & HAMMER only
Matthias Schmidt wrote: He, * FloW wrote: So far everything went smooth, except that the MAKEDEV commands failed from inside the installer. There was no specific error message. When i invoked MAKEDEV from the shell the devices were created without error, and then the installer would proceed. Can anyone reproduce this? No, never saw that during my tests. Do you had the chance to look into the installer's log file? If not, it should be saved into /var/log on your machine. I had another look at the install logs, the MAKEDEV commands look like: cd /dev && /bin/echo ad0s4a || /bin/sh MAKEDEV ad0s4a Shouldn't this be rather cd /dev && /bin/echo ad0s4a && /bin/sh MAKEDEV ad0s4a ? The corresponding command part is located at the end of contrib/bsdinstaller-1.1.6/src/lib/libinstaller/commands.c Regards FloW
Re: Installer & HAMMER only
He, * FloW wrote: > > So far everything went smooth, except that the MAKEDEV commands failed > from inside the installer. There was no specific error message. When i > invoked MAKEDEV from the shell the devices were created without error, > and then the installer would proceed. Can anyone reproduce this? No, never saw that during my tests. Do you had the chance to look into the installer's log file? If not, it should be saved into /var/log on your machine. > All HAMMER related stuff worked fine, also the boot loader, and the > HAMMER/PFS layout is set correctly as far as i can tell. So after a > reboot everything was ready, good work! Thanks :) > BTW, is there an obvious way to check the nohistory flags for /tmp, > /usr/obj etc.? Apart from changing files and then check hammer history... ls -lo /tmp Regards Matthias
Installer & HAMMER only
Hi there, just did a fresh install of a recent snapshot ISO from chlamydia, thereby testing the new HAMMER only install option of the DFly installer. So far everything went smooth, except that the MAKEDEV commands failed from inside the installer. There was no specific error message. When i invoked MAKEDEV from the shell the devices were created without error, and then the installer would proceed. Can anyone reproduce this? All HAMMER related stuff worked fine, also the boot loader, and the HAMMER/PFS layout is set correctly as far as i can tell. So after a reboot everything was ready, good work! BTW, is there an obvious way to check the nohistory flags for /tmp, /usr/obj etc.? Apart from changing files and then check hammer history... I also appreciated the pkgsrc and git make targets in /usr, nice! Regards, FloW
