1st contact with V3 Razor
boot in text mode thru lilo
Code: Select all
Loading Razor . . . . .
Bios data ckeck successfull
Undefined video mode number : 303
vesa mode problem ?
Code: Select all
Loading Razor . . . . .
Bios data ckeck successfull
Undefined video mode number : 303
aufs whiteout files are not respected in upper branches (activated modules) so the only solution to this bug is to use 'changes=EXIT:' or 'changes-ro' cheatcodes.save session for deleted folders/files eg. 1. delete /home/guest/.mc 2. save session to module 3 reboot 4 .mc still exist
Code: Select all
ld: warning: cannot find entry symbol _start; not setting start address
/usr/lib64/libreadline.so: undefined reference to `tputs'
/usr/lib64/libreadline.so: undefined reference to `tgoto'
/usr/lib64/libreadline.so: undefined reference to `tgetflag'
/usr/lib64/libreadline.so: undefined reference to `UP'
/usr/lib64/libreadline.so: undefined reference to `tgetent'
/usr/lib64/libreadline.so: undefined reference to `tgetnum'
/usr/lib64/libreadline.so: undefined reference to `PC'
/usr/lib64/libreadline.so: undefined reference to `tgetstr'
/usr/lib64/libreadline.so: undefined reference to `BC'
Code: Select all
- linuxrc: check removable media in first place when searching for .sgn/extramod/rootcopy (more often porteus stuff is placed on removable media than on a hard drive)
- linuxrc: check booting media in first place when searching for changes
if there is sda2 instead of sdb2 changes wont be mixed up alsoporteus-2.1 on /dev/sda1 and porteus-3.0 on /dev/sdb2