Re: [OmniOS-discuss] OmniOS CE question: will there be a LTS stable release?

2017-07-26 Thread Tobi Oetiker 


> On 26 Jul 2017, at 22:27, Peter Tribble  wrote:
> [...]
> but I know that with my $DAYJOB hat on the idea of
> dropping security updates for release X as soon as release Y comes out
> is a bit of a non-starter.

our idea is to support X as well as X-1 so there would be half a year overlap.

and I bet that if many people step up with checkbook or spare time and 
abilities in hand for LTS releases, that is certainly doable.

cheers
tobi 

___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

Re: [OmniOS-discuss] Bloody bump to r151023, and more

2017-05-15 Thread Tobi Oetiker 


> On 15 May 2017, at 21:47, Volker A. Brandt  wrote:

> This brings me to the following questions:
> 
> - What is the process of contributing something to either repo in the 
> "post-Dan" era?  Send a pull request to Theo?  Someone else?  Some reviewed 
> semi-automatic process? (I am still not friends with git :-)
> 
> - Who decides what goes into the repo?

As far as github goes they have added some nice voting system recently, so PRs 
can be commented on and Approved or Changes requested.

I think this would work very well for omnios.

cheers
tobi
___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

Re: [OmniOS-discuss] To the OmniOS Community

2017-05-15 Thread Tobi Oetiker 
I will also be glad to help with packaging. 

O+P is already running a repo on pkg.oetiker.ch but we have not widely 
publicized it.

My main use of omnios is as a server for kvm an lxzones, so I would also be 
willing to help with porting updates from joyent unfortunately I have no 
experience with this at
all.

Tobias Oetiker
t...@oetiker.ch
062 775 9902

> On 15 May 2017, at 01:10, Theo Schlossnagle  
> wrote:
> 
> I have to chime in. Communities aren't built on money; they are built on 
> time. I think there has been an unhealthy focus on how much money people are 
> willing to pledge without considering who would even be willing to accept 
> that money for their time. Those willing might not require payment at all. 
> 
> Communities are built on collective need and contributed time. It comes down 
> to volunteering. I have yet to see anyone pledge time to do work, and from my 
> perspective that is what is truly needed here. 
> 
> I was hoping not to be the first, but I will attempt to lead by example. I'll 
> pledge my time to do required security package publications on 014 and 022. 
> As security issues with packages in core arise, I will update the build 
> system, re-roll the packages and publish them.
> 
> If this will be successful, other people will need to commit to do the work 
> and we will democratize the access to make that work possible.
> 
> Best regards, 
> 
> Theo
> 
> 
>> On May 14, 2017 3:41 PM, "Michael Mounteney"  wrote:
>> On Sun, 14 May 2017 17:33:56 +0200
>> Krzysztof Grzempa  wrote:
>> 
>> > So, where are we at the moment? Any conclusions? Decisions? Plans?
>> 
>> TBH it's not looking good.
>> 
>> https://gitter.im/PostOmniOS/Lobby has reached no firm conclusion.  We
>> certainly are well-short of a group of qualified and committed people
>> who could take-on management of OmniOS.
>> 
>> The funding poll at
>> https://docs.google.com/spreadsheets/d/1IyAI950a-JkPgRRLSezZm9-Rt8HkfO_nIkubd_m8d_0/edit
>> is short by an order of magnitude of what it needs to set-up commercial
>> OmniOS support.  Even the promises amount to less than a serious salary.
>> 
>> I hate to be negative but somebody has to say it and we have to decide
>> how to move on.
>> 
>> __
>> Michael Mounteney
>> Landcroft Computing
>> ___
>> OmniOS-discuss mailing list
>> OmniOS-discuss@lists.omniti.com
>> http://lists.omniti.com/mailman/listinfo/omnios-discuss
> ___
> OmniOS-discuss mailing list
> OmniOS-discuss@lists.omniti.com
> http://lists.omniti.com/mailman/listinfo/omnios-discuss
___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

Re: [OmniOS-discuss] Backup script (one local, multiple remote snapshots)

2017-01-21 Thread Tobi Oetiker 
try www.znapzend.org

cheers
tobi

Tobias Oetiker
t...@oetiker.ch
062 775 9902

