torios team mailing list archive
-
torios team
-
Mailing list archive
-
Message #01978
Re: Compressed image file with ToriOS, forked from: custom tarballs
Hi again,
1. I fixed typing error concerning the size after expansion.
The size is 513 Mibibytes, and it will expand to 7.8 GB (Gigabytes)
2. I attached a picture and a text file, from the IBM Thinkpad T42.
Notice that problems due to slow searching for a floppy is solved by
blacklisting, and that the Pentium M processor works with a pae kernel
(with a little help from fake-pae).
3. Notice that these custom tarballs and this compressed image file all
illustrate how you can create your own custom ToriOS.
- Install programs and tweak your system
- Create a tarball with zmktbl
- Distribute the custom system by means of tarballs and install with the
same version of the OBI as you used to create the tarball.
- Or if you wish, clone your tweaked system (starting from the
compressed image file with the OEM mechanism).
Best regards
Nio
Den 2015-05-27 09:11, Nio Wiklund skrev:
> Hi all toriosadores,
>
> [See at the end of this mail]
>
> Den 2015-05-27 01:12, Nio Wiklund skrev:
>> Den 2015-05-26 23:34, Nio Wiklund skrev:
>>> Hi again Israel and Jack,
>> ...
>>> I made an OEM system (user oem, computer name oem) which seems to create
>>> problems for the OBI-installer while my own version of the OBI for
>>> precise works with it. (Also the standard OBI in Lubuntu Trusty works
>>> with such systems.) This system has the two 3.2 kernels with and without
>>> PAE and I will add fake-pae before uploading the tarball to Phill's
>>> server. I will install geany and evince too, but nothing big.
>>>
>>> - It works to use the OEM mechanism and nm-applet works.
>>>
>>> - The shutdown menu works correctly when I select the JWM session, but
>>> not in the ToriOS session. There is also a plain grey Openbox session,
>>> that works as it should. Openbox is necessary for the OEM mechanism to work.
>>>
>>> See the attached file.
>>>
>>> Best regards
>>> Nio
>> ...
>>
>> Hi again Israel and all testers,
>>
>>
>> Since before there is this text based version 2.9 or the OBI
>>
>> http://phillw.net/isos/one-button-installer/dd_images/dd_precise-obi_4GB_29_text.img.xz
>>
>> that I have been using as a reliable and light-weight tool to make and
>> use ToriOS tarballs. Use mkusb to install it to a USB pendrive.
>>
>>
>> A few minutes ago I uploaded the following tarball
>>
>> http://phillw.net/isos/linux-tools/OBI/precise/tarballs/ToriOS-pae-OEM_prec_use-by-OBI-in-precise.tar.xz
>>
>> which is the 'ToriOS-pae-OEM' tarball I tested in the previous mail.
>>
>>
>> Best regards
>> Nio
>>
>
> This same system, that is stored as a tarball is also stored as a
> compressed image file at Phill's server,
>
> http://phillw.net/isos/linux-tools/compressed-images/dd_ToriOS-pae-OEM_precise_7.8GB.img.xz
>
> The size is 513 Mibibytes, and it will expand to 7.8 GB (Gigabytes) to
> fit in slightly undersized 8 GB pendrives.
>
> - Use mkusb [in linux, and use 7-zip & Win32DiskImager in Windows] to
> install it to a fast USB pendrive or an internal drive. It will
> overwrite the partition table.
>
> - Use gparted to the swap partition and after that expand the root
> partition, so that the system will fill a larger part of the target
> drive (often the whole target drive).
>
> -o-
>
> But if you want to leave an existing system on the target drive, for
> example that you want to dual boot with Windows, please use the tarball
> and the OBI method instead.
>
> Best regards
> Nio
>
Attachment:
ToriOS_OEM_blacklist-floppy_fake-PAE_in_Thinkpad-T42.png
Description: PNG image
Welcome to ToriOS
dd-oem-pae@t42 ~ $ sudo lsblk -fm
[sudo] password for dd-oem-pae:
^C^C^C^C^C^C^C^C^C^C^C^C^C^C^C^C^C^C^C^C^C^C^C^C^Cdd-oem-pae@t42 ~ $ ^C
dd-oem-pae@t42 ~ $ cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc nodev,noexec,nosuid 0 0
# / was on /dev/sda1 during installation
UUID=66fb6de4-065a-446e-a3b6-b058887520c9 / ext4 errors=remount-ro 0 1
# swap was on /dev/sda5 during installation
UUID=ae9d2418-0fa7-4864-b2d1-a34c50770893 none swap sw 0 0
#/dev/fd0 /media/floppy0 auto rw,user,noauto,exec,utf8 0 0
dd-oem-pae@t42 ~ $ sudo nano /etc/modprobe.d/blacklist-floppy.conf
dd-oem-pae@t42 ~ $ cat /etc/modprobe.d/blacklist-floppy.conf
blacklist floppy
dd-oem-pae@t42 ~ $ sudo rmmod floppy
dd-oem-pae@t42 ~ $ sudo update-initramfs -u
update-initramfs: Generating /boot/initrd.img-3.2.0-84-generic-pae
dd-oem-pae@t42 ~ $ sudo lsblk -fm
NAME FSTYPE LABEL MOUNTPOINT NAME SIZE OWNER GROUP MODE
sda sda 37.3G root disk brw-rw----
├─sda1 ext4 ToriOSmay24-3ker ├─sda1 35G root disk brw-rw----
└─sda2 swap └─sda2 2.2G root disk brw-rw----
sr0 sr0 1024M root cdrom brw-rw----
sdb sdb 14.8G root disk brw-rw----
├─sdb1 ext4 ToriOSpaeOEMprec / ├─sdb1 7G root disk brw-rw----
└─sdb2 swap [SWAP] └─sdb2 337M root disk brw-rw----
dd-oem-pae@t42 ~ $ grep -i -e pentium -e pae /proc/cpuinfo
model name : Intel(R) Pentium(R) M processor 1.70GHz
flags : pae fpu vme de pse tsc msr mce cx8 mtrr pge mca cmov clflush dts acpi mmx fxsr sse sse2 ss tm pbe up bts est tm2
dd-oem-pae@t42 ~ $
References