I want to rewrite the mkXML function and merge it withmuch of the code from fkBranch_AutoPB.sh. That way I can turn it into a flexible routine that will generate a PBC file accordingly iiregardless if it’s run from interactive or batch modes.
Terry Poulin
Mergemaster
Started merging files today, after a fit of the screamming heeby jeebies. Phone ringing off the hook, getting A.F.K.’d every 2 minutes and playing 20 Questions with ma. My brain could sync back to work…
mkProject has become a mondo sized function but is now fairly complete and handles the split between interactive and batch modes it self. The batchJob function will be most of fkBranch_AutoPB.sh.
Rather then line of execution being
Interactive or batch test
run mkHome, mkProject, mainLoop e.t.c.
or run batchJob
fkBuild
It is now more like this
mkhome
mkproject
Interactive or batch test
run batchJob if batch
run mainLoop if interactive
fkBuild
Where mainLoop is the interactive root function that all the interactive I/O and configuration methods lay. The batchJob call just starts processing the information from the data. I’m also adding a usage function.
scrap
Well, I’m a bit leery about it but I’ve done it. I’ve posted fkBranch_AutoPB.sh on PC-BSDs forums. I had hoped to have a proof-of-concept out of this scraptest file before I delete it but I doubt that will happen without help. I also wanted to merge it into pbshell.sh and complete the last stuff so I’d have both interactive and batch modes covered plus the planB method of PBI Creation.
The scripts not pretty but its just garbage for testing work, glad I don’t really write finished shell scripts like that..
Been busy attacking an old Java source book. it dates back to before JDK1.0 but its a fun read. Maybe I’ll take up Java I dunno. Recently I’ve been rather bored with most languages. Perl and Java study have kept me busy but the more I look into perl the more it looks like a great tool you don’t want to have to read what some one else wrote some day just to quickly fix a problem and never rewrote it. Java I’ve never cared for the extra OOTyping needed but its more C/C++ like then Ruby or Python and still a nice language. AWT looks like a simple to learn setup but I’ve yet to see many Java apps that look nice. I don’t know what is the most often used these days though, AWT, SWT, Swing, or other standard issue.
Being idle recently has been annoying, without any thing to work on what fun is there having some of the greatest tools ever made?
You know as long as no one changed the hier for home directories I could interate through each one setting up the icon files. If I could use PBC to just pack the project directory and do the rest with my script. It could work but that would mean for batch mode to work a special but very simple for joe blow to write project file would have to be created. HmmmmmM !!!!
bored
Without being able to make any progess with getting an automated PBI creAted. And about as much info about whats wrong with the PBC file I ran through PBC.
I basically have nothing better to do then toy with typing tests and ancient computer history. It would be so nice if some one could help figure out why PBC does not work with the PBC files.
sigh…
Trash, FUnk, and Crapola.
Some times I feel, as if I speak and no one cares. Maybe I should just learn to keep my mouth shut and my business to my self. I don’t know any more.
Perhapes I should halt my work, let it rot and be done with it. Just go home and head out to the CQC Range with team mates. Life can be a load of bollocks some times… So far I’ve been wanting very much to start re-learning emacs but I can’t stand the infernal editor ! I remember when I started I couldn’t handle Vim so I tried XEmacs and learned it all right. While I don’t remember the keybinds well I remember them enough, I’m just to “Vi minded” to use emacsen. Also my Vi User how to post is nearly finished, I’ve but a few more things to add to it.
Untill I can find out what is wrong with the PBC file created by my proof-of-concept scraptest or get necessary data on how to bypass PBC all together. Most of my work is for naught. Dang it, I remember I started the day before thanksgiving and practicly sat at my laptop for three days. I’m not really a shell scripter by nature, although I’ve vastly improved. I worked like a dog to get as much done while having to learn and prototype several things on the go +work ITRW. Took a few days off then hit at it again and again and again. As time would allow, now it’s in pretty good shape (near alpha imho) and with a proper rewrite my scraptest files could be fused into the main implementation.
Yet with out some fscking help to deal with PBI Creator or by pass it there is little more I can do, execpt maybe refine my icon configuration and finish the PBI.*.sh generator. My plans have been for it set up the PBI file to automatically do detection if the PBI is preinstalled or optionally a conficting/old version when ran. Maybe I should just change the files to bear the GPL (barf) and post them on the forums for some one else to deal with, I ‘m getting sick of this $]-[|+. I started work in November, it’s nearing January now and I can’t continue very much alone.
QEMU
How to install PC-BSD using the QEMU Emulator
What is QEMU?
QEMU is software that allows you to emulate another computer in order to
install and use an operating system on your physical machine without actually
installing it. Much like a Famcom emulator uses software to create the
impression to a game ROM that it’s really running on a Nintendo 8-Bit console.
It’s really running on your PC. It’s basically the same thing.
For Windows you can download QEMU as a ZIP archive and unpack it to any working
directory. If your using an older version of windows you may want to install a
program such as 7-Zip or WinZip (I reccomend the former). In order to use the
accelerator module you need to download it as well. You can find a link to it
on the main QEMU web site. Un pack the archive (it’s tared and bzipped, try
7Zip or WinRar). Copy the kqemu.inf and kqemnu.sys files to your QEMU
installation.
If you are using a Unix/Linux system it is best to use what ever package
management system you have to install it. One should be able to find an RPM or
Deb for there system. PC-BSD users can install QEMU and KQEMU via PBI which
includes a simple GUI for setting it up.
The KQEMU module will make the installed system faster but it is not open
source software. Qemu is Open Source and Free Software. Installing this will
likey vary from system to system.
Qemu Website
http://fabrice.bellard.free.fr/qemu/
Qemu for Windows
http://www.h7.dion.ne.jp/~qemu-win/
I will deal with using QEMU at the command line since it is the only portable
interface (Win, Lin, BSD, Mac). If your using a Unix/Linux system strip off the
“.exe” every where.
Find the location of QEMU on your system once it’s installed. Open a terminal
emulator (command prompt window) and change directory to it’s location like
this, cd “C:Program FilesQEMU” or if using a Uinx/Linux system you can check
it’s installed location with the command “which qemu” -> C Shell users may have
to “rehash” after installing qemu before they can run it.
Now since QEMU does not use your actual hard ware (it emulates it’s own) you
need to create a file that QEMU can use to store data (acts like a hard drive
or swap file). We can create a harddisk image file in several different
formats. “raw” which should be portable between emulation software. “qcow”
which is probably the best choice for Windows systems. “cow” for Linux systems,
“vmdk” which makes a VMWare image, and cloop which ya don’t want to toy with
right now !
Depending on the format used the size of the file should grow till it reaches
the limit we give it. Now PC-BSD should fit on a 6GB hard drive but to get any
real work done 15GB would be more realistic, assuming you like to store a lot
of photos, music, and video files. Then again for getting real work done you
should install an operating system not use an emulator (in my humble opinion).
It is good for testing things though but a few things to remember.
0.) Emulated hardware does not relate to YOUR hardware. So some things may work
or not work after really installing an operating system. Just the same some
things may not work in the Emulator but may work on the real system as the
emulator is simulating hardware.
1.) The system will run much slower then had you really installed it. Not only
is it going to use an alloted amount of memory (RAM) your computer will all
ready be running it’s current operating system and other softwares. This is not
suitable for the “faint hearted” machines. The test system I have runs a
Pentium D 930 (2 x 3.0Ghz) CPU and 2048MB (2GB) of fast DDR2 Memory.
3.) With virtual solutions some times odd things about software just “don’t”
work but are fixed when installed on the real system. Like wise it can be the
other way around.
4.) A lot of things won’t work under emulation or not well, i.e. 3D Games e.t.c.
Ok phase one we will create a disk image to install an operating system on. I
suggest 5GB minimal, for this I will use an 8GB image file. Thanks to having a
500GB hard drive xD
qemu -create -f qcow acd.img 8G
The syntax as you can see is `qemu-img -option -f format filename sizeG. Now we
have to basic options on how to install, we can boot the emulator off a CD/DVD
or an ISO image.It’s rather nice if you can use the ISO image and save your
self from burning a CD-R just for testing the system.
If using a Windows system
qemu -L . -cdrom “\.E:” -hda acd.img -m 512 -boot d
If using a FreeBSD system
qemu -cdrom /dev/acd0 -hda acd.img -m 512 -boot d
The device names vary from Unix to Unix some tiems even Linux Distro to Distro.
It will probably be some thing like /dev/scd0 on a Linux based system.
Now this is very important the number after the -m is how many megabytes of
memory to give the emulated “virtual” PC. In my case I chose to allow 512MB of
Memory to run PC-BSD under emulation.
Now if you want to use the ISO image file it’s slightly different.
Windows
qemu -L . -cdrom Imagefile.iso -hda acd0.img -m 512 -boot -d
Unix/Linux
qemu -cdrom Imagefile.iso -hda acd0.img -m 512 -boot -d
After the system is installed you can run it like so
Windows
qemu -L . -hda acd0.img -m 512
Unix/Linux
qemu -hda acd0.img -m 512
To try and enable KQEMU for more speed add a “-kernel-kqemu” option like so
qemu -hda acd0.img -m 512 -kernel-kqemu
The system should now boot and you can see how it works.
I’ve installed the system but it is very slow, taking about 2 times longer to install then normal and many minutes to boot + without sound or network. I don’t have KQEMU so it makes emulated hardware feel faster then our first Pentium PC (with 32MB of memory). If my laptop wasn’t so slow I might try it out that way. For running WinVista I’d say go with KQEMU on a system with 4GB of RAM and a lot 3.5 GB for it hehehehahhA !
Funky Monkey
OK – We have progess and we have bugs.
To night I have completed most of what I would like to call scraptest code or testscrap code. Basically it’s my feelings for the kinda stuff ya just write to test it as you work on it with out meddling up your main source file/routines e.t.c. You could say it’s about as close to spagetti as I’m willing to get. I know what it does because I just wrote it ! And have time to comment it before re-writting it.
So far we are able to generate a PBI file pretty easy, the only problem is dealing with the PBI Files creation. I think I need to supply more info to the program before I can get a PBI that ‘works’ out of it, although aside from not even being able to pass www.pbidir.com standards. It’s a functional process – well it is essentially a throw away implementation but if I can gear it up. I’ll merge it into the main script file(s). It’s only a days work but it’s pretty good for the amature (me) and my wanting a proof-of-concept ironed out.
I’m not there 100% yet but I know there is a way to auto-mate the creation of PBI’s and I’m going to find it, some how, some way, some day !
Since nvi (afaik) only uses tabs and I have vim set to use spaces I think I’m going to be switched to using tabs instead of spaces for indentation. It beats having to toggle expandtab based on what editor I wrote the file in. When vim.orgs vim scripts section is up I’ll look for a fixer upper hehe.
I wish my mom would understand, I have got to be able to work. I need my freedom to pour into a problem till I solve it, with breaks of course but still long, through concintration. I know I’m not the best about getting things done (nor quickly) but I know I can solve this, aside from one really funky win-like feeling things have gone well. Sigh, I wish I could do more, learn more, be more…
Bubble brain
Well I’ve been working on a forked/branched off type thing of the origenal script. Geared for the purpose of auto-generating a PBI both as a proof of concept and development field. After its finished I’ll try to merge it into the main file (now interactive-branch). The only problem I see atm is icons. I’m going to try and get this version done so I can use it to show proof of concept that a script can be used to create a PBI file, with some measure of success.
It’s been going pretty well, some stretch converting stuff so getLibs can handle being run on a list instead as a part of a loop but all is good. Been doing most of the work in a ssh session on Vectra. So I’ve basically been using nvi instead of vim, good editor really. Well alls been good un till 20 minutes ago. My head feels like it’s in a bubble – total computational thought crash.
This is what happens when I have to play “hopping monkey” after dinner, my brain crashes and it don’t leave no coredump file for me to pick over what the frig I was analizing.
Ugh
Late shift
I’ve tweaked a few things based on my templetfications of the PBI.*.sh scripts, I can’t finish the process totally right now because I’m not at my laptop. While I keep the working (i.e. working on) copy of the file on my Lexar the actual project files including the templets are on my laptops HDD.
To do
- Finish pbi installer scripts and option to allow user to hand edit them using kwrite or ee
- Allow user to input the license and save it to a file to make a K-Menu link
- Fool proof icon setup
- Implement GTK+ support to getLibs // Prolly not till later
- Add demaind + support for a readme file and weblink k-menu entry, add associated functions
- Sort out templets to check if pkg is all ready instaleld, if possible also check for PBI.
- Implement “planB” routine(s) to fork out of fkBuild and wrap around PBI Creator, creating a minimalistic PBC file just in case
I don’t want ot have to use PBI Creator for this but if I can get by with generating a PBC file and running PBI Creator from the program. Using the PBC file to provide only what my system can’t do it it’s self. It might make a stop-gap for releasing it early but if it turns out to be the only way. At least it will be ready, not a set back. Considering that PC-BSD is open source under a BSD style license. I could probably poke around and try to find out how to implement some thing my self given enough time but some how I feel that would be redefining the words. Having to “Reverse Engineer” a “Open Source” application which is really an Oxy Moron if I ever heard it. So if the developers can’t help me bypass PBI Creator…. I’ll have to live with it and scream bloody murder if changes to PBI Creator & the .pbc file format ever phL|{|<$ //3 over.
All or nothing
I’ve gone as far as I can go without being able to generate a PBI file. I’ve e-mailed Tim for help but I don’t know what the response will be at all. I do know I want to avoid using PBI Creator for any thing as much as possible. I’ve also begun setting the ground work for setting up the PBI.SetupScript.sh & PBI.RemoveScript.sh templets to encourage more advanced users to handle interaction with the user based on whether KDE is running or not. Sigh, oh most time to head back to work for a second supprise shift.