Puppy documentation needs updated or replaced

[dimkr]

Look at lines 47 to 54: the release notes can be customized by the woof-CE user, by adding support/release_extras/"${DISTRO_FILE_PREFIX}.htm. index.html.{top,bottom} exist in the name of consistency, I guess.

[bigpup]

Just looked at HOWTO_dialup.htm as well, the one I renamed. Seems like it had a broken link.
Tried to correct it, but having no knowledge in the field, I ask you, @bigpup and @wizard, if this file is okay or not:-

I will look it over.
But I have not used dialup for a very long time.

Maybe someone, that has used dialup, will come along, and can offer advice.

I looked at it, but my eyes glassed over and I had a brain freeze!

I have never used any of this stuff with Puppy Linux or used dialup connection.

I did test all the clickable links and they are no good.
But I have no idea what they should be.

Sorry, can not help on this one.

Anyone out there that can help?

[bigpup]

@user1234
Should I just look at what is in the last doc directory, you attached, and see if I find anything?

I can do an overall check to see if something got missed.

Do you have something you want me to work on?

Some great work you are doing!

Note:
When I updated the forum FAQ.
What a crazy way to make a FAQ and how to edit it.
But as I learned what to do, it was easy in the end.
Halfway into it, me and rockedge realized, he had not provided me access to all the stuff I needed, to do the edits.

This thing about the index.html reminds me of that

[user1234]

@user1234
Should I just look at what is in the last doc directory, you attached, and see if I find anything?

I can do an overall check to see if something got missed.

Do you have something you want me to work on?

Some great work you are doing!

Note:
When I updated the forum FAQ.
What a crazy way to make a FAQ and how to edit it.
But as I learned what to do, it was easy in the end.
Halfway into it, me and rockedge realized, he had not provided me access to all the stuff I needed, to do the edits.

This thing about the index.html reminds me of that

I am sorry, I couldn't do anything for the documentation stuff yesterday, as I was too busy to even look at it. Will continue with the work today. I think forums.htm could also be added with some stuff. I'll do that today.

EDIT: I don't think forums.htm may need any addition/deletion of stuff after taking look at it once again. Updated the HOWTO_sns.htm file once again. Please check the file:-

HOWTO_sns.htm.tar.bz2

(1.67 KiB) Downloaded 41 times

I'll try to update installation.htm and root.htm, in case they need any update. I'll also try to update HOWTO-multimedia as well, the one needing most work. I request you to update cups_shell.htm, samba-printing.htm, Pudd.htm and HOWTO-internationalization.htm. I'm not so good at those topics.

I also request you @BarryK to please update the HOWTO_dialup.htm (the one which you actually named HOWTO_modem.htm). I don't think any of us might be able to update it . Here is HOWTO_dialup.htm:-

HOWTO_dialup.htm.tar.bz2

(6.3 KiB) Downloaded 60 times

Thanks!

[BarryK]

EDIT: I don't think forums.htm may need any addition/deletion of stuff after taking look at it once again. Updated the HOWTO_sns.htm file once again. Please check the file:-
HOWTO_sns.htm.tar.bz2

I'll try to update installation.htm and root.htm, in case they need any update. I'll also try to update HOWTO-multimedia as well, the one needing most work. I request you to update cups_shell.htm, samba-printing.htm, Pudd.htm and HOWTO-internationalization.htm. I'm not so good at those topics.

I also request you @BarryK to please update the HOWTO_dialup.htm (the one which you actually named HOWTO_modem.htm). I don't think any of us might be able to update it . Here is HOWTO_dialup.htm:-HOWTO_dialup.htm.tar.bz2
Thanks!

Don't ask me!
I don't have those HOWTO_ files in EasyOS anymore.
The only ones I still have are HOWTO_bash-parameter-expansion.htm and HOWTO_regexps.htm

Easy doesn't have wvdial anymore.
There is still /usr/local/simple_network_setup, but don't use it.

