|
Hopefully I'm just still looking in all the wrong places, but nVidia/ATI support in BSD is pretty crappy still right?
|
#
?
Nov 17, 2012 12:28
|
|
|
|
| # ? May 29, 2024 15:30 |
|
|
NVIDIA has published drivers for FreeBSD x86 and AMD64. It looks like only the open source radeonhd driver is available via ports. e: looks like the proprietary NVIDIA driver is available via ports as well. SamDabbers fucked around with this message at 13:45 on Nov 17, 2012 |
|
#
?
Nov 17, 2012 13:34
|
|
|
http://www.freebsd.org/news/2012-compromise.html Some FreeBSD servers were compromised - but FreeBSD wasn't "hacked".
|
|
#
?
Nov 17, 2012 14:15
|
|
|
Will that "hacking" delay the release of FreeBSD 9.1 even more (because of package auditing)? portsnap just told me that it grabbed 24085 patches. Is that normal? Did I mess something up? Was a mass update pushed somewhere? Also, how can I make gcc (or whatever FreeBSD 9.0/9.1 use) be more multi-core friendly? When compiling thing, top says it has one core at 100%, and the 23 other cores are idle. Actually, how can I get everything to use the CPU more? I'm using a Dual Xeon E5-2630 setup (12 physical, 24 logical cores). From extracting to compiling to moving data, most CPU cores just sit there, idle.
|
|
#
?
Nov 19, 2012 17:32
|
|
|
Xenomorph posted:Also, how can I make gcc (or whatever FreeBSD 9.0/9.1 use) be more multi-core friendly? When compiling thing, top says it has one core at 100%, and the 23 other cores are idle. You need to tell 'make' to use more cores make -j x Where x is the number of cores, on a workstation that's going to be # of logical CPU's in the system (24 in your case) + 1 I don't have a box in front of me but I think you can make that the default in /etc/make.conf
|
|
#
?
Nov 19, 2012 17:43
|
|
|
Bob Morales posted:You need to tell 'make' to use more cores Thanks. That info helped me find this: http://forums.freebsd.org/showpost.php?p=17604&postcount=14
|
|
#
?
Nov 19, 2012 17:59
|
|
|
Xenomorph posted:Thanks. One of the first things I did when I got my hands on an i7 was building everything I could get my hands on  Edit: You could probably used distcc to pair up with another box
|
|
#
?
Nov 19, 2012 18:01
|
|
|
Bob Morales posted:You need to tell 'make' to use more cores Make will already use kern.smp.cpus make jobs in ports that explicitly set MAKE_JOB_SAFE. Also it is a much better idea to set MAKE_JOBS_NUMBER and FORCE_MAKE_JOBS in your make.conf, as it will still build ports that explicitly report that they cannot be built with multiple make jobs, yet also build using multiple make jobs for ports that do not say and those that explicitly report being safe with multiple make jobs.
|
|
#
?
Nov 20, 2012 01:05
|
|
|
Xenomorph posted:Will that "hacking" delay the release of FreeBSD 9.1 even more (because of package auditing)? The delay will be because they have to rebuild all the packages again to ensure they weren't tampered with. Xenomorph posted:portsnap just told me that it grabbed 24085 patches. Is that normal? Did I mess something up? Was a mass update pushed somewhere? As part of the resync of the ports tree (subversion) it caused portsnap to think the entire ports tree was changed and everyone gets to redownload the entire tree. Lame. There's now a huge discussion of leaving subversion for an SCM that can handle cryptographic signing of commits so a tampered-with source tree is easily detected. Unfortunately git being GPL'd it's not a viable option, and Mercurial is a pig and would require that Python be brought into base. Fossil is being looked into... edit: fossil will not happen. perhaps forking/extending svn. Xenomorph posted:Also, how can I make gcc (or whatever FreeBSD 9.0/9.1 use) be more multi-core friendly? When compiling thing, top says it has one core at 100%, and the 23 other cores are idle. You can enable multiple cores for compiling all src and ports. Just please keep in mind that this is wholly unsupported and if you have any programs acting strange and someone finds out that you've been compiling everything with your own flags you will be told to rebuild your system normally. feld fucked around with this message at 16:29 on Nov 22, 2012 |
|
#
?
Nov 20, 2012 14:37
|
|
|
Would an upgrade from FreeBSD 9.1 RC3 to 9.1-RELEASE be a direct (and quick) binary upgrade, or is it some sort of "make world" process where I have to watch the system compile thousands of binaries?
|
|
#
?
Nov 28, 2012 18:36
|
|
|
Xenomorph posted:Would an upgrade from FreeBSD 9.1 RC3 to 9.1-RELEASE be a direct (and quick) binary upgrade, or is it some sort of "make world" process where I have to watch the system compile thousands of binaries? Whichever you prefer  The process should be something like: # freebsd-update upgrade -r 9.1-RELEASE
|
|
#
?
Nov 28, 2012 18:44
|
|
|
Iirc binary updates are only between release versions, not beta or RCs. You can easily source upgrade though, it should be well documented in the handbook. A few makes and mergasters and a reboot.
|
|
#
?
Nov 28, 2012 18:44
|
|
|
falz posted:Iirc binary updates are only between release versions, not beta or RCs. You can easily source upgrade though, it should be well documented in the handbook. A few makes and mergasters and a reboot. I believe it is releases and RCs only [1]
|
|
#
?
Nov 28, 2012 18:50
|
|
|
Well then there you go. Easy enough to do it either way really.
|
|
#
?
Nov 28, 2012 18:55
|
|
|
falz posted:Well then there you go. Easy enough to do it either way really. Either way is easy? Compiling from source has been an annoying chore so far. I've had to do it for anything that wasn't available via pkgng or pkg_install, or anything that didn't have an option I needed in its pre-compiled package (ADS support in Samba, for example). Upgrading the system from source means I'll be bombarded with dozens of build option prompts and then watch text scroll by for hours. It would be quicker to just wipe the drive and install 9.1-RELEASE from floppies.
|
|
#
?
Nov 28, 2012 22:34
|
|
|
Upgrading only updates the base OS, not ports so there are no build options at all. Here's my go to list of steps:code:
|
|
#
?
Nov 28, 2012 23:27
|
|
|
Xenomorph posted:Would an upgrade from FreeBSD 9.1 RC3 to 9.1-RELEASE be a direct (and quick) binary upgrade, or is it some sort of "make world" process where I have to watch the system compile thousands of binaries? If you're ever running abnormal version (say, you built 9-STABLE between 9.0 and 9.1, or runnig a -PRERELEASE) you can cheat the system by faking your version. If you claim to be 9.0-RELEASE and tell it you want to upgrade to 9.1-RELEASE you might download/replace more binaries than necessary but it certainly will work. code:feld fucked around with this message at 02:44 on Nov 29, 2012 |
|
#
?
Nov 29, 2012 02:32
|
|
|
falz posted:The only thing that takes a little while of human time is mergemaster and telling it to take the new base system file (don't do this for your passwd/group files). Use this for your /etc/mergemaster.rc to save some headaches: code:
|
|
#
?
Nov 29, 2012 02:34
|
|
|
I'm trying to install x11 from ports, and I'm getting an error near the end. What exactly is the problem? Here's the end of the output. Sorry for the wall of text but I'm not sure what's important and what isn't.code:icantfindaname fucked around with this message at 20:53 on Dec 2, 2012 |
|
#
?
Dec 2, 2012 20:50
|
|
|
I don't know how to help with your problem, but if you don't need custom compilation flags you can try installing the package. pkg_add -r <whatever you were trying to build>
|
|
#
?
Dec 3, 2012 00:25
|
|
|
You don't have python installed (somehow)
|
|
#
?
Dec 3, 2012 00:42
|
|
|
feld posted:You don't have python installed (somehow) Sure he does (2.7), he just doesn't have the source files in the proper place (or wherever the config wants them) it looks like.
|
|
#
?
Dec 3, 2012 00:57
|
|
|
LooseChanj posted:Sure he does (2.7), he just doesn't have the source files in the proper place (or wherever the config wants them) it looks like. You've probably figured out I'm totally incompetent by now, but how exactly am I supposed to fix this? Where are the python source files supposed to be exactly? Isn't ports supposed to download all the source files from the internet? Where is the config script located so I can look at it and see what it wants? icantfindaname fucked around with this message at 01:21 on Dec 3, 2012 |
|
#
?
Dec 3, 2012 01:12
|
|
|
Go to /usr/ports/lang/python27 and delete the known configuration with "make rmconfig". Then reinstall it with "make install clean".
|
|
#
?
Dec 3, 2012 01:28
|
|
|
Well, that did it. X is now up and running. Thanks for the help.
|
|
#
?
Dec 3, 2012 02:00
|
|
|
LooseChanj posted:Sure he does (2.7), he just doesn't have the source files in the proper place (or wherever the config wants them) it looks like. Right, his installation of python was incomplete/broken. There's no way on FreeBSD to install python from ports and not get the headers. feld fucked around with this message at 14:37 on Dec 3, 2012 |
|
#
?
Dec 3, 2012 14:32
|
|
|
Anyone know what is going on inside the FreeBSD world? pkgng repositories were wiped a few days ago: http://lists.freebsd.org/pipermail/freebsd-ports/2012-November/079711.html Our documentation suddenly became invalid since we were trying to stick with "pkg install" for a much software as possible (to keep it consistent with our "apt-get install" and "yum install" systems). On our 9.0 and 9.1 test systems, compiling the many, many packages from ports is the only way to test software now. - Does anyone know when the repositories will be back? Regarding the security issues, there hasn't been an update in almost two weeks. They had been updating every few days: http://www.freebsd.org/news/2012-compromise.html - Does anyone know if there is anything more to report on this or the release of 9.1? Some say that 9.1 is close: http://forums.freebsd.org/showthread.php?t=35688 But since then I've only noticed the pkgng repositories have had their contents deleted. - Is there somewhere to check to see what the status of 9.1 is?
|
|
#
?
Dec 11, 2012 00:09
|
|
|
Xenomorph posted:Anyone know what is going on inside the FreeBSD world? You can check the 9.1 branch in the svn repo but as far as I know it's just a matter of creating the release media and building packages. pkgng packes will come after that and probably after the release. I'd look into a poudriere setup for building packages because as it is mentioned in the links you posted, the freebsd pkgng infrastructure is in beta and is liable to be wiped at any moment.
|
|
#
?
Dec 11, 2012 01:56
|
|
|
It's up.  Edit, better link: ftp://ftp.freebsd.org/pub/FreeBSD/releases/ISO-IMAGES/9.1/ Xenomorph fucked around with this message at 16:09 on Dec 11, 2012 |
|
#
?
Dec 11, 2012 15:39
|
|
|
Very exciting! First the Samba 4.0 release, now 9.1 bits are beginning to appear. Just waiting for 9.1-RELEASE to hit freebsd-update...
|
|
#
?
Dec 11, 2012 23:44
|
|
|
When can we expect it to hit freebsd-update? I don't think I'll bother upgrading any ports til it's out. e: woohoo! Nam Taf fucked around with this message at 15:32 on Dec 12, 2012 |
|
#
?
Dec 12, 2012 14:28
|
|
|
It just appeared on update3/4/5.freebsd.org! Edit, updating now... # freebsd-update upgrade -r 9.1 Nice. I killed everything. pkg had its database of installed stuff, but after updating, I had another database (like things were installed via pkg_add again). "pkg2ng" just told me the database was corrupt and could not be converted. "pkg_info" had the newer versions, "pkg info" had the older versions. code:No biggie. I figured I could just deleted stuff in both databases (pkg_delete -a and pkg delete -a), then reinstall. Well, except for the pkgng repositories are still empty... And they don't have the 9.1 repositories up for pkg_add. I didn't realize this until I blew away the local installs. So I ended up compiling all my stuff from ports. It took a while, but when it finished I rebooted and things were back to normal. Linux compatibility & backup program (Retrospect), LDAP/kerberos authentication, Samba & winbind, etc. Xenomorph fucked around with this message at 23:03 on Dec 12, 2012 |
|
#
?
Dec 12, 2012 15:26
|
|
|
Xenomorph posted:It just appeared on update3/4/5.freebsd.org! I probably should have known this and been ready, but upgrading to 9.1 from 9.0 wiped out all the "state" in transmission-daemon. All the BSD ISOs I was helping seed have to be added back manually and re-verified. BSD is super easy to admin but I always forget the little things since I don't generally have to do anything TO the box besides use it 99.9% of the time.
|
|
#
?
Dec 12, 2012 22:59
|
|
|
Is it possible to boot a FreeBSD system from a USB stick and have it check for rootkits? I recall there was some tool that would scan installed package MD5's and such, can that be run from a USB stick against the host's attached drive? What other options are there?
|
|
#
?
Dec 15, 2012 22:08
|
|
|
Ninja Rope posted:Is it possible to boot a FreeBSD system from a USB stick and have it check for rootkits? I recall there was some tool that would scan installed package MD5's and such, can that be run from a USB stick against the host's attached drive? What other options are there? chkrootkit and rkunter both have FreeBSD ports, so I'd start there. Use dd to burn the memstick image to your memory stick, boot into that and then escape to a real shell and install both of those from ports/packages (do not use pkg add as the beta pkgng package repository provided by FreeBSD is currently not populated with anything significant). rkhunter does take perl, which does take a bit of time to build, so start with the other one if you don't want to use packages or build perl.
|
|
#
?
Dec 17, 2012 07:25
|
|
|
I had been waiting for the 9.1-release binaries to go up (so I don't have to compile everything I wanted to update/install from my 9.1-RC3 install). However, I just noticed this thread: http://forums.freebsd.org/showthread.php?t=36339 Is it worth it for me to set PACKAGESITE to packages-9-stable (ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-9-stable/Latest) to ensure my server stays up to date?
|
|
#
?
Dec 19, 2012 18:01
|
|
|
Xenomorph posted:I had been waiting for the 9.1-release binaries to go up (so I don't have to compile everything I wanted to update/install from my 9.1-RC3 install). However, I just noticed this thread: Yes, the release packages are never updated, even for security updates. The stable package branch will also get new packages added to it as they are added to the ports tree.
|
|
#
?
Dec 20, 2012 02:43
|
|
|
hifi posted:Yes, the release packages are never updated, even for security updates. The stable package branch will also get new packages added to it as they are added to the ports tree. Where's the best place to set PACKAGESITE, so it's system-wide?
|
|
#
?
Dec 20, 2012 12:49
|
|
|
Xenomorph posted:Where's the best place to set PACKAGESITE, so it's system-wide? Your root .cshrc  . With pkgng you get /usr/local/etc/pkg.conf though, but don't use that until they actually make packages for it (keep an eye on http://pkgbeta.freebsd.org).
|
|
#
?
Dec 20, 2012 13:29
|
|
|
|
| # ? May 29, 2024 15:30 |
|
|
hifi posted:Your root .cshrc pkg, you say? - Since I'm trying to get a server going for department-wide use in a way that my assistant can administer the thing when I'm not here, I've been trying to document everything I do; all my docs started with pkg_add. - Then I read about the advantages of pkg, and I updated everything for use with it. I used the pkg2ng tool and then updated my docs to use just pkg. - Then when updating from 9.1-RC3 to 9.1-RELEASE, the install somehow added a bunch of packages to the old database pkg_add uses. "pkg_version" and "pkg info" listed two sets of installed packages, with different versions of many things. The "pkg2ng" command would not work. I just got message after message like "the package info for package 'apache22-2.2.23_3' is corrupt" - I removed all installed packages/ports and tried to start fresh again with pkg, but then the pkgbeta site was emptied out, so I couldn't use that. - I tried to fall back to pkg_add, but the 9.1-RELEASE binaries still aren't out. - I re-installed all my stuff with ports / portmaster and updated my docs to use that. - I then read I should be using 9-stable with pkg_add if I want to avoid compiling stuff but still get updates. - And now you're saying I should wait for pkg to get updated. :/ I guess I picked a weird time to get into FreeBSD.
|
|
#
?
Dec 20, 2012 15:10
|
|