Building Blocks

Here is a place for your projects which are not officially supported by the Porteus Team. For example: your own kernel patched with extra features; desktops not included in the standard ISO like Gnome; base modules that are different than the standard ISO, etc...
Jack
Contributor
Contributor
Posts: 1246
Joined: 09 Aug 2013, 14:25
Distribution: Porteus 3.2.rc5 Mate 64 bit
Location: Marysville, OHIO USA

Re: Building Blocks

Post#121 by Jack » 11 Feb 2016, 21:21

I did what you ask me to do. Here is all the way I try it.

1. CD it did work
2. fat32 and didn't work
3. ext4 and didn't work
4. ntfs and didn't work

2, 3 and 4 stop in the same place.

And for my 0.02cent that don't mean I was right. It was what I was thinking it could be.

Code: Select all

guest@porteus:~$ sudo mount /dev/sdb1 /mnt/sdb1
    guest@porteus:~$ ls /mnt/sdb1/porteus/
    base/  modules/  optional/  ptest.sgn*  rootcopy/
And if you look at Boot Info above, you will see proteus data was specified to be on /dev/sdb1 in the Kernel Command Line. Also in porteus-livedbg listing it gives Porteus Data as being found on /dev/sdb1, sdb1 being in vfat format.
I can see all the files are there on the CD plus all the USB I made for test for you.

UPDATE The only way I run or use Porteus is ext4 and I never use CD rom. I haven't use CD rom for years.
I just like Slackware because I think it teach you about Linux to build packages where Ubuntu is like Windows you just install programs you want.

Bogomips
Full of knowledge
Full of knowledge
Posts: 2563
Joined: 25 Jun 2014, 15:21
Distribution: 3.2.2 Cinnamon & KDE5
Location: London

Re: Building Blocks

Post#122 by Bogomips » 11 Feb 2016, 21:49

Jack wrote:I did what you ask me to do. Here is all the way I try it.

1. CD it did work
2. fat32 and didn't work
3. ext4 and didn't work
4. ntfs and didn't work
Jack, having trouble booting from usb porteus. The bios only sees floppy, but have no floppy drive. So cannot do test for booting from usb. Made usb with neko tool, and this is what was working for me, in that it could get porteus data from usb, and start. Could you try neko tool with this new iso, and get bios to boot the usb created? Thanks.
Linux porteus 4.4.0-porteus #3 SMP PREEMPT Sat Jan 23 07:01:55 UTC 2016 i686 AMD Sempron(tm) 140 Processor AuthenticAMD GNU/Linux
NVIDIA Corporation C61 [GeForce 6150SE nForce 430] (rev a2) MemTotal: 901760 kB MemFree: 66752 kB

Jack
Contributor
Contributor
Posts: 1246
Joined: 09 Aug 2013, 14:25
Distribution: Porteus 3.2.rc5 Mate 64 bit
Location: Marysville, OHIO USA

Re: Building Blocks

Post#123 by Jack » 11 Feb 2016, 22:02

Bogomips wrote:
Jack wrote:I did what you ask me to do. Here is all the way I try it.

1. CD it did work
2. fat32 and didn't work
3. ext4 and didn't work
4. ntfs and didn't work
Jack, having trouble booting from usb porteus. The bios only sees floppy, but have no floppy drive. So cannot do test for booting from usb. Made usb with neko tool, and this is what was working for me, in that it could get porteus data from usb, and start. Could you try neko tool with this new iso, and get bios to boot the usb created? Thanks.
I all ready try neko tool and it did the same thing as 2, 3 and 4 it didn't work.
I just like Slackware because I think it teach you about Linux to build packages where Ubuntu is like Windows you just install programs you want.

Bogomips
Full of knowledge
Full of knowledge
Posts: 2563
Joined: 25 Jun 2014, 15:21
Distribution: 3.2.2 Cinnamon & KDE5
Location: London

Re: Building Blocks

Post#124 by Bogomips » 12 Feb 2016, 01:52

Ed_P wrote:And all the files they search for and use begin inside the mounted ISO.

Only the boot loaders access the NTFS formatted partition. The kernel and initrd are read from the ISO and read files inside the mounted ISO file's files.
No acquaintance with grub4dos, but have some idea about Grub2.

