pup-430-small.iso

There seem to be some satisfied customers using the "small" live-CD. If 96MB can be considered small. The full build is 105MB.

The small build is supposed to hve enough drivers to satisfy "95%" of users. If there is some really important driver missing, that is in the full build, let me know.

I don't want the small build to creep up in size though, adding less-commonly-required modules, I would rather identify more that can be taken out.

So the reverse applies, if you can see a module or group of modules that you reckon 95% of users will not need, let me know.

I would like to see if I can drive that 96MB even lower.

---

Comments

a small bug
Username: puppylinux
I found a bug??? I boot from the puppy-430-small.iso from cd when I right click the icon on the desktop,it like this: [img]http://puppy.cnbits.com/sites/default/files/editors/%E6%97%A0%E7%BA%BF%E7%94%B5%E5%AD%90/bug1.jpg[/img] And when I right click on the file in the "/",is like this : [img]http://puppy.cnbits.com/sites/default/files/editors/%E6%97%A0%E7%BA%BF%E7%94%B5%E5%AD%90/bug2.jpg[/img] what's wrong?

Viewnior
Username: panzerpuppy
"BarryK,you may want to upgrade Viewnior to v0.7. Here's what the author says about v0.7 and the cropping function: I will be brief. The project was started with "simple and fast" in mind. Cropping functionality in the last (0.7) release is the only and ,I assure you, the last exception. No image editing or photo management tools will be implemented, nor that "ultra mega giga fancy" functionality you may want. If you really hate the cropping functionality of v0.7, you can contact the author and tell him to add a compile-time switch for disabling the cropping functionality.

Mexican or Spanish
Username: filipo
"One of the funniest bugs in last version of Puppy Linux is the selection of language. if "en" is English "en-us" is American English, "fr" is Françsoise the use of "es" is Español. In latin america they speak diferent versions of Spanish because the origin of the language is form Spain, and started to spoke in latin america in 1492(see Christobal Columbus in wikipedia). In Spain we speak "Castellano" a variation of Spanish which Spaniards thing that it's exactly equal to Spanish. Outside Spain everybody call it Spanish. I know that these days in Mexican schools they try to explain to children that 1492 "discover of America" never happen or if happen was the worst thing of the world. And try to promote the hate against Spain. Ok, that it's politic not linux. You can put Mexican (derivated of Spanish) language for (es-mx). That's correct. But put Mexican (es) or Mexican (es-eu) for Spain Country... is the most ironic things. In Spain we don't speak Mexican. If the Aztecs will discover Europe in 1492 can be happen, but that didn't happen in this dimension. It seems like if you start to say that in UK the speak "Americanish" language. or in Portugal they speak "Brazilian".

karmic upup 430
Username: smil99
"Hi Barry, The excitement continues.‭ ‬I just built a karmic based upup using woof-20090917‭ ‬built system (typing from it).‭ ‬Most of the programmes work out of the box - network, gxine, inkscape, etc.‭ Another joy: a self-compiled go-office-3.1.pet also works flawlessly.‭ ‬Previous woof builds based on earlier kernel‭s ‬resulted in total freeze of X when I tried to open go-office. ‬ Other observations: 1. Abiword crashes upon print command if I start it from the desktop icon or menu.‭ However, print works fine if I initially click an existing file (eg, a doc file). 2. I had to install cups 1.3.10uj.pet before print could work. 3. 4. /temp/xerrs.log reports the following errors/failures: (EE) Failed to load module "freetype" (module does not exist, 0) (EE) Failed to load module "xtrap" (module does not exist, 0) WARNING: Deprecated config file /etc/modprobe.conf, all config files belong into /etc/modprobe.d/. (EE) [drm] drmOpen failed. (EE) CHROME(0): [dri] DRIScreenInit failed. Disabling DRI. Freed 12587008 (pool 1) (EE) config/hal: NewInputDeviceRequest failed (8) (EE) config/hal: NewInputDeviceRequest failed (8) (EE) config/hal: NewInputDeviceRequest failed (8) can not set locale properly (process:5099): Gdk-WARNING **: locale not supported by C library (process:8203): Gtk-WARNING **: Locale not supported by C library. Using the fallback 'C' locale. I am sure my lack of deeper technical knowledge when it comes to the inner tweakings of puppy is a hindrance to solving above problems. I would therefore wait to get some directions from you as to how to clear them. I also hope this will rekindle your desire to continue with the development of the upup series. Thanks as always. smil99

