SV-TUTZ : BT3b PERSISTENT CHANGES

[ats1080]

im running the usb drive version and i was tying out the persistent changes boot option but havn't had any luck with it actually saving anything. is there something i need to do?

EDIT SOLVED SEE SV TUT

[shamanvirtuel]

if you want to use persistent changes mode .....


you can'T DO IT ON A FAT 32 ONE YOU MUST WIPE YOUR USB & FORMAT IT EXT2, EXTRACT YOUR ISO .....

CD ONTO THE BOOT DIR / usb

BOOTINST.SH WILL NOT WORK WITH EXT2 BUT ONLY WITH FAT32

YOU MUST USE BOOTLILO.SH

RUN IT

THIS ONE CAN INSTALL ON ALL TYPE OF PARTITIONS AND CREATE A FOLDER CALLED SLAXCHANGES UNDER YOUR /BOOT DIRECTORY

DON'T TOUCH THIS FOLDER EVEN IF EMPTY

REBOOT ON YOUR NEW INSTALL

SELECT SAVE CHANGES MODE AND YOU're DONE
##########################################"

OR HERE IS THE METHOD I USED (RECOMENDED) THIS ONE IS BETTER BECAUSE YOU CAN DO IT ON FAT32 SO NO NEED TO WIPE THE DRIVE & REINSTALL ..........

BOOT YOUR USB

CD /mnt/XXXXXXX (THE USB WHERE IS THE BOOT DIR)

CD ./boot/syslinux

chmod +Xx lilo

chmod +Xx syslinux

OPEN syslinux.cfg

SELECT THE MODE YOU WANT TO ADD CHANGES & all options you want like rename modes , remove unused modes

EDIT APPEND LINE

ADD changes=/dev/XXX (AN EXT2 PRIMARY PARTITION SOMEWHERE IE ON A HD)

SAVE SYSLINUX.CFG

syslinux -s -f /dev/xxx1 (the partition where you extract iso and run bootlilo.sh)

reboot /select the mode where you added the changes mod

THAT's ALL !!!! 100 % PROOF OF CONCEPT !!!


#####################################

ENJOY !!!

[ats1080]

alright thanks ill give it a go.

[barbsie]

you can also save changes on the USB itself in FAT32, using a loop file (available on slax mirror). I was looking at a solution of using a loop-aes file just like in Knoppix, where the changes are changed on an encrypted file.

[juststormy]

you can also save changes on the USB itself in FAT32, using a loop file (available on slax mirror). I was looking at a solution of using a loop-aes file just like in Knoppix, where the changes are changed on an encrypted file.

Uhhhm barbsie can you explain this a little bit more?
A small tutorial would be nice. thx!

[shamanvirtuel]

yep remember that ...

nifty future ... when you say encrypted it's aes 256 ?

maybe the crypting process in real time will be too much ressource consuming...........

[wyze]

And this works as well

http://backtrack.offensive-security.com/index.php/Howto#save_configuration_to_USB_stick

[merlin051]

ok, created a partition on hda4 using ext2(used hirens)

made the changes to syslinux.cfg, upon booting into the changed mode, i egt the following error

mount: mounting aufs on union failed
fatal error - can't setup union (aufs)
Something went wrong this should never happen
please reboot your computer wiht CTRL+ALT+DEL

any idea's?

[hm2075]

i get the same error,

i think there is a problem with the changes line

[merlin051]

Ok, tried creating a ext2 partition on my 2gb stick, and put the same mods in place, but i'm still getting the same error.

read through all the BT2 save changes threads, still think i'm doing it right..

I'm gonna try formatting with ext2 now the trying to use the bootlilo.sh and see what that does for me.

Tried all of the above and still no joy :-/

[St3f@n]

Here it is the same.
2GB Stick (1,1GB primary Fat32, 500MB parimary Ext2, rest Fat32)
Got the same error.

md5 checksum is ok!!
formated and wiped the usb device serveral time,
make it bootable under windows, AND several times under Linux. no chance.

Next week i will try out an other USB-Stick.
Under BT2 this one works well, with the same config.

btw: the mounted ext2-Partition is not "green" when i show in dir /mnt/... all others (hda, sdb1 -the fast32 one with the system, and sdb3 - the fat32 for other data) are "green" displayed

