Fluppy 013

[jemimah]

This distro is no longer maintained. Please try Saluki instead.



Download: http://www.smokey01.com/jemimah/fluppy13
http://puppeee.com/files/fluppy13/

This is Puppeee with Eee-specific functionality removed and a full size kernel and a full Xorg with DRI, Mesa, and Nouveau.

Most of the information on the Puppeee website also pertains to Fluppy. Feel free to make use of the Puppeee forum to discuss Fluppy.

Web:http://puppeee.com/web/
Forum:http://puppeee.com/bb/

The current kernel version is 2.6.35.7. I add rfkill, preempt, usb-3, hibernate, hypertheading, runtime power management, kernel modesetting, samsung laptop, line6, and optimize for Atom processors. 3rd party drivers included are ndiswrapper, keucr, wl, rtl8192se, rt3070sta, acerhdf, tkusb, and backported brcm80211. I also add the Poulsbo backlight patch, patch the elantech driver so it can be disabled, and patch the eeepc-laptop module so the Eeepc 700 series can be overclocked.

Fluppy Features:

• -Suspend and Hibernate support (can be problematic on some hardware - so no promises at this point)
  -Acpi support including automatic power management when you plug or unplug, suspend when you shut the lid or press the sleep button, poweroff when you press the power button. (Also may or may not work depending on hardware)
  -Bluetooth Applet
  -Frisbee Network Manager
  -Midori Browser - mostly stable build with html5 video
  -Gstreamer multimedia with Parole, Xnoise, and Eina media players
  -Four Window managers: IceWM, OpenBox, Flwm, Compiz
  -Two Desktops: ROX, and LxLauncher
  -Based on 4.3.1 with many updates and bug fixes - there's not much left of 4.3.1 anymore
  -Many applications added with netbook usage in mind
  -Applications are small screen friendly
  -A wide selection of themes and a full set of gtk theme engines
  -Fully stocked control panel allows compact, easy to navigate menus

