What is "nanobsd" ?
-
Thare a new folder in the -stable 7.1 tree named: nanobsd
What the plan?Dream would come through if pfSense would flash on regular router like WRT54GL or somthin :o ;D
-
If I remember right, the embedded images may start using that, at least on 2.0. Not too sure of the particulars.
Here's some more info on nano:
http://www.freebsd.org/doc/en/articles/nanobsd/index.html -
i see nanobsd images available on snapshot server, r they stable enough to give it a try on a alix board or do they atleast get pfsense to a running state?
-
i see nanobsd images available on snapshot server, r they stable enough to give it a try on a alix board or do they atleast get pfsense to a running state?
Please honk when/if you gonna try any of the nano snaps. Let us/me know if it run, Thanks
-
I want to give it a try, but whats the difference between it and the embedded version? From the description from the above link it sounds the same, but the size of the image is bigger 30 (embedded) vs 37 (nanobsd). Any thoughts from anyone?
-
I want to give it a try, but whats the difference between it and the embedded version? From the description from the above link it sounds the same, but the size of the image is bigger 30 (embedded) vs 37 (nanobsd). Any thoughts from anyone?
I think the pfSense code is functionally identical, but apparently the nanobsd images use two slices, one to run off of and one for upgrading. If the upgrade takes, it uses the new slice, but if it fails, the old one is still there.
I need to pick up a spare CF and then I'll give them a spin. I could do it now, but with only one CF it's just kind of a pain to reflash too much, takes too long to get back up and running.
-
Ill give it a try in the next 5 mins on an alix c2c and report back.
Slam
-
FYI- You only need to download/dd the .img file, the .slice is for upgrades only.
-
Opps, thanks, Ill download the non slice images.
Slam
-
Ill give it a try in the next 5 mins on an alix c2c and report back.
Slam
Hoj, whare did you go?, you wrote 5min man, iv been waiting here since forever :)
-
lol I was half way flashing the slice image when I read Jimps post, so I had to stop and download the correct image, the image is 1GB when unpacked and it took ages to burn, I think atleast 10~13 mins, I dont have no serial port on these alix so I cant connect and see whats happening but Ive had no luck getting an ip from either ports…I have an atheros mini pci card installed, Ill take that out and try again, maybe its prompting for configuration?
Slam
-
Looks like I'll need a new CF before I try, mine is only 256MB :)
-
Hmm. Decided to try the nano image on my Alix just to see what happens.
Yes, the image is larger. It's go get a refreshing beverage longer. Maybe get up and get some fresh air longer. Not surprising- the root fs is 950M, the custom 1 GB 1.2.2 I built takes about the same time to write to the card.
Once loaded, it seems to run pretty much the same as the standard image. I tried it on a 2d3 with an atheros card and it came up fine with vr0 as lan and vr1 as wan. -
ohh ok.. I have not had time to try this yet, but it has a bigger image by default then the regular embedded? sounds good since it seemed like they were running out of room, at least with the 2.0 version. I will give this a try tonight!
-
ohh ok.. I have not had time to try this yet, but it has a bigger image by default then the regular embedded? sounds good since it seemed like they were running out of room, at least with the 2.0 version. I will give this a try tonight!
It may be that is the size for testing, not sure what the final target size will be. I'm also not sure if the usable space will really be 1/2 what you see in the image or what. Since it uses an active slice and an upgrade slice, the total space available may only be half the full image size.
-
Not sure how exiciting this is to everyone, but got it up and running on a Soekris 5500 box. Haven't tested much other then looking at the serial console interface, but I will test it out tomorrow night.
-
Definitely let us know if she upgrades successfully and any package installations. ;)
-
got everything up and running and logged into the web interface. I had some unusual errors at one point when I restarted the box and it had some sort of error and rebooted itself again and worked fine after it did a file system check. Tried to do an auto upgrade, which did not work. Tried downloading the slice and doing a manual update, which did not work. And last but not least I SSH'd in and tried from the console and it failed saying "/var: write failed, filesystem is full" I checked my stats and it says 9% full. Is there another procedure for updating a NanoBSD?
-
/var is still a memory disk, so this is the same problem that the embedded upgrades have had.
-
A little update, the nanobsd images really haven't seen much testing and debugging by the devs until the last couple days, and even then things are focusing on 2.0 and then backporting fixes where possible.
I've got nano image running on my ALIX right now with a FreeBSD 7.2-based image of 2.0, and it's getting better all the time. There are still some kinks to work out though.