any ideas, out there guys?
think i edited the "changes=/dev...." in syslinux.cfg right (using vi-Editor)

no problems with BT2

[St3f@n]

Update:

tested an other usb-key. the same problem at all

an other test fails also: take an second usb-key, with only a 2GB ext2 partition. edit the syslinux.cfg "changes=/dev/sdc1" but also the same error occured:

setting up directory for changes
/dev/sdc1
testing the filesystem for posix compatibility
setup union directory (using aufs, with adba=none)
mount: mounting aufs on union failed
Fatal error occured - can't .......

a few tests later, i am testing the stick with the my BT2-UsbStick the BT2 changes partition does it!!

has nobody out there any solution, or can explain me the the errormessages coming up?

SOLVED THE PROBLEM: Manually create in ext2 partition the "changes" folder. now it works!

[merlin051]

care to go into more detail on that please?

[St3f@n]

@merlin051:
create in your ext2 partition (this partition u will save the changes) a folder named "changes" i.e. /dev/sdb2/changes,

mount /dev/sdb2
mkdir changes

make sure your line in syslinux.cfg depends i.e. "changes=/dev/sdb2 ..."
thats all.

Tested this with 3USB-Stick (won`t save the changes all the time with the error messages on top of this thread, all works well, and changes are ok on next boot.

very lucky!

[merlin051]

did the above and now i'm getting past the aufs erroe and hitting a new one:

usage: init 0123456SsQqAaBbCcUu

then the scroll lock and caps lock led's start flashing and it just sits there, did some quick googleing and i think that means i'm telling it to look for something it cant find...

gonna go over what i did again and see if i can fix the error.


EDIT

Solved. apparently since my fingers are too fat for the buttons i managed to screw my syslinux.cfg file up, 35% of the APPEND line was tabbed down to the next line, moved this back up and my problem was sorted.

[abitaz]

Please tell me what I'm missing.
I formatted the 2GB USB Drive using a 1500MB ext2 primary and a 500MB ext2 primary. I copied the folders to sdb1 and ran bootlilo.sh. I edited the kde line and the persistent changes line in syslinux to include changes=/dev/sdb2. I added a folder on sdb2 named "changes". When I boot it doesn't even make a folder for changes on sdb2, it makes it on /mnt/tmp/changes, setting up directory for changes
/mnt/tmp/changes (or slaxchanges)
testing the filesystem for posix compatibility
setup union directory (using aufs, with adba=none)
mount: mounting aufs on union failed
Fatal error occured - can't .......

Then I get the same error as everyone. I've been working on this for 3 days and would really appreciate any help.

[St3f@n]

i dont know exactly what to do ( i never run bootlilo.sh due to use a fat32 partition) But when your read SVs thread on top of this thread, i think u dont need to edit the syslinux.cfg.

format ext2
copy BT2 Files on it
Run bootlilo.sh (empty folder "slaxchanges" under /boot was created)
do NOT edit syslinux.cfg
reboot your system
take "changes" option in bootmenu

and it does!

[abitaz]

UPDATE: I got it working with a fat32 and ext2 together. I think the first time I did that I made the ext2 partition with PARTED and that didn't work well for me. I made in with cfdisk now, and it's working well. Thanks all.



Thanks for the reply. I'll try that. I think I tried it, but I've tried so many different setups that who knows. The only problem is that the boot menu doesn't seem to show up in bootlilo. We'll see. Thanx.

EDIT: Yep, I tried it again and no luck. It starts by finding data on /dev/sdb1, but then it works with /mnt/tmp/ and the slaxchanges folder in tmp which obviously doesn't exist. Maybe there's something I have to edit in lilo.conf.
Still can use some help Thanks.




i dont know exactly what to do ( i never run bootlilo.sh due to use a fat32 partition) But when your read SVs thread on top of this thread, i think u dont need to edit the syslinux.cfg.

format ext2
copy BT2 Files on it
Run bootlilo.sh (empty folder "slaxchanges" under /boot was created)
do NOT edit syslinux.cfg
reboot your system
take "changes" option in bootmenu

and it does!

[Deathray]

Shamanvirtuel's tutorial worked perfectly. But I was wondering if it was possible
to change the
changes=/dev/XXX (AN EXT2 PRIMARY PARTITION SOMEWHERE IE ON A HD)
to the usb pen drive itself? So that all changes were saved to the usb drive.
Is that possible under fat32? Or do I have to re-format ext2?
Or is it possible to create a new partion in the usb pen drive as ext2
if fat32 is not supported?

[abitaz]

I have it set to save on the USB. Yes, you need to save on an ext2 partition. Either format the whole stick to ext2 and use lilo, which didn't work well for me. I have the BT3 files on a fat32 partition and save to a separate ext2 on the stick. Good luck!!

[Deathray]

Ok thanks a lot, saved me some time. Ill go ahead and create a new ext2 partition and see if I can get it to work ;)
EDIT. Works perfectly, thanks alot :D ..

[Deathray]

Just a summary of what I did for other people looking for help.
This made my 2 gb USB Pen Drive boot BT3 beta and save every change I made on the same disk it was booted from.


In order to have backtrack save changes to the same drive it is booted from, it
should have at least 1.2 gb. If the usb pen drive has less than this, do not worry, you can make the changes get saved to your hard disk.
For that, please follow shamanvirtuel's tutorial farther up.

Step 1. Split the usb pen drive into 2 partitions*. First partition (A) should be precisely 1 gb and FAT32 filesystem. Second partition (B) should have the remaining diskspace and be in EXT2 filesystem.

Step 2. Copy bt3 and boot directory to partition A.

Step 3. Manually create folder "changes" at root directory of partition B.

Step 4. Execute /boot/bootinst.sh

Step 5. Open terminal and CD to /boot/syslinux on partition A. Type
chmod +Xx lilo
chmod +Xx syslinux

Step 6. Open /boot/syslinux/syslinux.cfg
At the end of the APPEND line, under the mod you are planning to use. (Example KDE or simply text mode), add:
changes=/dev/XXX
XXX Should be replaced with the name of partition B on the USB Pendrive.
In my case, /dev/sdb2.
SAVE SYSLINUX.CFG

Step 7. Reboot and select the mode where you added the changes mod from step 6.
Credit goes to SV + rest in this thread, who helped me get it to work ;)

*I used qtparted from backtrack to split the usb into 2 partitions(easy with user interface). You could also follow DaKahuna's guide further down.
backtrack 3 beta bt3 usb save changes usb drive persistent changes save configurations to usb pen drive

[darth davidious]

Been using the Live disk version 2 and now 3. My hats off to the folks who created this awesome version of Linux.

This may be a dumb question but how do you partition the usb pen? (Step 1. Split the usb pen drive into 2 partitions). I tried gparted and other programs and google doesnt seem to have answers. I am sure there's prob a command way to do it like fdisk or mkfs but i can't seem to find any docs on it I want to split my 2 GB drive into fat32 and ext2 but I can't seem to find the way. Any help will be appreciated. Thanks

[DaKahuna]

Backup any data you have on the USB drive as that will be erased by the following steps:

1. format the USB drive for full size using a windows machine and format it to FAT 32
2. on you BackTrack system insert the USB drive and mount it. In BT3 Beta it should automount.
3. as root create the two partitions using fdisk.
fdisk /dev/sda
p (print to see what is on the drive)
if there are any exisitng partitions delete all of them using the "d" command
n (for new partition)
p (for primary)
1 (for first partition)
1 or enter (to start at the first partition)
+2048M (to create a 2GB partition)
t (to set the type)
b (to make the type FAT 32)

n (for new partition)
P (for a primary partition)
2 (for 2nd partition)
Enter (to accept the default start at next available partition number)
Enter (to accept the ending partition to use the rest of the disk)
t (to set type)
83 (to set type for Linux)

p (print to screen to make sure there are two partitions with the format you want)

w (write changes to the drive)

When write is finished you are returned to the command prompt.

run mount to see if the new drive is mounted or not. If not mount it using the mount command (note: you may need to create a directory in /mnt/ for the sda2 partition.

after the drive is mounted run mkfs.ext2 /dev/sda2 to set type for your linux partition to ext2

That should give you a general idea of what's involved.

[darth davidious]

Thanks Dakahuna, I managed to figure out using Jabra's pdf on installing backtrack to hard drive substituting my SDB1 instead. Your steps are identical. I love running BT3 off my USB with persistent changes!

On a similar note, has anyone been able to mount a Vista partition read/write within BT3?

[ragnaruk]

Great thread and thanks for the tips I finnaly got Bt3 booting from USB and saving changes in KDE mode, will try persistant change mode next to check it out, for anyone having trouble here ,,I could not get this to work at all using the code "83" for linux in fdisk, cfisk, or g parted I had to manuallly enter the command to format to EXT2 for partition 2, then it worked fine. it sometimes takes a painfully long time to shutdown, like 10-15 mins plus

addition,,, lol ok, now this is a cruel joke, after updating fast track when i reboot i now get , permission denied when i try to run fast track again, and yes i did logon as root, I dont get the logon screen while booting so i chose switch user and logged on as root, and still cant run fast track since updating it.

[Deathray]

On a similar note, has anyone been able to mount a Vista partition read/write within BT3?

http://www.linux-ntfs.org/doku.php

addition,,, lol ok, now this is a cruel joke, after updating fast track when i reboot i now get , permission denied when i try to run fast track again, and yes i did logon as root, I dont get the logon screen while booting so i chose switch user and logged on as root, and still cant run fast track since updating it.

I recall someone else having the same problem.
But nevermind, all you have to do is change the permissions for /pentest/misc/fast-track.py ;) . (chmod)
And by the way, BT boot's you as root by default.

[darth davidious]

EDIT...My Vista was hibernated...Once shutdown, BT3 can mount the volume. Thanks

[rdmbeaver]

I have my 4g transcend usb drive formatted with the 2 different partitions and save changes is working properly, however it is taking an ungodly length of time to unmount the file system on a restart/shutdown. I've watched for 10 minutes and it never finished. Last night i just left it and went to bed, and this morning it was restarted and all the changes were saved.

Any ideas on how to relieve this issue?

Thanks

[Munkey106]

Just a summary of what I did for other people looking for help.
This made my 2 gb USB Pen Drive boot BT3 beta and save every change I made on the same disk it was booted from.


In order to have backtrack save changes to the same drive it is booted from, it
should have at least 1.2 gb. If the usb pen drive has less than this, do not worry, you can make the changes get saved to your hard disk.
For that, please follow shamanvirtuel's tutorial farther up.

Step 1. Split the usb pen drive into 2 partitions*. First partition (A) should be precisely 1 gb and FAT32 filesystem. Second partition (B) should have the remaining diskspace and be in EXT2 filesystem.

Step 2. Copy bt3 and boot directory to partition A.

Step 3. Manually create folder "changes" at root directory of partition B.

Step 4. Execute /boot/bootinst.sh

Step 5. Open terminal and CD to /boot/syslinux on partition A. Type
chmod +Xx lilo
chmod +Xx syslinux

Step 6. Open /boot/syslinux/syslinux.cfg
At the end of the APPEND line, under the mod you are planning to use. (Example KDE or simply text mode), add:
changes=/dev/XXX
XXX Should be replaced with the name of partition B on the USB Pendrive.
In my case, /dev/sdb2.
SAVE SYSLINUX.CFG

Step 7. Reboot and select the mode where you added the changes mod from step 6.
Credit goes to SV + rest in this thread, who helped me get it to work ;)

*I used gparted from ubuntu to split the usb into 2 partitions(easy with user interface). You could also follow DaKahuna's guide further down.
backtrack 3 beta bt3 usb save changes usb drive persistent changes save configurations to usb pen drive


Thank you so much! I've been fighting with this for a few days and your post got it working!!!!

Thank you!!!!!!!!!!!

[Deathray]

Thank you so much! I've been fighting with this for a few days and your post got it working!!!!

Thank you!!!!!!!!!!!

Well your very welcome :p , just glad to be of help!

[eagle047]

Thanks to all who contributed to this thread. I followed DeathRay's post, then this post:
"How to "Restore All Of Your Sessions" on BT3 like it did in BT2!!"

(can't post urls yet :( )

My kde session is now restored on reboot, and I retain the fat32 file system for use as a regular pen drive on windows. :)

[JCasper]

I used purehate's video and got this pretty much working on my eee pc!! :) TY sir....

I have ran into a couple problems thus far though. First of all I get the "you passed an undefined mode number" error everytime I boot into backtrack, but this problem seems well documented and Im sure I can google it up.

Second, I got that fatal error as well. I just rebooted and it worked fine though, so idk. I really am loving this and appreciate you guys helping me get there. Also, it seems like you guys have a fix for that fatal error problem if I get it a time or two again.

For what it's worth, I'm using a WD passport 250 gig with an eee pc...Killer set up I must say.

**EDIT**Weird, I only get the fatal error you guys are speaking about when I choose the display number from the you passed an undefined mode number error. If I choose 1, it boots fine, if I choose any other mode number it doesnt.....Doesn't make sense to me, sorry if this is noobness not making sense.

[adi82]

Step 1. Split the usb pen drive into 2 partitions*. First partition (A) should be precisely 1 gb and FAT32 filesystem. Second partition (B) should have the remaining diskspace and be in EXT2 filesystem.
[/COLOR]

i am trying to boot "back track" from a partion of HDD and i had success but now i have to save changes ,but the partion of BT3 is FAT32.
i have an other partion , ubuntu, that is EXT3.do you recommend to save changes in Ubuntu partion or to do everything from the begging and to format the partion(where the BT3 is actually booting from) in ext2(this mean that can not be accessible from WinXP) and copy BT3 again.
any way ,what do you recommend to me?

I have an other question.why are you using ext2 instead of ext3?

p.s.: this is my first post!!!! Thank you:D

[smudgeface]

Ok, I feel pretty silly here...I typed sda not sdc and just deleted my laptops primary partition table (for my working installation of windows). Oops. This was a simple table (just had a single ntfs partition on it) but obviously it wont boot now. Can somebody guide me as to how to recreate the table that I just destroyed...
a link...a guide...really anything to get me back

Thanks in advance!!!

[JCasper]

.....What exactly were you attempting when you did this?

[smudgeface]

I was trying to repartition my USB stick and ended up wiping up my partition table for my main harddrive...

I fixed it though, and for anyone else who may end up doing this I will try to outline the solution briefly:
1) With a different computer, download gpart.linux (statically linked binary) onto a usb key
2) Boot the laptop (with the damaged HD partition table) off a BT3 CD/USB
3)chmod +x gpart.linux
4)execute ./gpart.linux /dev/etc and examine the results

sample:

Possible partition(Linux ext2), size(1200Mb), offset(0Mb)
Possible partition(Windows NTFS), size(1200Mb), offset(1200Mb)
...
Guessed primary partition table:

Primary partition(1)
type: 131(0x83)(Linux ext2 filesystem)
size: 1200mb #s(2457880) s(63-2457942)
chs: (0/1/1)-(152/254/61)d (0/1/1)-(152/254/61)r

Primary partition(2)
type: 007(0x07)(OS/2 HPFS, NTFS, QNX or Advanced UNIX)
size: 1200mb #s(2457880) s(2457944-4915823)
chs: (152/254/63)-(305/253/60)d (152/254/63)-(305/253/60)r

most of this is self explanatory (ie partition number, type, etc). The only part that I had to dig a bit for is
chs: (152/254/63)-(305/253/60)d (*num1*/254/63)-(*num2*/253/60)r
where *num1* is the start cylinder and *num2* is the end cylinder for that partition

5)using the cylinder/order/type information, rebuild the partition table with fdisk

by the way, I got my USB key working with persistent changes. Thanks Deathray!!!

[twocent$]

Hi All,

I know this post is somewhat dated but I just wanted to say thanks Munkey106. BT3 on the eeePC with Compiz running off a usb 4gb is now working great.

BTW. I found this site for some helpful tips and tweaks is anyone is interested....

ww.i-hacked.com/content/view/260/42/

[labiri]

Sorry guys, I can't get it to work...simply my changes are not saved, maybe I have too little experience on linux, so I wanted to ask some clarifications:


Step 5. Open terminal and CD to /boot/syslinux on partition A. Type
chmod +Xx lilo
chmod +Xx syslinux
What does it really do? I imagine it sets the permessions of those files, but I see them always with * at the end of filename (when listing the folder);

Step 6. Open /boot/syslinux/syslinux.cfg
At the end of the APPEND line, under the mod you are planning to use. (Example KDE or simply text mode), add:
changes=/dev/XXX
XXX Should be replaced with the name of partition B on the USB Pendrive.
In my case, /dev/sdb2.
SAVE SYSLINUX.CFG

I followed this guidelines strictly but I think I misanderstood something: here is my config lines, perphaps someone could point me out the error:

LABEL kde
MENU LABEL BT3 Graphics mode (KDE)
KERNEL /boot/vmlinuz
APPEND vga=0x317 initrd=/boot/initrd.gz ramdisk_size=6666 root=/dev/ram0 rw chexpand=256 autoexec=xconf changes=/dev/sda2;kdm

Ps: I'm working on the Asus EEEPC using an SDHC, don't know if it matters.
Any advice will be really appreciated :)

[haqthat]

Did you create a folder called 'changes' on your extra partition?

Is sda2 really the name of the partition you want to save changes to? Try typing 'mount' in the terminal, look for the partition that comes up as ext3. This is the one you should be using as your changes partition.

Also, when you are following this step "Open terminal and CD to /boot/syslinux on partition A. Can you show what you're entering into the terminal. I'd like to see how you get there.

[BTuser3]

Thanks for all those who posted replies to help.

I have a spare USB key which has already my stuff on it (music, programs, etc) and I decided to use that in order to boot BootTrack v3. OK, so I installed BTv3 on it, without recreating any partitions or all that, and it worked. No surprise, it just updated the MBR to reflect booting into BT3 on a reboot (thats as long as you leave the "boot" and "bt3" under the root directory of your USB key). Ok, now comes the part where am not sure about:

If I want to use that same configuration but let BT to write changes into /dev/sda1 (I dont want to have a second partition), will that work or I will need to create a folder called changes and point BT to /dev/sda1/changes? Basically, since I can write things to /dev/sda1, which is also the root directory of the USB key, why would should I not be able to write changes on that same partition? I think its possible. Any one have tried this? I will do some tests and report results, but if anyone already tried it, please let me know. Thanks.

[BTuser3]

I would also like to add: most of us know that Knoppix distros do work with persistent changes without creating any second partitions (pendrivelinux.com). Looking at the configuration of one of them, the following exists: an "mcnlive.loop" file (which acts as a loop device for saving changes), syslinux.cfg file (which has in the boot line, apend ... ... persist fromusb). Am not sure why it should not be possible to do the same with backtrack.

Am also working on booting Backtrack 3 from Windows without having to reboot it (just like many cases in perndrivelinux.com). So far, it actually works with me, its just that when KDE starts, the screen gets way too big and BT never actually succeeds to load it up. I dont think this is a majot issue, I will play around with the configs of Qemu and/or BT boot options. If anyone is interested on a mini tutorial on how to boot BT from Windows without a reboot, please let me know, I will come up with something nice and easy to follow (once I figure it out 100%.)

More testings under way.

[Munkey106]

If anyone is interested on a mini tutorial on how to boot BT from Windows without a reboot, please let me know, I will come up with something nice and easy to follow (once I figure it out 100%.)

More testings under way.

I'd absolutely love that, though I'm not sure if it's possible. It'd be great if it is though!

[BTuser3]

I'd absolutely love that, though I'm not sure if it's possible. It'd be great if it is though!

OK, most tests were done!

Actually its easier than I thought.

I booted BT3 today from within windows XP (without rebooting that is) and it works wonderfully, in both TEXT and GUI modes. I will post a mini-and-simple tutorial once I finalize a couple more things. ALSO, I got the persistent mode change to work within the same FAT32 partition (without the need of a second partition).

The concept is simple: instead of creating a second partition with ext2, just use an image file which is formatted with ext2 instead, and which resides in the root directory of the USB key. For BT3, that would be where the bt3b141207.iso file is, or in case where we are using the "reboot way", the boot and bt3 folders.

I tested the persistent change by changing the background and root password. Both were still there after a second "reboot-within-windows" attempt.

So up to this point, we have a working BT3 bootable from within Windows, under one FAT32 partition, and with persistent changes.

More tests under way to have the same concept work while actually rebooting from the USB stick and using that image file.

Here is a teaser picture:

hxxp://farm4.static.flickr.com/3026/2549101245_217ffb4e65.jpg?v=0

Dont forget to replace the xx...

[aidan_curtis]

me too would be interested in full explaination of both xp boot and save changes without ext2 partition

[aidan_curtis]

please could you us tell how to create the image file for the fat32 usb persistance
Thanks

[BTuser3]

I posted the tutorial under

http://forums.remote-exploit.org/showthread.php?p=88620#post88620

Enjoy :)