Re: OpenBSD-Update Tool

2013-02-10 Thread Jan Stary
On Feb 09 21:11:56, themazed...@gmail.com wrote:
 On 02/09/2013 08:42 PM, System Administrator wrote:
 OpenBSD is all about KISS (simplicity) -- have you tried running the bi-
 annual release update procedure? have you read (carefully) the FAQ
 section on upgrading? Many users report it takes less than 15 minutes
 to perform a *remote* upgrade. Also you need to mind that OpenBSD does
 not support version rollbacks or offer binary updates to stable. So
 will an additional tool which requires ongoing maintenance and a
 configuration file setup, really add value (simplicity) ?
 
 On 9 Feb 2013 at 20:23, Crookedmaze wrote:
 
 Dear OpenBSD Community,
 
 Hello I am wondering if there is a tool similar to FreeBSD-update on
 OpenBSD? If not are there any reasons for why a tool like this
 hasn't been developed? Also if there isn't a tool like this
 (I am pretty sure there isn't one as I have checked) if I were to
 develop one do you think it would be accepted into OpenBSD? Please
 let me know what you think!
 
 Sincerely,
 Crookedmaze
 
 
 Yes, System Administrator I have had a look at the FAQ the reason I am
 asking about such a tool is because it seems as if the only way to
 update OpenBSD (Errata update wise) is to download a patch from
 the errata page and to manually patch the source code then follow the
 instructions for applying the patch (Or you could follow stable using
 CVS). I just thought it would be easier (and Simpler) if you were
 able to patch the version of OpenBSD you are running by simply typing
 openbsd-update which would then apply the security update by download
 and installing a binary package.

Just upgrade with a snapshot, like everyone else.
It doesn't get much simpler than that.



Re: OpenBSD-Update Tool

2013-02-10 Thread James Griffin
-- Jan Stary h...@stare.cz [2013-02-10 09:08:14 +0100]:

 On Feb 09 21:11:56, themazed...@gmail.com wrote:
  On 02/09/2013 08:42 PM, System Administrator wrote:
  OpenBSD is all about KISS (simplicity) -- have you tried running the bi-
  annual release update procedure? have you read (carefully) the FAQ
  section on upgrading? Many users report it takes less than 15 minutes
  to perform a *remote* upgrade. Also you need to mind that OpenBSD does
  not support version rollbacks or offer binary updates to stable. So
  will an additional tool which requires ongoing maintenance and a
  configuration file setup, really add value (simplicity) ?
  
  On 9 Feb 2013 at 20:23, Crookedmaze wrote:
  
  Dear OpenBSD Community,
  
  Hello I am wondering if there is a tool similar to FreeBSD-update on
  OpenBSD? If not are there any reasons for why a tool like this
  hasn't been developed? Also if there isn't a tool like this
  (I am pretty sure there isn't one as I have checked) if I were to
  develop one do you think it would be accepted into OpenBSD? Please
  let me know what you think!
  
  Sincerely,
  Crookedmaze
  
  
  Yes, System Administrator I have had a look at the FAQ the reason I am
  asking about such a tool is because it seems as if the only way to
  update OpenBSD (Errata update wise) is to download a patch from
  the errata page and to manually patch the source code then follow the
  instructions for applying the patch (Or you could follow stable using
  CVS). I just thought it would be easier (and Simpler) if you were
  able to patch the version of OpenBSD you are running by simply typing
  openbsd-update which would then apply the security update by download
  and installing a binary package.
 
 Just upgrade with a snapshot, like everyone else.
 It doesn't get much simpler than that.

This is absolutely true. I'm fairly new to OpenBSD and have been
upgrading using snapshots since November and it takes minutes to
complete and couldn't be easier IMO, even for an idiot like me :-).

I used FreeBSD for many years but will not go back to it now. This
project is superior and whilst I can understand the reasons for
your suggestion, it just isn't needed.

-- 
Primary Key: 4096R/1D31DC38 2011-12-03
Key Fingerprint: A4B9 E875 A18C 6E11 F46D  B788 BEE6 1251 1D31 DC38



Re: reboot after panic: pool_do_put

2013-02-10 Thread Paul Irofti
Can you reproduce this consitently?

It would make it easier to debug for me.



Re: softraid RAID1 + CRYPTO error writing metadata

2013-02-10 Thread Joel Sing
On Sat, 9 Feb 2013, Andy Bradford wrote:
 Thus said Joel Sing on Sat, 09 Feb 2013 16:44:11 +1100:
  umount via DUID  does not work currently - this  will be fixed shortly
  after the next release freeze has ended.

 Will that  also include shutdown  of softraid  via DUID? e.g.,

 bioctl -d DUID

 Or is this not even possible?

This is a separate problem, which is solveable, but a fair amount of work will 
likely be required to do it properly.
-- 

Reason is not automatic. Those who deny it cannot be conquered by it.
 Do not count on them. Leave them alone. -- Ayn Rand



Re: Legal Question: OpenBSD Spin-off

2013-02-10 Thread Crookedmaze

On 02/10/2013 12:02 AM, bofh wrote:

Why not make it a ports/package then?

On Sat, Feb 9, 2013 at 9:25 PM, Crookedmazethemazed...@gmail.com  wrote:
   

On 02/09/2013 06:53 PM, Juan Francisco Cantero Hurtado wrote:
 

On Sat, Feb 09, 2013 at 11:46:58AM -0600, Crookedmaze wrote:

   

Hello Everyone!,

  I am creating an OpenBSD Spin-off and have a question about what the
rules are regarding doing something like this. I have looked at the
OpenBSD copyright page and it looks like doing so would be alright
but I would like to be sure that what I am doing is alright. I
do not necessarily aim to create a new OpenBSD based operating system
what I plan to do is to create my own spin-off off OpenBSD that comes
configured to function as a server for a game called Minecraft,
and comes with things like OpenJDK (required to run Minecraft), but it
will still be OpenBSD it will just have a slightly different default
configuration. Would the people using my spin-off be allowed to use
the OpenBSD package repositories to install packages and update them.
What I am trying to do is setup an OpenBSD spin-off that is setup to be a
secure Minecraft server, because right now many of the people who setup
Minecraft servers in their home run their servers on their personal
computers using Windows 7 or Vista and the server is usually running
as the administrative user. So what I would like to do is distribute
an OpenBSD Spin-off that is configured as a Minecraft server
that these people who are not very skilled can use (It will be highly
scripted and automated) and can run in Virtualbox or can be installed
on a dedicated server, I know this won't be as secure as a managed
server and I also know that security is a process not something you can
download but my goal is to setup something that will hopefully be more
secure than what most people are doing right now I am also doing this
because hopefully if people were to start using my Spin-Off of OpenBSD
then maybe more people will take an interest in OpenBSD.
Please let me know if this would be an OK thing to do. Also
feel free to comment on my idea and let me know what you think!

P.S. This is the first time I have ever posted to the OpenBSD misc
mailing list I have done my best to conform to the OpenBSD Mailing list
Netiquette guidelines, but please let me know if I have
done something incorrectly,

Sincerely,
Crookedmaze

 

The licenses of OpenBSD *base* allow you to distribute appliances but
you should check the licenses of each package included in your project.

Cheers.

Thanks for replying guys! Nicolai thank you for suggesting that I write
a shell script instead I think that is a great idea and I think that is
what I will do instead. Also Christopher now that I think about it I
think the daemon actually runs as a reduced user, I think earlier I was
thinking of the administrative user on Windows as the root user on BSD
in that all programs launched as that user run as admin but now that
I think about it I think in order to run a program as administrator
you need to right click and click run as administrator. Stefan I was
thinking about doing that but now I am leaning towards a shell script
that configures the server how it needs to be configured
(automatic updates chrooted sftp backup cronjobs etc.) I think this way
it will be a lot simpler and easier to transfer between using my OpenBSD
spin-off from release to release. Chris I have ended up deciding to
distribute my spin off as a shell script that you can run post OpenBSD
install so if you can install OpenBSD on a USB drive normally then
you should be able to. Juan thanks for letting me know that I can
redistribute*base*  that will be good to know in the future.
I would like to thank all of your for taking the time
to reply to my question.
   


 



   


That's a great idea Bofh, I'll have to look into that.



Re: OpenBSD-Update Tool

2013-02-10 Thread Crookedmaze

On 02/10/2013 02:40 AM, James Griffin wrote:

--  Jan Staryh...@stare.cz  [2013-02-10 09:08:14 +0100]:

   

On Feb 09 21:11:56, themazed...@gmail.com wrote:
 

On 02/09/2013 08:42 PM, System Administrator wrote:
   

OpenBSD is all about KISS (simplicity) -- have you tried running the bi-
annual release update procedure? have you read (carefully) the FAQ
section on upgrading? Many users report it takes less than 15 minutes
to perform a *remote* upgrade. Also you need to mind that OpenBSD does
not support version rollbacks or offer binary updates to stable. So
will an additional tool which requires ongoing maintenance and a
configuration file setup, really add value (simplicity) ?

On 9 Feb 2013 at 20:23, Crookedmaze wrote:

 

Dear OpenBSD Community,

Hello I am wondering if there is a tool similar to FreeBSD-update on
OpenBSD? If not are there any reasons for why a tool like this
hasn't been developed? Also if there isn't a tool like this
(I am pretty sure there isn't one as I have checked) if I were to
develop one do you think it would be accepted into OpenBSD? Please
let me know what you think!

Sincerely,
Crookedmaze


   

Yes, System Administrator I have had a look at the FAQ the reason I am
asking about such a tool is because it seems as if the only way to
update OpenBSD (Errata update wise) is to download a patch from
the errata page and to manually patch the source code then follow the
instructions for applying the patch (Or you could follow stable using
CVS). I just thought it would be easier (and Simpler) if you were
able to patch the version of OpenBSD you are running by simply typing
openbsd-update which would then apply the security update by download
and installing a binary package.
   

Just upgrade with a snapshot, like everyone else.
It doesn't get much simpler than that.
 

This is absolutely true. I'm fairly new to OpenBSD and have been
upgrading using snapshots since November and it takes minutes to
complete and couldn't be easier IMO, even for an idiot like me :-).

I used FreeBSD for many years but will not go back to it now. This
project is superior and whilst I can understand the reasons for
your suggestion, it just isn't needed.

   

Thanks for replying guys, I have looked into using snapshots but it
looks like the snapshots are based off of current and I had a look at
the FAQ and in section 5.1 of the FAQ it says.

Between formal releases of OpenBSD, /snapshots/ are made available
through the FTP sites http://www.openbsd.org/ftp.html. As the name 
implies, these are builds of whatever
code is in the tree at the instant the builder grabbed a copy of the 
code for that

particular platform. Remember, on some platforms, it may be DAYS before
 the snapshot build is completed and put out for distribution. There is no
promise that the snapshots are completely functional, or even install.

This makes me a little nervous and I think I would rather just follow
release with errata patches or just follow stable. OK, System
Administrator I see what you mean by overhead now, now that I think about
it I am starting to see what you mean by undue burdon (why would you add
something new if what is being used right now works just fine?) I will
have to have a look at marc.info and see what I can find on the topic on
binary updates there also. Nick your right I should stop trying to make
OpenBSD like FreeBSD or Linux, in all honestly I don't really mind the
current update process, really the only actual problem I have had with
it is simply that if you had multiple servers running OpenBSD
(eg if you had 200 servers why would you build the patch on all 200 of
them) but the tool Brian suggested I look at looked promising in that
it looks like you could just apply the patch on a single system build a
package and have all the other servers install the package.
Nick I also agree with you that there is
a certain simple elegance about OpenBSD its actually one of my
favorite things about OpenBSD in that it is secure by default
and the installer for it is great because I can install OpenBSD
in about 3 minutes (as opposed to 20-30+ minutes on others)
not to mention all the time I would normally have to spend
hardening the system post install. With OpenBSD its just a matter
of checking the errata page.

-Crookedmaze



Re: KVM switch - keyboard

2013-02-10 Thread Kent Fritz
Just a data point...one of the boxes I've tried (can't remember which
of Foxconn nt535, nt-i1250, nt-i2847) had a similar/same problem.
About 30%-50% of the time when I switched to it, no kernel messages on
the screen, no keyboard.  I found that plugging in a USB flash drive
caused both the flash drive and the keyboard to be detected -- so that
was my workaround.

I've not seen the problem on other HW using the same cheap KVM.

On Sat, Feb 9, 2013 at 11:58 AM, Bastien Durel bast...@durel.org wrote:
 Quoting Francois Pussault fpussa...@contactoffice.fr:

 Hi, many hardware cannot manage USB keyboards without it present at boot.
 because bios or equiv doesn't enable the port so the OS (whatever it is)
 cannot use it.

 [...]

 a solution could be to have an usb-test device connected to garantee usb
 is enable
 even if kvm is on another device.

 Hello,

 But KVM *is* connected at boot time, as you can see here :

 uhidev1 at uhub4 port 1 configuration 1 interface 1 CHESEN USB Keyboard
 rev 1.10/1.10 addr 3

 It's the diconnection-reconnection which is not managed.

 Regards,

 --
 Bastien
 --
 Bastien



Re: OpenBSD-Update Tool

2013-02-10 Thread MERIGHI Marcus
Hello Crookedmaze, 

you are too verbose for me to reply inline; thus:
- snapshots stability: I use the latest snapshot for a very short time
  on my notebook, then on my production machines (same arch of course).
  Doing this for years and bitten me only twice. Follow current.html,
  though! 
  Bonus: If you run -current it seems to me you get more attention from
  the devs.
- http://www.tedunangst.com/snapper.html
  Tried to use it when it was new, did not work for me, whatever that
  might mean. 

Bye, Marcus

themazed...@gmail.com (Crookedmaze), 2013.02.10 (Sun) 14:33 (CET):
 On 02/10/2013 02:40 AM, James Griffin wrote:
 --  Jan Staryh...@stare.cz  [2013-02-10 09:08:14 +0100]:
 
 On Feb 09 21:11:56, themazed...@gmail.com wrote:
 On 02/09/2013 08:42 PM, System Administrator wrote:
 OpenBSD is all about KISS (simplicity) -- have you tried running the bi-
 annual release update procedure? have you read (carefully) the FAQ
 section on upgrading? Many users report it takes less than 15 minutes
 to perform a *remote* upgrade. Also you need to mind that OpenBSD does
 not support version rollbacks or offer binary updates to stable. So
 will an additional tool which requires ongoing maintenance and a
 configuration file setup, really add value (simplicity) ?
 
 On 9 Feb 2013 at 20:23, Crookedmaze wrote:
 
 Dear OpenBSD Community,
 
 Hello I am wondering if there is a tool similar to FreeBSD-update on
 OpenBSD? If not are there any reasons for why a tool like this
 hasn't been developed? Also if there isn't a tool like this
 (I am pretty sure there isn't one as I have checked) if I were to
 develop one do you think it would be accepted into OpenBSD? Please
 let me know what you think!
 
 Sincerely,
 Crookedmaze
 
 
 Yes, System Administrator I have had a look at the FAQ the reason I am
 asking about such a tool is because it seems as if the only way to
 update OpenBSD (Errata update wise) is to download a patch from
 the errata page and to manually patch the source code then follow the
 instructions for applying the patch (Or you could follow stable using
 CVS). I just thought it would be easier (and Simpler) if you were
 able to patch the version of OpenBSD you are running by simply typing
 openbsd-update which would then apply the security update by download
 and installing a binary package.
 Just upgrade with a snapshot, like everyone else.
 It doesn't get much simpler than that.
 This is absolutely true. I'm fairly new to OpenBSD and have been
 upgrading using snapshots since November and it takes minutes to
 complete and couldn't be easier IMO, even for an idiot like me :-).
 
 I used FreeBSD for many years but will not go back to it now. This
 project is superior and whilst I can understand the reasons for
 your suggestion, it just isn't needed.
 
 Thanks for replying guys, I have looked into using snapshots but it
 looks like the snapshots are based off of current and I had a look at
 the FAQ and in section 5.1 of the FAQ it says.
 
 Between formal releases of OpenBSD, /snapshots/ are made available
 through the FTP sites http://www.openbsd.org/ftp.html. As the name
 implies, these are builds of whatever
 code is in the tree at the instant the builder grabbed a copy of the
 code for that
 particular platform. Remember, on some platforms, it may be DAYS before
  the snapshot build is completed and put out for distribution. There is no
 promise that the snapshots are completely functional, or even install.
 
 This makes me a little nervous and I think I would rather just follow
 release with errata patches or just follow stable. OK, System
 Administrator I see what you mean by overhead now, now that I think about
 it I am starting to see what you mean by undue burdon (why would you add
 something new if what is being used right now works just fine?) I will
 have to have a look at marc.info and see what I can find on the topic on
 binary updates there also. Nick your right I should stop trying to make
 OpenBSD like FreeBSD or Linux, in all honestly I don't really mind the
 current update process, really the only actual problem I have had with
 it is simply that if you had multiple servers running OpenBSD
 (eg if you had 200 servers why would you build the patch on all 200 of
 them) but the tool Brian suggested I look at looked promising in that
 it looks like you could just apply the patch on a single system build a
 package and have all the other servers install the package.
 Nick I also agree with you that there is
 a certain simple elegance about OpenBSD its actually one of my
 favorite things about OpenBSD in that it is secure by default
 and the installer for it is great because I can install OpenBSD
 in about 3 minutes (as opposed to 20-30+ minutes on others)
 not to mention all the time I would normally have to spend
 hardening the system post install. With OpenBSD its just a matter
 of checking the errata page.
 
 -Crookedmaze
 
 
 !DSPAM:5117a209295471622935288!



Re: OpenBSD-Update Tool

2013-02-10 Thread Nick Holland
On 02/10/13 08:33, Crookedmaze wrote:
...
 Thanks for replying guys, I have looked into using snapshots but it
 looks like the snapshots are based off of current and I had a look at
 the FAQ and in section 5.1 of the FAQ it says.
 
 Between formal releases of OpenBSD, /snapshots/ are made available
 through the FTP sites http://www.openbsd.org/ftp.html. As the name 
 implies, these are builds of whatever
 code is in the tree at the instant the builder grabbed a copy of the 
 code for that
 particular platform. Remember, on some platforms, it may be DAYS before
   the snapshot build is completed and put out for distribution. There is no
 promise that the snapshots are completely functional, or even install.
 
 This makes me a little nervous and I think I would rather just follow
 release with errata patches or just follow stable. 

One thing that is different between OpenBSD and most other open source
projects (and probably most closed source projects) is that we work hard
to keep the source tree ALWAYS functional -- if something goes into the
tree and is attached to the build, it either works, or beatings will be
applied.  If you install a snapshot and it doesn't work, someone screwed
up, it's your job at that time to scream loudly and make sure people
know, so the offending code is fixed or backed out, and measures will be
taken to deter the offender from doing it again.  (You don't want to
know, it isn't pretty.)

Unfortunately, our practice is rare enough that most people have a
(justified) fear of living at HEAD of the source tree, and even an
expectation that it is completely broken.  Things are different here in
OpenBSD.

But really, it's an extraordinary event for snapshots to be broken, and
it is important that people test them.

(That particular part of the FAQ has been updated repeatedly to try to
get the tone Just Right, and probably responsible for more..uh..
heated e-mails from Theo to me than anything else.  And, I it looks
like I missed this particular section last time I updated the paragraphs
very shortly before it.  Improvements are taking place now, see if I can
get it in before Theo lights his flame thrower...)

 OK, System
 Administrator I see what you mean by overhead now, now that I think about
 it I am starting to see what you mean by undue burdon (why would you add
 something new if what is being used right now works just fine?) I will
 have to have a look at marc.info and see what I can find on the topic on
 binary updates there also. Nick your right I should stop trying to make
 OpenBSD like FreeBSD or Linux, in all honestly I don't really mind the
 current update process, really the only actual problem I have had with
 it is simply that if you had multiple servers running OpenBSD
 (eg if you had 200 servers why would you build the patch on all 200 of
 them)

yes, don't.  Build on one, fast, otherwise mostly idle machine.  Build a
release.  Install to your 200 other machines.  Done.

 but the tool Brian suggested I look at looked promising in that
 it looks like you could just apply the patch on a single system build a
 package and have all the other servers install the package.
 Nick I also agree with you that there is
 a certain simple elegance about OpenBSD its actually one of my
 favorite things about OpenBSD in that it is secure by default
 and the installer for it is great because I can install OpenBSD
 in about 3 minutes (as opposed to 20-30+ minutes on others)
 not to mention all the time I would normally have to spend
 hardening the system post install. With OpenBSD its just a matter
 of checking the errata page.

I think 'e's got it. :)

Nick.



split-logfile

2013-02-10 Thread Mike.
I've been watching as OpenBSD seems to be moving towards the nginx
webserver, and I've made the switch from apache to nginx for all the
web servers I run.  One thing that was missing from the nginx installs
was the perl script that is used in apache-land to split a single
server access file into separate files for each virtual host -
split-logfile.

So I wrote a c language program with the functionality of
split-logfile, available here:
http://archive.mgm51.com/sources/split-logfile.html



Re: softraid RAID1 + CRYPTO error writing metadata -- WHEW

2013-02-10 Thread Alexander Hall

On 02/10/13 08:13, Scott McEachern wrote:


I could have sworn the man page for fsck(8) said something about rule #1
being don't panic, but I couldn't find it in there.  Must be somewhere
else.  So I didn't panic, watched a bit of TV and thought about it...


I'm pretty sure you're thinking about scan_ffs(8), which however 
suggests the following:


 1. Panic.  You usually do so anyways, so you might as well get it over
with.  Just don't do anything stupid.  Panic away from your
machine.  Then relax, and see if the steps below won't help you
out.
 2. ...

:-)

/Alexander



Re: KVM switch - keyboard

2013-02-10 Thread Bastien Durel

Quoting Kent Fritz fritz.k...@gmail.com:

Just a data point...one of the boxes I've tried (can't remember which
of Foxconn nt535, nt-i1250, nt-i2847) had a similar/same problem.
About 30%-50% of the time when I switched to it, no kernel messages on
the screen, no keyboard.  I found that plugging in a USB flash drive
caused both the flash drive and the keyboard to be detected -- so that
was my workaround.


Hello,

This workaround works here too. Thanks to Francois Pussault to suggest  
this first, although I did not understand first ;)



