On Thu, 28 Dec 2017 01:57:31 +0300, "jin" wrote:
> My company wrote an authentication software and dev. teams decided to close
> code to others. A customer requested to see codes under one certain
> condition. They demand to see our codes if our company fall into problems
> that cause to lose the
Hi
A weird request has arrived us from one of the our customers and it is
really unusual. Since I'm not a developer and i could not find any clue, i
guess that i need some guidance. Any help will be appreciated.
Here is the story
My company wrote an authentication software and dev. teams decided
On Dec 27, 2017 8:07 PM, Jordan Geoghegan wrote:
>
> Did you:
>
> # newfs /dev/rsd(whichever is correct)
>
> before reboot?
>
> That doesn't make sense. What would I be making a new filesystem for -- or
> on, for that matter. Disk formatting is taken care of by the
Did you:
# newfs /dev/rsd(whichever is correct)
before reboot?
That doesn't make sense. What would I be making a new filesystem for -- or on,
for that matter. Disk formatting is taken care of by the installer script.
Did you:
cp your kernels to the new sd's
Again, this doesn't make sense.
On Wed, Dec 27, 2017 at 03:01:12PM -0800, Jordan Geoghegan wrote:
> sparc* is not an fdisk / MBR platform
I don't have one :(
more inline
>
>
>
> On 12/27/17 14:56, Edgar Pettijohn wrote:
> > On Wed, Dec 27, 2017 at 02:29:09PM -0800, Jordan Geoghegan wrote:
> > > I tried installing again and
> If you wanted your personal git mirrors of OpenBSD, then you can do it
> with:
>
> https://github.com/hakrtech/repogen/repogen.sh
>
https://github.com/hakrtech/repogen/
Wrong URL in previous post. Sorry.
Hi,
If you wanted your personal git mirrors of OpenBSD, then you can do it with:
https://github.com/hakrtech/repogen/repogen.sh
This will generate git repos of OpenBSD's source, xenocara, ports and www.
You can then push src to your git repo hosting box. My test repo from that
script is:
sparc* is not an fdisk / MBR platform
On 12/27/17 14:56, Edgar Pettijohn wrote:
On Wed, Dec 27, 2017 at 02:29:09PM -0800, Jordan Geoghegan wrote:
I tried installing again and followed your instructions to a T and the
installer hung after typing reboot at the prompt upon finishing install.
I
On Wed, Dec 27, 2017 at 02:29:09PM -0800, Jordan Geoghegan wrote:
> I tried installing again and followed your instructions to a T and the
> installer hung after typing reboot at the prompt upon finishing install.
>
> I let it sit for 10-15 minutes after entering reboot command but then
>
I tried installing again and followed your instructions to a T and the
installer hung after typing reboot at the prompt upon finishing install.
I let it sit for 10-15 minutes after entering reboot command but then
determined it had likely frozen considering it said the disks had been
synced
On 27 Dec 2017, at 21:30, Theo de Raadt wrote:
>> By entering as su/doas sysctl kern.bufcachepercent=80 shows me the
>> change from default=20 to 80 as expected, but after a reboot the value
>> is set again/still to 20 (%).
>
> sysctl changes the running state. It does not change that file
> for
> By entering as su/doas sysctl kern.bufcachepercent=80 shows me the
> change from default=20 to 80 as expected, but after a reboot the value
> is set again/still to 20 (%).
sysctl changes the running state. It does not change that file
for future boots.
Thanks for the clarification Stefan. Did you have to manually run
installboot(8) or is the bootloader stuff taken care of automatically by
the install script?
On 12/27/17 04:52, Stefan Sperling wrote:
On Tue, Dec 26, 2017 at 12:56:53PM -0800, Jordan wrote:
The install procedure I followed
Hi
I installed 6.2-release/syspatched on new PC with a NVMe disk, via USB
Stick made from miniroot62.fs. It works fine, but something is different
from other 6.2 installs on other PC/server I've installed:
By entering as su/doas sysctl kern.bufcachepercent=80 shows me the
change from
Am Wed, 27 Dec 2017 08:29:37 -0800
schrieb Kai Wetlesen :
> Hi devs,
> I just wanted to say thank you for your hard work in developing
> syspatch. It has made my work as an OpenBSD admin a hell of a lot
> easier! That is all. Be merry, or something similar.
> ~Kai
>
+++ for
On Thu, December 21, 2017 1:14 pm, x9p wrote:
>
...
>
second batch sent by mail to the ones who sent me address/PO Box. still lots of
stickers.
cheers.
--
x9p | PGP : 0x03B50AF5EA4C8D80 / 5135 92C1 AD36 5293 2BDF DDCC 0DFA 74AE 1524
E7EE
Hi devs,
I just wanted to say thank you for your hard work in developing syspatch. It
has made my work as an OpenBSD admin a hell of a lot easier! That is all.
Be merry, or something similar.
~Kai
Special bonus from Arkynaias.net now:
Search the ultranet! Will a Luvbot of ours answer your pleasure callings?
Merry Xmas and have a happy new year!
Üven Cærlyen
Arkynaias.net
The only thing that is clear here is that you're wasting our time.
Em quarta-feira, 27 de dezembro de 2017 11:20:14 BRST, Üven Cærlyen
escreveu:
Den 12/27/2017 06:16, skrev Ian Sutton:
> please do not use this list to test markov bots, it is for
> miscellaneous
Den 12/27/2017 15:45, skrev Mike Burns:
On 2017-12-27 14.24.57 +0100, Üven Cærlyen wrote:
Den 12/27/2017 05:10, skrev Mike Burns:
Why are you sending this to misc@openbsd?
So basically when I say I am from Arkynaias, you are from Turdiona?
I don't understand.
I really really don´t think
Den 12/27/2017 05:10, skrev Mike Burns:
Why are you sending this to misc@openbsd?
So basically when I say I am from Arkynaias, you are from Turdiona?
Den 12/27/2017 06:16, skrev Ian Sutton:
please do not use this list to test markov bots, it is for
miscellaneous openbsd discussion, thanks
The two last reponses again, horribly poor coherence. How do you tell
people with such lacking wits to not reply?
Even more for a reason, for the
On Tue, Dec 26, 2017 at 12:56:53PM -0800, Jordan wrote:
> The install procedure I followed on the T4 was:
>
> 1) Boot install kernel and drop to shell and provision RAID partitions on
> both disks using the letter “a” via disklabel(8)
>
> 2) Assemble RAID volume with # bioctl -c 1 -l
23 matches
Mail list logo