NewWorld Blue White Mac Powerpc install -- problems with firewire and aec62xx driver.
Package: installation-reports INSTALL REPORT Debian-installer-version: Fill in date and from where you got the image Index of /pub/cdimage-testing/daily/powerpc/current Name Last modified Size Description Parent Directory 22-Sep-2004 00:26 - MD5SUMS22-Sep-2004 00:26 1k sarge-powerpc-businesscard.iso 22-Sep-2004 00:20 153M sarge-powerpc-netinst.iso 22-Sep-2004 00:26 310M Apache/1.3.31 Server at cdimage.debian.org Port 80 uname -a: The result of running uname -a on a shell prompt Linux bluemac 2.6.8-powerpc #1 Fri Aug 27 18:02:26 CEST 2004 ppc GNU/Linux Date: Date and time of the install Noon September 22, 2004 US East Coast time Method: How did you install? What did you boot off? If network install, from where? Proxied? Booted netinst CD directly At Yaboot prompt, specified: expert-powerpc video=ofonly Not proxied Machine: Description of machine (eg, IBM Thinkpad R32) Apple PowerMac Blue and White G3 - Rev A (before IDE chip was fixed) Processor: G3 300 MHz Memory: 384 Mbyte Root Device: IDE? SCSI? Name of device? /dev/hdc -- 6.4 GB IDE disk on the Mac motherboard IDE controller Root Size/partition table: Feel free to paste the full partition table, with notes on which partitions are mounted where. # mac-fdisk -l /dev/hdc /dev/hdc #type name length base ( size ) system /dev/hdc1 Apple_partition_map Apple63 @ 1( 31.5k) Partition map /dev/hdc2Apple_Driver_ATA Macintosh54 @ 64 ( 27.0k) Unknown /dev/hdc3Apple_Driver_ATA Macintosh74 @ 118 ( 37.0k) Unknown /dev/hdc4 Apple_Driver_IOKit Macintosh 512 @ 192 (256.0k) Unknown /dev/hdc5 Apple_Patches Patch Partition 512 @ 704 (256.0k) Unknown /dev/hdc6 Apple_Bootstrap boot 195313 @ 1216 ( 95.4M) NewWorld bootblock /dev/hdc7 Apple_UNIX_SVR2 swap 976563 @ 196529 (476.8M) Linux swap /dev/hdc8 Apple_UNIX_SVR2 root 11421868 @ 1173092 ( 5.4G) Linux native Block size=512, Number of Blocks=12594960 DeviceType=0x0, DeviceId=0x0 Drivers- 1: @ 64 for 21, type=0x701 2: @ 118 for 34, type=0xf8ff # mount /dev/hdc8 on / type ext3 (rw,errors=remount-ro) proc on /proc type proc (rw) sysfs on /sys type sysfs (rw) devpts on /dev/pts type devpts (rw,gid=5,mode=620) tmpfs on /dev/shm type tmpfs (rw) usbfs on /proc/bus/usb type usbfs (rw) # Output of lspci and lspci -n: # lspci :00:00.0 Host bridge: Motorola MPC106 [Grackle] (rev 40) :00:0d.0 PCI bridge: Digital Equipment Corporation DECchip 21154 (rev 02) :01:00.0 FireWire (IEEE 1394): Texas Instruments PCILynx/PCILynx2 IEEE 1394 Link Layer Controller (rev 02) :01:01.0 IDE interface: Silicon Image, Inc. (formerly CMD Technology Inc) PCI0646 (rev 05) :01:02.0 VGA compatible controller: ATI Technologies Inc 3D Rage Pro (rev 5c) :01:03.0 SCSI storage controller: Adaptec AHA-7850 (rev 03) :01:04.0 SCSI storage controller: Artop Electronic Corp ATP865 (rev 06) :01:05.0 ff00: Apple Computer Inc. Paddington Mac I/O :01:06.0 USB Controller: OPTi Inc. 82C861 (rev 10) # lspci -n :00:00.0 0600: 1057:0002 (rev 40) :00:0d.0 0604: 1011:0026 (rev 02) :01:00.0 0c00: 104c:8000 (rev 02) :01:01.0 0101: 1095:0646 (rev 05) :01:02.0 0300: 1002:4749 (rev 5c) :01:03.0 0100: 9004:5078 (rev 03) :01:04.0 0100: 1191:0009 (rev 06) :01:05.0 ff00: 106b:0017 :01:06.0 0c03: 1045:c861 (rev 10) # Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot worked:[o] Configure network HW: [o] Config network: [o] Detect CD: [o] Load installer modules: [o] Detect hard drives: [e] Partition hard drives: [e] Create file systems:[o] Mount partitions: [o] Install base system:[o] Install boot loader:[o] Reboot: [o] Comments/Problems: Description of the install, in prose, and any thoughts, comments and ideas you had during the initial install. Note 1: Booting without video=ofonly resulted in a scrambled screen. Note 2: Had to manually specify bmac ethernet interface. Note 3: This machine has two IDE disk drives. One (6.4 GB) is connected to the on-board IDE controller. The other one (180 GB) is connected to a SIIG Ultra ATA 133/100 PRO for Mac IDE
Re: newt and slang issues
On Wed, Sep 22, 2004 at 12:37:52PM +0100, Alastair McKinstry wrote: I will upload the slang change to testing-proposed-updates as soon as the sid package is accepted into the archive; is the newt translation significant enough for t-p-u ? Please upload to unstable only; the release team can push the package to testing from there once it's built on all archs. Ok, I won't upload then. Should the bugs be re-opened then and tagged RC and sarge to track this? Sending a quick note to debian-release is usually sufficient. The current console-tools, console-data, console-common in sid fix RC issues and should be pushed into sarge. The first two of these are being pushed in; I'll look at console-common tomorrow. Cheers, -- Steve Langasek postmodern programmer signature.asc Description: Digital signature
Re: Two Macedonias
siward wrote: I think the people of Greek Macedonia have a different objection : they were always called Macedonia, and now another region is trying to take their name away from them, which is offensive. This makes me laugh. It is possible that the peope of their northernly neighbour state also used to call their region Macedonia. Their republic has only come into existence recently, and this may only have been possible by their perception of them being part of a people that are 'Macedonians', that therefore obviously live in 'Macedonia'. LOL 2) use the names 'Republic Macedonia' and 'Greek Macedonia'. I like that one, but, as Steve Langasek said, in the namespace of autonomous territories, there is no collision at all. Regards, ogi -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#265183: pppoe workaround of the post-reboot problem
Marco has pretty much summed it up. I fail to see though why the modem asking the host to consider the modem the default gateway is a bug. The routing Because the modem is not a gateway and will not work as such? [snip] If the speedtouch DHCP server really provides a default route when it's configured for PPTP tunnels (something which I doubt and I think should be verified) It is a gateway and does work as such. Did I not write in my last e-mail that *without* starting pppoe one can reach the provider's WAN via the default route going via the speedtouch? As for the verification, doesn't the routing table I reported in the 1st mail in the thread suffice? I'll be happy to do any additional verifications if you want. *maybe* pppoeconf could check if the local address is 10.0.0.1 and 10.0.0.138 is the modem: if ping ... 10.0.0.138 \ wget --quiet --output-document=- http://10.0.0.138/welcome.htm \ | grep -q '^HEADTITLEADSL Index'; then echo yes fi Then it would have to check if the PPTP server is enabled. Unfortunately, .138 is the firmware default of my modem, but a lot of folks reconfigure the address; I can also imagine other models using addresses other than .138. As pppoeconf already discovers the modem by its own means, so I don't think the hardwiring saves a lot of coding. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Two Macedonias
On 23 2004 10:39, Ognyan Kulev wrote: siward wrote: I think the people of Greek Macedonia have a different objection : they were always called Macedonia, and now another region is trying to take their name away from them, which is offensive. This makes me laugh. I would really like to know why this looks funny to you, but I'll refrain from starting such a discussion in these lists. If you indeed have a reason, I'd be interested to know it, please mail me privately. It is possible that the peope of their northernly neighbour state also used to call their region Macedonia. Their republic has only come into existence recently, and this may only have been possible by their perception of them being part of a people that are 'Macedonians', that therefore obviously live in 'Macedonia'. LOL Right, it's obvious that you reject his views of the matter. However, I'm not going to trouble the lists with another flamewar on this matter. I think we can all agree that right now the issue is pretty much settled, but it would be best if there were no further insulting comments (I take 'LOL' as one). 2) use the names 'Republic Macedonia' and 'Greek Macedonia'. I like that one, but, as Steve Langasek said, in the namespace of autonomous territories, there is no collision at all. I agree on that one. Konstantinos
Bug#265183: pppoe workaround of the post-reboot problem
On Sep 23, Vassilii Khachaturov [EMAIL PROTECTED] wrote: It is a gateway and does work as such. Did I not write in my last e-mail that *without* starting pppoe one can reach the provider's WAN via the default route going via the speedtouch? Then the modem is configured as a router and you don't need need PPTP at all... Unfortunately, .138 is the firmware default of my modem, but a lot of folks reconfigure the address; I can also imagine other models using Their problem. addresses other than .138. As pppoeconf already discovers the modem by its own means, so I don't think the hardwiring saves a lot of coding. It does not discover the IP address. -- ciao, | Marco | [8119 feRgDBQtRyAFQ] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Two Macedonias
Konstantinos Margaritis wrote: I would really like to know why this looks funny to you, but I'll refrain from starting such a discussion in these lists. If you indeed have a reason, I'd be interested to know it, please mail me privately. I know that the history of Macedonia is taught differently in Bulgaria, Serbia, Macedonia, and Greek. I apologize for the too impulsive reply and I'll try to not make such in the future. Regards, ogi -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: [INTL:bg] Erased Bulgarian translation!
Quoting Dennis Stampfer ([EMAIL PROTECTED]): On Wed, Sep 22, 2004 at 09:57:10PM +0300, Ognyan Kulev wrote: In r21937, I committed improved Bulgarian translation that spans many strings. Now I've just checked out package/po/bg.po and all translation strings are empty! What's going on? Somehow, bubulle's script cleared the file (r21938), and the next run updated it with the .pot correctly: blank file means no translation, so all strings are untranslated. But: your commited file has a error: bg.po:2939: missing `msgstr' section msgfmt: found 1 fatal error maybe that is why bubulle's scripts cleared the file. I corrected it. You have now one untranslated message. Well, some more careful error handling should probably go in l10n-sync. I would appreciate if someone with (sorry to say this again...) more skills than me rewrites some parts of the script in order to have a better error handling. l10n-sync is in scripts/l10n -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Two Macedonias
2) use the names 'Republic Macedonia' and 'Greek Macedonia'. I like that one, but, as Steve Langasek said, in the namespace of autonomous territories, there is no collision at all. Well, in my opinion, if we decide changing FYROM to something in iso-codes (and thus, as a direct consequence, in debian-installer), we should use Macedonia. And, well, I'm pretty sure that most Greek users indeed share this advice. I'm already sure of this for one of them..:) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#272967: Acknowledgement (NewWorld Blue White Mac Powerpc install -- problems with firewire and aec62xx driver.)
I forgot to add: Note 5: Several times during the installation, I got an error message telling me that some modules were not loaded because they could not be found: ide-mod, ide-probe-mod, ide-detect, ide-generic Note 6: I installed the same netinst CD on my beige G3 tower, using BootX as boot loader. This machine also has the SIIG Ultra ATA controller. Curiously enough, I did *not* get timeout /lost interrupt messages on this install. Is it possible that the Beige G3 somehow declares itself to have a slower bus than the Blue White claims, and this causes the driver to use a slower DMA mode -- hence no timeouts? In other words, the Blue White is claiming to have a faster PCI bus than it really can deliver, but the Beige makes no such claims. The Blue and White pays the price for boasting, the Beige reaps the benefits of modesty? Also, curiously, the Beige G3 had no complaints about missing modules... Go figure! Rick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
[l10n] Missing strings in packages/po/bg.po
Hi, I've tested Bulgarian translation of d-i in expert26 and found that the following titles in main menu are not translated: Free memory (low memory install) EVMS module.. SSH... LVM... MD... Moreover, none of the po strings in partman-md are in packages/po/bg.po. (Just search for partman-md in bg.po.) Perhaps other udebs have such defects too. How this can be corrected? Regards, ogi -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
docbook-xml is used before being installed
Hi, I've installed sid snapshot of d-i and selected Desktop is tasksel. Many packages are installed, and at one moment there were vast amount of XML errors printed. It looks like the DocBook DTD is missing while some XML files (like documentation of eog) are processed. Later, docbook-xml is installed. Is this a known defect? Regards, ogi -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Two Macedonias
On 23 2004 11:44, Christian Perrier wrote: 2) use the names 'Republic Macedonia' and 'Greek Macedonia'. I like that one, but, as Steve Langasek said, in the namespace of autonomous territories, there is no collision at all. Well, in my opinion, if we decide changing FYROM to something in iso-codes (and thus, as a direct consequence, in debian-installer), we should use Macedonia. And, well, I'm pretty sure that most Greek users indeed share this advice. I'm already sure of this for one of them..:) Hm, I can't say I'm overjoyed with this choice. If this needs to be changed, I'd prefer the distiction to be made, 'Republic of Macedonia' would be far better and avoid unwanted comments from both sides. Konstantinos
Re: Two Macedonias
Konstantinos Margaritis wrote: On 23 2004 11:44, Christian Perrier wrote: 2) use the names 'Republic Macedonia' and 'Greek Macedonia'. I like that one, but, as Steve Langasek said, in the namespace of autonomous territories, there is no collision at all. Well, in my opinion, if we decide changing FYROM to something in iso-codes (and thus, as a direct consequence, in debian-installer), we should use Macedonia. And, well, I'm pretty sure that most Greek users indeed share this advice. I'm already sure of this for one of them..:) Hm, I can't say I'm overjoyed with this choice. If this needs to be changed, I'd prefer the distiction to be made, 'Republic of Macedonia' would be far better and avoid unwanted comments from both sides. Konstantinos I think the style in Australia is The former Republic of Macedonia. I've always though it peculiar, but I think our Greeks are happy with it, and the second bigest Greek city in the world is in Australia. Macedonia is a town in Victoria:-) -- Cheers John -- spambait [EMAIL PROTECTED] [EMAIL PROTECTED] Tourist pics http://portgeographe.environmentaldisasters.cds.merseine.nu/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Re: Two Macedonias
According to the EU Resolution FYROM cannot have the name Macedonia. If you plan to use this name then you have to add in a parenthesis the word Slav: Macedonia (Slav) I am putting the Resolution so you can read it. I'm sorry to say so, but if Debian does not comply to the resolution of the foreign ministers of the EU than i will be in the unpleasent position to bring the subject to the EU court. And by the way we do not share your opinion regarding two macedonians. The subject is political and extremely sensitive. The country of FYROM declared as Macedonia by Tito (the dictator) in order to take the northern part of Greece called Macedonia from the ancient times. Besides all Macedonians believed in the Greek Gods, spoke the Greek language, wrote in greek, had greek names (Alexander is in greek the man who repeals, the strong man) and took part in the Olympic Games (only greeks were allowed to participate). THE RESOLUTION: EXECUTIVE BOARD CONSEIL EXECUTIF F.B (2004) OS 2 March 2004 Note for the attention of the members of the Executive Board References concerning the former Yugoslav Republic of Macedonia and persons belonging to a minority or speaking a minority language outside the country Taking into account Resolution (95) 23 adopted by the Committee of Ministers on 19 October 1995 at the 547th meeting of Ministers' Deputies, the Secretarial is hereby instructed to use the following references provisionally for all purposes within the Council of Europe pending settlement of the difference which has arisen over the name of the State in question. They are to be used in all documents prepared by the Secretariat of the Council of Europe. The Parliamentary Assembly, the Congress of Local and Regional Authorities of Europe, the European Court of Human Rights and independent monitoring mechanisms are strongly encouraged to use these references. However, texts emanating or prepared under instructions from the Parliamentary Assembly, the Congress of Local and Regional Authorities of Europe, the European Court of Human Rights, independent monitoring mechanisms, as well as reports, declarations and other texts attributed to individual Parliamentarians, representatives to the Congress, judges of the Court or members of independent monitoring mechanisms will not have to be changed if they are not in line with the agreed references. As regards the country Country: The former Yugoslav Republic of Macedonia The inverted commas are an integral pan of the reference. When the term appears within a sentence, the the must be written with a small t Adjective/ Nationality: of the former Yugoslav Republic of Macedonia Examples: the government of the former Yugoslav Republic of Macedonia, the police of the former Yugoslav Republic of Macedonia citizen of the former Yugoslav Republic of Macedonia Adjective referring to culture: Macedonian (Slav) Examples: Macedonian (Slav) traditions. Macedonian (Slav) culture Language: Macedonian (Slav) As regards persons belonging to a minority or speaking a minority language outside the country Persons/group: Macedonian(s) accompanied by a footnote reading Terminology of self-identification used by the person(s) concerned Adjective: Macedonian (Slav) Examples: Macedonian (Slav) traditions. Macedonian (Slav) associations, Macedonian (Slav) schools Language: Macedonian (Slav) Jan Kleijssen Director of the Secretary General's Private Office -Original Message- From: Christian Perrier [EMAIL PROTECTED] To: [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED] Date: Thu, 23 Sep 2004 10:44:26 +0200 Subject: Re: Two Macedonias 2) use the names 'Republic Macedonia' and 'Greek Macedonia'. I like that one, but, as Steve Langasek said, in the namespace of autonomous territories, there is no collision at all. Well, in my opinion, if we decide changing FYROM to something in iso-codes (and thus, as a direct consequence, in debian-installer), we should use Macedonia. And, well, I'm pretty sure that most Greek users indeed share this advice. I'm already sure of this for one of them..:) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#272995: fails on g4 desktop
Package: installation-reports Debian-installer-version:Thursday september 23,daily builds testing uname -a: Darwin d9059.upc-d.chello.nl 7.5.0 Darwin Kernel Version 7.5.0: Thu Aug 5 19:26:16 PDT 2004; root:xnu/xnu-517.7.21.obj~3/RELEASE_PPC Power Macintosh powerpc Date: 23.9.2004 11,00 Method:businesscard.iso.boot cd,network Machine:apple g4 sawtooth Processor:g4 1.4 ghz upgradecard Memory:1.38gb Root Device: IDE hitachi 160 gb Root Size/partition table: hda13, 25 gb,otherpartitions OS X table, with notes on which partitions are mounted where. Output of lspci and lspci -n: Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot worked:[O ] Configure network HW: [O ] Config network: [ O] Detect CD: [ O] Load installer modules: [O ] Detect hard drives: [O ] Partition hard drives: [ O] Create file systems:[O ] Mount partitions: [O ] Install base system:[ O] Install boot loader:[O ] Reboot: [ E] Comments/Problems: When i reboot iget this: Welcome to Linux, Kernel 2.6.8.1-2powerpc linked at : 0 x c000 frame buffer at : 0 x 9c008000 [phys],0 x d008000[ios] klimit : 0x 0c 02eb210 Msr : 0 x 3030 Hido : 0 x 8410cobc pmac_init [ ] : exit id mach [ ] : done MMU : enter MMU : hw init hash : enter hash : find piece hash : patch hash : done MMU : mapin MMU : setio MMU : exit setup_arch : enter setup_arch : bootmen arch : exit openpic : enter openpic : timer openpic : externel openpic : spurious openpic : exit This is what i get with the ubuntu install. with the daily sarge build iget the same just shows a different kernel. The rc1 build installs OK [no sound},but when i upgrade to unstable it goes wrong again. over at Ubuntu somebody said its bug 1379 but i have a single processor-machine. Any suggestions Sebastian Jorissen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Two Macedonias
Vassilis Grigoriadis wrote: According to the EU Resolution FYROM cannot have the name Macedonia. If you plan to use this name then you have to add in a parenthesis the word Slav: Macedonia (Slav) I (as a Slavic) think that this name is very good. Regards, ogi -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: your mail
Processing commands for [EMAIL PROTECTED]: reopen 272325 Bug#272325: Unable to change language Bug reopened, originator not changed. End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Two Macedonias
Since, my comments displeased some people who were brave enough to accuse me of 'selling my country', I hereby denounce all 'authority' with regards to such matters. Feel free to decide whatever you like, I prefer to spend my time in some actually useful area, for example, complete the greek support in the installer, rather than commence in such arguments. Konstantinos -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#272325: Bug#272328: acknowledged by developer (broken images)
On 20 2004 01:20, Joey Hess wrote: You tested known broken images. Please retry. Actually, AFAIK the breakage Bastian is referring to did not get into any CD images for i386, since I built fixed initrds before the CDs built. Also, it did not manifest anything like the problem you describe. Past occurrances of the problem you describe have been bugs in bogl's framebuffer support with some kernels.. These bugs should be reopened. 272328 can be closed, apparently it's vmware specific (along with other quirks). But I'm reopening 272325, since it's still appearing on the latest images. Konstantinos
Re: [l10n] Missing strings in packages/po/bg.po
Quoting Ognyan Kulev ([EMAIL PROTECTED]): Hi, I've tested Bulgarian translation of d-i in expert26 and found that the following titles in main menu are not translated: Free memory (low memory install) EVMS module.. SSH... LVM... MD... Hmmm, none of these appear to be marked as translatable stuff. So, this needs some code change to partman-mdYou should report a bug against it asking for these to be marked as translatable. Moreover, none of the po strings in partman-md are in packages/po/bg.po. (Just search for partman-md in bg.po.) They are here. However, as the templates file is just named templates, you don't see partman-md in comments. For instance, Write the changes to the storage devices and configure RAID? (line 7219 in packages/po/template.pot) Several templates files need to be renamed to package.templates so that the general template.pot file has more useful information about the package each string pertains to. However, I was reluctant to make these changes a few weeks ago on all packages. I changed several of them, but several others still need this. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Stephanie33 has invited you to open a CHATING_WIVES account
CHATING_WIVES User Name: Stephanie33 Age: 33 Measurement: 36 28 36 Status: Married, but lonely Fantasy: Let some stranger fukc me hardcore and cum on my tits. Favorite sexual position: Oral Sex To accept this invitation and register for your account, visit http://candypersonal.com/wiv/signup.php ztop mail http://www.funnyface69.com/emms/preference/control.php
Re: Re: Two Macedonias
On 2004-09-23 11:33:49 +0100 Vassilis Grigoriadis [EMAIL PROTECTED] wrote: I'm sorry to say so, but if Debian does not comply to the resolution of the foreign ministers of the EU than i will be in the unpleasent position to bring the subject to the EU court. Matthew Garrett has already pointed out that this resolution does not bind debian. If we did comply, could Debian be charged in court elsewhere, because the constitutional name seems to be Republic of Macedonia? As far as I know, the Greek province Macedonia is not a republic in itself, and the Bulgarian province is officially named something else, so their consitutional name should not confuse anyone. The alternate view is that we should follow the ISO naming, but I'm not sure if we already do or not for other states. I suspect decisions like ISO, EU and so on were originally taken while the Republic of Macedonia had other concerns, including Greece's blockade. I suspect any EU court worth its salt would sort out EU member Slovenija's use of Republic of Macedonia before hearing a prosecution of a volunteer-run project, but I could be wrong. The resolution quoted dates from before Slovenija joined: I wonder if that was part of the motive for it? Please include debian-project in your reply. -- MJR/slefMy Opinion Only and not of any group I know Creative copyleft computing - http://www.ttllp.co.uk/ LinuxExpo.org.uk village 6+7 Oct http://www.affs.org.uk -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: bypassing partman
On Sat, Sep 18, 2004 at 02:19:10AM +0100, peter green wrote: for various reasons i want to be able to use debian installer to install on a block device that is not a partition is there any way to bypass partman and set up the mappings between mountpoints and block devices manually? I can not answer your question but unsell some new bug was introduced you don't need to bypass partman. 1. Start the installer in the expert mode so all questions will be asked 2. Choose to create by partman a new partition table on your block device. 3. You will be asked about its type. Choose loop. 4. Create one partition that ocupies the whole disk and use it. The loop partition table type is some hack provided by parted meaning that the storage device has only one partition and it ocupies the whole device. Anton Zinoviev -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Two Macedonias
On Thu, Sep 23, 2004 at 12:33:19PM +0300, Konstantinos Margaritis wrote: If this needs to be changed, I'd prefer the distiction to be made, 'Republic of Macedonia' would be far better and avoid unwanted comments from both sides. I am sure that nobody from Republic of Macedonia will complain if Debian uses this longer name instead of simply Macedonia. Anton Zinoviev -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Re: Re: Two Macedonias
Another solution could be to wait and keep the name as FYROM, since in a few months the negotiations between Greece and FYROM will start and will have as their subject the name of the country. Just another solution, Vassilis Grigoriadis -Original Message- From: MJ Ray [EMAIL PROTECTED] To: Vassilis Grigoriadis [EMAIL PROTECTED] Date: Thu, 23 Sep 2004 13:04:03 +0100 Subject: Re: Re: Two Macedonias On 2004-09-23 11:33:49 +0100 Vassilis Grigoriadis [EMAIL PROTECTED] wrote: I'm sorry to say so, but if Debian does not comply to the resolution of the foreign ministers of the EU than i will be in the unpleasent position to bring the subject to the EU court. Matthew Garrett has already pointed out that this resolution does not bind debian. If we did comply, could Debian be charged in court elsewhere, because the constitutional name seems to be Republic of Macedonia? As far as I know, the Greek province Macedonia is not a republic in itself, and the Bulgarian province is officially named something else, so their consitutional name should not confuse anyone. The alternate view is that we should follow the ISO naming, but I'm not sure if we already do or not for other states. I suspect decisions like ISO, EU and so on were originally taken while the Republic of Macedonia had other concerns, including Greece's blockade. I suspect any EU court worth its salt would sort out EU member Slovenija's use of Republic of Macedonia before hearing a prosecution of a volunteer-run project, but I could be wrong. The resolution quoted dates from before Slovenija joined: I wonder if that was part of the motive for it? Please include debian-project in your reply. -- MJR/slefMy Opinion Only and not of any group I know Creative copyleft computing - http://www.ttllp.co.uk/ LinuxExpo.org.uk village 6+7 Oct http://www.affs.org.uk
reassign to pcmcia-cs
reassign 248069 pcmcia-cs Thanks I think this is a bug in pcmcia-cs. Discover1 does not try to detect cards on the pcmicia bus and the module for the pcmcia bridge seems to be listed correctly. Gaudenz signature.asc Description: Digital signature
Processed: reassign to pcmcia-cs
Processing commands for [EMAIL PROTECTED]: reassign 248069 pcmcia-cs Bug#248069: [i386] [beta4] [netinst] failed to detect MELCO WLI-PCM-L11G(PCMCIA) with PCI board Bug reassigned from package `discover1-data' to `pcmcia-cs'. Thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#265183: pppoe workaround of the post-reboot problem
It is a gateway and does work as such. Did I not write in my last e-mail that *without* starting pppoe one can reach the provider's WAN via the default route going via the speedtouch? Then the modem is configured as a router and you don't need need PPTP at all... Marco, you seem to have forgotten another portion of the info I had mentioned earlier in the thread (to another portion of the same mail I had referred in the text you've just quoted!). While my traffic is routed to the WAN, being a 10. address it is NOT routable outside of it. Therefore, to get to the global Internet space, I need to establish PPTP. (A bit OT: I can still be using the provider's WAN e.g. to use their DNS forwarders rather than going to the DNS via the PPTP tunnel, but that would require me to add routes also to the DNS servers on the provider's LAN. This complication is not worth the negligible benefit of using the DNS. Overall, for a clean solution I should have the modem negotiate with my computer using a routing protocol and tell it about the provider WAN IPs reachable via the ethernet link to the modem, but this option is not provided, at least not in the default SpeedTouch config. Anyhow, this is not relevant to the pppoeconfig discussion.) Unfortunately, .138 is the firmware default of my modem, but a lot of folks reconfigure the address; I can also imagine other models using Their problem. Agreed, at least until a lot of folks complain :) addresses other than .138. As pppoeconf already discovers the modem by its own means, so I don't think the hardwiring saves a lot of coding. It does not discover the IP address. It knows its Ethernet address, it's the same LAN, and I bet it can send a RARP request to obtain one. Anyhow, as I am not giving a script patch and you do, I think that a hack that does what is needed in the most common case is definitely better than nothing. V. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processing of choose-mirror_1.04_i386.changes
choose-mirror_1.04_i386.changes uploaded successfully to localhost along with the files: choose-mirror_1.04.dsc choose-mirror_1.04.tar.gz choose-mirror_1.04_i386.udeb Greetings, Your Debian queue daemon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
choose-mirror_1.04_i386.changes ACCEPTED
Accepted: choose-mirror_1.04.dsc to pool/main/c/choose-mirror/choose-mirror_1.04.dsc choose-mirror_1.04.tar.gz to pool/main/c/choose-mirror/choose-mirror_1.04.tar.gz choose-mirror_1.04_i386.udeb to pool/main/c/choose-mirror/choose-mirror_1.04_i386.udeb Announcing to [EMAIL PROTECTED] Thank you for your contribution to Debian. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#273024: debian installer report
Package: installation-reports Debian-installer-version: netinst RC1 cd image 23-Sept 2004 0800 CST uname -a: Linux audit01 2.4.26-1-386 #1 Thu July 22 12:46:23 JST 2004 i686 GNU/Linux Date: 23-Sept 2004 0900 CST Method: CD Image, local CD drive (/dev/hdc) Machine: Dell Latitude C610 Laptop Processor: 1GHz Pentium III Memory: 512MB Root Device: IDE, hda Root Size/partition table: /dev/had1 5341581 blocks / ext3 /dev/hda2 14193427 blocks W95 Ext'd (LBA) /dev/hda5 3903763 blocks /home ext3 /dev/hda6 497983 blocks swapswa Output of lspci and lspci -n: :00:00.0 Host bridge: Intel Corp. 82830 830 Chipset Host Bridge (rev 04) :00:01.0 PCI bridge: Intel Corp. 82830 830 Chipset AGP Bridge (rev 04) :00:1d.0 USB Controller: Intel Corp. 82801CA/CAM USB (Hub #1) (rev 02) :00:1e.0 PCI bridge: Intel Corp. 82801 PCI Bridge (rev 42) :00:1f.0 ISA bridge: Intel Corp. 82801CAM ISA Bridge (LPC) (rev 02) :00:1f.1 IDE interface: Intel Corp. 82801CAM IDE U100 (rev 02) :00:1f.5 Multimedia audio controller: Intel Corp. 82801CA/CAM AC'97 Audio Controller (rev 02) :00:1f.6 Modem: Intel Corp. 82801CA/CAM AC'97 Modem Controller (rev 02) :01:00.0 VGA compatible controller: ATI Technologies Inc Radeon Mobility M6 LY :02:00.0 Ethernet controller: 3Com Corporation 3c905C-TX/TX-M [Tornado] (rev 78) :02:01.0 CardBus bridge: Texas Instruments PCI1420 :02:01.1 CardBus bridge: Texas Instruments PCI1420 :00:00.0 0600: 8086:3575 (rev 04) :00:01.0 0604: 8086:3576 (rev 04) :00:1d.0 0c03: 8086:2482 (rev 02) :00:1e.0 0604: 8086:2448 (rev 42) :00:1f.0 0601: 8086:248c (rev 02) :00:1f.1 0101: 8086:248a (rev 02) :00:1f.5 0401: 8086:2485 (rev 02) :00:1f.6 0703: 8086:2486 (rev 02) :01:00.0 0300: 1002:4c59 :02:00.0 0200: 10b7:9200 (rev 78) :02:01.0 0607: 104c:ac51 :02:01.1 0607: 104c:ac51 Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot worked:[O] Configure network HW: [O] Config network: [O] Detect CD: [O] Load installer modules: [O] Detect hard drives: [O] Partition hard drives: [O] Create file systems:[O] Mount partitions: [O] Install base system:[O] Install boot loader:[O] Reboot: [)] Comments/Problems: Wow! This really worked great. I had installed two other systems recently using the old method and this cut the install time in half, even though some of the configuration utilities were new to me (partitioning the hard drive, package selection using Aptitude). -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: No HFS driver, and change install priority menu option missing -- and other bugs found while testing 2.4 boot floppies on OldWorld PowerMac
On Mon, Sep 20, 2004 at 05:05:58PM -0400, Rick Thomas wrote: Package: installation-reports In addition to the already noted problems with 2.4 PowerPC boot floppies, I have two requests for modules to be included on the root or root-2: Ok, actually following up on this from Oldenbourg with an oldworld box on hand. 1) The change installation priority menu item should be available *very* early in the install process. Best would be immediately after loading the root-2. Currently, it is not available up thru partitioning, at least. Hehe. Well, this is a general thingy. The idea is to change this in the kernel command line with DEBCONF_PRIORITY=medium or low. Maybe i should create an 'expert' boot/boot-ofonly floppy set ? 2) The hfs and hfsplus (MacOS filesystem formats) filesystem modules should be available early on. This would make it much easier to save log files to a floppy or a zip disk. Also, they are *required* for support of booting with BootX, so that the kernel and initrd can be copied from /target/boot/ to the appropriate place on the MacOS partition prior to the reboot. Yeah, but you have to balance the usefullness of that together with the size limit of the floppies. For the sake of completeness, here's a list of the other things I've found that currently don't work about the 2.4 powermac boot floppies: 3) Country chooser is called before loading root-2, so it hangs trying to do a grep US on a file that is on root-2, but should be on root. I moved the iso-3166-udeb package to root againt, should fix this. 4) the ofonlyboot floppy never switches to text-mode screen. It reads and ejects the boot floppy. But, since the text mode screen never appears, it's impossible to proceed further. This happens on both my test machines, the beige G3 tower, and the 6500. Well, i have the impression that this is not a real problem, but a feature, well sort of. There is two cases, either the real fbdev driver (valkyrie here) will work, in which case you use the boot floppy, or it will not. The same goes for the ofonly. Either the offb framebuffer device will work, in this case you can chose to use the boot-ofonly floppy, or it will not. If neither offb or the real fbdev device will work, you are screwed anyway, not much d-i can do here, and the only solution is to fix/port/write the driver in the kernel. 5) It never finds my disk. It gets all the way to partitioner without loading either the mesh driver or the driver for my PCI IDE controller card. This is a problem. Probably linked with the trouble with more than one floppy disk. Theroetically it should be loaded from the net afterward. For the record, I do not have any of these problems with installing via BootX using the latest businesscard CD. Of course, for problems 3 and 4 this is a trivial statement. Because all the modules are in the initrd, or at least those you need, and afteward the rest is brought trough the network. Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
RE: bypassing partman
that assumes that partman lists the block device in quesion at all ;) i have discovered how to force it though mount block device on /target cd to /target to make it impossible to unmount proceed with the install as normal it will try to start partman fail and dump you in the main menu from here you can move on to install the base system it will try to start partman a couple more times then proceed to install the base system -Original Message- From: Anton Zinoviev [mailto:[EMAIL PROTECTED] Sent: 23 September 2004 13:06 To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Re: bypassing partman On Sat, Sep 18, 2004 at 02:19:10AM +0100, peter green wrote: for various reasons i want to be able to use debian installer to install on a block device that is not a partition is there any way to bypass partman and set up the mappings between mountpoints and block devices manually? I can not answer your question but unsell some new bug was introduced you don't need to bypass partman. 1. Start the installer in the expert mode so all questions will be asked 2. Choose to create by partman a new partition table on your block device. 3. You will be asked about its type. Choose loop. 4. Create one partition that ocupies the whole disk and use it. The loop partition table type is some hack provided by parted meaning that the storage device has only one partition and it ocupies the whole device. Anton Zinoviev -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: bypassing partman
On Thu, Sep 23, 2004 at 03:43:21PM +0100, peter green wrote: it will try to start partman a couple more times then proceed to install the base system I don't understand why it allowed you to proceed at all. ;-) One way to cheat is to configure some partition sheme by partman and then to change it manualy acording to your needs. Then the system will know that partman is configured and will not restart it. However in order not to proceed directly to the installation of the base system before you could setup your own version of /target the installation process has to be in expert mode. Anton Zinoviev -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#271782: (no subject)
Joey Hess [EMAIL PROTECTED] writes: Goswin von Brederlow wrote: Some more udeb sources missing in sarge: rootskel cdrom-checker anna ddetect debian-installer-utils lowmemcheck main-menu No udeb sources are in sarge, but I am not seeing these build-depends on them that you speak of. -- see shy jo They are not listed as Build-Depends since udebs are not installed on the build system as such. They are downloaded and unpacked to create the initrds instead. That's why I quoted build-depends. They need to be in the udebs Packages file. As you say there are no udeb sources in sarge (unless it is a regular source also building udebs). Apart from meaning that amd64 doesn't get udeb automatically it is also a GPL violation not to have the sources on the same medium as the udebs. Having the source on alioth isn't enough. For both those reasons I think it would be good to make a new D-I rc release during/after the debcamp and get that one moved to sarge with sources. MfG Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processing of cdrom-detect_1.02_i386.changes
cdrom-detect_1.02_i386.changes uploaded successfully to localhost along with the files: cdrom-detect_1.02.dsc cdrom-detect_1.02.tar.gz cdrom-detect_1.02_all.udeb Greetings, Your Debian queue daemon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
cdrom-detect_1.02_i386.changes ACCEPTED
Accepted: cdrom-detect_1.02.dsc to pool/main/c/cdrom-detect/cdrom-detect_1.02.dsc cdrom-detect_1.02.tar.gz to pool/main/c/cdrom-detect/cdrom-detect_1.02.tar.gz cdrom-detect_1.02_all.udeb to pool/main/c/cdrom-detect/cdrom-detect_1.02_all.udeb Announcing to [EMAIL PROTECTED] Thank you for your contribution to Debian. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
RE: bypassing partman
One way to cheat is to configure some partition sheme by partman and then to change it manualy acording to your needs. Then the system will know that partman is configured and will not restart it. this assumes that your system has block devices that patman recognises at all -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#273037: D-I warns that root on LVM won't work - but it does.
Package: debian-installer Version: rc1 Severity: minor I'm currently in the process of installing Sarge on a workstation, using sarge-i386-netinst.iso retrieved from http://cdimage.debian.org/pub/cdimage-testing/sarge_d-i/i386/rc1/sarge-i386-netinst.iso today. I had it talk German to me. Being an old hand in Debian installations, out of sheer habit I did quite a bit of fiddling with the partitions. In the end, I had configured /boot on /dev/hda1, one big LVM PV on /dev/hda2, a single LVM VG to use it, and different LVs with ext3 partitions for /, /var, /usr and /home, as well as swap. And finally a third of the hard disc left free for further developments. When I was through with the fiddling, a text came up to the extend that Debian supposedly does not support /boot or root on LVM, and that it probably wouldn't work. I didn't believe that, so I took a chance and indeed - without any further manual intervention to this respect, the machine came up into itself (i.e., without the CD inserted) to complete the next step of the installation. While I write this, it's downloading loads of packages from the local apt-proxy. Smooth sailing. Regards, and thank you for providing fine software Andreas -- Dr. Andreas Krüger, [EMAIL PROTECTED] GPG/PGP Fingerprint 8063 4A9B 362D 4220 A546 14C1 EA19 AADC FD44 5EB7 DV-RATIO Nordwest GmbH, Tel.: +49 211 577 996-0, Fax: +49 211 559 1617 Leostraße 31, 40545 Düsseldorf, Germany signature.asc Description: OpenPGP digital signature
Bug#265001: sparc issue solved
Hi, it seems that partman works alright but does not show everything it knows. It knows about the whole disk thing (or was it the Sol8-Install that created it?) and everything is fine now. To run fdisk (the 's' command there), the rescue system can be used _after_ installation. HS -- Mein GPG-Key ist auf meiner Homepage verfügbar: http://www.hendrik-sattler.de oder über pgp.net PingoS - Linux-User helfen Schulen: http://www.pingos.org
Re: bypassing partman
On Thu, Sep 23, 2004 at 04:30:50PM +0100, peter green wrote: this assumes that your system has block devices that patman recognises at all ok, then run nano /var/lib/dpkg/status And specify partman as installed. ;-) Anton Zinviev -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
read-edid is not on first disc
Hi, Obviously, the setup (after reboot and after installing mdetect) wants to install something (don't know what because it is not displayed) but read-edid is not on the first disc. Does not hurt much but gives a short error message. HS -- Mein GPG-Key ist auf meiner Homepage verfügbar: http://www.hendrik-sattler.de oder über pgp.net PingoS - Linux-User helfen Schulen: http://www.pingos.org
Bug#273056: D-I: Network / sources.list configuration issues using apt-proxy.
Package: debian-installer Version: rc1 Severity: minor I'm currently in the process of installing Sarge on a workstation, using sarge-i386-netinst.iso retrieved from http://cdimage.debian.org/pub/cdimage-testing/sarge_d-i/i386/rc1/sarge-i386-netinst.iso today. I have both a Squid and an apt-proxy server running in this LAN. I decided to enter my sources.list manually. The first time round, I mistyped. I got my second chance, very good! So far, so smooth sailing. Pretty much immediately thereafter, I was asked about which HTTP proxy to use. What's that about? The question left me confused. (Maybe I didn't read the screen carefully enough. If that is the case, please pardon me.) I declined giving an answer, as I did not understand why that would be useful. As a matter of fact, out of sheer configuration lazyness you can actually reach the apt-proxy through the Squid. But I certainly do not want the new box to actually do that. Only a moment later it became clear to me that this question was asked on behalf of Debian security updates. This is needlessly confusing. My suggestion: In the best Debian tradition, D-I should assume a person who edits manually knows what she is doing. Provide a template, yes. Drop the security line into sources.list, with an appropriate commentary, *before* the editor is fired, yes. Once we are at it, please add example lines for http_proxy and ftp_proxy, as comments. And then leave it at that, whatever comes out of the editor. Regards, and thank you for providing fine software Andreas -- Dr. Andreas Krüger, [EMAIL PROTECTED] GPG/PGP Fingerprint 8063 4A9B 362D 4220 A546 14C1 EA19 AADC FD44 5EB7 DV-RATIO Nordwest GmbH, Tel.: +49 211 577 996-0, Fax: +49 211 559 1617 Leostraße 31, 40545 Düsseldorf, Germany signature.asc Description: OpenPGP digital signature
Bug#273065: Installation report
Package: installation-reports INSTALL REPORT Debian-installer-version: daily build 20040923 (businesscard) uname -a: Linux feynman 2.6.8-1-386 #1 Sat Aug 28 13:18:58 EDT 2004 i686 GNU/Linux Date: 20040923 Method: Boot from CD, network configuration from DHCP Packages retrieved from internet Machine: Processor: AMD Athlon 64 3500+ Memory: 1 GB Root Device: SATA, Samsung SP1614C Root Size/partition table: /dev/sda1 / ext3 7GB /dev/sda2 ext3 7GB (reserved for amd64 /) /dev/sda7 /home ext3 130GB /dev/sda6 /varext3 15GB /dev/sda5 noneswap1GB /dev/hda/media/cdrom0 iso9660 ro,user,noauto 0 0 /dev/fd0/media/floppy0 autorw,user,noauto 0 0 Output of lspci and lspci -n: :00:00.0 Host bridge: VIA Technologies, Inc.: Unknown device 0282 :00:00.1 Host bridge: VIA Technologies, Inc.: Unknown device 1282 :00:00.2 Host bridge: VIA Technologies, Inc.: Unknown device 2282 :00:00.3 Host bridge: VIA Technologies, Inc.: Unknown device 3282 :00:00.4 Host bridge: VIA Technologies, Inc.: Unknown device 4282 :00:00.7 Host bridge: VIA Technologies, Inc.: Unknown device 7282 :00:01.0 PCI bridge: VIA Technologies, Inc. VT8237 PCI bridge [K8T800 South] :00:05.0 VGA compatible controller: STMicroelectronics STG4000 [3D Prophet Kyro Series] (rev 01) :00:0b.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8169 Gigabit Ethernet (rev 10) :00:0e.0 FireWire (IEEE 1394): VIA Technologies, Inc. IEEE 1394 Host Controller (rev 46) :00:0f.0 RAID bus controller: VIA Technologies, Inc. VIA VT6420 SATA RAID Controller (rev 80) :00:0f.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06) :00:10.0 USB Controller: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller (rev 81) :00:10.1 USB Controller: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller (rev 81) :00:10.2 USB Controller: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller (rev 81) :00:10.3 USB Controller: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller (rev 81) :00:10.4 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 86) :00:11.0 ISA bridge: VIA Technologies, Inc. VT8237 ISA bridge [K8T800 South] :00:11.5 Multimedia audio controller: VIA Technologies, Inc. VT8233/A/8235/8237 AC97 Audio Controller (rev 60) :00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge :00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge :00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge :00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge lspci -n :00:00.0 0600: 1106:0282 :00:00.1 0600: 1106:1282 :00:00.2 0600: 1106:2282 :00:00.3 0600: 1106:3282 :00:00.4 0600: 1106:4282 :00:00.7 0600: 1106:7282 :00:01.0 0604: 1106:b188 :00:05.0 0300: 104a:0010 (rev 01) :00:0b.0 0200: 10ec:8169 (rev 10) :00:0e.0 0c00: 1106:3044 (rev 46) :00:0f.0 0104: 1106:3149 (rev 80) :00:0f.1 0101: 1106:0571 (rev 06) :00:10.0 0c03: 1106:3038 (rev 81) :00:10.1 0c03: 1106:3038 (rev 81) :00:10.2 0c03: 1106:3038 (rev 81) :00:10.3 0c03: 1106:3038 (rev 81) :00:10.4 0c03: 1106:3104 (rev 86) :00:11.0 0601: 1106:3227 :00:11.5 0401: 1106:3059 (rev 60) :00:18.0 0600: 1022:1100 :00:18.1 0600: 1022:1101 :00:18.2 0600: 1022:1102 :00:18.3 0600: 1022:1103 Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot worked:[E/O] Configure network HW: [O] Config network: [O] Detect CD: [O] Load installer modules: [O] Detect hard drives: [O] Partition hard drives: [O] Create file systems:[O] Mount partitions: [O] Install base system:[O] Install boot loader:[O] Reboot: [O] Comments/Problems: I first tried to start the installation in default mode (2.4 kernel) On first hardware detection the system hang whilke trying to install sd_mod. While it is certainly acceptable that on a SATA machine install only works with 2.6, the installer shouldn't hang, but give a meaningful error message. After booting with linux2.6 the install run flawlessly. Great work! Gruesse, -- Frank Lichtenheld [EMAIL PROTECTED] www: http://www.djpig.de/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: No HFS driver, and change install priority menu option missing -- and other bugs found while testing 2.4 boot floppies on OldWorld PowerMac
On Thursday, September 23, 2004, at 11:02 AM, Sven Luther wrote: On Mon, Sep 20, 2004 at 05:05:58PM -0400, Rick Thomas wrote: Package: installation-reports In addition to the already noted problems with 2.4 PowerPC boot floppies, I have two requests for modules to be included on the root or root-2: Ok, actually following up on this from Oldenbourg with an oldworld box on hand. Glad you finally got an oldworld powermac box to test things on! (-8) I hope Oldenbourg is fun. It's a bit far for me to travel. 1) The change installation priority menu item should be available *very* early in the install process. Best would be immediately after loading the root-2. Currently, it is not available up thru partitioning, at least. Hehe. Well, this is a general thingy. The idea is to change this in the kernel command line with DEBCONF_PRIORITY=medium or low. Maybe i should create an 'expert' boot/boot-ofonly floppy set ? Hmmm... In general, I'd much prefer to solve this problem without a multiplication of floppies -- one for each possible boot-time option! It takes several minutes to download and burn a floppy. Multiply that by all the options I need to test, and you're talking about a serious investment of time. Can't we come up with some more general method of setting boot-time options? In this particular case, could someone please explain to me the logic behind putting the first availability of change installation priority so late in the game? 2) The hfs and hfsplus (MacOS filesystem formats) filesystem modules should be available early on. This would make it much easier to save log files to a floppy or a zip disk. Also, they are *required* for support of booting with BootX, so that the kernel and initrd can be copied from /target/boot/ to the appropriate place on the MacOS partition prior to the reboot. Yeah, but you have to balance the usefullness of that together with the size limit of the floppies. I understand the size constraints. But isn't that the reason why we added the root-2 floppy? Would adding hfs and/or hfsplus kick us over the edge into root-3 land? Enjoy! Rick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#273074: install: xfs with fstab options usrquota and/or grpquota mounts in read-only, system boots not/not good.
Package: install Severity: grave Justification: renders package unusable -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.4.26-1-k7 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] xfs flags chosen in sarge partition setup 'grpquota' and 'usrsquota' mount the xfs partition in read-only. This is because xfs don't understands it and defaults to read-only. Philip -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: newt and slang issues
On Wed, Sep 22, 2004 at 12:37:52PM +0100, Alastair McKinstry wrote: I will upload the slang change to testing-proposed-updates as soon as the sid package is accepted into the archive; is the newt translation significant enough for t-p-u ? Please upload to unstable only; the release team can push the package to testing from there once it's built on all archs. Ok, I won't upload then. Should the bugs be re-opened then and tagged RC and sarge to track this? The current console-tools, console-data, console-common in sid fix RC issues and should be pushed into sarge. console-common has also been reviewed and approved. Cheers, -- Steve Langasek postmodern programmer signature.asc Description: Digital signature
Re: No HFS driver, and change install priority menu option missing -- and other bugs found while testing 2.4 boot floppies on OldWorld PowerMac
On Thu, Sep 23, 2004 at 01:40:36PM -0400, Rick Thomas wrote: On Thursday, September 23, 2004, at 11:02 AM, Sven Luther wrote: On Mon, Sep 20, 2004 at 05:05:58PM -0400, Rick Thomas wrote: Package: installation-reports In addition to the already noted problems with 2.4 PowerPC boot floppies, I have two requests for modules to be included on the root or root-2: Ok, actually following up on this from Oldenbourg with an oldworld box on hand. Glad you finally got an oldworld powermac box to test things on! (-8) :) It doesn't seem to do netloading correctly though. I hope Oldenbourg is fun. It's a bit far for me to travel. Yeah, on both accounts. 1) The change installation priority menu item should be available *very* early in the install process. Best would be immediately after loading the root-2. Currently, it is not available up thru partitioning, at least. Hehe. Well, this is a general thingy. The idea is to change this in the kernel command line with DEBCONF_PRIORITY=medium or low. Maybe i should create an 'expert' boot/boot-ofonly floppy set ? Hmmm... In general, I'd much prefer to solve this problem without a multiplication of floppies -- one for each possible boot-time option! It takes several minutes to download and burn a floppy. Multiply that by all the options I need to test, and you're talking about a serious investment of time. Can't we come up with some more general method of setting boot-time options? In this particular case, could someone please explain to me the logic behind putting the first availability of change installation priority so late in the game? Because you will only see it if something else fails in the high priority thingy. I have modified the daily builds to boot into priority=medium by default now, so this should solve this. 2) The hfs and hfsplus (MacOS filesystem formats) filesystem modules should be available early on. This would make it much easier to save log files to a floppy or a zip disk. Also, they are *required* for support of booting with BootX, so that the kernel and initrd can be copied from /target/boot/ to the appropriate place on the MacOS partition prior to the reboot. Yeah, but you have to balance the usefullness of that together with the size limit of the floppies. I understand the size constraints. But isn't that the reason why we added the root-2 floppy? Would adding hfs and/or hfsplus kick us over the edge into root-3 land? We could indeed add it to root-2, but i would prefer to get the floppy loading work correctly before i do this rather cosmetic thing working. And hfs/hfsplus without ide/scsi driver is not really all that usefull, isn't it. Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: No HFS driver, and change install priority menu option missing -- and other bugs found while testing 2.4 boot floppies on OldWorld PowerMac
On Thursday, September 23, 2004, at 06:13 PM, Sven Luther wrote: I understand the size constraints. But isn't that the reason why we added the root-2 floppy? Would adding hfs and/or hfsplus kick us over the edge into root-3 land? We could indeed add it to root-2, but i would prefer to get the floppy loading work correctly before i do this rather cosmetic thing working. And hfs/hfsplus without ide/scsi driver is not really all that usefull, isn't it. OK. I think see the logic. I'm not clear on what comes from where as far as drivers and install components. Can you give me a general picture? (Seemingly, net-drivers and cd-drivers are obvious, but maybe not?) In particular, how are things that *aren't* on a particular floppy retrieved, and how does it know which of those to retrieve? Also, is there a general rule for what goes on root, root-2, one of the drivers floppy, or over the web? Thanks! Rick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
/etc/init.d/console-screen.sh does not run on 1st boot
Hi, Joey and I tried testing greek support here in Oldenburg, and since console-* packages seem to support greek quite well right now, I suggested we try dumping use of jfbterm for 2nd stage. Unfortunately, it does not work, it does not set the font at 1st boot (just after d-i reboots the system). Apparently, /etc/init.d/console-screen.sh does not run to set the console font, or if it does run, it does not succeed in setting the font to greek. The strange thing is that it works from second boot. Alastair, do you have any idea as to what might stop the script from setting the font on 1st boot, but not on 2nd boot? Thanks Konstantinos -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: No HFS driver, and change install priority menu option missing -- and other bugs found while testing 2.4 boot floppies on OldWorld PowerMac
On Thu, Sep 23, 2004 at 06:30:48PM -0400, Rick Thomas wrote: On Thursday, September 23, 2004, at 06:13 PM, Sven Luther wrote: I understand the size constraints. But isn't that the reason why we added the root-2 floppy? Would adding hfs and/or hfsplus kick us over the edge into root-3 land? We could indeed add it to root-2, but i would prefer to get the floppy loading work correctly before i do this rather cosmetic thing working. And hfs/hfsplus without ide/scsi driver is not really all that usefull, isn't it. OK. I think see the logic. I'm not clear on what comes from where as far as drivers and install components. Can you give me a general picture? (Seemingly, net-drivers and cd-drivers are obvious, but maybe not?) In particular, how are things that *aren't* on a particular floppy retrieved, and how does it know which of those to retrieve? Also, is there a general rule for what goes on root, root-2, one of the drivers floppy, or over the web? They are not, we need to find out a rule for those. Floppies are mainly worked and tested on x86, which have not the size problem we have. In root needs to be everything to load the rest of the floppies (the floppy driver and retriever) and the most of the other stuff. That is the only contraint. We put in root-2 the rest of the non-driver stuff, in the net drivers the network drivers, and in the cd drivers the ide/scsi/cdrom/disk/filesystem stuff, needed to make the cdrom work and retrieve more stuff from there. For the rest of it, it is up to us to take decisions. Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#273109: base-config: Choosing not to start an display manager leaves menu unexitable
Package: base-config Version: 2.45 Severity: important /usr/lib/base-config/menu/finish calls itself with $0 debconf 0 if no display manager is to be started, or $0 debconf 1 if a display manager is to be done. However, switching against $1, the debconf) option has: ask_dm=$1 if [ $ask_dm ]; then Ask about display manager fi This code returns failure if no display manager was chosen but the above stanza was run. Now here, $1 is debconf not the 1 or 0 it is obviously meant to be checking for. _Also_, changing to ask_dm=$2 doesn't work since [ 0 ] is _true_. I think what was meant is: ask_dm=$2 if [ $ask_dm -eq 1 ]; then Same code here for choosing a display manager to run fi Same The same if [ $ask_dm ]; then ... fi stanza appears later on in the debconf) section. This actually occurred to me in 2.40.5 (from Testing), but I've just looked and the code is the same. -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.5 Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 Versions of packages base-config depends on: ii adduser 3.59 Add and remove users and groups ii apt 0.5.27 Advanced front-end for dpkg ii bsdutils1:2.12-8 Basic utilities from 4.4BSD-Lite ii console-data2002.12.04dbs-46 Keymaps, fonts, charset maps, fall ii console-tools 1:0.2.3dbs-55Linux console and font utilities ii debconf 1.4.36 Debian configuration management sy ii debianutils 2.10.1 Miscellaneous utilities specific t ii gettext-base0.14.1-5 GNU Internationalization utilities ii passwd 1:4.0.3-30.1 Change and administer password and -- debconf information excluded -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#265183: pppoe workaround of the post-reboot problem
On Sep 23, Vassilii Khachaturov [EMAIL PROTECTED] wrote: Then the modem is configured as a router and you don't need need PPTP at all... Marco, you seem to have forgotten another portion of the info I had mentioned earlier in the thread (to another portion of the same mail I had referred in the text you've just quoted!). While my traffic is routed to the WAN, being a 10. address it is NOT routable outside of it. Therefore, to get to the global Internet space, I need to establish PPTP. Then you are not using PPTP to your modem but to your ISP, your modem is behaving correctly and you don't need pppoeconf at all, because there is no way we can know the details of PPTP tunneling used by every provider. -- ciao, | Marco | [8146 l'in59F1Sy6vA] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: No HFS driver, and change install priority menu option missing -- and other bugs found while testing 2.4 boot floppies on OldWorld PowerMac
On Thursday, September 23, 2004, at 06:45 PM, Sven Luther wrote: On Thu, Sep 23, 2004 at 06:30:48PM -0400, Rick Thomas wrote: On Thursday, September 23, 2004, at 06:13 PM, Sven Luther wrote: I understand the size constraints. But isn't that the reason why we added the root-2 floppy? Would adding hfs and/or hfsplus kick us over the edge into root-3 land? We could indeed add it to root-2, but i would prefer to get the floppy loading work correctly before i do this rather cosmetic thing working. And hfs/hfsplus without ide/scsi driver is not really all that useful, isn't it. OK. I think see the logic. I'm not clear on what comes from where as far as drivers and install components. Can you give me a general picture? (Seemingly, net-drivers and cd-drivers are obvious, but maybe not?) In particular, how are things that *aren't* on a particular floppy retrieved, and how does it know which of those to retrieve? Also, is there a general rule for what goes on root, root-2, one of the drivers floppy, or over the web? They are not, we need to find out a rule for those. Floppies are mainly worked and tested on x86, which have not the size problem we have. In root needs to be everything to load the rest of the floppies (the floppy driver and retriever) and the most of the other stuff. That is the only constraint. We put in root-2 the rest of the non-driver stuff, in the net drivers the network drivers, and in the cd drivers the ide/scsi/cdrom/disk/filesystem stuff, needed to make the cdrom work and retrieve more stuff from there. For the rest of it, it is up to us to take decisions. Let me see if I've got this right -- please correct me if I've misunderstood: BOOT) The boot floppy has the kernel and miboot loader stuff (fake System that's really a boot-loader, and empty Finder). That's all there is and it pretty much fills up the disk, even with a severely stripped-down (anorexic?) kernel. For what it's worth, there is about 169 K left. ROOT) The root floppy has enough on it to talk to the console and keyboard (at least as far as being able to tell cr, the space key, the arrow-keys, and the tab key -- none of which depend on locale) set the locale, and finally, load the root-2 floppy. That pretty much fills the floppy. There's about 160 K left on root of compressed space: equivalent to [maybe] 570 K of uncompressed space assuming a compression ratio similar to that of the current contents -- about 1:4. The largest single file is libc. After that is /var/lib/dpkg/info, /bin/busybox, and /usr/lib/locale. Together these account for about 1/3 of the uncompressed space. The remaining 2/3 is lots of small potatoes -- nothing one can point to and say That's big and useless. Let's get rid of it!. ROOT-2) The root-2 floppy is a bunch of udebs for all the components that wouldn't fit on root. [This is a good design, but it requires that root have everything needed to install a udeb, making the root floppy even more crowded.] The root-2 floppy seems to have about 600 K of free space. Since udeb's are already compressed, there's no issue of compressed vs uncompressed space on root-2. Most of the stuff on root-2 seems to be for setting up the network (The largest single file is nic-extra-modules-2.4.27-powerpc-small- di.udeb -- 409 K, over half the total.) Some of that could, theoretically, be moved to the net-drivers floppy, but what would be the point? As long as root-2 is needed at all for overflow from root, and there's free space on it, why not use it? However, it's worth keeping this observation in mind if space on root-2 becomes tight and net-drivers remains uncrowded. The only stuff that really is absolutely required to be on root-2 is that which is (1) not absolutely required to be on root, and (2) is needed for *both* a net-install *and* a CD-install. I'm not knowledgeable enough about the details of d-i architecture to tell which of the udebs on the present root-2 fits that criterion. Can you give me some clues? NET-DRIVERS) The net-drivers floppy, like root-2, is a collection of udeb's. This represents everything (modulo the stuff that goes on root-2 because it's there) that is needed to get to the point of being able to download stuff from the web. This includes drivers for *all* sorts of network interfaces (PCI NIC cards, wireless PC-card NICs for laptops, serial-IP for people who must use modems, etc, etc...). It also includes things like dhcp-client, choose-mirror, software for getting things over the web, and so on. Most of this latter stuff seems to have landed on root-2 for (guessing) historical reasons. Currently, the net-drivers floppy has about 447 K of free space. CD-DRIVERS) The cd-drivers floppy is also a collection of udeb's. It represents everything that is needed to get to the point of being able to load stuff off of a CD-ROM. The largest single file is scsi-modules-2.4.27-powerpc-small-di.udeb, followed closely by