Still have /usr/share/doc/Pudd.htm and samba-printing.htm, but haven't looked at them for years.
Hmm, Pudd.htm was last edited in Feb. 2013 and samba-printing.htm in Jan. 2013.

[user1234]

EDIT: I don't think forums.htm may need any addition/deletion of stuff after taking look at it once again. Updated the HOWTO_sns.htm file once again. Please check the file:-
HOWTO_sns.htm.tar.bz2

I'll try to update installation.htm and root.htm, in case they need any update. I'll also try to update HOWTO-multimedia as well, the one needing most work. I request you to update cups_shell.htm, samba-printing.htm, Pudd.htm and HOWTO-internationalization.htm. I'm not so good at those topics.

I also request you @BarryK to please update the HOWTO_dialup.htm (the one which you actually named HOWTO_modem.htm). I don't think any of us might be able to update it . Here is HOWTO_dialup.htm:-HOWTO_dialup.htm.tar.bz2
Thanks!

Don't ask me!
I don't have those HOWTO_ files in EasyOS anymore.
The only ones I still have are HOWTO_bash-parameter-expansion.htm and HOWTO_regexps.htm

Easy doesn't have wvdial anymore.
There is still /usr/local/simple_network_setup, but don't use it.

Still have /usr/share/doc/Pudd.htm and samba-printing.htm, but haven't looked at them for years.
Hmm, Pudd.htm was last edited in Feb. 2013 and samba-printing.htm in Jan. 2013.

So what do you think, will it be right to remove the file? By the way, does anyone still need dialup? And does puppy still support dialup?

[user1234]

@bigpup:-

Updated installation.htm. Here is the file:-
file deleted

EDIT: If you already saw that file, delete it and view this one. Updated installation.htm once again to make it look better. Here is the file:-

installation.htm.tar.bz2

(4.35 KiB) Downloaded 58 times

How I think it should look like-

screenshot_2022-11-15_1366x768.png (479.15 KiB) Viewed 1372 times

This makes me remember of the time when I used to do CSS work as my hobby, and would most of the times end up getting some style in a manner which I never understood. That's why I left CSS .

(Please report if the page on your device doesn't look like the image. My CSS skills are not that great though.)

EDIT (once again): What do you think, should I add this little, sort of button, which does nothing but scroll back to the top of the webpage, to every page? In my opinion, this makes the webpages look more on a (lighter) tutorial side than being a very-difficult-to-read documentation.

[williwaw]

@user1234
I downloaded your installation.htm.tar.bz2 and the included css

Code: Select all

<style>
		#scroll_back {
			border-radius: 100%;
			background-color: #56a8ff;
			color: #fff;
			width: 2em;
			height: 2em;
			position: fixed;
			z-index: 2;
			display: block;
			font-size: 200%;
			text-align: center;
			margin: 0px;
			padding: 0px;
			bottom: 1em;
			right: 1em;
			line-height: 2em;
		}
	</style>

in the file itself, renders in firefox and seamonkey as

Screenshot.png (211.32 KiB) Viewed 1353 times

also. I see you have some changes proposed for index.html, so rather than the both of us working on different edits, could you please change the FAQ link in the bottom as you see fit or perhaps to https://puppylinux-woof-ce.github.io/faq.html
tx

Edit including manual.css in the directory makes it render as you have it in your screenshot above.

[bigpup]

I just read your last few posts.
I will start working on your requests and get back with my results.

What do you think, should I add this little, sort of button, which does nothing but scroll back to the top of the webpage, to every page?

Sure, add it.
Well, maybe only needed on the longer pages.
As long as it works, it is a feature for people to use.

I do not remember what page it was, but one of them had a similar button, that I found useful.

Note:
Just started looking over the installation.htm
I found that scroll back to the top of the webpage button, very useful!
I clicked on a link, that took you to the bottom of the page, to read the References.
Clicking that scroll back to the top of the webpage button, was nice to use, to get back to top of page.
Very useful after using those reference links.

