Just-Lighthouse64-603/604

[edoc]

Headed to bed early ...

The libevent ... appeared to run fine.

The first sfs delta I tried generated this:

xdelta3: using default output filename: /mnt/home/jl64-603g/orig/JL64-603g.sfs
xdelta3: using default source filename: /mnt/home/jl64-603g/orig/JL64-603g.sfs
xdelta3: source /mnt/home/jl64-603g/orig/JL64-603g.sfs winsize 64 MB size 281604096
xdelta3: to overwrite output file specify -f: /mnt/home/jl64-603g/orig/JL64-603g.sfs

Press Enter or close this window to continue.

I tried creating a folder "orig" and putting a copy of the sfs in there with the delta.

It's still unclear to me how this is supposed to work.

Why doesn't it just create a second updated version of the sfs right where it is, with a slightly different name, then the user can manually swap the new for the old?

[Dry Falls]

Why doesn't it just create a second updated version of the sfs right where it is, with a slightly different name, then the user can manually swap the new for the old?

Well, it was a toss up. placing the delta file in the same folder as the original, then clicking the delta works fine if the original and new have different names. And I've never had much luck overwriting the original with a delta patch. So I create two directories (orig, new) and open both. Original files in the first and patches in the second. Rather than clicking the delta, I go to menu/utilities/Xdelta file difference manager. Then drag the original in the top box and the delta in the one below it. It generates a new file next to the delta patch in the new folder. No need for renaming, and especially, no confusion as to which one is which. I suppose there could be a better argument for the other method, but this is how I do it. I get confused too easily.

[edoc]

Apparently I'm even more easily confused!

I'll try this again when I get home from work later.

Thanks.

[gcmartin]

Netbooting in JLH, versus LH64, has a problem where it is not providing service to PC on the LAN who need boot service. In LH64 netbooting operation proceed as expected and remote PC can boot. But, JLH appears unable to get to the point of properly awaiting remote boot request in spite of the appearance of the Debug window on the desktop to observe PCs requesting boot service.

It occurs to me that I should probably boot the LH DVD and create the Netboot TFTPboot library on permanent media testing a PXE boot.
Then, boot the JLH DVD, link the TFTPboot folder to /root and start the DNSMASQ server manually using the same parms as shown in the netboot script.

If this affords the PXE PC to boot, then the problem is the script. If not, then its something in DNSMASQ on JLH.

I will try tomorrow when I return home.

[edoc]

Taking a break from mowing in 90F weather ...

Where do I find the sysd ... kd4 ... and devextra ... files to copy into "orig", please?

I have the jl64 ... already in there and the four delta's in "new".

Just call me paint-by-numbers.

Thanks ...

[Dry Falls]

Where do I find the sysd ... kd4 ... and devextra ... files to copy into "orig"

look on iso. If you frugal installed, drag them there.

Netbooting in JLH, versus LH64, has a problem where it is not providing service to PC on the LAN who need boot service.

It's the same with either/any dnsmasq. Mount L64-602b and chroot. It works. The script is the same in both. I made an sfs of lib64 from LH64 and it makes no difference, so I suspect it's not a missing library file. It's not the kernel because it works in LH64-602b running with k4.0.1. Either busybox makes no difference. Taking everything in account, the only other difference than glib/gcc is eudev. If this is the case, an old JLH64 (prior to installing eudev) should work. I'll give that a try.

df

[edoc]

Where do I find the sysd ... kd4 ... and devextra ... files to copy into "orig"

look on iso. If you frugal installed, drag them there.

Drag them into the jl64-603g folder where the frugal install files are or where the iso is?

Does it compare to the files inside the iso then replace them wherever the install placed them?

[Dry Falls]

drag them from the iso to where the frugal install is. Xdelta will use these to apply the patch. I'd drag them to the orig folder, then replace the new generated files (in 'new') with the ones where your frugal or save file is (or in the root/top of the partition/drive).

As for netboot, it's a eudev thing. Works fine with JL64-602 dated April 25, just prior to installing eudev. Works with k3.28.8 and k4.0.1. We need a work-around for eudev if that is possible. I'm not going to revert to udev because, as far as I'm concerned, it's a drag, and in fact, the whole system drags with udev + systemd.

df

[gcmartin]

Netboot issue: Thanks for understanding where the problem lies. With the splintering that has occurred, I am sure that much will be of issue as this competitive relations between the 2 groups exist. This is not the first, nor the last, that we have seen or will see in the technology arena.

Thanks for your findings @Dry Falls! Saving much anguish in nailing this ability.

