Tiny Core Base > TCB Bugs

Persistence and boot codes

(1/3) > >>

Kingdomcome:
Found a couple things dealing with boot codes

1. All the documentation shows that for PPI you use the boot code "tclocal=" where you actually need "local="

2. when using the boot codes "local=" and "opt=" and having both point at the same partition, opt does not get mounted.  the error on the boot screen says /dev/hdxy mounted or busy.

mikshaw:
2. This also applies when mixing in "home=" on the same partition.  The init script uses the flawed logic "if the mount command fails, then it isn't mounted", and so it simply gives up.

roberts:
It was never intended to run that way.

Typically when doing a traditional hard drive installation, one makes many partitions for their installation and not use a single partition. I thought single partition installations was a relic. Regarding persistence, this I had this in mind.

I will take this as a feature enhancement.

@mikshaw, why the vinegar?

tobiaus:
i would have guessed single partition installs would grow more common the more people use linux, so that partitioning is less "involved."

not necessarily for very large, popular debian-based distros that hold your hand through partitioning, (and must use swap) but for many others. then there is the swap file, removing need for a swap partition.

^thehatsrule^:
Chatted with Kingdomcome yesterday about this.  Came up with some sort of solution... there could be a better way of doing it.


--- Code: ---is_mounted()
{
  awk_line="\$2 == \"\/mnt\/$1\" {print \$2}"
  found=$(awk "$awk_line" /etc/mtab )
  [ -n "$found" ]
  return $?
}
--- End code ---

Then you could replace all mount lines as required with something like
--- Code: ---is_mounted $MY_DEVICE || mount /mnt/$MY_DEVICE
--- End code ---

---

For #1, he pointed out that it shows up on the F3 and the "getting started" doc.

I'm sure mikshaw didn't mean it like that :p  I vaguely remember someone running into this before with that...

Navigation

[0] Message Index

[#] Next page