[user1234]

also. I see you have some changes proposed for index.html, so rather than the both of us working on different edits, could you please change the FAQ link in the bottom as you see fit or perhaps to https://puppylinux-woof-ce.github.io/faq.html
tx

I'm sorry I don't get what you're saying. I have just changed the index.html.top to include few webpages that were previously not provided. Should I attach my version of index.html.top here?

@bigpup:- I also see that you have not changed the status of files that I and others have completed. Please change their status.

[williwaw]

I'm sorry I don't get what you're saying. I have just changed the index.html.top to include few webpages that were previously not provided. Should I attach my version of index.html.top here?

@bigpup:- I also see that you have not changed the status of files that I and others have completed. Please change their status.

@user1234
index.html.bottom was where I editing . You are doing index.html.top?

@bigpup

I guess you are consolidating the changes here and will put them into the PR at woof-ce?
one broken link fixed, please review

index.html.bottom.gz

remove the fake .gz

(2.19 KiB) Downloaded 49 times

I also see that you have not changed the status of files that I and others have completed. Please change their status.

+1

[bigpup]

This stuff is going so fast, it is hard to keep the list in the first post updated.
Sorry for that,
I will try to do better.

Well, life is getting in the way, sometimes

I think usr1234 has it figured out, how to get all of this into the Woof-CE repository.

[williwaw]

@bigpup

all the changes you see needing to be done have been acomplished?

@all
should any of these tutorials be included in the usr/share /doc edit PR?
I can help with the reformatting.

[bigpup]

@user1234
You did some very good work on this file.
I just saw some things that I felt could be added to or written differently.

So tell me honestly if you like it or want to change anything?

Maybe it could be a little of your version and a little of mine

I looked over the installation.htm

To me this is an important file to get correct.

I would like all to look it over.
Mainly looking for what everyone thinks of it and if they see more changes needed in the statements.

This is the new or edited statements.
Did this in a text editor, so it does not have the links.

Introduction

Puppy can be installed in many different ways. Consequently, the installer has many different choices which may be confusing to the new Puppy user. This document will attempt to clear that confusion. the Puppy User can confidently install Puppy Linux to your medium of choice in the desired manner.

Target Media

Puppy can be installed to all common media. USB sticks, USB hard drives, Firewire2 hard drives, CF (Compact Flash), SD card, internal Solid State Disk (SSD) and normal old Hard Drives (HDD - either IDE or SATA).
Even CD, DVD and BlueRay™1 installation (as such) is supported, but it will require special burning programs and drive that can do read/writes.
Alternatively, if you boot with a CD/DVD that was not closed when burned, CD-RW or DVD-RW8 you can save your session to the optical media and never worry about installing anything! No hard drive needed.

Live install

A live install is usually what is done on a USB flash drive (stick) or a CD/DVD.
All the Puppy files in the Puppy ISO are written to the USB stick or the CD/DVD.
The Puppy ISO has all the needed files to boot this type install and run the operating system.

Good way to try a Puppy version and see how you like it.

Frugal Install (Recommended to all)

Frugal is the name used for it, but it is still the complete Puppy operating system (OS), only installed in a special way.
All the Puppy OS is placed inside a Directory(Linux name for folder) or folder. Everything Puppy is kept inside this directory or folder.
Frugal name is about how little it uses space for the install. Frugal use of the resources on the drive.

Frugal install can be done on any device that is read/write capable. Can be placed on any partition with any type format.

By design, Puppy Linux runs in your systems Random Access Memory (RAM). Normally, a minimum of 512 MB9 (megabytes) of RAM is recommended to run Puppy but it will work with less (See 9). Don't worry, any machine built after 2003 is likely to have at least enough RAM.

