[gentoo-user] mkfs.btrfs check for bad blocks - howto
Hi, when creating a file system on a partition on a brand new hard disk, I have always used the '-c' twice to check for bad blocks. This works for ext3 and ext4. Now, I'd like to use a btrfs file system on some partitions but the '-c' option (to mkfs.btrfs or mkbtrfs) seems to have gone. What can I do about this? Many thanks for a hint, Helmut. -- Helmut Jarausch Lehrstuhl fuer Numerische Mathematik RWTH - Aachen University D 52056 Aachen, Germany
Re: [gentoo-user] mkfs.btrfs check for bad blocks - howto
On Thursday 10 June 2010 11:15:17 Helmut Jarausch wrote: Hi, when creating a file system on a partition on a brand new hard disk, I have always used the '-c' twice to check for bad blocks. This works for ext3 and ext4. Now, I'd like to use a btrfs file system on some partitions but the '-c' option (to mkfs.btrfs or mkbtrfs) seems to have gone. What can I do about this? Many thanks for a hint, Helmut. Hi Helmut, You could either first use mkfs for ext3 or 4 to check, or you could run badblock manually over the partition first to check. -- Joost
Re: [gentoo-user] mkfs.btrfs check for bad blocks - howto
On 10 Jun, J. Roeleveld wrote: On Thursday 10 June 2010 11:15:17 Helmut Jarausch wrote: Hi, when creating a file system on a partition on a brand new hard disk, I have always used the '-c' twice to check for bad blocks. This works for ext3 and ext4. Now, I'd like to use a btrfs file system on some partitions but the '-c' option (to mkfs.btrfs or mkbtrfs) seems to have gone. What can I do about this? Many thanks for a hint, Helmut. Hi Helmut, You could either first use mkfs for ext3 or 4 to check, or you could run badblock manually over the partition first to check. Thanks, Joost, but I don't know how to feed the output of badblocks to mkbtrfs. It looks as if btrfs cannot use a bad block list. Is that true? Helmut.
Re: [gentoo-user] Re: Strange python-updater error
Am 10.06.2010 07:36, schrieb Dale: To think the devs didn't believe this was going to cause some confusion. There is a news regarding python 3 after the install of python 3. It clearly says that is ok to have both installed parallel, and runnig python-updater is recommended, but you should never ever set python 3 as system default until further notice. On the dev-list putting python 3 into stable and how to handle it was debated with many powerful emotions assigned. They knew what they did.. If how they handled that problem is good or not is a other pair of shoes. Greetings Sebastian
Re: [gentoo-user] mkfs.btrfs check for bad blocks - howto
Helmut Jarausch writes: On 10 Jun, J. Roeleveld wrote: You could either first use mkfs for ext3 or 4 to check, or you could run badblock manually over the partition first to check. Thanks, Joost, but I don't know how to feed the output of badblocks to mkbtrfs. It looks as if btrfs cannot use a bad block list. Is that true? Isn't this obsolete nowadays? SMART capable drives should remap bad sectors automatically and replace them by spare sectors. Running badblocks -n might be necessary though in order to make the drive acess every block. So I would not trust a drive any more that actually still shows bad blocks. Wonko
Re: [gentoo-user] Re: Strange python-updater error
Sebastian Beßler wrote: Am 10.06.2010 07:36, schrieb Dale: To think the devs didn't believe this was going to cause some confusion. There is a news regarding python 3 after the install of python 3. It clearly says that is ok to have both installed parallel, and runnig python-updater is recommended, but you should never ever set python 3 as system default until further notice. On the dev-list putting python 3 into stable and how to handle it was debated with many powerful emotions assigned. They knew what they did.. If how they handled that problem is good or not is a other pair of shoes. Greetings Sebastian Yep, I was part of that discussion so I know about it. News item or not, marking something as stable still confuses people when you are then told you can't use it. With most packages it would not matter much but when very little can use this package, it is sort of silly. Dale :-) :-)
[gentoo-user] ethernet not working on new laptop (dell e6510)
I just purchased a dell latitude E6510, with a gigabit (hardwired) ethernet. It works fine under windows. I now have the (newest) gentoo installation disk (april) in the machine. The device is recognized and the e1000e module is loaded. ifconfig shows the mac address, but no IP addr. My router (linksys with the tomato firmware) shows that same mac address (presumably gotten when the windows machine was connected). If I run net-setup eth0, nothing changes. If I execute the manual ifconfig eth0 192.168.1.80 broadcast 192.168.1.255 netmask 255.255.255.0 up subsequent ifconfig's show this data but ping 192.168.1.1 (the IP addr of the router) fails However, 192.168.1.80 succeeds. Any help would be appreciated. thanks, allan
Re: [gentoo-user] ethernet not working on new laptop (dell e6510)
At Thu, 10 Jun 2010 17:59:56 -0400 cov...@ccs.covici.com wrote: Allan Gottlieb gottl...@nyu.edu wrote: At Thu, 10 Jun 2010 15:19:58 -0400 cov...@ccs.covici.com wrote: Try dhcpcd or pump manually -- I bet its some imcompatibility between the software and the router. I tried dhcpcd and it times out on waiting for carrier. pump is not on the gentoo installation disk. Thanks for the advice; I will try grml next. This dhcp bug is a bug I have reported, bug # 284631 -- please add your comments to this bug -- including dhcp version, router brand, etc. Done. (I can't find the dhcp version and can't boot it now since I have grml booted). For grml I needed to turn off framebuffer and some acpi stuff. But it has booted and I am starting to prepare the hard disk. Thanks for sending me to grml. allan
Re: [gentoo-user] ethernet not working on new laptop (dell e6510)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Em 10-06-2010 15:28, Allan Gottlieb escreveu: I just purchased a dell latitude E6510, with a gigabit (hardwired) ethernet. It works fine under windows. I now have the (newest) gentoo installation disk (april) in the machine. The device is recognized and the e1000e module is loaded. ifconfig shows the mac address, but no IP addr. My router (linksys with the tomato firmware) shows that same mac address (presumably gotten when the windows machine was connected). If I run net-setup eth0, nothing changes. If I execute the manual ifconfig eth0 192.168.1.80 broadcast 192.168.1.255 netmask 255.255.255.0 up subsequent ifconfig's show this data but ping 192.168.1.1 (the IP addr of the router) fails However, 192.168.1.80 succeeds. Any help would be appreciated. thanks, allan Maybe the system don't know the router. try this, in addiction of ifconfig *route add default gw **192.168.1.1 *Good Luck! -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.15 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkwRQx8ACgkQ35zeJy7JhCgAKgCgozrtlXJxZsj6bktO4P/MOCOk 15UAnjhtiwmWWmh+el1LyOdT2vkVjVAl =O5h5 -END PGP SIGNATURE-
Re: [gentoo-user] ethernet not working on new laptop (dell e6510)
At Thu, 10 Jun 2010 15:08:49 -0400 bjloc...@lockie.ca wrote: I just purchased a dell latitude E6510, with a gigabit (hardwired) ethernet. It works fine under windows. I now have the (newest) gentoo installation disk (april) in the machine. The device is recognized and the e1000e module is loaded. ifconfig shows the mac address, but no IP addr. My router (linksys with the tomato firmware) shows that same mac address (presumably gotten when the windows machine was connected). If I run net-setup eth0, nothing changes. If I execute the manual ifconfig eth0 192.168.1.80 broadcast 192.168.1.255 netmask 255.255.255.0 up subsequent ifconfig's show this data but ping 192.168.1.1 (the IP addr of the router) fails However, 192.168.1.80 succeeds. Run 'lspci'. Thanks. I just now did and it confirms the intel gigabit controller and (when run with -v) that the e1000e driver is being used. But I don't see what to do next. allan
Re: [gentoo-user] ethernet not working on new laptop (dell e6510)
At Thu, 10 Jun 2010 15:19:58 -0400 cov...@ccs.covici.com wrote: Allan Gottlieb gottl...@nyu.edu wrote: I just purchased a dell latitude E6510, with a gigabit (hardwired) ethernet. It works fine under windows. I now have the (newest) gentoo installation disk (april) in the machine. The device is recognized and the e1000e module is loaded. ifconfig shows the mac address, but no IP addr. My router (linksys with the tomato firmware) shows that same mac address (presumably gotten when the windows machine was connected). If I run net-setup eth0, nothing changes. If I execute the manual ifconfig eth0 192.168.1.80 broadcast 192.168.1.255 netmask 255.255.255.0 up subsequent ifconfig's show this data but ping 192.168.1.1 (the IP addr of the router) fails However, 192.168.1.80 succeeds. I have the same machine for a while -- returning for audio issues -- and loaded grml 10.4 live cd and had no problems with the dhcp. Encouraging. Try dhcpcd or pump manually -- I bet its some imcompatibility between the software and the router. I tried dhcpcd and it times out on waiting for carrier. pump is not on the gentoo installation disk. Thanks for the advice; I will try grml next. allan
Re: [gentoo-user] ethernet not working on new laptop (dell e6510)
At Thu, 10 Jun 2010 16:55:11 -0300 Zhu Sha Zang zhushaz...@yahoo.com.br wrote: Em 10-06-2010 15:28, Allan Gottlieb escreveu: I just purchased a dell latitude E6510, with a gigabit (hardwired) ethernet.? It works fine under windows. I now have the (newest) gentoo installation disk (april) in the machine. The device is recognized and the e1000e module is loaded. ifconfig shows the mac address, but no IP addr. My router (linksys with the tomato firmware) shows that same mac address (presumably gotten when the windows machine was connected). If I run net-setup eth0, nothing changes. If I execute the manual ifconfig eth0 192.168.1.80 broadcast 192.168.1.255 netmask 255.255.255.0 up subsequent ifconfig's show this data but ping 192.168.1.1 (the IP addr of the router) fails However, 192.168.1.80 succeeds. Any help would be appreciated. thanks, allan Maybe the system don't know the router. try this, in addiction of ifconfig *route add default gw **192.168.1.1 I had tried that (the handbook suggested it). I assume you meant the *'s for emphasis not to be entered *Good Luck! I may need it! allan
Re: [gentoo-user] ethernet not working on new laptop (dell e6510)
Allan Gottlieb gottl...@nyu.edu wrote: At Thu, 10 Jun 2010 15:19:58 -0400 cov...@ccs.covici.com wrote: Allan Gottlieb gottl...@nyu.edu wrote: I just purchased a dell latitude E6510, with a gigabit (hardwired) ethernet. It works fine under windows. I now have the (newest) gentoo installation disk (april) in the machine. The device is recognized and the e1000e module is loaded. ifconfig shows the mac address, but no IP addr. My router (linksys with the tomato firmware) shows that same mac address (presumably gotten when the windows machine was connected). If I run net-setup eth0, nothing changes. If I execute the manual ifconfig eth0 192.168.1.80 broadcast 192.168.1.255 netmask 255.255.255.0 up subsequent ifconfig's show this data but ping 192.168.1.1 (the IP addr of the router) fails However, 192.168.1.80 succeeds. I have the same machine for a while -- returning for audio issues -- and loaded grml 10.4 live cd and had no problems with the dhcp. Encouraging. Try dhcpcd or pump manually -- I bet its some imcompatibility between the software and the router. I tried dhcpcd and it times out on waiting for carrier. pump is not on the gentoo installation disk. Thanks for the advice; I will try grml next. This dhcp bug is a bug I have reported, bug # 284631 -- please add your comments to this bug -- including dhcp version, router brand, etc. -- Your life is like a penny. You're going to lose it. The question is: How do you spend it? John Covici cov...@ccs.covici.com
Re: [gentoo-user] ethernet not working on new laptop (dell e6510)
Allan Gottlieb gottl...@nyu.edu wrote: I just purchased a dell latitude E6510, with a gigabit (hardwired) ethernet. It works fine under windows. I now have the (newest) gentoo installation disk (april) in the machine. The device is recognized and the e1000e module is loaded. ifconfig shows the mac address, but no IP addr. My router (linksys with the tomato firmware) shows that same mac address (presumably gotten when the windows machine was connected). If I run net-setup eth0, nothing changes. If I execute the manual ifconfig eth0 192.168.1.80 broadcast 192.168.1.255 netmask 255.255.255.0 up subsequent ifconfig's show this data but ping 192.168.1.1 (the IP addr of the router) fails However, 192.168.1.80 succeeds. I have the same machine for a while -- returning for audio issues -- and loaded grml 10.4 live cd and had no problems with the dhcp. Try dhcpcd or pump manually -- I bet its some imcompatibility between the software and the router. -- Your life is like a penny. You're going to lose it. The question is: How do you spend it? John Covici cov...@ccs.covici.com
Re: [gentoo-user] ethernet not working on new laptop (dell e6510)
I just purchased a dell latitude E6510, with a gigabit (hardwired) ethernet. It works fine under windows. I now have the (newest) gentoo installation disk (april) in the machine. The device is recognized and the e1000e module is loaded. ifconfig shows the mac address, but no IP addr. My router (linksys with the tomato firmware) shows that same mac address (presumably gotten when the windows machine was connected). If I run net-setup eth0, nothing changes. If I execute the manual ifconfig eth0 192.168.1.80 broadcast 192.168.1.255 netmask 255.255.255.0 up subsequent ifconfig's show this data but ping 192.168.1.1 (the IP addr of the router) fails However, 192.168.1.80 succeeds. Any help would be appreciated. thanks, allan Run 'lspci'.
[gentoo-user] OT/2: netgrapgh, l2tpv3
Good afternoon, community. Whether there is a free alternative netgrapgh (freebsd) in linux? And still, whether it is possible on linux to use l2tpv3 tunnels? -- Best regards, Vince Mallow xmpp: w...@jabber.slan.ru web: http://gentoo-way.blogspot.com
