Re: Looking for good, small, canadian version laptop suggestions
On 10/16/13 12:27 PM, Gilbert Sanford wrote: I have purchased over 20 machines (about 50% laptop) from dfsdirectsales.com over the last 5 years, and most of them had next day business support still in effect from Dell. I had only one machine that needed service (a Latitude E6510,) and it was repaired at no charge within 2 days. Nice advertisement for Dell here on the list, but not applicable to the original question. From the FAQ: Does DFS Export? No. DFS does not ship items purchased from www.dfsdirectsales.com outside of the 50 United States. Last time I checked, Canada was not yet among them. Bernd
Re: crypto softraid DUID's
On Thu, Oct 17, 2013 at 07:50:43AM +0200, frantisek holop wrote: hi there, if i have a usb key, that is softraid encrypted, it has 2 DUID's. the first one (before bioctl) can be used to script bioctl when the key is inserted. when the SR CRYPTO drive is attached, it has another DUID. this can be used for mounting/unmounting. my question is, is that a security threat to have this 2nd DUID in /etc/fstab? could it be used as cleartext for brute forcing the SR CRYPTO drive? There are many other known plaintext bits in a filesystem, starting with the FFS magic marker. I don't think DUID matters at all in this context. Now whether it's possible to mount a known plaintext attack on AES-XTS, I leave that to the cryptographers. i also noticed that bioctl -c C -l accepts DUID's, but bioctl -d does not. it this by design? I would love a fix for this... -f -- i'm weird, but i'm saving up to be eccentric.
Re: crypto softraid DUID's
On Thu, Oct 17, 2013 at 01:24:19PM +0200, Tobias Ulmer wrote: On Thu, Oct 17, 2013 at 07:50:43AM +0200, frantisek holop wrote: i also noticed that bioctl -c C -l accepts DUID's, but bioctl -d does not. it this by design? I would love a fix for this... There's a small start here: http://marc.info/?l=openbsd-techm=133513662106783w=2 But it has issues pointed out by jsing which would need to be addressed first: http://marc.info/?l=openbsd-techm=136049955222157w=2
Re: crypto softraid DUID's
i also noticed that bioctl -c C -l accepts DUID's, but bioctl -d does not. it this by design? I would love a fix for this... I would love to see possible to create new crypto softraid devices while passing passphrase via stdin or keyfile :) jirib
Re: virtio network driver multicast support
2013/10/16 Jorge Luiz Silva Peixoto jorge.peix...@gmail.com: Hello, folks! Is IP multicast supported by virtio network driver on OpenBSD 5.3? Does CARP work with virtio network interfaces? Yes, so virtio network driver supports IP multicast, right? :) pfsync is not working when using vio interface with IP multicast. When I set pfsync using syncpeer it works fine. pfsync works when using em interface with IP multicast. The test bed is a couple of virtual machine running on Linux KVM. Thank you! Jorge Peixoto
Re: virtio network driver multicast support
On Thu, Oct 17, 2013 at 10:30:09AM -0300, Jorge Luiz Silva Peixoto wrote: 2013/10/16 Jorge Luiz Silva Peixoto jorge.peix...@gmail.com: Hello, folks! Is IP multicast supported by virtio network driver on OpenBSD 5.3? Does CARP work with virtio network interfaces? Yes, so virtio network driver supports IP multicast, right? :) pfsync is not working when using vio interface with IP multicast. When I set pfsync using syncpeer it works fine. pfsync works when using em interface with IP multicast. The test bed is a couple of virtual machine running on Linux KVM. I would bet the problem is on the virtual switch implementation in Linux. -- :wq Claudio
Re: new queueing subsystem
Hello Otto, Wednesday, October 16, 2013, 10:05:04 AM, you wrote: OM This will not be in 5.4, it wil be in 5.5. If you see shortcomings in OM the docs explain in more detail. It might be a good idea to return the altq section to the pf.conf man page for current. You probably need to mention that the new queuing is using hfsc model and what hfsc model is. I extensively use cbq and very confused by the current queuing manual. It seems that actual speed will be somewhere between min and max (and wont be equal to bandwidth), but how to get an idea where? Does the set prio affect this queuing or just creates some separate queues? -- Best regards, Borismailto:bo...@twopoint.com
Re: new queueing subsystem
It might be a good idea to return the altq section to the pf.conf man page for current. No. It would be better to remove the support now. Documenting the past and the future together never works. The old stuff is going away and does not need documenting.
Re: Looking for good, small, canadian version laptop suggestions
On 13-10-17 01:15 AM, Bernte wrote: On 10/16/13 12:27 PM, Gilbert Sanford wrote: I have purchased over 20 machines (about 50% laptop) from dfsdirectsales.com over the last 5 years, and most of them had next day business support still in effect from Dell. I had only one machine that needed service (a Latitude E6510,) and it was repaired at no charge within 2 days. Nice advertisement for Dell here on the list, but not applicable to the original question. From the FAQ: Does DFS Export? No. DFS does not ship items purchased from www.dfsdirectsales.com outside of the 50 United States. Last time I checked, Canada was not yet among them. Although a number of economists are certain this will happen eventually, it isn't the case quite yet! As I posted prevously, Dell Financial Services Canada has its own website: www.dfsdirect.ca. Their stuff tends to be a bit older, and a bit more expensive than the US site, and support isn't *quite* as good, but they still provide a pretty good deal for people with Canadian shipping addresses. Refurb laptops also show up from time to time on Tigerdirect.ca and Newegg.ca, usually at competitive prices. -- -Adam Thompson athom...@athompso.net
Re: virtio network driver multicast support
On 13-10-16 07:30 AM, Jorge Luiz Silva Peixoto wrote: Hello, folks! Is IP multicast supported by virtio network driver on OpenBSD 5.3? pfsync is not working when using vio interface with IP multicast. When I set pfsync using syncpeer it works fine. pfsync works when using em interface with IP multicast. The test bed is a couple of virtual machine running on Linux KVM. I'm not having any problems with CARP on vio(4)s inside KVM [Proxmox VE 3.1], which uses multicast, so I don't think there's an inherent problem with all multicast. Could still be a corner case with pfsync, though. -- -Adam Thompson athom...@athompso.net
Re: OT: SuperMicro X9SBAA-F with OpenBSD
On Fri, Oct 04, 2013 at 03:22:54PM -0700, Chris Cappuccio wrote: I accidentally got some supermicro boards with IPMI. Not sure why but under OpenBSD the IPMI freaks out crazy all the time. Probably wants to use some memory OpenBSD already uses or some shit. I just ignore the blinking light. One of these days Using Supermicro's IPMIView on OS X, I can use the KVM Console just fine and is very useful for my datacenter installations. The Text Console option has never worked right and I gave up on it quite a while back. This is with OpenBSD 5.3 and later on X9SCL-F, X9SCM-F, and X9SCI-LN4F boards. Bryan
Re: ntfs with big files
On Fri, 11 Oct 2013, Joel Sing wrote: On Thu, 10 Oct 2013, Manuel Giraud wrote: Hi, I have a ntfs partition with rather large (about 3GB) files on it. When I copy these files on a ffs partition they are corrupted. When I try to checksum them directly from the ntfs partition the checksum is not correct (compared to the same file on a fat32 partition copied with Windows). I tried this (with same behaviour) on i386 5.3 release and on i386 last week current. I'm willing to do some testing to fix this issue but don't really know where to start. See if you can isolate the smallest possible reproducable test case. If you create a 3GB file with known content (e.g. the same byte repeated), does the same issue occur? If so, how small do you need to go before the problem goes away? Also, what operating system (and version) was used to write the files to the NTFS volume? Hello, I encountered the same issue. Anything over the 2 GB limit is wrong. I mean, first exactly 2 GB of the file are read correctly, following that I get wrong data till the end of the file. It is reproducible with any file over 2 GB in size so far. Smells like int somewhere... I get the same wrong data with any release since at least 5.0, didn't test anything older, but I bet it is the same. The filesystem is a Windows XP NTFS system disk, 32-bit, the files were copied there with explorer.exe. Regards, David
Experiences with OpenBSD RAID5
It wasn't planned this way, it just happened over time, but I ended up with a couple of machines with a few 3TB RAID1 volumes. As a result, around 18TB total (all HDDs are 3TB) is actually 9TB once RAID1'd. Circumstances change, and I might be able to redeploy those HDDs as a RAID5 array. This, at least in theory, would allow the 18TB total to be realized as 15TB as RAID5, gaining me 6TB. For now, I'm able to back up my RAID1 arrays to non-RAID HDDs. While this makes me nervous, I want to at least try creating a RAID5 setup to experiment on, with an eye to fully replacing RAID1 with RAID5. (6TB of lost capacity is nothing to sneeze at!) I realize the bioctl(8) man page says Use of the CRYPTO RAID 4/5 disciplines are currently considered experimental. However, I've been using RAID1 and CRYTPO in bootable and non-bootable configurations, including full disk encryption, quite happily for a while now. I've tested by removing drives, booting, rebuilding, etc., and I've never had a problem. So while the page may say experimental, I've found CRYPTO to be rock-solid thus far. I've never tried softraid's RAID5, so I have no idea if it truly is experimental, or solid like CRYPTO, or somewhere in between. So I ask my fellow list'ers for their experiences with OpenBSD's RAID5 implementation. (Yes, I'm running -current.) Does it work for you? Have you had any good experiences? Any bad experiences? Have you had to actually rebuild a RAID5 array? Can you add another drive to the array at a later time, or does the array need to be destroyed and rebuilt from scratch? Any questions I'm forgetting? I need to know about these things, from real-world use, before using RAID5 in the long-term. Also, in theory, with RAID5 you only lose one drive for the parity, hence my 18TB non-RAID = 15TB RAID5 math. Is this correct in practise with softraid? All stories are welcome, including private emails. Thanks, -- Scott McEachern https://www.blackstaff.ca Beware the Four Horsemen of the Information Apocalypse: terrorists, drug dealers, kidnappers, and child pornographers. Seems like you can scare any public into allowing the government to do anything with those four. -- Bruce Schneier
Re: Experiences with OpenBSD RAID5
On 10/17/13 20:07, Scott McEachern wrote: ... I realize the bioctl(8) man page says Use of the CRYPTO RAID 4/5 disciplines are currently considered experimental. ... I've never tried softraid's RAID5, so I have no idea if it truly is experimental, or solid like CRYPTO, or somewhere in between. So I ask my fellow list'ers for their experiences with OpenBSD's RAID5 implementation. (Yes, I'm running -current.) Does it work for you? with the exception of the fact there's no code to rebuild a failed disk, works great. that's a pretty big exception for most people. :) Have you had any good experiences? Any bad experiences? Have you had to actually rebuild a RAID5 array? you should be trying this stuff yourself. Doesn't matter if *I* can rebuild your array, it matters if YOU can. You don't have to practice on 3TB disks, you can practice on 10GB disks...though understanding the time required for 3TB disks would be wise. Can you add another drive to the array at a later time, or does the array need to be destroyed and rebuilt from scratch? we'll have to get rebuild working before we get restructure. :) Also, in theory, with RAID5 you only lose one drive for the parity, hence my 18TB non-RAID = 15TB RAID5 math. Is this correct in practise with softraid? other than a 3TB disk is closer to 2.75TB than 3TB, yeah the math works the same with softraid as it does with hw raid. Nick.
SSDs in RAID and bio(4)
I don't have a great deal of experience with SSD disks but was spec'ing some systems to use them. We'd be doing RAID on the hosts and I'd prefer to have something supported by bio(4) for volume management. Do SSDs have any impact on ability to do this? Or can one use the same HW RAID controllers for volume management and bio(4) doesn't have to deal with any differences? Or do SSDs typically require special RAID controllers? Looking at Dell R420s and hoping the PERC controller + SSD combination will work under bio(4) (although knowing precisely the driver/controller would be necessary, I realize). -- DS
Re: Experiences with OpenBSD RAID5
On 10/17/13 20:57, Nick Holland wrote: with the exception of the fact there's no code to rebuild a failed disk, works great. that's a pretty big exception for most people. :) Hmm. That would present a problem. Let me make sure I'm absolutely clear here: A RAID5 array with four disks. I notice via bioctl(8) that one has failed. I pull the failed disk and replace it with my cold spare. I cannot use bioctl -R to incorporate the new disk into the array. Correct? (BTW, I know for a fact it works properly with RAID1.) So basically, if a drive fails, the RAID5 array is permanently borked until completely recreated with a new array, meanwhile I'll be trying to back up my data somewhere else. you should be trying this stuff yourself. Doesn't matter if *I* can rebuild your array, it matters if YOU can. You don't have to practice on 3TB disks, you can practice on 10GB disks...though understanding the time required for 3TB disks would be wise. As you've often advised in the past, test it yourself. I plan on it, just to see what happens. BTW, I tried it once with a 3TB RAID1, and I believe it took two days, but I could be wrong and is hardware-dependent. Either way, it takes a /long/-ass time. other than a 3TB disk is closer to 2.75TB than 3TB, yeah the math works the same with softraid as it does with hw raid. Nick. Yes, sorry for not making clear I realize that. I didn't want to do the usable space, GB/GiB, TB/TiB dance. You know what I mean.., hopefully. Either way, while I have the opportunity, I'm going to create some RAID5 arrays of varying sizes, pull (fail) disks, etc., and just see what happens for myself. Experimenting is fun! Unfortunately, if RAID5 cannot rebuild anything, it's about as useful as a leaky screwdriver and RAID1 remains the only viable option on OpenBSD. Damn. Thanks Nick, as always you're a gem of a resource. -- Scott McEachern https://www.blackstaff.ca Beware the Four Horsemen of the Information Apocalypse: terrorists, drug dealers, kidnappers, and child pornographers. Seems like you can scare any public into allowing the government to do anything with those four. -- Bruce Schneier
porter's handbook - pkg-readmes
While working on a port recently, I was unable to find documentation on
creating a pkg-readme. I'm not sure if it's not there, or I just didn't
look hard enough. In any case, here's a proposed change to
www/faq/ports/specialtopics.html to add some information about
pkg-readmes. If this is something that's better left undocumented to
prevent exponential growth of readme files for frivolous reasons... well,
then feel free to ignore this patch. I'm happy to add more information to
relevant man pages as well, but not sure where it would make sense.
gabe.
Index: specialtopics.html
===
RCS file: /var/cvs/www/faq/ports/specialtopics.html,v
retrieving revision 1.29
diff -u -p -u -r1.29 specialtopics.html
--- specialtopics.html 10 Oct 2012 08:50:07 - 1.29
+++ specialtopics.html 18 Oct 2013 02:04:58 -
@@ -51,6 +51,7 @@ PERFORMANCE OF THIS DOCUMENTATION
lia href=#Audio 3.4 - Audio Applications/a
lia href=#Mandoc 3.5 - Manual pages/a
lia href=#RcScripts 3.6 - rc.d(8) scripts/a
+ lia href=#PkgReadmes 3.7 - Package Readmes/a
/ul
hr
@@ -1217,6 +1218,30 @@ A
script/a can also be found in the templates directory of your ports tree.
+p
+
+a name=PkgReadmes/a
+h23.7 - Package Readmes/h2
+This section provides details on installing a package readme.
+
+h3Does my package need a readme?/h3
+A package may require special instructions to run on OpenBSD, or
+additional files may need to be downloaded before the port will work
+properly, or your port may rely on additional packages to support
+additional functionality. If this is the case, and you are unable to
+provide those features via flavors, a readme may be warranted.
+
+h3Creating and installing a readme/h3
+You can create a README file in the pkg directory of your port with
+the relevant information. Once your file is complete, add
+blockquotepre
+@cwd ${LOCALBASE}/share/doc/pkg-readmes
+${FULLPKGNAME}
+/pre/blockquote
+to your generated PLIST file. This will allow the pkg tools to copy
+your README to /usr/local/share/doc/pkg-readmes/ when your port is
+installed, and notify the user to check there for additional
+information.
p
font color= #e0
Re: Experiences with OpenBSD RAID5
On 10/17/13 21:34, Scott McEachern wrote: On 10/17/13 20:57, Nick Holland wrote: with the exception of the fact there's no code to rebuild a failed disk, works great. that's a pretty big exception for most people. :) Hmm. That would present a problem. Let me make sure I'm absolutely clear here: A RAID5 array with four disks. I notice via bioctl(8) that one has failed. I pull the failed disk and replace it with my cold spare. I cannot use bioctl -R to incorporate the new disk into the array. Correct? (BTW, I know for a fact it works properly with RAID1.) yep. works great for RAID1, not for RAID5. If you think about it, it's a pretty different process between the two. The RAID5 process is not yet written. So basically, if a drive fails, the RAID5 array is permanently borked until completely recreated with a new array, meanwhile I'll be trying to back up my data somewhere else. yep. basically, your RAID5 turns into RAID0 (with a performance hit), and you will need to dump/reload your data before it could be redundant again. Not that this might be without use. At my day job, I've got a machine set up that people use for analyzing large chunks of data. They copy it in, crunch it, then dump it. We are using RAID0 at the moment, but softraid RAID5 could have been used to give a little more cushion when the disk fails, so at least the current analysis could be continued. you should be trying this stuff yourself. Doesn't matter if *I* can rebuild your array, it matters if YOU can. You don't have to practice on 3TB disks, you can practice on 10GB disks...though understanding the time required for 3TB disks would be wise. As you've often advised in the past, test it yourself. hey, I'm redundant! :D I plan on it, just to see what happens. BTW, I tried it once with a 3TB RAID1, and I believe it took two days, but I could be wrong and is hardware-dependent. Either way, it takes a /long/-ass time. exactly. you don't want to promise replace the drive tonight and tomorrow all will be great if it takes two days. RAID5 should have a much longer rebuild time (RAID1: read once, write once. N disk RAID5: read N-1, write once). Also keep in mind that disk system performance during rebuild may be unacceptable for some applications. other than a 3TB disk is closer to 2.75TB than 3TB, yeah the math works the same with softraid as it does with hw raid. Yes, sorry for not making clear I realize that. I didn't want to do the usable space, GB/GiB, TB/TiB dance. You know what I mean.., hopefully. yes, I knew what you meant. I'm just pissed at disk vendors. it's been what, over 15 years they've been doing this? I'm still pissed. :) Either way, while I have the opportunity, I'm going to create some RAID5 arrays of varying sizes, pull (fail) disks, etc., and just see what happens for myself. Experimenting is fun! Unfortunately, if RAID5 cannot rebuild anything, it's about as useful as a leaky screwdriver and RAID1 remains the only viable option on OpenBSD. Damn. Thanks Nick, as always you're a gem of a resource. :) Nick.
Re: npppd / pppoe server troubles
Hi, On Wed, 16 Oct 2013 21:10:25 +0200 Gruel Bruno b.gr...@sdnet.info wrote: As i thought that it's doesn't read my users file i changed the username password but nothing else. Yes, the log shows the session is terminated because the passwords are mismatched. I checked by below snapshots, but I could not repeat the problem. OpenBSD 5.4-current (GENERIC) #77: Sun Oct 13 17:27:52 MDT 2013 dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC OpenBSD 5.4-current (GENERIC) #66: Sun Oct 13 15:54:12 MDT 2013 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC Can you try again with below patch? I'd like to get log for debug. Index: npppd/pap.c === RCS file: /cvs/openbsd/src/usr.sbin/npppd/npppd/pap.c,v retrieving revision 1.7 diff -u -p -r1.7 pap.c --- npppd/pap.c 18 Sep 2012 13:14:08 - 1.7 +++ npppd/pap.c 18 Oct 2013 04:06:27 - @@ -341,7 +341,11 @@ pap_local_authenticate(pap *_this, const pap_response(_this, 1, DEFAULT_SUCCESS_MESSAGE); return; } - } + pap_log(_this, LOG_INFO, password mismatch %s%s, + password, password0); + } else + pap_log(_this, LOG_INFO, could not get password for %s, + username); pap_response(_this, 0, DEFAULT_FAILURE_MESSAGE); }