--
Bastien



Re: apue : for openbsd : which edition?

2013-02-10 Thread Juan Francisco Cantero Hurtado
On Sun, Feb 10, 2013 at 01:00:50AM -0500, Mayuresh Kathe wrote:
 hello, may i know which would be the most suitable
 edition of 'apue' (1st or 2nd) to learn more about
 programming services under openbsd?
 thanks.

http://article.gmane.org/gmane.os.openbsd.misc/197135

Cheers.

-- 
Juan Francisco Cantero Hurtado http://juanfra.info



Re: softraid RAID1 + CRYPTO error writing metadata -- WHEW

2013-02-10 Thread Scott McEachern

On 02/10/13 14:17, Alexander Hall wrote:

On 02/10/13 08:13, Scott McEachern wrote:


I could have sworn the man page for fsck(8) said something about rule #1
being don't panic, but I couldn't find it in there.  Must be somewhere
else.  So I didn't panic, watched a bit of TV and thought about it...


I'm pretty sure you're thinking about scan_ffs(8), which however 
suggests the following:


 1. Panic.  You usually do so anyways, so you might as well get it over
with.  Just don't do anything stupid.  Panic away from your
machine.  Then relax, and see if the steps below won't help you
out.
 2. ...

:-)

/Alexander



Ah yes, thanks for the reminder.

