Anaconda-devel November 2005

anaconda-devel@lists.stg.fedoraproject.org

21 participants
18 discussions

Changing the default theme
by Manilal K M 05 Feb '06

05 Feb '06

Hello everybody, I don't know whether this query is an offtopic. However I need information regarding it. I have custom compiled the FC-4 and installed it sucessfully with the great help from anaconda-devel-list. Now I need to change the default theme clearlooks to "Simple". I edited the patch associated with redhat-artwork (redhat-artwork-0.121-clearlooks.patch) and the file "redhat-artwork-0.122/gtkrc1-skel" and changed them to "Simple". However I noticed NO change in the theme. After Logging in I still get the default Blucurve icons and Clearlooks theme. Kindly advice. regards Manilal

3 4

Kickstart prompt for network info using custom CD based install
by Deepak Naidu 05 Dec '05

05 Dec '05

Hi, I know this quest has been raised many times and also I find one in bugzillla as below. https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=119331 I am customizing CentOS-4.2 into one CD from 4 which uses 2.6.9 kernel and Anaconda-10. version. NOTE: CentOS is eqivalent to RHEL-4 When using kickstart in my custom CD, every thing goes fine and my system is up and running with one glitch... It does not prompts for Network configuration option even after it is not provided in the ks.cfg. So googling arround showed me that one has to comment dispatch.skipStep("network") option in kickstart.py in anaconda and then create the stage2.img... I did this and still it does not prompts.... Is there any other file or patch I have to edit or patch.... I hope some one has the ans ... or what is an alternative.... Cheers, Deepak Naidu. Linux your Life, Don't Window it [[]] { All for the best } --------------------------------- Yahoo! Messenger NEW - crystal clear PC to PC calling worldwide with voicemail

2 4

system-splash.png and derivatives
by Alan Milligan 01 Dec '05

01 Dec '05

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, One thing that really frustrates me about anaconda is that it's splash screen generation sucks -at least for anaconda <= FC4 - I'm not enough of a masochist to try the latest devel packages ;) system-splash.png is located in fedora-logos (or redhat-logos). When creating a Linux derivative distribution, the first thing we do is create a new -logos package (the second thing is a new -release package). However, upd-instroot hard-codes redhat-logos and fedora-logos into it's packages and thus does not unpack our -logos and then barfs when system-splash.png is not found. What I'd like to see instead, is something similar to the tzdate logic, where it checks through the %{PROVIDES} to discover this (maybe look for provides redhat-logos). At the moment, we have to cut new anaconda packages for each derivative - - with this change, we wouldn't need to. Another less glamorous option could be to pass this as a parameter to buildinstall, but I'd prefer to use the knowledge contained in the RPM's. Anyone care to comment? Any chance of getting this into FC5? Alan -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iD8DBQFDi+YcCfroLk4EZpkRAt0lAJ9d7qa2OgejRurZmRKjk8BoSe6vJwCeOmCd ZCDhuyr1t2IkljN+u96wgSA= =JPhx -----END PGP SIGNATURE-----

4 6

FC devel anaconda 10.90.8 with --test wants vnc password
by Patrick Mansfield 30 Nov '05

30 Nov '05

