[Cooker] Re: [i18n] something wrong with curl

2003-03-05 Thread John Danielson, II


Combelles, Christophe (MED, ALTEN) wrote:

When running urpmi, the output of "curl" is not correct :

(...)  ETA = 4521k, vitesse = 0:00:04

- ETA should not be a size, but a time
- speed (vitesse) should not be a time, but a rate
Is it only in french ?



Given the thread so far, what are the chances that urpmi is expecting 
data in a different order than curl is sending it??? Direct run with 
output to console does not always mean a return passback\response from 
an indirect call is understood right when an app is indirectly 
called If changing so that curl works messes up wget, the 
probability is that each uses different data order for passthrough 
response than the other when called or that the format parsed is 
different than what is sent (urpmi may not be understanding curl right 
cuz it is trying to handle passed data like wget passes data-- 
possible???). Given that urpmi says curl has failed but that a direct 
connect with curl succeeds, and  given that wget works with urpmi fine 
but urpmi has problems with curl even on club library access, I think 
modular INTER-relations (data handling) should be looked at. This is 
what a bundler of a software set I would buy from does, handles 
intermodular relations mostly. My brother makes a living fixing old 
masonry where the mortar was faulty and the walls are now crumbling 
(with physical structures) and does so in ways that let historic 
building meet historic codes (outside looks same, fix is stronger inside 
than ever), my skill lies in the area of seeing modular interrelation 
patterns of fault in computer systems by seeing patterns of breakage. 
Problem here might not be curl, might be that what urpmi thinks curl is 
sending is not what curl means.

cc cooker as outside poster to that list from this email address

John Danielson.




[Cooker] Email preferences:

2003-02-03 Thread John Danielson, II
The column headers for Reporter and Assignee in the email action prefs 
(online) are reversed:

I am never an assignee, or fixer, I can only due to peculiarities of 
mental ability analyze patterns and deduce functionally what is behind 
patterns. So, I turned off the prefs under Assignee. I got MYSELF 
excluded from any bug I report by doing this, so have no followup 
context for same-- unless I browse for it, and then only if it had the 
bug number in subject so cooker had it. If what I said about the scanner 
and printer bugs helped, I would like to know what did and did not help 
so I can tune my bug submissions.

They should be #1240 and #1242. Is it possible to get those threads 
echoed\repeated to me at the reply-to email address?? The first letter 
SHOULD be a capital J, how that happened is a long story but suffice to 
say there is a valid email box at netscape.net that is never picked up 
due to password database corruption.

Also, the link to the cooker maillist archives seems to have disappeared 
from the cooker page


Echoed as a suggestion set for wish list:

Please make the stock KDM login the default boot login again, we do not 
need things so dumbed down as the XP-pseudo imitation login would have 
it(if Halt were changed to Halt\Off and Reboot were left alone or 
changed to Restart or Warm Boot, much of  the longer lasting confusion 
would evaporate, English folks do not think of stop as turn off). 
Keystroke for keystroke(or mouse click for mouse click) is not needed if 
the similarity is enough that people who used Windows can use it. It 
was, as-was, the most intuitive part of KDE and Mandy for this 
EX-Windows user-- whose favorite was 98 SE and not 2000 or XP. I have 
used both 2000 and XP, and have set XP to classic mode for many folks 
because they wanted the older look back.

John Danielson.




Re: [Cooker] /dev/dvd , ide-scsi, devfs

2003-01-26 Thread John Danielson, II
rcc wrote:


the /dev/dvd link is missing

/etc/devfs/dvd.conf points to an ide cd device but there's only a
generic device at the target dir. Same is true for rdvd.conf and, in my
case, hdc.conf. The desired cd device is at scsi as the my ide dvdrom is
now scsi. BTW, how do I turn that feature off? Kernel append only has
the burner for ide-scsi.

ah, and the nvidia line in modules.devfs is obsolete: NVdriver is now
simply nvidia

- Mark


 

Mark, is this a combo drive, DVD and CD-RW??? Or a DVD burner??? My 
Mandrake uses my CD-RW subtype burner as SCSI also, but it does work-- 
for reading, sound CD play, and burning. I just told Mandrake 9.0 to use 
/dev/scd0 instead of /dev/cdrom for data reads.  Kscd thinks it has a 
SCSI CD-ROM for audio play. Burning will only happen in SCSI mode, was 
easiest to leave it that way all the time and that way Supermount and 
devfsd also work. Ditto for cooker, with a takeoff point from beta2.

With a combo drive, it is again easiest to run it as SCSI emulation on 
all the time AFAIK. I think, could be wrong and YMMV, that one or the 
other would be easiest to standardize on-- and burning software needs 
SCSI emulation on. My TDK behaves this way, my HP did also, and 
unfortunately I do not have the funds for Cendyne DV-RW right now (I 
spent money for more RAM instead).

John.

John Danielson.

--
Your favorite stores, helpful shopping tools and great gift ideas. 
Experience the convenience of buying online with Shop@Netscape! 
http://shopnow.netscape.com/





Re: [Cooker] VAIO support

2003-01-26 Thread John Danielson, II
B Lauber wrote:



Sorry, I don't think I was clear last time.  It's not that there is no 
APM support for VAIO -- it's that it's broken.  When the system 
recovers from a suspend, everything will lock after 3-5 seconds 
(before this, the keyboard and mouse will work perfectly.)

I have included the write-up of my syslog that I promised.  It may not 
be exact -- I had to copy it manually since the system freezes before 
it is written to the hd:


This is what my syslog reads when returning from a system suspend:

apmd[985]: System Suspend
apmd[985]: apmd_call_proxy: executing: 
'/etc/sysconfig/apm-scripts/apmd_proxy' 'resume'
usb: Initializing USB controller (usb-uhci): succeeded
kernel: mice: PS/2 mouse common for all mice
network: Setting network parameters: succeeded
apmd[985]: apmd_call_proxy: + Initializing USB controller (usb-uhci): 
[  OK  ]^M Setting network parameters: [  OK  ]^M Bringing up loopback 
interface:
network: Bringing up loopback interface: succeeded
kernel: 8139too Fast Ethernet driver 0.9.25
kernel: PCI: Enabling device 00:10.0 ( -> 0003)
kernel: PCI: Found IRQ 10 for device 00:10.0
kernel: IRQ routing conflict for 00:07.5, have irq 5, want irq 10
kernel: IRQ routing conflict for 00:07.6, have irq 5, want irq 10
kernel: PCI: Sharing IRQ 10 with 00:0a.1
kernel: PCI: Setting latency timer of device 00:10.0 to 64

**



If I enter a suspend while the system is first booting up , everything 
will work perfectly (keyboard works, mouse works, etc) until... well, 
here's the print-up:

Mounting local filesystems:   [  OK  ]
Checking loopback filesystems:[  OK  ]
Mounting loopback filesystems:[  OK  ]
Loading keymap: us[  OK  ]
Loading compose keys: compose.latin.inc   [  OK  ]
The BackSpace key sends: ^?   [  OK  ]
Enabling swap space:  [  OK  ]
Initializing firewire controller (ohci1394):  [  OK  ]
Building Window Manager Sessions  [  OK  ]
insmod: Hint: insmod errors can be caused by incorrect module 
parameters, including invalid IO or IRQ parameters.
You may find more information in syslog or the output from dmesg





Once again, I want to reiterate that I know for a fact that this 
problem did not exist in Mandrake 8.0.  If anyone has any idea why 
this problem formed between 8.0 and 8.2  (I never tested 8.1), that 
would be great.

As for now, I'm going to do more research into the problem -- Chao


From: Adam Williamson <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Re: [Cooker] VAIO support
Date: 25 Jan 2003 20:09:17 +

On Sat, 2003-01-25 at 17:06, B Lauber wrote:
>   Sony claims that VAIO systems are not designed for Linux, but I 
know for a
> fact that my system worked just fine w/ Mandrake 8.0.  If I can see 
anything
> in 9.1, I would like to see a modification for APM so that my 
system is able
> to suspend again.

Just add "acpi=off" to the append line in lilo.conf (or the
configuration file for whatever bootloader you use :>). Then you'll get
APM.

>   Here's what I know as of now:  the confusion  that causes the 
system to
> lock has something to do w/ the keyboard and the system's fan (I 
have a
> battery that causes the fan to studder at times; whenever it 
studders, the
> keyboard studders as well.  Furthermore, when the system recovers 
from a
> suspend, it will work for about 5 seconds until the fan 
reactivates.).  My
> guess is that the keyboard is wrongly detected and registered because
> between Mandrake versions 8.0 and 8.2 it has lost support for the 
windows
> keys (in 8.0, pushing the windows key would make the K menu pop up).
>   I will have more information soon -- I'm going to put 8.0 back 
onto my
> system and check the irq's of the keyboard and such.

