Puppy Linux Discussion Forum Forum Index Puppy Linux Discussion Forum
Puppy HOME page : puppylinux.com
"THE" alternative forum : puppylinux.info
 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

The time now is Mon 28 Jul 2014, 18:33
All times are UTC - 4
 Forum index » Advanced Topics » Cutting edge
Alternative way to build Ubuntu / Debian Puppy
Moderators: Flash, Ian, JohnMurga
Post new topic   Reply to topic View previous topic :: View next topic
Page 4 of 6 [83 Posts]   Goto page: Previous 1, 2, 3, 4, 5, 6 Next
Author Message
stemsee


Joined: 27 Jun 2013
Posts: 270
Location: London

PostPosted: Mon 09 Jun 2014, 05:19    Post subject:  

xinput installed on puppy results in # xinput list commmand showing one mouse0 and keyboard0, the same command on L64 and all other linux distros results in a list of input devices as seen in hardinfo - input . a 'Master' is the head to which are attached the first keyboard and mouse and all other input devices. By creating a second master xinput allows you to attach to it a second keyboard and mouse which gives another pointer that acts indepedently of the first as in multi-touch. You can of course create several masters with several pointers and keyboards etc. It may be possible still to 'map' a master to a display/screen/desktop. Which is useful for me and my family to share one pc with extra displays keyboard and mice = pseudo multi-seat without nested servers = accelerated graphics and much better performance. Not for most people's usage I know.

Edit: Here is the patch for mapping input device to screen.

http://lists.x.org/archives/xorg-devel/2011-July/023898.html

Last edited by stemsee on Thu 19 Jun 2014, 14:55; edited 3 times in total
Back to top
View user's profile Send private message MSN Messenger 
mavrothal


Joined: 24 Aug 2009
Posts: 1570

PostPosted: Mon 09 Jun 2014, 05:25    Post subject:  

jamesbond wrote:

One thing I didn't check when I put the modules.sfs into ZDRV - does ZDRV gets copied to RAM too at boot time? If not, that means when you use CD to boot it, the CD can't be taken out.

If there enough RAM, yes

Quote:
NG does mean "Next Generation" - as you can see from "samba-tng", "util-linux-ng", and many other examples Smile

Depends where you look Laughing

_________________
Kids all over the world go around with an XO laptop. They deserve one puppy (or many) too Very Happy
Back to top
View user's profile Send private message 
01micko


Joined: 11 Oct 2008
Posts: 7782
Location: qld

PostPosted: Mon 09 Jun 2014, 05:30    Post subject:  

--if suffix is -nfg then you absolutely know it's no good Razz

james, as for the the -o 64 option, I think it's a case of old isohybrid in slacko, nothing more.

PS @jamesbond. re kernel-kit. Do you have a script for getting kernel firmware and cutting out inappropriate bloat?

_________________
Woof Mailing List | keep the faith Cool |
Back to top
View user's profile Send private message Visit poster's website 
jamesbond

Joined: 26 Feb 2007
Posts: 2045
Location: The Blue Marble

PostPosted: Mon 09 Jun 2014, 06:42    Post subject:  

Quote:
xinput installed on puppy results in # xinput list commmand showing one mouse0 and keyboard0, the same command on L64 and all other linux distros results in a list of input devices as seen in hardinfo - input . a 'Master' is the head to which are attached the first keyboard and mouse and all other input devices. By creating a second master xinput allows you to attach to it a second keyboard and mouse which gives another pointer that acts indepedently of the first as in multi-touch. You can of course create several masters with several pointers and keyboards etc. It may be possible still to 'bind' a master to a display/screen/desktop. Which is useful for me and my family to share one pc with extra displays keyboard and mice = pseudo multi-seat without nested servers = accelerated graphics and much better performance. Not for most people's usage I know.

Ah, that's because xorg hotplugging is *NOT ENABLED* in puppy. The ones built with deb-build does work (if you also apply the pinstall.sh patches from rootfs). For others, what stemsee says is quite interesting, here's what Arch has to say about it: https://wiki.archlinux.org/index.php/Multi-pointer_X.
EDIT: typo.

@Mav, good that ZDRV is loaded into RAM Smile
@Mick, (about -o64) I see, thanks. I use that "-o 64" because the default is "-o 0" (basically means that the start of the partition includes the partition table itself) and certain machines will not boot with this setup.

Quote:
--if suffix is -nfg then you absolutely know it's no good
LOL Very Happy

Quote:
PS @jamesbond. re kernel-kit. Do you have a script for getting kernel firmware and cutting out inappropriate bloat?

No. What we usually do when we build the modules.sfs is something like this
Code:
# in kernel source, after completion of make oldconfig
make -j6 bzImage modules
make modules_install INSTALL_MOD_PATH=./modules
cp -a /lib/firmware modules
mksquashfs modules kernel-modules.sfs -comp xz -Xbcj x86

Basically we copy whatever existing firmware in the running Fatdog, may be plus a few that others have reported missing in the forum. What we have in firmware is quite large and may contain obsolete stuff as well (I cleaned out radeon firmware before we released 630, I think, but there are many other that I haven't looked at) ...

_________________
Fatdog64, Slacko and Puppeee user. Puppy user since 2.13

Last edited by jamesbond on Mon 09 Jun 2014, 08:47; edited 1 time in total
Back to top
View user's profile Send private message 
stemsee


Joined: 27 Jun 2013
Posts: 270
Location: London

PostPosted: Mon 09 Jun 2014, 07:57    Post subject:  

[quote="jamesbond"No. What we usually do when we build the modules.sfs is something like this
Code:
# in kernel source, after completion of make oldconfig
make -j6 bzImage modules
make modules_install INSTALL_MOD_PATH=./modules
cp -a /lib/firmware modules
mksquashfs modules kernel-modules.sfs -comp xz -Xbcj x86

Basically we copy whatever existing firmware in the running Fatdog, may be plus a few that others have reported missing in the forum. What we have in firmware is quite large and may contain obsolete stuff as well (I cleaned out radeon firmware before we released 630, I think, but there are many other that I haven't looked at) ...[/quote]

Exactly what I did and thought should be the solution.

XINPUT on puppy: After maybe two years I have my answer! Thank you Jamesbond. Barry Kauler owes you $50 au ! Or half anyway. lol

Also I am now typing from the trusty built in woof-ce-ng. Gave a blowfish result of 8.1 Unheard of!!!
Back to top
View user's profile Send private message MSN Messenger 
stemsee


Joined: 27 Jun 2013
Posts: 270
Location: London

PostPosted: Wed 11 Jun 2014, 00:18    Post subject: latest stable kernel non-pae
Subject description: 3.15
 

I am posting from RSH's L.A.S.S.I.E running on latest 'stable' kernel 3.15 non-pae i486 (but says i686), just compiled on kernel-kit-ng by 01micko with initrd by jamesbond, and kernel-modues.sfs with lots of firmware, manually squashed by stemsee. Kernel is 4G highmem, 1g/3g split 1gb for kernel and 3gb for user/system. So 3gb appears in specs. timer =1000hz.
I forgot to remove suffix so uname -a gives 3.15-EmSee-pae but it is not pae! Sorry about that.

Here is the kernel, initrd and modules.sfs
https://drive.google.com/file/d/0B4GhZVmB2RkwZWpnZFN5UVk2Q0k/edit?usp=1

enjoy!
capture22264.jpg
 Description   
 Filesize   32.66 KB
 Viewed   867 Time(s)

capture22264.jpg


Last edited by stemsee on Wed 11 Jun 2014, 05:59; edited 1 time in total
Back to top
View user's profile Send private message MSN Messenger 
stemsee


Joined: 27 Jun 2013
Posts: 270
Location: London

PostPosted: Wed 11 Jun 2014, 02:16    Post subject:
Subject description: DebianDog
 

Now posting from DebianDog, booted on FD initrd and 3.14.5 kernel with kernel-modules.sfs (zdrv), all hardware up and running ootb! Nice!

This is fun!! Now for some old pups!

I couldn't get Lazy pup nor Lupi to boot with the FatDog initrd.
Back to top
View user's profile Send private message MSN Messenger 
jamesbond

Joined: 26 Feb 2007
Posts: 2045
Location: The Blue Marble

PostPosted: Sun 15 Jun 2014, 03:43    Post subject:  

Just because it is quiet doesn't mean nothing is happening. Work on this is still on-going. Check out the "woof-next" branch of Woof-CE. It is still in early state - but it's moving. Summary here.
_________________
Fatdog64, Slacko and Puppeee user. Puppy user since 2.13
Back to top
View user's profile Send private message 
01micko


Joined: 11 Oct 2008
Posts: 7782
Location: qld

PostPosted: Sun 15 Jun 2014, 04:16    Post subject:  

General info-

Just remember... remove userspace aufs-utils as kernel-kit wraps the correct version (built against the new headers) in the zdrv sfs.

EDIT: Kernel-kit is now pushed to woof-CE.

_________________
Woof Mailing List | keep the faith Cool |
Back to top
View user's profile Send private message Visit poster's website 
stemsee


Joined: 27 Jun 2013
Posts: 270
Location: London

PostPosted: Fri 20 Jun 2014, 05:03    Post subject:  

@Jamesbond
How to manage savefile booting with FD initrd???
Back to top
View user's profile Send private message MSN Messenger 
jamesbond

Joined: 26 Feb 2007
Posts: 2045
Location: The Blue Marble

PostPosted: Fri 20 Jun 2014, 06:22    Post subject:  

stemsee wrote:
@Jamesbond
How to manage savefile booting with FD initrd???

Sorry, can you please clarify your question? Also, if this is Fatdog-related question, that should go to Fatdog thread (use the one you see is still active).

_________________
Fatdog64, Slacko and Puppeee user. Puppy user since 2.13
Back to top
View user's profile Send private message 
stemsee


Joined: 27 Jun 2013
Posts: 270
Location: London

PostPosted: Fri 20 Jun 2014, 08:44    Post subject:  

@jamesbond

Not fatdog proper but the initrd in woof-ng. Does the initrd require a kernel argument to load a puppy.2/3/4sf file and where does it mount it? Is pupsave=ram:/path/to/savefile still valid? And can initrd parse a line DISTRO_PUPSAVE=puppy-save.2/3/4sf

I am trying to boot an alien os but still have puppy savefile.
Back to top
View user's profile Send private message MSN Messenger 
jamesbond

Joined: 26 Feb 2007
Posts: 2045
Location: The Blue Marble

PostPosted: Fri 20 Jun 2014, 14:18    Post subject:  

stemsee wrote:
Not fatdog proper but the initrd in woof-ng. Does the initrd require a kernel argument to load a puppy.2/3/4sf file and where does it mount it? pupsave=ram:/path/to/savefile still valid?
It is specified in DISTRO_SPECS that got included in initrd by build-iso.sh. You can't simply change them by specifying them from boot parameter (Mick, please correct me if I'm wrong). Fatdog's initrd (the real one, not the one in woof-next --- the one in woof-next's is still Puppy original initrd) does allow you to specify what basesfs you want to load through a boot parameter.

Anyway, basesfs, in Puppy's initrd, gets mounted in /initrd/pup_ro2. ZDRV (the kernel modules) gets mounted in /initrd/pup_z. Savefile gets mounted in /initrd/pup_rw, except when you use PUPMODE=13, where it will get mounted at /initrd/pup_ro1.

Quote:
Is And can initrd parse a line DISTRO_PUPSAVE=puppy-save.2/3/4sf
I don't know. I don't think you can specify arbitrary names for Puppy savefile, though. Fatdog's initrd, on the other hand, does.
_________________
Fatdog64, Slacko and Puppeee user. Puppy user since 2.13
Back to top
View user's profile Send private message 
stemsee


Joined: 27 Jun 2013
Posts: 270
Location: London

PostPosted: Sat 21 Jun 2014, 14:59    Post subject:  

@jamesbond

Thanks again!
Back to top
View user's profile Send private message MSN Messenger 
jamesbond

Joined: 26 Feb 2007
Posts: 2045
Location: The Blue Marble

PostPosted: Tue 24 Jun 2014, 08:07    Post subject:  

Hot News!

woof-next now builds the following (will boot up to graphical desktop with rox/jwm - at least in qemu):
- 32/64-bit ubuntu trusty
- 32/64-bit debian sid
- 32/64-bit slackware 14.1
It shouldn't be too difficult to do 32/64-bit debian jessie or 32/64-bit ubuntu utopic for anyone who wants to to do that.

All puppies have native package manager: debian/ubuntu have synaptics configured; slackware will have gslapt configured.

woof-next adapts Puppy to the parent distro; this is a different approach from current Woof2 which adapts the parent distro to Puppy.

The following infrastructure has been setup:
1. Build-time:
- rootfs-packages/debian-setup contains specific files/setup instructions for debian/ubuntu (currently they are shared, if later this is difficult, it can easily be split)
- rootfs-packages/slack-setup contains specific files/setup instructions for slackware.

2. Run-time:
There is an "rc.distro" which comes from the above "distro*-setup" rootfs-package, it is called by rc.sysinit to adapt whatever PATH etc so that puppy can run on top the base distro.

3. Size minimisation - the build infrastructure has commands to take out the most common source of bloats (doc, gtk-doc, etc).

4. Devx can be build in the same way like the basesfs is built (a sample devx pkglist is given for slackware)

5. Brand-new kernel kit from Mick Cool (I think this is already in "testing" branch too).

The builders are more or less finished (unless if someone wants to contribute building from other parents, like Mageia, CentOS, etc - I think for me I'll stop at these three distros). The next (and long) journey is to test and adapt puppy scripts to work on top of these various parent distros.

_________________
Fatdog64, Slacko and Puppeee user. Puppy user since 2.13
Back to top
View user's profile Send private message 
Display posts from previous:   Sort by:   
Page 4 of 6 [83 Posts]   Goto page: Previous 1, 2, 3, 4, 5, 6 Next
Post new topic   Reply to topic View previous topic :: View next topic
 Forum index » Advanced Topics » Cutting edge
Jump to:  

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You can download files in this forum


Powered by phpBB © 2001, 2005 phpBB Group
[ Time: 0.1006s ][ Queries: 13 (0.0104s) ][ GZIP on ]