Tiny Core Base > TCB Bugs

I/O dev fd0

<< < (3/8) > >>

jpeters:
What do you use to gzip the edited tinycore file? I added the line, but get a kernel panic when I gzip it and cp back to /tinycore.  I tried gzip and gzip -9 with the same freakout result.

roberts:
That is why I asked about the nofstab option. But it was reported that it failed there.

Note the original does not set the perms or identify pendrive (vfat) properly.
Setting it back to original results in auto for vfat.

But this is why we have RC testing. I will look further. But could not reproduce the fd0 error.

Jason W:
"Fixed" was a term I used very loosely, meaning there was no more delay but without further diagnosis.  Since I have hardware that is affected by this I will also troubleshoot and see if I can help.

jpeters:
the correct way to repack edited tinycore is....?

Jason W:
I have booted with TC-1.1 and my fstab entries for a FAT16 usb key and a fat32 HD partition are as follows:

pendrive:
/dev/sda1       /mnt/sda1       vfat     noauto,users,exec,umask=000 0 0 # Added by TC    

HD partition:
/dev/hdb1       /mnt/hdb1       vfat     noauto,users,exec,umask=000 0 0 # Added by TC

I may be overlooking something, but that is what TC autodetected for my two fat partitions.  Are there other conditions that result in a different result?

Navigation

[0] Message Index

[#] Next page

[*] Previous page