Using this method, Puppy isn't actually installed on your system per se´, rather the Puppy files (the kernel or vmlinuz, an initial ram disk or initrd.gz, a main puppy system file known as the "Main SFS" usually named puppy_puppy-name_puppy-version.sfs or similar (for example-puppy_fossapup64_9.5.sfs) and perhaps a few other "SFS files" (the files ending in .sfs), depending on Puppy version, are copied to your drive and placed inside a folder or directory. This installs your Puppy.

To be able to boot a frugal install, a boot loader will also need to be installed.
Installer programs that are provided in Puppy, will install boot loaders that are designed to make proper boot menu entries for frugal install booting.
Most of these Puppy boot loader installers, will also find other than Puppy operating systems installed, and add them to the boot loader menu.
First read the installer help to make sure it can do this.

If you do a frugal install (folder or directory inside another operating system).
That operating system will already have a boot loader installed.
You can edit that boot loaders boot menu config file and add a entry for booting the frugal Puppy install.

Using this frugal install method, Puppy can be installed in almost any partition on almost any file system (eg: FAT32, NTFS, ext2, ext3, ext4). It can be installed inside an existing Installation of Windows, or other Linux such as Ubuntu or Fedora. To them it is just a folder or directory. A frugal install also works on all types of media3. Puppy development and testing is also inclined towards Frugal method of Puppy installation.
Some features of Puppy Linux only work in frugal installs.
Due to these reasons it is advisable that you use this method of installation.

For technical information see How Puppy Works.

Full Install

A Full installation is just like a Windows™ installation or any other Linux Installation. It requires it's own partition and it must be of a Linux type filesystem; most commonly ext2, ext3 or ext4 but others are possible. These are mostly used for internal HDDs or SSDs but can be used on external USB or FireWire HDDs.
It is not advisable to install Puppy using this method as there is already a better (Frugal Installation Method) present for installation.

Booting

Booting, in simple terms, is just your computer finding the files to execute the Operating System (OS). All Operating Systems need some way to boot. Puppy supports various methods of booting. Some require the editing of the special boot code at the start of the disk (MBR) so that the special Linux files can be found (kernel - vmlinuz and initrd.gz).

The boot loader provides this control of the boot process. Finding the files needed by the operating system, to start running the computer, and proceeding with the boot process to a working operating system.

Puppy can be made to dual-boot with Windows or another Linux or multi-boot with several operating systems. There are three main boot loader programs that Puppy supports out of the box for booting. Grub4dos, grub (legacy), Grub2, and Syslinux.

There are several boot loaders that can be used. Some are Puppy programs and are designed for how Puppy works.
Shown here so you can understand the differences.

Grub4dos (does not support GPT/UEFI systems) supports booting from vfat (FAT32 or FAT16) filesystems found in Windows™ 95, 98 and ME and the NTFS filesystem introduced in Windows™ NT and also the default filesystem of Windows™ 2000, XP, Vista , 7, 8, 8.1 and the Windows™ Server family. The Puppy program grub4dosconfig takes all the hard work out of installing a boot loader and automatically detects and configures loading of all your installed OS. If you're tentative about modifying the special boot sector on your hard drive you can install grub4dos to a USB key or a floppy disk.

Grub (legacy) supports booting from vfat (FAT32 or FAT16) filesystems found in Windows™ 95, 98 and ME but not NTFS. This makes it a good choice to install for ancient4 windows machines or pure Linux machines, with no windows. The program Legacy Grub config takes the hard work out of installing the grub boot loader. Again, if you're tentative about modifying the special boot sector on your hard drive or your partition's superblock you can install grub (legacy) to a USB key or a floppy disk.

Grub2confiig (Puppy program) is a script that installs the grub2 boot loader and makes the menu automatically probing installed systems, same way as the old Grub4DosConfig, enabling multi-boot with Windows, Ubuntu and etc.. It supports both legacy MBR system and new GPT/UEFI. Also supports UEFI Secure boot, thanks to the Gyrog's MOK manager, that will install the Puppy security key.

Grub2 is usually the boot loader used by another operating system that is also installed on your computer. That operating system installed and set it up.
To still use it, you will have to edit it's grub2 boot menu config file adding an entry for the Puppy frugal install.

