Robert Connolly wrote:
> Do any of you know assembly well enough to convert this:
It has been a few years.
> http://www.linuxfromscratch.org/~robert/new/dd.asm
> to something gcc can compile?
Are you looking to convert this to 'C' or just strip the unnecessary code
And remove all the options
Do any of you know assembly well enough to convert this:
http://www.linuxfromscratch.org/~robert/new/dd.asm
to something gcc can compile? And remove all the options, making bs=1 the
default, and 'dd from-file to-file' the only thing it does.
robert
pgp81S3OfJ8HD.pgp
Description: PGP signature
-
Dan Nicholson wrote:
> On 5/23/07, taipan67 <[EMAIL PROTECTED]> wrote:
>
>> The IPRoute2-2.6.20-070313 tarball contains :- man/man8/tc-bfifo.8 &
>> man/man8/tc-pfifo.8, the latter being a symlink to the former.
>>
>> Makefile installs both, then overwrites them with symlinks to
>> tc-pbfifo.8, w
On 5/23/07, taipan67 <[EMAIL PROTECTED]> wrote:
> The IPRoute2-2.6.20-070313 tarball contains :- man/man8/tc-bfifo.8 &
> man/man8/tc-pfifo.8, the latter being a symlink to the former.
>
> Makefile installs both, then overwrites them with symlinks to
> tc-pbfifo.8, which doesn't exist.
>
> My soluti
The IPRoute2-2.6.20-070313 tarball contains :- man/man8/tc-bfifo.8 &
man/man8/tc-pfifo.8, the latter being a symlink to the former.
Makefile installs both, then overwrites them with symlinks to
tc-pbfifo.8, which doesn't exist.
My solution is to :-
rm man/man8/tc-pfifo.8 && mv man/man8/tc-bfif
On Wed, May 23, 2007 at 01:59:48PM +0200, Jens Stroebel wrote:
> Bryan Kadzban wrote:
>
> > Hmm. I figured they'd show up on a different bus, since it is really a
> > different physical bus. Well, whatever. I'd still like to know where
> > the device symlink points though. :-)
>
> I'm not sur
Bryan Kadzban wrote:
~snip~
>
> Hmm. I figured they'd show up on a different bus, since it is really a
> different physical bus. Well, whatever. I'd still like to know where
> the device symlink points though. :-)
>
>
I seem to remember when I had a laptop that I used a pcmcia network card
Bryan Kadzban wrote:
> Hmm. I figured they'd show up on a different bus, since it is really a
> different physical bus. Well, whatever. I'd still like to know where
> the device symlink points though. :-)
I'm not sure which one... you mean like:
ls -l /sys/class/net/eth1/device
Jens Stroebel wrote:
> Bryan Kadzban wrote:
>> Would it work to use by-path persistence? That's not supported in
>> the book or by the udev developers because (e.g.) USB devices
>> change their paths way too often. But if these laptops only have
>> one PCMCIA slot, then that might work.
>
> Havi
Bryan Kadzban wrote:
> On Tue, May 22, 2007 at 06:03:39PM +0200, Jens Stroebel wrote:
>> On Mon, May 21, 2007 at 06:22:07PM -0400, Bryan Kadzban wrote:
>>
>>> (Why do you want it, by the way?)
>> That's because we install a laptop with a pcmcia-plugged network card.
>> Should someone at a later tim
10 matches
Mail list logo
