Search results

The PR is kern/164143

I have been prepping my servers for a FreeBSD 8.2R -> 9.0R upgrade. So far the upgrade process has been very easy and straight-forward. This thread caused me some pause on my gmirror server. It has two mirrors using MBR. Has this problem been confirmed from someone else regarding an issue...

I thought the issue could have resulted from an upgrade of MySQL 5.0.29 (databases/mysql50-client) to MySQL 5.5 (databases/mysql55-client) but I removed 5.5 and installed 5.0.29 again. I still received a mysqlclient error -- this time mysqlclient.15 instead of mysqlclient.18. maia-1.0.3.r1575_1...

Same issue here: [root@postfix /usr/ports/security/maia]# make install ===> maia-1.0.3.r1575_1 depends on shared library: mysqlclient.18 - not found ===> Verifying install for mysqlclient.18 in /usr/ports/databases/mysql55-client ===> Returning to build of maia-1.0.3.r1575_1 Error...

Thought I'd chime in since this topic about root's shell happens more times than I can remember. Don't change root's shell. This is very good advice. I always tell people who *DEMAND* bash or another "3rd party" shell for root to use "su -m" (uses current users shell ie: bash) or more...

Guess it's okay for you to be "condescending" and to actually expect 100% serious answers. Basically what they are saying is true though. You are wanting an updated software without updating your system. What steps have you taken? The answers given above are applicable to your situation...

I just did this upgrade (7.2p5 -> 8.0p1) remotely. I usually do a source update but this time opted for a binary update so I can make sure I stay "fresh" on both methods. It was absolutely mind-numbingly simple. The delete-old(-libs) function happens on the third time you run freebsd-update...

That appears to be what I want. I went in and checked my bsdlabel -e on gm1 and it already was setup how I wanted. I guess the real confusion was which partition that it created was the right one. crw-r----- 1 root operator 0, 161 Oct 20 19:33 gm1 crw-r----- 1 root operator 0...

Sorry to bump but I'm still having trouble getting this setup properly. Any ideas?

So I am able to slice/label/mount each drive individually just fine outside of geom_mirror. It's when I create a mirror that I run into problems. I created one large partition on ad8 and ad10. They were ad8s1d and ad10s1d respectively. They mounted fine at /ad8 and /ad10. I unmounted...

Right, but I'm not having a problem with the gmirror syntax or adding/removing devices. I'm having a drive slice problem. By doing the commands you recommend I would still need to format the drives for use which leaves me in the same position? Is the proper solution to delete the 500GB...

I have just added 2 hard drives to my 7.2-RELEASE-p4 server. These drives are identical WD 500GB 7200 SATA drives. The server is a Tyan GX28 (B2881G28S4H if you want the specific model for any reason). I;m having trouble getting the system to format these correctly. I sadly have relied on...

In this scenario you will almost *always* have to use a dos bootable disk with the dos flash program and bios file. There are a lot of variables but the above solution is a very general one without knowing anything more.

It's fairly hard to guess what the problem is with the information presented not giving the whole picture. However, I would suggest that vscan may not be what clamav is running as. A lot of setups use different permissions: -rw-r----- 1 clamav clamav 630K Aug 10 14:32 clamd.log -rw-r-----...

@danger: Just stumbled upon your sysinfo script. Pretty nice output with lots of information. Could be great for providing "background info" when asking for help on the forum to see where problems reside. Keep up the good work and thank you sir.

That is the incorrect way to update your jail. If you use ezjail, it makes everything so simple it's almost a joke. If you do not use ezjail then you need to understand a bit more about the jail process. Here is a very shortened version of what you would do: 1) Hopefully you have csup...

If I read this correctly then yes it is possible. Drive C will remain encrypted with XP and will not be written to. Drive D will have FreeBSD installed along with a bootmgr. The only trick here is having a bootmgr list and correctly map to both operating systems. I'd imagine that the easiest...

I didn't expect to see this thread pop up again. I thought the issue was laid to rest. I think people are completely ignoring the issue this thread addresses. It addresses the support and sometimes total dismissal of the finstall project to move into production. The last couple posts...

It's possible he included multiple or all packages by default. Most people wouldn't incur such a large install but it isn't out of the realm of possibility so it's wise to make it inclusive in the problem analysis.

The perl-after-upgrade script is often neglected. It is very easy and quite useful. That should've fixed the problem and I only post a reply to confirm this solution to anyone upgrading perl and breaking perl dependencies thereafter.