[prev in list] [next in list] [prev in thread] [next in thread]
List: pfsense-discussion
Subject: Re: [pfSense] Compile on Sun v215
From: Moshe Katz <moshe () ymkatz ! net>
Date: 2013-12-10 2:43:35
Message-ID: CALJwmGBWkO6pDqc98qK12b4Xcdx3MGGUghgEmM2tUcYVbBkYdw () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
On Dec 9, 2013 6:37 PM, "Adam Hunt" <voxadam@gmail.com> wrote:
>
> What parts of pfSense are so arch dependent. One would expect being based
on FreeBSD would make it quite portable.
>
>
> On Mon, Dec 9, 2013 at 3:25 PM, Jim Thompson <jim@netgate.com> wrote:
>>
>> it would be a lot of work.
>>
>> There was some work done back in history on a MIPS port. It never
>> actually finished.
>>
>> There is very little interest in a SPARC port, though, as Adam
>> allowed, nobody would really mind, other than the consequences of what
>> to call it, and how to explain the support model for it, etc.
>>
>> Jim
>>
>>
>> On Mon, Dec 9, 2013 at 3:46 PM, Adam Hunt <voxadam@gmail.com> wrote:
>> > pfSense only supports x86 and amd64 architectures. Though, I suppose
if you
>> > wanted to port it to SPARC nobody would mind.
>> >
>> >
>> > On Mon, Dec 9, 2013 at 3:55 AM, Jim Thompson <jim@netgate.com> wrote:
>> >>
>> >> Unlikely.
>> >>
>> >> -- Jim
>> >>
>> >> > On Dec 9, 2013, at 4:07, Denny Fuchs <linuxmail@4lin.net> wrote:
>> >> >
>> >> > hi,
>> >> >
>> >> > I want to use old two of Sun Fire SPARC v215 for pfsense. FreeBSD
8/98
>> >> > runs without any problems, so the only question is, if it does make
sense to
>> >> > compile pfsense on that hosts.
>> >> >
>> >> > Ram: 12GB
>> >> >
>> >> > # cat /proc/cpuinfo
>> >> > cpu : TI UltraSparc IIIi (Jalapeno)
>> >> > fpu : UltraSparc IIIi integrated FPU
>> >> > pmu : ultra3i
>> >> > prom : OBP 4.22.33 2007/06/18 12:47
>> >> > type : sun4u
>> >> > ncpus probed : 2
>> >> > ncpus active : 2
>> >> > D$ parity tl1 : 0
>> >> > I$ parity tl1 : 0
>> >> > cpucaps :
>> >> > flush,stbar,swap,muldiv,v9,ultra3,mul32,div32,v8plus,vis,vis2
>> >> > Cpu0ClkTck : 0000000059a53800
>> >> > Cpu1ClkTck : 0000000059a53800
>> >> > MMU Type : Cheetah+
>> >> > State:
>> >> > CPU0: online
>> >> > CPU1: online
>> >> >
>> >> > cu denny
>> >> >
>> >> >
Adam,
As I found when I tried to do a custom build for Nokia IP380 (a Pentium
III, so it is x86, but it requires removing USB support from the kernel in
order to boot successfully for some reason) and a custom build with Hyper-V
kernel extensions, there are really three problems.
1. Build System. As Jim said, you need to get the build system working
properly. I would have thought this would be fairly easy in my case, given
that I was making pretty much a single kernel change to each build, but it
turned out to be much more difficult.
2. Updates. Even once you have a working build system, you need to take
every released pfSense update and rebuild it for yourself. You could
likely automate that on your build system, but there's no guarantee that
you will be able to build future updates without needing to tweak anything
and/or assist the build system itself.
3. Packages. You may have to copy the package server and hottest your own
version for any packages that you care about.
Moshe
[Attachment #5 (text/html)]
<p dir="ltr"><br>
On Dec 9, 2013 6:37 PM, "Adam Hunt" <<a \
href="mailto:voxadam@gmail.com">voxadam@gmail.com</a>> wrote:<br> ><br>
> What parts of pfSense are so arch dependent. One would expect being based on \
FreeBSD would make it quite portable.<br> ><br>
><br>
> On Mon, Dec 9, 2013 at 3:25 PM, Jim Thompson <<a \
href="mailto:jim@netgate.com">jim@netgate.com</a>> wrote:<br> >><br>
>> it would be a lot of work.<br>
>><br>
>> There was some work done back in history on a MIPS port. It never<br>
>> actually finished.<br>
>><br>
>> There is very little interest in a SPARC port, though, as Adam<br>
>> allowed, nobody would really mind, other than the consequences of what<br>
>> to call it, and how to explain the support model for it, etc.<br>
>><br>
>> Jim<br>
>><br>
>><br>
>> On Mon, Dec 9, 2013 at 3:46 PM, Adam Hunt <<a \
href="mailto:voxadam@gmail.com">voxadam@gmail.com</a>> wrote:<br> >> > \
pfSense only supports x86 and amd64 architectures. Though, I suppose if you<br> \
>> > wanted to port it to SPARC nobody would mind.<br> >> ><br>
>> ><br>
>> > On Mon, Dec 9, 2013 at 3:55 AM, Jim Thompson <<a \
href="mailto:jim@netgate.com">jim@netgate.com</a>> wrote:<br> >> \
>><br> >> >> Unlikely.<br>
>> >><br>
>> >> -- Jim<br>
>> >><br>
>> >> > On Dec 9, 2013, at 4:07, Denny Fuchs <<a \
href="mailto:linuxmail@4lin.net">linuxmail@4lin.net</a>> wrote:<br> >> \
>> ><br> >> >> > hi,<br>
>> >> ><br>
>> >> > I want to use old two of Sun Fire SPARC v215 for pfsense. \
FreeBSD 8/98<br> >> >> > runs without any problems, so the only \
question is, if it does make sense to<br> >> >> > compile pfsense on \
that hosts.<br> >> >> ><br>
>> >> > Ram: 12GB<br>
>> >> ><br>
>> >> > # cat /proc/cpuinfo<br>
>> >> > cpu : TI UltraSparc IIIi (Jalapeno)<br>
>> >> > fpu : UltraSparc IIIi integrated FPU<br>
>> >> > pmu : ultra3i<br>
>> >> > prom : OBP 4.22.33 2007/06/18 12:47<br>
>> >> > type : sun4u<br>
>> >> > ncpus probed : 2<br>
>> >> > ncpus active : 2<br>
>> >> > D$ parity tl1 : 0<br>
>> >> > I$ parity tl1 : 0<br>
>> >> > cpucaps :<br>
>> >> > \
flush,stbar,swap,muldiv,v9,ultra3,mul32,div32,v8plus,vis,vis2<br> >> >> \
> Cpu0ClkTck : 0000000059a53800<br> >> >> > Cpu1ClkTck : \
0000000059a53800<br> >> >> > MMU Type : Cheetah+<br>
>> >> > State:<br>
>> >> > CPU0: online<br>
>> >> > CPU1: online<br>
>> >> ><br>
>> >> > cu denny<br>
>> >> ><br>
>> >> ></p>
<p dir="ltr">Adam,</p>
<p dir="ltr">As I found when I tried to do a custom build for Nokia IP380 (a Pentium \
III, so it is x86, but it requires removing USB support from the kernel in order to \
boot successfully for some reason) and a custom build with Hyper-V kernel extensions, \
there are really three problems.</p>
<p dir="ltr">1. Build System. As Jim said, you need to get the build system working \
properly. I would have thought this would be fairly easy in my case, given that I was \
making pretty much a single kernel change to each build, but it turned out to be much \
more difficult.</p>
<p dir="ltr">2. Updates. Even once you have a working build system, you need to take \
every released pfSense update and rebuild it for yourself. You could likely \
automate that on your build system, but there's no guarantee that you will be \
able to build future updates without needing to tweak anything and/or assist the \
build system itself.</p>
<p dir="ltr">3. Packages. You may have to copy the package server and hottest your \
own version for any packages that you care about.</p> <p dir="ltr">Moshe</p>
_______________________________________________
List mailing list
List@lists.pfsense.org
http://lists.pfsense.org/mailman/listinfo/list
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic