600mhz Alpha with 384megs of ram. On board sound and LAN.
This is a REAL AU model, with the qlogic SCSI card and the powerstorm
video card(in case you wanted to run OpenVMS). I would recommend using
a different video card or using the serial console for anything BSD or
I believe it has a 9 gig SCSI disk in it, but I've suplemented it with a
50gig IDE drive on the IDE chain. I've also replaced the IDE CD-ROM
with an 68-pin SCSI CD-ROM(yes, thats right, 68-pin).
I also have all the original docs with it.
I was running FreeBSD 5.3 on it until a week ago when I upgraded the
machine. Nice little hobby system.
$200 bucks or best offer. If anyone has any questions, or wishes to
haggle, please reply to me(and not the list, they hate that).
I just put together a new machine for a friend. Sempron 3100 on ASUS
K8V-MX. It was a rush job, because the computer she was using died. (Same
one I wrote about recently that was having lockup problems - pretty sure
now that it was the power supply. The last time she tried to turn it on, a
big spark came out the back, and that was the end of it. Memory and vid
card still test good.)
So now that she has a shiny new 64-bit system, I'm wondering whether to go
with 64-bit OS or stick to 32. I haven't had much time to research it, but
I understand that there are some problems with Macromedia Flash and Java,
which she needs.
Some of the reading I've done suggests that you can install the 32-bit
version of Firefox with the plugins to get around this. Anyone know if
it's really as easy as that? Are there any problems with running 32-bit
software on a 64-bit OS? Any particular bugginess with 64 that I should
know about in advance? She runs KDE desktop and uses Gimp a lot.
Oh, one other glitch I ran into - I tried to do the network install, but
the boot cd doesn't have the kernel modules for the LAN chip. I was
instructed to go to the install cd and make a "modules 3" floppy. There is
no modules 3 image on the cd or on the ftp site, but there are images for
"bootdisk1, bootdisk2, etc." Do I have to make the whole set and install
from floppy, or is there a way to find out which disk has the right module
and just use that with the cd? Or could I just put an older card in it for
the install and then change the network card setup afterward? I'm thinking
the latter would be easier than finding five or six blank floppy disks to use.
With specific respect to compiling, some apps I regularly compile -- especially Scribus -- require that in the ./configure stage you include --enable-libsuffix=64. In this particular case, it's because the Qt libraries are sensitive to the bit-ness. The BUILDING file should indicate such requirements.
I have an FC2 and FC3 machine which I want to get upgraded to FC4.
In the past, I used to spend an hour or two doing this type of thing
manually which was a pain but generally got the job done ... This time
around I was thinking of either using yum or burning some CDs and doing
the upgrade method (which the Fedora guys recommended to me).
Anyone have suggestions about what method works best? Any gotchas I should
worry about, etc?
Thanks in advance! :)
Randomly Generated Tagline:
"If you lend someone $20, and never see that person again, it was probably
worth it." - Zen Musings
-----BEGIN PGP SIGNED MESSAGE-----
I am playing with a single board computer (SBC) in an attempt to make a
diskless, fanless, silent firewall. Specifically, its the RouterBoard
532 (http://www.routerboard.com). The processor is MIPS based (4Kc).
I've been using the buildroot software (nice!) which made creating the
cross compiler enviroment considerably easier than my previous (failed)
attempts at doing this by hand. My cross compiler environment is now
working quite nicely.
I have created an environment where I have loaded software onto a
compact flash card and booted Linux 2.4.30 on this box. I have logged
in and gotten the box talking on the net. All 3 ethernet ports
function, as well as ssh and dhcp. Sweet!
My next step is to take the SuSE firewall scripts (they are GPL) and run
them on this box. However, I'm hitting a wall that I don't think I
should be hitting.
Within busybox, command substitution and pipes don't work on this MIPS
box (but they do work on my x86_64).
command substitution example: echo `cat /etc/hostname`
pipes: ls -l | grep foo
With neither of these working, real scripts don't work too well. :-(
I've traced the source code (gotta love free software!) and the code
fails whenever it calls the function dup2(). I'm not sure why dup2()
fails, but it does, returning EBADF (bad file descriptor). I tried
installing bash and noticed exactly the same thing.
dup2() seems to be implemented as a system call into the kernel, but
that's where I get lost.
I've been scouring the net and cannot find an answer. I must be doing
something wrong, but I know not what. Does anybody have any helpful hints?
Andy Stewart, Founder
Worcester Linux Users' Group
Worcester, MA, USA
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
-----END PGP SIGNATURE-----
The situation you describe about the removable drives mounting in /media
suggests it is using udev, hal, d-bus and ivman. Your home system should
be using udev, but not sure if it has hal or d-bus; even if, doesn't sound
like it has ivman. I'm not so sure about how to do this in FC, I'm a
gentoo guy, but you'd need to have all of those installed and set up. This
might be of some help: http://gentoo-wiki.com/HOWTO_ivman.
You need udev and d-bus for hal, and then just need to start the hal
daemon (hald). Then start ivman, and it should autodetect devices plugged
in and put them into /media. For example, /media/usbdisk0 would be the
first partion of the first usb disk plugged in (I do believe). It'll add
new devices to your /etc/fstab. You can, however, have a bit more control
over this, setting up a udev rule to make your disk use a specific device
file, for example /dev/mydrive and then put a listing in /etc/fstab to
mount /dev/mydrive at /media/mydrive. Then, when plugged in, udev will
create the /dev/mydrive device file and ivman will detect it's creation
and readiness and mount it at /media/mydrive. Spiffy stuff.
For more information on writing udev rules:
Bill Mills-Curran <bill(a)mills-curran.net> wrote...
> Subject: [Wlug] usb drive -- hotplug/automount
> To: Worcester Linux Users Group <wlug(a)wlug.org>
> Message-ID: <20051227205055.GA6082(a)bday.mills.curran>
> Content-Type: text/plain; charset=us-ascii
> I have a question about hotplugging & USB and some differences I see
> between 2 different FC3 systems (home & work).
> **** Home
> Initially, I configured my drive at home. I did NOT have the menu
> Preferences -> Removable Storage
> set to "Mount removable drives when hot-plugged". Without realizing
> that this was an option, I used manual entries in fstab:
> # usb drive
> LABEL=usblinux /mnt/usb/linux auto defaults,user 0 0
> /dev/sde2 /mnt/usb/windows auto defaults,user 0 0
> /dev/sde1 /mnt/usb/camera auto defaults,user 0 0
> This worked well & good. I was happy to be able to mount the
> partitions as a user. Note that the linux partition has a label
> Then, I moved the drive to my work machine.
> **** Work
> I plugged the drive in and was surprised to find that both partitions
> automatically mounted in /media:
> I also saw that entries were added to /etc/fstab, reflecting the mount
> points and device names.
> I recognized this as better action.
> Returning home...
> **** Home
> Plugging the drive in, I confirmed that nothing was happening in
> /media. I found the entry to automount the drive in:
> Preferences -> Removable Storage
> and enabled it. I unplugged and plugged the drive, and it mounted
> with this from df:
> Filesystem 1K-blocks Used Available Use% Mounted on
> /dev/sde1 72801276 1704196 67398920 3% /mnt/usb/camera
> /dev/sde2 4176756 96 4176660 1% /mnt/usb/windows
> This is not what I wanted. It used my fstab entries, and it picked
> the "camera" entry over the labeled entry.
> OK, so I deleted the fstab entries & tried again. This time nothing
> **** What I'd like to happen.
> 1. Mount when plugged in.
> 2. Don't specify the device -- after all, some other (new) usb device
> could disturb the device name.
> How do I get there?
> Wlug mailing list
> End of Wlug Digest, Vol 26, Issue 19
Carlton C. Stedman II, sageman(a)wpi.edu
"To iterate is human, to recurse, divine."
-- L. Peter Deutch
At the last meeting we briefly discussed building a Linux Router from a
single board computer. I was poking around the net and found the OpenWrt
project. I'm curious if anyone has any experience with OpenWrt?
I have a question about hotplugging & USB and some differences I see
between 2 different FC3 systems (home & work).
Initially, I configured my drive at home. I did NOT have the menu
Preferences -> Removable Storage
set to "Mount removable drives when hot-plugged". Without realizing
that this was an option, I used manual entries in fstab:
# usb drive
LABEL=usblinux /mnt/usb/linux auto defaults,user 0 0
/dev/sde2 /mnt/usb/windows auto defaults,user 0 0
/dev/sde1 /mnt/usb/camera auto defaults,user 0 0
This worked well & good. I was happy to be able to mount the
partitions as a user. Note that the linux partition has a label
Then, I moved the drive to my work machine.
I plugged the drive in and was surprised to find that both partitions
automatically mounted in /media:
I also saw that entries were added to /etc/fstab, reflecting the mount
points and device names.
I recognized this as better action.
Plugging the drive in, I confirmed that nothing was happening in
/media. I found the entry to automount the drive in:
Preferences -> Removable Storage
and enabled it. I unplugged and plugged the drive, and it mounted
with this from df:
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/sde1 72801276 1704196 67398920 3% /mnt/usb/camera
/dev/sde2 4176756 96 4176660 1% /mnt/usb/windows
This is not what I wanted. It used my fstab entries, and it picked
the "camera" entry over the labeled entry.
OK, so I deleted the fstab entries & tried again. This time nothing
**** What I'd like to happen.
1. Mount when plugged in.
2. Don't specify the device -- after all, some other (new) usb device
could disturb the device name.
How do I get there?
Hi, We have 2 dedicated servers, I'm hoping someone can help save me
some time and keep me from messing up the servers!
Our 2 servers are:
Server "A": 126.96.36.199
Server "B": 188.8.131.52 (not the real IPs obviously!)
I've configured Exim to allow us to send email to a domain literal (so mail sent to michaelz(a)[184.108.40.206] works)
What we'd like to do is have ALL email sent to server "A" go to server "B"... I know this can be done with MX files, but I'm not sure about setting up "domain zones" or if it's easier to just change some settings in Exim.
Santa brought me a nice 80 GB "portable" USB drive. My intended use
is a combination of backup and transporting personal files to/from
work (I want to remove them from my work hard drive). Both home and
work systems are FC3, but may be FC4 sometime soon.
I was ready to partitioning (4 GB fat, remainder ext3) when I started
reading up on logical volumes. They seem pretty neat, but I wonder
if they are useful for a portable drive. In particular, I can see
that some/all of the definitions for the group and volume are in
/dev/mapper, so I'd have to duplicate some of the setup on both
Any recommendations or experience? Would I be better off with
physical partitions for this use?