Syslinux supports booting from vfat (FAT32 or FAT16) filesystems found in Windows™ 95, 98 and ME and the many Linux filesystems such as ext2, ext3 and ext4. This is used in frugal installs to USB keys in Puppy Linux. USB keys can be formatted to vfat or ext(2,3,4). Syslinux can boot hard disks and other media but that is beyond the scope of this manual.

There is also a new filesystem available in some new Puppy versions called the "Flash Friendly File System" (f2fs) which is not currently supported by the boot loaders in Puppy but can be used all the same with a small vfat or ext2 filesystem to boot the kernel with syslinux (or grub4dos or grub2config) and then find the Puppy Linux files on the f2fs filesystem. If your Puppy supports f2fs you can install it to a USB flash drive or SD card and use a frugal5 or full6 type of install.

WakePup2 can also be used to boot Puppy. It is a floppy disk image that needs to be transferred to floppy disk. It can boot a CD from an ancient computer that can not boot from USB or CD in it's BIOS. Of course it can also boot the OS from the HDD. If WakePup2 is not in your Puppy then you can download it from the Puppy Package Manager (PPM).

NB: At the time of writing, Puppy's grub2config boot loader is only puppy boot loader program that supports GPT partitioning found in new Windows™ 8 machines (or newer) and some other operating systems.

You may be confused as to why there are so many options to install Puppy. Puppy is Open Source7 and people love to dive in and write code. It's difficult to say what works for everybody so we bundle together a few different programs for installation so that if one doesn't work the way you want then you can try a different approach. All of them may not be included in your Puppy install.

Typical installers you may find in Puppy for doing installs, but there may be others you will find in a specific Puppy.

Puppy Universal Installer. (aka PUI) This program covers nearly every type of installation from full to frugal and anything in between. If you want to do a full install this is the program you want. It is always included in Puppy Linux.

Frugalpup Installer. This one, as the name suggests, is an excellent choice if you are after a frugal install. Also can install a boot loader for UEFI, legacy bios, or both. Provides Puppy security key for UEFI secure boot enabled.

BootFlash. An installer specifically targeted at USB stick installs. You may want to try this one. Quick and easy.

F2fs Usb Installer. A specialized program to help you format and install to a f2fs USB flash stick or SD card which supports frugal5 or full6 types of installs.

Pburn a program for burning the Puppy ISO to a CD/DVD.

No matter what your situation, we think that we have got you covered. Enjoy installing or not installing, as the case may be ☻, Puppy Linux!

[bigpup]

@bigpup

all the changes you see needing to be done have been acomplished?

@all
should any of these tutorials be included in the usr/share /doc edit PR?
I can help with the reformatting.

Thanks for jumping in to help!

I am not totally sure yet.

I am not sure what usr1234 has not already done and completed.

Still looking them over. It takes time to review and think is that all needed.

Look over what I just posted about the installation.htm statements.

what do you think?

----------------------------------------------------------------------------------------------------------------------

should any of these tutorials be included in the usr/share /doc edit PR?
I can help with the reformatting.

My thinking on stuff that is on the forum.
Should just provide a link to the forum location.

That could be in the index.html

That is the help in the application menu -> help

Maybe make it a info entry saying something like.
for a lot more how to information, go here in the Puppy forum (link to forum location)

Maybe make it a clickable item in list in the help
More How To's or advanced How To's

The main purpose for the files in usr/share/doc are to have ones that can be accessed without a internet connection.
But I do not think all possible info should be there only.

[wizard]

For those who may be interested, the help files from "Getting Started and System Requirements" in .doc format are avaialble here: viewtopic.php?p=72847#p72847

Thanks
wizard

[user1234]

@williwaw:- yes, I have just changed index.html.top.

This stuff is going so fast, it is hard to keep the list in the first post updated.
Sorry for that,
I will try to do better.

