Re: less minor install issue
> On Thu, Oct 22, 2009 at 5:41 PM, Nick Holland > wrote: > > Daniel Malament wrote: > >> On 10/22/2009 5:37 AM, William Boshuck wrote: > And here I thought I remembered the new installer being described as > easier to use. > >> > >>> It is. Were it not so quick it would be positively > >>> boring. Just don't set mount points for the partitions > >> > >> Perhaps I should clarify: IMO, not double-checking with the user about > >> what specifically to wipe, especially when it used to, is a step back in > >> 'usability' (in the Jakob Nielsen sense) - or to put it another way, > >> user-friendliness. > > > > I presume you are talking about this question: > > > > The next step *DESTROYS* all existing data on these partitions! > > Are you really sure that you're ready to proceed? [no] y > > > > This question was asked AFTER you had fdisk'd and disklabled your > > disk. By this point, the data had been already potentially destroyed, > > I thought this question quite silly, in that it implies data has been > > safe up to this point...no, it hasn't, you have potentially been > > destroying things all over the place. > > Hey Nick, > > I don't wish to contradict you here, but ... I usually do installs and > never upgrades. So what I do is keep /home out of the mount points in > the disklabel stage, go through install, then re-add /home. I recall a > while back, I did get to this stage and agreed to proceed and as the > partitions were being newfs-ed I realized I had forgotten and included > /home in the list. I ^C out before the /home slice was reached. I > restarted the install, this time doing it "correctly", and my data in > /home was OK! > > Might have been a fluke ... but, it is what it is. You missed the point.
Re: thanks for 4.6!
2009/10/23 ropers : > > I'd like to share a few images with you. Well if a picture worth 1024 words... Then I got a video for you!! http://www.youtube.com/watch?v=i71bLCtDKzk If you don't like flash plugin: curl "http://v20.lscache7.c.youtube.com/videoplayback?ip=0.0.0.0&sparams=id%2Cexpi re%2Cip%2Cipbits%2Citag%2Calgorithm%2Cburst%2Cfactor&fexp=905700%2C900031&alg orithm=throttle-factor&itag=22&ipbits=0&signature=C61C80608E1A7EC812C02E92B98 C81BE64F2320B.CA1663F7340A6730BA2575257A9A49CB34A2CB6F&sver=3&expire=12562848 00&key=yt1&factor=1.25&burst=40&id=8bbd5b2c2b432b39" -o openbsd46.mp4
Re: less minor install issue
On Thu, Oct 22, 2009 at 5:41 PM, Nick Holland wrote: > Daniel Malament wrote: >> On 10/22/2009 5:37 AM, William Boshuck wrote: And here I thought I remembered the new installer being described as easier to use. >> >>> It is. Were it not so quick it would be positively >>> boring. Just don't set mount points for the partitions >> >> Perhaps I should clarify: IMO, not double-checking with the user about >> what specifically to wipe, especially when it used to, is a step back in >> 'usability' (in the Jakob Nielsen sense) - or to put it another way, >> user-friendliness. > > I presume you are talking about this question: > > The next step *DESTROYS* all existing data on these partitions! > Are you really sure that you're ready to proceed? [no] y > > This question was asked AFTER you had fdisk'd and disklabled your > disk. By this point, the data had been already potentially destroyed, > I thought this question quite silly, in that it implies data has been > safe up to this point...no, it hasn't, you have potentially been > destroying things all over the place. Hey Nick, I don't wish to contradict you here, but ... I usually do installs and never upgrades. So what I do is keep /home out of the mount points in the disklabel stage, go through install, then re-add /home. I recall a while back, I did get to this stage and agreed to proceed and as the partitions were being newfs-ed I realized I had forgotten and included /home in the list. I ^C out before the /home slice was reached. I restarted the install, this time doing it "correctly", and my data in /home was OK! Might have been a fluke ... but, it is what it is. --patrick
Re: thanks for 4.6!
On Thu, Oct 22, 2009 at 11:37:31PM +0100, Peter wrote: > Marco Peereboom wrote: >> dvorak is make belief benefit. >> >> > > The only disadvantages are if you're left handed (in the standard layout > more emphasis is placed on the right hand), and that even official > Dvorak keyboards and layouts within operating systems do not use > Dvorak's original number layout. > You can also use the single left hand version of dvorak... it's still faster (and a lot more pleasant) than qwerty (using both hands). -- DISCLAIMER: http://goldmark.org/jeff/stupid-disclaimers/ This message will self-destruct in 3 seconds.
Re: thanks for 4.6!
Matthias Kilian wrote: On Thu, Oct 22, 2009 at 11:37:31PM +0100, Peter wrote: It's debatable whether the Dvorak layout is any faster, but what is not in doubt is the reduction in key travel. you're not a pianist OK. Finger travel, not key travel. Happy? PK
Re: less minor install issue
Daniel Malament wrote: > On 10/22/2009 5:37 AM, William Boshuck wrote: >>> And here I thought I remembered the new installer being described as easier >>> to use. > >> It is. Were it not so quick it would be positively >> boring. Just don't set mount points for the partitions > > Perhaps I should clarify: IMO, not double-checking with the user about > what specifically to wipe, especially when it used to, is a step back in > 'usability' (in the Jakob Nielsen sense) - or to put it another way, > user-friendliness. I presume you are talking about this question: The next step *DESTROYS* all existing data on these partitions! Are you really sure that you're ready to proceed? [no] y This question was asked AFTER you had fdisk'd and disklabled your disk. By this point, the data had been already potentially destroyed, I thought this question quite silly, in that it implies data has been safe up to this point...no, it hasn't, you have potentially been destroying things all over the place. Nick.
Re: thanks for 4.6!
On Thu, Oct 22, 2009 at 11:37:31PM +0100, Peter wrote: > It's debatable whether the Dvorak layout is any faster, but what is not > in doubt is the reduction in key travel. you're not a pianist
Re: thanks for 4.6!
Marco Peereboom wrote: dvorak is make belief benefit. It's debatable whether the Dvorak layout is any faster, but what is not in doubt is the reduction in key travel. Not only are the frequently used keys closer together but the keyboard is also arranged so that alternate hands are used to type subsequent letters. The only disadvantages are if you're left handed (in the standard layout more emphasis is placed on the right hand), and that even official Dvorak keyboards and layouts within operating systems do not use Dvorak's original number layout. I started with software remapping of a standard keyboard and now use a hard wired 'Dvorak UK' buckling spring keyboard from Unicomp. It's a lovely piece of kit, albeit lighter than the IBM Model M and not exactly cheap on shipping. I can't say whether the Dvorak number layout is an improvement because I never bothered learning that part (neither can I properly touchtype on the number pad on QWERTY), but the standard keyboard layout is lovely to use and feels much better in operation, never mind the likely reduction in RSI. It's a bit of a pain in the arse in vi or Wordstar/joe, though.. PK
Re: thanks for 4.6!
On Thu, Oct 22, 2009 at 10:04:53PM +, Miod Vallat wrote: > > dvorak is make belief benefit. > > Tell that to my hands tendinitis... but maybe you're not writing enough > code for your hands to suffer, Marco. > > And `j' and `k' are next to each other on dvorak keyboards anyway. > miod++ I don't use it for gaining more speed or whatever the usual keyboard/editors/os/religion/etc stupid wars are all about. I'm using it for _my_ _own_ confort which _for_ _me_ has been quite visible since I switched. But have no fear, kili will rescue your arrows so that you can stretch and twitch your fingers even more :-)
Re: thanks for 4.6!
if i may... 3. Make history be local to the term first (for n entries) before searching/using the global index. On Fri, Oct 23, 2009 at 12:37:56AM +0200, Matthias Kilian wrote: > On Thu, Oct 22, 2009 at 10:01:47AM -0500, Marco Peereboom wrote: > > > Some people should really give vi-mode in ksh a try ;-) > > > > As a vi user I can't deal with it > > > > The reason being that you have to use j k to go up and down in the > > history. Life would be bliss if one could reassign the arrow keys. > > I'll put it on my ksh TODO list, which now consists of two entries: > > 1 cleanup and finish my 64 bit arithmetics diff (yes, i'm a hopeless > case of a slacker) > > 2 enable arrow keys in vi-mode > > Ciao, > Kili
Re: thanks for 4.6!
On Thu, Oct 22, 2009 at 10:01:47AM -0500, Marco Peereboom wrote: > > Some people should really give vi-mode in ksh a try ;-) > > As a vi user I can't deal with it > > The reason being that you have to use j k to go up and down in the > history. Life would be bliss if one could reassign the arrow keys. I'll put it on my ksh TODO list, which now consists of two entries: 1 cleanup and finish my 64 bit arithmetics diff (yes, i'm a hopeless case of a slacker) 2 enable arrow keys in vi-mode Ciao, Kili
Re: Network problems with OpenBSD 4.6 on a IBM xSeries 335
What happend if you change the bge1 interface to other network, example,
10.4.1.2 , for me, two interfaces on the same network, sometimes produces a
strange behavior.
I hope this can help !
On Thu, Oct 22, 2009 at 3:18 PM, Mauro Rezzonico wrote:
> I get myself an IBM xSeries 335 model 8676 on eBay a couple of weeks ago,
> installed OpenBSD 4.5 updated to 4.5-stable and did not notice any
> problems...
>
> Today I did a Fresh install of OpenBSD 4.6 and the network does not work!
>
> Unfortunately I am not able to understand what's the matter, meaning that
> the output of ifconfig & netstat look right to me, if I ping the first
> configured NIC (bge0), output is like I'm pinging lo0, any other IP (away,
> same segment, same machine) alway return 'Host is down'.
>
> Additionally, the machine is now unable to reboot itself: it shows the
> kernel message "Syncing disks" and then hangs (with OpenBSD 4.5 it did
> properly reboot itself as long as powerdown itself).
>
> As I said the machine is second hand from eBay, so there may be hardware
> issues I am unaware of, but everything 'just worked fine' with OpenBSD (I
> was able to checkout the 4.5-stable branch e recompile everything).
>
> There is a fxp0 NIC installed in a PCI-X slot.
>
> Moreover my network should not be the issue, as I have a HP Proliant DL145
> G2 on the same segment and on the same switch, that was running OpenBSD 4.5
> (following 4.5-stable), and received a fresh install of OpenBSD 4.6 this
> morning (followed by a checkout of 4.6-stable and a rebuild of everything)
> that is working perfectly fine...
>
> Transcript follows (with dmesg, ifconfig, netstat etc)
>
> **This is the dmesg with OpenBSD 4.5 GENERIC.MP**
>
> OpenBSD 4.5 (GENERIC.MP) #108: Sat Feb 28 14:58:58 MST 2009
>dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC.MP
> cpu0: Intel(R) XEON(TM) CPU 2.40GHz ("GenuineIntel" 686-class) 2.40 GHz
> cpu0: CPU,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 = 3220766720 (3071MB)
> avail mem = 3120787456 (2976MB)
> mainbus0 at root
> bios0 at mainbus0: AT/286+ BIOS, date 09/11/02, BIOS32 rev. 0 @ 0xfd7e1,
> SMBIOS rev. 2.3 @ 0xf7141 (43 entries)
> bios0: vendor IBM version "-[T2E110AUS-1.01]-" date 09/11/2002
> bios0: IBM eserver xSeries 335 -[867665X]-
> acpi0 at bios0: rev 0
> acpi0: tables DSDT FACP APIC ASF!
> acpi0: wakeup devices PCI0(S5)
> 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
> cpu1 at mainbus0: apid 6 (application processor)
> cpu1: Intel(R) XEON(TM) CPU 2.40GHz ("GenuineIntel" 686-class) 2.40 GHz
> cpu1: 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
> cpu2 at mainbus0: apid 1 (application processor)
> cpu2: Intel(R) XEON(TM) CPU 2.40GHz ("GenuineIntel" 686-class) 2.40 GHz
> cpu2: 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
> cpu3 at mainbus0: apid 7 (application processor)
> cpu3: Intel(R) XEON(TM) CPU 2.40GHz ("GenuineIntel" 686-class) 2.40 GHz
> cpu3: 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
> ioapic0 at mainbus0: apid 14 pa 0xfec0, version 11, 16 pins
> ioapic1 at mainbus0: apid 13 pa 0xfec01000, version 11, 16 pins
> ioapic2 at mainbus0: apid 12 pa 0xfec02000, version 11, 16 pins
> acpiprt0 at acpi0: bus 0 (PCI0)
> acpiprt1 at acpi0: bus 1 (PCI1)
> acpiprt2 at acpi0: bus 2 (PCI2)
> acpicpu0 at acpi0
> acpicpu1 at acpi0
> acpicpu2 at acpi0
> acpicpu3 at acpi0
> bios0: ROM list: 0xc/0x8000 0xc8000/0x4000 0xcc000/0x1800
> pci0 at mainbus0 bus 0: configuration mode 1 (bios)
> pchb0 at pci0 dev 0 function 0 "ServerWorks CMIC-WS Host (GC-LE)" rev 0x13
> pchb1 at pci0 dev 0 function 1 "ServerWorks CMIC-WS Host (GC-LE)" rev 0x00
> pchb2 at pci0 dev 0 function 2 "ServerWorks CMIC-LE" rev 0x00
> pci1 at pchb2 bus 1
> mpi0 at pci1 dev 1 function 0 "Symbios Logic 53c1030" rev 0x07: apic 13 int
> 6 (irq 9)
> scsibus0 at mpi0: 16 targets, initiator 7
> sd0 at scsibus0 targ 0 lun 0: SCSI3
> 0/direct fixed
> sd0: 70006MB, 512 bytes/sec, 143374000 sec total
> safte0 at scsibus0 targ 8 lun 0: SCSI2
> 3/processor fixed
> mpi0: target 0 Sync at 80MHz width 16bit offset 63 QAS 0 DT 1 IU 0
> vga1 at pci0 dev 1 function 0 "ATI Rage XL" rev 0x27
> wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
> wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
> fxp0 at pci0 dev 2 function 0 "Intel 8255x" rev 0x0d, i82550: apic 13 int 0
> (irq 10), address 00:02:b3:da:76:86
> inphy0 at fxp0 phy 1: i82555 10/100 PHY, rev. 4
> piixpm0 at pci0 dev 15 function 0 "ServerWorks CSB5" rev 0x93: polling
> iic0 at piixpm0
> spdmem0 at iic0 addr 0x50: 1GB DDR SDRAM registered ECC PC2100CL2.5
> spdm
Re: thanks for 4.6!
> dvorak is make belief benefit. Tell that to my hands tendinitis... but maybe you're not writing enough code for your hands to suffer, Marco. And `j' and `k' are next to each other on dvorak keyboards anyway. Miod
Re: thanks for 4.6!
dvorak is make belief benefit. On Thu, Oct 22, 2009 at 10:19:43PM +0300, Paul Irofti wrote: > On Thu, Oct 22, 2009 at 10:01:47AM -0500, Marco Peereboom wrote: > > On Thu, Oct 22, 2009 at 07:22:27AM +0200, Matthias Kilian wrote: > > > On Wed, Oct 21, 2009 at 10:00:28PM -0700, patrick keshishian wrote: > > > > > Funny, I always disliked CTRL-A being taken by screen, since it was > > > > > so handy to go back to the beginning of the command line in ksh. > > > > > But then, I make a lot of typing errors at the beginning of command > > > > > lines, I guess. :) > > > > > > > > I agree. C-a always annoyed me in screen for the same reason as you > > > > bring up: positioning to the beginning of the shell command. C-b is > > > > almost as annoying in vi when i want to page up ;) ... > > > > > > Some people should really give vi-mode in ksh a try ;-) > > > > As a vi user I can't deal with it > > > > The reason being that you have to use j k to go up and down in the > > history. Life would be bliss if one could reassign the arrow keys. > > Weird, its that which I miss most when I get to an unconfigured shell. > First thing is shoot set -o vi and enjoy. > > And before you shout dvorak, I also used this on qwerty-days :-)
Network problems with OpenBSD 4.6 on a IBM xSeries 335
I get myself an IBM xSeries 335 model 8676 on eBay a couple of weeks
ago, installed OpenBSD 4.5 updated to 4.5-stable and did not notice any
problems...
Today I did a Fresh install of OpenBSD 4.6 and the network does not work!
Unfortunately I am not able to understand what's the matter, meaning
that the output of ifconfig & netstat look right to me, if I ping the
first configured NIC (bge0), output is like I'm pinging lo0, any other
IP (away, same segment, same machine) alway return 'Host is down'.
Additionally, the machine is now unable to reboot itself: it shows the
kernel message "Syncing disks" and then hangs (with OpenBSD 4.5 it did
properly reboot itself as long as powerdown itself).
As I said the machine is second hand from eBay, so there may be hardware
issues I am unaware of, but everything 'just worked fine' with OpenBSD
(I was able to checkout the 4.5-stable branch e recompile everything).
There is a fxp0 NIC installed in a PCI-X slot.
Moreover my network should not be the issue, as I have a HP Proliant
DL145 G2 on the same segment and on the same switch, that was running
OpenBSD 4.5 (following 4.5-stable), and received a fresh install of
OpenBSD 4.6 this morning (followed by a checkout of 4.6-stable and a
rebuild of everything) that is working perfectly fine...
Transcript follows (with dmesg, ifconfig, netstat etc)
**This is the dmesg with OpenBSD 4.5 GENERIC.MP**
OpenBSD 4.5 (GENERIC.MP) #108: Sat Feb 28 14:58:58 MST 2009
dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC.MP
cpu0: Intel(R) XEON(TM) CPU 2.40GHz ("GenuineIntel" 686-class) 2.40 GHz
cpu0: CPU,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 = 3220766720 (3071MB)
avail mem = 3120787456 (2976MB)
mainbus0 at root
bios0 at mainbus0: AT/286+ BIOS, date 09/11/02, BIOS32 rev. 0 @ 0xfd7e1,
SMBIOS rev. 2.3 @ 0xf7141 (43 entries)
bios0: vendor IBM version "-[T2E110AUS-1.01]-" date 09/11/2002
bios0: IBM eserver xSeries 335 -[867665X]-
acpi0 at bios0: rev 0
acpi0: tables DSDT FACP APIC ASF!
acpi0: wakeup devices PCI0(S5)
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
cpu1 at mainbus0: apid 6 (application processor)
cpu1: Intel(R) XEON(TM) CPU 2.40GHz ("GenuineIntel" 686-class) 2.40 GHz
cpu1: 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
cpu2 at mainbus0: apid 1 (application processor)
cpu2: Intel(R) XEON(TM) CPU 2.40GHz ("GenuineIntel" 686-class) 2.40 GHz
cpu2: 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
cpu3 at mainbus0: apid 7 (application processor)
cpu3: Intel(R) XEON(TM) CPU 2.40GHz ("GenuineIntel" 686-class) 2.40 GHz
cpu3: 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
ioapic0 at mainbus0: apid 14 pa 0xfec0, version 11, 16 pins
ioapic1 at mainbus0: apid 13 pa 0xfec01000, version 11, 16 pins
ioapic2 at mainbus0: apid 12 pa 0xfec02000, version 11, 16 pins
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus 1 (PCI1)
acpiprt2 at acpi0: bus 2 (PCI2)
acpicpu0 at acpi0
acpicpu1 at acpi0
acpicpu2 at acpi0
acpicpu3 at acpi0
bios0: ROM list: 0xc/0x8000 0xc8000/0x4000 0xcc000/0x1800
pci0 at mainbus0 bus 0: configuration mode 1 (bios)
pchb0 at pci0 dev 0 function 0 "ServerWorks CMIC-WS Host (GC-LE)" rev 0x13
pchb1 at pci0 dev 0 function 1 "ServerWorks CMIC-WS Host (GC-LE)" rev 0x00
pchb2 at pci0 dev 0 function 2 "ServerWorks CMIC-LE" rev 0x00
pci1 at pchb2 bus 1
mpi0 at pci1 dev 1 function 0 "Symbios Logic 53c1030" rev 0x07: apic 13
int 6 (irq 9)
scsibus0 at mpi0: 16 targets, initiator 7
sd0 at scsibus0 targ 0 lun 0: SCSI3
0/direct fixed
sd0: 70006MB, 512 bytes/sec, 143374000 sec total
safte0 at scsibus0 targ 8 lun 0: SCSI2
3/processor fixed
mpi0: target 0 Sync at 80MHz width 16bit offset 63 QAS 0 DT 1 IU 0
vga1 at pci0 dev 1 function 0 "ATI Rage XL" rev 0x27
wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
fxp0 at pci0 dev 2 function 0 "Intel 8255x" rev 0x0d, i82550: apic 13
int 0 (irq 10), address 00:02:b3:da:76:86
inphy0 at fxp0 phy 1: i82555 10/100 PHY, rev. 4
piixpm0 at pci0 dev 15 function 0 "ServerWorks CSB5" rev 0x93: polling
iic0 at piixpm0
spdmem0 at iic0 addr 0x50: 1GB DDR SDRAM registered ECC PC2100CL2.5
spdmem1 at iic0 addr 0x51: 512MB DDR SDRAM registered ECC PC2100CL2.5
spdmem2 at iic0 addr 0x52: 1GB DDR SDRAM registered ECC PC2100CL2.5
spdmem3 at iic0 addr 0x53: 512MB DDR SDRAM registered ECC PC2100CL2.5
pciide0 at pci0 dev 15 function 1 "ServerWorks CSB5 IDE" rev 0x93: DMA
atapiscsi0 at pciide0 channel 1 drive 0
scsibus1 at atapiscsi0: 2 targets
cd0 at scsibus1 targ 0 lun 0: ATAPI 5/cdrom removable
cd0(
Re: 4.6 reboots x336 ibm server(s)
On Thu, Oct 22, 2009 at 9:20 PM, wrote: > I've seen the same on IBM x346 - install goes fine, reboot, and then it does > not > want to play nice. Installs and boot of all previous versions up until 4.6 work. I rolled back the server to 4.5 home release and it is back and running.
Re: Payment Card Industry (PCI) Data Security Standard HELP!
On 22 October 2009 c. 22:58:53 Stuart VanZee wrote: > The last is 8.5.13 locking users out after 6 failed login > attempts. Quite frankly I find this to be a pretty stupid > requirement as it causes a built in denial of service. I see > how creating a custom Authentication style would allow me to > do this (in spite of my reservations), but I don't really do > much in the way of c coding these days. I have been looking > at the code in login.c and login_passwd.c and I understand > about half of it (I think). If anyone could give me a shove > in the right direction I would sincerely appreciate it. Maybe I'll say something stupid but could not it be treated as "reset login session"? Then you can easily tune it via login.conf. I'd suggest you to have a talk with someone already implemented this requirement... -- Best wishes, Vadim Zhukov A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail?
Re: 4.6 reboots x336 ibm server(s)
Quoting FRLinux : > Hello, > > I have several IBM x series 336 servers and attempted to upgrade them > today. My usual way is to use a build server which makes a release for > my servers. It went well on that server (which is the only one not > being an IBM x336, that will teach me...) so decided to deploy the new > build to the IBM servers. > > When applied and i issued a reboot, the server rebooted after locking > at this line: > > "Intel E7520 Error Reporting" rev 0x0c at pci0 dev 0 function 1 not > configured > ppb0 at pci0 dev 2 function 0 "Intel E7520 PCIE" rev 0x0c > > At this stage, server reboots and its BIOS issues the following: > re-booting due to unexpected NMI at : > > Now, I have tested my build and the official 4.6 ISO which both show > exactly the same behavior. Thinking it might have been a system issue, > I tried 3 other servers which ALL reported the same NMI issue. That > leads me to believe that my systems do not have a hardware issue (as > the NMI message would imply). > > So, it looks like something in the 4.6 kernel code triggers that > behavior and I can test many things and provide output, please let me > know where I can start. > [cut] I've seen the same on IBM x346 - install goes fine, reboot, and then it does not want to play nice. Also got the unexpected NMI at : message. (This was a clean install, not an upgrade, so don't know if 4.5 works on this box or not.) Thanks.
Re: bioctl crypto passphrase file?
On Thu, Oct 22, 2009 at 3:55 PM, elias r. wrote: > > > Am 10/22/09 9:27 PM, schrieb Ted Unangst: >> >> On Thu, Oct 22, 2009 at 3:01 PM, elias r. wrote: >>> >>> thank you :) >>> I'll update it later that day! >>> >>> one question: why did you choose tty over stdin? >>> would using stdin be a security flaw? >> >> As you discovered, making it read from tty makes it harder for people >> to put their put their password in a script, which is generally a good >> idea. > > is it? > how i above mentioned, there are several usecases for this. > and now, when the passphrase-file option is implemented, i don't think you > are right. > i think that there is another reason for not using RPP_STDIN. "Passwords in files is generally bad idea" is not incompatible with "sometimes people think it's a good idea."
Re: bioctl crypto passphrase file?
Am 10/22/09 9:27 PM, schrieb Ted Unangst: On Thu, Oct 22, 2009 at 3:01 PM, elias r. wrote: thank you :) I'll update it later that day! one question: why did you choose tty over stdin? would using stdin be a security flaw? As you discovered, making it read from tty makes it harder for people to put their put their password in a script, which is generally a good idea. is it? how i above mentioned, there are several usecases for this. and now, when the passphrase-file option is implemented, i don't think you are right. i think that there is another reason for not using RPP_STDIN.
Re: a way to specify a specific scsi number at bioctl?
On Thu, Oct 22, 2009 at 11:02:26AM +1000, simplersolut...@gmail.com wrote: > > > > But, for sd on USB, it becomes more difficult to predict where do you > > plan to plug your USB keys. > > An alternative could be to use hotplugd(8) and to mount your "just > > identified sd using its label" on top of the wanted mount point. You > > just need to set a unique label per disk and rely on it. > > > > You can do all of this in config(8) without haing to recompile at all. Not really. Read hotplugd(8) and look for 'disklabel'. -- Olivier Cherrier mailto:o...@symacx.com
Re: bioctl crypto passphrase file?
> On Thu, Oct 22, 2009 at 3:01 PM, elias r. wrote: > > thank you :) > > I'll update it later that day! > > > > one question: why did you choose tty over stdin? > > would using stdin be a security flaw? > > As you discovered, making it read from tty makes it harder for people > to put their put their password in a script, which is generally a good > idea. As well, -p /dev/stdin will work.
4.6 reboots x336 ibm server(s)
Hello,
I have several IBM x series 336 servers and attempted to upgrade them
today. My usual way is to use a build server which makes a release for
my servers. It went well on that server (which is the only one not
being an IBM x336, that will teach me...) so decided to deploy the new
build to the IBM servers.
When applied and i issued a reboot, the server rebooted after locking
at this line:
"Intel E7520 Error Reporting" rev 0x0c at pci0 dev 0 function 1 not configured
ppb0 at pci0 dev 2 function 0 "Intel E7520 PCIE" rev 0x0c
At this stage, server reboots and its BIOS issues the following:
re-booting due to unexpected NMI at :
Now, I have tested my build and the official 4.6 ISO which both show
exactly the same behavior. Thinking it might have been a system issue,
I tried 3 other servers which ALL reported the same NMI issue. That
leads me to believe that my systems do not have a hardware issue (as
the NMI message would imply).
So, it looks like something in the 4.6 kernel code triggers that
behavior and I can test many things and provide output, please let me
know where I can start.
# dmesg
OpenBSD 4.5-stable (GENERIC) #0: Tue Aug 18 09:09:22 IST 2009
r...@puffy:/usr/src/sys/arch/i386/compile/GENERIC
cpu0: Intel(R) Xeon(TM) CPU 3.20GHz ("GenuineIntel" 686-class) 3.21 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,SBF,SSE3,MWAIT,DS-CPL,CNXT-ID,CX16,xTPR
real mem = 3623231488 (3455MB)
avail mem = 3517079552 (3354MB)
mainbus0 at root
bios0 at mainbus0: AT/286+ BIOS, date 02/15/07, BIOS32 rev. 0 @
0xfd6f1, SMBIOS rev. 2.3 @ 0xf5f9e (52 entries)
bios0: vendor IBM version "-[APE137AUS-1.14]-" date 02/15/2007
bios0: IBM eserver xSeries 336 -[883722Y]-
acpi0 at bios0: rev 2
acpi0: tables DSDT FACP APIC MCFG
acpi0: wakeup devices PCI0(S5)
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 200MHz
cpu at mainbus0: not configured
cpu at mainbus0: not configured
cpu at mainbus0: not configured
ioapic0 at mainbus0: apid 14 pa 0xfec0, version 20, 24 pins
ioapic1 at mainbus0: apid 13 pa 0xfec82000, version 20, 24 pins
ioapic2 at mainbus0: apid 12 pa 0xfec82400, version 20, 24 pins
acpiprt0 at acpi0: bus 4 (PCI2)
acpiprt1 at acpi0: bus 5 (PCI3)
acpiprt2 at acpi0: bus 1 (PCIS)
acpiprt3 at acpi0: bus 0 (PCI0)
acpicpu0 at acpi0
bios0: ROM list: 0xc/0xb000
ipmi at mainbus0 not configured
pci0 at mainbus0 bus 0: configuration mode 1 (bios)
pchb0 at pci0 dev 0 function 0 "Intel E7520 Host" rev 0x0c
"Intel E7520 Error Reporting" rev 0x0c at pci0 dev 0 function 1 not configured
ppb0 at pci0 dev 2 function 0 "Intel E7520 PCIE" rev 0x0c
pci1 at ppb0 bus 2
ppb1 at pci0 dev 4 function 0 "Intel E7520 PCIE" rev 0x0c
pci2 at ppb1 bus 3
ppb2 at pci2 dev 0 function 0 "Intel PCIE-PCIE" rev 0x09
pci3 at ppb2 bus 4
ppb3 at pci2 dev 0 function 2 "Intel PCIE-PCIE" rev 0x09
pci4 at ppb3 bus 5
ppb4 at pci0 dev 6 function 0 "Intel E7520 PCIE" rev 0x0c
pci5 at ppb4 bus 6
bge0 at pci5 dev 0 function 0 "Broadcom BCM5721" rev 0x11, BCM5750 B1
(0x4101): apic 14 int 16 (irq 11), address 00:14:5e:0a:08:56
brgphy0 at bge0 phy 1: BCM5750 10/100/1000baseT PHY, rev. 0
ppb5 at pci0 dev 7 function 0 "Intel E7520 PCIE" rev 0x0c
pci6 at ppb5 bus 7
bge1 at pci6 dev 0 function 0 "Broadcom BCM5721" rev 0x11, BCM5750 B1
(0x4101): apic 14 int 16 (irq 11), address 00:14:5e:0a:08:57
brgphy1 at bge1 phy 1: BCM5750 10/100/1000baseT PHY, rev. 0
"Intel E7520 Config" rev 0x0c at pci0 dev 8 function 0 not configured
uhci0 at pci0 dev 29 function 0 "Intel 82801EB/ER USB" rev 0x02: apic
14 int 16 (irq 11)
uhci1 at pci0 dev 29 function 1 "Intel 82801EB/ER USB" rev 0x02: apic
14 int 19 (irq 3)
ehci0 at pci0 dev 29 function 7 "Intel 82801EB/ER USB2" rev 0x02: apic
14 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
ppb6 at pci0 dev 30 function 0 "Intel 82801BA Hub-to-PCI" rev 0xc2
pci7 at ppb6 bus 1
vga1 at pci7 dev 1 function 0 "ATI Radeon VE" rev 0x00
wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
radeondrm0 at vga1: apic 14 int 16 (irq 11)
drm0 at radeondrm0
ichpcib0 at pci0 dev 31 function 0 "Intel 82801EB/ER LPC" rev 0x02
pciide0 at pci0 dev 31 function 2 "Intel 82801EB SATA" 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
wd0 at pciide0 channel 1 drive 0:
wd0: 16-sector PIO, LBA, 76324MB, 156312576 sectors
wd0(pciide0:1:0): using PIO mode 4, Ultra-DMA mode 5
ichiic0 at pci0 dev 31 function 3 "Intel 82801EB/ER SMBus" rev 0x02:
apic 14 int 17 (irq 3)
iic0 at ichiic0
spdmem0 at iic0 addr 0x50: 512MB DDR2 SDRAM registered
Re: bioctl crypto passphrase file?
On Thu, Oct 22, 2009 at 3:01 PM, elias r. wrote: > thank you :) > I'll update it later that day! > > one question: why did you choose tty over stdin? > would using stdin be a security flaw? As you discovered, making it read from tty makes it harder for people to put their put their password in a script, which is generally a good idea.
Re: Payment Card Industry (PCI) Data Security Standard HELP!
Stuart VanZee wrote: The last is 8.5.13 locking users out after 6 failed login attempts. Quite frankly I find this to be a pretty stupid requirement as it causes a built in denial of service. I see how creating a custom Authentication style would allow me to do this (in spite of my reservations), but I don't really do much in the way of c coding these days. I have been looking at the code in login.c and login_passwd.c and I understand about half of it (I think). If anyone could give me a shove in the right direction I would sincerely appreciate it. You might also want to see if you can accomplish what you want with login_radius or login_ldap (the latter is in ports) and a RADIUS or LDAP server. -- Matthew Weigel hacker unique & idempot . ent
Re: Keyboad layout on Macbook?
> I've just installe 4.5 on my Macbook. [...] > Unfortunately I can't get my keyboard function right! The most needed keys > aren't recognized (in ksh). "< > | etc" > There is no output when I press the keys :-( (neither in PC-style nor > Mac-Style) This seems to be a common problem with Apple hardware, they use their own ``holier than thou'' keyboard layouts. We support a few of their deviant layout as ``countrycode.apple'' keymaps. However there is no ``de.apple'' keyboard layout yet. To help creating one, could you send us a description of the keyboard layout (picture or pdf reference), as well as a list of the keys which produce the wrong output _in console mode_ (key label, and output you get). As for the keys not producing any output, an output of `hexdump -C /dev/wskbd' and telling which keys you pressed will do, but you will need to `pkill hexdump' from a remote session afterwards, since ^C will not work. This work will allow us to provide a working `de.apple' console layout. As for X configuration, I'm afraid I don't know what can be done besides using xmodmap to reconfigure the keys. Miod
Re: muting the keyboard bell with wsconsctl isn't working anymore
> Since the Oct.16 snapshot I can not disable the keyboard bell (beel) with > wsconsctl(8). > > $ wsconsctl > [...] > keyboard.bell.pitch=0 > keyboard.bell.period=0 > keyboard.bell.volume=0 > keyboard.bell.pitch.default=0 > keyboard.bell.period.default=0 > keyboard.bell.volume.default=0 > [...] > > Still I can hear the beep with eg.: echo '^G' You probably use an USB keyboard, which attaches as wskbd1. Until very recently these keyboards did not bell due to missing plumbing in the kernel. You should be able to mute the bell with # wsconsctl -f /dev/wskbd1 keyboard.volume=0 (and we definitely need to improve wsconsctl to recognize `keyboard1' as a valid device). Miod
Re: openbsd 3.9 umass not linking to a sd
That would void the warranties on the external disks I'm afraid. Is there no way to get this working in a stock 3.9 ? And would it work in 4.6 ? SWA On 22 Oct 2009, at 20:30, Kenneth R Westerback wrote: On Thu, Oct 22, 2009 at 02:48:09PM +0200, Laurens Vets wrote: Hey Swa, I seem to have painted myself in a corner somehow. I can't upgrade without getting the data off of the system and it doesn't want to play nice with USB drives. I could try to look at old school BSD stuff and think about building a new kernel, but the amount of "don't do that" seems to be high, so is there a better path ? Where ? I know it's an old release, trying to fix that, but in order to get there ... And there's no way to temporarily add an internal disk to an onboard IDE port or something? -Laurens Just plug the temp disk in to the IDE port (hoping it doesn't appear earlier than your existing disk in the probe or boot process!), then do the fdisk/disklabel/newfs/mount dance, copy your data off to the new filesystem, and it should be accessable to the new 4.6 install. Ken
Re: thanks for 4.6!
On Thu, Oct 22, 2009 at 10:01:47AM -0500, Marco Peereboom wrote: > On Thu, Oct 22, 2009 at 07:22:27AM +0200, Matthias Kilian wrote: > > On Wed, Oct 21, 2009 at 10:00:28PM -0700, patrick keshishian wrote: > > > > Funny, I always disliked CTRL-A being taken by screen, since it was > > > > so handy to go back to the beginning of the command line in ksh. > > > > But then, I make a lot of typing errors at the beginning of command > > > > lines, I guess. :) > > > > > > I agree. C-a always annoyed me in screen for the same reason as you > > > bring up: positioning to the beginning of the shell command. C-b is > > > almost as annoying in vi when i want to page up ;) ... > > > > Some people should really give vi-mode in ksh a try ;-) > > As a vi user I can't deal with it > > The reason being that you have to use j k to go up and down in the > history. Life would be bliss if one could reassign the arrow keys. Weird, its that which I miss most when I get to an unconfigured shell. First thing is shoot set -o vi and enjoy. And before you shout dvorak, I also used this on qwerty-days :-)
Re: Payment Card Industry (PCI) Data Security Standard HELP!
>Matthew Weigel > > I don't, I'm afraid, and a quick Google (which could have > answered some > of your other questions) suggests that it's come up before > both on misc@ > and elsewhere. I know you don't want to hear about how the > PCI DSS is > wrong, but in this case their wrongness is, I think, the > reason it's not > an available option. > > You could likely implement this yourself with a custom login > style, though. > Thank you all for the help. Yes, more than a few people have pointed out how poorly I did at Goggling this. I really have no excuses for that. I was searching from the wrong direction I guess. On the bright side, because this list houses some of the best brainpower anywhere I have all but two of the requirements finished (yes, the easy ones) and one of the two left I'm sure I can handle on my own. That being 8.5.12 which forces users not to reuse passwords. I'm pretty sure a passwordcheck in login.conf will do that once I code the program to track them. The last is 8.5.13 locking users out after 6 failed login attempts. Quite frankly I find this to be a pretty stupid requirement as it causes a built in denial of service. I see how creating a custom Authentication style would allow me to do this (in spite of my reservations), but I don't really do much in the way of c coding these days. I have been looking at the code in login.c and login_passwd.c and I understand about half of it (I think). If anyone could give me a shove in the right direction I would sincerely appreciate it. s
Re: bioctl crypto passphrase file?
thank you :) I'll update it later that day! one question: why did you choose tty over stdin? would using stdin be a security flaw? Am 10/22/09 12:36 AM, schrieb Marco Peereboom: It's in. On Wed, Oct 21, 2009 at 05:24:06PM +0200, elias r. wrote: Am 10/21/2009 05:11 PM, schrieb Marco Peereboom: I am working on a diff that will do this right. So hang on. On Wed, Oct 21, 2009 at 03:52:47PM +0200, elias r. wrote: Am 10/21/2009 03:43 PM, schrieb Alexander Hall: elias r. wrote: hum, nobody's got an answer? is there maybe a way via the shell pipelining to read the passphrase from a file and write it to stdin? should this work?: bioctl -c C -l /dev/wd0a softraid0
Re: make release fails on sgi
> Maurice Janssen wrote: >> Hi, >> >> I'm trying to build the file sets for 4.6-stable on an O2 machine, but it >> keeps failing with the following error: >> >> >> >> In file included from mips64/cpu.h:358, >> from machine/cpu.h:5, >> from mips64/param.h:44, >> from machine/param.h:42, >> from ../../../../sys/param.h:95, >> from ../../../../altq/altq_subr.c:30: >> ../../../../sys/sched.h:110: error: bit-field `spc_qs' width not an >> integer constant >> *** Error code 1 >> >> Stop in /usr/src/sys/arch/sgi/compile/GENERIC-IP27 (line 92 of >> /usr/share/mk/sys.mk). >> *** Error code 1 >> >> Stop in /usr/src/etc (line 12 of etc.sgi/Makefile.inc). > > > Just had a similar error during building xenocara file sets: > > In file included from /usr/xenocara/xserver/include/miscstruct.h:53, > from /usr/xenocara/xserver/include/regionstr.h:53, > from /usr/xenocara/xserver/include/region.h:51, > from /usr/xenocara/xserver/include/window.h:52, > from /usr/xenocara/xserver/include/input.h:55, > from /usr/xenocara/xserver/include/inputstr.h:52, > from /usr/xenocara/xserver/Xi/selectev.c:60: > /usr/X11R6/include/pixman-1/pixman.h:149: error: bit-field `p1' width not > an integer constant > *** Error code 1 > > Stop in /usr/xenocara/kdrive/obj/Xi (line 821 of Makefile). > > > Can this be caused by flaky hardware? Maybe, but then this could be an unexpected compiler configuration change. Do you have an /etc/mk.conf file specifying fancy compiler options? You might want to look at the files causing compilation problems (sys/sched.h, xenocara/lib/pixman/pixman/pixman.h) and compare them to fresh 4.6 files as well. Or it could be that either /usr/include/machine/_types.h or /usr/include/sys/_types.h has been modified or replaced, and definitions of types such as int32_t are missing. Miod
Re: openbsd 3.9 umass not linking to a sd
You can probably boot an install CD and go to the shell. Assuming you can then see sd* at umass (which is fairly likely), you should be able to mount/newfs as necessary, and copy the data from the ami (pax/tar/cp/dd are available). Or if you have another system running that you can save a backup onto you can easily run dump piped over ssh. On 2009-10-22, Swa Frantzen wrote: > I seem to have painted myself in a corner somehow. > I can't upgrade without getting the data off of the system and it > doesn't want to play nice with USB drives. > > The system: > - amd64 > - generic.mp kernel > - OpenBSD 3.9 > - contains an hardware raid card (AMI) creating 2 "virtual" sd drives: > sd0 and sd1 > Cannot touch them really, they contain precious data. > > When I hook up an USB drive, I get : > > umass0 at uhub1 port 1 configuration 1 interface 0 > umass0: LaCie LaCie HardDrive USB, rev 2.00/0.00, addr 2 > umass0: using SCSI over Bulk-Only > scsibus4 at umass0: 2 targets > > but no sd drive is assigned. (nor do any of those in existence aside > of sd0 and sd1 from the raid controller do anything). > > There are NO other USB devices used on that system, not even a keyboard. > > The system is showing age and I'd like to upgrade it, but without > having an offline copy of the data that's not going to happen. > And the LTO-3 tape drive is flacky at best, so I'd like to by some > really big external drives as backup (the AMI provides about 3Tbyte of > space) > > So I'd need to know how to trigger the kernel to let me do something > with that umass0 by "linking" it to a sd2 or so. > > Might there be too many scsibusses for the generic kernel? > > scsibus0: atapi CDROM > scsibus1: adaptec controller > scsibus2: AMI > scsibus3: AMI > scsibus4: USB > > I could try to look at old school BSD stuff and think about building a > new kernel, but the amount > of "don't do that" seems to be high, so is there a better path ? Where ? > > I know it's an old release, trying to fix that, but in order to get > there ... > > SWA > > > # dmesg > OpenBSD 3.9 (GENERIC.MP) #736: Thu Mar 2 04:02:03 MST 2006 > dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/ > GENERIC.MP > real mem = 2146410496 (2096104K) > avail mem = 1835237376 (1792224K) > using 22937 buffers containing 214847488 bytes (209812K) of memory > mainbus0 (root) > mainbus0: Intel MP Specification (Version 1.4) (AMD HAMMER ) > cpu0 at mainbus0: apid 0 (boot processor) > cpu0: AMD Opteron(tm) Processor 246, 2004.80 MHz > cpu0: > FPU > ,VME > ,DE > ,PSE > ,TSC > ,MSR > ,PAE > ,MCE > ,CX8 > ,APIC > ,SEP > ,MTRR > ,PGE > ,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,SSE3,NXE,MMXX,FFXSR,LONG, > 3DNOW2,3DNOW > cpu0: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 1MB > 64b/line 16-way L2 cache > cpu0: ITLB 32 4KB entries fully associative, 8 4MB entries fully > associative > cpu0: DTLB 32 4KB entries fully associative, 8 4MB entries fully > associative > cpu0: apic clock running at 200MHz > cpu1 at mainbus0: apid 1 (application processor) > cpu1: AMD Opteron(tm) Processor 246, 2004.55 MHz > cpu1: > FPU > ,VME > ,DE > ,PSE > ,TSC > ,MSR > ,PAE > ,MCE > ,CX8 > ,APIC > ,SEP > ,MTRR > ,PGE > ,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,SSE3,NXE,MMXX,FFXSR,LONG, > 3DNOW2,3DNOW > cpu1: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 1MB > 64b/line 16-way L2 cache > cpu1: ITLB 32 4KB entries fully associative, 8 4MB entries fully > associative > cpu1: DTLB 32 4KB entries fully associative, 8 4MB entries fully > associative > mpbios: bus 0 is type PCI > mpbios: bus 1 is type PCI > mpbios: bus 2 is type PCI > mpbios: bus 3 is type PCI > mpbios: bus 4 is type PCI > mpbios: bus 5 is type ISA > ioapic0 at mainbus0 apid 2: pa 0x8373bf24, version 11, 24 pins > ioapic1 at mainbus0 apid 3: pa 0x8373be24, version 11, 4 pins > ioapic2 at mainbus0 apid 4: pa 0x8373bd24, version 11, 4 pins > pci0 at mainbus0 bus 0: configuration mode 1 > ppb0 at pci0 dev 6 function 0 "AMD 8111 PCI-PCI" rev 0x07 > pci1 at ppb0 bus 1 > ohci0 at pci1 dev 0 function 0 "AMD 8111 USB" rev 0x0b: apic 2 int 19 > (irq 11), version 1.0, legacy support > usb0 at ohci0: USB revision 1.0 > uhub0 at usb0 > uhub0: AMD OHCI root hub, rev 1.00/1.00, addr 1 > uhub0: 3 ports with 3 removable, self powered > ohci1 at pci1 dev 0 function 1 "AMD 8111 USB" rev 0x0b: apic 2 int 19 > (irq 11), version 1.0, legacy support > usb1 at ohci1: USB revision 1.0 > uhub1 at usb1 > uhub1: AMD OHCI root hub, rev 1.00/1.00, addr 1 > uhub1: 3 ports with 3 removable, self powered > vga1 at pci1 dev 6 function 0 "ATI Rage XL" 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 "AMD AMD8111 LPC" rev 0x05 > pciide0 at pci0 dev 7 function 1 "AMD 8111 IDE" rev 0x03: DMA, channel > 0 configured to compatibility, channel 1 conf
Re: make release fails on sgi
Maurice Janssen wrote: Hi, I'm trying to build the file sets for 4.6-stable on an O2 machine, but it keeps failing with the following error: In file included from mips64/cpu.h:358, from machine/cpu.h:5, from mips64/param.h:44, from machine/param.h:42, from ../../../../sys/param.h:95, from ../../../../altq/altq_subr.c:30: ../../../../sys/sched.h:110: error: bit-field `spc_qs' width not an integer constant *** Error code 1 Stop in /usr/src/sys/arch/sgi/compile/GENERIC-IP27 (line 92 of /usr/share/mk/sys.mk). *** Error code 1 Stop in /usr/src/etc (line 12 of etc.sgi/Makefile.inc). Just had a similar error during building xenocara file sets: In file included from /usr/xenocara/xserver/include/miscstruct.h:53, from /usr/xenocara/xserver/include/regionstr.h:53, from /usr/xenocara/xserver/include/region.h:51, from /usr/xenocara/xserver/include/window.h:52, from /usr/xenocara/xserver/include/input.h:55, from /usr/xenocara/xserver/include/inputstr.h:52, from /usr/xenocara/xserver/Xi/selectev.c:60: /usr/X11R6/include/pixman-1/pixman.h:149: error: bit-field `p1' width not an integer constant *** Error code 1 Stop in /usr/xenocara/kdrive/obj/Xi (line 821 of Makefile). Can this be caused by flaky hardware? Maurice
Re: thanks for 4.6!
Hi misc, I'd like to share a few images with you. You'll probably go "WTF?" at first, but bear with with me, it's going to become clear in the end: 1. This is the entrance to my flat: http://imgur.com/C7XN7.jpg 2. This is my vehicle: http://imgur.com/o0FDH.jpg 3. This is my couch: http://imgur.com/QXpgB.jpg It's really a lilo that's folded and tied down in place, on top of corrugated cardboard boxes, and covered with a blanket. 4. This is some more of my furniture: http://imgur.com/Nwg9m.jpg 5. This is my portable music player: http://imgur.com/f1uzB.jpg 6. This is my best monitor: http://imgur.com/hZQj6.jpg After turning it on, you often have to smack the top of it, otherwise the image will not display correctly. 7. This is my firewall: http://imgur.com/mvhuM.jpg Yes, those are ISA slots. 8. This is my laptop. My *only* laptop: http://imgur.com/Tu1Ft.jpg 9. And *THIS* is my very own, brand spankin new OpenBSD 4.6 CD set: http://imgur.com/YIEh7.jpg *HELL YEAH!* (I especially like the evolution poster. First thing I'm doing is scanning that and printing it out much bigger.) Thank you! :) Thank you -- even though I personally can't wait for wearable computing and head-mounted displays to become widely available. :) Also, I'm actually quite fond of "massive, outdated computer circuitry". :-P But I guess there's a difference between Turing-complete *computers* and DRM and blob-infested *computing appliances* that wipe your ass and smack it too if you dare to want something that the usual RICOs don't like. Thanks and regards, --ropers
Re: openbsd 3.9 umass not linking to a sd
On Thu, Oct 22, 2009 at 02:48:09PM +0200, Laurens Vets wrote: > Hey Swa, > > >I seem to have painted myself in a corner somehow. > >I can't upgrade without getting the data off of the system and it > >doesn't want to play nice with USB drives. > > > > > > >I could try to look at old school BSD stuff and think about > >building a new kernel, but the amount > >of "don't do that" seems to be high, so is there a better path ? Where ? > > > >I know it's an old release, trying to fix that, but in order to > >get there ... > > And there's no way to temporarily add an internal disk to an onboard > IDE port or something? > > -Laurens > Just plug the temp disk in to the IDE port (hoping it doesn't appear earlier than your existing disk in the probe or boot process!), then do the fdisk/disklabel/newfs/mount dance, copy your data off to the new filesystem, and it should be accessable to the new 4.6 install. Ken
Re: Patch file for 4.6 isn't on the ftp server
> the link on this site: > http://www.openbsd.org/errata46.html > for the .tar.gz file with all patches (001 and 002) isn't on the ftp > server. Link directs to: > ftp://ftp.openbsd.org/pub/OpenBSD/patches/4.6.tar.gz > I get 550 No such file or directory. Ah. A script wasn't updated. That file will be on some of the mirrors within a few hours.
Re: thanks for 4.6!
On Thu, Oct 22, 2009 at 07:22:27AM +0200, Matthias Kilian wrote: > On Wed, Oct 21, 2009 at 10:00:28PM -0700, patrick keshishian wrote: > > > Funny, I always disliked CTRL-A being taken by screen, since it was > > > so handy to go back to the beginning of the command line in ksh. > > > But then, I make a lot of typing errors at the beginning of command > > > lines, I guess. :) > > > > I agree. C-a always annoyed me in screen for the same reason as you > > bring up: positioning to the beginning of the shell command. C-b is > > almost as annoying in vi when i want to page up ;) ... > > Some people should really give vi-mode in ksh a try ;-) Yes, and then ` makes a nice prefix on a sun keyboard (mirror image of Esc and easy to slap twice).
Re: thanks for 4.6!
On Thu, Oct 22, 2009 at 07:22:27AM +0200, Matthias Kilian wrote: > On Wed, Oct 21, 2009 at 10:00:28PM -0700, patrick keshishian wrote: > > > Funny, I always disliked CTRL-A being taken by screen, since it was > > > so handy to go back to the beginning of the command line in ksh. > > > But then, I make a lot of typing errors at the beginning of command > > > lines, I guess. :) > > > > I agree. C-a always annoyed me in screen for the same reason as you > > bring up: positioning to the beginning of the shell command. C-b is > > almost as annoying in vi when i want to page up ;) ... > > Some people should really give vi-mode in ksh a try ;-) As a vi user I can't deal with it The reason being that you have to use j k to go up and down in the history. Life would be bliss if one could reassign the arrow keys. > > Ciao, > Kili
Re: thanks for 4.6!
On Wed, Oct 21, 2009 at 09:54:20PM -0400, Nick Holland wrote: > William Boshuck wrote: > > > > The man page is typically excellent, so you can learn > > au besoin on the fly. > > May I also suggest the FAQ article written by tmux author Nicholas > Marriott? >http://www.openbsd.org/faq/faq7.html#tmux A really great page. Thanks.
Patch file for 4.6 isn't on the ftp server
Hi, the link on this site: http://www.openbsd.org/errata46.html for the .tar.gz file with all patches (001 and 002) isn't on the ftp server. Link directs to: ftp://ftp.openbsd.org/pub/OpenBSD/patches/4.6.tar.gz I get 550 No such file or directory. Regards Reni -- Reni Maroufi i...@maroufi.net
Re: smtpd IP log
On Mon, Oct 19, 2009 at 6:21 PM, Philippe NICOLAS wrote: > Anyway is it possible for smtpd to log the IP of the remote server in the > maillog as sendmail did it ? I was asking for the same thing. It's not useful, it's fundamental for any mail server admin. to know: who got our mail, when and with wich answer. Thanks a lot -- Cris, member of G.U.F.I Italian FreeBSD User Group http://www.gufi.org/
Re: Reading kernel limit usage at runtime
On Thu, Oct 22, 2009 at 3:24 PM, stan wrote: > I have a nachine that has run out of process table entries. One of my > co-workers asked how one could check for this, and I am afraid that I did > not know the answwer. > > So, how can one read the usage of kernel limits at rutime? sysctl kern.maxproc is probably what you're after
Re: Reading kernel limit usage at runtime
On Thu, Oct 22, 2009 at 09:24:43AM -0400, stan wrote: > I have a nachine that has run out of process table entries. One of my > co-workers asked how one could check for this, and I am afraid that I did > not know the answwer. > > So, how can one read the usage of kernel limits at rutime? See sysctl(3), KERN_MAXPROC. There is also getrlimit(2), specifically RLIMIT_NPROC, but that returns a different limit. You can compare the output of ps against those (OpenBSD does not appear to expose a system call for this; /usr/src/bin/ps/* is full of calls to kvm_*, see kvm(3)). Note that kern.maxproc can be raised, e.g. via sysctl.conf(5). Joachim
Re: Reading kernel limit usage at runtime
man systat On Thu, Oct 22, 2009 at 3:24 PM, stan wrote: > I have a nachine that has run out of process table entries. One of my > co-workers asked how one could check for this, and I am afraid that I did > not know the answwer. > > So, how can one read the usage of kernel limits at rutime? > > -- > One of the main causes of the fall of the roman empire was that, lacking > zero, they had no way to indicate successful termination of their C > programs. > > -- http://www.openbsd.org/lyrics.html
Reading kernel limit usage at runtime
I have a nachine that has run out of process table entries. One of my co-workers asked how one could check for this, and I am afraid that I did not know the answwer. So, how can one read the usage of kernel limits at rutime? -- One of the main causes of the fall of the roman empire was that, lacking zero, they had no way to indicate successful termination of their C programs.
Re: openbsd 3.9 umass not linking to a sd
Swa Frantzen wrote:
I can't upgrade without getting the data off of the system and it
doesn't want to play nice with USB drives.
Use the network, Swa... ;)
dump/rsync/rcp/sftp/ftp-put/nfs/wathever over a network link to a
different machine, maybe one that supports your USB disk...
It's not SO slow and, besides, does anybody have better ideas?
P.S.: I think you can do an SFTP remote mount over an SSH port in MAC OS
X ('X-Mailer: Apple Mail (2.936)')...
--
Mauro Rezzonico , Como, Italia
"Maybe this world is another planet's hell" - H.Huxley
Re: openbsd 3.9 umass not linking to a sd
Hey Swa, I seem to have painted myself in a corner somehow. I can't upgrade without getting the data off of the system and it doesn't want to play nice with USB drives. I could try to look at old school BSD stuff and think about building a new kernel, but the amount of "don't do that" seems to be high, so is there a better path ? Where ? I know it's an old release, trying to fix that, but in order to get there ... And there's no way to temporarily add an internal disk to an onboard IDE port or something? -Laurens
Re: less minor install issue
On Thu, Oct 22, 2009 at 03:34:45AM -0400, Daniel Malament wrote: > On 10/22/2009 2:41 AM, Theo de Raadt wrote: > >>There used to be a message before the install script wiped out > >>filesystems with newfs, listing the partitions and asking if you > >>were sure. Was this removed, or did I somehow miss something? > >>And WHY??? > > > >Because it is the install script. > > > >What did you think it was going to do. > > > >It's installing. It's job is to wipe disks. There is no need for > >stupid questions. > > Ah, the sarcasm I was expecting. And here I thought I remembered > the new installer being described as easier to use. (Or did I make > that last part up? Seems the same from a user perspective, just in > a different order. Not that I had a problem with the ease of use > either way, other than this.) > > In fact, there was a particular reason for my question. I had the > vague impression, probably erroneous, I suppose, that it was > possible to get the old install script to only newfs those systems > for which you specified a mount point. I was attempting to check > that in the anticipation that the script was actually going to tell > me what it was going to do. Granted, I probably should have tested > it in a more careful way, but at least the only real damage was to > cause a certain amount of aggravation. > > So assuming that the install script can't do what I was expecting, > is there some other way to do a fresh install to only one/some > partitions on a drive, or are the choices only a) blow the whole > drive away b) install to a clean disk or c) do an upgrade? > > P.S. I look forward to experiencing the usual wonderful work of the > OpenBSD team once I finish cleaning up this mess... The same mechanism to avoid newfs'ing a filesystem is in the new install script. i.e. use (C)ustom disk configuration and do not specify a mount point for the partition(s) you do not want newfs'ed. Asking the question was superfluous since it made no sense if you chose 'auto' and if you chose 'custom' you were taking full control yourself. i.e. at the prompt Use (A)uto layout, (E)dit auto layout, or create (C)ustom layout? [a] just choose (C)ustom and away you go. Ken
Re: output of daily script and man afterboot
On Thu, Oct 22, 2009 at 12:10:06PM +0200, Ingo Schwarze wrote: > > > or a bug of the daily script and how can i turn the mails off? > > Very probably, setting > VERBOSESTATUS=0 > in /etc/daily.local is all you want, see daily(8) for details. Thanks for the hint. I tested the daily script with VERBOSESTATUS=0 and get no mail. This is a better way than before, I will update my site46.tgz containing a /etc/daily.local. Yours Reni -- Reni Maroufi i...@maroufi.net
Re: thanks for 4.6!
On Wed, 21 Oct 2009, Brad Tilley wrote: > On Wed, Oct 21, 2009 at 1:45 PM, John Cosimano > wrote: > > One thing that screen got right is the A key. It's a lot closer to > Ctrl than B. So far, key proximity has been my only annoyance. I'm > guessing that can be customized. I resisted to C-b until now, but finally changed to C-a. Yes, it's easier. Cheers, -- Daniel Bolgheroni FEI - Faculdade de Engenharia Industrial http://www.dbolgheroni.eng.br/mykey ASCII ribbon campaign ( ) against HTML e-mail X / \
Re: Keyboad layout on Macbook?
On Sun, Oct 18, 2009 at 4:14 PM, Elmar Bschorer
wrote:
> Hi all,
>
> I've just installe 4.5 on my Macbook.
> __
> Modellname: B B MacBook
> B Modell-Identifizierung: B B B MacBook2,1
> B Prozessortyp: Intel Core 2 Duo
> B Prozessorgeschwindigkeit: B B 2.16 GHz
> B Anzahl der Prozessoren: B B B 1
> B Gesamtzahl der Kerne: 2
> B L2-Cache: B B 4 MB
> B Speicher: B B 2,5 GB
> B Busgeschwindigkeit: B 667 MHz
> B Boot-ROM-Version: B B MB21.00A5.B07
> B SMC-Version (System): 1.17f0
> B Seriennummer (System): B B B B W87252DJYA4
> B Hardware-UUID: B B B B --1000-8000-0019E33F0DF6
> B Sensor f|r plvtzliche Bewegung:
> B Status: B B B Aktiviert
>
>
> Unfortunately I can't get my keyboard function right! The most needed keys
> aren't recognized (in ksh). "< > | etc"
> There is no output when I press the keys :-( (neither in PC-style nor
> Mac-Style)
>
> My current keymap is de.
> Does anybody know how to get these keys running?
>
> Thanks a lot!
>
> Elmar
>
>
I had the same problem on my macbook. I do not think there is a easy
way to solve this.
What I did was that I mapped around some keys with xmodmap so I could
get the keys I needed to code (e.g [ ], {} etc).
I think that is you only chance.
BR
Dunceor
openbsd 3.9 umass not linking to a sd
I seem to have painted myself in a corner somehow. I can't upgrade without getting the data off of the system and it doesn't want to play nice with USB drives. The system: - amd64 - generic.mp kernel - OpenBSD 3.9 - contains an hardware raid card (AMI) creating 2 "virtual" sd drives: sd0 and sd1 Cannot touch them really, they contain precious data. When I hook up an USB drive, I get : umass0 at uhub1 port 1 configuration 1 interface 0 umass0: LaCie LaCie HardDrive USB, rev 2.00/0.00, addr 2 umass0: using SCSI over Bulk-Only scsibus4 at umass0: 2 targets but no sd drive is assigned. (nor do any of those in existence aside of sd0 and sd1 from the raid controller do anything). There are NO other USB devices used on that system, not even a keyboard. The system is showing age and I'd like to upgrade it, but without having an offline copy of the data that's not going to happen. And the LTO-3 tape drive is flacky at best, so I'd like to by some really big external drives as backup (the AMI provides about 3Tbyte of space) So I'd need to know how to trigger the kernel to let me do something with that umass0 by "linking" it to a sd2 or so. Might there be too many scsibusses for the generic kernel? scsibus0: atapi CDROM scsibus1: adaptec controller scsibus2: AMI scsibus3: AMI scsibus4: USB I could try to look at old school BSD stuff and think about building a new kernel, but the amount of "don't do that" seems to be high, so is there a better path ? Where ? I know it's an old release, trying to fix that, but in order to get there ... SWA # dmesg OpenBSD 3.9 (GENERIC.MP) #736: Thu Mar 2 04:02:03 MST 2006 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/ GENERIC.MP real mem = 2146410496 (2096104K) avail mem = 1835237376 (1792224K) using 22937 buffers containing 214847488 bytes (209812K) of memory mainbus0 (root) mainbus0: Intel MP Specification (Version 1.4) (AMD HAMMER ) cpu0 at mainbus0: apid 0 (boot processor) cpu0: AMD Opteron(tm) Processor 246, 2004.80 MHz cpu0: FPU ,VME ,DE ,PSE ,TSC ,MSR ,PAE ,MCE ,CX8 ,APIC ,SEP ,MTRR ,PGE ,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,SSE3,NXE,MMXX,FFXSR,LONG, 3DNOW2,3DNOW cpu0: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 1MB 64b/line 16-way L2 cache cpu0: ITLB 32 4KB entries fully associative, 8 4MB entries fully associative cpu0: DTLB 32 4KB entries fully associative, 8 4MB entries fully associative cpu0: apic clock running at 200MHz cpu1 at mainbus0: apid 1 (application processor) cpu1: AMD Opteron(tm) Processor 246, 2004.55 MHz cpu1: FPU ,VME ,DE ,PSE ,TSC ,MSR ,PAE ,MCE ,CX8 ,APIC ,SEP ,MTRR ,PGE ,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,SSE3,NXE,MMXX,FFXSR,LONG, 3DNOW2,3DNOW cpu1: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 1MB 64b/line 16-way L2 cache cpu1: ITLB 32 4KB entries fully associative, 8 4MB entries fully associative cpu1: DTLB 32 4KB entries fully associative, 8 4MB entries fully associative mpbios: bus 0 is type PCI mpbios: bus 1 is type PCI mpbios: bus 2 is type PCI mpbios: bus 3 is type PCI mpbios: bus 4 is type PCI mpbios: bus 5 is type ISA ioapic0 at mainbus0 apid 2: pa 0x8373bf24, version 11, 24 pins ioapic1 at mainbus0 apid 3: pa 0x8373be24, version 11, 4 pins ioapic2 at mainbus0 apid 4: pa 0x8373bd24, version 11, 4 pins pci0 at mainbus0 bus 0: configuration mode 1 ppb0 at pci0 dev 6 function 0 "AMD 8111 PCI-PCI" rev 0x07 pci1 at ppb0 bus 1 ohci0 at pci1 dev 0 function 0 "AMD 8111 USB" rev 0x0b: apic 2 int 19 (irq 11), version 1.0, legacy support usb0 at ohci0: USB revision 1.0 uhub0 at usb0 uhub0: AMD OHCI root hub, rev 1.00/1.00, addr 1 uhub0: 3 ports with 3 removable, self powered ohci1 at pci1 dev 0 function 1 "AMD 8111 USB" rev 0x0b: apic 2 int 19 (irq 11), version 1.0, legacy support usb1 at ohci1: USB revision 1.0 uhub1 at usb1 uhub1: AMD OHCI root hub, rev 1.00/1.00, addr 1 uhub1: 3 ports with 3 removable, self powered vga1 at pci1 dev 6 function 0 "ATI Rage XL" 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 "AMD AMD8111 LPC" rev 0x05 pciide0 at pci0 dev 7 function 1 "AMD 8111 IDE" rev 0x03: DMA, channel 0 configured to compatibility, channel 1 configured to compatibility pciide0: channel 0 disabled (no drives) atapiscsi0 at pciide0 channel 1 drive 0 scsibus0 at atapiscsi0: 2 targets cd0 at scsibus0 targ 0 lun 0: <_NEC, DVD_RW ND-3550A, 1.05> SCSI0 5/ cdrom removable cd0(pciide0:1:0): using PIO mode 4, Ultra-DMA mode 2 amdpm0 at pci0 dev 7 function 3 "AMD 8111 Power" rev 0x05: rng active iic0 at amdpm0 admcts0 at iic0 addr 0x2c ppb1 at pci0 dev 10 function 0 "AMD 8131 PCIX" rev 0x12 pci2 at ppb1 bus 2 ahd0 at pci2 dev 1 function 0 "Adaptec AHA-29320A U320" rev 0x10: apic 3 int 1 (irq 5) ahd0: aic7901, U320 Wide Channel A, SCSI Id=7, PCI 33 or 66Mhz, 512 SCBs scsib
Re: output of daily script and man afterboot
Hi Rene,
Rene Maroufi wrote on Thu, Oct 22, 2009 at 09:20:43AM +0200:
> I don't want the output of the daily script mailed.
> In man afterboot (section crontab) is an example to write the output
> in /var/log/daily.out, but this example doesn't work in 4.6.
> I used this always and it was no problem in 4.5, but in 4.6
> I get always mails.
Oops.
I overlooked that reference when changing daily(8).
> Is this a documentation bug in man afterboot
Yes.
The afterboot(8) manual is now wrong indeed.
Sorry.
I will soon prepare a fix.
> or a bug of the daily script and how can i turn the mails off?
Very probably, setting
VERBOSESTATUS=0
in /etc/daily.local is all you want, see daily(8) for details.
Actually, "do not send mail when there is nothing important to tell"
was the main idea of my changes.
In case you literally never want any mail from daily(8) - but i do not
recommend taking that route - you now need to edit the file /etc/daily.
near the very end, look for the lines
[ -s $MAINOUT ] && {
sysctl -n kern.version
uptime
cat $MAINOUT
} 2>&1 | mail -s "`hostname` daily output" root
Comment these, prepending '#' to each line.
But again, i rather recommend VERBOSESTATUS=0.
Leave the crontab(5) alone unless you want to switch off daily(8)
completely, which is definitely NOT recommended.
Switching off daily(8) implies switching off security(8).
Disabling daily(8) mailings outright works differently in 4.6
compared to 4.5. I think it is rarely needed, if ever.
I don't think it has become more difficult.
I think cleaning up the "2>&1 | tee |" mess in crontab(5)
was worth it. So i guess no code fixes are required right now.
Yours,
Ingo
Re: less minor install issue
On 10/22/2009 5:37 AM, William Boshuck wrote: And here I thought I remembered the new installer being described as easier to use. It is. Were it not so quick it would be positively boring. Just don't set mount points for the partitions Perhaps I should clarify: IMO, not double-checking with the user about what specifically to wipe, especially when it used to, is a step back in 'usability' (in the Jakob Nielsen sense) - or to put it another way, user-friendliness. (I know, not particularly an OBSD-prized value). While I don't have difficulty with using the installer to (ahem) install, I also don't necessarily think 'easy to use' has to be synonymous with 'easy to shoot yourself in the foot with'. Even an explicit message about not setting mount points for partitions that shouldn't be erased would be useful. Actually, s/Even an/Also, an/. But thanks for the tip.
Re: less minor install issue
On Thu, Oct 22, 2009 at 03:34:45AM -0400, Daniel Malament wrote: > On 10/22/2009 2:41 AM, Theo de Raadt wrote: > >>There used to be a message before the install script wiped out > >>filesystems with newfs, listing the partitions and asking if you were > >>sure. Was this removed, or did I somehow miss something? And WHY??? > > > >Because it is the install script. > > > >What did you think it was going to do. > > > >It's installing. It's job is to wipe disks. There is no need for > >stupid questions. > > Ah, the sarcasm I was expecting. And here I thought I remembered the > new installer being described as easier to use. It is. Were it not so quick it would be positively boring. Just don't set mount points for the partitions you don't want touched. If you are worried, dump said partitions in the unlikely event (e.g., you mess up) that you need to restore them (something you should do in any case). -wb
Re: bgpd strangeness
If you can try a -current snapshot on it (or at least build a -current bgpd/bgpctl even if you keep this kernel), that would be helpful because we'll know if the problem was already fixed. If it still happens it's worth checking logs for anything unusual, ideally run bgpd -v and make sure that syslog.conf is configured to save everything, for example: !bgpd *.* /var/log/bgpd and touch /var/log/bgpd; pkill -HUP syslogd On 2009-10-21, Csillag Tamas wrote: > Dear bgpd developers, > > I am using openbgpd IPv6 to peer with my ISP (The Hungarian Academic > and Research Network). > > In the current setup they are our only peer. > > It was working all fine with OpenBSD 4.3 but it stopped doing after > the upgrade to 4.6-beta > The full version is: > OpenBSD 4.6-beta (GENERIC) #11: Mon Jun 22 07:52:38 MDT 2009 > t...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC > > I tried to read the manpage tune some options etc... > When I issued "bgpctl show fib" no entries from the bgp peer, no lines > prefixed with "B". > > Later I found out that "bgpctl reload" fixed the issue. > > IPv6 routes are properly set up and show fib shows the needed entries. > > Can you help me what to do? I would like to eliminate the additional > step. Shall I upgrade to the latest snapshot/beta? Are there any > changes? > > I put my config file online here if that helps: > http://users.itk.ppke.hu/~cstamas/priv/bgpd.conf > > Thanks in advance! > > Regards, > cstamas
Re: less minor install issue
On 10/22/2009 4:31 AM, Jan Stary wrote: On Oct 22 03:34:45, Daniel Malament wrote: In fact, there was a particular reason for my question. I had the vague impression, probably erroneous, I suppose, that it was possible to get the old install script to only newfs those systems for which you specified a mount point. Which is exactly what happens with the new install script, too. Hm. I think I may have tried things the wrong way first. (Which like I said, I would have expected to notice _before_ it was too late.) Glad to know I didn't make that bit up, though. :) Also, FAQ 4.5.1 says Install: load OpenBSD onto the system, overwriting whatever may have been there. Note that it is possible to leave some partitions untouched in this process, such as a /home, but otherwise, assume everything else is overwritten. I missed that, but regardless, I'm not seeing anything about how to do that in the FAQ... So assuming that the install script can't do what I was expecting, is there some other way to do a fresh install to only one/some partitions on a drive, or are the choices only a) blow the whole drive away b) install to a clean disk or c) do an upgrade? Just leave the partition without a mount point for it in disklabel. Thanks. I think I may test this out a bit more thoroughly on a spare drive next time before risking further aggravation, though...
Re: Security script in OpenBSD
Elliott Barrere wrote: > What is the preferred procedure for changing files that are watched by > the security script (i.e. present in /etc/changelist)? vi, emacs, $EDITOR, whatever.. :-) > I have a few boxes cloned from one and I would like to change SSH keys > and other sensitive files but the script seems to be changing them > back. It most certainly does not. > Is there documentation somewhere for what the script currently does? Hmmm... Wild guess... The fine manual pages? $ man security or finally $ less /etc/security > > Thanks, > -elliott-
Re: less minor install issue
On Oct 22 03:34:45, Daniel Malament wrote: > In fact, there was a particular reason for my question. I had the vague > impression, probably erroneous, I suppose, that it was possible to get > the old install script to only newfs those systems for which you > specified a mount point. Which is exactly what happens with the new install script, too. Also, FAQ 4.5.1 says Install: load OpenBSD onto the system, overwriting whatever may have been there. Note that it is possible to leave some partitions untouched in this process, such as a /home, but otherwise, assume everything else is overwritten. > So assuming that the install script can't do what I was expecting, is > there some other way to do a fresh install to only one/some partitions > on a drive, or are the choices only a) blow the whole drive away b) > install to a clean disk or c) do an upgrade? Just leave the partition without a mount point for it in disklabel.
Re: Minor install issue
Donald Allen wrote: > When doing a clean install of 4.6 on a machine with a 20 Gb Windows > partition at the beginning of a 60 Gb disk, I needed to create the > OpenBSD (A6) partition. I did so in CHS mode. When it prompted me for > the starting sector of the partition, it offered [1] as the default. > When I hit 'enter', it complained that 0 was not a valid starting > sector. Typing '1' and then 'enter' worked around it. I will submit a > bug report later, if someone else hasn't beaten me to it. That is already fixed in -current. Thanks for noticing though. revision 1.22 date: 2009/07/24 23:28:00; author: halex; state: Exp; lines: +8 -9 properly sanitize the default value in ask_num(...)
Re: less minor install issue
On 10/22/2009 2:41 AM, Theo de Raadt wrote: There used to be a message before the install script wiped out filesystems with newfs, listing the partitions and asking if you were sure. Was this removed, or did I somehow miss something? And WHY??? Because it is the install script. What did you think it was going to do. It's installing. It's job is to wipe disks. There is no need for stupid questions. Ah, the sarcasm I was expecting. And here I thought I remembered the new installer being described as easier to use. (Or did I make that last part up? Seems the same from a user perspective, just in a different order. Not that I had a problem with the ease of use either way, other than this.) In fact, there was a particular reason for my question. I had the vague impression, probably erroneous, I suppose, that it was possible to get the old install script to only newfs those systems for which you specified a mount point. I was attempting to check that in the anticipation that the script was actually going to tell me what it was going to do. Granted, I probably should have tested it in a more careful way, but at least the only real damage was to cause a certain amount of aggravation. So assuming that the install script can't do what I was expecting, is there some other way to do a fresh install to only one/some partitions on a drive, or are the choices only a) blow the whole drive away b) install to a clean disk or c) do an upgrade? P.S. I look forward to experiencing the usual wonderful work of the OpenBSD team once I finish cleaning up this mess...
output of daily script and man afterboot
Hello, I don't want the output of the daily script mailed. In man afterboot (section crontab) is a example to write the output in /var/log/daily.out, but this example doesn't work in 4.6. I used this always and it was no problem in 4.5, but in 4.6 I get always mails. Is this a documentation bug in man afterboot or a bug of the daily script and how can i turn the mails off? Beside this: 4.6 is great. I like tmux and i will try smtpd in the next days. Regards Reni -- Reni Maroufi i...@maroufi.net
