WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Author Topic: Move the processing "home="  (Read 1727 times)

Offline MiniQ9

  • Newbie
  • *
  • Posts: 48
Move the processing "home="
« on: January 04, 2011, 04:02:02 PM »
I propose to move the processing kernel parameter home= after loading extensions, before processing the parameter restore=.
I explain. My home is located on a partition sda3 (reserfs), to connect you need to load modules.

Offline gerald_clark

  • TinyCore Moderator
  • Hero Member
  • *****
  • Posts: 4254
Re: Move the processing "home="
« Reply #1 on: January 04, 2011, 04:13:36 PM »
Have you tried making a .gz of the modules, and putting it in the tce directory?

Offline MiniQ9

  • Newbie
  • *
  • Posts: 48
Re: Move the processing "home="
« Reply #2 on: January 05, 2011, 03:20:34 AM »
Module filesystems ... tcz lies in tce and loaded with onboot.lst
However, the treatment occurs before the home= the time of loading modules.
Now problems are solved in bootlocal.sh:
Code: [Select]
#!/bin/sh
# put other system startup commands here
modprobe reiserfs
mount -o async,nodev /dev/sda3 /mnt/sda3
mount -o bind /mnt/sda3/home /home
.....
But it's a crutch, right?

Offline curaga

  • Administrator
  • Hero Member
  • *****
  • Posts: 11044
Re: Move the processing "home="
« Reply #3 on: January 06, 2011, 09:05:59 AM »
Some extensions create config files etc in $HOME, thus it needs to be available before loading extensions.
The only barriers that can stop you are the ones you create yourself.