Well, life is getting in the way, sometimes

I think usr1234 has it figured out, how to get all of this into the Woof-CE repository.

Are you saying should I open a PR for your updates as well? I have no problem doing that, just wanted to confirm that you are okay that I commit with my name to woof-CE, and not yours. Of course if you'll say that I do open a PR for you, I'll add your user name as the one who contributed, so that your contribution remains your contribution.

@bigpup:- Just another thing to note, here is the draft PR I've already opened. I can add your contribution as well in this PR, if you allow me to. All the files I've updated, and those which in my opinion did not need any modification, are all listed at the link only. For example, here is what you'll see currently (16 November 2022, 8:14 am UTC):-

IMG_20221116_134353.jpg (114.94 KiB) Viewed 1431 times

[user1234]

So tell me honestly if you like it or want to change anything?

Always note that this is puppy! Don't ask for permission, just advice ! We all are here giving advices, and thus the best advices would be kept .

Edit: Done adding that scroll-to-top button to all the files in a latest commit, whether the file was a small one or a lengthier one, to maintain uniformity. Added the style for that button in manual.css, to avoid repetition. I don't think there might be a need for providing the files, no big change is there that your content will get outdated. Here is an example of index.html.top, in case you want to know what you need to add:-

Code: Select all

<!DOCTYPE html>
<html>
<head>
	<title>DISTRO_NAME Help Page</title>
	<meta charset="utf-8">
<script language="JavaScript">

<!-- Begin
function formHandler(form){
var URL = document.form.site.options[document.form.site.selectedIndex].value;
window.location.href = URL;
}
function formHandler2(form2){
var URL = document.form2.site2.options[document.form2.site2.selectedIndex].value;
window.location.href = URL;
}
function search_site()
{
var url = "http://linux.die.net/man/1/"
// Append the text box input to the search url for the selected site
url = url + document.search_form.u_search.value;
// Change the the browser location to the new url
window.location.href = url;
}
// End -->

</script>


	<link href="./manual.css" rel="stylesheet" type="text/css">
	<link href="./flash-notice.css" rel="stylesheet" type="text/css">
</head>
<body>
	<!-- JUST THE NEXT LINE NEEDS TO BE ADDED!!! -->
	<a href="#" class="scroll_back_button" target="_self">&uArr;</a> <!-- JUST THIS LINE NEEDS TO BE ADDED!!! -->
	<!-- JUST THE PREVIOUS LINE NEEDS TO BE ADDED!!! -->

	<div id="container">
		<header id="logo-header">
			<img class="logo-96" alt="Logo" src="puppylogo96.png">
			<h3>Welcome to DISTRO_NAME version DISTRO_VERSION, released PUPPYDATE!</h3>
		</header>
		<p>
			<span style="background-color: rgb(255, 204, 204);padding:4px;">PLEASE READ: <a href="release-cutDISTRONAME-DISTRO_VERSION.htm">Release Notes for DISTRO_NAME DISTRO_VERSION</a></span>
		</p>
		<p>
			<h2>DISTRO_NAME help</h2>
			All DISTRO_NAME's local documentation is in HTML or plain text format and located in /usr/share/doc. This page is the master index.
		</p>
		<p>
			<h3>DISTRO_NAME-specific help</h3>
			<ul>
				<li><a href="installation.htm">About different installation methods</a></li>
				<li><a href="HOWTO_Internet.htm">HOWTO get onto the Internet</a></li>
				<li><a href="HOWTO-microsoft.htm">HOWTO view and edit Microsoft documents</a></li>
				<li><a href="HOWTO-multimedia.htm">HOWTO multimedia</a> (work with graphics, sound, video)</li>
				<li><a href="HOWTO-regexps.htm">HOWTO regular expressions</a> (what they are, how to use)</li>
				<li><a href="samba-printing.htm">HOWTO print with Samba and CUPS</a></li>
				<li><a href="../../local/petget/help.htm">HOWTO use the Puppy Package Manager</a></li>
				<li><a href="HOWTO-internationalization.htm">HOWTO Internationalization</a> (support non-English languages)</li>
				<li><a href="devx.htm">About Devx</a> The Puppy development environment</li>
				<li><a href="gtkdialog.htm">About Gtkdialog</a> The Puppy Linux GUI builder</li>
				<li><a href="root.htm">About root (administrator) and spot</a></li>
				<li><a href="forums.htm">Get more help - HOWTO Puppy Forums</a></li>
			</ul>
		</p>

