21 replies
by dennyboy2013
Will try to figure out later how to import
all my blogs from Blogger. Meantime, it can be viewed at:
by dennyboy2013
Been fiddling around with torrent files the last
couple of nights. Ran into NAT problems and fixed
them finally tonight. Had to go into the router
config and forward port 6881 calls to the box I'm
using Azureus on, using both TCP and UDP. Enabled
UPnP in Azureus. Had to allow the program access
in the machines firewall config, and fiddle with
the max u/l number and kb's. It's working ok now.
Got interested in it, since a lot of distros out
there aren't in iso format. You can ftp the whole
directory of all the files and create your own iso,
but in some cases, you're not going to get all the
other cd's you might need, like with packages and
ports. Or, you can get the .torrent files and d/l
everything, no sweat, into iso's. Debian's a good
case in point, the one I'm getting right now.
by dennyboy2013
What a chore! Thought I had both cpu's working
properly on the HP Netserver, only to find out
tonight the 2nd one wasn't. Turned out to be a
controller seating problem on the mobo. Got
that ironed out now, I hope.
Installed FreeBSD 5.4 Release on it, installed
some ports I needed, rebuilt the kernel for
SMP support, and it's working okay so far. Now
I'm installing Xorg and later Fluxbox for the
desktop. I'm sure there are some things I left
out, like certain compile arguments, but it's
just for experimentation right now, anyway.
Also added an extra 9GB h/d for storage and
backup. Ran sysinstall and used fdisk and
disklabel. That went okay, too. Hope the xorg
and fluxbox install goes as well.
by dennyboy2013
Been playing with the system a lot today.
Installed portupgrade on it, read up on
ports at Oreillynet. Lots of good stuff
there, especially from Dru Lavigne. Only
problem in the last 24 hours was when I
ran a cvsup for the ports tree. Left it
running when I went to bed, since it's
a long process sometimes. When I got up,
system was froze up. Had to cold boot it,
and naturally it bitched when booting as
to the system not being unmounted properly.
Wasn't too damned much I could do about
that!
On a windows security note, finally found
a damned key logger on my winbox. Gone
now, but it's worrisome. Found a really
good security site with lots of free stuff
at http://www.sysinternals.com and d/l a
lot of freebies. The most interesting one
was rootkit revealer. Previously, rootkits
were mostly, from what I understand, found
on unix type systems. Now they're making
there way into the windows world. Oh joy!
As if there's not always enough security
stuff to worry about!
Addendum (following a.m.)
Whew! I remember reading how long it can
take to install Gentoo, especially if you
are really a geek and build it from one of
the first stages. :-) I started installing
windowmaker and then firefox last night.
Got up this a.m. and it's still going hot
and heavy. Ran df on /usr last night and
got 15% used. Ran it just now and it's at
28%. I think that particular partition is
about 8 or 9GB. This is kind of like when
you install MS stuff. Eeooouuuhhhh!!!
by dennyboy2013
Had a terrible time getting Pine and GPG
to work together on the HP Netserver with
freebsd. Here are the program versions:
FreeBSD - 5.4 Release
Gnupg - 1.4.1
Pine - 4.62
Probably mentionedd it before. I'm still
running an old version of OpenBSD (3.3)
on my old laptop. GPG is on there with
Pine and works great and was easy to set
up. This new version was easy, once I'd
messed with it most of all day Sunday. :-)
Okay, here's the setup in Pine:
display-filters
(1st filter, all on one line)
"_LEADING(-----BEGIN PGP SIGNED MESSAGE)_" /usr/local/bin/gpg -decrypt
(2nd filter, all on one line)
"_LEADING(-----BEGIN PGP MESSAGE)_" /usr/local/bin/gpg -decrypt
sending-filters
(1st filter, all on one line)
/usr/local/bin/gpg -eas -r youremail@youremailprovider
(2nd filter, all on one line)
/usr/local/bin/gpg --clearsign
On the 1st sending filter, be sure to put
your email address. That's where I had so
much trouble, trying to figure out why I
could send an encrypted message to someone
on my keyring and they could read it, but
I couldn't read the same sent message in
my box.
by dennyboy2013
Okay, found out my last post on using Gpg
and Pine leaves out some things that I've
since had to work out. Here's what I did.
In Pine, go to Setup, then Config. Go down
until you see default-composer-hdrs. Enter
X-GPG-PUBLIC_KEY: http://wwwkeys.nl.pgp.net
X-GPG-FINGERPRINT: your id fingerprint here
Go further down to display filters. Enter
_LEADING("-----BEGIN PGP SIGNED MESSAGE")_ /usr/local/bin/gpg --decrypt
_LEADING("-----BEGIN PGP MESSAGE")_ /usr/local/bin/gpg --decrypt
Go on down to sending filters. Enter
/usr/local/bin/gpg -sae (this 1st one for encryption)
/usr/local/bin/gpg --clearsign (this one for signing)
There's only one person I send anything encrypted
to, so the following work around isn't too much of
a bother. Guess it could get worse if I had to start
encrypting a message to a whole bunch of recipients.
Anyway, when I address the message, I first put in
the intended recipient, then myself to be carbon
copied. When I send the message, I choose the first
gpg filter which encrypts and signs, type in my
password when it asks, and then gpg asks me for
recipient(s). First I type in the intended one and
hit enter. Then I type in myself and hit enter.
Then enter one more time on a blank line. Message
is sent to us both, he can read it, I can read the
copy in my sent messaages folder, and all's well.
I'm using FreeBSD 3.7 Release, GPG 1.4.1 and
Pine 4.62, so if anyone else knows of a better
way to do the above with installing a bunch of
God awful scripts and so forth, in other words,
just some settings I can change, & you read this,
please let me know!
by dennyboy2013
Hallelujah! That about sums up the way I feel.
I've never gotten X to look so good before. I
thought the install had been broken last night
when it stopped towards the end. Did a massive
clean up after all the installing. Tried Window
Maker today after running the X configuration
utility. Took several tries and doing some guess
work as to the video, but it's running now and
looks great. Hope the Thunderbird email program
and Enigmail for encryption go as well tonight.
by dennyboy2013
Talk about! I keep getting this when I boot:
unknown: PNP0303 can't assign resources (port)
unknown: PNP0f13 can't assign resources (irq)
unknown: PNP0501 can't assign resources (port)
unknown: PNP0700 can't assign resources (port)
unknown: PNP0401 can't assign resources (port)
(There a left and right brackets around the
PNP errors, but I can't put it in here, since
it gets interpreted as html tags when the page
is parsed).
Did a lot of Googling, and read where you no
longer can compile in support for the problem.
So, I kept fooling around with pci, irq, and
port settings in the bios. Eventually, I went
to far, to say the least. Machine flat would
not boot. Had to shut down, disconnect power,
remove and reseat the cmos battery, reset all
my bios settings, save and reboot. Still have
the error messages in dmesg, but at least I'm
back up and running.
by dennyboy2013
Tried several 3rd party NFS clients to be able to
access my home folders on the FreeBSD Netserver,
without much luck. Downloaded MS Windows Services
for Unix, set it up, had a hell of time with the
the settings, but it's up and running finally.
Kind of flaky on copying some files back and forth,
but maybe with some tweaking, it'll all iron out ok.
NFS was tricky to set up on the FreeBSD box, but I
got a lot of help off the internet, especially at
Oreilly's web site. As always, Dru Lavigne's site
was helpful, too. Next project will be getting my
old laptop still running OpenBSD 3.3 to mount the
exported folders from the FreeBSD box.
by dennyboy2013
Wow, it's been over a month since I posted on
here! Been really busy, day and night, working
on the old Netserver, adding ports, learning
port maintenance, picking up all kinds of tips
on Dru Lavigne's blog at Oreilly, recompiling
kernels, doing complete src upgrade rebuilds,
even tried creating a src repository, but ran
into some problems. I also tried using cvsup
on my xp box, but it was a lot of work for
nothing. Always had problems with corrupted
mac messages when running cvsup. Read a lot
on it and the main problem is, ssh having to
be patched to run on anything but OpenBSD.
At least that's what I gleaned from it. It
even has problems sometimes on FreeBSD, but
it always links back up and starts d/l again
after a time-out. Windows wouldn't do that.
I've even got some "invisible" files left
behind in my home dir in cygwin on the xp
box from cvsup. Can't delete them, either.
What a trip! Took my son's old PIII 800 box
and setup PC-BSD on it. Tried Ubuntu first,
but ran into big time problems with setting
up Xwindows, so I just blew that one off.
Had a really nice desktop, but I never could
get it out of 480x640 mode. When I did, it
all went to hell. Only problems I ran into
with PC-BSD was with the menu editor. I got
my one account so screwed up, I just wiped
it out and recreated it. Too used to working
at the terminal, typing everything in. Never
have had great luck with X in nix or bsd's.
by dennyboy2013
Yep, it pays to do that even when you're not buying something,
like when you're supposed to be reading the docs, but you're
just casually scanning through, hitting the high spots, and
then doing something like "make build". You know, something
small and inconsequential. :-) Been working with OpenBSD on
an extra computer I got back from my son, since coming back
from the hurricane Katrina evacuation. Didn't realize how
much I'd forgotten. As for the allusion to fine print, it had
to do with XF4, building the xwindows stuff, after I had done
a cvsup to get all new source, ports, docs & so forth. Built
the new kernel. No problem. Did all the necessary prework and
then built all the userland stuff. No problem. Did the after
work stuff like httpd docs, mergemaster, & so on. No problem.
Then I did the prework stuff you're supposed to do before you
mess with XF4, but I failed to read the part about tk-8.4.7
and tcl-8.4.7p1 needing to be installed, or the XF4 build would
fail, which it did. So, remember kiddies, READ THE FINE PRINT!
by dennyboy2013
Here's an excerpt from the OpenBSD docs, pertaining to my earlier post:
X uses a different build process than the rest of the OpenBSD tree, as it is based on imake, rather than the standard make(1) process. One consequence of this is there is no "obj" directory, generated binaries end up being intermixed with the source code, which can cause problems (or at least, excessive output) with cvs(1). A solution to this problem is to use lndir(1) to make a "shadow directory" consisting of symbolic links to the actual source directory for the XF4 tree.
i386 only: XF86Setup, used to configure XF3 servers on the i386 platform (and ONLY the i386 platform) requires the "tcl" and "tk" packages be installed before building X (found in the ports tree at /usr/ports/lang/tcl/8.4/ and /usr/ports/x11/tk/8.4/. Installing the "tk" package will install "tcl" as a dependency). As usual, installing a package is much faster than installing these applications from source. Failing to install these packages before building X is somewhat frustrating, as the system will work for some time before erroring out.
To compile X using the "shadow directory" of /usr/Xbld, use the following steps, compiling and installing new binaries into the proper directories, follow these steps:
# rm -rf /usr/Xbld
# mkdir -p /usr/Xbld
# cd /usr/Xbld
# lndir ../XF4
[...lots of output...]
# make build
[...lots of output...]"
by dennyboy2013
Here's an excerpt from the OpenBSD docs, pertaining to my earlier post:
X uses a different build process than the rest of the OpenBSD tree, as it is based on imake, rather than the standard make(1) process. One consequence of this is there is no "obj" directory, generated binaries end up being intermixed with the source code, which can cause problems (or at least, excessive output) with cvs(1). A solution to this problem is to use lndir(1) to make a "shadow directory" consisting of symbolic links to the actual source directory for the XF4 tree.
i386 only: XF86Setup, used to configure XF3 servers on the i386 platform (and ONLY the i386 platform) requires the "tcl" and "tk" packages be installed before building X (found in the ports tree at /usr/ports/lang/tcl/8.4/ and /usr/ports/x11/tk/8.4/. Installing the "tk" package will install "tcl" as a dependency). As usual, installing a package is much faster than installing these applications from source. Failing to install these packages before building X is somewhat frustrating, as the system will work for some time before erroring out.
To compile X using the "shadow directory" of /usr/Xbld, use the following steps, compiling and installing new binaries into the proper directories, follow these steps:
# rm -rf /usr/Xbld
# mkdir -p /usr/Xbld
# cd /usr/Xbld
# lndir ../XF4
[...lots of output...]
# make build
[...lots of output...]"
by dennyboy2013
Really weird! Started rebuilding everything last night on
the OpenBSD box and on the old Netserver with FreeBSD on
it. Finished up today when I got up. Had to get some sleep
after starting the new job last night. Everything went okay
on the OpenBSD box, but I had to reboot the old Netserver to
be able to do make kernel install on it. Kept hanging up. I
had to temporarily comment out the NFS imports off the Obsd
box before I rebooted. I could've umounted them, but wanted
to do a clean boot and see what happened. After that, okay.
Did the usual mergemaster song and dance on both okay, too.
Was a little scared on the Obsd box. It's not as simple and
you have to let it do a makedev, too. Anyways, both are back
up and running fine.
Installed portsnap on the Fbsd box the other night and really
like it, so far. No problems yet with it.
portsnap fetch
portsnap update
cd /usr/ports && make fetchindex
portsdb -u
portaudit -Fda
portversion -l "<"
portupgrade -arR
Last one only needed if portversion comes up with something
that's outdated. Saw today that one of the new fortune ports
shows broken. No big deal.
by dennyboy2013
What an exciting time! :-) Not really. Started new job.
Not usually fun, especially around the holidays. As usual,
I've run into conflicts on one of my BSD boxes between
perl modules and ports. I tried deleting some modules,
went too far, and couldn't get back into the CPAN shell.
Really buggered it up. I had done a full dump of /usr
several days before, but had never done a restore before.
After some experimenting, did the following:
1) Rebooted into single-user mode
2) Remounted / in rw mode, since it said it had to write
some stuff there. Now I don't think so, but it's not
important. It may have been referring to restoresymtable
which gets written to the root of the directory you're
doing a restore in, which, in this case, was /usr.
This morning, after rebuilding the kernel and while
rebuilding userland, I remembered to delete the file,
which the man page says you should do.
3) Mounted the /usr slice rw in /mnt and ran newfs on it.
4) Mounted /data2 slice which held the dump backup.
5) Cd into /usr and ran restore rf /data2/backups/usr.
Miracuously, everything worked out fine! Later, I ran a
perl script that lists all installed modules and removed
several, and then reinstalled them from /usr/ports.
Still having some problems, though. Couldn't do a make
install on SpamAssassin. It looked on a bunch of servers
before finally finding the source code, but then it said
the checksum was bad. I'll have to experiment with it
some more later. Below is some of the perl stuff I found
to help me out:
http://www.cpan.org/misc/cpan-faq.html#How_delete_Perl_modules
How do I remove installed Perl modules?
By using the ExtUtils::Installed and ExtUtils::Packlist
modules that come with Perl as in the example below. There
is also a more elaborate example in the ExtUtils::Packlist
man page.
#!/usr/local/bin/perl -w
use ExtUtils::Packlist;
use ExtUtils::Installed;
$ARGV[0] or die "Usage: $0 Module::Name\n";
my $mod = $ARGV[0];
my $inst = ExtUtils::Installed->new();
foreach my $item (sort($inst->files($mod))) {
print "removing $item\n";
unlink $item;
}
my $packfile = $inst->packlist($mod)->packlist_file();
print "removing $packfile\n";
unlink $packfile;
How do I find out what modules are already installed on my system?
* perldoc perllocal
Each time a module is installed on your system, it appends
information like the following to a file called perllocal.pod which
can be found in /usr/local/lib/perl5/version number/architecture/ or
something akin to that. The path for your specific installation is
in your @INC which you can divine with perl -V.
=head2 Wed May 12 13:42:53 1999: C L
=over 4
=item *
C
=item *
C
=item *
C
=item *
C
=back
Each entry includes the Module name, date and time it was
installed, where it was installed, linktype [ static or dynamic ],
version and executables, if any, included with the module.
* Use the ExtUtils::Installed module
ExtUtils::Installed provides a standard way to find out what
core and module files have been installed. It uses the information
stored in .packlist files created during installation to provide
this information. In addition it provides facilities to classify
the installed files and to extract directory information from the
.packlist files.
#!/usr/local/bin/perl
use ExtUtils::Installed;
my $instmod = ExtUtils::Installed->new();
foreach my $module ($instmod->modules()) {
my $version = $instmod->version($module) || "???";
print "$module -- $version\n";
}
produces the following list of modules and their version
Apache::DBI -- 0.87
Apache::DBILogConfig -- 0.01
Apache::DBILogger -- 0.93
AppConfig -- 1.52
Archive::Tar -- 0.22
BerkeleyDB -- 0.06
CGI -- 2.74
CPAN -- 1.59
CPAN::WAIT -- 0.27
Catalog -- 1.00
Compress::Zlib -- 1.11
Config::IniFiles -- 2.14
Convert::BER -- 1.26
Coy -- ???
Crypt::Rot13 -- 0.04
Crypt::SSLeay -- 0.16
DBI -- 1.14
[.....]
by dennyboy2013
Been too busy working my job, contending with family matters,
and trying to hack my way through FreeBSD and OpenBSD, all the
while making them work together harmoniously with my XP box.
My biggest headache lately has been trying to print to my
HP DeskJet 722C on my XP box from the two BSD boxes. Tried
all kinds of stuff like apsfilter, cups, and so forth. Now
I've got a rather simple setup on both BSD boxes for printcap.
I'm using foomatic-rip and ghostscript, along with pnm2ppa.ppd,
the printer file from linuxprinting.org for my DeskJet printer.
It was pretty open and above board on the FreeBSD box, since
foomatic-rip is by itself in the ports tree. But, in OpenBSD,
it's underneath /print/cups/files, and it took me a while to
snap to all I needed to do was copy it to /usr/local/bin along
with pnm2ppa.ppd, and then setup /etc/printcap. Ghostscript
was already in place due to another ports needed dependencies.
Been applying security patches lately, too, on both BSD boxes,
rather than going through all the rebuilding song and dance.
That's due to the fact that both OS's are coming out with a
new release shortly. I've already preordered my OpenBSD cd's,
and need to get off my duff (and wallet) and due the same for
FreeBSD. I highly encourage anyone who reads this blog and is
interested in running either operating system to order cd's.
You can ftp the FreeBSD iso's, and with OpenBSD, you can d/l
all the files and create your own iso's and burn them, but it
doesn't help the ongoing expenses for the developers. Most of
them work regular jobs and do their coding voluntarily, using
their own personal time. That's pretty strong commitment, and
I think it deserves some real support. Here's a good example
of how you can learn either system, along with NetBSD too,
even if you've always been a windoze addict like myself, just
by reading the man pages and accompanying docs, and not being
afraid of sweating over the keyboard a little and experimenting.
Right now, on my OpenBSD system, which is running on a PIII
box with 256MB of ram and two IDE h/d's, I can surf the net
in Xwindows using either Firefox or Opera or, in text mode,
Lynx. I do email, I'm learning how to setup spam control and
firewall security. I can create my own iso images from source
and burn them to cd's. I can print to my old Star 2410NX dot-
matrix printer on my FreeBSD HP Netserver or to my HP DeskJet
722C on my XP box. The only hurdle I still have to get over
is getting a scanner to work on the OpenBSD box. It's a PIII
and has USB ports, which the old Netserver doesn't, so it's
the natural choice. I've got an old HP ScanJet 3400C, but it
seems to have crapped out during Hurricane Katrina, probably
due to all the moisture in the house while we were gone for
the evacuation. So, I've been nosing around the Sane Project
site and eBay, trying to make a choice. The whole point of
this ongoing exercise in opensource is to finally, once and
for all, drop out of the Bill Gates financial support team.
I have nothing against him or Microsoft. But, I'd rather
run a system that's pretty damned secure from jump and is
opensource, than pay an arm and a leg for a system that's
constantly riddled with vulnerabilities. And, find myself
waitiing for weeks and sometimes, even months, for a patch,
when both OpenBSD and FreeBSD developers are constantly
monitoring and testing their code for insecurities, and
are always up front and honest when they find them, and
are quick to fix them and get them up on the net for users.
Okay, I am now climbing down from my soapbox. 'Nuff said
on that issue. Until next time, happy hacking!
by dennyboy2013
Yep, busy as heck. Lots of personal issues as usual.
Finally got my OpenBSD 3.9 cds and my new wireframe
daemon t-shirt. So busy, haven't had time to update
my system. And now, FreeBSD is out with version 5.5
which, as I understand it, will be the last in the
5-STABLE branch. I'd like to try 6.1 but I'm not too
sure how well it'd run on my old HP Netserver. 5.4
cadillacs on it, considering how old the hardware is.
As I'm writing this, I've got my latest backups on
the OpenBSD box tarred/gzipped and I'm running rsync
to update the mirrored backups here on the windoze
box. Working great. Had a hell of a time teaching
myself the ins and outs of rsync, but I've got it
doing everything I need it to do, now. It probably
is childs play for old nix hands, but I have trouble
finding time around here to keep on learning all I
need to know to run these systems proficiently. I
added another account from the FreeBSD box here on
the windoze box and ran into some issues with my
cygwin stuff, but it's ironed out now, too. I've
got cronjobs setup on both BSD boxes for the users
to be able to do backups across the LAN with rysnc
for their home directories, mail, and so forth.
I've got a new Seagate USB 2.0 160G external hard-
drive on this windoze box now, and it's sure nice
to have room for a change to do the backups that
have to be done. Found out one day, after hosing my
usr partition on my OpenBSD box just how nice backups
are. I had never done a restore before and wasn't too
sure I could pull it off, but it worked like a champ.
I had just done a full dump a few hours before, lucky
for me.
Got my hands on an old DEC Prioris dual-processor box
that got abandoned by the yacht club in Gulfport, and
picked up a serial cable to be able to run it without
a keyboard or monitor, but haven't gotten around to
doing all the setup yet. I've got OpenBSD 3.8 on it,
and it ran okay, but I had a kernel panic on it when
I tried booting it with the mp kernel. Haven't had a
chance to go back and reproduce it yet so I can run
a trace on it and try to see if it can be debugged.
Not really sure if the cpus are supported for smp in
OpenBSD. I'll have to investigate that before I fool
around with the mp stuff again. Might have to do some
hard wiring, bios work, and kernel tweaking if it is
supported. Time will tell.
I got an old Epson scanner off of eBay and it works
great on the windoze box, and I got the sane backends
to build on the OpenBSD box, but not the frontends.
I tried hacking some stuff, but to no avail. Got a
lot of help from the port maintainer, but he finally
got too busy to help any further. It's supposed to
be fully supported now, in the new 3.9 release, so
I'll need to get off my duff and get it installed
so I can try it again. X is working great on it with
the old voodoo card. I need to get some speakers on
it so I can fool around with the sound and some music.
Creating iso images, writing cds, erasing rewritables,
and so forth is a snap on it. Got foomatic stuff on
both BSD boxes and am able to print everything I need
to over here on the windoze box on the old HP Deskjet.
Also can print from here to the old Star dot-matrix
printer on the FreeBSD box, and also to it from the
OpenBSD box. I want to get to the point where, if this
windoze box craps out, I won't be pressured to hurry up
and fix it or replace it. Trying to get weaned as soon
as possible. I know, almost for sure, that I'm not going
to be able to afford the hardware I'll need to run Vista
when the final version is released. Not that I'd want to
spend that kind of money anyway, on a MS product, though,
in retrospect, I can say that XP has been pretty darned
reliable. I probably would've never gotten involved in
computers, as much as I have, it weren't for Microsoft.
It's just all the damned security issues that worry me.
Which brings to mind another project I want to get
started, getting pf setup on the OpenBSD box, along
with spamassassin and maybe clamd to protect the box
as much as possible. I've already got some basic pf
stuff down, but now nearly as much as I need do have.
Well, as can probably be seen from the timestamp on
this post, this is about the only time I really get
anymore to do much on my blog. And with that in mind,
my old butt needs to hit the rack for a while. Hope
it's not so long until I can get on here again.
by dennyboy2013
3.9 upgrade went pretty good, considering after I'd used
pkg_delete to get rid of all installed ports and packages,
I forgot to get rid of all the installed directories where all
were installed at, /usr/local/. Didn't realize it until I after
the upgrade was done and I was installing the newer
versions of everything I needed. SpamAssassin is where
the 'file collisions' started. It was a mess. Looking back,
and considering how quickly OpenBSD packages install,
I probably should've redone the pkg_delete thing, but I'm
hard-headed. Anyway, got it all done and tonight I did a
few image scans. Had to use xscanimage. Couldn't get
Gimp to acquire the image. Have to figure it out as I go
along, I suppose.
by dennyboy2013
This is my baby. :-) Saved this for myself and
whomever else is interested. Emacs is great,
but Vi is what I first learned on.
by dennyboy2013
Linux.com | Emacs tips: Windows and buffers
I mostly use Vi, but I'm eventually going to try get more
proficient with Emacs, too. So, saved this for myself and
whomever else is interested.
by dennyboy2013
Probably one of the most productive periods I've spent in the last few years,
the last few weeks since I upgraded OpenBSD to 3.9 on my number one
work box, and also on my old HP Netserver. I had run FreeBSD on it for a
long time, and then when I went to upgrade from 5.4 to 5.5 I ran into all
sorts of problems. OpenBSD, on the other hand, went in flawlessly. And,
as a plus, I didn't have to rebuild the kernel like I would've had to if I had
succeeded in installing FreeBSD. I loaded the bsd.mp kernel and it took
off fine and has ran fine since. All I had to do was do a config on it to make
up for CDT and keep the operating system and the hardware clock in sync.
With 3.9 I was able to finally get the sane-frontends installed and can scan
fine now with my old Epson using The Gimp. Only thing I haven't been able
to do is scan from another box on the local area network. I've tried over
and over with every kind of switch and configuration I can think of, to get
the xsane program to do it from the Cygwin bash shell on the windows box,
but I guess that dog just ain't gonna hunt. I also tried from the othe obsd
box to do it, but no luck there either. On the plus side, I can do everything
from my OpenBSD box now, that I can do from my windows box. That has
been a goal for a very long time. It just took some free time to devote to
learning enough to be able to accomplish it. I'm able to burn cd's, create
iso images, have users do automated nightly backups over the local area
network using ssh, rsync and cron, scp files back and forth easily taking
advantage of rsa keys with ssh and authorized_keys files, use ICQ through
an ncurses program MICQ. I've done dumps and, more importantly, restores
successfully. Learned that when I did a typo one day, deleting something
from /usr. That was before the upgrade, but it's stuck with me, especially
the need to backup regularly. Been listening to BSD podcasts from a really
cool site, bsdtalk.blogspot.com and have learned quite a bit from them.
Listened to Dru Lavigne the other night and started salivating, thinking of
how cool it'd be to get to go to FreeBSD bootcamp in Ottawa. Better get
back to work first and get some money coming in for that. :-)
Now I'm also trying to learn more about blogging. I feel like I'm back in
school, carrying one heck of a course load. :-) I'm able to pick up my blog
in my Wizz RSS reader in Firefox, and have registered with Performancing
too. Got that extension installed in Firefox, too. That's where I'm creating
this latest entry right now. So, if it comes out screwed up, don't blame it
on Performancing, Blogger, or Firefox. I'm sure it's my own ignorance of
how to do things the right way.
powered by performancing firefox
This discussion is closed to new replies.
Trending After Hours posts
Sort by Trending