[Sugar-devel] Apply Changes to Sugar live build.

[Shivam Rai]

I applied changes in a module through bash terminal in sugar live build.
I shutdown and started machine. The changes were not kept. What can be the
reason?

[Chihurumnaya Ibiam]

How did you apply the changes?

And also, can you keep similar discussions to one particular thread as it
makes it easier to
find for future reference as you already opened a similar thread earlier.
--
Ibiam Chihurumnaya

Post by Shivam Rai
I applied changes in a module through bash terminal in sugar live build.
I shutdown and started machine. The changes were not kept. What can be the
reason?
_______________________________________________
Sugar-devel mailing list
http://lists.sugarlabs.org/listinfo/sugar-devel

[Shivam Rai]

In terminal activity,I changed to super user with su command. Then cd/ to
respective directory. Then, vi(command) module.py.
It opened the module.Switched to insert mode(i). Changed the code. Then
saved and exit it using (:wq! )
I confirmed the changes by reopening the module. They are there. But when I
restarted it the changes were not kept. The module was in its original
state.

And Yes, I will make sure to keep related queries in same thread.

Post by Chihurumnaya Ibiam
How did you apply the changes?
And also, can you keep similar discussions to one particular thread as it
makes it easier to
find for future reference as you already opened a similar thread earlier.
--
Ibiam Chihurumnaya

Post by Shivam Rai
I applied changes in a module through bash terminal in sugar live build.
I shutdown and started machine. The changes were not kept. What can be
the reason?
_______________________________________________
Sugar-devel mailing list
http://lists.sugarlabs.org/listinfo/sugar-devel

[Chihurumnaya Ibiam]

What directory did you make the changes in?

Post by Shivam Rai
In terminal activity,I changed to super user with su command. Then cd/ to
respective directory. Then, vi(command) module.py.
It opened the module.Switched to insert mode(i). Changed the code. Then
saved and exit it using (:wq! )
I confirmed the changes by reopening the module. They are there. But when
I restarted it the changes were not kept. The module was in its original
state.
And Yes, I will make sure to keep related queries in same thread.

Post by Chihurumnaya Ibiam
How did you apply the changes?
And also, can you keep similar discussions to one particular thread as it
makes it easier to
find for future reference as you already opened a similar thread earlier.
--
Ibiam Chihurumnaya

Post by Shivam Rai
I applied changes in a module through bash terminal in sugar live build.
I shutdown and started machine. The changes were not kept. What can be
the reason?
_______________________________________________
Sugar-devel mailing list
http://lists.sugarlabs.org/listinfo/sugar-devel

[Shivam Rai]

/usr/lib/python3.8/site-packages/jarabe/desktop/favorites layout.py

for testing commit 118e73

P.s. I am using sugarlivebuild as vm in virtual box.

Post by Chihurumnaya Ibiam
What directory did you make the changes in?

Post by Shivam Rai
In terminal activity,I changed to super user with su command. Then cd/
to respective directory. Then, vi(command) module.py.
It opened the module.Switched to insert mode(i). Changed the code. Then
saved and exit it using (:wq! )
I confirmed the changes by reopening the module. They are there. But when
I restarted it the changes were not kept. The module was in its original
state.
And Yes, I will make sure to keep related queries in same thread.

Post by Chihurumnaya Ibiam
How did you apply the changes?
And also, can you keep similar discussions to one particular thread as
it makes it easier to
find for future reference as you already opened a similar thread earlier.
--
Ibiam Chihurumnaya

Post by Shivam Rai
I applied changes in a module through bash terminal in sugar live build.
I shutdown and started machine. The changes were not kept. What can be
the reason?
_______________________________________________
Sugar-devel mailing list
http://lists.sugarlabs.org/listinfo/sugar-devel

[Chihurumnaya Ibiam]

Yeah, that's a debian specific convention, you can read about it here
https://wiki.debian.org/Python under "Deviations from Upstream" so your
changes should be made to /usr/lib/python3.7/dist-packages/jarabe.

You can also make your changes to sugar sources in /usr/src/sugar*/ and
build then use rsync or just move the files where needed.
You can also see this in the live build,
https://github.com/sugarlabs/sugar-live-build/blob/master/src/config/hooks/normal/0900-sugar.hook.chroot
.

Post by Shivam Rai
/usr/lib/python3.8/site-packages/jarabe/desktop/favorites layout.py
for testing commit 118e73
P.s. I am using sugarlivebuild as vm in virtual box.

Post by Chihurumnaya Ibiam
What directory did you make the changes in?

Post by Shivam Rai
In terminal activity,I changed to super user with su command. Then cd/
to respective directory. Then, vi(command) module.py.
It opened the module.Switched to insert mode(i). Changed the code. Then
saved and exit it using (:wq! )
I confirmed the changes by reopening the module. They are there. But
when I restarted it the changes were not kept. The module was in its
original state.
And Yes, I will make sure to keep related queries in same thread.

Post by Chihurumnaya Ibiam
How did you apply the changes?
And also, can you keep similar discussions to one particular thread as
it makes it easier to
find for future reference as you already opened a similar thread earlier.
--
Ibiam Chihurumnaya
On Wed, Apr 14, 2021 at 11:18 AM Shivam Rai <

Post by Shivam Rai
I applied changes in a module through bash terminal in sugar live build.
I shutdown and started machine. The changes were not kept. What can be
the reason?
_______________________________________________
Sugar-devel mailing list
http://lists.sugarlabs.org/listinfo/sugar-devel

