November 2012 - openSUSE Users - openSUSE Mailing Lists

[opensuse] Re: Why does MS-Windows need no "initrd-equivalent" in order to boot w/a wider range of x86[-64] compat HW?
by Linda Walsh 01 Dec '12

01 Dec '12

Greg KH wrote: > On Wed, Nov 28, 2012 at 04:07:28PM -0800, Linda Walsh wrote: >> Perhaps someone can explain to me why Windows doesn't >> need a pre-boot ramdisk in order to boot, while Linux does? > > It does need one, and it has one, why do you think it doesn't? ---- The boot procedure for Windows is documented in the Windows NT internals book. There is no ramdisk that it uses. > > Note, this is _way_ off-topic here. --- Where do you think it would be "on-topic", considering _you_ don't want to hear it in any venue? You know the requirement of an initrd is bull, Claiming windows has one is even worse bullshit than I'd ever give you credit for. You can trace a windows boot -- there is no preload of a memory-resident copy of windows, that then loads windows. The drivers for the hardware are on the disk in /windows/system32/drivers. On Windows, it reads their boot managager, which then loads 'winload' which *demand*-loads drivers and services from disk -- they aren't all bound in to the kernel in order for it too boot. Please read Chapter 13 on Startup and Shutdown of the 5th edition of the Windows Internals book to get straightened out. The only time Windows needs a ramdisk during boot is when the boot-image needs to be downloaded from the net (i.e. a diskless boot). -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 4

[opensuse] Why does MS-Windows need no "initrd-equivalent" in order to boot w/a wider range of x86[-64] compat HW?
by Linda Walsh 30 Nov '12

30 Nov '12

Perhaps someone can explain to me why Windows doesn't need a pre-boot ramdisk in order to boot, while Linux does? I know Windows doesn't have all the drivers for all the hardware linked in with it's kernel -- it's dynamically loaded out of it's "/bin (windows/sytem32)" dir. So why does the linux kernel have this extra complication while windows does not? It's a bit embarrassing, I would think to see the wide range of HW supported by Windows **without** a special 'initrd' for drivers, while linux still doesn't support the range of HW that Windows does (some, but not ALL of that being due to short-sited HW providers who can't provide open specs or drivers). So what is Windows doing 'right', that Linux is unable to do? Maybe this is a kernel question -- maybe OpenSuse can't doing anything about this -- is this the case -- is this some kernel limitation? -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

14 22

Re: [opensuse] Why did Windows never do the equivalent of /home ?
by Martin Helm 30 Nov '12

30 Nov '12

Am 30.11.2012 22:37, schrieb Christopher Myers: > I think the big trick with all of this is that you have to do so > after Windows is installed, correct? With linux, you can specify to > use a different volume for home directories during installation. > Chris Of course and it is also a big pain in the *** to do it since you first have to make the "home" directory completely empty before you can mount a ntfs volume into it. It is not on par with what linux does, but the point is just that it is in principle possible if you really want it. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

Re: [opensuse] Why did Windows never do the equivalent of /home ?
by Christopher Myers 30 Nov '12

30 Nov '12

I think the big trick with all of this is that you have to do so after Windows is installed, correct? With linux, you can specify to use a different volume for home directories during installation. Chris >>> Martin Helm 11/30/12 3:26 PM >>> Am 30.11.2012 21:54, schrieb Duaine Hechler: > Wouldn't it behoove MS, to implement the /home concept (separating the > OS from the users' data in different partitions) ? > > Once I got "into" Linux, I never understood why MS did not implement > this. > > It would make it so much easier for all the support people (and users > - who do their own thing) > > Any ideas ? > This possibility exists for a very long time in windows (to be able to mount a ntfs partition as a directory) it is just not used by default, you need to do it yourself http://support.microsoft.com/kb/307889 -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] Cellular Modem (GOBI) w/openSUSE 12.2
by Adam Tauno Williams 30 Nov '12

30 Nov '12

I have a laptop with a Gobi 2000 wireless modem. The qcserial module is automatically loaded at boot but the device appears to be inoperative [no response to commands via minicom and /dev/ttyUSB0]. I'm told this device was working with a previous install, but it isn't working now [it was reinstalled]. Thoughts / suggestions? Bus 001 Device 004: ID 03f0:241d Hewlett-Packard Gobi 2000 Wireless Modem (QDL mode) - qcserial 12868 1 usb_wwan 20410 1 qcserial usbserial 47315 4 qcserial,usb_wwan - [ 15.345361] EDAC MC: Ver: 2.1.0 [ 15.346360] usbcore: registered new interface driver qcserial [ 15.346411] USB Serial support registered for Qualcomm USB modem [ 15.346446] qcserial 1-5:1.1: Qualcomm USB modem converter detected [ 15.346580] usb 1-5: Qualcomm USB modem converter now attached to ttyUSB0 -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 14

[opensuse] Hauppauge DVB-S cards - how to use the MAC address in udev rules?
by Per Jessen 30 Nov '12

30 Nov '12

