Re: How to create a Fedora 37 image for AWS
> Am 25.02.2023 um 00:23 schrieb Thomas Cameron via users > : > > Hey, all! I work for AWS, and I put together a quick HOWTO on setting up a > Fedora 37 instance using KVM, and then converting it to a format that can be > used to create a new EC2 instance on AWS. Note that this is a personal > project, is not endorsed by AWS, and was not produced by AWS. It’s just me. > > https://camerontech.com/fedora-aws/ > > I am not a web guy, I just did a super basic HTML page using Seahorse. It’s > literally something I threw together, and I am sure I missed some things, but > I hope that it is helpful for anyone who wants to build their own image. I > know there are a bunch of images already out there in the community, but I > wanted to document how to do it for yourself. > > I hope you find it helpful! The first questions that comes into my mind: why not use cloud image for Amazon? It’s not Fedora Server, but something alike. But that is your kickstart as well. Or use the generic cloud image, which includes cloud-init, and adjust that? And just in case you whish to provide a (real) Fedora Server, why don’t you use the provided KVM image and add some specifics apps using e.g. guestfish on the image (as described in the Fedora Server documentation)? Or use the kickstart from Fedora repository and add some specific apps to it? I’m just curious, no criticism. I created the KVM image and know about the difficulties and peculiarities using kickstart and imagefactory. Peter -- Peter Boy https://fedoraproject.org/wiki/User:Pboy p...@fedoraproject.org Timezone: CET (UTC+1) / CEST (UTC+2) Fedora Server Edition Working Group member Fedora docs team contributor Java developer and enthusiast ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: CentOS8 VM
On Sat, Feb 25, 2023 at 1:48 AM Peter Boy wrote: > > > Am 25.02.2023 um 05:33 schrieb Robert McBroom via users > > : > > > > Installed CentOS8 on a VM from > > > > CentOS-8.1.1911-x86_64-dvd1.iso > > > > Trying to update it gives > > > > Failed to download metadata for repo 'appstream' > > Error: Failed to download metadata for repo 'appstream' > > > > I have the rpm's on a local repository but disabling the repos has no > > effect on the error and will no proceed with the update. > > > > is there a fix? > > CentOS 8 is EOL since end of last year. My fix was: replacing CentOS with > Fedora Server, although my perspective may not be that unencumbered, given my > signature. Unless you are using very special application software or a very > special use case you will not face more issues as with CentOS, in some cases > rather even less, because the software versions are more recent. ++ I find Fedora Server is far superior to CentOS. With Fedora Server you get modern software without the need to take special actions like on CentOS. There's no putzing around with ancient software or Software Collections (SCL). When I look back at all the time I wasted over the years on CentOS trying to run a LAMP stack with Mediawiki... So much wasted time and energy... One thing to keep in mind is, you need to run dnf-system-upgrade every 6 months or so to keep up with Fedora's cadence. https://docs.fedoraproject.org/en-US/quick-docs/dnf-system-upgrade/ Jeff ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: CentOS8 VM
On 2/24/23 9:18 PM, Tim via users wrote: On Fri, 2023-02-24 at 23:33 -0500, Robert McBroom via users wrote: Installed CentOS8 on a VM from CentOS-8.1.1911-x86_64-dvd1.iso Trying to update it gives Failed to download metadata for repo 'appstream' Error: Failed to download metadata for repo 'appstream' You're really posting on the wrong list for CentOS, but CentOS 8 went end-of-life in December 2022. They'll probably remove various CentOS 8 files from their servers. If you want to use a CentOS that is still being updated, you can use CentOS 7 until mid 2024 (it goes end-of-life in June). And there's CentOS Stream which is not going end-of-life, but I don't use it, and don't know anything further about it. I've yet to decide what to do about it, I run a server on it because Fedora's life cycle is way too short for my liking. I really don't want such rapid major upheavals to a server. There are several newer distros that picked up where CentOS 8 left off. Take a look at AlmaLinux (https://almalinux.org/) or Rocky Linux (https://rockylinux.org/) -- both sourced from upstream RHEL and are 100% binary/bug-for-bug compatible with RHEL. They even provide easy migration tools from CentOS. Scott ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: How to create a Fedora 37 image for AWS
On 2/25/23 06:21, Peter Boy wrote: Am 25.02.2023 um 00:23 schrieb Thomas Cameron via users : Hey, all! I work for AWS, and I put together a quick HOWTO on setting up a Fedora 37 instance using KVM, and then converting it to a format that can be used to create a new EC2 instance on AWS. Note that this is a personal project, is not endorsed by AWS, and was not produced by AWS. It’s just me. https://camerontech.com/fedora-aws/ I am not a web guy, I just did a super basic HTML page using Seahorse. It’s literally something I threw together, and I am sure I missed some things, but I hope that it is helpful for anyone who wants to build their own image. I know there are a bunch of images already out there in the community, but I wanted to document how to do it for yourself. I hope you find it helpful! The first questions that comes into my mind: why not use cloud image for Amazon? It’s not Fedora Server, but something alike. But that is your kickstart as well. Or use the generic cloud image, which includes cloud-init, and adjust that? And just in case you whish to provide a (real) Fedora Server, why don’t you use the provided KVM image and add some specifics apps using e.g. guestfish on the image (as described in the Fedora Server documentation)? Or use the kickstart from Fedora repository and add some specific apps to it? I’m just curious, no criticism. I created the KVM image and know about the difficulties and peculiarities using kickstart and imagefactory. Thanks for the response! I could have, and probably should have, used Amazon EC2 Image Builder (https://aws.amazon.com/image-builder/), but I wanted to understand all the steps myself. And I specifically wanted the Fedora server build. This was mostly a thought exercise/learning experience thing, to be honest. I hoped that it would be helpful in case anyone else wanted to understand all the steps. Pure learning exercise. I had to look all over the web to find the right steps to build my own image and make it work. There were some things I had to find on Red Hat's web site, other things I needed to figure out from the AWS web site, and some trial and error things because there was stuff that weren't clearly documented or intuitive/obvious (like the recent change that S3 buckets require encryption). Honestly, this was just me nerding out and having fun, and I wanted to share it in case anyone else wanted to do the same. -- Take care! Thomas ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Taking better advantage of BTRFS
On Fri, Feb 24, 2023 at 09:31:22AM -0500, John Mellor wrote: > Ok, I'm anticipating a firestorm of BS responses on this, but here goes > anyway. > > We've now had BTRFS as the default filesystem for some time in Fedora. > However, there has been almost nothing done to take advantage of its > capabilities. This leads to some obvious questions about future work: > > 1) When are we going to see removal of the EXT2 /boot partition? It is no > longer required, as the boot process has been able to use BTRFS for years > now. The entire boot story is undergoing work now. The historical reason for /boot is encrypted installs. You need a unencryped thing to have the kernel/initramfs so it can boot up and unlock the encrypted drive. > 2) When are we going to see timeshifting tools built into the desktop, ala > Solaris? That's incredibly useful for developers. No idea there. When someone writes something I suppose. > > 3) The existing Windows-like update mechanism is undesirable. It solves a > non-existent problem on filesystems with inodes. Like all Unix-like systems, > even Ubuntu does not require this. The ability to snapshot means that the > weird reasoning that requires 2 reboots to install virtually all update > packages is no longer required under any circumstances. When is the > software update mechanism getting a fundamental redesign? I guess you are talking about offline updates here? It's the only way to do things in a completely reliable way. Updates are applied in a minimal boot target and you are 100% sure everything is restarted. If you really don't like it you can choose to just apply updates with dnf directly/live. Of course you will then be responsible for restarting everything that needs to be and deal with issues with running applications that have issues with being updated in this manner. offline updates are a full solution to the problem, and much better for most users. > 4) When is a standard backup mechanism that takes advantage of snapshotting > going to be in the distro? The published backup packages do not seem to be > aware of the better capabilities available in BTRFS. Wrapping a few CLI > tools in a GUI seems like it should be obvious, maybe 200 lines of > shellscript or less. There's a number already available. to name two: Name : btrfs-sxbackup Summary : Incremental btrfs snapshot backups with push/pull support via SSH URL : https://github.com/masc3d/btrfs-sxbackup License : GPLv2+ Description : Btrfs snapshot backup utility with push/pull support via SSH, retention, Email : notifications, compression of transferred data, and syslog logging. Name : btrbk Summary : Tool for creating snapshots and remote backups of btrfs sub-volumes URL : https://digint.ch/btrbk/ License : GPLv3+ Description : Backup tool for btrfs sub-volumes, using a configuration file, allows : creation of backups from multiple sources to multiple destinations, : with ssh and flexible retention policy support (hourly, daily, : weekly, monthly) > 5) If you encrypt your filesystems, the BTRFS built-in encryption mechanism > is not used. Why not? LUKS is still in use, even though that is more > complicated and slower. I note the possible ability to encrypt being added > if F38, but it seems like baby steps when a general solution is already in > the code. I've not followed it closely, but my understanding is that native btrfs encryption is still not landed in the linux kernel. You have to use dm-crypt currently, which uses LUKS. > 6) Compression is not the default. Why not? SSDs are 10x slower and disks > are 100x slower than the processors of even 10 years ago, so this omission > is slowing the system down. It is the default. Since Fedora 34: https://fedoramagazine.org/fedora-workstation-34-feature-focus-btrfs-transparent-compression/ > 7) Keep the last 3 update snapshots, not just the last 3 kernels. This > would keep backout scenarios a lot more consistent and functional. You can set this up with any of the various snapshot management tools above. I'm not convinced that snapshots like this are great, since there's also other non update data taking place potentially, and rolling back could mess those things up. I suppose it's less likely on a workstation than a server. > If I look at the changes coming in Fedora 38, I am disappointed in the lack > of innovation. All of these items should be in there to make the system > cleaner, better and faster. Most of these asks have already been in SUSE > for many years now, and are well debugged and understood. Fedora is > supposed to be leading the way at the edge, not way behind it. Or am I > missing something about the politics of the distro? There's no politics here. If you feel stongly that something should be implemented, feel free to work on implementing it, or convincing others to do so. Hope that helps, kevin sig
Re: Taking better advantage of BTRFS
On 2/25/23 11:20, Kevin Fenzi wrote: If you really don't like it you can choose to just apply updates with dnf directly/live. Of course you will then be responsible for restarting everything that needs to be and deal with issues with running applications that have issues with being updated in this manner. Not exactly difficult. Obviously, if the kernel's been upgraded, you need to restart to get it running. Otherwise, you run sudo dnf needs-restarting to find out what, if any, programs need to be restarted. (If you don't have it installed, you can get it by installing dnf-utils.) Most of the time, either nothing needs restarting, or there are one or two programs you'll need to exit and restart on your own. Occasionally, you may need to log out and log back in, but having to reboot for anything less than a kernel is fairly rare. HTH, HAND. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Taking better advantage of BTRFS
On Sat, Feb 25, 2023 at 12:53:59PM -0700, Joe Zeff wrote: > On 2/25/23 11:20, Kevin Fenzi wrote: > > If you really don't like it you can choose to just apply updates with > > dnf directly/live. Of course you will then be responsible for restarting > > everything that needs to be and deal with issues with running > > applications that have issues with being updated in this manner. > > Not exactly difficult. Obviously, if the kernel's been upgraded, you need > to restart to get it running. Otherwise, you run Or glibc, or dbus or systemd or ... > sudo dnf needs-restarting > > to find out what, if any, programs need to be restarted. (If you don't have > it installed, you can get it by installing dnf-utils.) Most of the time, > either nothing needs restarting, or there are one or two programs you'll > need to exit and restart on your own. Occasionally, you may need to log > out and log back in, but having to reboot for anything less than a kernel is > fairly rare. HTH, HAND. Yeah, needs restarting is pretty cool. If you are logging out and back in, a reboot really isn't that much more hassle IMHO. I used needs-restarting for a while a few years ago, but it was pretty often that you basically had to restart everything and a reboot was just a lot easier. YMMV. kevin signature.asc Description: PGP signature ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Taking better advantage of BTRFS
On Sat, 2023-02-25 at 12:53 -0700, Joe Zeff wrote: > On 2/25/23 11:20, Kevin Fenzi wrote: > > If you really don't like it you can choose to just apply updates > > with > > dnf directly/live. Of course you will then be responsible for > > restarting > > everything that needs to be and deal with issues with running > > applications that have issues with being updated in this manner. > > Not exactly difficult. Obviously, if the kernel's been upgraded, you > need to restart to get it running. Otherwise, you run > > sudo dnf needs-restarting > > to find out what, if any, programs need to be restarted. (If you > don't > have it installed, you can get it by installing dnf-utils.) Now part of the python3-dnf-plugins-core package so you don't need a separate command. With the plugin installed it just runs automatically. > Most of the > time, either nothing needs restarting, or there are one or two > programs > you'll need to exit and restart on your own. Occasionally, you may > need > to log out and log back in, but having to reboot for anything less > than a kernel is fairly rare. HTH, HAND. My only quibble is that it sometimes tells you (correctly) to restart something where it's not obvious how to do this other than logging out and in again, e.g. pipewire-media-session. If the plugin were better informed about this kind of component it would be more user-friendly. poc ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Taking better advantage of BTRFS
> On 25 Feb 2023, at 22:00, Patrick O'Callaghan wrote: > > On Sat, 2023-02-25 at 12:53 -0700, Joe Zeff wrote: >>> On 2/25/23 11:20, Kevin Fenzi wrote: >>> If you really don't like it you can choose to just apply updates >>> with >>> dnf directly/live. Of course you will then be responsible for >>> restarting >>> everything that needs to be and deal with issues with running >>> applications that have issues with being updated in this manner. >> >> Not exactly difficult. Obviously, if the kernel's been upgraded, you >> need to restart to get it running. I update all my fedora systems once a week. I do not recall the last time there was not a new kernel. As the reboot is once a week it is no inconvenience; I always do that. Barry >> Otherwise, you run >> >> sudo dnf needs-restarting >> >> to find out what, if any, programs need to be restarted. (If you >> don't >> have it installed, you can get it by installing dnf-utils.) > > Now part of the python3-dnf-plugins-core package so you don't need a > separate command. With the plugin installed it just runs automatically. > >> Most of the >> time, either nothing needs restarting, or there are one or two >> programs >> you'll need to exit and restart on your own. Occasionally, you may >> need >> to log out and log back in, but having to reboot for anything less >> than a kernel is fairly rare. HTH, HAND. > > My only quibble is that it sometimes tells you (correctly) to restart > something where it's not obvious how to do this other than logging out > and in again, e.g. pipewire-media-session. If the plugin were better > informed about this kind of component it would be more user-friendly. > > poc > ___ > users mailing list -- users@lists.fedoraproject.org > To unsubscribe send an email to users-le...@lists.fedoraproject.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org > Do not reply to spam, report it: > https://pagure.io/fedora-infrastructure/new_issue ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Taking better advantage of BTRFS
On 2/25/23 14:58, Patrick O'Callaghan wrote: Now part of the python3-dnf-plugins-core package so you don't need a separate command. With the plugin installed it just runs automatically. So when you use dnf upgrade, it also tells you what needs restarting? Cool! ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Taking better advantage of BTRFS
snapper (I believe this is suse's tool) can be installed on Fedora. Unfortunately it takes a little extra work to setup the subvolumes correctly. I found an article (on reddit?) and mine are setup as: sudo btrfs subvolume list / ID 256 gen 149284 top level 5 path root ID 257 gen 149284 top level 5 path home ID 258 gen 149105 top level 256 path var/lib/machines ID 260 gen 112374 top level 5 path snapshots Then mounted as: /dev/nvme0n1p3 248108356 94618996 151112236 39% /.snapshots snapper can be configured to make snapshots on command, or I believe automatically with each update On Sat, Feb 25, 2023 at 5:43 PM Joe Zeff wrote: > On 2/25/23 14:58, Patrick O'Callaghan wrote: > > Now part of the python3-dnf-plugins-core package so you don't need a > > separate command. With the plugin installed it just runs automatically. > > So when you use dnf upgrade, it also tells you what needs restarting? > Cool! > ___ > users mailing list -- users@lists.fedoraproject.org > To unsubscribe send an email to users-le...@lists.fedoraproject.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org > Do not reply to spam, report it: > https://pagure.io/fedora-infrastructure/new_issue > -- *Those who don't understand recursion are doomed to repeat it* ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
