Re: OpenBSD mascotte
On 25 Jul 2010, at 21:54, Christian Weisgerber wrote: > (I'm sure if somebody WANTED to, more of them could be made. Somebody > would have to talk to Steiner, find out if they still have the > patterns on file, if not give them an old plushie as a template, > maybe go through a few prototypes, front a few thousand euros for > a hundred-unit or so production run, and then figure out how to > sell them.) If you just wanted a handful then you might be able to find somebody here who would make them: http://etsy.com/ G. -- Sent from my email program on my computer sitting on my desk in my house. http://playr.co.uk/
Re: mount ffs as msdos, system hangs
bofh wrote: > Ok, when I first learnt how to use unix nearly 20 years ago, one of > the things I learnt was that a privileged user can break shit, but > should not cause kernels to hang or crash. That would be considered a > bug. Only DOS and windows 3.1 do that :) Unfortunately it's not that black and white, root can do some evil stuff with the mem/kmem, drm/xf86 and a boat loat of other gateways into kernel land. The point is that root can do a lot of stupid things, this is a feature, not a bug.. abuse wisely. In this case the kernel was told, by root, to interpret garbage on some partition.. pleasing 'root' is a high priority to 'kernel', they have a friends with benefits relationship. It's the best peep show I've seen, excluding all the ones with boobs. Enjoy Unix, I sure do. -Bryan.
Re: mount ffs as msdos, system hangs
frantisek holop wrote: > to know the road ahead, ask those coming back. You mean the ones who like it so much they travel it twice?
Re: mount ffs as msdos, system hangs
On Sun, Jul 25, 2010 at 8:01 PM, frantisek holop wrote: > well done misc@, living up to your name. > the bootcamp of the internet. > > It's better to create a crappy diff that gets rejected than whine incessantly on a mailing list that by your own admission has a reputation for being like boot camp. You claim to know a decent amount about the situation, why not at least take a crack at a fix?
Re: trouble autobooting loongson on gdium?
I updated the pmon paths. It autoboots. It autoboots the kernel. But then it prompts me for two devices (swap and I guess root fs). How do I remove those prompts? same: $ dmesg | grep ral ral0 at pci0 dev 13 function 0 "Ralink RT2561S" rev 0x00: irq 6, address 00:0e:8e:1e:ef:d0 ral0: MAC/BBP RT2561C, RF RT2527 Thanks, - Jay > Date: Sun, 25 Jul 2010 17:54:41 + > From: m...@online.fr > To: jay.kr...@cornell.edu > CC: misc@openbsd.org > Subject: Re: trouble autobooting loongson on gdium? > > > > Does it work after the installation? The installation media is supposed > > > > I don't think so. > > The device is recognized. > > ifconfig reports stuff. > > I think I even got a DHCP address, but can't ping anything. > > Hmm... did the particular wireless chip change on recent models? On the > gdium here it attaches as: > > ral0 at pci0 dev 13 function 0 "Ralink RT2561S" rev 0x00: irq 6, address 00:0e:8e:1f:03:3a > ral0: MAC/BBP RT2561C, RF RT2527 > > ...and I can connect to the neighbour's access point with a simple > ``dhclient ral0''. > > > > This is vecause you copied boot, bsd and bsd.rd to the root of the > > > > Aha. And "boot" varies, per configuration? The one I put there might not be correct? > > No, `boot' is the same for all supported loongson systems. But if you > copy it to the root of the ext2fs partition, you can't create a > directory of the same name. > > I.e. your partition contains > /boot > /bsd > while the installer and the documentation expect > /boot/ > /boot/boot > /boot/bsd > but your layout is fine as long as you update the PMON paths to not have > the `boot/' subdirectory in them. > > Miod
Re: mount ffs as msdos, system hangs
On Sun, Jul 25, 2010 at 10:46:50PM +0200, frantisek holop wrote: > hmm, on Sun, Jul 25, 2010 at 02:29:25PM -0600, Theo de Raadt said that > > > i think it doesnt matter what the user is, this shouldnt > > > be happening. > > > > We make the source code available, and yet noone here has even sat down > > for 30 seconds and gone and checked the kernel msdos mount code and realized > > that it almost nothing it can validate a filesystem on. > > does that almost nothing include the partition type number? > because i dont see why would the kernel msdos mount code > even try to start mounting an msdos filesystem with type of A6. If you wanted to mount according to the partition type number, DON'T USE '-t '. We give you the option to OVERRIDE the partition type number and you made use of that override. You have taken command and we will watch your further progress with interest. We give you the pistol. Even bullets. Shooting the rabbit or your foot is up to you. Ken > > > It saw that space of disk, validated it as msdos, and mounted it. > > > > This is not ffs. When you do stuff like that, we are not your nanny. > > are you really implying that there is no way to identify > a partition as various types of FAT? i think it's time > that you did some reading.. > > -f > -- > to get a loan you must prove you don't need it.
Re: mount ffs as msdos, system hangs
> hmm, on Sun, Jul 25, 2010 at 08:10:32PM -0400, Tony Abernethy said that > > Foreign file systems NEVER get prime attention. > > that's the kind of thinking that comes from redmond. You have no right to speak. > > When you do stupid things the results are rather predictable > > and you compound your error by trying to blame everybody else > > for your own singular lack of sanity. > > i did not blame anyone for my mistake. > just because you report what happened to you > and ask what the others think about, doesnt > mean that i blame them or demand a fix. > it could very well have happened that someone > said, yes this might be a bug, and someone > might have tried to fix it. the end. > > instead of saying right at beginning that for > this and this reason this and this happened > and for this and this reason it is not considered > a problem, this thread could have been a valuable > resource for the archive; but i was sent reading > the source, my parents were insulted and i was > sent to drown in a lake. now i also lack sanity. > > well done misc@, living up to your name. > the bootcamp of the internet. You are the one who makes misc what it is.
Re: mount ffs as msdos, system hangs
hmm, on Sun, Jul 25, 2010 at 08:10:32PM -0400, Tony Abernethy said that > Foreign file systems NEVER get prime attention. that's the kind of thinking that comes from redmond. > When you do stupid things the results are rather predictable > and you compound your error by trying to blame everybody else > for your own singular lack of sanity. i did not blame anyone for my mistake. just because you report what happened to you and ask what the others think about, doesnt mean that i blame them or demand a fix. it could very well have happened that someone said, yes this might be a bug, and someone might have tried to fix it. the end. instead of saying right at beginning that for this and this reason this and this happened and for this and this reason it is not considered a problem, this thread could have been a valuable resource for the archive; but i was sent reading the source, my parents were insulted and i was sent to drown in a lake. now i also lack sanity. well done misc@, living up to your name. the bootcamp of the internet. -f -- to know the road ahead, ask those coming back.
Re: mount ffs as msdos, system hangs
STeve Andre' [and...@msu.edu] wrote: > I think that is a fundamentally flawed assumption. Root can do > *ANYTHING*. Anything at all. Sure, preventing crashes is good, > but you can't get around the fact that root is omniscient. > Had this 'root' been *omniscient*, the incident wouldn't have happened. You probably meant to say that root is, in fact *omnipotent* ! p > On Sunday 25 July 2010 19:16:05 bofh wrote: > > Ok, when I first learnt how to use unix nearly 20 years ago, one of > > the things I learnt was that a privileged user can break shit, but > > should not cause kernels to hang or crash. That would be considered a > > bug. Only DOS and windows 3.1 do that :) > > > > On 7/25/10, STeve Andre' wrote: > > > On Sunday 25 July 2010 18:40:19 frantisek holop wrote: > > >> hmm, on Mon, Jul 26, 2010 at 12:12:32AM +0200, David Vasek said that > > >> > > >> > It is not what happened. The -t msdos was forced by you. But you > > >> > > >> ah shit. you are right :] > > >> > > >> and it worked because ffs does not overwrite the beginning > > >> of the partition. > > >> > > >> i misinterpreted what happened, > > >> but this is still a problem, right? :] > > >> > > >> -f > > > > > > It's a "problem" in that something bad happened, but that is because > > > of an operator error. In particular a root operator error: being root > > > has the potential for unlimited error. There is no fix or check for > > > "rm -rf /", is there. > > > > > > I've not looked at the code so I can't intelligently comment on what > > > checks you can or cannot do, but the fundamental issue is that root > > > has to be aware of every command entered, and must be prepared > > > to fix *anything*. An OS cannot prevent you from most problems. > > > Well, Windows tries, but look at what it feel like to use it... > > > -- > STeve Andre' > Disease Control Warden > Dept. of Political Science > Michigan State University > > A day without Windows is like a day without a nuclear incident. > -- I'm a VIP at my local liquor store and I'm root. Fear me ! -- PGP-Key: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x78AE48D9 PGP-Fingerprint: B4B5 2521 73BF 4BA3 13D2 80ED CF26 BE66 78AE 48D9
Re: mount ffs as msdos, system hangs
I think that is a fundamentally flawed assumption. Root can do *ANYTHING*. Anything at all. Sure, preventing crashes is good, but you can't get around the fact that root is omniscient. On Sunday 25 July 2010 19:16:05 bofh wrote: > Ok, when I first learnt how to use unix nearly 20 years ago, one of > the things I learnt was that a privileged user can break shit, but > should not cause kernels to hang or crash. That would be considered a > bug. Only DOS and windows 3.1 do that :) > > On 7/25/10, STeve Andre' wrote: > > On Sunday 25 July 2010 18:40:19 frantisek holop wrote: > >> hmm, on Mon, Jul 26, 2010 at 12:12:32AM +0200, David Vasek said that > >> > >> > It is not what happened. The -t msdos was forced by you. But you > >> > >> ah shit. you are right :] > >> > >> and it worked because ffs does not overwrite the beginning > >> of the partition. > >> > >> i misinterpreted what happened, > >> but this is still a problem, right? :] > >> > >> -f > > > > It's a "problem" in that something bad happened, but that is because > > of an operator error. In particular a root operator error: being root > > has the potential for unlimited error. There is no fix or check for > > "rm -rf /", is there. > > > > I've not looked at the code so I can't intelligently comment on what > > checks you can or cannot do, but the fundamental issue is that root > > has to be aware of every command entered, and must be prepared > > to fix *anything*. An OS cannot prevent you from most problems. > > Well, Windows tries, but look at what it feel like to use it... -- STeve Andre' Disease Control Warden Dept. of Political Science Michigan State University A day without Windows is like a day without a nuclear incident.
Re: mount ffs as msdos, system hangs
frantisek holop wrote: > the borderline between the useful and useless error checking > is sometimes a bit fuzzy i think. Not THAT fuzzy. Foreign file systems NEVER get prime attention. When you do stupid things the results are rather predictable and you compound your error by trying to blame everybody else for your own singular lack of sanity.
Re: mount ffs as msdos, system hangs
On Sun, Jul 25, 2010 at 11:29 AM, Robert wrote: > I haven't tried this mount, but IMHO if you mount some garbage as a > specific file system type, then the OS should give you an error and > deny the mount. It should not crash. > Maybe you are mounting through a script, for automated backups, or > through the automounter. Now if you insert by accident a wrong medium > then this shouldn't lead to a crash. You want the kernel to detect a bad filesystem at mount time. Let's think through the consequences of that. You can crash a system right now by mounting an otherwise valid ffs partition that has been corrupted in particular ways. This has been documented for *decades* on the mount_ffs man page. (I recall seeing it on the manpage in SunOS 4.1.0 in 1991 or so.) To prevent that, fsck would have to be built into the kernel (you might replace the binary, after all) and run on each mount. Note that 'preen' mode can be trivially tricked too, so each call to mount() will do a full fsck. What, you want to be able to mount a clean 1TB partition in less than an hour? But there might be some corruption in the structures around the 800GB mark! Oh, so you think we should defer this until the data is actually accessed? Really? Have you tried to work out the correctness invariants for this? Remember, since this is an NFS server, stuff can be accessed right after mount without path walking, so your invariants can't depend on path checking being done for them... If you're writing a script that needs to mount possibly corrupt data, then you need to screw your head on and do things like run fsck -y -t on the device first. And use a sane fs type. Philip Guenther
Re: mount ffs as msdos, system hangs
hmm, on Sun, Jul 25, 2010 at 04:33:27PM -0700, Philip Guenther said that > What does that get us? They can still fuck up ld.so or libc, and > poof, most the programs on the system will crash when started! > Overwrite /etc/passwd with /dev/random and rename /bin and your system > will stop being useful. > > WHAT PROBLEM ARE YOU TRYING TO SOLVE? the borderline between the useful and useless error checking is sometimes a bit fuzzy i think. i personally think this is an issue, perhaps not an important one, but one that i dont associate with bsd superior quality, that's all. i mean what was the chance of happening of this? but it could help make the system more robust.. it highlighted an issue "outside the box". -f -- bungee diving - living it up when you're going down!
Re: mount ffs as msdos, system hangs
On Sun, Jul 25, 2010 at 4:16 PM, bofh wrote: > Ok, when I first learnt how to use unix nearly 20 years ago, one of > the things I learnt was that a privileged user can break shit, but > should not cause kernels to hang or crash. That would be considered a > bug. Only DOS and windows 3.1 do that :) Hahahaha cp /etc/termcap /dev/mem That has crashed *every* version UNIX I have worked with, substituting an alternative large file on those pure sysv systems without /etc/termcap, of course. But let's say we figure out a way to do what you suggest and have the kernel robust and protected against all actions of a privileged user. What does that get us? They can still fuck up ld.so or libc, and poof, most the programs on the system will crash when started! Overwrite /etc/passwd with /dev/random and rename /bin and your system will stop being useful. WHAT PROBLEM ARE YOU TRYING TO SOLVE? Philip Guenther
Re: mount ffs as msdos, system hangs
Ok, when I first learnt how to use unix nearly 20 years ago, one of the things I learnt was that a privileged user can break shit, but should not cause kernels to hang or crash. That would be considered a bug. Only DOS and windows 3.1 do that :) On 7/25/10, STeve Andre' wrote: > On Sunday 25 July 2010 18:40:19 frantisek holop wrote: >> hmm, on Mon, Jul 26, 2010 at 12:12:32AM +0200, David Vasek said that >> >> > It is not what happened. The -t msdos was forced by you. But you >> >> ah shit. you are right :] >> >> and it worked because ffs does not overwrite the beginning >> of the partition. >> >> i misinterpreted what happened, >> but this is still a problem, right? :] >> >> -f > > It's a "problem" in that something bad happened, but that is because > of an operator error. In particular a root operator error: being root > has the potential for unlimited error. There is no fix or check for > "rm -rf /", is there. > > I've not looked at the code so I can't intelligently comment on what > checks you can or cannot do, but the fundamental issue is that root > has to be aware of every command entered, and must be prepared > to fix *anything*. An OS cannot prevent you from most problems. > Well, Windows tries, but look at what it feel like to use it... > > -- > STeve Andre' > Disease Control Warden > Dept. of Political Science > Michigan State University > > A day without Windows is like a day without a nuclear incident. > > -- Sent from my mobile device http://www.glumbert.com/media/shift http://www.youtube.com/watch?v=tGvHNNOLnCk "This officer's men seem to follow him merely out of idle curiosity." -- Sandhurst officer cadet evaluation. "Securing an environment of Windows platforms from abuse - external or internal - is akin to trying to install sprinklers in a fireworks factory where smoking on the job is permitted." -- Gene Spafford learn french: http://www.youtube.com/watch?v=30v_g83VHK4
Re: OpenBSD mascotte
> raven wrote: > >> i'm lookin around to get an OpenBSD Mascotte puppet (i dont know if it's >> the right word) in Europe, some time ago i see it on OpenBSD website. On 25 July 2010 22:54, Christian Weisgerber wrote: > > https://https.openbsd.org/images/pluffy.jpg > > There was a small production run of these Puffy plushies manufactured > by Steiner Plueschtiere (www.steiner-pluesch.de). I think it was > Wilhelm Buehler who managed the whole project, and they were then > sold mostly through Wim Vandeputte. > > I'm fairly certain they are not available anymore, and none of the > people originally involved are associated with OpenBSD any longer. I just found this via Google: http://www.linux-discount.de/Store/me19/ME19-A02-INT/de It's possible that *maybe* these folks still have stock. It doesn't say otherwise. regards, --ropers
Re: mount ffs as msdos, system hangs
On Sunday 25 July 2010 18:40:19 frantisek holop wrote: > hmm, on Mon, Jul 26, 2010 at 12:12:32AM +0200, David Vasek said that > > > It is not what happened. The -t msdos was forced by you. But you > > ah shit. you are right :] > > and it worked because ffs does not overwrite the beginning > of the partition. > > i misinterpreted what happened, > but this is still a problem, right? :] > > -f It's a "problem" in that something bad happened, but that is because of an operator error. In particular a root operator error: being root has the potential for unlimited error. There is no fix or check for "rm -rf /", is there. I've not looked at the code so I can't intelligently comment on what checks you can or cannot do, but the fundamental issue is that root has to be aware of every command entered, and must be prepared to fix *anything*. An OS cannot prevent you from most problems. Well, Windows tries, but look at what it feel like to use it... -- STeve Andre' Disease Control Warden Dept. of Political Science Michigan State University A day without Windows is like a day without a nuclear incident.
Re: mount ffs as msdos, system hangs
hmm, on Mon, Jul 26, 2010 at 12:12:32AM +0200, David Vasek said that > It is not what happened. The -t msdos was forced by you. But you ah shit. you are right :] and it worked because ffs does not overwrite the beginning of the partition. i misinterpreted what happened, but this is still a problem, right? :] -f -- when dating a homeless girl you can drop her off anywhere.
Re: mount ffs as msdos, system hangs
Theo de Raadt wrote: Thanks for telling me do so some reading, but a google of your name on these mailing lists will show a 10 year pattern of you not being able to self-help. Something to do with your parents, probably. 'this hammer *sucks* for putting screws in the wall! what's the deal with that?' speaking of long-running patterns i have noticed that frantisek has no end of msdos / windows problems with openbsd. after seeing the regularity with which the problems occur this seems like a stupid configuration. you could avoid all these problems by not using msdos support on openbsd e.g. have an openbsd machine setup as a samba server and save all your files there, instead of having some easily-broken dual-boot or external disk swapping setup. you can definitely put a screw in a wall using a hammer but it may occur to the more astute that you are using the wrong tool for the task.
Re: mount ffs as msdos, system hangs
On Sun, 25 Jul 2010, frantisek holop wrote: hmm, on Sun, Jul 25, 2010 at 02:29:25PM -0600, Theo de Raadt said that i think it doesnt matter what the user is, this shouldnt be happening. We make the source code available, and yet noone here has even sat down for 30 seconds and gone and checked the kernel msdos mount code and realized that it almost nothing it can validate a filesystem on. does that almost nothing include the partition type number? because i dont see why would the kernel msdos mount code even try to start mounting an msdos filesystem with type of A6. Hi Frantisek. It is not what happened. The -t msdos was forced by you. But you were not trying to mount a filesystem with type A6. A typo can happen but your mistake is in your interpretation of what has happened after the typo. Take a break and then think about it carefully. Regards, David
Re: mount ffs as msdos, system hangs
> hmm, on Sun, Jul 25, 2010 at 03:17:53PM -0600, Theo de Raadt said that > > ffs does not use the first 8K of a partition. > > > > You used to have MSDOS on there. > > yes, that is the correct answer. > > > it's a pitty the kernel is ignoring the partition type id. > > it's also a pitty that ffs apparently leaves the first 8k > untouched when creating a partition, begging for foot shooting > like this so other operating systems can go ahead and mount > the ffs partition as msdos and fall over as well. Yes, it is a pity that ffs leaves the first 8K untouched. We'll make sure that your install media from now on zaps the first 8K, where your boot code resides. > and it's a pitty i am such an idiot i dit not know about this > apparently well documented, absolutely common FAQ item > and had the audacity to bring it on this fine mailing list. It's a pity you don't go jump in a lake and drown yourself.
Re: mount ffs as msdos, system hangs
hmm, on Sun, Jul 25, 2010 at 03:17:53PM -0600, Theo de Raadt said that > ffs does not use the first 8K of a partition. > > You used to have MSDOS on there. yes, that is the correct answer. it's a pitty the kernel is ignoring the partition type id. it's also a pitty that ffs apparently leaves the first 8k untouched when creating a partition, begging for foot shooting like this so other operating systems can go ahead and mount the ffs partition as msdos and fall over as well. and it's a pitty i am such an idiot i dit not know about this apparently well documented, absolutely common FAQ item and had the audacity to bring it on this fine mailing list. -f -- user: a technical term used by computer pros. see idiot.
Re: mount ffs as msdos, system hangs
On Sun, Jul 25, 2010 at 4:46 PM, frantisek holop wrote: > does that almost nothing include the partition type number? > because i dont see why would the kernel msdos mount code > even try to start mounting an msdos filesystem with type of A6. You are more likely to see things if you look for them first...
Re: OpenBSD mascotte
2010/7/25 Christian Weisgerber : > patterns on file, if not give them an old plushie as a template, > maybe go through a few prototypes, front a few thousand euros for > a hundred-unit or so production run, and then figure out how to Make that hundreds ; I'm sure Steiner will start with a dozen units. And then somebody would have to sell them; Kernel Concepts (http://shop.kernelconcepts.de/) would be a good idea, since OpenBSD doesn't have booths at Linuxtag etc. anymore. Best Martin
Re: mount ffs as msdos, system hangs
>hmm, on Sun, Jul 25, 2010 at 02:29:25PM -0600, Theo de Raadt said that >> > i think it doesnt matter what the user is, this shouldnt >> > be happening. >> >> We make the source code available, and yet noone here has even sat down >> for 30 seconds and gone and checked the kernel msdos mount code and realized >> that it almost nothing it can validate a filesystem on. > >does that almost nothing include the partition type number? >because i dont see why would the kernel msdos mount code >even try to start mounting an msdos filesystem with type of A6. > >> It saw that space of disk, validated it as msdos, and mounted it. >> >> This is not ffs. When you do stuff like that, we are not your nanny. > >are you really implying that there is no way to identify >a partition as various types of FAT? i think it's time >that you did some reading.. ffs does not use the first 8K of a partition. You used to have MSDOS on there. Thanks for telling me do so some reading, but a google of your name on these mailing lists will show a 10 year pattern of you not being able to self-help. Something to do with your parents, probably.
Re: tmux and rogue window titles in the status line
hmm, on Sun, Jul 25, 2010 at 10:01:18PM +0100, Nicholas Marriott said that > that is not the window title, it is the window name > > you need to unset the automatic-rename option for that window, which > will have been set to off by the rename window escape sequence ok, it is automatic-rename. but maybe i wasn't clear, i dont want to turn off this feature, i rather want to make it useful after a rogue program sets it to some "random" string. if i rename the window to something, it will not change anymore based on what process is running there... is it a bug that after garbling it, it is not being updated anymore what process is running there? -f -- pain is inevitable, suffering is optional.
Re: tmux and rogue window titles in the status line
that is not the window title, it is the window name you need to unset the automatic-rename option for that window, which will have been set to off by the rename window escape sequence On Sun, Jul 25, 2010 at 10:11:17PM +0200, frantisek holop wrote: > i think we are not entirely on the same page here. > i did not meant the xterm, mrxvt, whatever terminal > windows title (or rather, only indirectly), but the > titles down in tmux's status line: > > 0: ksh 1:z!KB$+,*kB4EB4q*uEE"QCaKKEB-ot7B(Fu`E%B D0XD* 2:ksh 3:ksh > > running this: > > > echo \\033]2\;$(hostname)\\007 > > does not "clear" the tmux status line, only the terminal > emulator's title attribute. > > also, when set-title is on, it clears certain part of the title > but not all. > > it's very easy to reproduce this, just cat a binary file > in your terminal (yes, that's my hobby ;-) > > -f > -- > if you pull the wings off a fly, does it become a walk?
Re: OpenBSD mascotte
raven wrote: > i'm lookin around to get an OpenBSD Mascotte puppet (i dont know if it's > the right word) in Europe, some time ago i see it on OpenBSD website. https://https.openbsd.org/images/pluffy.jpg There was a small production run of these Puffy plushies manufactured by Steiner Plueschtiere (www.steiner-pluesch.de). I think it was Wilhelm Buehler who managed the whole project, and they were then sold mostly through Wim Vandeputte. I'm fairly certain they are not available anymore, and none of the people originally involved are associated with OpenBSD any longer. (I'm sure if somebody WANTED to, more of them could be made. Somebody would have to talk to Steiner, find out if they still have the patterns on file, if not give them an old plushie as a template, maybe go through a few prototypes, front a few thousand euros for a hundred-unit or so production run, and then figure out how to sell them.) -- Christian "naddy" Weisgerber na...@mips.inka.de
Re: sd0: 128000MB, 512 bytes/sec, 262144000 sec total - is this true? Kingston's Flash drive
Back from the movie Ronin: "if you have a doubt, there's no doubt". I once got a "nice" similar present in Beijing when they sold me a 2GB fake sony usbkey in 2005 (which was instead 64MB) for 20b,. After many chores with machines hung while copying on it, googling around I found a forum page where all the people who got fooled like I did gathered they said there that these fake keys were sold just to foreigners, and that the only way to use them was to use some proprietary tools to reformat them to the original capacity (btw, some *.exe tools). So I did and at least recovered the key which, with 64MB, still makes good use for a DOS boot. Better than nothing. Btw, now comes the fun part: on that forum there was an englishman complaining he had already mailordered 100 of them and payed UPFRONT :D On Sun, Jul 25, 2010 at 2:14 PM, Siju George wrote: > Hi, > > My Cousin was sold a Kingston Flash drive in the streets of Delhi. > It was told to Him that it was 128 GB. > It has a Kingston label with 128GB printed on it. > In windows as well as on OpenBSD it shows 128GB. > > But you cannot fill it with not more than around 1 GB. > > I guess this is some kind of hoax? > Any body came across these kind of drives? > > thanks > > --Siju
Re: mount ffs as msdos, system hangs
hmm, on Sun, Jul 25, 2010 at 02:29:25PM -0600, Theo de Raadt said that > > i think it doesnt matter what the user is, this shouldnt > > be happening. > > We make the source code available, and yet noone here has even sat down > for 30 seconds and gone and checked the kernel msdos mount code and realized > that it almost nothing it can validate a filesystem on. does that almost nothing include the partition type number? because i dont see why would the kernel msdos mount code even try to start mounting an msdos filesystem with type of A6. > It saw that space of disk, validated it as msdos, and mounted it. > > This is not ffs. When you do stuff like that, we are not your nanny. are you really implying that there is no way to identify a partition as various types of FAT? i think it's time that you did some reading.. -f -- to get a loan you must prove you don't need it.
Re: mount ffs as msdos, system hangs
> hmm, on Sun, Jul 25, 2010 at 01:08:45PM -0600, Theo de Raadt said that > > > > > > > > > > > > > > That's no excuse. The point here is that any unprivileged user can hang > > > the system at will. > > > > I don't see an unprivleged user. > > > > I see root performing the mount, since only root can perform mounts > > (unless a sysctl is activated, which noone uses). > > i sent the example as root, but i happen to use that sysctl. So it is root. > i havent tested this as unprivileged user though. Tough. If you enable that sysctl, it is your own responsibility. > i think it doesnt matter what the user is, this shouldnt > be happening. We make the source code available, and yet noone here has even sat down for 30 seconds and gone and checked the kernel msdos mount code and realized that it almost nothing it can validate a filesystem on. It saw that space of disk, validated it as msdos, and mounted it. This is not ffs. When you do stuff like that, we are not your nanny.
Re: mount ffs as msdos, system hangs
hmm, on Sun, Jul 25, 2010 at 01:08:45PM -0600, Theo de Raadt said that > > > > > > > > > > That's no excuse. The point here is that any unprivileged user can hang > > the system at will. > > I don't see an unprivleged user. > > I see root performing the mount, since only root can perform mounts > (unless a sysctl is activated, which noone uses). i sent the example as root, but i happen to use that sysctl. i havent tested this as unprivileged user though. i think it doesnt matter what the user is, this shouldnt be happening. sincerely, -noone -- you can give a man a fish, or you can teach him to fish.
Re: tmux and rogue window titles in the status line
i think we are not entirely on the same page here. i did not meant the xterm, mrxvt, whatever terminal windows title (or rather, only indirectly), but the titles down in tmux's status line: 0: ksh 1:z!KB$+,*kB4EB4q*uEE"QCaKKEB-ot7B(Fu`E%B D0XD* 2:ksh 3:ksh running this: > echo \\033]2\;$(hostname)\\007 does not "clear" the tmux status line, only the terminal emulator's title attribute. also, when set-title is on, it clears certain part of the title but not all. it's very easy to reproduce this, just cat a binary file in your terminal (yes, that's my hobby ;-) -f -- if you pull the wings off a fly, does it become a walk?
Re: mount ffs as msdos, system hangs
hmm, on Sun, Jul 25, 2010 at 12:02:25PM -0500, Chris Bennett said that > If I plug my 110volt computer into a 220volt socket, it will > promptly die too! > > Why on earth would you even try to do this? actually, it was a typo... nothing dramatic, no fuzzy testing of mount, a simple typo. and i reported it, because for example doing the opposite is impossible: $ sudo mount -t ffs /dev/sd1i /mnt mount_ffs: /dev/sd1i on /mnt: Invalid argument (sd1i is VFAT) now if this is a freak accident, and it should mount an fs it has no understanding of, and then fall over, and this being the normal state, then i sincerely apologize for the noise. i really dont understand whats going on lately on this list. people reporting valid issues are hammered by apologists. i am trying to make this system better as well, you know? -f -- teaching is the art of assisting discovery.
OpenBSD mascotte
Hi list, i'm lookin around to get an OpenBSD Mascotte puppet (i dont know if it's the right word) in Europe, some time ago i see it on OpenBSD website. Someone can help me ??? thanks, Francesco
Re: Multiple ESSIDs on a single wireless adapter?
Damien, Thank you very much for responding. (It would be great if support of virtual ssids is available some day...) Thanks to you and all OpenBSD developers for your great work. Regards, Yassen --- On Fri, 7/23/10, damien.bergam...@free.fr wrote: > > I want to configure multiple > > wireless interfaces, each > > advertised by its own ESSID (nwid according to OpenBSD > > ifconfig), using one and the same wireless adapter. > > (This > > is definitely possible on Linux -- I have a working setup > > and I am trying to reproduce it on OpenBSD 4.7). > > It is not possible on OpenBSD. > We do not support the creation of virtual access points > yet. > > Regards, > Damien
Re: mount ffs as msdos, system hangs
> >> i have just managed to "mount" an ffs partition > >> as msdos. the the system promptly dies. > >> > >> $ sudo fdisk sd0 > >> Disk: sd0 geometry: 120/255/63 [1935360 Sectors] > >> Offset: 0 Signature: 0xAA55 > >> Starting Ending LBA Info: > >> #: id C H S - C H S [ start:size ] > >> --- > >> > >> > >> 0: A6 0 1 1 -119 254 63 [ 63: 1927737 ] > >> OpenBSD 1: 00 0 0 0 - 0 0 0 [ > >> 0: 0 ] unused 2: 00 0 0 0 - 0 0 0 > >> [ 0: 0 ] unused 3: 00 0 0 0 - > >> 0 0 0 [ 0: 0 ] unused > >> $ sudo mount -t msdos -o nodev,nosuid,-x,-l,-m666 /dev/sd0a /mnt > >> $ > >> [dead system] > >> > >> can anybody reproduce this? > >> > > If I plug my 110volt computer into a 220volt socket, it will promptly > > die too! > > > > Why on earth would you even try to do this? > > > > > > That's no excuse. The point here is that any unprivileged user can hang > the system at will. I don't see an unprivleged user. I see root performing the mount, since only root can perform mounts (unless a sysctl is activated, which noone uses). Hey look everyone, it's another uneducated user mouthing off on a noisy mailing list. He goes blah blah blah, loving the sound of his own noise. There's no excuse for what he's saying. If he gave a damn about anything except his own noise he'd go look at the code and find out why this happened.
Re: mount ffs as msdos, system hangs
Chris Bennett escribis: frantisek holop wrote: hi there, i have just managed to "mount" an ffs partition as msdos. the the system promptly dies. $ sudo fdisk sd0 Disk: sd0 geometry: 120/255/63 [1935360 Sectors] Offset: 0 Signature: 0xAA55 Starting Ending LBA Info: #: id C H S - C H S [ start:size ] --- 0: A6 0 1 1 -119 254 63 [ 63: 1927737 ] OpenBSD 1: 00 0 0 0 - 0 0 0 [ 0: 0 ] unused 2: 00 0 0 0 - 0 0 0 [ 0: 0 ] unused 3: 00 0 0 0 - 0 0 0 [ 0: 0 ] unused $ sudo mount -t msdos -o nodev,nosuid,-x,-l,-m666 /dev/sd0a /mnt $ [dead system] can anybody reproduce this? If I plug my 110volt computer into a 220volt socket, it will promptly die too! Why on earth would you even try to do this? That's no excuse. The point here is that any unprivileged user can hang the system at will.
Re: mount ffs as msdos, system hangs
> I haven't tried this mount, but IMHO I don't see any humility.
Re: mount ffs as msdos, system hangs
On Sun, 25 Jul 2010 12:02:25 -0500 Chris Bennett wrote: > frantisek holop wrote: > > i have just managed to "mount" an ffs partition > > as msdos. the the system promptly dies. > If I plug my 110volt computer into a 220volt socket, it will promptly > die too! Well, hopefully it will only blow a fuse. I haven't tried this mount, but IMHO if you mount some garbage as a specific file system type, then the OS should give you an error and deny the mount. It should not crash. Maybe you are mounting through a script, for automated backups, or through the automounter. Now if you insert by accident a wrong medium then this shouldn't lead to a crash. regards, Robert
Re: tmux and rogue window titles in the status line
echo \\033]2\;$(hostname)\\007 On Sun, Jul 25, 2010 at 04:01:12PM +0200, frantisek holop wrote: > hi there, > > i am sure it happens to everyone once in a while > that a rogue program sets the window title in tmux's > status line to something unexpected, like > "1:z!KB$+,*kB4EB4q*uEE"QCaKKEB-ot7B(Fu`E%B D0XD*" > and stays there no matter what... > > as running subsequent programs never changes the title again, > this seems like a bug to me, but apart from that, i think > it would be nice to have a kind of "echo ^[c" for tmux, > a way to reset the window title to it's basic form (current > running program). is there an easy way to do that? > for example re-setting 'set -g status-right "[#S]"' > is not making a change.. > > -f > -- > if people listened to themselves more often, they would shut up.
Re: mount ffs as msdos, system hangs
frantisek holop wrote: hi there, i have just managed to "mount" an ffs partition as msdos. the the system promptly dies. $ sudo fdisk sd0 Disk: sd0 geometry: 120/255/63 [1935360 Sectors] Offset: 0 Signature: 0xAA55 Starting Ending LBA Info: #: id C H S - C H S [ start:size ] --- 0: A6 0 1 1 -119 254 63 [ 63: 1927737 ] OpenBSD 1: 00 0 0 0 - 0 0 0 [ 0: 0 ] unused 2: 00 0 0 0 - 0 0 0 [ 0: 0 ] unused 3: 00 0 0 0 - 0 0 0 [ 0: 0 ] unused $ sudo mount -t msdos -o nodev,nosuid,-x,-l,-m666 /dev/sd0a /mnt $ [dead system] can anybody reproduce this? If I plug my 110volt computer into a 220volt socket, it will promptly die too! Why on earth would you even try to do this?
Re: trouble autobooting loongson on gdium?
> > Does it work after the installation? The installation media is supposed > > I don't think so. > The device is recognized. > ifconfig reports stuff. > I think I even got a DHCP address, but can't ping anything. Hmm... did the particular wireless chip change on recent models? On the gdium here it attaches as: ral0 at pci0 dev 13 function 0 "Ralink RT2561S" rev 0x00: irq 6, address 00:0e:8e:1f:03:3a ral0: MAC/BBP RT2561C, RF RT2527 ...and I can connect to the neighbour's access point with a simple ``dhclient ral0''. > > This is vecause you copied boot, bsd and bsd.rd to the root of the > > Aha. And "boot" varies, per configuration? The one I put there might not be > correct? No, `boot' is the same for all supported loongson systems. But if you copy it to the root of the ext2fs partition, you can't create a directory of the same name. I.e. your partition contains /boot /bsd while the installer and the documentation expect /boot/ /boot/boot /boot/bsd but your layout is fine as long as you update the PMON paths to not have the `boot/' subdirectory in them. Miod
mount ffs as msdos, system hangs
hi there,
i have just managed to "mount" an ffs partition
as msdos. the the system promptly dies.
$ sudo fdisk sd0
Disk: sd0 geometry: 120/255/63 [1935360 Sectors]
Offset: 0 Signature: 0xAA55
Starting Ending LBA Info:
#: id C H S - C H S [ start:size ]
---
0: A6 0 1 1 -119 254 63 [ 63: 1927737 ] OpenBSD
1: 00 0 0 0 - 0 0 0 [ 0: 0 ] unused
2: 00 0 0 0 - 0 0 0 [ 0: 0 ] unused
3: 00 0 0 0 - 0 0 0 [ 0: 0 ] unused
$ sudo mount -t msdos -o nodev,nosuid,-x,-l,-m666 /dev/sd0a /mnt
$
[dead system]
can anybody reproduce this?
OpenBSD 4.7-current (GENERIC) #113: Sat Jul 10 14:50:49 MDT 2010
dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC
cpu0: Intel(R) Celeron(R) M processor 900MHz ("GenuineIntel" 686-class) 631 MHz
cpu0:
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,TM,SBF
real mem = 527527936 (503MB)
avail mem = 508919808 (485MB)
mainbus0 at root
bios0 at mainbus0: AT/286+ BIOS, date 03/11/09, BIOS32 rev. 0 @ 0xf0010, SMBIOS
rev. 2.5 @ 0xf06e0 (37 entries)
bios0: vendor American Megatrends Inc. version "1302" date 03/11/2009
bios0: ASUSTeK Computer INC. 701
acpi0 at bios0: rev 0
acpi0: tables DSDT FACP APIC OEMB MCFG
acpi0: wakeup devices P0P3(S4) P0P4(S4) P0P5(S4) P0P6(S4) P0P7(S4) MC97(S4)
USB1(S3) USB2(S3) USB3(S3) USB4(S3) EUSB(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 70MHz
ioapic0 at mainbus0: apid 1 pa 0xfec0, version 20, 24 pins
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus 5 (P0P3)
acpiprt2 at acpi0: bus 3 (P0P5)
acpiprt3 at acpi0: bus 1 (P0P6)
acpiec0 at acpi0
acpicpu0 at acpi0: C3, C2
acpitz0 at acpi0: critical temperature 90 degC
acpibat0 at acpi0: BAT0 model "701" serial type LION oem "ASUS"
acpiac0 at acpi0: AC unit online
acpiasus0 at acpi0
acpibtn0 at acpi0: LID_
acpibtn1 at acpi0: SLPB
acpibtn2 at acpi0: PWRB
acpivideo0 at acpi0: VGA_
acpivout0 at acpivideo0: CRTD
acpivout1 at acpivideo0: TVOD
acpivout2 at acpivideo0: LCDD
bios0: ROM list: 0xc/0xf800!
pci0 at mainbus0 bus 0: configuration mode 1 (bios)
pchb0 at pci0 dev 0 function 0 "Intel 82915GM Host" rev 0x04
vga1 at pci0 dev 2 function 0 "Intel 82915GM Video" rev 0x04
wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
intagp0 at vga1
agp0 at intagp0: aperture at 0xd000, size 0x1000
inteldrm0 at vga1: apic 1 int 16 (irq 5)
drm0 at inteldrm0
"Intel 82915GM Video" rev 0x04 at pci0 dev 2 function 1 not configured
azalia0 at pci0 dev 27 function 0 "Intel 82801FB HD Audio" rev 0x04: apic 1 int
16 (irq 5)
azalia0: codecs: Realtek ALC662
audio0 at azalia0
ppb0 at pci0 dev 28 function 0 "Intel 82801FB PCIE" rev 0x04: apic 1 int 16
(irq 5)
pci1 at ppb0 bus 4
ppb1 at pci0 dev 28 function 1 "Intel 82801FB PCIE" rev 0x04: apic 1 int 17
(irq 11)
pci2 at ppb1 bus 3
lii0 at pci2 dev 0 function 0 "Attansic Technology L2" rev 0xa0: apic 1 int 17
(irq 11), address 71:ec:da:32:72:24
ukphy0 at lii0 phy 1: Generic IEEE 802.3u media interface, rev. 2: OUI
0x001374, model 0x0002
ppb2 at pci0 dev 28 function 2 "Intel 82801FB PCIE" rev 0x04: apic 1 int 18
(irq 10)
pci3 at ppb2 bus 1
iwn0 at pci3 dev 0 function 0 "Intel Wireless WiFi Link 4965" rev 0x61: apic 1
int 18 (irq 10), MIMO 2T3R, MoW2, address 00:21:5c:04:9e:19
uhci0 at pci0 dev 29 function 0 "Intel 82801FB USB" rev 0x04: apic 1 int 23
(irq 3)
uhci1 at pci0 dev 29 function 1 "Intel 82801FB USB" rev 0x04: apic 1 int 19
(irq 7)
uhci2 at pci0 dev 29 function 2 "Intel 82801FB USB" rev 0x04: apic 1 int 18
(irq 10)
uhci3 at pci0 dev 29 function 3 "Intel 82801FB USB" rev 0x04: apic 1 int 16
(irq 5)
ehci0 at pci0 dev 29 function 7 "Intel 82801FB USB" rev 0x04: apic 1 int 23
(irq 3)
usb0 at ehci0: USB revision 2.0
uhub0 at usb0 "Intel EHCI root hub" rev 2.00/1.00 addr 1
ppb3 at pci0 dev 30 function 0 "Intel 82801BAM Hub-to-PCI" rev 0xd4
pci4 at ppb3 bus 5
ichpcib0 at pci0 dev 31 function 0 "Intel 82801FBM LPC" rev 0x04: PM disabled
pciide0 at pci0 dev 31 function 2 "Intel 82801FBM SATA" rev 0x04: DMA, channel
0 wired to compatibility, channel 1 wired to compatibility
wd0 at pciide0 channel 1 drive 0:
wd0: 1-sector PIO, LBA, 3815MB, 7815024 sectors
wd0(pciide0:1:0): using PIO mode 4, Ultra-DMA mode 4
ichiic0 at pci0 dev 31 function 3 "Intel 82801FB SMBus" rev 0x04: apic 1 int 19
(irq 0)
iic0 at ichiic0
spdmem0 at iic0 addr 0x50: 512MB DDR2 SDRAM non-parity PC2-5300CL5 SO-DIMM
usb1 at uhci0: USB revision 1.0
uhub1 at usb1 "Intel UHCI root hub" rev 1.00/1.00 addr 1
usb2 at uhci1: USB revision 1.0
uhub2 at usb2
New computer.
Hi misc@ My desktop pc is suffering slow death and I'm looking to get a new computer. I was thinking about i7 CPU, SSD drive and second monitor. I have still my trusty Nvidia GeForce 7600 GS that works fine with nv driver. I also need second monitor. And here comes my question. What motherboard chipset would you suggest to pick? Mateusz
Re: OpenBSD users.
Comodoro Rivadavia, Chubut, Argentina On Sat, Jul 17, 2010 at 20:07, Mateusz Gierblinski < mateusz.gierblin...@gmail.com> wrote: > Hi misc@ > > I'm just wondering. Where are you OpenBSD users from? > > I'm from Belgium, anyone else? > > Take care > > -- Hugo Osvaldo Barrera
tmux and rogue window titles in the status line
hi there, i am sure it happens to everyone once in a while that a rogue program sets the window title in tmux's status line to something unexpected, like "1:z!KB$+,*kB4EB4q*uEE"QCaKKEB-ot7B(Fu`E%B D0XD*" and stays there no matter what... as running subsequent programs never changes the title again, this seems like a bug to me, but apart from that, i think it would be nice to have a kind of "echo ^[c" for tmux, a way to reset the window title to it's basic form (current running program). is there an easy way to do that? for example re-setting 'set -g status-right "[#S]"' is not making a change.. -f -- if people listened to themselves more often, they would shut up.
Re: sd0: 128000MB, 512 bytes/sec, 262144000 sec total - is this true? Kingston's Flash drive
On 2010-07-25, Brynet wrote: > Yes, this is a known scam, they modify the max capacity and sell it as a > higher end model.. if you crack it open and attempt to find a datasheet > for the flash chip, you'll probably find it's only between 512M/4G. > > If you buy anything from these shady markets, assume you're going to get > swindled. caveat emptor. if it seems too good to be true, it probably is. same everywhere. it's just as likely to happen with some random online store in a 'western' country. small, high value, easily sold/used... it's hard to think of something that is better than memory sticks / flashcards as an easy target for people dealing in stolen/fake goods.
Re: Battery update frequency
Apparently I am wrong. So ignore me. On Sun, Jul 25, 2010 at 07:56:36AM -0500, Marco Peereboom wrote: > Don't think so. I think this is the same issue ketenis has where the > underlying hardware does not update the battery status and therefore > acpibat reads the cached values. > > Can you try plugging in (or out) the power or adjust the screen > brightness? That kicks the hardware in the face causing an update of > the battery as well. > > > On Sun, Jul 25, 2010 at 01:38:32PM +0200, Peter Hessler wrote: > > There was a fix for this very recently, please update to a snapshot or > > -current. > > > > On 2010 Jul 24 (Sat) at 12:04:56 -0700 (-0700), Luis Useche wrote: > > :HI Guys, > > : > > :I have a Dell Inspiron 1420 laptop where I am using OpenBSD. > > : > > :My problem is that the battery status is not updated frequently enough. It > > :is updated when the machine boots and when less than 10% of the battery is > > :remaining. I was wondering if this is the expected behavior. > > : > > :I check apm and apmd code and the "issue" seems to be comming from the acpi > > :driver itself. I tried to read acpi, but it looks very intimidating to me. > > : > > :Any thoughts? > > : > > :Thanks in advance, > > :Luis. > > : > > > > -- > > I often quote myself; it adds spice to my conversation. > > -- G. B. Shaw
Re: Battery update frequency
Don't think so. I think this is the same issue ketenis has where the underlying hardware does not update the battery status and therefore acpibat reads the cached values. Can you try plugging in (or out) the power or adjust the screen brightness? That kicks the hardware in the face causing an update of the battery as well. On Sun, Jul 25, 2010 at 01:38:32PM +0200, Peter Hessler wrote: > There was a fix for this very recently, please update to a snapshot or > -current. > > On 2010 Jul 24 (Sat) at 12:04:56 -0700 (-0700), Luis Useche wrote: > :HI Guys, > : > :I have a Dell Inspiron 1420 laptop where I am using OpenBSD. > : > :My problem is that the battery status is not updated frequently enough. It > :is updated when the machine boots and when less than 10% of the battery is > :remaining. I was wondering if this is the expected behavior. > : > :I check apm and apmd code and the "issue" seems to be comming from the acpi > :driver itself. I tried to read acpi, but it looks very intimidating to me. > : > :Any thoughts? > : > :Thanks in advance, > :Luis. > : > > -- > I often quote myself; it adds spice to my conversation. > -- G. B. Shaw
Re: sd0: 128000MB, 512 bytes/sec, 262144000 sec total - is this true? Kingston's Flash drive
Yes, this is a known scam, they modify the max capacity and sell it as a higher end model.. if you crack it open and attempt to find a datasheet for the flash chip, you'll probably find it's only between 512M/4G. If you buy anything from these shady markets, assume you're going to get swindled. Sorry. ;-) -Bryan.
sd0: 128000MB, 512 bytes/sec, 262144000 sec total - is this true? Kingston's Flash drive
Hi, My Cousin was sold a Kingston Flash drive in the streets of Delhi. It was told to Him that it was 128 GB. It has a Kingston label with 128GB printed on it. In windows as well as on OpenBSD it shows 128GB. But you cannot fill it with not more than around 1 GB. I guess this is some kind of hoax? Any body came across these kind of drives? thanks --Siju
Re: Battery update frequency
There was a fix for this very recently, please update to a snapshot or -current. On 2010 Jul 24 (Sat) at 12:04:56 -0700 (-0700), Luis Useche wrote: :HI Guys, : :I have a Dell Inspiron 1420 laptop where I am using OpenBSD. : :My problem is that the battery status is not updated frequently enough. It :is updated when the machine boots and when less than 10% of the battery is :remaining. I was wondering if this is the expected behavior. : :I check apm and apmd code and the "issue" seems to be comming from the acpi :driver itself. I tried to read acpi, but it looks very intimidating to me. : :Any thoughts? : :Thanks in advance, :Luis. : -- I often quote myself; it adds spice to my conversation. -- G. B. Shaw
svnserve and SASL
Hi, I'm having trouble to get svnserve + SASL to work under OpenBSD 4.7 stable. When I try to checkout I always get: svn: Authentication error from server: SASL(-13): user not found: no secret in database Here is my config: # cat /var/svn/myrepo/conf/svnserve.conf [general] # anon-access = read # auth-access = write # password-db = passwd # authz-db = authz realm = myrepo [sasl] use-sasl = true # min-encryption = 0 # max-encryption = 256 # cat /usr/local/lib/sasl2/subversion.conf pwcheck_method: auxprop auxprop_plugin: sasldb sasldb_path: /etc/svn-sasldb2 mech_list: ANONYMOUS DIGEST-MD5 This is how I create the user: # saslpasswd2 -c -f /etc/svn-sasldb2 -u myrepo username Some questions which might help me to debug/solve the problem: - can I get SASL to log somewhere on the server (I tried log_level: 7 in subversion.conf without success already)? - what is the correct name for SASL app config file: /usr/local/lib/sasl2/svn.conf or /usr/local/lib/sasl2/subversion.conf or what? - what is the correct sasldb_path in this file: with or without .db extension (saslpasswd2 seems to append .db automatically)? - do I need to add some special flags or something to use saslpasswd2 with DIGEST-MD5 or should I create the svn-sasldb2 in a different way? Any hints are welcome. Thanks in advance, Regards, JC6rg
