Porteus

Please mention your setup and which architecture (i586/x86_64) and which desktop your are using when posting bugs.

Things to remember:

This thread is for BUGS and not complaints or preferences.
Please confirm the bug on multiple hardware setups if possible.
Supply code or suggestions to rectify the problem where possible.

Acer Aspire Laptop, 4.0 XFCE x86_64, WiFi connected.

I´m not sure wether this is intentional or not:
Everything is fine when using a root terminal, but within a user terminal the "update-porteus" script fails:

ip command is in /sbin. Since /sbin is not in guest's PATH, the script fails.

Many, MANY thanks for Porteus 4.0.

I am running 32 bit version of Porteus 4.0 under Virtual Box.
Remastered a new ISO version with the core and crippled source modules, all ok.

Using the menus, made a Virtual Box Guest Additions module, module created ok, activated ok, and transferred to host for adding to iso.
For testing I also made modules with gdb 8.1 and valgrind 3.13.0 and those modules are ok.

Made a new iso with the tree modules above added, and it boots ok.
Valgrind works, gdb also, but vbox-guest module was not activated.

Doing df on the command line the vbox module does not appear, but the other modules appear on /mnt/live.

As the Porteus ISO is mounted on /mnt/sr0 going there and activating manually the vbox-guest module works, and appears on /mnt/live.

There are only some debug messages from glibtop.
Could that be the reason?

Many thanks once again.

I can take a look at that later. But I always had this feeling that the vbox-guest package doesn't work quite well on Linux -- I know it works sometimes, but that's the problem: sometimes...

Do you mind if I ask you why you want to use it? Lots of people think that it's needed to accomplish things that in fact we can do without it, like transferring files between virtual machine and real machine

Saudações do Brasil!

Off-Topic:
Why I need VBox guest and a 32 bit Linux? I need to teach IA32 Assembly and C programming under Linux. The students have a variety of machines with the majority of them being Windows, some OS X and some 64 bits Linux.

Yes, I know that one can develop and run 32 bit Linux apps under 64 bit Linux, but that is too much for a typical student. So we give them instructions on how to Install Virtual Box, how to create a shared folder, and a Porteus Iso with all the development tools needed already installed.

When they place the Virtual Machine in a very weird state (using a safe language for a forum), they just need to reboot it, and they do not loose the work, as it is saved on the shared folder.

We do not have to support lots of different weird Linuxes, as some distros out there are very weird. Last one I saw it was a distro that when installing Bison find not instal the corresponding library...

And when they do "strange things" like "fork bombs" it's on their machine.


And "Olá de Portuga!"

So we give them instructions on how to Install Virtual Box, how to create a shared folder, and a Porteus Iso with all the development tools needed already installed.

It's so great to see that Porteus helps kids in schools with learning! Keep up the good work.

Thanks for the offer of help fulalas. I would like to get this virtualbox guest more solid.

Added in 54 minutes 59 seconds:

but vbox-guest module was not activated.
Doing df on the command line the vbox module does not appear, but the other modules appear on /mnt/live.
As the Porteus ISO is mounted on /mnt/sr0 going there and activating manually the vbox-guest module works, and appears on /mnt/live.

Confirmed. The virtualbox-guest module is not loaded during boot on the porteus guest. Loading it manually from /mnt/sr0/porteus/modules/ works fine and you can then go on as usual and create shared folders etc. Nothing in TTY1 to show failure to load.

Booting wihtout 003 modules (textmode) the guest module loads OK.

Porteus 4.0 MATE

Mounting modules via Caja Actions Menu doesn't work (modules won't get activated). Any thoughts?

Thanks!

M. Eerie wrote: ↑

02 May 2018, 17:54

Mounting modules via Caja Actions Menu doesn't work (modules won't get activated). Any thoughts?

I just tried and it works. Module got mounted at /mnt/loop. What error are you getting?

Hi paf,
If need, another example here VirtualBox + VBoxGuestAdditions.iso + Porteus iso (Russian topic)

@jssouza

jssouza wrote: ↑

02 May 2018, 18:03

What error are you getting?

No error at all. The module is just not loaded.

M. Eerie wrote: ↑

02 May 2018, 17:54

Mounting modules via Caja Actions Menu doesn't work (modules won't get activated). Any thoughts?

Ok, just read your post again. You say the module wont get activated. It should not. It only gets mounted.

jssouza wrote: ↑

02 May 2018, 18:37

It only gets mounted

Ok, I understand. Can't it be activated via right-menu? I'd swear I've seen this option before.

Thanks for your answers.

M. Eerie wrote: ↑

02 May 2018, 19:40

Ok, I understand. Can't it be activated via right-menu?

Yes you can. Right click and select "Open With Activate"

Blaze wrote: ↑

02 May 2018, 18:12

Hi paf,
If need, another example here VirtualBox + VBoxGuestAdditions.iso + Porteus iso (Russian topic)

Many thanks, but the example on the link (if Google translate works fine) is for manually activating Virtual Box, and that works perfectly.
I can make a module with Virtual Box Guest additions and the module is made, and if I activate "by hand" the module, the module works.
Putting the module on a new Iso, does not work. But other modules on a new Iso, work...

Next week I will have time to see better what is happening ( I hope ).
Many thanks