Nios® V/II Embedded Design Suite (EDS)
Support for Embedded Development Tools, Processors (SoCs and Nios® V/II processor), Embedded Development Suites (EDSs), Boot and Configuration, Operating Systems, C and C++

tinylogin enable issue

Altera_Forum
Honored Contributor II
1,229 Views

Hello Hippo, 

 

Using buildroot guide step-14. 

 

I got the image for tftpd and tinylogin. 

I kept those images from romfs to rootfs dir respectively. 

 

1.) I wrote "ttys0:vt100:/bin/agetty 115200 ttys0" in rootfs/etc/inittab for tinylogin. 

After kernel boot process the login process didn't come. 

what should I do now. 

 

2.) To compile ssl, ssh and sshd as statically the changes require in Makefile. 

Kindly explain it? 

 

3.) Using inetd patch reference, I made change in tftpd/Makefile. It create the  

Image successfully. 

I tried to write the patch for that. but I am unable. 

can I send the modified telnetd/Makefile to you for mx140apps.diff updation. 

 

Kindly acknowledge me. 

 

 

thanks & regard, 

Goutam
0 Kudos
2 Replies
Altera_Forum
Honored Contributor II
311 Views

 

--- Quote Start ---  

originally posted by goutam_kumar@May 15 2006, 06:58 PM 

hello hippo, 

 

using buildroot guide step-14. 

 

i got the image for tftpd and tinylogin. 

i kept those images from romfs to rootfs dir respectively. 

 

1.) i wrote "ttyS0:vt100:/bin/agetty 115200 ttyS0[/b]" in rootfs/etc/inittab for tinylogin. 

After kernel boot process the login process didn't come. 

what should I do now. 

 

2.) To compile ssl, ssh and sshd as statically the changes require in Makefile. 

Kindly explain it? 

 

3.) Using inetd patch reference, I made change in tftpd/Makefile. It create the  

Image successfully. 

I tried to write the patch for that. but I am unable. 

can I send the modified telnetd/Makefile to you for mx140apps.diff updation. 

 

Kindly acknowledge me. 

 

 

thanks & regard, 

Goutam 

<div align='right'><{post_snapback}> (index.php?act=findpost&pid=15378) 

--- Quote End ---  

[/b] 

--- Quote End ---  

 

1. check if you have the right tty devices, jtag uart or serial uart have different device number. 

2. you should compile openssl lib in buildroot, but tftpd, ssh and sshd in uClinux-dist. 

I shall include the patches of openssl and zlib to buildroot.diff, if I can find some spare time. 

3. thank you, please post as attachment in the buildroot guide thread. 

I am thinking of drop the mx140apps and use only uClinux-dist for apps. How do you think?
0 Kudos
Altera_Forum
Honored Contributor II
311 Views

 

--- Quote End ---  

 

I am thinking of drop the mx140apps and use only uClinux-dist for apps. How do you think? 

<div align='right'><{post_snapback}> (index.php?act=findpost&pid=15393)</div> 

 

 

--- Quote End ---  

 

Hello Hippo, 

 

First of-all thanks for apreciating my suggestion. 

I think it will be a good option. because we want to enable apps. but for different apps have work with both dir apps/ and uClinux-dist/. 

 

Kindly add the patch to mx140apps.diff as patch for telnetd 

******************************************************************************** 

*** 

The below is telnetd-Makefile modified version (modified by Goutam) 

******************************************************************************** 

***# # configurable options# - set DEBUG = 1 to turn on debugging support#  

DEBUG = 0 

PROJ_NAME = telnetd 

INSTALL_DIR = ~/rootfs 

PROGS := $(PROJ_NAME) 

CFLAGS += -O2 

CROSS := nios2-linux-uclibc- 

CC := $(CROSS)gcc 

# # You should not need to modify anything beyond this point#  

 

FLTFLAGS := -s 8192 

CFLAGS += -DPARANOID_TTYS  

-DTERMCAP  

-DUSE_TERMIO  

-DKLUDGELINEMODE  

-D_GNU_SOURCE 

 

OBJS = global.o logwtmp.o state.o telnetd.o termstat.o  

authenc.o logout.o slc.o sys_term.o utility.o 

 

all: $(PROGS) 

 

$(PROJ_NAME): $(OBJS) 

$(CC) -elf2flt="$(FLTFLAGS)" -o $@ $^ 

 

.PHONY: clean 

clean: 

-rm -f *.[oad] *.gdb $(PROJ_NAME) 

 

.PHONY: install 

install: all 

ifeq "$(INSTALL_DIR)" "" 

$(error No installation directory specified) 

endif 

mkdir -p $(INSTALL_DIR)/bin 

install -v $(PROGS) $(INSTALL_DIR)/bin 

******************************************************************************** 

***
0 Kudos
Reply