|
GregNorc posted:Ok, so I just got a Thinkpad X201, and I'd like to run FreeBSD on it. What image did you use? The memstick .img or a CD/DVD .iso? Also, 7.x or 8.0? I know unetbootin has some quirks, try using https://launchpad.net/win32-image-writer/+download If it's not booting and you have your BIOS setup right, than it's just an issue with the USB stick you made being bootable or written right. It can be tricky the first few times you do it.
|
#
?
Apr 14, 2010 02:20
|
|
|
|
| # ? May 28, 2024 15:36 |
|
|
Did you try to dd the memstick image as explained in the release announcement?code:code:
|
|
#
?
Apr 14, 2010 13:23
|
|
|
falz posted:Did you try to dd the memstick image as explained in the release announcement? Thanks, I'm guessing this is the issue...I used the CD .img and not the memory stick image. However, I can create it on my main computer, which runs OSX, I just had mentioned windows since unetbootin has no OSX version. Right now I used "diskutil list" to find the approriate hard drive in /dev then ran "dd if=~/Documents/Downloads/8.0-RELEASE-i386-memstick.img of=/dev/disk2" It'd be nice to see a progress bar or have some sort of way of verifying it worked though, the first time it booted to a black screen, so I think I removed the USB drive too early. I'm gonna also try just writing the memstick image with unetbootin if this method fails. So yeah, if anyone has any ideas for verifying the image wrote correctly that'd be helpful, but I think this should solve the big issue.
|
|
#
?
Apr 14, 2010 15:50
|
|
|
GregNorc posted:Thanks, I'm guessing this is the issue...I used the CD .img and not the memory stick image. dd should terminate and drop you back to the prompt when its finished. If you didnt specify a blocksize using the bs= option then try something like this: "dd if=~/Documents/Downloads/8.0-RELEASE-i386-memstick.img of=/dev/disk2 bs=4K" Should speed things up a bit.
|
|
#
?
Apr 14, 2010 18:48
|
|
|
I have a really weird issue on an OpenBSD server which I'd love an outside take on. OpenBSD 4.5 running on a small Soekris 48xx, serving up stuff with Apache 1.3.29 running quite standard in its little chroot, except for a few virtualhosts (files.example.com, images.example.com and the like.) Anyway, after having served thousands of files in sizes from a few bytes to DVD image size (~4 gigs) there's now suddenly two ~4 gb zip files it refuses to send more than about 200 megs of. The files transfer fine over other methods (scp). It's the same (wrong) size every time. Copying the file to a different dir yields the same results. Other (big) files work fine. There's plenty of free space on both ends. Problem persists across Firefox, curl and wget. I'm at my wit's end here, and I can't get Google to turn up nothing.
|
|
#
?
Apr 19, 2010 07:24
|
|
|
There was change in 4.6 related to serving large files: http://www.openbsd.org/plus46.html, search that page for 'apache' It may or may not be the problem. I'd start by upgrading. 4.6 has been out for a while and 4.7 is coming soon. Upgrading is a lot easier than it used to be, just take a look at the FAQ for instructions: http://www.openbsd.org/faq/upgrade46.html If that doesn't work then you could try a different http server from ports such as apache2, lighttpd, or nginx.
|
|
#
?
Apr 19, 2010 07:48
|
|
|
I too blame apache 1.x, I had a similar issue on freebsd once. All my problems were solved by apache 2.x.
|
|
#
?
Apr 19, 2010 08:37
|
|
|
That seems to be a very likely answer. Files under 2 gigs work fine, files over work weird. I'll see about upgrading, usually I've just reinstalled every year or so. Thanks! Fake edit: In fact, look at these file sizes: file1 real size: 4504414950 transferred size: 209447654 difference: 4294967296 = 2^32 file2 real size: 4481562329 transferred size: 186595033 difference: 4294967296 = 2^32 Must be the 2GB bug.
|
|
#
?
Apr 19, 2010 12:12
|
|
|
It used to be a well-known fact that Apache 1.x was not reliable for large file transfers. It wasn't just a 2GB limit. It was simply less reliable the larger the file.
|
|
#
?
Apr 24, 2010 21:06
|
|
|
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?
|
|
#
?
May 11, 2010 13:42
|
|
|
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. You can create multiple pflog interfaces and then have rules log to specific interfaces with "log to pflog1" so that it's only playing sound on the events you want. I'd probably make something with Python that used subprocess to connect to the stdin and stdout of a tcpdump process listening to pflog1. Do you want to play sounds based on the packet data or specific sounds for specific packets? Playing specific sounds would be easy enough. I'm not sure how you would turn a packet into sound, it doesn't seem like there's enough data unless you were converting byte values into tones like 1 = 100Hz, 2 = 200Hz, etc. It looks like you could use Csound for that unless there's an easier way.
|
|
#
?
May 11, 2010 17:27
|
|
|
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. Just submit the IP's which are connecting to porn sites to https://oh Somebody fucked around with this message at 13:12 on May 13, 2010 |
|
#
?
May 11, 2010 17:58
|
|
|
Cpt.Wacky posted:You can create multiple pflog interfaces and then have rules log to specific interfaces with "log to pflog1" so that it's only playing sound on the events you want. I'd probably make something with Python that used subprocess to connect to the stdin and stdout of a tcpdump process listening to pflog1. That could work, though for some reason I was under the impression that pf could execute shell scripts on a per-rule basis, which would be easy enough to use to then pipe arbitrary .wav or .au files to /dev/audio - this could be fun as you could set up random background noise with random animal squeaks and squawks signifying different events, or hell, you could set yourself up to sound like NORAD on a bad day with careful selection of sounds and rules. My Python knowledge is non-existent (I work with PHP) but I'm tempted to learn - would this be a reasonable type of project to approach as a beginner? Where should I start? Bob Morales posted:Just submit the IP's which are connecting to porn sites to [redacted] Oh this is great! I often find myself using whatismyip.com as a handy shortcut while at clients, and I can see myself not thinking and using this instead now, which should go down pretty well... Somebody fucked around with this message at 13:12 on May 13, 2010 |
|
#
?
May 11, 2010 20:22
|
|
|
Masked Pumpkin posted:That could work, though for some reason I was under the impression that pf could execute shell scripts on a per-rule basis, which would be easy enough to use to then pipe arbitrary .wav or .au files to /dev/audio - this could be fun as you could set up random background noise with random animal squeaks and squawks signifying different events, or hell, you could set yourself up to sound like NORAD on a bad day with careful selection of sounds and rules. That's not a feature in pf on OpenBSD that I'm aware of. Maybe you're thinking of a Linux firewall? I'd start with some simple Python to get a feel for the syntax and features first. I'm doing to opposite, doing PHP when I've primarily done Python, and I'm having a hell of a time with stupid stuff like forgetting semi-colons. Dive Into Python and The Python Tutorial are both good ways to get up to speed. Then you can try something more complicated like this project. I'd give it a shot myself right now but I've got too many other projects going at the moment.
|
|
#
?
May 12, 2010 00:06
|
|
|
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.
|
|
#
?
May 12, 2010 01:39
|
|
|
OpenBSD 4.7 was officially released today. If you pre-ordered the CDs then you already had it 2 weeks ago. If you haven't tried OpenBSD in the last year or two, you should give it another look. The installer is still text-based, but has been improved to be simpler and faster. Upgrading is much easier now with sysmerge (although the upgrade instructions are still a bit confusing). There aren't a lot of huge new features in this release, just the usual steady improvements. Here's a summary but see the link above for more details.
Check the website for FTP mirrors. You can install via FTP by burning a small boot CD image, or if you insist there is now a 227 MB install CD image available.
|
|
#
?
May 19, 2010 16:33
|
|
|
Cpt.Wacky posted:OpenBSD 4.7 was officially released today. If you pre-ordered the CDs then you already had it 2 weeks ago. This caught my eye: New athn(4) driver for Atheros IEEE 802.11a/g/n wireless network devices I haven't run Open as a desktop environment for years, but this might be worth checking out on my laptop 
|
|
#
?
May 19, 2010 16:45
|
|
|
Dijkstracula posted:This caught my eye: http://www.openbsd.org/cgi-bin/man.cgi?query=athn&apropos=0&sektion=0&manpath=OpenBSD+Current&arch=i386&format=html code:Another thing that was introduced in the last few releases is the aucat audio server along with improved audio support, especially for the Azalia stuff. All the software in the ports tree has already been patched to support the aucat server, so it "just works" when you run aucat -l or start it at boot.
|
|
#
?
May 19, 2010 16:58
|
|
|
What is the preferred DNS server? Bind? djbdns? Something else? Also, is there a recommended Idiot's Guide to DNS on FreeBSD tutorial website or book? I know almost nothing about DNS and am going to dive in.
|
|
#
?
May 25, 2010 13:26
|
|
|
SmirkingJack posted:What is the preferred DNS server? Bind? djbdns? Something else? Also, is there a recommended Idiot's Guide to DNS on FreeBSD tutorial website or book? I know almost nothing about DNS and am going to dive in. http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/network-dns.html
|
|
#
?
May 25, 2010 13:40
|
|
|
Bob Morales posted:http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/network-dns.html Ah, yeah, I should have mentioned I saw that already.
|
|
#
?
May 25, 2010 18:59
|
|
|
SmirkingJack posted:What is the preferred DNS server? Bind? djbdns? Something else? Also, is there a recommended Idiot's Guide to DNS on FreeBSD tutorial website or book? I know almost nothing about DNS and am going to dive in. Bind is pretty much standard. What does that handbook section not explain? What do you want to do with DNS?
|
|
#
?
May 25, 2010 19:06
|
|
|
Cpt.Wacky posted:Bind is pretty much standard. What does that handbook section not explain? What do you want to do with DNS? I was mostly looking for software suggestions. I didn't look at the handbook too closely since it looked like a general DNS guide and more of a Bind how-to, but I went back and set it up. As it turns out, it was far less scary and complicated than I thought it would be. Thanks, everyone, for the suggestions!
|
|
#
?
May 28, 2010 15:08
|
|
|
SmirkingJack posted:I was mostly looking for software suggestions. I didn't look at the handbook too closely since it looked like a general DNS guide and more of a Bind how-to, but I went back and set it up. As it turns out, it was far less scary and complicated than I thought it would be. Thanks, everyone, for the suggestions! Thats because *NIX and Bind ARE the general use DNS 
|
|
#
?
May 28, 2010 16:40
|
|
|
Has anyone had any problems with pkg_add randomly hanging in OpenBSD? It seems to run fine while retrieving the first couple dependencies but then just hangs in the middle of pulling in any successive ones. I've tried letting it sit now for over 10 hours and it's still stuck at 0% on opensp-1.5.2. This seems to happen regardless of my specifying an ftp or http mirror in the PKG_PATH and I have had no connectivity problems to speak of.
|
|
#
?
Jul 1, 2010 18:58
|
|
|
TheShitWagon posted:Has anyone had any problems with pkg_add randomly hanging in OpenBSD? It seems to run fine while retrieving the first couple dependencies but then just hangs in the middle of pulling in any successive ones. I've tried letting it sit now for over 10 hours and it's still stuck at 0% on opensp-1.5.2. This seems to happen regardless of my specifying an ftp or http mirror in the PKG_PATH and I have had no connectivity problems to speak of. Are you trying to update packages? I had problems with it not finding stuff, so I just bit the bullet and reinstalled. Everything worked great after.
|
|
#
?
Jul 1, 2010 19:42
|
|
|
TheShitWagon posted:Has anyone had any problems with pkg_add randomly hanging in OpenBSD? It seems to run fine while retrieving the first couple dependencies but then just hangs in the middle of pulling in any successive ones. I've tried letting it sit now for over 10 hours and it's still stuck at 0% on opensp-1.5.2. This seems to happen regardless of my specifying an ftp or http mirror in the PKG_PATH and I have had no connectivity problems to speak of. -v Turn on verbose output. Several -v turn on more verbose output. By default, pkg_add is almost completely silent, but it reacts to keyboard status requests (see stty(1)). -v turns on basic messages, -vv adds relevant system operations, -vvv shows most internal computations apart from individual file/directory addi- tions, -vvvv also shows dependencies adjustments, and -vvvvv shows everything. Run it with one of those options and see if anything looks out of the ordinary.
|
|
#
?
Jul 1, 2010 20:02
|
|
|
I ran it at the most verbose level but I didn't really see anything out of the ordinary. It just ran for a few minutes and then hung on extracting some file (not a specific file, just a random file in the sequence).
|
|
#
?
Jul 1, 2010 21:35
|
|
|
TheShitWagon posted:I ran it at the most verbose level but I didn't really see anything out of the ordinary. It just ran for a few minutes and then hung on extracting some file (not a specific file, just a random file in the sequence). Are you running out of disks space or getting disk i/o errors or anything like that?
|
|
#
?
Jul 1, 2010 21:42
|
|
|
Apparently /usr is at 105% capacity. I wouldn't have thought to check since it wasn't giving me errors of any kind.
|
|
#
?
Jul 1, 2010 22:01
|
|
|
TheShitWagon posted:Apparently /usr is at 105% capacity. I wouldn't have thought to check since it wasn't giving me errors of any kind. That might be it. OpenBSD never makes /usr big enough
|
|
#
?
Jul 1, 2010 22:49
|
|
|
Bob Morales posted:That might be it. OpenBSD never makes /usr big enough I've never used the recommended partitions setup gives you, but how the hell is this possible unless you're using a drat small (by today's standards) drive?
|
|
#
?
Jul 1, 2010 23:01
|
|
|
The drive is only 20GB in size (VMWare drive). It was doing pretty well until I decided to try and install XFCE. I'll just make a bigger disk and reinstall OpenBSD with a tweaked /usr partition.
|
|
#
?
Jul 1, 2010 23:12
|
|
|
I wouldn't even bother partitioning in that scenario.
|
|
#
?
Jul 1, 2010 23:24
|
|
|
LooseChanj posted:I've never used the recommended partitions setup gives you, but how the hell is this possible unless you're using a drat small (by today's standards) drive? I wasn't paying attention to an install once on 250GB system, and the autodefaults still only gave me something like 1 or 1.5GB. It starting giving me errors when I built something that started building GNOME. ended up re-building the server the next day with 10GB instead. It was just a test server or else I would have stole some space from home and left it unallocated for poo poo like this in the future.
|
|
#
?
Jul 1, 2010 23:45
|
|
|
Bob Morales posted:I wasn't paying attention to an install once on 250GB system, and the autodefaults still only gave me something like 1 or 1.5GB. It starting giving me errors when I built something that started building GNOME. ended up re-building the server the next day with 10GB instead. The auto-partitioning isn't really meant for users who are compiling ports, especially huge monsters like GNOME, KDE, OpenOffice, etc. The expectation is that you'll use the packages which are always available for every release (unless you need an oddball flavor). You could be building -stable ports, but they just started doing those recently, and for that you should use a dedicated build box which is building -stable releases too. I use the auto-partitions on regular machines, and dump everything into a single huge root partition on the machines where I expect to build releases and ports. I have seen an occasional problem with pkg_add stalling, but it's usually an unreliable mirror, a bad PKG_PATH (trying to use packages from the previous version after upgrading), or a botched upgrade (using the wrong file sets by accident).
|
|
#
?
Jul 2, 2010 00:19
|
|
|
I took a machine down to compile the kernel (which took ~ 20 minutes) and then build the userland, and that took another 90 minutes. If it were an important machine, would it be better to build on another box and copy everything over? ie build a release?
|
|
#
?
Jul 2, 2010 01:55
|
|
|
Im trying to run my freebsd 8 box as a virtualbox host, after loving about with ports for a few days trying to get everything to compile remined me of red hat linux dependency fuckery. Anyhow, running bridged interface with em pci-e card nukes network performance for the machine as soon as the em device is put in to promiscious mode. Even if i close virtualbox and the card is taken out of promiscious mode the device still runs slow. Any thoughts about this?
|
|
#
?
Jul 2, 2010 09:26
|
|
|
How well does the Linuxulator work in FreeBSD 8/CURRENT? For getting things like Google Earth to work. And how up-to-date are the ports?
|
|
#
?
Jul 3, 2010 17:36
|
|
|
|
| # ? May 28, 2024 15:36 |
|
|
Bob Morales posted:I took a machine down to compile the kernel (which took ~ 20 minutes) and then build the userland, and that took another 90 minutes. Are you talking about OpenBSD? Building kernel and userland to get updates for -stable? I always build a release for each architecture on a non-production machine. It's much quicker to do an upgrade with the file sets from building a release than building the whole thing on each machine. You can do the in-place upgrade (easier for remote machines) or boot bsd.rd and use the upgrade option. The in-place upgrade can be quicker since you can copy the file sets over before you start the upgrade, so a slow network link won't slow down the upgrade process. The upgrade FAQ explains both methods.
|
|
#
?
Jul 3, 2010 20:35
|
|