Discussion, talk and tips
https://forum.puppylinux.com/
When I tried to do a save file on xenialpupp64, the thumbnail drive was not
even listed.
Had clicked the the thumbnail drive to make sure it was mounted.
And it's not even letting me choose the size of the save file, and the save file type.
What's going on here?
By 'thumbnail' do you mean an sdcard?
If so, see viewtopic.php?p=8074#p8074 and the links from it. Follow watchdog's instructions.
The kernel/vmlinuz included in Xenialpup64's ISO may not be new enough/have the instructions and firmware to boot from an sdcard. You could try swapping kernels. Note, if you replace xenialpup64's kernel with one from a recent Slacko (maybe any recent kernel) you may need firmware packaged in an fdrv.sfs, appropriately re-named.
Look on the drive for the boot loader menu config file.
Not sure how you did the install.
The config file should be one of these.
grub.cfg
menu.lst
syslinux.cfg
open in a text editor.
In the entries look for pmedia=
If it is pmedia=cd
Change it to pmedia=usbflash or ataflash.
save change.
If you already made a save.
Delete it or boot not using it.
So when you now shutdown you will be asked to make a save.
Any help?
.
.
Thanks, that worked.
Having trouble with it again.
Tried to do a reboot, it did not offer to to do a save file.
It has offered to resize the personal saved.
Can't figure out where it is saving it to.
Looked all over my thumbnail file, and can't fine any save
file on it.
Here is the grub file.
Code: Select all
insmod png
background_image /kodipup.png
set timeout=10
menuentry "Start kodipup" {
linux /vmlinuz pmedia=usbflash nouveau.modeset=0
initrd /initrd.gz
}
menuentry "Start kodipup - RAM only" {
linux /vmlinuz pfix=ram pmedia=usbflash nouveau.modeset=0
initrd /initrd.gz
}
menuentry "Start kodipup - No X" {
linux /vmlinuz pfix=nox pmedia=usbflash
initrd /initrd.gz
}
menuentry "Start kodipup - check filesystem" {
linux /vmlinuz pfix=fsck pmedia=usbflash
initrd /initrd.gz
}
menuentry "Start kodipup - No KMS" {
linux /vmlinuz nomodeset
initrd /initrd.gz
}
menuentry "Shutdown" {
halt
}
menuentry "Reboot" {
reboot
}
Where is it saving the puppy save file at?
Is there any way to pause the messages that flash on the screen, or
get a log file of what the puppy is doing?
Can't figure out where it is saving it to.
It might tell you in /etc/rc.d/PUPSTATE
log file of what the puppy is doing?
There are other files in /etc/rc.d/
There are log files in /tmp/
and in /var/log/
When I tried to do a save file on xenialpupp64, the thumbnail drive was not
even listed.
The menu entries you posted are for kodipup.
So what Puppy is it?
Tried to do a reboot, it did not offer to to do a save file.
If you boot and already have a save, it is not going to ask to make another one.
If you boot not using the save.
On shutdown is when it offers to make a save.
This kodipup entry boots not using the save.
menuentry "Start kodipup - RAM only" {
linux /vmlinuz pfix=ram pmedia=usbflash nouveau.modeset=0
initrd /initrd.gz
If you already made a save.
Delete the save and boot not having one to use or boot not using the save.
So when you now shutdown you will be asked to make a save.
Give the save a name, so you can figure out which one it is, if by chance, you end up with two saves.
Then delete the one that is in the wrong location or add .bak to the beginning of it's name, to have a backup save.
Do have to carefully select where to put it and size you want to make it.
2 or 3 GB is a good size.
Note:
You talked about being asked to resize the save.
So I assume you installed to a USB drive probably formatted fat32.
It is going to be a save file.
Fat 32 has a max file size limit of 4GB.
That is the max size you can make the save file.
But you can store stuff that is not settings or installed added programs, outside of the save. (documents, pictures, downloaded files, etc.....)
/mnt/home is a good place for that.
That is the top layer of the USB's file system. Not inside any directory/folder, but just on the USB.
If you want to find your pupsave completely in the dark (you have no idea where it is):
1. mount all your partitions
2. run pFind
3. click on All files (slow)**
4. search on xenialpupsave
I'm assuming the name on a 32 system. It might be xenialsave. There might be 64 in the name. The file extension is .2fs (another possible search term).
If you copy it to the boot partition folder that boots otherwise in LIVE mode, it should boot. If there's another pupsave there, you'll get a choice. If none, the copied pupsave is default.
A resize offer is usually because you're low on personal storage space. Sometimes it makes more sense to delete unneeded items (e.g., browser configurations in /root) and resave than to increase a pupsave. Another option is to copy the pupsave and rename it, so you have the one you currently have and the revised larger save.
**I would expect it to be in personal files and never system, but since system searches fast, it does not hurt.
Puppy linux is always wanting to save the save file to the c: drive
It's not giving me a choice to save to the thumbnail drive.
Used Lick to install it on my e: partition.
The thumbnail drive is formatted as ntfs .
It's also not showing me a picture with a menu on it.
No Menu.
Here is my updated grub file.
Code: Select all
insmod png
background_image /kodipup.png
set timeout=10
menuentry "Start kodipup" {
linux /vmlinuz pmedia=satahd nouveau.modeset=0
initrd /initrd.gz
}
menuentry "No save" {
linux /vmlinuz pfix=ram pmedia=satahd nouveau.modeset=0
initrd /initrd.gz
}
menuentry "Start kodipup - No KMS" {
linux /vmlinuz nomodeset
initrd /initrd.gz
}
menuentry "Shutdown" {
halt
}
menuentry "Reboot" {
reboot
}
Here is my lickgrub.cfg from the c: drive.
Code: Select all
## start header
insmod part_gpt
insmod part_msdos
insmod ntfs
set timeout=5
set default=2
insmod all_video
if loadfont /grub/fonts/unicode.pf2 ; then
set gfxmode=auto
set gfxpayload=keep
terminal_output gfxterm
fi
## end header
## start section xenialpup64-7.5-dev-uefi
menuentry 'xenialpup64 7.5 dev uefi' {
search --set=root --file /xenialpup64-7.5-dev-uefi/vmlinuz
linux /xenialpup64-7.5-dev-uefi/vmlinuz pfix=fsck psubdir=xenialpup64-7.5-dev-uefi
initrd /xenialpup64-7.5-dev-uefi/initrd.gz
}
menuentry 'xenialpup64 7.5 dev uefi (no save file)' {
search --set=root --file /xenialpup64-7.5-dev-uefi/vmlinuz
linux /xenialpup64-7.5-dev-uefi/vmlinuz pfix=ram savefile=none psubdir=xenialpup64-7.5-dev-uefi
initrd /xenialpup64-7.5-dev-uefi/initrd.gz
}
## end section xenialpup64-7.5-dev-uefi
## start section Windows
menuentry "Windows" {
insmod chain
search --set=root --file /EFI/Microsoft/boot/bootmgfw.efi
chainloader /EFI/Microsoft/boot/bootmgfw.efi
}
## end section Windows
## start section xenialpup64-7.5-uefi
menuentry 'xenialpup64 7.5 uefi' {
search --set=root --file /xenialpup64-7.5-uefi/vmlinuz
linux /xenialpup64-7.5-uefi/vmlinuz pfix=fsck psubdir=xenialpup64-7.5-uefi
initrd /xenialpup64-7.5-uefi/initrd.gz
}
menuentry 'xenialpup64 7.5 uefi (no save file)' {
search --set=root --file /xenialpup64-7.5-uefi/vmlinuz
linux /xenialpup64-7.5-uefi/vmlinuz pfix=ram savefile=none psubdir=xenialpup64-7.5-uefi
initrd /xenialpup64-7.5-uefi/initrd.gz
}
## end section xenialpup64-7.5-uefi
## start section Main-Comp-Kodi-15
menuentry 'Main Comp Kodi 15' {
search --set=root --file /Main-Comp-Kodi-15/vmlinuz
linux /Main-Comp-Kodi-15/vmlinuz pfix=fsck psubdir=Main-Comp-Kodi-15
initrd /Main-Comp-Kodi-15/initrd.gz
}
menuentry 'Main Comp Kodi 15 (no save file)' {
search --set=root --file /Main-Comp-Kodi-15/vmlinuz
linux /Main-Comp-Kodi-15/vmlinuz pfix=ram savefile=none psubdir=Main-Comp-Kodi-15
initrd /Main-Comp-Kodi-15/initrd.gz
}
## end section Main-Comp-Kodi-15
## start section Main-Comp-Kodi-16
menuentry 'Main Comp Kodi 16' {
search --set=root --file /Main-Comp-Kodi-16/vmlinuz
linux /Main-Comp-Kodi-16/vmlinuz pfix=fsck psubdir=Main-Comp-Kodi-16
initrd /Main-Comp-Kodi-16/initrd.gz
}
menuentry 'Main Comp Kodi 16 (no save file)' {
search --set=root --file /Main-Comp-Kodi-16/vmlinuz
linux /Main-Comp-Kodi-16/vmlinuz pfix=ram savefile=none psubdir=Main-Comp-Kodi-16
initrd /Main-Comp-Kodi-16/initrd.gz
}
## end section Main-Comp-Kodi-16
## start section Main-Comp-Kodi-17
menuentry 'Main Comp Kodi 17' {
search --set=root --file /Main-Comp-Kodi-17/vmlinuz
linux /Main-Comp-Kodi-17/vmlinuz pfix=fsck psubdir=Main-Comp-Kodi-17
initrd /Main-Comp-Kodi-17/initrd.gz
}
menuentry 'Main Comp Kodi 17 (no save file)' {
search --set=root --file /Main-Comp-Kodi-17/vmlinuz
linux /Main-Comp-Kodi-17/vmlinuz pfix=ram savefile=none psubdir=Main-Comp-Kodi-17
initrd /Main-Comp-Kodi-17/initrd.gz
}
## end section Main-Comp-Kodi-17
## start section MyKodi-Puppy64
menuentry 'MyKodi Puppy64' {
search --set=root --file /MyKodi-Puppy64/vmlinuz
linux /MyKodi-Puppy64/vmlinuz pfix=fsck psubdir=MyKodi-Puppy64
initrd /MyKodi-Puppy64/initrd.gz
}
menuentry 'MyKodi Puppy64 (no save file)' {
search --set=root --file /MyKodi-Puppy64/vmlinuz
linux /MyKodi-Puppy64/vmlinuz pfix=ram savefile=none psubdir=MyKodi-Puppy64
initrd /MyKodi-Puppy64/initrd.gz
}
## end section MyKodi-Puppy64
## start section chromium
menuentry 'chromium' {
search --set=root --file /chromium/vmlinuz
linux /chromium/vmlinuz pfix=fsck psubdir=chromium
initrd /chromium/initrd.gz
}
menuentry 'chromium (no save file)' {
search --set=root --file /chromium/vmlinuz
linux /chromium/vmlinuz pfix=ram savefile=none psubdir=chromium
initrd /chromium/initrd.gz
}
## end section chromium
So why is it not giving me a choice of drives and partitions to choose from?
So why is it not giving me a choice of drives and partitions to choose from?
Are both kodipup and xenialpup affected?
They are both booting from the Lick menu?
Has a save already been made for each one, placed wherever, and you boot using it?
It's the chromium pup, that I am using.
Could it be the pmedia=satahd causing my problem?
Maybe I should delete pmedia=satahd, let puppy figure it out on it's own.
Have had trouble from a similar puppy, when doing chrome and got no sound, when
it saved the save file on the c: drive.
Now you are talking about a completely different Puppy version?
Sure try pmedia=usbflash or just delete pmedia=
Tried again, and got chromium to give me several partitions to
save to.
But there is a bug in xenialpup64. It doesn't check for thumbnail drives.
Added pmedia=usbflash to the grub.cfg and it doesn't help any.
I'll repeat a slight variation of what I wrote at the beginning of this thread, "The kernel/vmlinuz included in Xenialpup64's ISO may not be new enough/have the instructions and firmware to properly make use of an ssd thumbnail drive".
Recommend you try Bionicpup64 or Fossapup64. I can think of no reason to prefer Xenialpup64 to Bionicpup64, except if Bionicpup64's built-in drivers don't include those which are needed for one's computer's hardware.
It might help if we know EXACTLY which thumbnail drive you have: make and model number. To quote bigpup, "We only know what you tell us."
Using a Lenvo Ideacentre computer.
Using Xenialpup64 because the kernel is smaller.
Ubuntu kernels seem to get while bigger and bigger with
each new version.
Please identify exactly what a "thumbnail drive" is. Is it a small USB flash drive? Is it an SD card that you plug into a slot?
Small usb drive flash drive
I think Lassar is using something like this, https://www.amazon.in/External-Speed-Re ... B07RYLL3QN. The problem is that it is not an 'ordinary' Flash-drive, nor a sata drive. To use it, drivers and firmware different from those other media are needed. As I suggested, xenial may not have the necessary drivers builtin. Frankly, I'm surprised that Lasser was able to boot from it; but having been able to do so I'm even more surprised it isn't recognized as a media on which a SaveFile can be placed.
Now that I've hunted up kodipup, :welcome: https://oldforum.puppylinux. ... fc#p953422 I can appreciate why Lassar wouldn't want to up-grade to bionicpup or fossapup.
There are a couple things he might try:
(1) Don't be two daunted by the size of newer kernel packages, themselves. The difference between Xenialpup's original and even the newest is less than 100 Mbs. To the extent that the contents of the kernel and associated drivers remain in RAM, they've be cached with a ratio of about 1-to-5: that is 1/5 of the space in RAM that was used on Storage. Swapping kernels takes less than 5 minutes. Ask if you need advice as to how to go about it.
(2) Although it may seem inconvenient, Puppys can operate without a SaveFile, storing changes in either an adrv.sfs or a ydrv.sfs or both. These, like xenialpup's zdrv.sfs will be loaded on boot-up. amethyst --formerly known as nic007-- provided a tool, Save2SFS, as part of his nicOS-Utility-Suite, viewtopic.php?p=12983#p12983. You don't have to create a SaveFile to use it. Just download, unpack, then SFS-Load, run the Suite, and choose Save2SFS. It will capture the contents of the changes you have in RAM, just as a Save would. If you had a Save, either an adrv or a ydrv will capture its contents as well. A ydrv will also capture the contents of an adrv and an already existing ydrv. In other words, you could first create a ydrv; then as you add things an adrv; and later choose to update that adrv or incorporate it into a new ydrv.
mikeslr wrote: ↑Tue Nov 16, 2021 12:31 amI think Lassar is using something like this, https://www.amazon.in/External-Speed-Re ... B07RYLL3QN. The problem is that it is not an 'ordinary' Flash-drive, nor a sata drive. To use it, drivers and firmware different from those other media are needed. As I suggested, xenial may not have the necessary drivers builtin.
What evidence do you have to support that statement?
It does have the necessary drivers.
I can access the thumbnail drive, when I click on sbd1.
The problem is with the script that looks for partitions.
It never occurred to the creator of this script, that you might want
to save the file to a thumbnail drive.
What is the name of file, that does this search?
Just to be sure.
This is a drive that plugs into a USB port?
Changing pmedia= to pmedia=usbflash, in the boot loader menu config file entry, should have fixed this.
But there needs to be no save made yet, so when you boot, no save is used.
Shutdown.
When asked to make a save, the drive should now be one of the options.
@ rcrsn51 if by evidence you mean direct evidence, then the answer is None. To have direct evidence I would need to have the EXACT same model of a thumb-drive as Lassar and run multiple tests under xenialpup64 and/or kodipup. But, if you include in your definition of “evidence” circumstantial evidence, a lot.
After finding kodipup, I knew it was a remaster of xenialpup64. Lasser did not write that he had changed Xenialpup64’s default kernel. The last official Xenialpup64 was published in November of 2017 employing the 4.4.95 kernel. I had wrongly assumed that Lassar had based Kodipup on it, and that –not having mentioned it-- he hadn’t changed its kernel. Examination revealed that Kodipup was based on an earlier version of Xenialpup64 and that it employs kernel version "4.9.58 (root@puppypc17434) #1 SMP PREEMPT Mon Nov 13 15:54:01 GMT 2017". Still, a Puppy created in 2017 would not have built-in drivers and firmware for hardware not yet manufactured.
From experience, a frequent reason for posts to Puppys’ Forums is problems with hardware which –after examination- is revealed to be the absence of drivers or firmware. From experience, hardware is manufactured to work with the Windows operating system. From experience, large capacity flash-drives were not prevalent in 2017. I assume they were based on new technological innovations. Researching that assumption revealed (a) it was mostly false, but (b) that not all thumb drives employ the same type of chip nor the same technology to access them.
The foregoing reveals that I was operating under a lot of assumptions, and you know what they say about assumptions. 
Still, in the absence of direct evidence the best we can do is formulate an hypothesis from general experience: to pose a theory to be tested rather than make a statement to be accepted as fact. I accept as a valid criticism your objection to my statement. As I had in my original response on this thread, I should have raised a driver/firmware problem as a possibility.
Lassar had posted that “When I tried to do a save file on xenialpupp64, the thumbnail drive was not even listed.” My original response was that “The kernel/vmlinuz included in Xenialpup64's ISO may not be new enough/have the instructions and firmware” Emphasis not in original.
After correcting the boot-argument per bigpup’s advice, Lassar posted:
Tried to do a reboot, it did not offer to to do a save file. It has offered to resize the personal saved.
Can't figure out where it is saving it to. Looked all over my thumbnail file, and can't find any save file on it". Then he posted, “Puppy linux is always wanting to save the save file to the c: drive. It's not giving me a choice to save to the thumbnail drive...The thumbnail drive is formatted as ntfs.
[From experience, Puppy usually can write to a drive formatted as ntfs. But note, Lasser's Puppy’s system files were written to the thumb-drive by LICK, a program running under Windows].
Lassar has tried both the boot-arguments “pmedia=satahd” and “pmedia=usbflash” without success. Ordinarily, Puppys know how to respond to either.
Lassar wrote, “xenialpup64. It doesn't check for thumbnail drives”. [I know from experience that xenialpup64 can both boot from and create a SaveFile on an ‘ordinary’ flash-drive, even one Formatted as ntfs].
You’re the expert. But –especially when Windows can write to media and Linux can not-- to me that suggests a driver/firmware problem.
One possible way to test that hypothesis would be to try a Puppy with a different kernel, or a Kodipup employing a different kernel. Perhaps too forcefully, that’s what I suggested.
What evidence do you have that it’s not a driver/firmware problem?
@ Lassar, exactly which Thumbnail drive do you have: Make, model and if possible specifications.
It's SanDisk 16 gigabyte thumbnail drive.
It's formatted as ntfs.
Was noticing that every partition is remounted, but does not remount & check the sdb1 flash drive.
Like I said, the sdd1 flash drive is accessable from puppy linux.
Wish I knew, which sh file does this.
If I did, I could find out, what the problem is, and fix it.
@Lassar: I cannot tell from this discussion where your installs are located. You are mixing Windows drive letters with Linux partition names.
Are you booting off a hard drive install, then trying to put your save file/folder on the flash drive?
It may be that some Puppies are not coded to allow that.
Used pfind file finder and located the file.
It's /usr/sbin/shutdownconfig
Since I am using pmedia=usbflash, it means the logic in this sh file is not right.
Code: Select all
#!/bin/sh
#(c) Copyright Barry Kauler sept. 2011 bkhome.org
#2011 GPL licence v3 (/usr/share/doc/legal)
#the idea of this script is that it is called when PUPMODE==5 by scripts
#/usr/bin/wmreboot and /usr/bin/wmpoweroff (which are called via the Shutdown menu).
#X is still running.
#the normal shutdown sequence is:
# /usr/bin/wmpoweroff ->(return to) /usr/bin/xwin -> /sbin/poweroff -> /etc/rc.d/rc.shutdown
# /usr/bin/wmreboot ->(return to) /usr/bin/xwin -> /sbin/reboot -> /etc/rc.d/rc.shutdown
#this script is putting up some GUI dialogs while X is still running, so when
#rc.shutdown is reached, it won't have to put up text-mode dialogs.
#to avoid code duplication, get this to work with and without X, and also call this
#script from rc.shutdown. From the console, no X, type "poweroff" or "reboot" will
#also (conditionally) run this script, via rc.shutdown.
#110924 various tweaks. fix default partition highlight.
#111012 a pupdialog window had wrong text, needed different from non-X dialog.
#120327 only show "*RECOMMENDED*" partition for savefile if >256MB free.
#120327 expBOOTDRV needs to be exported to rc.shutdown.
#120427 01micko: support ext4 in save-file. 120428
#120512 Karl Godt: some parameters missing from lines 626, 630, 642.
#120514 Karl Godt: precaution, save-file must be bigger than size used in ram.
#130128 support udf f.s. (see also sfsget, puppyinstaller, pmount, pup_event_frontend_d, drive_all, probepart).
#130216 support f2fs.
#130221 the 240 sec timeout to shutdown without saving, actually aborts timeout. fixed. see also pupdialog, wmpoweroff, wmreboot.
#130525 extend duration of creating save file please wait window.
#130712 fix 130522, 130525 dlgs showing in tray.
export SHUTDOWNCONFIG=1
DEFAULT_SAVE_SIZE=512 #MB
TIMELIMIT=$(echo $TIMELIMIT | tr -dc '0-9')
[ "$TIMELIMIT" ] || TIMELIMIT=60
if [ ! $DISPLAY ];then
export LANG=C #110928 console shutdown using 'dialog', disable i18n.
else
export OUTPUT_CHARSET=UTF-8
fi
. gettext.sh # enables use of eval_gettext (several named variables) and ngettext (plurals)
export TEXTDOMAIN=shutdownconfig
T_title="$(gettext 'First shutdown: save session')" # used 8 times
T_nosave="$(gettext 'No suitable partitions to save to. Shutting down without saving.')"
T_continue="$(gettext 'Continue')"
T_abort="$(gettext 'Abort')"
T_no="$(gettext 'No')"
T_notsave="$(gettext 'DO NOT SAVE')"
#/etc/rc.d/rc.shutdown will call shutdownconfig if this file does not exist, then will read its contents...
echo -n "" > /tmp/shutdownconfig_results
. /etc/rc.d/PUPSTATE
. /etc/DISTRO_SPECS
#puppy.sfs is in a subdirectory, default to saving in it...
PUPSFSFILE="`echo "$PUPSFS" | cut -f 3 -d ','`"
PSUBDIR="`dirname "$PUPSFSFILE"`"
[ "$PSUBDIR" = "/" ] && PSUBDIR=""
[ $PUPMODE -eq 5 ] && [ "$DEV1FS" = "iso9660" ] && PSUBDIR="" #100920 booting off cd, always default have savefile at /.
[ $PUPMODE -eq 5 ] && [ "$DEV1FS" = "udf" ] && PSUBDIR="" #130128 ditto, for udf f.s.
[ "$DEV1FS" = "msdos" ] && DEV1FS="vfat"
if [ $DISPLAY ];then
export XDIALOG_HIGH_DIALOG_COMPAT=true #for Xdialog.
DIALOGEXE="pupdialog"
DIALOGEXE2="Xdialog"
BACKGROUNDYELLOW='--background \#FFFF80' #110924 change to pale-yellow. yellow' #only works pupdialog.
BACKGROUNDPINK='--background pink' #ditto.
BACKGROUNDORANGE='--background \#FFDC32' #110924 change to pale-orange. orange' #ditto.
TITLEPARAM='--backtitle'
else
DIALOGEXE="dialog"
DIALOGEXE2="dialog"
TITLEPARAM='--title'
BACKGROUNDYELLOW=''
BACKGROUNDPINK=''
BACKGROUNDORANGE=''
fi
#120514 Karl Godt: precaution, save-file must be at least this big...
DU_INITRD_PUP_RW=0
[ "`mount | grep ' /initrd/pup_rw '`" != "" ] && DU_INITRD_PUP_RW=`du -B 1M -c /initrd/pup_rw |tail -n1 |awk '{print $1}'` #M=1024,MB=1000
#130525 introduced 130522. moved up.
ORANGEGTKRC="style \"windowstuff\"
{
bg[NORMAL] = \"#FFDC32\"
fg[NORMAL] = \"#000000\"
}
class \"*\" style \"windowstuff\"
"
echo "$ORANGEGTKRC" > /tmp/orange_gtkrc${$}
#================================================================
offerfido() {
#offering non-root, ###PENDING### for now
T_admin="$(gettext 'administrator')"
T_fidomsg="`eval_gettext \"fido CURRENTLY EXPERIMENTAL STATUS, PLEASE CHOOSE \\\${T_admin}\"`"
FIDOMSG2="\Zb\Z1${T_fidomsg}\Zn\ZB" #110926
T_fidotitle="$(gettext 'First shutdown: ask fido')"
T_yesno="$(eval_gettext "You are currently running Puppy as the \${T_admin} (also known as 'root') which is the preferred choice. However, for the paranoid, you may run Puppy as a less-privileged user 'fido'. Puppy boots up without requiring a password, whether as \${T_admin} or fido, but the latter will require jumping to \${T_admin} to perform some system-level tasks, which will require entry of the admin password -- this is viewed by many as an unnecessary hassle.")
$(eval_gettext "Puppy is structured in such a way that we consider running as \${T_admin} to be completely safe, and is the choice of most users, however fido is theoretically more secure.")
$(gettext "Note that Puppy only has one non-admin user, fido, as it is not a multi-user system in the normal sense -- instead, each person using Puppy on the same computer can have their own save-file (each one set to root or fido as the users wish).")
$(eval_gettext "Note also, the LoginManager (System menu) enables you to switch back to \${T_admin} if you decide later that you don't want to run as fido.")
${FIDOMSG2}"
#offer to save non-root...
${DIALOGEXE} ${BACKGROUNDYELLOW} ${TITLEPARAM} "$T_fidotitle" --colors --yes-label "$T_admin" --no-label "fido" --yesno "$T_yesno" 0 0
SAVECHOICE=$?
[ $SAVECHOICE -eq 1 ] && /usr/sbin/root2user
}
choosepartfunc() {
offerfido
#dialog to choose what partition to create ${DISTRO_FILE_PREFIX}save.2fs on...
case "$PMEDIA" in ""|cd|scsicd|satacd|idecd|atacd|usbcd) PCHOOSE="yes" ;; esac
case "$DEV1FS" in ntfs|xxx) PCHOOSE="yes" ;; esac
[ "$DEV1FS" = "msdos" ] && DEV1FS="vfat"
expBOOTDRV=''
if [ "$PMEDIA" = "usbflash" ];then #may have a small boot partition and a big 2nd.
expBOOTDRV="/dev/`echo ${PDEV1} | sed -e 's%[0-9]*$%%'`"
PCHOOSE="yes"
fi
if [ "$xPSUBDIR" -a "$PMEDIA" != "cd" ];then #if pup installed in a sub-directory, allow save-file in another partition (in same drive)...
expBOOTDRV="/dev/`echo ${PDEV1} | sed -e 's%[0-9]*$%%'`"
PCHOOSE="yes"
fi
if [ "$PSAVEMARK" != "" ];then #see /etc/rc.d/PUPSTATE
devnameonly="`echo -n "$PDEV1" | sed -e 's/[0-9]*$//'`"
SAVEPART="${devnameonly}${PSAVEMARK}" #partition that will-have ${DISTRO_FILE_PREFIX}save.
fi
if [ "$PSAVEPART" != "" ];then #see /etc/rc.d/PUPSTATE
SAVEPART="${PSAVEPART}"
fi
if [ "$SAVEPART" != "" ];then
spPATTERN='/dev/'"$SAVEPART"'|'
SAVEFS="`probepart -m | grep "$spPATTERN" | cut -f 2 -d '|'`"
SAVEFILE="$PSUBDIR/${DISTRO_FILE_PREFIX}save.2fs"
PUPSAVE="$SAVEPART,$SAVEFS,$SAVEFILE"
return 0
fi
if [ "$PCHOOSE" != "yes" ];then
SAVEFS="$DEV1FS"
SAVEPART="$PDEV1"
SAVEFILE="$PSUBDIR/${DISTRO_FILE_PREFIX}save.2fs"
PUPSAVE="$PDEV1,$DEV1FS,$SAVEFILE"
return 0
fi
if [ "$expBOOTDRV" = "" ];then
T_fidotitle="$(gettext 'First shutdown: get ready')"
T_yesno1="$(eval_gettext "WARNING: If you want to create a save-file (\${DISTRO_FILE_PREFIX}save.2fs) in a NTFS partition (Windows XP), it is strongly recommended that you defragment the partition first.")
$(eval_gettext 'Choose \Zb${T_abort}\ZB button to abort this save, start Windows and choose Start->All Programs->Accessories->System Tools->Defragment.')"
T_yesno2="$(gettext 'Make sure any required USB, floppy, etc. is PLUGGED IN NOW!')"
T_yesno3="$(eval_gettext 'Choose \Zb${T_continue}\ZB button to search available storage...')"
T_yesno="\Z1${T_yesno1}\Zn\n\n\Z5${T_yesno2}\Zn\n\n${T_yesno3}" #111003
case $DEV1FS in
iso9660|udf)
T_iso="`eval_gettext \"You have booted off a live-CD or DVD, and you can now save your personal settings and files to a USB Flash drive or any hard drive partition.
However, if you have burnt the CD/DVD as multisession (not closed), then sessions can be saved as additional tracks to the CD/DVD -- each saved session will appear on the CD/DVD as a directory with all the saved files in it, not as a single file. \Zb\Z1THIS IS STILL EXPERIMENTAL, AND DOES NOT WORK WITH LAPTOP OPTICAL DRIVES\Zn\ZB\"`"
T_yesno="$T_iso\n\n$T_yesno
$(eval_gettext "or \Zb${T_cd}\ZB button to save your session back to the CD/DVD..." )"
${DIALOGEXE} ${BACKGROUNDYELLOW} ${TITLEPARAM} "$T_fidotitle" --colors --extra-button --ok-label "$T_continue" --extra-label "$T_cd" --cancel-label "$T_abort" --yesno "$T_yesno" 0 0
SAVECHOICE=$?
[ "$SAVECHOICE" == "3" ] && PUPMODE=77 && SAVEPART="$PDEV1" && return 1 #save to cd/dvd.
[ ! $SAVECHOICE -eq 0 ] && return 3 #skip.
;;
*)
${DIALOGEXE} ${BACKGROUNDYELLOW} ${TITLEPARAM} "$T_fidotitle" --colors --yes-label "$T_continue" --no-label "$T_abort" --yesno "$T_yesno" 0 0
SAVECHOICE=$?
[ ! $SAVECHOICE -eq 0 ] && return 1 #abort.
;;
esac
fi
#130216 add f2fs...
PARTSLIST="`probepart -m 2> /dev/null | grep '^/dev/' | grep "$expBOOTDRV" | grep -E 'f2fs|ext2|ext3|ext4|reiserfs|btrfs|minix|msdos|vfat|exfat|ntfs' | cut -f 1-3 -d '|' | sed -e 's/msdos/vfat/g'`"
#nothing to save to...
if [ "$PARTSLIST" = "" ];then
if [ $DISPLAY ];then
/usr/lib/gtkdialog/box_splash -bg red -close box -fontsize large -timeout 10 -text "$T_nosave"
else
clear
echo "T_nosave"
sleep 5
fi
return 1
fi
T_waitprobing="$(gettext 'Please wait, probing partitions...')"
if [ "$DISPLAY" ]; then
/usr/lib/gtkdialog/box_splash -close never -fontsize large -text "$T_waitprobing" &
ppPID=$!
fi
SCHOICES=""; DEFTAG=""
rm -f /tmp/schoices.txt
rm -f /tmp/shutdownconfig_deftag
echo "$PARTSLIST" | grep -qw "$PDEV1" && INSTALLED="y" || INSTALLED=""
echo "$PARTSLIST" |
while read APART
do
ATAG="`echo -n "$APART" | cut -f 1 -d '|' | cut -f 3 -d '/'`"
ASIZE="`echo -n "$APART" | cut -f 3 -d '|'`"
AFS="`echo -n "$APART" | cut -f 2 -d '|'`"
AFREE=`df -m | grep "/dev/${ATAG} " | tr -s " " | cut -f 4 -d " "`
if [ ! $AFREE ];then
mount -t $AFS /dev/$ATAG /mnt/data > /dev/null 2>&1
#need to put in a check that it is not mounted ro. the
#mount script will fallback to ro for ntfs if rw mnt fails...
RETMNTVAL=$?
if [ $RETMNTVAL -eq 0 ];then
if [ "`mount | grep '(rw' | grep '/mnt/data'`" = "" ];then
umount /mnt/data
RETMNTVAL=1
else
#if the ntfs rw mount was forced (see /bin/mount script) it is unwise to use...
ERRMSG1=""
[ -s /tmp/ntfsmnterr.txt ] && ERRMSG1="`cat /tmp/ntfsmnterr.txt | grep 'Dirty volume mount'`"
if [ "$ERRMSG1" != "" ];then
T_ntfstitle="$(gettext 'First shutdown: NTFS warning')"
T_WARNING="\Z1\Zb$(gettext 'WARNING:')\ZB"
T_ntfs="$(eval_gettext "The ntfs-3g driver has determined that the NTFS filesystem in partition \${ATAG} is 'dirty'.")
$(gettext 'It will display in the next dialog box in the list of partitions to save to, but it is recommended that you do not use it.')
$(gettext "Instead, you should first run Microsoft Windows -- most often this problem is due to Windows not being shut down properly the last time it was used, leaving the filesystem in a 'dirty' state.")"
T_continue="$(gettext 'Click button to continue...')"
${DIALOGEXE} ${BACKGROUNDPINK} ${TITLEPARAM} "$T_ntfstitle" --colors --msgbox "${T_WARNING}\n${T_ntfs}\Zn\n\n${T_continue}" 0 0
fi
fi
fi
[ -f /tmp/ntfsmnterr.txt ] && rm -f /tmp/ntfsmnterr.txt
if [ $RETMNTVAL -eq 0 ];then
if [ "$ATAG" = "fd0" ];then
FFREE=`df -k | grep "/dev/$ATAG" | tr -s " " | cut -f 4 -d " "`
AFREE=`dc $FFREE 1000 \/ p` #not 1024
else
#for ntfs cannot use /dev/$ATAG, use mnt point in grep...
AFREE=`df -m | grep "/mnt/data" | tr -s " " | cut -f 4 -d " "`
fi
umount /mnt/data
fi
fi
if [ $AFREE -ne 0 ];then
if [ -z "$INSTALLED" ] && [ $AFREE -gt 512 ] && [ ! -s /tmp/shutdownconfig_deftag ];then
case $AFS in
ext?|reiserfs|minix|btrfs|f2fs) echo -n " --default-item ${ATAG}" > /tmp/shutdownconfig_deftag;;
esac
fi
if [ "$ATAG" = "$PDEV1" -a $AFREE -gt 256 ];then #120327
echo -n " --default-item ${ATAG}" > /tmp/shutdownconfig_deftag
echo "${ATAG} \"f.s.: $AFS `gettext 'Size:'` ${ASIZE}M `gettext 'Free:'` ${AFREE}M `gettext '*RECOMMENDED*'`\" " >> /tmp/schoices.txt
else
echo "${ATAG} \"`gettext 'Filesystem:'` $AFS `gettext 'Size:'` ${ASIZE}M `gettext 'Free:'` ${AFREE}M\" " >> /tmp/schoices.txt
fi
fi
done
kill $ppPID
[ -s /tmp/shutdownconfig_deftag ] && DEFTAG="`cat /tmp/shutdownconfig_deftag`"
[ -s /tmp/schoices.txt ] && SCHOICES="`cat /tmp/schoices.txt`"
if [ "$SCHOICES" = "" ];then
if [ $DISPLAY ];then
/usr/lib/gtkdialog/box_splash -bg red -close box -fontsize large -timeout 10 -text "$T_nosave"
else
clear
echo "$T_nosave"
sleep 5
fi
return 1
fi
xSCHOICES="`cat /tmp/schoices.txt | tr '\n' ' '`"
if [ `echo "$SCHOICES" | wc -l` -eq 1 ];then
SAVEPART="`echo -n "$SCHOICES" | cut -f 1 -d ' '`" #no need for dlg.
else
T_partitiontitle="$(gettext 'First shutdown: choose partition')"
T_menu="$(gettext 'Please choose a partition to create a pupsave on.')
$(gettext 'For Windows partitions(ntfs/vfat), Puppy makes a file with a Linux filesystem image in it. The size is typically 512MB - 4GB (it can be made bigger later).')
$(gettext 'On linux partitions(ext3 and etc.), Puppy makes a folder for pupsave. Unlike single file, the size is not predetermined but limited by the free space of the partition. A Linux partition is recommended, if available.')
$(gettext 'Highlight desired choice, then click OK button...')"
echo '#!/bin/sh' > /tmp/savedlg
echo -n "${DIALOGEXE} ${BACKGROUNDYELLOW} ${TITLEPARAM} \"${T_partitiontitle}\" --no-collapse --no-cancel ${DEFTAG} --menu \"${T_menu}\" 0 0 0 " >> /tmp/savedlg
echo -n "$xSCHOICES" >> /tmp/savedlg
echo ' 2>/tmp/tag.txt' >> /tmp/savedlg
chmod 755 /tmp/savedlg
#seems some people have problem, do not select anything...
T_notchosentitle="$(gettext 'First shutdown: Not chosen')"
T_tryagain="$(gettext 'Try again')"
T_yesno="$(gettext '\Zb\Z1ERROR:\Zn\ZB you did not choose any partition.')
$(eval_gettext 'Choose \Zb${T_tryagain}\ZB button to try again...')
$(eval_gettext 'Or, \Zb${T_abort}\ZB to shutdown without saving...')"
while [ 1 ];do
/tmp/savedlg
SAVEPART="`cat /tmp/tag.txt | head -n 1`" #head is in case of errs in output.
if [ "`echo -n "$SAVEPART" | grep --extended-regexp '^hd|^sd|^sc|^fd|^mmcblk'`" = "" ];then
${DIALOGEXE} ${BACKGROUNDPINK} ${TITLEPARAM} "$T_notchosentitle" --colors --yes-label "$T_tryagain" --no-label "${T_abort}" --yesno "$T_yesno" 0 0
[ ! $? -eq 0 ] && return 1 #abort.
continue
fi
break
done
fi
SAVEFS="`echo "$SCHOICES" | grep "^${SAVEPART} " | tr -s " " | cut -f 2 -d ':' | cut -f 2 -d " "`"
SAVEFILE="$PSUBDIR/${DISTRO_FILE_PREFIX}save.2fs"
[ "$SAVEPART" = "fd0" ] && SAVEFILE="/${DISTRO_FILE_PREFIX}save.2fs"
PUPSAVE="$SAVEPART,$SAVEFS,$SAVEFILE"
echo "$PUPSAVE" #TEST
return 0
} #end choosepartfunc
choosesizefunc(){
local KFREE SIZELIST NUM CHOICES FLABEL SLABEL ACHOICE KSIZE VALUES VALIDS val
KFREE=$1 ; SIZELIST="" ; NUM=1 ; CHOICES=""
MFREE=`expr $KFREE \/ 1024`
FLABEL="${MFREE}MB"
[ $KFREE -ge 1048576 ] && FLABEL="`dc $KFREE 1048576 \/ p`GB"
VALUES='32 64 128 256 512 768 1024 1280 2048 4096'
for val in $VALUES;do
[ "$val" -gt "$DU_INITRD_PUP_RW" ] && VALIDS="$VALIDS $val"
done
#global: DEFAULT_SAVE_SIZE in MB
[ $DEFAULT_SAVE_SIZE -gt 0 ] || DEFAULT_SAVE_SIZE=512
local NDEFAULT=1
for ACHOICE in $VALIDS
do
[ $ACHOICE -le $DEFAULT_SAVE_SIZE ] && NDEFAULT=$NUM
KSIZE=`expr $ACHOICE \* 1024`
SLABEL="${ACHOICE}MB"
[ $ACHOICE -ge 1024 ] && SLABEL="`dc $ACHOICE 1024 \/ p`GB"
if [ $KSIZE -lt $KFREE ];then
SIZELIST="$SIZELIST$NUM $SLABEL "
CHOICES="$CHOICES$KSIZE "
else
SIZELIST="$SIZELIST$NUM fill_partition(${FLABEL}) "
CHOICES="$CHOICES$KFREE "
break
fi
NUM=`expr $NUM + 1`
done
T_sizetitle="$(gettext 'First shutdown: size save-file')"
T_sitemenu="$(gettext 'Please choose the size you would like for the personal save file.')
$(gettext 'Note, 512M is a good choice, or highest if that not available.')
$(gettext 'Select choice, then click OK button...')"
${DIALOGEXE} ${BACKGROUNDYELLOW} ${TITLEPARAM} "$T_sizetitle" --no-collapse --no-cancel --default-item "$NDEFAULT" --menu "$T_sitemenu" 0 0 0 $SIZELIST 2>/tmp/sizetag.txt
NUM=`cat /tmp/sizetag.txt`
ACHOICE=`echo -n "$CHOICES" | cut -f $NUM -d ' '`
#return $ACHOICE
SIZEPFILE=$ACHOICE #global variable.
} # end of choosesizefunc()
choosestyle() {
#do not allow save to entire partition if pup installed in a subdirectory...
#xPSUBDIR="`echo -n "$PUPSFS" | cut -f 3 -d ',' | sed -e 's%/[^/]*$%%'`" #ex: sda3,ext2,/pup220/puppy.sfs will return /pup220
[ "$SAVEPART" = "$PDEV1" ] && [ -z "$xPSUBDIR" ] && OFFER_PARTITION="y" || OFFER_PARTITION=""
T_fstitle="$(gettext 'First shutdown: choose saving style')"
T_fsmenu="$(gettext "You can save the session in a 'folder(directory)' because you chose a Linux partition. Unlike single file, saving in a folder is not restricted to the fixed file size but by the free space on the partition. You can save multiple profiles by different name.")
$(gettext "A \Zbfolder\ZB is recommended for this case, but you still have another option if you have some reason and you want it.")"
T_folder="$(gettext 'Save in a folder.') $(gettext '*RECOMMENDED*')"
T_partition=$(gettext "Save to the entire partition. Only one profile.")
T_file=$(gettext 'Single file, ext2/3/4 filesystem image in it.')
if [ "$OFFER_PARTITION" ]; then
${DIALOGEXE} ${BACKGROUNDYELLOW} ${TITLEPARAM} "$T_fstitle" --colors --no-cancel --default-item folder --menu "$T_fsmenu" 0 0 0 folder "$T_folder" partition "$T_partition" file "$T_file" 2>/tmp/rc.shutdown_pupsave_style
else
${DIALOGEXE} ${BACKGROUNDYELLOW} ${TITLEPARAM} "$T_fstitle" --colors --no-cancel --default-item folder --menu "$T_fsmenu" 0 0 0 folder "$T_folder" file "$T_file" 2>/tmp/rc.shutdown_pupsave_style
fi
SAVESTYLE=$(cat /tmp/rc.shutdown_pupsave_style)
[ "$SAVESTYLE" ]
}
choosesize() {
#we should check to see that there is enough space on the partition...
PARTFREE=`df | grep "$SMNTPT" | tr -s " " | head -n 1 | cut -f 4 -d " "`
[ ! $PARTFREE ] && PARTFREE=0
[ $PARTFREE -lt 32768 ] && PARTFREE=`expr $PARTFREE - 1024` #leave some slack space.
[ $PARTFREE -gt 32768 ] && PARTFREE=`expr $PARTFREE - 8192` #leave some slack space.
SIZEPFILE=524288 #512M = 524288K
[ $SIZEPFILE -gt $PARTFREE ] && SIZEPFILE=$PARTFREE
[ $PARTFREE -gt 32768 ] && choosesizefunc $PARTFREE #sets SIZEPFILE
if [ "`echo -n $SAVEFILE | grep '\.[34]fs$'`" != "" ];then #ext3 f.s. needs minimum size.
[ $SIZEPFILE -lt 5000 ] && return 1 #precaution. rerwin discovered this.
fi
}
choosefs(){
#choose f.s. of save-file... 100410 for now, leave out ext4, doesn't work...
T_fstitle="$(gettext 'First shutdown: choose filesystem')"
T_fsmenu="$(gettext 'Previously, Puppy has only used 'ext2', now there is a choice. Regarding power-failure, note that Puppy will do a f.s. check at next boot so ext2 can recover, however journalled filesystems can recover even without a f.s. check. If in doubt, choose 'ext2'. After making the choice, click OK button...')"
T_ext2="$(gettext 'Maximum storage space, encrypted save-file must use ext2')"
T_ext3="$(gettext 'Journalled f.s., safest if power failure etc.')"
#120427 01micko: support ext4...
T_ext4="$(gettext 'Journalled f.s., safest if power failure etc.')"
if [ "`grep 'ext4$' /proc/filesystems`" != "" ];then #120428 technosaurus: simplify test.
${DIALOGEXE} ${BACKGROUNDYELLOW} ${TITLEPARAM} "$T_fstitle" --no-cancel --default-item ext4 --menu "$T_fsmenu" 0 0 0 ext2 "$T_ext2" ext3 "$T_ext3" ext4 "$T_ext4" 2>/tmp/rc.shutdown_pupsave_fs #120425 01micko
else
${DIALOGEXE} ${BACKGROUNDYELLOW} ${TITLEPARAM} "$T_fstitle" --no-cancel --default-item ext3 --menu "$T_fsmenu" 0 0 0 ext2 "$T_ext2" ext3 "$T_ext3" 2>/tmp/rc.shutdown_pupsave_fs #110926
fi
SFFS="`cat /tmp/rc.shutdown_pupsave_fs`"
[ "$SFFS" = "" ] && SFFS='ext2'
SFEXTNUM="`echo -n "$SFFS" | cut -c 4`"
SFEXT="${SFEXTNUM}fs" #ex: 2fs
}
choosename() {
#customise the name of the ${DISTRO_FILE_PREFIX}save file...
T_nametitle="$(gettext 'First shutdown: pupsave name')"
T_nameinput="$(eval_gettext "Would you like to customise the name of the '\${DISTRO_FILE_PREFIX}save'?")
$(eval_gettext "This is optional, but it is convenient to manage multiple profiles. If you have lots of '\${DISTRO_FILE_PREFIX}save' and you want to choose the right one at startup.")
$(eval_gettext "For example, if you enter 'john' here, the file will become '\${DISTRO_FILE_PREFIX}save-john'.")
$(gettext 'Type any alpha-numeric characters you wish, then click OK button:')"
MYUSERNAME="`${DIALOGEXE} ${BACKGROUNDYELLOW} ${TITLEPARAM} "$T_nametitle" --stdout --nocancel --inputbox "$T_nameinput" 0 0 ""`"
NAMEONLY="${DISTRO_FILE_PREFIX}save${CRYPT_NAME}"
if [ "$MYUSERNAME" != "" ];then
MYUSERNAME="`echo -n "$MYUSERNAME" | tr ' ' '_' | tr '-' '_' | sed -e 's/[^a-zA-Z0-9_.]//g'`"
NAMEONLY="$NAMEONLY-${MYUSERNAME}"
fi
}
choosecrypt_new() {
CRYPTO=""
T_cryptotitle="$(gettext 'First shutdown: encryption')"
T_cryptono="$(gettext 'NORMAL (no encryp.)')"
T_cryptoheavy="$(gettext 'Encrypt with LUKS')"
T_yesno="$(eval_gettext "Do you want to encrypt the '\${DISTRO_FILE_PREFIX}save'?")
$(eval_gettext "If the '\${DISTRO_FILE_PREFIX}save' is encrypted, then a password will have to be entered at every bootup. The reason for doing this is security, as no one else will be able to see what is inside the \${DISTRO_FILE_PREFIX}save. Encryption does slow \${DISTRO_NAME} down.")
LUKS = Linux Unified Key Setup.
$(eval_gettext "Encrypted \${DISTRO_FILE_PREFIX}save files have another advantage, they allow multiple users. Recommended if spouse and kids are going to be using the same \${DISTRO_NAME} installation.")
$(gettext 'Unless you have a good reason to use encryption, it is recommended not to, to avoid the overhead. Recommend choose \ZbNORMAL\ZB button...')"
${DIALOGEXE} ${BACKGROUNDYELLOW} ${TITLEPARAM} "$T_cryptotitle" --colors --ok-label "$T_cryptono" --cancel-label "$T_cryptoheavy" --yesno "$T_yesno" 0 0 #110926
RETVAL=$?
if [ $RETVAL -eq 1 ];then
T_passtitle="$(gettext 'First shutdown: password')"
T_passtext="$(gettext 'Please choose a password.
This must be remembered and entered at every bootup.')"
while [ 1 ];do
if [ "$DISPLAY" ] ; then
MYPASSWORD="$(/usr/lib/gtkdialog/box_passwd --show --default "puppyisgreat" "$T_passtitle" "$T_passtext")"
else
MYPASSWORD="`${DIALOGEXE} ${BACKGROUNDYELLOW} ${TITLEPARAM} "$T_passtitle" --screen-center --stdout --no-cancel --inputbox "$T_passtext" 0 0 "puppyisgreat"`" #110926
fi
[ "$MYPASSWORD" ] && break
done
DENSITY="z"
CRYPTO='luks'
CRYPT_NAME="_luks"
SFEXT="4fs"
SFFS="ext4"
fi
}
choosecrypt() {
CRYPTO=""
T_cryptotitle="$(gettext 'First shutdown: encryption')"
T_cryptono="$(gettext 'NORMAL (no encryp.)')"
T_cryptoheavy="$(gettext 'Heavy encrypted')"
T_cryptolight="$(gettext 'Light encrypted')"
T_yesno="$(eval_gettext "Do you want to encrypt the '\${DISTRO_FILE_PREFIX}save'?")
$(eval_gettext "If the '\${DISTRO_FILE_PREFIX}save' is encrypted, then a password will have to be entered at every bootup. The reason for doing this is security, as no one else will be able to see what is inside the \${DISTRO_FILE_PREFIX}save. Encryption does slow \${DISTRO_NAME} down slightly, the 'heavy' encryption the most. Two scenarios:")
\Zb$(gettext '1.')\ZB $(eval_gettext "If the \${DISTRO_FILE_PREFIX}save file is on a Flash drive, encryption is protection in case the drive is mislaid. Heavy encryption is recommended, as \${DISTRO_NAME} minimises writes to the save file (to prolong life of the Flash drive, but this also minimises encryption slowdown).")
\Zb$(gettext '2.')\ZB $(eval_gettext "If the \${DISTRO_FILE_PREFIX}save file is on a hard drive, 'light' encryption is recommended to minimise slowdown, particularly on older PCs.")
$(eval_gettext "Encrypted \${DISTRO_FILE_PREFIX}save files have another advantage, they allow multiple users. Recommended if spouse and kids are going to be using the same \${DISTRO_NAME} installation.")
$(gettext 'Unless you have a good reason to use encryption, it is recommended not to, to avoid the overhead. Recommend choose \ZbNORMAL\ZB button...')"
${DIALOGEXE} ${BACKGROUNDYELLOW} ${TITLEPARAM} "$T_cryptotitle" --colors --extra-button --ok-label "$T_cryptono" --cancel-label "$T_cryptoheavy" --extra-label "$T_cryptolight" --yesno "$T_yesno" 0 0 #110926
RETVAL=$?
if [ $RETVAL -eq 1 -o $RETVAL -eq 3 ];then
T_passtitle="$(gettext 'First shutdown: password')"
T_passtext="$(gettext 'Please choose a password.
This must be remembered and entered at every bootup.')"
while [ 1 ];do
if [ "$DISPLAY" ] ; then
MYPASSWORD="$(/usr/lib/gtkdialog/box_passwd --show --default "puppyisgreat" "$T_passtitle" "$T_passtext")"
else
MYPASSWORD="`${DIALOGEXE} ${BACKGROUNDYELLOW} ${TITLEPARAM} "$T_passtitle" --screen-center --stdout --no-cancel --inputbox "$T_passtext" 0 0 "puppyisgreat"`" #110926
fi
[ "$MYPASSWORD" ] && break
done
modprobe cryptoloop
if [ $RETVAL -eq 1 ];then
DENSITY="a" #heavy aes encryption
CRYPTO='-e aes'
modprobe aes_generic 2>/dev/null #builtin my recent kernels.
#did not explicitly load these two before, but do so in init script...
modprobe crypto_blkcipher 2>/dev/null #builtin my recent kernels.
modprobe cbc 2>/dev/null #110926 builtin in my 2.6.32-smp-45 kernel.
else
DENSITY="x" #light xor encryption.
CRYPTO='-e 1' #'-e xor' --bug, loads xor.ko which is something else.
fi
CRYPT_NAME="_crypt${DENSITY}"
SFEXT="2fs"
SFFS="ext2"
fi
}
nameclash() {
#save with different name if clash...
[ ! -e $SMNTPT$SAVEFILE ] && return 0
NAMEONLY=$(basename "$SAVEFILE")
NAMEROOT=${NAMEONLY%.*}
MNAMEONLY=$NAMEROOT
T_clashtitle="$(gettext 'First shutdown: name clash')"
T_save="$(gettext 'SAVE')"
T_yesno="$(eval_gettext "There already exists '\${NAMEONLY}' on the partition you chose.")
$(eval_gettext 'To create another one, with a slightly different name (such as ${MNAMEONLY}-1.${SFEXT}), select \Zb${T_save}\ZB button...')
$(eval_gettext 'To quit without saving, select \Zb${T_no}\ZB button...')"
${DIALOGEXE} ${BACKGROUNDPINK} ${TITLEPARAM} "$T_clashtitle" --colors --yes-label "$T_save" --yesno "$T_yesno" 0 0
[ ! $? -eq 0 ] && return 1
local BLA=1 #; local SFFIX=`echo "$SAVEFILE" | tail -c 5`
while [ -e $SMNTPT$SAVEFILE ]; do
SAVEFILE="$PSUBDIR/${NAMEROOT}-${BLA}"
[ "${SFEXT}" ] && SAVEFILE="$SAVEFILE.${SFEXT}"
BLA=`expr $BLA + 1`
done
}
enmount() {
sPTN="/dev/${SAVEPART} "
SMNTPT="`mount | grep "$sPTN" | head -n1 | tr -s " " | cut -f 3 -d " "`"
#ntfs uses /dev/fuse so '/dev/$SAVEPART' no good for grep... NOTE: this fixed later versions ntfs-3g, so this line actually redundant...
[ "$SMNTPT" = "" ] && SMNTPT="`ps -e | grep -o 'ntfs\-3g.*' | grep "$sPTN" | tr '\t' ' ' | tr -s ' ' | tr ' ' "\n" | grep '^/mnt/'`"
if [ "$SMNTPT" = "" ];then
mkdir /mnt/$SAVEPART 2>/dev/null
mount -t $SAVEFS /dev/$SAVEPART /mnt/$SAVEPART
SMNTPT="/mnt/$SAVEPART"
fi
return 0
}
changefolder() {
T_choosefoldertitle="$(gettext 'First shutdown: choose folder')"
T_inputbox="$(gettext 'Edit path. '/' means top-level of partition.
You are only allowed to save one-deep, for example: '/puppy300'.
If folder does not exist, it will be created. Spaces are not allowed.
If uncertain, just click OK button.')"
NEWSAVEPATH="`${DIALOGEXE} ${BACKGROUNDYELLOW} ${TITLEPARAM} "$T_choosefoldertitle" --screen-center --stdout --no-cancel --inputbox "$T_inputbox" 0 0 "$SAVEPATH"`"
[ "$NEWSAVEPATH" = "" ] && NEWSAVEPATH="$SAVEPATH"
[ "`echo -n "$NEWSAVEPATH" | cut -b 1`" != "/" ] && NEWSAVEPATH="/${NEWSAVEPATH}"
[ "$NEWSAVEPATH" != "/" ] && NEWSAVEPATH="`echo -n "$NEWSAVEPATH" | sed -e 's%/$%%'`"
NEWSAVEPATH="`echo -n "$NEWSAVEPATH" | sed -e 's/ //g'`"
SAVEPATH="$NEWSAVEPATH"
SAVEPATHs="$SAVEPATH"
[ "$SAVEPATH" != "/" ] && SAVEPATHs="${SAVEPATH}/"
SAVEFILE="${SAVEPATHs}${NAMEONLY}"
PUPSAVE="$SAVEPART,$SAVEFS,$SAVEFILE"
}
pupsavefunc() {
SAVEPATH="`dirname $SAVEFILE`"
#final sanity check...
AAAMB=`expr $SIZEPFILE \/ 1024`
T_sanititle="$(gettext 'First shutdown: sanity check')"
T_saniyes="$(gettext 'YES, SAVE')"
T_sanichange="$(gettext 'CHANGE FOLDER')"
while [ 1 ];do
nameclash || return 1
SAVEPATH=$(dirname "$SAVEFILE")
[ "$SAVEPATH" = '/' ] && SAVEPATH=''
NAMEONLY=$(basename "$SAVEFILE")
T_sanitext="`eval_gettext \"\Zb\Z1FINAL SANITY CHECK:\Zn\ZB
Partition you are saving to: \Zb\\\${SAVEPART}\ZB
The filesystem of \\\${SAVEPART} partition: \Zb\\\${SAVEFS}\ZB
Name of the save file: \Zb\\\${NAMEONLY}\ZB
Path (folder) of the save file: \Zb\\\${SAVEPATH}\ZB
Size of save file: \Zb\\\${SIZEPFILE}KB (\\\${AAAMB}MB)\ZB
Filesystem inside save file: \Zb\\\${SFFS}\ZB
If they definitely look right, choose \Zb\\\${T_saniyes}\ZB button...
Looks ok, but you want to change the folder, choose \Zb\\\${T_sanichange}\ZB...
If anything looks wrong, choose \Zb\\\${T_notsave}\ZB...\"`"
${DIALOGEXE} ${BACKGROUNDYELLOW} ${TITLEPARAM} "$T_sanititle" --colors --no-collapse --extra-button --ok-label "$T_saniyes" --extra-label "$T_sanichange" --cancel-label "$T_notsave" --yesno "$T_sanitext" 0 0 #110926
SANITYRET=$?
[ $SANITYRET -ne 0 -a $SANITYRET -ne 3 ] && return 1
[ $SANITYRET -eq 0 ] && break
if [ $SANITYRET -eq 3 ];then #change folder.
changefolder
else
SAVEFILE="${SAVEPATH}${NAMEONLY}"
PUPSAVE="$SAVEPART,$SAVEFS,$SAVEFILE"
fi
done
[ -f ${SMNTPT}${SAVEPATH} ] && return 1 #abort. must be a directory.
[ ! -d ${SMNTPT}${SAVEPATH} ] && mkdir -p ${SMNTPT}${SAVEPATH}
[ ! -d ${SMNTPT}${SAVEPATH} ] && return 1 #some kind of error, abort.
[ "$SAVEPART" = "fd0" ] && SIZEPFILE=`expr $SIZEPFILE - 16`
[ "$SFEXT" = "3fs" ] && JOPT='-j'
#echo "Creating $NAMEONLY in /dev/$SAVEPART, please wait awhile..."
T_createtitle="$(gettext 'First shutdown: creating save-file')"
T_createsf="$(eval_gettext "Creating \${NAMEONLY} in \${SAVEPART}, please wait awhile (no need to click OK button)...")"
altT_createsf="$(eval_gettext "Creating \${NAMEONLY} in \${SAVEPART}, please wait awhile...")"
if [ $DISPLAY ];then
#create nice window looking like prior ones...
export SHUTDLG="<window decorated=\"false\">
<vbox>
<text use-markup=\"true\"><label>\"<big><b>${T_createtitle}</b></big>\"</label></text>
<text use-markup=\"true\"><label>\"<big>${altT_createsf}</big>\"</label></text>
</vbox>
</window>"
GTK2_RC_FILES=/tmp/orange_gtkrc${$}:/root/.gtkrc-2.0 gtkdialog --center --class="splashwindow" --program=SHUTDLG & #130525 130712
w1PID=$!
else
${DIALOGEXE} ${BACKGROUNDORANGE} ${TITLEPARAM} "$T_createtitle" --colors --ok-label "OK" --msgbox "$T_createsf" 0 0 &
w1PID=$!
fi
dd if=/dev/zero of=${SMNTPT}$SAVEFILE bs=1k count=$SIZEPFILE >&2
sync
#pupkill $w1PID
echo "`eval_gettext \"Creating a \\\${SFFS} filesystem in \\\${NAMEONLY}...\"`"
if [ "$CRYPTO" = "" ];then
case $SFFS in
ext2) mkfs.ext2 -q -m 0 -F ${SMNTPT}$SAVEFILE ;;
ext3) mkfs.ext3 -q -m 0 -F ${SMNTPT}$SAVEFILE ;;
ext4) mkfs.ext4 -q -m 0 -F ${SMNTPT}$SAVEFILE ;;
esac
#...default is f.s. auto checked every 26 mounts or 180 days. tune2fs to change.
pupkill $w1PID #130525 moved down.
else
#note: loop2 is kept available for scripts to use. but, find which is free...
echo -e "Save this log somewhere and close this window to continue...\n" >/tmp/mk2fs.log
DEVLOOP="$(losetup-222 -f)"
if [ "$CRYPTO" = "luks" ] ; then
losetup -v $DEVLOOP ${SMNTPT}$SAVEFILE >>/tmp/mk2fs.log
echo -n "$MYPASSWORD" | cryptsetup luksFormat -v $DEVLOOP - &>>/tmp/mk2fs.log
echo -n "$MYPASSWORD" | cryptsetup luksOpen -v $DEVLOOP savefile - &>>/tmp/mk2fs.log
FSCK_DEV=/dev/mapper/savefile
else
#'-p 0' means read password from stdin...
echo "losetup-222 -v -p 0 $CRYPTO $DEVLOOP ${SMNTPT}$SAVEFILE" >>/tmp/mk2fs.log
echo "$MYPASSWORD" | losetup-222 -v -p 0 $CRYPTO $DEVLOOP ${SMNTPT}$SAVEFILE &>>/tmp/mk2fs.log
FSCK_DEV=$DEVLOOP
fi
echo "mke2fs -v -t $SFFS -m 0 -E nodiscard -F $FSCK_DEV" >>/tmp/mk2fs.log
mke2fs -v -t $SFFS -m 0 -E nodiscard -F $FSCK_DEV &>>/tmp/mk2fs.log && \
e2fsck -v -f -y -E discard $FSCK_DEV &>>/tmp/mk2fs.log || e2fsck -v -f -y $FSCK_DEV &>>/tmp/mk2fs.log
if [ $? -ne 0 ] ; then
pupkill $w1PID
/usr/lib/gtkdialog/box_ok "$(gettext 'Error')" error "$(gettext 'Unable to create filesystem')"
defaulttextviewer /tmp/mk2fs.log
fi
sync
pupkill $w1PID #130525 moved down.
[ "$CRYPTO" = "luks" ] && cryptsetup luksClose savefile
losetup -d $DEVLOOP
fi
sync
return 0
} #end pupsavefunc
save_directory() {
#final sanity check...
T_sanititle="$(gettext 'First shutdown: sanity check')"
T_saniyes="$(gettext 'YES, SAVE')"
T_sanichange="$(gettext 'CHANGE FOLDER')"
while [ 1 ];do
nameclash || return 1
SAVEPATH=$(dirname "$SAVEFILE")
[ "$SAVEPATH" = '/' ] && SAVEPATH=''
NAMEONLY=$(basename "$SAVEFILE")
T_sanitext="`eval_gettext \"\Zb\Z1FINAL SANITY CHECK:\Zn\ZB
Partition you are saving to: \Zb\\\${SAVEPART}\ZB
The filesystem of \\\${SAVEPART} partition: \Zb\\\${SAVEFS}\ZB
Path (folder) of the pupsave: \Zb\\\${SAVEPATH}/${NAMEONLY}\ZB
If they definitely look right, choose \Zb\\\${T_saniyes}\ZB button...
Looks ok, but you want to change the folder, choose \Zb\\\${T_sanichange}\ZB...
If anything looks wrong, choose \Zb\\\${T_notsave}\ZB...\"`"
${DIALOGEXE} ${BACKGROUNDYELLOW} ${TITLEPARAM} "$T_sanititle" --colors --no-collapse --extra-button --ok-label "$T_saniyes" --extra-label "$T_sanichange" --cancel-label "$T_notsave" --yesno "$T_sanitext" 0 0 #110926
SANITYRET=$?
[ $SANITYRET -ne 0 -a $SANITYRET -ne 3 ] && return 1
[ $SANITYRET -eq 0 ] && break
if [ $SANITYRET -eq 3 ];then #change folder.
changefolder
else
SAVEFILE="${SAVEPATH}${NAMEONLY}"
PUPSAVE="$SAVEPART,$SAVEFS,$SAVEFILE"
fi
done
mkdir -p $SMNTPT$SAVEFILE 2>/dev/null
PUPSAVEICON=/usr/local/apps/ROX-Filer/ROX/MIME/application-x-ext2-image.png
[ -s "$PUPSAVEICON" ] && cp -f "$PUPSAVEICON" "$SMNTPT$SAVEFILE/.DirIcon"
PUPMODE=128
SAVEPART=${SAVEPART}
SAVEFS=${SAVEFS}
PUPSAVE=${PUPSAVE}
SAVEFILE=${SAVEFILE}
NAMEONLY=${NAMEONLY}
SAVEPATH=${SAVEPATH}
MYPASSWORD=''
SFEXT=''
xPDEV=${PDEV1}
xDEVFS=${DEV1FS}
xPSUBDIR=${PSUBDIR}
SMNTPT=${SMNTPT}
CRYPTO=''
expBOOTDRV=${expBOOTDRV}
} #end sace_directory
offersfscopy() {
#offer to copy $DISTRO_PUPPYSFS (puppy.sfs) and $DISTRO_ZDRVSFS (zdrv.sfs) etc off the cd...
if [ "$DEV1FS" = "iso9660" -o "$DEV1FS" = "udf" ];then #test if booted off cd. 130128
if [ ! -f ${SMNTPT}/${DISTRO_PUPPYSFS} ];then #see file DISTRO_SPECS, init
NAMEONLY="`basename $SAVEFILE`"
T_copytitle="$(gettext 'First shutdown: copy .sfs from CD')"
T_copy="$(gettext 'COPY')"
msg1="$(printf "$(gettext "The CD has '%s' and maybe other .sfs files on it. It will speed startup considerably if these are on the hard drive.")" "${DISTRO_PUPPYSFS}")"
msg2="$(printf "$(gettext "Also, for PCs with less than 256MB of RAM, %s does not copy the %s file to RAM so the CD drive remains mounted, meaning that the drive cannot be used for other purposes.")" "${DISTRO_NAME}" "${DISTRO_PUPPYSFS}")"
msg3="$(printf "$(gettext "However, if you reply \Zb%s\ZB here then it will be copied to the same drive as the '%ssave' file and loaded from there at startup, thus freeing the CD drive for other uses.")" "${T_copy}" "${DISTRO_FILE_PREFIX}")"
msg4="$(printf "$(gettext "Even if you have heaps of RAM, it is still good to answer \Zb%s\ZB to get the faster startup.")" "${T_copy}")"
msg5="$(printf "$(gettext "Note: if a CD has extra .sfs files on it, by copying them to the same drive as the '%ssave' file, they are then available to be loaded at startup, which is configurable by the BootManager (the BootManager is in the System menu)")" "${DISTRO_FILE_PREFIX}")"
msg6="$(printf "$(gettext "If you answer \Zb%s\ZB here, please \Zb\Z1FIRST, RIGHT NOW\Zn\ZB, put the %s CD into the %s drive (the same one that the CD was in at startup), if it isn't already, THEN select the \Zb%s\ZB button...)")" "${T_copy}" "${DISTRO_NAME}" "${PDEV1}" "${T_copy}")"
yesno="${msg1}\n${msg2}\n${msg3}\n${msg4}\n\n${msg5}\n\n${msg6}"
${DIALOGEXE} ${BACKGROUNDYELLOW} ${TITLEPARAM} "$T_copytitle" --colors --yes-label "$T_copy" --yesno "$yesno" 0 0
RETVAL=$?
clear
if [ $RETVAL -eq 0 ];then
#echo "Please wait, accessing CD drive..."
T_waitcopy="$(gettext 'Please wait, copying .sfs files from CD...')"
if [ $DISPLAY ];then
#create nice window looking like prior ones...
export COPYSFSDLG="<window decorated=\"false\">
<vbox>
<text use-markup=\"true\"><label>\"<big><b>${T_copytitle}</b></big>\"</label></text>
<text use-markup=\"true\"><label>\"<big>${T_waitcopy}</big>\"</label></text>
</vbox>
</window>"
GTK2_RC_FILES=/tmp/orange_gtkrc${$}:/root/.gtkrc-2.0 gtkdialog --center --class="splashwindow" --program=COPYSFSDLG & #130712
cPID=$!
else
${DIALOGEXE} ${BACKGROUNDORANGE} ${TITLEPARAM} "$T_copytitle" --msgbox "$T_waitcopy" 0 0 &
cPID=$!
fi
APATTERN="/dev/$PDEV1 "
CDMNTPT="`mount | grep "$APATTERN" | cut -f 3 -d ' '`"
mkdir -p /mnt/$PDEV1
if [ "$CDMNTPT" = "" ];then
mount -t iso9660 /dev/$PDEV1 /mnt/$PDEV1
CDMNTPT="/mnt/$PDEV1"
fi
for ONESFS in `find $CDMNTPT -maxdepth 1 -type f -name \*.sfs | grep -v ' ' | tr '\n' ' '`
do
BASESFS="`basename $ONESFS`"
FILESIZEB=`stat --format=%s $ONESFS`
FILESIZEK=`expr $FILESIZEB \/ 1024 + 2048` #2MB slack.
BPATTERN=" $SMNTPT"'$'
DRVFREEK=`df -k | tr -s ' ' | grep "$BPATTERN" | cut -f 4 -d ' '`
if [ $DRVFREEK -gt $FILESIZEK ];then
echo "`eval_gettext \"Copying \\\${BASESFS}...\"`"
cp -f $ONESFS $SMNTPT/
sync
else
T_cantcopy="`eval_gettext \"Insufficient space! Cannot copy \\\${BASESFS}\"`"
echo "$T_cantcopy"
[ $DISPLAY ] && /usr/lib/gtkdialog/box_ok "$(gettext 'Shutdown config')" error "$T_cantcopy"
break
fi
done
busybox umount $CDMNTPT
pupkill $cPID
fi
fi
fi
} #end offersfscopy
#================================================================
xDEVFS="$DEV1FS"
xPDEV="$PDEV1"
if [ "$PSAVEMARK" != "" -a "$PDEV1" != "" ];then #see /etc/rc.d/PUPSTATE
devnameonly="`echo -n "$PDEV1" | sed -e 's/[0-9]*$//'`"
SAVEPART="${devnameonly}${PSAVEMARK}" #partition that will-have ${DISTRO_FILE_PREFIX}save.
spPATTERN='/dev/'"$SAVEPART"'|'
SAVEFS="`probepart -m | grep "$spPATTERN" | cut -f 2 -d '|'`"
xDEVFS="$SAVEFS"
xPDEV="$SAVEPART"
fi
[ ! "$DEV1FS" ] && xDEVFS='xxx' #this will enable choice of create a save-file.
SAVECHOICE=255
# some word processing now...
T_canceltitle="$(gettext 'Click close-box to cancel shutdown')"
T_countdown="$(gettext 'Shutdown in TIME seconds')"
T_savetofile="$(gettext 'SAVE TO FILE')"
T_savetopart="`eval_gettext \"SAVE TO \\\${xPDEV}\"`"
T_orwait240=""
[ $TIMELIMIT -gt 0 ] && \
T_orwait240=$(printf "$(gettext '(Or, wait %s seconds to shutdown without saving anything)')" "$TIMELIMIT")
T_save="$(gettext 'SAVE')"
T_cd="$(gettext 'SAVE TO CD')"
#130221 note, pupdialog will exit with 255 if click window close-box, 254 if timeout.
# former, want to abort shutdown, latter, shutdown without saving.
xPSUBDIR="`echo -n "$PUPSFS" | cut -f 3 -d ',' | sed -e 's%/[^/]*$%%'`" #ex: sda3,vfat,/pup220/puppy.sfs will return /pup220
T_ms="`eval_gettext \"You can save the session and all of the settings and personal data created so far.
If unsure, it is recommended that you do save the session, so all your personal settings and files will be automatically loaded at next boot.\"`"
if [ $DISPLAY ];then
T_display="`eval_gettext \"Click the \Zb\\\${T_save}\ZB button to be provided with the available save options, or click \Zb\\\${T_no}\ZB to exit immediately without saving anything.\"`" #111012 fix.
yesno="$T_ms \n\n$T_display \n\n$T_orwait240"
pupdialog --background '#FFFF80' --colors --title "$T_canceltitle" --backtitle "$T_title" --timeout $TIMELIMIT --countdown "$T_countdown" --no-label "$T_no" --yes-label "$T_save" --yesno "$yesno" 0 0 #120512
else
T_display="`eval_gettext \"Select \Zb\\\${T_save}\ZB (just press ENTER key) to be provided with the available save options, or select \Zb\\\${T_no}\ZB (TAB then ENTER) to exit without saving.\"`"
yesno="$T_ms \n\n$T_display \n\n$T_orwait240"
dialog --colors --title "$T_title" --timeout $TIMELIMIT --no-label "$T_no" --yes-label "$T_save" --yesno "$yesno" 0 0 #120512
fi
SAVECHOICE=$?
case $SAVECHOICE in
0)
if choosepartfunc; then
enmount
case $SAVEFS in
ext?|reiserfs|minix|btrfs|f2fs) SAVEFS_IS_LINUX="y";;
*) SAVEFS_IS_LINUX="";;
esac
SAVESTYLE='file'
DENSITY=''
SFEXT=''
if cryptsetup --help &>/dev/null && modprobe dm-crypt && modprobe xts ; then
choosecrypt_new
elif which losetup-222 2>/dev/null ; then
choosecrypt
fi
[ -z "$DENSITY" ] && [ "$SAVEFS_IS_LINUX" ] && choosestyle
if [ "$SAVESTYLE" = "file" ]; then
[ -z "$DENSITY" ] && choosefs
choosesize || exit ###FIXME###
fi
if [ "$SAVESTYLE" != "partition" ]; then
choosename
NAMEROOT="$NAMEONLY"
[ "${SFEXT}" ] && NAMEONLY="$NAMEROOT.${SFEXT}"
if [ "$PSAVEDIR" ];then
SAVEFILE="${PSAVEDIR}${NAMEONLY}"
else
SAVEFILE="$PSUBDIR/$NAMEONLY"
fi
#nameclash || exit ###FIXME###
PUPSAVE="$SAVEPART,$SAVEFS,$SAVEFILE"
fi
case "$SAVESTYLE" in
folder) save_directory && PUPMODE=128;;
partition) PUPMODE=32;;
file) pupsavefunc && PUPMODE=128;;
*) "SAVESTYLE=$SAVESTYLE" ;;
esac
fi
;;
3) echo ;; #case already handled above.
255) exit 255 ;; #wmreboot and wmpoweroff can cancel shutdown. 130221
*) echo "$(gettext 'Shutting down without saving...')" ;;
esac
if [ $PUPMODE -eq 128 ];then #will be saving session.
offersfscopy
fi
#--------------------------------------------------
if [ ! -f ${SMNTPT}/pupswap.swp ] ; then
if pupswap validate_drive ${SAVEPART} ; then
ONLY_IF_NO_SWAP=1 pupswap set_dir ${SMNTPT}
fi
fi
#--------------------------------------------------
#record all variables to a file...
#20140716 SFR: but first escape ' (if present) in MYPASSWORD
MYPASSWORD="`echo "$MYPASSWORD" | sed -e "s#'#'\\"'\\"'#g"`"
echo "PUPMODE=${PUPMODE}
SAVEPART='${SAVEPART}'
SAVEFS='${SAVEFS}'
SAVEFILE='${SAVEFILE}'
PUPSAVE='${SAVEPART},${SAVEFS},${SAVEFILE}'
NAMEONLY='${NAMEONLY}'
SAVEPATH='${SAVEPATH}'
MYPASSWORD='${MYPASSWORD}'
SFEXT='${SFEXT}'
xPDEV='${xPDEV}'
xDEVFS='${xDEVFS}'
xPSUBDIR='${xPSUBDIR}'
SMNTPT='${SMNTPT}'
CRYPTO='${CRYPTO}'
expBOOTDRV='${expBOOTDRV}'" > /tmp/shutdownconfig_results
# Add a savemark file if we save in a diffrent partition
# But not if defined by PSAVEPART in PUPSTATE
if [ "${PSAVEPART}" = "" -a "${SAVEPART}" != "${xPDEV}" ];then
SAVEDISK=$(echo "${SAVEPART}" | sed 's/[0-9]*//g')
PDEV1DISK=$(echo "${xPDEV}" | sed 's/[0-9]*//g')
xSAVEMARK=$(echo "${SAVEPART}" | sed 's/[^0-9]*//g')
if [ "${SAVEDISK}" = "${PDEV1DISK}" ];then
MOUNTED=$(grep "${xPDEV}" /proc/mounts)
if [ "$MOUNTED" ]; then
echo "${xSAVEMARK}" > /mnt/${xPDEV}${xPSUBDIR}/SAVEMARK
else
mkdir -p /mnt/${xPDEV} && mount /dev/${xPDEV} /mnt/${xPDEV}
echo "${xSAVEMARK}" > /mnt/${xPDEV}${xPSUBDIR}/SAVEMARK
fi
umount /mnt/${xPDEV} 2>/dev/null
fi
fi
exit 0
#the end#
Only 16 Gb and a Scandish. Disregard my 'missing drivers/firmware' suggestion. I've never had a problem booting or Saving to them.
But, I've never formatted them as ntfs.
Lassar, you still haven't answered rcrsn51's question. Are you booting off the hard-drive and trying to Save to the USB-Stick?
There is one other thing you can do which might help isolate what's going wrong. Part of the nicOS-Utility-Suite --referenced previously-- is a module for creating a SaveFile. Once created it can be moved anywhere.
Despite what appears to be 3 choices for the location of the creation, there are only 2: Your Home partition or RAM. Other partitions are not offered even if mounted.
Your Home partition is that on which your Puppy's system files [e.g. initrd(.gz), vmlinuz, puppy_xenialpup64_7.5.sfs, etc] are located. If your Puppy's system files are on the USB-Stick, and if MakeSave can create a SaveFile there, a comparison of its building code/logic with that of the 'built-in' Save code may reveal the problem.
If it can't create a SaveFile there, but moving a SaveFile created in RAM to the USB-Stick produces a viable SaveFile, then the 'built-in' code can be examined for a different problem.
Similarly, trying Kodipup after a 'kernel swap' --even if only with a kernel from xenialpup64-- may suggest that something went sideways during your remaster.
Yes, I am booting off the hard drive.
That is how I can directly modify the grub.cfg file
And am trying to save the save file to a usb drive.
What is line 120?
[ "$DEV1FS" = "msdos" ] && DEV1FS="vfat"
Is this a logic statement?
Should not $DEV1FS be sdb1 instead?
Just an idea. But easy to test.
I've never formatted a USB-Key/thumb-drive as ntfs. I also don't recall posts by anyone who has.
Boot into Puppy (pfix=ram so as not to have it use the SaveFile on your hard-drive). Don't have the US-key plugged in when you boot. Plug the thumb-drive in after you boot-up, but don't mount it. Before shutting down, use Menu>System>gparted to format the USB-Key to anything other than ntfs. Suggest Linux Ext3, but Fat32 is OK.
On shutdown can you now select the USB-Key as the location for the Save?
You may have found a previously undiscovered bug.