Re: [gentoo-user] Re: How to resume 'emerge -e @world' after grub fails?
On K, 2017-12-20 at 17:28 -0600, Dale wrote: > Grant Edwards wrote: > > On 2017-12-18, Grant Edwardswrote: > > > On 2017-12-18, John Blinka wrote: > > > > On Mon, Dec 18, 2017 at 11:00 AM, Grant Edwards > > > > wrote: > > > > > > > > > How do I skip grub and continue? > > > > emerge --skipfirst --resume > > [...] > > > > > Oddly, the failing package (grub:0) wasn't the first one: it was > > > about > > > 5-6 packags down the list. So I used --exclude instead. We'll > > > see > > > how far that gets... > > It took a couple days, but after "resuming" the emerge three times, > > it > > finished. The three failures were grub:0, matplotlib, and crrcsim. > > > > Each time the failed package was around 5th on the list when I did > > a > > resume. And, each time emerge insisted on rebuilding gcc and glibc > > first. [I don't remember what else preceded the failed packages > > when > > I did the resumes.] > > > > I think I'll postpone upgrading to profile 17 on my "real work" > > computers where I have a lot more packages installed. > > > > > I'm not sure why or what all this involves but there is a thread on > -dev > about a 17.1 profile coming at some point. One may want to consider > waiting to do to much for that. Some of the messages make it seem to > be > a really large process to upgrade to it. I'm hoping some or even > most > of it is just the devs testing things. o_O > > Just a thought. It's about making /usr/lib not be a symlink to lib64 anymore on amd64. I wouldn't wait for it, could get complicated and messy to do both at once. If 17.1 pans out (or well, maybe "18.0" when going out of experimental testing phase next year..), it won't need a full rebuild, at most only things that have /usr/lib/ entries (instead of /usr/lib64 or /usr/lib32) in portage CONTENTS file in VDB to fix those things up after the migration tool. And I don't see anything overeager in --depclean. Maybe a dependency was removed later, so with still default "--dynamic-deps y" you get them removed now. If this breaks something, then there's an automagic dep involved (which should have a bug report and be fixed), or some changes done to some ebuild without proper revbump. I think --with-bdeps toggling might let it remove build-time only deps, though. I didn't observe that being used in the thread here in a way that lets these build-time only deps get removed, for that to be it.
Re: [gentoo-user] Re: How to resume 'emerge -e @world' after grub fails?
Am Donnerstag, 21. Dezember 2017, 10:45:41 CET schrieb Jörg Schaible: > Hi, > > Am Mon, 18 Dec 2017 11:07:08 -0500 schrieb John Blinka: > > On Mon, Dec 18, 2017 at 11:00 AM, Grant Edwards > > > >wrote: > >> How do I skip grub and continue? > > > > emerge --skipfirst --resume > > This is unfortunately really dangerous, because "emerge --resume" will > recalculate the order of the outstanding packages and you have no guarantee > that the first one will be the one that failed the last run. In that case > you skip an arbitrary package and you may increase your problems. > > You can use --skipfirst only if you have restarted emerge with --resume only > and you have ensured that it will really continue with the failing package. > You may abort the build then with CTRL-C and restart emerge with both > options. That clashes with my understanding, so I looked it up, and it turns out I was right. From emerge(1): > --skipfirst > > This option is only valid when used with --resume. It removes > the first package in the resume list. Dependencies are > recalculated for remaining packages and any that have > unsatisfied dependencies or are masked will be automatically > dropped. Also see the related --keep-going option. Note the "remaining dependencies" part. Otherwise, what would be the point of --skipfirst if it were so unpredictable? > > I had to do that several times in my 17.0 upgrades. > > Maybe more times than necessary ;-) Really, sometimes I wonder why I keep seeing people on this list who clearly haven't heard of the --keep-going option. It's there for a reason. And don't tell me anybody actually *likes* having to manually continue the emerge process, because that's just so, so tedious. > Cheers, > Jörg Greetings -- Marc Joliet -- "People who think they know everything really annoy those of us who know we don't" - Bjarne Stroustrup signature.asc Description: This is a digitally signed message part.
[gentoo-user] Re: How to resume 'emerge -e @world' after grub fails?
Hi, Am Mon, 18 Dec 2017 11:07:08 -0500 schrieb John Blinka: > On Mon, Dec 18, 2017 at 11:00 AM, Grant Edwards >wrote: >> >> How do I skip grub and continue? >> >> > emerge --skipfirst --resume This is unfortunately really dangerous, because "emerge --resume" will recalculate the order of the outstanding packages and you have no guarantee that the first one will be the one that failed the last run. In that case you skip an arbitrary package and you may increase your problems. You can use --skipfirst only if you have restarted emerge with --resume only and you have ensured that it will really continue with the failing package. You may abort the build then with CTRL-C and restart emerge with both options. > I had to do that several times in my 17.0 upgrades. Maybe more times than necessary ;-) Cheers, Jörg
Re: [gentoo-user] What can cause printer to crop top of page?
On 2017.12.21 17:35, Mick wrote: On Thursday, 21 December 2017 21:24:57 GMT Jack wrote: > I may be grabbing at straws here, but what happens if you print > something in landscape? Is the trimmed edge the new top (long edge) or > still the same short edge? Aha! Good call. In landscape the cropping takes place on the left (short) edge, not the top of the page. > Does the same happen with other apps? browser, emacs, gimp (just make > a simple line drawing), pdf display, image viewer, ...? I'm thinking > of printing things that originate as different image types - maybe one > will behave differently and point to something in the process. Can you > send a plain text file to the printer with lp? I sent a page with Chromium in landscape, it cropped the left hand short edge too. PDF readers print with cropped top, in portrait. I sent a txt file with 'lpr -o fit-to-page' in portrait and the same cropping on the top of the page happens. If the actual text was sent to the printer (and not turned into ps or pdf first, then I blame the printer. So it is not application specific, but page orientation specific. No, it always happens on the first short edge to come out of the printer, no matter which way the pixels are oriented. That (to me) rules out everything except the printer, and just possibly the printer driver. Could it be something has gone wrong with the rollers? This is a brand new printer! Possibly, but my guess is some internal printer setting. Does the printer itself provide a web interface? If so, hunt through the options. You may find something there. (I'm not familiar with that printer, but all of the few wireless printers I have worked with provide a web interface on their configured IP address.) I'll try to print a page with MSWindows tomorrow, if only to prove if this is a cups problem or not. Thanks for your suggestions! -- Regards, Mick
Re: [gentoo-user] What can cause printer to crop top of page?
On Thursday, 21 December 2017 21:24:57 GMT Jack wrote: > I may be grabbing at straws here, but what happens if you print > something in landscape? Is the trimmed edge the new top (long edge) or > still the same short edge? Aha! Good call. In landscape the cropping takes place on the left (short) edge, not the top of the page. > Does the same happen with other apps? browser, emacs, gimp (just make > a simple line drawing), pdf display, image viewer, ...? I'm thinking > of printing things that originate as different image types - maybe one > will behave differently and point to something in the process. Can you > send a plain text file to the printer with lp? I sent a page with Chromium in landscape, it cropped the left hand short edge too. PDF readers print with cropped top, in portrait. I sent a txt file with 'lpr -o fit-to-page' in portrait and the same cropping on the top of the page happens. So it is not application specific, but page orientation specific. Could it be something has gone wrong with the rollers? This is a brand new printer! I'll try to print a page with MSWindows tomorrow, if only to prove if this is a cups problem or not. Thanks for your suggestions! -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] What can cause printer to crop top of page?
On Thursday, 21 December 2017 23:01:50 GMT Walter Dnes wrote: > Is there a default page size setting in your desktop environment that > could've changed? This problem is happening across different PCs, desktops/DEs and different applications. The common factor is they are all using CUPS, the same brother driver and the default page size of A4. I'll have another poke tomorrow into the http GUI of the printer and then try to print with MSWindows to see what happens. -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] What can cause printer to crop top of page?
Is there a default page size setting in your desktop environment that could've changed? -- Walter DnesI don't run "desktop environments"; I run useful applications
[gentoo-user] What can cause printer to crop top of page?
I've been using a Brother "HL-3140CW" model with the net-print/brother- hl3140cw-bin-1.1.4 driver from the brother-overlay. Since I moved to profile 17.0 (I think) pages are being cropped at the top when printing from various applications (LOWriter, Okular, etc.) on different PCs. In LOWriter I had to set a 35mm margin at the top, to be able to get just 13mm at the top of the physical A4 paper, before the top line of text is printed. I have used the Plasma systemsettings5 for printers as well as the http GUI of the printer to see if anything is amiss, but I can't find anything I can change to restore the page alignment as it was a couple of weeks ago. The OEM online help pages suggest to adjust the margins on the application you're are printing from. Any idea what has brought about this change and how I may be able to revert it? Have you noticed anything similar? -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] What can cause printer to crop top of page?
On Thursday, 21 December 2017 18:28:30 GMT you wrote: > On Thursday, 21 December 2017 17:01:09 GMT Jack wrote: > > It sounds to me like a possible A4/USLetter issue. Can you confirm > > that both LOWriter (and other apps) and cups (or whatever is driving > > the printer) are both set to A4? > > > > Jack > > Yes, CUPS and all desktop applications show A4 as the default paper size. > CUPS reports: > > $ lpoptions -p 'HL-3140CW' -l > PageSize/Media Size: *A4 Letter Legal Executive A5 A6 B5 JISB5 JISB6 EnvDL [snip ...] > > Are the above ppd entries correct, or am I misinterpreting the ppd logic? OK, uninstalled cups and the brother printer driver, deleted manually the / etc/cups/pdd/ files reinstalled cups and the brother printer driver and reconfigured the printer using the CUPS http page. Now the discrepancy has disappeared from the ppd file, but still the same error remains. Top of the page is cropped! Arrgh! -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] What can cause printer to crop top of page?
I may be grabbing at straws here, but what happens if you print something in landscape? Is the trimmed edge the new top (long edge) or still the same short edge? Does the same happen with other apps? browser, emacs, gimp (just make a simple line drawing), pdf display, image viewer, ...? I'm thinking of printing things that originate as different image types - maybe one will behave differently and point to something in the process. Can you send a plain text file to the printer with lp?
Re: [gentoo-user] What can cause printer to crop top of page?
On 12/21 02:20, Mick wrote: > I've been using a Brother "HL-3140CW" model with the net-print/brother- > hl3140cw-bin-1.1.4 driver from the brother-overlay. > > Since I moved to profile 17.0 (I think) pages are being cropped at the top > when printing from various applications (LOWriter, Okular, etc.) on different > PCs. > > In LOWriter I had to set a 35mm margin at the top, to be able to get just > 13mm > at the top of the physical A4 paper, before the top line of text is printed. > > I have used the Plasma systemsettings5 for printers as well as the http GUI > of > the printer to see if anything is amiss, but I can't find anything I can > change to restore the page alignment as it was a couple of weeks ago. > > The OEM online help pages suggest to adjust the margins on the application > you're are printing from. > > Any idea what has brought about this change and how I may be able to revert > it? Have you noticed anything similar? > > -- > Regards, > Mick Hi Mick, a shot into the dark: Would it be possible, that not the profile as such has caused the problem but the recompilation of such a lot of applications? May be a default setup has discarded a path setting to your personal settings of the application in question. Try the following: "Fail and win" :) Begin with the application, which is the one with is nearest to the user -- for example the word processor or office syit. Find the personal settings of that application and make a backyp of it to a save place. Load the config file/the ocnfig files and corrupt them (yes!). Start the application. If the application fails: Your settings will not be ignored. If the application runs fine: You have found the application, which was reset to "factory settings" via the recompilation. Until you find that application step forward into the direction of the printer (so to say) in choosing the application. If you have found the application, which ignores ytour personal setting you may have found the culprit. >From the backup restore the settings then start the application and point it to uour settings. Restart the application. May be this way you can figure out, what has happen. Cheers Meino
[gentoo-user] Kernel 4.14.7 no longer switches to VT7
Hi, after the update and installation of gentoo-sources-4.14.7 my two machines no longer switch to SDDM on VT7, it stays on VT1. However, I can switch manually using CTRL-ALT-7 to SDDM and login as usual. If I boot with the last stable kernel 4.12.12 anything is back to normal and the login screen of SDDM appears directly while the rest of the modules is loaded in background. Both machines have older Radeon chips (REDWOOD and CEDAR) and I managed to load also their firmware with the new kernel 4.14.7, but there's still no automatic switch to VT7 anymore. I found nothing obvious in /var/log/messages, dmesg or Xorg.0.log. What may cause this weird behavior? Cheers, Jörg
Re: [gentoo-user] What can cause printer to crop top of page?
On Thursday, 21 December 2017 15:16:32 GMT tu...@posteo.de wrote: > On 12/21 02:20, Mick wrote: > > I've been using a Brother "HL-3140CW" model with the net-print/brother- > > hl3140cw-bin-1.1.4 driver from the brother-overlay. > > > > Since I moved to profile 17.0 (I think) pages are being cropped at the top > > when printing from various applications (LOWriter, Okular, etc.) on > > different PCs. > > > > In LOWriter I had to set a 35mm margin at the top, to be able to get just > > 13mm at the top of the physical A4 paper, before the top line of text is > > printed. > > > > I have used the Plasma systemsettings5 for printers as well as the http > > GUI of the printer to see if anything is amiss, but I can't find anything > > I can change to restore the page alignment as it was a couple of weeks > > ago. > > > > The OEM online help pages suggest to adjust the margins on the application > > you're are printing from. > > > > Any idea what has brought about this change and how I may be able to > > revert > > it? Have you noticed anything similar? > > Hi Mick, > > a shot into the dark: > Would it be possible, that not the profile as such has caused the > problem but the recompilation of such a lot of applications? [snip ...] Thanks Meino, the problem is not with a particular application. Even when I print a test page from CUPS http interface/Maintenance, the top of the page is cropped and the bottom of the test page is consequently printed further up. I'll try reinstalling the firmware next using MSWindows in case something went sideways with the printer. It won't be the first coincidence this week. -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] What can cause printer to crop top of page?
On Thursday, 21 December 2017 17:01:09 GMT Jack wrote: > On 2017.12.21 09:20, Mick wrote: > > I've been using a Brother "HL-3140CW" model with the > > net-print/brother- hl3140cw-bin-1.1.4 driver from the brother-overlay. > > > > Since I moved to profile 17.0 (I think) pages are being cropped at > > the top when printing from various applications (LOWriter, Okular, > > etc.) on different PCs. > > > > In LOWriter I had to set a 35mm margin at the top, to be able to get > > just 13mm at the top of the physical A4 paper, before the top line of > > text is printed. > > > > I have used the Plasma systemsettings5 for printers as well as the > > http GUI of the printer to see if anything is amiss, but I can't find > > anything I can change to restore the page alignment as it was a > > couple of weeks ago. > > > > The OEM online help pages suggest to adjust the margins on the > > application you're are printing from. > > > > Any idea what has brought about this change and how I may be able to > > revert it? Have you noticed anything similar? > > It sounds to me like a possible A4/USLetter issue. Can you confirm > that both LOWriter (and other apps) and cups (or whatever is driving > the printer) are both set to A4? > > Jack Yes, CUPS and all desktop applications show A4 as the default paper size. CUPS reports: $ lpoptions -p 'HL-3140CW' -l PageSize/Media Size: *A4 Letter Legal Executive A5 A6 B5 JISB5 JISB6 EnvDL EnvC5 Env10 EnvMonarch Br3x5 FanFoldGermanLegal EnvPRC5Rotated Postcard EnvYou4 EnvChou3 210x270mm 195x270mm 184x260mm 197x273mm BRInputSlot/Paper Source: *AutoSelect Tray1 Manual BRResolution/Print Quality: *600dpi 600x2400dpi BRMonoColor/Color / Mono: Auto FullColor *Mono BRMediaType/Media Type: *Plain Thin Thick Thicker BOND Env EnvThick EnvThin Recycled Label Glossy PostCard BRColorMatching/Color Mode: *Normal Vivid None BRGray/Improve Gray Color: OFF *ON BREnhanceBlkPrt/Enhance Black Printing: *OFF ON BRTonerSaveMode/Toner Save Mode: OFF *ON BRImproveOutput/Improve Print Output: *OFF BRLessPaperCurl BRFixIntensity BRSkipBlank/Skip Blank Page: *OFF ON BRBrightness/Brightness: -20 -19 -18 -17 -16 -15 -14 -13 -12 -11 -10 -9 -8 -7 -6 -5 -4 -3 -2 -1 *0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 BRContrast/Contrast: -20 -19 -18 -17 -16 -15 -14 -13 -12 -11 -10 -9 -8 -7 -6 -5 -4 -3 -2 -1 *0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 BRRed/Red: -20 -19 -18 -17 -16 -15 -14 -13 -12 -11 -10 -9 -8 -7 -6 -5 -4 -3 -2 -1 *0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 BRGreen/Green: -20 -19 -18 -17 -16 -15 -14 -13 -12 -11 -10 -9 -8 -7 -6 -5 -4 -3 -2 -1 *0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 BRBlue/Blue: -20 -19 -18 -17 -16 -15 -14 -13 -12 -11 -10 -9 -8 -7 -6 -5 -4 -3 -2 -1 *0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 BRSaturation/Saturation: -20 -19 -18 -17 -16 -15 -14 -13 -12 -11 -10 -9 -8 -7 -6 -5 -4 -3 -2 -1 *0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 However, looking inside /etc/cups/ppd/HL-3140CW.ppd I see some strange things: *% Media Selection == *OpenUI *PageSize/Media Size: PickOne *OrderDependency: 11 AnySetup *PageSize *DefaultPageSize: A4 [snip ...] *OpenUI *PageRegion: PickOne *OrderDependency: 12 AnySetup *PageRegion *DefaultPageRegion: A4 [snip ...] BUT ... then I noticed this: *DefaultImageableArea: Letter<==What the ...?! *ImageableArea A4/A4: "12 12 583 830" *ImageableArea Letter/Letter: "12 12 600 780" *ImageableArea Legal/Legal: "12 12 600 996" [snip ...] AND *% Information About Media Sizes *DefaultPaperDimension: Letter<==Should this be here ...?! *PaperDimension A4/A4: "595 842" *PaperDimension Letter/Letter: "612 792" *PaperDimension Legal/Legal:"612 1008" Are the above ppd entries correct, or am I misinterpreting the ppd logic? -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] What can cause printer to crop top of page?
On 2017.12.21 09:20, Mick wrote: I've been using a Brother "HL-3140CW" model with the net-print/brother- hl3140cw-bin-1.1.4 driver from the brother-overlay. Since I moved to profile 17.0 (I think) pages are being cropped at the top when printing from various applications (LOWriter, Okular, etc.) on different PCs. In LOWriter I had to set a 35mm margin at the top, to be able to get just 13mm at the top of the physical A4 paper, before the top line of text is printed. I have used the Plasma systemsettings5 for printers as well as the http GUI of the printer to see if anything is amiss, but I can't find anything I can change to restore the page alignment as it was a couple of weeks ago. The OEM online help pages suggest to adjust the margins on the application you're are printing from. Any idea what has brought about this change and how I may be able to revert it? Have you noticed anything similar? It sounds to me like a possible A4/USLetter issue. Can you confirm that both LOWriter (and other apps) and cups (or whatever is driving the printer) are both set to A4? Jack
[gentoo-user] Re: How to resume 'emerge -e @world' after grub fails?
On 2017-12-21, Marc Jolietwrote: > Really, sometimes I wonder why I keep seeing people on this list who > clearly haven't heard of the --keep-going option. I know about the option and choose not to use it. I don't want it to "keep going" until I've looked at what failed and why. > It's there for a reason. And don't tell me anybody actually *likes* > having to manually continue the emerge process, because that's just > so, so tedious. You think manually controlling things is "tedious" and you run Gentoo? -- Grant
Re: [gentoo-user] Re: How to resume 'emerge -e @world' after grub fails?
On Thu, 21 Dec 2017 07:00:47 -0500, Marc Joliet wrote: > > [1 ] > [1.1 ] > [1.2 ] > Am Donnerstag, 21. Dezember 2017, 10:45:41 CET schrieb Jörg Schaible: > > > Hi, > > > > > > Am Mon, 18 Dec 2017 11:07:08 -0500 schrieb John Blinka: > > > > On Mon, Dec 18, 2017 at 11:00 AM, Grant Edwards > > > > > > > >wrote: > > > >> How do I skip grub and continue? > > > > > > > > emerge --skipfirst --resume > > > > > > This is unfortunately really dangerous, because "emerge --resume" will > > > recalculate the order of the outstanding packages and you have no guarantee > > > that the first one will be the one that failed the last run. In that case > > > you skip an arbitrary package and you may increase your problems. > > > > > > You can use --skipfirst only if you have restarted emerge with --resume only > > > and you have ensured that it will really continue with the failing package. > > > You may abort the build then with CTRL-C and restart emerge with both > > > options. > > That clashes with my understanding, so I looked it up, and it turns out I was > right. From emerge(1): > > > --skipfirst > > > > > > This option is only valid when used with --resume. It removes > > > the first package in the resume list. Dependencies are > > > recalculated for remaining packages and any that have > > > unsatisfied dependencies or are masked will be automatically > > > dropped. Also see the related --keep-going option. > > Note the "remaining dependencies" part. Otherwise, what would be the point of > --skipfirst if it were so unpredictable? > > > > I had to do that several times in my 17.0 upgrades. > > > > > > Maybe more times than necessary ;-) > > Really, sometimes I wonder why I keep seeing people on this list who clearly > haven't heard of the --keep-going option. It's there for a reason. And don't > tell me anybody actually *likes* having to manually continue the emerge > process, > because that's just so, so tedious. > > > Cheers, > > > Jörg > > Greetings > > -- > > Marc Joliet > I have been doing explicit packages as stated in another thread here and I just delete all the lines before the one that fails. I did not want to use --keep-going because I really did want to fix things as they came up, in case they might effect some packages further down on the list. What I did was to do emerge -ep @world | awk '/ebuild/ {print "="$4}' >a Once I had that a file, I just put emerge -1a before the first line and put \ at the end of each line and I was off to the slow races! Its been about a week with the bugs I had to research and the ebuilds I had to patch, etc. but its going now and there is only 1-200 packages to go out of 1500 or so. -- Your life is like a penny. You're going to lose it. The question is: How do you spend it? John Covici wb2una cov...@ccs.covici.com
[gentoo-user] Re: How to resume 'emerge -e @world' after grub fails?
Am Thu, 21 Dec 2017 13:00:47 +0100 schrieb Marc Joliet: > Am Donnerstag, 21. Dezember 2017, 10:45:41 CET schrieb Jörg Schaible: >> Hi, >> >> Am Mon, 18 Dec 2017 11:07:08 -0500 schrieb John Blinka: >> > On Mon, Dec 18, 2017 at 11:00 AM, Grant Edwards >> > >> >wrote: >> >> How do I skip grub and continue? >> > >> > emerge --skipfirst --resume >> >> This is unfortunately really dangerous, because "emerge --resume" will >> recalculate the order of the outstanding packages and you have no >> guarantee that the first one will be the one that failed the last run. >> In that case you skip an arbitrary package and you may increase your >> problems. >> >> You can use --skipfirst only if you have restarted emerge with --resume >> only and you have ensured that it will really continue with the failing >> package. You may abort the build then with CTRL-C and restart emerge >> with both options. > > That clashes with my understanding, so I looked it up, and it turns out > I was right. From emerge(1): > >> --skipfirst >> >> This option is only valid when used with --resume. It >> removes the first package in the resume list. >> Dependencies are recalculated for remaining packages and >> any that have unsatisfied dependencies or are masked will >> be automatically dropped. Also see the related >> --keep-going option. > > Note the "remaining dependencies" part. Otherwise, what would be the > point of --skipfirst if it were so unpredictable? Well, that's the difference between theory and practice. I've been bitten more than once, but you may do as you want, it's your system ... Cheers, Jörg