What's taking so long for FreeBSD 7 ? [Archive]

df-sean

01-16-2009, 06:51 PM

It's still listed as "beta/unstable".

The problem is during installation. Important point is that I installed FreeBSD 7.0 several months back with no issues at all. Then a couple months ago, I tried FreeBSD 7.1beta which failed in the exact same way as 7.1-release did yesterday.

Steps to repeat:

1. Install fresh FreeBSD 7.1

2. Install DA license with custombuild and php/apache defaults

3. Installer barfs on wget error as always

4. Compile DA custom wget package as instructed on DA site

5. Start installer again

6. Installer finishes with errors -- unable to compile PHP, etc. Recommends running custombuild -d all again.

7. More errors. Sorry I can't remember specifics, but from memory, MySQL installation is broken (can't be started), PHP still needs to be compiled again, Apache installation is broken (can't write to logs). In short, a very broken system.

Any one else having this kind of trouble?

floyd

01-17-2009, 07:02 AM

scsi said 7 was working not 7.1 The website says that 7.0 is in beta but that generally works. 7.1 is not listed at all.

Now you say:

Important point is that I installed FreeBSD 7.0 several months back with no issues at all.

Question answered. You asked about 7 and you say 7.0 works.

7.1 is a whole other question. Maybe you should be more specific in your questions the first time you ask them.

df-sean

01-17-2009, 05:26 PM

Sorry if my question wasn't specific. But my the essence of my question is the subject "What's talking so long for FreeBSD 7 ?".

The DA site lists support for FreeBSD 7.x (notice the "x" as opposed to a "0") as "Beta/Unstable".

To me this means that in some cases it will work fine and in other cases it won't. And this appears to be exactly what's happening.

Not trying to start any wars here. Just wondering when we can expect FreeBSD 7.x/DA to be considered "stable" and work more reliably.

floyd

01-17-2009, 06:12 PM

The DA site lists support for FreeBSD 7.x (notice the "x" as opposed to a "0") as "Beta/Unstable".

I don't know where you are seeing the 7.x but this page only list 7.0.
http://www.directadmin.com/install.html.

Maybe you should go back to 7.0 since you said it worked fine on that one. Or maybe consider using CentOS since DA is build first for RedHat systems.

nobaloney

01-18-2009, 07:24 AM

Floyd, you hit a lot of buttons on that one :).

Never tell a FreeBSD user to use CentOS.

That's almost as bad as telling a linux user to use FreeBSD :).

It's a religious thing. :D.

