copy2fs boot code

[Misalf]

Is there a reason for no  copy2fs  boot code?

If I get it right, when booting off of CD, there is no way to eject the CD after boot, unless it was remastered with added  /etc/sysconfig/tcedir/copy2fs.flg .

I'm currently thinking about how to add the  copy2fs  boot code to  tc-config  and   tce-setup  but please stop me if you know this would break things, as I'm not familiar with every method Core offers for loading extension (builtin/*.gz, *.tcz, PXE, etc.).

[Misalf]

Hmm, am I going too easy?
This works on my installation:

Code: [Select]

--- tce-setup.old
+++ tce-setup.new
@@ -35,6 +35,7 @@
  mkdir "$TCEDIR"/optional
  chown -R "$USER".staff "$TCEDIR"
  fi
+ [ -n "$COPY2FS" ] && touch "$TCEDIR"/copy2fs.flg
  [ -L /etc/sysconfig/tcedir ] && rm -f /etc/sysconfig/tcedir
  ln -sf "$TCEDIR" /etc/sysconfig/tcedir
  chown -R "$USER".staff "$TCEINSTALLED"
@@ -112,6 +113,7 @@
  case $i in
  cde) CDE=1 ;;
  base) ONLYBASE=1 ;;
+ copy2fs) COPY2FS=1 ;;
  esac
 done
 



[Misalf]

Yeah, too easy. Doesn't work for  base .
I might wait for comments before I dig further.

[Juanito]

If I get it right, when booting off of CD, there is no way to eject the CD after boot, unless it was remastered with added  /etc/sysconfig/tcedir/copy2fs.flg .

This works for me:

Code: [Select]

$ sudo umount /mnt/sr0
$ eject

[Misalf]

Really? Shouldn't it refuse to un-mount while there are extensions mounted from sr0 (resource or device busy) ?

[Juanito]

the extensions are loaded to ram, no?

[Misalf]

Oh, yes!
There is  /cde/copy2fs.lst , containing every extension stored in  /cde/optional . Big oversight. :p
This probably reduces my efforts by some degree as CDs are not affected.
I'd still find a  copy2fs  boot code useful but I'm realizing now that it's not really required. Maybe I'll come back to this if I can get it done without complicating things.