Page 49 of 91

Updated repo

Posted: Tue 08 Oct 2013, 03:37
by Geoffrey
Updated repo with a few new and updated apps, see Recent Repository Additions.

Updated repo

Posted: Thu 10 Oct 2013, 03:57
by Geoffrey
Updated repo yet again with more Qt apps, see Recent Repository Additions.

Posted: Thu 10 Oct 2013, 21:10
by ac2011
Good to see Carolina's still being developed/supported.

I have either a bug report or a feature request for version 1.1, not sure which.

Seagate Expansion 4TB external USB 3.0 drive, plugged into a USB 2.0 laptop. Seen perfectly under Puppeee 1.0, Fluppy 013 and Windows XP. Not seen by Carolina.

Looking at dmesg, it's failing to understand the drive's geometry: it assigns seven or eight device names (e.g. sde to sdk), none of which is correct. Doesn't matter whether I format the drive as one large NTFS partition, two smaller Ext3 partitions, four Ext 2 partitions, etc.: Carolina's not even getting as far as the partition table.

I've seen reports of this elsewhere online, with one fix being to blacklist a module ('uas') but I've tried that, and I don't think that module's even in Carolina. In any case, it didn't work.

This looks like a kernel issue, and the drive takes a long time to be recognised even at the initrd stage, whereas Fluppy sails straight through.

Any ideas on a work-around would be welcome.

Re: Carolina - 1.0

Posted: Fri 11 Oct 2013, 19:09
by sheldonisaac
I managed to make a symlink on the desktop for my friend, who does not want to know any more about computers than necessary.

The link is to a a script which causes evince to load the pdf manual for a phone I gave her.

How can we have an icon, eg a picture of a phone, for that symlink?
(instead of the generic thing it now has)

Thanks,
Sheldon

Re: Carolina - 1.0

Posted: Fri 11 Oct 2013, 22:05
by Geoffrey
sheldonisaac wrote:I managed to make a symlink on the desktop for my friend, who does not want to know any more about computers than necessary.

The link is to a a script which causes evince to load the pdf manual for a phone I gave her.

How can we have an icon, eg a picture of a phone, for that symlink?
(instead of the generic thing it now has)

Thanks,
Sheldon
Sheldon,

Use a launcher on the desktop instead.

Rightclick the desktop and in the rightclick menu select " Create Launcher. "
To add the pdf, in the command input add " evince /path/to/my.pdf "
then for the icon click the icon button and when the menu appears " Select icon from: " > " All Icons " > type " phone " in the search,
it will show a phone, select that and OK it.

Hope that helps.

Re: Carolina - 1.0

Posted: Fri 11 Oct 2013, 22:44
by sheldonisaac
Geoffrey wrote:
sheldonisaac wrote:I managed to make a symlink on the desktop for my friend, who does not want to know any more about computers than necessary.

The link is to a a script which causes evince to load the pdf manual for a phone I gave her.

How can we have an icon, eg a picture of a phone, for that symlink?
(instead of the generic thing it now has)

Thanks,
Sheldon
Sheldon,

Use a launcher on the desktop instead.

Rightclick the desktop and in the rightclick menu select " Create Launcher. "
To add the pdf, in the command input add " evince /path/to/my.pdf "
then for the icon click the icon button and when the menu appears " Select icon from: " > " All Icons " > type " phone " in the search,
it will show a phone, select that and OK it.

Hope that helps.
Wow, Geoffrey!
I will try it.

THANK YOU!

Posted: Mon 14 Oct 2013, 06:06
by umair
Hi Geoffrey :
I want to install Virtual Box to run Win xp in carolina. Tried different sfs files of vbox. also load the devx file of carolina, but no success. please help.
Thanks in advance.
UMAIR

Posted: Mon 14 Oct 2013, 06:27
by rg66
umair wrote:Hi Geoffrey :
I want to install Virtual Box to run Win xp in carolina. Tried different sfs files of vbox. also load the devx file of carolina, but no success. please help.
Thanks in advance.
UMAIR
You need to load the kernel sources as well as devx.

http://smokey01.com/carolina/sfs/kernel ... 13-ski.sfs for pae

http://carolina-linux.com/elroy/lina-li ... 2.13-c.sfs for non-pae

