On Sat, 5 Aug 2000, Frank Hale wrote:
> > Make sure /usr/sbin is in your $PATH
>
> Got it thanks, /usr/sbin is not currently in my path as I a su'ed to
> root. Will exit out and login as root. Thanks!
'su -' instead of 'su' will add /usr/sbin to your path.
--
Pekka Savola"
>
> Make sure /usr/sbin is in your $PATH
>
Got it thanks, /usr/sbin is not currently in my path as I a su'ed to
root. Will exit out and login as root. Thanks!
So what will happen when it creates the boot disks? Will it use the
kernel I have currently installed on my machine? 2.2.16? If not how
On Sat, Aug 05, 2000 at 09:03:35PM -0400, Frank Hale wrote:
>
> Yes using -t. So I can just run through the partition screen as normal
> (but nothing will happen) and go on through the installation? Would I
> just run throuh it as normal but it just doesn't execute the actual
> install process? I
On Sat, Aug 05, 2000 at 09:01:30PM -0400, Frank Hale wrote:
> ./upd-instroot: chroot: command not found
>
>
> It gets to ./upd-instroot and sits there, then I have to ctrl-c and kill
> it. Anyone know whats wrong?
Make sure /usr/sbin is in your $PATH
Matt
___
Matt Wilson wrote:
>
> As long as you're running it with -r (--rootpath) or -t (--test) you
> should be fine -- no partitioning or formatting will take place.
>
Yes using -t. So I can just run through the partition screen as normal
(but nothing will happen) and go on through the installation? W
> When make-boots is done, your images should be in the subdirectory images
> (still relative to the root of the CD). Instead of "make make-boots", you
> might want to try "make do-make", which also rebuilds the hdimage and the
> driver disks.
>
> I hope that helps.
>
Ok I did a make inside /mi
As long as you're running it with -r (--rootpath) or -t (--test) you
should be fine -- no partitioning or formatting will take place.
Matt
On Sat, Aug 05, 2000 at 08:23:29PM -0400, Frank Hale wrote:
> > Nuke the first and last line...
> >
>
> Got it, Thank you! It works now.
>
> Okay
> Nuke the first and last line...
>
Got it, Thank you! It works now.
Okay next question. When I am testing it what do I do when it gets to
the partition screen? Can I go past that point without screwing my hard
drive up? I'd like to see if it sees my new packages correctly.
Thanks a million,
F
>
> > I believe there's an old saying: "It was difficult to write, it should be
> > difficult to read".
>
> They probably don't want anyone messing with it thats why there is no
> comments. It just makes me so angry that the code has no comments plus
> is very ugly to look at, modify, compile, e
Nuke the first and last line...
> #resolv.conf -
> domain worldnet.att.net
> search worldnet.att.net
> nameserver 204.127.160.2
> nameserver 204.127.129.2
> nameserver
___
Redhat-devel-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/ma
> When anaconda reads /etc/resolv.conf, it knows that the loader (the C
> part of the installer that lives on the boot disk) has written
> /etc/resolv.conf - so it knows what the format will look like. What's
> your resolv.conf say?
>
#resolv.conf -
domain worldnet.att.net
search worldnet.att.n
cat /etc/resolv.conf -- are there any lines with only one word on it?
When anaconda reads /etc/resolv.conf, it knows that the loader (the C
part of the installer that lives on the boot disk) has written
/etc/resolv.conf - so it knows what the format will look like. What's
your resolv.conf say?
On Sat, Aug 05, 2000 at 07:42:42PM -0400, Frank Hale wrote:
>
> So I should get anaconda-7 and use it instead of the one which comes
> with 6.2?
Well, more bugs are fixed in the 7 code, but if you're shooting for a
6.2 based CD, you may as well take the least invasive approach and use
the 6.2 co
> > This starts up and gives me the RedHat logo but then craps out with some
> > error which doesn't really give me any information
>
> See, this may not look like information to you, but it can tell me
> exactly what is wrong. One thing I hate about "bug" reports is when
> people say "it printe
> We switched to Python for several reasons:
>
>1) it's dirt easy to debug -- errors raise exceptions that can
>easly be written to disk, we include the tiny pdb debugger so
>you can drop right in to a debugging session to poke at things
>in an uncaught exception
>
On Sat, Aug 05, 2000 at 05:49:26PM -0400, Frank Hale wrote:
>
> This starts up and gives me the RedHat logo but then craps out with some
> error which doesn't really give me any information
See, this may not look like information to you, but it can tell me
exactly what is wrong. One thing I hat
> You'd be better off starting from the
> .src.rpm in pinstripe and doing all your testing from
> BUILD/anaconda-7.0/, though.
>
So I should get anaconda-7 and use it instead of the one which comes
with 6.2?
> And, by the way, I'm not inclined to help you much more if you
> continue speaking th
>From 4.0 to 6.0 the code was in C. From 6.1 - current it's in
python.
We switched to Python for several reasons:
1) it's dirt easy to debug -- errors raise exceptions that can
easly be written to disk, we include the tiny pdb debugger so
you can drop right in to a debugging s
Frank Hale wrote:
>
> I've got several old RedHat dists, with the text mode installer. Does
> anyone know what language it was written in?
>
> Frank
>
I'm pretty sure that I read somewhere that they were written in C.
Supposedly the switch to python was made because it was simpler/faster
to w
>From the main anaconda file:
# booleans - value is 0 for false or non-zero for true
# test - in test mode?
# xmode - bring up text mode in a X terminal window?
# debug - in debug mode?
# serial - install via serial port (?)
# expert - in expert mode?
#
I've got several old RedHat dists, with the text mode installer. Does
anyone know what language it was written in?
Frank
___
Redhat-devel-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-devel-list
>
> What are you having trouble understanding?
I'd like to run the anaconda installer on my local drive. I've copied
the entire install CD to /redhat_cd. Since I modified alot of the
install packages and comps file. I made some new pixmaps and such for
the installer. I'd like to run anaconda in
> I believe there's an old saying: "It was difficult to write, it should be
> difficult to read".
They probably don't want anyone messing with it thats why there is no
comments. It just makes me so angry that the code has no comments plus
is very ugly to look at, modify, compile, etc I wonder
You're reading the wrong file. The important ones are fairly well
commented. Also, people unfamiliar with Python sometimes have trouble
getting used to some of the constructs... If you're used to reading
Python, the anaconda code is pretty self explanatory.
What are you having trouble understa
On Sat, 5 Aug 2000, Frank Hale wrote:
> Do the programmers at RedHat believe in putting comments in anaconda?
> Jesus christ the code couldn't be anymore unreadable.
>
> Frank
I believe there's an old saying: "It was difficult to write, it should be
difficult to read".
;-)
--
Pekka Savola
Do the programmers at RedHat believe in putting comments in anaconda?
Jesus christ the code couldn't be anymore unreadable.
Frank
___
Redhat-devel-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-devel-list
Are you posting from a different address than the one you subscribed
from? For example, I have the address [EMAIL PROTECTED] but it is
being forwarded to my real address. If I subscribe with my real address
and mail with the bigfoot one, or vice versa, I would get the same
message you got.
Jesse
On Sat, Aug 05, 2000 at 05:50:50PM -0400, Frank Hale wrote:
> after you make changes to anaconda where do you install it? Does it go
> under /RedHat/instimage? All the changes I made never took place because
If you make changes in misc/src/anaconda, you should then have them
copied over to instim
On Sat, Aug 05, 2000 at 05:45:59PM -0400, Frank Hale wrote:
> How are the RH boot disks created? I am modifying my RH 6.2 CD
> and would like to provide updated boot disks with kernel 2.2.16
> on it. Is there a HOWTO or FAQ somewhere that shows how to make
> an install boot disk for RedHat linu
after you make changes to anaconda where do you install it? Does it go
under /RedHat/instimage? All the changes I made never took place because
I didn't know you had to install it. I figured since the src was on the
install cd that it used that one to install RedHat, I was wrong.
Frank
___
I am in the process of changing the packages which are installed
with RH 6.2. I will then burn it to CD so that it can be installed.
Since I am making rather large changes to the installed packages I want
to change the release name (Zoot) to something like (Zoot-Update) or
something like that so t
On Fri, 4 Aug 2000, Jesse Marlin wrote:
> > I'm trying to get rid of NT and 95 form 10 workstations and can't roll
> > out Redhat6.2 as NIC's dont appear to ne2000 compat.
> > Does anyone know about the kingston cards and ne2000 compatibility.
> > The card is supposed to be NE2000 compatible and
How do you test anaconda. I made some changes to the pixmaps and I wanna
test it before I burn it to cd.
I'm using 6.2
I've tried:
./anaconda --gui
--rootpath=
--method=dir://path/to/my/modified/redhat/dist
This starts up and gives me the RedHat logo but then craps out with some
error which do
How are the RH boot disks created? I am modifying my RH 6.2 CD
and would like to provide updated boot disks with kernel 2.2.16
on it. Is there a HOWTO or FAQ somewhere that shows how to make
an install boot disk for RedHat linux? I'm specifically talking
about the install boot disk for RH insta
On Fri, Aug 04, 2000 at 08:49:20PM -0700, John Gerth wrote:
> I tried Rudi's patch (and the mouse patch in todo.py) but it
> still blew up trying to write the X config file later on.
Ooops! I thought I had posted a follow-up describing what had happened
during the final test (my mail was sent w
Adrian Browne writes:
> I'm trying to get rid of NT and 95 form 10 workstations and can't roll
> out Redhat6.2 as NIC's dont appear to ne2000 compat.
> Does anyone know about the kingston cards and ne2000 compatibility.
> The card is supposed to be NE2000 compatible and it is under NT and 95,
I just started getting messages about not being subscribed to
the list. Here is a copy of it. What's up? Have I been removed.
If I have been removed then I still have the side-effect of receiving
all emails from the list.
Your mail
and how would I find out?
On Sat, 5 Aug 2000, John Summerfield wrote:
> > Hi everyone
> >
> > I have two servers with RH 6.2 and a few others with 6.1
> >
> > I'm getting a TON of messages like the above on the 6.2 systems ONLY.
> > They're running the latest 2.2.16 kernel while the other serv
Rudi Chiarito wrote:
> I found a few more problems with anaconda and kickstart files. It took me
> a whole day to figure them out, also because I had never programmed in
> Python before. ;)
>
> First of all, as soon as I managed to find how to run anaconda in test
> mode (which is not THAT much h
On Sat, 5 Aug 2000, Ingo Luetkebohle wrote:
> On Sat, Aug 05, 2000 at 06:29:41PM +0300, Pekka Savola wrote:
> > Yes.. For a single package. But if you do 'rpm -F *.rpm' in RedHat/RPMS/,
> > split up, new _required_ packages etc. should be upgraded just fine.
>
> In short, "rpm -F", for me, only
On Sat, Aug 05, 2000 at 06:29:41PM +0300, Pekka Savola wrote:
> Yes.. For a single package. But if you do 'rpm -F *.rpm' in RedHat/RPMS/,
> split up, new _required_ packages etc. should be upgraded just fine.
What, exactly, do you mean by "required" packages?
I don't know if I am expressing mys
On Sat, 5 Aug 2000, Ingo Luetkebohle wrote:
> But thats exactly the other way 'round! *You* have to know that OpenSSH is
> the new ssh software and then rpm will do the right thing. However, what I
> would to like to see in rpm is something like "here are your pakets, update
> as much as you can"
On Sat, Aug 05, 2000 at 09:50:21AM -0400, Trond Eivind Glomsrød wrote:
> > Package: samba-common
> > Depends: some-package (>=3D 1.2.3) || some-other-package (>=3D 4.5.6)
> > Replaces: samba
> You could do that by having a virtual package provided by multiple
> packages (e.g. MTA)
I t
On Sat, Aug 05, 2000 at 04:49:49PM +0300, Pekka Savola wrote:
> > Instead of hard-coding the information about package replacements and
> > package importance into an update-tool, it could be put into the package
> > header and rpm should be able to read and *use* that information for the
> > "Fre
> I should have phrased my point better. Thanks for point that out. To make it
> short (more elaboration below):
>
> Instead of hard-coding the information about package replacements and
> package importance into an update-tool, it could be put into the package
> header and rpm should be able to
[EMAIL PROTECTED] (Ingo Luetkebohle ) writes:
> Package: samba-common
> Depends: some-package (>=3D 1.2.3) || some-other-package (>=3D 4.5.6)
> Replaces: samba
You could do that by having a virtual package provided by multiple
packages (e.g. MTA)
--
Trond Eivind Glomsrød
Red
Hoi Pekka,
I should have phrased my point better. Thanks for point that out. To make it
short (more elaboration below):
Instead of hard-coding the information about package replacements and
package importance into an update-tool, it could be put into the package
header and rpm should be able to
On Sat, 5 Aug 2000, Ingo Luetkebohle wrote:
> On Sat, Aug 05, 2000 at 07:30:34AM +0800, John Summerfield wrote:
> > mkkickstart is for cloning the same release; it does not cope well with
> > upgrades where packages get renamed, split up differently or otherwise
> > reoganised.
>
> Exactly. Tha
On Sat, Aug 05, 2000 at 07:30:34AM +0800, John Summerfield wrote:
> mkkickstart is for cloning the same release; it does not cope well with
> upgrades where packages get renamed, split up differently or otherwise
> reoganised.
Exactly. Thats what rpm is for.
IMHO, implementing much more flexib
On Sat, 5 Aug 2000, John Summerfield wrote:
> > On Fri, 4 Aug 2000, Pekka Savola wrote:
>
> >
> > Hmm, would be usable but I think of two things:
> >
> > 1. It would be cute to have a script line mkkickstart which generates the
> >config for an Upgrade (easy i think)
>
> mkkickstart is f
50 matches
Mail list logo
