Re: non-installable binaries in main (was Re: busybox_0.45-1_i386.changes REJECTED)
Alvaro wrote: > Where can I take a look at the new installer being developed, or is it just > an idea yet? It's only an idea at this point. It'll be developed on debian-boot. -- see shy jo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#66772: base: du produces wacked out results
reassign 66772 fileutils thanks In reference to a message from [EMAIL PROTECTED], dated Jul 05: > Package: base > Version: N/A > > I don't know if this can be reproduced on a system other than mine or what, > but here's some output I just got from du: > > connubialis$ du -hsc * > -1015078787.0 total yes, this is a known bug in the du binary in slink. It's fixed in potato. randolph -- Debian Developer <[EMAIL PROTECTED]> http://www.TauSq.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: not i18ned part in b-f 2.2.15
On Wed Jul 05, 2000 at 06:51:40PM -0400, Adam Di Carlo wrote: > > > If our bf-utf8 will be completed, we may need to change this > > in order to invoke the bterm and run the dpkg-reconfigure on that. > > Now with this issue added on top, I almost wonder if we shouldn't have > init invoke a wrapper which sets the lang stuff, takes care of the > bterm or whatever other console stuff, and then runs dpkg-reconfigure > ? I think this is the right approach. Then it is a matter of changing just one script... -Erik -- Erik B. Andersen Web:http://www.xmission.com/~andersen/ email: [EMAIL PROTECTED] --This message was written using 73% post-consumer electrons-- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#64500: CALL FOR HELP : debian boot floppies 2.2.15 on apus still not ok.
Sven LUTHER <[EMAIL PROTECTED]> writes: > i give the corrct place in the requester, and dbootstrap tries to loop mount > the rescue.bin image to fetch the kernel and the modules, and fail. > > I then tried testing by hand, with : > > $ mount -r -t vfat -o loop=/dev/loop0 resceu.bin /mnt > Mounting rescue.bin on /mnt failed : block device required > > well, i think i found the cause of this error, ... > > Now the strange thing, is that when i continue the installation stuff and > reboot with the same kernel on the partition just installed from the base > tarball, i can mount the rescue.bin image with the exact command given above. > > Thus i suspsect the problem lie with the root.bin image. or maybe the > dbootstrap mount command. > > I have tested to see if loop device is modular or not, (i built the kernel > with loops included) and got : > > $ grep loop /proc/ksyms > c016a084 loops_per_ser > c0161278 loopback_dev > c00aeeac loop_register_transfer > c00aeee4 loop_unregister_transfer > > this should be ok, since i get the same symbols on my i386 2.3.99-pre8 kernel > here at work. > > also i did test the loop0 device : > > from the root.bin image : > > $ ls -l /dev/loop0 > brw-r--r--r 1 root root 7, 0 Jun 6 21:50 /dev/loop0 > > (didn't change when i chmoded it to be 666 either :((() > > from the base installed system : > > $ ls -l /dev/loop0 > > brw-rw 1 root disk ... > > Any idea of what is going wrong here ? Sounds like busybox mount bug, yeah. Wonder why it only hits apus?? Did you ever get confirmation? Do you think you can pester andersee directly? -- .Adam Di [EMAIL PROTECTED]http://www.onShore.com/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: not i18ned part in b-f 2.2.15
Taketoshi Sano <[EMAIL PROTECTED]> writes: > In <[EMAIL PROTECTED]>, > at "Tue, 4 Jul 2000 22:59:14 +0900", > with "not i18ned part in b-f 2.2.15", > Akira YOSHIYAMA <[EMAIL PROTECTED]> writes: > > > I found that installed fresh base system (dbootstrap > > installed it and just rebooted) isn't i18ned because of > > dpkg-reconfigure and init. > > In the current b-f, boot-config and dpkg-reconfigure > > have basic system configurations of fresh Debian. > > boot-config and dpkg-reconfigure (debconf) > > are i18ned, but init runs dpkg-reconfigure directly > > in the case. So no one set envronment variables > > (include LANG,LC_MESSAGES, and LC_ALL) > > normally set by shells and dpkg-reconfigure show us > > only english messages. Do you wish this? Ew -- all that work > The current source for this is in > scripts/rootdisk/prototype/etc/inittab.install > > and this has > > 1:2345:respawn:/usr/sbin/dpkg-reconfigure base-config /dev/tty1 2>& > > So dpkg-reconfigure is invoked by init with this line in /etc/inittab > on the fresh installed base system. Hmm... this is probably run by a shell, so, as a hack, couldn't we do 1:2345:respawn:LANG=whatever LC_*=whatever /usr/sbin/dpkg-reconfigure base-config ... ? > If our bf-utf8 will be completed, we may need to change this > in order to invoke the bterm and run the dpkg-reconfigure on that. Now with this issue added on top, I almost wonder if we shouldn't have init invoke a wrapper which sets the lang stuff, takes care of the bterm or whatever other console stuff, and then runs dpkg-reconfigure ? > So if we can use some shell script (or else) here, and write > the required process (setting appropriate variables, and invoke > the dpkg-reconfigure and base-config, or so) in it, then it will > make it easy for us to adopt the bf-utf8 some day. > > How do you think ? Sounds good. Volunteering? -- .Adam Di [EMAIL PROTECTED]http://www.onShore.com/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#66772: base: du produces wacked out results
Package: base Version: N/A I don't know if this can be reproduced on a system other than mine or what, but here's some output I just got from du: connubialis$ du -hsc * 645MCD-Phish1 614MCD-Phish2 631MCD-Phish3 624MCD-Phish4 613MCD-Phish5 -1015078787.0 total du -bsc * 676220900 CD-Phish1 644081017 CD-Phish2 662102103 CD-Phish3 654439770 CD-Phish4 643044719 CD-Phish5 -1015078787 total du -bsc CD-Phish[1-4] 676220900 CD-Phish1 644081017 CD-Phish2 662102103 CD-Phish3 654439770 CD-Phish4 -1658123506 total -- System Information Debian Release: 2.1 Kernel Version: Linux connubialis 2.2.12 #4 Wed Sep 1 16:28:51 PDT 1999 i586 unknown -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: kernel 2.2.17 boot disk prob!
Sven Burgener <[EMAIL PROTECTED]> writes: > Forgive me for sending this mail in a cross-posting fashion, but I > really need some help here. This is what I posted previously to > debian-user: > > Thanks in advance for any replies! Well, you could check whether the rescue disk works and thereby confirm whether it's a partitioning or lilo problem vs a kernel problem. You didn't include partition information. -- .Adam Di [EMAIL PROTECTED]http://www.onShore.com/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Test Cycle Three Update
Boot floppies 2.2.16, source and i386 was uploaded to samosa a few hours ago. People are actively compiling m68k and alpha right now. I'm sure powerpc and sparc will follow shortly (dunno about arm). This should be release candidate. I mean, I know there will be more bugs and documentation is a bit stale still, but we can handle that in a point release or whatever. -- .Adam Di [EMAIL PROTECTED]http://www.onShore.com/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#66654: marked as done (/dev/cdrom doesn't exist after an installation)
Your message dated 05 Jul 2000 16:04:27 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#66654: /dev/cdrom doesn't exist after an installation has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Darren Benham (administrator, Debian Bugs database) -- Received: (at submit) by bugs.debian.org; 3 Jul 2000 13:35:06 + >From [EMAIL PROTECTED] Mon Jul 03 08:35:05 2000 Return-path: <[EMAIL PROTECTED]> Received: from cs11.catv.ne.jp [202.232.171.4] by master.debian.org with esmtp (Exim 3.12 2 (Debian)) id 1396NL-0004F5-00; Mon, 03 Jul 2000 08:35:04 -0500 Received: from localhost by cs11.catv.ne.jp (8.9.1/3.7W) id WAA02667; Mon, 3 Jul 2000 22:33:45 +0900 (JST) From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: /dev/cdrom doesn't exist after an installation X-Mailer: Mew version 1.94.2 on Emacs 20.7 / Mule 4.0 (HANANOEN) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <[EMAIL PROTECTED]> Date: Mon, 03 Jul 2000 22:34:43 +0900 X-Dispatcher: imput version 2228(IM140) Lines: 10 Delivered-To: [EMAIL PROTECTED] Package: boot-floppies Version: 2.2.15-2000-06-07 Severity: wishlist /etc/fstab contains /dev/cdrom line, but I can't find /dev/cdrom file after a normal installation. I had to creata a symbolic file by myself. I wish the installer did it. -Inoue<[EMAIL PROTECTED]> --- Received: (at 66654-done) by bugs.debian.org; 5 Jul 2000 20:03:35 + >From [EMAIL PROTECTED] Wed Jul 05 15:03:35 2000 Return-path: <[EMAIL PROTECTED]> Received: from relay03.netaddress.usa.net [204.68.24.183] by master.debian.org with smtp (Exim 3.12 2 (Debian)) id 139vOR-0007mz-00; Wed, 05 Jul 2000 15:03:35 -0500 Received: (qmail 19109 invoked from network); 5 Jul 2000 20:03:02 - Received: from dsl-234-232-186-216.cust.dslnetworks.net (HELO arroz.fake) ([EMAIL PROTECTED]) by relay03.netaddress.usa.net with SMTP; 5 Jul 2000 20:03:02 - Received: by arroz.fake (Postfix, from userid 421) id D002E93802; Wed, 5 Jul 2000 16:04:27 -0400 (EDT) Sender: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Re: Bug#66654: /dev/cdrom doesn't exist after an installation References: <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> From: Adam Di Carlo <[EMAIL PROTECTED]> Date: 05 Jul 2000 16:04:27 -0400 In-Reply-To: [EMAIL PROTECTED]'s message of "Thu, 06 Jul 2000 02:05:30 +0900" Message-ID: <[EMAIL PROTECTED]> Lines: 30 User-Agent: Gnus/5.0803 (Gnus v5.8.3) Emacs/20.7 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Delivered-To: [EMAIL PROTECTED] [EMAIL PROTECTED] writes: > Really? > I think my CD-ROM is common. > > inoue@hako$ dmesg|grep hdc > ide1: BM-DMA at 0xcb08-0xcb0f, BIOS settings: hdc:DMA, hdd:pio > hdc: CRD-8400B, ATAPI CDROM drive > hdc: ATAPI 40X CD-ROM drive, 128kB Cache Indeed, it's a pretty standard ATAPI CD-ROM. > Needless to say, I can use /dev/hdc. > FYI, I didn't use a CD-ROM (I mean, CD-ROM media) during > installation. Yes -- dbootstrap should be making code for symlinking /dev/hdc -> /dev/cdrom, but (IIRC) that code is only activated if you actually install via CD-ROM. Kinda wierd but that's the way it works. You can understand why I think. Closing this bug, since the boot-floppies is for *installation* only -- it's purpose is not to configure all the hardware, nor is it feasible for boot-floppies to accomplish this goal. -- .Adam Di [EMAIL PROTECTED]http://www.onShore.com/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#66654: dev/cdrom doesn't exist after an installation
> > /etc/fstab contains /dev/cdrom line, > > but I can't find /dev/cdrom file after a normal installation. > > I had to creata a symbolic file by myself. > > I wish the installer did it. > > I believe the installer does do it when it can determine what a likely > CD-ROM device is. > > What sort of CD-ROM do you have? > Really? I think my CD-ROM is common. inoue@hako$ dmesg|grep hdc ide1: BM-DMA at 0xcb08-0xcb0f, BIOS settings: hdc:DMA, hdd:pio hdc: CRD-8400B, ATAPI CDROM drive hdc: ATAPI 40X CD-ROM drive, 128kB Cache Needless to say, I can use /dev/hdc. FYI, I didn't use a CD-ROM (I mean, CD-ROM media) during installation. Thanks. -Inoue <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: CALL FOR HELP : debian boot floppies 2.2.15 on apus still not ok.
Sven LUTHER wrote: > > BTW what's the fs type of root.bin supposed to be? I can't mount it here. > > root.bin is just a compressed ext2 root image. > > dbootstrap does some gunzip & piping magic to mount it, but mv root.bin > root.bin.gz && gunzip root.bin.gz will do also. Aaah it worked now, thanks. > Do you have the same problem as me with the mounting of the rescue.bin image > (it is a vfat image) ? I can only test it on the i386 SuSE 6.4 here at work, and it mounts without problems. Michel -- It's not a bug, it's tradition! __ Earthling Michel Dänzer (MrCooper) \ CS student and free software enthusiast Debian GNU/Linux (powerpc,i386) user \ member of XFree86, Team *AMIGA*, AUGS -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
possible to unify some m68k docs ?
Do you have time to merge this stuff (which is the same as in m68k-specials) into the main install manual? http://www.debian.org/~holgate/m68k-quick-install/sgml-source.tgz Most important stuff is the corrections. As I understand it, the above also includes some "quickstart" stuff which sounds really nice and all arches should have, but you could add that as condition to m68k only for now. Thoughts? -- .Adam Di [EMAIL PROTECTED]http://www.onShore.com/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: CALL FOR HELP : debian boot floppies 2.2.15 on apus still not ok.
On Wed, Jul 05, 2000 at 02:53:48PM +0200, Michel Dänzer wrote: > Sven LUTHER wrote: > > > i give the corrct place in the requester, and dbootstrap tries to loop mount > > the rescue.bin image to fetch the kernel and the modules, and fail. > > Should drivers.tgz be in rescue.bin? It's not. No it is supposed to be in driver-1.bin. > If the config.gz in rescue.bin is the config of the kernel you use, it does > indeed include the loopback device and vfat. thought so also, ... > > Now the strange thing, is that when i continue the installation stuff and > > reboot with the same kernel on the partition just installed from the base > > tarball, i can mount the rescue.bin image with the exact command given > > above. > > > > Thus i suspsect the problem lie with the root.bin image. or maybe the > > dbootstrap mount command. > > That's a strong indication. BTW what's the fs type of root.bin supposed to be? > I can't mount it here. root.bin is just a compressed ext2 root image. dbootstrap does some gunzip & piping magic to mount it, but mv root.bin root.bin.gz && gunzip root.bin.gz will do also. Do you have the same problem as me with the mounting of the rescue.bin image (it is a vfat image) ? Friendly, Sven LUTHER -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#66030: tries to read past end of driver-3.bin
It's not as easy to fix as I thought. There is a program, floppy_split, that does this and it's written in C -- I dunno, maybe someone who is more of an expert could look at this? -- .Adam Di [EMAIL PROTECTED]http://www.onShore.com/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#66654: dev/cdrom doesn't exist after an installation
[EMAIL PROTECTED] writes: > /etc/fstab contains /dev/cdrom line, > but I can't find /dev/cdrom file after a normal installation. > I had to creata a symbolic file by myself. > I wish the installer did it. I believe the installer does do it when it can determine what a likely CD-ROM device is. What sort of CD-ROM do you have? -- .Adam Di [EMAIL PROTECTED]http://www.onShore.com/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: localized bf for potato release?
"J.A. Bezemer" <[EMAIL PROTECTED]> writes: > Cc:'d to -cd to increase awareness: if the disks-*/ size changes, the CD > creation scripts must be adjusted. (At least, AFAIK there is no autodetection > feature yet). Ah, thanks for pointing that out. Maybe a totally independant area, dists/potato/main/disks-i386/ru/current would be better and won't cause any suprises for cd folks or whatever. This seems worse for the user though since they won't really know to look there. > Do you have any idea how much extra images we're talking about? Per arch? Root and rescue per language. this is going to vary based on what flavors for i386 are used. At worst, that is 2 disks * 1.44 MB * 16 languages * 4 flavors == 184.32 MB. That's for one arch. This is a very severe pain in the ass, make no mistake. We have a language chooser system which seems to support quite a lot of languages (not all!) but it is not very well tested yet? (I still think we should supply it anyway). > And maybe an idea: since the l10'd floppy series are >90% the same, > we could possibly think of some "binary patching to the desired > language" scheme. I'll leave further exploration of options to > people with more time ;-) Good idea, and it really is pretty feasible (the only variance on the rescue disk for instance -- .Adam Di [EMAIL PROTECTED]http://www.onShore.com/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
2.2.16 tagged
2.2.16 is tagged. We are building it now. Sorry for the delay but I wanted to be reasonably confident this really was a full release candidate. -- .Adam Di [EMAIL PROTECTED]http://www.onShore.com/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: boot-floppies bug cleanup
If your closing bugs I would rather you would just email to [EMAIL PROTECTED] rather than slapping the severity to fixed. Thus the submitter gets a message. -- .Adam Di [EMAIL PROTECTED]http://www.onShore.com/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: CALL FOR HELP : debian boot floppies 2.2.15 on apus still not ok.
Sven LUTHER wrote: > i give the corrct place in the requester, and dbootstrap tries to loop mount > the rescue.bin image to fetch the kernel and the modules, and fail. Should drivers.tgz be in rescue.bin? It's not. If the config.gz in rescue.bin is the config of the kernel you use, it does indeed include the loopback device and vfat. > Now the strange thing, is that when i continue the installation stuff and > reboot with the same kernel on the partition just installed from the base > tarball, i can mount the rescue.bin image with the exact command given > above. > > Thus i suspsect the problem lie with the root.bin image. or maybe the > dbootstrap mount command. That's a strong indication. BTW what's the fs type of root.bin supposed to be? I can't mount it here. Michel -- Apologies are so hard to give. Would you accept some potatoes instead? __ Earthling Michel Dänzer (MrCooper) \ CS student and free software enthusiast Debian GNU/Linux (powerpc,i386) user \ member of XFree86, Team *AMIGA*, AUGS -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: not i18ned part in b-f 2.2.15
Hi. (Akira is the main hacker for ja version of boot-floppies in JP packages, i.e. bo-jp, hamm-jp, slink-jp. And he is one of main hackers in locale development for ja on glibc2.) In <[EMAIL PROTECTED]>, at "Tue, 4 Jul 2000 22:59:14 +0900", with "not i18ned part in b-f 2.2.15", Akira YOSHIYAMA <[EMAIL PROTECTED]> writes: > I found that installed fresh base system (dbootstrap > installed it and just rebooted) isn't i18ned because of > dpkg-reconfigure and init. > In the current b-f, boot-config and dpkg-reconfigure > have basic system configurations of fresh Debian. > boot-config and dpkg-reconfigure (debconf) > are i18ned, but init runs dpkg-reconfigure directly > in the case. So no one set envronment variables > (include LANG,LC_MESSAGES, and LC_ALL) > normally set by shells and dpkg-reconfigure show us > only english messages. Do you wish this? The current source for this is in scripts/rootdisk/prototype/etc/inittab.install and this has 1:2345:respawn:/usr/sbin/dpkg-reconfigure base-config /dev/tty1 2>& So dpkg-reconfigure is invoked by init with this line in /etc/inittab on the fresh installed base system. If our bf-utf8 will be completed, we may need to change this in order to invoke the bterm and run the dpkg-reconfigure on that. So if we can use some shell script (or else) here, and write the required process (setting appropriate variables, and invoke the dpkg-reconfigure and base-config, or so) in it, then it will make it easy for us to adopt the bf-utf8 some day. How do you think ? -- Taketoshi Sano: <[EMAIL PROTECTED]>,<[EMAIL PROTECTED]>,<[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
CALL FOR HELP : debian boot floppies 2.2.15 on apus still not ok.
Hello, ... This is a call for help, i am totally lost here, and if nobody helps me out on this, i am afraid the apus boot floppies will chip as is, without working properly. This is not so big a deal, because it is possible to do a full install in the current state of things, but still it would be nicer if this was fixed before the potato release, ... this morning i did try 2.2.15, and the problem still is there. The problem (already described in bug 64500, 43 days old as of today) is the following. Everything works fine, but when i come to the step where i would normally do : * install os kernel & modules i give the corrct place in the requester, and dbootstrap tries to loop mount the rescue.bin image to fetch the kernel and the modules, and fail. I then tried testing by hand, with : $ mount -r -t vfat -o loop=/dev/loop0 resceu.bin /mnt Mounting rescue.bin on /mnt failed : block device required well, i think i found the cause of this error, ... Now the strange thing, is that when i continue the installation stuff and reboot with the same kernel on the partition just installed from the base tarball, i can mount the rescue.bin image with the exact command given above. Thus i suspsect the problem lie with the root.bin image. or maybe the dbootstrap mount command. I have tested to see if loop device is modular or not, (i built the kernel with loops included) and got : $ grep loop /proc/ksyms c016a084 loops_per_ser c0161278 loopback_dev c00aeeac loop_register_transfer c00aeee4 loop_unregister_transfer this should be ok, since i get the same symbols on my i386 2.3.99-pre8 kernel here at work. also i did test the loop0 device : from the root.bin image : $ ls -l /dev/loop0 brw-r--r--r 1 root root 7, 0 Jun 6 21:50 /dev/loop0 (didn't change when i chmoded it to be 666 either :((() from the base installed system : $ ls -l /dev/loop0 brw-rw 1 root disk ... Any idea of what is going wrong here ? Anything else i could test here ? In particular i would like other apus user to test this (with various kernels) and report to me about it. It can be tested in an non partition damaging way by : 1) booting with the latest debian root.bin image as ramdisk. 2) respond only to the keyboard question once it has booted. 3) switch to console 2 4) type enter to get a prompt 5) try : $ mount -r -t vfat -o loop=/dev/loop0 resceu.bin /mnt And see if it can be mounted ... Not so difficult isn't it, but if nobody can be worried to confirm on this, i guess it is not worth for me to waste my time on this, isn't it, anyway, _I_ can install debian without problem with the current boot floppies, ... Friendly, Svne LUTHER -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