Posted: Mon 14 Oct 2013, 06:58
by umair
rg66 wrote:
umair wrote:Hi Geoffrey :
I want to install Virtual Box to run Win xp in carolina. Tried different sfs files of vbox. also load the devx file of carolina, but no success. please help.
Thanks in advance.
UMAIR
You need to load the kernel sources as well as devx.

http://smokey01.com/carolina/sfs/kernel ... 13-ski.sfs for pae

http://carolina-linux.com/elroy/lina-li ... 2.13-c.sfs for non-pae
@rg66:
Thnx for quick reply.
I managed to install Virtual Box. Created virtual machine of 5 GB in home folder. But when I run the machine I saw the following error:
Any Idea ????

Posted: Fri 18 Oct 2013, 09:03
by ac2011
I don't know if this is of interest to anyone, but I've patched Carolina's initrd.gz so you can run with ramboot=1, as was possible in Puppeee and Fluppy.

I find this useful for when the kids are using my machine, as any damage they do is undone on a reboot. Also useful for testing new software: install a PET, test it, if you don't like it it's gone on reboot.

If anyone wants it, here it is. You just need to add 'ramboot=1' to the boot line. I've merely copied the code from Jemimah's Fluppy 013 initrd.gz and applied it in the relevant places, and added a new /mnt/tmpfs3 directory for it to use.

Given the size of the SFS files you'll need a fair amount of RAM, but on a 1GB or 2GB machine it's pretty handy.

I've barely tested this, having only just finished it, so be warned...

Hmm... can't upload. Forum complains about an empty file, and says the maximum allowed file size is 0MB. Is that because I haven't posted enough yet?

Updated repo

Posted: Sat 19 Oct 2013, 03:32
by Geoffrey
Updated repo with more Qt apps, see Recent Repository Additions.

I may as well do a bit of advertising for Carolina which contains some nice software.
There is the latest Nomacs image viewer, this now has a mosaic creator built in, along with it's many other features,
a great app to adjust raw camera images, along with it's ability to crop, resize and image conversion.

Firefox 24 from Carolina Repository

Posted: Fri 25 Oct 2013, 14:50
by oligin10
Hi guys, just spent some time with Carolina and it is fantastic! Any chance it will be supported longer term? Also, just a heads up. Firefox 24 doesn't install properly. When trying to run from menu or quick launch, it doesn't want to work. I had uninstalled Firefox ESR and installed Firefox 24. I can run it from usr/lib/firefox. I couldn't run from terminal. I also checked with Racy NOP 522 and same problem there. Hope you guys can keep this up. IMHO this should be the official Puppy. Thanks again, Rob

Re: Firefox 24 from Carolina Repository

Posted: Fri 25 Oct 2013, 20:39
by Geoffrey
oligin10 wrote: Firefox 24 doesn't install properly. When trying to run from menu or quick launch, it doesn't want to work. I had uninstalled Firefox ESR and installed Firefox 24. I can run it from usr/lib/firefox. I couldn't run from terminal.
I found the problem, it's a typo in /usr/bin "firefox" reads as "firfox", just rename it and it will be sweet.
I'll fix the package, strange it took so long to be noticed.
I guess most wouldn't uninstall the old version and only install firefox over the top of the existing one, thus keeping the good symlink.

Fixed

Posted: Sat 26 Oct 2013, 14:25
by oligin10
Thanks Geoffrey, all good now. Thanks for the quick response and solve. I hope you guys keep this running. I was amazed how polished this is. I know its based off Saluki, but it has really advanced since then. Thanks again, Rob

Ramboot code

Posted: Sun 27 Oct 2013, 00:55
by ac2011
As mentioned in my earlier post, I modified the original Carolina initrd.gz to use the 'ramboot' sections from Fluppy (also present in Puppeee). I find this feature useful: other people might too.

I can't seem to upload attachments to this forum, so I've explained how I did it here. The code should actually allow you to add ramboot=1 to almost any other version of Puppy too, though I haven't yet tried that.

Backup everything before you start, and have a spare bootable medium on hand (e.g. USB stick or CD) as this could potentially make your system unbootable if your only running OS is Carolina.

First, make a temporary directory containing a copy of the Carolina initrd.gz. In that directory, do this:

