Re: report errors with ports apps
On 2012-03-07, Mihai Popescu mih...@gmail.com wrote: Hello, What is the proper way to report glitches or errors from applications present in ports only ( not in base) ? Is it ok to discuss those on ports@ ? I want to avoid doing this on misc@ from now on. Thank you. Yes ports@ is ok.
Re: My OpenBSD 5.0 installation experience (long rant)
On Wed, Mar 07, 2012 at 08:24:31PM +0100, Benny Lofgren wrote: On 2012-03-07 17.23, Dennis den Brok wrote: On 2012-03-07, Raimo Niskanen raimo+open...@erix.ericsson.se wrote: So I think a pronounced confirmation question before touching the disk is not a bad thing. It is what many would expect. As there seems to be much resistance to one more (redundant) question in the installer, I suggest to add a simple message to that part of the installer, as in (Choosing 'whole disk' will become effective immediately.) or even Use (W)hole disk (writes to disk immediately) or (E)dit the MBR? [whole] In my opinion, this is the single suggestion in this entire thread that's actually worth implementing. It's an easy fix, doesn't change the installer's handling one bit (although it consumes a few more of the precious bytes) and it might actually prevent someone else with attention deficit disorder to wreck their disk in the future. And even if it doesn't, it should at least cool you down enough to opt out of embarking on a rant about it... +1 Regards, /Benny -- internetlabbet.se / work: +46 8 551 124 80 / Words must Benny Lofgren/ mobile: +46 70 718 11 90 / be weighed, / fax:+46 8 551 124 89/not counted. /email: benny -at- internetlabbet.se -- / Raimo Niskanen, Erlang/OTP, Ericsson AB
Re: My OpenBSD 5.0 installation experience (long rant)
On Wed, 2012-03-07 at 16:23 +, Dennis den Brok wrote: As there seems to be much resistance to one more (redundant) question in the installer, I suggest to add a simple message to that part of the installer, as in (Choosing 'whole disk' will become effective immediately.) or even Use (W)hole disk (writes to disk immediately) or (E)dit the MBR? [whole] While the FAQ is indeed clear, the installer's simplicity appears at that point a little deceptive, in that one (I know I was) is tempted to think that such a user-friendly installer would not harm one so easily... Don't you think it all gets too far? One should generally expect that choosing use the whole disk means that all the data on disk will be lost. If the user doesn't pay attention to installer, this wording won't help. Furthermore, the more chatty installer is, the less amount of newcomers would be reading the messages.
Re: My OpenBSD 5.0 installation experience (long rant)
On Wed, 2012-03-07 at 23:06 -0300, Marcos Bento Luna wrote: ...Ok, another try and I'm back staring at the disk partitioning tool, however I cold not guess wich was the correct partition I should select, because the information was displayed in bytes, not GBs, and the OpenBSD partition I had created was of similar size to another three partitions already in place. Sorry, but didn't you notice a message about pressing h for help? If you used it, you would learn that p G will show the gigabytes values. Some linux instalers i used are more straightforward and certainly help people like me to perform a succesfull install the way we want it without screwing everything up. From the linux world the best installer for me was that of Arch Linux, though compared to OpenBSD's one it suffered from lack of polish (and FWIW cfdisk is the worst partitioning tool ever). Some years ago I also tried Ubuntu, OpenSuSE (or what is the current capitalization?), Debian, Fedora and Gentoo, with all of them (may be except Gentoo, where there was no installer at the time) being crappy. Though OpenBSD installer is not the main feature of OpenBSD for me (it is only used to install OS anyway), I wouldn't like it to change in any way now, as I just can't think of a way to make it better.
Re[2]: My OpenBSD 5.0 installation experience (long rant)
08 PP0QQP0 2012, 14:22 PQ Dmitrij D. Czarkoff czark...@gmail.com: On Wed, 2012-03-07 at 16:23 +, Dennis den Brok wrote: Use (W)hole disk (writes to disk immediately) or (E)dit the MBR? [whole] While the FAQ is indeed clear, the installer's simplicity appears at that point a little deceptive, in that one (I know I was) is tempted to think that such a user-friendly installer would not harm one so easily... Don't you think it all gets too far? One should generally expect that choosing use the whole disk means that all the data on disk will be lost. If the user doesn't pay attention to installer, this wording won't help. Furthermore, the more chatty installer is, the less amount of newcomers would be reading the messages. my sentiments exactly. if they don't think about what's written, will it make it better to write some more? besides, what does exactly writes to disk immediately mean? ok, it writes, so what? will it change MBR? will it change something else? or will it just read sector and write it back (i.e. no actual change)? may be the install script may be changed so that it does dd if=/dev/sdXc of=/tmp/sdXc.mbr count=1 so that after chosing the whole disk option and breaking the install script, you still have an option to get your partition table back. it needs to be documented of course...
Re: My OpenBSD 5.0 installation experience (long rant)
On Thu, 08 Mar 2012 10:50:15 +0100 Dmitrij D. Czarkoff wrote: Furthermore, the more chatty installer is, the less amount of newcomers would be reading the messages. I had a thought last night, how worrying that my mind jumped to OpenBSD in front of the TV. It occurred to me that it wasn't too long ago that the installer switched from asking to partition first or had less questions at the beginning and flicking through those quickly may explain why the op hit enter so readily and why this hasn't come up before when the first question was a more important one. Then again I have doubts it will ever come up again too. What was the reason for the re-order?
Re: My OpenBSD 5.0 installation experience (long rant)
On 03/08/12 06:48, Kevin Chadwick wrote: On Thu, 08 Mar 2012 10:50:15 +0100 Dmitrij D. Czarkoff wrote: Furthermore, the more chatty installer is, the less amount of newcomers would be reading the messages. I had a thought last night, how worrying that my mind jumped to OpenBSD in front of the TV. It occurred to me that it wasn't too long ago that the installer switched from asking to partition first or had less questions at the beginning and flicking through those quickly may explain why the op hit enter so readily and why this hasn't come up before when the first question was a more important one. Then again I have doubts it will ever come up again too. What was the reason for the re-order? It was reworked so that in the most common, simplest installs, you could just hit ENTER for almost everything quickly and up-front, then walk away and let the install take place (keep in mind, while many users love their five-minute-install amd64 systems, a lot of developers use machines where a full install may take a long time. We like to be able to walk away and come back to a finished install, not find out its been waiting for us to answer another question). The developers were very proud of and happy with this. This Hit Enter a bunch of times to do the install is a highly desired property by those who do a lot of installs. There have been many internal discussions about adding questions about real options, which have been vetoed because ADDITIONAL QUESTIONS ARE NOT DESIRED. Again, real operational changes are vetoed. Are you sure? questions just don't have a chance. Sorry (but not very. I love it). (the new installer was also smaller, which is also a desirable trait, as that means more devices can be added to (or more accurately, fewer removed from) the install kernels) Nick.
Re: My OpenBSD 5.0 installation experience (long rant)
It really is amazing how much the install is genuinely loved on OpenBSD. I think there are other distributions out there where the installer is liked or even praised, but I would describe my feelings and what I see here as love. It is always a pleasure when I have the chance to show someone the install process for the first time or hear their accounts of success or failure. I started out with OpenBSD around 2.3 and the funny thing is that I am most impressed by how the installer disk setup is improved since those days. At least I don't have to start off the discussion about how c is the whole disk, etc.
Re: My OpenBSD 5.0 installation experience (long rant)
whether Use (W)hole disk or (E)dit the MBR? [whole] or Use (W)hole disk, use the (O)penBSD area, or (E)dit the MBR? [OpenBSD] I would like empty in Square brackets[ ], user should input w/o/e here, only Enter should do nothing but repeat last line.
Re: My OpenBSD 5.0 installation experience (long rant)
On Thu, Mar 08, 2012 at 02:43:46PM +0400, Mo Libden wrote: 08 PP0QQP0 2012, 14:22 PQ Dmitrij D. Czarkoff czark...@gmail.com: On Wed, 2012-03-07 at 16:23 +, Dennis den Brok wrote: Use (W)hole disk (writes to disk immediately) or (E)dit the MBR? [whole] While the FAQ is indeed clear, the installer's simplicity appears at that point a little deceptive, in that one (I know I was) is tempted to think that such a user-friendly installer would not harm one so easily... Don't you think it all gets too far? One should generally expect that choosing use the whole disk means that all the data on disk will be lost. If the user doesn't pay attention to installer, this wording won't help. Furthermore, the more chatty installer is, the less amount of newcomers would be reading the messages. my sentiments exactly. if they don't think about what's written, will it make it better to write some more? besides, what does exactly writes to disk immediately mean? ok, it writes, so what? will it change MBR? will it change something else? or will it just read sector and write it back (i.e. no actual change)? The point is that when you choose [W] or [Enter] the MBR is overwritten with new content erasing all existing partitions but if you choose [E] you get to the MBR editor, where you will have to explicitly order it to write to the MBR. And the immediate action of the first choice is not obvious from the installer dialogue. This I think shows better what your choices are: (W)rite the MBR to use the whole disk or (E)dit the MBR? [write] Where the two operations Write and Edit have a clear contrasting meaning, or: Write the MBR to use the (W)hole disk or (E)dit the MBR? [whole] to not having to change an installer script variable name (a lesser change) -- / Raimo Niskanen, Erlang/OTP, Ericsson AB
Network interfaces order changes on boot
Hello, I ave this 5.0 box I just setup. It works nicely but on boot network interfaces order seems to randomly change. The box has two bye nics, bge0 and bge1. Basically on reboot the box may pick a different device for the physical interfaces than the time before. Swapping cables restores operation, but is painful. Everything is fine otherwise. dmesg and ifconfig output below. thanks dmesg: OpenBSD 5.0 (GENERIC.MP) #59: Wed Aug 17 10:19:44 MDT 2011 dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC.MP cpu0: Intel(R) Pentium(R) D CPU 3.00GHz (GenuineIntel 686-class) 3 GHz cpu0: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUS H,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,EST,CNXT-ID,CX16, xTPR real mem = 3219234816 (3070MB) avail mem = 3156508672 (3010MB) mainbus0 at root bios0 at mainbus0: AT/286+ BIOS, date 01/08/07, BIOS32 rev. 0 @ 0xffe90, SMBIOS rev. 2.3 @ 0xf0450 (72 entries) bios0: vendor Dell Inc. version A09 date 01/08/2007 bios0: Dell Inc. Precision WorkStation 380 acpi0 at bios0: rev 2 acpi0: sleep states S0 S1 S3 S4 S5 acpi0: tables DSDT FACP SSDT APIC BOOT ASF! MCFG HPET acpi0: wakeup devices VBTN(S4) PCI0(S5) PCI4(S5) PCI2(S5) PCI3(S5) PCI1(S5) PCI5(S5) PCI6(S5) MOU_(S3) USB0(S3) USB1(S3) USB2(S3) USB3(S3) 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 199MHz cpu1 at mainbus0: apid 1 (application processor) cpu1: Intel(R) Pentium(R) D CPU 3.00GHz (GenuineIntel 686-class) 3 GHz cpu1: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUS H,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,EST,CNXT-ID,CX16, xTPR ioapic0 at mainbus0: apid 8 pa 0xfec0, version 20, 24 pins ioapic0: misconfigured as apic 0, remapped to apid 8 acpimcfg0 at acpi0 addr 0xf000, bus 0-63 acpihpet0 at acpi0: 14318179 Hz acpiprt0 at acpi0: bus 5 (PCI4) acpiprt1 at acpi0: bus 2 (PCI2) acpiprt2 at acpi0: bus -1 (PCI3) acpiprt3 at acpi0: bus 1 (PCI1) acpiprt4 at acpi0: bus 3 (PCI5) acpiprt5 at acpi0: bus 4 (PCI6) acpiprt6 at acpi0: bus 0 (PCI0) acpicpu0 at acpi0 acpicpu1 at acpi0 acpibtn0 at acpi0: VBTN bios0: ROM list: 0xc/0xf000! 0xcf000/0x2000! 0xd1000/0x2000 0xd3000/0x1000 cpu0: Enhanced SpeedStep disabled by BIOS pci0 at mainbus0 bus 0: configuration mode 1 (bios) pchb0 at pci0 dev 0 function 0 Intel 82955X Host rev 0x00 ppb0 at pci0 dev 1 function 0 Intel 82955X PCIE rev 0x00: apic 8 int 16 pci1 at ppb0 bus 1 vga1 at pci1 dev 0 function 0 vendor NVIDIA, unknown product 0x014e rev 0xa2 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) wsdisplay0: screen 1-5 added (80x25, vt100 emulation) azalia0 at pci0 dev 27 function 0 Intel 82801GB HD Audio rev 0x01: msi azalia0: codecs: Sigmatel STAC9200 audio0 at azalia0 ppb1 at pci0 dev 28 function 0 Intel 82801GB PCIE rev 0x01: apic 8 int 16 pci2 at ppb1 bus 2 ppb2 at pci0 dev 28 function 4 Intel 82801G PCIE rev 0x01: apic 8 int 16 pci3 at ppb2 bus 3 bge0 at pci3 dev 0 function 0 Broadcom BCM5721 rev 0x11, BCM5750 B1 (0x4101): apic 8 int 16, address 00:10:18:18:00:27 brgphy0 at bge0 phy 1: BCM5750 10/100/1000baseT PHY, rev. 0 ppb3 at pci0 dev 28 function 5 Intel 82801G PCIE rev 0x01: apic 8 int 17 pci4 at ppb3 bus 4 bge1 at pci4 dev 0 function 0 Broadcom BCM5751 rev 0x01, BCM5750 A1 (0x4001): apic 8 int 17, address 00:12:3f:7c:c1:e6 brgphy1 at bge1 phy 1: BCM5750 10/100/1000baseT PHY, rev. 0 uhci0 at pci0 dev 29 function 0 Intel 82801GB USB rev 0x01: apic 8 int 21 uhci1 at pci0 dev 29 function 1 Intel 82801GB USB rev 0x01: apic 8 int 22 uhci2 at pci0 dev 29 function 2 Intel 82801GB USB rev 0x01: apic 8 int 18 uhci3 at pci0 dev 29 function 3 Intel 82801GB USB rev 0x01: apic 8 int 23 ehci0 at pci0 dev 29 function 7 Intel 82801GB USB rev 0x01: apic 8 int 21 usb0 at ehci0: USB revision 2.0 uhub0 at usb0 Intel EHCI root hub rev 2.00/1.00 addr 1 ppb4 at pci0 dev 30 function 0 Intel 82801BA Hub-to-PCI rev 0xe1 pci5 at ppb4 bus 5 ichpcib0 at pci0 dev 31 function 0 Intel 82801GB LPC rev 0x01: PM disabled pciide0 at pci0 dev 31 function 1 Intel 82801GB IDE rev 0x01: 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: HL-DT-ST, CDRW/DVD GCC4482, E107 ATAPI 5/cdrom removable cd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 2 pciide0: channel 1 ignored (disabled) ahci0 at pci0 dev 31 function 2 Intel 82801GR AHCI rev 0x01: msi, AHCI 1.1 ahci0: PHY offline on port 1 ahci0: PHY offline on port 2 ahci0: PHY offline on port 3 scsibus1 at ahci0: 32 targets sd0 at scsibus1 targ 0 lun 0: ATA, WDC WD1600JS-75N, 10.0 SCSI3 0/direct fixed t10.ATA_WDC_WD1600JS-75NCB1_WD-WCANM1767909 sd0: 152587MB, 512 bytes/sector, 31250 sectors ichiic0 at pci0 dev 31 function 3 Intel 82801GB SMBus rev 0x01: SMI iic0 at ichiic0 spdmem0 at iic0 addr 0x50:
Re: pfsync changes in current?
On 2012 Mar 07 (Wed) at 15:58:21 +0200 (+0200), Kapetanakis Giannis wrote: :Hi, : :I'm running a setup of Active/backup firewalls with carp/pfsync :successfully for the last year. : :Today I've upgraded the primary firewall to the latest snapshot (12 Feb), :and as soon as the firewall booted it became MASTER before pfsync :bulk transfer completed. : :Mar 7 15:42:04 echidna /bsd: carp: pfsync0 demoted group carp by 1 :to 133 (pfsync bulk start) :Mar 7 15:42:04 echidna /bsd: carp: pfsync0 demoted group pfsync by 1 :to 1 (pfsync bulk start) :Mar 7 15:42:04 echidna /bsd: carp: pfsync0 demoted group carp by -1 :to 128 (pfsyncdev) :Mar 7 15:42:04 echidna /bsd: carp: pfsync0 demoted group pfsync by :-1 to 0 (pfsyncdev) : :At this point carp group is also automatically demoted to 0-zero and :it takes over as MASTER. Can you show this piece from the logs? Do you have additional logs? How are the interfaces connected, do you have a dedicated link for the pfsync traffic? Can you also share your ruleset? :I manually did ifconfig -g carp carpdemote to force it to SLAVE :in order for pfsync bulk transfer to complete and don't loose active :connections. : :Mar 7 15:46:11 echidna /bsd: carp: pfsync0 demoted group carp by -1 :to 0 (pfsync bulk done) :Mar 7 15:46:11 echidna /bsd: carp: pfsync0 demoted group pfsync by :-1 to 0 (pfsync bulk done) : :Secondary firewall is running 5.0 GENERIC#96 i386 from 21 Nov 2011. :Can it be a mis-communication between the 2 firewalls due different :versions? : :regards, : :Giannis : -- Perfect day for scrubbing the floor and other exciting things.
Re: My OpenBSD 5.0 installation experience (long rant)
The installation routine has been thoughtfully designed and does exactly as intended. OpenBSD caters to the craftsman, not the casual user. If a user is not committed to a high level of responsibility (and freedom), install-time is a great time for a wake-up call. I doubt Leonardo will make this same mistake again. He has learned, as we all have, to look at tools from an enhanced perspective. On Mar 8, 2012, at 9:41 AM, Raimo Niskanen wrote: On Thu, Mar 08, 2012 at 02:43:46PM +0400, Mo Libden wrote: 08 PP0QQP0 2012, 14:22 PQ Dmitrij D. Czarkoff czark...@gmail.com: On Wed, 2012-03-07 at 16:23 +, Dennis den Brok wrote: Use (W)hole disk (writes to disk immediately) or (E)dit the MBR? [whole] While the FAQ is indeed clear, the installer's simplicity appears at that point a little deceptive, in that one (I know I was) is tempted to think that such a user-friendly installer would not harm one so easily... Don't you think it all gets too far? One should generally expect that choosing use the whole disk means that all the data on disk will be lost. If the user doesn't pay attention to installer, this wording won't help. Furthermore, the more chatty installer is, the less amount of newcomers would be reading the messages. my sentiments exactly. if they don't think about what's written, will it make it better to write some more? besides, what does exactly writes to disk immediately mean? ok, it writes, so what? will it change MBR? will it change something else? or will it just read sector and write it back (i.e. no actual change)? The point is that when you choose [W] or [Enter] the MBR is overwritten with new content erasing all existing partitions but if you choose [E] you get to the MBR editor, where you will have to explicitly order it to write to the MBR. And the immediate action of the first choice is not obvious from the installer dialogue. This I think shows better what your choices are: (W)rite the MBR to use the whole disk or (E)dit the MBR? [write] Where the two operations Write and Edit have a clear contrasting meaning, or: Write the MBR to use the (W)hole disk or (E)dit the MBR? [whole] to not having to change an installer script variable name (a lesser change) -- / Raimo Niskanen, Erlang/OTP, Ericsson AB
Re: My OpenBSD 5.0 installation experience (long rant)
On Mar 08 07:20:56, Nick Holland wrote: On 03/08/12 06:48, Kevin Chadwick wrote: On Thu, 08 Mar 2012 10:50:15 +0100 Dmitrij D. Czarkoff wrote: Furthermore, the more chatty installer is, the less amount of newcomers would be reading the messages. I had a thought last night, how worrying that my mind jumped to OpenBSD in front of the TV. It occurred to me that it wasn't too long ago that the installer switched from asking to partition first or had less questions at the beginning and flicking through those quickly may explain why the op hit enter so readily and why this hasn't come up before when the first question was a more important one. Then again I have doubts it will ever come up again too. What was the reason for the re-order? It was reworked so that in the most common, simplest installs, you could just hit ENTER for almost everything quickly and up-front, then walk away and let the install take place (keep in mind, while many users love their five-minute-install amd64 systems, a lot of developers use machines where a full install may take a long time. We like to be able to walk away and come back to a finished install, not find out its been waiting for us to answer another question). I remember this being the first selling point for me back when I did my first install. The OS installs I did before (various linuxes) took considerably more time (not mentioning a certain non-open-sourced OS, whose install took hours), and you HAD TO BE THERE ALL THE TIME AND STARE AT THE SCREEN, just to press an occasional OK every now and then. The feature of giving it all my input and walking away was the very first sign that this is what I want. Jan
MATHNASIUM, Gimnasio de Matemáticas. publicidad bo sig
[demime 1.01d removed an attachment of type image/jpeg which had a name of fencontradamente.jpg] [demime 1.01d removed an attachment of type image/jpeg which had a name of rabanero.jpg]
Re: openbsd 5.0 lifebook p1110 kernal panic on suspend/standby
Ted Unangst t...@tedunangst.com writes: As a short term workaround, type -c at the boot prompt, then disable cbb at the next prompt, then quit, and see what happens. I still get a panic and it didn't change the panic string or the trace. Kendall On Wed, Mar 07, 2012, Kendall Shaw wrote: Kendall Shaw ks...@kendallshaw.com writes: Hi, I have a lifebook p1110 which causes a kernel panic related to APM, I think. Either by setting power savings settings in BIOS to suspend or standby, or disabling power savings in BIOS and running apmd and apm -z or apm -S causes a kernal panic. Do you have any advice, other than give up on being able to use suspend? The sub-notebook has no serial port, so I'm typing the trace and ps results: trace: Debugger(d08cee78,d85dde58,d08ad043,d85dde58,0) at Debugger+0x4 panic(d08ad043,d10cc000,d85dde8c,d10aea00,0) at panic+0x5d timeout_add(d10aea4c,a,8,0,d10aea00) at timeout_add+0xbf pccbb_checksockstat(d10aea00,0,0,ff00,0) at pccbb_checksockstat+0x6e pccbbactivate(d10aea00,3,d85ddeec,d059f4b8,d10b1e00) at pccbbactivate+0x409 config_activate_children(d10b1e00,3,3,12,50307dc) at config_activate_children+0x45 config_activate_children(d10b0fc0,3,246,0,1) at config_activate_children+0x45 apm_suspend(2,0,d85ddf50,800b,0) at apm_suspend+0x91 apm_periodic_check(d10b1f80,20,d097df84,0,d10b1f80) at apm_periodic_check+0x19c apm_thread(d10b1f80) at apm_thread+0x20 Bad frame pointer: 0xd0b8ce38 ps: apmd getty ksh cron inetd sendmail sshd ntpd pflogd syslogd dhclient aiodoned update cleaner reaper pagedown crypto pfpurge pcic0,0,1 pcic0,0,0 usbtask usbatsk apm0 syswq idle0 kmthread init swapper Someone sent me email pointing out that I should include the panic string: timeout_add: not initialized Kendall
STARTTLS DSA vs RSA
I have an OpenBSD system with sendmail/TLS configured according to starttls(8) which calls for DSA keys. I have a situation where an MS Exchange Server contacts my sendmail in an attempt to transfer a message. The transfer fails with no shared cypher. This sendmail handles over 10k messages per day, so DSA is clearly supported by most in email-land. About twice a year, this shared cypher issue comes up. I am not a full time administrator and am not wise to the ways of all things email and crypto, so my question is: Why does starttls(8) describe only DSA ? Is this just because nobody has updated the man page, and are there reasons to prefer one over the other? I am being pressured to fix this. Should I dig into this and figure out how to use both? It looks like the easy thing to do is regenerate the certs with RSA alone. Is that advisable? Thanks, Ray
Re: rsync screams about read-only filesystem
On 03/05/12 21:24, Jiri B wrote: OK I agree I was very vague, mostly because I have thought it must be very obvious PEBKAC. Sorry. Well, here is as much info as I collected. The goal of the script below is to synchronize in memory filesystem directories to USB stick. Some lines are just to print output of the mount state, touch works and listing a test file looks OK. Why does touch work but rsync does not? My bet is you are not writing to the filesystem you expect. I smell symlinks in /mfs/home. /Alexander Thanks for help. jirib %--- #!/bin/sh set -x rc=0 date # main stuff mount | egrep /[ ]+ if mount -uw / ; then mount | egrep /[ ]+ touch /.testfile ls -l /.testfile printf Synchronizing in memory /root to /mfs/root backup ... /usr/local/bin/rsync -vhaz --delete /root/ /mfs/root/ printf Synchronizing in memory /var to /mfs/var backup ... /usr/local/bin/rsync -vhaz --delete -f - *.sock \ -f - **/empty/dev/log \ -f - **/log/ /var/ /mfs/var/ printf Synchronizing in memory /var/log latest data to /mfs/var_log backup ... /usr/local/bin/rsync -vhaz --delete \ -f- *.old -f- *.gz -f- *.[0-9]* /var/log/ /mfs/var_log/ mount -ur / mount | egrep /[ ]+ else echo Error: problem to have writtable '/' filesystem fi let rc=rc+$? # logs mount | egrep /mfs/log[ ]+ if mount -uw /mfs/log ; then mount | egrep /mfs/log[ ]+ touch /mfs/log/.testfile ls -l /mfs/log/.testfile printf Synchronizing in memory /var/log to /mfs/log backup ... /usr/local/bin/rsync -I -vhaz /var/log/ /mfs/log/ mount -ur /mfs/log mount | egrep /mfs/log[ ]+ else echo Error: problem to have writtable '/mfs/log' filesystem fi let rc=rc+$? # home mount | egrep /mfs/home[ ]+ if mount -uw /mfs/home ; then mount | egrep /mfs/home[ ]+ touch /mfs/home/.testfile ls -l /mfs/home/.testfile printf Synchronizing in memory /home to /mfs/home backup ... /usr/local/bin/rsync -I -vhaz --delete /home/ /mfs/home/ mount -ur /mfs/home mount | egrep /mfs/home[ ]+ else echo Error: problem to have writtable '/mfs/home' filesystem fi let rc=rc+$? return $rc ---% %--- + rc=0 + date Mon Mar 5 21:02:22 CET 2012 + mount + egrep /[ ]+ /dev/sd0a on / type ffs (local, noatime, read-only) + mount -uw / + mount + egrep /[ ]+ /dev/sd0a on / type ffs (local, noatime) + touch /.testfile + ls -l /.testfile -rw-r--r-- 1 root wheel 0 Mar 5 21:02 /.testfile + printf Synchronizing in memory /root to /mfs/root backup ... Synchronizing in memory /root to /mfs/root backup ... + /usr/local/bin/rsync -vhaz --delete /root/ /mfs/root/ sending incremental file list ./ .emacs.d/ deleting .emacs.d/auto-save-list/ sent 412 bytes received 22 bytes 868.00 bytes/sec total size is 56.34K speedup is 129.82 + printf Synchronizing in memory /var to /mfs/var backup ... Synchronizing in memory /var to /mfs/var backup ... + /usr/local/bin/rsync -vhaz --delete -f - *.sock -f - **/empty/dev/log -f - **/log/ /var/ /mfs/var/ sending incremental file list sent 20.49K bytes received 199 bytes 41.38K bytes/sec total size is 8.77M speedup is 423.68 + printf Synchronizing in memory /var/log latest data to /mfs/var_log backup ... Synchronizing in memory /var/log latest data to /mfs/var_log backup ...+ /usr/local/bin/rsync -vhaz --delete -f- *.old -f- *.gz -f- *.[0-9]* /var/log/ /mfs/var_log/ sending incremental file list sent 432 bytes received 15 bytes 894.00 bytes/sec total size is 2.21M speedup is 4946.18 + mount -ur / + mount + egrep /[ ]+ /dev/sd0a on / type ffs (local, noatime, read-only) + let rc=rc+0 + mount + egrep /mfs/log[ ]+ /dev/sd0d on /mfs/log type ffs (local, noatime, nodev, noexec, nosuid, read-only) + mount -uw /mfs/log + mount + egrep /mfs/log[ ]+ /dev/sd0d on /mfs/log type ffs (local, noatime, nodev, noexec, nosuid) + touch /mfs/log/.testfile + ls -l /mfs/log/.testfile -rw-r--r-- 1 root wheel 0 Mar 5 21:02 /mfs/log/.testfile + printf Synchronizing in memory /var/log to /mfs/log backup ... Synchronizing in memory /var/log to /mfs/log backup ... + /usr/local/bin/rsync -I -vhaz /var/log/ /mfs/log/ sending incremental file list authlog authlog.0.gz daemon daemon.0.gz daily.out daily.out.old failedlogin ftpd lastlog lpd-errs maillog maillog.0.gz maillog.1.gz maillog.2.gz maillog.3.gz maillog.4.gz messages messages.0.gz messages.1.gz messages.2.gz messages.3.gz messages.4.gz monthly.out pflog pflog.0.gz pflog.1.gz pflog.2.gz secure secure.0.gz security.out security.out.old sendmail.st snmpd weekly.out wtmp wtmp.0 xferlog nginx/access.log nginx/error.log sent 351.11K bytes received 756 bytes 100.53K bytes/sec total size is 2.48M speedup is 7.04 + mount -ur /mfs/log + mount + egrep /mfs/log[ ]+ /dev/sd0d on /mfs/log type ffs (local, noatime, nodev, noexec, nosuid, read-only) + let rc=rc+0 + mount + egrep /mfs/home[ ]+
Re: My OpenBSD 5.0 installation experience (long rant)
On Thu, Mar 8, 2012 at 3:18 AM, Dmitrij D. Czarkoff czark...@gmail.com wrote: Though OpenBSD installer is not the main feature of OpenBSD for me (it is only used to install OS anyway), I wouldn't like it to change in any way now, as I just can't think of a way to make it better. Sorry, hate to beat a dead horse... There is one use case where I would like to see the installer enhanced: I have a laptop with OpenBSD installed. I want to install to a flash/USB drive, or SD card, or eSATA drive... I start the laptop with boot bsd.rd Select (I)nstall Eventually get to the question: Available disks are: sd0 sd1 sd2 Which one is the root disk? (or 'done') [sd0] At this point I usually say oh crap, hit ^c, and go read the dmesg or `disklabel sd1` to make sure I pick the right disk. It would be nice if the installer would tell me a little something about the available disks so I could pick the right one: sd0: 238418MB, 512 bytes/sector, 488281250 sectors sd1: 1907MB, 512 bytes/sector, 3905536 sectors sd2: 3751MB, 512 bytes/sector, 7683072 sectors Available disks are: sd0 sd1 sd2 Which one is the root disk? (or 'done') [sd0] --- install.sub.origThu Mar 8 16:28:52 2012 +++ install.sub Thu Mar 8 16:30:24 2012 @@ -2134,6 +2134,9 @@ # Get ROOTDISK, ROOTDEV and SWAPDEV. while :; do + for _dk in $(get_dkdevs | sed s,^$,none, ); do + dmesg |grep $_dk: |sed -n '$p' + done ask_which disk is the root disk '$(get_dkdevs | sed s,^$,none, )' [[ $resp == done ]] exit [[ $resp != none ]] break
Re: openbsd 5.0 lifebook p1110 kernal panic on suspend/standby
Z --dan -Original Message- From: Kendall Shaw ks...@kendallshaw.com Sender: owner-misc@openbsd.orgDate: Thu, 08 Mar 2012 13:24:42 To: misc@openbsd.org Subject: Re: openbsd 5.0 lifebook p1110 kernal panic on suspend/standby Ted Unangst t...@tedunangst.com writes: As a short term workaround, type -c at the boot prompt, then disable cbb at the next prompt, then quit, and see what happens. I still get a panic and it didn't change the panic string or the trace. Kendall On Wed, Mar 07, 2012, Kendall Shaw wrote: Kendall Shaw ks...@kendallshaw.com writes: Hi, I have a lifebook p1110 which causes a kernel panic related to APM, I think. Either by setting power savings settings in BIOS to suspend or standby, or disabling power savings in BIOS and running apmd and apm -z or apm -S causes a kernal panic. Do you have any advice, other than give up on being able to use suspend? The sub-notebook has no serial port, so I'm typing the trace and ps results: trace: Debugger(d08cee78,d85dde58,d08ad043,d85dde58,0) at Debugger+0x4 panic(d08ad043,d10cc000,d85dde8c,d10aea00,0) at panic+0x5d timeout_add(d10aea4c,a,8,0,d10aea00) at timeout_add+0xbf pccbb_checksockstat(d10aea00,0,0,ff00,0) at pccbb_checksockstat+0x6e pccbbactivate(d10aea00,3,d85ddeec,d059f4b8,d10b1e00) at pccbbactivate+0x409 config_activate_children(d10b1e00,3,3,12,50307dc) at config_activate_children+0x45 config_activate_children(d10b0fc0,3,246,0,1) at config_activate_children+0x45 apm_suspend(2,0,d85ddf50,800b,0) at apm_suspend+0x91 apm_periodic_check(d10b1f80,20,d097df84,0,d10b1f80) at apm_periodic_check+0x19c apm_thread(d10b1f80) at apm_thread+0x20 Bad frame pointer: 0xd0b8ce38 ps: apmd getty ksh cron inetd sendmail sshd ntpd pflogd syslogd dhclient aiodoned update cleaner reaper pagedown crypto pfpurge pcic0,0,1 pcic0,0,0 usbtask usbatsk apm0 syswq idle0 kmthread init swapper Someone sent me email pointing out that I should include the panic string: timeout_add: not initialized Kendall
Re: STARTTLS DSA vs RSA
On Thu, Mar 8, 2012 at 1:49 PM, Raymond Lillard r...@sonic.net wrote: Why does starttls(8) describe only DSA ? ... Is this just because nobody has updated the man page, and are there reasons to prefer one over the other? For quite a while, DSA *was* the Mandatory-To-Implement authentication algorithm for TLS. That changed only after RSA went out of patent protection. Updating the page would be a good thing, if anyone has time... I am being pressured to fix this. Should I dig into this and figure out how to use both? It looks like the easy thing to do is regenerate the certs with RSA alone. Is that advisable? IMO, that's probably the best thing to do. If you have some sort of PKI infrastructure around your existing key(s), then it _might_ be useful to rebuild sendmail to support configuring it with *both* RSA and DSA keys, but I doubt it would be worth the complexity. Philip Guenther
Re: My OpenBSD 5.0 installation experience (long rant)
On Thu, Mar 08, 2012 at 04:40:47PM -0700, Barry Grumbine wrote: On Thu, Mar 8, 2012 at 3:18 AM, Dmitrij D. Czarkoff czark...@gmail.com wrote: Though OpenBSD installer is not the main feature of OpenBSD for me (it is only used to install OS anyway), I wouldn't like it to change in any way now, as I just can't think of a way to make it better. Sorry, hate to beat a dead horse... There is one use case where I would like to see the installer enhanced: I have a laptop with OpenBSD installed. I want to install to a flash/USB drive, or SD card, or eSATA drive... I start the laptop with boot bsd.rd Select (I)nstall Eventually get to the question: Available disks are: sd0 sd1 sd2 Which one is the root disk? (or 'done') [sd0] At this point I usually say oh crap, hit ^c, and go read the dmesg or `disklabel sd1` to make sure I pick the right disk. Why not 'oh crap, hit !, check the disks, exit, and then answer the question'? No need to restart when a shell is a ! away. Exiting the shell reprints the last question. I don't think the size will let everyone identify the disks. Many of my setups have multiple disks with the same size. Ken
Re: My OpenBSD 5.0 installation experience (long rant)
On 07/03/12 15:27 +0100, Leonardo Sabino dos Santos wrote: On Wed, Mar 7, 2012 at 2:44 PM, Russell Garrison russell.garri...@gmail.com wrote: I am absolutely intrigued by this story despite my better judgement. You were able to cook your own full OpenBSD installer on a USB stick with GRUB instead of downloading an ISO or using PXE, but you failed disk setup in the installer? It really would be interesting to see if you can read just http://www.openbsd.org/faq/faq4.html , particularly 4.5.3 and then come back to us with anything other than a mea culpa. I admit to pressing Enter at some of the questions without reading carefully. It simply never crossed my mind that the default action for the installer is to erase the whole disk without chance for review. I still think that's a disaster waiting to happen. You made a stupid assumption. It bit you. I don't see the problem here, you're in the midst of installing an operating system, it wants to make big changes to your system. Pay attention. -- richo || Today's excuse: microelectronic Riemannian curved-space fault in write-only file system http://blog.psych0tik.net [demime 1.01d removed an attachment of type application/pgp-signature which had a name of signature.asc]
Re: My OpenBSD 5.0 installation experience (long rant)
On Thu, Mar 08, 2012, Kenneth R Westerback wrote: On Thu, Mar 08, 2012 at 04:40:47PM -0700, Barry Grumbine wrote: Available disks are: sd0 sd1 sd2 Which one is the root disk? (or 'done') [sd0] At this point I usually say oh crap, hit ^c, and go read the dmesg or `disklabel sd1` to make sure I pick the right disk. Why not 'oh crap, hit !, check the disks, exit, and then answer the question'? No need to restart when a shell is a ! away. Exiting the shell reprints the last question. I think the installer should present enough possible that escaping to shell and restarting is the option of last resort, not standard procedure. I don't think the size will let everyone identify the disks. Many of my setups have multiple disks with the same size. It would have helped me a few times. Even if it doesn't, the proposed change isn't adding questions or interfering with existing users, so I'd call it an improvement.
Re: My OpenBSD 5.0 installation experience (long rant)
On Thu, 2012-03-08 at 16:40 -0700, Barry Grumbine wrote: Available disks are: sd0 sd1 sd2 Which one is the root disk? (or 'done') [sd0] At this point I usually say oh crap, hit ^c, and go read the dmesg or `disklabel sd1` to make sure I pick the right disk. That's interesting, as for me bsd.rd only creates sd0, so I have to find the right sdN in dmesg and then cd /dev; sh MAKEDEV sdN if I want to install OS there...
Snappy Answers to Stupid Questions - WTF?
Do you want users at all? Or was Linus right? -- Fredrik Stax\ang | rot13: s...@hcqngr.hh.fr This is all you need to know about vi: ESC : q ! RET
Re: Snappy Answers to Stupid Questions - WTF?
On Fri, Mar 09, 2012 at 08:28:37AM +0100, Fredrik Staxeng wrote: Do you want users at all? Or was Linus right? well, we *do* prefer those who come with a sense of humor. - P -- Peter N. M. Hansteen, member of the first RFC 1149 implementation team http://bsdly.blogspot.com/ http://www.bsdly.net/ http://www.nuug.no/ Remember to set the evil bit on all malicious network traffic delilah spamd[29949]: 85.152.224.147: disconnected after 42673 seconds.
Re: Snappy Answers to Stupid Questions - WTF?
On Fri, Mar 09, 2012 at 08:28:37AM +0100, Fredrik Staxeng wrote: | Do you want users at all? Or was Linus right? Linus was right. Now please excuse me while I go and masturbate to some other primates[1]. Paul 'WEiRD' de Weerd [1]: http://article.gmane.org/gmane.linux.kernel/706950 PS: Was that snappy enough ? At least your question was indeed pretty stupid... -- [++-]+++.+++[---].+++[+ +++-].++[-]+.--.[-] http://www.weirdnet.nl/
Re: My OpenBSD 5.0 installation experience (long rant)
That's interesting, as for me bsd.rd only creates sd0, so I have to find the right sdN in dmesg and then cd /dev; sh MAKEDEV sdN if I want to install OS there... as somebody else said the easiest thing is to use whatever fdisk you prefer and make an OpenBSD partition before starting the OBSD installer. The OBSD installer usually finds that and you go right to disklabel