Grub Procedure
  1. Kernel and Initrd Extraction
    1. Grub1 User
      1. Mounts Iso on Loop
      2. Extracts Kernel and Initrd to directories on same partition
      3. Using Menu.lst informs bootloader of their whereabouts
    2. Grub2 Program
      1. Mounts Iso on Loop
      2. Extracts Kernel and Initrd
      3. Passes pointer to them to bootloader routine
  2. Bootloader Routine
    1. Loads Kernel into Memory
    2. Places Initrd in a Special Memory Fille
  3. Grub bows out and hands over to Kernel
  4. Kernel decompresses Initrd
  5. Kernel executes Init (here I'm not sure which is which), which then executes Init Script in Initrd
  6. Init Script has to be able to find Porteus Data sgnfile, and only able to do so if can read filesystem on which iso resides in order to be able to loop mount the iso, in the case of isos.
Linux porteus 4.4.0-porteus #3 SMP PREEMPT Sat Jan 23 07:01:55 UTC 2016 i686 AMD Sempron(tm) 140 Processor AuthenticAMD GNU/Linux
NVIDIA Corporation C61 [GeForce 6150SE nForce 430] (rev a2) MemTotal: 901760 kB MemFree: 66752 kB

User avatar
Ed_P
Contributor
Contributor
Posts: 3402
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 3.2.2 64-bit ISO
Location: Western NY, USA

Re: Building Blocks

Post#125 by Ed_P » 12 Feb 2016, 04:31

Bogomips wrote:Init Script has to be able to find Porteus Data sgnfile,
To this we agree.
Bogomips wrote:and only able to do so if can read filesystem on which iso resides in order to be able to loop mount the iso, in the case of isos.
Then why does the bootloader do this?
Bogomips wrote:Places Initrd in a Special Memory Fille
And this?
Bogomips wrote:Mounts Iso on Loop
Everything is already in memory, there is no need to read the filesystem to loop the iso again.

BTW Have tried the 100216 iso, still the same problem. I even added a map of firaDisk.gz to a menu like I use to read my BartPE.iso and it didn't help either. Very strange. Maybe a missing symlink?
Ed

Bogomips
Full of knowledge
Full of knowledge
Posts: 2563
Joined: 25 Jun 2014, 15:21
Distribution: 3.2.2 Cinnamon & KDE5
Location: London

Re: Building Blocks

Post#126 by Bogomips » 12 Feb 2016, 17:19

@ Jack Can you check this out?
  1. Using neko tool have formatted usb which was tested before. On the usb formatted by neko tool, see if checksums are the same as on mine?

    Code: Select all

    guest@porteus:~$ md5sum /mnt/sdb1/boot/syslinux/vmlinuz 
    c0377a5c8c07fb47be5e714c7ce3a78d  /mnt/sdb1/boot/syslinux/vmlinuz
    guest@porteus:~$ md5sum /mnt/sdb1/boot/syslinux/initrd.img 
    f5090165416f6711e0ad2f87014e567f  /mnt/sdb1/boot/syslinux/initrd.img
    
  2. If they are the same, please try:
    1. Boot the usb (or cd if usb doesn't work)
    2. At the boot screen select TEXT mode
    3. Hit TAB key and add to Command Line: from=/dev/sdb1
    4. Hit Enter to boot
  3. If above test has worked, I would ask you to try:
    1. Code: Select all

      mkdir -p /mnt/sdb2/bld/ab
    2. Then copy abSlak_100216.iso to /bld/ab
    3. Check Copy:

      Code: Select all

      guest@porteus:~$ ls -lh /mnt/sdb2/bld/ab/abSlak_100216.iso 
      -rw------- 1 guest guest 240M Feb 11 01:07 /mnt/sdb2/bld/ab/abSlak_100216.iso
      
    4. As in 2 above, add to Command Line: from=/dev/sdb2/bld/ab/abSlak_100216.iso and boot.
Thanks.


Results from #3 (after logging into darkstar):

Code: Select all

root@darkstar:~# cat /proc/cmdline
base_only noauto from=/dev/sdb2/bld/ab/abSlak_100216.iso

root@darkstar:~# cat /var/log/porteus-livedbg
# Recognized devices:
/dev/sr0: LABEL="Porteus" TYPE="iso9660"
/dev/sda1: UUID="ca6ce5e1-1bbd-4170-87f7-5fd0448e5f56" TYPE="reiserfs"
/dev/sda3: SEC_TYPE="msdos" UUID="4B46-EEEA" TYPE="vfat"
/dev/sda4: UUID="966b254d-20de-4376-b736-ddf89150a6b3" TYPE="reiserfs"
/dev/sda5: LABEL="kix" UUID="e737efd6-32f4-4a80-bbc1-a6ad3114b4d5" TYPE="ext2"
/dev/sda6: UUID="f554b881-2089-4c0f-8de2-70900bdc4e14" TYPE="ext2"
/dev/sda7: UUID="0d2c9e21-5e47-4dd3-a279-38551711f3dd" TYPE="swap"
/dev/sda8: UUID="AF61-DAE9" TYPE="vfat"
/dev/sda9: LABEL="iso" UUID="5bf4078e-3d9c-46e6-8a43-2dfc0eef3aeb" TYPE="ext2"
/dev/sda10: LABEL="p_10" UUID="ed3f74cd-26bb-47bd-86b0-5e690663dd55" TYPE="ext2"
/dev/sda11: UUID="6a0167f6-5cf7-412d-b85f-0076ca590371" TYPE="swap"
/dev/sdb1: SEC_TYPE="msdos" UUID="12D4-A2F1" TYPE="vfat"
/dev/sdb2: UUID="ec468a0e-7848-416d-9d29-3c74a1bfb486" TYPE="ext4"

# Booting device:
/mnt/sdb2

# Porteus data found in:
/mnt/isoloop/porteus

# Changes are stored in:
memory

# Non standard /rootcopy dir:
none

# Modules activated during boot time:
/mnt/isoloop/porteus/base/000-kernel.xzm
/mnt/isoloop/porteus/base/001-core.xzm
Linux porteus 4.4.0-porteus #3 SMP PREEMPT Sat Jan 23 07:01:55 UTC 2016 i686 AMD Sempron(tm) 140 Processor AuthenticAMD GNU/Linux
NVIDIA Corporation C61 [GeForce 6150SE nForce 430] (rev a2) MemTotal: 901760 kB MemFree: 66752 kB

Jack
Contributor
Contributor
Posts: 1246
Joined: 09 Aug 2013, 14:25
Distribution: Porteus 3.2.rc5 Mate 64 bit
Location: Marysville, OHIO USA

Re: Building Blocks

Post#127 by Jack » 12 Feb 2016, 18:13

You need to find a computer that will boot up with USB so you can see. I know the CD dose work.

When I have time I will do what you want me to do. I have all kinds of problem at my home right now.
I just like Slackware because I think it teach you about Linux to build packages where Ubuntu is like Windows you just install programs you want.

Bogomips
Full of knowledge
Full of knowledge
Posts: 2563
Joined: 25 Jun 2014, 15:21
Distribution: 3.2.2 Cinnamon & KDE5
Location: London

Re: Building Blocks

Post#128 by Bogomips » 12 Feb 2016, 23:18

Ed_P wrote:
Bogomips wrote:and only able to do so if can read filesystem on which iso resides in order to be able to loop mount the iso, in the case of isos.
Then why does the bootloader do this?
Bogomips wrote:Places Initrd in a Special Memory Fille
And this?
Bogomips wrote:Mounts Iso on Loop
Everything is already in memory, there is no need to read the filesystem to loop the iso again.
The way I understand it, it's like the division of labour, where there are strict union demarcated lines. The Kernel says, it's not its job to know about an iso mounted on a loop, which is somewhere in memory. The boot loader says it's my job to extract the kernel, decompress it and place it in memory together with initrd in a special memory file. Once done the only other responsibility is to unmount everything and exit. The Kernel's job at bootup is to just decompress the Initrd and invoke the init program which then executes the linuxrc script of Initrd.
Somewhat simplistic picture of my understanding of things. :roll:
Linux porteus 4.4.0-porteus #3 SMP PREEMPT Sat Jan 23 07:01:55 UTC 2016 i686 AMD Sempron(tm) 140 Processor AuthenticAMD GNU/Linux
NVIDIA Corporation C61 [GeForce 6150SE nForce 430] (rev a2) MemTotal: 901760 kB MemFree: 66752 kB

User avatar
brokenman
Site Admin
Site Admin
Posts: 5652
Joined: 27 Dec 2010, 03:50
Distribution: Porteus v3.2rcX all desktops
Location: Brazil
Contact:

Re: Building Blocks

Post#129 by brokenman » 12 Feb 2016, 23:51

Tested from a USB drive and found to be working.

I copied the files onto a partition on the USB drive. Changed into the boot directory and ran the porteus installer (as per a normal porteus install). Jack may need to employ the 'delay' cheat code if it is not finding the sgn file. The USB device probably needs some time to settle.

Not sure if you are interested (or it has already been posted here) in the following but I will post it anyway in case you missed it.

line 24,36,28 in rc.M throws errors on boot.

Other boot warnings/errors include:
Can't find /home/guest/p01 in fstab
Line 63 in /etc/rc.d/rc.M /usr/sbin/acpid No such file or directory
How do i become super user?
Wear your underpants on the outside and put on a cape.

Jack
Contributor
Contributor
Posts: 1246
Joined: 09 Aug 2013, 14:25
Distribution: Porteus 3.2.rc5 Mate 64 bit
Location: Marysville, OHIO USA

Re: Building Blocks

Post#130 by Jack » 12 Feb 2016, 23:59

brokenman wrote:Tested from a USB drive and found to be working.

I copied the files onto a partition on the USB drive. Changed into the boot directory and ran the porteus installer (as per a normal porteus install). Jack may need to employ the 'delay' cheat code if it is not finding the sgn file. The USB device probably needs some time to settle.

Not sure if you are interested (or it has already been posted here) in the following but I will post it anyway in case you missed it.

line 24,36,28 in rc.M throws errors on boot.

Other boot warnings/errors include:
Can't find /home/guest/p01 in fstab
Line 63 in /etc/rc.d/rc.M /usr/sbin/acpid No such file or directory
It finds the sgn file but in the next line it count down then I see the error. Maybe my USB thumb drive are to slow.
I just like Slackware because I think it teach you about Linux to build packages where Ubuntu is like Windows you just install programs you want.

User avatar
Ed_P
Contributor
Contributor
Posts: 3402
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 3.2.2 64-bit ISO
Location: Western NY, USA

Re: Building Blocks

Post#131 by Ed_P » 13 Feb 2016, 05:37

brokenman wrote:Tested from a USB drive and found to be working.

I copied the files onto a partition on the USB drive. Changed into the boot directory and ran the porteus installer
In the two cases where this is working, your test and the CD test, something else is involved in making the ISO work, the app used to create the CD and the Porteus install to create the USB drive. The files to boot are apparently in the ISO but the ISO itself appears not to be bootable. It's like it is just a big zip file. That's why even with the drivers Bogomips has added to the newest ISO it doesn't boot.
Ed

User avatar
francois
Contributor
Contributor
Posts: 5118
Joined: 28 Dec 2010, 14:25
Distribution: kde xfce porteus manjaro kubun
Location: Enfin l'été, le changement climatique attendu: le soleil.

Re: Building Blocks

Post#132 by francois » 13 Feb 2016, 09:20

It seems that you guys are working hard here. Have you adressed the creation of the devel module necessary to build vbox guest additions? Or you are not there yet.

Is is possible to get a summary of what has been achieved yet? :)
Voltaire: Le mieux est l'ennemi du bien.

Bogomips
Full of knowledge
Full of knowledge
Posts: 2563
Joined: 25 Jun 2014, 15:21
Distribution: 3.2.2 Cinnamon & KDE5
Location: London

Re: Building Blocks

Post#133 by Bogomips » 13 Feb 2016, 14:22

^ As our friend from down under would say: do refer to 1st Post of Thread, then the link and some posts leading up to it, and after, which is the whole point of the exercise. :twisted:
Jack wrote:It finds the sgn file but in the next line it count down then I see the error. Maybe my USB thumb drive are to slow.
Probably. At the boot screen you need to add perhaps delay=12 to Kernel Command Line. Have an iffy usb so put 20, which gives enough time to pull it out and push it in again so that Ready Light shows.
Kriss wrote:But if I can be of assistance with adding some new feature or improving something, just tell me and I'll try... =)
Edited linuxrc for overlayfs. You could certainly help with checking copy2ram, ramsize=, zram=. This is what I got:

Code: Select all

root@darkstar:~# date
Sat Feb 13 23:00:09  2016
root@darkstar:~# cat /proc/cmdline
initrd=initrd.img 3 copy2ram ramsize=30% noauto from=/dev/sdb2/bld/ab/abSlak_100216.iso zram=30% BOOT_IMAGE=vmlinuz

root@darkstar:~# cat /var/log/porteus-livedbg
# Recognized devices:
/dev/sda1: UUID="ca6ce5e1-1bbd-4170-87f7-5fd0448e5f56" TYPE="reiserfs"
/dev/sda3: SEC_TYPE="msdos" UUID="4B46-EEEA" TYPE="vfat"
/dev/sda4: UUID="966b254d-20de-4376-b736-ddf89150a6b3" TYPE="reiserfs"
/dev/sda5: LABEL="kix" UUID="e737efd6-32f4-4a80-bbc1-a6ad3114b4d5" TYPE="ext2"
/dev/sda6: UUID="f554b881-2089-4c0f-8de2-70900bdc4e14" TYPE="ext2"
/dev/sda7: UUID="0d2c9e21-5e47-4dd3-a279-38551711f3dd" TYPE="swap"
/dev/sda8: UUID="AF61-DAE9" TYPE="vfat"
/dev/sda9: LABEL="iso" UUID="5bf4078e-3d9c-46e6-8a43-2dfc0eef3aeb" TYPE="ext2"
/dev/sda10: LABEL="p_10" UUID="ed3f74cd-26bb-47bd-86b0-5e690663dd55" TYPE="ext2"
/dev/sda11: UUID="6a0167f6-5cf7-412d-b85f-0076ca590371" TYPE="swap"
/dev/sdb1: SEC_TYPE="msdos" UUID="12D4-A2F1" TYPE="vfat"
/dev/sdb2: UUID="ec468a0e-7848-416d-9d29-3c74a1bfb486" TYPE="ext4"

# Booting device:
/mnt/sdb2

# Porteus data found in:
/mnt/isoloop/porteus

# Changes are stored in:
memory

# Non standard /rootcopy dir:
none

# Modules activated during boot time:
/memory/copy2ram/000-kernel.xzm
/memory/copy2ram/001-core.xzm

root@darkstar:~# df -h .
Filesystem      Size  Used Avail Use% Mounted on
overlay         435M  231M  204M  54% /

root@darkstar:~# free -m
              total        used        free      shared  buff/cache   available
Mem:            868          27         505         236         335         578
Swap:           905           0         905
root@darkstar:~# df -h
Filesystem      Size  Used Avail Use% Mounted on
tmpfs           435M  6.4M  428M   2% /run
devtmpfs        431M     0  431M   0% /dev
tmpfs           435M  231M  204M  54% /mnt/live/memory
/dev/loop1       88M   88M     0 100% /mnt/live/memory/images/000-kernel
/dev/loop2      140M  140M     0 100% /mnt/live/memory/images/001-core
overlay         435M  231M  204M  54% /
/dev/sda9        77G   72G  1.4G  99% /root//mnt/sda9
In comparison my normal Porteus:

Code: Select all

guest@porteus:~$ df -h .
Filesystem      Size  Used Avail Use% Mounted on
aufs            265M  6.6M  258M   3% /
guest@porteus:~$ free -m
             total       used       free     shared    buffers     cached
Mem:           880        865         14          0         26        454
-/+ buffers/cache:        384        495
Swap:          644          9        635
guest@porteus:~$ df -h
Filesystem                             Size  Used Avail Use% Mounted on
aufs                                   265M  6.6M  258M   3% /
devtmpfs                               440M  4.0K  440M   1% /dev
/dev/sda4                              3.9G  3.8G  101M  98% /mnt/sda4
/mnt/live/run                          441M  347M   94M  79% /run
/dev/sda9                               77G   72G  1.4G  99% //mnt/sda9
There seems to be a 54M shortfall in the overlay system.
Last edited by Bogomips on 14 Feb 2016, 00:46, edited 2 times in total.
Reason: Replying Jack
Linux porteus 4.4.0-porteus #3 SMP PREEMPT Sat Jan 23 07:01:55 UTC 2016 i686 AMD Sempron(tm) 140 Processor AuthenticAMD GNU/Linux
NVIDIA Corporation C61 [GeForce 6150SE nForce 430] (rev a2) MemTotal: 901760 kB MemFree: 66752 kB

User avatar
francois
Contributor
Contributor
Posts: 5118
Joined: 28 Dec 2010, 14:25
Distribution: kde xfce porteus manjaro kubun
Location: Enfin l'été, le changement climatique attendu: le soleil.

Re: Building Blocks

Post#134 by francois » 13 Feb 2016, 19:40

I understand that the essential info is in the first post.

Thanks. :)
Voltaire: Le mieux est l'ennemi du bien.

