RE: I'm at a loss running Debian
About this kernel option, can someone provide me some details for nslu2-debian how to do that, and is it necessary, or is it enough to do the update-initramfs -u and after that the flash-kernel command ? I tried the /dev/disk/by-uuid/xxx thing, and together with that, i started with both drives (usb-stick & harddrive) attached, All went well till the reboot ... It just won't work with the external harddrive connected at boottime ... The difference is, that i can unplug it and reboot the nslu2 and afterwards re-attach it, in this manner, it boots up fine, but this can't be the right thing to keep doing in the future ... Maybe it was a bit too much in my first post, so i'm gonna ask it again specifically, does someone have experience in cloning a usb-flash stick with programs like ghost or acronis, and put such an image back ?? I tried it, and it doesn't work, although I can browse the contents of the ghost file perfectly ... Or is it maybe a problem with the .bin file that I flashed to the slug ?? I made such a .bin file with the cat /dev/mtdblock* > backup.bin command ... Although both things should be o.k., the slug won't boot up after flashing the .bin file back to the slug & the ghost file to the memory stick ! A quick question, I've put my swapfile on my external harddrive, but after 10 minutes of inactivity this drive goes into standby, will this give problems to the slug using the swapfile ? As there will be a short delay for the drive to boot-up ? And I don't wont to wear down my flashdrive, by repeatedly writing to it ... If this swapfile on the harddrive procedure won't work in my case, I guess there's nothing left than fatten the slug, isn't it ??? Kind regards, Bart -Oorspronkelijk bericht- Van: Lennart Sorensen [mailto:[EMAIL PROTECTED] Verzonden: maandag 13 augustus 2007 23:42 Aan: Bob CC: debian-arm@lists.debian.org Onderwerp: Re: I'm at a loss running Debian On Mon, Aug 13, 2007 at 09:56:29PM +0200, Bob wrote: > I must say, I'm not familiar with the LABEL=blah or UUID=xxx-xxx syntax. > Do you have an example of a fstab entry using these attributes? > I guess I could look it up on google, but it would be nice to have it in > this thread also... # /etc/fstab: static file system information. # # UUID=35963d32-f15e-497e-859a-ed1cb366b0f3 / ext3 defaults0 1 UUID=dcdceb9f-3a7c-43d8-80dc-0493d7c0fa88 /data4 ext3defaults 0 1 UUID=d79bc11c-461a-45a3-932b-f993777bef3e /data ext3defaults 0 1 etc... And in the boot loader (on i386) I have root=UUID=35963d32-f15e-497e-859a-ed1cb366b0f3 as a kernel option. -- Len Sorensen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#437742: libdb4.6: FTBFS on arm: in testsuite, run_subsystem: env env007: db open:invalid argument
Package: db Version: 4.6.18-1 Severity: serious http://buildd.debian.org/fetch.cgi?pkg=db;ver=4.6.18-4;arch=arm;stamp=1187033603 Modified test suite run started at: 09:02 08/13/07 Berkeley DB 4.6.18: (July 17, 2007) Running environment tests (09:02:08) Running archive tests (09:06:40) Running backup tests (09:12:27) Running locking tests (09:13:19) Running logging tests (09:28:18) Running memory pool tests (11:41:35) Running transaction tests (11:49:11) Running byte-order tests (11:57:39) Running recno backing file tests (19:31:15) Running DBM interface tests (19:31:25) Running NDBM interface tests (19:31:37) Running Hsearch interface tests (19:31:48) ! grep ^FAIL obj/ALL.OUT FAIL: run_subsystem: env env007: db open:invalid argument make: *** [build] Error 1 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: I'm at a loss running Debian
On Mon, Aug 13, 2007 at 09:56:29PM +0200, Bob wrote: > I must say, I'm not familiar with the LABEL=blah or UUID=xxx-xxx syntax. > Do you have an example of a fstab entry using these attributes? > I guess I could look it up on google, but it would be nice to have it in > this thread also... # /etc/fstab: static file system information. # # UUID=35963d32-f15e-497e-859a-ed1cb366b0f3 / ext3 defaults 0 1 UUID=dcdceb9f-3a7c-43d8-80dc-0493d7c0fa88 /data4 ext3defaults 0 1 UUID=d79bc11c-461a-45a3-932b-f993777bef3e /data ext3defaults 0 1 etc... And in the boot loader (on i386) I have root=UUID=35963d32-f15e-497e-859a-ed1cb366b0f3 as a kernel option. -- Len Sorensen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: I'm at a loss running Debian
* [Bob] > I must say, I'm not familiar with the LABEL=blah or UUID=xxx-xxx syntax. > Do you have an example of a fstab entry using these attributes? I think it would be something like this: UUID=526d869d-7760-40a4-9a27-759cc8242aa7 / ext3 defaults,errors=remount-ro 0 1 All in one line, so ignore any line breaks added by your mail client. The line was copied from /etc/fstab on my desktop running Ubuntu, but should work the same in Debian. Øystein -- Outgoing mail is certified Virus Free. ..of course, the virus would tell you the same thing.. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: I'm at a loss running Debian
Lennart Sorensen wrote: > On Mon, Aug 13, 2007 at 08:04:13PM +0200, Bob wrote: >> I tried the /dev/disk/by-label approach some time ago, but found it to >> be quite unstable on the nslu2. >> On my boxes, the partition label was not always read from the disk, and >> the boot failed. >> >> Then I changed the entries in fstab to use "/dev/disk/by-uuid" instead, >> and since then, I have not had any problems. > > Use LABEL=blah or UUID=xxx-xxx... rather than /dev/disk/... > Much simpler and not specific to udev or anything else. > > This applies both to the kernel command line and /etc/fstab. I must say, I'm not familiar with the LABEL=blah or UUID=xxx-xxx syntax. Do you have an example of a fstab entry using these attributes? I guess I could look it up on google, but it would be nice to have it in this thread also... -- Bob -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: I'm at a loss running Debian
On Mon, Aug 13, 2007 at 08:04:13PM +0200, Bob wrote: > I tried the /dev/disk/by-label approach some time ago, but found it to > be quite unstable on the nslu2. > On my boxes, the partition label was not always read from the disk, and > the boot failed. > > Then I changed the entries in fstab to use "/dev/disk/by-uuid" instead, > and since then, I have not had any problems. Use LABEL=blah or UUID=xxx-xxx... rather than /dev/disk/... Much simpler and not specific to udev or anything else. This applies both to the kernel command line and /etc/fstab. -- Len Sorensen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: I'm at a loss running Debian
DE POOTER Bart wrote: > # /etc/fstab: static file system information. > # > # > > proc /proc proc > defaults 0 0 > /dev/disk/by-label/root / ext3 > defaults,errors=remount-ro,noatime 0 1 > /dev/disk/by-label/swapstick noneswap > sw 0 0 > /dev/disk/by-label/swapstick /media/usb0 auto > rw,user,noauto 0 0 > /dev/disk/by-label/root /media/usb1 auto > rw,user,noauto,noatime 0 0 > > I added labels with the tune2fs command … So far everything’s working > allright I tried the /dev/disk/by-label approach some time ago, but found it to be quite unstable on the nslu2. On my boxes, the partition label was not always read from the disk, and the boot failed. Then I changed the entries in fstab to use "/dev/disk/by-uuid" instead, and since then, I have not had any problems. Just a thought.. -- Bob -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
RE: Open21xx Bug Report
Thanks for the insight. I'll compile it both ways, signed-char and unsigned-char to make sure everything works before I do a new release. Cheers, Keith -Original Message- From: Michel Dänzer [mailto:[EMAIL PROTECTED] Sent: Monday, August 13, 2007 3:41 AM To: Paul Wise Cc: Keith Clifford; [EMAIL PROTECTED]; debian-powerpc; [EMAIL PROTECTED]; debian-arm@lists.debian.org Subject: RE: Open21xx Bug Report On Sat, 2007-08-11 at 15:55 +, Paul Wise wrote: > On Sat, 2007-08-11 at 08:19 -0700, Keith Clifford wrote: > > > This is the first time these problems have been brought to my attention. > > Unfortunately, I don't have access to the platforms that the build is > > failing on. So, unless someone is willing to step up and help me > > troubleshoot the problems on those platforms, there is little I can do. > > > > I guess you'll have to remove Open21xx from Debian. > > Looks like it never built/worked on those platforms: > > http://buildd.debian.org/build.php?arch=&pkg=open21xx > > Hopefully someone on the porter lists will be able to help (CCed). > > If no-one replies, I'm willing to use the Debian development machines to > help you fix this issue. I'm not familiar with the open21xx source or > package, and I have little time for Debian stuff, so I'll need some > direction and hints about this. Given the list of failing architectures, I think the most likely cause is some code relying on char being signed by default. And indeed, building the as21 directory with -fsigned-char makes it build for me. -- Earthling Michel Dänzer | http://tungstengraphics.com Libre software enthusiast | Debian, X and DRI developer
RE: Bug#376159: Open21xx Bug Report
Good catch. Putting the EOF in the character buffer doesn't sound like a bright thing to do either. I'll review the whole section and get a release to you. Thanks for you help, Keith -Original Message- From: Matej Vela [mailto:[EMAIL PROTECTED] Sent: Monday, August 13, 2007 4:37 AM To: Michel Dänzer Cc: [EMAIL PROTECTED]; Paul Wise; Keith Clifford; debian-powerpc; [EMAIL PROTECTED]; debian-arm@lists.debian.org Subject: Re: Bug#376159: Open21xx Bug Report Michel Dänzer <[EMAIL PROTECTED]> writes: > On Sat, 2007-08-11 at 15:55 +, Paul Wise wrote: >> Looks like it never built/worked on those platforms: >> >> http://buildd.debian.org/build.php?arch=&pkg=open21xx >> >> Hopefully someone on the porter lists will be able to help (CCed). >> >> If no-one replies, I'm willing to use the Debian development machines to >> help you fix this issue. I'm not familiar with the open21xx source or >> package, and I have little time for Debian stuff, so I'll need some >> direction and hints about this. > > Given the list of failing architectures, I think the most likely cause > is some code relying on char being signed by default. And indeed, > building the as21 directory with -fsigned-char makes it build for me. You're right, as21/cpp.c was comparing a plain char to EOF. I've uploaded the attached patch, let's see if it works. Thanks, Matej
Re: Bug#376159: Open21xx Bug Report
On Mon, 2007-08-13 at 13:36 +0200, Matej Vela wrote: > Michel Dänzer <[EMAIL PROTECTED]> writes: > > > On Sat, 2007-08-11 at 15:55 +, Paul Wise wrote: > >> Looks like it never built/worked on those platforms: > >> > >> http://buildd.debian.org/build.php?arch=&pkg=open21xx > >> > >> Hopefully someone on the porter lists will be able to help (CCed). > >> > >> If no-one replies, I'm willing to use the Debian development machines to > >> help you fix this issue. I'm not familiar with the open21xx source or > >> package, and I have little time for Debian stuff, so I'll need some > >> direction and hints about this. > > > > Given the list of failing architectures, I think the most likely cause > > is some code relying on char being signed by default. And indeed, > > building the as21 directory with -fsigned-char makes it build for me. > > You're right, as21/cpp.c was comparing a plain char to EOF. I've > uploaded the attached patch, let's see if it works. Works here. -- Earthling Michel Dänzer | http://tungstengraphics.com Libre software enthusiast | Debian, X and DRI developer
Re: Bug#376159: Open21xx Bug Report
Michel Dänzer <[EMAIL PROTECTED]> writes:
> On Sat, 2007-08-11 at 15:55 +, Paul Wise wrote:
>> Looks like it never built/worked on those platforms:
>>
>> http://buildd.debian.org/build.php?arch=&pkg=open21xx
>>
>> Hopefully someone on the porter lists will be able to help (CCed).
>>
>> If no-one replies, I'm willing to use the Debian development machines to
>> help you fix this issue. I'm not familiar with the open21xx source or
>> package, and I have little time for Debian stuff, so I'll need some
>> direction and hints about this.
>
> Given the list of failing architectures, I think the most likely cause
> is some code relying on char being signed by default. And indeed,
> building the as21 directory with -fsigned-char makes it build for me.
You're right, as21/cpp.c was comparing a plain char to EOF. I've
uploaded the attached patch, let's see if it works.
Thanks,
Matej
--- open21xx-0.7.5.orig/as21/cpp.c
+++ open21xx-0.7.5/as21/cpp.c
@@ -235,7 +235,7 @@
/* - 2 to leave room for testing comments and quotes */
while (chars_read < max_size - 2)
{
-ch = buf[chars_read] = getc( yyin );
+buf[chars_read] = ch = getc( yyin );
if (ch == EOF)
{
goto read_done;
RE: Open21xx Bug Report
On Sat, 2007-08-11 at 15:55 +, Paul Wise wrote: > On Sat, 2007-08-11 at 08:19 -0700, Keith Clifford wrote: > > > This is the first time these problems have been brought to my attention. > > Unfortunately, I don't have access to the platforms that the build is > > failing on. So, unless someone is willing to step up and help me > > troubleshoot the problems on those platforms, there is little I can do. > > > > I guess you'll have to remove Open21xx from Debian. > > Looks like it never built/worked on those platforms: > > http://buildd.debian.org/build.php?arch=&pkg=open21xx > > Hopefully someone on the porter lists will be able to help (CCed). > > If no-one replies, I'm willing to use the Debian development machines to > help you fix this issue. I'm not familiar with the open21xx source or > package, and I have little time for Debian stuff, so I'll need some > direction and hints about this. Given the list of failing architectures, I think the most likely cause is some code relying on char being signed by default. And indeed, building the as21 directory with -fsigned-char makes it build for me. -- Earthling Michel Dänzer | http://tungstengraphics.com Libre software enthusiast | Debian, X and DRI developer
I'm at a loss running Debian
Hi, I want to run Debian r4 on my NSLU2, but it seems like a nightmare to me Ive spent about a whole week on it, trying to get it to run like it should, and somehow everything comes to an end before all things are finished ! I will explain all and hope someone can shed a light on it, cause im about giving it up Story : 1) I Flashed the di-nslu2.bin file to the slug, and after that ive attached my 1 Gb usb-stick to the upper usb port (disk2) 2) The whole installation process was a pain in the ass too, it regularly gave up announcing an error with the initramfs-tools, after formatting the whole usb-stick all over again, it sometimes goes through 3) After everything is set-up, i want to change the default behaviour of mounting the disks by its sdx number, so i put labels on the 2 partitions (1st partition is the root partition which is about 750 Mb, and 2nd partition is the swap partition of about 256 Mb) 4) I added the noatime etc Look at my fstab here > # /etc/fstab: static file system information. # # proc /proc proc defaults 0 0 /dev/disk/by-label/root / ext3 defaults,errors=remount-ro,noatime 0 1 /dev/disk/by-label/swapstick none swap sw 0 0 /dev/disk/by-label/swapstick /media/usb0 auto rw,user,noauto 0 0 /dev/disk/by-label/root /media/usb1 auto rw,user,noauto,noatime 0 0 I added labels with the tune2fs command So far everythings working allright 5) After changing my fstab, i give the following commands : update-initramfs u and after that a flash-kernel command, all this to make these changes permanent in the flash (these advice comes from various sources, so I guess its right) 6) Everythings still booting fine, nows the time to attach my 320 GB mybook external harddrive to port1, again, everythings allright, and after adding labels to this disk and making changes permanent to the flash, its still alright But my swappartition on the usb-stick needs to be excluded from the fstab, because i made a swap partition on my external harddrive, so what I did was putting a remark # character before these two lines : #/dev/disk/by-label/swapstick none swap sw 0 0 #/dev/disk/by-label/swapstick /media/usb0 auto rw,user,noauto 0 0 7) Ill post my new fstab with the entries after making these changes and after my hardddrive is attached : # /etc/fstab: static file system information. # # # # Disk 1 USB Stick 1 Gb proc /proc proc defaults 0 0 /dev/disk/by-label/root / ext3 defaults,errors=remount-ro,noatime 0 1 #/dev/disk/by-label/swapstick none swap sw 0 0 #/dev/disk/by-label/swapstick /media/usb0 auto rw,user,noauto 0 0 /dev/disk/by-label/root /media/usb1 auto rw,user,noauto,noatime 0 0 # # Disk 2 WD Mybook 320GB /dev/disk/by-label/mybookdata /data ext3 defaults,noatime 1 2 /dev/disk/by-label/swapmybook none swap sw 0 0 /dev/disk/by-label/swapmybook /media/usb2 auto rw,user,noauto,noatime 0 0 /dev/disk/by-label/mybookdata /media/usb3 auto rw,user,noauto,noatime 0 0 8) After making these changes and reboot the slug, it just wont boot anymore So, I thought, I change the entries of the fstab back to like it was when still booting fine (with LTOOLS tool under windows), and boot the slug again, guess what Still doing nothing After that - Ive learned from the past I installed everything again and made images with ghost32.exe (v8 i guess) of my whole usb-stick (not just the partitions) and made a copy of my flash by means of the following command : /dev/mtdblock* > backup.bin So I thought im safe if something happens again And off course it had happen again, so I flashed my backup.bin file to the slug, and put the ghost image back on my usb-stick Great was my dissapointment that the slug still refused to boot 9) Im at a loss now, last time i put my stick back in after the slug was started without usb-stick attached, the slug was working on the stick for hrsss, so I thought, maybe a checkdisk is going on, and maybe itll be allright after that nope, still nothing After that, there seems to be error on my ext3 file system too 10) So, my questions, what is the problem that my slug wont boot after r