That said, even though my first hosting platform was Slackware Linux, we used BSD/OS (http://en.wikipedia.org/wiki/BSD/OS) for years. The company was bought out by WindRiver, who raised the support and licensing costs dramatically, about the same time we started looking at the early Cobalt RaQs (my first ones were the RaQ2 models). So we slowly and painfully moved back to Linux.

Since Cobalt RaQs were running a spinoff of Red Hat Linux, when we left them (or rather, when Sun abandoned us), we used Red Hat Linux, and then later Whitebox Linux and CentOS Linux, as we moved on, first to Plesk (we were a Gold Partner) and then to DirectAdmin.

The trip, down a long and winding road, was certainly worth it to us.

Jeff

df-sean

01-18-2009, 06:32 PM

I'd give anything for a decent control panel like DA but which worked WITH the FreeBSD ports system rather than against it ;-)

HMTKSteve

01-18-2009, 09:38 PM

What is the barf message that the installer fails on in reference to wget?

df-sean

01-18-2009, 09:50 PM

For anyone else that might encounter this... I've found that by changing two things about the way I installed DA has resolved all my problems (not entirely sure which change is responsible for the fix).

1. DON'T "touch .custombuild" before installing. This is no longer necessary since DA gives you the option to choose customapache or custombuild.

2. DON'T install *any* packages before installing DA. Obviously, no apache, myqsl, etc. But also, not even bash for example. I noticed that bash pulled in a couple of dependencies like libiconv and gettext. I think there might have been version inconsistencies that were causing custombuild to lose its marbles.

I've always installed bash and portupgrade straight away after installing FreeBSD, then I proceed to DA install. Never had a problem before. But anyway, after making sure of those two things above, I'm able to install just fine with no issues so far.

Except just one... The wget issue still requires intervention as explained here:
http://help.directadmin.com/item.php?id=77

elvandar

01-27-2009, 10:53 AM

FreeBSD websrv01.xxxx 7.1-STABLE FreeBSD 7.1-STABLE #4 r186904: Thu Jan 8 19:11:44 CET 2009 root@websrv01.xxx:/usr/obj/usr/src/sys/WEBSRV01 i386

We use Directadmin on our i386 7.1-STABLe machine for ages and that works fine. I custom compiled all packages (including PHP which might have one flaw with it so that the marina skin does not work (yet)) and no one ever complained to us that it isn't working.

And no, it didn't help me so far being a FreeBSD committer, I just took over the configuration in the 'configure.x' files that are in the custombuild directory and made several symlinks. I am still trying to free up time to rewrite custombuild for FreeBSD so that it can use the actual ports-system instead of doing the "interesting" recompile thing with a thing that is not actually the thing to do for FreeBSD users, sadly time is an issue for most of us ;-)

//Remko
FreeBSD Committer

Equand

01-28-2009, 05:49 PM

damn, it would be good to have it working on freebsd 7.1
Because we are going to install a 2x 4xcore Xeon server with 32 gigs of ram and as told in this message http://lists.freebsd.org/pipermail/freebsd-performance/2009-January/003660.html it's advantages would be used fully only with bsd 7.1 .
i've installed DA on freebsd 6.4 and it was a pain in the ass because DA uses 'old' codes and 'old' binaries...

df-sean

01-28-2009, 06:19 PM

For that hardware config, you might consider using a 64-bit OS to take advantage of all that RAM. If it needs to work with DA, I think you're stuck with CentOS for 64-bit support.

Personally, my biggest complaint about FreeBSD/DA isn't the age of the packages. It's the fact that by reinventing the wheel with DA packages instead of using FreeBSD ports, it ruins one of the best features of FreeBSD -- the ports system.

For example, to install mod_python on FreeBSD is a simple one-liner with the ports system. But not if Apache was installed by DA. In that case, ports will try to reinstall a non-DA blessed version of Apache as a required dependency of mod_python and things quickly go haywire. So this means you have to install mod_python from source and you can't really use the ports system. And this is a common source of headaches for me with other packages too.

For me, the Holy Grail would be a FreeBSD 64-bit version of DA which works *with* the ports system rather than against it :-)

</rant>

Equand

01-28-2009, 06:36 PM

Well i got a 64-bit FreeBSD 6.4 running DA right now with lib32 enabled.
I had to manually compile almost everything...
So now I try to upgrade to 7.1 using freebsd-update, so the current 4-core 8GB ram system will work decentlye with less LOCKs

Let's see were it will get us...

p.s.: don't even try to tell me anything about linux =), that's just hurting my feelings

df-sean

01-28-2009, 06:45 PM

Wow nicely done! Please let us know how your upgrade goes.

Invader Zim

01-29-2009, 02:13 AM

I've long wanted DA to use the ports when installed on FreeBSD. It is indeed unfortunate that it does not. We've struggled installing Da on FreeBSD 7.0 in combination with ports but it didn't work out all too well. Hitting snag after snag (the biggest example is the libiconv/*csh segfault problem). Getting it to work and then to find out that Installatron can't connect to mysql, no matter what was also something that took the wind out of our sails, so we just gave up after 5 weeks or trial and error.

elvandar

01-29-2009, 11:24 AM

Invader Zim

01-29-2009, 11:37 AM

I never got any information from anyone that things do not work or something. 64bit system with 32bit compat shims might work out best indeed.

Installatron might have used /tmp/mysql.sock or something, which is placed somehwere else on the FreeBSD system, creating a symbolic link might have fixed that, but given that you stopped trying, this might no longer be resolved.