Bogomips
Full of knowledge
Full of knowledge
Posts: 2563
Joined: 25 Jun 2014, 15:21
Distribution: 3.2.2 Cinnamon & KDE5
Location: London

Re: Building Blocks

Post#135 by Bogomips » 14 Feb 2016, 21:29

brokenman wrote:Tested from a USB drive and found to be working.

I copied the files onto a partition on the USB drive. Changed into the boot directory and ran the porteus installer (as per a normal porteus install).
Thanks for verification. Now, on to ntfs. Modprobed ntfs.ko, so think should adjust linuxrc to use ntfs instead of ntfs-3g.

Using neko's iso 2 bootable usb tool, have been been able to boot usb from bios (thanks to brainstorm suggestions contributed by your compatriot in my other thread), which also worked: Booting from USB
  • Porteus data Extracted from Iso

    Code: Select all

    Sat Feb 13 00:55:36  2016
    root@darkstar:~# cat /proc/cmdline
    initrd=initrd.img 3 from=/dev/sdb1 BOOT_IMAGE=vmlinuz
    root@darkstar:~# cat /var/log/porteus-livedbg
    # Recognized devices:
    /dev/sda1: UUID="ca6ce5e1-1bbd-4170-87f7-5fd0448e5f56" TYPE="reiserfs"
    /dev/sda3: SEC_TYPE="msdos" UUID="4B46-EEEA" TYPE="vfat"
    /dev/sda4: UUID="966b254d-20de-4376-b736-ddf89150a6b3" TYPE="reiserfs"
    /dev/sda5: LABEL="kix" UUID="e737efd6-32f4-4a80-bbc1-a6ad3114b4d5" TYPE="ext2"
    /dev/sda6: UUID="f554b881-2089-4c0f-8de2-70900bdc4e14" TYPE="ext2"
    /dev/sda7: UUID="0d2c9e21-5e47-4dd3-a279-38551711f3dd" TYPE="swap"
    /dev/sda8: UUID="AF61-DAE9" TYPE="vfat"
    /dev/sda9: LABEL="iso" UUID="5bf4078e-3d9c-46e6-8a43-2dfc0eef3aeb" TYPE="ext2"
    /dev/sda10: LABEL="p_10" UUID="ed3f74cd-26bb-47bd-86b0-5e690663dd55" TYPE="ext2"
    /dev/sda11: UUID="6a0167f6-5cf7-412d-b85f-0076ca590371" TYPE="swap"
    /dev/sdb1: SEC_TYPE="msdos" UUID="12D4-A2F1" TYPE="vfat"
    /dev/sdb2: UUID="ec468a0e-7848-416d-9d29-3c74a1bfb486" TYPE="ext4"
    
    # Booting device:
    /mnt/sdb1
    
    # Porteus data found in:
    /mnt/sdb1/porteus
    
    # Changes are stored in:
    memory
    
    # Non standard /rootcopy dir:
    none
    
    # Modules activated during boot time:
    /mnt/sdb1/porteus/base/000-kernel.xzm
    /mnt/sdb1/porteus/base/001-core.xzm
  • Porteus data in Iso on USB

    Code: Select all

    root@darkstar:~# date
    Sat Feb 13 01:01:37  2016
    root@darkstar:~# cat /proc/cmdline
    initrd=initrd.img 3 from=/dev/sdb2/bld/ab/abSlak_100216.iso BOOT_IMAGE=vmlinuz
    root@darkstar:~# cat /var/log/porteus-livedbg
    # Recognized devices:
    /dev/sda1: UUID="ca6ce5e1-1bbd-4170-87f7-5fd0448e5f56" TYPE="reiserfs"
    /dev/sda3: SEC_TYPE="msdos" UUID="4B46-EEEA" TYPE="vfat"
    /dev/sda4: UUID="966b254d-20de-4376-b736-ddf89150a6b3" TYPE="reiserfs"
    /dev/sda5: LABEL="kix" UUID="e737efd6-32f4-4a80-bbc1-a6ad3114b4d5" TYPE="ext2"
    /dev/sda6: UUID="f554b881-2089-4c0f-8de2-70900bdc4e14" TYPE="ext2"
    /dev/sda7: UUID="0d2c9e21-5e47-4dd3-a279-38551711f3dd" TYPE="swap"
    /dev/sda8: UUID="AF61-DAE9" TYPE="vfat"
    /dev/sda9: LABEL="iso" UUID="5bf4078e-3d9c-46e6-8a43-2dfc0eef3aeb" TYPE="ext2"
    /dev/sda10: LABEL="p_10" UUID="ed3f74cd-26bb-47bd-86b0-5e690663dd55" TYPE="ext2"
    /dev/sda11: UUID="6a0167f6-5cf7-412d-b85f-0076ca590371" TYPE="swap"
    /dev/sdb1: SEC_TYPE="msdos" UUID="12D4-A2F1" TYPE="vfat"
    /dev/sdb2: UUID="ec468a0e-7848-416d-9d29-3c74a1bfb486" TYPE="ext4"
    
    # Booting device:
    /mnt/sdb2
    
    # Porteus data found in:
    /mnt/isoloop/porteus
    
    # Changes are stored in:
    memory
    
    # Non standard /rootcopy dir:
    none
    
    # Modules activated during boot time:
    /mnt/isoloop/porteus/base/000-kernel.xzm
    /mnt/isoloop/porteus/base/001-core.xzm