Looks like there will need to be a new direction for either DNSMASQ or JLH low level if this service will continue for users of the distro.

[edoc]

OK, finally sorted out the delta update process & ran them.

Copied the delta-updated three over the originals ones in the boot folder.

Then went to Menu - Setup - Bootmanager and added the three new SFS files.

Rebooted.

Looks much better.

Opened Konqueror OK.

Tried "localhost:631" for CUPS which partially worked but was unresponsive when Manage Printers, Find New Printers, etc. buttons selected.

Closed Konqueror and opened CUPS from Menu & it defaulted to IceCat.

Same buttons were responsive but it doesn't Find the printer connected via USB (it's working via the old version of JL64).

NOTE: This is on a Samsung NB30 Netbook - I should be able to test on a true laptop (Dell D630) tomorrow - just to eliminate something odd about the hardware.

[Dry Falls]

Looks like there will need to be a new direction for either DNSMASQ or JLH low level if this service will continue for users of the distro.

But I still think it should work with some experimenting with dnsmasq.conf. Here is an example dnsmasq.conf.netboot from fatdog (with dnsmasq-2.7):

Code: Select all

##### Configuration file for dnsmasq #####
#
# Sample configuration for BIOS net-booting (PXE booting).
# It is a replacement of the original netboot-server used in earlier version
# of Fatdog.
#
# This sample setting will work for VirtualBox using "Host-only" network.
# Watch for *** CHANGE THIS *** comment and change them accordingly.
# 

# *** CHANGE THIS ***
# Network interface to listen to. 
# Or just comment out the line to listen to all interfaces.
interface=vboxnet0

# Only bind to the specified IP and interface above.
# This allows multiple dnsmasq to run at the same time.
bind-interfaces

# Disable DNS - we don't need it.
port=0

# Map PXEClient vendor-class to PXE tag - we will use the PXE tag later.
dhcp-vendorclass=set:PXE,PXEClient

# Set notPXE tag if it PXE tag isn't set.
tag-if=set:notPXE,tag:!PXE

# Don't service DHCP request if not from PXE client.
dhcp-ignore=tag:notPXE

# *** CHANGE THIS ***
# Range of IP address to be allocated for DHCP requests.
# Ensure it is in the same subnet as the IP of the specified interface above.
# (VirtualBox "Host-only" network IP is 192.168.56.xxx by default).
dhcp-range=tag:PXE,192.168.56.200,192.168.56.210

# No need to test whether DHCP address to be allocated is already used.
no-ping

# Filename of bootloader.
dhcp-boot=pxelinux.0

# Commands to send back to pxelinux: 208 is magic, 209 is config filename, 
# 210 is path-prefix, 211 is reboot-time (in seconds) in case of failure.
dhcp-option-force=tag:PXE,208,F1:00:74:7E
dhcp-option-force=tag:PXE,209,"default"
dhcp-option-force=tag:PXE,210,"pxelinux.cfg/"
dhcp-option-force=tag:PXE,211,30

# Enable TFTP server - PXE boot uses TFTP.
enable-tftp

# *** CHANGE THIS ***
# Root directory of files that will be served by the TFTP server.
# It doesn't exist by default, so create symlink to the real path.
#
# In the actual directory.put pxelinux.0, create pxelinux.cfg directory, and
# create pxelinux.cfg/default config file (filenames specified earlier).
#
tftp-root=/var/lib/tftp

As it is in JL64, almost everything in dnsmasq is commented out.

df

[gcmartin]

Forum hiccup and double posted! This browser error report in a frontend to double post. The correct response to this screen is to: EXIT it! Do not resend! No matter if you have posted in a thread/PMs.

I think this is a problem with the forum's support site (and/or software release level in handling site volumes).

[gcmartin]

I am using Just-Lighthouse (JLH), BUT, this problem seems to be more a general problem than specific.

I have, again, a problem where 603g too, will not boot on my Acer BIOS X2 PC w/2GB RAM,where it boots fine on a Dell BIOS P4 w/1GB. The boot message is the same "..... L64-603g.sfs not found" when booting on the X2???

On Dell, speed is good, access to Internet is good, apps working, stable. I expect to add more RAM to this configuration in the future. Currently it reports

Code: Select all

bash-4.2# free
             total         used         free       shared      buffers
Mem:       1005340       924360        80980       395012        70832
-/+ buffers:             853528       151812
Swap:      4290556       179920      4110636

bash-4.2# uname -a
Linux JLH603g-Dell1GB 4.0.1-JL-64 #1 SMP Sat May 2 11:23:52 PDT 2015 x86_64 Intel(R) Pentium(R) 4 CPU 3.06GHz GenuineIntel GNU/Linux

