(old)Puppy Linux Discussion Forum

stemsee wrote:Boot code to mount main sfs, not copytoram?

Open initrd.xz and in ./init-tree/etc, open BOOTCONFIG and remove 'yes' from line 4: Or run script (just click) from iso image, 'BOOTCONFIG-editor' -- save and exit.
done.
May have to do this in your save file as well.
Then in your boot menu, remove 'copy' from pfix or append. That should do it.
sfs files will mount during bootup unless you exercise the option (ram or mount) from the console during bootup.
If you're just running from a save file or save-to-partition, you can also do this from the boot manager.
This should apply to the main sfs as well as additional sfs modules.

df

Doesn't work! Main file persistently copies to ram. I negated every instance in the init. There is some code for forcing copy2ram when more than 256mb ram is detected I think that is overriding everything else.

COPYEXTRASFS* gets asked during boot anyway and copies or mounts depending on input, so that is ok.

I presume you've tried "pfix=nocopy" ("pfix=noram" is suppose to be the same).
In either case the base file is mounted at /initrd/mnt/tempfs.
Be that as it may, the initrd and init script still needs work, something I've been attempting with great difficulty. As well, event manager doesn't work as it suggests as far as the save dialog on shutdown under pupmode=12. For the time being, I've opted for noautosave, where copy-to-ram seems to make more sense.

df

yep tried each/both ... !

New iso uploaded (v. JL64-703). see o/p

If you have a save file (or save to partion), the first boot of your save session now correctly runs boot manager when x starts. The bottom of the last dialog box (push sfs) gives the option of ram or mount for future boots. This can be changed later.

df

pet to remove non-functional 'fido' (spot is non-root login account)
also some minor fixes.
re-uploaded Devx & 2_plasma5.

Hi D F,

Tested the new iso, it boots ok BUT when I add pkeys=be it stalls and give me some can't conclude with TTY bs.

With us keyboard all is fine BUT internet : nada.

Great week-end all.

E Z

update to Wifi-Connection-Suite

Thanks Stemsee. On the sfs, move /sbin and /share to /usr. May need to first. I inadvertently removed '/opt/local/etc/oui.txt' in the remaster. Is that still necessary in the new iteration of wifi-connect? I'll get it back if it is. There is a oui.txt in /usr/share (link to hwdata) from slackware already. Also, a pet will overwrite the application files. Otherwise, wifi-connect points to wifi-connect-2.

Eztuxr, I couldn't replicate your pkeys issue. Tried 'pkeys=be' after vmlinuz in grub ram and with savefile and got "loadkeys be-latin1" in both cases. Booted fine with new keyboard. It might be that you used a savefile from a previous iteration? Or, as happens occassionally, it was just a startup glitch which will disappear next try.

df

ps., I'll take a look at what I've dove to dhcp. It may involve removing frisbee altogether if this is going to be an ongoing issue. Might have to break down and buy a wifi dongle to test it. As it is, all I've done with wifi is as a deaf and blind man posing as a train-spotter.

O yeah, oui.txt is for the random mac generator which uses 29,000 real world company mac address prefixes. Thanks for pointing that out, I will repackage.

wifi-connect-2 is obsolete, as Wifi-Connect now allows interface selection first. All the scripts do. Wifi-Scanner-2 behaves a little differently to Wifi-Scanner so I left them both in.

Quite a few bugs and improvements, particularly with Wifi-Connect now showing key on or off and AP mac addresses.

Wifi-HotSpot uses create_ap (included /usr/sbin/create_ap/*) which gets compiled on first use so devx must be loaded or dev libraries installed/loaded.

As the name implies, this is an experimental delta file to be applied to JL64-703.sfs (NOT the iso)...
experimental-base-delta.tar.gz (14M)
CHANGES:

• installed upd-JL64-1.pet
  removed all frisbee
  added (replaced) rc.network (etc) from BarryK's Easy
  added sns (simple-network-setup) and (replaced) connection-wizard (from same)
  reinstalled dhcpd
  removed wifi-connect...JL64
  added wifi-connect-2017

works fine for me (eth0 only) but a bit verbose

df

Uploaded JL64-703v2.iso 412M See o/p for link
md5sum: b356890125faaab47a41222b019f6ead

A little fix to pupver ('ver') which was loading xfce4-panel (line 32 should say xfce4-panel.bin):

some new pets uploaded:

EDIT: whoops! That's my address!

JL64-704
Probably the last in this series. See opening post

df

Dry Falls:

I tried downloading the iso three times and it failed each time.
Could you check and see if you could fix it.

Hi Pete22

Not sure what the problem is, but I just downloaded the iso with midori (there goes half my monthly sattelite quota!). No problem. mdsum checks out: 81c3d04098d3b39d66ce5101b9c3dda9 JL64-704.iso

You might also try http://just-lighthouse.000webhostapp.com/. Still goes to gdrive. That's the bummer!

I've fixed the problem with the new rc.network file but it's not quite ready for release. Till the next release (JL64-705), which is an alpha release based on slackware64-current, if the machine doesn;t auto-connect eth0 at first boot, just have to hit the connect button. I tested JL64-704 on a borrowed laptop and wifi worked without a hitch.

By the way, xfce now comes with cairo doc. I want to make Xfce the default desktop in 705. Still a few bugs to work out.

Thanks for your interest.

it occurred to me that I could download the iso because I was logged in. Seems they've changed the way google links your files. Here's the new "sharable" link:

https://drive.google.com/file/d/0B-9zDf ... sp=sharing

will change the link in the opening post now. Sorry for the confusion.

df

You can present the link shorter btw

https://drive.google.com/file/d/0B-9zDf ... Gx5YTBFY28

Thanks to Dry Falls and stemsee for helping me get JL to download.

Now I am trying to do a fugal install. However, Grub4dos does not see Just-Lightouse. Any ideas.

Pete22

PS I figured it out.