Re: cvs files from attic show up in update
On 07/03/15 09:33, n.reu...@hxgn.net wrote:
> Dear misc,
>
> i have a script running every night on my openbsd 5.7 -stable box to fetch
> the latest sources from cvs. If some files changed, it will send a mail.
> This morning i got the following output from last nights run:
>
> ? gnu/usr.bin/binutils-2.17/gas/testsuite/gas/mmix
>
> Here is the line of code:
>
> # update system sources
> cd /usr/src
> /usr/bin/cvs -d ${CVSROOT} -q up -rOPENBSD_5_7 -Pd \
> | /usr/bin/tee ${LOG}
>
> As far as is understand, the testsuite was importet by mistake and moved
> to the attic directly after the import approx. 4 years ago:
> http://cvsweb.openbsd.org/cgi-bin/cvsweb/src/gnu/usr.bin/binutils-2.17/gas/.
> I also don't have the testsuite-folder on my disk.
>
> Now, is this a problem with cvs or somehow "buggy, but expected"
> behaviour? I have ever seen this message before, and i don't see any
> activity on binutils in -stable. Or is it safe to filter out line starting
> with '?' ?
>
> Any insight is greatly appreciated.
>
>
> Thanks and best regards
> Nils
>
>
>From man cvs(1)
? filefile is in your working directory, but does not correspond to
anything in the source repository, and is not in the list of files for
cvs to ignore (see the description of the -I option).
$ cd /usr/src/usr.bin/sed
$ cvs -R -q up -Pd
$ touch extra
$ cvs -R -q up -Pd
? extra
$ rm extra
$ cvs -R -q up -Pd
$
Re: Cannot run Snort
On 06/27/15 09:12, Wong Peter wrote: > Dear All, > > I had installed Snort but cannot run it. > > Error Message: Can't load library liblzma.s0.2.0 > > What need to install? I had install the lzlib but still cannot solved it. > Which packages need to install or how to tell snort to look up the shared > library? > try xz, it should have been installed with snort, current version does include the dependency. For 5.7 the dependency is missing. $ pkg_info -Sq snort snort-2.9.7.3,@daq-2.0.5,@libdnet-1.12p10,@pcre-8.37p0,@xz-5.2.1,c.80.0,crypto.34.0,daq.2.1,dnet.1.0,lzma.2.1,m.9.0,pcap.8.0,pcre.3.0,pthread.19.0,z.5.0 $ pkg_info -f xz | grep lzma.so @lib lib/liblzma.so.2.1 The pkglocatedb package should help to find any missing packages... $ pkg_locate lzma.so.2 xz-5.2.1:archivers/xz:/usr/local/lib/liblzma.so.2.1
Re: openbsd 5.7 libs "bad major"
On 05/02/15 08:57, Joseph Oficre wrote: > Hi @misc! > > Trying to build opennx through ports and catch this > ===> Installing wxWidgets-gtk2-2.8.12p9 from /usr/packages/amd64/all/ > Can't install wxWidgets-gtk2-2.8.12p9 because of libraries > |library atk-1.0.21209.1 not found > | /usr/local/lib/libatk-1.0.so.21409.1 (atk-2.14.0): bad major > |library gio-2.0.4000.0 not found > | /usr/local/lib/libgio-2.0.so.4200.0 (glib2-2.42.1p0): bad major > |library glib-2.0.4000.0 not found > | /usr/local/lib/libglib-2.0.so.4200.0 (glib2-2.42.1p0): bad major > |library gobject-2.0.4000.0 not found > | /usr/local/lib/libgobject-2.0.so.4200.0 (glib2-2.42.1p0): bad major > |library gthread-2.0.4000.0 not found > | /usr/local/lib/libgthread-2.0.so.4200.0 (glib2-2.42.1p0): bad major > Direct dependencies for wxWidgets-gtk2-2.8.12p9 resolve to gtk+2-2.24.26 > libiconv-1.14p1 sdl-1.2.15p6 gettext-0.19.4 libmspack-0.5alphav0 > iodbc-3.52.9p1 > Full dependency tree is libnettle-2.7.1p1 dbus-1.8.16v0 gdbm-1.11p0 > libmspack-0.5alphav0 libelf-0.8.13p2 png-1.6.16 iodbc-3.52.9p1 > gnutls-3.2.21 jasper-1.900.1p2 librsvg-2.40.7 gdk-pixbuf-2.30.8 atk-2.14.0 > hicolor-icon-theme-0.14 gettext-0.19.4 glib2-2.42.1p0 jpeg-9a > libxml-2.9.2p0 p11-kit-0.22.1 gtk+2-2.24.26 libiconv-1.14p1 gmp-5.0.2p2 > libdaemon-0.14p0 libtasn1-4.2p0 tiff-4.0.3p2 cups-libs-2.0.2 > shared-mime-info-1.4 bzip2-1.0.6p1 cairo-1.14.0p1 avahi-0.6.31p15 > libcroco-0.6.8p0 harfbuzz-0.9.38 gtk-update-icon-cache-2.24.26 pcre-8.35 > graphite2-1.2.4 gnome-icon-theme-symbolic-3.12.0p1 > gnome-icon-theme-3.12.0p1 pango-1.36.8 sdl-1.2.15p6 libffi-3.0.13 xz-5.2.0 > python-2.7.9p0 lzo2-2.08 > *** Error 1 in /usr/ports/x11/wxWidgets (/usr/ports/infrastructure/mk/ > bsd.port.mk:1961 '/var/db/pkg/wxWidgets-gtk2-2.8.12p9/+CONTENTS': @if ...) > *** Error 1 in /usr/ports/x11/wxWidgets (/usr/ports/infrastructure/mk/ > bsd.port.mk:2473 'install') > *** Error 1 in . (/usr/ports/infrastructure/mk/bsd.port.mk:2100 > '/usr/obj/ports/opennx-0.16.0.729/.dep-x11-wxWidgets') > *** Error 1 in . (/usr/ports/infrastructure/mk/bsd.port.mk:2556 > '/usr/obj/ports/opennx-0.16.0.729/.extract_done') > *** Error 1 in . (/usr/ports/infrastructure/mk/bsd.port.mk:1940 > '/usr/packages/amd64/all/opennx-0.16.0.729.tgz') > *** Error 1 in . (/usr/ports/infrastructure/mk/bsd.port.mk:2493 > '_internal-package') > *** Error 1 in . (/usr/ports/infrastructure/mk/bsd.port.mk:2473 'package') > *** Error 1 in . (/usr/ports/infrastructure/mk/bsd.port.mk:1957 > '/var/db/pkg/opennx-0.16.0.729/+CONTENTS') > *** Error 1 in /usr/ports/x11/nx/opennx (/usr/ports/infrastructure/mk/ > bsd.port.mk:2473 'install') > > > So as i know the problem is bad lib version. For example i need atk-2.14.0. > The main thing is that i have atk-2.14.0 package installed (but no 2.14.0 > lib present, lol). > > How can i solve this without reinstalling packages? Because it wants to > remove a lot of dependecies > Upgrade process was pretty simple, just loaded bsd.rd, (U), then sysmerge > and pkg_add -u. So i cant truly understand how could my pretty system do > this to me :c > Looks like mixing 5.6 and 5.7 packages. > Can't install wxWidgets-gtk2-2.8.12p9 because of libraries > |library atk-1.0.21209.1 not found > | /usr/local/lib/libatk-1.0.so.21409.1 (atk-2.14.0): bad major wxWidgets-gtk2 wants the atk-2.12 (5.6) library atk-1.0.21209.1, but you have atk-2.14 (5.7) library atk-1.0.21409.1 installed. Your trying to install the 5.6 version of wxWidgets-gtk2 maybe PKG_PATH is set wrongly to 5.6 packages. Or you didn't clean out /usr/ports/package/all/amd64 so have old packages built under 5.6.
Re: Gnash, mplayer, Firefox losing its mind in current 28 Feb
Hi,
> On Sat, Mar 07, 2009 at 06:58:39PM +0000, Nigel J. Taylor wrote:
>> I have found the mouse pointer being locked to the right edge as well, and
>> very
>> annoying. I can normally recover, the I move the middle mouse button up/down
>> and
>> press escape, that seems to release the mouse pointer for me, not much help
>> if
>> you have a two button mouse. I use an amd64 current build, and I found the
>> issue
>> is not confined to firefox/gnash.
>
> what window manager are you using?
Mainly kde, also run others, can't be sure, I think had the same happen with
some other window managers.
>
>> Regards
>>
>> Nigel Taylor
>>
>> Ed Ahlsen-Girard wrote:
>>> Running current from a Feb 28 snapshot, I have found that if either
>>> mplayer or gnash (from snapshots) are installed, and if embedded media
>>> gain focus in FireFox, the mouse pointer will slide to the right edge of
>>> the window and stay there until the system is restarted. The pointer
>>> can be moved up and down along the edge, but will not leave it, and
>>> focus cannot be moved to another window. Ctrl-arrow keys have no
>>> effect. A gnash core file of 8064892 bytes exists. Dmesg below, core
>>> on request.
>>>
>>> Ed Ahlsen-Girard
>>>
>>> OpenBSD 4.4-current (GENERIC) #6: Fri Mar 6 22:42:12 CST 2009
>>>e...@puff.waynel.local:/usr/src/sys/arch/i386/compile/GENERIC
>>> cpu0: Intel Pentium III ("GenuineIntel" 686-class, 512KB L2 cache) 499 MHz
>>> cpu0:
>>> FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE
>>>
>>> real mem = 335118336 (319MB)
>>> avail mem = 315379712 (300MB)
>>> mainbus0 at root
>>> bios0 at mainbus0: AT/286+ BIOS, date 08/01/01, BIOS32 rev. 0 @ 0xffe90,
>>> SMBIOS rev. 2.2 @ 0xfb410 (64 entries)
>>> bios0: vendor Dell Computer Corporation version "A10" date 08/01/01
>>> bios0: Dell Computer Corporation OptiPlex GX1 500Mbr+
>>> apm0 at bios0: Power Management spec V1.2
>>> apm0: AC on, battery charge unknown
>>> acpi at bios0 function 0x0 not configured
>>> pcibios0 at bios0: rev 2.1 @ 0xf/0x1
>>> pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xfc670/176 (9 entries)
>>> pcibios0: PCI Interrupt Router at 000:07:0 ("Intel 82371AB PIIX4 ISA"
>>> rev 0x00)
>>> pcibios0: PCI bus #2 is the last bus
>>> bios0: ROM list: 0xc/0xd000 0xd/0x8000
>>> cpu0 at mainbus0: (uniprocessor)
>>> pci0 at mainbus0 bus 0: configuration mode 1 (bios)
>>> pchb0 at pci0 dev 0 function 0 "Intel 82443BX AGP" rev 0x03
>>> intelagp0 at pchb0
>>> agp0 at intelagp0: aperture at 0xf000, size 0x400
>>> ppb0 at pci0 dev 1 function 0 "Intel 82443BX AGP" rev 0x03
>>> pci1 at ppb0 bus 1
>>> "ATI Rage Pro" rev 0x5c at pci1 dev 0 function 0 not configured
>>> piixpcib0 at pci0 dev 7 function 0 "Intel 82371AB PIIX4 ISA" rev 0x02
>>> pciide0 at pci0 dev 7 function 1 "Intel 82371AB IDE" rev 0x01: DMA,
>>> channel 0 wired to compatibility, channel 1 wired to compatibility
>>> wd0 at pciide0 channel 0 drive 0:
>>> wd0: 16-sector PIO, LBA, 9765MB, 1728 sectors
>>> wd1 at pciide0 channel 0 drive 1:
>>> wd1: 16-sector PIO, LBA, 76319MB, 156301488 sectors
>>> wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 2
>>> wd1(pciide0:0:1): using PIO mode 4, Ultra-DMA mode 2
>>> atapiscsi0 at pciide0 channel 1 drive 0
>>> scsibus0 at atapiscsi0: 2 targets, initiator 7
>>> cd0 at scsibus0 targ 0 lun 0: ATAPI 5/cdrom
>>> removable
>>> cd0(pciide0:1:0): using PIO mode 4, DMA mode 2
>>> uhci0 at pci0 dev 7 function 2 "Intel 82371AB USB" rev 0x01: irq 11
>>> piixpm0 at pci0 dev 7 function 3 "Intel 82371AB Power" rev 0x02: SMBus
>>> disabled
>>> vga1 at pci0 dev 14 function 0 "ATI Radeon 9200 SE Sec" rev 0x01
>>> wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
>>> wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
>>> radeondrm0 at vga1: irq 9
>>> drm0 at radeondrm0
>>> ppb1 at pci0 dev 15 function 0 "DEC 21152 PCI-PCI" rev 0x03
>>> pci2 at ppb1 bus 2
>>> ohci0 at pci2 dev 11 function 0 "Acer Labs M5237 USB" rev 0x03: irq 9,
>>> version 1.0, legacy support
>>> ehci0 at pci2 dev 11 function 3 "Acer Labs M5239 USB2" rev 0x01: irq 10
>>> usb0 at ehci0: USB re
Re: Gnash, mplayer, Firefox losing its mind in current 28 Feb
I have found the mouse pointer being locked to the right edge as well, and very
annoying. I can normally recover, the I move the middle mouse button up/down and
press escape, that seems to release the mouse pointer for me, not much help if
you have a two button mouse. I use an amd64 current build, and I found the issue
is not confined to firefox/gnash.
Regards
Nigel Taylor
Ed Ahlsen-Girard wrote:
> Running current from a Feb 28 snapshot, I have found that if either
> mplayer or gnash (from snapshots) are installed, and if embedded media
> gain focus in FireFox, the mouse pointer will slide to the right edge of
> the window and stay there until the system is restarted. The pointer
> can be moved up and down along the edge, but will not leave it, and
> focus cannot be moved to another window. Ctrl-arrow keys have no
> effect. A gnash core file of 8064892 bytes exists. Dmesg below, core
> on request.
>
> Ed Ahlsen-Girard
>
> OpenBSD 4.4-current (GENERIC) #6: Fri Mar 6 22:42:12 CST 2009
>e...@puff.waynel.local:/usr/src/sys/arch/i386/compile/GENERIC
> cpu0: Intel Pentium III ("GenuineIntel" 686-class, 512KB L2 cache) 499 MHz
> cpu0:
> FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE
>
> real mem = 335118336 (319MB)
> avail mem = 315379712 (300MB)
> mainbus0 at root
> bios0 at mainbus0: AT/286+ BIOS, date 08/01/01, BIOS32 rev. 0 @ 0xffe90,
> SMBIOS rev. 2.2 @ 0xfb410 (64 entries)
> bios0: vendor Dell Computer Corporation version "A10" date 08/01/01
> bios0: Dell Computer Corporation OptiPlex GX1 500Mbr+
> apm0 at bios0: Power Management spec V1.2
> apm0: AC on, battery charge unknown
> acpi at bios0 function 0x0 not configured
> pcibios0 at bios0: rev 2.1 @ 0xf/0x1
> pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xfc670/176 (9 entries)
> pcibios0: PCI Interrupt Router at 000:07:0 ("Intel 82371AB PIIX4 ISA"
> rev 0x00)
> pcibios0: PCI bus #2 is the last bus
> bios0: ROM list: 0xc/0xd000 0xd/0x8000
> cpu0 at mainbus0: (uniprocessor)
> pci0 at mainbus0 bus 0: configuration mode 1 (bios)
> pchb0 at pci0 dev 0 function 0 "Intel 82443BX AGP" rev 0x03
> intelagp0 at pchb0
> agp0 at intelagp0: aperture at 0xf000, size 0x400
> ppb0 at pci0 dev 1 function 0 "Intel 82443BX AGP" rev 0x03
> pci1 at ppb0 bus 1
> "ATI Rage Pro" rev 0x5c at pci1 dev 0 function 0 not configured
> piixpcib0 at pci0 dev 7 function 0 "Intel 82371AB PIIX4 ISA" rev 0x02
> pciide0 at pci0 dev 7 function 1 "Intel 82371AB IDE" rev 0x01: DMA,
> channel 0 wired to compatibility, channel 1 wired to compatibility
> wd0 at pciide0 channel 0 drive 0:
> wd0: 16-sector PIO, LBA, 9765MB, 1728 sectors
> wd1 at pciide0 channel 0 drive 1:
> wd1: 16-sector PIO, LBA, 76319MB, 156301488 sectors
> wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 2
> wd1(pciide0:0:1): using PIO mode 4, Ultra-DMA mode 2
> atapiscsi0 at pciide0 channel 1 drive 0
> scsibus0 at atapiscsi0: 2 targets, initiator 7
> cd0 at scsibus0 targ 0 lun 0: ATAPI 5/cdrom
> removable
> cd0(pciide0:1:0): using PIO mode 4, DMA mode 2
> uhci0 at pci0 dev 7 function 2 "Intel 82371AB USB" rev 0x01: irq 11
> piixpm0 at pci0 dev 7 function 3 "Intel 82371AB Power" rev 0x02: SMBus
> disabled
> vga1 at pci0 dev 14 function 0 "ATI Radeon 9200 SE Sec" rev 0x01
> wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
> wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
> radeondrm0 at vga1: irq 9
> drm0 at radeondrm0
> ppb1 at pci0 dev 15 function 0 "DEC 21152 PCI-PCI" rev 0x03
> pci2 at ppb1 bus 2
> ohci0 at pci2 dev 11 function 0 "Acer Labs M5237 USB" rev 0x03: irq 9,
> version 1.0, legacy support
> ehci0 at pci2 dev 11 function 3 "Acer Labs M5239 USB2" rev 0x01: irq 10
> usb0 at ehci0: USB revision 2.0
> uhub0 at usb0 "Acer Labs EHCI root hub" rev 2.00/1.00 addr 1
> usb1 at ohci0: USB revision 1.0
> uhub1 at usb1 "Acer Labs OHCI root hub" rev 1.00/1.00 addr 1
> xl0 at pci0 dev 17 function 0 "3Com 3c905B 100Base-TX" rev 0x24: irq 11,
> address 00:c0:4f:22:a7:b8
> exphy0 at xl0 phy 24: 3Com internal media interface
> isa0 at piixpcib0
> isadma0 at isa0
> com0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo
> com1 at isa0 port 0x2f8/8 irq 3: ns16550a, 16 byte fifo
> pckbc0 at isa0 port 0x60/5
> pckbd0 at pckbc0 (kbd slot)
> pckbc0: using irq 1 for kbd slot
> wskbd0 at pckbd0: console keyboard, using wsdisplay0
> pmsi0 at pckbc0 (aux slot)
> pckbc0: using irq 12 for aux slot
> wsmouse0 at pmsi0 mux 0
> pcppi0 at isa0 port 0x61
> midi0 at pcppi0:
> spkr0 at pcppi0
> lpt0 at isa0 port 0x378/4 irq 7
> npx0 at isa0 port 0xf0/16: reported by CPUID; using exception 16
> fdc0 at isa0 port 0x3f0/6 irq 6 drq 2
> fd0 at fdc0 drive 0: 1.44MB 80 cyl, 2 head, 18 sec
> isapnp0 at isa0 port 0x279: read port 0x203
> wss1 at isapnp0 "CS4236B, CSC, , WSS/SB" port
> 0x534/4,0x388/4,0x220/16 irq 5 drq 1,0: CS4236/CS4236B (vers 0)
> audio0 at wss1
> joy0 at isapnp0 "CS4236B, CSC000F, , Game" port 0x3a0/8
> "CS4236B, CSC0010, , Ctrl" at isapnp0 port 0
Re: -CURRENT intel(4) problem
I just encountered what looks like the same issue. Worked with OpenBSD v4.4, has
been working since OpenBSD v3.2. I will try some of the suggestions.
I also noticed that the /dev/drm0 is being removed, and then complaining it's
not there any longer. Running MAKEDEV recreates /dev/drm0.
Attached is a dmesg and Xorg.0.log, any news or progress please let me know.
Regards
Nigel Taylor
dmesg and Xorg.0.log attached.
OpenBSD 4.5 (GENERIC) #1749: Sat Feb 28 14:51:18 MST 2009
dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC
cpu0: Intel(R) Pentium(R) 4 CPU 1.80GHz ("GenuineIntel" 686-class) 1.80 GHz
cpu0:
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM
real mem = 259551232 (247MB)
avail mem = 242667520 (231MB)
mainbus0 at root
bios0 at mainbus0: AT/286+ BIOS, date 05/28/02, BIOS32 rev. 0 @ 0xeba30, SMBIOS
rev. 2.3 @ 0xfd486 (46 entries)
bios0: vendor Compaq version "686O2 v1.08" date 05/28/2002
bios0: Compaq Evo D510 SFF
acpi0 at bios0: rev 0
acpi0: tables DSDT FACP SSDT SSDT SSDT SSDT SSDT SSDT SSDT APIC SSDT SSDT SSDT
SSDT SSDT SSDT SSDT
acpi0: wakeup devices PCI0(S4) HUB_(S4) COM1(S4) COM2(S4) USB1(S1) USB2(S1)
USB3(S1) EUSB(S1) PBTN(S4)
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: apic clock running at 99MHz
ioapic0 at mainbus0: apid 8 pa 0xfec0, version 20, 24 pins
ioapic0: misconfigured as apic 0, remapped to apid 8
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus 5 (HUB_)
acpicpu0 at acpi0
acpibtn0 at acpi0: PBTN
bios0: ROM list: 0xc/0xac00! 0xcac00/0x1800 0xcc400/0x1800 0xe1c00/0x9000!
pci0 at mainbus0 bus 0: configuration mode 1 (bios)
pchb0 at pci0 dev 0 function 0 "Intel 82845G Host" rev 0x01
vga1 at pci0 dev 2 function 0 "Intel 82845G Video" rev 0x01
wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
intagp0 at vga1
agp0 at intagp0: aperture at 0xf000, size 0x800
inteldrm0 at vga1: apic 8 int 16 (irq 5)
drm0 at inteldrm0
uhci0 at pci0 dev 29 function 0 "Intel 82801DB USB" rev 0x01: apic 8 int 16
(irq 5)
uhci1 at pci0 dev 29 function 1 "Intel 82801DB USB" rev 0x01: apic 8 int 19
(irq 11)
ehci0 at pci0 dev 29 function 7 "Intel 82801DB USB" rev 0x01: apic 8 int 23
(irq 5)
usb0 at ehci0: USB revision 2.0
uhub0 at usb0 "Intel EHCI root hub" rev 2.00/1.00 addr 1
ppb0 at pci0 dev 30 function 0 "Intel 82801BA Hub-to-PCI" rev 0x81
pci1 at ppb0 bus 5
fxp0 at pci1 dev 4 function 0 "Intel 8255x" rev 0x08, i82559: apic 8 int 16 (irq
5), address 00:02:b3:42:02:56
inphy0 at fxp0 phy 1: i82555 10/100 PHY, rev. 4
fxp1 at pci1 dev 8 function 0 "Intel PRO/100 VM" rev 0x81, i82562: apic 8 int 20
(irq 10), address 00:08:02:83:f2:d0
inphy1 at fxp1 phy 1: i82562EM 10/100 PHY, rev. 0
ichpcib0 at pci0 dev 31 function 0 "Intel 82801DB LPC" rev 0x01
pciide0 at pci0 dev 31 function 1 "Intel 82801DB IDE" rev 0x01: DMA, channel 0
configured to compatibility, channel 1 configured to compatibility
wd0 at pciide0 channel 0 drive 0:
wd0: 16-sector PIO, LBA, 38166MB, 78165360 sectors
wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 5
atapiscsi0 at pciide0 channel 1 drive 0
scsibus0 at atapiscsi0: 2 targets
cd0 at scsibus0 targ 0 lun 0: ATAPI 5/cdrom
removable
cd0(pciide0:1:0): using PIO mode 4, DMA mode 2
auich0 at pci0 dev 31 function 5 "Intel 82801DB AC97" rev 0x01: apic 8 int 17
(irq 5), ICH4 AC97
ac97: codec id 0x41445372 (Analog Devices AD1981A)
ac97: codec features headphone, 20 bit DAC, No 3D Stereo
audio0 at auich0
usb1 at uhci0: USB revision 1.0
uhub1 at usb1 "Intel UHCI root hub" rev 1.00/1.00 addr 1
usb2 at uhci1: USB revision 1.0
uhub2 at usb2 "Intel UHCI root hub" rev 1.00/1.00 addr 1
isa0 at ichpcib0
isadma0 at isa0
com0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo
com1 at isa0 port 0x2f8/8 irq 3: ns16550a, 16 byte fifo
pckbc0 at isa0 port 0x60/5
pckbd0 at pckbc0 (kbd slot)
pckbc0: using irq 1 for kbd slot
wskbd0 at pckbd0: console keyboard, using wsdisplay0
pms0 at pckbc0 (aux slot)
pckbc0: using irq 12 for aux slot
wsmouse0 at pms0 mux 0
pcppi0 at isa0 port 0x61
midi0 at pcppi0:
spkr0 at pcppi0
lpt0 at isa0 port 0x378/4 irq 7
npx0 at isa0 port 0xf0/16: reported by CPUID; using exception 16
fdc0 at isa0 port 0x3f0/6 irq 6 drq 2
fd0 at fdc0 drive 0: 1.44MB 80 cyl, 2 head, 18 sec
mtrr: Pentium Pro MTRR support
softraid0 at root
root on wd0a swap on wd0b dump on wd0b
umass0 at uhub0 port 1 configuration 1 interface 0 "vendor 0x0930 USB Flash
Memory" rev 2.00/1.00 addr 2
umass0: using SCSI over Bulk-Only
scsibus1 at umass0: 2 targets, initiator 0
sd0 at scsibus1 targ 1 lun 0: <, USB Flash Memory, 1.04> SCSI0 0/direct
removable
sd0: 980MB, 512 bytes/sec, 2007040 sec total
X.Org X Server 1.5.3
Release Date: 5 November 2008
X Protocol Version 11, Revision 0
Build Operating System: OpenBSD 4.5 i386
Current Operating System: OpenBSD vultest.btc3.po
Re: 4.5 snapshot fails to detect pcmcia/cardbus adapters
Hi,
Update, had an idea to try same adapters in second laptop, can't install OpenBSD
v4.5 from snapshot, but could run up bsd.rd off the install CD and get the
dmesg, as below, on this laptop the cards are detected.
OpenBSD 4.5 (RAMDISK_CD) #1112: Sat Feb 28 15:06:26 MST 2009
dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/RAMDISK_CD
cpu0: Intel(R) Core(TM) Duo CPU T2500 @ 2.00GHz ("GenuineIntel" 686-class) 2 GHz
cpu0:
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,VMX,EST,TM2,xTPR
real mem = 1063219200 (1013MB)
avail mem = 1021431808 (974MB)
mainbus0 at root
bios0 at mainbus0: AT/286+ BIOS, date 08/21/06, BIOS32 rev. 0 @ 0xfdbf4, SMBIOS
rev. 2.4 @ 0xe4f00 (65 entries)
bios0: vendor FUJITSU // Phoenix Technologies Ltd. version "Version 1.18" date
08/21/2006
bios0: FUJITSU SIEMENS LIFEBOOK S7110
acpi0 at bios0: rev 0
acpi0: tables DSDT FACP SSDT MCFG SSDT SSDT APIC HPET BOOT
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: apic clock running at 166MHz
cpu at mainbus0: not configured
ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus 8 (PCIB)
acpiprt2 at acpi0: bus 2 (RP01)
acpiprt3 at acpi0: bus 3 (RP02)
acpiprt4 at acpi0: bus 5 (RP03)
bios0: ROM list: 0xc/0xe600! 0xce800/0x1000 0xcfa00/0x1000 0xdc000/0x1c00!
pci0 at mainbus0 bus 0: configuration mode 1 (bios)
pchb0 at pci0 dev 0 function 0 "Intel 82945GM Host" rev 0x03
vga1 at pci0 dev 2 function 0 "Intel 82945GM Video" rev 0x03
wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
"Intel 82945GM Video" rev 0x03 at pci0 dev 2 function 1 not configured
"Intel 82801GB HD Audio" rev 0x02 at pci0 dev 27 function 0 not configured
ppb0 at pci0 dev 28 function 0 "Intel 82801GB PCIE" rev 0x02: apic 2 int 22
(irq 11)
pci1 at ppb0 bus 2
mskc0 at pci1 dev 0 function 0 "Marvell Yukon 88E8055" rev 0x12, Yukon-2 EC
Ultra rev. A1 (0x2): apic 2 int 16 (irq 11)
msk0 at mskc0 port A: address 00:17:42:30:80:2a
eephy0 at msk0 phy 0: 88E1149 Gigabit PHY, rev. 1
ppb1 at pci0 dev 28 function 1 "Intel 82801GB PCIE" rev 0x02: apic 2 int 21
(irq 11)
pci2 at ppb1 bus 3
ppb2 at pci0 dev 28 function 2 "Intel 82801GB PCIE" rev 0x02: apic 2 int 20
(irq 11)
pci3 at ppb2 bus 5
wpi0 at pci3 dev 0 function 0 "Intel PRO/Wireless 3945ABG" rev 0x02: apic 2 int
18 (irq 11): could not power ON adapter
uhci0 at pci0 dev 29 function 0 "Intel 82801GB USB" rev 0x02: apic 2 int 23
(irq 11)
uhci1 at pci0 dev 29 function 1 "Intel 82801GB USB" rev 0x02: apic 2 int 20
(irq 11)
uhci2 at pci0 dev 29 function 2 "Intel 82801GB USB" rev 0x02: apic 2 int 18
(irq 11)
uhci3 at pci0 dev 29 function 3 "Intel 82801GB USB" rev 0x02: apic 2 int 16
(irq 11)
ehci0 at pci0 dev 29 function 7 "Intel 82801GB USB" rev 0x02: apic 2 int 23
(irq 11)
usb0 at ehci0: USB revision 2.0
uhub0 at usb0 "Intel EHCI root hub" rev 2.00/1.00 addr 1
ppb3 at pci0 dev 30 function 0 "Intel 82801BAM Hub-to-PCI" rev 0xe2
pci4 at ppb3 bus 8
cbb0 at pci4 dev 3 function 0 "O2 Micro OZ711MP1 CardBus" rev 0x21: apic 2 int
16 (irq 11)
"O2 Micro Firewire" rev 0x02 at pci4 dev 3 function 4 not configured
cardslot0 at cbb0 slot 0 flags 0
cardbus0 at cardslot0: bus 9 device 0 cacheline 0x0, lattimer 0x20
pcmcia0 at cardslot0
ichpcib0 at pci0 dev 31 function 0 "Intel 82801GBM LPC" rev 0x02: PM disabled
pciide0 at pci0 dev 31 function 1 "Intel 82801GB IDE" rev 0x02: DMA, channel 0
configured to compatibility, channel 1 configured to compatibility
atapiscsi0 at pciide0 channel 0 drive 0
scsibus0 at atapiscsi0: 2 targets
cd0 at scsibus0 targ 0 lun 0: ATAPI 5/cdrom
removable
cd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 2
pciide0: channel 1 ignored (disabled)
ahci0 at pci0 dev 31 function 2 "Intel 82801GBM AHCI" rev 0x02: apic 2 int 19
(irq 11), AHCI 1.1
ahci0: PHY offline on port 2
scsibus1 at ahci0: 32 targets
sd0 at scsibus1 targ 0 lun 0: SCSI3 0/direct fixed
sd0: 76319MB, 512 bytes/sec, 156301488 sec total
"Intel 82801GB SMBus" rev 0x02 at pci0 dev 31 function 3 not configured
usb1 at uhci0: USB revision 1.0
uhub1 at usb1 "Intel UHCI root hub" rev 1.00/1.00 addr 1
usb2 at uhci1: USB revision 1.0
uhub2 at usb2 "Intel UHCI root hub" rev 1.00/1.00 addr 1
usb3 at uhci2: USB revision 1.0
uhub3 at usb3 "Intel UHCI root hub" rev 1.00/1.00 addr 1
usb4 at uhci3: USB revision 1.0
uhub4 at usb4 "Intel UHCI root hub" rev 1.00/1.00 addr 1
isa0 at ichpcib0
isadma0 at isa0
com0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo
pckbc0 at isa0 port 0x60/5
pckbd0 at pckbc0 (kbd slot)
pckbc0: using irq 1 for kbd slot
wskbd0 at pckbd0: console keyboard, using wsdisplay0
npx0 at isa0 port 0xf0/16: reported by CPUID; using exception 16
rd0: fixed, 3800 blocks
ep1 at pcmcia0 function 0 "3Com, Megahertz 574B, B" port 0xa000/32: address
00:01:03:fb:8c:a7
tqphy0 at ep1 phy 0: 78Q2120 10/100 PHY, rev. 10
umass0 at uhub0 port 2 configuration 1 interface
4.5 snapshot fails to detect pcmcia/cardbus adapters
Hi,
I have just tried out the 4.5 snapshot on a laptop, and found that the
cardbus/ethernet adapters I used are no longer detected. Both types had been
working with OpenBSD v4.4.
The laptop had OpenBSD v4.4 installed, and the card was detected as in this
extract.
ep1 at pcmcia0 function 0 "3Com, Megahertz 574B, B" port 0xa000/32: address
00:01:03:fb:8c:a7
tqphy0 at ep1 phy 0: 78Q2120 10/100 PHY, rev. 10
softraid0 at root
root on rd0a swap on rd0b dump on rd0b
I had a second type of card, again the card was detected by v4.4 as below, which
is the same driver type as the internal adapter.
rl1 at cardbus0 dev 0 function 0 "D-Link Systems DFE-690TXD" rev 0x10: irq 11,
address 00:0d:88:29:0d:04
rlphy1 at rl1 phy 0: RTL internal PHY
softraid0 at root
root on rd0a swap on rd0b dump on rd0b
The full dmesg with v4.5 snapshot is below with either card with it is the same,
neither card is being found. The difference between the OpenBSD v4.4 and v4.5
dmesgs are the adapter missing lines in v4.5 plus the expected and this
-cpu0 at mainbus0
-pci0 at mainbus0 bus 0: configuration mode 1 (no bios)
+cpu0 at mainbus0: (uniprocessor)
+pci0 at mainbus0 bus 0: configuration mode 1 (bios)
The following appears in the configuration for GENERIC and RAMDISK_CD, which I
think implies they should be enabled, where do I look next?
ep* at pcmcia? # PCMCIA based 3C5xx ethernet
rl* at cardbus? # RealTek 81[23]9 ethernet
Regards
Nigel Taylor
OpenBSD 4.5 (RAMDISK_CD) #1112: Sat Feb 28 15:06:26 MST 2009
dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/RAMDISK_CD
cpu0: Intel(R) Pentium(R) III Mobile CPU 1000MHz ("GenuineIntel" 686-class) 1
GHz
cpu0:
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE
real mem = 1063743488 (1014MB)
avail mem = 1021931520 (974MB)
mainbus0 at root
bios0 at mainbus0: AT/286+ BIOS, date 07/02/02, BIOS32 rev. 0 @ 0xfd850, SMBIOS
rev. 2.3 @ 0x3f6f (47 entries)
bios0: vendor Phoenix/FUJITSU version "Version 1.06" date 07/02/2002
bios0: FUJITSU SIEMENS LIFEBOOK S Series
apm0 at bios0: Power Management spec V1.2
acpi at bios0 function 0x0 not configured
pcibios0 at bios0: rev 2.1 @ 0xfd850/0x7b0
pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xfdf30/176 (9 entries)
pcibios0: PCI Interrupt Router at 000:31:0 ("Intel 82371FB ISA" rev 0x00)
pcibios0: PCI bus #3 is the last bus
bios0: ROM list: 0xc/0xd200! 0xcd800/0x1000
cpu0 at mainbus0: (uniprocessor)
pci0 at mainbus0 bus 0: configuration mode 1 (bios)
pchb0 at pci0 dev 0 function 0 "Intel 82830M Host" rev 0x04
vga1 at pci0 dev 2 function 0 "Intel 82830M Video" rev 0x04
wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
"Intel 82830M Video" rev 0x00 at pci0 dev 2 function 1 not configured
uhci0 at pci0 dev 29 function 0 "Intel 82801CA/CAM USB" rev 0x02: irq 11
uhci1 at pci0 dev 29 function 1 "Intel 82801CA/CAM USB" rev 0x02: irq 11
ppb0 at pci0 dev 30 function 0 "Intel 82801BAM Hub-to-PCI" rev 0x42
pci1 at ppb0 bus 1
rl0 at pci1 dev 9 function 0 "Realtek 8139" rev 0x10: irq 11, address
00:e0:00:ba:c5:66
rlphy0 at rl0 phy 0: RTL internal PHY
cbb0 at pci1 dev 10 function 0 "O2 Micro OZ6933 CardBus" rev 0x02: irq 11
cbb1 at pci1 dev 10 function 1 "O2 Micro OZ6933 CardBus" rev 0x02: irq 11
"TI TSB43AB21 FireWire" rev 0x00 at pci1 dev 12 function 0 not configured
wi0 at pci1 dev 13 function 0 "Intersil PRISM2.5" rev 0x01: irq 11
wi0: PRISM2.5 ISL3874A(Mini-PCI) (0x8013), Firmware 1.1.0 (primary), 1.4.1
(station), address 00:e0:00:89:12:4e
cardslot0 at cbb0 slot 0 flags 0
cardbus0 at cardslot0: bus 2 device 0 cacheline 0x0, lattimer 0x20
pcmcia0 at cardslot0
cardslot1 at cbb1 slot 1 flags 0
cardbus1 at cardslot1: bus 3 device 0 cacheline 0x0, lattimer 0x20
pcmcia1 at cardslot1
ichpcib0 at pci0 dev 31 function 0 "Intel 82801CAM LPC" rev 0x02: 24-bit timer
at 3579545Hz
pciide0 at pci0 dev 31 function 1 "Intel 82801CAM IDE" rev 0x02: DMA, channel 0
configured to compatibility, channel 1 configured to compatibility
wd0 at pciide0 channel 0 drive 0:
wd0: 16-sector PIO, LBA, 28615MB, 58605120 sectors
wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 5
atapiscsi0 at pciide0 channel 1 drive 0
scsibus0 at atapiscsi0: 2 targets
cd0 at scsibus0 targ 0 lun 0: ATAPI 5/cdrom removable
cd0(pciide0:1:0): using PIO mode 4, Ultra-DMA mode 2
"Intel 82801CA/CAM SMBus" rev 0x02 at pci0 dev 31 function 3 not configured
"Intel 82801CA/CAM AC97" rev 0x02 at pci0 dev 31 function 5 not configured
"Intel 82801CA/CAM Modem" rev 0x02 at pci0 dev 31 function 6 not configured
usb0 at uhci0: USB revision 1.0
uhub0 at usb0 "Intel UHCI root hub" rev 1.00/1.00 addr 1
usb1 at uhci1: USB revision 1.0
uhub1 at usb1 "Intel UHCI root hub" rev 1.00/1.00 addr 1
isa0 at ichpcib0
isadma0 at isa0
com0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo
pckbc0 at isa0 port 0x60/5
pckbd0 at pckbc0 (kbd slot)
pckbc0: using irq 1 for kbd slot
wskbd0 at pckbd0: console keyboard, using wsdisplay0
npx0 at isa0
Re: Root as R/O
Take a look at Live CD or Live DVD methods for OpenBSD, / contains /dev /etc
copies are made in memory file systems (changes to /etc will be lost). Mounting
a read-only / can simply be reversed with mount -u -w /. To make it more
difficult take a look at chflags schg, which make files immutable and can only
be removed in single user mode. Example below, root home directory changed to
/home/root, you can also take a look at securelevel set to 2 instead of 1 in
rc.securelevel
$ grep rc.mfs /etc/rc
[ -f /etc/rc.mfs ] && . /etc/rc.mfs
$ cat /etc/rc.mfs
echo "Copy existing files"
cp /dev/MAKEDEV /home/root/mfssetup
tar czf /home/root/mfssetup/etc.tgz /etc
echo -n "Creating mfs {"
mount -t mfs -o nosuid,-i=128,-s=3000 swap /dev
cp /home/root/mfssetup/MAKEDEV /dev
(cd /dev; ./MAKEDEV all )
echo -n " dev"
mount -t mfs -o nosuid,-s=49152 swap /etc
tar xphzf /home/root/mfssetup/etc.tgz -C /
echo " etc}"
$ mount
/dev/wd0a on / type ffs (local, noatime, read-only, softdep)
/dev/wd0e on /home type ffs (local, nodev, noexec, nosuid, softdep)
/dev/wd0f on /usr type ffs (local, noatime, nodev, read-only, softdep)
/dev/wd0g on /var type ffs (local, nodev, noexec, nosuid, softdep)
/dev/wd0h on /var/log type ffs (local, nodev, noexec, nosuid, softdep)
mfs:18565 on /tmp type mfs (asynchronous, local, noatime, nodev, noexec, nosuid,
size=256000 512-blocks)
mfs:19145 on /var/tmp type mfs (asynchronous, local, noatime, nodev, noexec,
nosuid, size=256000 512-blocks)
mfs:7845 on /dev type mfs (asynchronous, local, nosuid, size=3000 512-blocks)
mfs:25656 on /etc type mfs (asynchronous, local, nosuid, size=49152 512-blocks)
Regards
Nigel Taylor
Bret S. Lambert wrote:
> On Sun, Mar 01, 2009 at 03:03:53PM +0100, Jean-Francois wrote:
>> Janusz,
>>
>> I try to secure a box by forbidding the change to main system files.
>> /dev /etc /tmp /var are on separate slides and would be w/r of course.
>
> If /etc/ is on a seperate partition, how would you read /etc/fstab
> in order to know which disks/partitions to mount under / ?
>
> - Bert
>
>> Le dimanche 01 mars 2009 C 13:15 +0100, Janusz Gumkowski a C)crit :
>>> On Sun, Mar 01, 2009 at 10:18:54AM +0100, Jean-Francois wrote:
Hi All,
One could develop a little bit the addvantage(s) of mounting root as
read only ?
>>> Myself, I don't see any.
>>>
>>> /dev, /etc, /tmp and /var/* are changed a lot during startup or while the
>>> system is running.
>>>
>>> What are you trying do do, exactly?
Re: sftp chroot ?
Hi, You might try a looking at Match in the sshd_config man pages, ChrootDirectory. Something like this in sshd_config, home directories must be root owned if chrooted. This is in Openssh v5.1, not sure when it was introduced. ChrootDirectory %h Subsystem sftpinternal-sftp Match group wheel ChrootDirectory none This defaults to chroot to the home directory, unless users are in the group wheel, you can do this the other way around default is not to chroot, users in a specific group are chrooted. Regards Nigel Taylor Jean-Francois wrote: > Hello, > > If I understand this will chroot any user. Am I correct ? > - Is root chrroted as well ? > - Is it possible to chrrot only some users ? > > I am afraid that is I do this then all users will be chrooted and I > won't be able to turn this back since I will not have access to /etc. > > Line to be changed in sshd_config : > #ChrootDirectory none > > Thanks > JF > > Le lundi 23 fC)vrier 2009 C 19:07 +0100, Floor Terra a C)crit : >> See sshd_config(5) and search for ChrootDirectory. >> >> Floor >> >> On Feb 23, 2009 6:24 PM, "Jean-Francois" >> wrote: >> >> Hi All, >> >> As far as I understand, the sftp service is always running >> since it is >> the ssh daemon (maybe one can correct me if I'm wrong). >> Hence I need to chroot some users to specific directories. >> I prefer not to use vsftp at present time if this feature is >> available >> with sftp of OpenBSD. >> >> One can help me ? >> >> Thank you; >> JF
Re: OPENVAS on OpneBSD [was Re: PCI Compliant Vulnerability Scanner]
Simon, I have nearly completed a port of OpenVAS for OpenBSD. I have it running but a few things to resolve before submitting to the ports. Regards Nigel Taylor Simon Slaytor wrote: > Dorian B|ttner wrote: >> Looking for openvas? >> http://www.derkeiler.com/Mailing-Lists/securityfocus/pen-test/2005-11/0067.html >> >> > I've been looking at OpenVAS has anyone got it working under OpenBSD?
Re: The correct way to use bsd.rd
The RAMDISK_CD kernel bsd in /usr/src/sys/arch/`machine`/compile/RAMDISK_CD is not the same as bsd.rd as you have found out it has an empty ramdisk, it the initial stage, to get a bsd.rd you need to build a release after building the userland. Details for building a release are in the FAQ's and man pages. Building the release will use the RAMDISK_CD to build the kernel in bsd, reserving space for the ramdisk, and then the make release process adds the ramdisk (miniroot) into this creating the bsd.rd. You will find what the build release does under /usr/src/distrib/ramdisk The install / update shells are in /usr/src/distrib/miniroot The resulting bsd.rd created by the release is placed into $DESTDIR/snapshot, and then into the release directory $RELEASEDIR. The RAMDISK - is for the floppynn.fs, RAMDISKB, RAMDISKC for floppynnB.fs, and floppynnC.fs. It all works for building a release, but as pointed out never needed for following current. I build a release so I have an install with all the patches for stable, I can use on a number of machines which use stable, rather than applying the patches on each. If what your are asking is can you just build bsd.rd without building the full release - possibly, maybe setting DESTDIR, RELEASEDIR and a make in /usr/src/distrib/ramdisk might work, really your on your own if your trying to do that. Regards Nigel Taylor Jordi Beltran Creix wrote: > I am NOT trying to boot my root partition using bsd.rd. Although I see > that I can using the -a option. I was trying to get a bsd.rd image > like the one from the CDs, with the Install Upgrade and Shell options. > I followed the instructions from release(8) closely but the generated > binary is the same - it tells me it tries to boot from the ramdisk > device and that it has size 0 and reboots. I don't intend it to use as > a way to upgrade, it is easier to download the newer snapshots, I was > just testing the functionality. I am obviously missing something and > this is why I asked. > I've just downloaded the one from the snapshots and see it is > RAMDISK_CD. Do I need to build the RAMDISK_CD kernel instead of > RAMDISK and it will work? > > Thank you > > 2008/9/28 Stijn <[EMAIL PROTECTED]>: >> Jordi Beltran Creix wrote: >>> I am using a virtual machine to try and follow -CURRENT.I have >>> installed a snapshot, downloaded the cvs source, built it and run to >>> see if it worked, up to there everything is okay. >>> Reading the FAQ I found out that the "official" way to follow current >>> more or less closely is to build a ramdisk image(or download a bsd.rd >>> image from the servers) and boot from that. However, when I place my >>> newly generated image in / and boot from it, it tells me that it lacks >>> a root filesystem. Obviously it is lacking a ramdisk, but I don't know >>> where to get that from and I have been unable to find the appropriate >>> manpage or piece of documentation. Could you please point it out to >>> me? >>> Thank you >>> >>> >>> >>> >> From the FAQ: >> http://openbsd.org/faq/faq4.html#bsd.rd >> >> bsd.rd is used to install, upgrade or doing system maintenance. It's not >> used to boot of your machine for normal usage. >> >> HTH, >> Stijn
Re: security fixes for packages
Daniel Ouellet wrote: Comhte wrote: Ok, so does it mean that -stable or -release are useless ??? and people buy useless CDs every 6 monthes ? I can't believe it. I really don't understand why these fixes are not provided anymore. Then do something about it and start contributing too. May be you will see how painful this is to do when you will actually do something like that and then have big mouth clueless guys like you acting like you do now complaining about your freely given time to the project and thankless users like you. If I want a fix or later version of a package for stable, I just take the current port from CVS, and build for stable v4.3, here is a small list of those successfully built ports. bzip2-1.0.5 clamav-0.93 firefox-i18n-en-GB-2.0.0.14 gnupg-1.4.9 mozilla-firefox-2.0.0.14 nmap-4.60 pgadmin3-1.8.2 postgresql-client-8.3.1 postgresql-server-8.3.1 qemu-0.9.1 kqemu-1.3.0pre11p2 Not all will build, many will. Quite agree don't complain either contribute or do it yourself. They give you their time and you have the guts to complain and asked them to do more then they already do freely and on their own time!? No wonder that they do less and less in some special cases like this. Keep complaining and may be one day it will simply not be available at all anymore. Then what will you do... Apologies then? i don't want to go back to Debian... ;) No one stop you by the way and I am sure you will not be miss either with your ungrateful attitude. With all due respect, you should think before you write this one, really. It is given free out of goodwill to you and you think you deserved more? Regards, Daniel Regards Nigel Taylor
Re: problems passing radius traffic through pf
You haven't really supplied enough information, the full pf.conf and
firewall ip addresses would have been better. This is a slight guess at
whats wrong.
You say the request is from access point to radius server I would expect
to see a rule like this in your pf.conf
pass in on $ proto udp from 10.50.3.11 to 172.30.30.5 port 1812
The pass rules keeps the state, allowing the return udp traffic. What
your seeing is blocked return udp traffic, because the udp state is
established in the opposite direction, the pass is ignored. Looks like
you have the rule on the wrong interface also. The other interfaces are
missing as full pf.conf not supplied. You might have to pass port 1813
also replacing 1812 by { 1812, 1813 }.
Regards
Nigel Taylor
[EMAIL PROTECTED] wrote:
> I have a Domain Controller in a DMZ which is handling radius requests from
> my access point. I'm having problems passing the radius information
> successfully through pf. The pf box is a soekris running 4.1.
>
> Mar 09 09:58:56.467664 rule 3/(match) block in on sis4: 172.30.30.5.1812 >
> 10.50.3.11.2055: Axs! id:1 [1477] [|radius] (frag 25868:[EMAIL PROTECTED])
> Mar 09 09:58:56.467745 rule 3/(match) block in on sis4: 172.30.30.5 >
> 10.50.3.11: (frag 25868:[EMAIL PROTECTED])
>
> # more /etc/pf.conf | grep pix_if
> pix_if = "sis4"
> pass quick log on $pix_if from any to 10.50.3.11
> block in log on $pix_if
> pass out on $pix_if
>
> In this case, 172.30.30.5 is my radius server, and 10.50.3.11 is my access
> point. Even though I am logging the pass rule, I do not seeing getting
> hit through tcpdump. If I take out the block in log on $pix_if, radius
> information flows ok.
>
> Thanks,
>
> runelind at runelind dot net
Re: How can I build a release without writing into the /usr/src tree?
I do not use /usr/src or /usr/obj myself instead I use /builds/src etc. The way I do this is having a /etc/mk.conf file like this. PIPE=-pipe BSDOBJDIR=/builds/obj BSDSRCDIR=/builds/src XENOCARA_OBJDIR=/builds/Xobj XOBJDIR=/builds/Xobj XENOCARA_TOP=/builds/xenocara XSRCDIR=/builds/xenocara WRKOBJDIR=/builds/pobj PORTSDIR=/builds/ports DISTDIR=/builds/distfiles PACKAGE_REPOSITORY=/builds/packages Look at the man page for mk.conf and make your own. Regards Nigel Taylor Don Jackson wrote: > Hello, > > I try to studiously follow the "STABLE" branch. > > I carefully follow the directions in the FAQ. > > When I build my new kernel, I use the alternate instructions: > >Variation on above process: Read-only source tree > >Sometimes, you may wish to ensure your /usr/src/sys directory > remains untouched. >This can be done by using the following process: > >$ cd /somewhere >$ cp /usr/src/sys/arch/i386/conf/GENERIC . >$ config -s /usr/src/sys -b . GENERIC >$ make clean && make depend && make > ... lots of output ... > > After building my new kernel, I reboot, build userland, reboot, and > then go to build a release. > > In the build process for a release ( make release ), at some point, > here is what happens: > >cd /home/openbsd/4.1/src/etc/../sys/arch/amd64/conf && config GENERIC >config: cannot create ../compile/GENERIC: Permission denied >*** Error code 2 > >Stop in /home/openbsd/4.1/src/etc (line 11 of etc.amd64/Makefile.inc). > > (FYI, /usr/src -> /home/openbsd/4.1/src ) > > Looks like make release is trying to build a new kernel in my /usr/src > tree. > > 1) Is there a way to get make release to NOT build a new kernel inside > my source tree? > > 2) Actually, I have already built a GENERIC kernel anyway, it would be > very nice >if "make release" would be able to figure that out, and just use > the already built >GENERIC kernel. I understand it will still need to build bsd.mp, > bsd.rd, etc., >but hopefully it would build those outside the source tree also. > > Don
Re: Trouble compiling 3.9 kernel on a 3.8 system
Look at the "build a kernel" thread in the misc@openbsd.org mail lists (2006-05-02) http://marc.theaimsgroup.com/?l=openbsd-misc&m=114657146711212&w=2 Regards Nigel Taylor Jason Murray wrote: > First off why am I doing this? Because I use RaidFrame and the upgrade I > need the raid psuedo device compiled into the kernel. I have > successfully used this approach to move from 3.6->3.7->3.8. I was hoping > to use this to move to 3.9. > > Yes I've searched the web for answers. I can't find anything obviously > wrong. > > I've downloaded the 3.9 src.tar.gz and sys.tar.gz and expandeded them. > > Anyway on to the problem. Any ideas why this is happening? Thanks in > advance. > > #cd /usr/src/sys/arch/i386/compile/GENERIC > #make depend > . > . > . > cp /usr/src/sys/arch/i386/compile/GENERIC/../../../../conf/param.c . > sh /usr/src/sys/arch/i386/compile/GENERIC/../../../../kern/genassym.sh > cc -Werror -Wall -Wstrict-prototypes -Wmissing-prototypes > -Wno-uninitialized -Wno-format -Wno-main -fno-builtin-printf > -fno-builtin-log -O2 -pipe -nostdinc -I. > -I/usr/src/sys/arch/i386/compile/GENERIC/../../../../arch > -I/usr/src/sys/arch/i386/compile/GENERIC/../../../.. -DDDB -DDIAGNOSTIC > -DKTRACE -DACCOUNTING -DKMEMSTATS -DPTRACE -DCRYPTO -DSYSVMSG -DSYSVSEM > -DSYSVSHM -DUVM_SWAP_ENCRYPT -DCOMPAT_35 -DCOMPAT_43 -DLKM -DFFS > -DFFS_SOFTUPDATES -DUFS_DIRHASH -DQUOTA -DEXT2FS -DMFS -DXFS -DTCP_SACK > -DTCP_ECN -DTCP_SIGNATURE -DNFSCLIENT -DNFSSERVER -DCD9660 -DUDF > -DMSDOSFS -DFIFO -DPORTAL -DINET -DALTQ -DINET6 -DIPSEC -DPPP_BSDCOMP > -DPPP_DEFLATE -DMROUTING -DBOOT_CONFIG -DI386_CPU -DI486_CPU -DI586_CPU > -DI686_CPU -DUSER_PCICONF -DUSER_LDT -DAPERTURE -DCOMPAT_SVR4 > -DCOMPAT_IBCS2 -DCOMPAT_LINUX -DCOMPAT_FREEBSD -DCOMPAT_BSDOS > -DCOMPAT_AOUT -DPROCFS -DACPIVERBOSE -DPCIVERBOSE -DEISAVERBOSE > -DUSBVERBOSE -DWSDISPLAY_COMPAT_USL -DWSDISPLAY_COMPAT_RAWKBD > -DWSDISPLAY_DEFAULTSCREENS="6" -DWSDISPLAY_COMPAT_PCVT -DPCIAGP > -D_KERNEL -Di386 -DMAXUSERS=32 < > /usr/src/sys/arch/i386/compile/GENERIC/../../../../arch/i386/i386/genassym.cf >> assym.h.tmp && mv -f assym.h.tmp assym.h > In file included from /usr/src/sys/uvm/uvm_map.h:392, > from /usr/src/sys/uvm/uvm_extern.h:380, > from /usr/src/sys/sys/user.h:45, > from /tmp/genassym_c.UYmDD23251:9: > /usr/src/sys/sys/systm.h:163: warning: conflicting types for built-in > function `vsnprintf' > /usr/src/sys/sys/systm.h:165: warning: conflicting types for built-in > function `snprintf' > /usr/src/sys/sys/systm.h:190: warning: conflicting types for built-in > function `memcpy' > /usr/src/sys/sys/systm.h:195: warning: conflicting types for built-in > function `memset' > In file included from /usr/src/sys/sys/systm.h:303, > from /usr/src/sys/uvm/uvm_map.h:392, > from /usr/src/sys/uvm/uvm_extern.h:380, > from /usr/src/sys/sys/user.h:45, > from /tmp/genassym_c.UYmDD23251:9: > /usr/src/sys/lib/libkern/libkern.h:158: warning: conflicting types for > built-in function `memcmp' > /usr/src/sys/lib/libkern/libkern.h:165: warning: conflicting types for > built-in function `strncpy' > /usr/src/sys/lib/libkern/libkern.h:171: warning: conflicting types for > built-in function `strncmp' > *** Error code 1 > > Stop in /usr/src/sys/arch/i386/compile/GENERIC (line 691 of Makefile).
Re: build a kernel
Compiling 3.9 under 3.8 is not supported, upgrade to 3.9 and build under 3.9. http://www.openbsd.org/faq/faq5.html Step 1, in Building OpenBSD from Source is Upgrading to the closest available binary. It is possible to resolve errors below and build 3.9 under 3.8, but takes some work, you have only hit the first of many problems you will hit, and may not get much help. Do the upgrade to 3.9 from CD and save yourself the trouble. Regards Nigel holger glaess wrote: > hi > > i did an cvsup from 38 to 3.9 then everthing was documented ( cd > /usr/src/sys/arch/i386/conf ; config GENERIC ; cd ../compile/GENERIC ; make > depend ) > to make shure if i did somthing wrong i got the whole source by ftp > (src.tar.gz and sys.tar.gz ) for 3.9 > > and get on both this error ! > any clue for me ? > > holger > > # make depend > mkdir -p /usr/src/sys/arch/i386/compile/GENERIC/lib/kern > depending the kern library objects > depending the compat library objects > sh /usr/src/sys/arch/i386/compile/GENERIC/../../../../kern/genassym.sh cc > -Werror -Wall -Wstrict-prototypes -Wmissing-prototypes -Wno-uninitialized > -Wno-format -Wno-main -fno-builtin-printf -fno-builtin-log -O2 -pipe > -nostdinc -I. -I/usr/src/sys/arch/i386/compile/GENERIC/../../../../arch > -I/usr/src/sys/arch/i386/compile/GENERIC/../../../.. -DDDB -DDIAGNOSTIC > -DKTRACE -DACCOUNTING -DKMEMSTATS -DPTRACE -DCRYPTO -DSYSVMSG -DSYSVSEM > -DSYSVSHM -DUVM_SWAP_ENCRYPT -DCOMPAT_35 -DCOMPAT_43 -DLKM -DFFS > -DFFS_SOFTUPDATES -DUFS_DIRHASH -DQUOTA -DEXT2FS -DMFS -DXFS -DTCP_SACK > -DTCP_ECN -DTCP_SIGNATURE -DNFSCLIENT -DNFSSERVER -DCD9660 -DUDF -DMSDOSFS > -DFIFO -DPORTAL -DINET -DALTQ -DINET6 -DIPSEC -DPPP_BSDCOMP -DPPP_DEFLATE > -DMROUTING -DBOOT_CONFIG -DI386_CPU -DI486_CPU -DI586_CPU -DI686_CPU > -DUSER_PCICONF -DUSER_LDT -DAPERTURE -DCOMPAT_SVR4 -DCOMPAT_IBCS2 > -DCOMPAT_LINUX -DCOMPAT_FREEBSD -DCOMPAT_BSDOS -DCOMPAT_AOUT -DPROCFS > -DACPIVERBOSE -DPCIVERBOSE -DEISAVERBOSE -DUSBVERBOSE -DWSDI SP! > LAY_COMPAT_USL -DWSDISPLAY_COMPAT_RAWKBD -DWSDISPLAY_DEFAULTSCREENS="6" > -DWSDISPLAY_COMPAT_PCVT -DPCIAGP -D_KERNEL -Di386 -DMAXUSERS=32 < > /usr/src/sys/arch/i386/compile/GENERIC/../../../../arch/i386/i386/genassym.cf > > assym.h.tmp && mv -f assym.h.tmp assym.h > In file included from /usr/src/sys/uvm/uvm_map.h:392, > from /usr/src/sys/uvm/uvm_extern.h:380, > from /usr/src/sys/sys/user.h:45, > from /tmp/genassym_c.nXGRIw9116:9: > /usr/src/sys/sys/systm.h:163: warning: conflicting types for built-in > function `vsnprintf' > /usr/src/sys/sys/systm.h:165: warning: conflicting types for built-in > function `snprintf' > /usr/src/sys/sys/systm.h:190: warning: conflicting types for built-in > function `memcpy' > /usr/src/sys/sys/systm.h:195: warning: conflicting types for built-in > function `memset' > In file included from /usr/src/sys/sys/systm.h:303, > from /usr/src/sys/uvm/uvm_map.h:392, > from /usr/src/sys/uvm/uvm_extern.h:380, > from /usr/src/sys/sys/user.h:45, > from /tmp/genassym_c.nXGRIw9116:9: > /usr/src/sys/lib/libkern/libkern.h:158: warning: conflicting types for > built-in function `memcmp' > /usr/src/sys/lib/libkern/libkern.h:165: warning: conflicting types for > built-in function `strncpy' > /usr/src/sys/lib/libkern/libkern.h:171: warning: conflicting types for > built-in function `strncmp' > *** Error code 1 > > Stop in /usr/src/sys/arch/i386/compile/GENERIC (line 691 of Makefile). > #
Re: 3.9 Release Available
Some minor things I noticed, the following is still at 3.8 http://www.openbsd.org/pkg-stable.html http://www.openbsd.org/errata38.html should link to a http://www.openbsd.org/pkg-stable38.html, rather than the above. As an example in pkg-stable.html the package clamav-0.88.1.tgz only exists for 3.7, 3.8 and current. 3.9 only has clamav-0.88.tgz available. There appears to be an issue here also with the CVS ports tree, as clamav has been updated to 0.88.1 for 3.7, 3.8 stable and current is now at 0.88.2, while 3.9 stable has been left at version 0.88. gnupg also appears to have been left behind at version 1.4.2.1 for 3.9 in CVS while 3.8 moved on to 1.4.2.2 and current is at 1.4.3. Both these are in the ports/security CVS tree. Regards Nigel Bob Beck wrote: > > May 1, 2006. > > We are pleased to announce the official release of OpenBSD 3.9. > This is our 19th release on CD-ROM (and 18th via FTP). We remain > proud of OpenBSD's record of eight years with only a single remote > hole in the default install. As in our previous releases, 3.9 > provides significant improvements, including new features, in nearly > all areas of the system: > > - Improved hardware support, including: > o Some G5-based Apple Macintosh machines, including W^X support (currently > restricted to 32-bit mode). > o Many more audio drivers in the OpenBSD/macppc port. > o Support for many system sensors (temperature, voltage, fan speed) via > the following subsystems: > o Dell's Embedded Server Management (esm) > o Intelligent Platform Management Interface (ipmi) > o I2C/SMBus sensor subsystems found on most motherboards (iic) > o Touchpad on recent Apple laptops (tpms). > o nfe, a binary blob free driver for the NVIDIA nForce Ethernet interface. > o Opteron systems now have all their PCI buses detected. > o CardBus and PCMCIA support on OpenBSD/amd64. > o ixgb, Intel PRO/10GbE Ethernet. > o Support for new Intel i82571, i82572 and i82573 PCI Express based > devices > in the em(4) driver. > o Support for new Broadcom BCM5714, BCM5715 and BCM5903M based devices in > the bge(4) driver. > o Support for new Ralink RT2501 and RT2600 based devices in ral. > o Support for ASIX AX88178 Gigabit and AX88772 10/100 based devices > in axe(4). > o Support for devices incorporating GCT RF transceivers in rtw. > o Zaurus remote control (zrc) support. > o Initial Sound Blaster Audigy support in the emu(4) driver. > o The Level 1 LXT1001 Gigabit driver has been fixed and now works > (lge(4)). > o More HP Smart ARRAY controllers recognized by the ciss(4) driver. > o Support the Intel i915 AGP. > o Support for both older and newer IDE and SATA controllers in the > pciide(4) driver, including: > o ATI's IXP 200/300/400 IDE controllers > o Broadcom's ServerWorks HT-1000 IDE controller > o a few older Intel PIIX IDE controllers > o Broadcom's ServerWorks K2 and HT-1000 SATA controllers > o VIA's VT6410 and VT8251 SATA controllers > o some newer NVIDIA SATA controllers > o Added IBSS support to the iwi(4) driver. > o Added bus_dma support to the de(4) and san(4) drivers. > o A lot of fixes and improvements to the uaudio(4) audio driver. > o Support for the SMC SMC91C1xx Ethernet chips in the sm(4) driver as well > as MII support. > o New adb(4) and framebuffer (macfb(4)) drivers on OpenBSD/mac68k, plus > switch to wscons(4). > > - New tools: > o ftp-proxy(8) has been rewritten, and a tftp version, tftp-proxy, > has been added. > o sdiff(1), a side-by-side file comparison tool, rewritten by us. > o getent(1), a tool to get entries from the administrative databases. > > - New functionality: > o ancontrol functionality has been completely merged into ifconfig. > o apmd(8) can be used to increase or decrease CPU speed automatically, > depending on CPU usage and, if supported, battery status. > o nc(1) now supports HTTP Proxy authentication, making it very useful as > a ssh ProxyCommand. > o Userland ppp(8) has IPv6 support. > o A number of fixes and new functionality for trunk(4): > o New active/passive failover mode > o Fixed multicast support, for carp(4) and pfsync(4) over trunk > interfaces. > o Interface capabilities depending on the trunk ports, for > full-size vlan(4) MTUs. > o Improved functionality for ipsecctl(8). > o Added multicast routing to GENERIC. It is now possible to enable > multicast routing in the kernel with the > sysctl(8) option net.inet.ip.mforwarding=1. > o It is now possible to set a default vlan(4) priority via ifconfig(8). > > - Assorted improvements and code cleanup: > o libpcap has been upd