Code: Select all

mkdir initdir
cd initdir
zcat ../initrd.gz | cpio -i -d
Now create a new temp mount-point for the ramboot code to use (note, we're doing this inside the 'initdir' directory, hence the lack of a leading /):

Code: Select all

mkdir mnt/tmpfs3
Now you need to edit the 'init' script in your favourite text editor and insert the necessary ramboot code at various points. Hopefully I've included enough of the surrounding code for you to work out where this all goes.

First bit:

Code: Select all

#pmedia= usbflash|usbhd|usbcd|ataflash|atahd|atacd|atazip|scsihd|scsicd|cd
[ $pmedia ] && PMEDIA=$pmedia #boot parameter, broad category of boot media. ex: cd.
[ $pdev1 ] && PDEV1=$pdev1    #boot parameter, partition have booted off. ex: hda3
[ $psubdir ] && PSUBDIR=$psubdir #boot parameter, directory for puppy files. ex: puppy220
[ $pkeys ] && PKEYS=$pkeys #boot parameter, keyboard layout w476

# next bit added for ramboot
[ $ramboot ] && RAMBOOT=yes
Second bit:

Code: Select all

  #[ "$REMOVABLEDRVSAVE" = "1" ] && PUPMODE=13
  [ "$REMOVABLEDRVSAVE" = "1"  -a  "$PMEDIA" != "usbhd" ] && PUPMODE=13  #110116 shinobar.
  [ "$PMEDIA" = "usbflash" ] && PUPMODE=13 #v404 fix classmate, with internal usb flash.
  [ "$PMEDIA" = "ataflash" ] && PUPMODE=13 #w019 constrain writes to internal flash drv.
 ;;
 76) #v3.01 64+8+4 multisession cd.
  PUPMODE=77 #yes, want tmpfs top layer.
 ;;
esac

# next bit added for ramboot
[ "$RAMBOOT" = "yes" ] && PUPMODE=12
Third bit:

Code: Select all

 #normal ${DISTRO_FILE_PREFIX}save.2fs file. just mount it from where it is...
 echo -n "Loading personal file $PUPSAVEFILE ($PUPSAVEDEV)..." > /dev/console 
 [ "`echo "$PUPSAVEFS" | grep 'ext[234]'`" != "" ] && echo "/dev/$PUPSAVEDEV /mnt/dev_save $PUPSAVEFS defaults  1 1" >> /etc/fstab #v2.21

# next bit added for ramboot
if [ "$RAMBOOT" = "yes" ] ; then
        if [ "$PUPSAVEDEV" = '' ] ; then
                echo -e -n " \\033[1;31mError, Save file is required for ramboot option  \\033[0;39m" 
                exit
        fi
        mntfunc $PUPSAVEFS /dev/$PUPSAVEDEV /mnt/tmpfs3 noatime
        cd /mnt/tmpfs3/${PSUBDIR}
        SIZE=0
	SIZE=`ls *fs | while read line ; do SIZEK=$(du -k $line| cut -f 1); SIZE=$(expr $SIZE + $SIZEK); echo $SIZE ; done |tail -n 1`
        SIZE=`expr $SIZE + 1000`
        if [ $SIZE -gt $RAMSIZE ] ; then
                echo -e -n " \\033[1;31mError, Files too big to fit in RAM  \\033[0;39m" > /dev/consol
                exit
        fi
        mount -t tmpfs -o size=${SIZE}k tmpfs /mnt/dev_save
        mkdir /mnt/dev_save/$PSUBDIR
        echo -e  " \\033[1;35mCopying files to RAM  \\033[0;39m" > /dev/console #purple.
        echo -e  " \\033[1;35m${SIZE}KB RAM will be used\\033[0;39m" > /dev/console
        ls *fs |while read line ; do
                echo -e -n " \\033[1;35m${line} \\033[0;39m" > /dev/console #purple.
                cp -af ${line} /mnt/dev_save/$PSUBDIR > /dev/console 2>&1
        done
        cd
        umntfunc /mnt/tmpfs3
 else
      mntfunc $PUPSAVEFS /dev/$PUPSAVEDEV /mnt/dev_save noatime #-t $PUPSAVEFS -o noatime /dev/$PUPS
 fi