Along with this manual.css:-

manual.css.tar.bz2

(880 Bytes) Downloaded 51 times

Edit #2: I have updated root.htm with the content I thought needed a place there. Here is the current file:-

root.htm.tar.bz2

(2.74 KiB) Downloaded 42 times

This was the final file from my side!!! I think other files can be updated by someone else, as I am not even close to those subjects. I will now open the Pull Request. @bigpup, @williwaw, @dimkr and others, please review it.

Here is the PR:- https://github.com/puppylinux-woof-CE/woof-CE/pull/3598

Here is the doc folder (as .tar.bz2):- https://github.com/lakshayrohila/woof-C ... ion-update

[bigpup]

@user1234

Thanks for that information. Now I understand where we are with this.

Question:
Have you put all the updated files, offered by me and williwaw, in your pull request to Woof-CE?
I had the understanding that you were putting everything together into one pull request?
Thanks for doing the pull request!!

This is not really the time to make a pull request to Woof -CE

I would like to look over everything, that has been done, and make sure we got everything.

You must have more time than I do to work on this.

It is taking me longer to review.

Other things in my life, limit my time to work on this.

This is going to take me a few days, maybe a week to look over it all.
Looking over all of this also is double checking it is all working.

I know you have done all of this with what you produced.
Bu I am the other set of eyes, to maybe see something you did not.

Note:
I see you use a different name at Woof-CE.

I have found, that using the same name you have on this forum, gets a little more respect.
They recognize the name, as someone that supports, and uses Puppy.

-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------

I am not looking for recognition for doing this, so your name on the pull request is who should be on it.

You have done the most work on this and deserve the credit!

Do not forget williwaw has been helping and we should thank he/she, very much, for their help!!

Others have posted in this topic and their input has also helped!

-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

If you see nothing wrong with my statement corrections to the installation.htm.

We need to make a new one with those changes.
I can do a new one.

Unless you want to update it, with my statement changes, while I am reviewing the other stuff

Thanks!

[user1234]

@user1234

Thanks for that information. Now I understand where we are with this.

Question:
Have you put all the updated files, offered by me and williwaw, in your pull request to Woof-CE?

This is not really the time to make a pull request to Woof -CE

I would like to look over everything, that has been done, and make sure we got everything.

You must have more time than I do to work on this.

It is taking me longer to review.

Other things in my life, limit my time to work on this.

This is going to take me a few days, maybe a week to look over it all.
Looking over all of this also is double checking it is all working.

I know you have done all of this with what you produced.
Bu I am the other set of eyes, to maybe see something you did not.

-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------

I am not looking for recognition for doing this, so your name on the pull request is who should be on it.

You have done the most work on this and deserve the credit!

Do not forget williwaw has been helping and we should thank he/she, very much, for their help!!

Others have posted in this topic and their input has also helped!

-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

If you see nothing wrong with my statement corrections to the installation.htm.

We need to make a new one with those changes.
I can do a new one.

Unless you want to update it, with my statement changes, while I am reviewing the other stuff

Thanks!

The pull request is there to be reviewed, does not depend on what time it will require to review it. Once every reviewer is satisfied with the documentation, then only will this PR be merged into the woof-CE. This PR does not contain anyone else's work, just mine. I think, it is better that you all open pull requests for your work, so that your work is recognised. But if anyone wants that I do the pull request work for you, by your name (not actually github user name though, it will be mine).

