/srv/irclogs.ubuntu.com/2024/02/26/#ubuntu-server.txt

kenyonit's bad if you accidentally have multiple default routes and one is provided by DHCP to some router that doesn't actually have Internet access, for example00:11
=== chris14_ is now known as chris14
=== foo_ is now known as foo
=== tomreyn_ is now known as tomreyn
unixtippsehttps://releases.ubuntu.com/jammy/ubuntu-22.04.4-desktop-amd64.iso12:40
unixtippsehttps://old-releases.ubuntu.com/releases/jammy/ubuntu-22.04.3-live-server-arm64.iso12:40
unixtippseIs there any sort of view of the download servers that will provide stable links to ISOs even as they are grandfathered to the "old-releases" URL?12:40
unixtippse(Sorry should have been amd64 in the second link)12:40
=== sdeziel_ is now known as sdeziel
=== mgedmin_ is now known as mgedmin
=== cisme is now known as 040AAD994
ShadowLabsHas anyone been abel to get kerberos working wiht tickets longer than 4 hours when connected to an AD environment, ive set my krb5.conf and gpo for longer tickets but showing a klist with the default principal im only seeing a 4 hour expiration and renewal time19:59
kenyonShadowLabs: I think the domain policy can override your setting20:13
ShadowLabsdomain policy. is that something different than group policy? I've never heard of it or how to change settings of that 20:15
kenyonnot an AD expert, I just know that from configuring Quest VAS (which is how we join machines to AD domains). I googled https://learn.microsoft.com/en-us/windows/security/threat-protection/security-policy-settings/kerberos-policy20:18
ShadowLabsya its the same group policy that ive alreadyh set 20:20
ShadowLabsquest is funny in the manner that they dont use their product in house.20:22
kenyonnot sure if funny or sad21:19
tewardunixtippse: not really, there's different servers holding different data for different reasons, so there's no way to really get one unified download page.22:19
=== JanC is now known as Guest4767
=== JanC_ is now known as JanC
twbHey, I'm trying to remember the name of a thing Ubuntu had 10+ years ago for OEM vendors.  You could do a fully-automated install, and then on first boot it'd ask something like "What's the computer's name?  What's the network config?" and then it'd set those up and then uninstall itself.23:51
twbThe idea being that the hardware vendor could pre-install that and the receiving customer would only get prompted for the bare minimum23:52

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!