ACPI works very well on my C1XD; suspend doesn't seem to work, however.
(At least not with "cat 3 > /proc/acpi/sleep", which is the only method
I've heard of to invoke a suspend under ACPI.
--
adamw



Sorry, I don't think I was clear last time.  It's not that there is no 
APM support for VAIO -- it's that it's broken.  When the system 
recovers from a suspend, everything will lock after 3-5 seconds 
(before this, the keyboard and mouse will work perfectly.)

I have included the writup of my syslog that I promised.  It may not 
be exact -- I had to copy it manually since the system freezez before 
it is written to the hd:



apmd[985]: System Suspend
apmd[985]: apmd_call_proxy: executing: 
'/etc/sysconfig/apm-scripts/apmd_proxy' 'resume'
usb: Initializing USB controller (usb-uhci): succeeded
kernel: mice: PS/2 mouse common for all mice
network: Setting network parameters: succeeded
apmd[985]: apmd_call_proxy: + Initializing USB controller (usb-uhci): 
[  OK  ]^M Setting network parameters: [  OK  ]^M Bringi

Re: Serial ATA support or not... Was:Re: [Cooker] Corrections/Addonto lspci database...

2003-01-25 Thread John Danielson, II
Thomas Backlund wrote:


Viestissä Sunnuntai 26. Tammikuuta 2003 00:21, John Danielson, II kirjoitti:
 

Some of the new VIA and Intel mainboards that support 3+ GIG CPUs allow
for these drives, but they right now are future tech given the mech.
prices for about 90% of the public. We do not need to heavily worry
about these particular busses right now, IMHO, but in 2 years when R&D
costs of mfrs. are somewhat paid for, they may start to become very
popular in things like backup appliances and high-end cluster storage
units, especially for those heavily into animated high quality graphics.

John.
   


Well actually the SATA disks are not so far away...
Here in Finland they are taking pre-orders for Seagate SATA disks now...
and Maxtor Maxline disks should show up next month (don't know their price...)

as for the Seagate Barracuda V 120GB, the price is:
IDE: 178,- Euro
SATA: 276,- Euro

but you can also buy an SATA to UATA adapter for 58,- Euro,
and hook up any IDE disk you want...

It may be aiming too high to aim for a full support in 9.1 since they
have to be tested... but after that Release the SATA disks should
have found their way to the stores...

Well, that's just my opinion...
---

Thomas
**
[EMAIL PROTECTED]  
www.iki.fi/~tmb/
**



 

That is interesting, and for those with the need for extreme speed, yes. 
For me, I will spend about $100.00 US for 100GB Western Digital JB 
series( 8MB buffer, 7200 RPM, ATA/100) and say that is all I need and 
then some for my P4\1.8GHz box(which says it runs at about 3600 
Bogomips, but will also be a 2.53 GHz by then) for the next year or so. 
As it has a 40 GB in a swap tray, a 60 that will be joining it in a 
companion swap tray, and an 80 GB JB series that ran me all of $85.00 US 
three months ago, I think a price increase of 2.5X is not in the cards 
for the common man yet. Yes, first models are available from 
Manufacturers, like fiber channels were available 2 plus years ago.

Those who work for Digital Domain or Image&Light Magic or work heavily 
with Crystal Space 3D need those kinds of HDs, yes. And when they drop 
to about 3\4 of current price I will want one of teh S\ATAs to go on the 
Intel PEBT2 motherboard I am hankering for(wanting badly)-- 8 months to 
a year for that, would be my guess. ATA's have halved in price per Gig, 
almost, in the last year. 120 GB JB series WD HDs are commonly available 
for about $130.00 USD over here, and can be had as low as $110.00 USD at 
qty 10-pack or more. For 9.2, this is something to look at seriously, 
but would shelve until then in a wishlist folder or email archive for 
wishlist work.

Idea valid, yes(very much so), but would have to say urgency is kinda low.

John.




Re: [Cooker] Corrections/Addon to lspci database...

2003-01-25 Thread John Danielson, II
Thomas Backlund wrote:


Viestissä Lauantai 25. Tammikuuta 2003 22:44, Pixel kirjoitti:
 

Thomas Backlund <[EMAIL PROTECTED]> writes:

given network added to the pcitable:

0x10b70x9201  "3c59x" "3Com Corporation|3c920 Tornado"

(this is format we use for pci devices, please give it that way if
possible :)

   

01:0b.0 RAID bus controller: Silicon Image: Sil3112 Serial ATA (rev 01)
...
as the kernel also know about:
SiI3112 Serial ATA: IDE controller at PCI slot 01:0b.0
SiI3112 Serial ATA: chipset revision 1
SiI3112 Serial ATA: not 100% native mode: will probe irqs later
 

what is this module?

thanks!
   


well actually it seems to be built in ide support, from
/usr/src/linux/drivers/ide/pci/siimage.c

but if that would be built as a module, it should have the name siimage, 
shouldn't it...


---

Thomas
**
[EMAIL PROTECTED]  
www.iki.fi/~tmb/
**



 

While Serial ATA is in a sense for Hard Drives and is tuned for storage 
media, it will not take standard IDE or ATA connections-- in fact, the 
bussing standards for it are not finalized yet(they are in the same 
state of completion as is dual-channel DDR RAM, which has initial 
offerings available but no finalized standards are fully in place for 
that yet, either). What the bus does is very high pumped speed HD access 
via a serial connect-- the throughput is comparable to firewire plus 10% 
or so, and the data flow is serial with separate dedicated control lines 
on the same connector. Typically it is run inside the FSB area of a 
mainboard, and to a degree will imitate ATA. It is intended for HDs with 
10,000 to 15,000 or higher rotational speeds and thus very low average 
seek times. Silicon Image, Promise, and HighPoint Technology are touting 
these. The earliest drives for this are in the price range of Maxtor's 
fiber channel drives, as the same basic mechs are needed for both S\ATA 
and fiber channel to support the high speed access.

What is being discussed now is the degree to which one will be able to 
hot-swap these drives like SCSI drives can so be swapped. It is 
proposed, and most agree, that it will be as hot-swappable as SCSI or 
USB or Firewire. The connector Pics I have seen are smaller, 10-16 wire 
connectors. They are not pure fiber connect.

Some of the new VIA and Intel mainboards that support 3+ GIG CPUs allow 
for these drives, but they right now are future tech given the mech. 
prices for about 90% of the public. We do not need to heavily worry 
about these particular busses right now, IMHO, but in 2 years when R&D 
costs of mfrs. are somewhat paid for, they may start to become very 
popular in things like backup appliances and high-end cluster storage 
units, especially for those heavily into animated high quality graphics.

John.





Re: [Cooker] Re: [Contrib-Rpm] chrony-1.19-1mdk

2003-01-25 Thread John Danielson, II
Ben Reser wrote:


On Fri, Jan 24, 2003 at 10:39:45PM -0700, Vincent Danen wrote:
 

Agreed.

Or, even better, split ntp into two packages... ntp-client and
ntp-server.  You only need ntpdate and /etc/ntp/step-tickers to set the
time from a remote ntp server... running the full-blown ntpd is silly.

For instance, on a local network of 10 machines, only one machine needs
to run ntpd, and get the time from an external NTP server.  The other 9
machines just need to run ntpdate on boot or at a desired interval...
they don't all need to run ntpd.
   


According to the ntp people ntpdate is deprecated.  They basically tell
you to use ntpd with certain options which isn't really a good
replacement for it.

Note the disclaimer on the top of this page:
http://www.eecis.udel.edu/~ntp/ntp_spool/html/ntpdate.html

 

I run ntpd as they recommend, but sync(by calling ntpd from webmin using 
the hardware->time server choice) via the Webmin interface. Webmin 
writes a decent call to ntpd. I tend to sync once a month, and that 
keeps me within 10 sec of real. For standalone boxes like mine in the 
US, http://nist.time.gov/ is webbable also, with a javascripted time 
display that self-syncs to nist. on pane one, you choose time zone, pane 
two shows time to second. Good for general use.

John.

--
Your favorite stores, helpful shopping tools and great gift ideas. 
Experience the convenience of buying online with Shop@Netscape! 
http://shopnow.netscape.com/





Re: [Cooker] [Bug 1037] [Installation] beta2 fails to get xwindowsworking

2003-01-24 Thread John Danielson, II
[Bug 1037] wrote:


https://qa.mandrakesoft.com/show_bug.cgi?id=1037





--- Additional Comments From [EMAIL PROTECTED]  2003-01-25 02:36 ---
This workaround works - but begs the question, how is it that linux loses track
of its cdrom? I've seen that problem before under 8.1



--- You are receiving this mail because: ---
You are on the CC list for the bug, or are watching someone who is.



--- Reminder: ---
assigned_to: [EMAIL PROTECTED]
description: 
I've tried to install 9.1b2 twice tonight on my ibm x21 laptop. Everything goes
fine, except that xwindows won't start after install completes. After the
install, it boots only to console (even when I tell it to default to gnome).
When I say startx, it complains that things are not properly setup. Setup never
queries me about the display.

When I su and try to run drakconf to configure the display, it asks for cd1
again, but when I put it in, it doesn't recognize it.

When I try running xf86config to set things up, it goes through everything ok,
but when I run startx, it gives an execsv error about x.


 

Sorry, the part during install is Not losing track of drive, in fact 
there is a file that got stuck in ISO for CD1 that is just plain wrong. 
That is why reregistering it after install with the urpmi.update for 
source cdrom1 works (with that CD in drive, urpmi reads the CD itself to 
see what is on it and updates its database accordingly, THEN it can find 
what is on it correctly). There are two files on CD ISOs from Mandrake 
that do this, hdlist and synthesis. on an ISO set, there can be two of 
these on CD1, one set for the whole CD set (which the installer reads at 
the beginning), and another for just the CD1. With betas and last minute 
changes, ISO contents can change and get moved from CD to CD. That is 
the how it can happen that a CD1 cannot be found and the drive drivers 
can be fine. Another way is to acidentally burn so that the wrong volume 
label gets burned, but in my case I know for a fact that the CD-ROM 
drive worked and the burning was correct to what was in the ISO and the 
ISOs came from main mirrors and md5summed right before burning in 
addition to all the above. And I had the same basic thing happen to me.

in my case, after install I did this to get into the KDE GUI:

tried the approach you did, same result;
then did this oddball set of things:

invoked 'gdm' and got an error telling me X was running , after about 30 
seconds at 3500+ bogomips (1793 actual MHz P4 box), and did I want to 
try that using a different display-- I told it yes. And X came up with 
KDE loading. After playing a bit, I updated cooker to two days ago, and 
now system comes up sweet as a fresh cucumber from the midwest-- or in 
Dolphin, as I multiboot cooker and Dolphin. Each is on a separate HD. 
The only way each can see part of the other is if I manually mount a 
partition. KDE 3.1 is sweetly implemented for a test release, and this 
is an early one which is even more exciting.

John.

John.




Re: [Cooker] [Bug 1062] [drakxtools] New: No ip over 1394

2003-01-24 Thread John Danielson, II
[Bug 1062] wrote:


https://qa.mandrakesoft.com/show_bug.cgi?id=1062

  Product: drakxtools
Component: DrakConnect
  Summary: No ip over 1394
  Version: 9.1-0.13mdk
 Platform: PC
  URL: [EMAIL PROTECTED]
   OS/Version: All
   Status: UNCONFIRMED
 Severity: major
 Priority: P1
   AssignedTo: [EMAIL PROTECTED]
   ReportedBy: [EMAIL PROTECTED]


DrakConnect doesn't list eth1394 as a driver, and expert mode crashes when I 
try it. This is after I have done insmod eth1394.o.gz and re booted. Actually, 
this option should be offered during the install, automatically, so those of 
us who are relying on our firewire cards to connect two windows machines will 
be able to network our new Linux install to, say, our winxp machine. (My case).
Even though my Linux bootup screen says eth0 is "OK", my winxp machine can't 
tell it's there. xp says "1394 Connection A network cable is unplugged." The 
Linux machine is dual booted with winme which does work with ip over 1394, 
Internet and everything. Linux needs to do ip over 1394 "out of the box", 
firewire has been around for some time now. And I can't find ANY documentation 
on the eth1394 module anywhere. Any ideas?



--- You are receiving this mail because: ---
You are on the CC list for the bug, or are watching someone who is.


 

Firewire support is still being finalized, as is USB 2.0 which is being 
also finalized as far as things ever are in the Linux world. Kernel 
developers are working on this still, it is not fully and completely a 
part of any stock distro exept as one might consider LFS or Gentoo a 
stock thing (you compile from source and tweak right now to get ieee1394 
support going right if you also have USB or especially USB 2.0 also, 
among other things). This is a linux-wide issue, not just a Mandrake 
one. I do not think that even a USB 2.0 direct-connect cable works in 
Linux commonly yet. At a guess, we will need to wait for things from 2.5 
development branch of kernel to be back-ported(patched back into the 2.4 
branch) if that is feasible, or for 2.6 to come out in late 2003 to 
early 2004. Software driver support for classes of things tends to take 
longer than for pinpoint drivers-- and for what the other operating 
system you use has, the base support is already there. For Linux, sorry 
to say not yet. Linux was first designed for servers and older boxes, 
those tend to use NICs instead of direct-connects, and for that reason 
Linux has supported a bunch of NICs for a very long time. The consumer 
variants of things have been not heavily worked on compared to LAN and 
server technology classes of devices. For now, the following direct 
connects are feasible and fairly easily accomplished:
1. Null modem serial port connects, with or without modems involved 
(modem to modem and serial port to serial port with special cabling are 
both possible);
2. NIC to NIC connects with a crossover cable between them, and;
3. Parallel (ieee1284 type, two way Parallel) cable connects.
Of those three, Gigabit NIC to NIC would be fastest and would be faster 
than firewire also in terms of what you could do with data that also 
needs to be stored even in a caching way when transferred. Next fastest 
would be about as fast as actual USB 1.1, and that would still be a 
NIC-to-NIC connection (Intel eepro100s work, as do some 3COMs, VERY 
well, for this and for  LAN use).

Cheapest is a tossup between 1 and 2, for Linux.

John.




Re: [Cooker] urpmi is broken in latex cooker

2003-01-24 Thread John Danielson, II
Kim Schulz wrote:


On Fri, 24 Jan 2003 17:05:45 -0500
Charles A Edwards <[EMAIL PROTECTED]> wrote:
 

On Fri, 24 Jan 2003 22:43:50 +0100
Kim Schulz <[EMAIL PROTECTED]> wrote:

   

What is wrong? 
 

Same here.

urpmi-4.2-11 caused it. 
You can revert to -10 or wait for -12 and manually install it.
   



It works if you use --wget


 

It works VERY, VERY well with wget, and I think wget also has more 
flexibility in how and when it times out(I know wget  can resume 
fetches, though I do not know if this has been integrated into urpmi's 
calling of it-- it also can do single file ftp sessions, and this it 
looks like it is doing(wget call for each rpm chosen, as single RPMs). I 
did my first update from beta2 isos to what was then current with an
urpmi.update --wget Cooker_main
followed by an
urpmi --wget --auto-select --media Cooker_main

and it figured out things very nicely for me. It grabbed about 200 MB of 
files and proceeded to dep analyze, then install properly. In fact, with 
a media name variation, this is how I always update even in Dolphin if I 
do not want pinpoint updating of an app plus deps.

John.




Re: [Cooker] [Bug 1023] [Installation] New: unable to go back tothe start of the installation

2003-01-24 Thread John Danielson, II
Pixel wrote:


"John Danielson, II" <[EMAIL PROTECTED]> writes:

 

anyway, most things should be accessible in the "summary" step, isn't
that enough?

 

IF that is documented, YES. Tell people to fix via summary what seems still
broken(and make that statement prominently early in install, that install has
changed and summary (or Advanced Setup, see below) now gets you where there is
no advanced button earlier)-- like printers, etc. People will not guess that--
if the box were titled Advanced Setup, they might catch on easier that the
buttons WORK (except for the sound aspect, and this inconsistency might throw
some folks for  a loop ("It's the only thing there that I cannot get to the
config of by clicking on, WHY???").
   


the ergonomy of the "summary" step will (should?) change :)

not everything is decided yet, remarks will be welcome, even if not
everything is possible. I think (hope?:) I took into account most
remarks i've received!

 

BTW, would the folks in charge of documentation contact me??? I have some time
free and could help with that better than coding details in languages I either
knew and have forgotten most of the details of or have not learned. I also
have threads in the Club in documentation and translation areas working (on
this topic, documentation for end users), and a tiny website if anyone wishes
to see what the perspective behind this request is adn who in general I am.
   


please contact [EMAIL PROTECTED]
(there may be some other way, but at least i know this one works :)


 

Thank you, will contact her and yes, you do very well at integrating 
comments\remarks\ideas into reality.  :)

John.

--
Your favorite stores, helpful shopping tools and great gift ideas. 
Experience the convenience of buying online with Shop@Netscape! 
http://shopnow.netscape.com/





Re: [Cooker] [Bug 1054] [rpmdrake] New: Mandrake Update hangs ifSource is bad

2003-01-24 Thread John Danielson, II
[Bug 1054] wrote:


https://qa.mandrakesoft.com/show_bug.cgi?id=1054

  Product: rpmdrake
Component: MandrakeUpdate
  Summary: Mandrake Update hangs if Source is bad
  Version: 2.0-27mdk
 Platform: All
   OS/Version: All
   Status: UNCONFIRMED
 Severity: normal
 Priority: P1
   AssignedTo: [EMAIL PROTECTED]
   ReportedBy: [EMAIL PROTECTED]


When a Mandrake Update mirror entry is not valid, Mandrake Update will hang
forever with the dialog "Please wait, contacting mirror to update packages."  
The only way to recover is (novice method) kill the window or (expert method)  
ps for the urpmi process and kill it. 
   
The Log Messages within the Mdk Control Center only says
  "MandrakeUpdate[3081]: launched command: /usr/sbin/urpmi.update
update_source"
   
Console messages are equally terse, hanging with the status message: 
  retrieving description file of "update_source"...
   
There are two things. First is that urpmi.update cannot recover if the update  
source URL is bad. It fails just the same way if invoked from the  
command-line. The second is that mirror URLs retrieved from the Choose A   
Mirror interface are not reliable.  It's trial and error to select a working   
mirror as an Update Source, then that Source can become invalid some time  
later.
  
SUGGESTION: Why _commit_ to an Update Source at all? Why not present the user   
with the Mirror List EACH TIME he/she invokes Mandrake Update? If fetching the   
Mirror List should fail, there can be one in cache. Then the user would choose   
one (or more?) from the List and press a button to retrieve the Description   
File. Any mirror that delivers a proper Description File is the mirror we use   
to retrieve files. If this fails, however, the user would be alerted and   
invited to try another mirror from the list. Repeat until success. 
  
The interface could get specific about failures w/o too much trouble, 
informing the user that the Mirror is full (try later), or else it doesn't 
respond (network down?), or the path is missing and requires administrator's 
attention. 

   
full console trace:
   
mcc pid 3052
examining synthesis file [/var/lib/urpmi/synthesis.hdlist.Installation CD 1
(x86) (cdrom1).cz]
examining synthesis file [/var/lib/urpmi/synthesis.hdlist.Installation CD 2
(x86) (cdrom2).cz]
examining synthesis file [/var/lib/urpmi/synthesis.hdlist.International CD
(x86) (cdrom3).cz]
examining synthesis file [/var/lib/urpmi/synthesis.hdlist.update_source.cz]
examining synthesis file [/var/lib/urpmi/synthesis.hdlist.Installation CD 1
(x86) (cdrom1).cz]
examining synthesis file [/var/lib/urpmi/synthesis.hdlist.Installation CD 2
(x86) (cdrom2).cz]
examining synthesis file [/var/lib/urpmi/synthesis.hdlist.International CD
(x86) (cdrom3).cz]
retrieving description file of "update_source"...



--- You are receiving this mail because: ---
You are on the CC list for the bug, or are watching someone who is.


 

Yes, it looks like urpmi cannot subparse 500 series ftp info messages or 
echo to a dialog (either would work, if a 15 line scrollable ftp status 
dialog or child pane\Xwindow would be doable). I found 3\4 of the 
failures, when followed by immediate ftp linkups, showed 530-- mirror at 
capacity for this class of user-- errors. Not dead mirror, not bad URL 
per se, rather mirror busy for anonymous access. so, typically in that 
case switched to another CONTINENT for downloading. I now, in my 
Software Manager in 9.0, install instead of update, and list by 
upgradability-- if the upgradability list would also show source, oe 
could pick from an upgradability list more intelligently and eliminate 
the use of the auto-updater module in MCC except for security updates. 
This would save dev time, lots of it. One or the other needs doing, imho.

John.





Re: USB disk drive problems - was Re: [Cooker] kernel panic debugging

2003-01-24 Thread John Danielson, II
Chmouel Boudjnah wrote:


Owen Savill <[EMAIL PROTECTED]> writes:

 

3) There is a kernel patch for the SanDisk USB disk caddies but this
does not appear to have been incorporated into the Mandrake kernel.
   


look weird, i don't have such beast to test, but if you point me to it
i will maybe integrated.



 

Might be very useful to look at the code for that-- SanDisk can use 
memory cards as virtual disks. Some IBM Microdisks work on a similar 
theme driver-wise, as there are both PCMCIA and memory card reader 
adapters for same. Essentially, SanDisk has what they call\classify as a 
virtual drive adapter, but it is mostly an IC memory module reader for 
one of their module lines. Large IC cards with 256 MB and up were made 
for high-density digital cameras, and  it was convenient to have readers 
that handled them as HDs for older PCs that were USB capable but not USB 
2.0 capable. In the US, about 5 variants of this theme exist (IC card as 
virtual HD, reversing the SWAP idea for portability of data 
convenience). Take a pocket sized reader, floppy or CD with drivers, and 
high capacity card to any USB capable box, install drivers, run and 
carry decent sized chunks of data in tiny package about size of a CD 
Business card to any box that will take the data and has USB capable 
O/S. Some of these run at USB 2.0 rates.

John.

--
Your favorite stores, helpful shopping tools and great gift ideas. 
Experience the convenience of buying online with Shop@Netscape! 
http://shopnow.netscape.com/





Re: [Cooker] [Bug 955] [Installation] wheel mouse boundaries notreleased after wheel test

2003-01-24 Thread John Danielson, II
[Bug 955] wrote:


https://qa.mandrakesoft.com/show_bug.cgi?id=955





--- Additional Comments From [EMAIL PROTECTED]  2003-01-24 15:32 ---
No, it's a very common PS/2 mouse :

Logitech cordless wheel mouse
M/N : M-RG45
P/N : 850612-1000

But I don't think it depends on the mouse type.



--- You are receiving this mail because: ---
You are on the CC list for the bug, or are watching someone who is.



--- Reminder: ---
assigned_to: [EMAIL PROTECTED]
description: 
- Start install with a wheel mouse
- choose "standard wheel mouse" at mouse choice, click next
- test your buttons and click "next"

--> even at the next step, the mouse cannot be driven outside the dark blue area.

expected behaviour : the mouse boundaries should be limited only for the wheel
test, but should be released for the next dialog.


 

It is NOT only a logitech thing-- Microsoft Wheel Mouse Optical 
(Glidepoint chip), USB and PS\2 multimodal with a PS\2 physical connect 
does this also. This mouse behaves as a:

[root@ root]# cat /etc/sysconfig/mouse
MOUSETYPE=imps2
XMOUSETYPE=IMPS/2
FULLNAME="PS/2|Generic PS2 Wheel Mouse"
XEMU3=no
WHEEL=yes
device=psaux
[root@ root]#

and thusly works, but as a glidepoint it races when hooked to PS\2 port 
(psaux) but works as a USB-- in 9.0, and in 91. beta2 post-install ( but 
has bounding box probs IN install after mouse test, and since the 
summary box is in that bounding area, is this a high priority thing??? 
simply map within test box bounds after mouse test for dialogs???). 
Basicly, looks like mouse settings are not being taken\accepted\then 
USED by installer, or this is a bounding box persistence problem per se 
and not relevant to the mouse driver-- way back when, some folks forced 
a full screen bounding box reset after small dialogs locked mice cursors 
to small areas in a couple other operating systems-- I think this might 
be a lack of remapping the mousable area frame size as part of a 
successful test exit, and it persists until a larger screen area is 
refreshed\repainted than the old area (it was called bounding box focus 
retention in one operating system, and persisted when folks either 
forgot to force a new box the size of the window or full screen as 
appropriate in a submodule exit, or forgot to define a default large 
enough and return to that default after a module exit, or changed the 
default and forgot to revert it by multiusing one variable). I am 
getting similar things with MCC in beta2, not mouse boundaries, but 
refresh\repaint area resets not happening until the full right pane is 
forced to repaint with a menu event like a choice to see logs or not.  I 
have had to in some cases unembed MCC submodules to get them to run (KDE 
desktop). This latter thing might be programmatically related, so I 
include here. Some modules in MCC stick with the wait logo and label 
displayed and no GUI action I can derive will open them-- boot floppy is 
one such in MCC in KDE.

John.





Re: [Cooker] [Bug 1023] [Installation] New: unable to go back tothe start of the installation

2003-01-24 Thread John Danielson, II
Pixel wrote:


"Combelles, Christophe (MED, ALTEN)" <[EMAIL PROTECTED]> writes:

 

I agree, it seems like a regression since 9.0

And there are "next" and "back" buttons.
So we expect the "back" button to be able to bring us back to the beginning.
(though it doesn't seem to work on 9.1b2).
So why shouldn't it be possible to jump directly to a particular step ?
   


because some people decided that it was too powerful?

anyway, most things should be accessible in the "summary" step, isn't
that enough?


 

IF that is documented, YES. Tell people to fix via summary what seems 
still broken(and make that statement prominently early in install, that 
install has changed and summary (or Advanced Setup, see below) now gets 
you where there is no advanced button earlier)-- like printers, etc. 
People will not guess that-- if the box were titled Advanced Setup, they 
might catch on easier that the buttons WORK (except for the sound 
aspect, and this inconsistency might throw some folks for  a loop ("It's 
the only thing there that I cannot get to the config of by clicking on, 
WHY???").

BTW, would the folks in charge of documentation contact me??? I have 
some time free and could help with that better than coding details in 
languages I either knew and have forgotten most of the details of or 
have not learned. I also have threads in the Club in documentation and 
translation areas working (on this topic, documentation for end users), 
and a tiny website if anyone wishes to see what the perspective behind 
this request is adn who in general I am.

John.




Re: [Cooker] [Bug 1037] [Installation] New: beta2 fails to get xwindowsworking

2003-01-23 Thread John Danielson, II
[Bug 1037] wrote:


https://qa.mandrakesoft.com/show_bug.cgi?id=1037

  Product: Installation
Component: Installation
  Summary: beta2 fails to get xwindows working
  Version: 1.771
 Platform: PC
   OS/Version: All
   Status: UNCONFIRMED
 Severity: blocker
 Priority: P2
   AssignedTo: [EMAIL PROTECTED]
   ReportedBy: [EMAIL PROTECTED]


I've tried to install 9.1b2 twice tonight on my ibm x21 laptop. Everything goes
fine, except that xwindows won't start after install completes. After the
install, it boots only to console (even when I tell it to default to gnome).
When I say startx, it complains that things are not properly setup. Setup never
queries me about the display.

When I su and try to run drakconf to configure the display, it asks for cd1
again, but when I put it in, it doesn't recognize it.

When I try running xf86config to set things up, it goes through everything ok,
but when I run startx, it gives an execsv error about x.



--- You are receiving this mail because: ---
You are on the CC list for the bug, or are watching someone who is.


 

Stick CD1 back in, and in console:

su - root
(root password)
urpmi.update cdrom1

then when it finishes go do what you did before with XFdrake if needed. 
CD1 will now be figured out.

My understanding, this will be fixed in the Beta3 release. That will be 
the next set of frozen ISOs.

John.




Re: [Cooker] 9.1 Beta 2

2003-01-23 Thread John Danielson, II
Teletchéa Stéphane wrote:


Le jeu 23/01/2003 à 14:23, Robert Fox a écrit :
 

On Thu, 2003-01-23 at 12:08, Warly wrote:
   

Shouldn't we agree on making compromise and selecting some
applications instead of including everything ? As an example shouldn't
we agree on making xcdroast, or k3b, the mandrake default burner, and
convince everybody to test it and make it good enough for everyone,
instead of having 5 of them ?
 

Well said!!!  I think we should use a voting system (like the RPM
package voting in the MandrakeClub) which narrows down the top apps like
e-mail, browser, news reader, text editor, etc.

Having a default application and maybe one alternative (second runner
up) would help reduce confusion for newbies and make the distro more
manageable size wise.

The third and fourth tier softwares could then be available from a
"Mandrake Updateable" website (kinda like the PLF and Texstar's stuff)
using RPMDRAKE.

This would be awesome!

Great idea Warly!
   


I think i agree for almost what i said, but i would remind you some
stuff :
as a scientist, i use specific applications which are not very useful in
day-to-day usage (xmgrace, pybliographic, xdrawchem), so they will not
collect enough votes.
But these are mandatory for me and some others ...

I think these applications should stay in the downloadable isos.
For day-to-day applications, i think it could be a great idea to have
two applications for each task (may be one for kde, the other for
gnome).

Other applications could be available via Mandrake Club if desired. It
could be a good way to enrich the club's lack of attract (except for
charity reasons) : here is a good way to improve the Club's attracting
value.

Stef

*~~*
Linux 2.4.19-16mdk #1 Fri Sep 20 18:15:05 CEST 2002
1:00pm up 13 days, 52 min, 3 users, load average: 1.00, 1.02, 1.02
 

I hate to say this, but in fact Lindows in version 3.0 is doing most of 
what we are doing in the Club as far as apckages, but giving one year 
access for those that buy systems with Lindows on, then selling at 
$99.00 per year for access after that.

Essentially, $99.00 per user or machine per year would pay for a huge 
hunk of bandwidth. Am willing to stay at silver membership (cannot 
afford higher right now) but would suggest going to a level that cuts 
out the lowest level or where the lowest level cuts out library access 
for non-core upgrades and additional tested packages, starts at about 
$100.00 per year, and give 3-6 months access with a boxed set purchase. 
At that income\user point, most of the apps we are culling could be 
libraried on club mirrors and at that level, Mandrake could get a 
professional data librarian to track the main mirror(which in essence is 
why Lindows went to the software library concept, they run a limited 
number of very high speed and high capacity mirrors, and library 
memberships pay for a lot of the pure data handling costs (as opposed to 
dev costs). While I do not mean to suggest a me-too thing here, I do 
think the general principle holds water, with RPM and mirror content 
management a librarian kind of thing that the club could fund if done right.

Down the line, we might build a Scientific ISO, a Media ISO, and use the 
category chunking to advantage as a library management thing-- if  we 
get enough call to build an ISO, and enough users then download to pay 
for the cost of generating a valid tested ISO, then we could also sell 
same pre-burned as add-on packages. I am going to propose this also on 
the Club, see if can get a bunch of feedback. If you want, will echo 
that to AOLM NG also, see what the response is.

John.




Re: [Cooker] [Bug 1028] [harddrake] New: My disc writer doesn't appearin Harddrake hardware list

2003-01-23 Thread John Danielson, II
[Bug 1028] wrote:


https://qa.mandrakesoft.com/show_bug.cgi?id=1028

  Product: harddrake
Component: harddrake
  Summary: My disc writer doesn't appear in Harddrake hardware list
  Version: 9.1-0.12mdk
 Platform: PC
   OS/Version: All
   Status: UNCONFIRMED
 Severity: normal
 Priority: P2
   AssignedTo: [EMAIL PROTECTED]
   ReportedBy: [EMAIL PROTECTED]


Connected on the second IDE plug, as a slave. It is an Hewlett Packard one, and
I can mount it.

what kind of information do you need?



--- You are receiving this mail because: ---
You are on the CC list for the bug, or are watching someone who is.


 

Ok, can you tell us the model as well as the firmware rev from 
Windows??? HP has this habit of reissuing and revising firmware patches 
for older burners\writer\readers. I had an 8100i a while back, that had 
been firmware revised to be mmc2 compatible, and later a 9100n that I 
could burn to as a generic mmc2 and which no specific driver was known 
for in the hardware list. In quite a few cases, HP has had various 
others private label things for them. Most of the 9000 series responds 
to mmc2 compatible commands except where a firmware flash build error or 
burn error occurred. I ignored such as an analyst, as they met the base 
specs for mmc2 close to standard enough to be group-classed as mmc2 or 
mmc3 compatible.

Both Stomp Click-N-Burn 2.0, based on licensed Veritas algorithms, and 
Easy CD Creator can burn to them, and Linux could also do so at about 
1\2 rated capacity and ran them at full rotational speed at which speed 
they vibrated the computer case quite loudly. As Veritas knows very well 
how to talk to their firmware, maybe someone could talk to them about 
adapting their Linux HP driver solutions used for their software for 
burning with Mandrake over the long haul??? Right now Veritas is 
concentrating on backup solutions in re Linux, but most of their backup 
solutions can use CD-R or CD-RW as backup media-- they work closely with 
HP in regard to HP drives for backup, have for a long time.

I now use TDK, because their drives  more fully meet the mmc standard 
sets, does not step its rotational and burn speeds radically until over 
the 20X mark. I can say this, the packet to packet rates on a TDK 
40x12x40x can be set to 20x and vary from 43x to 18x from one packet 
chunk to next and still not make coasters. The average overall ISO burn 
comes out to about 115% of rated speed chosen, and this brand is the 
only brand I can burn 90%+reliable ISO sets at 20X on B- media while my 
system is doing other things. I usually run burns with burnproof on. 
gCombust works fine with this drive over the 6+ months I have had it 
(TDK VeloCD 40x12x40x, which cost me far less than half the price of my 
older HP 9100 series). I have burned about 70 ISO sets of 3 CDs each 
with it. I THINK it is burning in a standards emulation mode in Linux, 
but emulates very well. It also is an unknown as to specific model, and 
TDK also tends to stick new capacities in firmware applied to older mech 
designs.

John.







Re: [Cooker] Chanintech Apogee(7VJL) on board lan does not work

2003-01-23 Thread John Danielson, II
John Allen wrote:


On Thursday 23 January 2003 12:19, Chmouel Boudjnah wrote:
 

John Allen <[EMAIL PROTECTED]> writes:
   

The via-rhine driver loads fine, and ifstatus says there is a link
heartbeat, but no traffic ever goes through the interface.
 

via-rhine works fine, are you sure you have your network properly
configured ?
   


Maybe it is just the Chaintech 7VJL then. (I have installed a 3Com card and it 
works fine). I have also tried the VIA driver from Chaintech, and the one 
directly from VIA, same result.

It does however work perfectly under Windows XP.

I hopefully will be getting another 7VJL, and if works on that I can just send 
the current one back.

Thanks.
 

Under THOSE circumstances, you might also see if the BIOS has the 
embedded LAN turned off. Linux can detect things that the computer BIOS 
will not flow data to, then users wonder why the heck data traffic 
cannot happen until they either use an add-on card or check the BIOS 
(sometimes in peripherals, sometimes advanced setup, sometimes PNP 
area). I have also had Linux not like defaulted resources that conflict 
but which windows treats as non-dedicated and uses with less efficiency 
if conflicted. I lost LAN, then sound, then both, and finally after 
telling my BIOS to reconfigure itself yet AGAIN (actually time 6, and a 
BIOS Flash) most conflicts were resolved and things worked in Linux. 
Chaintechs do this, some Soyo boards that are modern do this, Intel 
boards that are modern do this.
The south bridges mitigate such things to a large degree, and I know 
this because of two things that area growing-in-frequency pattern: the 
BIOSs are coded to stack SB routed traffic first if must, and Windows 
uses SB drivers that turn conflicts over to the SB of modern boards 
rather than direct access. Internal to Windows the SB stacked IRQs are 
separated out, that is why you can see Windows using IRQs 16-20 
internally these days-- this sacrifices efficiency per stream for 
compatibility with modern boards that in essence use the SB as a very 
good resource conflict mitigator for media and LAN data streaming, and 
they typically chunk USB into that, and firewire-- the combo of IRQ plus 
port set is used to determine what resource is wanted, not primarily 
just IRQ any more or IRQ foremost with I\O port second, they are used 
TOGETHER now. Over the long haul, linux will have to recognize changes 
that have descended into chipware and firmware.

Thumbnail Linguistic XREF\Perspective:

SOUTH BRIDGE is secondary chipset controller of resource flows, paired 
with North Bridge, or primary chipset controller. In England, it is 
called a southbridge by some, in the US two words are used for this 
chipset chip. In Europe, closest equiv. I can think of in English is 
Ancillary main chipset controller, or multimedia controller (while north 
bridge would be the main chipset controller). I would like to be 
enlightened as to how you folks differentiate the chips in a now-dual 
main-chipset board structure, so we can understand each other better.

John.




Re: [Cooker] beta 2 review up

2003-01-22 Thread John Danielson, II
Charlie wrote:


Before I started mucking around trying to make the system recognize the CD 
drives all that was in the append line of lilo.conf was:

"devfs=mount hdd=ide-scsi" 

which is correct. That's my Mitsumi CR-4804 TE CD-RW. Harddrake still claimed 
that the CD-ROM drive (Liteon LTN 403L) was a scsi drive. and showed the 
CD-RW not at all. Plus I kept seeing this or something like it in the logs:

Jan 21 13:04:02 localhost kernel: ide-scsi: hdc: unsupported command in 
request queue (0)
Jan 21 14:31:18 localhost last message repeated 14 times
Jan 21 14:42:38 localhost last message repeated 36 times
Jan 21 14:53:40 localhost last message repeated 36 times

which makes sense when the thing is mis-identified.


Yes, this does make sense this way. Plus, I learn things this way, too 
(make suggestions given my level of knowledge, see why things work 
different by looking at replies and taking correction and amplification 
into account) ... :) Thanks.

 

if there, remove, reboot 2-3 times and see if reappears. If is from a
boot module, reboot should trigger recreate, if not then it might stay
away.
   


I chased every file I could think of all day trying to make things work 
correctly, then re-installed 9.1beta2 on a new 40 GB drive that had nothing 
on it at all. Same thing.

The addition of hdc=ide-cdrom (thanks Pixel!) seems to have improved things. 
I'll report back after I reboot again since I just installed the latest 
initscripts. My fingers are crossed.
 

grub.menu ditto. grub can grab data from lilo.conf if invoked\linked in
after lilo was used for boot loader.

John.
   


Thanks John. 
 

If I think I can contrib, will try. Welcome for what little I could do.







Re: [Cooker] [Bug 986] [kdebase] New: 9.1beta2 gdm dialog in racewith shutdown/reboot

2003-01-22 Thread John Danielson, II
[Bug 986] wrote:


https://qa.mandrakesoft.com/show_bug.cgi?id=986

  Product: kdebase
Component: kdebase
  Summary: 9.1beta2 gdm dialog in race with shutdown/reboot
  Version: 3.1-0.rc6.19mdk
 Platform: PC
   OS/Version: All
   Status: UNCONFIRMED
 Severity: major
 Priority: P2
   AssignedTo: [EMAIL PROTECTED]
   ReportedBy: [EMAIL PROTECTED]


I'm not sure where to submit this.  It happens in both KDE and GNOME in
9.1beta2.  If I select either "shutdown" or "reboot" from the KDE/GNOME Logout
dialog, the graphical login prompt comes back up anyway and stays there.  If I
do a CTRL-ALT-BSP, the shutdown or reboot proceeds normally.  However, I doubt
that Joe Sixpack is going to know to do something like that.



--- You are receiving this mail because: ---
You are on the CC list for the bug, or are watching someone who is.


 

Correct, now at the bottom of the graphical login screen the system 
button has the reboot and halt options, and those work anytime the 
graphical login is invoked(click system button, choose action). It looks 
like the mortar(scripts) processing the halt and reboot calls are not 
passing them to the gdm right so that things just continue toward the 
reboot or halt (German for American English shutdown). Essentially, 
desktop is shutting down, but the graphical login thing is now being 
just called, not an entry point into its appropriate action points as if 
the shutdown from desktop were being fully honored and acted upon.

John.




Re: [Cooker] beta 2 review up

2003-01-21 Thread John Danielson, II
Charlie wrote:


On Tuesday 21 January 2003 06:14 pm, Adam Williamson wrote:
 

On Wed, 2003-01-22 at 01:09, Pixel wrote:
   

Pixel - I'm not sure this is your / DrakX's fault =). I noticed Cooker
starting doing this on my machine a few days back. I have a DVD-ROM /
CD-ROM (no writing functions) as /dev/hdc on this machine, and a CDRW
drive as /dev/hdd. Up until recently this was correctly setup by
Cooker, with /dev/hdc left alone and the CDRW put through ide-scsi as
/dev/scd0. However, just recently, for some reason, both of my drives
are being run through the ide-scsi emulation, so now the DVD-ROM comes
up as /dev/scd0 and the CDRW is /dev/scd1. I think it may be some kind
of kernel bug - I think it started happening the last time I upgraded
the kernel. Is anyone else in the same situation (with some CDRW drives
and some not-RW drives) with the same issue? Unfortunately I don't know
how ide-scsi is configured so I don't know where to start looking for
the problem...:/

   

:-(

try booting with "hdc=ide-scsi hdd=ide-cdrom" (or maybe hdd=ide-cd)
 

Er, do you mean the other way around? As I said, it's hdc that's meant
to stay as an IDE device, and hdd that's meant to be scsi-fied :). If
you do, I'll try that out next time I reboot, and report back.
   


I just did (both ways hdc=ide-cd and hdc=ide-cdrom) and there's no difference. 
Interesting thing though, now I get a red "failed" at the devfs mounting 
local filesystems "no medium found" warning. Floppy drive tries to run at 
boot now too. I have no access to any removable media now at all. The floppy 
may have been part of it previously. Yep, I just checked the copy of mtab I 
saved and what's at /etc/mtab now, the same exactly.

  What to look for now?
 

check your lilo.conf or boot config module in MCC for an append request 
for hdc, i.e.:

hdc=ide-scsi

if there, remove, reboot 2-3 times and see if reappears. If is from a 
boot module, reboot should trigger recreate, if not then it might stay away.

grub.menu ditto. grub can grab data from lilo.conf if invoked\linked in 
after lilo was used for boot loader.

John.

--
Your favorite stores, helpful shopping tools and great gift ideas. 
Experience the convenience of buying online with Shop@Netscape! 
http://shopnow.netscape.com/





Re: [Cooker] [Bug 974] [mount] New: fat32 filesytem mounted as world-writable

2003-01-21 Thread John Danielson, II
Dan Scott wrote:


I agree with your evaluation, Pixel. 

Rationale: 
-- 
Worrying about a largely theoretical Linux virus seems pretty pointless.
Let's think about the user base that we're targeting: 

* absolute beginners (the same ones likely to use autologin and msec 0):
will want to browse through their FAT32 filesystem to load and edit
their MS Word documents, then reboot into Windows for some other
application where they may also load the same document in MS Word again,
until they become accustomed to Linux and break ties with Windows. These
users are quite unlikely to quickly figure out how to change the mount
permissions, and not particularly likely to understand why they were
prevented from writing to those files in the first place... if it's
FAT32, in Windows they can delete pretty much anything they like. 

* power users: familiar with at least one desktop environment, able to
find drakconf and change the permissions to lock themselves out of FAT32
partitions if they so desire (or able to browse the HOWTOs and learn
enough to edit /etc/fstab to do the right thing) 

* LPIC-certified sysadmins: able to tweak /etc/fstab to their heart's
content 

Just to get my own biases out of the way, I'm LPIC-1 certified, but
(shh) probably closer to a power user than sysadmin. I would expect this
kind of setting to be determined by msec, and/or easily tweakable
through drakconf. 

Dan 

On Tue, 2003-01-21 at 20:05, Pixel wrote: 
 

"[Bug 974]" <[EMAIL PROTECTED]> writes:

   

The value of umask(=0) makes many system files on the FAT32 partition writable by a  
non-root linux user. This is very undesirable and risky. In the extreme case, a  
well-designed linux virus can easily damage the windows system files !! 
The proper solution to this is to change the umask value to 022 so that only root has 
write access to the FAT32 system.
 

umask=0 is what people want AFAIK...

cooker people, WYT?

@resolution=invalid
@product=Installation
   


 

I agree with Dan in part. What I do to cope with this in part is:

First, share only data files- that leaves older macro viruses, they tend 
to mostly corrupt files that are of the file type that the macro was 
written for, and the types I shared get scanned on open by NAV anyway. 
Actually, now I use only apps that run in Win4Lin 4.0. And they are 
writing data to directories that are actually on Ext3FS files systems. 
My /home is now huge, about 20 Gig.

Secondly, I could in Windows simply select all files in a directory, 
remove the read only that previous versions of Mandrake marked said 
files, and edited to my content thereafter.  Windows users with Linux 
multiboot who run ISOs or file sets in SAO or TAO with fixate to CD-RW 
also quickly catch on to the need to do this when transferring those to 
other boxes that need to be able to operate them. I do this 5-10 times a 
week-- not complaining, saying that Windows users will usually know how 
to fix with 3 mouse clicks in Windows.

Thirdly, I tend to use RAV desktop AV in LINUX to check my pseudo FAT32 
file subsystem encapsulated in four subtrees of my ext3  /home part, 
once a week or so(did this with my Windows true FAT32s before)-- and 
found nothing, nada for the month I have been doing so(this month from 
end of December 2002). 90% of Windows viruses primarily propagate from 
box to box by email, and while a novice might THINK something that said 
it was a Word doc trashed his machine, it was an executable 
encapsulation inside the doc that unarchived and acted. So, email AV 
scanning will break at entry for almost any known viruses. AND, RAV 
desktop for Linux has every def. that RAV fro mail servers has and every 
def. that the RAV for Windows has. AND, Windows viruses cannot trash 
Linux apps except those few that were ported with identical compromises 
built in and retained from other operating systems source apps.

Documenting this triune strat might just help quell such things, and if 
Mandrake can partner to include a year of RAV desktop in PowerPack or 
PowerSuite that would probably complete a non-recoding full solution.

John.




Re: [Cooker] [Bug 939] [Installation] Unable to configure Video server

2003-01-21 Thread John Danielson, II
[Bug 939] wrote:


https://qa.mandrakesoft.com/show_bug.cgi?id=939





--- Additional Comments From [EMAIL PROTECTED]  2003-01-22 03:15 ---
Valid for 9.1 beta 2



--- You are receiving this mail because: ---
You are on the CC list for the bug, or are watching someone who is.



--- Reminder: ---
assigned_to: [EMAIL PROTECTED]
description: 
9.1 beta 2 - At Summary step of installation, video **NOT** configured so I
attempted to do it manually.  Found monitor (Dell P991), found adapter (GEForce
DDR2), selected XFree 4.whatever.  Configuration complains: "Server SVGA is not
available.  (should be in /mnt/usr/X11R6/bin/XFree86)

I don't know if this is due to installer not starting network, or excessively
tight security.  (I'm seeing messages from lpinfo bitching about unable to
connect to server: connection refused.)

Booting to command line prompt, startx command fails


 

Re: booting to command prompt, startx fails:

Confirm existence, BUT, add this: booting into x by calling gdm works, 
ie I left X running (it was up, though in radically a wrong video mode 
with a"live" mouse cursor but no input accepted as a CLI entry would 
give with a failsafe after clicking on the console area),  and just 
invoked gdm. A kdm call failed also, must have been an x-kdm related 
problem and not a pure X start problem. So, with a gdm call following a 
reboot after install first time session without telling the boot config 
wizard to boot into.

Prelim primary drilldown hypothesis, kdm or linking to kdm  from X 
broken as to video settings, kdm not coming up in 1024x768(as set by 
installer) and therefore not interacting right to the input, or not 
failsafe mode delineation for kdm's linkings that it will use.

Lesser prob. possibility-- Geforce card was linked to default nv11 
driver, possible that new kdm is optuned for the nVidia mfr drivers(kdm 
breaking against scripting and/or driver itself).

I cannot drill further without comparison data.

Data needed: Is anyone who is NOT using an nVidia card experiencing this???

John.




Re: [Cooker] diskdrake prob followed by maint session problem withsolution

2003-01-17 Thread John Danielson, II
Thomas Backlund wrote:


From: "John Danielson, II" <[EMAIL PROTECTED]>
 

Any system that has EVER had a file system with Windows or DOS on it has
 

the
 

following part structure.

Part #s 1-4 can be primary.
Part #5 is always an extended part table to hold logical drives.
Parts 6 and up can be logicals.

 

|
| And Windows allows for 4 primaries, not 3. So a mixed system or a
| migrators system will have a mess.
|

You have misread the partition tables, or how it works...

Windows/dos (or actually the partitioning scheme) does allow
for 4 primaries, BUT the extended partition counts as one primary.

You dot believe me? If so, it's easy to test ...
1. Create 4 primary partitions. (make sure you leave some empty space
   on the disk, for example 4  x 1GB partitions on a 10 GB disk leaves
   you with 6 GB of free space on the disk...)

2. Now try to make a extended partition... IT WON'T WORK

3. Remove one of  the primary partitions. Now you can create an
   extended partition that uses the free space on the disk,
   that also allows you to make logical partitions...

Thomas





 

OK, point made, because I did that(I had thought the extended part table 
was a special case).

However, some of what I was trying to say is that what linux sees as how 
Windows numbers things is that the extended table is always one up from 
that last created Primary, also. therfore, what happens when a windows 
tool is used to make Ext3 or Ext2 is that:

If primary 1 and 2 exist, then extended part table is 3, first logical 
is 5, etc.
If primary 1 exists, then extended part table is 2 and the logicals 
start at 5.

diskdrake numbers it 4-- so long as only and forever Diskdrake works on 
parts, this is fine, but when it errors it does need something else to 
work on it to fix or the /etc/fstab manually revised after an e2fsck 
failure at boot.

If a Windows or DOS based tool, including Ranish, sees a single primary, 
an extended numbered 4 and a logical numbered 5 it will says the chain 
is invalid. most GUI'd Windows tools will then invalidate the drive 
insofar as access is concerned.

Linux Logical parts can live within a Win95 Ext'd LBA defined if they 
themselves each bound on CHS boundaries. User cannot calc those 
boundaries, new current HD have variable sectors per track-- either 
diskdrake talks to drive controller or it needs to use nearest pure 
cylinder bound less than user assigned space (calcing with avg. 
sectors\track will give a CHS bound, good enough). What does w newbie do 
when asking fro size of part??? 8,000,000 Kbytes is roughly 8Gig-- so he 
says 8,000 MB. Asks for that. PM 8.0 lets you drag, and shows you valid 
CHS boundary increments. Nice-- if use then part numbers change versus 
what /etc/fstab was written to reflect, things get mashed AGAIN until 
manual edit performed.

Windows based tools that are backward compatible do this, and I also get 
different sized parts out of what diskdrake tells me while the windows 
tools tell exactly what the bound is by changing the size dynamically to 
show the revised size bounded to CHS. Newbie favors this info level, 
WILL use these tools if was a Windows power user tired of paying for 
Windows junk that crashes and has security holes that Linux does not 
(prime business motivator, and where Mandrake tends to get support 
funds, and where I KNOW RedHat gets support and training income).

Easiest fix is to unhook the mount link by commenting it, then reboot 
and try to fix. Diskdrake erred, so newbie is GONNA try something else. 
Newbie likes GUIs-- is he gonna go for a CLI based thing that has no 
visual feedback and little validate before write?? No, he is not-- is he 
gonna pay for something obviously broken??? Half won't-- our market 
increase potential for Linux Mandrake as a whole just halved itself. I 
gotta sell Windows users on this thing, and if must say here is how you 
do this with windows tools to handle a diskdrake prob, they are not 
gonna use diskdrake, tell friends they can't cuz its broke, and the FUD 
starts, and Mandrake's rep suffers. The core user tools HAVE to be 
clear, clearly doced, with fallback recovery procedures in that doc-- 
procedures tuned for EASY.

Two major areas picking up Linux use in my area-- Small businesses and 
end users, and both need things they can do for themselves, not things 
having to pay someone for tech support. I have a school district 
interested in the LTSP, but if a Parapro cannot maintain a HD with GUI'd 
Linux tools he is gonna use GUI'D windows tools that the district has on 
hand. Resulting conflicts between Mandrake's tools and other tools that 
can make valid Ext3 parts that linux can use will result in increased 
resistance to Linux rather than a ground swell, and where schools go 
there go our kids here for the most part -- another resistance to overcome.

John.







Re: [Cooker] diskdrake prob followed by maint session problem withsolution

2003-01-17 Thread John Danielson, II
Pixel wrote:


"John Danielson, II" <[EMAIL PROTECTED]> writes:

 

The commented line is what I had to pull to get the machine to boot past an
ext2 fsck that said it could not find a superblock when I tried to boot the
machine into Linux.
[...]
I was trying to use Diskdrake from the GUI when this happened, as any newbie
would.
   


so, as far as i understand, the bug is:

 when creating a partition on a live system with
 diskdrake, it writes the partition table, it
 writes the fstab, *but* it doesn't manage to
 format the partition because it wants to reboot
 first.

is that it?

if that's the pb, I thought it was fixed, *unless* you did resize a
partition first.


 

Summary:

Write part table as Ext2Fs when Ext3FS type chosen.
Fails to format-- errors and says it has to do so after reboot.
Then wants to write fstab anyway.

No resize. No extended part table anything else can recognize of common 
available tools a newbie would have handy.

NOT FIXED!

John.

--
Your favorite stores, helpful shopping tools and great gift ideas. 
Experience the convenience of buying online with Shop@Netscape! 
http://shopnow.netscape.com/





Re: [Cooker] diskdrake prob followed by maint session problem with solution

2003-01-16 Thread John Danielson, II
Pixel wrote:


"John Danielson, II" <[EMAIL PROTECTED]> writes:

 

Any system that has EVER had a file system with Windows or DOS on it has the
following part structure.

Part #s 1-4 can be primary.
Part #5 is always an extended part table to hold logical drives.
Parts 6 and up can be logicals.
   


it really seems like we can't agree on terminology or ???

% fdisk -l /dev/sda

[...]

  Device BootStart   EndBlocks   Id  System
/dev/sda1 1 2 16033+  83  Linux
/dev/sda2   * 3   263   2096482+  83  Linux
/dev/sda3   264   276104422+  83  Linux
/dev/sda4   277  1106   9755  Extended
/dev/sda5   277   340514048+  83  Linux
/dev/sda6   341   353104391   82  Linux swap
...
/dev/sda11 1013  1106755023+  83  Linux

parts #5-#11 are included in #4


 

And Windows allows for 4 primaries, not 3. So a mixed system or a 
migrators system will have a mess.

You are using SCSI, me IDE also.

fdisk -l /dev/hda

Disk /dev/hda: 255 heads, 63 sectors, 9729 cylinders
Units = cylinders of 16065 * 512 bytes

  Device BootStart   EndBlocks   Id  System
/dev/hda1   * 1  1021   8201151   83  Linux
/dev/hda2  1022  9729  69947010f  Win95 Ext'd (LBA)
/dev/hda5  1022  1071401593+  82  Linux swap
/dev/hda6  2960  3980   8201151   83  Linux
/dev/hda7  1072  2959  15165297   83  Linux
/dev/hda8  3981  5313  10707291   83  Linux
/dev/hda9  5314  8513  25703968+  83  Linux
/dev/hda10 8514  8901   3116578+  83  Linux
/dev/hda11 8902  9729   6650878+  83  Linux

Partition table entries are not in disk order
[root@ root]# fdisk -l /dev/hdb
omitting empty partition (5)

Disk /dev/hdb: 255 heads, 63 sectors, 4865 cylinders
Units = cylinders of 16065 * 512 bytes

  Device BootStart   EndBlocks   Id  System
/dev/hdb1   * 1   648   5205028+  83  Linux
/dev/hdb2   649   698401625   82  Linux swap
/dev/hdb3   699  4865  33471396f  Win95 Ext'd (LBA)
/dev/hdb5   700  1606   7285414+  83  Linux
/dev/hdb6  1607  2368   6120702   83  Linux
/dev/hdb7  2369  4865  20057121   83  Linux
[root@ root]# fdisk -l /dev/hdd

Disk /dev/hdd: 255 heads, 63 sectors, 7297 cylinders
Units = cylinders of 16065 * 512 bytes

  Device BootStart   EndBlocks   Id  System
/dev/hdd1 1  1021   8201151b  Win95 FAT32
[root@ root]#

where anything based on DOS or Windows sticks the extended is based on 
how many Primaries there are:

What fdisk saw on theHD after diskdrake was done as I described was:
hda1 /
hda4 Extended
hda5 /cookermirror (type unknown)
as in /etc/fstab
but hda5 was unformatted and marked as Ext2 when I told Diskdrake to use 
Ext3

here is the /etc/fstab

[root@ root]# cat /etc/fstab
/dev/hdb1 / ext3 defaults 1 1
# /dev/hda5 /Cookermirror ext3 noauto 1 2
none /dev/pts devpts mode=0620 0 0
/dev/hdb7 /home ext3 defaults 1 2
none /mnt/cdrom supermount 
dev=/dev/scd0,fs=auto,ro,--,iocharset=iso8859-1,codepage=850,umask=0 0 0
none /mnt/floppy supermount 
dev=/dev/fd0,fs=auto,--,iocharset=iso8859-1,sync,codepage=850,umask=0 0 0
/dev/hdd1 /mnt/hd auto 
user,iocharset=iso8859-1,kudzu,codepage=850,noauto,umask=0,exec 0 0
/dev/hda1 /newslash ext3 defaults 1 2
none /proc proc defaults 0 0
none /tmp tmpfs defaults 0 0
/dev/hdb6 /usr ext3 defaults 1 2
/dev/hdb5 /var ext3 defaults 1 2
/dev/hdb2 swap swap defaults 0 0
[root@ root]#

The commented line is what I had to pull to get the machine to boot past 
an ext2 fsck that said it could not find a superblock when I tried to 
boot the machine into Linux.

BTW, Supermount WORKS on this P4 box, even in stock Mandrake 9.0.

I was trying to use Diskdrake from the GUI when this happened, as any 
newbie would.

John.









Re: [Cooker] diskdrake prob followed by maint session problem withsolution

2003-01-16 Thread John Danielson, II
Pixel wrote:


"John Danielson, II" <[EMAIL PROTECTED]> writes:

 

Something that just happened to me made me think that documenting a particular
recovery process would help many people:

How to get your /etc/fstab file edited from a floppy boot when your
partitioning is set up to have a separate /usr part:

Go into maintenance shell, as the e2fsck fails due to it thinking from the
/etc/fstab that a partition is /dev/hda5 when it is /dev/hda6 (or some such
radically wrong number, part 5 should always be the extended part table).
   


[...]

 

Just a thought, but could flesh out the procedure if wanted for newbie to know
how to edit /etc/fstab from what a floppy boot drops to when an unrecoverable
bad superblock error is triggered by diskdrake assigning /dev/hda5 to first
extended part and not allowing for the extended part table(and then erroring
as it is created, but still offering to write the /etc/fstab, which I did let
it do last night at 1 AM). diskdrake defaults optional things like
/cookermirror to extended\logical type, but fails to set up an exclusion of
part 5 for the extended part table and writes a /dev/hda5 entry in /etc/fstab
for the new part if it is the first logical created on a physical disk--
sheesh. Then it decides the extended part table has a bad superblock because
is trying to use it as a partition that can be read to and written to directly.
   


i'm missing something. what is this "part 5 being special"?


 

Any system that has EVER had a file system with Windows or DOS on it has 
the following part structure.

Part #s 1-4 can be primary.
Part #5 is always an extended part table to hold logical drives.
Parts 6 and up can be logicals.

Anyone with a multiboot box which has windows, or who never wiped the HD 
to retain data they wanted to still use with that data on FAT or FAT32 
parts will end up using partition managers based on what they have. 
Things like PM 8, PM 7, anything based on a FAT O/S host, will indeed 
renumber a part 5 to 6 and encapsulate it in a part 5 that is a table 
showing start and end points of the logical drives within the extended 
partition.

Relevance to us??? We have one HECK of a lot of migrators who like the 
GUI of Mandrake better than RedHat or others.

Even Ranish Part does this, when you tell it you want a logical part it 
builds an extended shell for the logical, then builds the logical inside 
it. Diskdrake does not, and this is a migration issue not a pure Linux 
only issue-- but how many of us are discussing growth, the need for 
revenue, and the need to meet the needs of migrators to get more users???

Diskdrake offers a preference, and lists logical and primary. When I try 
to build a second part on a drive with one primary part, and the part 
name is one I type in, the following happens:

1. Part shows in display of parts as second part in line (fine, but I 
did not tell ti what kind, I let it default to whatever). I have told it 
type Ext3FS.
2. When I then tell it to format, it says you have to reboot before you 
can do this.
3. When it asks if you want the changes written to /etc/fstab, what will 
a newbie do??? Say ok, let it do that, probably-- nothing obvious tells 
him not to, he does not know the reason for or consequences of the 
failure to format.
4. Now, we have  a problem-- the part table has a begin and end mark for 
an Ext type part (but everything I can use other than Diskdrake says it 
is actually a marked as type EXt2 in the part table itself on HD, not an 
Ext3 and /etc/fstab got written as if the part was there and valid as a 
type Ext3 as part 5(it assumed logical type, used part 5)).
5. So, newbie then gets out his faithful floppy bootable toolkit, the 
one he knows how to use-- the one that has DOS based Part tools in it.
6. He looks at his part, sees his tools not only think is wrong type, 
but that they will not format it, because no extended part table 
surrounds it. None of those tools have the ability to slightly relocate 
the existing part, encapsulate in an extended table, and make the table 
unnumbered, they all number it 5 in the master part table and do a chain 
pointer to begin of extended part table as begin of part 5 which to 
their eyes has no data except that table for logicals. So, he wipes it 
and reboots and runs into this catch 22 where fstab is now out if sync, 
or he creates the part in an extended as a logical and then the extended 
table start point ends up being primary 5 in the resulting part table, 
but Linux at boot is looking  still for a data part in 5 because the 
fstab got written for a part that no longer exists.
7.  Linux runs Ext2fs, Ext2fs fails because the extended part TABLE has 
no superblock and therefore it MUST be invalid.
8.  Boot fails, newbie is caught in the catch 22 I proposed a document 
solution to get out of.
9. I, as  a migrating newbie, lost about 300 hours of time (and about 5 
GIG of data 6 times) figuring out what the heck w

[Cooker] diskdrake prob followed by maint session problem with solution

2003-01-16 Thread John Danielson, II
Soemthing that just happened to me made me think that documenting a 
particular recovery process would help many people:

How to get your /etc/fstab file editted from a floppy boot when your 
partitioning is set up to have a seperate /usr part:

Go into maintenance shell, as the e2fsck fails due to it thinking from 
the /etc/fstab that a partition is /dev/hda5 when it is /dev/hda6 (or 
some such radically wrong number, part 5 should always be the extended 
part table).

type

/bin/cat /etc/fstab

find which part has /usr and mount it

now type

/usr/vi  /etc/fstab

OR type

/usr/emacs-nox /etc/fstab

comment out the offending part spec.

POINT, you might be dropped in a maint shell and have a situation where 
your file editors are in /usr and /usr is not mounted and you need to 
figure out what part /usr is on to mount it.

SUGGESTION:

Stick an editor in /bin and document which one it is(vi would work, if 
man were accessible easily from a / only mounting in a maint shell). 
Most newbies do not know what usually is in the part of the / subtree on 
/ part by default and quite a few read the NGs and are told to separate 
out /usr.

I am also printing this for myself.

Just a thought, but could flesh out the procedure if wanted for newbie 
to know how to edit /etc/fstab from what a floppy boot drops to when an 
unrecoverable bad superblock error is triggered by diskdrake assigning 
/dev/hda5 to first extended part and not allowing for the extended part 
table(and then erroring as it is created, but still offering to write 
the /etc/fstab, which I did let it do last night at 1 AM). diskdrake 
defaults optional things like /cookermirror to extended\logical type, 
but fails to set up an exclusion of part 5 for the extended part table 
and writes a /dev/hda5 entry in /etc/fstab for the new part if it is the 
first logical created on a physical disk-- sheesh. Then it decides the 
extended part table has a bad superblock because is trying to use it as 
a partition that can be read to and written to directly.

John.






Re: [Cooker] install : automatic logon should be told "not recommended"

2003-01-15 Thread John Danielson, II
Pixel wrote:


"John Danielson, II" <[EMAIL PROTECTED]> writes:

 

(which is what the login to KDE does) but DO go to the X-gui'd login. The
first 10 installs I made of Mandrake got wiped because the video settings for
X were scragged and I did not know how NOT to autoad KDE.
   


in the old recommended mode, it was that way when it was decided
"safe" to have X without asking.

 

Just perspective. Wish list for longer term-- ask if the user has used Linux
before first thing in install, then do certain things like forced\defaulted
gui'd login but not a force\default to desktop if answer is no, and be more
verbose about choices and logic for choosing if no or offer to show a tutorial
(and recommend seeing it) before installing.
   


the current trend is to remove the "recommended" install and have the
option to choose expert choices in the dialog boxes (using the
"Advanced" button).

alas, this change impacts quite a lot of things... hopefully in the
end there will be both freedom-of-choice and ease :-/


 

Actually, usually was able to get to the login if the X login was used-- 
it was a VESA video mode login. The problems I had came when the desktop 
manager did a mode and resolution shift (or X did) that caused a 
different pick from the refresh table, and the acceptable monitor ranges 
were out of bounds-- in one case, 2 KHz out of range for horizontal sync 
totally TRASHED display as the system load progressed and desktop inited.

Since one can get to console from the X login screen a few ways, one 
does not need the option to autoload a desktop at all in the installer, 
IMHO. Simply set the X login to a lower res and color depth that is VESA 
if the video test failed-- branch past that setting of res only IF the 
video test suceeded. most video cards still in use can handle 
640x480x256 (8 Bit) color, so poke a default like that,  
overwrite\replace after video test suceeds. No video test, default to 
fail action.  A lot of pre-1996 monitors have a lack of a good versatile 
800x600x16 bit mode set, and those things last so long if well treated 
that there are lots of them handed down and in use.

Doing just that would eliminate the hardest thing for many newbies to 
grasp and work around-- video failure during boot(as THEY see it, boot 
ends when desktop is up and running).

I agree about the recommended part, but the basic assumptions need to be 
filled in if the advanced button is not selected and choices not 
completed through any needed choice testing. Default minimal until 
better tested, insofar as video goes. I would myself just change 
recommended to basic or SAFER.

John.






Re: [Cooker] install : automatic logon should be told "not recommended"

2003-01-15 Thread John Danielson, II
J. Greenlees wrote:




Pixel wrote:


Christophe Combelles <[EMAIL PROTECTED]> writes:



Matter of ergonomics :

The automatic logon is not a very secure feature.




[...]



Either : Add the string "(not recommended)" just after the string 
"do you want
to use this feature", to give the good advice,

Or better : replace the two buttons "YES" and "NO" with two radio 
buttons
"yes" and "no". The radion button enabled by default should be "no". 
And add a
standard "next" button.
So the user which does not understand this feature will just click 
on "next"
and won't have this feature enabled, which is a good choice.



i agree the ergonomics of this box is no good.

but i do not agree this is that unsafe.

i'd agree to add "(not recommended)" iff the user has a
password-secured bootloader. and in that case, it's even better not to
propose autologin :)



for people new to linux from windows, the automatic login is what 
windows gives them.
for single user home use it may not be as much a risk, which is where 
linux will have to get people from windows to expand user base.

would definitely put a "not recommended for business/company/corporate 
computers" tag in. though most network admins should know that anyway.

been discussing in a forum about linux/ windows, most windows users 
won't switch until point and click ui is all they have to deal with.

maybe a single cd version set up for complete new users that gives 
them the mushroom treatment windows users are used to from ms. no 
options to speak of during install, no choice in ui, and set to 
runlevel 5 after install with automatic login. this would allow 
un-informed windows users to check Mandrake out in a way they are used 
to being treated. ;)
(though I would recommend against completely removing their windows 
partitions during the install, even though windows would demand that 
any other partitions be rebuilt.




As a Windows user from 3.0 up, AND as a Linux user for a couple years, I 
can tell you that what Windows users are used to is a graphical login, 
but do not need an autologin straight into a desktop for the most part 
in order to be comfortable. My Mandrake and Redhat installs do NOT go to 
a desktop autoload (which is what the login to KDE does) but DO go to 
the X-gui'd login. The first 10 installs I made of Mandrake got wiped 
because the video settings for X were scragged and I did not know how 
NOT to autoad KDE.

Just perspective. Wish list for longer term-- ask if the user has used 
Linux before first thing in install, then do certain things like 
forced\defaulted gui'd login but not a force\default to desktop if 
answer is no, and be more verbose about choices and logic for choosing 
if no or offer to show a tutorial (and recommend seeing it) before 
installing.

John.




Re: [Cooker] gcombust - wrong written amount bad directories in image

2003-01-15 Thread John Danielson, II
Lyall Pearce wrote:


I like using gcombust but ever since mdk 8 (it used to work in mkd 
7.2), it has not quite functioned correctly.
The progress window of a burn is off. (1mb of 5.8mb instead of 10mb of 
580mb for example)
It does not affect the operation of the program, it just detracts from 
the whole experience - particularly if you are showing someone how you 
burn CDs.
I checked the rpms and there do not seem to be any updates I have found.

gcombust-0.1.52-1mdk
mkisofs-1.15-0.a32.1mdk
cdrecord-1.11-0.a32.amdk

Thanks for any help.

...Lyall



Yes, my gCombust does similar things. The third digit (1s digit) of the 
MBs burn of is missing, and the second digit (10s digit) of the total is 
missing-- but only on the dialog=type child window. The lower layer 
messages in the message pane in the main window show the right figures 
when things are complete. And the burns are great. This happens in both 
KDE and Gnome on my box.

John.





Re: [Cooker] Prepare for the onslaught.

2003-01-11 Thread John Danielson, II
Buchan Milne wrote:


On Sat, 11 Jan 2003, [iso-8859-1] G?tz Waschk wrote:

 

Do we really want a distro that will install on fewer machines than
Windows XP, Redhat 8.1, SuSE 8.2, Lycoris, Lindows and Solaris 9
Intel???
 

No, but you still can install from network or hd.
   


True, but chances are that if a user has a CD-ROM drive that won't read a
700MB ISO, hd install may not be that easy (first have to download the
files which can't be read from the CD, or the whole tree, in both
cases assuming there is sufficient space on the hard disk).

 

But if this problem
is easily solvable, it should be done.
   


Warly??? What says Mandrakesoft? (Or is there anyone else not convinced
700MB ISOs are a bad idea?)

(Of course, for betas which ship only one ISO, 700MB ISOs are probably ok,
since the user probably had to download the ISO anyway, and could do an HD
install from the ISO, in fact I plan on doing that today if I have time.
But beta testers are usually better customers than boxed-set buyers)

Buchan

 

Buchan:

There are three ways around this that I can think of:

Any burner can also read, and read CDs as big as it can burn, and read 
every format it can burn. The last three times I stuck Mandrake into a 
box, it was by using the burner to read the CDs it had burnt many days 
before.

Any DVD player can read CDs also.

A floppy boot image could be modified so all files from CD were 
batch-copied to HD, as a tree. Then the boot from the  revised floppy 
image cut to floppy will bypass the pure boot issue totally.

Pentium class machines, which Mandrake is tuned to, yes??, generally are 
recent enough to have recent HDs. If, then, they cannot boot to CD at 
all, the user will probably find he has either a dirty CD media, a dirty 
CD laser lens head, a dirty reflecting mirror inside drive, a bad cable, 
or a bad stick of RAM in the box, or that the jumpering of CD or HD is 
wrong-- 99% of Pentium class boxes CAN boot from floppy if a very old 
CD-ROM drive was not grandfathered into the box and a decent cable.

Way 4-- borrow a CD-ROM drive temporarily from another box, or install 
Mandrake on the HD that belongs on the target box in a box with a Cd-ROM 
drive that can boot.

Let's say, for example, that we went to 4 download images at 650 MB. not 
only does one than have more to download because of the TOC needed in 
each archive being one more than if the set were fit onto 3 700 MB 
images, but the likelyhood of four download sessions instead of three 
increases the likelyhood of needing to redownload one ISO and also the 
time to check increase because now there are four ISO to check. I would 
offer a set of 650's as well as a set of 700's, but for shipment or club 
only, and make it a slightly more limited set and stated as such (3 CDs 
only). The rest can be grabbed on the web, yes those who have read 
capability for the bigger archives can grab bigger archives adn be happy 
with a more fully fledged set of files they know are good, and those who 
choose to rely on the web can take the chance of repeated reacquisition 
of archives made needful due to the fact that ftp can be locally or 
remotely fallible, or fallible in transit.

John.







[Cooker] confirm 9f6c1768ded85e0807f19d3d5b27f7d9

2003-01-06 Thread John Danielson, II


Guillaume Rousse wrote:

I'm unable to print a complete document at once.

Printer output 20 first pages, then stop. I've tried to print following 
page by specifying a range in xpp, but all i got are two to six pages 
bunch each time, whereas full document is 196 pages long...

Document is a pdf file converted to ps by pdf2ps.



Guillame,

This may at first sound dumb-- BUT, the PDFs I print take up huge 
amounts of RAM and it looks like CUPS is not calling for swap memory as 
needed, or ghostscript is not, or the lpd is not. I typically run into 
this when top says that I have less than ten MB RAM open (of 1 GIG) and 
find that resetting cups by force fixes:

service -f cups

About 7\8 of the time, every apparently hung job then merrily comes out 
of whichever of my my printers it is sent to. I think this may be at 
least partly a RAM and lpd issue, not a pure CUPS issue(though cups 
locks, it may not be code in cups itself, it may simply be seeing a 
paused printer as lpd hangs for lack of work space in RAM). Can't prove 
it, but the same things for the same reasons have happened in a lot of 
other operating systems and on other platforms and there sometimes the 
PORT driver had to be unlocked by reinitializing and things then 
sometimes continued.

I have gone into top and found mutliple instances of:

parallel
cups
lpr

running when this happens, and usually fully restarting the cups service 
as above fixed this also usually.

John Danielson.

--- Begin Message ---

Guillaume Rousse wrote:


I'm unable to print a complete document at once.

Printer output 20 first pages, then stop. I've tried to print following page 
by specifying a range in xpp, but all i got are two to six pages bunch each 
time, whereas full document is 196 pages long...

Document is a pdf file converted to ps by pdf2ps.

 

Guillame,

This may at first sound dumb-- BUT, the PDFs I print take up huge 
amounts of RAM and it looks like CUPS is not calling for swap memory as 
needed, or ghostscript is not, or the lpd is not. I typically run into 
this when top says that I have less than ten MB RAM open (of 1 GIG) and 
find that resetting cups by force fixes:

service -f cups

About 7\8 of the time, every apparently hung job then merrily comes out 
of whichever of my my printers it is sent to. I think this may be at 
least partly a RAM and lpd issue, not a pure CUPS issue(though cups 
locks, it may not be code in cups itself, it may simply be seeing a 
paused printer as lpd hangs for lack of work space in RAM). Can't prove 
it, but the same things for the same reasons have happened in a lot of 
other operating systems and on other platforms and there sometimes the 
PORT driver had to be unlocked by reinitializing and things then 
sometimes continued.

I have gone into top and found mutliple instances of:

parallel
cups
lpr

running when this happens, and usually fully restarting the cups service 
as above fixed this also usually.

John Danielson.




--
Your favorite stores, helpful shopping tools and great gift ideas. 
Experience the convenience of buying online with Shop@Netscape! 
http://shopnow.netscape.com/




--- End Message ---


Re: [Cooker] bugzilla and bugstatus

2003-01-02 Thread John Danielson, II
Quel Qun wrote:


On Thu, 2003-01-02 at 17:16, Steffen Barszus wrote:
 

Hi !

I wonder how many votes a bug needs to get confirmed status, and how I can 
influence a bug to be confirmed. I've reported some bugs some time ago and 
the still are in status unconfirmed. As long as they are unconfirmed they are 
ignored right ? 
I'm namely interested in bugs 634-636. So if someone can state on this ... ?!

   

It needs one vote to be confirmed and its status switched to new.
 

And how does one take the verbal confirm as comment one of bug 634 as of 
14.12.02 and tell the person to please vote??? that person suggested 
pushing it to "confirmed" as they knew it existed since version 7.2. I 
would like to know how to vote also, please???





[Cooker] Ping Till-- ML-1210 defaults....

2003-01-02 Thread John Danielson, II
Please update the following:

defaults for the ML-1210 Samsung, using "gdi" are as follows (only 
things that print on the align.ps that is now on linuxprinting.org that 
had to be altered to get mine working, 350 pages later are shown, other 
variables correct).

MFR says:

ml 12.02
mb 12.02
mr 12.02
mt 12.02

and with this the random locks that require a service -f cups and a hard 
printer power cycle to overcome disappear, but:

printing anything piped to lpr in console prints shifted left by a 
bunch-- I used man pages to get the left alignment approximate, 
alternating with the alignmargins script you posted on 
linuxprinting.org. (downloaded 30.12.2002),  and had the following m 
variables when I called it quits:

Margins (x,y) -79.01, -77.01
ml-mt Same as mfr above.

This yields perfect positioning from anything in X\KDE and a slight 1\2 
char dropout on left side of any man page for the outdented header and 
subheader lines only. The rules show I am getting an effective 600x780 
printout area on page with all margins (physical print area) varying 
from each other less than 1\64th" and the rotational skew is zero this 
way. I have the bottom arrows not quite square to bottom of printed 
corners, and the scale says the bottom printed edge would be _below 
bottom_ of my physical US letter pages (which are physically 21.75 cm by 
28.00 cm) by .2 cm if the margin of physical print at bottom were not 
.5cm or about 5\64". Was this align.ps calibrated for an A4 page of 
paper??? Or a Legal size piece of paper current calibration needs to 
be worked on. I was calibrating at 600x600, which is highest density 
this printer can handle. hookup of the Samsung ML-1210 was to /dev/lp0 
and not /dev/usb/lp0 or lp1 (my Stylus likes /devusb/lp0 adn cUPS and 
lpr go nuts when two drivers are hooked to same physical port driver, so 
the stylus gets the usb so I can use a 2 M long cable with it-- the 
Samsung is about 2.75 M away from main computer box location, so am 
using an IEEE1284 ~3 M (10 feet) with the Samsung that is a Belkin 
twisted pair solution for low signal loss)

This page also printed this tall on my Epson stylus C80, so either we 
have a tib of vertical height exaggeration to deal with or the align.ps 
page is too high by a tib (my Stylus just used a zero top edge margin, 
it can print topedge-to-bottomedge under right circumstances (1440x720, 
but not highest quality submode).

With the default settings of all zeros for the margins as given in the 
included-with-MDK 9.0 ppd for this printer, the align.ps prints exactly 
once with the output rotated about 5 degrees clockwise before the 
printer locks(lock solution-- reboot or restart cups AFTER power cycling 
printer(I finally copied the mfr's ppd from the mfr's driver CD to the 
HD, and renamed it Printer.ppd) as this is my default printer. BTW, I 
had to copy align.ps to the same directory as alignmargins to get 
alignmargins to run, the line that included Find "aelign.ps"(the ae was 
a Latin special character ae) needless to say did not work at all until 
modified to find "align.ps" with the file to be found in the same 
directory as alignmargins. (/usr/sbin is where old one was, new one got 
stuck in after old one got mv'd to be oldalign).

If this is the wrong place for this, let me know what email you want it 
sent to, OK? i figured this needed some rebrewing

Nicely done other than vertical aspect of align.ps and also the ML-1210 
stock base specs.

John Danielson.