Well, I did post here (http://www.directadmin.com/forum/showthread.php?p=148484) and here (http://www.directadmin.com/forum/showthread.php?p=148618). MySQL wasn't the only problem. There were problems with SuPHP, apache, just a multitude really. but then again, it might just be due to that howto I followed to combine DA & FreeBSD's ports (see below).

Note that by having libiconv from ports I never -ever- got a coredump for csh...
Neither have I. But I have had coredumps with the libiconv installed by DA's installation script which required me to reinstall libiconv from ports. I'm also not the only one (http://www.directadmin.com/forum/showthread.php?t=27741&highlight=freebsd+7.0).

Equand

01-29-2009, 05:19 PM

Wow nicely done! Please let us know how your upgrade goes.
Ok so I've done the upgrade. After
/usr/sbin/freebsd-update -r 7.1-RELEASE upgrade && /usr/sbin/freebsd-update -r 7.1-RELEASE install
check if everything is still ok

shutdown -r
then
/usr/sbin/freebsd-update install(also had to edit some files at this point using vi - goddammit why not ee!?)
then
portsnap -I update (if it asks for something just give it to it, it may ask for fetching and extracting the pkgdb or something, don't remember, but nonetheless do what it asks to.)
Had a bunch of problems with libpthreads and old libs
first with the libs -
cd /usr/ports/misc/compat6x; make; make install
then with that bug of libpthreads a shell script

#!/bin/sh
#Fix For /usr/bin/ld: /usr/lib/libpthread.a(thr_syscalls.o): relocation R_X86_64_32S can not be used when making a shared object; recompile with -fPIC
#/usr/lib/libpthread.a: could not read symbols: Bad value
#Thanx Mel_Flynn on forums.freebsd.org

mkdir /tmp/pthread.bkp
mv /usr/lib/libpthread* /tmp/pthread.bkp/
cd /usr/lib
for ext in .a .so _p.a; do
ln -vs libthr$ext libpthread$ext
done
Than just do
portupgrade -af again.
I've also encountered a bug in ImageMagick and Perl installed from sources on 7.1, maybe because of the old version, but the ports version installed seamlessly in this Release.
then I had to ./build apache and ./build php5-cli and recompile my mysql from sources to catch the new threads (I don't like binaries and I don't like ports setup unless DA makes it compatible with current DA setup).
The system is now working great.
Because of compat6.x I didn't have to recompile all the other stuff which is obviously not the point of my upgrade. But anyways when there'll be new Custombuild stuff i'll try to upgrade it || not on this server, because it's the clients one.

Cheers guys, almost 7+ hours to figure all of this and google all the bugs. Hope this will be useful for somebody.

labrocca

01-29-2009, 08:13 PM

http://www.freebsd.org/releases/7.0R/announce.html

http://www.freebsd.org/releases/7.0R/announce.html

As of yesterday FreeBSD is not supporting 7.0. That means no more security updates. DA has really dropped the ball with it's BSD support imho. Today I am upgrading to 7.1 branch and I hope all goes well but if I need to fight to get it all working so be it. I still want the 64-bit BSD version too. I can't stand having to run the 32 bit binaries on a quad-core. It's ridiculous.

bought out by WindRiver, who raised the support and licensing costs dramatically, about the same time we started looking at the early Cobalt RaQs (my first ones were the RaQ2 models). So we slowly and painfully moved back to Linux.

Since Cobalt RaQs were running a spinoff of Red Hat Linux, when we left them (or rather, when Sun abandoned us), we used Red Hat Linux, and then later Whitebox Linux and CentOS Linux, as we moved on, first to Plesk (we were a Gold Partner) and then to DirectAdmin.

Spooky. I started with the raq2 as well. Cobalt made imho some impressive machines. At least until Sun bought them and destroyed the low-end server market in one purchase. That has always annoyed me.

I then ran Plesk a few years. Eventually they also moved up in pricing and to be honest I was never that happy with Plesk. They also were bought and that's when their pricing got high.

Then I went FreeBSD around 4.11 I think. Been there ever since. I used webmin for a short time but really it wasn't suitable for my needs. I could probably deal with webmin now but of course I have a lifetime license for DA. So as long as DA supports the latest version of BSD I will use it. It doesn't look however this is going to be true much longer at this rate.

For me, the Holy Grail would be a FreeBSD 64-bit version of DA which works *with* the ports system rather than against it :-)

I agree but realistically I doubt DA will bother. To me an even better solution would be a similar commercial package that was dedicated to FreeBSD. DA isn't cutting it and neither is Webmin.

scsi

01-30-2009, 08:09 AM

http://www.freebsd.org/releases/7.0R/announce.html

As of yesterday FreeBSD is not supporting 7.0. That means no more security updates. DA has really dropped the ball with it's BSD support imho. Today I am upgrading to 7.1 branch and I hope all goes well but if I need to fight to get it all working so be it. I still want the 64-bit BSD version too. I can't stand having to run the 32 bit binaries on a quad-core. It's ridiculous.

Spooky. I started with the raq2 as well. Cobalt made imho some impressive machines. At least until Sun bought them and destroyed the low-end server market in one purchase. That has always annoyed me.

I then ran Plesk a few years. Eventually they also moved up in pricing and to be honest I was never that happy with Plesk. They also were bought and that's when their pricing got high.

Then I went FreeBSD around 4.11 I think. Been there ever since. I used webmin for a short time but really it wasn't suitable for my needs. I could probably deal with webmin now but of course I have a lifetime license for DA. So as long as DA supports the latest version of BSD I will use it. It doesn't look however this is going to be true much longer at this rate.

I agree but realistically I doubt DA will bother. To me an even better solution would be a similar commercial package that was dedicated to FreeBSD. DA isn't cutting it and neither is Webmin.

All you do is complain.

Equand

01-30-2009, 08:39 AM

All you do is complain.
what do you expect him to do? rewrite da installation scripts?

hostpc.com

01-30-2009, 08:59 AM

All you do is complain.

I don't see it as "complaining" - he's looking for user and script author feedback on a legitimate question. We could have inserted any OS into this question, it'd still be legitimate.

I don't use BSD - except on a couple of boxes we manage for other customers, personally, I don't like it - but it does have a large following and because someone is persistent in obtaining answers to valid questions shouldn't label them as a "complainer".

Remember, we're all here working together. Directadmin is arguably the best control panel on the market (IMHO) - but if we want it to succeed, we all need to band together and work for it's growth and stability. IMHO, bashing another user for asking questions is counterproductive.

labrocca

01-30-2009, 10:50 AM

All you do is complain.

I am not here to be a DA cheerleader or to coddle members opinions.

If it makes you feel any better I am overall very happy with DA. I don't think it's too much to ask that a software listing FreeBSD support keep up with the latest versions.

DA is giving us two choices. Either run outdated versions or suffer trying to upgrade and deal with problems without their support. DA has had the time to update itself for 7.x which is still listed as beta and now 7.1 is out. Their 7.0 beta is dead now since it's a non-supported branch by FreeBSD.

I will say I updated my server to 7.1 yesterday and I didn't have a single issue with DA. Is that a positive enough comment for you? However I did spend some time getting it working right on 7.0. The upgrade using freebsd-update was fairly painless except for a kernel rebuild to Generic and then back to my custom. DA though just started right up along with all services. I was actually pretty surprised and very pleased. Let's see what happens though on next build or update of a port. :D

floyd

01-30-2009, 10:55 AM

I will say I updated my server to 7.1 yesterday and I didn't have a single issue with DA.

So basically your comment about DA making you use outdated software has no merit since according to you it works just fine on 7.1.

labrocca

01-30-2009, 11:06 AM

As I said though...I spent a lot of time getting it to work on 7.0. I have to assume the changes I made for that allowed it to work well on 7.1.

Will it work..yeah it will. Will I get support...no...I won't. There are about 60 posts in this 7.0 section and only one by DA support telling us Zend Optimizer won't work. As stated..they have had a year to work on getting 7x version out of beta and haven't. Really I don't see why it should take that long. Maybe the 64-bit version would take time to create properly and bug fix but the 32 bit version should have been busted out months ago.

Also what's their plan? What's their timeframes? We have zero information. I expect that kind of thing from a free open source project not from a paid software. I shelled out the full $300 for DA Lifetime. I didn't get it repackaged or from a reseller. I paid full price. Is it so much to ask that DA keep up to date with FreeBSD versions? Is it so much to ask that DA inform us of the progress they are making on creating the branch?

I almost get the feeling that they won't ever support 7x and will just drop FreeBSD.

I want to keep using DA. I like it. It's overall been a good experience for me. So of course I am unhappy when I am updating to latest version and pretty much my support is gone for it in exchange. I offered to be a beta tester for a 64-bit 7x version but seems they haven't really started it yet.

I am not here to attack DA. But I will criticize it's policies especially ones that effect me.

floyd

01-30-2009, 11:18 AM

I shelled out the full $300 for DA Lifetime. I didn't get it repackaged or from a reseller. I paid full price. Is it so much to ask that DA keep up to date with FreeBSD versions?

I don't know. But I do know a $300 lifetime license with absolutely no support from DA is still a lot better than 1 year of Cpanel. If you want to start putting a price tag on things then my opinion is that given the choices out there you still got the best deal.

hostpc.com

01-30-2009, 11:22 AM

I don't know. But I do know a $300 lifetime license with absolutely no support from DA is still a lot better than 1 year of Cpanel. If you want to start putting a price tag on things then my opinion is that given the choices out there you still got the best deal.

Wow. Aside from the cpanel comment, I don't agree with you on that point. (cpanel sucks).

I don't care if someone paid $5 for it, it was sold as supported, commercial software. If they can't support it or if their development tree isn't branching out in this direction any longer, they (da) should provide a different avenue for clients that purchased this product (labeled lifetime). I understand it says "beta" - but there's some responsibility here that needs to be addressed by DA, IMHO.

As I said, I don't use FreeBSD, or anything other than CENT/RHEL (no, not even windows) - but if I had purchased X lifetime licenses for Cent, and they suddenly dropped development of it, I'd be a little pissed too.

labrocca

01-30-2009, 11:23 AM

Without support I would just use Webmin. I almost switched on my new server. If the 7.x didn't work out for me then that was my second choice. I won't use Cpanel. If I needed to...I wouldn't use a panel. I am not reselling. I use DA for simple control of my server. I do 90% of everything via SSH already. Adding new domains and email accounts is just simpler with DA but Webmin isn't far behind for ease of use.

Have you seen webmin lately?

As I said, I don't use FreeBSD, or anything other than CENT/RHEL (no, not even windows) - but if I had purchased X lifetime licenses for Cent, and they suddenly dropped development of it, I'd be a little pissed too.

Exactly. You can see a lot of BSD users not very happy at current situation. DA knows we won't switch from BSD. I been using it before there was a CENT OS. I would drop DA before dropping BSD. And that's the corner they are pushing some of us towards.

floyd

01-30-2009, 11:41 AM

I don't care if someone paid $5 for it, it was sold as supported, commercial software.

I am just saying even without support $300 is still a good price and I know knowing what I know now about DA I would have paid $300 if support was not included. I have been using DA for almost 4 years and have 71 lifetime licenses. I don't think I have ever emailed them for support. But I am also using the system that DA is built on.

Have you seen webmin lately?

Yes I use it all the time alongside DA. Great for admins, not so great for end users. If I did not have other end users I would just use webmin.

but if I had purchased X lifetime licenses for Cent, and they suddenly dropped development of it

I know your opinion will be different but here is another viewpoint to consider. The license for DA is for the lifetime of DA not for a particular OS.

What if the OS goes out of business? The license you have for DA is still valid. You just have to use another OS with it.

If you want to say that the license is for DA on a prticular OS then that would mean that if you wanted to use another OS you would have to purchase another license. You would not be able to transfer the license to another OS.

But hey, I don't use FreeBSD. I really don't care. I don't even know why I am here in this thread.

labrocca

01-30-2009, 11:59 AM

Yes I use it all the time alongside DA. Great for admins, not so great for end users. If I did not have other end users I would just use webmin.

That's my current position as an admin only. I am kicking off all my clients. They are just not worth my time to be honest. Most are friends though that didn't pay me much to begin with.

I am just saying even without support $300 is still a good price and I know knowing what I know now about DA

It is a good price but let's say I wanted to run a second license. As DA is right now with their BSD support I wouldn't choose to use it. It's a great value for many new admins or people that want to do reselling. I am not in that position.

What if the OS goes out of business?

FreeBSD has not gone out of business. They have kept a good pace of development even. DA should keep up. It was their decision to support FreeBSD.

Bah...gonna try and get some work done. Moving some sites to new server today.

Bye guys.

floyd

01-30-2009, 12:07 PM

FreeBSD has not gone out of business. They have kept a good pace of development even. DA should keep up. It was their decision to support FreeBSD.

I am not saying they did or ever will. I am commenting about all OS's.

Is the lifetime license for DA on a particular OS? No. Do they have to continue to support FreeBSD just because somebody bought a lifetime license? No. The license is still valid. But that is how I am reading it. Maybe we should get a comment from DA staff.

Equand

01-30-2009, 01:34 PM

I am not saying they did or ever will. I am commenting about all OS's.

Is the lifetime license for DA on a particular OS? No. Do they have to continue to support FreeBSD just because somebody bought a lifetime license? No. The license is still valid. But that is how I am reading it. Maybe we should get a comment from DA staff.
Wow man you are completely not right. Directadmin supports the releases, I mean if they release version 6.0 that means there won't be any changes which will break compatability in further releases, that's why DA supports 6.x, now for the 7th branch they still got it in beta, however why the hell it would be beta? all they need to fix is port installing everything else works ok (well 64bit is not completely all right but okay...).

floyd

01-30-2009, 01:44 PM

Wow man you are completely not right.

Interesting. You tell me I am not right but then don't comment on anything I said. The license if for DA. It is not for a particular OS.

scsi

01-30-2009, 02:00 PM

Wow man you are completely not right. Directadmin supports the releases, I mean if they release version 6.0 that means there won't be any changes which will break compatability in further releases, that's why DA supports 6.x, now for the 7th branch they still got it in beta, however why the hell it would be beta? all they need to fix is port installing everything else works ok (well 64bit is not completely all right but okay...).

Its in beta because they are still testing its functionality. Dont worry about it it works fine I guess. There is also no reason you cannot install everything via ports on your own.

Equand

01-30-2009, 02:32 PM

Its in beta because they are still testing its functionality. Dont worry about it it works fine I guess. There is also no reason you cannot install everything via ports on your own.
sure, if DA could allow a clean install...

IT_Architect

01-30-2009, 04:43 PM

For me, the Holy Grail would be a FreeBSD 64-bit version of DA which works *with* the ports system rather than against it :-)
I'm not sure what will happen with DA regarding ports. What I do know is that cPanel did a full rewrite, or so they say, on FreeBSD and their statement said use FreeBSD only if you know what you are doing, and the ONLY supported method of updating cPanel under FreeBSD is if you DO use ports. I haven't worked with cPanel lately but from I've heard, it now works well and is not fragile. I haven't tried Plesk lately although it's free for one domain and one e-mail. I'm not big fan of qMail.

scsi

01-30-2009, 10:51 PM

But custombuild is the one that installs everything why cant it just be updated to use the freebsd ports? I doubt anything with directadmin would have to change besides that.

IT_Architect

01-31-2009, 10:01 AM

But custombuild is the one that installs everything why cant it just be updated to use the freebsd ports? I doubt anything with directadmin would have to change besides that. I'm with you. I don't know how DA's install works but according to cPanel, switching to ports for everything solved their BSD problems. The posts by some of the users confirm that. Ports and PortSnap are the way to go for us.

So far things working good for us with 7. I'm working on 7.1, that's why I'm visiting this thread. I'm not going to get my shorts in a bunch until I run into problems.

I doubt anybody ends up on FreeBSD without getting dragged there kicking and screaming. Because of that the conversion ratio from FreeBSD to Linux for a control panel will be about zero because the possibility doesn't even exist for those people. Linux is where they came from. They tried long and hard to stay there, but couldn't.

df-sean

02-01-2009, 04:31 PM

I doubt anybody ends up on FreeBSD without getting dragged there kicking and screaming.
Personally, I was delighted to move to FreeBSD. I find it to be a far more stable experience and far more pleasant to work with than my previous experiences with Debian and various RedHat clones.

Not trying to win any converts here, but just to make the point: I think there *are* a lot of converts who came to FreeBSD from a Linux background and never looked back. I'm one of 'em.

Now if only DA would give FreeBSD the first class treatment it deserves... :-)