# above bit added for ramboot (and next line commented out)
 
# mntfunc $PUPSAVEFS /dev/$PUPSAVEDEV /mnt/dev_save noatime #-t $PUPSAVEFS -o noatime /dev/$PUPSAVEDEV /mnt/dev_save
Fourth bit:

Code: Select all

       if [ "$nocopysfs" = "" ];then
        echo -en "\\033[1;35m" >/dev/console #35=purple
        echo "'${basepupsfs}' now copying to hard drive (but only available next boot)..." >/dev/console
        echo -en "\\033[0;39m" >/dev/console
        PPATTERN="/dev/$xPUPSFSDEV "
        PUPSFSDEVMNTPT="`mount | grep "$PPATTERN" | cut -f 3 -d ' '`"

		# next bit added for ramboot
		[ "$RAMBOOT" = "yes" ] && PUPSFSDEVMNTPT=/mnt/dev_save
Fifth bit:

Code: Select all

 #100920 decide whether to copy .sfs's to ram (see prior decision above)...
 pdPATTERN="`echo "$PUPSFSDEV" | sed -e 's/[0-9]*$//'` " 
 if [ "$PNOCOPY" != "yes" ];then
  [ "`echo -n "$ATADRIVES" | grep "$pdPATTERN"`" = "" ] && COPYCONTENDER='yes' #test if not fast internal drive.
  [ $PUPMODE -eq 5 ] && COPYCONTENDER='yes'
  [ "$DEV1FS" = "iso9660" ] && COPYCONTENDER='yes'
 fi
 [ "$PCOPY" = "yes" ] && COPYCONTENDER='yes'
 [ "$COPYCONTENDER" = "yes" ] && [ $RAMSIZE -gt 220000 ] && [ $RAMSIZE -gt $MINRAM2CPY ] && COPY2RAM="yes"

 # next bit added for ramboot
 [ "$RAMBOOT" = "yes" ] && COPY2RAM=""
Once you've done all that, you then rebuild the initrd.gz file:

Code: Select all

find . | cpio -o -H newc | gzip -9 > ../initrd_new.gz
When it's finished, copy the initrd_new.gz file to wherever you boot Carolina from, and rename it to initrd.gz (or you might be able to set up a new entry in your grub/syslinux file to use initrd_new.gz instead of initrd.gz). Booting with the kernel boot parameter 'ramboot=1' should move the Carolina SFSs and save files onto a ramdrive: they must all be in the same directory to start with, and you may need to specify pdev1 and psubdir on the kernel boot line too. And you need enough spare RAM...

Remember, nothing will be saved when you shut down.

If someone tries this code, please let me know if it works OK. It's fine for me, but if it needs any modifications I'll edit this post.

Posted: Sun 27 Oct 2013, 11:00
by spandey
I have done a frugal install of carolina in harddisk. The machine has intel integrated graphics. The characters in the screen appear compressed. the font is very light any idea how to fix it?

Posted: Mon 28 Oct 2013, 21:49
by Geoffrey
spandey wrote:I have done a frugal install of carolina in harddisk. The machine has intel integrated graphics. The characters in the screen appear compressed. the font is very light any idea how to fix it?
I found that the Custom DPI isn't working until it is unchecked the checked again, this will increase font size and boldness, give that a try, you'll find it in Control Panel > Desktop > Appearance, hope that helps.

Posted: Thu 31 Oct 2013, 06:47
by umair
Refer to my previous post about installation of VBOX in Carolina, I finally managed to get it working without any problem. I used the vbox.sfs from carolina's repos also loaded the devx.sfs file and all goes well. Here is the screenshot.
UMAIR

Dukto

Posted: Sat 02 Nov 2013, 09:29
by Geoffrey
Dukto, is a lan file transfer application, it also comes as a app for Window, Mac, iPad and Android.

I've tested it with another laptop running Carolina and with an Android tablet, it works fine for file,
folder and text transfer, you need only drag n drop on the application window to send.

this requires QT to work, only tested with Carolina, if it proves to be any good I'll add it to the repo, some feed back would be welcome.

my carolina

Posted: Sun 03 Nov 2013, 04:53
by erikkire
still using carolina. love it. tnx!