On Wed, Dec 19, 2001 at 03:32:51PM -0500, Mark Horn wrote:
> 1) Is this the correct forum to identify this kind of problem? If not, can
>you kindly direct me where I should go?
Seems logical to me.
> 2) Did I do something wrong during initial setup that prevented creating
>a functioning
Nice clear review, Jeff.
On Mon, Nov 26, 2001 at 03:30:40PM -0500, Jeff Sheinberg wrote:
> o The default lilo configuration makes it impossible to
> interactive with lilo at boot time. This is really a poor
> choice for the default. Instead, the default lilo
> configuration shou
On Fri, Oct 26, 2001 at 02:05:39PM +1300, Mark van Walraven wrote:
> Kindly review the change and let me know what you think.
I've done three full installs with the change and observed no additional
problems. Ok to commit it?
Thanks,
Mark.
--
To UNSUBSCRIBE, email to [EMAIL P
On Fri, Nov 16, 2001 at 02:44:53PM +1300, Mark van Walraven wrote:
> On Thu, Nov 15, 2001 at 03:51:55PM -0900, Ethan Benson wrote:
-
> > i have yet to see any proof of this.
>
> I don't believe you ever will see it.
I wish to apologise to Ethan and the list for my petula
On Thu, Nov 15, 2001 at 03:51:55PM -0900, Ethan Benson wrote:
> On Fri, Nov 16, 2001 at 01:41:52PM +1300, Mark van Walraven wrote:
> >
> > If I didn't have important reason to get the system up quickly, I'd just
> > work away in single-user mode. If /var/tmp is o
On Tue, Nov 13, 2001 at 03:06:38PM -0900, Ethan Benson wrote:
> your missing the point:
>
> > > > > what good will this do? the permissions of the mount point
> > > > > directory are irrelevant as they will be replaced by the
> > > > > permissions of the root directory of the mounted filesystem.
On Tue, Nov 13, 2001 at 08:03:43PM -0800, John H. Robinson, IV wrote:
> thus i submit: fix /tmp, or fix /var/tmp, so they both act the same way.
Single-user mode is severely crippled if /tmp is not world writeable.
So one option is not as good as the other.
> consitency is the path to least surp
On Tue, Nov 13, 2001 at 04:20:36AM -0900, Ethan Benson wrote:
> On Tue, Nov 13, 2001 at 12:02:18PM +0100, Kjetil Torgrim Homme wrote:
> > Ethan Benson <[EMAIL PROTECTED]> writes:
-
> > > what good will this do? the permissions of the mount point
> > > directory are irrelevant as they will be repl
Dear list,
partition_config::mount_partition() uses mode 01777 when creating /tmp
as a mount-point, but doesn't for /target/var/tmp. A fix is:
Index: boot-floppies/utilities/dbootstrap/partition_config.c
===
RCS file: /cvs/debian-b
On Mon, Nov 05, 2001 at 12:39:19AM +0100, Erik Tews wrote:
> I am currently a little bit experimentating with installing debian
> directly into lvm. Theory is not so difficult, and it works with a lot
> of handwork during the installation-process. One of the main problems is
I made some private m
Hi Erik,
I'm still preparing some documentation, but here's the rough procedure.
I'm sending a copy to debian-boot in case this is useful to anyone else.
Check the boot-floppies software out of the Debian CVS archive. See
http://cvs.debian.org/boot-floppies/README-CVS?rev=1.9&content-type=text/v
On Mon, Oct 29, 2001 at 04:02:23PM +0100, Eduard Bloch wrote:
> And how do you download without having the NIC driver? As said before,
> we have 2.4MB in NIC drivers. With the kernel a bit too much for one floppy.
Aggghh! Why do you ignore what was written earlier?
I wrote:
are compile
On Fri, Oct 26, 2001 at 11:12:58AM +0200, Eduard Bloch wrote:
> > I presume you mean the target root? It's already mounted by the time
> > the driver disks are installed. Of course, you can also download to a
> > Ramdisk.
>
> Yes, this driver should go into the kernel. But the source may be Cod
On Fri, Oct 26, 2001 at 12:12:17PM -0400, Adam Di Carlo wrote:
> I'm not moving to 2.4 for i386 boot-floppies, the kernels are too big,
> and it's too late to do that anyhow.
I'll take that as a positive sign that release is soon!
> Mark van Walraven <[EMAIL PROTECTE
Hi,
On Mon, Jan 01, 2001 at 06:55:19PM -0800, Osamu Aoki wrote:
> The mouse can be used by both in Linux console (gpm) and X window.
> Preferred configuration / signal flow shall be as follows.
>
> mouse => /dev/psaux => gpm => /dev/gpmdata -> /dev/mouse => X
This made sense when the psaux dr
On Thu, Oct 25, 2001 at 05:25:24PM -0700, David Kimdon wrote:
> > Or is there any way to build boot-floppies using 2.4.X kernels?
> In principle we should be able to do that. I've considered
> re-openning the 2.4/2.2 question myself, but I fear. We need to get
> woody out, no new features.
ISTR
Dear list,
If a filesystem is manually mounted on /target using the shell on tty2,
dbootstrap will detect it and suggest installing the kernel, but never
copies the network settings or creates the dbootstrap_settings file on
the target root.
This makes installing root on a MD, LVM, NBD or loop d
On Thu, Oct 25, 2001 at 11:31:03AM +0200, Eduard Bloch wrote:
> To "download", you first have to get root mounted. And the source, of
> course. This may be a NIC (any type!) or a harddisk with a filesystem.
I presume you mean the target root? It's already mounted by the time
the driver disks are
On Thu, Oct 25, 2001 at 10:00:24AM +0200, Eduard Bloch wrote:
> But you have probably right. Installing kernel-image along with other
> packages is a bad idea, IMHO, since it has many predepends.
> But when Woody stabilize, the kernel installation routine could be
> modified to get the package fro
On Thu, Oct 25, 2001 at 07:41:10AM +0200, Gerhard Tonn wrote:
> It works fine on s390, but where do I get the latest debootstrap from?
Look in http://incoming.debian.org/ .
Regards,
Mark.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL P
On Wed, Oct 24, 2001 at 03:04:36PM -0700, David Kimdon wrote:
> partition_config.c : If there is only one drive, assume that is the drive we
> want to partition. FIXME: do we like this?
I think I would definitely blink if zapped into cfdisk without having
explicitly selected the drive. Currentl
On Mon, Oct 22, 2001 at 06:20:13PM -0600, Erik Andersen wrote:
> I did indeed re-enable wc. But seriously though, if you know
> the file's name, couldn't you just stat(2)? Something like:
>
> struct stat statbuf;
> ...
> stat(filename, &statbuf);
> filesize = statbuf.st_size;
On Sat, Oct 20, 2001 at 04:23:05AM -0600, Erik Andersen wrote:
> Umm. What possible good would it do to parse dd output? Check the
> return code. or stat the output file if you are paranoid.
It was a way to determine file size in the absence of wc. But if you've
enabled wc in b-f busybox, the
On Sat, Oct 20, 2001 at 01:41:25AM -0800, Ethan Benson wrote:
> > > > BTW: does "ls --block-size=1 -s" look broken to you?
> > >
> > > busybox ls doesn't know what that is.
> >
> > Sorry, meant fileutils' ls. Bug?
>
> the ls you have available on boot-floppies is busybox, not fileutils.
Forge
On Sat, Oct 20, 2001 at 01:03:12AM -0800, Ethan Benson wrote:
> but parsing some basically informative verbosity output from a utility
> is a damned fragile kludge of a way to do something, what if the
> format of this output changes in the future?
Agree with the sentiment, but changing the outpu
On Fri, Oct 19, 2001 at 11:20:18PM -0800, Ethan Benson wrote:
> On Sat, Oct 20, 2001 at 06:34:12PM +1300, Mark van Walraven wrote:
> > Substitute "> FILE" for "touch FILE".
>
> that should already be done in the last patch or two that were NMUed,
On Sat, Oct 20, 2001 at 12:54:23PM +1000, Anthony Towns wrote:
> On Fri, Oct 19, 2001 at 06:46:32PM -0400, Joey Hess wrote:
> > Removed stuff:
> > /bin/touch
> > /usr/bin/head
> > /usr/bin/sort
> > /usr/bin/wc
>
> ...are all used by debootstrap.
Substitute "> FILE" for "touch FIL
On Fri, Oct 19, 2001 at 01:11:30AM -0400, Joey Hess wrote:
> We strip modules as much as is possible. I have never heard of stripping
> the kernel itself.
Stripping all symbols is highly likely to break the kernel. However, GCC
generates a .ident field in object files, which seems to be unnecess
On Thu, Oct 18, 2001 at 04:02:19AM -0800, Ethan Benson wrote:
> On Thu, Oct 18, 2001 at 06:59:40PM +1000, Glenn McGrath wrote:
> >
> > Problems should be reported upstream where apropriate, not to assign blame,
> > but so the upstream author knows about it and can fix it for all users of that
> >
On Thu, Oct 18, 2001 at 04:36:14PM +1300, Mark van Walraven wrote:
> BTW, I tend to agree with David about not changing the dbootstrap code
> at this stage. I have been adding a 'manual' option to mount_partition
Damn, sorry, hit 'y' (send) when I meant 'q'
On Wed, Oct 17, 2001 at 02:55:11PM -0800, Ethan Benson wrote:
>thank you for completly missing the point.
Ok, no need to be rude. I see I went down the wrong track. I'm sorry.
> i am not talking about libfdisk, i am talking about busybox.
>
> its mount -t auto design is fundementally flawed,
On Sun, May 13, 2001 at 03:30:56PM +1000, Robert Butler wrote:
> Problem is I can't press that "Continue" button, so have never gotten past
> this screen. No response to any keyboard or mouse commands from this screen,
> including Ctrl-alt-delete: I have to reboot via the reset button. Of course
>
Hi,
On Mon, Apr 02, 2001 at 05:52:02AM -0400, [EMAIL PROTECTED] wrote:
> without the floppy. It all went fine until it got to "Verifying DMI pool
> data", (normally it would then start win me), but then instead of giving me
> the choice of Linux/windows it just prints 01 01 01 01 01 01 continuo
On Fri, Mar 30, 2001 at 10:49:37PM +1000, Herbert Xu wrote:
> But why are you compiling cramfs in if you're using ext2 initrd images?
> The images I make can't handle ext2 images anyway since ext2 isn't compiled
> in.
Well, I took it from the kernel-source changelog and the description
in the mkc
On Wed, Mar 28, 2001 at 09:29:14PM +1000, Herbert Xu wrote:
> zhaoway <[EMAIL PROTECTED]> wrote:
>
> > Does anyone have this problem for kernel 2.4.1? When I compiled in
> > cramfs, initrd cannot work. Kernel message screen just say:
>
> > wrong magic <== spit out by cramfs(?) which shouldn't be
On Tue, Jul 18, 2000 at 08:39:01PM +0300, Jaakko Niemi wrote:
> I just tried to install potato on a machine with Mylex DAC960PG
> raid card and noticed that the DAC960 driver is a module.
> The module is unusable unless one has some other media where
> to install the modules and base syst
On Sat, Jul 01, 2000 at 07:32:18PM -0700, Randolph Chung wrote:
> 64823 incorrect LILO automatic placement on i386
>
> ISTR some discussions about why we don't allow what the bug submitter
> wanted, because it doesn't work in certain configurations or something.
> Mark, are you still around? Ma
37 matches
Mail list logo