Now roadie who cannot run 64 bit informed me in a pm on 6th Feb, which I hope he does not mind me quoting from:
I'm using a 4.3.3 kernel I compiled some time ago to use in an early Nemesis, and using your initrd.img. The kernel doesn't have overlay compiled in.
I threw a current base together and it boots fine to a login, actually went straight to an Xfce when I added it in. Looking at your lsmod, I see that overlay is loaded, as it is in mine.
And in a later pm:

Code: Select all

bash-4.3# df -h
Filesystem      Size  Used Avail Use% Mounted on
tmpfs           499M  6.1M  493M   2% /mnt/live
devtmpfs        497M     0  497M   0% /dev
/dev/sda5       6.5G  4.8G  1.5G  77% /mnt/sda5
/dev/sdb1        30G   21G  7.5G  74% /mnt/sdb1
tmpfs           499M  441M   58M  89% /mnt/live/memory
/dev/loop0       33M   33M     0 100% /mnt/live/memory/images/000-kernel
/dev/loop1       63M   63M     0 100% /mnt/live/memory/images/001-core
/dev/loop2      256K  256K     0 100% /mnt/live/memory/images/lxterminal-0.2.0-i486-1ponce
overlay         499M  441M   58M  89% /
tmpfs           499M  240K  499M   1% /run
Looks like Porteus format Overlay could have made it right through to XFCE!
brokenman wrote:Not sure if you are interested (or it has already been posted here) in the following but I will post it anyway in case you missed it.

line 24,36,28 in rc.M throws errors on boot.

Other boot warnings/errors include:
Can't find /home/guest/p01 in fstab
Line 63 in /etc/rc.d/rc.M /usr/sbin/acpid No such file or directory
Wasn't sure if worth pursuing, but since you mention it, will pursue it myself or maybe others could for that matter?
Linux porteus 4.4.0-porteus #3 SMP PREEMPT Sat Jan 23 07:01:55 UTC 2016 i686 AMD Sempron(tm) 140 Processor AuthenticAMD GNU/Linux
NVIDIA Corporation C61 [GeForce 6150SE nForce 430] (rev a2) MemTotal: 901760 kB MemFree: 66752 kB

Post Reply