Questions

1. Can the X2 problem be explained?
2. Is there a boot-time parm that can be suggested to be used when booting this distro on the X2s?
3. Anyone else notice this, as it has happened to me on last several releases?(Never occurred on LH or early versions of JLH)

Ideas?

[Dry Falls]

Code: Select all

L64-603g.sfs not found

means pmedia=cd was not invoked, if you are booting from a cd/dvd. Use boot menu 3 (4 for usb). Otherwise, init will look for the base file on the harddrive or partition. No pmedia=* assumes a frugal instal. pfix=ram (menu 2) is not going to make it on all machines/bios-firmware. If you've gotten as far as you have, you don't have to worry about bootability. Remember, the pmedia boot parameter is a "helper" for stubborn machines. It's not always necessary, as on your other boxes, you've gotten by with bootmenu 2. Also, make sure there are no other grub or isolinux cfg files on your drive, as they will be loaded to boot from. just rename them for the time being.

[edoc]

Power supply arrived so I switched the HDD to the Dell D630 laptop & booted.

Need to modify the desktop settings some for less clutter - my wife doesn't care about most of that data - but looks good otherwise.

I got the Wine error message during boot - which also referenced "no 32-bit" something -
might that be causing the CUPS failure?

I'll see if I can add the zWine SFS, reboot, and test CUPS again ...

[edoc]

Follow-up ...

zWine doesn't show up in BootManager SFS.

I tried both with the "g" and without it.

I tried SFS boot on the fly and that didn't appear to work either.

I appear to have two versions of zWine on my HDD, a 1.5xxx and a 1.7xxx version.

BTW: CUPS allows me to click Add Printer after the manual setup (Find New Printers still comes up empty) but there's nothing there in Administration. I did have to use a printer driver located in /usr/share/ppd/ rather than in /mnt/home/savedownloads/ to get that far.

[Dry Falls]

I appear to have two versions of zWine on my HDD, a 1.5xxx and a 1.7xxx version.

Addons prefaced with 'z' load automatically and in a different fashion than other addons. In a frugal install, it has to be located in the same directory as your base file. Having two is probably going to really confound things. Trying out a new JL64 version should probably not use a pre-existing save-file or addons associated with an earlier version if they have been changed (move the old ones elsewhere -- a mdsum check will tell you if they are changed). As for cups, I'd recommend reading through the extensive documentation provided. You may need to run with the 'documentation.sfs' for cups html ui to work properly. I'll have to fix that oversight for the next release. If you have the devx, you can use system-config-printer.

df

edit. No, documentation.sfs is not necessary to run cups html interface. You may have a unique printer from those represented in the cups data base and would need to install its drivers separately. But first I'd go through the cups documentation.

[mikeslr]

Hi edoc:

I got the Wine error message during boot - which also referenced "no 32-bit" something -
might that be causing the CUPS failure?

I'll see if I can add the zWine SFS, reboot, and test CUPS again ...

See my post: http://murga-linux.com/puppy/viewtopic. ... 303#837303. The short version is that zWine adds not only Wine but 32-bit compatibility. Since I use shinobar's Wine-portable, I wanted the latter without the former. So I used James Bond's 32-bit compatibility SFS, renaming it to zWine-1.5.28-i486_602.sfs. Link to 32-bit compatibility SFS on that post.

To accomplish the same with JustLightHouse 603g, I renamed the compatibility SFS to zWine-1.7.23-i486_603g.sfs.

Dry Fall's advice that "Addons prefaced with 'z' load automatically and in a different fashion than other addons" suggests that it may not have been necessary that I renamed the 32-bit compatibility SFS to exactly match the zWine I was replacing. Will test the next time I setup JustLightHouse.

mikesLr

[gcmartin]

Thanks @Dry Falls.

No change on X2 boots
The pfix and pmedia parms you suggest already exists in the bootmanager selections. But, NO pfix option changes or pmedia changes affect the problem. JLH as it currently exists, will NOT boot on my 2 X2s, where this was not a problem in LH.

Just an FYI as I'll continue LH on the X2 which is used to Netboot to test certain distros on various PCs.

Wondering if this has anything to do with eudev as pointing out relating to the Netboot problem. Is there any possibility that the 2 are related to the same contributor?

If there is a JLH distro, you have, which you know gets around the 2 issues, please suggest. Or if there are other boot steps you want me to take, I will.

[edoc]

I sat still & watched the complete boot-up and observed zWine...SFS being located.

I do have it in the same folder as the Frugal files, and other SFS files, for JL64-503g.