> On 21 Jan 2017, at 19:00, Richard Elling  
> wrote:
> 
> 
> 
>> On Jan 21, 2017, at 8:07 AM, Dale Ghent  wrote:
>> 
>> We developed Zetaback for this.
> 
> +1 for zetaback. There are perhaps hundreds of implementations of this over 
> the years. I think you'll find that zetaback is one of the best designs.
> 
>  -- richard
> 
>> As for how you exactly want your snapshots to be in number and how long they 
>> should stay around, you might be able to configure a backup policy which 
>> covers that.
>> 
>> https://github.com/omniti-labs/zetaback
>> 
>> The documentation is perdoc within the zetaback script.
>> 
>> /dale
>> 
>>> On Jan 21, 2017, at 8:33 AM, Matej Žerovnik  wrote:
>>> 
>>> Hello,
>>> 
>>> I would like to implement backup for one of my servers with zfs send/recv. 
>>> My scenario would be the following:
>>> 
>>> For each dataset:
>>> - keep one daily snapshot on src server
>>> - copy daily snapshot from src server to backup server
>>> - on backup server, I would like to have one daily, one weekly and one 
>>> monthly snapshots
>>> 
>>> I checked out some ZFS backup scripts I found on GitHub, but non of them 
>>> did that I wanted (znapzend came close, but it keeps too many snapshots for 
>>> my case)
>>> 
>>> Does anyone has anything like that implementented? If yes, would be willing 
>>> to share?
>>> 
>>> Thanks, Matej
>>> ___
>>> OmniOS-discuss mailing list
>>> OmniOS-discuss@lists.omniti.com
>>> http://lists.omniti.com/mailman/listinfo/omnios-discuss
>> 
>> ___
>> OmniOS-discuss mailing list
>> OmniOS-discuss@lists.omniti.com
>> http://lists.omniti.com/mailman/listinfo/omnios-discuss
> ___
> OmniOS-discuss mailing list
> OmniOS-discuss@lists.omniti.com
> http://lists.omniti.com/mailman/listinfo/omnios-discuss

___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

Re: [OmniOS-discuss] LDAP external auth for CIFS service

2016-08-27 Thread Tobi Oetiker 
Gordon

from your explanation it is not quite clear to me if one colud use an openldap 
server, and how one would have to go about telling illumos to use it.

cheers
tobi

> On 26.08.2016, at 18:14, Gordon Ross  wrote:
> 
> Sorry for the delay -- been quite busy.  I do look at this list, but
> only occasionally.
> 
> The way LDAP auth. works in SMB servers like Samba is that the server
> allows SMB clients (i.e. Windows) to logon using accounts that work
> the same as "local" accounts (what Windows would call "local"
> accounts, meaning they are NOT domain accounts).  However, while the
> SMB clients think these are "local" accounts, the server uses
> something akin to the name service switch functions for LDAP to get
> the details of these accounts needed for SMB.
> 
> Such accounts are not really "local", but are defined in your LDAP
> service.  The SMB server needs a way to get some Windows-specific
> details about those accounts from LDAP, including the "NT password
> hash" (for authentication) and some other Windows-ish details.
> 
> The current LDAP libraries in illumos are sufficient for this (though
> for other reasons, it would be nice if we could update them some day).
> What's missing is some "glue" in the name service switch design, and
> perhaps a new lookup method for the "NT password hash", which is
> similar conceptually to the "shadow password" back-end functions.  One
> can probably pretty much copy/paste the LDAP back-end function for
> shadow passwd. to make the "ntpass" or whatever we call this new
> nsswitch method.  The current /var/smb/smbpasswd stuff, currently
> accessed directly from libsmb should really go through the "files"
> back-end, and we might want to consider taking the opportunity to
> change the format of that file (though that means doing some format
> conversion work during upgrades).  Once a new nsswitch method for
> "ntpass" (or whatever) is in place, the parts of this in the SMB
> server (mostly libsmb) are fairly easy.
> 
> Requests for this feature have come up from time to time over the last
> few years, but (so far) not from anyone who wanted it badly enough to
> pay for the work.
> 
> Gordon
> 
> 
>> On Thu, Aug 18, 2016 at 11:15 AM, Dan McDonald  wrote:
>> 
>>> On Aug 18, 2016, at 11:04 AM, Mick Burns  wrote:
>>> 
>>> *bump*
>>> anyone ?
>> 
>> I'm going to forward your note to someone I know who works on CIFS.  He's 
>> not on this list.
>> 
>> Stay tuned,
>> Dan
>> 
>> ___
>> OmniOS-discuss mailing list
>> OmniOS-discuss@lists.omniti.com
>> http://lists.omniti.com/mailman/listinfo/omnios-discuss
> ___
> OmniOS-discuss mailing list
> OmniOS-discuss@lists.omniti.com
> http://lists.omniti.com/mailman/listinfo/omnios-discuss
> 

___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

Re: [OmniOS-discuss] LX for OmniOS update

2016-08-08 Thread Tobi Oetiker 
hi dan

great news ... a question ... for testing this, a vm would be fine, right?

cheers
tobi

Tobias Oetiker
t...@oetiker.ch
062 775 9902

