I'm seriously considering shutting down our funtoo forums and just redirecting everyone over to https://www.reddit.com/r/funtoo/for 'forums'.
Reason: reddit gets funtoo a lot more exposure and provides a popular forums-style discussion area.
Before making a decision, I want to get feedback from people here. It is cool to have our own forums but there is also some downside that only a fraction of Funtoo users participate in forums and new users may have an easier time posting questions to reddit. It also ensures that our funtoo reddit community will be 'staffed' with true funtoo users, which is important.
you can use that of course is as the Stage 3 is compress don't have any problem
but you can use a personal script, I use that
more faster but more size on disk :
tar -cvpf /stage4.tar.xz --directory=/ --exclude=/stage4.tar.xz --exclude=/dev/* --exclude=/lost+found --exclude=/mnt/* --exclude=/proc/* --exclude=/run/* --exclude=/sys/* --exclude=/tmp/* --exclude=/var/log/* --exclude=/var/run/* --exclude=/var/tmp/* /
or that more slow(very slow) but less than half of the other option :
tar -cpvf - --directory=/ --exclude=/stage4.tar.xz --exclude=/dev/* --exclude=/lost+found --exclude=/mnt/* --exclude=/proc/* --exclude=/run/* --exclude=/sys/* --exclude=/tmp/* --exclude=/var/log/* --exclude=/var/run/* --exclude=/var/tmp/* . | xz -9e -c - > /stage4.tar.xz
of course you can change the exclude folders and files as you wish.
you can use that of course is as the Stage 3 is compress don't have any problem
but you can use a personal script, I use that
more faster but more size on disk :
tar -cvpf /stage4.tar.xz --directory=/ --exclude=/stage4.tar.xz --exclude=/dev/* --exclude=/lost+found --exclude=/mnt/* --exclude=/proc/* --exclude=/run/* --exclude=/sys/* --exclude=/tmp/* --exclude=/var/log/* --exclude=/var/run/* --exclude=/var/tmp/* /
or that more slow(very slow) but less than half of the other option :
tar -cpvf - --directory=/ --exclude=/stage4.tar.xz --exclude=/dev/* --exclude=/lost+found --exclude=/mnt/* --exclude=/proc/* --exclude=/run/* --exclude=/sys/* --exclude=/tmp/* --exclude=/var/log/* --exclude=/var/run/* --exclude=/var/tmp/* . | xz -9e -c - > /stage4.tar.xz
of course you can change the exclude folders and files as you wish.
It's been pretty quiet lately so I want to throw in another "thank you" to the crew that creates and maintains Funtoo. I discovered Funtoo as a way to fight systemd but I've been really pleased at what a great all-around distro it's proven to be. So, "Thanks!"
I am very thankful for Funtoo's existance. I'm really glad that you guys(the team) are still maintaining it and I hope it continues for long. I began with Gentoo and I found it incredibly frustrating, and after hours of work I found out my touchpad didn't work with Gentoo kernel. Funtoo on the other hand has been a dream and everything I wanted in a system, I made an account to lurk about and share whatever I can to show community.
Thanks, Daniel and others and for every contribution. It was a long journey, but now from a Kubuntu background I'm in the process of adopting a Funtoo system with KDE Plasma 5.
Is it a good or bad idea to take a syste, backup by running:
tar cpJfv funtooLinux.tar.xz /
rather than making an iso image of the partition/disk. Does it matter?
you can use that of course is as the Stage 3 is compress don't have any problem
but you can use a personal script, I use that
more faster but more size on disk :
tar -cvpf /stage4.tar.xz --directory=/ --exclude=/stage4.tar.xz --exclude=/dev/* --exclude=/lost+found --exclude=/mnt/* --exclude=/proc/* --exclude=/run/* --exclude=/sys/* --exclude=/tmp/* --exclude=/var/log/* --exclude=/var/run/* --exclude=/var/tmp/* /
or that more slow(very slow) but less than half of the other option :
tar -cpvf - --directory=/ --exclude=/stage4.tar.xz --exclude=/dev/* --exclude=/lost+found --exclude=/mnt/* --exclude=/proc/* --exclude=/run/* --exclude=/sys/* --exclude=/tmp/* --exclude=/var/log/* --exclude=/var/run/* --exclude=/var/tmp/* . | xz -9e -c - > /stage4.tar.xz
of course you can change the exclude folders and files as you wish.
I've been trying to get early boot Intel microcode updating working on my Funtoo install. I have verified with microcode-ctl that I can update my CPU's microcode manually from the command line. However, after following the instructions at https://wiki.gentoo.org/wiki/Intel_microcodeI have been unable to get it working at boot.
Here's an entry from my /etc/boot.conf
"Funtoo - Gentoo 4.8.6 + CK/MuQSS 0.135 + UKSM" {
kernel vmlinuz-4.8.6-gentoo-ck6
initrd /lib/firmware/microcode.cpio initramfs-genkernel-x86-4.8.6-gentoo-ck6
params += real_root=auto rootfstype=auto
params += mtrr_reg_cleanup=6
}
and the corresponding section of /boot/grub/grub.cfg
menuentry "Funtoo - Gentoo 4.8.6 + CK/MuQSS 0.135 + UKSM - vmlinuz-4.8.6-gentoo-ck6" {
insmod part_msdos
insmod btrfs
set root=(hostdisk//dev/sda,msdos1)
search --no-floppy --fs-uuid --set e050f0b2-8494-4e53-a19f-6c57f036cc41
linux /boot/vmlinuz-4.8.6-gentoo-ck6 rootfstype=auto mtrr_reg_cleanup=6 real_root=/dev/sda1 rootfstype=btrfs
initrd /boot/initramfs-genkernel-x86-4.8.6-gentoo-ck6
set gfxpayload=keep
}
Notice that the "/lib/firmware/microcode.cpio" was removed from the initrd line when grub.cfg was processed by the boot-update utility.
boot-update needs to have support for this added, or some other method for providing the microcode to the kernel at boot should be proposed.
AdiosKid reacted to drobbins in Getting Rid of Forums and Moving to Reddit?
AdiosKid got a reaction from artemeciagreen in Taking a system backup as a tar archive.
AdiosKid got a reaction from coosee in Taking a system backup as a tar archive.