Jump to content
Read the Funtoo Newsletter: Summer 2023 ×

pytony

Funtoo Linux Developer
 View Profile  See their activity

  • Posts

    46

  • Joined

  • Last visited

  • Days Won

    5

 Content Type 

Posts posted by pytony

  1. ego trouble

    in Portage Help

    Posted

    Yes the problem was that appi used the default system encoding to read files, which is ascii when LANG=C. I assumed encoding should always be utf-8 for these files and explicitly read them with this encoding. If it happens that they may be encoded with a different charset on some systems, I'll have to handle this...

  8. Change to kits and python confusion

    in Portage Help

    Posted

    `epro update` updates the contents of the file `/etc/portage/make.profile/parent`. This file contains profiles that determine default useflags, masks, make.conf, ... These profiles depend on the python-kit branch you use and profiles you set with epro.

    `epro update` is indeed missing from documentation. You can file an issue on Jira about it.

  12. Funtoo Reinstall - Some hints?

    in General Discussion

    Posted

    Thanks Tassie_Tux, I think I'm gonna do a separate `/var` and  `/usr/portage/distfiles`. I don't especially need options tuned for mysql performance. This is a database I only use occasionally when I am teleworking.

     

    I am currently reading about ZFS. If I understand correctly, I can use ZFS instead of LVM as it ships with its own logical volume manager. However I guess I still need LVM if I want to have distinct filesystems on each volume.

  13. Funtoo Reinstall - Some hints?

    in General Discussion

    Posted

    Hi,

     

    I'm planning to reinstall Funtoo in order to move to pure64 (as I'm not using any 32bit).

     

    Upstream of said reinstall, I think about repartitioning my disks.

     

    I would like to leave some space free in order to be able to install LFS aside.

     

    I do have one 56GB SSD (sda), one 233GB HDD (sdb) and 1?4GB RAM.

     

    My disks are currently partitioned as the following :

     

    • / -> /dev/sda3 53.5GB
    • /boot -> /dev/sda1 0.5GB
    • swap -> /dev/sda2 2GB
    • /home -> /dev/sdb1 233GB

    I think about keeping /boot and swap as-is, and split rootfs in 30GB for Funtoo and 23.5GB for LFS

     

    However according  to df, rootfs already takes 30GB. So I scanned my disk to identify huge folders :

     

    • /usr (19G)
      • /usr/portage (11G)
        • /usr/portage/distfiles (9.8G)
      • /usr/src (2.8G)
      • /usr/share (2.1G)
      • /usr/lib64 (1.8G)
    • /var (11G)
      • /var/lib (9.7G)
        • /var/lib/mysql (9.5G)

     

    Don't you think it would be appropriate to leave /var/lib on its own partition (uppon /dev/sda) ? Or maybe the whole /var directory should be on the HDD rather than on the SSD ?

     

    Maybe /usr/portage would also be welcome on its own partition ?

     

    If I do this, I guess I will have to setup an initramfs (which I don't have yet). I see it as an opportunity to learn what it is, how it works and why it is needed.

     

    If I setup an initramfs, I will take the opportunity to go back to LVM as well (I left LVM in order to get rid of the initramfs when I wanted to focus on the kernel).

     

    Finally, I also think about learning  more about filesystems and try "unusual" ones. Until now, I've only been using ext[2-4] and XFS. I've heard a lot about ZFS and BtrFS. Unfortunately I don't know much about filesystems (only got a very basic course about FAT, inode-based FS and the differences) and I don't know what changes I will be able to notice and what things I will be able to do with another filesystem. Do you think it is advisable to, let's say, use ZFS for the rootfs and learn more about filesystems a few months later ?

     

    Thank you all.

  14. Stupid Admin Tricks

    in Server Help

    Posted

    I'm picking up your w!! trick for vim :P

     

    mkdir and cd in a row:

    mkncd() {
  mkdir -pv $1
  cd $1
}

    In my python virtualenvs (using virtualenvwrapper), I have a postactivate hook to cd in the right directory after "workon virtualenv":

    [[ -f "$VIRTUAL_ENV/.workpath" ]] && cd $(cat $VIRTUAL_ENV/.workpath)

  16. funtoo logo ideas

    in Funtoo Infrastructure

    Posted

    Agreed with the @j-g- choice.

    And since you asked above, 80x80:

     

    uVdaJcq.png

     

    80x80 png (actually 96x36 or something, but close enough.)

     

    I don't think the point was actually to get a 80x80 logo, but a squared logo (ie. that can be used as a favicon or any squared icon).

  17. Post your make.conf

    in General Discussion

    Posted 


    
MAKEOPTS="-j7"
    

    
EMERGE_DEFAULT_OPTS="-j --load-average=6"
    

    
ALSA_CARDS="hda-intel"
    
VIDEO_CARDS="nouveau"
    
INPUT_DEVICES="evdev"
    

    
PHP_TARGETS="php5-6"
    

    
FEATURES="${FEATURES} splitdebug"
    

    
USE="${USE} udev -systemd -pulseaudio"
    

    
WORK_OVERLAYS=""
    
#WORK_OVERLAYS="${WORK_OVERLAYS} /home/tony/Workspace/Funtoo/funtoo-overlay"
    
#WORK_OVERLAYS="${WORK_OVERLAYS} /home/tony/Workspace/Funtoo/funtoo-mysql"
    
#WORK_OVERLAYS="${WORK_OVERLAYS} /home/tony/Workspace/Funtoo/sapher-overlay"
    
#WORK_OVERLAYS="${WORK_OVERLAYS} /usr/local/portage"
    

    
PORTDIR_OVERLAY="${PORTDIR_OVERLAY} ${WORK_OVERLAYS}"
    

    
source /var/lib/layman/make.conf

  25. kernel not found...

    in Installation Help

    Posted

    first mistake:

    In order to install Funtoo Linux, you will first need to boot your computer using a Linux-based Live CD or USB stick

    I tried to install from my working OS !!!

     

     

    It shouldn't be an issue, unless you want to install Funtoo on the same disk, which would have failed miserably at step 2: Prepare you disks.

     

    >  little confusin at least to ME !

    > Do I need to touch /etc/fstab on funtoo install ??? ???

     

    Yes, this depends on the partitions you created. If ever you don't need to edit it, you must at least make sure it matches your configuration.

     

    You may succeed to chroot in the system and fix the issue using a live USB.

×
×
  • Create New...