Re: CVS commit: src/usr.sbin/sysinst
On Tue, Aug 12, 2014 at 10:39:05PM +0100, David Laight wrote: > Is that really the best order? > Wouldn't it be more useful to look in . first? Yes, probably. Martin
Re: CVS commit: src
david@ wrote: > > Note sysinst(8) requires some spare space in /tmp during installation, > > especially on using non-default settings on choosing installation sets etc. > > on ports which don't use tmpfs or mfs during installation. > > (100KB would be enough for this newsmips case though) > > It is also useful if there is enough space for sysinst to drop core. I don't think it's so worth in the real world. > Unless the system has very limited memory (in which case it really won't > run much) then adding a meg or two to the ramdisk size probably doen't > matter. - no automated method to calculate necessary size to maintain the numbers - few user will report problems using core (it isn't trivial to copy core on ramdisk into other working machines) - developers usually use /usr/sbin/sysinst binary rather than actual install kernels with crunchgen + makefs + mdsetimage + reboot (gdb requires target binary and crunched binary is annoying) - x86 ports already have USB install images without ramdisk and they are also useful enough for debug --- Izumi Tsutsui
Re: CVS commit: src
On Mon, Aug 11, 2014 at 05:25:29AM +0900, Izumi Tsutsui wrote: > riz@ wrote: > > > Module Name:src > > Committed By: riz > > Date: Sun Aug 10 20:04:30 UTC 2014 > > > > Modified Files: > > src/distrib/newsmips/floppies/ramdisk: Makefile > > src/sys/arch/newsmips/conf: INSTALL > > > > Log Message: > > Bump the ramdisk size; the longer paths on the build cluster are > > likely enough to put this over the edge. > > > > > > To generate a diff of this commit: > > cvs rdiff -u -r1.31 -r1.32 src/distrib/newsmips/floppies/ramdisk/Makefile > > >> -IMAGESIZE= 2560k > >> +IMAGESIZE= 2660k > > Note sysinst(8) requires some spare space in /tmp during installation, > especially on using non-default settings on choosing installation sets etc. > on ports which don't use tmpfs or mfs during installation. > (100KB would be enough for this newsmips case though) It is also useful if there is enough space for sysinst to drop core. Unless the system has very limited memory (in which case it really won't run much) then adding a meg or two to the ramdisk size probably doen't matter. IIRC it is compressed in the install media. David -- David Laight: da...@l8s.co.uk
Re: CVS commit: src/usr.sbin/sysinst
On Wed, Aug 06, 2014 at 09:11:47AM +, Martin Husemann wrote: > Module Name: src > Committed By: martin > Date: Wed Aug 6 09:11:46 UTC 2014 > > Modified Files: > src/usr.sbin/sysinst: main.c > > Log Message: > Make sysinst use the catalog files installed in /usr/share/sysinst (if > available), fall back to . if not, or use build-in english otherwise. Is that really the best order? Wouldn't it be more useful to look in . first? David -- David Laight: da...@l8s.co.uk
Re: CVS commit: src/sys/fs/msdosfs
On Sun, Jul 13, 2014 at 04:34:59PM +0200, Martin Husemann wrote: > On Sun, Jul 13, 2014 at 04:31:58PM +0200, Martin Husemann wrote: > > Why does lsof define _KERNEL ? > > Let me rephrase: we provide the userland important stuff when either _KERNEL > or MAKEFS is defined - maybe MAKEFS should be renamed and lsof could use the > new define instead of _KERNEL. > > MSDOSFS_MOUNT_USERLAND_DEFS or something. or _KMEM_USER ? David -- David Laight: da...@l8s.co.uk