--
Scott McEachern

https://www.blackstaff.ca



Re: reboot after panic: pool_do_put

2013-02-10 Thread frantisek holop
hmm, on Sun, Feb 10, 2013 at 12:04:37PM +0200, Paul Irofti said that
 Can you reproduce this consitently?

i wouldn't say consistently but oftenish.
it just happened again right after i started
up opera again.  but sometimes opera would
keep working long long time before panicing.

no other opera users seeing this?

i can run some more gdb commands on the crash
image if it helps and/or try patches.

-f
-- 
the cow is a machine which makes grass fit for us people.



Re: Legal Question: OpenBSD Spin-off

2013-02-10 Thread Maximo Pech
Well, installing openbsd is not what I'd call easy for people with few
technical skills.

Why not make it a live system that boots from cd/dvd/USB/sd with everything
already configured and ready to run?

El sábado, 9 de febrero de 2013, Crookedmaze escribió:

 On 02/09/2013 06:53 PM, Juan Francisco Cantero Hurtado wrote:

 On Sat, Feb 09, 2013 at 11:46:58AM -0600, Crookedmaze wrote:


 Hello Everyone!,

  I am creating an OpenBSD Spin-off and have a question about what the
 rules are regarding doing something like this. I have looked at the
 OpenBSD copyright page and it looks like doing so would be alright
 but I would like to be sure that what I am doing is alright. I
 do not necessarily aim to create a new OpenBSD based operating system
 what I plan to do is to create my own spin-off off OpenBSD that comes
 configured to function as a server for a game called Minecraft,
 and comes with things like OpenJDK (required to run Minecraft), but it
 will still be OpenBSD it will just have a slightly different default
 configuration. Would the people using my spin-off be allowed to use
 the OpenBSD package repositories to install packages and update them.
 What I am trying to do is setup an OpenBSD spin-off that is setup to be a
 secure Minecraft server, because right now many of the people who setup
 Minecraft servers in their home run their servers on their personal
 computers using Windows 7 or Vista and the server is usually running
 as the administrative user. So what I would like to do is distribute
 an OpenBSD Spin-off that is configured as a Minecraft server
 that these people who are not very skilled can use (It will be highly
 scripted and automated) and can run in Virtualbox or can be installed
 on a dedicated server, I know this won't be as secure as a managed
 server and I also know that security is a process not something you can
 download but my goal is to setup something that will hopefully be more
 secure than what most people are doing right now I am also doing this
 because hopefully if people were to start using my Spin-Off of OpenBSD
 then maybe more people will take an interest in OpenBSD.
 Please let me know if this would be an OK thing to do. Also
 feel free to comment on my idea and let me know what you think!

 P.S. This is the first time I have ever posted to the OpenBSD misc
 mailing list I have done my best to conform to the OpenBSD Mailing list
 Netiquette guidelines, but please let me know if I have
 done something incorrectly,

 Sincerely,
 Crookedmaze


 The licenses of OpenBSD *base* allow you to distribute appliances but
 you should check the licenses of each package included in your project.

 Cheers.

 Thanks for replying guys! Nicolai thank you for suggesting that I write
 a shell script instead I think that is a great idea and I think that is
 what I will do instead. Also Christopher now that I think about it I
 think the daemon actually runs as a reduced user, I think earlier I was
 thinking of the administrative user on Windows as the root user on BSD
 in that all programs launched as that user run as admin but now that
 I think about it I think in order to run a program as administrator
 you need to right click and click run as administrator. Stefan I was
 thinking about doing that but now I am leaning towards a shell script
 that configures the server how it needs to be configured
 (automatic updates chrooted sftp backup cronjobs etc.) I think this way
 it will be a lot simpler and easier to transfer between using my OpenBSD
 spin-off from release to release. Chris I have ended up deciding to
 distribute my spin off as a shell script that you can run post OpenBSD
 install so if you can install OpenBSD on a USB drive normally then
 you should be able to. Juan thanks for letting me know that I can
 redistribute*base*  that will be good to know in the future.
 I would like to thank all of your for taking the time
 to reply to my question.



