Page 1 of 13

Posted: Wed 16 Jan 2013, 15:25
by simargl
bark_bark_bark wrote:Just don't break the kernel like you did with the 3.6.8 kernel.
Hmm.. wise guy? And very optimistic if you think that, I care about YOUR problems!

Posted: Wed 16 Jan 2013, 15:31
by stifiling
This distro needs a thread on the Arch Linux forums as well. because there's 'no way' they won't find it useful.

Posted: Wed 16 Jan 2013, 15:36
by bark_bark_bark
whoa.. no need to be hostile, bro. I just want to have your puppy become better (as well as stable). I could help by testing the ISO before release though. I don't care which kernel you use (as long as it's from January 2012 or newer). I want to make sure the kernel is fully stable, but I have confidence in the fact that kernel compile errors are less likely to happen for the next version.

i know in pre-ArchPup 12.12.x that broadcom devices worked, but they don't in that version because of kernel-related errors.

Anyways I will be happy to help your Puppy become a success. Don't let that post fool you into thinking it was 100% your fault that the kernel was broken, the kernel sources itself is to blame too. (I know because I've done some test compilations of kernels.)

Remember think proudly about your puplet. I think it's very unique. I would recommend it to anyone who want to switch from arch to Puppy.

Just keep experimenting, it will pay off.

EDIT: You may think you know what my problems are, but you don't and you never will.

Posted: Wed 16 Jan 2013, 16:51
by mavrothal
simargl wrote:Also I'm thinking to replace thunar + pup-volume-monitor with spacefm.
That may be a ggod idea. Mostly because I _think_ that the patched glib required for pup-volume-monitor gives problems
simargl wrote:so maybe I will use 3.4.25 or latest from that series, it was updated 2013-01-1
Wise.
Also calimero's kernels and ausf-utils suggested by cinclus_cinclus below may be a good idea. Did you check if their config matches yours?
(is always a good idea to follow "upstreams". Less work for you :wink: )
bark_bark_bark wrote: Aufs is a joke to me. Plus the SFS files used by puppy aren't Aufs, they're SquashFS 4.x format (Puppy 3/4 used v3).
:shock:
You do not have a clue what aufs is. Do you?...

Posted: Wed 16 Jan 2013, 16:55
by bark_bark_bark
I know what Aufs is, I just think it sucks.

Posted: Wed 16 Jan 2013, 17:26
by mavrothal
bark_bark_bark wrote:I know what Aufs is, I just think it sucks.
I see.
And what your preferred layered filesystem would be? (and why?)

Posted: Wed 16 Jan 2013, 17:30
by bark_bark_bark
Aufs is not a layered FS, but I'll just deal with it's existence for now.

Posted: Wed 16 Jan 2013, 17:41
by mavrothal
bark_bark_bark wrote:Aufs is not a layered FS
Is not?
How would you characterize it then?

Posted: Wed 16 Jan 2013, 17:49
by pemasu
http://aufs.sourceforge.net/
Aufs3 -- advanced multi layered unification filesystem version 3.x
http://aufs.sf.net
Junjiro R. Okajima

Posted: Wed 16 Jan 2013, 18:08
by bark_bark_bark
oh wow thank you for the clarifaction.

Posted: Wed 16 Jan 2013, 18:22
by mavrothal
pemasu,
you are not fun at all... :lol:

Posted: Wed 16 Jan 2013, 21:04
by simargl
For new release there will be 3 sfs files in main iso:
archpup-132.sfs (core + Xorg)
adrv-132.sfs (openbox+thunar+geany)
archapps-132.sfs (qt firefox and everything else)


If for example archpup-132.sfs need some fixing I can after upload only that file not the whole iso.

development files from archpup-132.sfs will be moved to archdev.sfs, but
adrv and archapps will be self-containable -> nothing will be splitted :x, that is only right way

Adequate photo :P
Image

Posted: Wed 16 Jan 2013, 21:57
by darkcity
this is my system-
Image

Posted: Thu 17 Jan 2013, 05:53
by mavrothal
simargl wrote: mounting cd-rom, dvd, and usb :o fat-32 formatted all works
but :!: mounting internal hard disk drive (ntfs or ext4), failed with something like 'specify partition type error'
In devices list in spacefm are shown mount loop files, I couldn't disable that.
Interesting is that usb devices are handled properly with spacefm but they don't show at all in thunar without restarting pup-volume-monitor.
If I am able to fix problems with mounting internal disk and hiding loop devices, this could easily replace thunar and pup-volume-monitor.
To remove loop files I added this to /root/.config/spacefm/session*

Code: Select all

dev_show_hide_volumes-s=-/dev/loop0 -/dev/loop1 -/dev/loop2 -/dev/loop3 -/dev/loop4 -/dev/loop5  # etc
Like you I had problem mounting internal drives but also USB srives (ext or fat). It says "no mount program was found" and asks for udisks a 3+MB download.
Maybe a custom command to use pmount... :wink:

Posted: Thu 17 Jan 2013, 08:31
by simargl
mavrothal wrote:Like you I had problem mounting internal drives but also USB srives (ext or fat). It says "no mount program was found" and asks for udisks a 3+MB download.
Maybe a custom command to use pmount...
It works also with udevil, only that drives are mounted to /run/root/* instead of /mnt/.
Maybe make custom script apmount :idea: with options mount and unmount and call that from spacefm.

Posted: Thu 17 Jan 2013, 08:53
by Anniekin
interested... compiled for i686 or wat?

Posted: Thu 17 Jan 2013, 09:27
by simargl
Yes, Arch Linux is optimized for i686 cpu.
mavrothal: I made apmount script, works with every tested device and is so simple that I will add it below. :)

Code: Select all

#!/bin/bash

mount_function() {
  DRIVE=$(echo $DRIVE_FULL | sed 's/\/dev\///')
  if [ ! -d /mnt/$DRIVE ]; then mkdir /mnt/$DRIVE; fi
  mount /dev/$DRIVE /mnt/$DRIVE
}

umount_function() {
  umount $DRIVE_FULL
}

case "$1" in

  mount)
    DRIVE_FULL="$2"
    mount_function ;;

  umount)
    DRIVE_FULL="$2"
    umount_function ;; 
    
  *)
    echo "apmount
options: mount umount" ;;
esac

Posted: Thu 17 Jan 2013, 09:58
by mike delaw
Hi!

I like ArchPup a lot since everything works and works good. But I have a couple of questions ( I am a complete newbie in Arch based Distros so please bear with me):

- how do I set a keymap to Slovenian language?

I have installed additional software (I didn't set any mirrors since default one is really fast!), but I have ran into problems with Wine and VLC:
- I have installed wine (or I think I did) bu it's not showing in menus ...
- I have installed VLC through yaourt but it didn't show up in menu. I tried pacman -S vlc and then it showed up in the menu, but refused to open.

What are proper commands for those two - pacman -S wine and pacman -S vlc or should I do something else ...

I am sorry that I have to ask these elementary questions, but I just want to know ...

Posted: Thu 17 Jan 2013, 10:36
by simargl
Hi mike delaw, and welcome 8)
For changing keymap to slovenian I believe you should edit /root/.start and replace

Code: Select all

setxkbmap us
setxkbmap si 
VLC will not run as root, that is decision of its developers, so use this (to start it as user arch)

Code: Select all

su arch
vlc 
For wine first start winecfg from terminal, setup your options and it will then work.
Also you might consider using makesfs wine, to have program wine in sfs module and load only
when you need it. :wink:

Posted: Thu 17 Jan 2013, 10:36
by mike delaw
Thank you.