Top posting:
So, I do want the five years of LTS in 18.04. {I think - see below.]
A substantial reason I'm not using debian/devuan is LTS support. I'm
glad to be schooled in that regard, if someone has arguments to make. But I
generally want to install a VM/Server/Box for a client and leave it alone as
much as possible for as long as possible, and while it still works as initially
designed. Less drama for me (less income perhaps too) and I can leave it sit,
knowing that security patches are going to get applied and I don't need to
do much, other than to watch that it stays healthy.
So, how do you all handle the Debian, IIRC, two year cycle? Do Debian upgrades
go off pretty smoothly, so you have a 99% chance of moving from, say, jessie to
stretch without any hassles other than mostly "apt-get distro upgrade"
or whatever it is?
Some of that angst gets less potent as more stuff moves to VM's etc. But
even then, it's not a totally trivial concern either.
---
But given what you say about this release just happening to work on 18.04 -
makes me think we should absolutely not rely on any future version functioning
on 18.04. Correct? We might get lucky or not.
And if we don't get lucky, and we need a security patch - well we'll
have to upend our install to go to debian or something...
Does that summarize things reasonably well?
TIA
Louis, et al.
LPHvBvs> Hi Gregory,
>> -----Oorspronkelijk bericht-----
>> Van: samba [mailto:samba-bounces at lists.samba.org] Namens
>> Gregory Sloop via samba
>> Verzonden: maandag 30 juli 2018 17:22
>> Aan: samba at lists.samba.org
>> Onderwerp: [Samba] Louis; re:your repo and Ubuntu 18.04
>> So, Louis - I'm quite interested in using your repo for Samba
>> support on 18.04.
>> You note there's some detail on it on the github site - but I
>> don't seem to find it.
LPHvBvs> Yes, correct, i lots track of that, due to some family matters.
LPHvBvs> But the guide line is in the list.
LPHvBvs> 1) https://lists.samba.org/archive/samba/2018-May/215429.html
LPHvBvs> 2) small fix :
LPHvBvs> https://lists.samba.org/archive/samba/2018-May/215430.html
LPHvBvs> 3) small fix :
LPHvBvs> https://lists.samba.org/archive/samba/2018-May/215436.html
>> Also - while I know it's all just best intentions etc - is
>> this something you intend to do for a while?
LPHvBvs> Yes, but debian wil be the first.
LPHvBvs> If you use the package on Ubuntu, try to keep you server as clean as
possible.
LPHvBvs> The packages work fine, but you install to much, you might get
depend problems
LPHvBvs> due to the packages needed for samba, like tevent ldb tdb etc..
LPHvBvs> I did not back track all other packages with dependecies to
LPHvBvs> the one samba uses for ubuntu.
>> [I'd be glad to toss some $$$ your way to help, if that's
>> helpful. I'd toss some bucks to SerNet - but while the costs
>> aren't massive, they do charge quite a lot for small shops,
>> when you add the Sernet fees over, say, five years - for a
>> few servers.]
LPHvBvs> Always helpfull. I have a paypal address, i'll have to look
LPHvBvs> that up, i dont use that much.
LPHvBvs> Crypto is also ok for me, just tell what and i'll send an
LPHvBvs> adres, the addresses will be on my site once launched.
>> Recap:
>> 1) Is this something you intend to do for a while?
LPHvBvs> Yes.
>> 2) Do you have a link to your Ubuntu FAQ for using your repo?
LPHvBvs> I'll go make that in a few days, probely next week, depends
LPHvBvs> on the about of work im having here.
>> 3) Thanks for all the help you've given me - especially the
>> walk-through for Ubuntu 18.04 a while back. I got a working
>> install on 18.04 a lot quicker as a result. I may give that
>> up for using your current repo on Ubuntu - but we'll see.
>> --
>> To unsubscribe from this list go to the following URL and read the
>> instructions: https://lists.samba.org/mailman/options/samba
LPHvBvs> And thank you for the nice comments.
LPHvBvs> Best regards,
LPHvBvs> Louis
On Tue, 31 Jul 2018 09:48:37 -0700 Gregory Sloop via samba <samba at lists.samba.org> wrote:> Top posting: > > So, I do want the five years of LTS in 18.04. {I think - see below.] > > A substantial reason I'm not using debian/devuan is LTS support.Debian has its own version of LTS: https://wiki.debian.org/LTS>I'm > glad to be schooled in that regard, if someone has arguments to make. > But I generally want to install a VM/Server/Box for a client and > leave it alone as much as possible for as long as possible, and while > it still works as initially designed. Less drama for me (less income > perhaps too) and I can leave it sit, knowing that security patches > are going to get applied and I don't need to do much, other than to > watch that it stays healthy.Also know as 'sit and let it bit-rot' ;-)> > So, how do you all handle the Debian, IIRC, two year cycle? Do Debian > upgrades go off pretty smoothly, so you have a 99% chance of moving > from, say, jessie to stretch without any hassles other than mostly > "apt-get distro upgrade" or whatever it is?Can only speak for myself, but dist-upgrade has always worked for me, okay there might be minor glitches, but never anything major. Having said that, it might be slightly easier to install a new OS and the latest version of Samba, especially if it is a DC.> > Some of that angst gets less potent as more stuff moves to VM's etc. > But even then, it's not a totally trivial concern either.For a DC it is trivial ;-) and not much harder for a Unix domain member.> > --- > But given what you say about this release just happening to work on > 18.04 - makes me think we should absolutely not rely on any future > version functioning on 18.04. Correct? We might get lucky or not.From my understanding, Louis creates the Samba debs for his use and then kindly makes them available for others to use. I think he also has some Ubuntu clients, so the Ubuntu debs should also be available for sometime, but I cannot promise this and I don't think Louis can either. He might find that he no longer has any Ubuntu machines. Nobody can foretell the future, but, from my understanding, Louis plans to provide the debs for the foreseeable future.> > And if we don't get lucky, and we need a security patch - well we'll > have to upend our install to go to debian or something... > > Does that summarize things reasonably well?Yes Rowland
>> A substantial reason I'm not using debian/devuan is LTS support.RPvs> Debian has its own version of LTS: https://wiki.debian.org/LTS Yeah, I've seen that. Not a lot of faith in it though. It sounds a lot like "trust me, someone's going to do it." [I know, cheap, quick, well done - and I want all three. Sigh.] If they'd been doing it the last five years and it worked, then I'd feel better about it.>>I'm >> glad to be schooled in that regard, if someone has arguments to make. >> But I generally want to install a VM/Server/Box for a client and >> leave it alone as much as possible for as long as possible, and while >> it still works as initially designed. Less drama for me (less income >> perhaps too) and I can leave it sit, knowing that security patches >> are going to get applied and I don't need to do much, other than to >> watch that it stays healthy.RPvs> Also know as 'sit and let it bit-rot' ;-) MMMM. Bit-rot! Delicious! [Or does it get *better* with age, like Whiskey?]>> So, how do you all handle the Debian, IIRC, two year cycle? Do Debian >> upgrades go off pretty smoothly, so you have a 99% chance of moving >> from, say, jessie to stretch without any hassles other than mostly >> "apt-get distro upgrade" or whatever it is?RPvs> Can only speak for myself, but dist-upgrade has always worked for me, RPvs> okay there might be minor glitches, but never anything major. RPvs> Having said that, it might be slightly easier to install a new OS and RPvs> the latest version of Samba, especially if it is a DC. RPvs>>> Some of that angst gets less potent as more stuff moves to VM's etc. >> But even then, it's not a totally trivial concern either.RPvs> For a DC it is trivial ;-) and not much harder for a Unix domain member. So, lets assume I've got a samba DC - pure samba, no Win AD boxes at all. Rather than upgrading the in-place DC's you'd might simply spin up a new DC join it to the domain, and then migrate everything [roles] etc? Is there any downside to doing that? [And that does get around version upgrades, and follows how I generally like to do things - spin up new, and never upgrade an in-place setup. That way, if something really goes south, I can simply turn the "old" one back on and try again.]