12:03 a.m.
Phil R wrote
I could not get SVN 7704 to compile and didn't see where any
snapshot
archive where it was successfully created either.
I apologize I should have looked closer at this the first time - apparently
I could not either - see date stamps below on these snapshots of the source
code - I was on 7702 when I responded the first time the other day - note
7702 was pulled 5 Min after 7704.
/her7702 │ 4096│Aug 19 00:54
/her7704 │ 4096│Aug 19 00:49
/her7737 │ 4096│Sep 3 13:11
I have since moved up to 7737 - but as I am writing this EMAIL noticed my OS
had crashed - SIE issue - and I noticed in the change log there have been
some changes in this part of the hercules code recently - so I might be
headed back to 7702.
You may have misunderstood. I haven't created any Fedora DASD. I
have
been using the 'turnkey images' of FC11 & FC14 available at:
I did - I thought you had gotten further with FC15
<snip>
While messing with some of this lately, I have discovered the
hercules.init
script located at the above link causes hercules to get a
segmentation
fault when specific choices are made during IPL. It works >fine
with FC11,
but with FC14 if one selects one of the two choices 0 or 1 instead of
letting the default linux kernel boot, a segmentation fault occurs.
If
left to time out, the default kernel starts to boot >and continues until
logon >prompt is displayed.
Not sure - I started on FC11 and updated it to FC12 in place - skipped FC14
and installed from scratch FC15 - FC15 seems really stable to me have not
had any issues -
So as to leave most of old stuff behind I tried to boot FC15 using the
kernel.img, initrd.img & generic.prm from
s/images/
Those dates match what I have here from the ISO DVD for FC15
So I pulled the latest Source code snapshot - 7747 compiled it - and tried
to boot the install images -
it just loops never getting past - the Linux message - "Trying to unpack
rootfs image as initramfs..."
Went back to 7702 and it came up to the network configuration fine.
Using the hercules.init script mentioned above with minor changes for
FC15
DASD and hercules version line, upon IPL of C, hercules gives a
segmentation fault almost immediately. When I used an >older
version of
hercules, or started hercules without the script ( don'r remember
>which one
worked), I get to a point where it tells me a blacklist exists and do I want
to clear it or continue.
I definitely can get that far on 7702
It also starts asking about a gateway IP address ??? Is that my Host
OS
leased IP address it grabbed via automagic means when I booted my host PC ?
Are you running hercules under Windows or Linux?
It also depends if you are using CTCs - it would be the IP address at the
other end, if you are using LCS devices it should be your router or gateway
to the internet. LCS Devices are simpler to use on Linux you do not need
to add routes just a change to sysctl.conf to
net.ipv4.conf.default.proxy_arp = 1
And the Linux guest just appears as another machine on your network - this
setting is for RHEL/Fedora Linux
Here is the final config - copied from
/etc/sysconfig/network-scripts/ifcfg-eth0 - highlighting the things you will
be prompted for during the install.
From herc Config
0740.2 LCS -n /dev/net/tun 192.168.100.121
From FC15 networking config
DOMAIN="dpcomputersolutions.com"
NM_CONTROLLED="yes"
OPTIONS="layer2=0" // take default
DNS1="192.168.100.5" // IP of
DNS Server used on your network
IPADDR="192.168.100.121" // IP of
hercules FC15 guest IP address
SUBCHANNELS="0.0.0740,0.0.0741" // LCS Devices
GATEWAY="192.168.100.1" // router gateway
on your network
PORTNAME="0"
NETMASK="255.255.255.0" // netmask
BOOTPROTO="static"
NETTYPE="lcs" // LCS Device for network adapter
DEVICE="eth0"
MTU="1500"
ONBOOT="yes"
> Do I have to have the modules for TUN and brothers loaded ( via
the
hercules.init script ) in order to get access to anything from FC15 ?
Typically I do not - and Hercules loads everything required from the search
path - so I have nothing in my config using LDMOD
Hopefully this helps -
Phil Pinto
--
This message has been scanned for viruses and
dangerous content.
--
This message has been scanned for viruses and
dangerous content.