karmic upup430 correction
Username: smil99
"Please ignore all the strange &#8237 strings in the above post. I wrote it in abiword and copied/pasted in here. I guess those are remnants of abiword formatting. smil99.

a small bug
Username: charlie6
"@ puppylinux Hi, currently run pup-430-small from live-cd: did not notice any trouble - when right cliking as you did everything is normal.

kernel panic
Username: charlie6
"Hi, on Medion PIII laptop 600MHz 192 MBRam I attempted to do a frugal install on a ext3 partition (as I am used to do on other computers...) and got this at boot after install from fresh live-cd. Tryed several times with reformat of partitions...no change. [code]Loading drivers needed to access disk drives ....done Searching for puppy files in computer disk drives...done Loading the 'pup-430.sfs' main file ... done Setting up the layered file system... done Performing a 'switch-root' to the layered filesystem ...Kernel panic - not syncing: Atempted to kill init![/code] The same install with the former pup424 gave no problem instead (except the fixed grub problem). Cheers Charlie

kernel panic
Username: charlie6
"Hi, on Medion PIII laptop 600MHz 192 MBRam I attempted to do a frugal install on a ext3 partition (as I am used to do on other computers...) and got this at boot after install from fresh live-cd. Tryed several times with reformat of partitions...no change. [code]Loading drivers needed to access disk drives ....done Searching for puppy files in computer disk drives...done Loading the 'pup-430.sfs' main file ... done Setting up the layered file system... done Performing a 'switch-root' to the layered filesystem ...Kernel panic - not syncing: Atempted to kill init![/code] The same install with the former pup424 gave no problem instead (except the fixed grub problem). Cheers Charlie

kernel panic issue
Username: Marc
"I have the same problem as Charlie, except without the kernel panic. I am currently laboring under the assumption that this layered file system is a DFMS enacted by some sort of root or bootkit. I didn't enact any layered file system, and immediately before loading Puppy, had run Darik's Boot And Nuke. So provided that Puppy does not expressly employ a layered file system, it's safe to assume that Charlie and I are not "using" purely Puppy... --does that seem correct? ... in which case--to address Charlie's issue--you've got another issue to contend with, probably outside the scope of this blog?

Old thread
Username: BarryK
"marc, You are posting to a very old blog thread, 2009, Puppy 4.x. What Puppy are you using? What, exactly is the problem you are experiencing? If you are using an old 4.x Puppy, then I am not supporting that.

lupu-528 Kernel Panic - not syncing - attempted to kill init...
Username: Sky Aisling
"Hello, I'm hoping it is ok to post here. I normally post on John Murga's forum, but it is down today. Here is the situation: I created a USB flash drive of [b]Lucid Puppy 528[/b]. Error message upon boot: [i]Kernel Panic - not syncing - attempted to kill init... [/i] The USB drive brand is ATP 1 gig ToughDrive. The host PC is a Nobilis -RTS-N4018 M50E10, no HDD, 512 RAM, Pentium(R)Mproc 1.73 ghz (Note: only available input are USB ports.) I used the BootFlash USB installer option to create the bootable flash drive. The md5sum check is good. I re-installed several times. The drive previously held Lucid Puppy 520 and worked with no problems on same machine. I've tested the machine with another brand USB stick containing lupu-520 with no problems. Using Gparted, I viewed the setup of the old stick with lupu-520 against the new stick with lupu-528. The two setups look identical. Using a GUI screen I looked at the contents of lupu-528 on the ToughDrive. Looks like all the files are there. What else can I do to eliminate the error and get a clean boot? Note: my terminal skills are limited but I am willing to try if you go slow in your explanations. Thank you in advance. Here is a screenshot of what GParted sees: Here is a screenshot of what the GUI screen see for file content: oppps! I find no way to send screenshots. What a sweet dog 'Puppy' must have been. So small yet so BIG in spirit. Thank you for naming your systems 'Puppy'.

lupu-528 Kernel Panic - not syncing - attempted to kill init...
Username: Sky Aisling
"Regarding the above post... This is my first ever posting in this blog. How do I post screenshots? Thank you.

Re screenshots
Username: BarryK
"This blog is for developer discussion (mostly). Please post your question here: http://puppylinux.info/

Tags: woof