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 =
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.
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
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.
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
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
On 2010-07-25, Brynet bry...@gmail.com 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
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*uEEQCaKKEB-ot7B(Fu`E%B D0XD*
and stays there no matter what...
as running subsequent programs never changes the
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
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
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
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
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
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
On Sun, 25 Jul 2010 12:02:25 -0500
Chris Bennett ch...@bennettconstruction.biz 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,
I haven't tried this mount, but IMHO
I don't see any humility.
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
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
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 damien.bergam...@free.fr wrote:
I want to
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
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, gasp! it was a typo... nothing dramatic,
no fuzzy testing of mount, a simple typo.
and
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*uEEQCaKKEB-ot7B(Fu`E%B D0XD* 2:ksh 3:ksh
running this:
echo
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
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
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
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
raven ra...@lilik.it 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
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
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
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
2010/7/25 Christian Weisgerber na...@mips.inka.de:
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
On Sun, Jul 25, 2010 at 4:46 PM, frantisek holop min...@obiit.org 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
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
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
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
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
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
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
raven ra...@lilik.it 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 na...@mips.inka.de wrote:
https://https.openbsd.org/images/pluffy.jpg
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' and...@msu.edu wrote:
On Sun, Jul 25, 2010 at 4:16 PM, bofh goodb...@gmail.com 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
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
On Sun, Jul 25, 2010 at 11:29 AM, Robert info...@die-optimisten.net 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
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
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
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
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
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
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
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
On Sun, Jul 25, 2010 at 8:01 PM, frantisek holop min...@obiit.org 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
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?
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
53 matches
Mail list logo