Geffy

02-03-2009, 04:09 PM

With a bit of hoop jumping its quite possible to run DA on a server and manage just about everything with ports, the exception I've got at the moment is exim which I'm still running from the da_exim pkg, vm-pop3d isn't an issue we're using Dovecot and proftpd seems fine straight from ports. The biggest hoop was apache, but we compromised on /usr/local/etc/apache22 and its config then including the ips.conf and /etc/httpd/conf/httpd.conf just having the Include lines for the virtual hosts.

We've only done this on one server though, after that management opted for FedorianOSHat instead and someone else now gets to manage them, I handle our internal systems (FreeBSD) manually.

Only thing I'm now wondering is if a portupgrade update of perl to 5.8.9 is going to break Exim at all. It looks like /usr/sbin/exim is statically linked but I'm still a bit apprehensive.

Invader Zim

02-04-2009, 12:05 AM

Despite DA not using the ports system on FreeBSD I do get messages from portaudit, like

Affected package: proftpd-1.3.1
Type of problem: proftpd -- Long Command Processing Vulnerability.
Reference: <http://www.FreeBSD.org/ports/portaudit/0f51f2c9-8956-11dd-a6fe-0030843d3802.html>

Affected package: freetype2-2.3.5
Type of problem: FreeType 2 -- Multiple Vulnerabilities.
Reference: <http://www.FreeBSD.org/ports/portaudit/4fb43b2f-46a9-11dd-9d38-00163e000016.html>

