Ray Atnip wrote:
I know I'm responding to this msg a little late but I wasn't ready to
upgrade until
now.
I'm using a Soekris board and CF disk. (no floppy or hard drive).
The 'partial' backups seem to be the ideal way to upgrade but it appears
that
they will overwrite the existing lrp on the
Basically just lrpkg -i :-)
And lncurses.lrp. And lrdline2.lrp.
You will have to relink /bin/sh with /bin/ash to make all Bering scripts
happy. Dig in the archives, there is a message explaining the details.
Did you try the bash package in the glibc 2.0 directory?
Thanks for the link, Mike, but
Charles -- are you familiar with this problem? Your raid guide mentions
being able to use raid5 partitions, but this error is stopping me. I've
also looked through the software raid-howto and found nothing about this
error. I've google'd the error and the only thing I've been able to
find
On Tue, 21 Dec 2004, Michael McClure wrote:
raid-disk 2
Yes, I know, ignore the fact that the 2nd partition sets are on the same
disk -- I'm just trying to see if I can get it to work. I also tried
doing a straight Raid 1 using the first two partitions in the set above
and get the
Michael McClure wrote:
Thanks for the reply. Should I be using a different version/release
that would work better for RAID? If so, pls let me know. As far as
your info requests, see below.
thanks.
mike.
# lsmod
Module PagesUsed by
3c59x 19984 1
pci-scan
Charles Steinkuehler wrote:
Michael McClure wrote:
Thanks for the reply. Should I be using a different version/release
that would work better for RAID? If so, pls let me know. As far as
your info requests, see below.
thanks.
mike.
# lsmod
Module PagesUsed by
3c59x
Max
rawdata wrote:
Basically just lrpkg -i :-)
And lncurses.lrp. And lrdline2.lrp.
You will have to relink /bin/sh with /bin/ash to make all Bering
scripts happy. Dig in the archives, there is a message explaining the
details.
Did you try the bash package in the glibc 2.0 directory?
Thanks
On Wed, 22 Dec 2004, Erich Titl wrote:
Yep, the problem is, bin/bash is also in initrd.list, why I would not know. I
will check with Charles which did som modification in this area early this
year
cheers
Erich
Cheers to you, Erich. I commented out bin.bash in initrd.list, and the
darn thing
Sorry to intrude on this thread, but I noticed a few things.
The first being that the drive partitions are not set correctly. If I
recall correctly, the partition types need to be set to fd Linux raid
auto
chernobyl# fdisk /dev/sda
Command (m for help): p
Disk /dev/sda: 9104 MB, 9104953344
Interestingly enough, I found that my port 113 appeared to be closed
while all other ports I tested (up to 1056) using the Shields Up
program seemed invisible.
I added a rule in /etc/shorewall/rules
DROP netfwtcp 113
then the port showed up as stealthed. Ahh,
Why did
Sorry. Forgot to mention that I am using Bering uClibc - the newest
version.
On Tue, 2004-12-21 at 23:40 -0800, Terry Erickson wrote:
Interestingly enough, I found that my port 113 appeared to be closed
while all other ports I tested (up to 1056) using the Shields Up
program seemed invisible.
This doesn't seem available. I don't see an fd type or anything related
to a raid type? Perhaps you're thinking a later version that
Dachstein's kernal?
Command (m for help): t
Partition number (1-4): 1
Hex code (type L to list codes): l
0 Emptyc Win95 FAT32 (LB 64 Novell
12 matches
Mail list logo
