It is OK, the USB stick will boot from either. It has syslinux installed for legacy BIOS machines, and refind for UEFI machines.Billtoo wrote: The bios in this pc shows all UEFI and Legacy bootable devices on the
same screen, the bios on the laptop just showed Legacy devices but it
booted from that, should have turned off Legacy?
Thanks.
Thanks for persevering. I will go through it again and test all the steps.don570 wrote:I tried the connect button to set up firewall and samba but still couldn't
make a server.
If running from a USB drive, min would be 2GB, but recommend 8GB min for ongoing usability. Ref:kuman11 wrote:BarryK,
What are the min requirements for installing an Easy OS?
as it uses Ubuntu DEBs.
Code: Select all
image/bmp=eog.desktop
image/gif=eog.desktop
image/jpeg=eog.desktop
image/jpg=eog.desktop
image/pjpeg=eog.desktop
image/png=eog.desktop
image/svg+xml=eog.desktop
image/tiff=eog.desktop
Code: Select all
# ./blender
AL lib: (EE) UpdateDeviceParams: Failed to set 44100hz, got 48000hz instead
Error! Blender requires OpenGL 2.1 to run. Try updating your drivers.
# Hi Sage,Sage wrote:Good to see you back, rerwin, and thanks for the heads-up on problems with wired networks. So few following now that it's difficult to get good advice! Suspect most punters just head for the hills...
Thanks for that comment, Bill. I have never, ever managed to connect with Frisbee on legions of systems since it was first announced. Apart from being unnecessarily complicated, I wonder whether it has something to do with UK being on PoA rather than PoE like RoW? Ignorance usually wins out in my case, though. IMHO these compact distro need to be (small!), fast, simple, universal and foolproof! Failing on any aspect is failure, surely?! Chasing apps that major releases do well misses the point.I connect to the wired network with Frisbee
Hi Sage,Sage wrote:Thanks for that comment, Bill. I have never, ever managed to connect with Frisbee on legions of systems since it was first announced. Apart from being unnecessarily complicated, I wonder whether it has something to do with UK being on PoA rather than PoE like RoW? Ignorance usually wins out in my case, though. IMHO these compact distro need to be (small!), fast, simple, universal and foolproof! Failing on any aspect is failure, surely?! Chasing apps that major releases do well misses the point.I connect to the wired network with Frisbee
Good.don570 wrote:3) To my surprise Samba server went smoothly.
I ticked off all the options except printer and didn't choose advanced.
Also I didn't even set up a samba user i.e. no smbpasswd -a was used.
My other computer saw the server, no problem.
richard,rerwin wrote:Barry,
With recent Puppies and Easy, I have encountered issues with the detection and connection of wired and wireless network interfaces. I have been working on solutions for the puppies and have now developed changes to rc.network_eth and the SNS rc.network for Easy and (probably) related distros. Running Easy Xerus64 0.6.8 from a USB flash drive, the following fixes work on my old 2008-BIOS Compaq Presario SR5413WM with a 64-bit AMD uniprocessor. I provide them here for your consideration.
The main problem is the slow starting of the network devices during boot-up, which necessitates increasing loop counts to wait up to 20 seconds, mainly for driver loading. My PC needs 12-18 seconds I have seen cases with both Easy and Xenialpup where dhcpcd does not appear to change resolv.conf (judging from the "MODTIME" values) even though a connection can be made if resolv.conf contains nameserver data (by ignoring the MODTIME test); clearing resolv.conf during initialization (in network_default_connect) and changing the MODTIME comparison logic seems to handle that special case.
Although I have yet to see an instance (with the change) of the MODTIME not changing, that might be because clearing of the resolv.conf content could force an initial update.
Also, adding a timeout value for dhcpcd seems to improve chances of success in connecting -- I assume that delays the return from dhcpcd, allowing more time for the resolv.conf update.
I also found that rc.network_eth does not find the wired ethernet device because it is a "bridge" ([0680]) instead of a controller ([0200]); I add a check for the bridge as long as it has "Ethernet" in its name (from lspci -nn).
Attached are difference listings and the updated scripts, as well as a hardware summary of my PC. The tarball should probably be extracted to /tmp or "home". For anyone desiring to test with the scripts, they should be installed as follows:Richard
- network_default_connect ==> /usr/sbin
rc.network ==> /usr/local/simple_network_setup
rc.network_eth ==> /etc/rc.d
rerwin,rerwin wrote:The main problem is the slow starting of the network devices during boot-up, which necessitates increasing loop counts to wait up to 20 seconds, mainly for driver loading. My PC needs 12-18 seconds I have seen cases with both Easy and Xenialpup where dhcpcd does not appear to change resolv.conf (judging from the "MODTIME" values) even though a connection can be made if resolv.conf contains nameserver data (by ignoring the MODTIME test); clearing resolv.conf during initialization (in network_default_connect) and changing the MODTIME comparison logic seems to handle that special case.
Although I have yet to see an instance (with the change) of the MODTIME not changing, that might be because clearing of the resolv.conf content could force an initial update.
Also, adding a timeout value for dhcpcd seems to improve chances of success in connecting -- I assume that delays the return from dhcpcd, allowing more time for the resolv.conf update.
Code: Select all
DHCPCDFIX="-I ''"
#180108 use inotifywait to query resolv.conf...
inotifywait -t 30 -q -e modify /etc/resolv.conf & #weird, -d (daemonize) does not work)
inPID="$!"
dhcpcd $DHCPCDFIX $INTERFACE
wait $inPID
if grep '^nameserver' /etc/resolv.conf >/dev/null; then
echo "$INTERFACE" > /tmp/sns_interface_success
exit #success.
else
ifconfig $INTERFACE down
dhcpcd --release $INTERFACE 2>/dev/null
ip route flush dev $INTERFACE
fi