On Tue, 5 Dec 2023 at 21:33, Geert Stappers wrote:
What / which debian archive is being used?
>
> (I'm suspecting an outdated debian archive mirror )
>
I used just that very URL
http://ftp.debian.org/debian/dists/bookworm/main/installer-amd64/current/images/netboot/
But when I browse
the above site and upper
directories I don't see any newer mini ISO images.
Any ideas...?
tnx!
Dick Visser
Hii
On https://wiki.debian.org/Cloud/AmazonEC2Image/Bookworm it says
This preview AMIs are intended to allow you to start testing Debian 12
deployments and migrations before the official release occurs on 2023-06-10.
While the changelog at the bottom mentions
-
*2023-06-12* - Official
"works for me"
vagrant@bullseye:~$ uname -a
Linux bullseye 5.10.0-22-amd64 #1 SMP Debian 5.10.178-3 (2023-04-22) x86_64
GNU/Linux
dick.visser@GA0267 mainstream_distros$ vagrant -v
Vagrant 2.3.4
This is on an intel mac with virtualbox Version 7.0.8 r156879 (Qt5.15.2)
On Thu, 11 May 2023 at
of delay.
If it is of interest to anyone, this was done by combining
"gather_facts=no" with "wait_for_connection" and "setup".
thx!
--
Dick Visser
Trust & Identity Service Operations Manager
GÉANT
39
end=16777183 new: size=41680863 end=41943007
[3.184491] EXT4-fs (nvme0n1p1): mounted filesystem with ordered
data mode. Opts: (null)
done.
Begin: Running /scripts/init-bottom ... done.
[3.210828] Not activating Mandatory Access Control as
/sbin/tomoyo-init does not exist.
[3.36811
2021 16:13:50
+. Up 42.21 seconds.
I guess this is not a problem with the Debian image, and I can
probably configure our deployment to cope with this delay, but I'm
curious as to why this happens.
FYI this is an eu-central-1 (frankfurt).
thx
--
Dick Visser
Trust & Identity Service Operat
On Thu, 23 Sept 2021 at 12:38, Michael Kesper wrote:
>
> Hi Dick,
>
> Am 23.09.21 um 11:52 schrieb Dick Visser:
> > To answer my own question: yes this is possible, by using a cloud-init
> > style user data blob:
> >
> >
> > #cloud-init
> >
they happen.
Is there a way to override this behavior? Perhaps by having some
flags/code in the user_data?
many thanks
--
Dick Visser
Trust & Identity Service Operations Manager
GÉANT
To answer my own question: yes this is possible, by using a cloud-init
style user data blob:
#cloud-init
package_update: false
package_upgrade: false
package_reboot_if_required: false
On Thu, 23 Sept 2021 at 11:17, Dick Visser wrote:
>
> Hi
>
> I noticed that newly created bullse
all security updates including any
dependencies that are not in Debian-Security?
If this is the wrong forum, apologies, and what would be a more
suitable place to ask.
thx!
--
Dick Visser
Trust & Identity Service Operations Manager
GÉANT
0:18:23.000Z"
}
Because the glob pattern for the Name matches both, and the backport
one was released 10 minutes later, this was picked....
I have now updated the glob to "debian-10-amd64-*" so that we pick the
non-backported AMI again.
--
Dick Visser
Trust & Identity Service Operations Manager
GÉANT
The thing I was after is how to have 127.0.0.1 as the resolver.
Turns out I just had to uncomment this line in /etc/dhcp/dhclient.conf:
prepend domain-name-servers 127.0.0.1;
thx!
On Fri, 6 Dec 2019 at 20:31, Noah Meyerhans wrote:
>
> On Fri, Dec 06, 2019 at 04:42:18PM +0100, Dick
Hi
I'm struggling to add custom nameservers to /etc/resolv.conf.
The file gets overwritten on reboot, but I can't find out where this is done.
Any ideas?
thx
--
Dick Visser
Trust & Identity Service Operations Manager
GÉANT
I think consistent device names were mainly meant for laptops etc where a
range of different interfaces popping in and out is a common use case.
Servers are more or less the opposite.
Btw my NAT script now works great across stretch and buster, and also
Ubuntu xenial/bionic work.
Thx
On Sat, 19
On Fri, 18 Oct 2019 at 02:24, Ross Vandegrift wrote:
>
> On Fri, Oct 18, 2019 at 01:04:56AM +0200, Dick Visser wrote:
> > On Fri, 18 Oct 2019 at 00:53, Noah Meyerhans wrote:
> > > Can you explain why this causes problems for you? We want to keep device
> > > re
sabled.
I'm using one of the AWS shell scripts (configure-pat.sh, which has
eth0 hardcoded) to do PAT for private instances, and this can be used
with many distros, but now not with Debian Buster.
--
Dick Visser
Trust & Identity Service Operations Manager
GÉANT
n additional reboot and makes deployment harder than it
should be (or, than it is with Stretch).
Could this perhaps be added to the next build?
Many thanks
--
Dick Visser
Trust & Identity Service Operations Manager
GÉANT
18 matches
Mail list logo
