xenialpup64bit alongside lubuntu [Solved]

[foxpup]

Is this the complete grub.cfg?
Maybe earlier there is

Code: Select all

set timeout=0

If so change 0 to -1 so you have all the time to look and choose.

[d_vineet]

No. this is not the full file. In order to avoid clutter, I have attached it.
And I have edited my previous reply to add one imp note. Can you pl. review it?

[d_vineet]

Upon searching official ubuntu docs reg grub2, found that right SHIFT key or ESCAPE key needs to be pressed for showing boot options.
Did that and saw the option of puppy.
Thank you very much for all your patience and help.

[foxpup]

Upon searching official ubuntu docs reg grub2, found that right SHIFT key needs to be pressed for showing boot options.

Didn't know that. Learning something as well I may look how it is done in Lubuntu.

Glad I could help.

[ITSMERSH]

Maybe, the "pmedia=usbflash" option isn't correct?

I would change it to pmedia=atahd - just to make sure...

[foxpup]

One final remark.
It is possible that Lubuntu, when it updates, makes changes to grub. Sometimes this can mess up things.
Best to keep a copy of grub.cfg, just in case.

[foxpup]

Maybe, the "pmedia=usbflash" option isn't correct?

I would change it to pmedia=atahd - just to make sure...

"usbflash" just gives you a "save" button on the desktop to save the session to the pupsavefoler or pupsavefile manually.
Then in the event manager you can set the interval for saving to the pupsave to 0 (never).

[d_vineet]

One observation--
We had created a folder manually on sda2 and copied files there.
Was it needed? Because upon first time exit, puppy automatically did that by asking self-explanatory options (and overwritten upon what we had copied).

[foxpup]

One observation--
We had created a folder manually on sda2 and copied files there.
Was it needed? Because upon first time exit, puppy automatically did that by asking self-explanatory options (and overwritten upon what we had copied).

You are right, it was not needed. Xenialpup, and most newer Puppies do that.
I had forgotten, because I seldom boot Puppy from usb, I put it on the hd immediately, like you have done now, but from another Puppy that is already on the hd.
Well, now you know how it goes.

The entry added into the grub.cfg was still needed to be able to boot from hd.

There is also a tool, LICK, that can be used to install Puppy to an uefi machine. It is often included in newer Puppies.
It preserves windows boot, but I don't know how it handles lubuntu or other nixes.

I prefer manually though. I want to know what i am doing.

[bigpup]

Bigpup

If this is a EFI machine with gpt hd, I don't think grub4dos will work.
Or am I mistaken?

1/2 correct.
Grub4dos will work with UEFI bios.
It will not work with a drive that uses a GPT partition table.
GPT partition table setup does not have the storage location that Grub4dos normally uses for it's files.

The hard drive probably is using a MSDOS MBR partition table setup. Grub4dos can work on that.
Could use Gparted to look at the drive.
Device information will tell you.


You basically manually did what the Universal Installer would do for a frugal install.

As I said earlier, getting a boot loader to work with every operating system is always the issue.
Manually putting the Xenialpup boot entry into the Lubuntu grub boot loader is one way to do it.

Sometimes it is whatever works, works!

[bigpup]

Maybe, the "pmedia=usbflash" option isn't correct?

I would change it to pmedia=atahd - just to make sure.

Both will work. What they control is how the save is used.

pmedia=usbflash will mount the save as read only.
This is normal option for USB flash drive installs.
Any changes, added stuff, setting changes, etc... will be placed in a save ramdisk that uses computer ram. Stuff is put in the actual save when you shutdown, at a set time (default 30 min), or click on the save icon.
This helps to limit writes to a USB flash drive. They do have a write limit before failure.

pmedia=atahd will mount the save as read/write all the time.
This is normal option for hard drive installs.
You do something and it is written to the save, as you do it.
It still does it again, at shutdown, to make sure everything in ram, that needs to be in the save, gets into it.
Hard drives can handle lots of writes.

[foxpup]

Hard drives can handle lots of writes.

And SSD? Are they not to be considered as flash?

[bigpup]

Sure.

If you really think it is a problem with SSD's.
SSD's have been around long enough and have wear limiting built in now.
For normal home user, it would take 10+ years before even getting close to writes causing any problems.
Even then, the data is not lost. It just starts having problems being able to write new data to storage.


This is no longer the early days of SSD's.