The Ultimate BSD Thread™ - The Devil Wears a Neckbeard

The Something Awful Forums > Discussion > Serious Hardware/Software Crap > The Ultimate BSD Thread™ - The Devil Wears a Neckbeard

falz: Jan 29, 2005; 01100110 01100001 01101100 01111010

Combat Pretzel posted:

Is there a reason why there's still no 64bit NVidia driver?

Nvidia simply doesn't make them, not listed here. On a somewhat related subject, didn't AMD/ATI open up the specs to all of their video hardware 18ish months ago? I was under the impression that this would generally eventually result in good open free drivers for ATI GPU's. Anyone know the progress or status of this?

Edit: Also, read the mailing list thread at the bottom of that nvidia link, it directly addresses AMD64 issues on FreeBSD from Nvidia's perspective (and is 3 years old)

# ¿ Apr 26, 2009 17:38

Adbot: ADBOT LOVES YOU

# ¿ May 9, 2024 23:29

falz: Jan 29, 2005; 01100110 01100001 01101100 01111010

juggalol posted:

port 8043

Is FreeNAS's default gateway set? If not it would work locally but not from the internet. Also simply telnetting to the port from the outside is probably the easiest test.

# ¿ Apr 29, 2009 00:38

falz: Jan 29, 2005; 01100110 01100001 01101100 01111010

juggalol posted:

I can ping google.com from the FreeNAS box, so it's definitely getting out to the net.

Your defaultrouter line is fine. You pinging google confirms this. The only other thing I can think of, as someone else mentioned, is firewall rules on the FreeNAS to only permit the local subnet to connect to its admin interface.

# ¿ Apr 29, 2009 17:09

falz: Jan 29, 2005; 01100110 01100001 01101100 01111010

LooseChanj posted:

Dumped straight back to a shell prompt.

If the only (EE) is the one you listed earlier, it's likely your problem. It seems to indicate you're using the "nv" driver as well, you could try x11/nvidia-drver. You should also try to run x without an xorg.conf, it's quite good at auto detecting stuff.

# ¿ May 27, 2009 15:18

falz: Jan 29, 2005; 01100110 01100001 01101100 01111010

You probably want "make package-recursive" which will build the package for the port you want and packages for all of its dependencies. Ideally you would have a web server on the server you're making packages on and you can just "pkg_add -r http://server/Latest/package_name.tbz". You could also just somehow get the files to the other server and call the file directly.

The PACKAGESITE variable is looked at by default. If you change it to your server it will be looked at first and you could just use "pkg_add -r gnome" will work. If you really want to get in depth, use tinderbox.

# ¿ Sep 23, 2009 19:11

falz: Jan 29, 2005; 01100110 01100001 01101100 01111010

roadhead posted:

Anyone

code:

freebsd-update -r 8.0-RC2 upgrade

yet?

I'm doing that now on an 8.0-RC1 box that's my home/test server. This started life as 8.0 Beta1 and has been upgraded the 5 or so steps each time a new beta/RC came out. It's a SMB and WWW server that does various other things such as avimerge. No problems at any point at all

# ¿ Oct 30, 2009 15:12

falz: Jan 29, 2005; 01100110 01100001 01101100 01111010

porkface posted:

Smooth upgrade path from 4.5.2 here, right?

Can't tell if this is a joke post, but upgrades from 4 are not smooth. 5 and up are.

# ¿ Nov 25, 2009 15:04

falz: Jan 29, 2005; 01100110 01100001 01101100 01111010

jandrese posted:

Pretty simple. I think there are BSD tools for finding out what's already installed, but they're unnecessary. If you want to find out what ports you have, just cd to /var/db/pkg and do an ls. Each port is a directory in there.

While ls /var/db/pkg does work, pkg_info lists the packages with nice brief descriptions. Normally compiling from ports is best but he should be aware that pkg_add will install a precompiled port quickly. The negative part of this is that you cannot set configuration options and the binary port is likely to be slightly out of date.

# ¿ Apr 5, 2010 02:50

falz: Jan 29, 2005; 01100110 01100001 01101100 01111010

Did you try to dd the memstick image as explained in the release announcement?

code:

dd if=8.0-RELEASE-amd64-memstick.img of=/dev/da0 bs=10240 conv=sync

There's a dd for windows and someone wrote specific instructions on how to do this on windows for FreeBSD here. Once you find the partition that the USB disk is it's:

code:

dd if=8.0-RC2-amd64-memstick.img of=\\?\Device\Harddisk1\Partition0 bs=10240 --progress

# ¿ Apr 14, 2010 13:23

falz: Jan 29, 2005; 01100110 01100001 01101100 01111010

Masked Pumpkin posted:

I have an OpenBSD box running pf on my network, and it's been a great success. It occurred to me that it might be fun to redirect sound from pflog (or at least tcpdump) to /dev/audio, but this is failing - I think because the output is not in any format recognisable to the device and/or because it's a continuous stream. I don't particularly care about hearing any and every thing that goes through the network, but would be interested in having some pf rules output a random .au file to the device.

While this can be done with a cron job that runs through the pf log periodically, I'm sure there's a better way to do this, but have no idea what that might be - any ideas?

This is what peep is for.

# ¿ May 12, 2010 01:39

falz: Jan 29, 2005; 01100110 01100001 01101100 01111010

`freebsd-update` can only update from RELEASE kernels. Use the traditional compiled method, which is in the handbook. We've updated several boxes at work, no issues as usual. In short:

code:

csup stable-supfile
cd /usr/src
make clean
make buildworld
make buildkernel
make installkernel
mergemaster -p
make installworld
mergemaster -U
reboot