Jeremy - Building and running with anaconda-10.90.8 with a --test install, it is asking for a vnc password, though I have not (and AFAICT for test can't) set one. I tried using no password, root password, and my own local password to no avail. This was working fine with FC devel of about two weeks ago, with anaconda anaconda-10.89.12. Is there a workaround, open bug, or ? The text output is: # ./anaconda --vnc --test -m nfs:/9.47.66.169//netinst/Fedora/Core/development/i386 Probing for video card: S3 Inc. Trio 64 3D Probing for monitor type: Unknown monitor Probing for mouse type: Generic - 3 Button Mouse (PS/2) Starting VNC... The VNC server is now running. Please connect to 9.47.66.49:1 to begin the install... Unknown exception setting vnc password. Unable to set vnc password - using no password! Make sure your password is at least 6 characters in length. Press <enter> for a shell Starting graphical installation... Loading /lib/kbd/keymaps/i386/qwerty/us.map.gz And vncviewer output (pops up password window and then outputs the last line): [palm ~]$ vncviewer 9.47.66.49:1 VNC Viewer Free Edition 4.1.1 for X - built Aug 4 2005 06:43:41 Copyright (C) 2002-2005 RealVNC Ltd. See http://www.realvnc.com for information on VNC. Tue Nov 29 16:41:55 2005 CConn: connected to host 9.47.66.49 port 5901 CConnection: Server supports RFB protocol version 3.8 CConnection: Using RFB protocol version 3.8 Tue Nov 29 16:41:59 2005 main: No password configured for VNC Auth -- Patrick Mansfield

3 3

Redhat network support
by abayomi onibudo 27 Nov '05

27 Nov '05

Hi all, i am building a custom distribution and i will like to remove the RedHat network support from my distribution during and after the boot process. does anyone know how to do this? thanks Abayomi

2 1

RedHat nash
by abayomi onibudo 27 Nov '05

27 Nov '05

Hi all, does anyone know if it is possible to remove RedHat nash or replace it with some other custom version from the booting process, if not at least remove the message. Thanks Abayomi

2 1

Anaconda in fc4
by John Summerfied 22 Nov '05

22 Nov '05

For a short while I have a laptop I can play with. I must, however, put it to work RSN. It's had, in turn, Kubuntu Breezy, SuSE 10, Mandriva 2006.1. As shipped, it had something like this: hda1 Compaq(!) recovery partition 5 G or so hda2 38G Windows XP Home (vfat32 and I mean very fat) hda{3,4} Extended (dunno which) hda5 Another very fat XP partition ("data"). K resized (very nicely) hda5 to give me space to install Linux. Suse, I installed over U and that was fine too. I know S can resize NTFS (I've done so) so I expect it would find very fat partitions a doddle. Next I replaced S with M. M, I found, has a nice GUI which promises to resize very fat partitions too (post-install in this case, the question didn't arise earlier). I used it to trim hda2; it would only take 5 Gb off it, presumably because there's a file in the way and it's not into defragging. I also pruned a little off windows D:. The result was I had a couple of fragments of free space when I came to try Fedora Core 4. Note that all me efforts to install FC4 were in text mode. Sadly, FC4 just could not cope with it. Autopartition using existing Linux partitions failed because it couldn't do its create LVM thing (sorry, I've no way of transporting stuff off this computer - no floppies, no serial port and the DVD burner was in use) unless I do a network install. I tried manual partitioning, and choosing partitions by pressing "enter" seemed to choose one to edit, but it wanted to create in cylinders (does not work), when I chose "megabytes" it didn't tell me how many I could have. I tried fdisk to create free space, but using free space doesn't work either. Meanwhile Linux has done to Windows what Windows is famous for doing to Other Operating Systems: made it unbootable. Eventuallly I manged to make one of the small bits into Linux Swap, another into Linux Native and install FC4 into that. There's still a lot of unused space:-((( Since this was going into a small paritions I decided to omit X. I was surprised deselecting X didn't also deselect Ghome and all the other stuff that requires X. I was also surprised I didn' get to examine individual package selections: I wanted xen and could not see how to be sure I was getting it. I wasn't, I didn't, I had to get it manually later. In summary: FC4's disk partitioning is farqued. Users doing a manual install of FC4 need more scope for package-selection. Note: if any of the others had made such a botch of partitioning they'd not have got installed. I'm not at all sure Anaconda's going let me install into all that free space. What I intend for this laptop is XP Professional (work licence) plus Linux: the disk will be mostly wiped RSN. If Jeremy or another Anaconda hacker has anything to ask, do so soon. I don't need help to fight my way out of this. Note: installing FC5 beta is possible (provided it's not going to be too flakey). -- Cheers John -- spambait 1aaaaaaa(a)computerdatasafe.com.au Z1aaaaaaa(a)computerdatasafe.com.au Tourist pics http://portgeographe.environmentaldisasters.cds.merseine.nu/ do not reply off-list

1 0

[PATCH] FC4 cannot load driver disk image on a disk partition
by Akinobu Mita 22 Nov '05

22 Nov '05

Hello, I tried to load driver disk image on a partition in USB storage device. (/dev/sda1:dd.img) But It failed. Steps to Reproduce: 1. create driver disk image (dd.img) 2. put dd.img on USB storage device partition (/dev/sda1) 3. start FC4 installer with "linux dd" 4. select driver disk source as /dev/sda1 and choose the file "dd.img" Actual results: anaconda went wrong stage. anaconda displays: ---| Insert Driver Disk |--- Insert your driver disk into /dev/sda and press "OK" to continue. Expected results: Successfully load from driver disk image. I think below patch fixes this problem. but it is untested. --- anaconda-10.3.0.7/loader2/driverdisk.c.orig 2005-07-27 18:25:13.000000000 +0900 +++ anaconda-10.3.0.7/loader2/driverdisk.c 2005-07-27 18:25:56.000000000 +0900 @@ -380,6 +380,7 @@ int loadDriverFromMedia(int class, modul break; } stage = DEV_LOAD; + break; } case DEV_INSERT: {

3 5

Redhat 9 & Anaconda
by Joubert Berger 22 Nov '05

22 Nov '05

I have been changing my boot kernel to use the 2.4.31 kernel from kernel.org<http://kernel.org>for a Redhat 9 distribution. I now have everything working except it will not mount my partitions after they have been formated. I can manually mount them. But, they don't mount when it starts trying to install the RPM packages. I am using the megaraid2 driver from the 2.4.31 kernel. Can anyone point me to where I might look what is going on. --joubert

1 0

Help - rebuilding CD's, error - "Not a CentOS disk"
by Scott Sharkey 20 Nov '05

20 Nov '05

Hi All, I'm building a custom CentOS distribution. I've followed the directions on the anaconda-devel website at Fedora, plus am using Johnny Hughes' build.sh script, and am having a strange problem. The CD's build OK, and when I boot from them they skip the "test the MD5 sum" step, go to text mode, and request what language, keyboard, and media I want. I answer CDROM, and get back "That is not a valid CentOS-4 CDROM". Interestingly, if I put in a REAL CentOS-4 CDROM, hit back, and try again, I get the same error. I have checked - there is a .discinfo file on the disk, and it's contents seem right. I did notice that the isolinux directory does NOT get updated stage2.img, or hdinst.img files, even though I'm running buildinstall. Also, the boot.iso and bootdisk.img files disappear from the /images directory. I am assuming that I'm having an error with the buildinstall step, though no errors are logged in the file. But I was under the impression that buildinstall was supposed to rebuild the stage2.img. It does appear to be rebuilding the vmlinuz kernel and the isolinux.bin files. Any suggestions? I'm currently reading through upd-instroot script to see if that shed's any light. Thanks! -Scott

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Anaconda-devel November 2005