Bug#421402: It's installed by default but not activated and configured by default!
En/na Frans Pop ha escrit: On Saturday 28 April 2007 22:38, Xan wrote: Yes the packages of selinux are installed by default but not activated and configured by default (parameter selinux=1 in kernel, politics file, etc) and there is no possibility of doing it in the d-i I think that the bug should be marked as open for these reasons Not really. The selinux people in Debian will make that decision when the time is ripe. There is absolutely no bug that needs to be tracked, especially not in the installation system. So, is there planned option for activated and configured in future releases? If yes, will you provide options to debian-installer for not activate it (for those who don't want it)? Thanks, Xan. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#421338: macbook pro installation issue
Julien BLACHE wrote: \Félix Guerrero [EMAIL PROTECTED] wrote: Hi, Image version: debian 4.0 r0 ia64 Apple machines aren't ia64, they're i386/amd64 machines. So, you used the wrong architecture, grab an i386 or amd64 installation media instead. Maybe we could add a warning in the ia64 images when such an image is used on an amd64 machine; this ia64/amd64 issue comes up really often. -- Regards, EddyP = Imagination is more important than knowledge A.Einstein signature.asc Description: OpenPGP digital signature
Bug#413263: Proposed release goal: Switch to GRUB2
Geert Stappers wrote: Op 25-04-2007 om 10:54 schreef Otavio Salvador: [EMAIL PROTECTED] (Geert Stappers) writes: My advice to make that switch (and switch back) more easy, is to implement a bootselector. | 7000 - 8000 Post-base-install | 7000 apt-setup | pkgsel + 7200 bootloaderselector (all) . 7500 palo-installer (hppa) | grub-installer (i386) + grub2-installer (i386,amd64,powerpc,...) | yaboot-installer (powerpc/powermac_newworld, powerpc/chrp*) | quik-installer (powerpc/powermac_oldworld) | zipl-installer (s390) | arcboot-installer (mips) | delo-installer (mipsel) | silo-installer (sparc) | vmelilo-installer (m68k/vme*) | glantank-installer (arm/iop32x) . lilo-installer (i386) . elilo-installer (ia64, i386) . nobootloader (all) | 7800 finish-install So all installers at the same menu-item-number. Which would mean fun, fun, fun since grub2 menu item would be after grub item; this would mean that grub2 needs either: - to be before grub2 in the order - not to load grub at all by default (probably the best choice) - force somehow, through a dependency the dependency on grub2, making grub2 the default choice I faced the same issue with ppp-udeb for which initially I set its menu-item-number to be 18 (they were up to 100 back then), but it was not chosen since it ordered after netcfg, so I had to set it to 17, so it has priority when is loaded. -- Regards, EddyP = Imagination is more important than knowledge A.Einstein signature.asc Description: OpenPGP digital signature
Re: this ia64/amd64 issue comes up really often.
Op 29-04-2007 om 14:28 schreef Eddy Petri??or: Julien BLACHE wrote: Apple machines aren't ia64, they're i386/amd64 machines. So, you used the wrong architecture, grab an i386 or amd64 installation media instead. Maybe we could add a warning in the ia64 images when such an image is used on an amd64 machine; Please elaborate your proposal. Brainstorm, throw ideas at the community, share ideas. Feel free. Don't let you be hinderd, surely not by the rest of this E-mail. this ia64/amd64 issue comes up really often. Less often then plain ignorance. I also feel sad to see installation reports that say | Base System Installation Checklist: | [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it | | Initial boot: [E] | Detect network card:[ ] | Configure network: [ ] | Detect CD: [ ] | Load installer modules: [ ] | Detect hard drives: [ ] | Partition hard drives: [ ] | Install base system:[ ] | Clock/timezone setup: [ ] | User/password setup:[ ] | Install tasks: [ ] | Install boot loader:[ ] | Overall install:[ ] | | Comments/Problems: | | I can not continue with the installation process. IMNSHO is the best way to fix these issues, is the sell pre-installed GNU/Linux computers. Cheers Geert Stappers signature.asc Description: Digital signature
Bug#413263: Proposed release goal: Switch to GRUB2
Op 29-04-2007 om 16:23 schreef Eddy Petri??or: Geert Stappers wrote: My advice to make that switch (and switch back) more easy, is to implement a bootselector. is to implement a bootloader selector. + 7200 bootloaderselector (all) . 7500 palo-installer (hppa) | grub-installer (i386) + grub2-installer (i386,amd64,powerpc,...) | yaboot-installer (powerpc/powermac_newworld, powerpc/chrp*) [ various bootloader installers ] . nobootloader (all) | 7800 finish-install So all installers at the same menu-item-number. Which would mean fun, fun, fun since grub2 menu item would be after grub item; this would mean that grub2 needs either: - to be before grub2 in the order - not to load grub at all by default (probably the best choice) - force somehow, through a dependency the dependency on grub2, making grub2 the default choice [1] The default bootloader-installer will be set during build of the bootloader-selector. The bootloader-selector has a low debconf priority, so it wouldn't be shown by default. At menu item number 7200 is the 'isinstallable'-flag set to true for the installer udeb. With a higher (more detailed) debconf priority will the user be asked for the bootloader of choice. This is where grub or grub2 can be selected. A bootparameter has the same effect. Cheers Geert Stappers [1] Either I don't understand you or you don't understand me. As I don't have time to explain that others are wrong, I will spend my time on explain what I have in mind. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: extra network selector
Op 29-04-2007 om 16:23 schreef Eddy Petri??or: Geert Stappers wrote: My advice to make that switch (and switch back) more easy, is to implement a bootloaderselector. + 7200 bootloaderselector (all) . 7500 [ installer of bootloader ] | 7800 finish-install So all installers at the same menu-item-number. Which would mean fun, fun, fun since grub2 menu item would be after grub item; this would mean that grub2 needs either: - to be before grub2 in the order - not to load grub at all by default (probably the best choice) - force somehow, through a dependency the dependency on grub2, making grub2 the default choice I faced the same issue with ppp-udeb for which initially I set its menu-item-number to be 18 (they were up to 100 back then), but it was not chosen since it ordered after netcfg, so I had to set it to 17, so it has priority when is loaded. Would it make sense to add after netcfg a menu item that may ask for extra network configuration? I say *may* ask, because debconf priority does default surpressed it. The extra network selector will request if PPPoE, ADSL at USB and such are needed. HtH GSt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: waking up in the 10.x.x.x network
Op 23-04-2007 om 11:03 schreef Michael S. Peek: Geert Stappers wrote: I would go talk to the administrator of the registration server. and ask for a directory on the that web server. Let's say that they go for it and let me have a d-i directory on the registration web server. I boot my install client, get an address in 10.x.x.x, download the preseed file from the web server -- and then crash when d-i can't see the internet to download the rest of the packages... Right? Because when you're in 10.x.x.x, the only thing you can see is this one web server. I would still have to find a way to re-configure the ethernet with it's correct IP address using the preseed files downloaded from the web server. Would that be possible? Maybe by having preseed execute a script? I suppose I would have to not only ifconfig the interface with the correct values, but presumably change d-i's debconf database too, as I don't know which is used to write out the /target/etc/network/interfaces file during the installation process. ... They didn't go for it. They're too paranoid. Which doesn't surprise me any. Even if I could get their DHCP server to serve me my correct static addresses that would solve the problem. I think. I would still need to make sure that after installation the system is set up to be static instead of DHCP. See your problem as a challenge. Increase the fun to split then in several smaller challenges. For two of the three challenges, you can find allies on this mailinglist. Doing DHCP over HTTP was posted last week. Getting a static IP address, preseeded over the network, can be done by executing netcfg a second time. In fact, it has allready be done, about one / two years ago [1]. The thrid challenge is getting server facility on your network. My advice: Request an address in 10.x.x.x network and assign that address as an alias to a (web)server you have write access to. Cheers Geert Stappers [1] Getting feedback about netcfg second time, is appriciated. (a request for help finding it back is also fine :-) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: waking up in the 10.x.x.x network
Op 23-04-2007 om 11:59 schreef Alex Owen: Michael S. Peek said: If I attempt to set up my own DHCP server then I run into a race condition between my DHCP server and the campus DHCP server. There's no way to tell d-i which server to contact, so it'll listen to the first one that it hears back from. So as near as I can tell, there is just no way to make this work. The DHCP protocol has the Vendor Class Identifier which could ne incoperated into the d-i dhcp-client. The dhcp protocol and many (good) clients allow multiple dhcp servers. The debian-installer dhcp client sends a vendor-class-identifier of d-i. The debian-installer dhcp client SHOULD be configurable to only accept dhcp leases which come from servers that send a reply containing a vendor-class-identifier of d-i. If d-i is using dhclient then an /etc/dhclient.conf with a select-timeout line and a require line should enable this functionality if I have read the man page right. It is a shame that http://d-i.alioth.debian.org/manual/en.i386/apbs02.html B.2.5 seems to say that d-i overloads the dhcp filename option to find the location of the preseed file. In my opinion this is better handled using vendor-encapsulated-options. Check out sun solaris install docs for ideas on this front! Mind you I guess there are many simple dhcp servers out there thus making overloading the filename option more practical. Hmm... I think there was some talk of changing the dhcpclient engine for lenny... there seemed to be lots of suggestions... my vote is for udhcpc. Anyway making the dhcp client in d-i more featureful with regards multiple dhcp servers perhaps could be added as a lenny release goal??? Just some thoughts! Alex Owen obvious The thoughts have been seen. The best way to get the wishes and the features added, is to provide program code for it. Writing the wishes/ideas/proposal down on the wiki or in the BTS will prevent that they get lost in the mailinglist archive. /obvious HtH GSt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: this ia64/amd64 issue comes up really often.
Geert Stappers wrote: Op 29-04-2007 om 14:28 schreef Eddy Petri??or: Julien BLACHE wrote: Apple machines aren't ia64, they're i386/amd64 machines. So, you used the wrong architecture, grab an i386 or amd64 installation media instead. Maybe we could add a warning in the ia64 images when such an image is used on an amd64 machine; Please elaborate your proposal. what's not clear? if you try to boot an ia64 image and it fails, the error message should suggest (if clear detection is not possible) that the user might be trying to boot the wrong type of image and maybe he/she should try an amd64 image which is the proper image for Intel Core 2 processors Brainstorm, throw ideas at the community, share ideas. Feel free. Don't let you be hinderd, surely not by the rest of this E-mail. this ia64/amd64 issue comes up really often. Less often then plain ignorance. You can't expect everybody to know how debian called its amd64/x86_64 architecture. Even the people that are close to debian might not know the difference (I know I also was confused). And since Intel Core 2 processors are produced by Intel, people *expect* the arch to be called something along the lines of i386, i486, and not k6, k7 or amd*, so ia64 - oh Intel architecture, 64 bits, that's it is the first thing that springs to mind. This is the reason behind many choices made in all kinds of places which are taken on the account of the element of the least surprise. Not knowing the history of the x86_64 arch is NOT plain ignorance. You can't expect everybody to know such things. I appreciate what Debian wanted to do (pay a tribute to amd), but we have to admit the choice backfired. I would be really curious about some comparative graphs about the downloads of the ia64 images around the release of etch and around the release of sarge (also in comparison with i386, amd64 and other images)... I wouldn't be surprised if there was a big difference since Intel Core 2 processors became more common place during sarge's lifetime and is *easy* to make the wrong choice... I also feel sad to see installation reports that say this is not quite the same thing, although I understand what are you trying to prove. IMNSHO is the best way to fix these issues, is the sell pre-installed GNU/Linux computers. I agree, but I'd say pre-installed with Debian GNU/Linux ;-) -- Regards, EddyP = Imagination is more important than knowledge A.Einstein signature.asc Description: OpenPGP digital signature
Bug#420631: dvgrab does not grab 1394raw
reassign 420631 kernel-image tags 420631 moreinfo thanks Op 23-04-2007 om 18:39 schreef Ian Schindler: When I boot using vmlinuz-2.6.18-4-amd64, dvgrab cannot get a handle on 1394raw. When I boot using vmlinuz-2.6.16-2-486, everything works fine. I have no idea why that might be. The people who package the kernel-image might known. You can help them by providing the difference of lsmod for both kernels. HtH GSt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Proposed release goal: Switch to GRUB2
Steve Langasek wrote: If the intent really is to drop grub1, I agree that grub2 should be renamed to 'grub' to ensure a smooth upgrade path. Couldn't BTW grub become an empty package depending either on grub2 or on grub1? (this seems more clean, and would allow for different dependencies on different architectures.) -- Luca Brivio -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#421323: Bug in Debian expertgui installer
highdruff ha scritto: Attilio Fiandrotti schrieb: highdruff ha scritto: Package: debian-installer Version: Etch 4.0r0 Hello If Debian Etch 4.0r0 installed from the official DVD (i386) with the bootparameter expertgui and then deactivate the root Account to use sudo there is a Bug in Gnome Menue. Whenever you will start an administrative application with Gnome Menue there comes an password Dialog and a error Message like this: Incorrect Password (but it is the right one) because the entry in Gnome Menue is e.g for start Synaptic gksu -u root /usr/sbin/synaptic but the right way is: gksudo -u root /usr/sbin/synaptic. Then the Application will start correctly and the wrong password Dialog is away. Does this bug shows up only with expertgui or also with expert boot option? thanks Attilio Both boot options expert and expertgui have it. cu Mathias ah ok, so that's not related to the gtk frontend, i guess this bug has to be reassigned to the belonging package (i don't know what it is). thanks attilio -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: extra network selector
Geert Stappers wrote: I faced the same issue with ppp-udeb for which initially I set its menu-item-number to be 18 (they were up to 100 back then), but it was not chosen since it ordered after netcfg, so I had to set it to 17, so it has priority when is loaded. Would it make sense to add after netcfg a menu item that may ask for extra network configuration? I say *may* ask, because debconf priority does default surpressed it. The extra network selector will request if PPPoE, ADSL at USB and such are needed. That was the plan, to incorporate somehow ppp-udeb into netcfg. -- Regards, EddyP = Imagination is more important than knowledge A.Einstein signature.asc Description: OpenPGP digital signature
seen ntfs from debian v.4
I install the last version of Debian 4 in a Toshiba Laptop, (Satellite 100 w/Centrino duo processor) and there is no sound in linux but in windows. The second thing is I cannot acces my files in windows from linux. Could you please tell me how to do it or if you need more info to help me? Thank you very much, Fernando -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
