tag:blogger.com,1999:blog-4361733293216582854.post5935814427054561363..comments2024-01-24T23:36:45.356-08:00Comments on Adrian Chadd's Ramblings: FreeBSD on a tiny system; what's missingAdrianhttp://www.blogger.com/profile/17496219706861321916noreply@blogger.comBlogger5125tag:blogger.com,1999:blog-4361733293216582854.post-46152080109613095182016-10-24T00:10:10.893-07:002016-10-24T00:10:10.893-07:00hi ,
i have try all the steps given by you and wh...hi ,<br /><br />i have try all the steps given by you and which is present on the gitub.com to run freebsd on mips processor . i have run the build.sh after doing all the neccessary settings , but when i run it using qemu it through an error that no kernel found . <br /><br /><br />can you help me in getting out of this , or you can provide me the image which you build for freebsd / mips .Anonymoushttps://www.blogger.com/profile/06323273989318853356noreply@blogger.comtag:blogger.com,1999:blog-4361733293216582854.post-399464888518027172016-09-13T18:10:18.602-07:002016-09-13T18:10:18.602-07:00I'm the author of jobd, and it does sound like...I'm the author of jobd, and it does sound like your needs mesh well with the design goals of jobd. If you end up hacking on jobd, I'd be interested to hear about it, and willing to take any patches to improve efficiency on tiny hardware.<br /><br />It uses kqueue(2) to dispatch events from a single master process, so you don't end up with multiple supervisor processes like in other solutions.<br /><br />It's cron emulation code tries to avoid unnecessary wakeups. Unlike tho original cron, which wakes up every minute, jobd only wakes up when there is at least one job that is ready to run. For example, if you had a single cronjob that ran once per hour, it would sleep for an entire hour before waking up to run the job.<br /><br />The question about IPC and notifications is another area where I want to improve jobd and offer a simple event notification system. Even without an IPC mechanism, you could do things like have jobd watch a file or directory for changes, and then launch a job when a change is detected.Anonymoushttps://www.blogger.com/profile/03205160115986421831noreply@blogger.comtag:blogger.com,1999:blog-4361733293216582854.post-65864859669095523332016-09-06T20:49:35.331-07:002016-09-06T20:49:35.331-07:00devd can do the ntpdate thing, and likely the othe...devd can do the ntpdate thing, and likely the other stuff that happens when an interface comes upAnonymoushttps://www.blogger.com/profile/08661894485809686710noreply@blogger.comtag:blogger.com,1999:blog-4361733293216582854.post-13050869131558509552016-08-14T21:48:22.051-07:002016-08-14T21:48:22.051-07:00We're using s6 at work, and it works out mostl...We're using s6 at work, and it works out mostly ok. Mostly once you get around the linuxisms, and the lack of sensible time code in it (its calculations for daemon run duration is based on system time, not wall clock, so if your box boots jan 1, 1970 then gets NTP, things are.. hilarious), and some of the arcane bits to get logging working right.<br /><br />But mainly it's how many processes and memory it uses - these boards can have 16MB or 32MB of RAM, so every process adds overhead. I'm thinking of either jobd or writing something single process and lightweight (based on BSD init, and minimal bits from jobd/launchd) because of the insanely small memory footprints for 2016.<br /><br />Damned IoT.Adrianhttps://www.blogger.com/profile/17496219706861321916noreply@blogger.comtag:blogger.com,1999:blog-4361733293216582854.post-84607306804179226392016-08-14T12:22:43.375-07:002016-08-14T12:22:43.375-07:00You might want to look at s6 and s6-rc. The design...You might want to look at s6 and s6-rc. The design is clean and portable enough to work on FreeBSD out of the box even if it's written for Linux. I have s6-svscan working as PID 1 on FreeBSD 10.3 in a test VM and it reduces the userspace boottime to < 1s.Anonymoushttps://www.blogger.com/profile/08878350622123574507noreply@blogger.com