Affected package: png-1.2.23_1
Type of problem: png -- unknown chunk processing uninitialized memory access.
Reference: <http://www.FreeBSD.org/ports/portaudit/57c705d6-12ae-11dd-bab7-0016179b2dd5.html>

So despite not being installed via the ports, they are registered? It's a bit odd to have portaudit report this and then not be able to update them via the ports, just in case something gets broken (compilation wise or config wise).

Equand

02-08-2009, 05:21 PM

yeah i also had portupgrade report this ports...

guys also check after rebuilding the directadmin to not relink the libiconv.so to another libiconv, that can render your system useless by segfaulting csh.
check the link in /usr/local/lib/libiconv.so to lead to libiconv.so.3 not so.6 or anything that DA may provide...

pucky

02-09-2009, 09:10 AM

This is a fairly large thread yet noone from DA has chimed in. Why is that? I'd like to hear from someone from DA on what they intend to do. Im still running 6.1 and 6.2 installs but im ready to start upgrading my boxes.

pucky

02-09-2009, 09:46 PM

BUMP

The message you have entered is too short! :rolleyes:

DirectAdmin Support

02-10-2009, 05:09 PM

Hello,

We'll look at changing the iconv to use ports instead of from source in custombuild.. that's really the only hangup right now for it's "unstable" status. The workaround for using /bin/sh is simple enough to do which is probably why it's been put off, but it's just that, a workaround.