> On 09.08.2016, at 00:21, Dan McDonald  wrote:
> 
> I just pushed two commits to io-lx-public:
> 
> commit f35040a7b2d3acea4f879afbc7ae4d8bfa09b575
> Author: Dan McDonald 
> Date:   Mon Aug 8 17:17:31 2016 -0400
> 
>systemd kool-aid drinkers (e.g. Ubuntu 16) need proc_clock_highres 
> privileges
> 
> commit 179ef6d69f69f2c5fb540fecf8cc3707168fb76f
> Author: Dan McDonald 
> Date:   Thu Aug 4 10:47:33 2016 -0400
> 
>libdladm needs to be a bit more LX-aware
> 
> 
> The most recent has allowed me to boot Ubuntu 16 *AND* CentOS 7.2 on an 
> OmniOS-hosted LX zone.
> 
> I'll be merging with Joyent's stuff again relatively soon and preparing to 
> spin both a non-LX bloody update and an accompanying LX update on our LX 
> publisher:
> 
>http://pkg.omniti.com/omnios/LX/
> 
> I've not heard from anyone, so I'm going to assume nobody has played with LX 
> zones on OmniOS yet.  It's still "alpha/beta"-y IMHO, but I really could use 
> the feedback, especially from people with more Linux experience than me.  (I 
> *rarely* have used UNIX variants outside of MacOS X and Solarish ones for the 
> past 20 years, and most of those exceptions were for IPsec interoperability 
> testing back when I was at Sun.)
> 
> We're contemplating including "LX Beta" in OmniOS r151020, as preparation for 
> r151022 (i.e. the Next LTS release) to include LX zones.  Your feedback 
> should be invaluable in helping us guide things in.
> 
> Thanks,
> Dan
> 
> ___
> OmniOS-discuss mailing list
> OmniOS-discuss@lists.omniti.com
> http://lists.omniti.com/mailman/listinfo/omnios-discuss
> 

___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

Re: [OmniOS-discuss] Crashplan alternatives?

2015-06-03 Thread Tobi Oetiker 
I have not gotten round to trying this, but sinc crashplan is written in java, 
it might still be possible to run it on omnios. at least the old crashplan was 
sucessfully used in unsuported environments.

cheers
tobi

Tobias Oetiker
t...@oetiker.ch
062 775 9902

 On 04.06.2015, at 03:39, Guo-Rong Koh guorong@gmail.com wrote:
 
 To anyone who comes across this post in future.
 
 All my Crashplan backup clients (Linux  Windows) eventually failed
 when the 4.2.0 update rolled through.
 
 I ended going with option 1, creating a Linux KVM instance and
 installing Crashplan there.
 Usefully, Crashplan allows you to adopt a computer and I was able to
 continue backups where they stopped by making the existing Solaris 
 archives visible to the Linux Crashplan KVM.
 
 regards,
 Guo-Rong
 
 
 On Fri, 2015-05-22 at 10:42 +0930, Guo-Rong Koh wrote:
 Hello everyone,
 
 I know others here are running Crashplan for Solaris on OmniOS.
 However, given the (not so recent) retirement announcement:
 https://helpdesk.code42.com/entries/53070937-Solaris-Platform-Retirement-Announcement
 I'm seeking some discussion and advice on possibilities.
 
 My original strategy for supporting Linux and Windows clients in a home 
 server
 environment is starting to disintegrate.
 Due to this issue:
 http://support.code42.com/CrashPlan/Latest/Troubleshooting/Computer-To-Computer_Backups_Between_CrashPlan_App_4.2.0_And_Earlier_Versions_Continuously_Synchronize
 my Linux client is now no longer backing up the way it used to (OmniOS 
 server is on Crashplan 3.7, Linux client automatically upgraded to 4.2.0).
 Thankfully, the Windows clients seem to be OK for now.
 
 Eventually however, I expect the whole solution to fail when Code42 EOL all 
 Solaris support.
 
 My current options are:
 1. Migrate Crashplan to a Linux KVM instance
  - this seems like the least effort for now
 2. Find an alternate, multiplatform solution
  - thus far I have found nothing suitable
 
 Do others here have a migration plan?
 
 regards,
 Guo-Rong
 ___
 OmniOS-discuss mailing list
 OmniOS-discuss@lists.omniti.com
 http://lists.omniti.com/mailman/listinfo/omnios-discuss
___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

Re: [OmniOS-discuss] announcement znapzend a new zfs backup tool

2014-11-27 Thread Tobi Oetiker 
hi stefan

 On 27.11.2014, at 22:51, qutic development mailingli...@qutic.com wrote:
 
 Hi Tobi,
 
 is there a way to specify ssh on another port than 22?
 


I would just setup your .ssh/config file appropriately

cheers
tobi


 Thanks
 Stefan
 
 On 29.07.2014, at 17:50, Tobias Oetiker t...@oetiker.ch wrote:
 
 Just out:
 
 ZnapZend a Multilevel Backuptool for ZFS
 
 It is on Github. Check out
 
 http://www.znapzend.org
 
 cheers
 tobi
 
___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss