Okay most people will get it after practicedealing with permissions is trying.
but I totally fail and try to avoid doing permissions like the plague.
Light-Debian-Core-Live-CD-Wheezy + Porteus-Wheezy
Hi nooby; Hope you`re doing well my friend. "God Jul."
Say... How difficult is it to immigrate to Sweden.? The U.S. is heading for disaster...
In Puppyizing Debian, it`ll be a case of bit by bit hacking of some of it`s protections.
# I made scripts for Rox`s "Send To" that run sudo, like: sudo xfwrite $@
Now I can edit most any file without getting protection errors.
# I don`t know if Xfe filer is going to work out so well, it`s inflexible and hard to use.
Installed arander gui for xrander and it`s no help at all. # Need a gui to set resolution.
But arander installed Python, so maybe try installing PcManFM for a test.
.
Say... How difficult is it to immigrate to Sweden.? The U.S. is heading for disaster...
In Puppyizing Debian, it`ll be a case of bit by bit hacking of some of it`s protections.
# I made scripts for Rox`s "Send To" that run sudo, like: sudo xfwrite $@
Now I can edit most any file without getting protection errors.
# I don`t know if Xfe filer is going to work out so well, it`s inflexible and hard to use.
Installed arander gui for xrander and it`s no help at all. # Need a gui to set resolution.
But arander installed Python, so maybe try installing PcManFM for a test.
.
sunburnt I know too little for to give good advice on such.
No criticism to you I love that you care about me. Much appreciated.
But to be fair to Toni and everybody else active in the thread.
Back to the topic.
So if I get it. Squeeze is much easier to make small
but have another repo than Wheezy that is much bigger
but have modern kernels and updated programs in it's repo
So we need both then? Am I right
No criticism to you I love that you care about me. Much appreciated.
But to be fair to Toni and everybody else active in the thread.
Back to the topic.
So if I get it. Squeeze is much easier to make small
but have another repo than Wheezy that is much bigger
but have modern kernels and updated programs in it's repo
So we need both then? Am I right
I use Google Search on Puppy Forum
not an ideal solution though
not an ideal solution though
Hi, Nooby,nooby wrote:So we need both then? Am I right
I don't know who will need both exactly. You can put it this way:
Squeeze version - for old + new hardware, but old versions programs for old computers.
Wheezy version - for new hardware but new versions of programs, too much RAM hungry programs. I can't use Iceweasel at all on my computer from Wheezy version.
I need mostly Squeeze. Wheezy I hope will become modern brother of puppy linux. Maybe not from the version I made but it seems it heading this direction and nobody can stop it now
Sunburnt, thank you for what you are doing. I would never do it as fast and as good as you will.
Cheers, Toni
Translate rus-->eng
Hi, Sunburnt,
Here's my promise to you:
[quote]
For not-russian users: Some features of the use of sfs-linux
============================================================
Aurhor of the sfs-linux addressed their version Russian-speaking (and writing) Linux OS users and interface system originally Russified. In this case there are no obstacles to change the interface such as English or other European language.
Author once expressed that outside of Russia (eg Western Europe) it has not received a response to his of published.
I am one of the users (and testers and even fans) of sfs-linux.
Finding interest in the development of Linux users who do not know Russian language, I took the liberty to translate into English some of the interesting features of the system sfs-linux.
This is a free translation into English: ambiguities may arise in connection with different semantics in Russian and English languages, as well as some use different jargon. (Sergey Klimkin, Moscow, Russia)
Main autors page (author's nickname is "sfs"):
http://uco.puppyrus.org/forum/thread176.html
and its latest development (PuppyRusArch), together with the team puppyrs.org:
http://forum.puppyrus.org/index.php/board,154.0.html
sfsl is a debian+puppy linux clone
----------------------------------
Authors remark: "SFSLinux = attempt to make deb puppy. apt-get for puppy"
Minimalist direction: Debian with jwm, openbox. For experienced users, for the old equipment.
Main: multi-kernel (kernel can be changed) and a working prototype script remaster
With 'frugal' (based on live-boot) and software as a plug-in squashfs.
Can work from: CD, USB-flash, HDD.
sfsl-c-120129.iso - debian CrunchBang based
http://uco.puppyrus.org/go/url=http://w ... 27wd7bq6s9
sfsl-ds-120425.iso - debian-stable based
http://uco.puppyrus.org/go/url=http://w ... 120425.iso
sfsl-ds-120530.iso - - debian-stable based
http://uco.puppyrus.org/go/url=http://w ... 120530.iso
sfsl-c_vmlinuz-2.6.32-5-686.tar.bz2 - kernel
http://uco.puppyrus.org/go/url=http://w ... hw2367q3x6
sfsl-c_vmlinuz-3.2.0-0.bpo.1-686-pae.tar.bz2 - kernel
http://uco.puppyrus.org/go/url=http://w ... 2y6dq99yv8
openbox-3.5.0ru-i486s.sfs - as desktop environment
http://uco.puppyrus.org/go/url=http://w ... rdxr87bmo2
tint2-2-0.11g4-xz.sfs - system monitor
http://uco.puppyrus.org/go/url=http://u ... gDioImv8i1
--------------------------------------------------------------------------
The easiest recipe for creating your module:
sudo apt-get update
sudo apt-get install <PROGRAM>
sudo live-snapshot-t squashfs
Generally such a module would be good:
unsquashfs
clean / var; / usr / share doc, locale, etc.,
and then repack: mksquashfs ...
To live-sn.squashfs appeared immediately in the right place:
live-snapshot-o ...
Looks like I understood the meaning of live-sn.squashfs:
Frozen save-version.
If something is updated - doing a new one. If something messed up - overloads - and all in original condition.
About what is done in LupuRusBit "eternally alive puppy".
So it turns out that species conservation 3:
live-sn.cpio.gz - (rw read + write), dynamic dimension, with're compressing
live-sn.squashfs - (ro read-only), with're compressing
live-rw (optional home-rw) - (rw read + write), fixed size, without compression
and everywhere instead of a file, you can use a disk partition.
Looks like you can also combine them ...
I think the optimum live-sn.cpio.gz. Change happens when you reboot and shutdown. Want to insure - before shutting rename live-sn ***. Cpio.gz. The system will create a new one.
sfsl-w (debian wheezy verson):
------------------------------
During testing remaster (new version), gathered wheezy
To run it, replace in previous ISO: zz-* sfsl-c.squashfs --> zz-* sfsl-w.squashfs
And to collect it manually - code for terminal:
sudo sed -i 's/squeeze/wheezy/g;s/stable/testing/g' /etc/apt/sources.list
sudo apt-get update
sudo apt-get dist-upgrade
remaster
Saving in all versions of the sfsl same: use the same package live-boot.
All forms of saving, except live-sn.squashfs must be in root of the ext partition (root of the ISO-image).
live-sn.squashfs - should be in the same place where the base system.
If there are any problems with my GUI-snapshot, use the command in a terminal:
live-snapshot-t squashfs
But live-sn.squashfs can bring problems.
I advise you to use live-sn.cpio.gz - it is safer.
Do not forget the layers AUFS-systems: first *.squashfs alphabetically, then *.sfs
*-rw saving - ext-filesystem is packed into a file.
*-rw saving so you can mount:
mount *-rw / <INTO>-o loop
If there is a kernel parameter "persistent" (in line 'kernel' or 'append' loader file system) - loaded "live-sn.cpio.gz" "live-rw" "home-rw" (if they exist).
They must lie at the root of the media ext-partition.
Combine cpio.gz c rw not tried.
When additional kernel parameters "persistent-subtext = sfsc", as files (or partitions) used conservation: "live-sn-sfsc.cpio.gz" "live-rw-sfssc" "home-rw-sfssc".
Instead sfsc can write something else - by the user. Thus it is possible to have different save-files.
With the advent of the system script "sfs-get" (manager of the *.sfs user modules), I think that is not correct to connect the modules all at once, but by the need to:
sfs-get module-name.sfs
There is a variant of the automounter: rename *.sfs --> *.squashfs and put in /live.
The priority of the loading from /live - in alphabetical order. Base modules zz * must be at the end of the loading (so their names start with the letter "z").
Options for auto-loading modules *.sfs in the system sfs-linux
-------------------------------------------------- -----------
A. automounting modules *.sfs
1.Create in the root partition with a downloadable distribution DIR /_sfs ( directory name can be anything, but all the same)
2.Move into all modules *.sfs
3.In the kernel parameters (loader file) prescribe "sfsdir=_sfs"
The rest of the kernel parameters do not affect to auto-mount. Mounts the file /etc/rc.local
B. Alternative - rename modules *.squashfs and put in a folder with the same modules of the distributive.
Loaded in alphabetical order (in the presence of duplicate files - will be on the last of Alfabet module)
With this one I've had the problem of not working for the modules to system crash on loading.
C. Set in startup or run in a terminal;
automntsfs /media/sda1/_sfs
(path and folder location - any available for system)
Prescribe a program to autostart sfsl-up:
1. Create <LABEL>.desktop ( eg in text-editor)
2 . Put *.desktop in DIR /home/q/.config/autostart
To start from the root - put in the field Exec=sudo YOUR_PROGRAM
Manufacturing module *.sfs
--------------------------
Recipe 1 (complex, below there are 2 easier, but then get a larger in size module)
1. In DIR /live/cow system stores all you have made changes after loading
2 . boot system without save-files (save-partitions)
3 . sudo apt-get update; sudo apt-get - no-install-recommends install "YOUR-PROGRAM"
4 . Make sure that the program is working
5 . Analyze /live/cow and /var/cache/apt (here stored downloaded *.deb packages)
6. Copy /live/cow on ext*-partition in a directory sfs-tmp (or any other name)
7. boot system without save-files (save-partitions)
8. Copy from sfs-tmp into system <main-executable-file-of-program>
9. ldd `which <main-executable-file-of-program> ` | grep no
10. Add missing libraries of sfs-tmp into system
11. Make sure that the program is working
12. All copied from sfs-tmp into system, preserving the structure DIR's rewrite on ext *-partition of the DIR sfs-tmp2 (name, you can select any other). Correct LABEL.desktop (in /usr/share/applications), make sure that the program and its icon appears in the right place at the menu
13. mksquashfs sfs-tmp2 PROGRAM-NAME_VERSION.sfs -comp xz-Xbcj x86.
-comp xz only for kernels > 2.6.38 . Give greater compression module , but will increase the runtime mksquashfs
You can find any software of any distribution on http://pkgs.org and fabricate modules.
But if the software is available for installation via apt, it is the best way
Manufacturing module *. Sfs
--------------------------
Recipe 2 (for those who complicated recipe 1)
1. sudo apt-get update
sudo apt-get -d --no-install-recommends install "YOUR-PROGRAM"
2. mkdir sfs-tmp2. Unpack downloaded in the mc /var/cache/apt/archives/*.deb in sfs-tmp2, keeping the folders structure
3. Optional item: comprehend content sfs-tmp2, remove superfluous (alien locale unnecessary docks, ...)
4. mksquashfs sfs-tmp2 PROGRAM-NAME_VERSION.sfs-comp xz-Xbcj x86
The increase in the save file *-rw:
-----------------------------------
1. Create file live-rw-2 (instead of "2" can be anything else)
2. sudo mkdir /mnt/rw1;sudo mkdir /mnt/rw2
sudo mount <PATH-TO>/live-rw /mnt/rw1 -o loop
sudo mount <PATH-TO>/live-rw-2 /mnt/rw2 -o loop
3. Rewrite of the live-rw in live-rw-2
4. mv live-rw2 live-rw
or tweak the configuration file in grub4dos
The alternative - to move "fatty directory" from -rw to the free space (preferably to the ext*-partition, otherwise the files will be lost right)
and make a sym-link (ln-s or in mc: ctrl + x + s)
Do not be carried in preserving large files!
As of sfsl FRUGAL do sfsl FULL
------------------------------
My opinion - then lost the main idea.
Better install a normal distribution, and finished it (who you have enough knowledge for this).
But if you are one user at a stationary PC and do not tend to experiment:
1. partitioning your hard disk. You need at least one ext* partition for / and a swap partition
2. install the Linux boot loader, or use an existing. Installation utility for grub4dos You can find in ISO-image /boot/grub4dos/install
3. load sfsl with all modules you need and Your save-file (if exists)
4. rewrite all to prepared partition. Do not forget about the kernel and initrd
5. improve the standard boot loader (NOT live-boot kernel parameters).
for example: /boot/vmlinuz1 root=UUID=4db63c04-36a5-4da3-862e-c3aa82c48fd3 ro quiet splash
(booting with a file save and in mc copy all files from the root section (hard perversion)).
Manufacturing sfs-module with user settings
-------------------------------------------
Optimally, do not make save-file, but make the module with user settings and modules with user-installed software.
Create module "User Settings" - perhaps the first thing to do:
1. sudo-s
2. mkdir -p /tmp/tmp && cp -R /home/q /tmp/tmpp
3. clean caches, etc.
4. mksquashfs /tmp/tmp USER_SETTINGS.sfs
Here is an example kernel boot line with keys menu.lst file loader grub4dos:
----------------------------------------------------------------------------
kernel /_sfsl/live/vmlinuz320 live-media-path=/_sfsl/live/up quickusbmodules boot=live config persistent persistent-subtext=sfsc quickreboot debug swapon mountall sfsdir=_sfs
where:
persistent-subtext=sfsc подключить файл
Here's my promise to you:
[quote]
For not-russian users: Some features of the use of sfs-linux
============================================================
Aurhor of the sfs-linux addressed their version Russian-speaking (and writing) Linux OS users and interface system originally Russified. In this case there are no obstacles to change the interface such as English or other European language.
Author once expressed that outside of Russia (eg Western Europe) it has not received a response to his of published.
I am one of the users (and testers and even fans) of sfs-linux.
Finding interest in the development of Linux users who do not know Russian language, I took the liberty to translate into English some of the interesting features of the system sfs-linux.
This is a free translation into English: ambiguities may arise in connection with different semantics in Russian and English languages, as well as some use different jargon. (Sergey Klimkin, Moscow, Russia)
Main autors page (author's nickname is "sfs"):
http://uco.puppyrus.org/forum/thread176.html
and its latest development (PuppyRusArch), together with the team puppyrs.org:
http://forum.puppyrus.org/index.php/board,154.0.html
sfsl is a debian+puppy linux clone
----------------------------------
Authors remark: "SFSLinux = attempt to make deb puppy. apt-get for puppy"
Minimalist direction: Debian with jwm, openbox. For experienced users, for the old equipment.
Main: multi-kernel (kernel can be changed) and a working prototype script remaster
With 'frugal' (based on live-boot) and software as a plug-in squashfs.
Can work from: CD, USB-flash, HDD.
sfsl-c-120129.iso - debian CrunchBang based
http://uco.puppyrus.org/go/url=http://w ... 27wd7bq6s9
sfsl-ds-120425.iso - debian-stable based
http://uco.puppyrus.org/go/url=http://w ... 120425.iso
sfsl-ds-120530.iso - - debian-stable based
http://uco.puppyrus.org/go/url=http://w ... 120530.iso
sfsl-c_vmlinuz-2.6.32-5-686.tar.bz2 - kernel
http://uco.puppyrus.org/go/url=http://w ... hw2367q3x6
sfsl-c_vmlinuz-3.2.0-0.bpo.1-686-pae.tar.bz2 - kernel
http://uco.puppyrus.org/go/url=http://w ... 2y6dq99yv8
openbox-3.5.0ru-i486s.sfs - as desktop environment
http://uco.puppyrus.org/go/url=http://w ... rdxr87bmo2
tint2-2-0.11g4-xz.sfs - system monitor
http://uco.puppyrus.org/go/url=http://u ... gDioImv8i1
--------------------------------------------------------------------------
The easiest recipe for creating your module:
sudo apt-get update
sudo apt-get install <PROGRAM>
sudo live-snapshot-t squashfs
Generally such a module would be good:
unsquashfs
clean / var; / usr / share doc, locale, etc.,
and then repack: mksquashfs ...
To live-sn.squashfs appeared immediately in the right place:
live-snapshot-o ...
Looks like I understood the meaning of live-sn.squashfs:
Frozen save-version.
If something is updated - doing a new one. If something messed up - overloads - and all in original condition.
About what is done in LupuRusBit "eternally alive puppy".
So it turns out that species conservation 3:
live-sn.cpio.gz - (rw read + write), dynamic dimension, with're compressing
live-sn.squashfs - (ro read-only), with're compressing
live-rw (optional home-rw) - (rw read + write), fixed size, without compression
and everywhere instead of a file, you can use a disk partition.
Looks like you can also combine them ...
I think the optimum live-sn.cpio.gz. Change happens when you reboot and shutdown. Want to insure - before shutting rename live-sn ***. Cpio.gz. The system will create a new one.
sfsl-w (debian wheezy verson):
------------------------------
During testing remaster (new version), gathered wheezy
To run it, replace in previous ISO: zz-* sfsl-c.squashfs --> zz-* sfsl-w.squashfs
And to collect it manually - code for terminal:
sudo sed -i 's/squeeze/wheezy/g;s/stable/testing/g' /etc/apt/sources.list
sudo apt-get update
sudo apt-get dist-upgrade
remaster
Saving in all versions of the sfsl same: use the same package live-boot.
All forms of saving, except live-sn.squashfs must be in root of the ext partition (root of the ISO-image).
live-sn.squashfs - should be in the same place where the base system.
If there are any problems with my GUI-snapshot, use the command in a terminal:
live-snapshot-t squashfs
But live-sn.squashfs can bring problems.
I advise you to use live-sn.cpio.gz - it is safer.
Do not forget the layers AUFS-systems: first *.squashfs alphabetically, then *.sfs
*-rw saving - ext-filesystem is packed into a file.
*-rw saving so you can mount:
mount *-rw / <INTO>-o loop
If there is a kernel parameter "persistent" (in line 'kernel' or 'append' loader file system) - loaded "live-sn.cpio.gz" "live-rw" "home-rw" (if they exist).
They must lie at the root of the media ext-partition.
Combine cpio.gz c rw not tried.
When additional kernel parameters "persistent-subtext = sfsc", as files (or partitions) used conservation: "live-sn-sfsc.cpio.gz" "live-rw-sfssc" "home-rw-sfssc".
Instead sfsc can write something else - by the user. Thus it is possible to have different save-files.
With the advent of the system script "sfs-get" (manager of the *.sfs user modules), I think that is not correct to connect the modules all at once, but by the need to:
sfs-get module-name.sfs
There is a variant of the automounter: rename *.sfs --> *.squashfs and put in /live.
The priority of the loading from /live - in alphabetical order. Base modules zz * must be at the end of the loading (so their names start with the letter "z").
Options for auto-loading modules *.sfs in the system sfs-linux
-------------------------------------------------- -----------
A. automounting modules *.sfs
1.Create in the root partition with a downloadable distribution DIR /_sfs ( directory name can be anything, but all the same)
2.Move into all modules *.sfs
3.In the kernel parameters (loader file) prescribe "sfsdir=_sfs"
The rest of the kernel parameters do not affect to auto-mount. Mounts the file /etc/rc.local
B. Alternative - rename modules *.squashfs and put in a folder with the same modules of the distributive.
Loaded in alphabetical order (in the presence of duplicate files - will be on the last of Alfabet module)
With this one I've had the problem of not working for the modules to system crash on loading.
C. Set in startup or run in a terminal;
automntsfs /media/sda1/_sfs
(path and folder location - any available for system)
Prescribe a program to autostart sfsl-up:
1. Create <LABEL>.desktop ( eg in text-editor)
2 . Put *.desktop in DIR /home/q/.config/autostart
To start from the root - put in the field Exec=sudo YOUR_PROGRAM
Manufacturing module *.sfs
--------------------------
Recipe 1 (complex, below there are 2 easier, but then get a larger in size module)
1. In DIR /live/cow system stores all you have made changes after loading
2 . boot system without save-files (save-partitions)
3 . sudo apt-get update; sudo apt-get - no-install-recommends install "YOUR-PROGRAM"
4 . Make sure that the program is working
5 . Analyze /live/cow and /var/cache/apt (here stored downloaded *.deb packages)
6. Copy /live/cow on ext*-partition in a directory sfs-tmp (or any other name)
7. boot system without save-files (save-partitions)
8. Copy from sfs-tmp into system <main-executable-file-of-program>
9. ldd `which <main-executable-file-of-program> ` | grep no
10. Add missing libraries of sfs-tmp into system
11. Make sure that the program is working
12. All copied from sfs-tmp into system, preserving the structure DIR's rewrite on ext *-partition of the DIR sfs-tmp2 (name, you can select any other). Correct LABEL.desktop (in /usr/share/applications), make sure that the program and its icon appears in the right place at the menu
13. mksquashfs sfs-tmp2 PROGRAM-NAME_VERSION.sfs -comp xz-Xbcj x86.
-comp xz only for kernels > 2.6.38 . Give greater compression module , but will increase the runtime mksquashfs
You can find any software of any distribution on http://pkgs.org and fabricate modules.
But if the software is available for installation via apt, it is the best way
Manufacturing module *. Sfs
--------------------------
Recipe 2 (for those who complicated recipe 1)
1. sudo apt-get update
sudo apt-get -d --no-install-recommends install "YOUR-PROGRAM"
2. mkdir sfs-tmp2. Unpack downloaded in the mc /var/cache/apt/archives/*.deb in sfs-tmp2, keeping the folders structure
3. Optional item: comprehend content sfs-tmp2, remove superfluous (alien locale unnecessary docks, ...)
4. mksquashfs sfs-tmp2 PROGRAM-NAME_VERSION.sfs-comp xz-Xbcj x86
The increase in the save file *-rw:
-----------------------------------
1. Create file live-rw-2 (instead of "2" can be anything else)
2. sudo mkdir /mnt/rw1;sudo mkdir /mnt/rw2
sudo mount <PATH-TO>/live-rw /mnt/rw1 -o loop
sudo mount <PATH-TO>/live-rw-2 /mnt/rw2 -o loop
3. Rewrite of the live-rw in live-rw-2
4. mv live-rw2 live-rw
or tweak the configuration file in grub4dos
The alternative - to move "fatty directory" from -rw to the free space (preferably to the ext*-partition, otherwise the files will be lost right)
and make a sym-link (ln-s or in mc: ctrl + x + s)
Do not be carried in preserving large files!
As of sfsl FRUGAL do sfsl FULL
------------------------------
My opinion - then lost the main idea.
Better install a normal distribution, and finished it (who you have enough knowledge for this).
But if you are one user at a stationary PC and do not tend to experiment:
1. partitioning your hard disk. You need at least one ext* partition for / and a swap partition
2. install the Linux boot loader, or use an existing. Installation utility for grub4dos You can find in ISO-image /boot/grub4dos/install
3. load sfsl with all modules you need and Your save-file (if exists)
4. rewrite all to prepared partition. Do not forget about the kernel and initrd
5. improve the standard boot loader (NOT live-boot kernel parameters).
for example: /boot/vmlinuz1 root=UUID=4db63c04-36a5-4da3-862e-c3aa82c48fd3 ro quiet splash
(booting with a file save and in mc copy all files from the root section (hard perversion)).
Manufacturing sfs-module with user settings
-------------------------------------------
Optimally, do not make save-file, but make the module with user settings and modules with user-installed software.
Create module "User Settings" - perhaps the first thing to do:
1. sudo-s
2. mkdir -p /tmp/tmp && cp -R /home/q /tmp/tmpp
3. clean caches, etc.
4. mksquashfs /tmp/tmp USER_SETTINGS.sfs
Here is an example kernel boot line with keys menu.lst file loader grub4dos:
----------------------------------------------------------------------------
kernel /_sfsl/live/vmlinuz320 live-media-path=/_sfsl/live/up quickusbmodules boot=live config persistent persistent-subtext=sfsc quickreboot debug swapon mountall sfsdir=_sfs
where:
persistent-subtext=sfsc подключить файл
- Attachments
-
- sfs-linux_some-features_EN.txt.tar.gz
- (4.84 KiB) Downloaded 190 times
sfs-tools - scripts & executables
I can put here to learn and apply scripts from the package's sfsToni:
If we load only 01-base.sfs + 02-base.sfs and create from this point 04-extra.sfs it will also work fine.
But if we decide then to load 01+02+03+04-sfs - dpkg database will not have any information about 03-extra.sfs because it was not loaded while creating 04-extra.sfs
I'm sure it is already solved from the russian team and I know JBV solved it for FoxyRoxyLinux, so it will not be a problem to use something similar here.
Of these files, I did module sfs-tools.squashfs, it is loaded at the same time with main module silesystem.syauashfs in my own ubuntu-ISO-image and works correctly.
Unfortunately, in Debian wheezy it does not work (yet) - the reasons we have already discussed.
I'm going to repeat it in the distribution Debian squeese - sure there is work.
Download the archive here 800 KB does not work.
Therefore, the external link:
sfs-tools.tar.gz 802 KB
http://yadi.sk/d/-QCwBcdFEJi3u
sfs-tools.squashfs 780 KB
http://yadi.sk/d/g054-9aIEJu7c
Re: sfs-tools - scripts & executables
Thank you, Sergey,sklimkin wrote:I can put here to learn and apply scripts from the package's sfs
This will save us a lot of work.
Cheers, Toni
I love slitaz-linux - perhaps the smallest of the entire family of Linux, from those that are acceptable for the desktop environment and full of "gentleman's kit" of programs in the base distribution. Plus convenient and compact interface with its own repository. Plus the opportunity to work with deb-packages repositories, and convert in slitaz packages.
And all this in the ISO-image of size less than 40 MB
This is OFFTOP for our topic, but it is an illustration of what can be both functional and minimalistic Linux.
Here's a screenshot of one of the base distributions 'slitaz-razorqt' with kernel 3.2.14
And all this in the ISO-image of size less than 40 MB
This is OFFTOP for our topic, but it is an illustration of what can be both functional and minimalistic Linux.
Here's a screenshot of one of the base distributions 'slitaz-razorqt' with kernel 3.2.14
- Attachments
-
- slitaz-razorqt_kerel-3.2.14.png
- slitaz razorqt screenshot
- (164.47 KiB) Downloaded 319 times
-
Pelo
Brain storming distros for geek
I First downloaded this light Debian Core Live CD Wheezy. Not yet tried; But when reading the topic this light Debian will be be a Huge Puppy. I dont know.
Sudo : i hate it. Nobody can use that as user ! Debian needs years of computing classes
I look at it; I come back.
Sudo : i hate it. Nobody can use that as user ! Debian needs years of computing classes
I look at it; I come back.
Re: Brain storming distros for geek
Hi, Pelo,Pelo wrote:I First downloaded this light Debian Core Live CD Wheezy. Not yet tried; But when reading the topic this light Debian will be be a Huge Puppy. I dont know.
Sudo : i hate it. Nobody can use that as user ! Debian needs years of computing classes
I look at it; I come back.
forget sudo with Light Debian. You are logged in as root.
I'm working on 75-80 Mb wheezy version with one kernel. The testing version at the moment have two kernels.
I'm not sure how huge it will come after proper cleaning. I think in 200 Mb iso after cleaning we can add a lot.
Cheers, Toni
BTW does someone has impressions from IceWM? I start to like it a lot. It has desktop background image option and desktop icons without need of Rox-Filer. I will post a pictures later.
Creation-way & size of the final image
List of a archives & final-ISO's dedootstrap & chroot & live created:
---------------------------------------------------------------------
debian-squeeze-minbase-debootstrap.tar.gz - 67.9 MB
debian-squeeze-3.2.0-4-686-pae-minbase+kernel_chroot.tar.gz - 114.3 MB
debian-squeeze-3.2.0-4-686-pae-minbase+kernel+minprogs_chroot.tar.gz - 159.0 MB
debian-squeeze-3.2.0-4-686-pae-LXDE-installed.tar.gz - 370.3 MB
debian-squeeze-3.2.0-4-686-pae-Gnome-installed.tar.gz - 473.5 MB
debian-squeeze-3.2.0-4-686-pae-Gnome-sfs-final2.tar.gz - 321.1 MB (hard purged)
debian-live-gnome.iso - 337.3 MB (hard purged)
official live-boot-debian-squeeze-gdm.tar.gz - 1.1 GB
debian-wheezy-minbase-debootstrap.tar.gz - 74.8 MB
debian-wheezy-minbase-kernel-headers.tar.gz - 122.7 MB
debian-wheezy-minbase-kernel-headers-network.tar.gz - 140.5 MB
chroot-debian-wheezy-LXDE-slim-final.tar.gz - 264.3 MB
chroot-debian-wheezy-LXDE-slim-final3.tar.gz - 247.0 MB (hard purged)
debian-wheezy-LXDE-sfs.iso - 264.3 MB (hard purged)
official live-boot_debian-wheezy-lxde.tar.gz - 1.1GB
ubuntu-lucid--minbase_chroot.tar.gz - 122.5 MB
ubuntu-minbase+kernel+headers.tar.gz - 147.1 MB
ubuntu-lucid-2.6.32-21_chroot-final.tar.gz - 281.2 MB
ubuntu-lucid-3.0.0-32_chroot-final.tar.gz - 284.3 MB
ubuntu-lucid-gnome-panel.iso - 290.0 (hard purged)
ubuntu-lucid-gnome-panel_sfs.iso - 307.9 (hard purged)
I would not put Tony's data into the table - my results compare with its - terrible results
---------------------------------------------------------------------
debian-squeeze-minbase-debootstrap.tar.gz - 67.9 MB
debian-squeeze-3.2.0-4-686-pae-minbase+kernel_chroot.tar.gz - 114.3 MB
debian-squeeze-3.2.0-4-686-pae-minbase+kernel+minprogs_chroot.tar.gz - 159.0 MB
debian-squeeze-3.2.0-4-686-pae-LXDE-installed.tar.gz - 370.3 MB
debian-squeeze-3.2.0-4-686-pae-Gnome-installed.tar.gz - 473.5 MB
debian-squeeze-3.2.0-4-686-pae-Gnome-sfs-final2.tar.gz - 321.1 MB (hard purged)
debian-live-gnome.iso - 337.3 MB (hard purged)
official live-boot-debian-squeeze-gdm.tar.gz - 1.1 GB
debian-wheezy-minbase-debootstrap.tar.gz - 74.8 MB
debian-wheezy-minbase-kernel-headers.tar.gz - 122.7 MB
debian-wheezy-minbase-kernel-headers-network.tar.gz - 140.5 MB
chroot-debian-wheezy-LXDE-slim-final.tar.gz - 264.3 MB
chroot-debian-wheezy-LXDE-slim-final3.tar.gz - 247.0 MB (hard purged)
debian-wheezy-LXDE-sfs.iso - 264.3 MB (hard purged)
official live-boot_debian-wheezy-lxde.tar.gz - 1.1GB
ubuntu-lucid--minbase_chroot.tar.gz - 122.5 MB
ubuntu-minbase+kernel+headers.tar.gz - 147.1 MB
ubuntu-lucid-2.6.32-21_chroot-final.tar.gz - 281.2 MB
ubuntu-lucid-3.0.0-32_chroot-final.tar.gz - 284.3 MB
ubuntu-lucid-gnome-panel.iso - 290.0 (hard purged)
ubuntu-lucid-gnome-panel_sfs.iso - 307.9 (hard purged)
I would not put Tony's data into the table - my results compare with its - terrible results
That is why (see my chart) would be very useful to see and "touch" your result. Can You put the image somewhere and preferably log file image creation?stu91 wrote:
Currently posting from a custom live wheezy build - i made it much the same way as sklimkin described on page 3 where you start with the min debian base and add to it - i have xorg, blackbox, xfe, wicd-gtk wifi plus some other stuff and .iso is around 170mb i didn't remove or trim anything all locals docs etc are still included, so some room for improvement i think - this was just a test to see how all this debootstrap, chroot and build stuff works so no public upload here.
@saintless - is there some reason you build the other way starting with a debian iso and removing?
Sergey; Lots of info my friend, I`ll look at it and let you know what I understood.
# What`s the chance of making an English sfsl-Wheezy? Just set the locale I think.?
This would surely make it more popular here in the west. Hosting it is no problem.
I`ve used IceWM before, very good. And the menu is C style syntax, not horrible XML.
It`s an old WM, not sure if it`s maintained now. I guess OpenBox or others arn`t normal.?
Rox may still be desirable, I can`t see how to make Xfe work for Debian permissions.
Unless Deb-Wheezy is made to run as root... I`d thought hacking permissions was good.
.
# What`s the chance of making an English sfsl-Wheezy? Just set the locale I think.?
This would surely make it more popular here in the west. Hosting it is no problem.
I`ve used IceWM before, very good. And the menu is C style syntax, not horrible XML.
It`s an old WM, not sure if it`s maintained now. I guess OpenBox or others arn`t normal.?
Rox may still be desirable, I can`t see how to make Xfe work for Debian permissions.
Unless Deb-Wheezy is made to run as root... I`d thought hacking permissions was good.
.
Privet, Sergey,
from your list I see linux-headers included. Note this I don't have them included. The rest is a matter of making zerosize man, doc, info and removing files from var and usr/share. For example in wheezy debian I get more than 100 Mb to clean only in /var/cache/apt and /var/lib/apt I don't mean downloaded deb files. They are cleaned with apt-clean.
nothing against rox, openbox and others. Only experimenting with it. Just I'm surprised how flexible and easy to use is IceWM. And It gives an opportunity to minimize the iso size much.
Cheers, Toni
from your list I see linux-headers included. Note this I don't have them included. The rest is a matter of making zerosize man, doc, info and removing files from var and usr/share. For example in wheezy debian I get more than 100 Mb to clean only in /var/cache/apt and /var/lib/apt I don't mean downloaded deb files. They are cleaned with apt-clean.
Hi, Sunburnt,sunburnt wrote:I`ve used IceWM before, very good. And the menu is C style syntax, not horrible XML.It`s an old WM, not sure if it`s maintained now. I guess OpenBox or others arn`t normal.?
nothing against rox, openbox and others. Only experimenting with it. Just I'm surprised how flexible and easy to use is IceWM. And It gives an opportunity to minimize the iso size much.
Cheers, Toni
Last edited by saintless on Sat 14 Dec 2013, 19:29, edited 1 time in total.
Hi, sunburnt.
I can not locate the place of the author and distribute its distribution - it's not entirely correct.
And I can not do it correctly - I'm no expert in this matter, I do not even know the English language.
IceWM and JWM still quite popular desktop managers (for those who know what the "issue price").
Not everyone needs Gnome, Unity and even LXDE.
I agree with you - the clear C-syntax lot more convenient and easier to read than XML.
About Rox, Xfe and root-permissions I suggest to wait a bit - Tony clarify these issues.
Sergey.
I can not locate the place of the author and distribute its distribution - it's not entirely correct.
And I can not do it correctly - I'm no expert in this matter, I do not even know the English language.
IceWM and JWM still quite popular desktop managers (for those who know what the "issue price").
Not everyone needs Gnome, Unity and even LXDE.
I agree with you - the clear C-syntax lot more convenient and easier to read than XML.
About Rox, Xfe and root-permissions I suggest to wait a bit - Tony clarify these issues.
Sergey.
What exactly do you mean by this, Sunburnt?sunburnt wrote:I can`t see how to make Xfe work for Debian permissions
You are running as root I guess. The root startup warning is removed from XFE.
Now I see 8 desktops on the picture you posted. Is there any chance you are running the first uploaded version of Light-Wheezy. There is a second one which login as root. It is Light-Debian-Core-Wheezy-T1.iso and has only 2 desktops.
If you mean file permissions in XFE you can change them from file properties menu.
If you mean something else give some details what you need and I will search for answer.
Cheers, Toni
Hi Toni !
All so I do it too.
Yet I set at the beginning of installation "localepurge" program.
This program prompts you to select the desired locale (or locales) and then she cleans /usr/share/locale /doc and /... - forgot what else
I leave mandate only en_EN and ru_RU
I clean /usr/share/man /var/... by hands.
Large size of my distro explained quite simply, I put:
1. network-manager
2. Xorg (without trimming it)
3. LXDE or Gnome-Desktop (Gnome-Panel as variant)
But after all that remains is this:
/bin - 6.4 MB
/lib - 89.1 MB
/sbin - 7.0 MB
/var - 8.8 MB
Attention!: /usr - 489.6 MB
where:
/usr/bin - 41.2 MB
/usr/lib - 329.4 MB
/usr/sbin -5.6 MB
/usr/share - 97.0 MB
/usr/src - 18.6 MB
And if I cut out a lot in /usr/share by hands, in /usr/lib nothing you can not touch.
That is the "secret of success."
If you say very briefly, the desktop environment, even with the average for the quality and beauty of the graphics is very expensive - telle est la vie.
All so I do it too.
Yet I set at the beginning of installation "localepurge" program.
This program prompts you to select the desired locale (or locales) and then she cleans /usr/share/locale /doc and /... - forgot what else
I leave mandate only en_EN and ru_RU
I clean /usr/share/man /var/... by hands.
Large size of my distro explained quite simply, I put:
1. network-manager
2. Xorg (without trimming it)
3. LXDE or Gnome-Desktop (Gnome-Panel as variant)
But after all that remains is this:
/bin - 6.4 MB
/lib - 89.1 MB
/sbin - 7.0 MB
/var - 8.8 MB
Attention!: /usr - 489.6 MB
where:
/usr/bin - 41.2 MB
/usr/lib - 329.4 MB
/usr/sbin -5.6 MB
/usr/share - 97.0 MB
/usr/src - 18.6 MB
And if I cut out a lot in /usr/share by hands, in /usr/lib nothing you can not touch.
That is the "secret of success."
If you say very briefly, the desktop environment, even with the average for the quality and beauty of the graphics is very expensive - telle est la vie.
Privet, Sergey,
I'm not sure if this debian-wheezy-LXDE-sfs.iso - 264.3 MB (hard purged) is the same from here:
http://yadi.sk/d/jaDtHF5RDF9FD But from the last one I suggest you to remove also:
/var/lib/apt/lists:
ftp.ru.debian.org_debian_dists_wheezy_main_binary-i386_Packages -27,2M
bftp.ru.debian.org_debian_dists_wheezy_main_i18n_Translation-en - 17,6Mb
They will be generated again after running apt-get update.
About Xorg I first install
xserver-xorg-core with no-install-recomends. Window manager full package and then I install xinit full with recomends. This way I get almost full xorg.
Poka, Toni
I'm not sure if this debian-wheezy-LXDE-sfs.iso - 264.3 MB (hard purged) is the same from here:
http://yadi.sk/d/jaDtHF5RDF9FD But from the last one I suggest you to remove also:
/var/lib/apt/lists:
ftp.ru.debian.org_debian_dists_wheezy_main_binary-i386_Packages -27,2M
bftp.ru.debian.org_debian_dists_wheezy_main_i18n_Translation-en - 17,6Mb
They will be generated again after running apt-get update.
About Xorg I first install
xserver-xorg-core with no-install-recomends. Window manager full package and then I install xinit full with recomends. This way I get almost full xorg.
Poka, Toni
Saintless; Where is the "second Wheezy" you speak of.? The original link is the same size.
I`ll continue with this one for a little, I assumed it was a "test install".
I`ll keep my mods to clone to your newer Wheezy.
# Speaking of it... Does anyone want my Wheezy mods for the menu and Rox desktop.?
Does Debian have gui apps to edit JWM`s menu and task bar, and Rox`s desktop.?
If not then lets decide on a gui kit ( probably GtkDialog ), and I`ll make some for it.
But first I`ll ask the authors of Puppy`s guis to see if we can use a few of the good ones.
.
I`ll continue with this one for a little, I assumed it was a "test install".
I`ll keep my mods to clone to your newer Wheezy.
# Speaking of it... Does anyone want my Wheezy mods for the menu and Rox desktop.?
Does Debian have gui apps to edit JWM`s menu and task bar, and Rox`s desktop.?
If not then lets decide on a gui kit ( probably GtkDialog ), and I`ll make some for it.
But first I`ll ask the authors of Puppy`s guis to see if we can use a few of the good ones.
.
Hi, Sunburnt,sunburnt wrote:Saintless; Where is the "second Wheezy" you speak of.? The original link is the same size.
I`ll continue with this one for a little, I assumed it was a "test install".
I`ll keep my mods to clone to your newer Wheezy.
# Speaking of it... Does anyone want my Wheezy mods for the menu and Rox desktop.?
Does Debian have gui apps to edit JWM`s menu and task bar, and Rox`s desktop.?
If not then lets decide on a gui kit ( probably GtkDialog ), and I`ll make some for it.
But first I`ll ask the authors of Puppy`s guis to see if we can use a few of the good ones.
.
the second wheezy is the only one on the site now. It boots as root. The previous which seems you work with is removed.
Please, save your Rox mods and post them.
As far as I know Debian doesn't have GUI JWM and taskbar editing programs. The menu items are managed from update-menus command.
I agree we have to decide some things.
1. Two kernels included or only one and which one?
2. Jwm + Rox + GtkDialog or different.
3. What basic programs to include in the puppy like version.
4. What is the maximum iso size for the puppy like version?
I suggest to keep only 686-pae kernel. And maximum iso size 200 Mb or less.
Cheers, Toni
Uploaded IceWM-Wheezy-Light-Debian-pae.iso - 81 Mb. I think this is the best I can do to slim down Wheezy.
http://www.smokey01.com/saintless/
Only one kernel - 3.2.0-4-686-pae
It has iceWM with desktop walpaper and desktop icons support. Desktop icons use 4 Mb RAM. There is Show-Icons menu option to start them.
Added basic GUI image editor and snapshot program XPaint. Added options to load and eject CD/DVD from the menu. You can change the theme from menu. The rest is the same as Squeeze Light version.
First post updated.
Cheers, Toni
http://www.smokey01.com/saintless/
Code: Select all
md5sum 11c10c02f636902219a6423a5603f62f IceWM-Wheezy-Light-Debian-pae.isoIt has iceWM with desktop walpaper and desktop icons support. Desktop icons use 4 Mb RAM. There is Show-Icons menu option to start them.
Added basic GUI image editor and snapshot program XPaint. Added options to load and eject CD/DVD from the menu. You can change the theme from menu. The rest is the same as Squeeze Light version.
First post updated.
Cheers, Toni
- Attachments
-
- desktop1.jpg
- (61.7 KiB) Downloaded 377 times