John

Equand

02-11-2009, 06:14 PM

Chrysalis

02-14-2009, 01:42 AM

Got 2 DA boxes running FreeBSD 7.0, with the reminder ealier in the thread that 7.0 is indeed EOL I will shortly be updating these boxes to 7.1, I expect no problems since minor freebsd revisions tend to not break things like directadmin.

The problem I see at the moment with the freebsd support is the obvious lack of port usage, the broken csh binary after installing DA and that it installs out of date packages.

Utilising the ports system would mean providing the ports tree is up to date then any installed packages would also be up to date, it would solve dependency issues hence the broken csh and it should in theory be easier for DA to maintain scripts as using ports is simpler than manual configuring/compiling.

labrocca

02-14-2009, 01:31 PM

With portsnap updating the ports tree has never been easier. They should definitenly use the ports. I don't think any FreeBSDer even questions that. I even think if they did take the time they might gain many more DA users in the BSD community that scoff at DA's lack of ports use. It's a weird akward feeling to install stuff in BSD without ports.

df-sean

02-14-2009, 03:33 PM

Wow -- I guess I'm not the only one with these feelings after all :-)

DirectAdmin Support

02-14-2009, 03:35 PM

http://www.directadmin.com/forum/showthread.php?p=150413#post150413

bjseiler

02-15-2009, 06:18 AM

Could you clarify then if any of the steps (1, 2, or 5) from this post are required then to get FreeBSD 7.1 64 to work "out of the box" with DA?

http://www.directadmin.com/forum/showthread.php?t=27741&highlight=freebsd

I went through the above process this week to get one machine running. No real major issues but definitely not as easy as when running setup just works.

It is definitely nice to be able to get the full power out of the machines.

64 bit with 4GB RAM, DA, Freebsd 7.1

Processor Name Intel(R) Xeon(R) CPU 3065 @ 2.33GHz (2333.51-MHz K8-class CPU)
Total Memory 4082.01 MB
Free Memory 3387.13 MB

Same exact machine with 32 bit

Processor Name Intel(R) Xeon(R) CPU 3065 @ 2.33GHz (2333.51-MHz 686-class CPU)
Total Memory 3314.17 MB
Free Memory 1952.39 MB

Thank you for continuing to support FreeBSD. I would also like it if everything used ports but I have no problem settling for just working without having to do a ton of custom changes and tweaks each time I need to set up a new server or update an old one.