Re: panic on fresh snap (was: [ppc] Daily digest, Issue 573 (1 messages))
See [EMAIL PROTECTED] -p.
Re: acpi is working but halt -p is now working, why?
Jay Jesus Amorin wrote: im running openbsd 4.1-current on my laptop, acpi is working but halt -p is not working, it will just reboot instead of halt, WHY? here's my additional info: # sysctl -aA | grep acpi kern.timecounter.hardware=acpitimer0 kern.timecounter.choice=i8254(0) acpihpet0(1000) acpitimer0(1000) dummy(-100) hw.sensors.acpiac0.indicator0=On (power supply) hw.sensors.acpibat0.volt0=14.80 VDC (voltage) hw.sensors.acpibat0.volt1=12.54 VDC (current voltage) hw.sensors.acpibat0.amphour0=3.81 Ah (last full capacity) hw.sensors.acpibat0.amphour1=0.21 Ah (warning capacity) hw.sensors.acpibat0.amphour2=0.13 Ah (low capacity) hw.sensors.acpibat0.amphour3=3.42 Ah (remaining capacity), OK hw.sensors.acpibat0.raw0=2 (battery charging), OK hw.sensors.acpibat0.raw1=unknown (rate), UNKNOWN hw.sensors.acpitz0.temp0=51.05 degC (zone temperature) Although, it is APM, try: # sysctl machdep.apmhalt=1 -pachl
Re: opinion about pf rules?
On Fri, Mar 30, 2007 at 11:51:43AM +0200, Anze Povsic wrote:
> Hello!
>
> First of all i would like to say many many thanks to obsd comunity especially
> to obsd developers for realy great product
> i realy appreciate your work, now is a second time i pre-order cd-set just to
> support the project.
> but what i wrote this message is thath i would like to heard what you people
> think about the pf.conf i include in the mail
> those rules are on the gateway to protect machines on LAN.
> thanks to any comments and sorry for my english.
Okay, you asked for it... quite a bit of commentary, and my take on your
ruleset, below.
> # $OpenBSD: pf.conf,v 1.31 2006/01/30 12:20:31 camield Exp $
> #
> # See pf.conf(5) and /usr/share/pf for syntax and examples.
> # Remember to set net.inet.ip.forwarding=1 and/or net.inet6.ip6.forwarding=1
> # in /etc/sysctl.conf if packets are to be forwarded between interfaces.
>
> ext_if="tun0"
tun0? Are you sure?
> int_if="fxp0"
>
> NoRoute="{0.0.0.0/8, 169.254.0.0/16, 192.0.2.0/24, 204.152.64.0/23,
> 224.0.0.0/3, 127.0.0.1/8, 192.168.0.0/16, 172.16.0.0/12, 10.0.0.0/8,
> 255.255.255.255/32 }"
/32 is not required. I don't think blocking unroutable nets is terribly
useful.
> OutTCP="{1494, 5999, http, https, smtp, pop3, whois, domain, ssh, ftp,
> ftp-data, auth, ntp, nntp}"
> OutUDP="{1604, ntp, domain}"
> Bad_ports="5,69,135,137,138,139,445,524,548,666,1080,1433,1434,2283,2535,3127,3128,3410,8866,9898,4899,6129,12345,6667,33270,60001,54321,65289,2407,1711,31337,1,65506,2745"
Enumerating bad ports isn't going to help you... see below.
> set loginterface $ext_if
That is not usually required, but otherwise okay.
> set optimization aggressive
If you don't know that you need this, don't use it. Dropping idle
sessions is not a good thing.
> set block-policy drop
> set state-policy if-bound
if-bound should not be used unless necessary. It makes things less
standard and more complex.
> scrub in on { lo $ext_if, $int_if } all fragment reassemble random-id
> scrub out on { lo $ext_if, $int_if } all fragment reassemble random-id
You might want to use
scrub on { $ext_if $int_if } fragment reassemble random-id \
reassemble-tcp
set skip on lo0
instead; it's less verbose, adds TCP normalization (which should work
perfectly in 99.9% of all cases), and bypasses pf for traffic on the
loopback interface.
> nat-anchor "ftp-proxy/*"
> rdr-anchor "ftp-proxy/*"
> nat on $ext_if from $int_if:network to any -> ($ext_if:0) static-port
Do you need the static-port? You might want to experiment with using it
only for whatever truly needs it - I don't know what pf does when it
handles multiple NAT'ed connections from the same source port in this
case. You should probably find out.
> rdr on $ext_if proto tcp from any to any port smtp -> 127.0.0.1 port spamd
This will redirect *all* incoming traffic to spamd; effectively, your
host is a tarpit for mail servers. Is that the intention? If not, read
spamd(8).
> rdr on $int_if proto tcp from any to any port ftp -> 127.0.0.1 port 8021
> rdr on $int_if proto tcp from any to any port www -> 127.0.0.1 port 3128
Make sure whatever HTTP proxy you use is properly secured.
> block in on $ext_if all
> block out on $ext_if all
More concisely, 'block on $ext_if'. Note that you allow *all* traffic
out! It's usually best to start with 'block all'.
> anchor "ftp-proxy/*"
>
> block return-rst out log on $ext_if proto tcp all
> block return-rst in log on $ext_if proto tcp all
> block return-icmp out log on $ext_if proto udp all
> block return-icmp in log on $ext_if proto udp all
Huh? That's more properly spelled
'block return log on $ext_if'
which also handles non-tcp, non-udp traffic. Again, just block
everything.
> antispoof for { lo, $ext_if, $int_if } inet
That doesn't make sense; you want quick, at least, and there's no reason
to limit this to inet.
> block in inet6 all
> block out inet6 all
>
> pass in on lo all
> pass out on lo all
This is best replaced by 'set skip on lo0'.
> block in log on $ext_if inet proto tcp from any to any flags /WEUAPRS
> block in log on $ext_if inet proto tcp from any to any flags FUP/FUP
> block in log on $ext_if inet proto tcp from any to any flags SR/SR
> block in log on $ext_if inet proto tcp from any to any flags SF/SFRA
> block in log on $ext_if inet proto tcp from any to any flags UAPRSF/UAPRSF
> block in log on $ext_if inet proto tcp from any to any flags WEUAPRS/WEUAPRS
> block in log on $ext_if inet proto tcp from any to any flags F/SFRA
> block in log on $ext_if inet proto tcp from any to any flags U/SFRAU
> block in log on $ext_if inet proto tcp from any to any flags FPU/SFRAUP
Huh? pf knows how to normalize traffic, that's what scrub is for.
All in all, I'd recommend replacing everything up to now with:
ext_if="tun0"
int_if="fxp0"
OutTCP="{1494, 5999, http, https, smtp, pop3, whois, domain, ssh, ftp,
ftp-data, auth, ntp, nntp}"
OutUDP="{1604, ntp, domain}"
set loginterfa
Re: [OT] Re: Long WEP key
On Sat, Mar 31, 2007 at 03:03:06PM +1000, Sunnz wrote: > So both OpenVPN and Ipec are VPN? Which one is more secure? If I have > UNIX(like) OS only in my network which one can be used? Yes, they can both be used to implement VPNs. Most operating systems have some degree of support for IPsec, and OpenVPN runs on most OSes, as well. There are a lot of cruddy IPsec implementations out there, though, and it tends to be rather complicated. On the other hand, it should be faster than OpenVPN, and can be better tailored to one's needs. All in all, I might choose OpenVPN if it involved end users (lots of NAT, Windows, and other crappy stuff), would probably go for IPsec if only handling UNIXes that supported it (even if it's harder than OpenVPN to set up), and not even consider OpenVPN if I only needed to support OpenBSD. Joachim
Re: Is OpenBSD good/best for my 486?
On Fri, Mar 30, 2007 at 11:35:49PM -0400, Douglas Allan Tutty wrote: > Then there's aesthetics. I learn best by understanding. Since UNIX > culture was born on slow (by today's standards) machines, why not learn > in that mode to start? What steps would I skip if my machine is too > slow if I'm dedicated to learning on it and not trying to cut corners to > make it run faster? OpenBSD runs just fine on slower hardware; be prepared to take a while for certain things, and use the provided binary stuff instead of compiling your own whenever possible. Joachim
uvm_mapent_alloc: out of static map entries
on my not so busy i386 4.0-current web server I get "uvm_mapent_alloc: out of static map entries" ~ once every two days. The archives bear a wide range of suggestions, from tweaking kernel feature xy to not touching anything, because that's stupid. However, this message bothers me a bit and so I am seeking for advice how to track the problem down (if any). The machine runs apache with mod_gzip, openssl and php5 plus myqsql. I have set those up in a most default way, for mysql I've followed the guidelines on openbsdsupport.org. below you'll find output of vmstat -m, netstat -n and ps aux thanks, Stephan $ vmstat -m Memory statistics by bucket size Size In Use Free Requests HighWater Couldfree 16 9497 285415 2199511001280 83060 32 3563 108949 102837831 640 903052 64 4463 613294411422 320 338543 128 5238 9162 987939 160 7321 256 5185239 826192 80 18140 512 92443401313642 40 79758 1024 2241 516078151 201445813 2048 163 23 32751 10 11346 4096 30 32 87109 5 59289 8192 72 48770 5474 163845 0 1905 5 0 32768 33 0 1527 5 0 65536 10 0462 5 0 1310720 0864 5 0 2621440 0 1241 5 0 5242880 0 3584 5 0 Memory usage type by bucket size Size Type(s) 16 devbuf, pcb, routetbl, ifaddr, sysctl, UFS mount, sem, dirhash, in_multi, exec, xform_data, VM swap, UVM amap, UVM aobj, USB, USB device, temp 32 devbuf, pcb, routetbl, ifaddr, vnodes, UFS mount, sem, dirhash, proc, VFS cluster, ether_multi, xform_data, VM swap, UVM amap, USB, packet tags, temp 64 devbuf, pcb, routetbl, UFS mount, sem, dirhash, in_multi, pfkey data, UVM amap, UVM aobj, USB, NDP, temp 128 devbuf, routetbl, ifaddr, vnodes, dirhash, ttys, exec, inodedep, UVM amap, USB, USB device, ip6_options, NDP, temp 256 devbuf, routetbl, ifaddr, sysctl, ioctlops, vnodes, shm, VM map, sem, dirhash, file desc, proc, NFS srvsock, NFS daemon, newblk, UVM amap, USB, USB device, temp 512 devbuf, pcb, ifaddr, ioctlops, mount, UFS mount, shm, dirhash, file desc, ttys, exec, UVM amap, USB device, temp 1024 devbuf, ioctlops, namecache, UFS mount, file desc, proc, ttys, exec, UVM amap, UVM aobj, crypto data, temp 2048 devbuf, ifaddr, sysctl, ioctlops, UFS mount, shm, file desc, pagedep, VM swap, UVM amap, temp 4096 devbuf, ioctlops, UFS mount, file desc, MSDOSFS mount, UVM amap, temp 8192 devbuf, NFS node, namecache, UFS quota, UFS mount, ISOFS mount, inodedep, UVM amap 16384 devbuf, indirdep, UVM amap, temp 32768 devbuf, namecache, UFS mount, VM swap, UVM amap 65536 VM swap, UVM amap 131072 UVM amap 262144 UVM amap 524288 UVM amap Memory statistics by type Type Kern Type InUse MemUse HighUse Limit Requests Limit Limit Size(s) devbuf 534 744K809K 39322K 8900 0 16,32,64,128,256,512,1024,2048,4096,8192,16384,32768 pcb32 4K 5K 39322K175720 0 16,32,64,512 routetbl74 6K 7K 39322K 21010 0 16,32,64,128,256 ifaddr39 9K 9K 39322K 390 0 16,32,128,256,512,2048 sysctl 3 3K 3K 39322K30 0 16,256,2048 ioctlops 0 0K 4K 39322K 10720080 0 256,512,1024,2048,4096 mount10 5K 5K 39322K 110 0 512 NFS node 1 8K 8K 39322K10 0 8192 vnodes55 7K 43K 39322K 2161460 0 32,128,256 namecache 341K 41K 39322K30 0 1024,8192,32768 UFS quota 1 8K 8K 39322K10 0 8192 UFS mount4191K 91K 39322K 410 0 16,32,64,512,1024,2048,4096,8192,32768 shm 3 3K 3K 39322K 180 0 256,512,2048 VM map 3 1K 1K 39322K30 0 256 sem11 1K 1K 39322K 740 0 16,32,64,256 dirhash7514K 49K 39322K533310 0 16,32,64,128,256,512 file desc2510K 13K 39322K 29090 0 256,512,1024,2048,4096 proc19 3K 3K 39322K 190 0 32,256,1024 VFS cluster 0 0K 4K 39322K 2955160
Ralink pci on spark64?
Hi, I plan to turn my Sun Ultra 10 into a firewall/access point using a supported Ralink PCI card. But I see on this page http://www.openbsd.org/sparc64.html#hardware that Ralink PCI is not supported by the port. ral man page says that some cards are fuzzy about PCI 2.2, and my Sun Ultra with psycho bus probably doesn't have PCI 2.2. Is this the reason? Maxim
bus_space_map on i386
Hello! I would like to use bus_space_map for writing a framebuffer driver (on i386). I've read the manpage, which sais the 4th argument of the function is the "cacheable" argument. I would like to use BUS_SPACE_MAP_LINEAR. But that doesn't seem to be defined on i386 (it's the same with BUS_SPACE_MAP_CACHEABLE and BUS_SPACE_MAP_PREFETCHABLE). What should I pass as 4th argument? Did I get it right that the "tag"-variable just differentiates the IO-space from the memory space? Thanks in advance, Markus
Testing stack-gap
Hi,
I wrote a trivial program to test the stack-gap feature under openbsd
4.0 i386.
There's something I can't get about the output of that software, and
maybe someone can help me shed some light on it.
Here's the program:
8<---
#include
#include
#include
# define FIRST 400
# define SECOND 400
# define THIRD 400
# define FOURTH 400
# define LAST FOURTH
# define last fourth
# define NUMOFVEC 4
void stackgap( int * pointer );
int main( void )
{
// This is here as a placeholder
int a = 129;
stackgap( &a );
return EXIT_SUCCESS;
}
void stackgap( int * pointer ) {
char first[FIRST];
char second[SECOND];
char third[THIRD];
char fourth[FOURTH];
printf("\n\n***\n");
printf("* STACK GAP *");
printf("\n***\n\n");
printf("Distance between the only variable in main and the first vector is:
%ld bytes \n\n",(long) pointer - (long) first);
}
8<---
Obviously address of vectors change every execution, and that's ok, but
distance between variable "a" and vector first varies between 460 and
472 bytes. Shouldn't it be fixed? Why does this happens? I tought stack
gap couldn't influence relative placement of variables in stack frames.
Thanks in advance,
Gufo
Widescreen flat panel
Hi, I just bought a 22 inches 16/10 flat panel. Saddly, I can't get in the native resolution (1680x1050). I was wondering if a recent (4.1 snapshot of March 23rd) nv driver of X is already able to handle such mode, as I found out it may be the bottleneck. I tried different ModeLine generators from the net, and tried to do it myself using Xorg' logfile. Not helping me out. -- "Linux is for Windows(c) haters while BSD is for UNIX lovers". http://teardrop.free.fr/
Re: no AMANDA: backing up to a remote tape
Jon Simola wrote: > On 3/30/07, Jacob Yocom-Piatt <[EMAIL PROTECTED]> wrote: > >> NOTE: TAPE=/dev/nrst0 here so it doesn't rewind after tar-ing > > That's your problem. > > unset TAPE, or just use the default /dev/rst0 device. > lol! i'm retarded, i guess the manpages really ARE that illuminating. > (hysterical raisins and all)
Re: Testing stack-gap
On 3/31/07, Sbranzo <[EMAIL PROTECTED]> wrote: Obviously address of vectors change every execution, and that's ok, but distance between variable "a" and vector first varies between 460 and 472 bytes. Shouldn't it be fixed? Why does this happens? I tought stack gap couldn't influence relative placement of variables in stack frames. you should look at the alignment of the variables each run.
Re: panic on fresh snap (was: [ppc] Daily digest, Issue 573 (1 messages))
Hi Pedro, The March 30th snapshot appears to have fixed this on alpha/amd64/i386/macppc. Thanks, Marius On 3/31/07, Pedro Martelletto <[EMAIL PROTECTED]> wrote: See [EMAIL PROTECTED] -p.
Re: Testing stack-gap
On 31/03/07 10:26, Ted Unangst wrote: > >472 bytes. Shouldn't it be fixed? Why does this happens? I tought stack > >gap couldn't influence relative placement of variables in stack frames. > > you should look at the alignment of the variables each run. So variables could be aligned differently each run even though stack gap is 8-byte aligned. And the system doesn't align at 8-bytes data between stack frames, or am I missing something? Thanks, Gufo
Re: Widescreen flat panel
xinit -- -logverbose 9 -verbose 9 && send the EDID info? Try a liveCD that that has the 'nvidia' binary driver and see if they have support yet, it may be a simple hack. ~BAS On Sat, 2007-03-31 at 18:46 +0200, Eric Dillenseger wrote: > Hi, > > I just bought a 22 inches 16/10 flat panel. > Saddly, I can't get in the native resolution (1680x1050). > > I was wondering if a recent (4.1 snapshot of March 23rd) nv driver of X > is already able to handle such mode, as I found out it may be the > bottleneck. > > I tried different ModeLine generators from the net, and tried to do it > myself using Xorg' logfile. Not helping me out.
Re: Very slow raid performance with ami(4)
Do you know if an Intel-rebadged srcs28x would care if i plugged in an lsi battery? On visual inspection the hardware looks 100% identical. Probably the only thing changed is the firmware.. On 3/30/07, Stuart Henderson <[EMAIL PROTECTED]> wrote: On 2007/03/30 13:18, Roy Kim wrote: > I didn't realize there's two different batteries. What does the > 'intelligent' version of the battery do extra? LSIiBBU01 (intelligent) has some kind of comms relating to charge state etc, I think it may also have a longer runtime. LSIBBU03 (non-intelligent) doesn't, and was something like a third of the price where I bought mine (scan.co.uk). My approach was to get the cheaper one and spend the difference on drives to backup at least some of the data onto, the amount of data you can lose in one go with SATA RAID gets a bit worrying (-: (dump over ssh to a hard drive on another machine is simple and quite effective). Other tips include not rushing the installation (spend some time making the cables nice and tidy) and setup some monitoring (sensorsd is fine); besides RAID status, it is useful to check temperature, voltages, and fan speed if you can.
Re: Widescreen flat panel
On Sat, Mar 31, 2007 at 12:53:56PM -0500, Brian A. Seklecki wrote: > xinit -- -logverbose 9 -verbose 9 && send the EDID info? Try a liveCD > that that has the 'nvidia' binary driver and see if they have support > yet, it may be a simple hack. > > ~BAS > > On Sat, 2007-03-31 at 18:46 +0200, Eric Dillenseger wrote: > > Hi, > > > > I just bought a 22 inches 16/10 flat panel. > > Saddly, I can't get in the native resolution (1680x1050). > > > > I was wondering if a recent (4.1 snapshot of March 23rd) nv driver of X > > is already able to handle such mode, as I found out it may be the > > bottleneck. > > > > I tried different ModeLine generators from the net, and tried to do it > > myself using Xorg' logfile. Not helping me out. > > > Well, I tried differents settings and got one that is quite working, screen width is 1680 but height is more than 1050, and I can scroll the display up and down. Maybe 1600x1200. I'm using the following setup: Section "Monitor" # DisplaySize 470 300 Identifier "Monitor0" VendorName "BNQ" ModelName"BenQ FP222W" ### Comment all HorizSync and VertSync values to use DDC: HorizSync30.0 - 82.0 VertRefresh 56.0 - 76.0 Option "DPMS" ModeLine"1680x1050" 146.2 1680 1784 1960 2240 1050 1053 1059 1089 +hsync + EndSection Section "Device" Identifier "Card0" Driver "nv" VendorName "nVidia Corporation" BoardName "NV34 [GeForce FX 5200]" BusID "PCI:1:0:0" EndSection Section "Screen" Identifier "Screen0" Device "Card0" Monitor"Monitor0" SubSection "Display" Viewport 0 0 Depth 24 Modes "1680x1050" EndSubSection EndSection And this is the relevant part of the Xorg.0.log: (II) NV: driver for NVIDIA chipsets: RIVA 128, RIVA TNT, RIVA TNT2, (II) Primary Device is: PCI 01:00:0 (--) Chipset GeForce FX 5200 found (II) NV(0): Initializing int10 (--) NV(0): Chipset: "GeForce FX 5200" (II) NV(0): Creating default Display subsection in Screen section "Screen0" for depth/fbbpp 16/16 (==) NV(0): Depth 16, (==) framebuffer bpp 16 (==) NV(0): RGB weight 565 (==) NV(0): Default visual is TrueColor (==) NV(0): Using HW cursor (--) NV(0): Linear framebuffer at 0xD800 (--) NV(0): MMIO registers at 0xE000 (==) NV(0): Write-combining range (0xe000,0x100) was already clear (II) NV(0): I2C bus "DDC" initialized. (II) NV(0): Probing for analog device on output A... (--) NV(0): ...found one (II) NV(0): Probing for analog device on output B... (--) NV(0): ...can't find one (II) NV(0): Probing for EDID on I2C bus A... (II) NV(0): I2C device "DDC:ddc2" registered at address 0xA0. (II) NV(0): I2C device "DDC:ddc2" removed. (--) NV(0): DDC detected a CRT: (II) NV(0): Manufacturer: BNQ Model: 7707 Serial#: 16800 (II) NV(0): Year: 2007 Week: 3 (II) NV(0): EDID Version: 1.3 (II) NV(0): Analog Display Input, Input Voltage Level: 0.700/0.700 V (II) NV(0): Sync: Separate Composite (II) NV(0): Max H-Image Size [cm]: horiz.: 47 vert.: 30 (II) NV(0): Gamma: 2.20 (II) NV(0): DPMS capabilities: StandBy Suspend Off; RGB/Color Display (II) NV(0): Default color space is primary color space (II) NV(0): First detailed timing is preferred mode (II) NV(0): redX: 0.644 redY: 0.332 greenX: 0.288 greenY: 0.601 (II) NV(0): blueX: 0.153 blueY: 0.077 whiteX: 0.313 whiteY: 0.329 (II) NV(0): Supported VESA Video Modes: (II) NV(0): [EMAIL PROTECTED] (II) NV(0): [EMAIL PROTECTED] (II) NV(0): [EMAIL PROTECTED] (II) NV(0): [EMAIL PROTECTED] (II) NV(0): [EMAIL PROTECTED] (II) NV(0): [EMAIL PROTECTED] (II) NV(0): [EMAIL PROTECTED] (II) NV(0): [EMAIL PROTECTED] (II) NV(0): [EMAIL PROTECTED] (II) NV(0): [EMAIL PROTECTED] (II) NV(0): [EMAIL PROTECTED] (II) NV(0): [EMAIL PROTECTED] (II) NV(0): [EMAIL PROTECTED] (II) NV(0): [EMAIL PROTECTED] (II) NV(0): Manufacturer's mask: 0 (II) NV(0): Supported Future Video Modes: (II) NV(0): #0: hsize: 800 vsize 600 refresh: 75 vid: 20293 (II) NV(0): #1: hsize: 1024 vsize 768 refresh: 75 vid: 20321 (II) NV(0): #3: hsize: 1280 vsize 1024 refresh: 60 vid: 32897 (II) NV(0): #4: hsize: 1280 vsize 1024 refresh: 75 vid: 36737 (II) NV(0): #5: hsize: 1152 vsize 864 refresh: 75 vid: 20337 (II) NV(0): Supported additional Video Mode: (II) NV(0): clock: 146.2 MHz Image Size: 433 x 271 mm (II) NV(0): h_active: 1680 h_sync: 1784 h_sync_end 1960 h_blank_end 2240 h_bor (II) NV(0): v_active: 1050 v_sync: 1053 v_sync_end 1059 v_blanking: 1089 v_bor (II) NV(0): Supported additional Video Mode: (II) NV(0): clock: 25.2 MHz Image Size: 376 x 301 mm (II) NV(0): h_active: 640 h_sync: 656 h_sync_end 752 h_blank_end 800 h_border: (II) NV(0): v_active: 350 v_sync: 387 v_sync_end 389 v_blanking: 449 v_border: (II) NV(0): Ranges: V min: 56 V max: 76 Hz, H min: 30 H max: 84 kHz, PixClock (II) NV(0): Monitor name: BenQ FP222W (II) NV(0): Probing for EDID on I2C bus B... (II) NV(0): I2C device "DDC:ddc2" registered at address 0xA0. (II) NV(0): I2C device "DDC:ddc2" removed. (II) NV(0)
comments on book by Levi
I'm perusing books on Unix administration. I see that Nemeth et al is listed on the books section of the web site. The latest edition (3rd) was published in 2000. On Indego, I see another book and wonder if any of you have seen it and care to comment: Levi. Unix Administration: A comprehensive source book for effective systems. Hard cover, published in 2002. ISBN: 0849313511. Thanks, Doug.
Re: Widescreen flat panel
DDC/EDID can be a killjoy. I want to say that there was an Option "NoEDID" "true" ~~BAS On Sat, 2007-03-31 at 21:09 +0200, Eric Dillenseger wrote: > (II) NV(0): Supported VESA Video Modes: > (II) NV(0): [EMAIL PROTECTED] > (II) NV(0): [EMAIL PROTECTED] > (II) NV(0): [EMAIL PROTECTED] > (II) NV(0): [EMAIL PROTECTED] > (II) NV(0): [EMAIL PROTECTED] > (II) NV(0): [EMAIL PROTECTED] > (II) NV(0): [EMAIL PROTECTED] > (II) NV(0): [EMAIL PROTECTED] > (II) NV(0): [EMAIL PROTECTED] > (II) NV(0): [EMAIL PROTECTED] > (II) NV(0): [EMAIL PROTECTED] > (II) NV(0): [EMAIL PROTECTED] > (II) NV(0): [EMAIL PROTECTED] > (II) NV(0): [EMAIL PROTECTED]
Re: Ralink pci on spark64?
It would help to see the dmesg(8) output of the card on a supported platform. Do you mean ral(4)? Many PCI drivers will just-work. ~BAS On Sat, 2007-03-31 at 16:12 +0200, Maxim Belooussov wrote: > Hi, > > I plan to turn my Sun Ultra 10 into a firewall/access point using a > supported Ralink PCI card. But I see on this page > http://www.openbsd.org/sparc64.html#hardware that Ralink PCI is not > supported by the port. > > ral man page says that some cards are fuzzy about PCI 2.2, and my Sun > Ultra with psycho bus probably doesn't have PCI 2.2. Is this the > reason? > > Maxim
Prism54 card - any developers that can make use of it?
I am sick of messing with my XG-600 PRISM54 based wireless card. It does have Linux support (in Ubuntu), and I haven't tried it in OpenBSD but I know FreeBSD doesn't have a driver by default for it. If there is a developer out there who likes fidling with wireless drivers, I would be more than happy to mail the card out, free of charge, yours to keep. It is a mini-pci card. I am also posting this offer on planet.ubuntu.com but I would much rather see it go to use in OpenBSD. Steve
Re: Widescreen flat panel
On Saturday 31 March 2007, Brian A. Seklecki wrote: > DDC/EDID can be a killjoy. I want to say that there was an > > Option "NoEDID" "true" As an aside (in case it helps anyone). Using the nVidia binary under Linux I have to set: Option "ModeValidation""NoMaxPClkCheck" in order to use the digital out to drive my widescreen monitor. Turning off EDID totally does not work. Chris
Re: lsi logic sparc64 config?
megarc(8) has been ported to some non-Linux platforms. MegaCli runs in emulation mode in others (dirty dirty hack). The best bet is a bio(4) interface or a hardware raid that has a non-BIOS/proprietary CLI management interface. ~BAS On Sat, 2007-03-31 at 14:37 +1000, David Gwynne wrote: > On 31/03/2007, at 8:16 AM, Bryan Irvine wrote: > > > This might be a little off-topic, but I can't find the answer > > anywhere. > > > > Since the LSI logic sata 150-4 cards need to be configured via the > > cards bios (at bootup on i386) I can't figure out if there is a way > > to configure a RAID when using a sparc64 platform. > > > > Is this possible? > > the ami(4) driver isn't enabled on sparc64, so aside from not being > able to configure the card in the machine, we're not sure you'll be > able to use it either. we have taken care to make it as portable as > possible, but i doubt it will work too well. > > dlg
Re: Ralink pci on spark64?
On Sat, Mar 31, 2007 at 04:12:20PM +0200, Maxim Belooussov wrote: > Hi, > > I plan to turn my Sun Ultra 10 into a firewall/access point using a > supported Ralink PCI card. But I see on this page > http://www.openbsd.org/sparc64.html#hardware that Ralink PCI is not > supported by the port. > > ral man page says that some cards are fuzzy about PCI 2.2, and my Sun > Ultra with psycho bus probably doesn't have PCI 2.2. Is this the > reason? > > Maxim Most Ralink cards are 3.3v only, which means your Ultra 10 probably isn't going to work, this is what the note is about. No one with the relevant Ralink hardware has a new enough sparc64 to play with to see if it works, so it is not enabled in the default sparc64 GENERIC kernel.
adding video cameras for cms on openbsd.
Any suggestions for opensource video survelliance applications on OpenBSD? I setup an openbsd server to support a condominium association, and it has been successful using cyrus-imap and drupal. Now I was asked if we could add video cameras and security using the openbsd server. The short answer is yes, the correct answer is maybe :) and what approach depends on coverage and budget I realize a practical discussion is way beyond the scope of this list with questions like, do the cameras do the video capture or have the CTV signal come back to server to capture, and how much done by hardware how much done by software, motion detection could switch from time lapse to full or from quadrant view to active camera?..., and so on, that said... Is anyone using some opensource project or the like on openbsd to coordinate the storage of video and retrieval through a web interface and if so how mature or suggestions? (and maybe embed in drupal or other cms if can) As afore I will do a summary report back to the list for others if I find enough snippets to suggest approaching building survielliance using openbsd and maybe apache/mysql/php or the like. Else a proprietary hardware solution may be considered, since I said emphatically no MSd0ze solution for something supporting 6 - 30 cameras with access to retrieve and view stored video upto several weeks or more. TIA.
Re: hw.sensor empty
Please provide dmesg with your mail. I guess you have no sensors in your box or they're not supported yet. somebody off list had similar problem and remembered me to maintain userland and kernel in sync. after doing this, sensors were there... thanks, -- giovanni