[Srevin Saju]

Post by Shivam Rai
In terminal activity,I changed to super user with su command. Then cd/ to
respective directory. Then, vi(command) module.py.
It opened the module.Switched to insert mode(i). Changed the code. Then
saved and exit it using (:wq! )
I confirmed the changes by reopening the module. They are there. But when I
restarted it the changes were not kept. The module was in its original
state.

As you mentioned about using the live build, I hope you are aware that the
sugar live build is not persistent. Live ISOs keep their changes only in the
RAM. once they are shutdown, they no longer carry the old changes across,
(unless you have installed the live build to a virtual hard disk ¯\_(ツ)_/¯),
but there is a great possibility that you are running it live from the ISO file
itself.

Cheers.

Post by Shivam Rai
And Yes, I will make sure to keep related queries in same thread.

Post by Chihurumnaya Ibiam
How did you apply the changes?
And also, can you keep similar discussions to one particular thread as it
makes it easier to
find for future reference as you already opened a similar thread earlier.
--
Ibiam Chihurumnaya

Post by Shivam Rai
I applied changes in a module through bash terminal in sugar live build.
I shutdown and started machine. The changes were not kept. What can be
the reason?
_______________________________________________
Sugar-devel mailing list
http://lists.sugarlabs.org/listinfo/sugar-devel

[Shivam Rai]

I made virtual hard disk from sugarlivebuild.iso file and Later booted my
virtual machine from that virtual hard disk . Applied changes, but on
restart the changes were not kept.

Post by Shivam Rai

Post by Shivam Rai
In terminal activity,I changed to super user with su command. Then cd/

to

Post by Shivam Rai
respective directory. Then, vi(command) module.py.
It opened the module.Switched to insert mode(i). Changed the code. Then
saved and exit it using (:wq! )
I confirmed the changes by reopening the module. They are there. But

when I

Post by Shivam Rai
restarted it the changes were not kept. The module was in its original
state.

As you mentioned about using the live build, I hope you are aware that the
sugar live build is not persistent. Live ISOs keep their changes only in the
RAM. once they are shutdown, they no longer carry the old changes across,
(unless you have installed the live build to a virtual hard disk ¯\_(ツ)_/¯),
but there is a great possibility that you are running it live from the ISO file
itself.
Cheers.

Post by Shivam Rai
And Yes, I will make sure to keep related queries in same thread.

Post by Chihurumnaya Ibiam
How did you apply the changes?
And also, can you keep similar discussions to one particular thread as

it

Post by Shivam Rai

Post by Chihurumnaya Ibiam
makes it easier to
find for future reference as you already opened a similar thread

earlier.

Post by Shivam Rai

Post by Chihurumnaya Ibiam
--
Ibiam Chihurumnaya
On Wed, Apr 14, 2021 at 11:18 AM Shivam Rai <

Post by Shivam Rai
I applied changes in a module through bash terminal in sugar live

build.

Post by Shivam Rai

Post by Chihurumnaya Ibiam

Post by Shivam Rai
I shutdown and started machine. The changes were not kept. What can be
the reason?
_______________________________________________
Sugar-devel mailing list
http://lists.sugarlabs.org/listinfo/sugar-devel

[James Cameron]

That is an expected outcome. Don't make a virtual hard disk from the
ISO. That way you have a live build as a hard disk, without any
persistence. Instead, follow the normal Debian procedures for
installing the operating system to a new virtual hard disk.

Sorry, I don't have a reference to the Debian documentation.

I made virtual hard disk from  sugarlivebuild.iso file and Later booted my
virtual machine from that virtual hard disk . Applied changes, but on restart
the changes were not kept.

In terminal activity,I changed to super user with su command. Then  cd/

to

respective directory. Then, vi(command) module.py.
It opened the module.Switched to insert mode(i). Changed the code. Then
saved and exit it using (:wq! )
I confirmed the changes by reopening the module. They are there. But when

I

restarted it the changes were not kept. The module was in its original
state.

As you mentioned about using the live build, I hope you are aware that the
sugar live build is not persistent. Live ISOs keep their changes only in the
RAM. once they are shutdown, they no longer carry the old changes across,
(unless you have installed the live build to a virtual hard disk ¯\_(ツ)_/
¯),
but there is a great possibility that you are running it live from the ISO file
itself.
Cheers.

And Yes, I will make sure to keep related queries in same thread.

Post by Chihurumnaya Ibiam
How did you apply the changes?
And also, can you keep similar discussions to one particular thread as

it

Post by Chihurumnaya Ibiam
makes it easier to
find for future reference as you already opened a similar thread

earlier.

Post by Chihurumnaya Ibiam
--
Ibiam Chihurumnaya
On Wed, Apr 14, 2021 at 11:18 AM Shivam Rai <[4]

Post by Shivam Rai
I applied changes in a module through bash terminal in sugar live

build.

Post by Chihurumnaya Ibiam

Post by Shivam Rai
I shutdown and started machine. The changes were not kept. What can be
the reason?
_______________________________________________
Sugar-devel mailing list
[6]http://lists.sugarlabs.org/listinfo/sugar-devel

[6] http://lists.sugarlabs.org/listinfo/sugar-devel
_______________________________________________
Sugar-devel mailing list
http://lists.sugarlabs.org/listinfo/sugar-devel