Re: 3.0.18 testing needed
Will you add i18n for jp? Or do they build special bf anyways? Just curious. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: 3.0.18 testing needed
On 16-Dec-2001 Adam Di Carlo wrote: > "Sean 'Shaleh' Perry" <[EMAIL PROTECTED]> writes: > >> Will you add i18n for jp? Or do they build special bf anyways? Just >> curious. > > The i18n builds do include Japanese support. Is that what you were > asking about? > en pt de pl fr es ja sv it hu no jp there -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: 3.0.18 testing needed
>> >> en pt de pl fr es ja sv it hu >> >> no jp there > > What do you think ja is ? > java? dunno -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
confusing message during disk format
During install there is a question that asks: "Would you like me to not check the drive for errors?" or something real close. It defaults to Yes and skips the lengthy drive check. My problem with this message is that it is very confusing. It should read: "Would you like the drive to be checked for errors?" and default to No. I can make this a bug if that is easier. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: confusing message during disk format
> > Ugh.Unfortunately, the YesNoBox doesn't support defaulting to No. > Can't we just change the wording maybe? > I am trying to avoid an action, yet clicking yes? That is plain wrong. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: regarding xviddetect
This is all moot if we move to X 4. X does it own monitor / vid card detection now. So, for potato, as much work as we see fit should go there. For woody, let's help Branden get Xfree 4 working. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: regarding xviddetect
On 21-Aug-2000 Wichert Akkerman wrote: > Previously Sean Perry wrote: >> This is all moot if we move to X 4. X does it own monitor / vid card >> detection now. > > I wonder if it doesn't make more sense to use a mixed X3/X4 setup for > woody and base the decision on which server to use on the installed > videocard? > by woody release (at least 6 - 8 months) Xfree 4 should be safe enough for everyone to use. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
RE: regarding xviddetect
On 21-Aug-2000 Adam Di Carlo wrote: > > I know there are still plenty of video cards that xviddetect does not > detect. I can see a lot of bug reports to that effect. > > I think it would be worthwhile to maintain a branch of xviddetect so > that anXious could know about more videocards which get updated at > Potato point releases. Do you agree? > so here is the break down: current cards are supported in XF 4. Older cards (ISA) are likely to not be supported unless they are popular. The driver has to be ported )-: So, this means we have a process like: try to XF 4 autodetect if fail try to XF 3 autodetect if fail punt? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
RE: BRAILLE IMPLIMENTATION AT BOOTUP.
On 06-Oct-2000 [EMAIL PROTECTED] wrote: > > Hello!! > I am one of those blind guys that wish it would be posible to boot linux > and have a view of whats happening from the first time to the last. > NOw i am only posible to use the brailledisplay at consolemode. > I know someone here was writing to the blinux-list but there were no > answers. > It seems that no one at the blinux-list is interessted in braillesupport > at boot and installation. > /Anders. > this sounds like a very interesting task. To try to accomplish it would require a programmer who can either read braille or lives near a linux using blind person who is willing to assist in the debugging. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#75505: base: mod(utils?)conf should not overwrite /etc/m
On 24-Oct-2000 KoV wrote: > Package: base > Version: 20001024 > Severity: normal > > I think modules.conf should not be overwritten on an upgrade of it's utils > I always lost every configuration I have done for my soundcard and my isdn > modules whenever I upgrade to new versions of modutils (modconf?) shouldn't > it be put at conffiles ;)? > /etc/modutils/foo. You put your changes there and update-modules reads it and autogenerates the modules.conf and what not. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
FW: Comments from a first-time Debian install.....
From: [EMAIL PROTECTED] I'm not on any of the Debian developer's mailing lists yet, and I didn't want to send this to some inappropriate place. (I'd really rather not replicate RMS's drive-by flaming on the tcl list from a few years ago. :-) However, I thought some Debian developers might appreciate these notes which I took as I tried for the first time to actually install Debian from scratch, as opposed to using apt-get on a system which someone else had set up for me. These notes were taken from a perspective of a Linux expert, but someone who's still relatively new to Debian install procedures. I've tried to add some comments about how a novice would react when presented with some of the challenges I faced, though, and I think the bottom line is that Debian's install has gone a long way from when Marc helped me install Debian 2.0 back in June, 1999. But if I needed to give my parents or some other non-technical friends/relatives a Linux distribution to install, it wouldn't be Debian; Red Hat or Caldera simply have much friendly install systems. Feel free to forward this (or pieces of it) wherever it might be appropriate. - Ted Comments on Debian 2.2 install === (This is my first time installing Debian unasisted. The first time was with Debian 2.0, with Marc Merlin doing the install of the base system, and my being left to answer the hundreds of questions with no way of getting back to the question, and being asked many, many times where the newserver was. Glad that's no longer a problem.) The debian install is much better than when I first saw it, but it still has a lot of rough edges. Having tried Red Hat and Caldera's installers, Debian still has a long way to go before a novice user won't be intimidated by the install process. Initial setup = Far, far too many decision points. It's good to give flexibility to the expert, but for most users it's too much. Suggestion: have a "basic" and "expert" modes, where the "expert" mode eliminates some of the decision points, and have a "back" button!!! Having a nice flow where you can either initialize another partition, or go on --- and then having experimented with a choice, go back to a previous choice point is very sound and basic UI desing principles. There's a reason why Microsoft Wizards are appreciated by novice users; Debian should take advantage of their millions spent in UI research. Another UI point. With three choices in the first few screens, it will make it much more obvious which button is selected. Because the background around each dialog box is blue, with blue meaning "highlighted" and "red" meaning not highlighted", it's not clear which is which. For a while I thought "red" meant highlighted I won't go into the X versus non-X installation, since there are some real tradeoffs here, except to say that this kind of "warm and fuzzy" thing certainly makes a difference with novice users. The first time I did an initial install, PCMCIA was not configured properly. I have a Vaio 505TX, and this kind of PCMCIA CD-ROM install has been problematic before with other distributions. It was able to boot from the PCMCIA CD-ROM; that part worked fine. However, it bombed out trying to find the kernel and modules. I tried for a while, but it appears there's no way to support that directly from the CD-ROM given my hardware configuration. So I booted back into Windows, created a scratch partition, and copied the entire Debian Potato 2.2 Binary-i386 R0 CD-ROM into that scratch partition and then tried again. The second time I tried, I was able to load the kernel modules. This screen here really needs simplifying. There's no reason to make the user decide which modules should be loaded on a full system at such an early point in the install. Regardless of where you fall on the "modules should be dynamically loaded" versus the "modules should be statically loaded at boot-time" argument, at the initial install time only those modules which are desperately needed to install the system should be asked for. If nothing else, deferring this means that the installation system may have more resources at its disposal to provide a more friendly interface to the user. On this second install attempt, for some reason PCMCIA wasn't happy. I did try to configure it, but it failed for some mysterious reason. It didn't give any clear indication that PCMCIA had failed until later, when the second install bombed out and I started investigating... However, because it bombed out, it wasn't able to find the CD-ROM automatically. So the system went into what I later discovered was apt-setup, where one of the questions it asked me was whether I wanted the non-free software or not. I said yes, but given that CD-1 (which I had copied onto a spare partition) doesn't have non-free software, the debian configuration system bombed out that that
