From: Justin H. <car...@ya...> - 2004-06-29 15:36:28
|
CONFIG_ALSA=n CONFIG_APCUPSD=y CONFIG_ARPWATCH=n CONFIG_BINUTILS=y CONFIG_BOOT_OPTION_VGA=80x25 CONFIG_BRIDGE_UTILS=y CONFIG_CDRTOOLS_ON_CD=n CONFIG_CLAMAV=n CONFIG_CRON=y CONFIG_CVS=y CONFIG_CYRUS_SASL=n CONFIG_DAEMONTOOLS=y CONFIG_DDUP=n CONFIG_DEVIL_DOC_ISO=n CONFIG_DEVIL_MAN_ISO=n CONFIG_DISABLELOGGING=n CONFIG_DISTCCD=n CONFIG_DJBDNS=n CONFIG_DNSMASQ=n CONFIG_DOSFSTOOLS=n CONFIG_DOVECOT=n CONFIG_EAGLE_USB=n CONFIG_EBTABLES=y CONFIG_ETHTOOL=y CONFIG_EZ_IPUPDATE=n CONFIG_FETCHMAIL=n CONFIG_FILE=y CONFIG_FROX=n CONFIG_FWLOGWATCH=n CONFIG_GCC3=y CONFIG_GCC_PIE=y CONFIG_GCC_STACK_PROTECTOR=y CONFIG_GPM=n CONFIG_HEARTBEAT=y CONFIG_HEIMDAL=n CONFIG_HIGHMEM=y CONFIG_HOTPLUG=y CONFIG_HTTPD=n CONFIG_IANS=y CONFIG_INITRD_FS=EXT2 CONFIG_IPAC_NG=y CONFIG_IPROUTE2=y CONFIG_ISC_BIND=n CONFIG_ISC_DHCP=y CONFIG_JFS=y CONFIG_JFTPGW=n CONFIG_JOE=n CONFIG_KERNEL_CPU=686 CONFIG_L2TPD=y CONFIG_LCD4LINUX=y CONFIG_LFTP=y CONFIG_LHA=n CONFIG_LIBSAFE=y CONFIG_LIBSTDC_COMPAT=y CONFIG_LINUX_NR_CPUS=4 CONFIG_LINUX_SMP=y CONFIG_LINUX_VERSION=2.6 CONFIG_LINUX_WLAN_NG=n CONFIG_LM_SENSORS=y CONFIG_LOGROTATE=y CONFIG_LVM2=y CONFIG_LYNX=y CONFIG_MC=n CONFIG_MDADM=y CONFIG_MEMTEST86=y CONFIG_MGETTY=n CONFIG_MINICOM=y CONFIG_MOTION=n CONFIG_MOXIO_SMARTIO=n CONFIG_MTOOLS=n CONFIG_MTR=y CONFIG_MT_ST=n CONFIG_MYSQL_CLIENT=y CONFIG_MYSQL_SERVER=n CONFIG_NAIL=n CONFIG_NCFTP=y CONFIG_NETACCT=n CONFIG_NET_SNMP=y CONFIG_NICE=n CONFIG_NO_IP_UPDATER=n CONFIG_NO_LOCALE=y CONFIG_NTOP=n CONFIG_NTP=y CONFIG_OIDENTD=n CONFIG_OPENLDAPLIB=n CONFIG_OPENSSH=y CONFIG_OPENSSL_BIN=y CONFIG_OPENVPN=y CONFIG_PASSWDGEN=y CONFIG_PCIUTILS=y CONFIG_PCMCIA_CS=n CONFIG_PERL=n CONFIG_PMAKE=4 CONFIG_POPTOP=y CONFIG_PORTMAP=n CONFIG_PORTSLAVE=n CONFIG_POSTFIX=n CONFIG_POSTGRESQL_CLIENT=y CONFIG_POSTGRESQL_SERVER=n CONFIG_PPP=y CONFIG_PPTP_CLIENT=y CONFIG_PRISM54=n CONFIG_PSCHED_CLOCK_SOURCE=PSCHED_JIFFIES CONFIG_PWLIB=n CONFIG_PYTHON=n CONFIG_QADSL=n CONFIG_QUAGGA=n CONFIG_QUOTA_TOOLS=n CONFIG_RADVD=n CONFIG_RAIDTOOLS=n CONFIG_RCS=n CONFIG_RPM=n CONFIG_RPPPPOE=n CONFIG_RRLOGIND=n CONFIG_RSYNC=y CONFIG_SARG=n CONFIG_SCREEN=y CONFIG_SER=y CONFIG_SG3_UTILS=y CONFIG_SHOREWALL=n CONFIG_SMARTMONTOOLS=y CONFIG_SNORT=y CONFIG_SQUID=n CONFIG_SQUIDGUARD=n CONFIG_STUNNEL=y CONFIG_SUDO=n CONFIG_SYSSTAT=y CONFIG_TCPDUMP=y CONFIG_TCP_WRAPPERS=y CONFIG_TELNET_BSD=y CONFIG_THTTPD=y CONFIG_UNARJ=n CONFIG_UNRAR=n CONFIG_UNZIP=n CONFIG_USE_DISTCC=n CONFIG_VIM=y CONFIG_VLAN=y CONFIG_VOBCOPY=n CONFIG_VSFTPD=n CONFIG_VTUN=y CONFIG_WATCHDOG=y CONFIG_WEBALIZER=n CONFIG_WGET=y CONFIG_WIRELESS_TOOLS=n CONFIG_WOL=y CONFIG_WVDIAL=n CONFIG_XFS=n CONFIG_XINETD=y CONFIG_ZIP=n CONFIG_ZISOFS=y CONFIG_CPU=686 |
From: Tim T. <t....@co...> - 2004-06-29 16:14:53
|
Justin Hannah wrote: > Using CVS HEAD, I tried to slim down Devil Linux for my needs and > build it but "make build" gets stuck when using my .config file. If I > simply replace the .config with the original, make prepare build then > everything works fine up until cramfs but that is a different problem > to work out later. > > There is nothing in tmp/LOGS/build besides prepare, and that one looks > fine. > > Here is my .config file... Any ideas? By stuck do you mean hung? I'm not an expert at this but: Did you do the whole make thing, ie, make mrproper make unpack make menuconfig make prepare make build make iso "make mrproper" blows aways the whole tmp dir which includes the unpacked sources (annoying) but sometimes it is the only way I can get a change to build. Sometimes a "make clean prepare" is enough. Did you edit the .config directly or did you use "make menuconfig"? Tim |
From: Justin H. <car...@ya...> - 2004-06-29 18:34:48
|
Yes I built it exactly like you described and I used make menuconfig. By being stuck I mean it sits there and does not do anything. I pasted the .config file so others perhaps can load it in their system, compile and see if they have the same experience. Thanks, Justin Tim Tait <t....@co...> wrote: Justin Hannah wrote: > Using CVS HEAD, I tried to slim down Devil Linux for my needs and > build it but "make build" gets stuck when using my .config file. If I > simply replace the .config with the original, make prepare build then > everything works fine up until cramfs but that is a different problem > to work out later. > > There is nothing in tmp/LOGS/build besides prepare, and that one looks > fine. > > Here is my .config file... Any ideas? By stuck do you mean hung? I'm not an expert at this but: Did you do the whole make thing, ie, make mrproper make unpack make menuconfig make prepare make build make iso "make mrproper" blows aways the whole tmp dir which includes the unpacked sources (annoying) but sometimes it is the only way I can get a change to build. Sometimes a "make clean prepare" is enough. Did you edit the .config directly or did you use "make menuconfig"? Tim ------------------------------------------------------- This SF.Net email sponsored by Black Hat Briefings & Training. Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com _______________________________________________ Devil-linux-discuss mailing list Dev...@li... https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss --------------------------------- Do you Yahoo!? New and Improved Yahoo! Mail - 100MB free storage! |
From: Heiko Z. <he...@zu...> - 2004-06-29 20:16:21
|
Justin, > Yes I built it exactly like you described and I used make menuconfig. By > being stuck I mean it sits there and does not do anything. I pasted the > .config file so others perhaps can load it in their system, compile and > see if they have the same experience. As I wrote in my other email, to analyze the problem we need your tmp/LOGS/build/prepare file. -- Regards Heiko Zuerker http://www.devil-linux.org |
From: Tim T. <t....@co...> - 2004-06-29 20:26:48
|
Justin Hannah wrote: > Yes I built it exactly like you described and I used make menuconfig. > By being stuck I mean it sits there and does not do anything. I > pasted the .config file so others perhaps can load it in their system, > compile and see if they have the same experience. > > Thanks, > > > Justin > > > Tim Tait <t....@co...> wrote: > > Justin Hannah wrote: > > > Using CVS HEAD, I tried to slim down Devil Linux for my needs and > > build it but "make build" gets stuck when using my .config file. > If I > > simply replace the .config with the original, make prepare build > then > > everything works fine up until cramfs but that is a different > problem > > to work out later. > > > > There is nothing in tmp/LOGS/build besides prepare, and that one > looks > > fine. > > > > Here is my .config file... Any ideas? > > By stuck do you mean hung? > > I'm not an expert at this but: > > Did you do the whole make thing, ie, > > make mrproper > make unpack > make menuconfig > make prepare > make build > make iso > > "make mrproper" blows aways the whole tmp dir which includes the > unpacked sources (annoying) but sometimes it is the only way I can > get a > c hange to build. Sometimes a "make clean prepare" is enough. > > Did you edit the .config directly or did you use "make menuconfig"? > > Tim > Like Heiko said logs would help. But I did have a similar problem in 1.1.x, when I checked the logs I realized that one of the lines was an interactive prompt for new build option for one of the packages. Thus entering "n" into the terminal that was running the build let it continue. Tim |
From: Justin H. <car...@ya...> - 2004-06-30 04:17:15
|
I figured it would probably be something simple like this. I will try that 'n' idea next but I can't use kernel 2.4 because it dosen't like my new hardware (Intel E7210 chipset P4) such as the E1000 hanging off the southbridge chipset etc. The prepare log shouldn't matter since prepare exits cleanly, its build that it gets stuck on. Theres no log besides prepare, unless its appending to it? - Justin Tim Tait <t....@co...> wrote: Like Heiko said logs would help. But I did have a similar problem in 1.1.x, when I checked the logs I realized that one of the lines was an interactive prompt for new build option for one of the packages. Thus entering "n" into the terminal that was running the build let it continue. Tim ------------------------------------------------------- This SF.Net email sponsored by Black Hat Briefings & Training. Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com _______________________________________________ Devil-linux-discuss mailing list Dev...@li... https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss --------------------------------- Do you Yahoo!? New and Improved Yahoo! Mail - 100MB free storage! |
From: Heiko Z. <he...@zu...> - 2004-06-30 13:26:21
|
> I figured it would probably be something simple like this. I will try > that 'n' idea next but I can't use kernel 2.4 because it dosen't like my > new hardware (Intel E7210 chipset P4) such as the E1000 hanging off the > southbridge chipset etc. OK it looks like we have to fix the problems then. ;-) I wanted to wait for the new grsecurity, before I include 2.6.7. So you will have to wait a couple more days for this. > The prepare log shouldn't matter since prepare exits cleanly, its build > that it gets stuck on. Theres no log besides prepare, unless its > appending to it? It has nothing to do with "make prepare", because there is also a script prepare which is executed at the beginning of "make build". Send us the logfile or turn of the logfiles in "make menuconfig", then you can also see where it hangs. -- Regards Heiko Zuerker http://www.devil-linux.org |
From: Heiko Z. <he...@zu...> - 2004-06-29 18:46:18
|
> Using CVS HEAD, I tried to slim down Devil Linux for my needs and build it > but "make build" gets stuck when using my .config file. If I simply > replace the .config with the original, make prepare build then everything > works fine up until cramfs but that is a different problem to work out > later. > > There is nothing in tmp/LOGS/build besides prepare, and that one looks > fine. Can you post the tmp/LOGS/build/prepare file ? > Here is my .config file... Any ideas? The HEAD tag is the current development version (DL 1.3). This version uses Kernel 2.6 which is currently not really working. Switch to kernel 2.4 You can also use the rel-1-2-patches tag (with Kernel 2.4), which is much more stable and soon will become 1.2 -- Regards Heiko Zuerker http://www.devil-linux.org |