On my new mythtv backend, I have two Hauppauge DVB-S cards for satellite reception. I would like to assign permanent device names to them using some udev rules. The cards do have unique MAC addresses, but afaict, they are not available through/to udev. udevadm does not list it, see below. Any suggestions? (apart from using the adapter_nr argument on the module). thanks Per # udevadm info --attribute-walk --name /dev/dvb/adapter3/frontend0 Udevadm info starts with the device specified by the devpath and then walks up the chain of parent devices. It prints for every device found, all possible attributes in the udev rules key format. A rule to match, can be composed by the attributes of the device and the attributes from one single parent device. looking at device '/devices/pci0000:00/0000:00:1e.0/0000:0a:01.2/dvb/dvb3.frontend0': KERNEL=="dvb3.frontend0" SUBSYSTEM=="dvb" DRIVER=="" looking at parent device '/devices/pci0000:00/0000:00:1e.0/0000:0a:01.2': KERNELS=="0000:0a:01.2" SUBSYSTEMS=="pci" DRIVERS=="cx88-mpeg driver manager" ATTRS{irq}=="19" ATTRS{subsystem_vendor}=="0x0070" ATTRS{broken_parity_status}=="0" ATTRS{class}=="0x048000" ATTRS{consistent_dma_mask_bits}=="32" ATTRS{dma_mask_bits}=="32" ATTRS{local_cpus}=="00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000001" ATTRS{device}=="0x8802" ATTRS{enable}=="1" ATTRS{msi_bus}=="" ATTRS{local_cpulist}=="0" ATTRS{vendor}=="0x14f1" ATTRS{subsystem_device}=="0x9202" ATTRS{numa_node}=="-1" looking at parent device '/devices/pci0000:00/0000:00:1e.0': KERNELS=="0000:00:1e.0" SUBSYSTEMS=="pci" DRIVERS=="" ATTRS{irq}=="0" ATTRS{subsystem_vendor}=="0x1014" ATTRS{broken_parity_status}=="0" ATTRS{class}=="0x060401" ATTRS{consistent_dma_mask_bits}=="32" ATTRS{dma_mask_bits}=="32" ATTRS{local_cpus}=="00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000001" ATTRS{device}=="0x244e" ATTRS{enable}=="1" ATTRS{msi_bus}=="1" ATTRS{local_cpulist}=="0" ATTRS{vendor}=="0x8086" ATTRS{subsystem_device}=="0x02f7" ATTRS{numa_node}=="-1" looking at parent device '/devices/pci0000:00': KERNELS=="pci0000:00" SUBSYSTEMS=="" DRIVERS=="" -- Per Jessen, Zürich (2.3°C) http://www.dns24.ch/ - free DNS hosting, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 6

[opensuse] Re: Why does MS-Windows need no "initrd-equivalent" in order to boot w/a wider range of x86[-64] compat HW?
by Linda Walsh 30 Nov '12

30 Nov '12

Claudio Freire wrote: > On Thu, Nov 29, 2012 at 10:30 PM, Linda Walsh <suse(a)tlinx.org> wrote: >> Jim Henderson wrote: >>> If you want to understand why Linux uses initrd, I suggest you take some >>> time and talk with the Linux kernel developers, after reading up on the >>> history of the Linux kernel. >> ---- >> Linux kernel developers will say it isn't necessary. >> >> It's only when you want 1 kernel/disk image to move >> to rather diverse hardware -- which isn't something users generally >> do. > > It's exactly what binary distributions do. Isn't Windows a binary distribution? Or are you saying it includes source? Your argument that it is needed for binary distributions when Windows is a binary distribution as well, doesn't add up. You need a temporary media when you install the OS. But after it is installed, why do you need it? -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] LibreOffice 3.6.4 RC1 available
by Basil Chupin 30 Nov '12

30 Nov '12

As the Heading states, it's available for trying out. My first comment about it: it's fast! Oh, and it works for me :-) . BC -- Using openSUSE 12.2 x86_64 KDE 4.9.3 & kernel 3.6.8-1 on a system with- AMD FX 8-core 3.6/4.2GHz processor 16GB PC14900/1866MHz Quad Channel Corsair "Vengeance" RAM Gigabyte AMD3+ m/board; Gigabyte nVidia GTX550Ti 1GB DDR5 GPU -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 2

[opensuse] Re: Why does MS-Windows need no "initrd-equivalent" in order to boot w/a wider range of x86[-64] compat HW?
by Linda Walsh 30 Nov '12

30 Nov '12

Jim Henderson wrote: > If you want to understand why Linux uses initrd, I suggest you take some > time and talk with the Linux kernel developers, after reading up on the > history of the Linux kernel. ---- Linux kernel developers will say it isn't necessary. It's only when you want 1 kernel/disk image to move to rather diverse hardware -- which isn't something users generally do. How often do you take 1 disk image and try to move it to different pieces of HW? You worked in an ancient enterprise with 250K users that had no HW standards? You are implying no ability to load needed parts over a network -- thus no net? Even non-OS vendors are taking to downloading stubs, by default, and checking your system for what parts/drivers need to be downloaded to bring it up to some 'standard'. But that's during an upgrade -- NOT daily booting. You are going off into installation issues, which I am NOT talking about. I'm talking about post-installation -- steady state systems. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] Re: (unknown)
by Malcolm 29 Nov '12

29 Nov '12

On Thu 29 Nov 2012 11:40:14 AM CST, Amaury Viera Hernández wrote: >Hello everyone, >I need to connect at one server for the first time and that it not ask >to me the authorization to add the server host to the >file .ssh/knownhosts: this is possible using the /etc/ssh_config file, >but is for all users > >HashKnownHosts no >UserKnownHostsFile /dev/null >GlobalKnownHostsFile /dev/null >StrictHostKeyChecking no > > >I need to connect for the first time and that client do not ask me for >authorice the server and add it to knownhosts >Could spcify using this in a file in .ssh? >How? >I apologize for my language, >Regards, Amaury. > Hi You need to run; ssh-keygen Then copy the contents of the ~/.ssh/id_rsa.pub into the remote servers ~/.ssh/authorized_keys file -- Cheers Malcolm °¿° (Linux Counter #276890) openSUSE 12.2 (x86_64) Kernel 3.4.11-2.16-desktop up 2 days 1:28, 4 users, load average: 0.43, 0.19, 0.16 CPU Intel i5 CPU M520(a)2.40GHz | Intel Arrandale GPU -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 1