And yes, I do thank you both @bigpup and @williwaw . You both have helped a lot.

@bigpup, can you share with me the modified installation.htm, its very hard to review than to contribute . Just attach the installation.htm here and I'll add the modified content.

Edit: Yes, I'll be editing the installation.htm. will have to review what you have written, but will do it by tomorrow.

[bigpup]

I have to work on my version of the installation.htm

Will post it when I am done.

Here I am again. Life is getting in my way.

In about 30 minutes, I have to go to town, and will be gone the rest of the day, until dinner time

[bigpup]

I think it would be better to have everything in one pull request, but we can do separate ones.

It will be about 2 weeks before I will be ready to offer one for what I have done.

[bigpup]

I just looked over the cups_shell.htm

I know there is some stuff posted on this forum we could provide links to.

Those links to the old forum are OK for what they are.

However the really good posts, that where made by a certain someone, are no good anymore.
That person decided to delete all the good info in them.

[rcrsn51]

However the really good posts, that where made by a certain someone, are no good anymore.
That person decided to delete all the good info in them.

I will assume that you are talking about me. That content was unmaintained, out-of-date and irrelevant to modern Puppies. It was exactly what you would NOT want to include in new documentation.

[williwaw]

I think it would be better to have everything in one pull request, but we can do separate ones.
It will be about 2 weeks before I will be ready to offer one for what I have done.

I also have to get up to speed with Github to make a PR for index.html.bottom.
@user1234
Is forking to my own repo and merging the preferred method?

[user1234]

I think it would be better to have everything in one pull request, but we can do separate ones.
It will be about 2 weeks before I will be ready to offer one for what I have done.

I also have to get up to speed with Github to make a PR for index.html.bottom.
@user1234
Is forking to my own repo and merging the preferred method?

Of course it is. You'll have to fork woof-CE so that it is available to your own account (you cannot edit directly to puppylinux/woof-CE), edit your fork and open a PR.

[bigpup]

However the really good posts, that where made by a certain someone, are no good anymore.
That person decided to delete all the good info in them.

I will assume that you are talking about me. That content was unmaintained, out-of-date and irrelevant to modern Puppies. It was exactly what you would NOT want to include in new documentation.

You could see a lot of excellent work in those old topics!

Those old topics were very, very good.

I really wish there were some updated ones, we could point people to

I always considered rcrsn51, the expert on how to get printing working, in Puppy Linux!

[bigpup]

Right now I am taking the installation.htm and adding some more info to it.

Explaining that a frugal install is still the complete Puppy OS and a little info on why it is called frugal.

Updating some info about boot loaders.

Adding some info about the installer programs you may find in a Puppy version.
Especially the ones that can handle UEFI with secure boot enabled and what is also needed to do that.

[bigpup]

@user1234

I added what I wanted for information to the installation.htm file.

I added about Live Install, but I messed up the linking, from the listed sections at the top.

The one for Live Install and Frugal Install.

Will you please correct this linking?

I have never done this deep an edit and not sure how to do this type linking.

Here is my version:

installation.htm.zip

(6.07 KiB) Downloaded 49 times

.
Thanks for your help!

[user1234]

@user1234

I added what I wanted for information to the installation.htm file.

I added about Live Install, but I messed up the linking, from the listed sections at the top.

The one for Live Install and Frugal Install.

Will you please correct this linking?

I have never done this deep an edit and not sure how to do this type linking.

Here is my version:
installation.htm.zip
.
Thanks for your help!

I'll do it, maybe a improving the linking scheme (or whatever you call it as, I am not a professional) as well this time. Will start the work as soon as I open my laptop.

EDIT:-
@bigpup, thanks for your content. Here is the modified file-

installation.htm.tar.bz2

(5.66 KiB) Downloaded 58 times

Have also added support for color changes in references when you click either of the references. A good way of allowing the user to know where they need to look for references.

I have added this version of installation.htm to my PR, as it is related to it. Thank you for your contribution!