Re: Installing OpenBSD on SSD drives
2009/11/6 Jean-Frangois SIMON > 2009/11/6 > >> Quoting Jean-Frangois SIMON : >> >> >> [cut] >> >> > The error actually appears while installing xfont46.tgz which is very >> > very >> > slow. It is normal speed util that particular file . >> > errors : many "atascsi_atapi_cmd_done, timeout" >> > one "d0(ahci0:3:0): Check Condition (error 0x70) on opcode 0x28 >> > SENSE KEY: Illegal Request" >> >> Are you installing from CD - is the CD medium and the CD/DVD drive >> definitely good? >> >> It might be a dumb question, but is it DEFINITELY the SSD at fault here? >> >> Thanks. >> > > Hi, > I tried booting on the CD from another device but it happened to do the > same thing. > > There is no evidence that the SSD is the root cause but I assume because > all other operating systems works fine on that machine, and the SSD is the > only exotic thing in, also it just makes some errors on the disk while > installing so I assume the disk is at fault. > > I will try to install on a standard drive see if there is any problem. > > Regards > It appears to go the same way on a normal hard drive. I will try various things tonight. Reagrds
Re: Installing OpenBSD on SSD drives
2009/11/6 > Quoting Jean-Frangois SIMON : > > [cut] > > > The error actually appears wjile installing xfont46.tgz which is very > > very > > slow. It is normal speed util that particular file . > > errors : many "atascsi_atapi_cmd_done, timeout" > > one "d0(ahci0:3:0): Check Condition (error 0x70) on opcode 0x28 > > SENSE KEY: Illegal Request" > > Are you installing from CD - is the CD medium and the CD/DVD drive > definitely good? > > It might be a dumb question, but is it DEFINITELY the SSD at fault here? > > Thanks. > Hi, I tried booting on the CD from another device but it happened to do the same thing. There is no evidence that the SSD is the root cause but I assume because all other operating systems works fine on that machine, and the SSD is the only exotic thing in, also it just makes some errors on the disk while installing so I assume the disk is at fault. I will try to install on a standard drive see if there is any problem. Regards
Re: rum wireless adapter in hostap mode
On Thu, Nov 5, 2009 at 20:00, Hugo Osvaldo Barrera wrote: > I'm trying to set up a small box as an 802.11g AP, but there seems to > be something wrong. > Regrettably, the only devices close by I have to test the connection are > -A Windows XP PC > -A Windows 7 PC > -A PSP > I'm pretty sure the problem isn't any of the clients anyway. > For testing purposes, I'm running a totally insecure network. I'll add > the WPA stuff later. > > When I try to connect from the PSP I get an error message saying > "Check the security settings for the network and try again". It DOES > auto-detect is as "security:none" though. > When I try to connect from one of the windows PC, I get the typical > really helpful message saying "Could not connect to the network" > ehci_idone: ex=0x801f7600 is done! > ehci_idone: ex=0x802aaa00 is done! > > RTFM: http://www.openbsd.org/cgi-bin/man.cgi?query=rum&apropos=0&sektion=0&manpath=OpenBSD+Current&arch=i386&format=html I like the part that says: The rum driver supports automatic control of the transmit speed in BSS mode only. Therefore the use of a rum adapter in Host AP mode is dis- couraged. Host AP mode doesn't support power saving. Clients attempting to use power saving mode may experience significant packet loss (disabling power saving on the client will fix this).
Re: Xorg Fails to start.
On Fri, Nov 6, 2009 at 2:55 AM, Steven
wrote:
> Hi,
>
> I'm unable to get Xorg to start any more on my computer since about
> three, or four snapshots ago. I'm not desperate for a GUI, but it
> would be nice. Fails whether machdep.allowaperture is set to 1, or
> 2.
It looks like /dev/pci* devices are setup incorrectly. re-run MAKEDEV
The devices should look like:
lrwx-- 1 root wheel 4 Jul 4 19:10 /dev/pci -> pci0
crw--- 1 root wheel 72, 0 Jul 18 10:29 /dev/pci0
crw--- 1 root wheel 72, 1 Jul 18 10:29 /dev/pci1
crw--- 1 root wheel 72, 2 Jul 18 10:29 /dev/pci2
crw--- 1 root wheel 72, 3 Jul 18 10:29 /dev/pci3
>
> dmesg, /etc/X11/xorg.conf and Xorg.0.log outputs follow.
> machdep.allowaperture set to 2.
>
> OpenBSD 4.6-current (GENERIC) #353: Mon Nov 2 10:58:43 MST 2009
>dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC
> cpu0: AMD Athlon(tm) processor ("AuthenticAMD" 686-class, 256KB L2 cache)
> 1.20 GHz
> cpu0:
> FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR
> real mem = 804810752 (767MB)
> avail mem = 771358720 (735MB)
> mainbus0 at root
> bios0 at mainbus0: AT/286+ BIOS, date 07/13/01, BIOS32 rev. 0 @ 0xfb5d0,
> SMBIOS rev. 2.2 @ 0xf0800 (38 entries)
> bios0: vendor Award Software International, Inc. version "6.00 PG" date
> 07/13/2001
> bios0: Gigabyte Technology Co., LTD 7DXR
> apm at bios0 function 0x15 not configured
> acpi0 at bios0: rev 0
> acpi0: tables DSDT FACP
> acpi0: wakeup devices SLPB(S5) PCI0(S5) USB0(S4) USB1(S4) UAR1(S4)
> acpitimer0 at acpi0: 3579545 Hz, 24 bits
> acpiprt0 at acpi0: bus 0 (PCI0)
> acpicpu0 at acpi0
> acpibtn0 at acpi0: PWRB
> acpibtn1 at acpi0: SLPB
> bios0: ROM list: 0xc/0x8000 0xcc000/0x4000! 0xd/0x4000
> cpu0 at mainbus0: (uniprocessor)
> pci0 at mainbus0 bus 0: configuration mode 1 (bios)
> pchb0 at pci0 dev 0 function 0 "AMD 761 PCI" rev 0x13
> amdagp0 at pchb0
> agp0 at amdagp0: aperture at 0xd000, size 0x400
> ppb0 at pci0 dev 1 function 0 "AMD 761 PCI-PCI" rev 0x00
> pci1 at ppb0 bus 1
> vga1 at pci1 dev 5 function 0 "ATI Mach64" rev 0x27
> wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
> wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
> pcib0 at pci0 dev 7 function 0 "VIA VT82C686 ISA" rev 0x40
> pciide0 at pci0 dev 7 function 1 "VIA VT82C571 IDE" rev 0x06: ATA100,
> channel 0 configured to compatibility, channel 1 configured to
compatibility
> wd0 at pciide0 channel 0 drive 0:
> wd0: 16-sector PIO, LBA, 78167MB, 160086528 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
> atapiscsi1 at pciide0 channel 1 drive 1
> scsibus1 at atapiscsi1: 2 targets
> cd1 at scsibus1 targ 0 lun 0: ATAPI 5/cdrom
> removable
> cd0(pciide0:1:0): using PIO mode 4, DMA mode 2
> cd1(pciide0:1:1): using PIO mode 4, Ultra-DMA mode 2
> uhci0 at pci0 dev 7 function 2 "VIA VT83C572 USB" rev 0x1a: irq 11
> uhci1 at pci0 dev 7 function 3 "VIA VT83C572 USB" rev 0x1a: irq 11
> viaenv0 at pci0 dev 7 function 4 "VIA VT82C686 SMBus" rev 0x40: can't map
PM
> i/o space
> rl0 at pci0 dev 12 function 0 "D-Link Systems 530TX+" rev 0x10: irq 10,
> address 00:50:ba:59:24:c3
> rlphy0 at rl0 phy 0: RTL internal PHY
> eap0 at pci0 dev 14 function 0 "Ensoniq CT5880" rev 0x03: irq 5
> ac97: codec id 0x83847608 (SigmaTel STAC9708/11)
> ac97: codec features 18 bit DAC, 18 bit ADC, SigmaTel 3D
> audio0 at eap0
> midi0 at eap0:
> uhci2 at pci0 dev 15 function 0 "VIA VT83C572 USB" rev 0x50: irq 11
> uhci3 at pci0 dev 15 function 1 "VIA VT83C572 USB" rev 0x50: irq 10
> ehci0 at pci0 dev 15 function 2 "VIA VT6202 USB" rev 0x51: irq 7
> usb0 at ehci0: USB revision 2.0
> uhub0 at usb0 "VIA EHCI root hub" rev 2.00/1.00 addr 1
> pciide1 at pci0 dev 16 function 0 "Promise PDC20265" rev 0x02: DMA, channel
> 0 configured to native-PCI, channel 1 configured to native-PCI
> pciide1: using irq 11 for native-PCI interrupt
> pciide1: channel 0 disabled (no drives)
> pciide1: channel 1 disabled (no drives)
> isa0 at pcib0
> isadma0 at isa0
> 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
> pcppi0 at isa0 port 0x61
> midi1 at pcppi0:
> spkr0 at pcppi0
> 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
> usb1 at uhci0: USB revision 1.0
> uhub1 at usb1 "VIA UHCI root hub" rev 1.00/1.00 addr 1
> usb2 at uhci1: USB revision 1.0
> uhub2 at usb2 "VIA UHCI root hub" rev 1.00/1.00 addr 1
> usb3 at uhci2: USB revision 1.0
> uhub3 at usb3 "VIA UHCI root hub" rev 1.00/1.00 addr 1
> usb4 at uhci3: USB revision 1.0
> uhub4 at usb4 "VIA UHCI root hub" rev 1.00/1.00 addr 1
> biomask fddd netmask fddd ttymask ffdf
> mtrr: Pentium Pro MTRR support
>
Re: Installing OpenBSD on SSD drives
> 2009/11/5 Jean-Frangois SIMON : > > Hello, > > Is there any particular problem with installing OpenBSD on a SSD HD ? > > I've been using flash based SSD's in OpenBSD systems for 6 or 7 years, > starting with small CF in firewalls and now SATA SSD's in desktops and > laptops. > > Never had a problem installing to them and never had one go bad. I > just use noatime, softdep and no swap (but I guess looking at the > opinions of devs here, no swap is now just a bad habit). As a result of your luck, tomorrow you will be hit by a bus. Or so say the internet-surfing drama queens on our mailing lists.
Re: Installing OpenBSD on SSD drives
2009/11/6 > Quoting Jean-Frangois SIMON : > > [cut] > > > The error actually appears wjile installing xfont46.tgz which is very > > very > > slow. It is normal speed util that particular file . > > errors : many "atascsi_atapi_cmd_done, timeout" > > one "d0(ahci0:3:0): Check Condition (error 0x70) on opcode 0x28 > > SENSE KEY: Illegal Request" > > Are you installing from CD - is the CD medium and the CD/DVD drive > definitely good? > > It might be a dumb question, but is it DEFINITELY the SSD at fault here? > > Thanks. > > This is JUST what I was about to reply. Additionally, can you install onto some other disk on the same PC, (an HDD), to make sure it's not some other component? (Yes, I realize it sounds silly, but it's still something you ought to try). (Sorry Richard for sending this just to you the first time, instead of the misc@, my mistake)
rum wireless adapter in hostap mode
I'm trying to set up a small box as an 802.11g AP, but there seems to be something wrong. Regrettably, the only devices close by I have to test the connection are -A Windows XP PC -A Windows 7 PC -A PSP I'm pretty sure the problem isn't any of the clients anyway. For testing purposes, I'm running a totally insecure network. I'll add the WPA stuff later. When I try to connect from the PSP I get an error message saying "Check the security settings for the network and try again". It DOES auto-detect is as "security:none" though. When I try to connect from one of the windows PC, I get the typical really helpful message saying "Could not connect to the network" Network card is a D-Link DWA-110. It's an Atom-based mini-ITX PC. This is my configuration (Hope I didn't leave anything out): # ifconfig rum0 rum0: flags=8843 mtu 1500 lladdr 00:22:b0:54:21:0b priority: 4 groups: wlan media: IEEE802.11 autoselect mode 11g hostap status: active ieee80211: nwid CasaDeHugo chan 11 bssid 00:22:b0:54:21:0b 100dBm inet6 fe80::222:b0ff:fe54:210b%rum0 prefixlen 64 scopeid 0x4 inet 172.16.0.1 netmask 0x broadcast 172.16.0.255 # cat /etc/hostname.rum0 # /etc/hostname.rum0 inet 172.16.0.1 255.255.0.0 172.16.0.255 media autoselect mediaopt hostap mode 11g chan 11 nwid CasaDeHugo Comment: I've tried with the "-wpa -wpapsk" as well, just in case, though I believe it's not really necessary if I haven't used WPA just before Also, I HAVE run # sh /etc/netstart rum0 after editing the file (just in case :D) # dmesg OpenBSD 4.6 (GENERIC.MP) #81: Thu Jul 9 21:26:19 MDT 2009 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 2135109632 (2036MB) avail mem = 2060738560 (1965MB) RTC BIOS diagnostic error 80 mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.4 @ 0xe3590 (23 entries) bios0: vendor Intel Corp. version "LF94510J.86A.0140.2008.1231.0012" date 12/31/2008 bios0: Intel Corporation D945GCLF2D acpi0 at bios0: rev 0 acpi0: tables DSDT FACP APIC WDDT MCFG ASF! acpi0: wakeup devices SLPB(S4) P32_(S4) UAR1(S4) UAR2(S4) PEX0(S4) PEX1(S4) PEX2(S4) PEX3(S4) PEX4(S4) PEX5(S4) UHC1(S3) UHC2(S3) UHC3(S3) UHC4(S3) EHCI(S3) AC9M(S4) AZAL(S4) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Atom(TM) CPU 330 @ 1.60GHz, 1596.36 MHz cpu0: FPU,VME,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,DS-CPL,TM2,CX16,xTPR,NXE,LONG cpu0: 512KB 64b/line 16-way L2 cache cpu0: apic clock running at 134MHz cpu1 at mainbus0: apid 2 (application processor) cpu1: Intel(R) Atom(TM) CPU 330 @ 1.60GHz, 1612.08 MHz cpu1: FPU,VME,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,DS-CPL,TM2,CX16,xTPR,NXE,LONG cpu1: 512KB 64b/line 16-way L2 cache cpu2 at mainbus0: apid 1 (application processor) cpu2: Intel(R) Atom(TM) CPU 330 @ 1.60GHz, 1612.08 MHz cpu2: FPU,VME,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,DS-CPL,TM2,CX16,xTPR,NXE,LONG cpu2: 512KB 64b/line 16-way L2 cache cpu3 at mainbus0: apid 3 (application processor) cpu3: Intel(R) Atom(TM) CPU 330 @ 1.60GHz, 1612.08 MHz cpu3: FPU,VME,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,DS-CPL,TM2,CX16,xTPR,NXE,LONG cpu3: 512KB 64b/line 16-way L2 cache ioapic0 at mainbus0 apid 2 pa 0xfec0, version 20, 24 pins ioapic0: misconfigured as apic 0, remapped to apid 2 acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus 4 (P32_) acpiprt2 at acpi0: bus 1 (PEX0) acpiprt3 at acpi0: bus -1 (PEX1) acpiprt4 at acpi0: bus 2 (PEX2) acpiprt5 at acpi0: bus 3 (PEX3) acpiprt6 at acpi0: bus -1 (PEX4) acpiprt7 at acpi0: bus -1 (PEX5) acpicpu0 at acpi0 acpicpu1 at acpi0 acpicpu2 at acpi0 acpicpu3 at acpi0 acpibtn0 at acpi0: SLPB pci0 at mainbus0 bus 0 pchb0 at pci0 dev 0 function 0 "Intel 82945G Host" rev 0x02 vga1 at pci0 dev 2 function 0 "Intel 82945G Video" rev 0x02 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 0x8000, size 0x1000 inteldrm0 at vga1: apic 2 int 16 (irq 11) drm0 at inteldrm0 ppb0 at pci0 dev 28 function 0 "Intel 82801GB PCIE" rev 0x01: apic 2 int 17 (irq 255) pci1 at ppb0 bus 1 re0 at pci1 dev 0 function 0 "Realtek 8168" rev 0x02: RTL8168C/8111C (0x3c00), apic 2 int 16 (irq 11), address 00:1c:c0:c8:ce:49 rgephy0 at re0 phy 7: RTL8169S/8110S PHY, rev. 2 ppb1 at pci0 dev 28 function 2 "Intel 82801GB PCIE" rev 0x01: apic 2 int 18 (irq 255) pci2 at ppb1 bus 2 ppb2 at pci0 dev 28 function 3 "Intel 82801GB PCIE" rev 0x01: apic 2 int 19 (irq 255) pci3 at ppb2 bus 3 uhci0 at pci0 dev 29 function 0 "Intel 82801GB USB" rev 0x01: apic 2 i
Re: http://www.theregister.co.uk/2009/11/03/linux_kernel_vulnerability/
2009/11/5 Tobias Ulmer : > Dear sweetheart, > > On Thu, Nov 05, 2009 at 01:12:58AM +0100, Claire beuserie wrote: >> Yes, I know, I was present in the room when Illja gave the talk in 2006 at >> the CCC Kongress and the two OpenBSD developers in the room decided to >> completely ignore the exploit he showed until Miod reproduced it two weeks >> later... > > > http://events.ccc.de/congress/2006/Fahrplan/day_4.en.html: > Schedule Day 4: 30.12.2006 > 11:30 > Unusual bugs Ilja > > http://openbsd.org/errata39.html: > 017: SECURITY FIX: January 3, 2007 i386 only > Insufficient validation in vga(4) may allow an attacker to gain root > privileges if the kernel is compiled with option PCIAGP and the actual > device is not an AGP device. The PCIAGP option is present by default on > i386 kernels only. > > http://blogs.23.nu/ilja/2007/01/: > "So one of the things I noticed after my unusual bugs talk, the OpenBSD > guys fix bugs _FAST_. I mean really fast ! bugfix and announcement > within a few days. Not many vendors can pull that off." > > Two weeks, eh? Want it in a black frame with a white caption > reading "EPIC FAIL"? I'd start gimp for that. Way ahead of you here: http://imgur.com/f5UZ9.jpg
Re: Installing OpenBSD on SSD drives
Quoting Jean-Frangois SIMON : [cut] > The error actually appears wjile installing xfont46.tgz which is very > very > slow. It is normal speed util that particular file . > errors : many "atascsi_atapi_cmd_done, timeout" > one "d0(ahci0:3:0): Check Condition (error 0x70) on opcode 0x28 > SENSE KEY: Illegal Request" Are you installing from CD - is the CD medium and the CD/DVD drive definitely good? It might be a dumb question, but is it DEFINITELY the SSD at fault here? Thanks.
Xorg Fails to start.
Hi,
I'm unable to get Xorg to start any more on my computer since about
three, or four snapshots ago. I'm not desperate for a GUI, but it
would be nice. Fails whether machdep.allowaperture is set to 1, or
2.
dmesg, /etc/X11/xorg.conf and Xorg.0.log outputs follow.
machdep.allowaperture set to 2.
OpenBSD 4.6-current (GENERIC) #353: Mon Nov 2 10:58:43 MST 2009
dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC
cpu0: AMD Athlon(tm) processor ("AuthenticAMD" 686-class, 256KB L2 cache) 1.20
GHz
cpu0:
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR
real mem = 804810752 (767MB)
avail mem = 771358720 (735MB)
mainbus0 at root
bios0 at mainbus0: AT/286+ BIOS, date 07/13/01, BIOS32 rev. 0 @ 0xfb5d0, SMBIOS
rev. 2.2 @ 0xf0800 (38 entries)
bios0: vendor Award Software International, Inc. version "6.00 PG" date
07/13/2001
bios0: Gigabyte Technology Co., LTD 7DXR
apm at bios0 function 0x15 not configured
acpi0 at bios0: rev 0
acpi0: tables DSDT FACP
acpi0: wakeup devices SLPB(S5) PCI0(S5) USB0(S4) USB1(S4) UAR1(S4)
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpiprt0 at acpi0: bus 0 (PCI0)
acpicpu0 at acpi0
acpibtn0 at acpi0: PWRB
acpibtn1 at acpi0: SLPB
bios0: ROM list: 0xc/0x8000 0xcc000/0x4000! 0xd/0x4000
cpu0 at mainbus0: (uniprocessor)
pci0 at mainbus0 bus 0: configuration mode 1 (bios)
pchb0 at pci0 dev 0 function 0 "AMD 761 PCI" rev 0x13
amdagp0 at pchb0
agp0 at amdagp0: aperture at 0xd000, size 0x400
ppb0 at pci0 dev 1 function 0 "AMD 761 PCI-PCI" rev 0x00
pci1 at ppb0 bus 1
vga1 at pci1 dev 5 function 0 "ATI Mach64" rev 0x27
wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
pcib0 at pci0 dev 7 function 0 "VIA VT82C686 ISA" rev 0x40
pciide0 at pci0 dev 7 function 1 "VIA VT82C571 IDE" rev 0x06: ATA100, channel 0
configured to compatibility, channel 1 configured to compatibility
wd0 at pciide0 channel 0 drive 0:
wd0: 16-sector PIO, LBA, 78167MB, 160086528 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
atapiscsi1 at pciide0 channel 1 drive 1
scsibus1 at atapiscsi1: 2 targets
cd1 at scsibus1 targ 0 lun 0: ATAPI 5/cdrom removable
cd0(pciide0:1:0): using PIO mode 4, DMA mode 2
cd1(pciide0:1:1): using PIO mode 4, Ultra-DMA mode 2
uhci0 at pci0 dev 7 function 2 "VIA VT83C572 USB" rev 0x1a: irq 11
uhci1 at pci0 dev 7 function 3 "VIA VT83C572 USB" rev 0x1a: irq 11
viaenv0 at pci0 dev 7 function 4 "VIA VT82C686 SMBus" rev 0x40: can't map PM
i/o space
rl0 at pci0 dev 12 function 0 "D-Link Systems 530TX+" rev 0x10: irq 10, address
00:50:ba:59:24:c3
rlphy0 at rl0 phy 0: RTL internal PHY
eap0 at pci0 dev 14 function 0 "Ensoniq CT5880" rev 0x03: irq 5
ac97: codec id 0x83847608 (SigmaTel STAC9708/11)
ac97: codec features 18 bit DAC, 18 bit ADC, SigmaTel 3D
audio0 at eap0
midi0 at eap0:
uhci2 at pci0 dev 15 function 0 "VIA VT83C572 USB" rev 0x50: irq 11
uhci3 at pci0 dev 15 function 1 "VIA VT83C572 USB" rev 0x50: irq 10
ehci0 at pci0 dev 15 function 2 "VIA VT6202 USB" rev 0x51: irq 7
usb0 at ehci0: USB revision 2.0
uhub0 at usb0 "VIA EHCI root hub" rev 2.00/1.00 addr 1
pciide1 at pci0 dev 16 function 0 "Promise PDC20265" rev 0x02: DMA, channel 0
configured to native-PCI, channel 1 configured to native-PCI
pciide1: using irq 11 for native-PCI interrupt
pciide1: channel 0 disabled (no drives)
pciide1: channel 1 disabled (no drives)
isa0 at pcib0
isadma0 at isa0
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
pcppi0 at isa0 port 0x61
midi1 at pcppi0:
spkr0 at pcppi0
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
usb1 at uhci0: USB revision 1.0
uhub1 at usb1 "VIA UHCI root hub" rev 1.00/1.00 addr 1
usb2 at uhci1: USB revision 1.0
uhub2 at usb2 "VIA UHCI root hub" rev 1.00/1.00 addr 1
usb3 at uhci2: USB revision 1.0
uhub3 at usb3 "VIA UHCI root hub" rev 1.00/1.00 addr 1
usb4 at uhci3: USB revision 1.0
uhub4 at usb4 "VIA UHCI root hub" rev 1.00/1.00 addr 1
biomask fddd netmask fddd ttymask ffdf
mtrr: Pentium Pro MTRR support
uhidev0 at uhub1 port 2 configuration 1 interface 0 "KYE USB MOUSE" rev
1.10/0.00 addr 2
uhidev0: iclass 3/1
ums0 at uhidev0: 3 buttons, Z dir
wsmouse0 at ums0 mux 0
vscsi0 at root
scsibus2 at vscsi0: 256 targets
softraid0 at root
root on wd0a swap on wd0b dump on wd0b
/etc/X11/xorg.conf
# File generated by xorgconfig.
#
# Copyright 2004 The X.Org Foundation
#
# Permission is hereby granted, free of charge, to any person obtaining a
# copy of this software and associated documentation files (the "Software"),
# to deal in the Software without restriction, including without limitation
# the rights to use, copy, modify, merge, publish, dis
Re: Package dependencies size estimate script
Hi Aaron
On 11/6/09, Aaron Mason wrote:
> On Fri, Nov 6, 2009 at 2:42 AM, wrote:
>> Hi
>>
>> Just wanted to share a script with fellow OpenBSD
>> desktop users who like to keep minimal non-base
>> software on the machine and prefer to use lighter
>> alternatives whenever possible.
>>
>> This script will help you estimate the total space
>> which will be used by a given package as well as
>> all the dependencies (recursively).
>>
>> It has to be run inside a directory with your
>> mirror of all packages. The o/p is a text file
>> in /tmp directory.
>>
>> This was made quickly for myself long time back.
>> Please consider the quality as such. Works for me.
>> Hope it can come in handy to someone.
>>
>> Take care.
>>
>> Srikant.
>>
>> -
>>
>> #!/bin/sh
>> # Find the full depency list for a given package
>> # in cmd. line
>> # Assumes one is in a dir with all packages
>>
>> # Temporary files
>> tmp_file_1=$(mktemp)
>> tmp_file_2=$(mktemp)
>> tmp_file_3=$(mktemp)
>>
>> echo $1 > $tmp_file_1
>>
>> ctr=0
>> over=0
>> while [ $over -ne 1 ]
>> do
>>cat $tmp_file_1 | fgrep -v -f $tmp_file_3 \
>>| xargs -I % pkg_info -f % \
>>| fgrep @depend | cut -d : -f 3 \
>>| grep -v '^$' | sort \
>>| uniq >> $tmp_file_2
>>
>>md5_old=`cat $tmp_file_1 | md5`
>>md5_new=`cat $tmp_file_2 | md5`
>>if [ `echo $md5_new | fgrep -xc $md5_old` -eq 1 ]; then
>>over=1
>>fi
>>cat $tmp_file_1 >> $tmp_file_3
>>cat $tmp_file_2 > $tmp_file_1
>>ctr=$(( ctr+1 ))
>> done
>>
>> cat $tmp_file_2 | sort | uniq > /tmp/$1-dependencies
>> echo "-" >> /tmp/$1-dependencies
>> ctr=$(( ctr-2 ))
>> echo "No. of levels of dependencies : $ctr" \
>>>> /tmp/$1-dependencies
>> count=`cat $tmp_file_2 | sort | uniq | wc -l | sed 's/ //g'`
>> echo "No. of dependencies : $count" \
>>>> /tmp/$1-dependencies
>>
>> cat $tmp_file_2 | sort | uniq | xargs -I % pkg_info -s % \
>>| fgrep Size: | awk '{ print $2 }' > $tmp_file_3
>> siz=0
>> {
>> while read rline
>> do
>>siz=$(( siz+rline ))
>> done
>> } < $tmp_file_3
>> echo "Estimated total size of dependencies: $siz" \
>>>> /tmp/$1-dependencies
>>
>> rm -rf $tmp_file_1
>> rm -rf $tmp_file_2
>> rm -rf $tmp_file_3
>>
>>
>
> pkg-info will also look for PKG_PATH and check remotely if there are
> any addresses there, I believe, so having a local mirror isn't
> necessary.
>
> --
> Aaron Mason - Programmer, open source addict
> I've taken my software vows - for beta or for worse
>
Thanks for pointing it out as well as the diff.
Learnt a couple of things from it.
Take care.
Srikant.
Re: Installing OpenBSD on SSD drives
2009/11/5 Jean-Frangois SIMON : > Hello, > Is there any particular problem with installing OpenBSD on a SSD HD ? I've been using flash based SSD's in OpenBSD systems for 6 or 7 years, starting with small CF in firewalls and now SATA SSD's in desktops and laptops. Never had a problem installing to them and never had one go bad. I just use noatime, softdep and no swap (but I guess looking at the opinions of devs here, no swap is now just a bad habit). Shane
Re: Package dependencies size estimate script
On Fri, Nov 6, 2009 at 2:42 AM, wrote:
> Hi
>
> Just wanted to share a script with fellow OpenBSD
> desktop users who like to keep minimal non-base
> software on the machine and prefer to use lighter
> alternatives whenever possible.
>
> This script will help you estimate the total space
> which will be used by a given package as well as
> all the dependencies (recursively).
>
> It has to be run inside a directory with your
> mirror of all packages. The o/p is a text file
> in /tmp directory.
>
> This was made quickly for myself long time back.
> Please consider the quality as such. Works for me.
> Hope it can come in handy to someone.
>
> Take care.
>
> Srikant.
>
> -
>
> #!/bin/sh
> # Find the full depency list for a given package
> # in cmd. line
> # Assumes one is in a dir with all packages
>
> # Temporary files
> tmp_file_1=$(mktemp)
> tmp_file_2=$(mktemp)
> tmp_file_3=$(mktemp)
>
> echo $1 > $tmp_file_1
>
> ctr=0
> over=0
> while [ $over -ne 1 ]
> do
>cat $tmp_file_1 | fgrep -v -f $tmp_file_3 \
>| xargs -I % pkg_info -f % \
>| fgrep @depend | cut -d : -f 3 \
>| grep -v '^$' | sort \
>| uniq >> $tmp_file_2
>
>md5_old=`cat $tmp_file_1 | md5`
>md5_new=`cat $tmp_file_2 | md5`
>if [ `echo $md5_new | fgrep -xc $md5_old` -eq 1 ]; then
>over=1
>fi
>cat $tmp_file_1 >> $tmp_file_3
>cat $tmp_file_2 > $tmp_file_1
>ctr=$(( ctr+1 ))
> done
>
> cat $tmp_file_2 | sort | uniq > /tmp/$1-dependencies
> echo "-" >> /tmp/$1-dependencies
> ctr=$(( ctr-2 ))
> echo "No. of levels of dependencies : $ctr" \
>>> /tmp/$1-dependencies
> count=`cat $tmp_file_2 | sort | uniq | wc -l | sed 's/ //g'`
> echo "No. of dependencies : $count" \
>>> /tmp/$1-dependencies
>
> cat $tmp_file_2 | sort | uniq | xargs -I % pkg_info -s % \
>| fgrep Size: | awk '{ print $2 }' > $tmp_file_3
> siz=0
> {
> while read rline
> do
>siz=$(( siz+rline ))
> done
> } < $tmp_file_3
> echo "Estimated total size of dependencies: $siz" \
>>> /tmp/$1-dependencies
>
> rm -rf $tmp_file_1
> rm -rf $tmp_file_2
> rm -rf $tmp_file_3
>
>
I made a patch to streamline a few things (such as using cat when the
command accepting its output can take a file argument anyway) and put
the rm commands onto one line. Here it is, in unified format:
--- pkg_estimate.orig.shFri Nov 06 11:59:58 2009
+++ pkg_estimate.sh Fri Nov 06 12:02:52 2009
@@ -2,6 +2,7 @@
# Find the full depency list for a given package
# in cmd. line
# Assumes one is in a dir with all packages
+#or PKG_PATH is available
# Temporary files
tmp_file_1=$(mktemp)
@@ -14,7 +15,7 @@
over=0
while [ $over -ne 1 ]
do
- cat $tmp_file_1 | fgrep -v -f $tmp_file_3 \
+ fgrep -v -f $tmp_file_3 $tmp_file_1 \
| xargs -I % pkg_info -f % \
| fgrep @depend | cut -d : -f 3 \
| grep -v '^$' | sort \
@@ -26,31 +27,28 @@
over=1
fi
cat $tmp_file_1 >> $tmp_file_3
- cat $tmp_file_2 > $tmp_file_1
+ cp -f $tmp_file_2 $tmp_file_1
ctr=$(( ctr+1 ))
done
-cat $tmp_file_2 | sort | uniq > /tmp/$1-dependencies
+sort $tmp_file_2 | uniq > /tmp/$1-dependencies
echo "-" >> /tmp/$1-dependencies
ctr=$(( ctr-2 ))
echo "No. of levels of dependencies : $ctr" \
>> /tmp/$1-dependencies
-count=`cat $tmp_file_2 | sort | uniq | wc -l | sed 's/ //g'`
+count=`sort $tmp_file_2 | uniq | wc -l | sed 's/ //g'`
echo "No. of dependencies : $count" \
>> /tmp/$1-dependencies
-cat $tmp_file_2 | sort | uniq | xargs -I % pkg_info -s % \
+sort $tmp_file_2 | uniq | xargs -I % pkg_info -s % \
| fgrep Size: | awk '{ print $2 }' > $tmp_file_3
siz=0
-{
+
while read rline
do
siz=$(( siz+rline ))
-done
-} < $tmp_file_3
+done < $tmp_file_3
echo "Estimated total size of dependencies: $siz" \
>> /tmp/$1-dependencies
-rm -rf $tmp_file_1
-rm -rf $tmp_file_2
-rm -rf $tmp_file_3
\ No newline at end of file
+rm -rf $tmp_file_1 $tmp_file_2 $tmp_file_3
\ No newline at end of file
--
Aaron Mason - Programmer, open source addict
I've taken my software vows - for beta or for worse
Re: Package dependencies size estimate script
On Fri, Nov 6, 2009 at 2:42 AM, wrote:
> Hi
>
> Just wanted to share a script with fellow OpenBSD
> desktop users who like to keep minimal non-base
> software on the machine and prefer to use lighter
> alternatives whenever possible.
>
> This script will help you estimate the total space
> which will be used by a given package as well as
> all the dependencies (recursively).
>
> It has to be run inside a directory with your
> mirror of all packages. The o/p is a text file
> in /tmp directory.
>
> This was made quickly for myself long time back.
> Please consider the quality as such. Works for me.
> Hope it can come in handy to someone.
>
> Take care.
>
> Srikant.
>
> -
>
> #!/bin/sh
> # Find the full depency list for a given package
> # in cmd. line
> # Assumes one is in a dir with all packages
>
> # Temporary files
> tmp_file_1=$(mktemp)
> tmp_file_2=$(mktemp)
> tmp_file_3=$(mktemp)
>
> echo $1 > $tmp_file_1
>
> ctr=0
> over=0
> while [ $over -ne 1 ]
> do
>cat $tmp_file_1 | fgrep -v -f $tmp_file_3 \
>| xargs -I % pkg_info -f % \
>| fgrep @depend | cut -d : -f 3 \
>| grep -v '^$' | sort \
>| uniq >> $tmp_file_2
>
>md5_old=`cat $tmp_file_1 | md5`
>md5_new=`cat $tmp_file_2 | md5`
>if [ `echo $md5_new | fgrep -xc $md5_old` -eq 1 ]; then
>over=1
>fi
>cat $tmp_file_1 >> $tmp_file_3
>cat $tmp_file_2 > $tmp_file_1
>ctr=$(( ctr+1 ))
> done
>
> cat $tmp_file_2 | sort | uniq > /tmp/$1-dependencies
> echo "-" >> /tmp/$1-dependencies
> ctr=$(( ctr-2 ))
> echo "No. of levels of dependencies : $ctr" \
>>> /tmp/$1-dependencies
> count=`cat $tmp_file_2 | sort | uniq | wc -l | sed 's/ //g'`
> echo "No. of dependencies : $count" \
>>> /tmp/$1-dependencies
>
> cat $tmp_file_2 | sort | uniq | xargs -I % pkg_info -s % \
>| fgrep Size: | awk '{ print $2 }' > $tmp_file_3
> siz=0
> {
> while read rline
> do
>siz=$(( siz+rline ))
> done
> } < $tmp_file_3
> echo "Estimated total size of dependencies: $siz" \
>>> /tmp/$1-dependencies
>
> rm -rf $tmp_file_1
> rm -rf $tmp_file_2
> rm -rf $tmp_file_3
>
>
It works great, by the way. Tested on 4.6 release. I'd probably also
cat the contents of /tmp/$1-dependencies, but that's just me.
--
Aaron Mason - Programmer, open source addict
I've taken my software vows - for beta or for worse
Re: Installing OpenBSD on SSD drives
Ted Unangst wrote: On Thu, Nov 5, 2009 at 3:32 PM, Joachim Schipper wrote: Still, the point I was trying to make - that leaving part of your disk unpartitioned doesn't really help - stands, no? Depends. Partitioning or not partitioning is unlikely to make a difference, as it's writes that matter. However, if you need 32G of space, but buy a 128G disk, that will last longer. The 32G will almost certainly last "long enough", but if you're paranoid, you can buy assurance by getting a larger disk. So leaving part of the disk unpartitioned implies you have extra space, which does help, but it's not the partitioning itself which makes the difference. I agree with Ted and would like to expand on it: Partitioning the disk to extend its life only works after a secure erase of the drive and never ever touching the non-partitioned space. The reason for this is due to the SSD's internal mapping of logical OS-addressable sectors to its physical sectors. Take for example a fresh (newly bought or secure erased) 40G drive and put a 32G partition on it. For the SSD controller there will always be 8G worth of sectors that have never been touched and therefore can be used without wear-leveling its contents first. But if you even once use this partition and fill up the 8G, the mapping table will be filled up as well and even after deleting the content and/or the partition it will from this point on shuffle around these obsolete 8G of data. No type of formatting can free up these sectors other than secure erasing, which of course only applies to the whole drive. To be clear, something like a zero-format (dd if=/dev/zero) doesn't help as well, as the SSD controller would then shuffle around sectors with only 0x00 in it. So it takes self-control on your part to keep the SSD long-lived and fast. Maybe some better way would be to use the Host Protected Area feature. It limits the amount of OS-addressable sectors, thus the disk space always appears smaller to the OS than it really is and you can use the "whole" disk. In fact I suspect this is what Intel does with its X25-E SLC drives. The amount of sectors of the 32G drive is 62,500,000 which is an "odd" number since disks usually don't have such a nice looking number of sectors. Unfortunately the price point keeps me from verifying that. The X25-M consumer drives don't have a HPA-hidden space. I would therefore be thankful if someone with such a precious drive could check on that. I checked my X25-M with HDAT2 which boots into MS-DOS. For the sake of completeness: All of this applies only to SSDs without the TRIM ATA command. TRIM-enabled SSDs and OSs don't need this workaround.
Re: tmux as an educational facilitator
thanks everyone on/off-list for pointing out that screen can do this as well. it was not the point of my mail though. it was not a pissing contest what screen and tmux can/can't do. everyone can now stop sending screen -x, thank you. $ screen -x ksh: screen: not found -f -- if they can send a man to the moon... why not send 'em all?
Re: Installing OpenBSD on SSD drives
2009/11/6 Jean-Frangois SIMON : > > > 2009/11/4 Aaron Mason >> >> 2009/11/5 Jean-Frangois SIMON : >> > Hello, >> > Is there any particular problem with installing OpenBSD on a SSD HD ? I >> > once could on one machine but on my actual machine it simply does'nt >> > work. >> > After a while, the SSD disk becomes like overloaded and unavailable to >> > continue the installing process of 4.6. >> > Regards >> > >> > >> >> Hi Jean-Francios, >> >> Is this a used SSD? That happens with used ones because they end up >> doing twice the work - once to erase the used block and again to >> actually write the block (and several blocks around them, AAMOF). >> >> If you have a "secure erase" option available, use it. This will >> restore the data blocks to an unused state, and restore full speed >> again. >> >> HTH >> > > Hi Aaron, > I'm not sure I fully understood you, yes it has been used many times. Should > I erase it completely in order to refresh properly the drive ? > > BTW I actually make regular save of the while drive because I'm afraid that > it one days stops to works (the SSD on my server) and since it actually > hosts a website, that's a good reason for me to tarball it once in a while, > generally after many updates of the site. > > Regards > Jean-Frangois > I assume you're talking about zero filling - I'm not sure that would have the desired effect since it wouldn't mark the sectors as unused. What I'm referring to actually erases the data in each sector and marks them as unused. AFAIK only Intel drives have this functionality, but a google will tell you if yours does or not - I'm sure other people have asked. For some clarity, this page might clear things up: http://www.anandtech.com/storage/showdoc.aspx?i=3531&p=8 HTH -- Aaron Mason - Programmer, open source addict - Oh, why does everything I whip leave me?
Re: Installing OpenBSD on SSD drives
On Thu, 5 Nov 2009 21:32:59 +0100 Joachim Schipper wrote: > On Thu, Nov 05, 2009 at 12:14:15PM -0500, Ted Unangst wrote: > > On Thu, Nov 5, 2009 at 10:28 AM, Joachim Schipper > > wrote: > > > This seems predicated on the firmware being smart enough to swap > > > out bad sectors for good setors that are addressable but not used > > > in practice. Is the firmware that smart? (I know about > > > wear-levelling and swapping in "reserve" sectors, but that's > > > different - those *cannot* be addressed.) > > > > There are no reserve sectors, there's just sectors. Some of them > > are reserved, but they're no different from the normal sectors. > > > > Think of it like a 6GB machine running PAE (and only one process). > > You can only address 4GB at maximum, but if something goes bad, > > there's other memory your virtual addresses can get mapped to. If > > you are only writing to 1GB of space though, it's easily spread out > > over all 6GB. The high 2GB is not special or different. > > I was going to send a "you misunderstood my point" message, but you > are right about the "no special sectors" part, and I knew better. > Thanks for the correction! > > Still, the point I was trying to make - that leaving part of your disk > unpartitioned doesn't really help - stands, no? > > Joachim It makes no difference if the "free space" is kept free by not partioning it or simply not using all of the partitioned space. - Robert
Re: tmux as an educational facilitator
On Thu, 5 Nov 2009, frantisek holop wrote: > as an old time screen user i was perplexed to see that when i > attached to an already attached tmux session, both clients were > updated real time and accepted input as well. the ascii art with > the differing terminal window sizes is also a breakthrough idea. $ screen -x -- Daniel Bolgheroni FEI - Faculdade de Engenharia Industrial http://www.dbolgheroni.eng.br/mykey ASCII ribbon campaign ( ) against HTML e-mail X / \
Re: Installing OpenBSD on SSD drives
On Thu, Nov 5, 2009 at 3:32 PM, Joachim Schipper wrote: > Still, the point I was trying to make - that leaving part of your disk > unpartitioned doesn't really help - stands, no? Depends. Partitioning or not partitioning is unlikely to make a difference, as it's writes that matter. However, if you need 32G of space, but buy a 128G disk, that will last longer. The 32G will almost certainly last "long enough", but if you're paranoid, you can buy assurance by getting a larger disk. So leaving part of the disk unpartitioned implies you have extra space, which does help, but it's not the partitioning itself which makes the difference.
Re: Installing OpenBSD on SSD drives
On Thu, Nov 05, 2009 at 12:14:15PM -0500, Ted Unangst wrote: > On Thu, Nov 5, 2009 at 10:28 AM, Joachim Schipper > wrote: > > This seems predicated on the firmware being smart enough to swap out bad > > sectors for good setors that are addressable but not used in practice. > > Is the firmware that smart? (I know about wear-levelling and swapping > > in "reserve" sectors, but that's different - those *cannot* be > > addressed.) > > There are no reserve sectors, there's just sectors. Some of them are > reserved, but they're no different from the normal sectors. > > Think of it like a 6GB machine running PAE (and only one process). > You can only address 4GB at maximum, but if something goes bad, > there's other memory your virtual addresses can get mapped to. If you > are only writing to 1GB of space though, it's easily spread out over > all 6GB. The high 2GB is not special or different. I was going to send a "you misunderstood my point" message, but you are right about the "no special sectors" part, and I knew better. Thanks for the correction! Still, the point I was trying to make - that leaving part of your disk unpartitioned doesn't really help - stands, no? Joachim
Re: Installing OpenBSD on SSD drives
2009/11/5 Robert > On Thu, 5 Nov 2009 20:08:48 +0100 > Jean-Frangois SIMON wrote: > > > 2009/11/4 STeve Andre' > > > > > On Wednesday 04 November 2009 16:10:06 Jean-Frangois SIMON wrote: > > > > Hello, > > > > Is there any particular problem with installing OpenBSD on a SSD > > > > HD ? I once could on one machine but on my actual machine it > > > > simply does'nt > > > work. > > > > After a while, the SSD disk becomes like overloaded and > > > > unavailable to continue the installing process of 4.6. > > > > Regards > > > > > > I played with one, briefly, and it seemed to work. A litte weird, > > > not hearing anything from it... > > > > > > But I'm not at all eager to actually use them just yet. Look for > > > the goofs Intel has had with them. How long will they last, and > > > what is the failure mode like? More often than not a spinning disk > > > will give notice of impending death with a few bad spots before The > > > End. But what of an SSD? By its very nature I could see an > > > address line going, leaving a very weird pattern of unaffected data. > > > > > > SSDs are the future, I'm fairly sure but I think they need to mature > > > as well as get bigger. > > > > > > Lastly, saying where the install hangs would really help. And of > > > course how big is it and who made it? > > > > > > --STeve Andre' > > > > > > > > Hello, > > It will be a small SSD like 32 Go or 64 Go for my personal computer. > > It actually works for my home server however installing on my main > > computer fails during the installing process by going slower and > > slower then making IO errors. > > Regards > > Those errors are not printed to the screen? > The SSD also inhibits printing of the dmesg? > Sorry if i am mistaken and you don't want your issue resolved, but only > rant. In that case you can disregard this mail. > > - Robert > I actually just posted them before (some ten minutes ago in the same thread). More cannot be done (like dmesg) at the moment because yes, it can be printed out on the screen, but i'm not used to the stuff that makes it out of a very minimalistic system such as a serial console, sorry for that. Regards
Re: Installing OpenBSD on SSD drives
2009/11/4 Aaron Mason > 2009/11/5 Jean-Frangois SIMON : > > Hello, > > Is there any particular problem with installing OpenBSD on a SSD HD ? I > > once could on one machine but on my actual machine it simply does'nt > work. > > After a while, the SSD disk becomes like overloaded and unavailable to > > continue the installing process of 4.6. > > Regards > > > > > > Hi Jean-Francios, > > Is this a used SSD? That happens with used ones because they end up > doing twice the work - once to erase the used block and again to > actually write the block (and several blocks around them, AAMOF). > > If you have a "secure erase" option available, use it. This will > restore the data blocks to an unused state, and restore full speed > again. > > HTH > > Hi Aaron, I'm not sure I fully understood you, yes it has been used many times. Should I erase it completely in order to refresh properly the drive ? BTW I actually make regular save of the while drive because I'm afraid that it one days stops to works (the SSD on my server) and since it actually hosts a website, that's a good reason for me to tarball it once in a while, generally after many updates of the site. Regards Jean-Frangois
Re: Installing OpenBSD on SSD drives
2009/11/4 K K > 2009/11/4 Jean-Frangois SIMON : > > Hello, > > Is there any particular problem with installing OpenBSD on a SSD HD ? I > > once could on one machine but on my actual machine it simply does'nt > work. > > After a while, the SSD disk becomes like overloaded and unavailable to > > continue the installing process of 4.6. > > Regards > > Sounds like an issue with your SSD? > Can you supply a dmesg, and details on the SSD, make/model/supplier, > as well as the motherboard and how the drive appears to the BIOS? > > > On Wed, Nov 4, 2009 at 4:12 PM, Ted Unangst wrote: > > 2009/11/4 Roger Schreiter : > >> it is like for any OS on SSD HD. Make sure, you are using > >> no swap partition! > > > > This is ridiculous advice. > > This *was* reasonable advice for the older generations of > CompactFlash, but may no longer be a consideration with newer > flash/SSD drives. > > I have run many embedded servers (mostly OpenBSD on Soekris) without > swap, never had any problems traceable to the lack of swap space. > > > >> And if you are using an application, which is writing > >> a lot of things into files, put the respective dirs into > >> ramdisks! > > > > Combined with this is even dumber. > > > > If you can't swap, you're already in trouble if you run into memory > > pressure. So then you go and put the filesystem in RAM to make sure > > there's lots of extra memory pressure? > > Actually, the above is standard advice for running any Unix on flash, > as people have been doing with Soekris and CF since at least 2001. > > The idea isn't to put "the filesystem" into RAM, but rather to reduce > the write operations by mounting filesystems used for frequently > written smal files (e.g. /var/tmp) as ramdisks. > > Kevin > Model and make is not anymore available, it was LDLC (website ldlc.com). It must be very recent since they removed their products from the market. This is something possible that they do have has dome problems with it. The error actually appears wjile installing xfont46.tgz which is very very slow. It is normal speed util that particular file . errors : many "atascsi_atapi_cmd_done, timeout" one "d0(ahci0:3:0): Check Condition (error 0x70) on opcode 0x28 SENSE KEY: Illegal Request" The SSD appears in the bios as "Veritech SSD 2009-03" Motherboard : Gigabyte GA-MA790X-DS4 F4 After quite a while, it finally finished the install process (passed the various errors) but the boot on SSD drive fails and crashes. Unfortunately, I am not used to extract from a machine that half works the dmesg and kernel crash informations (using serial interface). I have bought 2 cards (exactly identical) from the same supplier, and actually one of them work in production on mye server, and the one on my personal computer works fine with other operating systems (ex. Ubuntu). Regards
Re: Installing OpenBSD on SSD drives
On Thu, 5 Nov 2009 20:08:48 +0100 Jean-Frangois SIMON wrote: > 2009/11/4 STeve Andre' > > > On Wednesday 04 November 2009 16:10:06 Jean-Frangois SIMON wrote: > > > Hello, > > > Is there any particular problem with installing OpenBSD on a SSD > > > HD ? I once could on one machine but on my actual machine it > > > simply does'nt > > work. > > > After a while, the SSD disk becomes like overloaded and > > > unavailable to continue the installing process of 4.6. > > > Regards > > > > I played with one, briefly, and it seemed to work. A litte weird, > > not hearing anything from it... > > > > But I'm not at all eager to actually use them just yet. Look for > > the goofs Intel has had with them. How long will they last, and > > what is the failure mode like? More often than not a spinning disk > > will give notice of impending death with a few bad spots before The > > End. But what of an SSD? By its very nature I could see an > > address line going, leaving a very weird pattern of unaffected data. > > > > SSDs are the future, I'm fairly sure but I think they need to mature > > as well as get bigger. > > > > Lastly, saying where the install hangs would really help. And of > > course how big is it and who made it? > > > > --STeve Andre' > > > > > Hello, > It will be a small SSD like 32 Go or 64 Go for my personal computer. > It actually works for my home server however installing on my main > computer fails during the installing process by going slower and > slower then making IO errors. > Regards Those errors are not printed to the screen? The SSD also inhibits printing of the dmesg? Sorry if i am mistaken and you don't want your issue resolved, but only rant. In that case you can disregard this mail. - Robert
testing smtpd; can someone hit me with a cluestick
i'm testing smtpd (OpenBSD/i386 -STABLE; stock GENERIC.MP)
here're the full headers from a mail i sent from a host at $work. my
domain is cna.org , not cna.org.net . but i cannot figure out if
something i have done is appending that ``.net'' after the ``.org''. my
employer doesn't even own our equivalent .net domain, so i'm not sure
this is a mail relay or something that's configured incorrectly in our
enterprise. i've seen DNS mis-configurations append things to the end of
hostnames when you forget a dot, but i can't see how that's involved
here. but if so, please educate me.
you'll see this in the envelope from and From: and a few others.
i'm aware that there is no header rewriting at the moment, so it's
perfectly OK that the hostname isn't being stripped out. but obviously
that hostname doesn't resolve in the DNS outside of our enterprise
proper. i can't suss out if that has anything to do with what i'm
seeing though. i'm assuming that's why SpamAssassin is complaining with
UNPARSEABLE_RELAY below.
my /etc/mail/smtpd.conf is very basic:
listen on lo0
map "aliases" { source db "/etc/mail/aliases.db" }
accept for local deliver to mbox
accept for all relay via "mail.cna.org"
smtpd -n returns ``configuration OK'', so i will assume that my config
is OK. it is worth noting that mail.cna.org is a not-very-`wise' product
from Novell that exhibits all sort of brain-deadness from time to time.
it's mangled by others; i have some 4.5 boxen still on base sendmail
that behaves as i expect.
i didn't attempt to obfuscate any info in the headers, as that can
sometimes cause confusion for folks who are trying to help. any nudges
in the right direction much appreciated.
final note: i'm using /usr/bin/mail -v to send these test messages.
(sorry for the odd line wraps)
>From j...@radbsd1.cna.org.net Thu Nov 5 18:42:35 2009
Return-Path: j...@radbsd1.cna.org.net
Received: from sender2.cna.org (sender2.cna.org [192.189.236.25])
by cosmicnetworks.net (8.14.3/8.14.3) with ESMTP id
nA5IgSol019411
for ; Thu, 5 Nov 2009 18:42:29 GMT
Received: from sender.CNA.ORG (unknown [192.168.200.13])
by sender2.cna.org (Spam & Virus Firewall) with ESMTP id
41AA0F6CA6
for ; Thu, 5 Nov 2009 13:42:23 -0500 (EST)
Received: from sender.CNA.ORG ([192.168.200.13]) by sender2.cna.org with
ESMTP id ErZ9TZCoxVxa9fDG for ; Thu,
05 Nov 2009 13:42:23 -0500 (EST)
Received: from radbsd1.cna.org ([192.168.156.252])
by sender.CNA.ORG with ESMTP; Thu, 05 Nov 2009 13:42:21 -0500
X-OpenSMTPD-Loop: j...@cosimano.net
Received: from radbsd1.cna.org (localhost [IPv6:::1])
by radbsd1.cna.org (OpenSMTPD) with ESMTP id
1257446540.BsYROsckto8emQkk
for ; Thu, 5 Nov 2009 13:42:20 -0500 (EST)
Received: (from j...@localhost, uid 1000)
by radbsd1.cna.org
Thu, 5 Nov 2009 13:42:20 -0500 (EST)
From: jmc
Date: Thu, 5 Nov 2009 13:42:20 -0500 (EST)
Message-Id: <5400691765769033861.enqu...@radbsd1.cna.org>
To: j...@cosimano.net
Subject: testing net
X-SMTP-Vilter-Version: 1.3.6
X-Spamd-Symbols: TVD_SPACE_RATIO,UNPARSEABLE_RELAY
laksdfjakljdfa
Re: Installing OpenBSD on SSD drives
2009/11/4 STeve Andre' > On Wednesday 04 November 2009 16:10:06 Jean-Frangois SIMON wrote: > > Hello, > > Is there any particular problem with installing OpenBSD on a SSD HD ? I > > once could on one machine but on my actual machine it simply does'nt > work. > > After a while, the SSD disk becomes like overloaded and unavailable to > > continue the installing process of 4.6. > > Regards > > I played with one, briefly, and it seemed to work. A litte weird, not > hearing anything from it... > > But I'm not at all eager to actually use them just yet. Look for the > goofs Intel has had with them. How long will they last, and what is > the failure mode like? More often than not a spinning disk will give > notice of impending death with a few bad spots before The End. But > what of an SSD? By its very nature I could see an address line going, > leaving a very weird pattern of unaffected data. > > SSDs are the future, I'm fairly sure but I think they need to mature > as well as get bigger. > > Lastly, saying where the install hangs would really help. And of > course how big is it and who made it? > > --STeve Andre' > > Hello, It will be a small SSD like 32 Go or 64 Go for my personal computer. It actually works for my home server however installing on my main computer fails during the installing process by going slower and slower then making IO errors. Regards
pf.conf reassemble and antispoof questions
I have been on OBSD 4.4 for a bit and had not really messed with pf.conf for a while. When I updated to 4.6 there were a couple of settings that seemed ambiguous to me. 1) under Options, "set reassemble on". I know it is on by default but I got a parsing error when I tried it. I also found some man pages online that were missing this option however the man page in 4.6 does include it. So A) Is this supposed to work still? B) Is there a difference between setting "set reassemble on" in the options vs. "match in all scrub reassemble tcp"? 2)Using urpf-failed vs. antispoof. http://www.openbsd.org/faq/pf/filter.html says "uRPF provides the same functionality as antispoof rules." Is it truly identical? I could not find anything in the man page that explicitly says the are functionally equivalent. Is there a reason to use one over the other... or will one be deprecated? Thanks!
