WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Author Topic: tinycore_v3.6rc3  (Read 15352 times)

Offline Lee

  • Hero Member
  • *****
  • Posts: 645
    • My Core wiki user page
Re: tinycore_v3.6rc3
« Reply #15 on: April 22, 2011, 11:24:24 AM »
/etc/motd in 3.6rc3 mentions www.tinycorelinux.com.  Should it be www.tinycorelinux.net?

32 bit core4.7.7, Xprogs, Xorg-7.6, wbar, jwm  |  - Testing -
PPR, data persistence through filetool.sh          |  32 bit core 8.0 alpha 1
USB Flash drive, one partition, ext2, grub4dos  | Otherwise similar

Offline netnomad

  • Hero Member
  • *****
  • Posts: 1026
Re: tinycore_v3.6rc3
« Reply #16 on: April 22, 2011, 11:49:05 AM »
hi roberts,

i did not mix manual, command line, with TC system generated encryption.

these are my bootcodes:

kernel (hd32)/boot/bzImage waitusb=5 protect restore=LABEL=tc vga=795 psmouse.proto=imps tz=GMT-2 laptop kmap=de mydata=data36

i think that in the protect mode my restore-path is not used. its not important whether i use restore=LABEL=tc or restore=sda2,
the /etc/sysconfig/bfe stores my password and the /etc/sysconfig/mydata stores the name of my backup-file correctly, but the /opt/.backup_device is empty.
when i restore my encrypted backup with the gui, then at first there is no entry or path in the backup/restore-gui and i have to insert the path, for my example sda2.
so i think in my bootcodes that you see above the restore-path is not used at all.
manually with the help of the backup-gui i can restore my encrypted-backup without any problems.

on the other side in the normal unecrypted mode the restore works automatically at the reboot.
« Last Edit: April 22, 2011, 03:51:40 PM by netnomad »

Offline roberts

  • Administrator
  • Hero Member
  • *****
  • Posts: 7361
  • Founder Emeritus
Re: tinycore_v3.6rc3
« Reply #17 on: April 22, 2011, 03:34:03 PM »
Both bkg and theme boot codes are relics from early TC v1.x days for JWM.
. Use control panel->wallpaper to easily select options desired.
how to make this setup persistent?

If you are using images then simply add /opt/backgrounds to /opt/.filetool.lst
image.jpg and leuchtturm.jpg were already both in /opt/backgrounds
tcl3.6rc3 with bootcode bkg=image.jpg.. dont show the "image" (can be activated with the wallpaper menue)
mc3.6.3 with bootcode bkg=leuchtturm.jpg show the "leuchtturm" direct after boot
Curious. Different on both release.
the microcore is using the lst=microorg.lst bootoption, not tcl, which is automaticaly loading the onboot.lst file
If you see a difference between TC and MC, it is likely that you are not using the Xprogs.tcz in the release candidate area.
10+ Years Contributing to Linux Open Source Projects.

Offline roberts

  • Administrator
  • Hero Member
  • *****
  • Posts: 7361
  • Founder Emeritus
Re: tinycore_v3.6rc3
« Reply #18 on: April 22, 2011, 04:50:45 PM »
@netnomad

I don't see a tce directory specified in your boot codes.
That has allowed me to see your issue regarding protect.
I have a correction for the next rc.
10+ Years Contributing to Linux Open Source Projects.

Offline netnomad

  • Hero Member
  • *****
  • Posts: 1026
Re: tinycore_v3.6rc3
« Reply #19 on: April 22, 2011, 04:54:11 PM »
hi roberts,

thank you for your response.
actually i did not need the tce-directory bootcode yet...

thanks