Menu
▾
▴
devil-linux-develop — developer discussions
You can subscribe to this list here.
| 2001 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(55) |
Oct
(44) |
Nov
(156) |
Dec
(123) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2002 |
Jan
(130) |
Feb
(156) |
Mar
(162) |
Apr
(171) |
May
(97) |
Jun
(127) |
Jul
(58) |
Aug
(81) |
Sep
(86) |
Oct
(45) |
Nov
(41) |
Dec
(84) |
| 2003 |
Jan
(71) |
Feb
(87) |
Mar
(133) |
Apr
(152) |
May
(151) |
Jun
(232) |
Jul
(320) |
Aug
(237) |
Sep
(271) |
Oct
(536) |
Nov
(301) |
Dec
(393) |
| 2004 |
Jan
(393) |
Feb
(184) |
Mar
(314) |
Apr
(225) |
May
(139) |
Jun
(77) |
Jul
(87) |
Aug
(75) |
Sep
(139) |
Oct
(50) |
Nov
(8) |
Dec
(28) |
| 2005 |
Jan
(66) |
Feb
(63) |
Mar
(14) |
Apr
(14) |
May
(8) |
Jun
(23) |
Jul
(21) |
Aug
(6) |
Sep
(29) |
Oct
(55) |
Nov
(38) |
Dec
(8) |
| 2006 |
Jan
(5) |
Feb
(10) |
Mar
(1) |
Apr
(15) |
May
(32) |
Jun
(44) |
Jul
(11) |
Aug
(8) |
Sep
(9) |
Oct
(14) |
Nov
(4) |
Dec
(3) |
| 2007 |
Jan
(3) |
Feb
(3) |
Mar
(2) |
Apr
|
May
|
Jun
|
Jul
(35) |
Aug
(49) |
Sep
(8) |
Oct
(42) |
Nov
(44) |
Dec
(7) |
| 2008 |
Jan
(2) |
Feb
(7) |
Mar
(8) |
Apr
(80) |
May
(74) |
Jun
(29) |
Jul
(5) |
Aug
(7) |
Sep
(6) |
Oct
(1) |
Nov
|
Dec
|
| 2009 |
Jan
(8) |
Feb
(19) |
Mar
(3) |
Apr
(24) |
May
(22) |
Jun
(23) |
Jul
(8) |
Aug
(23) |
Sep
(8) |
Oct
(27) |
Nov
(52) |
Dec
(27) |
| 2010 |
Jan
(36) |
Feb
(29) |
Mar
(17) |
Apr
(28) |
May
(21) |
Jun
(4) |
Jul
|
Aug
(28) |
Sep
(18) |
Oct
(6) |
Nov
(34) |
Dec
(16) |
| 2011 |
Jan
(18) |
Feb
(12) |
Mar
|
Apr
|
May
(9) |
Jun
(1) |
Jul
(5) |
Aug
(5) |
Sep
(7) |
Oct
(16) |
Nov
(26) |
Dec
(17) |
| 2012 |
Jan
(6) |
Feb
(34) |
Mar
(52) |
Apr
(10) |
May
(3) |
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
(4) |
Nov
(1) |
Dec
(4) |
| 2013 |
Jan
(5) |
Feb
|
Mar
|
Apr
(5) |
May
(4) |
Jun
|
Jul
|
Aug
(14) |
Sep
|
Oct
|
Nov
|
Dec
|
| 2014 |
Jan
|
Feb
(2) |
Mar
(5) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(3) |
Dec
(11) |
| 2015 |
Jan
(5) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(1) |
Sep
(1) |
Oct
(1) |
Nov
|
Dec
|
| 2016 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(2) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2017 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2018 |
Jan
(2) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Bruce S. <bw...@ar...> - 2003-07-29 16:59:50
|
> > While you're changing linuxrc, I wonder if it'd be a good idea to > > recreate /etc/Devil-release & /etc/issue & /etc/issue.net _after_ /etc > > is untar'ed from media? > > Good idea ! Go ahead and do it. I would, if I could ever build an ISO again! And this time I updated from CVS and updated source (and it even worked this time - I think :) This is after a make mrproper : make[2]: Leaving directory `/data/build/tmp/e2fsprogs-1.33/lib/blkid' test -d doc && cd doc && make install-doc-libs make[2]: Entering directory `/data/build/tmp/e2fsprogs-1.33/doc' /bin/rm -rf /data/build/tmp/tmp/info/libext2fs.info* ../mkinstalldirs /data/build/tmp/tmp/info mkdir /data/build/tmp/tmp/info for i in libext2fs.info* ; do \ /bin/install -c -m 644 $i /data/build/tmp/tmp/info/$i ; \ done gzip -9 /data/build/tmp/tmp/info/libext2fs.info* make[2]: Leaving directory `/data/build/tmp/e2fsprogs-1.33/doc' if test ! -d e2fsck -a ! -d debugfs -a ! -d misc -a ! -d ext2ed ; then make install-libs ; fi make[1]: Leaving directory `/data/build/tmp/e2fsprogs-1.33' cp: cannot stat `/data/build/tmp/tmp/sbin/mke2fs-static': No such file or directory ERROR /data/build/scripts/e2fsprogs install failed make: *** [install] Error 1 |
|
From: Bruce S. <bw...@ar...> - 2003-07-29 16:13:13
|
> cp: cannot stat `/data/build/tmp/tmp/sbin/mke2fs-static': No such file > or directory FYI, the mke2fs-static file doesn't exist: root:/data/build# ll tmp/tmp/sbin total 1080 drwxr-xr-x 2 root root 4096 Jul 29 09:29 . drwxr-xr-x 5 root root 4096 Jul 29 09:29 .. -rwxr-xr-x 1 root root 19704 Jul 29 09:29 badblocks -rwxr-xr-x 1 root root 20472 Jul 29 09:29 blkid -rwxr-xr-x 1 root root 43624 Jul 29 09:29 dumpe2fs -rwxr-xr-x 1 root root 586956 Jul 29 09:29 e2fsck -rwxr-xr-x 1 root root 37248 Jul 29 09:29 e2image -rwxr-xr-x 2 root root 78136 Jul 29 09:29 e2label -rwxr-xr-x 2 root root 78136 Jul 29 09:29 findfs -rwxr-xr-x 1 root root 32084 Jul 29 09:29 fsck lrwxrwxrwx 1 root root 6 Jul 29 09:29 fsck.ext2 -> e2fsck lrwxrwxrwx 1 root root 6 Jul 29 09:29 fsck.ext3 -> e2fsck -rwxr-xr-x 1 root root 5852 Jul 29 09:29 logsave -rwxr-xr-x 1 root root 86664 Jul 29 09:29 mke2fs lrwxrwxrwx 1 root root 6 Jul 29 09:29 mkfs.ext2 -> mke2fs lrwxrwxrwx 1 root root 6 Jul 29 09:29 mkfs.ext3 -> mke2fs -rwxr-xr-x 1 root root 3892 Jul 29 09:29 mklost+found -rwxr-xr-x 1 root root 57764 Jul 29 09:29 resize2fs lrwxrwxrwx 1 root root 7 Jul 29 09:29 tune2fs -> e2label root:/data/build# |
|
From: Bruce S. <bw...@ar...> - 2003-07-29 15:34:27
|
It's just not my day ... :-( I hacked the e2fsprogs script to copy the non-static version, so I can get past that error. I built an ISO, and it won't boot. ... Freeing initrd memory: 2862k freed VFS: Mounted root (ext2 filesystem). Freeing unused kernel memory: 112k freed Kernel panic: No init found. Try passing init= option to kernel. |
|
From: Bruce S. <bw...@ar...> - 2003-07-29 13:57:04
|
> >cp: cannot stat `/data/build/tmp/tmp/sbin/mke2fs-static': No such file > >or directory > > OK that's now an error which comes out of my latest changes. > run ./build.sh build opt=e2fsprogs again and check if you see the file > "/data/build/tmp/tmp/sbin/mke2fs-static" Nope, still not there. Why would it be there now? I did a cvs update and didn't get anything new. - BS |
|
From: Heiko Z. <hz...@pr...> - 2003-07-29 13:50:23
|
On 07/29/2003 09:31:11 AM Bruce Smith wrote: >> Looks like a problem in the makefile of e2fsprogs. >> Does a "make clean install" work ? > >Let's see ... nope! > > >make[2]: Entering directory `/data/build/tmp/e2fsprogs-1.33/doc' >/bin/rm -rf /data/build/tmp/tmp/info/libext2fs.info* >../mkinstalldirs /data/build/tmp/tmp/info >mkdir /data/build/tmp/tmp/info >for i in libext2fs.info* ; do \ >/bin/install -c -m 644 $i /data/build/tmp/tmp/info/$i ; \ >done >gzip -9 /data/build/tmp/tmp/info/libext2fs.info* >make[2]: Leaving directory `/data/build/tmp/e2fsprogs-1.33/doc' >if test ! -d e2fsck -a ! -d debugfs -a ! -d misc -a ! -d ext2ed ; then= >make install-libs ; fi >make[1]: Leaving directory `/data/build/tmp/e2fsprogs-1.33' >cp: cannot stat `/data/build/tmp/tmp/sbin/mke2fs-static': No such file= >or directory >ERROR >/data/build/scripts/e2fsprogs install failed >make: *** [install] Error 1 OK that's now an error which comes out of my latest changes. run ./build.sh build opt=3De2fsprogs again and check if you see the fil= e "/data/build/tmp/tmp/sbin/mke2fs-static" HZ = |
|
From: Bruce S. <bw...@ar...> - 2003-07-29 13:31:24
|
> Looks like a problem in the makefile of e2fsprogs.
> Does a "make clean install" work ?
Let's see ... nope!
make[2]: Entering directory `/data/build/tmp/e2fsprogs-1.33/doc'
/bin/rm -rf /data/build/tmp/tmp/info/libext2fs.info*
../mkinstalldirs /data/build/tmp/tmp/info
mkdir /data/build/tmp/tmp/info
for i in libext2fs.info* ; do \
/bin/install -c -m 644 $i /data/build/tmp/tmp/info/$i ; \
done
gzip -9 /data/build/tmp/tmp/info/libext2fs.info*
make[2]: Leaving directory `/data/build/tmp/e2fsprogs-1.33/doc'
if test ! -d e2fsck -a ! -d debugfs -a ! -d misc -a ! -d ext2ed ; then
make install-libs ; fi
make[1]: Leaving directory `/data/build/tmp/e2fsprogs-1.33'
cp: cannot stat `/data/build/tmp/tmp/sbin/mke2fs-static': No such file
or directory
ERROR
/data/build/scripts/e2fsprogs install failed
make: *** [install] Error 1
|
|
From: Heiko Z. <hz...@pr...> - 2003-07-29 13:16:44
|
On 07/29/2003 09:08:08 AM Bruce Smith wrote: >OK, I see there is another new update to scripts/e2fsprogs >I updated that script only, ran ./build.sh build opt=3De2fsprogs >And now I get a different error when running make install: :-) > > >test -d doc && cd doc && make install-doc-libs >make[2]: Entering directory `/data/build/tmp/e2fsprogs-1.33/doc' >/bin/rm -rf /data/build/tmp/tmp/info/libext2fs.info* >../mkinstalldirs /data/build/tmp/tmp/info >mkdir /data/build/tmp/tmp/info >for i in libext2fs.info* ; do \ >/bin/install -c -m 644 $i /data/build/tmp/tmp/info/$i ; \ >done >gzip -9 /data/build/tmp/tmp/info/libext2fs.info* >make[2]: Leaving directory `/data/build/tmp/e2fsprogs-1.33/doc' >if test ! -d e2fsck -a ! -d debugfs -a ! -d misc -a ! -d ext2ed ; then= >make install-libs ; fi >make[1]: Leaving directory `/data/build/tmp/e2fsprogs-1.33' >cp: cannot create hard link `/data/build/tmp/ISO/cdtree/sbin/findfs' t= o >`/data/build/tmp/ISO/cdtree/sbin/e2label': File exists >ERROR >/data/build/scripts/e2fsprogs install failed >make: *** [install] Error 1 Looks like a problem in the makefile of e2fsprogs. Does a "make clean install" work ? Heiko = |
|
From: Bruce S. <bw...@ar...> - 2003-07-29 13:08:20
|
OK, I see there is another new update to scripts/e2fsprogs
I updated that script only, ran ./build.sh build opt=e2fsprogs
And now I get a different error when running make install: :-)
test -d doc && cd doc && make install-doc-libs
make[2]: Entering directory `/data/build/tmp/e2fsprogs-1.33/doc'
/bin/rm -rf /data/build/tmp/tmp/info/libext2fs.info*
../mkinstalldirs /data/build/tmp/tmp/info
mkdir /data/build/tmp/tmp/info
for i in libext2fs.info* ; do \
/bin/install -c -m 644 $i /data/build/tmp/tmp/info/$i ; \
done
gzip -9 /data/build/tmp/tmp/info/libext2fs.info*
make[2]: Leaving directory `/data/build/tmp/e2fsprogs-1.33/doc'
if test ! -d e2fsck -a ! -d debugfs -a ! -d misc -a ! -d ext2ed ; then
make install-libs ; fi
make[1]: Leaving directory `/data/build/tmp/e2fsprogs-1.33'
cp: cannot create hard link `/data/build/tmp/ISO/cdtree/sbin/findfs' to
`/data/build/tmp/ISO/cdtree/sbin/e2label': File exists
ERROR
/data/build/scripts/e2fsprogs install failed
make: *** [install] Error 1
|
|
From: <no...@fr...> - 2003-07-29 03:02:40
|
This email is to inform you about the release of version '1.3.0' of 'mdadm' through freshmeat.net. All URLs and other useful information can be found at http://freshmeat.net/projects/mdadm/ The changes in this release are as follows: Minor bugfixes and documentation enhancements were made, and the new DegradedArray event can be signaled in --montor mode if mdadm notices a degraded array when it starts. Project description: mdadm is a tools for creating, maintaining, and monitoring Linux "md" device arrays, also known as Software RAID. If you would like to cancel subscription to releases of this project, login to freshmeat.net and choose 'home' from the personal menubar at the top of the page. You'll be presented with a list of projects you're subscribed to in the right column, which you may cancel by highlighting the project in question and clicking the 'delete' button. Sincerely, freshmeat.net ____________________________| Advertising |____________________________ Got the debugger blues? Try Etnus TotalView, the Best Linux/UNIX debugger on the planet. With superior C++ support, the best thread debugging available, a great GUI, and more useful features than any other debugger, TotalView helps reveal bugs faster than any other debugger. And it provides more insight and analysis about your code and your data. So cure the debugger blues. Get your free 15-day trial at http://www.etnus.com/Download/demo-tv.html ____________________________| Advertising |____________________________ |
|
From: Heiko Z. <he...@zu...> - 2003-07-28 23:10:25
|
Bruce Smith wrote: >>>executing busybox with option build >>>make[1]: Entering directory `/data/build' >>>make[1]: *** No rule to make target `oldconfig'. Stop. >>>make[1]: Leaving directory `/data/build' >>>ERROR >>>/data/build/scripts/busybox build failed >>>make: *** [build] Error 1 >> >>Did you update the sources from the FTP server? > > > Yup. I just did it again, and paid attention this time: :-) > > mirror: Access failed: 550 busybox-1.00-pre1.tar.bz2: Permission denied > > Not to mention: > mirror: Access failed: 550 man-pages-1.58.tar.bz2: Permission denied > mirror: Access failed: 550 openvpn-1.4.2.tar.gz: Permission denied > > I fixed them. I hate when that happens.... Sorry! Heiko |
|
From: Heiko Z. <he...@zu...> - 2003-07-28 23:10:24
|
Bruce Smith wrote: > While you're changing linuxrc, I wonder if it'd be a good idea to > recreate /etc/Devil-release & /etc/issue & /etc/issue.net _after_ /etc > is untar'ed from media? > > Otherwise they are wrong after updating to a new CD and using an old > floppy. > Good idea ! Go ahead and do it. Heiko |
|
From: Bruce S. <bw...@ar...> - 2003-07-28 22:50:47
|
While you're changing linuxrc, I wonder if it'd be a good idea to recreate /etc/Devil-release & /etc/issue & /etc/issue.net _after_ /etc is untar'ed from media? Otherwise they are wrong after updating to a new CD and using an old floppy. - BS |
|
From: Bruce S. <bw...@ar...> - 2003-07-28 22:47:41
|
> >executing busybox with option build > >make[1]: Entering directory `/data/build' > >make[1]: *** No rule to make target `oldconfig'. Stop. > >make[1]: Leaving directory `/data/build' > >ERROR > >/data/build/scripts/busybox build failed > >make: *** [build] Error 1 > > Did you update the sources from the FTP server? Yup. I just did it again, and paid attention this time: :-) mirror: Access failed: 550 busybox-1.00-pre1.tar.bz2: Permission denied Not to mention: mirror: Access failed: 550 man-pages-1.58.tar.bz2: Permission denied mirror: Access failed: 550 openvpn-1.4.2.tar.gz: Permission denied I fixed them. - BS |
|
From: Heiko Z. <hz...@pr...> - 2003-07-28 21:54:29
|
On 07/28/2003 05:31:43 PM Bruce Smith wrote: >... >make[1]: Leaving directory `/data/build/tmp/rpm-4.0.4' >removing debug symbols from binaries > >executing busybox with option build >make[1]: Entering directory `/data/build' >make[1]: *** No rule to make target `oldconfig'. Stop. >make[1]: Leaving directory `/data/build' >ERROR >/data/build/scripts/busybox build failed >make: *** [build] Error 1 Did you update the sources from the FTP server? cya Heiko = |
|
From: Bruce S. <bw...@ar...> - 2003-07-28 21:31:56
|
...
make[1]: Leaving directory `/data/build/tmp/rpm-4.0.4'
removing debug symbols from binaries
executing busybox with option build
make[1]: Entering directory `/data/build'
make[1]: *** No rule to make target `oldconfig'. Stop.
make[1]: Leaving directory `/data/build'
ERROR
/data/build/scripts/busybox build failed
make: *** [build] Error 1
|
|
From: Heiko Z. <hz...@pr...> - 2003-07-28 18:46:50
|
On 07/28/2003 02:14:52 PM Bruce Smith wrote: >> >>Doesn't initrd use all the utilities from busybox now? >> >>If so, does busybox support uclibc? >> > >> >Oh yes it does. I'll give it shot. >> > >> >We currently use ext2 for our shmfs, if we switch to minix we save = at >> >least another 1 MB. Any complains? > >Yes, minix has a filename size limit of 14 or 30 characters >(depending on format options). > >This will break applications that use longer filenames. OK, bye bye minix idea. ;-) >> >I actually never used minix before, but I expect that it supports t= he >> >"normal" file ownerships and permissions. >> >> Shit! I forgot that our shmfs can get quite big, i.e. when you use >chroot >> jails. > >Yes, Minux has a 64MB partition size limitation. >That could be a problem. :-) > >Would using ReiserFS save any memory over ext2? I doubt it. The problem is that we need to have the correct mkfs.xxxx tool in our initrd. I'll check tonight how big the static binary is. Heiko = |
|
From: Bruce S. <bw...@ar...> - 2003-07-28 18:15:06
|
> >>Doesn't initrd use all the utilities from busybox now? > >>If so, does busybox support uclibc? > > > >Oh yes it does. I'll give it shot. > > > >We currently use ext2 for our shmfs, if we switch to minix we save at > >least another 1 MB. Any complains? Yes, minix has a filename size limit of 14 or 30 characters (depending on format options). This will break applications that use longer filenames. > >I actually never used minix before, but I expect that it supports the > >"normal" file ownerships and permissions. > > Shit! I forgot that our shmfs can get quite big, i.e. when you use chroot > jails. Yes, Minux has a 64MB partition size limitation. That could be a problem. :-) Would using ReiserFS save any memory over ext2? - BS |
|
From: Heiko Z. <hz...@pr...> - 2003-07-28 17:55:25
|
On 07/28/2003 01:47:53 PM "Heiko Zuerker" wrote: >On 07/28/2003 01:40:47 PM Bruce Smith wrote: >>Doesn't initrd use all the utilities from busybox now? >>If so, does busybox support uclibc? > >Oh yes it does. I'll give it shot. > >We currently use ext2 for our shmfs, if we switch to minix we save at >least >another 1 MB. Any complains? >I actually never used minix before, but I expect that it supports the >"normal" file ownerships and permissions. Shit! I forgott that our shmfs can get quite big, i.e. when you use chr= oot jails. Heiko = |
|
From: Heiko Z. <hz...@pr...> - 2003-07-28 17:48:59
|
On 07/28/2003 01:40:47 PM Bruce Smith wrote: >> >>I just did a few more changes (already in CVS) and checked the >memory usage. >> >>You can boot now with only 22 MB of RAM. >> > >> > Wow!!! >> >> Just saw that I lied, I used 24 MB. >> VMWare doesn't let you select 22MB. > >Still, that's very good. > >Most old PC's I've seen (that are still usable as a firewall) >have either 32MB or 16MB, so 16MB would be a good goal. >If we don't get there, 32MB is still great! > >> > What's the pro's & con's of using uclibc in initrd? >> It is much smaller then glibc but doesn't have all functionality. >> It should certainly be enough to get through the initrd. >> >> > Is anything stuck using it after boot? >> >> Should not. > >Sounds like it'd be worth a try. I think so, too. >Doesn't initrd use all the utilities from busybox now? >If so, does busybox support uclibc? Oh yes it does. I'll give it shot. We currently use ext2 for our shmfs, if we switch to minix we save at l= east another 1 MB. Any complains? I actually never used minix before, but I expect that it supports the "normal" file ownerships and permissions. cya Heiko = |
|
From: Bruce S. <bw...@ar...> - 2003-07-28 17:41:00
|
> >>I just did a few more changes (already in CVS) and checked the memory usage. > >>You can boot now with only 22 MB of RAM. > > > > Wow!!! > > Just saw that I lied, I used 24 MB. > VMWare doesn't let you select 22MB. Still, that's very good. Most old PC's I've seen (that are still usable as a firewall) have either 32MB or 16MB, so 16MB would be a good goal. If we don't get there, 32MB is still great! > > What's the pro's & con's of using uclibc in initrd? > It is much smaller then glibc but doesn't have all functionality. > It should certainly be enough to get through the initrd. > > > Is anything stuck using it after boot? > > Should not. Sounds like it'd be worth a try. Doesn't initrd use all the utilities from busybox now? If so, does busybox support uclibc? - BS |
|
From: Heiko Z. <he...@zu...> - 2003-07-28 16:10:23
|
Bruce Smith wrote: >>>What's the current status of the CD only version now? >>>I haven't updated for a couple days .... >> >>It's ready to play around. >>There are some minor bugs left, which have to be fixed. > > > Do I need to mrproper? Or can I just rebuild an ISO after make clean? > (I haven't updated since mid-last-week) Yes you need a "make mrproper". I did also some changes to the Kernel config. Heiko |
|
From: Heiko Z. <he...@zu...> - 2003-07-28 16:10:23
|
Bruce Smith wrote: >>I just did a few more changes (already in CVS) and checked the memory usage. >>You can boot now with only 22 MB of RAM. > > Wow!!! Just saw that I lied, I used 24 MB. VMWare doesn't let you select 22MB. >>I'm almost certain we can bring that down to 16 MB, when we use uclibc >>and static binaries within the Initrd. >>The only question is if we want to do this. > > > I don't know anything about uclibc. > > What's the pro's & con's of using uclibc in initrd? It is much smaller then glibc but doesn't have all functionality. It should certainly be enough to get through the initrd. > Is anything stuck using it after boot? Should not. cya Heiko |
|
From: Bruce S. <bw...@ar...> - 2003-07-28 15:55:09
|
> > What's the current status of the CD only version now? > > I haven't updated for a couple days .... > > It's ready to play around. > There are some minor bugs left, which have to be fixed. Do I need to mrproper? Or can I just rebuild an ISO after make clean? (I haven't updated since mid-last-week) - BS |
|
From: Bruce S. <bw...@ar...> - 2003-07-28 15:49:45
|
> I just did a few more changes (already in CVS) and checked the memory usage. > You can boot now with only 22 MB of RAM. Wow!!! > I'm almost certain we can bring that down to 16 MB, when we use uclibc > and static binaries within the Initrd. > The only question is if we want to do this. I don't know anything about uclibc. What's the pro's & con's of using uclibc in initrd? Is anything stuck using it after boot? - BS |
|
From: Dean N. <di...@ti...> - 2003-07-28 15:29:39
|
Heiko Zuerker wrote: >Dean Nedelman wrote: >> (From the 7/17 snapshot...) > >Freakin' snapshot... >Please suspend all testing with this version, I'll release soon another >testing version which should work better. > When you get the new one out, I'll go ahead and download it. Right now, with the exception of these errors and the shutdown error (which you have already acknowledged and Bruce has indicated is fixed in the CVS) - it is working for me. >> 95% of the time, when I boot I get the following errors while it is trying >> to create my Postfix chroot jail - though I do not believe it is Postfix >> related. The errors (and the few lines before and after it) are: >> >> Starting hotplug modules >> ** can't synthesize pci hotplug events >> creating chroot jail for POSTFIX.grsec: attempted resource overstep by >> requesting 4096 for RLIMIT_CORE against limit 0 by (basename:1131) UID(0) >> EUID(0), parent (usb.agent:1061) UID(0) EUID(0) >> grsec: attempted resource overstep by requesting 4096 for RLIMIT_CORE >> against limit 0 by (logger:1132) UID(0) EUID(0), parent (usb.agent:1061) >> UID(0) EUID(0) >> ...................... [OK] >> Starting Postfix: [OK] >> Setting GRSecurity parameters: [OK] >> >> >> >> So, the problem appears to be USB related. I have not modified any >> GRSecurity settings. > >I don't get this messages. Do you have any USB devices connected? Which >ones? I have no USB devices attached (though the way things are going I am considering getting some flash devices to store devil-linux on the next time I am working). If it means anything, my USB controller shows up as "usb-uhci". (I know that there are 3 different types of usb controllers under Linux 2.4. [This gets reduced to a single common code in 2.6]) I also see in my syslog from around that time the message: usb.agent: ... no modules for USB product 0/0/0 Dean |
35 messages has been excluded from this view by a project administrator.