Re: Legal Question: OpenBSD Spin-off

2013-02-10 Thread Rod Whitworth
On Sun, 10 Feb 2013 18:09:56 -0600, Maximo Pech wrote:

Well, installing openbsd is not what I'd call easy for people with few
technical skills.

Crap! It is well documented and very little data needs to be typed in
as most input can be done by accepting the default.


Why not make it a live system that boots from cd/dvd/USB/sd with everything
already configured and ready to run?

Live  CDs can be a PITA.. People have built them and they aon't setting
the world on fire.
You can make your own USB flash by following the instructions in the
FAQ (= same as install to the HD, just different HDD name.

Installing in under 5 minutes is possible on a real drive - USB sticks
are much slower.
If I am doing a quick test I sometimes install to a real HDD on USB.

Meanwhile go read the FAQ about installing and try it. Unless you are
an absolute dummy you should be able to absorb the instructions and do
the install.

If you can't handle that, then OpenBSD is probably not for you and,
given some of the horrors in some Linux Live-CDs, you may be best to
stick to windows or mac.

*** NOTE *** Please DO NOT CC me. I am subscribed to the list.
Mail to the sender address that does not originate at the list server is 
tarpitted. The reply-to: address is provided for those who feel compelled to 
reply off list. Thankyou.

Rod/
---
This life is not the real thing.
It is not even in Beta.
If it was, then OpenBSD would already have a man page for it.



Re: OpenBSD-Update Tool

2013-02-10 Thread Ed Ahlsen-Girard
 But really, it's an extraordinary event for snapshots to be broken,
 and it is important that people test them.
 

I have been running snapshots for years. I don't recall anything broken
in base that I even noticed. There were some problems with ports, but
they were fixed about as rapidly as upstream developments permitted.

If I were running a high visibility production server I might run
stable, but that'd just be to minimize changes and downtime.

-- 

Edward Ahlsen-Girard
Ft Walton Beach, FL