To install: Download and decompress the zip file. Copy the contents to a FAT or Ext2/3/4 formatted USB drive. Go into the boot directory, and click bootinst.sh (or bootinst.bat if you're running Windows). Alternately, you can use the BootFlash USB installer to create a blank bootable USB drive, then copy the Fluppy files to the bootable USB and it should work. Important: Do not run the bootinstaller script before you've copied it to the usb drive or you may overwrite the bootloader on your hard drive. More complete installation instructions are found on the Puppeee website. http://puppeee.com/web/download/

Package Compatibility: Fluppy should work with 4.3.1 packages with a few exceptions. Hardware drivers won't work. Also Fluppy comes with dbus, gconf, xcb, libnotify, SDL, and some other libraries not found in 4.3.1 so you should probably avoid installing pets that contain these libraries.


While the included Midori is small and fast, it's not quite bug free. I recommend downloading one of these browsers.
Chrome 10 SFS:http://puppeee.com/files/distsfs/chrome-10.sfs
Opera 11 SFS: http://puppeee.com/files/sfs/opera11.00.sfs
Firefox 3.6 SFS: http://puppeee.com/files/sfs/firefox-3.6.15.sfs
Seamonkey 2 SFS: http://puppeee.com/files/sfs/seamonkey-2.0.11.sfs

Kernel Source: http://puppeee.com/files/sources/linux- ... ed.tar.bz2
DevX: http://puppeee.com/files/puppeee4.4rc2/eee_devx_514.sfs
Note: the devx must be renamed to flp_devx_013.sfs

Printing SFS: http://puppeee.com/files/distsfs/printer-scanner-5.sfs

Compiz SFS: http://puppeee.com/files/distsfs/Compiz-0.8.6-1.sfs
Note: Compiz has only been tested with Intel graphics. The python sfs is needed for compiz configuration. The compiz sfs includes cairo dock but rox panel is the default

[01micko]

Seems to work just fine on the 701sd, of course only limited testing.. got a black square where I believe bluetooth applet should be.

The installer works great in Puppy, crap in some other linux I wonder if it's the bash version? Puppy's is quite old.

I might give the installer a test in XP.

Cheers (and I think there will be many a happy netbook owner when they discover this )

[TomRhymer]

Running on an Acer Aspire One D-150 from a flash drive. Runs very well with Pupeee.

First boot, loads up but has an odd issue with PWireless2. Normally when I run it, it shows Eth0 and WLan0. With this one, it also shows a Pan0. I have no idea what that is. I enter in my wireless info, and it connects but takes about twice as much time as usual. It keeps giving me messages about Pan0 connecting and DHCP on Pan0.

It starts up Chrome and works with a few sites, but if I try to go to either forum, it locks up Puppy.

Rebooted and got same results. Rebooted again, connected to wireless but didn't start Chrome. Shut down, saved file to flash drive. Tried to reboot to Fluppy but got boot error. Formatted flash drive and reinstalled. Started up, saved again, got boot error again.

[jemimah]

To get rid of pan0, go to the dhcp tab in pwireless2, click pan0, check ignore, then click save.

[Lobster]

What if you don't have a netbook?

It works on my desktop AND I am connected
(something I could not do with Puppeee)

Boot up and setup was straightforward and
will be familiar (well the non ISO is a bit perplexing
but if booting from keydrive - quite a good method
- even a windows setup)
Update ISO now available

I have a wired Ethernet connection
and Fluppy looks for a wireless connection

So I ran the connection wizard again
- clicked on DHCP and there was an Ethernet eth0 connect
which I was able to choose and save.

For me a non-web computer is only 10% efficient
so now I have a working Fluppy on my desktop PC
(not Atom powered - it is an AMD 64 X2)

Chrome is fast
The interface is gorgeous and makes the experience of
usage pleasurable and modern (and changeable)

Anyway just an initial bark:

Woof woof

update
I am now back in Lucid
Chrome disappeared
I mean vanished. Would not load . . .
(I had just added bookmarks)
but that should not do anything weird . . .

Did ctrl + alt + backspace
and could not run xwin

had to turn off machine and reboot
for those who like exploring this is worth trying, testing
and offering feedback
Hope the desktop running possibility continues . . .

[nooby]

Congrats Jemimah to one of the best looking puppy I've seen.

Beats both Quirky 1.00 and Lucid Puppy 5.00 with horse length in being good looking indeed.

But on AMD Dual Core there seems to be bugs to sort out.

I used pfix=ram and then used your driver pet and used xorg and did firewall and then connect which was non intuitive to me.

May I ask you to include SNS from Quirky if that is possible?

Very few newbies would know that one are expected to use DHCP to get wired LAN going.
anyway it worked and I did save the succesful connection and started up chrome.

Now the error did happen.

I had only played a local radio station audio for 2 minutes when the browser freezed everything. The only way to get out of freeze was to do a hard reboot.

Is this a Chrome issue or a Fluppy issue?

Should I test to use Xvesa instead? Or use Firefox?
Or add some cheat code?

A minor quibble.

M$ Windows force us to double click and then Linux un-teach the double click and now Fluppy force us to double click again.

[BHINTZ]

Fluppy installed just fine on a thinkpad T40.

Does ramboot work the same way on laptops as on netbooks?

If so I may be able to put off buying a battery for this machine.

I haven't tried much but it seems to be excellent

bob

[jemimah]

I think I will keep it so it can run on desktops - the only drawback is that it won't boot as fast.

Ramboot does not work at the moment, it probably will in 002.

Wired Ethernet should work with no configuration unless you need a static IP.

You can change the double click setting to single click the ROX options.

If you have trouble with Chrome please attempt to start it from the command line by typing 'google-chrome' in the terminal and reporting any error messages. It's hard for me to know what the problem is if you just tell me 'it crashes'.

Puppeee is relatively stable, and Quirky is relatively stable, but the combination of Puppeee with the Quirky kernel is untried. Especially on hardware other than EeePC.

[dawnsboy]

I am constantly playing around with Puppy. I have tested many variants on my eeepc 701 and prefer Puppeee. I wondered though if it might not be feasible to run a netbook with a specialty puplet such as Puppeee or Fluppy on my mini-itx pc. So I decided to give it a whirl.

The pc has a D201GLY2 intel motherboard with Intel 220 celeron processor and an embedded SiS Mirage graphic chipset. It also has a gig of ram. I installed a recent model SATA hard drive from an Acer laptop.

Initial thougthts

The pro's

Fluppy loaded the correct xorg configuration on initial boot. No other puppy or puplet has done that. I always have to upgrade the driver.

It is a nimble little OS on this hardware and brings up to date software to my desktop without sacrificing speed.

Openbox is a great little manager to use in conjunction with rox-panel.

Con's

Like most puppy official releases or puplets I have to add the boot parameter acpi=off to get it to boot otherwise it drops out of ram console early in the game. I have found through trial and error that puppies with the 2.6.25.16 kernel will find my SATA hard drive and boot without difficulty.

Chrome freezes. I ripped it out and installed your firefox sfs intended for Puppeee. I removed the tiny menu addon as it is not needed on this box. Firefox works very well in this environment.

Chrome will not use the gxine or xine plugins. Displays message "missing plug-in". I am thinking this must be a chrome issue as it happens in every puppy variant I have used chrome browser with. It will find and use the mplayer plug-in. No matter though because I ripped it out and installed firefox.

I really do not see why this would not be a good option for Net Top boxes. It is a fine idea to build this OS. If it turns out to be as stable as Puppeee then we have a winner. Thank you.

Here is a screen shot.

[jemimah]

Here is a potential fix to the Chrome crashing problem:

Code: Select all

mount -t tmpfs none /dev/shm

This should be be run at every bootup. I'll add it to the sysinit script in Fluppy002 and see if that sorts it.

[Lobster]

I think I will keep it so it can run on desktops - the only drawback is that it won't boot as fast.

That I can run it on a desktop will compensate for the slow booting time
and allow me to have a 'computer on USB' that eventually works across two platforms I use.

I hope the Chrome crash fix code works
I will look in on Fluppy from time to time
especially if released as an ISO


I showed Fluppy to a developer friend
yesterday and the Icewm froze and I had to reset the computer.
Sorry about not providing sufficient feedback
initially I just wanted you to know it works (sort of)
on a desktop and I can get a connection to the net (for a short while)

I am certain it is much more stable on an Atom powered netbook (as it was designed for)

[hokal]

Help needed.
I have installed Fluppy and so far I like it. I have also installed OO and installed my printers in CUPS.

I upgraded to CUPS 1.3.11 !!!

My OO finds the printers and printing is without any problem.
ALL OTHER PROGRAMS do not find any printer.

So CUPS does not tell the Fluppy programs where to find the printers ??

BTW: without upgrading CUPS to 1.3.11 all puppy programs will freeze on trying to print!

[BHINTZ]

suspend does not begin with closing lid, but does start with shutdown menu on thinkpad t40 - it comes back up quickly when opening lid or pushing power button

The fix for chrome works fine on this machine

I am looking forward to 002 and possible ramboot

bob

[jemimah]

If you manage to crash it, and can still open the terminal, or already have one open, type 'dmesg' and let me know what it says at the end.

[raffy]

Excellent - works out of the box in my Atom combo-board. (This is a US$80 board with CPU.)

Attaching logs...

[jemimah]

I've posted Fluppy 002. Hopefully the Chrome crashing problem is fixed. Ramboot should work now too.

[Lobster]

Worlds most hopeless tester here . . .
I was in the process of making a video on installing fluppy
but the bootinst.sh did not seem to work (worked OK in 001)

I ran it from the command line and output is below
I am a great believer in positivity
but has the text editor added more than you intended?

No - not the text editor - something in the code, could be this?
+ being actually added, rather than functions . . .

I'll add the complete code at the end of this post

TARGET=$(egrep "[^[:space:]]+[[:space:]]+$MYMNT[[:space:]]+" /proc/mounts | cut -d " " -f 1)
- this is a job for a chihuahua in pink goggles

Code: Select all

# ./bootinst.sh
+ set -e
+ export TARGET=
+ TARGET=
+ export MBR=
+ MBR=
+++ dirname ./bootinst.sh
++ cd -P .
++ pwd
+ export MYMNT=/initrd/mnt/dev_save/iso/fluppy/NewDir/boot
+ MYMNT=/initrd/mnt/dev_save/iso/fluppy/NewDir/boot
+ '[' /initrd/mnt/dev_save/iso/fluppy/NewDir/boot '!=' '' -a /initrd/mnt/dev_save/iso/fluppy/NewDir/boot '!=' . -a /initrd/mnt/dev_save/iso/fluppy/NewDir/boot '!=' / ']'
++ egrep '[^[:space:]]+[[:space:]]+/initrd/mnt/dev_save/iso/fluppy/NewDir/boot[[:space:]]+' /proc/mounts
++ cut -d ' ' -f 1
+ TARGET=
+ '[' '' '!=' '' ']'
++ dirname /initrd/mnt/dev_save/iso/fluppy/NewDir/boot
+ MYMNT=/initrd/mnt/dev_save/iso/fluppy/NewDir
+ '[' /initrd/mnt/dev_save/iso/fluppy/NewDir '!=' '' -a /initrd/mnt/dev_save/iso/fluppy/NewDir '!=' . -a /initrd/mnt/dev_save/iso/fluppy/NewDir '!=' / ']'
++ egrep '[^[:space:]]+[[:space:]]+/initrd/mnt/dev_save/iso/fluppy/NewDir[[:space:]]+' /proc/mounts
++ cut -d ' ' -f 1
+ TARGET=
+ '[' '' '!=' '' ']'
++ dirname /initrd/mnt/dev_save/iso/fluppy/NewDir
+ MYMNT=/initrd/mnt/dev_save/iso/fluppy
+ '[' /initrd/mnt/dev_save/iso/fluppy '!=' '' -a /initrd/mnt/dev_save/iso/fluppy '!=' . -a /initrd/mnt/dev_save/iso/fluppy '!=' / ']'
++ egrep '[^[:space:]]+[[:space:]]+/initrd/mnt/dev_save/iso/fluppy[[:space:]]+' /proc/mounts
++ cut -d ' ' -f 1
+ TARGET=
+ '[' '' '!=' '' ']'
++ dirname /initrd/mnt/dev_save/iso/fluppy
+ MYMNT=/initrd/mnt/dev_save/iso
+ '[' /initrd/mnt/dev_save/iso '!=' '' -a /initrd/mnt/dev_save/iso '!=' . -a /initrd/mnt/dev_save/iso '!=' / ']'
++ egrep '[^[:space:]]+[[:space:]]+/initrd/mnt/dev_save/iso[[:space:]]+' /proc/mounts
++ cut -d ' ' -f 1
+ TARGET=
+ '[' '' '!=' '' ']'
++ dirname /initrd/mnt/dev_save/iso
+ MYMNT=/initrd/mnt/dev_save
+ '[' /initrd/mnt/dev_save '!=' '' -a /initrd/mnt/dev_save '!=' . -a /initrd/mnt/dev_save '!=' / ']'
++ egrep '[^[:space:]]+[[:space:]]+/initrd/mnt/dev_save[[:space:]]+' /proc/mounts
++ cut -d ' ' -f 1
+ TARGET=/dev/sda5
+ '[' /dev/sda5 '!=' '' ']'
+ break
+ '[' /dev/sda5 = '' ']'
++ cat /proc/mounts
++ grep noexec
++ grep '^/dev/sda5'
+ '[' '' ']'
++ echo /dev/sda5
++ sed -r 's/[0-9]+$//g'
+ export MBR=/dev/sda
+ MBR=/dev/sda
+ export NUM=5
+ NUM=5
+ cd /initrd/mnt/dev_save
+ which xterm
/usr/bin/xterm
+ [[ 0 != 0 ]]
+ which xterm
/usr/bin/xterm
+ [[ 0 = 0 ]]
+ xterm -e boot/syslinux/linuxinstall.sh
+ exit
# 

Code: Select all

#!/bin/bash
set -x
set -e
export TARGET=""
export MBR=""

# Find out which partition or disk are we using
export MYMNT=$(cd -P $(dirname $0) ; pwd)
while [ "$MYMNT" != "" -a "$MYMNT" != "." -a "$MYMNT" != "/" ]; do
   TARGET=$(egrep "[^[:space:]]+[[:space:]]+$MYMNT[[:space:]]+" /proc/mounts | cut -d " " -f 1)
   if [ "$TARGET" != "" ]; then break; fi
   MYMNT=$(dirname "$MYMNT")
done

if [ "$TARGET" = "" ]; then
   echo "Can't find device to install to."
   echo "Make sure you run this script from a mounted device."
   exit 1

fi

if [ "$(cat /proc/mounts | grep "^$TARGET" | grep noexec)" ]; then
   echo "The disk $TARGET is mounted with noexec parameter, trying to remount..."
   mount -o remount,exec "$TARGET"
fi

export MBR=$(echo "$TARGET" | sed -r "s/[0-9]+\$//g")
export NUM=${TARGET:${#MBR}}
cd "$MYMNT"

which $TERM
if [[ $? != 0 ]] ; then
	which xterm
	if [[ $? = 0 ]] ; then
		TERM=xterm
	else
		which konsole
		if [[ $? = 0 ]] ; then
			TERM=konsole
		else
			which rxvt
			if [[ $? = 0 ]] ; then
				TERM=rxvt
			fi
		fi
	fi
fi
which $TERM
if [[ $? = 0 ]] ; then
	$TERM -e boot/syslinux/linuxinstall.sh
	exit
fi

clear
echo "-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-"
echo "                        Welcome to Fluppy boot installer                         "
echo "-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-"
echo
echo "This installer will setup disk $TARGET to boot only Fluppy."
if [ "$MBR" != "$TARGET" ]; then
   echo
   echo "Warning! Master boot record (MBR) of $MBR will be overwritten."
   echo "If you use $MBR to boot any existing operating system, it will not work"
   echo "anymore. Only Fluppy will boot from this device. Be careful!"
fi
echo
echo "Press Enter to continue, or Ctrl+C to abort..."
read junk
clear

echo "Flushing filesystem buffers, this may take a while..."
sync

# setup MBR if the device is not in superfloppy format
if [ "$MBR" != "$TARGET" ]; then
   echo "Setting up MBR on $MBR..."
   ./boot/syslinux/lilo -S /dev/null -M $MBR ext # this must be here to support -A for extended partitions
   echo "Activating partition $TARGET..."
   ./boot/syslinux/lilo -S /dev/null -A $MBR $NUM
   echo "Updating MBR on $MBR..." # this must be here because LILO mbr is bad. mbr.bin is from syslinux
   cat ./boot/syslinux/mbr.bin > $MBR
fi

echo "Setting up boot record for $TARGET..."
./boot/syslinux/syslinux -d . $TARGET

echo "Disk $TARGET should be bootable now. Installation finished."

echo
echo "Read the information above and then press any key to exit..."
read junk

[jemimah]

I don't think you copied the files to the usb drive before running the installer script.

[Lobster]

Worlds most hopeless tester here . . .

Thanks Jemimah

[jemimah]

You should make sure you didn't wack the bootloader on your hard drive.