falz fucked around with this message at 19:26 on Jul 23, 2010

# ¿ Jul 23, 2010 19:23

falz: Jan 29, 2005; 01100110 01100001 01101100 01111010

A records will be followed for mail delivery if no MX record exists. If I were to send mail to foo@w1.acme.com and there's no MX record, mail servers would send it to that server whose A is w1.acme.com.

Is it running the default MTA (sendmail) or something else? Assuming the mail you're concerned with is foo@acme.com, something in yourconfiguration considers acme.com locally. look in /etc/mail if it's sendmail.

One way to force it would be to create an entry (and the file) /etc/mail/mailertable that looks like:

code:

acme.com smtp:exchange.acme.com

then run:

code:

makemap hash /etc/mail/mailertable < /etc/mail/mailertable

# ¿ Dec 6, 2010 23:59

falz: Jan 29, 2005; 01100110 01100001 01101100 01111010

Curious of anyone's experience using OpenBSD as a router, specifically with OpenBGPD and OpenOSPFD? In a lab VM environment I'm testing full BGP feeds and convergence times, things are much faster than on the Cisco hardware I have to test on due to Cisco general purpose CPU speeds being slow. Target hardware to be used would be generic Dell servers with Broadcom and/or Intel NICs, or possibly these Lanner network appliances which according to their sales engineers will run OpenBSD just fine and are less expensive than servers when you consider they have dedicated Intel NICs for each port.

There is info on this page that has network tweaks that apparently help a lot as well.

Any feedback appreciated, this would be for routing ~100-~300mbps and dealing with full BGP feeds.

Edit: I couldn't find any config examples for BGP filters other than the man page so I've been putting config examples and notes on this page if it helps anyone out.

falz fucked around with this message at 16:55 on Apr 30, 2011

# ¿ Apr 30, 2011 16:51

falz: Jan 29, 2005; 01100110 01100001 01101100 01111010

I have actually posted to misc@ a few times in the last week with great success- an OpenBGPD dev wrote a patch for some buggy behavior which was wonderful and very promising if my org uses it in production.

I posted here in hopes of avoiding bias by those who are openbsd zealots. If i don't recieve any feedback here i will likely post this question in misc@.

# ¿ May 1, 2011 17:41

falz: Jan 29, 2005; 01100110 01100001 01101100 01111010

If you still need anything:
* http://falz.net/static/sa/coretemp.ko-i386
* http://falz.net/static/sa/coretemp.ko-amd64

# ¿ Aug 4, 2011 14:55

falz: Jan 29, 2005; 01100110 01100001 01101100 01111010

Masked Pumpkin posted:

The server only has one network interface, so simply using different metrics in routing is not an option.

Having one interface shouldn't matter. Your script should probably just set the metric on the route in question, not completely remove it.

# ¿ Oct 12, 2011 14:23

falz: Jan 29, 2005; 01100110 01100001 01101100 01111010

If you actually use telnet to admin your box your passwords would have been sniffed anyway.

# ¿ Dec 24, 2011 03:58

falz: Jan 29, 2005; 01100110 01100001 01101100 01111010

Good thing that quote was posted over 3 weeks ago!

# ¿ Dec 24, 2011 19:01

falz: Jan 29, 2005; 01100110 01100001 01101100 01111010

Looks like 9.0 RELEASE was tagged in CVS so I decided to upgrade to it. All good so far, ipv6 config in rc.conf changed slightly but no big deal.

* What's New
* What's cooking for FreeBSD 9

# ¿ Jan 3, 2012 04:35

falz: Jan 29, 2005; 01100110 01100001 01101100 01111010

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: Jan 29, 2005; 01100110 01100001 01101100 01111010

Well then there you go. Easy enough to do it either way really.

# ¿ Nov 28, 2012 18:55

falz: Jan 29, 2005; 01100110 01100001 01101100 01111010

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:

grep -v \#  /usr/share/examples/cvsup/stable-supfile | grep -v ^$ > /root/stable-supfile
# edit /root/stable-supfile to set mirror

csup /root/stable-supfile
cd /usr/src
make clean
make buildworld
make buildkernel
make installkernel
cd /usr/src
mergemaster -p
make installworld
mergemaster -U

reboot

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).

# ¿ Nov 28, 2012 23:27

falz: Jan 29, 2005; 01100110 01100001 01101100 01111010

Don't build from source, use FreeBSD's package management system - ports.

short answer:

code:

pkg_add -r sudo

better/longer answer:

http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/ports-using.html

# ¿ Jan 12, 2013 02:28

falz: Jan 29, 2005; 01100110 01100001 01101100 01111010

Put something in /etc/apmd.conf that does:

code:

/etc/ntpd stop
/etc/ntpdate start
/etc/ntpd start

maybe something like this? the first exec was already in there

code:

apm_event STANDBYRESUME {
        exec "/etc/rc.resume apm standby";
        exec "/etc/ntpd stop";
        exec "/etc/ntpdate start";
        exec "/etc/ntpd start";
}

falz fucked around with this message at 18:17 on Feb 5, 2013

# ¿ Feb 5, 2013 18:13

Adbot: ADBOT LOVES YOU

# ¿ May 9, 2024 23:29

falz: Jan 29, 2005; 01100110 01100001 01101100 01111010

Look ma, more BSDs! http://edgebsd.org/

# ¿ Aug 22, 2013 14:44

The Something Awful Forums > Discussion > Serious Hardware/Software Crap > The Ultimate BSD Thread™ - The Devil Wears a Neckbeard